LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Block diagram label cannot be displayed

Solved!
Go to solution

In my LabVIEW 2010 project (which I have been using for over ten years) I can no longer display block diagram labels in one particular VI (the main one, about 1.2MB in size, so not one that could be re-created from scratch.

 

Also, if I create a control from the block diagram, I cannot access it on the front panel.  Clicking on "Find Terminal" takes me to the FP but the control is not there and the FP grid is not shown, just a plain background.  It is as if the control is outside the bounds of the FP.

 

This first occurred in the summer of last year and I had to roll back about a month and then re-code.  But the problem has re-occurred.

 

I have been adding in a lot of FP controls over this time - is there some sort of size limit that I am hitting?

 

Has anyone else seen anything like this?

0 Kudos
Message 1 of 9
(376 Views)

Hi D_J,

 


@D_J wrote:

This first occurred in the summer of last year and I had to roll back about a month and then re-code.  But the problem has re-occurred.


Rollback again to a "known working" revision.

I guess you implemented a SCC tool atleast the last time, when you didn't use it anyway?

 


@D_J wrote:

In my LabVIEW 2010 project (which I have been using for over ten years) I can no longer display block diagram labels in one particular VI (the main one, about 1.2MB in size, …

 

I have been adding in a lot of FP controls over this time - is there some sort of size limit that I am hitting?


Size limits exists for the block diagram size, and for the frontpanel size (aka positions of frontpanel elements) too.

If you would tell us your VI metrics we could judge if you hit those limits…

 

Often the VI filesize is also an indicator of "problems to occur". 1.2MB isn't "really large", but it's also not a "tiny" VI…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 9
(370 Views)

Hi GerdW

 

Thanks for the speedy reply.  Yes, I do use SCC.  Here are the VI metrics of the latest (not-working) VI.

 

D_J_1-1737456329209.png

D_J

 

0 Kudos
Message 3 of 9
(364 Views)

Hi D_J,

 

and what about the "VI metrics" found in the Tools->"VI Profile" menu?

This will list fp/bd sizes…

 

7MB block diagram objects? Don't you think it would make sense to split your "one to bind them all" VI into some smaller subVIs?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 9
(353 Views)

Hi GerdW,

 

The majority of the code is in sub VIs (this is my preferred option) but the is still a fair bit in this main VI.

 

I have attached the VI metrics; the VI in question is called "Main Program.vi"

 

D_J

 

 

 

0 Kudos
Message 5 of 9
(349 Views)

Hi D_J,

 

the "Main Program.vi" has a diagram size of 9656×6238 pixels according to your metrics: while this is below the allowed limits (2^15-1=16383) it is quite large. (IMHO it is way too large…)

 

When you somehow managed to introduce an (position) offset to your block diagram objects you easily move out of the allowed range (of 2^15) and so LabVIEW will begin to act strangely - like not being able to show front panel elements belonging to block diagram terminals…

 

I recommend to refactor your Main VI to a reasonable (block diagram) size!

 

Other metrics of the Main VI:

  • >5700 nodes
  • 471 structures and 1450 diagrams
  • 165 controls and 328 indicators
  • ~200 global reads and writes (each)

All those numbers are "big"…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 6 of 9
(336 Views)
Solution
Accepted by topic author D_J

Apologies, but the metrics that I posted were for a working version.  Here is the data for the non-working version.

 

D_J_0-1737460114811.png

 

0 Kudos
Message 7 of 9
(333 Views)

Thank you!

0 Kudos
Message 8 of 9
(329 Views)

Hi Gerd,

 

Just to say "thank you" for your help back in January.  I refactored my main VI into three (two which are primarily UIs, with the main VI now doing the grunt work but without a UI).  Then main VI is about 2/3 of its previous size and I have not seen any re-occurrence of the problems that I posted about.

 

David

Message 9 of 9
(50 Views)