I have a vi written for the CFP-2110. It reads values from a set uf CFP-AI-110 analog input blocks and writes values to a cfp-do-401. The program has two timed loops, one to read and record values at 6 hz, and another to control three outputs on the DO-401 to move a cylinder back and forth for some lifecycle testing.
When I run the program during development on the PC it works fine, stops at the end of the cycles I set, etc. When I build and set it to run at startup, and connect to the CFP-2210 with a web browser, it also runs fine and stops like it should as long as a remain in "control" of it on the web browser. However, when I start it, then release control and just monitor it, it will not stop like it should. The controls on the User interface indicate that iot stopped, but the cycling keeps going and it keeps counting. As soon as I do a request control in the browser, it stops as it should.
What is the difference between "controlling" and monitoring when it comes to program execution? I plan to leave this running unattended and I really need it to stop on time.
Thanks for any info that might pertain to this.
Solved! Go to Solution.
Seems that when monitoring only, when I set the property node "value" of the control, the control appears to change, but the actual values does not in the program. When I "request control", the value then changes. If I re-load the web page, the controls "indication" goes back to the original state.
If in my program I write a False to the property node of a switch control, the control will appear to turn off, however, apparently the value it supplies continues to be True. If I re-load the web page, it appears to turn back on. If I do a request control, it appears to turn off and the values is then False.
What I did to resolve this is create local variables from the controls I needed to operate programmatically and write to them. Instead of using the Value property node. It works fine now.