PDP800 is reset every time I add a profibus node.
Good morning colleagues! I tell you that I am integrating profibus nodes to DCS Bailey (Pair of BRC410 rev M5) with a redundant PDP800 master (rev B3) with EWS S + Eng 1.2.
The first node I add is a VSD with a motor. I configure the template in CF, add it in CH, synchronize, compile and load through Online Config. I read and write data, and start the engine.
When adding another node to the segment, a CI801 with an AI810, I load the DTM in CF, add it in CH, synchronize, compile and load using Online Config.
When the new control logic associated with the new segment goes into service, the PDP800 immediately resets and the profibus segment drops, causing the motor to stop and the VSD to throw a communication fault.
Is it normal that every time I add a profibus node to the segment, the master is reset? Or am I doing something wrong? Beforehand thank you very much.
The first node I add is a VSD with a motor. I configure the template in CF, add it in CH, synchronize, compile and load through Online Config. I read and write data, and start the engine.
When adding another node to the segment, a CI801 with an AI810, I load the DTM in CF, add it in CH, synchronize, compile and load using Online Config.
When the new control logic associated with the new segment goes into service, the PDP800 immediately resets and the profibus segment drops, causing the motor to stop and the VSD to throw a communication fault.
Is it normal that every time I add a profibus node to the segment, the master is reset? Or am I doing something wrong? Beforehand thank you very much.
Asked 1 month ago
Answers
0
Not 100% sure if adding an PROFIBUS node can be done bump less, have never tried this myself. Perhaps someone else here has experience with this.
Anyhow you need to look into what changes Composer Field has done during the CF sync to determine what caused the reset.
I would expect that the PDP800 FC227 parameters has changed due to the extra PROFIBUS node (parameters like TTR and watchdog time), major changes in these could cause the PDP800 to reset. Seen that adding parameter like LIVE=1 to FC227 causes it to reset.
It could also be that the existing VSD's FC228 parameters have been changed due to a new watchdog time setting caused by the extra node, if so the VSD would have a outage if it don't support Hot Configuration in Run (HCIR).
I would check the CF sync log or an controller verify log to see what was changed in the online config, if there was an change in the existing FC228 you should check if HCIR is available for this model.
Anyhow you need to look into what changes Composer Field has done during the CF sync to determine what caused the reset.
I would expect that the PDP800 FC227 parameters has changed due to the extra PROFIBUS node (parameters like TTR and watchdog time), major changes in these could cause the PDP800 to reset. Seen that adding parameter like LIVE=1 to FC227 causes it to reset.
It could also be that the existing VSD's FC228 parameters have been changed due to a new watchdog time setting caused by the extra node, if so the VSD would have a outage if it don't support Hot Configuration in Run (HCIR).
I would check the CF sync log or an controller verify log to see what was changed in the online config, if there was an change in the existing FC228 you should check if HCIR is available for this model.
Answered 1 month ago
Add new comment