| Products > Test Equipment |
| Pocket-Sized 6 GHz 1 TS/s ET Scope |
| << < (53/107) > >> |
| SJL-Instruments:
--- Quote from: joeqsmith on February 06, 2024, 12:35:54 am ---Interesting. The idea of using the previously set value to determine how to interpret the entry isn't user intuitive IMO. I can't believe someone would want it work this way. I'm sure as sales grow, you will receive lots of opinions and I wouldn't be surprised if some of those are not how things typically work. If I get 20 people to suggest you should scan right to left with the earliest time always on the right side, will you do it? Just remember it's your product. --- End quote --- We're currently rethinking this. Really, the complaints were from situations where a unit with no prefix doesn't make sense. (For example, setting the timebase position to "50" can only mean 50 ns, not 50 s.) On the other hand, the vertical offset is debatable - requesting "200" probably means "200 mV", but if a high-voltage probe is used, it could mean "200 V". Perhaps the best thing to do is implement things as you suggested, requiring an explicit prefix (so "200" would always mean "200 V"). The only exception would be for things like the timebase, where a 50s position is outside the capability of the hardware. This would make things as consistent as possible, and the software would only "correct" the user entry if it's completely unambiguous. |
| joeqsmith:
I've received comments about people trying to use my VNA software where they enter for example 140m for frequency and can't understand that isn't 140MHz. Failure of our education system isn't something I can address with my software. I assume the user knows what they want. I fully understand our friends reasoning in the attached clip. 10MHz, voltage set just above where the scope will trigger. Lots of back and forth to center the waveform at 10mV/div. Now set it to 5mV/div. Now change it back to 10mV/div. What is the cause of it going unstable? It's channel 2, so nothing to do with the trigger. Easy to repeat. |
| nctnico:
--- Quote from: SJL-Instruments on February 05, 2024, 07:49:13 pm --- --- Quote from: joeqsmith on February 05, 2024, 06:59:18 pm ---Really? Personally, I'm not a fan of software that tries to outguess me. If it units are volts and I enter 50, it should give me 50, not m,u,n... It should always do the same thing. But that's just MO. --- End quote --- We had it implemented as you stated, and changed it after receiving complaints that e.g. typing 50 into the offset box would set it to 50V instead of 50mV. --- End quote --- I agree with Joe here. Don't try to guess at typing errors. All test equipment I have uses values as they are typed in. If they are outside the range, you'll get an error. Otherwise the punched in value is used. |
| SJL-Instruments:
Thanks nct and joe for the pointers. We'll change all input methods to the standard behavior in the next release (this weekend). --- Quote from: joeqsmith on February 06, 2024, 01:22:02 am ---10MHz, voltage set just above where the scope will trigger. Lots of back and forth to center the waveform at 10mV/div. Now set it to 5mV/div. Now change it back to 10mV/div. What is the cause of it going unstable? It's channel 2, so nothing to do with the trigger. Easy to repeat. --- End quote --- We've tried to replicate this setup, but can't reproduce the behavior you're seeing (attached). It would be helpful to capture the raw CDF data when this occurs. Just to be clear, you're putting a 10 MHz sine wave into CH1 & CH2? Or all channels? As to why the vertical division has any effect at all: the displayed vertical region changes the CDF search bounds. This in principle shouldn't affect anything (just gives higher resolution), but gives a starting point if you want to investigate it over serial. |
| joeqsmith:
If there truly is a problem with customers entering out of range values, you may want to consider coercing the entry to the boundary conditions. The low cost VNAs keep evolving and I don't want to waste time changing the limits when a new model is released, so I don't coerce the settings. I had a person trying to set their VNA outside of it's upper frequency limit. Somehow they seemed to feel the software could magically turn a 4GHz VNA into a 10GHz VNA. For something I give away for free, I refuse to work to the least common denominator. You may not have a choice but to add some checks. *** Looking at the PicoTech software, they appear to set boundary conditions. |
| Navigation |
| Message Index |
| Next page |
| Previous page |