Two problems; first - despite no discernable power outage, diagnostic buffer says "STOP caused by power failure".
Second problem - on restart the PLC goes into STOP mode. The following is from the diagnostic buffer: (remember event 58 occured before event 57)
S7 Diagnostic Buffer said:
Event 57 of 100: Event ID 16# 49A0
STOP caused by parameter assignment error or unpermissible difference between preset and actual configuration: startup disabled
No relevance for user (SDB no.): 1005
Previous operating mode: STOP (internal)
Requested operating mode: STOP (internal)
External error, Incoming event
11:22:29.111 AM 02/24/2009
Event 58 of 100: Event ID 16# 6547
Parameter assignment error assigning parameters to modules (not on P bus, cancel download)
no relevance for user: SDB number: 1005
Operating mode: STOP (internal)
Internal error, Incoming event
11:22:29.026 AM 02/24/2009
I can reproduce this fault by powering the rack off and on again. When I watch the rack power back up, I can see that the CP343-1 appears to have a fault on power up.
So I went to the diag buffer for the CP343-1:-
343-1 diagnostic buffer said:
-----------------------------------------------------------------------
02/03/09 11:25:22
Module type: CP 343-1 IT
Module version: V 2.0.7
Hardware version: 1
Order number: 6GK7 343-1GX11-0XE0
S7 subnet ID of destination network: ---
Address of dest. station
network attachment: 10.96.25.167
Rack: 0
Slot: 4
-----------------------------------------------------------------------
1 ! 01/01/1994 12:00:00.412 AM OMS Event ID: 0xF9C1:0x0301 / 0x00000020
No valid configuration data found.
OMS error code: 0x0020
2 01/01/1994 12:00:00.854 AM Mgt Event ID: 0xF9C1:0x0203 / 0x00000020
Module database invalid.
Internal cause: 0x0020
3 01/01/1984 12:00:00.000 AM Mgt Event ID: 0xF9C1:0x0260 / 0x00000000
The MAC address was fetched from the system SDB. This is the configured address.
4 01/01/1984 12:00:00.000 AM Mgt Event ID: 0xF9C1:0x0254 / 0x00000064
Network interface: Automatic setting, TP/ITP at 100 Mbps full duplex
5 !! 01/01/1984 12:00:00.000 AM Mgt Event ID: 0xF9C1:0x0223 / 0x00020020
Module STOP due to parameter assignment.
6 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x0316 / 0x03EC0000
The CPU containing the SDBs loads an SDB 1004 with assured consistency of type 0x0000; no corresponding SDB of this type was found in the database.
7 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x0319 / 0x03EC0000
The reloaded SDB 1004 was already loaded by the CPU containing the SDBs (SDB type 0x0000); this does not change the consistency of the database.
8 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x0316 / 0x03ED3002
The CPU containing the SDBs loads an SDB 1005 with assured consistency of type 0x3002; no corresponding SDB of this type was found in the database.
9 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x0316 / 0x03EE3100
The CPU containing the SDBs loads an SDB 1006 with assured consistency of type 0x3100; no corresponding SDB of this type was found in the database.
10 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x031C / 0x03EF3118
The SDB 1007 loaded by the CPU containing the SDBs is the consistency assurance SDB (SDB type 0x3118)
11 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x032C / 0x03EF3118
Database now consistent after SDB 1007 was loaded by the CPU containing the SDBs (SDB type 0x3118)
12 01/01/1984 12:00:00.000 AM OMS Event ID: 0xF9C1:0x032D / 0x00000000
The retentive part of the module database will be erased after loading by the CPU module.
13 01/01/1984 12:00:00.000 AM Mgt Event ID: 0xF9C1:0x0260 / 0x00000000
The MAC address was fetched from the system SDB. This is the configured address.
14 01/01/1994 12:00:00.000 AM Time synchronization Event ID: 0xF9C1:0x0619 / 0x00000000
The SIMATIC mode was selected for time-of-day synchronization of the module.
15 01/01/1994 12:08:04.590 AM Mgt Event ID: 0xF9C1:0x0215 / 0x00000000
Downloading the module database causes module restart
16 01/01/1994 12:08:05.666 AM Mgt Event ID: 0xF9C1:0x0254 / 0x00000064
Network interface: Automatic setting, TP/ITP at 100 Mbps full duplex
17 01/01/1994 12:08:08.588 AM Mgt Event ID: 0xF9C1:0x0220 / 0x00000000
I/O enable by S7 CPU
The PLC can be restarted by
twice going from RUN-P to STOP to RUN-P. This appears to confirm that the PLC is not missing any code it needs to restart but I don't understand why it's not restarting automatically.
Before anyone says I need to sort the power supply issues out, I KNOW!!
I need to find out why it won't restart first. (Siemens Tech support, usually excellent IMHO, told me not to investigate further until I sorted out power. So if your car won't start, just don't ever turn the engine off then?)
