IMMFP01 status Report
I have problem that on my system IMMFP01, INNIS01, INNPM01 and NICL01, i have got error that communication from server to IMMFP01 stop and all things stopped and in 1 minute all motors are ready, in alarm list it shows NSYSERR on specific PCU. i change NICL card with new one but same error exist. Now i check From composer pcu status from report picture attached, it tell me node offline:YES what is that mean. Bcoz on this node all motor is running and it is behaviour is normal but after some hours it goes in bad quality.
Asked 4 months ago
Answers
0
Hi,
With regards to an IMMFP01 stopping and then motors becoming ready shortly after, the MFP and NPM do not normally stop and restart automatically due to a module fault. If I understand your description of the symptoms correctly it might be worth looking at the power supply to the PCU. The NSYSERR also indicates a problem with the PCU. I.E. Power, Fans etc. If you can perform a problem report on the NPM when the alarm is active it might give you more information.
With regards to the NPM status report, Node offline means that the PCU has lost communications with another node that it was previously communicating with. This could be another PCU, connectivity server or standalone historian ICI anywhere in the system. A misconfiguration in a Loop/Infinet input function code node address may also cause the problem. The good news though, is that the problem report will contain details of node that cannot no longer be reached.
Cheers,
Alan
With regards to an IMMFP01 stopping and then motors becoming ready shortly after, the MFP and NPM do not normally stop and restart automatically due to a module fault. If I understand your description of the symptoms correctly it might be worth looking at the power supply to the PCU. The NSYSERR also indicates a problem with the PCU. I.E. Power, Fans etc. If you can perform a problem report on the NPM when the alarm is active it might give you more information.
With regards to the NPM status report, Node offline means that the PCU has lost communications with another node that it was previously communicating with. This could be another PCU, connectivity server or standalone historian ICI anywhere in the system. A misconfiguration in a Loop/Infinet input function code node address may also cause the problem. The good news though, is that the problem report will contain details of node that cannot no longer be reached.
Cheers,
Alan
Answered 4 months ago
0
Just to clarify, are the motors actually stopping in the field, or are they just showing as bad quality at the HMI?
If they are actually stopping, I agree with Alan that it sounds like a power supply issue at the PCU.
If they are just going bad quality, then node offline means the communication is dropping out for some other reason (bad NIS, NPM probably)
If they are actually stopping, I agree with Alan that it sounds like a power supply issue at the PCU.
If they are just going bad quality, then node offline means the communication is dropping out for some other reason (bad NIS, NPM probably)
Answered 4 months ago
0
What version of S+ Engineering are you using? Have seen some versions where the problem report does not show the problem. Use the HMI systems problem report and verify what the NPM's problem is. Are you testing loop imports into the MFP controller for bad quality? Could it be that BQ on import is the reason for motors stopping?
Upload status reports on the MFP controller and alarm log from HMI, the limited info you have provided is not enough to pinpoint why you motors have stopped.
Upload status reports on the MFP controller and alarm log from HMI, the limited info you have provided is not enough to pinpoint why you motors have stopped.
Answered 4 months ago
Add new comment