Products > Test Equipment
Pocket-Sized 6 GHz 1 TS/s ET Scope
SJL-Instruments:
--- Quote from: joeqsmith on January 13, 2024, 10:47:02 pm ---Looking at your manual to see what is included, I see no mention of cables. Assuming you provide one, how long is it? What interface connector is provided to connect to the PC? My two PCs for example support USB3.0 type A connectors. If you don't supply adapters/cables, and if it is critical, what guidelines do you offer?
--- End quote ---
The accessory list is provided on the homepage - we'll add it to the manual as well (edit: done), thanks for catching that.
We currently provide a 3' USB-C to USB-C cable and a hex key (for opening/repairing the device).
We don't currently provide a USB-A adapter, but we'll do that in the future - thanks.
We have a sizable factor of safety built into the USB power draw, and we only need USB 2.0 FS comms (12 Mbaud, the "heavy lifting" occurs device-side). We have run the GigaWave over a USB extension cord without issues. It will be interesting to see whether the device runs into issues near your ignition system, but we think it has a good chance of working (fingers crossed).
--- Quote from: joeqsmith on January 13, 2024, 11:07:52 pm ---How about adding some basic measurements beyond what you have. P-P for example. Maybe have a look at what other scopes offer for basic measurements. I like how even my 80's LeCroy can at the touch of a button throw up a hand full of parameters. If you don't like those, they offer a pretty broad spectrum of measurements they can make.
I think John's comment out his 11GHz $1000 DSO
--- Quote ---I find it difficult to use, mainly because of the software.
--- End quote ---
is a case where the UI is VERY important and can brake a product. Limited features to achieve a simple interface is not IMO a good solution. I want something feature rich, just easy to drive. As you said, your software is easy to drive and doesn't require a users to read a novel to run it. But it also lacks a lot of basic functions.
--- End quote ---
Thanks for the pointers. We'll implement all the standard measurements (likely by next update).
For P-P specifically, the software already implements this measurement (choose the "Vertical" category when adding a measurement).
--- Quote from: joeqsmith on January 13, 2024, 11:07:52 pm ---Let me give you an example of what I consider a problem with your UI. Say I have some signal that I want to look at. I have some pre-trigger and want to find the falling edge. I can't just capture unlimited data so I need to change the delay (timebase position) manually to hunt for it. In order to do this, I have to type in the delay I want. There is no inc/dec key. No way to select how much to inc/dec by.... All manual and very painful. That, or I am not understanding how it works. I would expect all of the controls to have an easy way to adjust then outside of typing in the values. Your trigger level for example allows me to set it by dragging the pointer.
--- End quote ---
You can use the scroll wheel (or on touchscreen, pinch horizontally) to zoom out the timebase until you see the falling edge. (Drag the holdoff marker to the right if it doesn't appear within the trigger holdoff.) Then zoom in onto the falling edge, dragging horizontally to shift the timebase. This will center the falling edge nicely with a usable zoom level - no need to type anything.
Of all the controls currently exposed in the main view, only the timebase resolution (points/div) and the trigger direction (rising/falling) actually require you to go click on the setting itself. We'll rewrite the manual to be more clear about all this. We've laid out the controls more clearly in revision H3 of the manual.
Please let us know of any other "basic features" you think are missing - this feedback is extremely helpful.
joeqsmith:
Thanks, I now see that mouse wheel and selecting the screen and dragging will set the Base and Position. Same for dragging the offsets. This is actually quite usable. My monitors do not support touch but that is good to know if I were to use a tablet to run it. Also, very good to know about the USB 2. Sorting a good cable should not be a problem then.
I had completely missed the Vertical measurements. :palm:
How do I save a waveform to memory and recall it, overlay? How do I enable persistence?
***
If you could stream the sweeps to disk and publish the format, that may also be helpful.
Adding histograms would also be nice to have.
Allow user to change the measurements rather than having to delete them and create new.
Add markers to waveform showing where the measurements are made. For example show where the 20/80% points are.
SJL-Instruments:
--- Quote ---How do I save a waveform to memory and recall it, overlay? How do I enable persistence?
--- End quote ---
We don't have these options implemented yet - we'll queue them up for next update (or the one after).
Our immediate thought is to put the waveform save/recall/overlay in the File menu, and persistence as a checkbox in the advanced options for each channel.
Is there an existing UI for these that you particularly like? (This question also applies to your suggestions below.)
--- Quote ---If you could stream the sweeps to disk and publish the format, that may also be helpful.
Adding histograms would also be nice to have.
Allow user to change the measurements rather than having to delete them and create new.
Add markers to waveform showing where the measurements are made. For example show where the 20/80% points are.
--- End quote ---
Many thanks for these suggestions. We've added them to the todo list - ETA hopefully 2 weeks for all of these.
joeqsmith:
--- Quote from: SJL-Instruments on January 14, 2024, 12:53:15 am ---Many thanks for these suggestions. We've added them to the todo list - ETA hopefully 2 weeks for all of these.
--- End quote ---
Big thanks!
--- Quote from: SJL-Instruments on January 14, 2024, 12:53:15 am ---Is there an existing UI for these that you particularly like? (This question also applies to your suggestions below.)
--- End quote ---
Maybe you could make a poll on this site asking for this kind of input. Keep it generic and I am sure countless people will provide you with their opinions.
points2:
Hi SLJ,
more questions :D
1. the USB plug => is type-C
but you provide an adapter usb-C to USB-A
1.1. Does it mean that the USB link is USB.2 ?
1.2. Did you test the performance of the device with different "power supply" :
for instance
=> the USB link
vs
=> a tweaked USB link that enable to get power from an external PS, for instance a "nice" linear PS (less noisy than the power coming from a hub / PC...)
2. Trigger frequency : internal vs external.
I guess this question is valid to any sampling scope... (?)
Is it better to rely on (your advice) =>
2.1. the hardware to find out the trigger frequency & stick to it (timebase + PLL ; given that both have their own jitter)
2.2. OR, using an external clock signal (that match the frequency to trigger) ; for instance, a DIY clock based on a "good" tcxo ? (as I don't deal with >100 different frequencies, :D , it is cheap to buy a fixed-frequency oscillator from a vendor..., and quite easy to get a rather good stability)
thanks
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version