OPC UA \"Status Mapping\" and null value
Posted: Mon Aug 13, 2018 9:09 am
Hi all,
We use the mapping OPC UA status codes to WinCC OA user bits.
If the server has a bad quality signal, WinCC OA does not set a user bit.
Using -dbg 27 we found out that the OPC UA server sends a bad quality signal with null value.
Using the WinCC OA OPC UA server, the user bits are set correctly, when imitating bad quality, -dbg 27 shows that in this case, the WinCC OA OPC UA server sends a bad quality signal with the value.
Can we assume that the problem is that the server sends values ??with null value? Change server logic is not possible. Can we do something ourselves?
It is very important for us to obtain a status code, becouse we must know the reason for the bad quality.
Any suggestion?
We use the mapping OPC UA status codes to WinCC OA user bits.
If the server has a bad quality signal, WinCC OA does not set a user bit.
Using -dbg 27 we found out that the OPC UA server sends a bad quality signal with null value.
Using the WinCC OA OPC UA server, the user bits are set correctly, when imitating bad quality, -dbg 27 shows that in this case, the WinCC OA OPC UA server sends a bad quality signal with the value.
Can we assume that the problem is that the server sends values ??with null value? Change server logic is not possible. Can we do something ourselves?
It is very important for us to obtain a status code, becouse we must know the reason for the bad quality.
Any suggestion?