Siglent SDS1104X-E Hack to 200Mhz， and full options ?

[n3mmr]

Hi Plurn... I'd like to here of your 6.1.33 workaround to the shellcmd issue.....
...

details supplied via personal message.

Can I also partake of your way to achieve password free telnet access in release 33?

[plurn]

Can I also partake of your way to achieve password free telnet access in release 33?

details supplied via personal message.

For anyone else that wants this, I suggest request it here like n3mmr has done and anyone who has been given the details can send the details to the person requesting via personal message. Then put a note in this thread saying it has been supplied.

Just in case I am not around to provide the info.

That is just a suggestion - you can do as you please of course.

[sundance]

@plurn | n3mmr:
Mind to send me a PM?

[timgiles]

@anyone who who has the PM or wrote the original - can you pm timgiles :-) thank you in advance

[MikeLud]

Can someone PM Plurn workaround

Thanks In Advanced
Mike

[tv84]

Run the update (one time only) and do:

http://<scope_IP>/web_img/startTelnet9999.php

The rest is self-explanatory.

Made by plurn.

[starlight_tools]

Plurn, I would appreciate a copy of your work around as well please.

[tek2232]

Plurn can you send me a copy ?

Thanks

[plurn]

@ sundance timgiles MikeLud starlight_tools tek2232

details will be supplied via personal message in the next few minutes.

[toodle]

Hi,
Can I also get a pm of your way to achieve password free telnet access in release 33?
Thanks in advance

[MikeLud]

toodle PM sent

[Higginse]

Likewise I would appreciate a copy of the workaround info if you wouldn't mind.
Thanks in advance.

[melwin]

Any chance I could learn the magic incantation as well? Would be much appreciated! Thanks.

[bluejedi]

@plurn I too would appreciate a copy of the workaround info.
Thanks in advance.

[tv84]

Check my previous (edited) post.

[jousis]

One more question, will the hack mess the SAG1021 license ?


edit. it took me a while, sorry

[KungFuJosh]

The .33 firmware is annoying! There's so many extra steps to do basic things like setting probe attenuation. Before this stupid firmware, turning the dial would easily adjust. Now you have to select it, go to the next screen, select it again, and then turn the knob. 

[tinhead]

The .33 firmware is annoying! There's so many extra steps to do basic things like setting probe attenuation. Before this stupid firmware, turning the dial would easily adjust. Now you have to select it, go to the next screen, select it again, and then turn the knob. 

this is due to fact that the same firmware (executable) seems to compiled for different models, so one can find inside as well SDS5000X, SDS2000X-E, SDS1000X-E and SDS2000X+(10bit, what?), where some of these models support active probe and their information/calibration - that's why the menu has been changed

EDIT: actually deep look inside the .33 firmware shows as well other interesting things, like MIL-1553 or Flex options, not only new 10bit DSO SDS2000XPlus, hmm

[tv84]

EDIT: actually deep look inside the .33 firmware shows as well other interesting things, like MIL-1553 or Flex options, not only new 10bit DSO SDS2000XPlus, hmm

Because they are using the same source code as in the SDS5000X... Nothing more.

[tautech]

EDIT: actually deep look inside the .33 firmware shows as well other interesting things, like MIL-1553 or Flex options, not only new 10bit DSO SDS2000XPlus, hmm

Oh, juicy. 
Actually I need MIL-1553 as an option for one of my customers classroom sets of SDS1202X-E for cadet training use.....nice to know it's part of later FW but I did suspect it was. 

All we need now is to work on enabling it. 

[Rerouter]

Its fully baked in there. Its just the access chain for the menus are missing if you try using the specific commands you will soft lock the scope application.

They also hard coded the menu tree unlike previous versions. (I wonder why  ;. ) its not yet obvious to me where the menu / UI thread is. As I know where the menu entry points are. They are just dereferenced.

Personally I would love the option to buy the canfd decoder

[tinhead]

EDIT: actually deep look inside the .33 firmware shows as well other interesting things, like MIL-1553 or Flex options, not only new 10bit DSO SDS2000XPlus, hmm

Because they are using the same source code as in the SDS5000X... Nothing more.

that's right, but on the other hand what the firmware is doing depends on model name, i tried already SDS2000X-E binary on SDS1000X-E and was of course nothing special, it worked exactly as the SDS1000X-E firmware did. So vice versa it could be possible to lie about hardware version to get 2000 series features running on 1000 series.

Personally I would love the option to buy the canfd decoder

the firmware does read and evaluate at least options_canfd_cfg.bin files, once i placed it (copy of my unused wifi_cfg.bin), it immediately created options_canfd_times.txt, even if this is not available feature on 1000X-E, so the hope remains (however, there are some changes to licensing check, some extra _md5_ here and there ...)

[tv84]

that's right, but on the other hand what the firmware is doing depends on model name, i tried already SDS2000X-E binary on SDS1000X-E and was of course nothing special, it worked exactly as the SDS1000X-E firmware did. So vice versa it could be possible to lie about hardware version to get 2000 series features running on 1000 series.

But the 1000 and 2000 are equal in terms of Options licenses, so no much gain there.

The big question is: did you see anywhere the use of a 5000 option in a 1000/2000 menu?

Because running the 5000 FW in the 1000 should be another ballgame...

PS: is it possible to trigger, for example,  CANFD analysis/decoding via SCPI?

[bluejedi]

I tried several memory dumps made via web interface/SCPI but I am unable to find my scope id in the dump. I can only find a sequence of at most 2 scope id bytes matching in memory but not more. I'm running v7.1.6.1.26 + root telnet access patch (the one that requires root pwd).

I also tried to make a dump via telnet with: cat /dev/mem > /usr/bin/siglent/usr/mass_storage/U-disk0/memdump10.bin but this consistently fails with the following error: cat: read error: Bad address

Are there any other possibilities to extract the keys from the scope?

[bluejedi]

Run the update (one time only) and do:

http://<scope_IP>/web_img/startTelnet9999.php

Install the attached .ads before or after the 6.1.33 update?