...
This manual serves as an end-user manual to configure and use the DaqMux through the IOC.
The DaqMux sub-system is shown in Figure 1. The DaqMux component of the FPGA in the application board of the ATCA allows the user to choose to stream up to four streams to the software (IOC) of the input streams routed to the DaqMux. All ATCA projects are configured to have two DaqMuxes, one associated with each AMC daughter board, summing a total of 8 streams routed to software. Each of the two DaqMux has 20 streams of data routed to its input. Acquisition can be either continuous, single, or single many times. In all three cases a trigger is needed. In the continuous case (i.e. continuous mode), at every trigger, the DaqMux acquires a number of configured bytes (i.e. Frame count) and sends them up to software. In single acquisition (trigger mode), the DaqMux is armed only once, and a number of configured words (i.e. Frame count) is sent to software with or without a header. Finally, single many-times-acquisition is just a sub-case of single acquisitions, however; auto re-arm is enabled, and every time there is a trigger, a number of configured words (i.e. Frame count) is sent to software with or without a header.
...
Anchor | ||||
---|---|---|---|---|
|
The Graphical user interface of a DaqMux is shown in Figure 2. The main graphical user interface for configuring the DaqMux is quite simple and masks a lot of the DaqMux configurations. It only allows the user to perform the following:
...
Clicking on the Down Converter Front Panel Image and the Up Converter Front Panel Image shows the up converters and the down converters AMC card front panel images respectively, and are shown in Figure 3. Each port on the AMC card front panel has a name and may be referenced in the DaqMux output stream selection drop box.
...
The DaqMux output stream selection dropbox example is shown in Figure 4.
Anchor | ||||
---|---|---|---|---|
|
...
Source | Description |
---|---|
${MuxIn#} : Test | Test pattern stream (simple counter data) |
${MuxIn#} : Disable | Disable stream |
${MuxIn#} : ADC${ADC#} | ADC Source not connected |
${MuxIn#} : DAC${DAC#} | DAC Destination not connected |
${MuxIn#} : DBG${DBG#} | Debug streams - application specific and used for debugging (e.g. not used in GMD firmware) |
${MuxIn#} : RF IN ${RF#} : ADC${ADC#} FP | Stream data coming through AMC front panel physical port RF IN ${RF#} through ADC${ADC#} |
${MuxIn#} : RF OUT MON : ADC${ADC#} FP | Stream data coming through AMC front panel physical port RF OUT MON through ADC${ADC#} |
${MuxIn#} : DC IN ${DC#} : ADC${ADC#} FP | Stream data coming through AMC front panel physical port DC IN ${DC#} through ADC${ADC#} |
${MuxIn#} : TRIG MON : ADC${ADC#} (FP) | Stream data coming through AMC front panel physical port TRIG MON through ADC${ADC#} |
${MuxIn#} : CLK PLL DAC : DAC${DAC#} | Stream the applied voltage to the voltage controlled oscillator transmitted through DAC${DAC#} |
${MuxIn#} : LO PLL DAC : DAC${DAC#} | Stream the applied LO signal mixed with RF sinal to get an IF signal transmitted through DAC${DAC#}. This is specific to the LLRF applcation |
${MuxIn#} : DAC OUT : DAC${DAC#} (FP) | Stream data coming out through AMC front panel physical port DAC OUT through DAC${DAC#} |
${MuxIn#} : RF OUT : DAC${DAC#} (FP) | Stream data coming out through AMC front panel physical port RF OUT through DAC${DAC#} |
The DaqMux settings setup page allows the user to fine control the DaqMux by reading and writing to and from the DaqMux registers and some CPSW sequencers (program sequences of writings to a register). The DaqMux settings setup GUI is shown in Figure 5.
...
A full list of all PVs and their Register mapping and description can be seen in Table 2. This table was extracted from the firmware YAML file of the DaqMux. Registers with a blank PV name are not exported to EPICS. PVs with not register names are generated in CPSW libraries, and eventually control registers by applying a sequence of values to them.
...
The DaqMux streams are routed to the DRAM on the application board, and are read using another series of components and exported to the software using the cpswDebugStreamAsynDriverConfigure IOC shell command, which is out of the scope of this document. This module provides all stream information in format of PVs. The available exported PVs are shown in Table 3. As can be seen, this module exports the streams represented with STR (and no longer with DAQMUX). Usually the software engineer would keep the numbering the same and just changing the string to minimize confusion.
...
PV name | Description |
---|---|
${DEVICE}:STR{DAQMUX#}:STREAM_TYPE(0-3) | The data type of the corresponding channel |
${DEVICE}:STR{DAQMUX#}:STREAM_SHORT(0-3) | The data stream of the corresponding channel on full speed |
${DEVICE}:STR{DAQMUX#}:STREAM_SLOWSHORT(0-3) | The data stream of the corresponding channel on reduced speed |
...