PicoScope 7 Software
Available on Windows, Mac and Linux
Command line parameter details
Command line parameter details
Hi,
Is there a resource that gives details on the command line interface? I've read the User Guide and used the command line help but I can't find the details I'm after. For example, I'd like to add a view and give it a specific name. I see how to add a view and there's a command to rename a view but I can't find the details on how to pass the desired name to picoscope.
If I use:
picoscope /a View.Rename
Then a dialog box pops up but I want to pass the name from the command line.
I shan't bore you with the different combinations I've tried; I'm sure I've missed something obvious.
If I try the Macro Recorder all it gives me is:
View.Rename.Click
I'm also struggling with how to select a view to change settings. Basically I'm trying to go through several files and set a Spectrum window for each of them with similar settings. When I try:
picoscope /a Spectrum.SpectrumBins.SelectedIndex=13
I get an error message unless I've used the GUI to select the relevant view beforehand, which kind of defeats the point.
I was hoping to:
1. create a new view (that's OK)
2. rename it "example_view_name" (so that I knew what the view would be called would be)
3. select the new spectrum view, "example_view_name"
4. change the settings for "example_view_name"
5. export the data from "example_view_name"
I guess there must be somewhere that explains the different command line options, parameters and switches but I can't find it. I have read that the command line interface is old and perhaps becoming a legacy item but it would be useful to use the bits that are there.
Any help will be appreciated.
Is there a resource that gives details on the command line interface? I've read the User Guide and used the command line help but I can't find the details I'm after. For example, I'd like to add a view and give it a specific name. I see how to add a view and there's a command to rename a view but I can't find the details on how to pass the desired name to picoscope.
If I use:
picoscope /a View.Rename
Then a dialog box pops up but I want to pass the name from the command line.
I shan't bore you with the different combinations I've tried; I'm sure I've missed something obvious.
If I try the Macro Recorder all it gives me is:
I'm also struggling with how to select a view to change settings. Basically I'm trying to go through several files and set a Spectrum window for each of them with similar settings. When I try:
picoscope /a Spectrum.SpectrumBins.SelectedIndex=13
I get an error message unless I've used the GUI to select the relevant view beforehand, which kind of defeats the point.
I was hoping to:
1. create a new view (that's OK)
2. rename it "example_view_name" (so that I knew what the view would be called would be)
3. select the new spectrum view, "example_view_name"
4. change the settings for "example_view_name"
5. export the data from "example_view_name"
I guess there must be somewhere that explains the different command line options, parameters and switches but I can't find it. I have read that the command line interface is old and perhaps becoming a legacy item but it would be useful to use the bits that are there.
Any help will be appreciated.
Re: Command line parameter details
Hi Doug,
I would suggest having a look at the following posts:
topic40358.html?&p=143430&hilit=Automation#p143430
topic38401.html?&p=136661&hilit=automation#p136661
...and considering using a Mouse click automation tool (a Google search will give you a few options).
Regards,
Gerry
I would suggest having a look at the following posts:
topic40358.html?&p=143430&hilit=Automation#p143430
topic38401.html?&p=136661&hilit=automation#p136661
...and considering using a Mouse click automation tool (a Google search will give you a few options).
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: Command line parameter details
Hi Gerry,
Thanks for looking at this. I had seen one or both of those posts when I'd been searching the forum before. But I guess the answer to my original questions is 'No, there is no resource for details on the command line interface (CLI)'.
I did appreciate that the CLI had limitations but did not realise how limited it and the macro system are. I know this is said in one of the other posts but it still surprises me that there are commands there but no documentation on how to use them.
I've got ~450 .psdata files to process and was planning to go through them using the CLI to adjust the spectrum settings but it's probably not worth doing. If I was going to consider extra software or tools then I'll look for something that'll do the job with .CSV files rather than try and use a mouse click automation tool to wrestle PicoScope into doing what I want.
Thanks for replying.
Regards,
Doug.
Thanks for looking at this. I had seen one or both of those posts when I'd been searching the forum before. But I guess the answer to my original questions is 'No, there is no resource for details on the command line interface (CLI)'.
I did appreciate that the CLI had limitations but did not realise how limited it and the macro system are. I know this is said in one of the other posts but it still surprises me that there are commands there but no documentation on how to use them.
I've got ~450 .psdata files to process and was planning to go through them using the CLI to adjust the spectrum settings but it's probably not worth doing. If I was going to consider extra software or tools then I'll look for something that'll do the job with .CSV files rather than try and use a mouse click automation tool to wrestle PicoScope into doing what I want.
Thanks for replying.
Regards,
Doug.
Re: Command line parameter details
Hi Doug,
You're correct, the answer is that there aren't any comprehensive notes to the Automation commands (as mentioned in the linked post).
The thing is that it was an internal tool which was superseded by more sophisticated test software a long time ago (in fact so long ago that the it may actually be easier to rip it out and start all over again), so no point in working on it for internal use. We have the Software Development Kit for more sophisticated applications and only a limited number of Software Developers, who are under extreme pressure to get the next version of our Software out for Test & Measurement (not to mention all of the critical bug fixes that need to be done in the old software while transitioning) so working on it for external use would create more problems than solutions.
Sorry, I forgot to add that what you could do, if you just want to change Spectrum values, is load a Settings file that is the same as the Data file (with the exception of the data and the settings that you need changed). This can be done with an automation command.
Regards,
Gerry
You're correct, the answer is that there aren't any comprehensive notes to the Automation commands (as mentioned in the linked post).
The thing is that it was an internal tool which was superseded by more sophisticated test software a long time ago (in fact so long ago that the it may actually be easier to rip it out and start all over again), so no point in working on it for internal use. We have the Software Development Kit for more sophisticated applications and only a limited number of Software Developers, who are under extreme pressure to get the next version of our Software out for Test & Measurement (not to mention all of the critical bug fixes that need to be done in the old software while transitioning) so working on it for external use would create more problems than solutions.
Sorry, I forgot to add that what you could do, if you just want to change Spectrum values, is load a Settings file that is the same as the Data file (with the exception of the data and the settings that you need changed). This can be done with an automation command.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist