I'm playing around with the USB serial interface to simplify some pre-compliance tests. However, I can only get the live data out of the TinySA when the trace CALC is set to aver4 or quasi. The following commands in this order return all the same live values but none the aver4 or quasi:
- "scan 1000000 350000000 290 3" (second column)
- "data 0"
- "data 1"
- "data 2"
?
I would expect to see the following values (all with level correction):
- "data 0": "live or last? trace" when you do any of the CALC actions. If no calculation is active "data 0" returns all zero's
- "data 1": stored trace of the currently active trace
- "data 2": calculated values like average4 or quasi-peak. If no CALC was set, this would be the raw=unprocessed values.
Is that correct?
?
Just some more questions/remarks:
2) command "scan 1000000 2000000 290 3" returns '1000000?8.633344e+01 0.000000000 ' per line. The first value is the frequency, the second the "measured value" but what's the third column?
3) when setting trace.calc=aver4/quasi and then?immediately?scan, are the values already averaged? do the commands block until the scan completes?
4) scan always returns values with level correction, right?
5) "clearconfig 1234" also erases level correction?
6) Is there a command to reset to factory defaults (but keeping level correction) so when setting up a new measurement, I can start from a known configuration? or is it only possible with a manually setup preset?
7) trace with dBuV returns b'1: dB\x1dV 100.000000000 10.000000000 \r\n' \x1d is neither "u" nor "¦Ì"?
Version: tinySA v0.3, tinySA_v1.4-33-ga8bffcf
?
