Products > Test Equipment
Siglent .ads firmware file format
CustomEngineerer:
Just to be absolutely certain there wasn't an issue with newer scopes I went ahead and went through the procedure on my SDS1104X-E that I ordered on last Monday and received on Thursday from Saelig. When I received the scope it had
Software Version: 7.6.1.20R3
FPGA Version: 2018-01-20
Hardware Version: 01-03
That day I went ahead and installed the SDS1004X-E_6.1.25R2.ADS firmware (listing this way since I'm still a little confused about if the 7 at the beginning of the version should be part of the firmware number) and afterwords checking the system information screen then showed
Software Version: 7.0.6.1.25R2
FPGA Version: 2018-03-06
Hardware Version: 01-03
Yesterday I installed the official OS update from the Siglent, SDS1004X-E_OSV1_EN-1.zip file, and checking the system information screen after showed:
Software Version: 7.1.6.1.25R2
FPGA Version: 2018-03-06
Hardware Version: 01-03
I had planned on holding off on installing the modified system files until I knew for sure I was going to keep the scope, but since its easily reversible I figured Id go ahead and make sure it does indeed work as expected. I installed the four files from the SDS1004X-E_OSV1_EN_eevblog.zip file earlier in this thread and sure enough I was then able to telnet into the scope with the expected username and password.
In the attached screenshot (sorry for not separating the two attempts into separate screenshots), the first telnet login attempt was while the scope had the official Siglent OS files installed, then before I attempted the second login, I restarted the scope with an inserted USB thumb drive containing the modified OS files. You can see the second attempt is able to login.
CustomEngineerer:
Everything you are doing looks correct to me, sorry, I'm out of ideas.
SMB784:
--- Quote from: CustomEngineerer on July 02, 2018, 01:20:47 am ---Everything you are doing looks correct to me, sorry, I'm out of ideas.
--- End quote ---
I am thinking it has something to do with taking the software from the USB and putting it onto the scope. I will try doing that from a different computer than the one I am currently using.
SMB784:
Well, I have fixed the login issue.
Something about adding the custom files to the USB with my Desktop running Ubuntu 18.04 was causing them to not be recognized by the scope (I guess)
I tried adding the files to the USB using my raspberry pi, and lo and behold i am now able to telnet into the scope with both the raspberry pi and my desktop.
No idea what the deal was with that, but at least now I can log in.
Thank you all for your help, seriously.
CustomEngineerer:
Great news. Congrats!!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version