Unexpected Behavior of Automation Commands

Having problems ? let us know the details here
Post Reply
Hailey7891
Newbie
Posts: 0
Joined: Wed Sep 30, 2015 1:50 am

Unexpected Behavior of Automation Commands

Post by Hailey7891 »

I am trying to program through Automation Commands of PicoScope 6. Those features, such as configuring, obtaining waveform data, getting measurements and even FFT data, are all necessary for us to help auto-testing come true.
At the beginning, there seemed like meet our all requirements, but now, more testings, more problems. These problems are so big, I have no idea if I should continue the development in this way.
Maybe you can also provide us supports to solve those problems. I list some of them as following.


1. The waveform data got by “Copy.AsText” is different from the screen display, different from that got by [File > Save As…]. Why, I can not figure out what’s going on?

2. With the command “Copy.AsText”, I found some unexpected string of “NaN” in the clipboard buffer.

3. In some unknown cases, with the command of “PicoScope /a Measurements.CSV?”, “Command Prompt” seems like failing to wait an end-string terminator, just continuous data flow with white-space coming. In the data flow, only part of them is about measurements while the rest all is just white-space. The point is even that part of valid data flow is also only the part of expected measurements, such as “A, Cycle Time, 999.9ms, ”.


4. > PicoScope /a Trigger.Type.SelectedItem=Simple Edge
> 0ms: Trigger.Type.SelectedItem=Simple
> Error: the command Trigger.Type.SelectedItem=Simple failed
I thought it should not have failed, but obviously, the string “Edge” after the white-space is ignored.


5. With adding or deleting the spectrum views, it is impossible to get measurements of the old scope view any more. (Of course, I am sure there are always still some measurements kept in that scope view)
> PicoScope /a Measurements.CSV?
> 0ms: Measurements.CSV?
> NONE


6. Attempt to do some configures which are hidden in extension dialog is always failed unless you have opened that dialog at least once time after PicoScope 6 starts. For example, “Lowpass Filtering”. With the below command sent, you will find it does not work when you open the dialog and check this.
> PicoScope /a Channel.#0.LowPass.Enable.Checked=True

Hailey7891
Newbie
Posts: 0
Joined: Wed Sep 30, 2015 1:50 am

Re: Unexpected Behavior of Automation Commands

Post by Hailey7891 »

1. The waveform data got by “Copy.AsText” is different from the screen display, different from that got by [File > Save As…].
You can recreate this issue referring to "File.SaveAs vs Edit.CopyAsText".

5. With adding or deleting the spectrum views, it is impossible to get measurements of the old scope view any more.
You can recreate this issue referring to "fft vs measurements.PNG".


Thanks!
Attachments
File.SaveAs vs Edit.CopyAsText.txt
File.SaveAs vs Edit.CopyAsText.txt
(224.83 KiB) Downloaded 555 times
File.SaveAs vs Edit.CopyAsText.pssettings
File.SaveAs vs Edit.CopyAsText.pssettings
(4.31 KiB) Downloaded 434 times
fft vs measurements.PNG
fft vs measurements.PNG

AndrewA
PICO STAFF
PICO STAFF
Posts: 401
Joined: Tue Oct 21, 2014 3:07 pm

Re: Unexpected Behavior of Automation Commands

Post by AndrewA »

Hi Hailey,

1. Differences between 'file save as' csv and 'Copy as text'
I found a number differences between the two-
-The waveforms start at a different place compared to picoscope.
-'Copy as text' has a few more samples.
-If a low pass is applied to channels the 'Copy as text' samples are not filtered.
-There is an offset in the sample times

I have created bug in our ticket system am waiting feedback from our development team.
Please use the data from the 'File' 'Save as' menu, this matches the data seen in the Picoscope buffer windows.

2. Try clicking on (select) the graph view before issuing the measurement command. (In your picture the spectrum view is selected)
I not sure if you can change the select view via the automated commands.
Regards Andrew
Technical Specialist

Post Reply