quote:以下是引用Zane在2014-03-16 01:46:34的发言:quote:以下是引用nucman在2014-03-15 19:55:49的发言:
针对粉尘和震动严重,怀疑cpu在运行过程中和mmc卡瞬间接触不良造成的。那么该如何验证呢?
如果CPU停机或重启,这是在CPU的诊断缓冲区里是可以查到记录的,但这并不能直接证明就是这个原因。事实上,早期大多数情况下,都是做更换维修的,先换CPU,逐渐地发现与电源的关系很大,就电源和CPU一块儿换,这时候这种现象也不是一种孤立的现象了,甚至有的客户是周而复始的,于是通过简单的统计学,就可以发现一些问题,环境很差是一个必然的条件,这一点从最终返回来的维修备件上可以看出,有的用了几个月的模块,就跟用了多少年似的,那个脏啊。
逐渐的,手里的废旧模块多了,看看能不能拼拼凑凑,攒个维修备件之类的,好歹也能做个测试,于是把模块拆开,清理干净,想找故障点,结果发现,绝大多数的电源在清理后上电都能正常工作,好长时间都没事儿,一多半的CPU在清理后也能恢复工作,但其中还是会有部分在工作一段时间后重新出现故障。后续在和客户的交流中的得知,故障现象早就有了,客户都是到了没法恢复了才来找你的,很多的机器在故障早期是重启上电或重新下载程序后,都自行恢复了,随着粉尘堆积得愈发严重,遇到湿度大的情况,或极度干燥的情况,都会频繁导致故障的,最后不可收拾了。
从此后,再遇见这种故障现象,我一般都会让客户先清理一下模块重新上电运行,如果可以恢复但短期内故障再现,就果断地更换电源及CPU,若是S7-400还包括底板。
还经历过2个比较经典的例子:
一台用了一年多的工控机说经常死机,正好去现场调试新设备,顺带看看,记过发现工控机里太糟糕了,粉尘絮状物充斥机箱内,CPU的风机都被堵住了,于是找来刷子和吸尘器,把工控机打开里里外外做了个大扫除,清理出来一大盆垃圾,擦干净后如新机一般,再上电后系统一切正常。
还有一台用了几个月的工控机,也是说突然频繁死机,用户给返回了。打开机箱一看,工作环境还可以,里面的粉尘只是薄薄的一层,于是让一个小青年同事给简单清理了一下,重新上电后故障依旧。正当没辙准备送西门子维修时,无意中发现粉尘含油,而且是金属粉尘,于是我亲自动手仔仔细细地把这台工控机的板子又清理了一遍,完事后再上电一切OK ,不放心又让工控机连续运转了3天72小时,都没事才发货。
感谢Zane的经验分享!!!相信会给很多工控网友很多启示。
我谈谈我的处理方法。从客户获取到现场工况,怀疑是灰尘震动导致MMC卡接触不良。我的验证思路是,找一台同类型的PLC实验,运行过程中拔掉MMC卡,观察诊断缓冲区的信息,如果某些关键信息与客户提供的丢数据的PLC诊断缓冲区信息一致,那么间接验证了客户PLC丢失数据的原因就是存储卡接触不良。
实验步骤如下:
1.设置DB1.DBW0的初始值为12343,在变量表中在线修改其过程值为123

2.运行过程中拔掉MMC卡,PLC进入Stop状态

重新启动后可以看到DB1.DBW0的过程值恢复为初始值12343

诊断缓冲区信息:
Event 1 of 10: Event ID 16# 4302
Mode transition from STARTUP to RUN
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; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered by switch setting; last power on backed up
Previous operating mode: STARTUP (warm restart)
Requested operating mode: RUN
Incoming event
01:24:46.581 PM 11/11/2013
Event 2 of 10: Event ID 16# 1381
Request for manual warm restart
Startup information:
- Startup without modified system configuration
- No difference between setpoint and actual configuration
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Warm restart triggered by switch setting; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of automatic startup type at power on:
- Warm restart triggered by switch setting; last power on backed up
Requested OB: Startup OB (OB100)
OB not found, or disabled, or cannot be started in the in the current operating mode
Incoming event
01:24:46.580 PM 11/11/2013
Event 3 of 10: Event ID 16# 4301
Mode transition from STOP to STARTUP
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; last power on backed up
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of the automatic startup type at power on:
- Warm restart triggered by switch setting; last power on backed up
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
01:24:45.861 PM 11/11/2013
Event 4 of 10: Event ID 16# 5371
Distributed I/Os: End of the synchronization with a DP master/IO controller on slot 2
Number of distributed stations: 0
Incoming event
01:24:44.071 PM 11/11/2013
Event 5 of 10: Event ID 16# 430E
Memory reset executed
Previous operating mode: STOP (memory reset)
Requested operating mode: STOP (own initialization)
Incoming event
01:24:37.854 PM 11/11/2013
Event 6 of 10: Event ID 16# 4546
STOP caused by CPU memory management
Previous operating mode: STOP (own initialization)
Requested operating mode: STOP (memory reset)
Internal error, Incoming event
01:24:35.759 PM 11/11/2013
Event 7 of 10: Event ID 16# 4300
Power on backed up
Previous operating mode: No voltage
Requested operating mode: STOP (own initialization)
Incoming event
01:24:35.759 PM 11/11/2013
Event 8 of 10: Event ID 16# 6522
Illegal memory submodule: replace submodule and reset memory
Operating mode: STOP (own initialization)
Internal error, Incoming event
01:24:35.759 PM 11/11/2013
Event 9 of 10: Event ID 16# 4580
STOP: backup buffer contents inconsistent (no transition to RUN)
Previous operating mode: No voltage
Requested operating mode: STOP (memory reset)
Internal error, Incoming event
01:24:28.797 PM 11/11/2013
Event 10 of 10: Event ID 16# 494E
Power failure
Previous operating mode: STOP (memory reset)
Requested operating mode: No voltage
External error, Incoming event
01:24:28.787 PM 11/11/2013
可以重点关注Event5和Event6,可以看到 CPU进行了memory reset。
客户提供的诊断缓冲区中也发现了与之一致的信息。所以间接验证了丢数据原因之一就是灰尘震动导致MMC卡接触不良。