[4] As soon as I start the Picoscope 6 Automotive software I hear the unloading of a USB device while almost on the same time the software says that no suitable device is found:
3_niet_herkend_in_pico_software.png
[5] When I check the device manager after [4] the Picoscope doesn't show up in the device manager list:
4_uit_device_manager.png
So for some reason the "recognized" Picoscope gets unloaded as soon as the Pico automotive software is loaded resulting in the software not finding a suitable instrument.
Do you know how I can resolve this issue.
What I did so far:
-> reinstalled the software with the repair option
-> rebooted my windows pc several times
-> performed all the above as a "Windows"-administrator
Best regards,
Asim
-->
Hi,
I am using the Picoscope 4425 with the Picoscope 6 Automotive software version: 6.12.7.2724.
Normally I am using a virtual machine but since I couldn't get the Picoscope recognized anymorewithin my virtual machine I grabbed my windows 7 pro 64 bit laptop and installed Picoscope 6 Automotive on the laptop.
Despite the fact that my laptop is a "pure" windows laptop I also didn't managed to get the picoscope up and running.
What happens is the following:
[1] I start up windows
[2] I plug the Picoscope 4425 in the usb-port
[3] The picoscope gets recognized properly by windows. As you can see it shows up in the device manager:
1_pico_goed_herkend.png
2_pico_goed_herkend.png
[4] As soon as I start the Picoscope 6 Automotive software I hear the unloading of a USB device while almost on the same time the software says that no suitable device is found:
3_niet_herkend_in_pico_software.png
[5] When I check the device manager after [4] the Picoscope doesn't show up in the device manager list:
4_uit_device_manager.png
So for some reason the "recognized" Picoscope gets unloaded as soon as the Pico automotive software is loaded resulting in the software not finding a suitable instrument.
Do you know how I can resolve this issue.
What I did so far:
-> reinstalled the software with the repair option
-> rebooted my windows pc several times
-> performed all the above as a "Windows"-administrator
It's got to be something and nothing causing your problem, I'm using Windows 7 Pro and 64 bit like you and the scope runs OK on my computer using Pico software automotive as you listed.
We had never seen anything like that before last week. Have a customer with this exact scenario now. But in this case, only the USB 3.0 port is affected. His 2.0 ports are working just fine. This is an Acer Win 7 pro 64 with good resources.
My first thought was what Martyn mentioned that there is a lack of sufficient USB power. The customer was not wanting to spend more time chasing this but if we had something else to go on I could probably talk him into it.
Asim, if you are fron NL or BE, why don’t you come along, we can try swap laptops and scope and do some research what works where. I have the same scope, win 7 x64, vista x32.
I just received a brand new 4425, installed software on a work supplied laptop and successfully connected scope hardware. However I am unable to connect to my personal laptop running windows 7 64 bit. Im having the same issues as asim, my laptop sees the scope connected via multiple USB ports but as soon as the software runs, is looses connection and all I get is DEMO mode. I have reinstalled software multiple times and experience the same issues. Ive tried running STABLE and BETA versions with no improvement. Any update on this issue? I can get by with the computer from my work but my personal would be preferred as it is way more powerful and I can bring home with me.
Maybe not relevant, which software are you running? Other devices on the usb ports in the same time?
Is scope showing ok on Device Manager? Some print screens?
Compared USB voltages and found my DELL Latitude E6440 had slightly lower out put (4.9-5.1V) than the HP I use at the shop (5.2-5.4V). I tried a USB booster cable but still not able to connect the scope. Both laptops are running latest versions of windows 7 pro service pack 1. When the scope is connected the computer makes the "ding-dong" sound and the drivers are verified, as soon as the Pico software is launched you hear the "dong-ding" as if the USB is disconnected and the software defaults to demo mode. The "connect device" menu refreshes automatically when connecting the USB but it never "finds" the scope and again defaults to demo. Same result with version 6.12.7 and 6.13.1
Hello and thank you for your feedback and so sorry this is not resolved.
Could I ask if you have access to a double headed USB 2.0 lead
I ask this because it does sound like current limitation to the Pico Device via USB 3.0 sockets/laptop
At the point of connection to your scope (Handshake) load is applied to the USB port until the handshake is complete, where by current consumption is reduced dramatically
A double headed USB 2.0 cable will move the diagnosis along by one head of the USB cable providing power and data exchange, whilst the other provides additional power only
Moving on, could we check for any environmental/current limiting settings specific to your laptop device?
Finally can we obtain a trace file from the Pico Technology folder.
This will involve connecting your scope as normal, waiting for the failure to connect, then closing the software.
Upon closure a trace file will be written to the PC, could you send this over tosupport@picotech.com