Wow Thanks ! - I guess it was kind of obvious but yes, plugging in a mouse really makes a difference - recommended !
There are still unresolved issues around VNA calibration and saving of calibration.
One has been referred to already by Ghislain
Am I correct in assuming that in such case, after the user calibration (OSLT) has been successfully performed, the status in the upper left of the screen would have to change to Cor (=calibrated)?
Now it shows --- regardless of what I do.
According to the user manual on page 76:
3.5.6 Calibration
Set calibration related items. The calibration status is displayed in the upper left corner of the screen.
The calibration status and display are as follows:
No calibration data --- (displayed in gray)
Calibrated Cor (displayed in blue)
Correction Off Off (displayed in gray)
Need to re-calibrate C? (displayed in blue)
I experience the same - the unit seems to be calibrated (I know this becuase I am calibrating with a known dodgy load and it accounts for it perfectly). But it is disconcerting to see that the status is ---
I did find that if I do 1-port Cal followed by just an "Open" Cal the status changes to "Cor" and the 1-port cal is not lost. So there is another good work around.
It begs the question: What is the point of having a menu option just for "Open" calibration and another for "Short" Calibration when there is none for "Load" Calibration ? I mean if you want to do a calibration you either select "1-port" or "Through" which include all elements.
OK, next problem. When you Save the calibration to a file, switch the instrument off, switch on again, it has lost the calibration. Aha - but you saved it to a file ? Load the file and, yes you guessed it, you have still not got your calibration back. The only answer is to repeat the calibration.
Now this is not a huge problem because I think you probably need to calibrate at every use anyway - especially if you've had the instrument off and come back for another session. But you are supposed to be able to do this and it makes me queasy that if some of these small items don't work, what is there that also doesn't work and that might give you really dodgy results when you don't realise it?
After having read everything I can find, I am now starting to think that this might all be down to the unit being an "upgraded" SSA. Perhaps the firmware is trying to deal with a use case that it wasn't written for - like maybe there isn't a proper factory VNA calibration file and it is getting into a twist as it tries to combine a non-existent file with a user cal file.
I did have a look at the logs and thought I may have the answer but there are log entries to say successful factory vector calibration applied, so it probably isn't that after all. But perhaps something similar that I haven't thought of ?
Regards
Eloso