S7 CP 443-5 报警,如何处理?

已锁定

小宝哥们

  • 帖子

    15
  • 精华

    0
  • 被关注

    17

论坛等级:游侠

注册时间:2004-03-30

普通 普通 如何晋级?

S7 CP 443-5 报警,如何处理?

1499

1

2013-04-08 11:31:29

S7 CP 443-5 报警信息如下:(设备可以工作)。硬件组态中没有14号子站,如何消除?其他报警代表什么,如何合理配置CP 443?
Diagnostic buffer of module CP 443-5 Ext
Order No./ Des cription Component Version
6GK7 443-5DX04-0XE0 Hardware 2
- - - Firmware V 6.1.7
Event 1 of 192: Event ID 16# F9C1:2317
DP master information:
Currently configured number of slaves: 14
Currently polled number of slaves: 14
Currently configured number of slaves to poll: 14
Currently configured number of slaves not to be polled: 0
External error, Incoming event
10:07:21.922 PM 01/01/1994
Event 2 of 192: Event ID 16# F9C1:23DD
Copy mode of the slaves for inputs:
- 11 slave(s) without consistency
- 3 slave(s) with short consistency (slave by slave)
- 0 slave(s) with short consistency (slot by slot)
- 0 slave(s) with long consistency
External error, Incoming event
10:07:21.921 PM 01/01/1994
Event 3 of 192: Event ID 16# F9C1:23DC
Copy mode of the slaves for outputs:
- 12 slave(s) without consistency
- 2 slave(s) with short consistency (slave by slave)
- 0 slave(s) with short consistency (slot by slot)
- 0 slave(s) with long consistency
External error, Incoming event
10:07:21.921 PM 01/01/1994
Event 4 of 192: Event ID 16# F9C1:236E
DP master delay time / minimum slave interval
The configured DP master delay time is 0 usec.
The highest min. slave interval in the DP subsystem is 600 usec.
External error, Incoming event
10:07:21.888 PM 01/01/1994
Event 5 of 192: Event ID 16# F9C1:2357
Conf. monitoring time for data transfer
is shorter than 6 times the slave watchdog time (PROFIBUS addr. 30).
Corrected monitoring time: 1200 ms.
External error, Incoming event
10:07:21.886 PM 01/01/1994
Event 6 of 192: Event ID 16# F9C1:2313
Max. diagnostic data length that can be evaluated:
DP master 1: 244 bytes / DP master 2: 244 bytes
Number of saved diagnostic messages: min. 32 / max: 32
External error, Incoming event
10:07:21.884 PM 01/01/1994
Event 7 of 192: Event ID 16# F9C1:032C
Database now consistent after SDB 1010 was loaded by the CPU containing the SDBs (SDB type 3118)
External error, Incoming event
10:07:21.849 PM 01/01/1994
Event 8 of 192: Event ID 16# F9C1:031C
The SDB 1010 loaded by the CPU containing the SDBs is the consistency assurance SDB (SDB type 3118)
External error, Incoming event
10:07:21.849 PM 01/01/1994
Event 9 of 192: Event ID 16# F9C1:0317
Subsystem stopped after loading the existing SDB 1004 with assured consistency by the CPU containing the SDBs ; the existing SDB of type 3100 will be replaced since the time stamps are different.
External error, Incoming event
10:07:21.592 PM 01/01/1994
Event 10 of 192: Event ID 16# F9C1:031B
The already reloaded SDB 1004 will be replaced by an SDB with a later time stamp (SDB type 3100), the previously loaded consistency assurance SDB is retained.
External error, Incoming event
10:07:21.592 PM 01/01/1994
Event 11 of 192: Event ID 16# F9C1:0317
Subsystem stopped after loading the existing SDB 1001 with assured consistency by the CPU containing the SDBs ; the existing SDB of type 3002 will be replaced since the time stamps are different.
External error, Incoming event
10:07:21.339 PM 01/01/1994
Event 12 of 192: Event ID 16# F9C1:031B
The already reloaded SDB 1001 will be replaced by an SDB with a later time stamp (SDB type 3002), the previously loaded consistency assurance SDB is retained.
External error, Incoming event
10:07:21.339 PM 01/01/1994
Event 13 of 192: Event ID 16# F9C1:0317
Subsystem stopped after loading the existing SDB 2002 with assured consistency by the CPU containing the SDBs ; the existing SDB of type 2000 will be replaced since the time stamps are different.
External error, Incoming event
10:07:20.745 PM 01/01/1994
Event 14 of 192: Event ID 16# F9C1:031B
The already reloaded SDB 2002 will be replaced by an SDB with a later time stamp (SDB type 2000), the previously loaded consistency assurance SDB is retained.
External error, Incoming event
Event 21 of 192: Event ID 16# F9C1:032C
Database now consistent after SDB 1008 was loaded by the CPU containing the SDBs (SDB type 3118)
External error, Incoming event
10:02:53.172 PM 01/01/1994
Event 22 of 192: Event ID 16# F9C1:031C
The SDB 1008 loaded by the CPU containing the SDBs is the consistency assurance SDB (SDB type 3118)
External error, Incoming event
10:02:53.172 PM 01/01/1994
Event 29 of 192: Event ID 16# F9C1:200B
Module entering the logical token ring in the STEP E mode.
Normal data exchange can be resumed
External error, Incoming event
09:53:01.625 PM 01/01/1994
Event 30 of 192: Event ID 16# F9C1:2000
The module has dropped out of the logical token ring.
Due to a problem on the bus or due to an incorrect or missing configuration, no data transfer is possible. Other possible cause: Reconfiguration changed the module to a passive bus node.
External error, Incoming event
09:53:01.588 PM 01/01/1994
Event 31 of 192: Event ID 16# F9C1:200B
Module entering the logical token ring in the STEP E mode.
Normal data exchange can be resumed
External error, Incoming event
09:52:56.383 PM 01/01/1994
S7 CP 443-5 报警,如何处理? 已锁定
编辑推荐: 关闭

请填写推广理由:

本版热门话题

SIMATIC S7-300/400

共有54617条技术帖

相关推荐

热门标签

相关帖子推荐

guzhang

恭喜,你发布的帖子

评为精华帖!

快扫描右侧二维码晒一晒吧!

再发帖或跟帖交流2条,就能晋升VIP啦!开启更多专属权限!

  • 分享

  • 只看
    楼主

top
您收到0封站内信:
×
×
信息提示
很抱歉!您所访问的页面不存在,或网址发生了变化,请稍后再试。