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....

that should be the saved startup configuration.

Will try with empty config.

Benno

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 acquiri...

I have the idea you miss the start of the packet.
Can you set the trigger somewhat later so the whole message is visible.

Benno

Can you post a .psdata file (or link to some cloud storage with a .psdata)
An preferably can-h and can-l at the same time e.g. ch-A and ch-B

Benno

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.

Benno

You need to use the SDK for this.

There are some samples on the picoscope github

https://github.com/picotech

Benno

The sig gen has a output resistance (i think 600 ohm)
so you have actually 800 ohm and 150 nf.

for this low values of your R you need to take this into account.

Benno

I have done streaming 10Ms/sec for about 4 weeks 24/7 so it is possible.

Also done 4 ch 5Ms/sec (so a total 20Ms/sec) for about 8 hours.

O and both of the above was done on a USB2 type scope the 4424.
I have also a USB3 version 4444 scope but not tested, it should stream even faster.

Benno

I would use C++ for this and use multiple threads.
1 for reading the data from the picoscope.
1 for processing the read data (without locking the 1st thread)
1 for displaying the result or send the result to a python display app.

Benno

2 more things you can test come to mind.

1. short the inputs of the scope.
2. power down your phone. Or put it at least 10-20 meters away.
3. If your laptop has mobile connect turn that off.

Benno

set time base above 200 ms/dev and trigger at 99% and a trigger value witch will never occur.

Benno

Thanks that was the solution deep measure.

Benno

Over here,

https://github.com/picotech/picosdk-ni-labview-examples

Benno

in the example .psdata from the first post

the times below so max low time or max high time.

Benno