Test and Measurement Forum

picoscope works well until addition of set_ets

Post your LabVIEW discussions here

picoscope works well until addition of set_ets

Postby jeff@seametrics » Mon Mar 05, 2007 10:32 pm

hello, I am writing code for pico scope using ps3000.dll. it works quit well until I use the set_ets() command. it appears that it doesn't trigger when I activate ets(). it just hangs in run_block().

I am running a signal generator directly into my picoscope, the pico is triggered by an external signal from my signal generator. I have set this all up correctly because it works just great when I'm not using ETS. I have also put my signal generator on another oscilliscope to confirm that I do indeed have a trigger signal.

the order I am calling functions is:

1) open pico
2) set channel
3) set trigger
4) set ets
5) run block
6) wait for data to be ready
7) get times and values
8) repeat 5 to 7

I also read in another thread that a person spoke with a pico technology tech person who said to repeat steps 3 to 7. I tried this but only with the same result.... the code hangs in run_block.

I also noticed that there is some bug in your picoscope software with ETS. when I use your software I set the trigger on external and and auto and it works just fine. if I set ETS it doesn't seem to work. I have seen it work only a few times and it is generally very problematic.

I would appreciate some assistance so I can proceed with my work. A phone call would be most helpful. thank you.

Jeff
jeff@seametrics
User
User
 
Posts: 2
Joined: Mon Mar 05, 2007 10:05 pm

ETS works... I'm using the ctypes module with python

Postby jeff@seametrics » Tue Mar 06, 2007 5:25 pm

I got this ETS thing to work today, for those interested...

I should not that my code is written with Python and I'm using ctypes to call up the ps3000.dll.

the problem seemed to be that my trigger was occuring once per second. I recall something in the pico documenation regarding wait time, so I thought I'll try increasing the triggering frequency. I set my trigger to occur at 30 hz. now ets works just great. this also was a problem when I used the pico tech software. not sure why this happens....

I am using the following order of calls:

1) open pico
2) set channel
3) set trigger
4) set ets
5) run block
6) wait for data to be ready
7) get times and values

I repeat 3 to 7 for a continuous loop.

Jeff
jeff@seametrics
User
User
 
Posts: 2
Joined: Mon Mar 05, 2007 10:05 pm

Postby ziko » Fri Mar 09, 2007 4:02 pm

Hi and thank you for your post.

We are looking into your query, however there will be a delay in answering programming questions for the moment.

Kind regards
Ziko

Technical Specialist
ziko
Zen Master
Zen Master
 
Posts: 1705
Joined: Fri Dec 01, 2006 10:03 am
Location: St Neots


Return to LabVIEW

Who is online

Users browsing this forum: No registered users and 0 guests