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-0045) - This video gives basic information on Using the INTRESUME "Resume Interrupts" 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 will inform the PLC to resume the normal processing of all Interrupt triggers that have been suspended by using the Interrupt Suspend Instruction If interrupt events occur while the interrupts were suspended, they get queued into a pending list based upon the order of priority. This list shows that order of priority. So, if you have this option unchecked and trigger this instruction all pending interrupts will process first based upon this list. Now if do check this box, all pending interrupts that are currently in the pending cue will be cleared and only interrupts from that point on will be processed. This instruction will be used in conjunction with the INT Suspend instruction in order to block out a section of ladder logic that you don’t want interrupted by the interrupt events. This Helps ensure that data being accessed from different places don’t overwrite one another. In normal ladder execution, this data coherency is rarely an issue, but with interrupts it is not only possible, but likely, and can cause some and highly frustrating problems.