Reply To: Queued Sweep Bug?

I wanted to come back to this — sorry, I had some work travel and haven’t been able to finish off updating y’all and doing some testing.

What we found:

The SM200B’s *did not* have this synchronization issue. When we kick them both off at the same time, with the same 10MHz reference and queue scans, it can run for hours and still be 1:1 in sync with scans.

With the SM200C’s, we notice a divergence right away. I assume with the latency inherent in networking, we end up with multiple scans on one done before the other even gets the command. Makes some sense. But I would’ve thought that if we queued the same # of sweeps and finished them that we’d see identical numbers at the end, which we aren’t. It might be an issue with our trigger line for counting sweeps?

So we went to try and work around it, but just doing the single sweeps at a time. Which works for us, and seems to count correctly (potentially exonerating our trigger line? If it counts correctly here, then it should be able to count queued sweeps too, right? The queued sweeps are ~20% faster though…but that’s fine for us for now).

I think that we might need to scope the GPIO outputs during these sweeps to figure out what’s going on.