General > General Technical Chat
Rigol DS1052E to DS1102E Hack Poll
saturation:
This thread collates all failures of the firmware modification on Rigol 1052E scopes by its users.
Please post problems you've had with the mod, what you've done to fix it or if it has remained unfixed.
migsantiago:
My DS1052E has its original firmware, no mods at all. ;D
ThunderSqueak:
As of right now, I have not modded my DS1052E... I decided to try using the scope factory stock for now and can always do the mod later if I need too :)
saturation:
I'm surprised, even if the poll has a long way to go, there are a good many reporting they have not done the mod. You get the impression from all the other eevblog posts that most folks are doing the mod.
I am so far as with these posts. The risk of getting a dead scope that could not be user fixable far outweighs the benefit of having a 100MHz bandwidth I don't need right now.
What I think we need to work on is how to fix scopes that bricked on the mod, and get it back working. That would make the mod less risky since there is a clear way to set it back to factory specs.
--- Quote from: ThunderSqueak on June 30, 2010, 02:35:26 am ---As of right now, I have not modded my DS1052E... I decided to try using the scope factory stock for now and can always do the mod later if I need too :)
--- End quote ---
--- Quote from: shafri on June 30, 2010, 03:58:50 am ---dont do the mod for no reason, unless u ar dealing with 100MHz system or more that you want it to show up in your DSO so badly. if you do, be ready to face the probable consequences.
--- End quote ---
Polossatik:
--- Quote from: shafri on June 30, 2010, 01:04:42 pm ---i've modded mine, something screwed up
--- End quote ---
your's is the only one that I know that failed and that was basically due typing to much stuff in hyperterminal ,
about 200 people downloaded already the files form the usb mod post, so that makes easely 100 mods who went ok...
so i think the mod itself is quite safe, especially when using USB
The only other report I know of is actually a firmware update failure
Navigation
[0] Message Index
[#] Next page
Go to full version