plus a video will be great.
start from here from what i observe.
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1612639/#msg1612639
Ian posted the most concise instructions for the bandwidth upgrade in that thread:
1. Update with the OS update with the known root password.
2. telnet to the scope, and log in as root.
3. Execute these commands:
mount -o remount,rw ubi2_0 /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv bandwidth.txt bandwidth.bak
4. Reboot
I don't think there has been a definitive consensus on unlocking the other options without option codes?
Ian posted the most concise instructions for the bandwidth upgrade in that thread:
1. Update with the OS update with the known root password.
a) Which you get.... where?
b) How do you install it?2. telnet to the scope, and log in as root.
a) Telnet port #?3. Execute these commands:
mount -o remount,rw ubi2_0 /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv bandwidth.txt bandwidth.bak
4. Reboot
Is that definitively all it takes? I've read a few places that there's some weird aliasing at high frequencies that isn't in the real 200Mhz version of the 'scope, that maybe something else needs tweaking.
To me it seems weird that you'd hide the bandwidth.txt file instead of modifying it (if I were a Siglent firmware writer I'd default to low bandwidth when the file is missing)I don't think there has been a definitive consensus on unlocking the other options without option codes?
You mean the "software" part of the AWG, MSO and WiFi options?
- You install the OS just like you'd install the one you got from SIGLENT -- just follow their instructions
- The telnet port is the default one telnet uses -- just telnet to the ip address of the scope.
- Yes, that is all it takes. Others have confirmed that the bandwidth is increased.
- It looks to me like the scope is deliberately designed to be hackable. It would be very easy for it to have been much harder. It is not. It is *very* easy.
3. Execute these commands:
mount -o remount,rw ubi2_0 /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv bandwidth.txt bandwidth.bak
4. Reboot
Even when this particular case do not need but with bit expensive way in history I have learned that after editing it is good practice to use sync command before shut down.
Even when this particular case do not need but with bit expensive way in history I have learned that after editing it is good practice to use sync command before shut down.
Linux knows how to do a sync before a soft reboot but the word "reboot" is ambiguous, yes. Some people might power-cycle it instead of typing "shutdown -r" at the command line.
(take note, ian.ameline).
- You install the OS just like you'd install the one you got from SIGLENT -- just follow their instructions
- The telnet port is the default one telnet uses -- just telnet to the ip address of the scope.
Nice attitude.
Other 'scopes have different ports, I just want the port used by Siglent to be written down clearly (which you've failed to achieve).
If some scope manufacturer do not follow RFC854 about Telnet protocol it is they own problem.
It is clearly stated in RFC854 page 15. L=23
If some scope manufacturer do not follow RFC854 about Telnet protocol it is they own problem.
It is clearly stated in RFC854 page 15. L=23
I don't think "RTFM!" should be used in a "step by step" guide - this is the FM.
- You install the OS just like you'd install the one you got from SIGLENT -- just follow their instructions
- The telnet port is the default one telnet uses -- just telnet to the ip address of the scope.
Nice attitude.
Other 'scopes have different ports, I just want the port used by Siglent to be written down clearly (which you've failed to achieve).- Yes, that is all it takes. Others have confirmed that the bandwidth is increased.
Nobody's doubting the bandwidth increases but some people claim to have noticed weird aliasing or that the capacitors are different.
Those problems might be just the probes. It's reasonably well known that cheap-ass probes start to go to hell around 250MHz and one of the differences between the two models is that you get much better probes with the 200MHz version.
It it is the probes then a new set of probes should probably be thrown into the upgrade mix, that puts the price of the "hacked" version up by $100.
Food for thought, yes?- It looks to me like the scope is deliberately designed to be hackable. It would be very easy for it to have been much harder. It is not. It is *very* easy.
How do you explain the fact that the 'scope is only eight months old but you already need to download old firmwares to be able to do it, that newer firmwares don't work? What happens if Siglent decides to encrypt that file and make it default to 50Mhz when it's missing? It is *very* easy to make it much harder.
(and what happens when Siglent removes that old firmware from their web site?)
PS: Nowhere near as easy as a Rigol (neener neener).
Even when this particular case do not need but with bit expensive way in history I have learned that after editing it is good practice to use sync command before shut down.
Linux knows how to do a sync before a soft reboot but the word "reboot" is ambiguous, yes. Some people might power-cycle it instead of typing "shutdown -r" at the command line.
(take note, ian.ameline).
http://lmgtfy.com/?q=default+telnet+port
If you're too lazy to use google, I really don't know how to respond. You may have chosen the wrong hobby if you expect someone else to do all the work for you.
There -- now my attitude is clear.
Next question: When people say "the one with the known root password", what would that password be?
(I think we have to assume that not everybody will "know" it)
Next question: When people say "the one with the known root password", what would that password be?
(I think we have to assume that not everybody will "know" it)
As regards the concern that you are restricted to using the outdated firmware to perform the bandwidth upgrade, it is possible to modify any firmware revision yourself and insert your own custom password. You can follow the posts by janekivi & tv84 in the Siglent .ads file thread where the process is described in detail.
sync
mount -o sync,rw,remount /usr/bin/siglent/firmdata0/
sync
mv /usr/bin/siglent/firmdata0/bandwidth.txt /usr/bin/siglent/firmdata0/bandwidth.bak
sync
mount -o sync,ro,remount /usr/bin/siglent/firmdata0/
sync