PicoScope 7 Software
Available on Windows, Mac and Linux
5444D MSO for Win10, no suitable device found
5444D MSO for Win10, no suitable device found
Hello,
We've been using the 5444D MSO for a while now in a Win 10 VM on a Linux host via USB3 and a power supply, and have had no issues. However, the device appears to have stopped working.
In the Win10 VM the device shows up in the Device Manager as "PicoScope 5000 series PC Oscilloscope, I've confirmed that it runs .NET >3.5, that Windows is updated, and that the red light is on. However, I no longer hear the clicking noises when starting the software and it reports that no devices were found. I've tried 6.14.10 as well as some older version ~ 6.13.something. The trace.xml contains these lines that might be of interest (I've removed the tags as I'm unable to figure out how to escape brackets to show up properly in the message):
...
Found device 0CE9_1217
Complete
Attempting to load ps5000a.dll
Finished loading ps5000a.dll
Opening device using DLL ps5000a.dll
...
Opening device unsuccessful. Error UnknownDeviceError [Timeout(323)]
No of Devices Found: 0
Complete
I've also tried connecting via USB2 and that didn't seem to make a difference.
Thank you!
We've been using the 5444D MSO for a while now in a Win 10 VM on a Linux host via USB3 and a power supply, and have had no issues. However, the device appears to have stopped working.
In the Win10 VM the device shows up in the Device Manager as "PicoScope 5000 series PC Oscilloscope, I've confirmed that it runs .NET >3.5, that Windows is updated, and that the red light is on. However, I no longer hear the clicking noises when starting the software and it reports that no devices were found. I've tried 6.14.10 as well as some older version ~ 6.13.something. The trace.xml contains these lines that might be of interest (I've removed the tags as I'm unable to figure out how to escape brackets to show up properly in the message):
...
Found device 0CE9_1217
Complete
Attempting to load ps5000a.dll
Finished loading ps5000a.dll
Opening device using DLL ps5000a.dll
...
Opening device unsuccessful. Error UnknownDeviceError [Timeout(323)]
No of Devices Found: 0
Complete
I've also tried connecting via USB2 and that didn't seem to make a difference.
Thank you!
Re: 5444D MSO for Win10, no suitable device found
Hi grmask,
Could you answer the following:
What has changed since the device was last working (including Linux distro components, VM Software version, Windows 10 updates, version of .NET being used, and PicoScope 6 version)?
How long ago was the device last working?
What distribution of Linux are you using, and what VM software are you using?
Exactly which version of .NET is being used for PicoScope 6 (and is your PATH statement correctly pointing to where it is located)?
Could you post the Trace.xml file.
Regards,
Gerry
Could you answer the following:
What has changed since the device was last working (including Linux distro components, VM Software version, Windows 10 updates, version of .NET being used, and PicoScope 6 version)?
How long ago was the device last working?
What distribution of Linux are you using, and what VM software are you using?
Exactly which version of .NET is being used for PicoScope 6 (and is your PATH statement correctly pointing to where it is located)?
Could you post the Trace.xml file.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: 5444D MSO for Win10, no suitable device found
Hi Gerry,
Thanks for your reply.
I last used it before the winter holidays (maybe early December?), so there's probably been some host/guest OS updates via APT and Windows updates, but I don't think there've been any large updates. I tried it without success, then tried updating PicoScope 6 and .NET (because one of your FAQs had mentioned that it mattered) on my guest Windows OS.
I am using Pop OS 19.10 (which I think is based on the Ubuntu distro) on my host and use VirtualBox 6.0.14.
My Win10 guest has .NET Framework 4.5.1 and 4.5.2 listed under Apps. There was no Path variable pointing to any of the .NET directories, but I've added it to both the system and user path variables (C:\Windows\Microsoft.NET\Framework\v4.0.30319) and rebooted the VM, but it still responds with the unsuitable device message.
This is the resulting Trace.XML in full (apologies, I'm still unsure how to escape the tags).
Trace opened 1/7/2020.
Using default culture: English (United States).
Splash shown after 1419.896ms
Begin
Cleanup
Begin
IPC PicoScopeAutomationServer registered
Application 'PicoScope 6' (version 6.14.10.4759) starting.
0E2F77C8CD0B9245726D0CDEF9B8E272
User is not Guest
Administrator Privileges
Running Unrestricted
Host Operating System - Windows
OS Version - Microsoft Windows NT 10.0.18362.0
.net Version - 4.0.30319.42000
Running on Mono - False
Current Directory - C:\Program Files (x86)\Pico Technology\PicoScope6
Manufacturer: innotek GmbH, Model: VirtualBox
Total Physical Memory 8589463552
Found device 0CE9_1217
Complete
Attempting to load ps5000a.dll
Finished loading ps5000a.dll
Opening device using DLL ps5000a.dll
Opening device unsuccessful. Error UnknownDeviceError [NotResponding(7)]
No of Devices Found: 0
Complete
Processor Count - 1
CPU0 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
CPU0 Architecture: 9, Address Width: 64
64Bit Operating System - True
64Bit Process - False
Command Line - "C:\Program Files (x86)\Pico Technology\PicoScope6\PicoScope.exe"
Settings file version - 11.3.1
Preferences file version - 2.0.0
Probes file version - 1.0.0
Data file binary header version - 1
Removing
No test menu file found
Creating
Done Create
Sceen resolution : 1920 x 999
Splash screen closed after 5392.2654ms
Unregistered () Button.Click
Non-forced update check
Installed Stable Version v6.14.10
Downloading release details from http://updates.picotech.com/TandM.xml?ver=061410
Xml Starts With '???<?xml version="1.0" encoding="utf-8"?>
<ArrayO'
There were no updates to display
GlobalDeviceManager.Close()
Trace Closing
Thanks,
grmask
Thanks for your reply.
I last used it before the winter holidays (maybe early December?), so there's probably been some host/guest OS updates via APT and Windows updates, but I don't think there've been any large updates. I tried it without success, then tried updating PicoScope 6 and .NET (because one of your FAQs had mentioned that it mattered) on my guest Windows OS.
I am using Pop OS 19.10 (which I think is based on the Ubuntu distro) on my host and use VirtualBox 6.0.14.
My Win10 guest has .NET Framework 4.5.1 and 4.5.2 listed under Apps. There was no Path variable pointing to any of the .NET directories, but I've added it to both the system and user path variables (C:\Windows\Microsoft.NET\Framework\v4.0.30319) and rebooted the VM, but it still responds with the unsuitable device message.
This is the resulting Trace.XML in full (apologies, I'm still unsure how to escape the tags).
<ArrayO'
Thanks,
grmask
Re: 5444D MSO for Win10, no suitable device found
Hi grmask,
We may be able to approach this another way, but it would require you emailing our support team on the helpdesk, so could you send your email to support@picotech.com and mark it for my attention.
Regards,
Gerry
We may be able to approach this another way, but it would require you emailing our support team on the helpdesk, so could you send your email to support@picotech.com and mark it for my attention.
Regards,
Gerry
Gerry
Technical Specialist
Technical Specialist
Re: 5444D MSO for Win10, no suitable device found
Thanks Gerry, will do.
grmask
grmask
Re: 5444D MSO for Win10, no suitable device found
Hi,
I noticed that this thread is already somewhat old. I'm still posting here, because I have the same exact issue as described by grmask.
I'm trying to run PicoScope 6.14.44.5870 in Windows 10. Windows is running in a VirtualBox (version 6.1.26) VM on Ubuntu 20.04.
Here is the trace.xml:
Did you ever find a solution? I would be very grateful for any help.
I noticed that this thread is already somewhat old. I'm still posting here, because I have the same exact issue as described by grmask.
I'm trying to run PicoScope 6.14.44.5870 in Windows 10. Windows is running in a VirtualBox (version 6.1.26) VM on Ubuntu 20.04.
Here is the trace.xml:
Code: Select all
-
Trace opened 30.09.2021.
Using default culture: German (Germany).
Splash shown after 519.2306ms
Begin
Application 'PicoScope 6' (version 6.14.44.5870) starting.
12B87E8CD28B94E75D0601A716A00583
Cleanup
User is not Guest
No Administrator Privileges
Running Unrestricted
Host Operating System - Windows
OS Version - Microsoft Windows NT 10.0.19043.0
.net Version - 4.0.30319.42000
Running on Mono - False
Current Directory - C:\Program Files (x86)\Pico Technology\PicoScope6
Begin
IPC PicoScopeAutomationServer registered
Manufacturer: innotek GmbH, Model: VirtualBox
Total Physical Memory 17179398144
Found device 0CE9_1217
Complete
Attempting to load ps5000a.dll
Finished loading ps5000a.dll
Opening device using DLL ps5000a.dll
Opening device unsuccessful. Error UnknownDeviceError [NotResponding(7)]
No of Devices Found: 0
Complete
Processor Count - 1
CPU0 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
CPU0 Architecture: 9, Address Width: 64
64Bit Operating System - True
64Bit Process - False
Command Line - "C:\Program Files (x86)\Pico Technology\PicoScope6\PicoScope.exe"
Settings file version - 11.5.1
Preferences file version - 2.0.0
Probes file version - 1.0.0
Data file binary header version - 1
Removing
No test menu file found
Creating
Done Create
Sceen resolution : 1920 x 1080
Splash screen closed after 3674.6092ms
Unregistered () Button.Click
Non-forced update check
Installed Stable Version v6.14.44
Downloading release details from http://updates.picotech.com/TandM.xml?ver=061444
Xml Starts With '???
There were no updates to display
GlobalDeviceManager.Close()
Trace Closing