I am testing Driver Multiplexer with two Kepware OPC UA servers.
Q1> When failover switching to secondary driver successfully, data updates can see in values.
But the issue is
Historian logging still considers to log or not depending on deadband value of another driver IO tag. I noticed this when I found the data is not updated in historian. How should i fix it? I want to get new data values log when switching to secondary driver starts.
I fixed with periodic logging interval. But I think it is not feasible way because it will increase SSD size. How to make the new data log to historian while switch over starts?
Q2> Tag count in this project is 75K tags. Two Kepware OPC UA servers are polling data from IED relays. Can VTScada switch to secondary Kepware OPC UA server reliable and no data loss for these 75 K tags (large system)?
I am testing Driver Multiplexer with two Kepware OPC UA servers.
Q1> When failover switching to secondary driver successfully, data updates can see in values.
But the issue is
Historian logging still considers to log or not depending on deadband value of another driver IO tag. I noticed this when I found the data is not updated in historian. How should i fix it? I want to get new data values log when switching to secondary driver starts.
I fixed with periodic logging interval. But I think it is not feasible way because it will increase SSD size. How to make the new data log to historian while switch over starts?
Q2> Tag count in this project is 75K tags. Two Kepware OPC UA servers are polling data from IED relays. Can VTScada switch to secondary Kepware OPC UA server reliable and no data loss for these 75 K tags (large system)?