Hi,
I have written a couple of small apps that use Picoscope Automotives command-lines to trim and convert *.psdata files.
I have found that the beta release 6.5.42 is not liking these commands. Is this a temporary problem? will command-line control still be available? It would be a shame to lose this feature.
Thanks for your reply Ziko.
I have installed the new Beta 6.5.54.0 and I am still having the same problem. It seems to stall during the conversion process.
I am currently testing this on a 32bit XP machine.
You have written some great apps so we are keen to help you with this! Can you give an example of a command line option that used to work OK, but is causing problems in the new beta?
(By this I mean what you would type in the run box or command prompt).
Hi Alan,
Thank you for your kind words. Here is a snippet of
how i am invoking the conversion and trimming processes using VB.NET.
I am using very similar code in four of my apps.
Picoscope.exe /C "C:\Documents and Settings\Rod\My Documents\Waveforms\COP_GOOD.psdata" /F PSDATA /B 1:2
A few observations that may help:
I have noticed that during the conversion process Picoscope makes the new file but nothing is written to it. The size is usually only a couple of bytes. Also, if I try to cancel the process at the Picoscope system tray icon the context menu will not draw. I find I have to kill the process in taskmanager.
I caught this 'Queue empty' Exception when using cmd.exe with the same arguments.
System.InvalidOperationException was unhandled
Message="Queue empty."
Source="System"
StackTrace:
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Queue`1.Dequeue()
at eg.d(Boolean )
at eg.a(Boolean , Boolean )
at en.b()
at kr.Execute()
at hw.a(String[] , Boolean )
at Pico.PicoScope.PicoApp.AppMain(String[] args, Boolean consoleMode)
at a.a(String[] )
InnerException:
Just to let you know, our software engineers tell me that they are aware of the problem and it will be fixed on the next release. I will keep you informed.
Just thought I'd chip in on this subject - I've been trying to convert files using the command line for a while now. To cut a long story short, it's still not working in PicoScope beta 6.7.2. Occasionally I get the desired outcome, but most of the time I get a directory full of files which are all 0k in size, and the picoscope process just sits there in Task Manager consuming a constant amount of memory (~75MB) and no cpu time.
Will this ever get fixed? It's a bit of a chore going through the files and manually converting the file type...
By the way, trial and error also suggests that the help is wrong and that in order to convert to the Matlab data format, one should use the following syntax:
I've also tried the latest beta and I am finding it fine to convert a *.psdata file to a *.csv file as long as I am not using the /b command. As soon as I use the /b (multiple waveform) command I get the same problem as mentioned - *_1.csv, *_2.csv etc all zero byte file size.
You can try sending your data file to support@picotech.com, you may get a file size too big from our helpdesk system but we do have a backup in place to pick up large files.