G'day
I was using my ADC200-50 yesterday with the old software (?version) The frequency meter was a bit erratic in reading the waveform so I decided to update the old software I have been using for a year or so. I updated to PicoFull_r5_16_2. The new software seemed to load OK but when I open the new Picoscope I get ADC-200 not connected. I click on continue and I get waiting for ADC. When I try PicoLog under settings - input channels I get Error 13(H255 50). The red power LED is on and I have tried another parallel cable. The software manager says the LPT1 port is working OK. My ADC200 is a few years old so I chose the PicoFull_r5_16_2 version where the other version cautions only for new. I downloaded the software a second time and get the same responce. I use Download Accelerator and then burn to CD to then move it to the laptop that has the ADC200 connected to it.
I'm STUFFED??????
Wotsup?
Regards
wires
Laptop runs Win98 and PC is XP SP2
I have just successfully printed from the LPT1 port.
On my PC hard drive I found an old copy of PicoFull_r5_14_6.exe which I assume I was using on the laptop. I burnt it to CD and loaded it onto the laptop and no go??? Still not finding the ADC200 - Double stuffed.
Going to get another PC to put in the workshop in place of the laptop to see if the laptop has died.
G'day ziko
Removed from add/remove programs - Icons gone from desktop. Reload and tick as requested. Shutdown and restart - still no good.
Removed from programs/Pico - Icons gone from desktop. Go to C:\Programs and delete Pico files. Reload from a second copy and tick as requested. Shutdown and restart - still no good.
Any more suggestions?? Or do I purchase a new Scope???
G'day ziko
Went to c:\windows\system32\drivers\ and the only two things there were Gm.dis and GmReadme (Roland sound canvas sound set) there was no adc200.sys
I did a search and no adc200.sys file was found anywhere on C:\ drive (only drive on this laptop)
I am now even more confused?????
Regards
wires
Hi the instructions I gave you were for windows XP however if you are running windows 98 you will need to look in c:\windows\system\ the file that you will see pico.vxd instead.
Hi I have found an issue on 5_16_2 on one Windows98 PC that does not detect the ADC200, however after installing 5_17_1 it works, so try and install 5_17_1 and let me know how you get on?
G'day Ziko
I will try your latest suggestion in two days time when I return and let you know how it goes.
I re-installed the previous version that I was using and have found that by disconnecting the parallel cable and the power then reconnecting the power then the parallel cable I can use my ADC200 for the duration of that session. When I restart my laptop I have to go through the procedure again.
I have finished the one task that I needed to use the ADC200 for urgently. So the pressure is off for the moment.
I hope the 5_17_1 works.
I have uninstalled all previous and installed 5_17_1 and so far the scope works although when I use the frequency meter it reads 0 all the time. Voltage gives readings but I have not checked for accuracy.
I do not have the time to explore any further.
I could not attach the .pss file as it is not in the list of Allowed Extensions and Sizes in the Add an Attachment below????? I get a not allowed message when I try to attach the .pss file. Can I e-mail the .pss file to you some other way?
One channel is a BAUD signal and the other is just a square wave. I am trying to match the frequency of the square wave to the BAUD rate.
With the scope and the two meters displayed I get a varying frequency reading (sometimes 0) on the BAUD signal but the square wave is always 0 When I swap the A & B probes the scope display and meter readings change position but the readings are the same. Deleting the scope from the screen or only displaying one meter at a time still gives a frequency reading of 0 on the meter.
Thank you for your considerable help in all of this.
Hi thank you for the files, actually the psd file was better than sending the settings file because it shows what frequency you are trying to measure.
The frequency is too low to measure. Due to the way it takes frequency measurements it has to to take measurements for a period of time and calculate from that what the frequency is. The time it takes to measure the the frequency is not long enough for this low frequency.
However if you do an add measurements and choose the appropriate time base it will (two cycles on the screen) it will give the correct readings.