Products > Test Equipment

Pocket-Sized 6 GHz 1 TS/s ET Scope

<< < (66/107) > >>

SJL-Instruments:

--- Quote from: joeqsmith on February 15, 2024, 01:10:58 am ---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. 

--- End quote ---
Could you provide the command sequence? We will try to reproduce the hang.

Are you able to reliably reproduce the "fail" message? What was happening just before it occurred?

joeqsmith:

--- Quote from: SJL-Instruments on February 15, 2024, 01:26:11 am ---
--- Quote from: joeqsmith on February 15, 2024, 01:10:58 am ---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. 

--- End quote ---
Could you provide the command sequence? We will try to reproduce the hang.

Are you able to reliably reproduce the "fail" message? What was happening just before it occurred?

--- End quote ---

The firmware will need improvements before I could hunt down your problem with the spam messages.    Send the following two commands.  Scope will respond with "CH1 BAD: 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0".   Close the test software and try to connect with your software.

5332 DA62 2D43 A11C 1456 0D
74F5 71ED 8586 AEF6 3B79 0D

SJL-Instruments:

--- Quote from: joeqsmith on February 15, 2024, 02:47:15 am ---The firmware will need improvements before I could hunt down your problem with the spam messages.    Send the following two commands.  Scope will respond with "CH1 BAD: 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0".   Close the test software and try to connect with your software.

5332 DA62 2D43 A11C 1456 0D
74F5 71ED 8586 AEF6 3B79 0D

--- End quote ---
The first command is interpreted as "S2", since the third byte (0xDA) is non-printable and the rest of the command is ignored.
This will cause subsequent commands to fail, as a minimum of 3 triggers per sample (S3) is required. The default value is 4096.
We will document this in the next manual revision.

joeqsmith:
Try this script, should get the same response.  Scope should not reconnect after sending them.   Both scripts fail 100% of the time. 
6A22 912D 41A5 DCC3 8EA6 0D
7832 9A43 72E4 011D 2F2A 0D
2491 424C 10D3 D3E3 A99C 0D
7467 A795 2B74 ADB8 15F1 0D

IMO, the firmware should NEVER require a hard reset like this.   Normally, I would subject it to random packets, varying lengths, different terminators, patterns, speeds, attempt overflows....  Just your basic 101 stuff.  That's all am doing now.   That's how I made it spam the bus.  The CH1 BAD:  fault is the most prevalent.  I suspect the firmware is just not well written to make sure it handles packet faults.  You may be better off just going over it than trying to hunt down why a a specific set of commands takes it out. 

joeqsmith:

--- Quote from: SJL-Instruments on February 15, 2024, 02:58:04 am ---The first command is interpreted as "S2", since the third byte (0xDA) is non-printable and the rest of the command is ignored.
This will cause subsequent commands to fail, as a minimum of 3 triggers per sample (S3) is required. The default value is 4096.
We will document this in the next manual revision.

--- End quote ---

I think you are missing the point.  I don't think pointing out that your firmware is not robust and to treat it like a princess or it will require a power cycle is time well spent.  Far better to harden the firmware so it handles all unforeseen conditions gracefully.  Again just MO. 

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