Unified Keygen script for SIGLENT

[TomKatt]

I just ran the script unedited as-is and plugged in the SN, Model and ID codes from my SDS804X HD scope.  I didn't do anything with the keygen variable.

The BW codes generated by the script match the codes I generated earlier and the 200 MHz code matches the code I used to upgrade my scope, which now identifies itself as a SDS824X HD.  So the BW options look correct to me.

I have no need for the other options as I already have LA and AWG gear, so I have not tried those codes.  But the ones generated by this script match the ones I generated earlier when I did my upgrade so I would assume they are also correct.  The only difference is the codes generated by this script have lower case alphas, while the ones generated by the script I originally used are all uppercase (but again, same code).  Not sure if that matters.  I will try enabling those options tomorrow morning just for kicks to see if the scope accepts them (I assume it will).

I agree with others here that if you're going to put together a unified script, it would be preferable to somehow have the user select their model and then only display codes for the BW and options appropriate for that model.  Displaying a full page of codes - most of which do not apply to the model requested - is likely to cause some confusion.  So basically there should be some table that lists the models capable of being upgraded and the BW and option codes applicable to that model if possible.

But it is nice to have ONE script for everything.

Thanks!

Edit - I also have an SDS1104X-E that I can test tomorrow.  It seems like both models use the same code scheme, so if it works for one it likely works for both. The only difference is they have different option code names.

[tautech]

I just ran the script unedited as-is and plugged in the SN, Model and ID codes from my SDS804X HD scope......

I have no need for the other options as I already have LA and AWG gear, ...........

Have you installed the new FW into SLA1016 to properly support SDS800X HD models ?
https://int.siglent.com/u_file/download/24_03_05/SLA_8.2.3_EN.zip

[TomKatt]

I just ran the script unedited as-is and plugged in the SN, Model and ID codes from my SDS804X HD scope......

I have no need for the other options as I already have LA and AWG gear, ...........

Have you installed the new FW into SLA1016 to properly support SDS800X HD models ?
https://int.siglent.com/u_file/download/24_03_05/SLA_8.2.3_EN.zip

Thank you for looking out for us users here 

I keep forgetting to clarify that I have dedicated equipment and not scope plug-in modules (DSlogic LA), so no FW needed.  I am aware the Siglent modules need FW updates to work with the new SDS800 HD scopes.

[TomKatt]

Confirmed that option codes install on my SDS1104X-E (entered lowercase as generated).  Unfortunately, my SDS800X is in use elsewhere so I cannot test it today - but the SDS800X HD uses the same keygen (3) so I am sure they will work as well.   The only thing that I'd need to confirm is what option name is used to enable the AWG on the SDS800X - 'AWG' or 'FG' as it seems I've seen references to both in different posts...  But I'm sure that one of those works.

I have grown to appreciate the touchscreen on the SDS800X - using the encoder on the SDS1104X-E to enter codes seems ancient now lol.

[tautech]

.

I have grown to appreciate the touchscreen on the SDS800X - using the encoder on the SDS1104X-E to enter codes seems ancient now lol.

Really, have you not discovered the convenience of webservers ?
And Copy/Paste ?
 

[TomKatt]

.

I have grown to appreciate the touchscreen on the SDS800X - using the encoder on the SDS1104X-E to enter codes seems ancient now lol.

Really, have you not discovered the convenience of webservers ?
And Copy/Paste ?
 

Point taken 

I occasionally use networking when I'm on the bench, but that takes real estate and my bench is already cramped.

But there are many time's I need to troubleshoot on the production floor and network is not available.  I guess I could set up the laptop, but that's just more stuff to carry around and set up.

Edit - speaking of networking, I hope Siglent eventually adds WiFi and datalogging to the SDS800X HD series...

[tautech]

.

I have grown to appreciate the touchscreen on the SDS800X - using the encoder on the SDS1104X-E to enter codes seems ancient now lol.

Really, have you not discovered the convenience of webservers ?
And Copy/Paste ?
 

Point taken 

I occasionally use networking when I'm on the bench, but that takes real estate and my bench is already cramped.

But there are many time's I need to troubleshoot on the production floor and network is not available.  I guess I could set up the laptop, but that's just more stuff to carry around and set up.

Oh I hear ya but commented WRT the subject of this thread. 

Edit - speaking of networking, I hope Siglent eventually adds WiFi and datalogging to the SDS800X HD series...

They well know some of our views about WiFi for 800X. I think it will be implemented in due course but the more that use their supply channels to give feedback the sooner it might be implemented.

In the meanwhile get yourself a TP-Link TL-WR802N and set it to Bridge mode for WiFi connectivity which for my use at the bench and twiddling with settings or even installing official options the instrument is 10m away and with X-E, HD or whatever else, I have full control and with the SCPI webserver page can get or install anything I need.

One I shipped out today was connected to WiFi using the above and the NZ NTP server IP set as I like to for everything we supply.

[OP-SEC]

It was tricky to get the script to produce the correct keys for the SDS1000X HD, but I did manage to get it working in the end.

First, I couldn't use the actual scope serial number. I had to use the output of MD5_SRLN? for both SN and ID in the script.
BTW the names for these variables are very confusing. It's very easy to mic up the MD5_SRLN? and the serial number that's actually written on the back of the instrument. Keygen = 3 is the correct option for this scope.

OK.  If you had to use the result of 'MD5_SRLN?' for both SN and ID, then the proper Keygen is actually '1' and you can skip SN alltogether.  SN is only used by Keygen = '3'.  Can you try switching Keygen = '1' just for grins and giggles verify? 

[OP-SEC]

Hi everyone.

Just adding a bit more here in attempt to (1) get things working for everyone and (2) get better defaults built into the script...

You can "force" the script to use different Keygen routines.  If the bandwidth codes the script generates for you work but, the codes for other options don't try switching to a different Keygen version.

The following will generate the same 'bwopt' codes but different 'otheropt' codes:
Keygen = '1'
Keygen = '3'

Keygen = '2' is a different animal alltogether.  If the bwopt codes work for you and the otheropt codes don't, I don't know what to tell you.

[KungFuJosh]

In the meanwhile get yourself a TP-Link TL-WR802N and set it to Bridge mode

The TP-Link AC750 is a better option, and nearly the same price. At least here anyway.