Writing Convention

In order to use the feature of autoconfiguration for communications port inside the eHS Gen 4 block, the *.conf file used must follow a set of writing conventions:

eHS description must follow the template: eHSx?? : Replacing ?? with one of the supported eHS form factors: 16, 32, 64 or 128. This will allow the automatic configurator to set the correct form factor.

eHS port description should finish with the the following suffixes :

• eHSx64_In for DataIn port            (Must be a DataIn port)
• eHSx64_Config for config LoadIn port      (Must be a LoadIn port)
• eHSx64_Rst for reset LoadIn port         (Must be a LoadIn port)
• eHSx64_Avg for average DataOut port       (Must be a DataOut port)
• eHSx64_Out for DataOut port          (Must be a DataOut port)
• eHSx64_Swg for sine wave generator DataIn port  (Must be a DataIn port)
• TSDO for TSDO Digital generators' DataIn ports  (Must be DataIn ports)

Managing TSDO : To associate the TSDO digital generators to a specific eHS core, use the same Slots and Sections for the TSDO as the eHS core's. Since each TSDO block does 8 channel and all TSDO blocks' channels are concatenated together, the subsection index is used to specify the order of the concatenation starting from the least significant bit (1 is the first group of 8ch, 2 represent channels 9 to 16 etc..).

Multiple eHS must be distinguished by the Slot and Section field : To identify the different communication ports of an eHS block we need to know which eHS those ports are connected to. Here's an example of two eHS connected to ports DataIn 1 and 2

1. DataIn1 eHSx64_In 5 A NA -1 32
2. DataIn2 eHSx64_In 6 A NA -1 32

All ports with Slot and Section 5 A will be associated to the first eHS and all ports with Slot and Section 6 A will be associated to the second eHS.