Products > Test Equipment
Pocket-Sized 6 GHz 1 TS/s ET Scope
joeqsmith:
Tooltips is nice. Consider providing a means to disable it and include that setting when saving the setup. Bug wise, of course if you run that script I provided, and run your software without a power cycle, you still can't detect the scope is present. I'm guessing you are aware of this and it will require a firmware change to solve it.
It it much faster compared with when I first looked at it. The whole user experience is much improved. You've come a long way.
I imagine if you turn the crank again (new products) it will get easier based on what you have learned.
SJL-Instruments:
--- Quote from: joeqsmith on April 06, 2024, 04:03:52 pm ---Tooltips is nice. Consider providing a means to disable it and include that setting when saving the setup.
--- End quote ---
Thanks - we will include this in the next update.
--- Quote from: joeqsmith on April 06, 2024, 04:03:52 pm ---Bug wise, of course if you run that script I provided, and run your software without a power cycle, you still can't detect the scope is present. I'm guessing you are aware of this and it will require a firmware change to solve it.
--- End quote ---
Yes, this will be fixed in the v15 firmware update. Currently we're estimating this to be released in mid-May. The planned changes for v15 are also listed in the software changelog on our website.
--- Quote from: joeqsmith on April 06, 2024, 04:03:52 pm ---I imagine if you turn the crank again (new products) it will get easier based on what you have learned.
--- End quote ---
Yep, the current user experience for the GigaWave sets the minimum bar for what we want to release in the future. :)
joeqsmith:
- Implement SCPI standard. [Backwards-compatible with existing protocol.]
Are you planning to remove the older protocol once the new one has been adopted? Will new products use the new protocol only? Something different?
The real advantage IMO to implementing SCPI is to use the current product as test case. I doubt many people will write custom software for it and those that do will have already locked down their interface. Down side is it adds complexity and increases the risk of there being problems.
- Store jitter calibration in firmware, perform automatic jitter correction in software.
I though the current firmware stored the calibrations and that is why you have a unique release for each individual scope. I can't imagine having to support something like this in production.
SJL-Instruments:
New products will use SCPI only. As you said, the main benefits of SCPI for the GigaWave are (1) ease of use for new users, and (2) to be sure we have a bug-free implementation for future products. Whatever we implement, backwards compatibility is the #1 consideration and we will keep the current interface available.
Perhaps the current interface is already easy enough to get started with. We are the worst possible judge of whether this is true for new users, given how long we’ve spent thinking about the protocol. You did mention inconsistencies with the return terminators being a possible sticking point. SCPI would define all the low-level considerations like this in a standard way.
***
The current firmware does store the calibrations. There is no additional complexity needed to also store the jitter calibration. It’s not currently stored because it’s not necessary for the current functionality of the scope. From our perspective, this is a small change and straightforward to implement.
joeqsmith:
--- Quote from: SJL-Instruments on April 08, 2024, 01:47:12 pm ---Perhaps the current interface is already easy enough to get started with. We are the worst possible judge of whether this is true for new users, given how long we’ve spent thinking about the protocol. You did mention inconsistencies with the return terminators being a possible sticking point. SCPI would define all the low-level considerations like this in a standard way.
--- End quote ---
It will be interesting to see how you solve problems like stacking commands. I had asked about it early on, then you took the stance of requiring a single command and waiting for an ack.
--- Quote ---Concatenating commands
Multiple commands can be issued to an instrument in a single string. They are made of simple commands separated by a semicolon character (;). For example, the command to "Measure a DC voltage then measure an AC current" would be issued as MEASure:VOLTage:DC?;:MEASure:CURRent:AC?.
--- End quote ---
Doing a quick search for the standard, came up with this one which is very old.
https://www.ivifoundation.org/downloads/SCPI/scpi-99.pdf
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version