Thanks for your responses.
I've tried a few time bases ranging from the default down to 20uS.
Occasionally I get a waveform displayed that looks rough and this could be representative of the actual signal but any attempts to change timebase, change volts/div or interrupt the signal causes all communication with the software to fail. To recover I have to shut down the software, remove the USB, wait a bit, plug back in, wait, and then start the software. Most of the time it won't acquire anything after that either and I have to repeat.
Something is not right.
Maybe 1 time in 5 or so it will start displaying the signal and triggering normally for a bit before hanging. When it hangs button response takes 10 seconds and I can't close the software without using task manager.
It's a bit frustrating.
Just tried data logger mode and it produced a trace right up until the moment I switched my source on. I'm using a 100Mhz scope probe with the x10 switch active. Closed the software, then attached to my 1v/1kHz cal signal and the software just hangs.
My USB voltage is 4.6v, measured on a USB port with my DMM, so I wonder if this is the issue. I wonder if the PCBScope is dragging it even lower.
I've added in a powered USB hub, which is powered from a low ripple 5.04v switching power supply. In datalogging mode it'll run for a bit with no input and even sometimes continue to display a trace after switching on my analogue scope and measuring the cal signal, but if I turn the analogue scope off I can immediately hear that windows reports the PCBscope has been removed.
I'm not sure what else to do here. Is this unit defective?