Dears, I set up remote property on thingworx, but quality of tag is inconsistent on thingworx and kepware. quality of the remote property on thingworx is GOOD as the the screenshoot but I checeked this tag on QC which is provided by kepware. The tag quality is UNKONWN, and _system._Error of this tag is also true. I am so confused with this inconsistancy, could anyone tell me which quality is correct?

L

LeoChen

8-Gravel

Solved

Property quality on ThingWorx and Kepware is inconsistent

Forum|Forum|2 years ago
September 11, 2023
1 reply
2155 views

Dears,

I set up remote property on thingworx, but quality of tag is inconsistent on thingworx and kepware.

quality of the remote property on thingworx is GOOD as the the screenshoot

but I checeked this tag on QC which is provided by kepware. The tag quality is UNKONWN, and _system._Error of this tag is also true.

I am so confused with this inconsistancy, could anyone tell me which quality is correct?

Best answer by VladimirRosu_116627

Hi @LeoChen ,

If you change the startType to "useDefaultValue" does this behavior change?

Otherwise probably some of my Kepware colleagues might be able to chime in (I do believe it would be wise to open a support case in parallel anyway).

V

VladimirRosu_116627

19-Tanzanite

Hi @LeoChen ,

How certain are you that the property value in Composer is the same as the one in the OPC Client?

I am asking this because Composer only gets the VTQ (which includes the Quality that derives the thumbs up/down) when you click the the Properties tab or when you click the Refresh button.

There's a service called GetPropertyValuesVTQ (or GetPropertyTime if you want to be specific) - execute that and compare the property timestamp with the one from the OPC Client. If indeed the timestamps are the same, the question is valid (not that I can answer why).

But still, we would need to know this first.