Spectrum parameter 64001 represents a list of the amplitude values of the most recently fetched trace. In case we want to get the associated frequency of each point in the list - through a driver or Automation script - what is the best way to do so?
Is there another spectrum parameter which can directly provide the frequency points, or should we calculate these ourselves based on start freq, stop freq and number of points?
How is this handled by Cube?
Note: for various reason we don't/can't go through a spectrum script, so the question is specifically how to get this data via a driver or Automation script.
Wouter Demuynck [SLC] [DevOps Advocate] Answered question 31st January 2023
Some things to be aware of:
- Cube does not receive its values directly from the connector. There's an SLSpectrum module in between which manages multiple simultaneous client sessions and monitors.
- Cube receives the values for its session via the 64xxx parameters. These parameter IDs are the same ones which the connector uses to pass trace information towards SLSpectrum
- Depending on how the connector has been written, the connector might not continuously be feeding new trace data into parameter 64001 but might only do so when requested to by the spectrum module. I guess that depends on the driver.
Wouter Demuynck [SLC] [DevOps Advocate] Answered question 31st January 2023