LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Block diagram messed up


@pincpanter wrote:

 

But probably this will not work.

yes also it doesnt work

 
0 Kudos
Message 11 of 22
(967 Views)

Is it possible for you to attach the actual VI?

0 Kudos
Message 12 of 22
(943 Views)

Actually i cant share all, but i can share a part of the vi. You can find it attached.

0 Kudos
Message 13 of 22
(920 Views)

Hi ocan,

 

LabVIEW comes with several inbuilt tools to "measure" VI quality.

One of them is Tools->Profile->VI metrics…

 

This is its report on your VI:

Your VI clearly is too wide ("Breite" = width)!

LabVIEW only allows (max) 16383 pixels for width and height, the StyleGuide recommends to limit block diagrams to just one screen!

 

Get a working backup of your VI from your backup system (aka SCC tool) and your problem is gone…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 22
(912 Views)

When i check it, it doesnt seen that large.


@GerdW wrote:

 

Get a working backup of your VI from your backup system (aka SCC tool) and your problem is gone…


Also can you please share how to do it?

0 Kudos
Message 15 of 22
(904 Views)

Hi ocan,

 


@truskawka wrote:

When i check it, it doesnt seen that large.


@GerdW wrote:

 

Get a working backup of your VI from your backup system (aka SCC tool) and your problem is gone…


Also can you please share how to do it?


  • Get the backup media, where you stored safe copies of all your work in regular intervals: choose an older revision of your VI from those backups and get it.
  • With SCC tools (Source Code Control) it's much easier: here you can use a menu to "checkout" an older revision of your VIs from your "repository" (terms refer to SVN).

 

When you don't have backups nor did use any SCC system then you learned the importance of both now the hard way!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 16 of 22
(906 Views)

I dont have any backup actually. Is there any way to fix that vi?

0 Kudos
Message 17 of 22
(901 Views)

Hi ocan,

 


@truskawka wrote:

I dont have any backup actually. Is there any way to fix that vi?


No backups?

You can "fix" this VI by recreating it from scratch… (Use the documentation you wrote for your VI or whole project to remember all the functionality you put into this VI.)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 18 of 22
(897 Views)

unfortunately no. I think i need to start from top

0 Kudos
Message 19 of 22
(890 Views)

Hi ocan,

 


@truskawka wrote:

I think i need to start from top


Before you start coding you should implement a SCC tool. Or atleast setup a backup strategy. Really!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 20 of 22
(882 Views)