Products > Test Equipment
Siglent .ads firmware file format
<< < (42/85) > >>
SaKhan:

--- Quote from: BillB on September 19, 2018, 06:48:36 pm ---
--- Quote from: SaKhan on September 19, 2018, 04:18:28 pm ---I am curious whether the precision of a hacked SPD3303X-E is similar to SPD3303X.

--- End quote ---

I think it is.  Even before the hack, my X-E would accept remote 1mA changes and show them through EasyPower.  It would also accept remote 1mV changes from EasyPower even though it would truncate the response.  However, the 1mA and 1mV changes were happening at the output terminals of the X-E even though the display was not being updated.  From what I could tell, the X-E is really an X minus the display digit.  So, if you were using the X-E purely through SCPI, you'd almost already have an X (except for the truncated mV command response)

--- End quote ---

Thanks for the info. I am planning to buy one and was trying to "justify" the price difference.
kerouanton:

--- Quote from: tv84 on September 17, 2018, 09:35:22 pm ---The method is simple:

--- End quote ---

Confirmed working on mine. Thanks tv84, again!
BillB:
Here is a graph of the SPD3303X-E timer stepping through .100-.104mV in 1mV/5 second steps. 
vt100:

--- Quote from: tv84 on August 25, 2018, 09:25:34 pm ---
--- Code: ---        private static void search_licenses()
        {
            byte[] buffer = System.IO.File.ReadAllBytes(@"memdump.bin");

            for (int j = 0, l = 0; j < 2; j++, l += 0x20)
            for (int i = 0, strStart = 0, strSize = 0; i < buffer.Length; i++)
                if (((buffer[i] < '2') || (buffer[i] > '9')) && ((buffer[i] < 'A' + l) || (buffer[i] > 'Z' + l)) && buffer[i] != ('L' + l) && buffer[i] != ('O' + l))
                {
                    if (strSize == 16)
                        Console.WriteLine("{0:X8} - {1}", strStart, Encoding.UTF8.GetString(buffer, strStart, strSize));
                    strSize = 0;
                    strStart = i + 1;
                }
                else strSize++;
        }
--- End code ---

--- End quote ---

A more comprehensive version of the key locator, based on tv84's code snippet above, has been posted to:

https://github.com/Siglent/FindKeys.git

This .NET Core 2.1 program will find keys when they span memory segment boundaries by extracting leftover segments of strings and concatenating them with other segments found elsewhere in the memory dump.

Based upon testing on 2 scopes, all 7 keys (50mhz, 70mhz, 100mhz, 200mhz, AWG, MSO and WIFI) were located 100% of the time in 1 pass.

Note this code only works for SDS1xxxX-E scopes currently, additional scopes will be added as they become available.

--
vt100
the world's best dumb terminal
kerouanton:
Nice. But I'm wondering how Siglent will react considering you created a "Siglent" account on Github to host this code!
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