Writing Convention

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

AOMR port description should finish with the the following suffixes :

• AOMR_In for DataIn port           (Must be a DataIn port)
• AOMR_Config for config LoadIn port     (Must be a LoadIn port)

Multiple machines must be distinguished by the Slot and Section fields : To identify the different communication ports of a AOMR block we need to know which analog output mezzanine those AOMR are connected to. Here's an example of two AOMR connected to two different analag output mezzanine:

1. DataIn1 AOMR_In    2  A  NA  -1  32
2. DataIn2 AOMR_In    2  B  NA  -1  32
3. LoadIn6 AOMR_Config  2  A  NA  -1  32
4. LoadIn7 AOMR_Config  2  B  NA  -1  32

All ports with Slot and Section 2 A will be associated to the first AOMR and all ports with Slot and Section 2 B will be associated to the second AOMR.

An AOMR block connected to multiple output mezzanine : To identify multiple mezzanine controlled by a single AOMR, the different Slot number and Section must be concatenated :

1. DataIn1 AOMR_In    11  AB  NA  -1  32
2. DataIn2 AOMR_In    23  AA  NA  -1  32
3. LoadIn6 AOMR_Config  11  AB  NA  -1  32
4. LoadIn7 AOMR_Config  23  AA  NA  -1  32

All ports with Slot and Section 1 A and 1 B will be associated to the first AOMR and all ports with Slot and Section 2 A and 3 A will be associated to the second AOMR