PM866 Fault
Hi .... I have a tech support case opened up for this and waiting for a call back, but wanted to post a message here as well... we had a PM866A (non redundant) go into fault mode; F LED is red, P LED is green. When I look at the controller log, what I see is:
This PM has been unintentionally stopped.
Reason:
- Soft Error Upset detected by the FPGA
Press init button or remove power to restart...
What could cause this error? Should I be thinking about a redundant processor; would that help for a case like this?
thanks
This PM has been unintentionally stopped.
Reason:
- Soft Error Upset detected by the FPGA
Press init button or remove power to restart...
What could cause this error? Should I be thinking about a redundant processor; would that help for a case like this?
thanks
Asked 1 year ago
Answers
0
Responding to the two comments recently added to my question from a year ago...
Shortly after the failure, ABB released bulletin 3BSE093337 (Modulebus failure on AC 800M Controllers, PM858, PM862, PM866A), and contacted me to replace the controller under warranty.
Our system did not use Modulebus, just remote IO drops via Profibus. But reading the bulletin and looking at the architecture of the PM866, there's a chip on the processor used for Modulebus... my theory is that this failure could impact the PM866 regardless of whether or not Modulebus IO is actually used?
FWIW, the original PM866 continued to run fine for 6 months after the initial failure. I then had an opportunity to replace it, and the new module has been running fine since.
Shortly after the failure, ABB released bulletin 3BSE093337 (Modulebus failure on AC 800M Controllers, PM858, PM862, PM866A), and contacted me to replace the controller under warranty.
Our system did not use Modulebus, just remote IO drops via Profibus. But reading the bulletin and looking at the architecture of the PM866, there's a chip on the processor used for Modulebus... my theory is that this failure could impact the PM866 regardless of whether or not Modulebus IO is actually used?
FWIW, the original PM866 continued to run fine for 6 months after the initial failure. I then had an opportunity to replace it, and the new module has been running fine since.
Answered 2 months ago
by eskabod Rank: 730 on 2/6/2020 12:45:43 AM | Like (0) | Report
Hi,
Did you maybe get an answer to this question? I’m having a same problem... Thanks in advance!
by jerry.sjogren Rank: 2082 on 3/11/2020 2:35:50 AM | Like (0) | Report
Hi,
March 8th 2020 same happened at customer site. We downloaded program and now the system is up.
Is this firmware related or HW related, Snips of log & Controlbuilder version:
* wL01:05:402.152.876 * WL01:05:402.152.886 * SC06:05:402.152.892 * SC07:05:402.156.956
No powerfailinfo and/or stallinfo to report
Post Mortem controller log:
I 2020-03-08 00:45:15.299 ... flushed 0 messages (first message might be repeated)
This PM has been unintentionally stopped.
Reason:
- Soft Error Upset detected by the FPGA
Press init button or remove power to restart...
I 1979-12-31 00:00:00.592 Product : AC 800M PM866
I 1979-12-31 00:00:00.594 Version : 6.0.0-2 (Build 6.0.200.10)
I 1979-12-31 00:00:00.596 Created : 2017-12-14
I 1979-12-31 00:00:00.598 ABB AB
I 1979-12-31 00:00:00.600
I 1979-12-31 00:00:00.601 Controller Reset
I 1979-12-31 00:00:00.726 Position Module Firmware Name Date Version
I 1979-12-31 00:00:00.729 0 PM866 FW866 2017-12-14 6.0.200.10
I 1979-12-31 00:00:00.732 OMEGA 2017-12-14 6.0.200.10
I 1979-12-31 00:00:00.735 CPU Unit N/A PM866A F
Add new comment