Heidenhain-Data Change
Data change trigger executes transfers with a changing Heidenhain value. You might specify tolerances and time intervals as to optimize the number of transfers – forced transfer, even if no change is made, or limitation of transfers with many data changes.
| Access data | Select a set of Heidenhain access data. |
| Trigger item | Item whose change will execute the transfer. Browse items with tag browser (“...” button). |
Use the extended button to define further properties
| At most every | Minimum interval in which transfer will be executed even if no data change has occurred. Integers only, unit from milliseconds to hours. |
| At least every | If data change frequently the number of transfers can be limit. An entry means, e. g. Transfer every second maximum even if data changes more frequently. Integers only. Units from milliseconds to hours. |
| Trigger at ... difference (%) | Transfer will only execute if data changes by this difference. |
| Trigger at ... difference (absolute) | Transfer will only execute if data changes by this difference. |
| Trigger at each data change | Default. Overrides tolerance settings. |
| Trigger if quality changed | Activate the checkbox if you want to trigger at quality change. |
| Trigger if timestamp changed | Activate the checkbox if you want to trigger when the timestamp is changed. |
| Metadata output | Activate the checkbox if you want the metadata to be output. |
tip
Tip: To set conditions for relative and absolute tolerance, project two data change triggers linked with AND or OR.