Article - CS270197
Saving a Thing in ThingWorx with properties bound to a PLC, resets the value on the PLCs
Modified: 28-Dec-2017
Applies To
- ThingWorx Platform 8.0
Description
- Bound properties do not initialize values on thing startup
- Every time a PLC (Programmable Logic Controller) property is changed in the Composer, after saving it, instead of having the new value, it is updated with the zero (0) value or with the default one
- In the connected device PLC Modbus Ethernet the data can be seen in the Current value
- Changing the Current Value, this value updates correctly with the new one both in the PLC and in the Thing in the Composer
- Once the system is up and running it's fine
- But any time it is modified in the Composer, and click Save the value is set to 0
- The Thing is directly linked to Kepware connected to the automation layer, and the values are properly read from Kepware
- In the KepServer all the values are in read-write mode, the default one
- Warning and Error messages noticed:
- Validation Warning: Thing <thing> Had An Invalid Remote Binding To Property : [<property>] - Property Name Not Found
- Error notifying things of propertyBinding changes on activate
- The KepServer is generating the following warning, even during the non-working hours:
- Write request rejected on read-only item reference
- The write error in Kepware logs shows up when saving the thing, thus triggering the write operation from the thing to a read-only Kepware tag
This is a printer-friendly version of Article 270197 and may be out of date. For the latest version click CS270197