Test and Measurement Forum

Fast USB driver in sleep mode

Forum for discussing PicoScope (version 5)

Fast USB driver in sleep mode

Postby jyh » Fri Aug 04, 2006 1:28 pm

When time scale is >20ms/div, Picoscope remains in sleep mode whatever the mode selected (standard, chart recorder or block mode).
More details in http://hemery.sytes.net/Pico/fast-usb-driver.htm
Any advice?
Thank you
jyh
Active User
Active User
 
Posts: 13
Joined: Wed Nov 23, 2005 3:48 pm
Location: CERN (Geneva)

Postby Michael » Mon Aug 14, 2006 9:55 am

Hello,

I was not able to load the web page via the link. Could you confirm the address?

Also, is this function direct from the driver or are you using PicoLog or PicoScope?

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby jyh » Tue Aug 15, 2006 8:35 pm

Hello,
The link http://hemery.sytes.net/Pico/fast-usb-driver.htm is valid
and has been recently accessed from UK according to its attached log file.
Nevertheless, the consistant amount of upgrades that flooded
over the past days from MS may have disrupted the access to this site.

Yes, PICOSCOPE is the software package in use and that, despite the latest
fast USB driver, still encounters problems with time windows larger than 20ms.

Regards
JyH
jyh
Active User
Active User
 
Posts: 13
Joined: Wed Nov 23, 2005 3:48 pm
Location: CERN (Geneva)

Postby Michael » Wed Aug 16, 2006 7:53 am

Hello JyH,

Thank you for the confirmation.

There seems to be a couple of things here.

The timebase you mentioned was >20ms but the screenshot shows a 200ms timebase. Typical problems appear when using 200ms or greater AND a trigger mode. You are not using a trigger but a similar problem is occuring.

Right, so lets look at the DrDAQ. In essence it behaves like a digital storage scope but it is not a true DSO. The samples taken are digitized and sent directly to the PC. The CPU dictates the timing and the samples are stored in the driver buffer. When sampling at >=200ms/div and using a trigger, the unit will need to sample blocks for transfer to the application. Triggering is not supported outside of this block mode.

Now the problem you are seeing does not invlove the trigger. So, I think I remember from previous posts that you are using the USB adapter?? If so, then there is a solution that we are currently working on that will fix this problem. I know some changes were released in the last version of PicoScope (5.14.6), others will follow.

Best regards,
Michael
Michael - Tech Support
Pico Technology
Web Support Forum
Michael
Zen Master
Zen Master
 
Posts: 656
Joined: Thu Jul 07, 2005 12:41 pm
Location: St Neots, Cambridgeshire

Postby jyh » Thu Aug 17, 2006 8:21 am

Hello Michael,
Thank you for your reply. I will keep using the // interfaces till the next software release. My interest in using the USB interface type comes from the use of light portable laptops that no longer provide the // port socket.
Regards
JyH
jyh
Active User
Active User
 
Posts: 13
Joined: Wed Nov 23, 2005 3:48 pm
Location: CERN (Geneva)


Return to PicoScope 5

Who is online

Users browsing this forum: No registered users and 2 guests