Host Engineering Forum

General Category => Do-more CPUs and Do-more Designer Software => Topic started by: CMDRMOORE on November 12, 2012, 07:15:07 PM

Title: ISG-Equipment power interrupted.
Post by: CMDRMOORE on November 12, 2012, 07:15:07 PM
I have a simple $Main program with no other blocks. If the program is running and in another stage other than the ISG, which is SG0, and the power is removed from the PLC, the program will not start at SG0 when power returns. I must place the PLC in Program mode and then return to Run mode to get SG0 to run. This is dangerous on my machine. I was looking into EXIT as a fix, but it cannot execute on power loss and if it is executed every power-up, it loops. Any suggestions?
Title: Re: ISG-Equipment power interrupted.
Post by: franji1 on November 12, 2012, 08:17:55 PM
This issue was addressed in our first maintenance release for both Do-more Designer and in the Do-more firmware.

Go here to download the latest Designer software v 1.0.2.
http://support.automationdirect.com/products/domore.html

Then you will need to update your firmware in your CPU with 1.0.6 of the OS.  This is done from the System Information page.  The link above has a video to show how to update the firmware.

Details on the maintenance release are available here
http://forum.hosteng.com/wndm/updates.pdf
Title: Re: ISG-Equipment power interrupted.
Post by: CMDRMOORE on November 13, 2012, 12:48:25 PM
Thank you. I had upgraded the software but not the firmware.
Title: Re: ISG-Equipment power interrupted.
Post by: franji1 on November 13, 2012, 01:16:12 PM
The firmware change specifically addressed the issue of $Main to ALWAYS run from the "initial stage" after a power-cycle, regardless of the fact that $Main's corresponding PROGRAM stucture is RETENTIVE (i.e. maintains "state" after power loss).  After power-up in RUN mode, the firmware clears all the SG bits in $Main, but maintains the .ScanCounter, .TimeSlice, etc., similar to what it does on a normal PGM->RUN transition.  All other System Tasks are also RETENTIVE

All USER PROGRAM and TASK structures default to being NON-retentive, but can be made retentive using the new check box in the Configure Code Block dialog.