PicoScope 7 Software
Available on Windows, Mac and Linux
Loss of buffer data when USB is disturbed
Loss of buffer data when USB is disturbed
I ran into a loss of data-issue yesterday when a USB disturbance caused Picoscope to throw a thousand captured waveform buffers to some kind of dark computer void.
I was using a 2205 as waveform capture-device in an ESD-test (works better than expected, even at automotive ESD) where a short repetitive test pattern was captured at 10 Hz and all captures where stored in the waveform buffer. After a 1500ish captures and 30-40 ESD discharges an ESD-pulse did cause a disturbance of USB communication (the scope, USB or computer, whatever) that halted the picoscope capture as the communication went down, but when the communication was restored automatically haft a second later picoscope threw all captured waveforms from the buffer away, to my great annoyance as we had to run the test again.
Is there a method of keep captured buffer data when a communication error occurs?
For me it does not matter if it is automatically saved or i got prompted to save it manually? It is also acceptable to stop the capture and wait for user input (well, this could be a option for the user to set if they want a automagic restart or a stop&save data function..)
//Filip
I was using a 2205 as waveform capture-device in an ESD-test (works better than expected, even at automotive ESD) where a short repetitive test pattern was captured at 10 Hz and all captures where stored in the waveform buffer. After a 1500ish captures and 30-40 ESD discharges an ESD-pulse did cause a disturbance of USB communication (the scope, USB or computer, whatever) that halted the picoscope capture as the communication went down, but when the communication was restored automatically haft a second later picoscope threw all captured waveforms from the buffer away, to my great annoyance as we had to run the test again.
Is there a method of keep captured buffer data when a communication error occurs?
For me it does not matter if it is automatically saved or i got prompted to save it manually? It is also acceptable to stop the capture and wait for user input (well, this could be a option for the user to set if they want a automagic restart or a stop&save data function..)
//Filip
Re: Loss of buffer data when USB is disturbed
Hi Filip,
There isn't, currently, any way to keep the already captured data, once communication has been lost between PicoScope 6 and the hardware. When communication errors interrupt a test, most often the test is void, so there doesn't seem much point in saving invalid data (this is especially true where the communication error only rarely occurs, and where the test can be quickly repeated, which is typical when using a Scope as opposed to a data logger). So, where the communication error is due to a fault, the way to go would be to find and fix the fault.
However, if you are working in an environment where you are (a) prone to communication errors that are not caused by a fault in the PicoScope hardware, Communication hardware or software, and not rare, (b) performing a test that is time consuming to run and/or setup, and (c) you are concerned that the fault may occur after you have captured valid data, then you can set PicoScope 6 up to perform automatic saving of the data using Alarms. The data can be saved after each capture or when all buffers have been filled (for more information on saving data automatically using alarms see this post: https://www.picotech.com/support/topic40259.html?&p=143164&hilit=using+alarms#p143164).
Regards,
Gerry
There isn't, currently, any way to keep the already captured data, once communication has been lost between PicoScope 6 and the hardware. When communication errors interrupt a test, most often the test is void, so there doesn't seem much point in saving invalid data (this is especially true where the communication error only rarely occurs, and where the test can be quickly repeated, which is typical when using a Scope as opposed to a data logger). So, where the communication error is due to a fault, the way to go would be to find and fix the fault.
However, if you are working in an environment where you are (a) prone to communication errors that are not caused by a fault in the PicoScope hardware, Communication hardware or software, and not rare, (b) performing a test that is time consuming to run and/or setup, and (c) you are concerned that the fault may occur after you have captured valid data, then you can set PicoScope 6 up to perform automatic saving of the data using Alarms. The data can be saved after each capture or when all buffers have been filled (for more information on saving data automatically using alarms see this post: https://www.picotech.com/support/topic40259.html?&p=143164&hilit=using+alarms#p143164).
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist