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.
Cookies are not enabled on your browser.
Cookies are required for our site. Please enable cookies in your browser preferences to continue.
AutomationDirect's COVID-19 Related Supply Chain Update currently shows we have our normal high levels of product inventory. Considered an essential business as defined by the CISA, we continue to fill customer orders in accordance with current rulings. Click here to read or download our full statement. (Updated: 6/1/2020)
NOTICE: Due to heavy volume, FedEx and UPS are currently not guaranteeing delivery times. More information can be found at each carrier's website.
Before placing your order, please ensure you will be available to receive packages (and freight when applicable) at your facility.
(VID-DD-0036) - This video gives basic information on Using the GOTO "Go To Label" 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.
** Software Version used in this video: Do-more Designer 2.0.3
This instruction is used to skip over some code and arrive at the label instruction in your code. Once you have skipped to the location of the Label you will then continue on from that point in the ladder code. This instruction can only be used to skip to a label that located within the same Program or Task as the instruction. If the Label that you are skipping to is before this GOTO instruction, this will creating a looping action, and make this a Yielding instruction. With these looping applications it is important to monitor the time slice of your code block and also the demand that this will be placing on the CPU scan time. If this ends up causing issues the best starting places would be to adjust your code block yield settings or your CPU Default watchdog Timeout.