Showing results for 
Search instead for 
Did you mean: 

Motor control and graphs

Hye all

I have a major problem. im using Lv to control a motor and the motor is moving a thermistor. LV is also reading the input from this thermistor and grpahing it. My problem is when the motor is off LV grpahs away perfectly yet when i press the button to turn on the motor it stops graphing and taking data yet if i turn off the motor it starts plotting again. im controlling the motor using a D.A.Q and taking in thermistor outputs with the same D.A.Q.

Any help would be immensly appreciated
Regards Martin Garvey
0 Kudos
Message 1 of 2
Have you tried running with execution highlighting to see where it stalls?

(I don't understand your VI at all, it makes little sense to me. Which button turns the motor on? Why are there 3 different stop buttons? What is the meaning of the two hidden "iteration (0:initialize)" terminals that never get a value? There is data dependency between the two parallel loops (via device #) so the upper loop cannot start until the lower loop finishes Is this as intended? Do you really need to send the PSU Command string with each iteration of the lower loop? What is the difference between the two case structures except for the wait? ...?)
0 Kudos
Message 2 of 2