This version of Internet Explorer is either no longer supported by Microsoft, or is obsolete and some features of our store may no longer be supported.
Please consider upgrading or use a different browser.
Carrier service guarantees are now partially active after being suspended last summer.
First, Priority & Standard Overnight service guarantees are now restored for FedEx and UPS.
See FedEx Service Update / UPS Service Alert for additional information.
(VID-DD-0048) - This video gives basic information on Using the JMPI "Indexed Jump" instruction in the Do-more Designer software. It presents information that is commonly missed by users. This WILL NOT be a complete tutorial for the instruction but rather a supplement to the help file and customer experience.
**Prices were valid at the time the video was released and are subject to change.
** Software Version used in this video: Do-more Designer 2.0.3
This instruction is used to transition from one stage to another stage based upon the index number in the instruction. The main functional difference between this instruction and the regular Jump instruction is that is allows for the use of a variable to define the Target stage. This allows for more dynamic control of which stage the program code block will be transitioning to. This index number is not the same as the actual number of the stage but rather the index number within the specified range, in the instruction. So if you had S7 thru S42 as the stage range of this instruction, an index of 0 will jump to S7, an index of 1 to S8 If this index number is out of range of the instruction the stage that the program will jump to is specified here as the Last exception. All Stage programming instructions can only be entered in a Program code block. And jump instructions can only target Stages within the same program code block When this instruction is executed, it does NOT cause an immediate exit of the current stage it only disables the current Stage and enables the target Stage. So, if this jump is triggered, this logic is not skipped and even though it is after the jump in the logic it will be evaluated on the same scan that the jump is triggered. The target stage, if below the jump in the ladder code will be evaluated the same scan that the Jump is triggered. If before in the ladder scan it will be evaluated the next scan on the controller. Once a stage is terminated any out coils will be turned off as part of the termination behavior.