The DeviceTypes.xml file used by the PUP driver is in XML format, so some knowledge of xml encoding is required, but not too difficult to follow. In general, do not edit the first line. Comment lines (each starts with “<!--” and ends with “-->”) may be edited, but have no effect on the parsing of the file.
Lines within the <deviceTypes> section can be edited to modify the device and point learn processes.
Each <device> entry in the <deviceTypes> section should always have the following items:
controllerType — a text description.
ct — integer for the controller type, corresponds to the ct attribute.
cm — integer for the controller manufacturer, corresponds to the cm attribute.
snc — serial number channel, the channel that contains the serial number.
sna — serial number attribute, the attribute that contains the serial number.
rdChCmd — does the controller support the “read channel” command? This is a feature of later generation controllers that allows the point discovery process to determine dynamically the list of channels in the device. If set to true, channel entries in this file for the device will not be used and may be omitted.
<channel address> — one entry for each channel that is desired to be discovered in the device. To skip any channel during a learn, then remove the corresponding line from the device. Additional channels may be added as needed, or descriptions/prefixes may be modified as desired, using the following syntax:
channel address — the Hex integer address of a channel.
desc — the long description of a channel, used in learn displays and for naming point folders.
prefix — the short description of a channel, used as a default prefix for point names created during the learn.
See the next Example: HX1 and GPC1 section for two example <device> entries.