NS quality for OPC variable

3 Posts
2 Users
0 Likes
29 Views
(@haidarova@fiord.com)
Posts: 0
New Member Guest
 

Hello,
In the topic near I've seen the status NS for OPC was mentioned.
Can anybody tell me more about the situation when the OPC variable can have NS status in PcVue?
A customer meet such situation. Bit OPC variables have NS quality for the False value and they have Good quality for the True value. What can be wrong with the False value? Also then PcVue changes the bit value it's fine with both cases, the quality is always Good. So there are some problem in receiving the False value from OPC.
He uses NETxKNX OPC Studio

2753=366 KNXOPC
2753=367 SCADA
 
Posted : 24/02/2016 7:54 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hi Anna,

I understood the following: PcVue is communicating for 1 bit with an OPC Server. In PcVue the Quality is NS when the value is false and it's OK when the value is true. But with another OPC Client (NETxKNX OPC Studio) it is always good.
Confirm?

In this case I advise you set the OPC traces in PcVUe and check what we receive from the OPC Server.

Nico

 
Posted : 01/03/2016 9:22 am
(@haidarova@fiord.com)
Posts: 0
New Member Guest
 

Thank you for your advices. The traces was done and the quality was good.

I've tested such configuration.
NS for the OPC variable can be Uncertain quality.
But in this case the problem was in a bug and the update helped.

I think it would be good to have access to the list or a database of SPRs for the such cases where we can search the problem among the SPRs for better understanding the situation.

 
Posted : 04/03/2016 2:36 pm