Trigger Time

Forum for discussing PicoScope version 6 (non-automotive version)
Post Reply
Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Trigger Time

Post by Moonwalker »

On my old Hameg I had a timer showing time since last trigger. I cannot find this in Picoscope.
This is useful when measuring non repetitive signals.

Gerry
PICO STAFF
PICO STAFF
Posts: 1145
Joined: Mon Aug 11, 2014 11:14 am

Re: Trigger Time

Post by Gerry »

Hi Moonwalker,

If you mean time since the Trigger occurred for the current capture, then that value is not needed because it will always be zero. PicoScope 6 performs an adjustment of the timing of all samples so that the Trigger passes through zero.

Regards,

Gerry
Gerry
Technical Specialist

Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Re: Trigger Time

Post by Moonwalker »

No what I mean is time since last trigger.
Ex - I have similar pulses coming in every 5-20seconds. I would need to know the time since the last trigger (or time waiting for trigger) to know the time since the last pulse( or trigger).

Gerry
PICO STAFF
PICO STAFF
Posts: 1145
Joined: Mon Aug 11, 2014 11:14 am

Re: Trigger Time

Post by Gerry »

Hi Moonwalker,

This is not currently available in PicoScope 6, but is intended for an up and coming version (unfortunately, I wouldn't be able to say exactly when that will be, but pay close attention to the next Beta version).

Regards,

Gerry
Gerry
Technical Specialist

Martyn
Site Admin
Site Admin
Posts: 4491
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Trigger Time

Post by Martyn »

If you enable the preferences panel (Views->View Preferences) you will have a panel on the right that will give a Microsoft timestamp for each capture to 1 second accuracy.

The timestamp Gerry has mentioned will be in micro seconds if the scope supports the functionality.
Martyn
Technical Support Manager

Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Re: Trigger Time

Post by Moonwalker »

Thanks the Timestamp in the preferences windows may help but is not exactly as I want. You need to compare the Timestamp with the current time and compute difference to get proper Trigger time.

I think this is very easy to implement since you already have Timestamp of last trigger. Just add another label below Capture Time and compute difference with current time - updating it say every 100ms max.

Martyn
Site Admin
Site Admin
Posts: 4491
Joined: Fri Jun 10, 2011 8:15 am
Location: St. Neots

Re: Trigger Time

Post by Martyn »

Which scope do you have ?
Martyn
Technical Support Manager

Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Re: Trigger Time

Post by Moonwalker »

5444D

Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Re: Trigger Time

Post by Moonwalker »

Any update on this?

Gerry
PICO STAFF
PICO STAFF
Posts: 1145
Joined: Mon Aug 11, 2014 11:14 am

Re: Trigger Time

Post by Gerry »

Hi Moonwalker,

Our development team are working to complete the new Software version that will include the function that I mentioned above, however, unfortunately, we are not in a position to be able to give Timescales (there is a discussion about all of this here: topic40416.html).

Regards,

Gerry
Gerry
Technical Specialist

Moonwalker
Newbie
Posts: 0
Joined: Tue Feb 11, 2014 6:36 pm

Re: Trigger Time

Post by Moonwalker »

Any update on this please?
I still cant find this option in latest version.

Gerry
PICO STAFF
PICO STAFF
Posts: 1145
Joined: Mon Aug 11, 2014 11:14 am

Re: Trigger Time

Post by Gerry »

Hi Moonwalker,

Sorry, there was some confusion on my part in previously answering your question, based on what you mentioned earlier in your post. This is because the answer will be different depending upon what type of Sampling Mode and/or what type of Triggering Mode you are using.

If you have Pulses being captured every 5-20 seconds, then you will be using Normal Triggering with a Sampling Mode that is either Progressive or Non-Progressive, in PicoScope 7 (Fast Sampling Mode or Slow Sampling Mode in PicoScope 6). If you are not using Progressive Mode, the Captures will be stored in split Buffers, and can be viewed using the Waveform viewer. Once you have captured all of the pulses you want, the Waveform Viewer will be displaying the last capture, so you can step through the previous captures using the '-' button of the Waveform Viewer widget. If you click on the Widget itself, the Waveform Navigator opens, where you can then select 'On' in the 'Capture time' option, to turn on the times of each capture (as mentioned by Martyn). You can then just subtract the time of one capture from the time of the following capture to get the time between 2 captures to the precision of the nearest second. If you want higher precision than 1 second, and all of your pulses are being generated at the exact same frequency, then you can capture a high number of Pulses and then subtract the first Capture Time from the last Capture Time, then divide that figure by the number of Captures - 1, to give you a more precise Time between the Captures. This is not what I though tyou were referring to, so this is will not be something that will be done automatically by our PicoScope 7 software (or added by our Development team).

If instead, you are using Progressive Mode Sampling, then the Trigger will only Fire for the start of the Pulse Train and the rest of the Pulses will just be captured as one large Capture. If there are more Pulses to be Captured then there will be a short delay before the Software then starts capturing the next train of Pulses, once the Next Trigger has fired. If you want to know what the delay between 2 consecutive Triggers of this type is (or the delay between the end of the last Capture and the Start of the next one) then our Software does not give you this information. There is a technique that could be used to find this delay but it would only be accurate to within milliseconds (or 10's of milliseconds, depending upon how much variation there is in the time it takes for your Picoscope and computer to establish USB end point connections for transport, in between each stream of Captured data).

For Progressive Mode Sampling, with Rapid Trigger Captures you would need to be capturing pulses separated by less than 1ms and our PicoScope 6 & 7 Software does not give you this information (at less than 1 second precision).

Regards,

Gerry
Gerry
Technical Specialist

Post Reply