Device Template File Hierarchy

The structure of a CygNet device template file is hierarchical; elements are nested within other elements, creating structural relationships. While the structure of a specific device template file depends on many variables, available component elements fit into a defined position relative to other component elements.

The following tables are intended to help you visualize the structural relationships between component elements. Not all of the component elements listed here are used in all EIEs. Use the following example hierarchies as a pattern to follow when editing existing device template files.

Native/Proprietary Device Template File Hierarchy

The following example represents the structure of native/proprietary device template files. Click available links for more information about an element and/or its attributes.

<deviceDefinition>

<dnp3Support>

</dnp3Support>

<dataGroups>

<DataGroup>

<dgOrdinals>

<ex>

</dgOrdinals>

<dgElements>

<DataGroupElement>

<ref>

<selection>

<sn/>

</selection>

</ref>

<source/>

<MapValName>

<ex/>

</MapValName>

</DataGroupElement>

</dgElements>

<supportDg>

<SupportDataGroup/>

</supportDg>

<readBlocks>

<block/>

</readBlocks>

<writeBlocks>

<block/>

</writeBlocks>

<uccRecvParms>

<RecParmName/>

</uccRecvParms>

<uccSendParms>

<SendParmName/>

</uccSendParms>

</DataGroup>

</dataGroups>

<statusFlags>

</statusFlags>

<defDataGroups>

<DefaultDataGroup/>

</defDataGroups>

<defUisCmds>

<UISCommandName>

<uccItems>

<DG_F_DEV/>

<DG_T_DEV/>

</uccItems>

</UISCommandName>

</defUisCmds>

<specCmds>

<UISCommandName/>

</specCmds>

<fmsMaps>

<alarmItems>

<eFMS_ALARM_ITEM/>

</alarmItems>

<batchItems>

<eFMS_BATCH_ITEM/>

</batchItems>

<configItems>

<eFMS_CFG_ITEM/>

</configItems>

<eventItems>

<eFMS_EVENT_ITEM/>

</eventItems>

<historyItems>

<eFMS_PV_ITEM/>

</historyItems>

</fmsMaps>

<gmrMaps>

<alarmItems>

<eGMR_ALARM_ITEM/>

</alarmItems>

<configItems>

<eGMR_CFG_ITEM/>

</configItems>

<eventItems>

<eGMR_EVENT_ITEM/>

</eventItems>

<historyItems>

<eGMR_PV_ITEM/>

</historyItems>

</gmrMaps>

<enums>

<MapValName>

<Enumeration/>

</MapValName>

</enums>

</deviceDefinition>

Modbus Device Template File Hierarchy

The following example represents the structure of Modbus device template files. Click available links for more information about an element and/or its attributes.

<deviceDefinition>

<dataGroups>

<DataGroup>

<dgOrdinals>

<ex>

</dgOrdinals>

<dgElements>

<DataGroupElement/>

<ref>

<selection>

<sn/>

</selection>

</ref>

<source/>

<MapValName>

<ex/>

</MapValName>

</DataGroupElement>

</dgElements>

<supportDg>

<SupportDataGroup/>

</supportDg>

<modbusReadBlocks>

<block/>

</modbusReadBlocks>

<modbusWriteBlocks>

<block/>

</modbusWriteBlocks>

<cardBlocks>

<preCard>

<block/>

</preCard>

<card>

<block/>

</card>

<postCard>

<block/>

</postCard>

</cardBlocks>

<uccRecvParms>

<RecParmName/>

</uccRecvParms>

<uccSendParms>

<SendParmName/>

</uccSendParms>

</DataGroup>

</dataGroups>

<defDataGroups>

<DefaultDataGroup/>

</defDataGroups>

<defUisCmds>

<UISCommandName>

<uccItems>

<DG_F_DEV/>

<DG_T_DEV/>

</uccItems>

</UISCommandName>

</defUisCmds>

<fmsMaps>

<alarmItems>

<eFMS_ALARM_ITEM/>

</alarmItems>

<batchItems>

<eFMS_BATCH_ITEM/>

</batchItems>

<configItems>

<eFMS_CFG_ITEM/>

</configItems>

<eventItems>

<eFMS_EVENT_ITEM/>

</eventItems>

<historyItems>

<eFMS_PV_ITEM/>

</historyItems>

<productItems>

<eFMS_PRODUCT_ITEM/>

</productItems>

<ticketItems>

<eFMS_TICKET_ITEM/>

</ticketItems>

</fmsMaps>

<gmrMaps>

<alarmItems>

<eGMR_ALARM_ITEM/>

</alarmItems>

<configItems>

<eGMR_CFG_ITEM/>

</configItems>

<eventItems>

<eGMR_EVENT_ITEM/>

</eventItems>

<historyItems>

<eGMR_PV_ITEM/>

</historyItems>

</gmrMaps>

<enums>

<MapValName>

<ex/>

</MapValName>

</enums>

</deviceDefinition>

Back to top