We have known for a long time that the muxed readout (PFB readout v2) has a firmware bug where the IQ values output by the readout have a nonzero offset: both I and Q are centered around -0.5 if the ADC doesn't see a real signal. The tProc-configured readout (readout v3) and the new version of the muxed readout (PFB readout v3) share this problem. This PR adds a "iq_offset" constant for each readout, which is used to correct the data, and this constant is set correctly (based on recent or past testing) for every readout block.
There's also a minor bugfix that affects the timestamp updates for PFB v3 readout.
We have known for a long time that the muxed readout (PFB readout v2) has a firmware bug where the IQ values output by the readout have a nonzero offset: both I and Q are centered around -0.5 if the ADC doesn't see a real signal. The tProc-configured readout (readout v3) and the new version of the muxed readout (PFB readout v3) share this problem. This PR adds a "iq_offset" constant for each readout, which is used to correct the data, and this constant is set correctly (based on recent or past testing) for every readout block.
There's also a minor bugfix that affects the timestamp updates for PFB v3 readout.