У нас на объекте система управления построена на H-system из двух PLC S7 400 — Master и Standby.
Один из PLC ушёл в STOP. Запускаться в RUN не хочет. Redundant система теперь работает в «Solo Mode». Тот PLC который в норме теперь Master.
— Захожу в Hardware Configuration. Пытаюсь делать Download to PLC в режиме RUN. Загрузка срывается следующим сообщением:
Как видно из картинки срывается Warm Restart ПЛК который в STOP’е.
— Пробую другое:
В Hardware Configuration пробую перейти в режим Online, когда пишет что офлайн и онлайн отличается выбираю Download from PLC to PG. Всё грузится, онлайн запускается. Пытаюсь открыть Module Information стопанутого PLC. Выдает такое окно:
По железу первое что проявилось: это ошибки BUSF на модулях CP.
Где искать ошибку? Полез в Diagnsotic Buffer.
Ошибки следующие:
Diagnostic buffer of module CPU 417-4 H
Order No./ Description Component Version
6ES7 417-4HT14-0AB0 Hardware 1
— — — Firmware V 4.5.2
Rack: —
Slot: —
Settings:
Time including CPU/local time difference (+6 h)
Event 1 of 120: Event ID 16# 530D
New startup information in STOP mode
Startup prevented by:
User program invalid
— Module or submodule assignment not evaluated or evaluation aborted with errors (SDB 1,3,5,2X,9X)
— STOP request exists
— Cold restart or warm restart necessary
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered via MPI
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
— No startup type/following memory reset
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
02:53:43.024 PM 06/19/2015
Event 2 of 120: Event ID 16# 4542
STOP caused by object management system
Previous operating mode: STOP (internal)
Requested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Internal error, Incoming event
02:53:43.020 PM 06/19/2015
Event 3 of 120: Event ID 16# 530D
New startup information in STOP mode
Startup prevented by:
Loading user program or internal inconsistency detected
(SDBs less than 200 incomplete, superfluous, or incorrect)
User program invalid
— Module or submodule assignment not evaluated or evaluation aborted with errors (SDB 1,3,5,2X,9X)
— STOP request exists
— Cold restart or warm restart necessary
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered via MPI
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
— No startup type/following memory reset
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
02:53:42.723 PM 06/19/2015
Event 4 of 120: Event ID 16# 6550
Error in test value (CRC) of a block
FC number: 3040
No relevance for user : 0xd235
No relevance for user : 0x0000
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Internal error, Incoming event
02:53:41.373 PM 06/19/2015
Event 5 of 120: Event ID 16# 6550
Error in test value (CRC) of a block
FC number: 2752
No relevance for user : 0xd235
No relevance for user : 0x0000
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Internal error, Incoming event
02:53:41.287 PM 06/19/2015
Event 6 of 120: Event ID 16# 6550
Error in test value (CRC) of a block
DB number: 3478
No relevance for user : 0xd235
No relevance for user : 0x0000
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Internal error, Incoming event
02:53:40.662 PM 06/19/2015
Event 7 of 120: Event ID 16# 6550
Error in test value (CRC) of a block
DB number: 3371
No relevance for user : 0xd235
No relevance for user : 0x0000
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Internal error, Incoming event
02:53:40.626 PM 06/19/2015
Event 8 of 120: Event ID 16# 530D
New startup information in STOP mode
Startup prevented by:
User program invalid
— Parameter assignment for MPI or DP interfaces not evaluated or inconsistent
(SDB1XXX incomplete, superfluous, or incorrect)
— Module or submodule assignment not evaluated or evaluation aborted with errors (SDB 1,3,5,2X,9X)
— STOP request exists
— Cold restart or warm restart necessary
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered via MPI
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
— No startup type/following memory reset
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
02:53:39.668 PM 06/19/2015
Event 9 of 120: Event ID 16# 49D1
LINK-UP/UPDATE aborted
No relevance for user (Z1): 8ff9
No relevance for user (Z2): 80ff (Z3): 0035
Previous operating mode: LINK-UPRequested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
External error, Incoming event
02:53:39.666 PM 06/19/2015
Event 10 of 120: Event ID 16# 43E6
Master CPU: Link-up/update by standby CPU aborted
Trigger event: LINK-UP/UPDATE aborted
Previous operating mode: LINK-UP
Requested operating mode: RUN
Event occurred in the master CPU in rack 0
Incoming event
02:53:39.666 PM 06/19/2015
Event 11 of 120: Event ID 16# 49A4
STOP: inconsistency in the configuration data
occurred when checking Parameters for local consistency
No consistency entries assignable
Error type: The time stamp delivered by the PROFIBUS DP or PROFINET IO interfaces does not correspond with the configured CPU data
Previous operating mode: LINK-UP
Requested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
External error, Incoming event
02:53:39.666 PM 06/19/2015
Event 12 of 120: Event ID 16# 43E0
Change from STOP (internal) to link-up mode
STOP due to: STOP caused by object management system
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered via MPI
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of the automatic startup type at power on:
— Warm restart triggered via MPI
Previous operating mode: STOP (internal)
Requested operating mode: LINK-UP
Event occurred in the standby CPU in rack 1
Incoming event
02:52:28.096 PM 06/19/2015
Event 13 of 120: Event ID 16# 43E0
Change from RUN to link-up mode
Previous operating mode: RUN
Requested operating mode: LINK-UP
Event occurred in the master CPU in rack 0
Incoming event
02:52:28.096 PM 06/19/2015
Event 14 of 120: Event ID 16# 43E0
Change from STOP (internal) to link-up mode
STOP due to: STOP caused by object management system
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered via MPI
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of the automatic startup type at power on:
— Warm restart triggered via MPI
Previous operating mode: STOP (internal)
Requested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
02:52:27.970 PM 06/19/2015
Event 15 of 120: Event ID 16# 530D
New startup information in STOP mode
Startup prevented by:
User program invalid
— Module or submodule assignment not evaluated or evaluation aborted with errors (SDB 1,3,5,2X,9X)
— Cold restart or warm restart necessary
Startup information:
— Time for time stamp at the last backed up power on
— Single processor operation
Current/last startup type:
— Warm restart triggered by switch setting
Permissibility of certain startup types:
— Manual startup not permitted, corrections in parameter assignment, submodule, etc. necessary
Last valid operation or setting of automatic startup type at power on:
— Warm restart triggered via MPI
Operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
Incoming event
02:52:27.970 PM 06/19/2015
Есть мысль что в СТОП уходит из за этого event’а:
Event 11 of 120: Event ID 16# 49A4
STOP: inconsistency in the configuration data
occurred when checking Parameters for local consistency
No consistency entries assignable
Error type: The time stamp delivered by the PROFIBUS DP or PROFINET IO interfaces does not correspond with the configured CPU data
Previous operating mode: LINK-UP
Requested operating mode: STOP (internal)
Event occurred in the standby CPU in rack 1
External error, Incoming event
02:53:39.666 PM 06/19/2015
Что ещё можно сделать?
— Сделать загрузку Hardware Configuration в режиме STOP? Пока нет возможности остановить тех. процесс. Поможет ли?
— В режиме Online Hardware Config заходил в Operating Mode. Там жал кнопку Switch To. Доступен только один вариант — Switch to Altered configuration. Что произойдёт, если сделать это переключение?
По предоставленной информации понятно ли в чём проблема?
MrPLC.com sells used surplus products. MrPLC.com is not an authorized distributor, affiliate, or representative for the brands we carry. Products sold by MrPLC.com come with MrPLC.com’s 1-year, 2-year, or 3-year warranty and do not come with the original manufacturer’s warranty. Designated trademarks, brand names and brands appearing herein are the property of their respective owners. This website is not sanctioned or approved by any manufacturer or tradename listed.
Rockwell Disclaimer: The product is used surplus. MrPLC.com is not an authorized surplus dealer or affiliate for the Manufacturer of this product. The product may have older date codes or be an older series than that available direct from the factory or authorized dealers. Because MrPLC.com is not an authorized distributor of this product, the Original Manufacturer’s warranty does not apply. While many Allen-Bradley PLC products will have firmware already installed, MrPLC.com makes no representation as to whether a PLC product will or will not have firmware and, if it does have firmware, whether the firmware is the revision level that you need for your application. MrPLC.com also makes no representations as to your ability or right to download or otherwise obtain firmware for the product from Rockwell, its distributors, or any other source. MrPLC.com also makes no representations as to your right to install any such firmware on the product. MrPLC.com will not obtain or supply firmware on your behalf. It is your obligation to comply with the terms of any End-User License Agreement or similar document related to obtaining or installing firmware.
Digital modules
4.4 Diagnostics for digital modules
4.4.2
Overview
The table below gives an overview of the diagnostic messages for the digital modules with
diagnostics capability.
You can find out which diagnostic message each module is capable of in the Appendix entitled
«Diagnostic data of the signal modules».
Table 4-6
Module error
Internal error
External error
Channel error
External auxiliary voltage missing
Front connector missing
No module parameters
Incorrect parameters
Channel information available
STOP mode
Internal voltage failure
EPROM error
Hardware interrupt lost
Parameter assignment error
Short-circuit to M
Short-circuit to L+
Wire break
Fuse blown
Sensor supply missing
Load voltage L+ missing
Note
Prerequisite for detecting errors indicated by programmable diagnostic messages is an
appropriate configuration of the digital module in STEP 7.
90
Diagnostic messages of the digital modules
Diagnostic message
LED
Scope of diagnostics
INTF/EXTF
Module
INTF
Module
EXTF
Module
INTF/EXTF
Module
EXTF
Module
EXTF
Module
INTF
Module
INTF
Module
INTF/EXTF
Module
—
Module
INTF
Module
INTF
Module
INTF
Module
INTF
Channel
EXTF
Channel
EXTF
Channel
EXTF
Channel
INTF
Channel
EXTF
Channel/channel
group
EXTF
Channel/channel
group
S7-400 Automation System Module Data
Reference Manual, Ausgabe 11/2016, A5E00850736-08
Programmable
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes