I have a PS4444 when I connect the external power to the scope pico scope crashes on startup.
If I plug in the external power after the software is started there is no problem. (trace.004.xml)
The other traces trace.001.xml - trace.005.xml are from crashing startups.
Unfortunately, I don't have a PicoScope 4444 to hand as I'm working from home. So, to attempt to make the exact cause of the crash a bit clearer (so that we can get a faster resolution to this), could you do the following:
1/ Could you start PicoScope 6 and make exactly the same sequence of setting changes for when the PicoScope is not powered, as the setting changes you made when the PicoScope was powered, immediately after the Pico Technology Splash Screen disappears up until the Software Crashed, i.e. as listed below, and could you take screen shots of the setting changes made from the first Trigger to the end of the list, as your mouse is hovering over each final selection value to click on it:
Resolution changed to 14 bits
CollectionTime changed to 5000 s/div
CollectionTime changed to 5 ms/div
Channel A Coupling set to DC
Channel B Coupling set to DC
Channel C Coupling set to DC
Channel D Coupling set to DC
Trigger.Type.SelectedIndex=0
Trigger set to : NonAdvancedEdge
Source/Channel Index Changed to 0
Trigger Direction set to Entering
2/ Could you try attaching the PicoScope to a USB 3.00 port, and powering it from the plug in power adapter, and then running exactly the same sequence of setting changes again (no screenshots needed).
Could you then post the 2 Trace files and screenshots.
The software crashes on startup.
Without the external power (only usb power) the software runs normal.
wen picoscope is started with external power connected it crashes on startup as noted on the images in the first post.
When plugging in the external power after picoscope has started and is acquiring data there is no problem.
Tested the external power and it is exactly 5V (adapter delivered with scope)
I have also a 3403D and this starts without problemen when external power is connected.
So I guess it is a combination of the 4444 and external power on startup of the picoscope software.
If I have time i will install an older version see if the problems then disappear.
OK that would be a useful test. By the way the trace files you posted must be for a different problem then because they indicate crashes after running that sequence of commands.
ok with default startup settings on USB power everything works as it should.
On external power the data collection is not starting it wont crash but acquisition is not started.
Even if I press multiple times on the start button.
in the trace 'Device reported to application USB3.0 device not on USB3.0 port.'
This is correct it is a USB3.1 port (ASMedia USB 3.1).
So on this port USB powered ok external powered a lot of error messages in the trace xml.
We are looking into this. In the meantime, what I forgot to ask you is, did you manage to get the acquisition started when running on the different PC port?
There was an other situation I could reproduce this, I have also a 3403D and when the default config is saved with the 3403D then the 4444 crashes on startup. (this is from memory I have to set this up again to confirm this)
O j that is more the 6 seconds ago (my memory is only 6 seconds 'blub')
But tried to recreate the setup as I mentioned above and I could not repeat it, also tested on the USB 3.1 ports. Since my last post windows had got a lot of updates and picoscope software is at 6.14.44 now.
And also picoscope 7 is installed besides the 6.14 version. (none of them crashes now with external power)