-
Notifications
You must be signed in to change notification settings - Fork 0
4.2. Defaults
Usually, field values can not only be read from a device but also be written to that device. In order to avoid duplicate message definitions, defaults can be used.
A row starting with a star symbol "*" in front of a message type defines the defaults for further rows in that file. The defaults will then be used for blank columns of a message definition with that message type (ignoring the poll priority).
One exception to this generic approach is the "ID" column: The value of the ID column in a defaults row will be prepended to the "ID" column in message definitions of that type having an empty "PBSB" column.
Fields part of a defaults row will be prepended to the fields of a message definition of that type.
The example from the previous paragraph can be further reduced using defaults and templates like this:
| type | circuit | name | comment | ZZ | PBSB | ID | field1 | part | type/templates | |
|---|---|---|---|---|---|---|---|---|---|---|
| *r | ehp | 08 | B509 | 0D | ||||||
| *w | ehp | 08 | B509 | 0E | ||||||
| r1 | brinetemp | 0F00 | tempsensor | |||||||
| r;w | brinetempcal | CD00 | calibration | |||||||
| Download CSV |