LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Block Diagram is not working properly

Solved!
Go to solution

I do not understand the first method you describe. 

The second method though sounds interesting, I will have a look at it. 

0 Kudos
Message 11 of 26
(862 Views)

1st method: select all the cluster manipulation, but not the property nodes. Select "Create Sub VI". You'll get a Sub VI with an input and output cluster, that will fit the property nodes.

 

2nd method: more or less the same, but include the property nodes in the selection.

0 Kudos
Message 12 of 26
(847 Views)

@GerdW wrote:

 

Right now it's already 31888 pixels wide…

 


Depending on where the origin is, you are already outside the valid range. (details)

Message 13 of 26
(841 Views)

Is there a limitation on the length or on the width of the block diagram?

How did you come up with the amount of pixels?

 

Thanks.

 

0 Kudos
Message 14 of 26
(831 Views)

@akara wrote:

Is there a limitation on the length or on the width of the block diagram?

How did you come up with the amount of pixels?


Just go read the article Altenbach already linked to.  It will answer all of your questions on block diagram size.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 15 of 26
(827 Views)

Hi akara,

 

you can check those items in the VI profiling tool. Don't forget to make those block diagram properties visible...

Best regards,
GerdW


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

Of course the simplest (and ugliest) solution is to (I know you'll going to regret this, and I might as well)...

 

Spoiler
Right click those flat sequence frames and convert to stacked sequence frames. Then remove the excessive space with ctrl+alt+mousedrag, or automatic diagram clean up. 

An absolutely very bad bad bad advice, without any doubt (this will have some rational). It will solve your immediate problem though.

 

Please don't think it will make the code better. You should still:

+ continue doing those free courses (wishful thinking),

+ make Sub VI's,

+ stop copying code to replicate behaviour.

Message 17 of 26
(802 Views)

Of course the simplest (and ugliest) solution is to (I know you'll going to regret this, and I might as well)...

 

 

Spoiler
Right click those flat sequence frames and convert to stacked sequence frames. Then remove the excessive space with ctrl+alt+mousedrag, or automatic diagram clean up. 

An absolutely very bad, bad, bad advice (bad), without any doubt (this will have some rational). It will solve your immediate problem though.

 

 

Please don't think it will make the code better. You should still:

+ continue doing those free courses (wishful thinking),

+ make Sub VI's,

+ stop copying code to replicate behaviour.

0 Kudos
Message 18 of 26
(800 Views)

I do not understand what you mean. 

 

Where are you referring to now?

0 Kudos
Message 19 of 26
(774 Views)

Does LabVIEW have a limitation on the amount of graphs that can be used?

 

What about the case they are placed in different tabs, so the amount of pixels remains low?

 

0 Kudos
Message 20 of 26
(772 Views)