Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
kcbrown:
--- Quote from: Karel on May 14, 2017, 10:00:16 pm ---:FUNCtion:WREPlay:FEND != :FUNCtion:WRECord:FEND !!
--- End quote ---
Ah. Yes, you're right, those should be different. My apologies. So it appears the internals are confusing the two, which is a bug.
Sent from my iPhone using Tapatalk
technogeeky:
In case Rigol does ever visit: Rigol would, at this point, have nothing to lose and everything to gain by releasing/open sourcing the firmware.
* It would be easy for them to determine people who brick their scopes from firmware changes.
* Clearly there aren't companies even younger than Rigol trying to copy them.
* It would allow Rigol to do absolutely no product development and still increase their pressure on the competition. For example, if you compare the new Keysight scope which is a few hundred dollars more to the 1054z, it's a difficult decision perhaps. But if you compare the Keysight with the Rigol 1054z with open source and community improved firmware, then it's no contest. All of the features of the Keysight could easily be added to the 1054z.[/li][/list].
* Rigol could even re-use the improvements in future scopes; allow customers to adapt features they like from competitor's scopes (like Rhode and Schwartz's amazing serial decode UI) and re-integrate these features into their scopes while being liability free...
I don't really see the downside. The Rigol 1054z is already probably the best selling oscilloscope of all time. The software feature keying mechanism is already hacked.
Can anyone else here come up with business arguments that would make this move a clear win? Is there something I'm missing, where they will be throwing away something that Rigol considers critical?
Cheers,
-tg
Fungus:
--- Quote from: kcbrown on May 14, 2017, 11:32:47 pm ---
--- Quote from: Karel on May 14, 2017, 10:00:16 pm ---:FUNCtion:WREPlay:FEND != :FUNCtion:WRECord:FEND !!
--- End quote ---
Ah. Yes, you're right, those should be different. My apologies. So it appears the internals are confusing the two, which is a bug.
--- End quote ---
Oh, duh! Yes. :palm:
bitseeker:
I had to read through that a few times, as well, since the commands are very similar looking. Perhaps the bug arose from a similar confusion during coding of the functionality. Nice bug find, Karel.
Regarding Rigol doing something because it would seem to make sense to, I have one word for it: "pluses". :horse:
Seriously, though, it would be nice to be able to fix things ourselves. But, alas, we're the minority. Hence, I'd be skeptical of it happening, but very pleased if it did.
boggis the cat:
--- Quote from: technogeeky on May 15, 2017, 02:50:59 am ---In case Rigol does ever visit: Rigol would, at this point, have nothing to lose and everything to gain by releasing/open sourcing the firmware.
...
Can anyone else here come up with business arguments that would make this move a clear win? Is there something I'm missing, where they will be throwing away something that Rigol considers critical?
Cheers,
-tg
--- End quote ---
I am surprised that none of the low-cost manufacturers have considered this. After all, if your firmware is already being hacked, why not harness that work?
One argument against this would be that someone could grab that code-base and install it is their own hardware, precluding any significant software development. This could end up with the first-mover manufacturer having both their hardware design and software copied rapidly by competitors.
Although, if the DS/MSO1xxxZ series is now due for replacement (due to Siglent's recent release -- likely to be followed up by a four channel option at minimum), then it may well be worth the experiment. Hantek or someone lower down the quality chain might take your code, but then they're stuck on the now obsolete hardware platform so are still lagging you.
(Another argument may be that more could be squeezed from older products, thus disrupting the 'upgrade cycle'. I don't know how big a factor this is.)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version