Is everyone's probe readout / probe detect function working as expected?
On the only probe I have with this - Cal Test CT3288ARA/P6501R discussed above - the behaviour I see is:
If I power up with the probe with readout pin connected to any channel on boot I see: "Probe detected: channel x", where x is correct channel. Probe disconnecting and reconnecting never again yields a probe detect message on any of the channels (not just the channel that had the probe attached to start with).
If I power up without any probes connected, then the "probe detected: channel x" and "probe disconnected: channel x" messages all work as you'd expect; every time you connect or disconnect a probe the message appears. .
So it seems that if you have a readout-enabled probe connected at boot that the readout only ever works that first time during the boot process and is dead ever after. Bug, faulty unit, or some weird logic I'm not understanding the benefit of?
My readout pin measures 10.7K to BNC shield.
In the niggles stakes, not having had a scope with readout before, I find it mildly annoying that if you remove a probe with readout that it goes back to 1x, instead of back to whatever you'd set it to last time you'd changed it and not had a probe with readout connected, but I guess that is just "the way it is"... On the basis of seeing how it behaves I'd almost prefer to have the readout function disabled. (eg have a probe without readout connected, set to 10x manually, connect readout probe and disconnect, it's gone back to 1x).