We have a system set up as follows:
2 X S7 417H Prcessors on two racks set up for redundancy
2 X CP443-1 communications modules (1 on each rack)
The redundancy between the processors works perfectly. When we switch one processor off the other takes over, very nice.
We are using Citect to communicate with the both PLCs over ethernet. Citect is using a backend/frontend driver called PSDirect. The backend is a third party driver by ProScada. Our problem is that the backend driver does not seem to recognise that that processor has stopped and continues to get frozen data from the stopped processor. If we remove the ethernet connection from the CP443-1 module associated with the stopped processor then the driver swaps to the standby.
Anybody had any experience with this?
2 X S7 417H Prcessors on two racks set up for redundancy
2 X CP443-1 communications modules (1 on each rack)
The redundancy between the processors works perfectly. When we switch one processor off the other takes over, very nice.
We are using Citect to communicate with the both PLCs over ethernet. Citect is using a backend/frontend driver called PSDirect. The backend is a third party driver by ProScada. Our problem is that the backend driver does not seem to recognise that that processor has stopped and continues to get frozen data from the stopped processor. If we remove the ethernet connection from the CP443-1 module associated with the stopped processor then the driver swaps to the standby.
Anybody had any experience with this?