Hello Hexibot and thank you for the detailed feedback
With regards to
hexibot43 wrote:I had been having real trouble getting my 4423 to work properly,
Can you help here with the symptoms?
Have you experienced continual/intermittent failure of the scope to connect upon launch of the PicoScope software?
(Could you send the trace file for such an event)
Or, have you experienced issues once the scope is running during capture?
(Could you send a psdata file for such an event)
hexibot43 wrote:I had some trouble getting the Scope to complete enumeration. With the PortPilot in-line the scope would hang while attempting to connecting the scope. I'm still not sure what was going on with that. It appears to be working well now. Perhaps it was my bad USB cable causing some problems.
The USB cables in question, were they the Pico Blue USB cables?
If so have you had/suffered repeat failure of Pico Blue USB cables? I would be very interested to recover your Pico blue USB cable if this is the case to pass onto engineering for evaluation.
I stress the use of the Pico Blue USB cable as they are a high quality cable, contain additional strands of cable, complete with improved grounding. This ensures the integrity of the signals measured, during transfer to the PC (Low noise level) along with the power supply/ground.
What are the length of the USB cables under test?
There is a general acceptance in the field of USB 2.0 communication that the absolute maximum USB cable length that can be utilised is approximately 5 metres before the integrity of the power supply and data begins to suffer. (5 meters being the industry standard)
Given our scopes are powered via the USB we have to err on the side of caution and for this reason we have opted to manufacture a 4.5 meter USB 2.0 extension.
Many thanks Hexibot for the detailed information supplied as wht you have highlighted is the importance of the quality of USB link and how cable quality has a direct effect on performance.