I did a new cal on the H4. It turned out as before, so the old cal was good.
Here are my notes.
H4 phase 1.5 after cal, no cal devices attached. w coax (75 VoP) extension, 1475 ps delay to correct, phase -13.6
After power cycle, phase 1.8 !!
connected coax again, phase -17.0, delay 1460 ps to correct
So...it seems that I need to cycle power after a cal, and then reload the cal. Hmmm...every time I checked, after the first time, the results were close enough.
Saver v0.4.0 - what a mess. Windows 10 x64.
phase1.81 Error during sweep Stopped list index out of bounds
Manage. Don't know how this actually works.
Change to 101 point (H4 is 401), BANDWIDTH to 1000 Hz (H4 is 100)
No error this time, so it seems that Saver doesn't like 401 points. S11 phase -17.14, Saver apparently stops H4 from displaying the sweep, so tapping on screen updates. No. Not always.
Delay -731 ps - no delay applied in H4
Saver left H4 in unstable state, so cycled power
Saver after App
H4 phase -17.1, Saver -17.09
Saver delay -730 ps. as before.
** Note here that Saver is still reporting a delay way off from the H4 and App. And that these values are in the ballpark of what I observer previously, so Saver is consistent. I don't know what I am doing different from you folks, but I sure don't get useful delays. Sure the phase goes to zero, but the delay is way off from the H4 and App.
App v1.1.208 1.783
After power cycle, no delay on H4, phase 1.789
w coax (75 VoP) extension, H4 phase -17.1
App phase -16.84, delay 1463 ps
Disconnected. Closed App. H4 still sweeping.
Checked points, delay, bandwidth...all unchanged, BUT Saver changes those in ways I don't understand yet.
** At one point, App went into a loop on access violation. Needed to kill it. Wouldna shutdown.
Reran Saver. See above.
So at least App is in the same range as the H4. But they should all agree much closer than this. It's all just number crunching. Same numbers, should be same results.
If there is some trick to running Saver, I'm open to suggestions.
Rich NE1EE