Article - CS310670
Best practice for using the the Torque Tool Driver in KEPServerEX / ThingWorx Industrial Connectivity to send data to ThingWorx Platform
Modified: 24-Jul-2019
Applies To
- ThingWorx Kepware Server (legacy) 8.3
- Kepware Server (formerly KEPServerEX) 6.5.850.0
- ThingWorx Kepware Server (legacy) 8.3
- Driver: Torque Tool
- Interface: ThingWorx Native Interface
Description
- Best practice for using the the Torque Tool Driver in KEPServerEX / ThingWorx Industrial Connectivity (KSE/TWIC) to send data to ThingWorx Platform
- How to prevent, as much as possible, not receiving accurate data from the Torque Tool and other unsolicited events
- How to ensure that the unsolicited results data will be provided to the Thingworx platform as soon as possible
- How to ensure that all results data will be processed accurately by ThingWorx services (log to ext. DB) before a new torque tool event is registered
- NewData tags need to be slightly delayed to allow Thingworx platform ingest the results before triggering on the NewData tag
This is a printer-friendly version of Article 310670 and may be out of date. For the latest version click CS310670