THE MESSAGE THAT FOLLOWS IS JUST A TRANSCRIPTION OF AN E-MAIL I´VE JUST SENT TO PICOTECH TECHNICAL SUPPORT A FEW MINUTES AGO. I DECIDED TO PUT IT IT HERE SO THAT A BIGGER NUMBER OF PEOPLE CAN TAKE A LOOK AT IT AND, WHO KNOWS, GIVE ME A HAND TOO! THANKS IN ADVANCE FOR YOUR HELP !
Hi,
here I am again, Sebastien, asking for your help !
I´d thought you´d like to know that I successfully put the example
(adc200.vi) to work - what was happening is that I inadvertently forgot
that I was using a 10x probe to acquire my DC signal. A pretty simple
thing, isn´t it?.
Ok. With all doubts concerning the previous misunderstanding cleared, I
decided to deeply study the manual so that I could be able to develop my
own LabVIEW program, since the provided example doesn´t run on continuous
mode and this is a necessity of my program - on the program I´m currently
developing the user should be able to, among other things, configure the
unit and eliminate the DC offset anytime he so desired.
On the studies mentioned before I found out - I think - why the example
can´t run continuosly : it´s because it would try to open the ADC 212 a
second time and, since it wasn´t closed before, a fatal error would occur
-the function used to open it returns a value of 0 if the unit could not
be opened, what makes me think I could use it to implement a decision
structure, but I haven´t tried it yet. I discovered that the function
adc200_stop can be used to stop the operation of the unit, so that if I
decided to make another data acquisition I wouldn´t need to open the unit
again, and that the function adc200_close_unit can be used to stop and
then close the unit, so that another application which would make use of
the unit could run without trouble - I think I wouldn´t need to close it,
if this application only acquired aquisition data.
On the past three days or so I committed myself entirely to the
development of the program but yesterday something quite strange started
to happen : the ADC 212/100 doesn´t seem to be working properly ! Whatever
the value of the DC power supply, the data acquired by PicoScope, the
adc200.vi and my program doesn´t change at all and, worst of all, doesn´t
really make any sense! Right know I´m trying to discover the causes of
this problem bu I think I´m running out of options ...
As always, any help you could provide will be deeply appreciated !
PS :
Yesterday I became a member of the Pico Technology Support and Discussion
Forum and so I´m going to take a look at it to see if someone already
faced a similar problem.
I´ll be anxiously awaiting your reply!
Giovani Marcelino Nesi
Design Engineer
Gavea Sensors Measurement Solutions
www.gaveasensors.com
LabVIEW program developed using adc20032.dll is not working
-
Sarah
Hi Sarah !
I thought you at Pico Technical Support would like to know that I´ve just tested the new example - sebadc200.vi - sent to me via e-mail but, to my chagrin, it didn´t worked at all. Also, in the last message I wrote I forgot to give some other information that could be vital. This new info is related to the led on the front side of the ADC-212/100.
Before the problems I related started to happen I noticed that, when I used PicoScope or the program I´ve been developing to acquire the DC signal of the power supply, the led would turn on and remain so until PicoScope or my program stopped their execution. Also, when I used the old example - adc200.vi - the led would turn on, remain so while data acquisition is being accomplished, and then turn off, as the program execution quits after the acquisition.
Now, what happens is something quite distinct. When I use PicoScope the led doesn´t even turn on at all but, as I can see in the graph, it aquires a signal that is the same regardless of changes in the signal coupling or the value of the DC power supply - I can´t really figure out the reason for this! When I use the new example - sebadc200.vi - or my program the led turns on for just an instant when the program is starting to run and then it turns off - also here, the acquired signal has the same characteristics of the signal acquired using PicoScope, i.e., it´s the same regardless of changes in the signal coupling or the value of the DC power supply.
I also think that you´d like to know that in no moment the ADC suffered mechanical shocks of any kind and that the manual instructions were followed to their fullest.
PS.:
I decided to write my message down here in the forum instead of sending it via e-mail because you people recommended it. Besides,I think this this way more can be able to help.
As always, any help would be deeply appreciated. I´ll be anxiously awaiting your reply.
Giovani
I thought you at Pico Technical Support would like to know that I´ve just tested the new example - sebadc200.vi - sent to me via e-mail but, to my chagrin, it didn´t worked at all. Also, in the last message I wrote I forgot to give some other information that could be vital. This new info is related to the led on the front side of the ADC-212/100.
Before the problems I related started to happen I noticed that, when I used PicoScope or the program I´ve been developing to acquire the DC signal of the power supply, the led would turn on and remain so until PicoScope or my program stopped their execution. Also, when I used the old example - adc200.vi - the led would turn on, remain so while data acquisition is being accomplished, and then turn off, as the program execution quits after the acquisition.
Now, what happens is something quite distinct. When I use PicoScope the led doesn´t even turn on at all but, as I can see in the graph, it aquires a signal that is the same regardless of changes in the signal coupling or the value of the DC power supply - I can´t really figure out the reason for this! When I use the new example - sebadc200.vi - or my program the led turns on for just an instant when the program is starting to run and then it turns off - also here, the acquired signal has the same characteristics of the signal acquired using PicoScope, i.e., it´s the same regardless of changes in the signal coupling or the value of the DC power supply.
I also think that you´d like to know that in no moment the ADC suffered mechanical shocks of any kind and that the manual instructions were followed to their fullest.
PS.:
I decided to write my message down here in the forum instead of sending it via e-mail because you people recommended it. Besides,I think this this way more can be able to help.
As always, any help would be deeply appreciated. I´ll be anxiously awaiting your reply.
Giovani
-
Sarah
Hi Sarah !
I´ve already figured out why my program wasn´t functioning at all! To my deepest chagrin, both the desktop AND the laptop which I used to test it had problems in their parallel ports. Last friday I decided to test it on another PC, since I really couldn´t believe why the ADC 212/100 or my program crashed all of a sudden and then, to my surprise, it worked just fine !
Thanks again gor your help !!!
P.S. :
I´ve another question but I´ll post it in a new topic!
I´ve already figured out why my program wasn´t functioning at all! To my deepest chagrin, both the desktop AND the laptop which I used to test it had problems in their parallel ports. Last friday I decided to test it on another PC, since I really couldn´t believe why the ADC 212/100 or my program crashed all of a sudden and then, to my surprise, it worked just fine !
Thanks again gor your help !!!
P.S. :
I´ve another question but I´ll post it in a new topic!