I wish my Rigol had a battery option! With the power analysis function it would be THE machine for solar power systems diagnostics!
just reflash the v00.01.03.00.01 build from end of April, and try again.
Probably you got a scope with a v00.01.03.00.01 build from mid may, hence the different checksum.
Has anybody take them up on their offer? It does say it in quite verbatim:QuoteThe open source software is provided for free. RIGOL uses third-party open source
software subject to the specified licenses. You are entitled to use the open source
software subject to their respective license. If you or any third party wants to obtain
the complete corresponding source code for the software from us, please contact:
RIGOL (SUZHOU) TECHNOLOGIES
E-mail: service@rigol.com
Website: www.rigol.com
This offer is valid for three years after you received the software.
I did ask them for the software, so lets see what happens next (but would be nice to know if others already did this too)
Has anybody take them up on their offer? It does say it in quite verbatim:QuoteThe open source software is provided for free. RIGOL uses third-party open source
software subject to the specified licenses. You are entitled to use the open source
software subject to their respective license. If you or any third party wants to obtain
the complete corresponding source code for the software from us, please contact:
RIGOL (SUZHOU) TECHNOLOGIES
E-mail: service@rigol.com
Website: www.rigol.com
This offer is valid for three years after you received the software.
I did ask them for the software, so lets see what happens next (but would be nice to know if others already did this too)
So I never received a reply. So yesterday, I've sent a request to the European office, and got a reply promptly. They asked where I've sent the previous request too, and that they would prepare the files I requested (I requested all sources for all products :p)
They said they'd send them to me on november 17th. No idea why it is taking so long, maybe that's the day they'll open their github.com/rigol repo?
Anyway, fingers crossed!
Has anybody take them up on their offer? It does say it in quite verbatim:QuoteThe open source software is provided for free. RIGOL uses third-party open source
software subject to the specified licenses. You are entitled to use the open source
software subject to their respective license. If you or any third party wants to obtain
the complete corresponding source code for the software from us, please contact:
RIGOL (SUZHOU) TECHNOLOGIES
E-mail: service@rigol.com
Website: www.rigol.com
This offer is valid for three years after you received the software.
I did ask them for the software, so lets see what happens next (but would be nice to know if others already did this too)
So I never received a reply. So yesterday, I've sent a request to the European office, and got a reply promptly. They asked where I've sent the previous request too, and that they would prepare the files I requested (I requested all sources for all products :p)
They said they'd send them to me on november 17th. No idea why it is taking so long, maybe that's the day they'll open their github.com/rigol repo?
Anyway, fingers crossed!
What a turn! You "blew up the bomb" and you will now be feared in Rigol.
But, they can provide the code executed by the processor that runs in the OS. And this is just the user interface, if I'm not mistaken. The main work is done in the FPGA and they are not required to publicate this code.
Probably the Rigol guys are reading this thread. Guys, come out, don't be afraid of open source - third-party firmware that will inevitably appear will make your product even more popular. I think people will love your product if you become open. This path was followed by PC-giving the opportunity to independently assemble computers and expand them, thereby sharply breaking away from the closed Apple, which is held in the market of show-offs.
If this thread is not read by Rigol specialists, oliv3r, please pass these thoughts on to them.
Course the 4 FPGA's are interesting too; but lets treat those as 'hardware' for now
once we know the interfaces between the hardware, FPGA and the software, we could even start to re-write the FPGA software :p
But for now, lets first see Rigol uphold the GPL
I don't know much about licensing. If I'm not mistaken, using Linux with a GPL license requires publishing the source code of running programs?
They said they'd send them to me on november 17th. No idea why it is taking so long, maybe that's the day they'll open their github.com/rigol repo?
Anyway, fingers crossed!
unfortunately the root:root login is not working, I only get an acces denied message:
login as: root
root@10.0.0.18's password:
Access denied
admin:rigol won't work either.
Has anyone more infos for this scope?
I have a portable inverter with a fairly large battery. It's not the same as having an internal battery. Portable inverter, mine included, are notorious for having very poor A/C waveforms. They're supposed to be "modified sine-waves" but they look much more like a square-wave when examined. I hate to subject my equipment to such poor quality mains power. I have a much older OWON 100MHz, 2-channel scope with battery option. I'll likely continue to use that instrument in the field for my solar installation consulting. /Users/stevenjaynes/Pictures/Inverter Waveforms/IMG_4918.jpg
just reflash the v00.01.03.00.01 build from end of April, and try again.
Probably you got a scope with a v00.01.03.00.01 build from mid may, hence the different checksum.
Thanks for posting this info!
I just got a MSO5074 with that same mid-May version of the v00.01.03.00.01 firmware (listed onscreen as Build: 2020-05-18 11:42:06)
The patch checksums didn't work.
After I rolled back to the April version of the v00.01.03.00.01 firmware (listed on-screen as Build: 2020-03-30 15:56:36), the patching worked!
Thank you to all who contributed to this effort! It is impressive and apprecitated!
Hi All! Just joined so I could post, after spending... well, multiple hours reading the history of this amazing journey.
[..]
I also just got a MSO5072 with the mid-May firmware, same number and build timestamp listed above.
I went ahead and used the well-worn ssh enabler, ssh in, use the command line to copy the appEntry file onto a USB stick at /media/sda1 and took it to another computer to do the MD5.
If you have any kind of unix computer (linux or Mac) simply type
$ md5 /Volumes/USB_DRIVE/appEntry
or whatever the appropriate path is for you. md5 should be present by default in most unix-like systems.
MD5 (appEntry) = 783a31ebdc0d4acb7b9dc244155ba1c6
From everything I'm seeing here, it seems like this piece of info should be enough to get the patcher to work? Am I misunderstanding?
I'm not sure if it's too subtle or if I read it and not figured that was it.
"Easy way".
Or, I noticed that some of their posts have apparently been deleted, was this license generator posted and then deleted?
Hey. I just bought one too. I would like to make backup from current firmware and all the data(as i would make image in windows world) before i try this "hack". How can i make backup and later use that backup as a recovery as well? Im not very familiar with linux backup. Thanks in advance.