Setting or changing default setup parameters, series 5000.

Post any questions you may have about our current range of oscilloscopes
Post Reply
Posts: 1
Joined: Mon Dec 16, 2019 6:32 am

Setting or changing default setup parameters, series 5000.

Post by jacasey »

Hi - I have a series 5000 scope, and have successfully used it in embedded test systems. I am working on a new job for a client that will be similar - they want to bury the scope for checking saved waveforms after a fault. This job, howver, won't have a computer hooked up by default.

I would like to change the default setup parameters so that it always powers up in a particular configuration (always "running", waiting for a trigger on a digital line, particular timebase, range, sample depth, etc.) That way the data will be available from the last burst triggered on a fault when the user plugs in a laptop to examine. I didn't see any reference in the 5000 manual or the SDK manual for changing these settings, but may have missed it. Can you help me?

Jeff Casey
Rockfield Research Inc.
Las Vegas, NV, USA

Posts: 1034
Joined: Mon Aug 11, 2014 11:14 am

Re: Setting or changing default setup parameters, series 5000.

Post by Gerry »

Hi jacasey,

If you mean that the data from a previous session created on the a laptop would be available on the same laptop, when they plug the PicoScope in, then yes, that is true. If, on the other hand, you mean that the user will be able to see the data from the previous session on a different laptop to the one on which it was created, then that it is not possible as the data is not stored on the PicoScope (it is overwritten once it has been transferred to the Laptop).

If you are using the same laptop, and you want the previous session data to be easily available to an inexperienced user, then you could just ask them to go to 'File->Recent_Files', and click on the top file. If you absolutely want it completely automated, then it's a lot of work for little improvement, but you could use our Automation commands, running from a batch file, e.g.:
@echo off
echo Opening PicoScope 6 and the last bust triggered fault /a /a File.Open.IO=C:\Users\{Your Windows User Name}\{path to the file}\{file name}.psdata

where {path to the file}\{file name} is where you save the fault file to, in Alarms.
You could turn this batch file into an executable file, so that they just need to click on the shortcut of the executable, say, on the desktop, instead of the PicoScope 6 shortcut on the run menu, after connecting the Laptop to the PicoScope.


Technical Specialist

Post Reply