I acquired a used Rigol which has the i2c decoder disabled. I tried to contact them for a quote on a license for the decoders but Rigol North America would not respond.
I’m looking forward to software that makes it a decent tool that it should have been!
The Rigol license situation is strange because the company clearly doesn’t take it seriously. The communities on the internet find ways to “unlock” the features with easy hacks and keygens because their protection is so minimal. Then they don’t patch or change anything, so even new releases are easily hacked.
If they cared, they would have spent some effort to try to close some of the loopholes. I think they’re treating the options like an upsell opportunity at time of original sale, but then they turn a blind eye toward the “unlocking” that happens in the aftermarket.
The strategy has worked for them so far because they’ve become very popular due to their reputation as being unlockable.
I once had a problem with one of their scopes. I emailed them, and they sent me back the admin password that works on every one of their devices. In the admin menu, I could enable any paid feature.
Market segmentation for hobbyists who are price sensitive and very influential, so they think of Rigol as extremely high performance for low price, which it is, if you have a keygen, although this is a smaller market it is influential.
The other market segment is "price is no object" educational institutions who think nothing of a purchase order of 25 scopes for each station in a EE lab. So charge them an extra $100 or whatever to not filter out high frequencies or to display an extra digit on the voltmeter on a power supply. Its free money, the .edu labs will gladly pay for it so may as well charge them... (edited to add for the non-EE people, the competitor of Rigol isn't Rigol-$100 or Rigol+$100, its places like Agilent who charge 10x, 20x as much for the same performance. So $100 here, $100 there, its a rounding error, its not like you're buying Agilent gear for 15x the price.)
I am doing my “research” before buying an oscilloscope and I think Tektronix entered the game in this price segment - December 18 is premiere of their 1 Series. I had their TAS 455 but the custom system for Rigol can win with my sentiment.
If someone from Tektronix is reading this, my unsolicited advice is: don't have bugs. Bugs on oscilloscopes waste a lot of time. My own Rigol scope wouldn't trigger on the external trigger until I factory reset it. The Rigol scope at work crashes (and shows an Android "... has stopped" screen) when you press the "wrong" button in the main menu.
Don't enter a reboot loop if the USB power supply can't provide enough power. Etc.
they take it seriously when you reach out for support / calibration / anything enterprise
their strategy worked on me; my personal scope was an unlocked rigol that became more powerful than anything else in its price class, i got comfortable with it and carried it around sometimes
They clearly do this on purpose, which is great for us individuals. But also the prices of those licenses are stupid too, but I suppose institutions would fork out
Hey - derail, and maybe not helpful to you but ... Have you considered a Logic Analyzer I stead for this? $10 for the Chinese ones, can use the Selae software (same chip), and I found it more convenient than using the Rigol. I use the Rigol for analog, but never found it convenient for digital.
A logic analyzer is a better fit. I hadn't purchased a Salea (love them, use them at work) because of the cost, a bit out of my hobby budget which is why I was trying to lean on the equipment I already have. I know Salea prefers that their software only be used with their hardware; how do you prevent their software from detecting a fake and locking you out?
This will reflect my own anecdotal experience only: Pulseview crashes frequently (multiple times per session), and requires setting up the view each time you re open it, e.g. post-crash. I don't remember if it was a straight up crash, or just stopping receiving data from the probe until I restarted it. It has been a few years since I tried, but I recall it as an unpleasant experience, and was frustrated with myself for putting up with it as long as I did prior to switching to Logic.
The parts aren’t super cheap. The FPGA and all the precision and temp stable components add up. But for the most part, you are paying for their engineering.
This is a really impressive piece of work, a scope isn't just a generic SBC with an ADC attached, it's a huge amount of fully custom analog and digital circuitry that you need to work with, combined with extensive signal processing software requirements, UI code, and so on. Julian (with some AI help) has essentially replicated what an entire dev team at Rigol did over quite a long period of time, it's actually worth getting a Rigol over other similar brands just for this.
At least from the eevblog post, it seems like the only re-implemented part is the "host" side, so Linux. A scope also has an FPGA, which is where the signal processing, sample memory, and acquisition happens. This one is much harder to reverse engineer, because it's effectively impossible to decompile the bitstream back to code (verilog), it's not possible to debug it in any meaningful way, so you're really starting from scratch in the dark.
And it's extra hard, because you need to know what's connected to which pin on the FPGA, which is impossible to do without desoldering it or destroying the board.
Well, the github repository makes it look like much more was accomplished: Linux on the host was actually already done by someone else, he (and his AI agent) apparently reverse-engineered the custom application of Rigol which controls the FPGA (I suppose he left the FPGA configuration file alone) and is able to perform measurements.
If he can get a black-box spec for what the FPGA's supposed to do, he can write a cleanroom implementation (or perhaps even add features), or rebuild the whole thing, including what the FPGA actually does and how.
I don't know what FPGA is in these (edit: it's Xilinx), but the usual problem is that toolchains tend to be highly proprietary.
You can’t get a black box spec for the FPGA’s duties from reverse engineering the main CPU software because it is a high speed interface between the ADCs, RAM, and the system. You could get the details of the commands and data interface, but actually reimplementing the FPGA would be a separate reverse engineering task which is nontrivial.
> scope isn't just a generic SBC with an ADC attached, it's a huge amount of fully custom analog and digital circuitry that you need to work with,
Oscilloscopes are an interesting target for projects like this because a lot of the difficult low level work is cleanly separated from the UI. It’s in the FPGA bitstream or signal processing code that might be completely separate from the UI.
The UI app isn’t exactly trivial because handling large volumes of data at high speed on limited hardware never is, but it doesn’t require reimplementing the entire firmware stack of the scope.
That’s what makes me optimistic about these projects. There is a lot of room to fix the UI and make it expandable by the community.
Lots of EEVBlog members embraced the Agentic coding phenomena. They have written so much software tools for their test instrument that actually have a use for their hobby.
The reverse engineering capabilities of the new models really help in reviving and creating software for old instrument that have no documentation at all. It's like they all discovered a new hobby of software thinkering to use on their electronic hobby.
The same phenomenon in going on with synthesizers firmware. People going crazy modding previously closed hardware, adding missing features and breaking down artificial segmentation.
I am getting really tired of seeing people shitting on other people’s hard work for no reason other than it was written by AI.
Software has always been sloppy. There are plenty of UI written by humans that look like shit, even after spending more money than likely was burned here.
If you think this effort is so bad, then show us how you could do better without AI. Otherwise, your kind of snark is not contributing constructively here (or anywhere).
well, this goes into the area, where bugs can make your workshop go up in flames (or your devices doing nothing). Kind of weird to use vibecoding for that, but ok...
I'm getting tired of people shitting on other people's work just because someone else did everything for them!
> Software has always been sloppy
Whatever your opinion on AI is, can we at least agree if you can tell from one look it's slop, you must have been holding it wrong?
People make mistakes, and they learn from them. This is at best training a rented SaaS, while the operator is paying for the privilege.
> show us how you could do better without AI
Believe me or not, I also have some projects in electronics, and I do disclose my AI usage, or often lack thereof. I don't happen to own a Rigol scope, and honestly don't have the skills or interest to reverse engineer my own scope.
I could probably contribute a better UI, but let's be honest, is the author interested in that contribution? Probably not.
Will anyone in good faith argue you can't levy any criticism, unless you first make a competing product? This is not even forbidding customers from criticizing a restaurant, this is you also excluding fellow chefs, just because they won't cook the same meal for you on the spot.
Gods I hope this works because Rigol has the worst UX in the industry. I have multiple pieces of test equipment I got for $100 on aliexpress and all of them have better thought out and usable UIs than the $15k Rigol equipment at work.
It's been thirty fucking years and Rigol still can't figure out how to program a goddamn knob without giving it so much acceleration that it skips 400 steps every time you touch it.
Rigol's software makes me so angry that I've convinced everyone at work to ban purchasing Rigol and instead buy from literally anyone else. I'd rather use a damn vacuum tube oscilloscope than a modern Rigol turd.
really? i am considering switching to Rigol from siglent because my damn siglent scope can not zoom out of captured signal. Apparently i was using it wrong. But the Keysight scope in my lab allows that.
I acquired a used Rigol which has the i2c decoder disabled. I tried to contact them for a quote on a license for the decoders but Rigol North America would not respond.
I’m looking forward to software that makes it a decent tool that it should have been!
The Rigol license situation is strange because the company clearly doesn’t take it seriously. The communities on the internet find ways to “unlock” the features with easy hacks and keygens because their protection is so minimal. Then they don’t patch or change anything, so even new releases are easily hacked.
If they cared, they would have spent some effort to try to close some of the loopholes. I think they’re treating the options like an upsell opportunity at time of original sale, but then they turn a blind eye toward the “unlocking” that happens in the aftermarket.
The strategy has worked for them so far because they’ve become very popular due to their reputation as being unlockable.
I once had a problem with one of their scopes. I emailed them, and they sent me back the admin password that works on every one of their devices. In the admin menu, I could enable any paid feature.
Market segmentation for hobbyists who are price sensitive and very influential, so they think of Rigol as extremely high performance for low price, which it is, if you have a keygen, although this is a smaller market it is influential.
The other market segment is "price is no object" educational institutions who think nothing of a purchase order of 25 scopes for each station in a EE lab. So charge them an extra $100 or whatever to not filter out high frequencies or to display an extra digit on the voltmeter on a power supply. Its free money, the .edu labs will gladly pay for it so may as well charge them... (edited to add for the non-EE people, the competitor of Rigol isn't Rigol-$100 or Rigol+$100, its places like Agilent who charge 10x, 20x as much for the same performance. So $100 here, $100 there, its a rounding error, its not like you're buying Agilent gear for 15x the price.)
I am doing my “research” before buying an oscilloscope and I think Tektronix entered the game in this price segment - December 18 is premiere of their 1 Series. I had their TAS 455 but the custom system for Rigol can win with my sentiment.
TIL! That's great to hear.
If someone from Tektronix is reading this, my unsolicited advice is: don't have bugs. Bugs on oscilloscopes waste a lot of time. My own Rigol scope wouldn't trigger on the external trigger until I factory reset it. The Rigol scope at work crashes (and shows an Android "... has stopped" screen) when you press the "wrong" button in the main menu.
Don't enter a reboot loop if the USB power supply can't provide enough power. Etc.
> the company clearly doesn’t take it seriously.
they take it seriously when you reach out for support / calibration / anything enterprise
their strategy worked on me; my personal scope was an unlocked rigol that became more powerful than anything else in its price class, i got comfortable with it and carried it around sometimes
They clearly do this on purpose, which is great for us individuals. But also the prices of those licenses are stupid too, but I suppose institutions would fork out
Hey - derail, and maybe not helpful to you but ... Have you considered a Logic Analyzer I stead for this? $10 for the Chinese ones, can use the Selae software (same chip), and I found it more convenient than using the Rigol. I use the Rigol for analog, but never found it convenient for digital.
A logic analyzer is a better fit. I hadn't purchased a Salea (love them, use them at work) because of the cost, a bit out of my hobby budget which is why I was trying to lean on the equipment I already have. I know Salea prefers that their software only be used with their hardware; how do you prevent their software from detecting a fake and locking you out?
This is the open source alternative:
https://sigrok.org/wiki/PulseView
This will reflect my own anecdotal experience only: Pulseview crashes frequently (multiple times per session), and requires setting up the view each time you re open it, e.g. post-crash. I don't remember if it was a straight up crash, or just stopping receiving data from the probe until I restarted it. It has been a few years since I tried, but I recall it as an unpleasant experience, and was frustrated with myself for putting up with it as long as I did prior to switching to Logic.
> how do you prevent their software from detecting a fake and locking you out?
Good question - this is a risk; could happen, and can't prevent it. Hasn't happened yet anecdotally.
Why are these so expensive, by the way?
It's a low volume product sold mainly to companies/professionals that's managed to bill itself as premium. It's amazing it isn't more expensive.
A lot of effort went into "just work" software.
The parts aren’t super cheap. The FPGA and all the precision and temp stable components add up. But for the most part, you are paying for their engineering.
It doesn’t become free once you cover costs.
I agree though, the margin does seem high.
Probably depends on the model of the scope, but I found it fairly easy to find a feature key generator to unlock scope features on mine. cough riglol.
This is a really impressive piece of work, a scope isn't just a generic SBC with an ADC attached, it's a huge amount of fully custom analog and digital circuitry that you need to work with, combined with extensive signal processing software requirements, UI code, and so on. Julian (with some AI help) has essentially replicated what an entire dev team at Rigol did over quite a long period of time, it's actually worth getting a Rigol over other similar brands just for this.
Ob-direct link to the repo: https://github.com/deckerjulian/oos
At least from the eevblog post, it seems like the only re-implemented part is the "host" side, so Linux. A scope also has an FPGA, which is where the signal processing, sample memory, and acquisition happens. This one is much harder to reverse engineer, because it's effectively impossible to decompile the bitstream back to code (verilog), it's not possible to debug it in any meaningful way, so you're really starting from scratch in the dark. And it's extra hard, because you need to know what's connected to which pin on the FPGA, which is impossible to do without desoldering it or destroying the board.
Well, the github repository makes it look like much more was accomplished: Linux on the host was actually already done by someone else, he (and his AI agent) apparently reverse-engineered the custom application of Rigol which controls the FPGA (I suppose he left the FPGA configuration file alone) and is able to perform measurements.
and the code looks very similar to all the wideband sdrs we have mostly forgotten now...
Although a 0-dependency approach from-scratch approach is likely sensible here.
If he can get a black-box spec for what the FPGA's supposed to do, he can write a cleanroom implementation (or perhaps even add features), or rebuild the whole thing, including what the FPGA actually does and how.
I don't know what FPGA is in these (edit: it's Xilinx), but the usual problem is that toolchains tend to be highly proprietary.
You can’t get a black box spec for the FPGA’s duties from reverse engineering the main CPU software because it is a high speed interface between the ADCs, RAM, and the system. You could get the details of the commands and data interface, but actually reimplementing the FPGA would be a separate reverse engineering task which is nontrivial.
> scope isn't just a generic SBC with an ADC attached, it's a huge amount of fully custom analog and digital circuitry that you need to work with,
Oscilloscopes are an interesting target for projects like this because a lot of the difficult low level work is cleanly separated from the UI. It’s in the FPGA bitstream or signal processing code that might be completely separate from the UI.
The UI app isn’t exactly trivial because handling large volumes of data at high speed on limited hardware never is, but it doesn’t require reimplementing the entire firmware stack of the scope.
That’s what makes me optimistic about these projects. There is a lot of room to fix the UI and make it expandable by the community.
I wish if there was a way to increase memory depth. I don't know, even by hacking an nvme drive onto it so it could save all the data quickly.
"a lot of AI help" I assume...
Lots of EEVBlog members embraced the Agentic coding phenomena. They have written so much software tools for their test instrument that actually have a use for their hobby.
The reverse engineering capabilities of the new models really help in reviving and creating software for old instrument that have no documentation at all. It's like they all discovered a new hobby of software thinkering to use on their electronic hobby.
The same phenomenon in going on with synthesizers firmware. People going crazy modding previously closed hardware, adding missing features and breaking down artificial segmentation.
What difference does it make?
That the author can't maintain the project without shovelling more money into the money furnace. Or that the UI looks like slop.
Are you really sure about your facts?
I am getting really tired of seeing people shitting on other people’s hard work for no reason other than it was written by AI.
Software has always been sloppy. There are plenty of UI written by humans that look like shit, even after spending more money than likely was burned here.
If you think this effort is so bad, then show us how you could do better without AI. Otherwise, your kind of snark is not contributing constructively here (or anywhere).
well, this goes into the area, where bugs can make your workshop go up in flames (or your devices doing nothing). Kind of weird to use vibecoding for that, but ok...
Or incorrect measurements leading the user to spend weeks chasing ghosts...
"You're absolutely right, my code assumed every waveform is sinusoidal! But in my defense, I left a FIXME comment about that."
(Not about this project, just a general pattern with Claude)
> people’s hard work
> written by AI
I'm getting tired of people shitting on other people's work just because someone else did everything for them!
> Software has always been sloppy
Whatever your opinion on AI is, can we at least agree if you can tell from one look it's slop, you must have been holding it wrong?
People make mistakes, and they learn from them. This is at best training a rented SaaS, while the operator is paying for the privilege.
> show us how you could do better without AI
Believe me or not, I also have some projects in electronics, and I do disclose my AI usage, or often lack thereof. I don't happen to own a Rigol scope, and honestly don't have the skills or interest to reverse engineer my own scope.
I could probably contribute a better UI, but let's be honest, is the author interested in that contribution? Probably not.
Will anyone in good faith argue you can't levy any criticism, unless you first make a competing product? This is not even forbidding customers from criticizing a restaurant, this is you also excluding fellow chefs, just because they won't cook the same meal for you on the spot.
also that this might relatively fast lead to interesting physical effects if claude makes an error...
Gods I hope this works because Rigol has the worst UX in the industry. I have multiple pieces of test equipment I got for $100 on aliexpress and all of them have better thought out and usable UIs than the $15k Rigol equipment at work.
It's been thirty fucking years and Rigol still can't figure out how to program a goddamn knob without giving it so much acceleration that it skips 400 steps every time you touch it.
Rigol's software makes me so angry that I've convinced everyone at work to ban purchasing Rigol and instead buy from literally anyone else. I'd rather use a damn vacuum tube oscilloscope than a modern Rigol turd.
really? i am considering switching to Rigol from siglent because my damn siglent scope can not zoom out of captured signal. Apparently i was using it wrong. But the Keysight scope in my lab allows that.
oh and when you press a knob it skips steps. It is almost impossible to press it without turning it a little.
this is what ai should be used to enable, opening up hardware