Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
ezeio2:userinterface:configuration:fields [2022-09-21 16:36] – [Configuring Fields] johpar | ezeio2:userinterface:configuration:fields [2024-01-04 17:11] (current) – [Configuring Fields] andreh | ||
---|---|---|---|
Line 21: | Line 21: | ||
**Asset Tag** | **Asset Tag** | ||
- | If an Asset Tag has been entered in the config settings of a Field, the tag/s will appear here. | + | If an Asset Tag has been entered in the config settings of a Field, the tag/s will appear here. |
**View** | **View** | ||
Line 48: | Line 48: | ||
**Asset Tag** | **Asset Tag** | ||
- | Enter nicknames or codes here, separated by a comma. These " | + | Enter nicknames or codes here, separated by a comma. These " |
+ | |||
+ | Tags names should always start with a letter, and only include letters, numbers, underscore (_) and hyphen (-). Spaces, international letters or other special characters are not supported in tags. | ||
+ | |||
+ | Asset tags can be user defined and/or generated by a device driver. They can be unique such as " | ||
It is common for hundreds controllers to be used for the same purpose across an account. The configuration could be identical or utilize different devices for the same purpose. For example: a fleet of engine driven pumps. The size, design and manufacture may vary, but they all use fuel, oil, coolant, and pump fluid. Assigning an asset tag for each of the common data points allows them to be easily reference regardless of their Field number. | It is common for hundreds controllers to be used for the same purpose across an account. The configuration could be identical or utilize different devices for the same purpose. For example: a fleet of engine driven pumps. The size, design and manufacture may vary, but they all use fuel, oil, coolant, and pump fluid. Assigning an asset tag for each of the common data points allows them to be easily reference regardless of their Field number. | ||
Line 119: | Line 123: | ||
**Reverse expression** | **Reverse expression** | ||
- | This setting is optional and left blank for most applications. | + | This setting is optional and left blank for most applications. |
**Log interval** | **Log interval** | ||
Line 155: | Line 159: | ||
**Median filter (1s) (check box)** | **Median filter (1s) (check box)** | ||
- | Checking this box will filter out any high or low values that __do not persist__ for more that 1 second. | + | Checking this box will filter out any high or low values that __do not persist__ for more that 1 second. |
| | ||
- | //Field values are updated every 1/10th of a second. The filter buffer holds 21, of these values/ | + | //Field values are updated every 1/10th of a second. The filter buffer holds 21 of these values/ |
**Writable (check box)** | **Writable (check box)** | ||
+ | Checking this box allows users to manually change the value of the Field. Once checked and saved, the cell in the Field' | ||
+ | |||
+ | __Peripheral device example: | ||
+ | |||
+ | __No "Data expression" | ||
**Continuous write (check box)** | **Continuous write (check box)** | ||
+ | The value of a Field is calculated every 1/10th of a second. If the Field is mapped to a writable register, " | ||
**Show on system tab (check box)** | **Show on system tab (check box)** | ||
- | Checking this box will make the Field appear on the controller status table, found under the Manage screen' | + | For some applications may be desirable to show a sub-set of the Fields on the Manage level. |