JUMP - Where in the macro they should gobrowsing

If you have noticed in Accelerated macros sometimes the Device Jump is at the end and sometimes its at the beginning of the macro. Now that we are doing a lot of custom programming, it's good to understand why this is and how we should be doing it.

It's actually pretty simple. If the device is being controlled with a standard 1way driver than the Jump can be first. However if you're controlling the device with a 2way module then the Jump needs to be last.