Test and Measurement Forum

ADC-212/3 application upgraded from LabView 6i to Labview

Post any questions about our parallel port products

ADC-212/3 application upgraded from LabView 6i to Labview

Postby taarhaug » Thu Jun 01, 2006 7:16 pm

hi,

we've been using ADC-212/3s on several test rigs for fuel cells for years. the application is current interrupt measurement of the electrolyte resistance. for this and external trigger is used.

without too much knowledge of the source code running under LabView 6i we recently upgraded to LabView 8. This caused an error in functionality of the oscilloscope: the trigger only works once. Running the picoscope software works fine. Upgrading to the latest drivers did not solve the problem.

Any suggestions on how to solve this problem?

Thor Anders
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby Michael » Fri Jun 02, 2006 2:25 pm

Hello Thor,

Can you post your VI for this?

I will have a look at it for you.

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby taarhaug » Tue Jun 06, 2006 1:02 pm

you can have a look at your own code: ADC200_testvi.vi

basically, the first trigger is performed but the subsequent ones are not. I have to exit LabView to get the scope LED back on.

Thor
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby Michael » Tue Jun 06, 2006 1:12 pm

Hello Thors,

You will need to call the close_unit function to close the driver succesfully.

Please check the documentation for function declarations.

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby taarhaug » Tue Jun 06, 2006 1:26 pm

...since the .vi works perfectly under LabView 6i, where and why is the close needed? :)

TA
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby taarhaug » Tue Jun 06, 2006 2:17 pm

I tested the close option, and this is what happened:

Labview version:

6i: works as before
7.1: triggers once, then crashes labview
8.0: triggers once, then crashes labview

you tell me that this is not a driver problem.

Thor
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby Michael » Wed Jun 07, 2006 9:12 am

Hello THor,

I still believe this is a labview problem. The driver works fine as displayed when running PicoScope software. I will have to look more closely at the VI for the 212.

We are looking at overhauling our Labview example code to improve functionality.

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby taarhaug » Wed Jun 14, 2006 2:17 pm

I am trying to debug the adc200.vi. The first run gives a adc200_get_status value of 0 while the next run 13. I can't find 13 in the documentation?

Thor.
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby taarhaug » Wed Jun 14, 2006 2:43 pm

nevermind. fixed it somehow.

thor
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway

Postby Michael » Fri Jun 16, 2006 3:08 pm

Hello Thor,

Error code 13 means unable to open the unit. in this case, LabVIEW has already opened the driver so it cannot open again.

YOu may have noticed that it will be OK if you close LV and reopen it. You must call the close_unit function to drop the driver.

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby taarhaug » Mon Jun 19, 2006 12:43 pm

Well, that makes sense then.

My fault your initial response did not work for me: inserting the close_ function gave no arguments by default. Little did I know that port number was required. Once reading the function declaration I added the proper argument and it worked straight away.

Thor Anders
taarhaug
Active User
Active User
 
Posts: 7
Joined: Thu Jun 01, 2006 3:02 pm
Location: Trondheim, Norway


Return to Parallel Port Products

Who is online

Users browsing this forum: No registered users and 0 guests