News:

  • June 26, 2026, 03:58:14 PM

Login with username, password and session length

« previous next »
Pages: [1]

Author Topic: DoMore power up state  (Read 16497 times)

CReese

  • Hero Member
  • *****
  • Posts: 184
DoMore power up state
« on: May 27, 2014, 01:53:07 PM »
Hello,

From the manual, a DoMore should power up in the same mode that it was in when it lost power. I am finding, however, that after power loss I often get a processor that comes up in Program Mode when it was in Run Mode before power down. Needless to say, in systems where power loss is frequent, this is a serious issue. How can I troubleshoot this?

Thanks,
Colin
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6161
  • Yes Pinky, Do-more will control the world!
Re: DoMore power up state
« Reply #1 on: May 27, 2014, 11:21:51 PM »
There are a few things that prevent return to RUN mode.
1. Any I/O change, even in auto config mode.
2. An I/O module failure.
3. Ethernet remote base offline.
4. Loss of retentive memory due to a bad battery.

Do you have any error or warning indications? Are there any interesting log entries like indication of an I/O config change or retentive memory initialization?
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

CReese

  • Hero Member
  • *****
  • Posts: 184
Re: DoMore power up state
« Reply #2 on: June 10, 2014, 12:33:21 PM »
I have all sorts of warnings, but these are due to things that are not problems, e.g. using retentive elements in stages. Will these prevent start-up in run mode? Also, are start-up errors logged?
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6161
  • Yes Pinky, Do-more will control the world!
Re: DoMore power up state
« Reply #3 on: June 10, 2014, 12:41:02 PM »
I referring to the system log on the Event Logs page of the System Information dialog. If the retentive memory was wiped or there were I/O change notices, they will be flagged there.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

CReese

  • Hero Member
  • *****
  • Posts: 184
Re: DoMore power up state
« Reply #4 on: September 16, 2014, 12:25:33 PM »
I just had this happen again on a boat. Big problem-o. I will follow this advice and check the logs ...

Colin
Logged

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6161
  • Yes Pinky, Do-more will control the world!
Re: DoMore power up state
« Reply #5 on: September 16, 2014, 01:23:58 PM »
Help me understand what happened and I can likely propose solutions.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

CReese

  • Hero Member
  • *****
  • Posts: 184
Re: DoMore power up state
« Reply #6 on: September 16, 2014, 02:08:31 PM »
Not sure I see anything that sticks out here. I suppose after the new program was put in (S1521), it could have been in program mode until it was power cycled? It's possible that the Run status was not noticed, as the stale data was not in an alarm state, and then when it was power cycled it was noticed, as the contacts are normally closed. I'll continue to power cycle the thing and see if I see it again.

