...
Next step is to calculate the time related to each section of the integration window: pre-edge, inter-edges, and post-edge. Basically, we multiply the size of the window section in ticks by the period of the tick in nanoseconds, as calculated before. The inter-edges is different because the firmware delivers half of the size. That's why we have B*2 in the calculation. The register names and Asyn parameter names for each of the AMC cards are in the table below.
Gliffy Diagram | ||||||
---|---|---|---|---|---|---|
|
Register name | Asyn parameter name |
---|---|
/mmio/AppTop/AppCore/SysGenMr[0]/DspPreprocConfigMr[0]/NumberSamples0 | AMC0:SENS0:NumSamp0 |
/mmio/AppTop/AppCore/SysGenMr[1]/DspPreprocConfigMr[0]/NumberSamples0 | AMC1:SENS0:NumSamp0 |
/mmio/AppTop/AppCore/SysGenMr[0]/DspPreprocConfigMr[0]/TrigDelay1 | AMC0:SENS0:TrigDelay1 |
/mmio/AppTop/AppCore/SysGenMr[1]/DspPreprocConfigMr[0]/TrigDelay1 | AMC1:SENS0:TrigDelay1 |
/mmio/AppTop/AppCore/SysGenMr[0]/DspPreprocConfigMr[0]/NumberSamples1 | AMC0:SENS0:NumSamp1 |
/mmio/AppTop/AppCore/SysGenMr[1]/DspPreprocConfigMr[0]/NumberSamples1 | AMC1:SENS0:NumSamp1 |
The next step is to provide PVs for the user to change the pre, inter, and post edges windows in nanoseconds and convert them back to tick counts. This step is more tricky because the firmware does not accept odd numbers.
Gliffy Diagram | ||||
---|---|---|---|---|
|