PicoScope 7 Software
Available on Windows, Mac and Linux
Bug in 6.14.10
Bug in 6.14.10
Hello.
I think I found two bugs in the Picoscope 6.14.10 software.
1.) If you use masks in a measurement and add an alarm to save the Buffers when the mask test fails and then open the saved file in Picoscope the opened file will start saving the buffers again (as the mask tests fails again). If you have two views for two channels active and two masks it will save the data twice if both masks fail in that file. Interestingly the second file is a little bit bigger than the first originally saved file.
2.) If you have have a time domain measurement and add a spectrum view to that and then want to save a *.mat file then the Sampling-Timebase in the Matfile is wrong.
Unfortunately I can't upload a testfile as it tells me "http error" when I try to.
Regards
Christian
I think I found two bugs in the Picoscope 6.14.10 software.
1.) If you use masks in a measurement and add an alarm to save the Buffers when the mask test fails and then open the saved file in Picoscope the opened file will start saving the buffers again (as the mask tests fails again). If you have two views for two channels active and two masks it will save the data twice if both masks fail in that file. Interestingly the second file is a little bit bigger than the first originally saved file.
2.) If you have have a time domain measurement and add a spectrum view to that and then want to save a *.mat file then the Sampling-Timebase in the Matfile is wrong.
Unfortunately I can't upload a testfile as it tells me "http error" when I try to.
Regards
Christian
Re: Bug in 6.14.10
Hi Fasti,
Regarding your points:
1/ The reason that happens is as follows:
(a) The default state on startup is for PicoScope 6 software to be running a capture with no trigger, so that the user can see that the PicoScope is working. That is important behaviour and not likely to change.
(b) Let's say that you have a saved data file that includes a mask that is set up to trigger an alarm if the mask fails, and the mask is set set up for a specific waveform from the Signal Generator. Now, when you load it, the capture will run, the mask will fail and the data file will be saved. If the waveform is from an external signal source (which is common usage), then the capture will run and the mask won't fail (unless the external signal, occurring at start up, happens to be the error signal that the mask has been set to catch and fail).
So, with both (a) and (b) occurring, you get the behaviour that you are experiencing, and therefore this is not a bug. It's expected behaviour (and in fact, can be usable for externally generated signals). So, you just need to be aware of this when loading the data file. This is especially true where you have the alarm action of 'Resume Capture' after saving the data file. With 'Resume Capture', the newly loaded data file will continually save files to your hard drive, if the signal source is the Sig Gen, but there are some ways to stop the continual saving activity here: https://www.picotech.com/support/topic31951.html?&p=112341&hilit=alarm+save+file#p112341).
However, if you really want to avoid the save on startup behaviour, then you can do that by saving your mask/alarm setup as a settings file. That way, you can start PicoScope 6 without the autosave behaviour and manually load the settings file for your mask/alarm setup, while no capture is running.
2/ Could you attach your data file to an email, referring to this topic, and send it to support@picotech.com. In the meantime you could try working with CSV files (if you're number of samples is less than the Excel limit for the number of rows).
Regards,
Gerry
Regarding your points:
1/ The reason that happens is as follows:
(a) The default state on startup is for PicoScope 6 software to be running a capture with no trigger, so that the user can see that the PicoScope is working. That is important behaviour and not likely to change.
(b) Let's say that you have a saved data file that includes a mask that is set up to trigger an alarm if the mask fails, and the mask is set set up for a specific waveform from the Signal Generator. Now, when you load it, the capture will run, the mask will fail and the data file will be saved. If the waveform is from an external signal source (which is common usage), then the capture will run and the mask won't fail (unless the external signal, occurring at start up, happens to be the error signal that the mask has been set to catch and fail).
So, with both (a) and (b) occurring, you get the behaviour that you are experiencing, and therefore this is not a bug. It's expected behaviour (and in fact, can be usable for externally generated signals). So, you just need to be aware of this when loading the data file. This is especially true where you have the alarm action of 'Resume Capture' after saving the data file. With 'Resume Capture', the newly loaded data file will continually save files to your hard drive, if the signal source is the Sig Gen, but there are some ways to stop the continual saving activity here: https://www.picotech.com/support/topic31951.html?&p=112341&hilit=alarm+save+file#p112341).
However, if you really want to avoid the save on startup behaviour, then you can do that by saving your mask/alarm setup as a settings file. That way, you can start PicoScope 6 without the autosave behaviour and manually load the settings file for your mask/alarm setup, while no capture is running.
2/ Could you attach your data file to an email, referring to this topic, and send it to support@picotech.com. In the meantime you could try working with CSV files (if you're number of samples is less than the Excel limit for the number of rows).
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: Bug in 6.14.10
Hello Gerry.
Thanx for your reply. I am not sure if you are talking about the same issue....
In my case I record data on one computer with a picoscope where I set the mask to a certain limit where I want to detect spikes of a voltage source (not the signal generator) and let the alarm save that to a psdata file. This file is then moved to another computer without a picoscope attached to it but with the picoscope 6 software on it and I open that file and as soon as it opens, it starts to save the data again. As there is no picoscope attached the triggering is not active and even if a picoscope would be attached I doubt that it might fail the mask test with that settings I use for the mask test. I just want to see the recorded data and do some measurements on it or save it as mat file.
For your suggestion with the csv... that won't work as we save 62Mpoints of 15 Bit 2 channel data. I will send a file to the support address as soon as I have regained access to my measurement files. Due to the Corona-crisis we have to work from home.
Fortunately now I can at least upload the small file for the mask test.
Regards
Christian
Thanx for your reply. I am not sure if you are talking about the same issue....
In my case I record data on one computer with a picoscope where I set the mask to a certain limit where I want to detect spikes of a voltage source (not the signal generator) and let the alarm save that to a psdata file. This file is then moved to another computer without a picoscope attached to it but with the picoscope 6 software on it and I open that file and as soon as it opens, it starts to save the data again. As there is no picoscope attached the triggering is not active and even if a picoscope would be attached I doubt that it might fail the mask test with that settings I use for the mask test. I just want to see the recorded data and do some measurements on it or save it as mat file.
For your suggestion with the csv... that won't work as we save 62Mpoints of 15 Bit 2 channel data. I will send a file to the support address as soon as I have regained access to my measurement files. Due to the Corona-crisis we have to work from home.
Fortunately now I can at least upload the small file for the mask test.
Regards
Christian
- Attachments
-
- maskfail-save-bug.psdata
- (443.76 KiB) Downloaded 376 times
Re: Bug in 6.14.10
Hi Fasti,
O.K. I see your point, which is not desirable behaviour (I was assuming that you were loading the data file for setting up the capture, rather than for analysis).
Thanks for bringing that to our attention. As this could be more of a problem than just deleting one file, with unattended capture, and an alarm that restarts the capture, I will raise it with our development team.
Regards,
Gerry
O.K. I see your point, which is not desirable behaviour (I was assuming that you were loading the data file for setting up the capture, rather than for analysis).
Thanks for bringing that to our attention. As this could be more of a problem than just deleting one file, with unattended capture, and an alarm that restarts the capture, I will raise it with our development team.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: Bug in 6.14.10
Hi all.
I just wanted to see if the Bug was fixed now that it's nearly 2 years that I reported it and well, it is not!
Regards
Fasti
I just wanted to see if the Bug was fixed now that it's nearly 2 years that I reported it and well, it is not!
Regards
Fasti