For a project I do it would be nice to have control over the PicoScope program. Preferred a TCP/IP connection.
options
- Set (horizontal) zoom factor
- Set (horizontal) scroll position
- Start capturing.
- Stop capturing.
- Set timebase
- Set number of samples
- Set trigger options.
......
It is for synchronizing the PicoScope window with a high-speed video.
When stepping trough the video the scope visible data will be automatically aligned with the video data.
So human typing is not an option, but if you can make the same interface available by TCP (witch will be quit simple in C#) this will be a nice addition to the PicoScope software for me.
Also for debugging a complex machine control, the machine control software can trigger the PicoScope program to stop sampling and save the data for later analyze.
This saves a input on the scope witch you would normally use to trigger with a digital output signal.
Tested in windows xp and works without problem.
Tested Win7-64 error message as above.
CMD start as admin (same error)
PicoScope and CMD start as admin (same error)
Problem solved, PicoScope crashed several times on my system and left 5 incances of PicoScope.*32 open in the task manager.
After I killed all instances of PicoScope.exe*32 and restarted the PicoScope program the automation commands work as expected.
It looks as though you may only be able to control a single instance of the software so there may have been some confusion if other instances of PicoScope 6 were running.
Do these automation commands help? I will put in a feature enhancement request for consideration.
The other instances were of crashed PicoScope programs, they were not visible on the screen but still consuming about 1Gig of memory. They showed up only in the task-manager.
This was because I was working with big datasets and the PicoSocpe seems not too stable with this big datasets.
The automation commands will do the trick, only they are very slow compared to commands over a TCP connection.
This is because for every command a new instance of PicoScope is started for a short time.
Still not found the automation commands to start and stop the capturing.
If the future request is for TCP automation commands it will cover both multiple instances and a speed increment for the automation commands.
It is necessary to start an instance of PicoScope 6 before sending the automation commands.
There doesn't appear to be a start/stop command - you can create your own settings file and setup PicoScope 6 to start automatically with those settings.
To stop the capture you could use a single trigger or alarm condition or Buffer.Previous.
I'll add the additional comments to the feature request.
Start/Stop is available through automation (Called Run, and Run.Pressed=true/false lets you stop and start). However, I've found a bug which means that many commands are not being reported to the command line correctly. This will be fixed in our next release, but until then please refer to the attached Commands.txt which lists all the supported automation commands.
Simply HTTP POST the command string to the URL and get a string response. The demo application uses .NET IPC and is much faster than the command line interface. It should give you an idea of what is possible with your own solution.
If you compile it yourself you'll require a copy of Griffin.Networking and Griffin.Networking.Protocol.Http or the NuGet package manager which will fetch these for you.