cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

ThingWorx Navigate is now Windchill Navigate Learn More

Translate the entire conversation x

Unbound Property Quality Behavior Thingworx

JK_10744682
13-Aquamarine

Unbound Property Quality Behavior Thingworx

HI all,

 

I have confused on the behavior of unbound properties and their quality. I create a new property, and it comes back as UNKNOWN quality. Then I set the value to something other than 0 and it comes back as GOOD. What causes GOOD vs UNKNOWN exactly in an unbound property? Is there a way to have an unbound property always be GOOD quality?

ACCEPTED SOLUTION

Accepted Solutions

Hi @JK_10744682 ,

A property that was created will always have quality UNKNOWN (even if you set the Default Value). That signifies that the property never received property updates. As soon as you set it to something, the quality will change to GOOD (or BAD depending on how it's set).

Considering this, an unbound property will be GOOD quality once it received a property update, but not before that.

View solution in original post

1 REPLY 1

Hi @JK_10744682 ,

A property that was created will always have quality UNKNOWN (even if you set the Default Value). That signifies that the property never received property updates. As soon as you set it to something, the quality will change to GOOD (or BAD depending on how it's set).

Considering this, an unbound property will be GOOD quality once it received a property update, but not before that.

Announcements


Top Tags