I purchased a NamelessRC AIO from a local dealer - this is my second one, and the first one worked great.  This one has been a nightmare.

First, I had problems getting BLHeli to read the ESCs - each time I plugged in, a random one or two would show up as unknown, and then be fine the next time.  

This one I took for a maiden this evening and a few seconds in, I got a "Core temp" warning that climbed really fast.  Before I understood what was happening, the quad flipped out and crashed a couple of feet into the grass. Now, no ESCs beep on startup.  

I brought it in and took it apart, I noticed the MCU was REALLY hot.  I desoldered everything and plugged in again, and sure enough the whole MCU got burning hot quickly, so I unplugged. 

Upon looking over the board, I noticed that it appears a Mosfet is missing.  I don't think the crash could have done this - but could this cause the MCU to overheat?  I'm assuming the board is done for but I'd like to think it's not my fault before I go back to the dealer.  Do boards ship like this?  Seems like sketchy QC.

   

The failure rate for AIO boards is still pretty high.

I would try and ask for a replacement if possible.

Thanks kafie! I just heard back and he said he'll give me a new one no charge. I just wonder from an electronics standpoint if the missing fet is what's causing the MCU if possible.

The MCU frying itself will either be an external short to one of the input circuits to the MCU, or an internal sort within the MCU itself. If anything, the missing MOSFET would help mitigate any external shorts that might have been present on that part of the circuit because all of the pads that it was once soldered to are now all open circuit.

(17-Jul-2021, 06:33 PM)SnowLeopardFPV Wrote: The MCU frying itself will either be an external short to one of the input circuits to the MCU, or an internal sort within the MCU itself. If anything, the missing MOSFET would help mitigate any external shorts that might have been present on that part of the circuit because all of the pads that it was once soldered to are now all open circuit.

So do you mean the missing mosfet wouldn't be the problem as it is no longer transporting a current?

I checked again and the 5v regulator on the opposite side of the MCU is what's burning. I'm tempted to replace the regulator, but the missing mosfet and the fact that blheli couldn't ever seem to read all the ESCs at once tell me that maybe this is indeed a faulty board. I'll return it tomorrow.

(18-Jul-2021, 05:02 AM)JinxFPV Wrote: So do you mean the missing mosfet wouldn't be the problem as it is no longer transporting a current?

Yes, exactly that.