The "Send to controller" button in the script editor appears to be
functioning differently than I would have expected. I can see in the
application director that it actually does something, but I would think it
would update the program and it would start running again from the
beginning with the new code...or at least see the new lines.
Test Scenario #1.
1) Created a script with no errors, sent to station, sent to controller,
and performed a download all. Made sure the script was working
by watching the CurrentLine change at the expected intervals.
2) Opened script and introduced a divide be zero equation...then
compiled, saved to station, save to controller.
3) I could see the CurrentLines still changing back and forth at
expected intervals and kept on humming along. The line
with the divide by zero error was executed with no issue. In
other words, it wasn't seen.
4) Performed a download all objects, and the divide by zero
error was caught at the expected CurrentLine when it
got to it. The CurrentLine went to Line E, and then escaped at the
proper time, and went back to Line E at the proper time.
Test Scenario #2:
1) Performed items 1,2,3 from above.
2) Warm booted the controller by pressing the button for a second,
instead of performing a download all objects.
3) The divide by zero error was now cycling.
If a "download all" needs to be performed with every script
change, it would be detrimental to engineering the job, the
jobsite checkout, and servicing it later on when the equipment
might not be allowed to be shut off.
Have a question? Please contact us with details, and we will respond.
Look through existing questions to find popular answers.
Want to know more about Exchange and its possibilities?
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!
Register today for FREE
Already have an account?Log in