4 in 1 ESC not beeping when battery is pugged in

M

mr.carr

Member
Hello everyone. i don't know where to start i'm extremely new to this and i just got my quad put together and when i plug in the battery i do not get any beeps but the other bords get power. and the beta flight will connect to it but i can't do anything in it.
 
What escs, and fc?

I just had this problem on a build from yesterday I think it was the firmware on the escs was outdated and a quick flash of the spider 4in1 esc to the most recent firmware fixed it. You'll need to connect to blheli and see if it recognizes your escs.
 
Dugdog47 said:
What escs, and fc?

I just had this problem on a build from yesterday I think it was the firmware on the escs was outdated and a quick flash of the spider 4in1 esc to the most recent firmware fixed it. You'll need to connect to blheli and see if it recognizes your escs.
Click to expand...
hi. thank you for responding to me. it is the tekko esc and the kakute f7 atlatl v2 stack.
 
If getting 0 beeps there are only two possibilities, the ESC isn't getting power or the ESC isn't properly connected to the motor (or I supposed a 3rd the motor is dead). Even without an FC or anything sending it signals the ESC will do a couple of startup beeps to the motor (assuming firmware not corrupt on the ESC itself, as @Dugdog47 mentioned flashing it would fix this). Double check your connections to the motor, and double check your power to the ESC from the battery is good, take some pics if not sure.
 
wafflejock said:
If getting 0 beeps there are only two possibilities, the ESC isn't getting power or the ESC isn't properly connected to the motor (or I supposed a 3rd the motor is dead). Even without an FC or anything sending it signals the ESC will do a couple of startup beeps to the motor (assuming firmware not corrupt on the ESC itself, as @Dugdog47 mentioned flashing it would fix this). Double check your connections to the motor, and double check your power to the ESC from the battery is good, take some pics if not sure.
Click to expand...
here are some pics of how i have it put together. in BLHELI it says found multiple esc configuration in silabs mode. and when i click read setup it will give me this message (serial interface''m4wfcintf'' connected successfully. and below that connection to esc#1 failed! channel number 1 exceeds the capabilities of the current interface.
 

Attachments

  • 20210303_133033-min.jpg
    20210303_133033-min.jpg
    952.4 KB · Views: 2
  • 20210315_182349-min.jpg
    20210315_182349-min.jpg
    641.7 KB · Views: 3
  • 20210315_182415-min.jpg
    20210315_182415-min.jpg
    539.8 KB · Views: 3
  • 20210315_182430-min.jpg
    20210315_182430-min.jpg
    567.6 KB · Views: 3
  • 20210315_195758-min.jpg
    20210315_195758-min.jpg
    794.1 KB · Views: 2
Would try disconnect fc to esc signal wire and see if get beeps with just esc to motors if so double check the pin positions in the connector/wire between fc and esc, even though same port for the plug it may be different pin layout, different mfgs choose different order no real standard I'm aware of.
 
wafflejock said:
Would try disconnect fc to esc signal wire and see if get beeps with just esc to motors if so double check the pin positions in the connector/wire between fc and esc, even though same port for the plug it may be different pin layout, different mfgs choose different order no real standard I'm aware of.
Click to expand...
silence :( i'm starting to think i fried it with my soldering job
 
mr.carr said:
silence :( i'm starting to think i fried it with my soldering job
Click to expand...
Yah I mean looks pretty good to me but could have cooked something critical still like mcu or a connection to a pin on it from the mosfets, or something or could have just been doa or corrupted firmware from the factory (maybe slipped through whatever qc they're doing). I googled the error you got and found a few posts but nothing with definitive answer unfortunately. Let us know if you make any headway debugging though or just decide to replace it.
 
wafflejock said:
Yah I mean looks pretty good to me but could have cooked something critical still like mcu or a connection to a pin on it from the mosfets, or something or could have just been doa or corrupted firmware from the factory (maybe slipped through whatever qc they're doing). I googled the error you got and found a few posts but nothing with definitive answer unfortunately. Let us know if you make any headway debugging though or just decide to replace it.
Click to expand...
I sent holybro an email about the situation to see if there's any possibility that they might know something but if not and any of the software can't detect it I'm probably just going to get a new ESC.
 
Back
Top