S1503, Thu Sep 11 19:38:56 2014, Default User updated the PLC gate array
S1504, Thu Sep 11 19:39:54 2014, Default User changed mode to RUN
S1505, Thu Sep 11 21:26:54 2014, Default User changed mode to PROGRAM
S1506, Thu Sep 11 21:26:58 2014, System content changed by Default User (Program/SysConfig/Documentation)
S1507, Thu Sep 11 21:27:02 2014, Default User changed mode to RUN
S1508, Thu Sep 11 21:27:37 2014, System content changed by Default User (Program)
S1509, Thu Sep 11 21:30:06 2014, System content changed by Default User (Program)
S1510, Thu Sep 11 21:30:58 2014, System content changed by Default User (Program)
S1511, Thu Sep 11 21:31:40 2014, System content changed by Default User (Program)
S1512, Thu Sep 11 21:32:12 2014, System content changed by Default User (Program)
S1513, Thu Sep 11 21:40:35 2014, System content changed by Default User (Program/Documentation)
S1514, Thu Sep 11 21:42:21 2014, System content changed by Default User (Program/Documentation)
S1515, Thu Sep 11 21:45:03 2014, System content changed by Default User (Program/Documentation)
S1516, Thu Sep 11 21:55:21 2014, System content changed by Default User (Program/Documentation)
S1517, Thu Sep 11 22:33:25 2014, System content changed by Default User (Program/Documentation)
S1518, Thu Sep 11 22:44:41 2014, System content changed by Default User (Program/Documentation)
S1519, Sat Sep 13 01:26:10 2014, System content changed by Default User (Program)
S1520, Mon Sep 15 19:34:51 2014, System content changed by Default User (Program)
S1521, Mon Sep 15 19:46:05 2014, System content changed by Default User (Program/Documentation)
S1522, Tue Sep 16 16:20:37 2014, System was turned off
S1523, Tue Sep 16 16:20:46 2014, System was turned on
S1524, Tue Sep 16 16:20:52 2014, PLC rebooted following hardware watchdog timeout.
S1525, Tue Sep 16 16:20:52 2014, System was turned off
S1526, Tue Sep 16 16:20:52 2014, System was turned on
S1527, Tue Sep 16 16:20:57 2014, PLC rebooted following hardware watchdog timeout.
S1528, Tue Sep 16 16:20:57 2014, System was turned off
S1529, Tue Sep 16 16:20:57 2014, System was turned on
S1530, Tue Sep 16 16:21:02 2014, PLC rebooted following hardware watchdog timeout.
S1531, Tue Sep 16 16:21:02 2014, System was turned off
S1532, Tue Sep 16 16:21:02 2014, System was turned on
S1533, Tue Sep 16 16:21:07 2014, PLC rebooted following hardware watchdog timeout.
S1534, Tue Sep 16 16:21:07 2014, System was turned off
S1535, Tue Sep 16 16:21:07 2014, System was turned on
S1536, Tue Sep 16 16:21:12 2014, PLC rebooted following hardware watchdog timeout.
S1537, Tue Sep 16 16:21:12 2014, System was turned off
S1538, Tue Sep 16 16:21:12 2014, System was turned on
S1539, Tue Sep 16 16:21:17 2014, PLC rebooted following hardware watchdog timeout.
S1540, Tue Sep 16 16:21:17 2014, System was turned off
S1541, Tue Sep 16 16:21:17 2014, System was turned on
S1542, Tue Sep 16 16:21:23 2014, PLC rebooted following hardware watchdog timeout.
S1543, Tue Sep 16 16:21:23 2014, System was turned off
S1544, Tue Sep 16 16:21:23 2014, System was turned on
S1545, Tue Sep 16 16:21:28 2014, PLC rebooted following hardware watchdog timeout.
S1546, Tue Sep 16 16:21:28 2014, System was turned off
S1547, Tue Sep 16 16:21:28 2014, System was turned on
S1548, Tue Sep 16 16:21:33 2014, PLC rebooted following hardware watchdog timeout.
S1549, Tue Sep 16 16:21:33 2014, System was turned off
S1550, Tue Sep 16 16:21:33 2014, System was turned on
S1551, Tue Sep 16 16:21:38 2014, PLC rebooted following hardware watchdog timeout.
S1552, Tue Sep 16 16:21:38 2014, System was turned off
S1553, Tue Sep 16 16:21:38 2014, System was turned on
S1554, Tue Sep 16 16:49:29 2014, Default User changed mode to RUN
S1555, Tue Sep 16 16:51:12 2014, System was turned off
S1556, Tue Sep 16 16:51:30 2014, System was turned on
Logged

CReese

  • Hero Member
  • *****
  • Posts: 184
Re: DoMore power up state
« Reply #7 on: September 16, 2014, 02:09:36 PM »
The engineer didn't mention that he cycled the power 11 times, but I suppose if it's broken already, it's not hard to imagine reverting to the Windows solution.

C
Logged

plcnut

  • Hero Member
  • *****
  • Posts: 814
    • premiersi.com
Re: DoMore power up state
« Reply #8 on: September 16, 2014, 02:20:22 PM »
If the hardware watchdog times out more than 10 times, the system will go to program mode.
Are you running the latest firmware?
Do you have any EMAIL instructions in your program?

EDIT: The power off/on in the log is due to the hardware timeout, NOT the physical power.
« Last Edit: September 18, 2014, 07:36:08 AM by plcnut »
Logged
Circumstances don't determine who we are, they only reveal it.

~Jason Wolthuis
Premier Systems Integration, LLC
http://premiersi.com

BobO

  • Host Moderator
  • Hero Member
  • *****
  • Posts: 6161
  • Yes Pinky, Do-more will control the world!
Re: DoMore power up state
« Reply #9 on: September 17, 2014, 12:41:14 AM »
As 'nut mentioned, the watchdog reboots are due to a firmware lockup and subsequent recovery. After 10 times, the system refuses to go back to run mode in case it is due to a runaway failure. If it ever gets stuck in a reboot loop, you can't recover it remotely. This prevents that.

This is likely a problem we've already fixed. I would definitely update firmware to the latest.

It is also possible to override the watchdog reboot run mode lockout, by clearing the watchdog reboot count. Can't remember exactly what the variable is, but I'm thinking it is $WatchdogReboots. Just write it to zero in your initialization code, and it will prevent future lockouts. That isn't fixing the cause of the watchdog reboot, but it will prevent it from dropping into program mode. I would encourage you to update the firmware also, since this sounds exactly like a bug 'nut helped us find and fix.
Logged
"It has recently come to our attention that users spend 95% of their time using 5% of the available features. That might be relevant." -BobO

CReese

  • Hero Member
  • *****
  • Posts: 184
Re: DoMore power up state
« Reply #10 on: September 18, 2014, 02:52:32 PM »
will do. thanks for the help!

C
Logged
Pages: [1]
« previous next »