This is a discussion re the bad Accel, Gyro and Baro values that we're seeing with ArduCopter-3.1. The increase in the SPI bus speed from 500khz to 8Mhz has exposed a hardware problem on some boards. That hardware problem is that the 3.3V regulator has been blown so all sensors are running at 5V instead of the intended 3.3V.
How have these regulators been burnt out?
- Attaching a radio receiver or MinimOSD to the APM while the APM is only powered through the USB (see video below)
- Some clone boards seem to come from the factory with blown regulators. 3DR boards might also come with blown regulators although they do a specific check of the regulator as part of the regular QA process.
- It is not (as far as we know) actually caused by the AC3.1 software itself, it just exposes the problem. You could prove this to yourself by checking the 3.3V regulator (see video above) before and after the upgrade.
How can we fix the regulator?
Option #1: If it's a new board (so that it's less likely you burned it out yourself) you could report the problem to the retailer that sold you the board and ask for an replacement. If it's 3DR it's called an "RMA".
Option #2: if you're handy with a soldering iron you can replace the regulator yourself. On the APM2.5.2 (and higher) boards it's not that difficult. On the APM2.5 it's far more difficult.
For APM2.5.2 : TPS79133DBVR
For APM 2.5: MIC5219-3.3YML TR
How can I stop it from happening again?
Do not connect any devices such as a radio receiver, MinimOSD, GPS, etc while the APM is powered especially while powered only through the USB cable.
Attaching a 100uF capacitor across any of the APM's radio input's 5V and GND pins will stop the regulator from being blown by plugging in a receiver. video here!
There are very few reports of regulators being blown twice and no reports of it ever failing in flight.
Below are some graphs of the types of values that we are seeing on these boards.
Replies
iskess,
Updated! look ok?
Hi All
After much delay.... we have some news :)
First the problem.... we all know that. 5v on the 3.3v rail. but how?
there were a list of suspected causes of the failure of the 3.3v reg.
1 plugging in a UBEC backwards on the RX rail. no issue, as the center pin is 5v, couldn do damage this way.
2 connecting the 5v bec to the power pins the wrong way around, ie 5v to ground, 0v to vcc. could be done... and in testing this, vcc3.3 dropped to -0.3v
3 Servo noise on the rail. quite a plausable one, this was my prime suspect.
And as can be seen in the scope trace, the 3.3v jumps whenever the 5v rail goes above 6v. however, there was no sign of permanent damage. (this also assumed the onboard zener was damaged, simulated by removal of the zener.
4 direct short of the 5V to ground.
this had the obvious effect of shutting things down, and showed the 3.3v rail could hold above the 5v rail during shutdown for around 11 ms at 6-700mv above the 5v rail.
But again, no matter haw many times it was repeated, the failure did not come.
6 short of 3.3v reg to ground.
Again, no issues, it handled it well.
7 5v connected directly to the 3.3v rail via a faulty component.
Again, the reg had no problem with 5v on both sides.
and the Most rediculous suggestion of all.....
connecting a receiver while powered just by the USB could do it......
surely not I say....
watch the videos in order... the first showing the most unlikely to be the actual cause
the problem repeated
the second eliminates the u32 PPM encoder from the equation (as well as the level shifters)
reducing the suspects
and the third :) a solution a simple 100uF ceramic capacitor across the 5v rail
the solution
but the problem is still a problem.... WHY? what is it about the receivers that cause this. as you will see in video 1, it is not a large capacitance causing an inrush.
theories are welcome.......
Another note.... NO FIRMWARE WAS ON THE BOARD.......... this is a hardware issue, it is not caused by 3.01 firmware, but 3.01 shows the error if it is there.
so, to mod your board to reduce the risk of this happening? connect a cap to a old servo cable, between the blac and the red. use a ceramic cap, 100uF and plug this into Analogue 2 (if not used) make sure to remove the signal wire.
and finally, thankyou to 3DR who sent me 3 brand new, factory blank APM2.6's for this test.
Can you try shorting 5v to ground through an inductor?
One more thing for any 3DR guys listening, this may be a good time for a PSA announcement warning against plugging in peripherals while powered up.
Interesting. I actually have been putting capacitors on most of my boards already. I often leave the Input rail unpopulated, since I us PPM Sum, which leaves some convenient Vcc solder pads empty. I just solder a cap directly to those rails. I had done it just to protect against the possibility of power supply problems due to contact bounce due to vibration. Just seemed like a good idea.
I'll have to check, but the one that I have that is failed, I don't think I added the cap.
Did you by chance check to see if the diode between 3.3V and 5V would protect against this failure?
Would be interesting to find out if plugging anything else in while it's running would cause the same fault (GPS, Mag, etc).
Nice work Phillip
Link for videos in a playlist.
I'm temporarily closing this thread. I will re-open it in a few days once Philip has had a chance to do some more analysis on the problem.
-
12
-
13
-
14
-
15
-
16
of 30 Next