Products > Test Equipment
Pocket-Sized 6 GHz 1 TS/s ET Scope
<< < (65/107) > >>
joeqsmith:
It corrects the save settings problem I saw. 

When you create multiple prereleases, you may want to consider having a unique version number in the header.   As I share screen shots, I don't want you asking me what version of software I was running.  It is up to you to track your code.  Internally, I don't care, but anything that leaves your office should have a unique identifier, IMO.

About the lockup.  I was running some longer sweeps and I think what may be happening is I do something that tells the software to do something besides sweeping.  The scope continues to dump data and the software can't abort it.  This is a total guess on my part.  It had looked like it hung as I have seen.  Nothing displayed in the graph as before.  This time I just let it sit for a long while and sure enough, it recovered.   It is very possible I was running high resolution wide time ranges when I have seen it hang before. 
SJL-Instruments:

--- Quote from: joeqsmith on February 13, 2024, 02:48:23 pm ---It corrects the save settings problem I saw.

--- End quote ---
Thanks for confirming. We've released this version as v2.5.9 (primarily to resolve the flicker problem).


--- Quote from: joeqsmith on February 13, 2024, 02:48:23 pm ---When you create multiple prereleases, you may want to consider having a unique version number in the header.   As I share screen shots, I don't want you asking me what version of software I was running.  It is up to you to track your code.  Internally, I don't care, but anything that leaves your office should have a unique identifier, IMO.

--- End quote ---
We will do this going forward - thanks.


--- Quote from: joeqsmith on February 13, 2024, 02:48:23 pm ---About the lockup.  I was running some longer sweeps and I think what may be happening is I do something that tells the software to do something besides sweeping.

--- End quote ---
To clarify, this means the hangup happened as you were changing some settings? Do you remember which ones?
This narrows it down quite a bit - likely a inter-process communication issue. Hopefully we can resolve this by next release.


--- Quote from: joeqsmith on February 13, 2024, 03:31:13 am ---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.   

--- End quote ---
We will work on these bugfixes/features for the next release. As we get through this list, we'll send you occasional prereleases for feedback.
joeqsmith:

--- Quote from: SJL-Instruments on February 13, 2024, 03:04:24 pm ---
--- Quote from: joeqsmith on February 13, 2024, 02:48:23 pm ---About the lockup.  I was running some longer sweeps and I think what may be happening is I do something that tells the software to do something besides sweeping.

--- End quote ---
To clarify, this means the hangup happened as you were changing some settings? Do you remember which ones?
This narrows it down quite a bit - likely a inter-process communication issue. Hopefully we can resolve this by next release.

--- End quote ---

Sadly I do not but I can believe that my sweep times were in the order of several minutes.   When I was playing around writing my own code for it, I never flush Windows buffers.  It was easy to get my software in a mode where the scope had I expect, already dumped it's data but my software would be looking for other responses.   This is what made me wonder if you don't have a similar condition.   I think I have seen it happen three times.  Rare.
joeqsmith:
While attempting to make some very long, high resolution sweeps, I managed to get the scope to lockup to the point where exiting the software and reloading, it does not find the unit.     My guess is a power cycle is going to recover it.   I think I have had it hang in such a way that required a power cycle twice now.   
joeqsmith:
Power cycle did shake it loose.  If an automotive companies firmware required you to pull the battery terminal every now and then, would you find that acceptable?  What about an aircraft?     

I started to write some simple test scripts to stress test your product and it seems easy enough to reproduce the lockups.  I could provide you with a sequence of commands that will cause it to hang.  I suspect you could just go through your firmware and clean that up.    I've also now seen where the scope will spam the data bus, sending  "FAIL 752440 0"  non stop for example.   The manual makes no mention of it.   Maybe it means something to you. 

Not having your firmware source I can't really guide you.  I guess we can rug sweep it like the double cal and hope no one runs into it.     

Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod