ezeio2:userinterface:configuration:fields

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
ezeio2:userinterface:configuration:fields [2022-11-30 17:11] – johparezeio2: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 "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.  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. Reverse expressions only effect writable "Fields" or registers. For more information see [[https://doc.eze.io/ezeio2/expref/start#reverse_expressions|]]+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** **Log interval**
  • ezeio2/userinterface/configuration/fields.1669828308.txt.gz
  • Last modified: 2022-11-30 17:11
  • by johpar