Hi everyone.
We changed our line from PLC5 to CtrlLgx, and in the same time changed our Hydro Tester machine. We added a panelview that eliminated lots of digital I/Os and it all communicate through ethernet. We have 2 internet card in PLC chassis, one for all IO including the hmi, and other for bussiness network (data collection).
Program on our PLC consist of one 10ms scheduled routine that includes 25 subroutines and controls our hydro tester, and 4 continues tasks that control other machines on the line.
I want to add that on the panelview we monitor real-time test pressure operation set up as graph and as a digital display of a current value of test pressure. Beside that we have 30-40 different IO points on the HMI itself (start cycle, pause, etc..)
Everything run fine in first couple of weeks, but now it looks like the network is deteriorating and losing the speed and the bandwidth without adding any new IOs or major logic changes.
First we had delay on the graph itself where the test pressure just stops going up and becomes straight line (because new data is not coming in and it keeps showing the number where it got stuck), which confused hell out of our Op, but the process itself worked good with proper cycle and testing.
Recently we started getting error messages on the HMI saying:
CIP conection (1) open rejection (error 2040101) on route ControlLogix in slot 0 of the chassis at XXX.XXX...rest doesnt show but I believe its our internet address of IO internet card.
Also when the OP change mode from Manual to Auto or anything like that it takes forever for the screen to show and change color from green to red etc..
Are we hitting the wall with our Ethernet bandwidth and panelview requirements or something similar ?
I am debating to suggest getting one more Internet card (it would be 3 in total, and putting the third one and a HMI on separate subnet, but am not sure if it would help since it is still the same PLC that has to do the work and poll the data and do the calculation ??? Also that would require pulling separate ethernet cables so those two network dont share the same switches either.
I am not sure if I miss anything, but if I did, I would be glad to add more explanation.
Thanks for reading,
Darko
We changed our line from PLC5 to CtrlLgx, and in the same time changed our Hydro Tester machine. We added a panelview that eliminated lots of digital I/Os and it all communicate through ethernet. We have 2 internet card in PLC chassis, one for all IO including the hmi, and other for bussiness network (data collection).
Program on our PLC consist of one 10ms scheduled routine that includes 25 subroutines and controls our hydro tester, and 4 continues tasks that control other machines on the line.
I want to add that on the panelview we monitor real-time test pressure operation set up as graph and as a digital display of a current value of test pressure. Beside that we have 30-40 different IO points on the HMI itself (start cycle, pause, etc..)
Everything run fine in first couple of weeks, but now it looks like the network is deteriorating and losing the speed and the bandwidth without adding any new IOs or major logic changes.
First we had delay on the graph itself where the test pressure just stops going up and becomes straight line (because new data is not coming in and it keeps showing the number where it got stuck), which confused hell out of our Op, but the process itself worked good with proper cycle and testing.
Recently we started getting error messages on the HMI saying:
CIP conection (1) open rejection (error 2040101) on route ControlLogix in slot 0 of the chassis at XXX.XXX...rest doesnt show but I believe its our internet address of IO internet card.
Also when the OP change mode from Manual to Auto or anything like that it takes forever for the screen to show and change color from green to red etc..
Are we hitting the wall with our Ethernet bandwidth and panelview requirements or something similar ?
I am debating to suggest getting one more Internet card (it would be 3 in total, and putting the third one and a HMI on separate subnet, but am not sure if it would help since it is still the same PLC that has to do the work and poll the data and do the calculation ??? Also that would require pulling separate ethernet cables so those two network dont share the same switches either.
I am not sure if I miss anything, but if I did, I would be glad to add more explanation.
Thanks for reading,
Darko