Why you should no longer use DEFINE_PROGRAM and replace with a timeline.
Why you should no longer use define_program in Netlinx
Since the introduction of the NX series controllers we have suggested as a rule that DEFINE_PROGRAM is not used as the interpreter runs very much faster than the NI series controllers did. Using DEFINE_PROGRAM to change variables has shown to cause slowing of the controllers and even interpreter pend causing the controller to no longer run.
What do we recommend you use instead?
This is where timelines really come into their own, with the ability to create, pause, restart and vary the cycle interval, Timelines are a far superior way to handle timed or poll events if needed. Attached to this article is an example of a timeline template, replacing the DEFINE_PROGRAM section of the axs file. This will help with integrating older code with DEFINE_PROGRAM into the NX series environment.