Products > Test Equipment
Pocket-Sized 6 GHz 1 TS/s ET Scope
joeqsmith:
If we use the LiteVNA for a source and track the measured risetime, we see about a 2.5ps error. Much tighter than the 12ps we were seeing. With the faster trigger rate, we can collect a lot more data at a reasonable time, greatly improving the measurement.
***
It's continued to run over the afternoon. The combined error is still under 3ps.
SJL-Instruments:
--- Quote from: joeqsmith on June 10, 2024, 03:26:40 am ---Still does not appear correct when loading the setup with CDF set manual vs auto. Odd is if I expected it to be in auto after loading the setup, I select the CDF sampling options and it changed to auto and starts sweeping very slowly. If I select apply (auto is still selected) it appears to change back to manual. Really odd.
--- End quote ---
This is fixed in version 2.6.7 (just released). We have added the time drift auto-tracking, liveplotting, and histogram features (alongside various bugfixes). Looking forward to seeing the results of the test.
joeqsmith:
Thanks! I will download and try it out over the weekend.
****
Very nice. Simple to use.
This is a different LiteVNA (other one is in use) but the values are very close to what I saw using my software with the other unit. I also tried out some of the problems I brought up. So far, these all appear corrected. I think the dialog box popping up when you reach the maximum reference waveforms is fine. Really, that's a lot of waveforms and I am not expecting this would be a typical case anyway. I have not yet tried the tracking.
https://www.eevblog.com/forum/testgear/show-us-your-square-wave/msg5542531/#msg5542531
I'm not liking that when the tracking is enabled, all other functions are disabled. The problem is when you zoom in and start the tracking, it may already have drifted too far. By the time you shut off tracking, close the menu, get things aligned again, then re-enable tracking, it may have already drifted too far. Then you get things finally tracking and want to rearrange all the windows or add something, you start the whole process over again.
It does track and I can at least make the measurement but it's a pain to use with my old Tektronix pulser having so much drift. One fix would be let everything warm up for a half hour or so until the drift is less per time unit. Then enable the tracking. Personally, I would drop this limitation. It's not like the PC is being stressed.
SJL-Instruments:
As Lasmux has just announced on his thread (linked below), our partnership with Lasmux Devices is now active.
https://www.eevblog.com/forum/testgear/12-ghz-active-probe-project/125/
After purchase of a 2.7 GHz active probe from Lasmux, you can receive a voucher for US$300 off any GigaWave scope. The probe itself costs less than this, so it's no-brainer if you were thinking about buying a GigaWave anyway.
If you already purchased a probe, the offer applies retroactively - just contact Lasmux for the voucher code. We recommend buying the SMA-SMA version of the probe for use with the scope.
In our opinion, the probe is extremely impressive for the price, and complements our scope well. We recommend watching joeqsmith's review of the probe (post #111 in the above linked thread) if you're interested.
SJL-Instruments:
--- Quote from: joeqsmith on June 14, 2024, 06:14:22 pm ---I'm not liking that when the tracking is enabled, all other functions are disabled. The problem is when you zoom in and start the tracking, it may already have drifted too far. By the time you shut off tracking, close the menu, get things aligned again, then re-enable tracking, it may have already drifted too far. Then you get things finally tracking and want to rearrange all the windows or add something, you start the whole process over again.
It does track and I can at least make the measurement but it's a pain to use with my old Tektronix pulser having so much drift. One fix would be let everything warm up for a half hour or so until the drift is less per time unit. Then enable the tracking. Personally, I would drop this limitation. It's not like the PC is being stressed.
--- End quote ---
Thanks for the feedback. We'll remove this restriction in the next update (ETA next week).
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).
***
Here's a prerelease that removes this restriction. Note that the timebase controls are disabled while tracking is active. The timebase can still be adjusted with the tracking window open (but not yet started).
https://gigawave-releases.s3.us-east-2.amazonaws.com/GigaWave_v2.6.8_PREVIEW20240615_Windows.zip
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version