For some reason Ignition seems to be changing the quality code that it receives from kepware. If I connect using kepware client, the kepware client shows my device tags with a bad quality code as code 20. that same tag in ignition shows a code of 600 which is unknown and causes the ignition clients to not see the last known value. I have also tried matrikon explorer, and although it doesnt give you the quality code number, it shows the quality as being bad last known value, which is what it should be.
Any ideas on why this is happening?
I am using 7.2.5
You’ll need to view the quality through another UA client then. DA quality codes and UA status codes aren’t the same; whatever quality code 20 is when using a DA client is going to be something different in UA.
What’s probably happening is that we don’t have a translation defined from whatever the UA status code is to the set of known data qualities you see in Ignition. When this happens you get DataQuality.UNKNOWN.
It looks like 20=“Bad, showing last value”, which probably doesn’t have a mapping. I’ve never seen this quality used… but doesn’t mean it shouldn’t be mapped. With SQLTags, some qualities allow the value to be used, and some don’t, we’ll have to map this so that we can specify it to allow the value to pass through.
[quote=“diat150”]fwiw it works fine for opc-da thru the opc-com module.
Is this something you can fix for a pre 7.3 release?[/quote]
Yeah, because we have a mapping defined for quality code 20 to DataQuality… but we don’t have a mapping defined for whatever UA StatusCode the wrapper is turning quality code 20 into.
I installed uaexpert and was able to connect and get the status code. I believe this is what you need right? once I put the tag back in good quality the statuscode just says good.
Ah right, that’s my fault. I totally forgot about this.
I went to add it, but then decided I should gather some other opinions on what DataQuality this should actually map to. Then I forgot to follow through
