Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ardiadminguide:data_linking [2016/08/01 04:26] optrix |
ardiadminguide:data_linking [2018/12/10 23:51] (current) optrix |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====Data Linking==== | + | ====Data Linking / Binding==== |
| - | Data linking is the process of linking your [[properties|properties]] to external data, such as a historian or live source. | + | Data linking (also known in ARDI as 'Binding') is the process of linking your [[properties|properties]] to external data, such as a historian or live source. |
| Each property on each asset can be connected to a different live and/or historical source for every [[contexts|context]] you have. | Each property on each asset can be connected to a different live and/or historical source for every [[contexts|context]] you have. | ||
| Line 30: | Line 30: | ||
| Pick a data source from the droplist (the list will only contain those data sources appropriate for your chosen time-frame and context) to connect the property to external data. Depending on the [[driver]] being used, you might be asked to provide some additional information (lookup value, field name, IP address, memory register etc.). | Pick a data source from the droplist (the list will only contain those data sources appropriate for your chosen time-frame and context) to connect the property to external data. Depending on the [[driver]] being used, you might be asked to provide some additional information (lookup value, field name, IP address, memory register etc.). | ||
| + | |||
| + | {{linking_data.png}} | ||
| Once you've saved the information, the relevant drivers are restarted. | Once you've saved the information, the relevant drivers are restarted. | ||
| Line 35: | Line 37: | ||
| ===Transform the Incoming Data=== | ===Transform the Incoming Data=== | ||
| - | Some information comes from the driver in a very raw state - this is usually very true of [[ardi-modbus|Modbus/TCP]], where every value is often scaled between 0 and 65535. | + | Some information comes from the driver in a very raw state - this is usually very true of the **Modbus** protocol, where in the hardware every value is often scaled between 0 and 65535. |
| When dealing with that sort of data source, **[[transforms]]** can be useful for making the value more human-readable. | When dealing with that sort of data source, **[[transforms]]** can be useful for making the value more human-readable. | ||
| The 'Edit Transform' button only appears once you've created the link between your property and your external source. | The 'Edit Transform' button only appears once you've created the link between your property and your external source. | ||