Products > Test Equipment

Pocket-Sized 6 GHz 1 TS/s ET Scope

<< < (64/107) > >>

joeqsmith:

--- Quote from: SJL-Instruments on February 12, 2024, 11:41:39 pm ---
--- Quote from: joeqsmith on February 12, 2024, 09:16:22 pm ---2.5.9 prerelease, error when saving settings.   Not repeatable. 
***
Strike that.  It repeats.   

--- End quote ---
We're looking into this, and will send you an updated prerelease version when we find the root cause (hopefully today).
We can reproduce the error if the scope is disconnected prior to saving settings. Is this what happened in your case? (To be clear, we consider this a bug, and will fix it.)

--- End quote ---

It's possible but I am not certain.  I really like having this feature and appreciate you adding it.   


--- Quote from: SJL-Instruments on February 12, 2024, 11:41:39 pm ---
--- Quote from: joeqsmith on February 12, 2024, 09:16:22 pm ---Also,  I suspect there is something still different between your software and mine when it comes to the power user mode.   I can set your software to what I believe are the same settings as my software and will get different results.   Does your software for example no allow trigger values in the mV range?  Maybe the boundary settings are limited?   For what ever reason, with my software I am able to work with much smaller signals than with yours.  Something in your software appears to be limiting me.   Really strange.

--- End quote ---
There are two possible reasons:
1. On startup, the software performs the DC offset trim automatically (Section 3.7.2) if nothing is connected. This will shift all voltages on the ~mV scale. This isn't relevant if signals are connected on startup.
2. For backwards compatibility reasons, the trigger level command sent to the scope is 22 DAC units (~1 mV) higher than entered in the software.
Otherwise, there are no limits set in power-user mode. Any boundary limits are explicitly shown (the displayed value will be clamped).

--- End quote ---

This is where I would like to see an auto setup.  I am working with sub 10mV signals and can believe it is a DC offset problem and the trigger will need to change.  I adjusted it a fair amount trying to locate a level but may not have gone far enough.  I'll try again later.   Think about it, one button, auto set.  Just getting the vertical and trigger set would be very helpful compared with my trial an error technique.  The computer would be much faster. 


--- Quote from: SJL-Instruments on February 12, 2024, 11:41:39 pm ---
--- Quote from: joeqsmith on February 12, 2024, 03:03:59 pm ---Same flicker problem.  I obviously can't explain why you are not able to replicate it or why you felt the need to release it when it was clear there was a major problem with the prerelease.   IMO, your goal should be to release high quality software.  Seeing a problem like this flicker in the wild just isn't something that should ever happen.

--- End quote ---
Going forward, we will cut back our release schedule to once per two weeks. This will give us more time for QA, and still gives a reasonable turnaround time for user requests. In hindsight, weekly releases were on the edge of what we could handle.

--- End quote ---
I want to be clear about this.  Feel free to send me prereleases while I continue to evaluate the product.  I don't mind testing them along with running my other tests.  I think giving yourself more time to test your software is a big step in the right direction.   

joeqsmith:
If I do disconnect the scope from the PC, how do I get your software to reconnect to it without having to exit and restart? 

SJL-Instruments:

--- Quote from: joeqsmith on February 13, 2024, 02:00:01 am ---If I do disconnect the scope from the PC, how do I get your software to reconnect to it without having to exit and restart? 

--- End quote ---
Currently the software does not support this. We will add this to the next version.


--- Quote from: joeqsmith on February 13, 2024, 12:54:59 am ---This is where I would like to see an auto setup.  I am working with sub 10mV signals and can believe it is a DC offset problem and the trigger will need to change.  I adjusted it a fair amount trying to locate a level but may not have gone far enough.  I'll try again later.   Think about it, one button, auto set.  Just getting the vertical and trigger set would be very helpful compared with my trial an error technique.  The computer would be much faster. 

--- End quote ---
This is being worked on - we aren't happy enough with the reliability yet, but with any luck it should be ready for next release.


--- Quote from: joeqsmith on February 13, 2024, 12:54:59 am ---
--- Quote from: SJL-Instruments on February 12, 2024, 11:41:39 pm ---We're looking into this, and will send you an updated prerelease version when we find the root cause (hopefully today).
We can reproduce the error if the scope is disconnected prior to saving settings. Is this what happened in your case? (To be clear, we consider this a bug, and will fix it.)

--- End quote ---

It's possible but I am not certain.  I really like having this feature and appreciate you adding it.   

--- End quote ---
We've found the root cause of this issue, and will send you a patched version tomorrow to test.

joeqsmith:
For the power-user, consider making the End the total collection time rather than the end time.  If I want 1.6ns of data, I have add it to the Start in my head.  Then if I change the start, I have to manually calculate and enter a new end.   Maybe others would not run it that way but that would be my preference.  If you allow both a start/stop times and start/duration, and cover both would be great.   

DC offset was the problem.  Adjusting the trigger to a different level corrected it. 

Not finding any other major problems with the software.

***
When you start the program, it starts out with the menu that allows selection of the simulation.  You have to select the scope, then select OK.  I have been trained so well by Microsoft,  could you allow the double click selection so I don't have to move the mouse a second time and select another button?   

When you start the program, it flashes a few boxes on the screen before it loads.  This is something new.  Could you clean this up?

While I really like the new vertical scale with the drop down + custom, after selecting custom the only way to get back to drop down mode is to right click, select Select All,  right mouse click, select Delete, click outside the box or select the spin icon.   That's a lot going on for what should be a one click operation. 

FFT could use some cursor measurements.  Peak readouts... 

I was watching some of Picotech's reviews of their 9400.  I can't say I am a fan of their UI but they do have some good ideas that make it easier to drive their scopes. 

***
FFT settings are not included in the Save Settings. 

***
Closing the FFT window and reopening it will cause it to reset to some defaults rather than using the last settings causing me to have to reset it up every time.   





SJL-Instruments:

--- Quote from: joeqsmith on February 13, 2024, 03:31:13 am ---For the power-user, consider making the End the total collection time rather than the end time.  If I want 1.6ns of data, I have add it to the Start in my head.  Then if I change the start, I have to manually calculate and enter a new end.   Maybe others would not run it that way but that would be my preference.  If you allow both a start/stop times and start/duration, and cover both would be great.

--- End quote ---
Got it - we will make this change in the next version.


--- Quote from: joeqsmith on February 13, 2024, 03:31:13 am ---Not finding any other major problems with the software.

--- End quote ---
We have sent you an updated prerelease of v2.5.9. If the last issue is resolved, we will release this publicly as a bugfix update.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod