Test and Measurement Forum

by **Teemu** » Wed Jun 14, 2006 9:12 am

sw 5.3.19 pico 3206

What can be the problem. everytime I use long timescales (more than 500ms/div), my computer crashes to a bluescreen.

Computer is compaq NC6320 with 1gb memory and with centrino duo processor.

When using long timescales, CPU-usage goes to 100% and after a while, computer crashes.

I have tryed to adjust the maximum samplevalue /trace to smaller values, but it does't have any effects.

by **Michael** » Wed Jun 14, 2006 11:48 am

Hello,

It sounds like the continuous sampling mode is struggling to pass data thorugh the USB pipeline. You can check to see if your Windows or USB host controller has an updated driver available.

Try changing the slow sampling mode to block mode and see if this helps.

Please see the attached video on how to change to block mode sampling.

Best regards,
Michael

by **Teemu** » Wed Jun 14, 2006 3:19 pm

Hello

This blockmode helps, but in this mode I can't use this as a plotter in long timescales. I see this 50s/div scale very usable if it only works.

I tryed to search latest usb chipset drivers (intel 82801G (ich7 family) but without success

by **Michael** » Fri Jun 16, 2006 4:04 pm

hello,

It is difficult for us to pinpoint the problem as we cannot reproduce your exact environment. As Block Mode helps your slow sampling, the problem still remains that real time data transfer is not possible.

Could you try an experiment with PicoLog? Try setting a 1ms sample interval for 10k samples in realtime continuous mode? If the problem appears here too, then we are looking at a USB host/RootHub driver problem.

Also, please try another USB port on your machine.

Best regards,
Michael

by **Teemu** » Wed Jun 21, 2006 10:44 am

I tested this as you described in realtime continous mode with 10000 samples , interval 1ms and with setting" as many as possible" readings per sample.

Scope didn't crash.

What can we do next ?

by **Michael** » Thu Jun 22, 2006 10:17 am

Hello Teemu,

We are trying to repeat your scenario but we need to clarify somethings.

Can you clarify if you are using more than one scope window and can you post a PSD file with your scope settings? This should help us get to the bottom of this.

Best regards,
Michael

by **Teemu** » Thu Nov 16, 2006 12:13 pm

Hello

I updated to picoscope software to 5.15 and now everything looks fine.

I got another problem when using now recorder, I get error old ps3000.dll file found please reinstall. I did reinstall the software, but I still get the same error.

What could I do next.

Teemu

by **Michael** » Thu Nov 16, 2006 12:47 pm

Hello Teemu,

YOu will need to uninstall the PS3000, unplug and then reinstall the software. Now you will be able to plug in the scope and try again.

Best regards,
Micheal

by **Teemu** » Thu Nov 16, 2006 2:33 pm

I try twice, but still the same.

my piglog is version 5,15,5 and ps3000.dll 3,1,0,1

I used search in windows aand no other versions of ps3000.dll is found from computer.

What next ?

Best Regards

Teemu

by **Michael** » Thu Nov 16, 2006 2:56 pm

Hello Teemu,

Please download the attached DLL and copy to your Pico Directory overwriting the old version of the file.

Best regards,
Michael

by **Teemu** » Fri Nov 17, 2006 8:20 am

Hello

Now everything looks to work very fine. thank you for a fast solution.

For your future development, I am missing some features which are present normally in all standard oscilloscopes.

-option to select trace A-B and A+B. this is very useful in many cases.

- you have setting voltage range which means setting for complete screen area. usually oscilloscopes uses setting in format volts/div. at the moment it looks that voltage selection does not follow the probe multiplier setting.

Thank you for a very good product,

Regards

Teemu

Pico Technology

Test and Measurement Forum

picoscope crashes windows to bluescreen

picoscope crashes windows to bluescreen

Who is online