LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

While loop and for loop condition terminal

Hello friends,

 

I am using labview 8.6. The condition terminal of the while loop and conditional for loop is behaving in just the opposite way.

When i wire a true to the condition terminal of my loop, the while loop continues to run when I click on run. when I wire a FALSE, it stops.

 

Is there any setting change that I have to make it to get it work properly.

 

Please suggest on this.

 

Thanks and regards,

Herok

0 Kudos
Message 1 of 9
(4,194 Views)
You can change the behaviour of the loop condition terminal from the right click menu of the terminal.
--
Tomi Maila
0 Kudos
Message 2 of 9
(4,191 Views)

Hi Tomi,

 

Thanks for your quick reply. It is not the question of conditional terminal. Let me explain my problem better.

 

Please have a look at the attachment that I am sending. For both the loops, the condition is CONTINUE if TRUE but in my case, both the loops are showing opposite behaviours as mentioned in the figure.

 

Can you please let me know what change should I make in the settings.

 

Thanks in advance.

 

Regards,

Herok

0 Kudos
Message 3 of 9
(4,183 Views)

Hi Tomi,

 

Thanks for your quick reply. It is not the question of conditional terminal. Let me explain my problem better.

 

Please have a look at the attachment that I am sending. For both the loops, the condition is CONTINUE if TRUE but in my case, both the loops are showing opposite behaviours as mentioned in the figure.

 

Can you please let me know what change should I make in the settings.

 

Thanks in advance.

 

Regards,

Herok

0 Kudos
Message 4 of 9
(4,178 Views)

Photoshopped!!

 

Seriously now, your understanding is correct and that behavior is not. Can you attach a VI that does this?

Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
For he does not know what will happen; So who can tell him when it will occur? Eccl. 8:7

0 Kudos
Message 5 of 9
(4,168 Views)

Hello JCarmody,

 

Thanks for  your reply.

 

I am sending you the VI. I am not sure if this would help you because only in 2 computers this behaviour is seen. In others, it works as it is supposed to work.

 

This is strange but true. So I was thinking if there are any settings change that someone has made by mistake. I am not able to find any such settings.

 

Regards,

Herok

 

 

0 Kudos
Message 6 of 9
(4,163 Views)
Well, seems like in the example VI both are while loops and for me both work as expected. I didn't have 8.6 installed though.
--
Tomi Maila
0 Kudos
Message 7 of 9
(4,151 Views)

Herok wrote:

Hello JCarmody,

 

Thanks for  your reply.

 

I am sending you the VI. I am not sure if this would help you because only in 2 computers this behaviour is seen. In others, it works as it is supposed to work.

 

This is strange but true. So I was thinking if there are any settings change that someone has made by mistake. I am not able to find any such settings.

 

Regards,

Herok

 

 


Autogrow.PNG

Herok-

here is an example of code that behaves like you describe.  The not (hidden in the second loop) also has its output wire hidden by the input wire.  To find out if you have hidden functions select the loop right-click and enable the "Autogrow" property.   You can also configure the LabVIEW.ini to place structures with or without Autogrow enabled (Tools>Options>Block Diagram> about halfway down the page.


"Should be" isn't "Is" -Jay
0 Kudos
Message 8 of 9
(4,139 Views)

Please do NOT attach .bmp images with the extension changed to .jpg to circumvent the forum filters!

 

 


Herok wrote:

I am sending you the VI. I am not sure if this would help you because only in 2 computers this behaviour is seen. In others, it works as it is supposed to work.


 

Whatever you are seeing must be due to some corruption or folding error. It all works fine here.

 

To make sure there are no hidden objects, simply press the cleanup button which would reveal any extra stuff (which is obviously not there). Does it fix itself if you click the termination terminal an even number of times? What if you remove the bad loop and create a new one?

 

Could it be you have some problems with the graphics card and the icon of the conditional terminal does not update correctly?

 

Whay happens if you connect a control instead of a diagram constant?

 

What is different on the computers where it acts incorrectly (different CPU (brand, model), #of cores, etc.) 

Message 9 of 9
(4,136 Views)