Redundant PLC Connect with Kepware OPC servers not working.
Hello.
We are trying to achieve redundancy with 3rd party OPC servers.
We have two ASCS-servers (ASCS3 and ASCS4) with PLC-Connect and Kepware installed on both servers.
If we use the built in opc-client in kepware we get good readings from the controllers on both ASCS-servers.
If we use ASCS3 as sole provider we get god readings and quality from the Kepware-server.
However, if we:
- Use ASCS4 as sole provider we get "Bad/Last Known Value" on PLC-connect object.
- Use ASCS3 as Provider1 and ASCS4 as Provider2 we get "Bad/Non-specific" reading with <ZERO Time> as time stamp. (Provider selection is done through Generic Control Network Configuration aspect)
- Use ASCS4 as Provider1 and ASCS3 as Provider2 we get "Bad/Non-specific" reading with <ZERO Time> as time stamp. (Provider selection is done through Generic Control Network Configuration aspect)
- Create the service providers in the service-structure and not through the Generic Control Network Configuration aspect it looks like everything is working but both providers are actually reading the data from the Kepware server on ASCS3.
The Kepware on ASCS3 does show active clients and tags but not the kepware on ASCS4 (except when we are using the built in client).
No matter what we try we are unable to get PLC-Connect to fetch data from the Kepware server on ASCS4, please advice on next steps.
Versions:
800 xA: 6.1.0
PLC Connect Version: 6.1.0
Kepware KEPServerEX 6.8.
Best Regards
Denniz
We are trying to achieve redundancy with 3rd party OPC servers.
We have two ASCS-servers (ASCS3 and ASCS4) with PLC-Connect and Kepware installed on both servers.
If we use the built in opc-client in kepware we get good readings from the controllers on both ASCS-servers.
If we use ASCS3 as sole provider we get god readings and quality from the Kepware-server.
However, if we:
- Use ASCS4 as sole provider we get "Bad/Last Known Value" on PLC-connect object.
- Use ASCS3 as Provider1 and ASCS4 as Provider2 we get "Bad/Non-specific" reading with <ZERO Time> as time stamp. (Provider selection is done through Generic Control Network Configuration aspect)
- Use ASCS4 as Provider1 and ASCS3 as Provider2 we get "Bad/Non-specific" reading with <ZERO Time> as time stamp. (Provider selection is done through Generic Control Network Configuration aspect)
- Create the service providers in the service-structure and not through the Generic Control Network Configuration aspect it looks like everything is working but both providers are actually reading the data from the Kepware server on ASCS3.
The Kepware on ASCS3 does show active clients and tags but not the kepware on ASCS4 (except when we are using the built in client).
No matter what we try we are unable to get PLC-Connect to fetch data from the Kepware server on ASCS4, please advice on next steps.
Versions:
800 xA: 6.1.0
PLC Connect Version: 6.1.0
Kepware KEPServerEX 6.8.
Best Regards
Denniz
Answers
This question has not yet been answered.
Add new comment