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

--- Quote from: CustomEngineerer on July 01, 2018, 09:42:47 pm ---
--- Quote from: SMB784 on July 01, 2018, 04:26:27 pm ---Its possible that they have invalidated this method of changing the root user login when you install the official software update first.

Any suggestions are most welcome.

--- End quote ---

No, the work being done by forum members has been on the latest firmware and os versions from what I can tell. Post one of your telnet sessions (including initiating the telnet connection) so we can see that you are connecting correctly. Also it might be useful to have a screenshot of the IP configuration screen on the scope. Are you able to connect to the webserver on the scope through your browser?

--- End quote ---

He sees the login prompt.
tautech:

--- Quote from: tv84 on July 01, 2018, 10:25:46 pm ---
--- Quote from: CustomEngineerer on July 01, 2018, 09:42:47 pm ---
--- Quote from: SMB784 on July 01, 2018, 04:26:27 pm ---Its possible that they have invalidated this method of changing the root user login when you install the official software update first.

Any suggestions are most welcome.

--- End quote ---

No, the work being done by forum members has been on the latest firmware and os versions from what I can tell. Post one of your telnet sessions (including initiating the telnet connection) so we can see that you are connecting correctly. Also it might be useful to have a screenshot of the IP configuration screen on the scope. Are you able to connect to the webserver on the scope through your browser?

--- End quote ---

He sees the login prompt.

--- End quote ---
Yes.
And to progress further you must have the modified OS installed and any command spelling and syntax correct.
CustomEngineerer:
I get that he thinks he is. But without knowing his comfort level with the command line I would prefer to see proof to be able to rule it out. If he swears that the firmware has been installed correctly, and he is for sure using the correct username and password, then the next thing to check is that he really is connecting to the scope. I agree that it does sound like he probably is, but I've seen telnet connections fool other users before (as in they were at the telnet prompt, but not actually connected to anything).

On a separate note, thanks for your contributions in getting this process worked out.

Edit: I don't mean the first line as an insult. smb784 specifically mentioned earlier that wasn't completely sure was using telnet correctly, and I really have seen telnet connections trick people before.
SMB784:

--- Quote from: CustomEngineerer on July 01, 2018, 10:39:44 pm ---I get that he thinks he is. But without knowing his comfort level with the command line I would prefer to see proof to be able to rule it out. If he swears that the firmware has been installed correctly, and he is for sure using the correct username and password, then the next thing to check is that he really is connecting to the scope. I agree that it does sound like he probably is, but I've seen telnet connections fool other users before (as in they were at the telnet prompt, but not actually connected to anything).

On a separate note, thanks for your contributions in getting this process worked out.

Edit: I don't mean the first line as an insult. smb784 specifically mentioned earlier that wasn't completely sure was using telnet correctly, and I really have seen telnet connections trick people before.

--- End quote ---

Don't worry I'm not insulted :)  Having spent almost 15 years in a physics lab in the quest for my Ph.D., I am used to making simple but easily overlooked mistakes.  Here is how I performed this update.

First, I formatted a USB to FAT32, and downloaded the 25R2 Firmware .ads onto the USB stick from Siglent America's official website, and installed it to the device.  You can verify that by looking at the top left corner of the first image attached in this email.

Then I reformatted the USB as FAT32 and downloaded the latest operating system and extracted the four files onto the USB.  I then plugged the USB into the scope and restarted it, allowing it to install the new operating system.  See the first attached image for verification of this process (top, middle, and bottom panels).

I turned on DHCP and connected the ethernet cable between it and my router, allowing it to acquire an IP address from my router.  See the second attached image for verification.

Then I removed the USB while the scope was on, turned the scope off, reformatted the USB to FAT32, and downloaded the custom software install from Janekivi's weblink from this thread.  I extracted this custom firmware zip onto the USB, and plugged it into the oscilloscope and turned it on.  The scope booted up, and after boot I telneted in on port 23 and tried to log in with login name root and the correctly spelled password.  See third attached image for verification of this process (top, bottom panels).

Take special note in the images of the date stamps for each of the files uploaded to the USB.  That is how I verified that I had the correct files on the USB

Thank you all again for all of your hard work and help, let me know if you see any errors in my process.
SMB784:
I have updated my installation method in the post immediately preceding this one.
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