LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

2019 LabView Core 1 exercise 8-3 question

Solved!
Go to solution

I am doing exercise 8-3 in 2019 LabView Core 1 and cannot reproduce the same results.

 

According to the tutorial manual, the max and min value outside the loop suppose to show the min and max once i stop the vi, but it doesn't show.

 

It uses the Signal Processing's "Amplitude and Level" and "Array Max & Min" blocks.

ChienNano_1-1588472390688.png

 

 

ChienNano_0-1588472360804.png

 

Could somebody help me and tell me how to fix it? my VI is also attached.

 

Really appreciate,

Chien

0 Kudos
Message 1 of 5
(2,458 Views)

Sorry I am new to this Forum, and I don't know how to start a new post.

Wondering if someone can teach me to start a new post to ask question? I really appreciate.

Also,I am doing exercise 8-3 in 2019 LabView Core 1 and cannot reproduce the same results.

 

According to the tutorial manual, the max and min value outside the loop suppose to show the min and max once i stop the vi, but it doesn't show.

 

It uses the Signal Processing's "Amplitude and Level" and "Array Max & Min" blocks.

ChienNano_1-1588469702931.png

 

ChienNano_0-1588469672381.png

 

Could somebody help me and tell me how to fix it? my VI is also attached.

 

Really appreciate,

Chien

0 Kudos
Message 2 of 5
(2,465 Views)
Solution
Accepted by topic author ChienNano

How are you stopping your VI?

 

Did you use the Stop boolean button control?

Message 3 of 5
(2,440 Views)

Highly appreciate.

I pressed the abort stop button on the top left corner, not the stop button for the while loop.

Now, it works.

0 Kudos
Message 4 of 5
(2,434 Views)

Now you know you can't do that.  That is "Abort" which means stop your code dead in its tracks.  It never has a chance to exit the while loop and update those indicators.

 

The abort button should only be used for runaway code and debugging purposes.  Never in normal operation.

I would have thought the purpose of the button would have been covered in a lesser earlier than #8.

 

Also, the button called "Run Continuously" should be rarely used and only for debugging purposes.  It is helpful for when debugging a subVI that doesn't have a loop  and has a couple inputs and outputs and you want it to keep running while you test out various inputs to see what the resulting output would be.

0 Kudos
Message 5 of 5
(2,370 Views)