Differences

This shows you the differences between two versions of the page.

--- ezeio2:userinterface:configuration:fields [2021-12-08 17:05] – [Configuring Fields] johpar
+++ ezeio2:userinterface:configuration:fields [2024-01-04 17:11] (current) – [Configuring Fields] andreh
@@ Line 21: / Line 21: @@
 **Asset Tag**
 If an Asset Tag has been entered in the config settings of a Field, the tag/s will appear here.
 **View**
@@ Line 48: / Line 48: @@
 **Asset Tag**
-Enter nicknames or codes here, separated by a comma. These "Tags" are an alternate means of referencing one or more Fields and utilized in message templates, some dashboard Widgets and anywhere expressions are used (Fields,  alarms, alarm & restore actions, timers). Asset tags can be user defined and/or generated by a device driver. They can be unique such as "HVACload" or generic such as "load". Asset tags should be kept short, starting with a letter, and containing no special characters or spaces. The asset tags are entered on the Field's configuration, for example as: HVACload  and referenced in an expression or message template as: <HVACload>
+Enter nicknames or codes here, separated by a comma. These "Tags" are an alternate means of referencing one or more Fields and utilized in message templates, some dashboard Widgets and anywhere expressions are used (Fields,  alarms, alarm & restore actions, timers).
+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 "HVACload" or generic such as "load". Asset tags should be kept short, starting with a letter, and containing no special characters or spaces. The asset tags are entered on the Field's configuration, for example as: HVACload  and referenced in an expression or message template as: <HVACload>
 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**
-This setting is optional and left blank for most applications.
+This setting is optional and left blank for most applications. Reverse expressions only effect writable "Fields" or registers. For more information see [[ezeio2/expref/start#reverse_expressions|reverse expressions]]
 **Log interval**
@@ Line 125: / Line 129: @@
 The default log interval of 10 minutes is included with basic service. Two upgrades to the logging service are available, "Logging down to 1 minute" (includes 1, 2, & 5 minute intervals) and "logging down to 5 seconds" (includes 5 & 15 second intervals).
-=== Log method ===
+**Log method**
 Several different logging methods are available.
@@ Line 152: / Line 156: @@
 This box is checked by default. Un-checking it will disable logging for the Field
+**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. This effectively introduces a 1 second delay. This delay effects alarms and other logic.
+//Field values are updated every 1/10th of a second. The filter buffer holds 21 of these values/samples. The samples are sorted from highest to lowest and the middle (median) is selected to update the field. Every 1/10th of a second the oldest sample is removed, a new sample is added and the median is selected. //
 **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's view column will change from light grey to white. Select a setting on the "Display format in view" dropdown menu that provides a means of manipulating the value, such as; Number, Switch, or Slider. With number selected, clicking in the cell will produce a pop-up box for the user to enter and submit a new value. This feature functions differently whether the Field is mapped to a connected device or not. When mapped to writable register on a peripheral device, the new value will be written to the register. If no mapping (no "Data expression" entered) the Field value can be referenced by Alarms, Timers, Script or application drivers.
+__Peripheral device example:__  Write a new RPM setpoint to an engine controller
+__No "Data expression" example__:  Manually change the threshold in an "Alarm condition setting".
 **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, "Continuous write" will attempt to write the value shown to every time the Field is calculated.
 **Show on system tab (check box)**
-Checking this box will make the Field appear on the controller status table, found under the Manage screen's Systems tab.
+For some applications may be desirable to show a sub-set of the Fields on the Manage level. Checking this box will make the Field appear on the controller's status table, found under the Manage screen's Systems tab.