|
|
| Author |
Message |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Thu Jun 01, 2006 7:16 pm Post subject: ADC-212/3 application upgraded from LabView 6i to Labview |
|
|
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 |
|
| Back to top |
|
 |
Michael Guru

Joined: 07 Jul 2005
Posts: 93
Location: St Neots, Cambridgeshire
|
Posted: Fri Jun 02, 2006 2:25 pm Post subject: |
|
|
Hello Thor,
Can you post your VI for this?
I will have a look at it for you.
Best regards,
Michael |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Tue Jun 06, 2006 1:02 pm Post subject: |
|
|
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 |
|
| Back to top |
|
 |
Michael Guru

Joined: 07 Jul 2005
Posts: 93
Location: St Neots, Cambridgeshire
|
Posted: Tue Jun 06, 2006 1:12 pm Post subject: |
|
|
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 |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Tue Jun 06, 2006 1:26 pm Post subject: |
|
|
...since the .vi works perfectly under LabView 6i, where and why is the close needed?
TA |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Tue Jun 06, 2006 2:17 pm Post subject: |
|
|
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 |
|
| Back to top |
|
 |
Michael Guru

Joined: 07 Jul 2005
Posts: 93
Location: St Neots, Cambridgeshire
|
Posted: Wed Jun 07, 2006 9:12 am Post subject: |
|
|
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 |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Wed Jun 14, 2006 2:17 pm Post subject: |
|
|
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. |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Wed Jun 14, 2006 2:43 pm Post subject: |
|
|
nevermind. fixed it somehow.
thor |
|
| Back to top |
|
 |
Michael Guru

Joined: 07 Jul 2005
Posts: 93
Location: St Neots, Cambridgeshire
|
Posted: Fri Jun 16, 2006 3:08 pm Post subject: |
|
|
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 |
|
| Back to top |
|
 |
taarhaug Active User

Joined: 01 Jun 2006
Posts: 7
Location: Trondheim, Norway
|
Posted: Mon Jun 19, 2006 12:43 pm Post subject: |
|
|
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 |
|
| Back to top |
|
 |
|