Pocket-Sized 6 GHz 1 TS/s ET Scope

[joeqsmith]

Do you have a sense of how much your source is drifting (in ns/minute for example)? We didn't run into the issue you're describing during our QA, but we suspect our test sources had much slower long-term drift (perhaps ~100 ps per minute).

Shown sampled at 30 second intervals.   At 100ps per division or 100ps per minute drift on startup. 

Screen has 12 divisions. Center the transition using 10ps per division.  Transition is 40ps or 4 divisions.   Drift is 6 seconds per division.  Sweep rate is say a minute....  You can drag the waveform.... nope..  You can change the horz scale.... nope..  It's all locked out.  Best you can do is let everything warm up enough to allow for multiple transitions to remain on the screen for several sweeps, then enable the tracking.  It works as I let it run for about an hour last night to collect that data.   It's just not something you can measure from a cold start. 

[joeqsmith]

I tried the pre-release but I really would not limit any of the adjustments. 

I wonder if there is some difference in how we implemented the tracking that prevents you from allowing full access to all of the settings.   With mine, after I collect a sweep, I calculate the transition's center switch point.  Prior to the next sweep, I change the delay to recenter.   I do this on every sweep. 

[SJL-Instruments]

I tried the pre-release but I really would not limit any of the adjustments. 

I wonder if there is some difference in how we implemented the tracking that prevents you from allowing full access to all of the settings.   With mine, after I collect a sweep, I calculate the transition's center switch point.  Prior to the next sweep, I change the delay to recenter.   I do this on every sweep. 

The transition point is recalculated at the end of each sweep, then the timebase position is adjusted accordingly.

The concern is that the user may be in the middle of adjusting the timebase when the automatic adjustment is being applied. To solve this, we can temporarily pause tracking as long as the user is interacting with the timebase settings. The pre-release was a quick workaround in case you wanted to run additional experiments.

There are also many edge cases to consider due to interactions with other features. (For example, what to do if the user switches on/off power-user mode while the tracking is active? What if de-embedding is enabled?) For the official release, we will implement the necessary logic to handle this gracefully (or disable features for which we can't find a good resolution).

[joeqsmith]

For your software, has anyone besides me asked about adding tracking? The only reason I brought it up was to run that test for the person who had asked about it in the square wave thread.  It may be a non-issue.  Maybe just leave it as-is.  If I need to, I will just wait for things to stabilize enough to get a few transitions on one screen before enabling the the tracking to give it a chance to lock.

Really, we shouldn't be taking data this soon after power up anyway.  I'm just being impatient. 

[SJL-Instruments]

For your software, has anyone besides me asked about adding tracking? The only reason I brought it up was to run that test for the person who had asked about it in the square wave thread.  It may be a non-issue.  Maybe just leave it as-is.  If I need to, I will just wait for things to stabilize enough to get a few transitions on one screen before enabling the the tracking to give it a chance to lock.

Really, we shouldn't be taking data this soon after power up anyway.  I'm just being impatient. 

We haven't gotten any other requests for this feature. If you're fine with leaving it as-is, then we'll put 2.6.8 on hold for now.
Agreed that it's best to wait for the signal to stabilize before making precise measurements. 

That said, if anyone following this thread needs this feature, let us know and we'll put it back in our queue.

[SJL-Instruments]

(Thanks @points2 for reminding us to post here )

The GigaWave 6400 (4-channel) is now available in the EU. All EU orders come with free shipping (FedEx Intl Priority), and all duties/VAT paid by us (DDP). The price shown on our website is VAT-inclusive, and will be the total cost to you.

[points2]

hi SJL-Instruments,
Nice that you managed to get the EU "approval" (although I admit I don't know what it means... except that from now on you can ship here).

idea : changing the title of this thread, to show clearly that GigaWave is a "SAMPLING SCOPE", BUT NOT "another scope" like the dozens of REAL-TIME scope on the market.

To the attention of newbies & former newbies (the others already knows the Gigawave is a device to own
1. if you don't know what's a sampling scope => ask your web search engine => you'll know everything (on top reading this thread from page.1)
2. you may need a Gigawave if, like me, your point of interest has moved over time to "high speed" signal and basically, you often use your scope close to its time-scale limit to look at "what you want"  .
3. a sampling scope simply UNLOCKS the limitations of a real-time scope vs BW & rise-time ! (vs price tag)
4. a sampling scope, by design, works with "repetitive signals", thus => any digital signal ! but "digital signal are everywhere"  and their accuracy (vs time) is key in any real-time process... and they are everywhere

[joeqsmith]

...
idea : changing the title of this thread, to show clearly that GigaWave is a "SAMPLING SCOPE", BUT NOT "another scope" like the dozens of REAL-TIME scope on the market.

I assume those who come to the EEVBLOG would see that 1 TS/sec and know that is a sampling scope.   

To the attention of newbies & former newbies (the others already knows the Gigawave is a device to own
1. if you don't know what's a sampling scope => ask your web search engine => you'll know everything (on top reading this thread from page.1)
2. you may need a Gigawave if, like me, your point of interest has moved over time to "high speed" signal and basically, you often use your scope close to its time-scale limit to look at "what you want"  .
3. a sampling scope simply UNLOCKS the limitations of a real-time scope vs BW & rise-time ! (vs price tag)
4. a sampling scope, by design, works with "repetitive signals", thus => any digital signal ! but "digital signal are everywhere"  and their accuracy (vs time) is key in any real-time process... and they are everywhere

I suggest you follow your own advice starting with 1) then review what you wrote and see if you would like to maybe make a few changes.