Time/post-trigger delay bug?

Forum for discussing PicoScope version 6 (non-automotive version)
Post Reply
adynis
Active User
Active User
Posts: 11
Joined: Sun Mar 22, 2009 2:26 am

Time/post-trigger delay bug?

Post by adynis » Thu Apr 09, 2009 10:16 pm

Hello,
It's about a picoscope 2204.
Trying to understend the post trigger delay I observed some unusual things:
- If i set a time delay which it is "in the screen" (entire arrow is visible when selecting the trigger yellow point) it's ok
- If i move the triger to the left and the arrow tries to get out of the screen, something will go wrong: Picoscope freeze OR the signal simply doesn't appears OR it changes to "stop capturing". I can't see the signal anymore. In ~ 60% of my tests with the trigger "out of screen" I got to a freeze of picoscope in first ... minute. If i disconnect the usb cable, it comes back working ... but without the scope attached to it ... so .. no signal.

I attached some screenshots with the trigger in the 2 cases: the trigger arrow in the screen (and working) and out of the scren (and not working)


Which is the problem here ? It's a mistake of mine?, it's a software bug ? It's a hardware bug ?
Thank you.

~~~~~~~~~~~~~~~~~~~~~
I have Windows Vista x64
PicoScope® 6 - PC Oscilloscope software version: 6.2.2.12
Copyright 1995-2009, Pico Technology Ltd

Model: PicoScope 2204
Serial Number: [...]
USB Version: 2,0
Calibration Date: 6 octombrie 2008
Hardware Version: 16
Driver Version: 2, 0, 8, 1
Attachments
Help Example.png
This is the help example which i wanted to try
(156.62 KiB) Downloaded 48 times
FastPrintScreen 13.png
If the time trigger delay is "in the screen" it works fine
(89.38 KiB) Downloaded 47 times
FastPrintScreen 14.png
if the delay is "out of the screen" it stops displaing the signal or it freeze
(79.11 KiB) Downloaded 52 times

Robin
Advanced User
Advanced User
Posts: 558
Joined: Fri Sep 19, 2008 10:17 am

Post by Robin » Tue Apr 14, 2009 9:24 am

Hi

This does appear to be a software bug. I will report it to our development team.

Thanks for bringing this to our attention.

Robin

adynis
Active User
Active User
Posts: 11
Joined: Sun Mar 22, 2009 2:26 am

Post by adynis » Tue Apr 14, 2009 10:19 am

I understand that you could reproduce this problem.
I'm glad to hear that it isn't a hardware problem because this means that it will be resolved in the feature.
Usually ... what is the time period to resolve this kind of bugs ? Or ... in other words ... whan could i espect to appear a new version of PicoSoft ? (aproximatively)

Thank you

Robin
Advanced User
Advanced User
Posts: 558
Joined: Fri Sep 19, 2008 10:17 am

Post by Robin » Tue Apr 14, 2009 12:16 pm

Hi

The bug should be fixed in the next release of PicoScope 6. We don't have a planned release date currently, I'm afraid. However, we are always updating and adding features and new releases occur roughly every 1-2 months.

You can subscribe to our newsletter, to keep up-to-date with releases.

You can also email us: support@picotech.com

Robin

adynis
Active User
Active User
Posts: 11
Joined: Sun Mar 22, 2009 2:26 am

Post by adynis » Fri May 08, 2009 9:47 pm

Is there a full list with the changes resolved in every version of picoscope 6 ?
I think the problem in this topic hasn't been resolved yet :p

Robin
Advanced User
Advanced User
Posts: 558
Joined: Fri Sep 19, 2008 10:17 am

Post by Robin » Mon May 11, 2009 7:28 am


Post Reply