I recently changed the computer on which I had satisfactorily ran my
custom-made Visual-Basic script to record data from the ADC-100. Once I
tried my program on the new machine, it produced strange results.
I then realised that my new laptop was running Windows 2000 (I had prev. used Win98), so I upgraded the driver files from your website to the latest versions. However, the code STILL does not work! I checked the wiring, and all the hardware that I am using, but these are all functioning normally.
The ADC-100 unit produces normal results on my old Win98 machine with the old drivers, and I tried the same code on another Win2000 machine, and the strange results were the same. (The 'strange results' is that the ADC-100 claims to be reading a very fluctuating 613mV when it should read zero)
I then tried to run the 'example code' entitled adc10032.xls. Both inputs should read 0V (this has been checked with a multimeter), but instead I'v got readings 222 to 613mV on both channels.
*I am not using the printer adapter
*I am running a Celeron using Windows 2000, Excel 2000 and both your and our VBasic software, and getting the same glitch
*The glitch has been duplicated on another Win2000/Excel2000 machine
*I am using pico.sys V1.5 (31/July/2002), with adc10032.dll modified
22/Nov/2002 and installed in the windows\system32 folder.
*The ADC refuses to count higher that 2299, and is also fond of producing
2059. Note that these numbers are 1000 1111 1011 and 1000 0000 1011
respectively. This occurs when 0V is being given to it, and the range is set
to the higher voltage ranges. When range set lower, the results are more
random, but still very likely to be 1000 xxxx 1011.
*Both AC/DC buttons are pushed in, on the DC setting.
If you can give any insight as to what is going on, it would be greatly, greatly appreciated.