Author Topic: Rigol 1052E Glitch/bug (Read 6338 times)

aluqard89 · « **on:** March 27, 2013, 10:33:11 am »

Hey guys!

Ive been a long follower of this nice community but never got the urge to post but now i feel that i need your support got a real problem with my rigol 1052E.

I have uploaded a video on it as it may describe the problem better Rigol 1052E Glitch/bug .

Please help

hammil · « **Reply #1 on:** March 27, 2013, 12:02:08 pm »

If this happened a few months on, I doubt it was the hack that caused it. I think you've just got some loose connections or bad silicon... Try reflashing the firmware and see if that fixes anything. Otherwise, see if you can send it back under warranty (make sure to 'undo' the hack first, just to be safe).

saturation · « **Reply #2 on:** March 27, 2013, 12:14:09 pm »

The simplest thing is turn it back to a 1052e, run 'Factory' setup then do self calibration. If all is fine, then something in your hack caused the problem. If its not fine, then the scope is in a position to be returned to the factory, assuming they don't find out it was tampered with.

MikeK · « **Reply #3 on:** March 27, 2013, 04:50:31 pm »

Why does it immediately go into Run mode, and with the Measure functions on, after the unit is first powered up?

M0BSW · « **Reply #4 on:** March 27, 2013, 05:00:16 pm »

Please reply when and if you set it back to factory setting ,I'm most interested.

c4757p · « **Reply #5 on:** March 27, 2013, 05:09:04 pm »

God, it seems like every second Rigol scope has some funny intermittent glitch. I get that it could have happened during the conversion, but really, the only mechanisms that could cause funny malfunctions due to the conversion could do the same thing due to a proper firmware upgrade as well.

I second the suggestion to revert back to factory and check. About to do the same with mine, actually. Mine has yet another glitch that nobody seems to have heard of before me.

aluqard89 · « **Reply #6 on:** March 27, 2013, 05:35:19 pm »

I tried the factory setup in Storage/factory/load and i got the same resullts : /. One funny thing is the scope seem to be working fine in the software Ultrascope over usb :S.
so firmware is fine then? hmmm could it be a connection problem with the panel?

Thanks for the replys really appriciate it =)

c4757p · « **Reply #7 on:** March 27, 2013, 05:37:18 pm »

Did you actually reverse the conversion? I think that option just wipes the configuration, not the firmware image.

aluqard89 · « **Reply #8 on:** March 27, 2013, 05:43:34 pm »

no i did not reverse dont know really how to make the reverse happen

aluqard89 · « **Reply #9 on:** March 27, 2013, 06:11:33 pm »

took a picure of the system info

Uploaded with ImageShack.us

AlphZeta · « **Reply #10 on:** March 27, 2013, 06:46:54 pm »

Could it be issue with the rotary encoder? Assuming that it used to work, I don't know why it would stop working all of a sudden?

I checked the settings on mine hacked 1052E, it seems that yours is newer, but curiously enough the FPGA version is 2.00 which is lower then mine (2.05). By the way, my hardware version is 57.

aluqard89 · « **Reply #11 on:** March 27, 2013, 07:50:16 pm »

Strange indeed, i have reverted back to 50mhz 1052e still the same problem

. Calibrated a couple of times no luck there either ....

I quess the only best thing to do is to use the warrenty , before opening the case up

The thing is that some of the buttons is acting like random too
The rotery encoder seem to be working as it responds but not with the correct action

Sent from my Nexus 7 using Tapatalk HD

AlphZeta · « **Reply #12 on:** March 27, 2013, 08:16:33 pm »

Quote from: aluqard89 on March 27, 2013, 07:52:05 pm

My hardware version is blank what is causing blanking?

Sent from my Nexus 7 using Tapatalk HD

Even after you switched the version back? I don't know what's causing it blank but I'd check with Rigol first before doing anything else with it (sounds like it's still under warranty).

aluqard89 · « **Reply #13 on:** March 27, 2013, 08:37:46 pm »

Yes even after . yes will contact the local store i bought it from

Sent from my Nexus 7 using Tapatalk HD

saturation · « **Reply #14 on:** March 28, 2013, 12:00:12 pm »

Sorry to read, but in the end, that's why its important to buy locally, just in case you have to return it for warranty. When you get the new one, I would do a burn in; leave it on for 1 week on screen saver mode to blank the screen, this insures whatever glitch happens, happens early. If it survives, few devices malfunction if they work well after a 24/7 burn in. You need not connect the inputs to anything. You are looking for a manufacturing defect, not a design defect.

Quote from: aluqard89 on March 27, 2013, 08:37:46 pm

Yes even after . yes will contact the local store i bought it from

Sent from my Nexus 7 using Tapatalk HD

drieg · « **Reply #15 on:** March 29, 2013, 06:30:57 pm »

Quote from: aluqard89 on March 27, 2013, 06:11:33 pm

took a picure of the system info

Uploaded with ImageShack.us

According to s/n your unit is HW version 58. This version is not supported by FW 00.02.02.02.00. Second problem I see is, that units with s/n starting DS1ED142 have factory calibration data stored in another location than units made before. Plese upgrade your unit to 00.03.01.00.00 (do not use 00.04.00.00.01 yet as this version has another bug - commands for trigger delay adaptation doesn't work correctly - we might need them later). Post SysInfo printscreen again and let us know if problems persist.

aluqard89 · « **Reply #16 on:** March 29, 2013, 11:02:17 pm »

ok i have updated it to 03.01, calibrated and factory load but problem still exist. Funny thing is that its working perfectly in Ultrascope

new pic of sysinfo

drieg · « **Reply #17 on:** March 30, 2013, 07:32:15 am »

Maybe hw issue with front panel board or it's connection.

Can you tell me how exactly did you do the 1102 hack (step-by-step, via serial or USB cable?, etc..) and how long have you been running FW 2.02? So far I haven't seen hw damage due running unsupported hw on lower versin, but never did any long-term testing.

snipersquad100 · « **Reply #18 on:** March 30, 2013, 04:22:10 pm »

Does this hack still work with new version's of the software?

hammil · « **Reply #19 on:** March 31, 2013, 10:11:01 pm »

It requires a downgrade-hack-upgrade procedure, but yes, it is possible.

drieg · « **Reply #20 on:** April 02, 2013, 10:39:46 am »

I really cannot recommend this method as it wipes out some calibration data.

As for aluqard89's problem - after checking/fixing calibration data the problem still exits. It looks like a hw issue...


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Rigol 1052E Glitch/bug (Read 6338 times)

Share me