Products > Test Equipment

Pocket-Sized 6 GHz 1 TS/s ET Scope

<< < (63/107) > >>

SJL-Instruments:
Thanks for the additional information and screen capture. We've just sent you a prerelease of v2.5.9, which we think fixes the root cause of the flickering.

joeqsmith:

--- Quote from: SJL-Instruments on February 12, 2024, 02:10:54 am ---The flickering issue is hardware-dependent, and we were only able to reproduce it on one machine.

--- End quote ---

I also ran it on a newer PC with the following:

NVIDIA RTX A4500, CUDA cores 7168, Compute Compatibility 8.6
Intel(R) Core(TM) i9-10980XE CPU, 3.00GHz   
64.0 GB
Windows 10 Pro, 22H2, 19045.3930

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.   

Running the prerelease 2.5.9 on the above hardware does not appear to exhibit the flicker.   I will test it tonight on the old PC and get back with you. 

joeqsmith:
I have tried the 2.5.9 prerelease on my old PC and it no longer exhibits the flicker.    :-+

The updated case arrived today as well. 

joeqsmith:
2.5.9 prerelease, error when saving settings.   Not repeatable. 

***
Strike that.  It repeats.   

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.

SJL-Instruments:

--- 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.)


--- 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).


--- 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.

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