Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 Hi everyone,
I'm new to FPV and I recently crashed my Nazgula v3 drone. The battery took the hit but the drone its self doesn't have any damage. Now when I plug in the battery the audio is different, Its 3 regular beeps but the last 2 are a down beat tone. Also the orange light which say 'BAT' stays on. I'm not seeing anything wrong in Betaflight. My controller binds normally and the motors spin no problem. Any help would be greatly appreciated, Thanks! ![[-]](https://intofpv.com/images/collapse.png) • Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 It's possible when damage occurred to the battery during the crash that it caused a voltage surge to the ESC board and resulted in some damage to it, or if you weren't quick enough to disarm the quad when it crashed and the motors not being able to spin due to the props being caught on something could have caused enough EMF backflow through the ESC MOSFETs to damage them.
Post up a video showing the 5 tones being played during start-up. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (27-Apr-2024, 11:59 AM)SnowLeopardFPV Wrote: It's possible when damage occurred to the battery during the crash that it caused a voltage surge to the ESC board and resulted in some damage to it, or if you weren't quick enough to disarm the quad when it crashed and the motors not being able to spin due to the props being caught on something could have caused enough EMF backflow through the ESC MOSFETs to damage them.
Post up a video showing the 5 tones being played during start-up. Hey thanks for the quick response, Attached is a link to the video of the start up tone. When the drone crashed it was disarmed and the motors were not spinning. Also I attached a photo of the Battery. ![[Image: iudsCF8l.jpeg]](https://i.imgur.com/iudsCF8l.jpeg) https://drive.google.com/file/d/1If6A_OA...sp=sharing • Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 I see what you mean. Those last two tones are much faster than you normally hear from BLHeli_S ESC with Bluejay firmware installed on them. I don't have any BLHeli_S with Bluejay firmware later than V0.16 on them so I'm not sure if later Bluejay firmware changed the time period between the last two tones. Were those last two tones always that fast?
What Bluejay formware version is on your ESCs? It might be worth trying to reflash the same firmware version to them in case something somehow got corrupted. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (27-Apr-2024, 04:50 PM)SnowLeopardFPV Wrote: I see what you mean. Those last two tones are much faster than you normally hear from BLHeli_S ESC with Bluejay firmware installed on them. I don't have any BLHeli_S with Bluejay firmware later than V0.16 on them so I'm not sure if later Bluejay firmware changed the time period between the last two tones. Were those last two tones always that fast?
What Bluejay formware version is on your ESCs? It might be worth trying to reflash the same firmware version to them in case something somehow got corrupted. I just re flashed the ESC's and they’re now currently running on BlueJay Q-H-30 0.19. 24Hz. No luck though unfortunately. The difference in the start up tone now is the is the last 2 beats are a down beat. : Q • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (27-Apr-2024, 07:27 PM)AirbusFPV Wrote: I just re flashed the ESC's and they’re now currently running on BlueJay Q-H-30 0.19. 24Hz. No luck though unfortunately. The difference in the start up tone now is the is the last 2 beats are a down beat. : Q Do you think its possible the Capacitor is damaged? • Posts: 5,867 Threads: 47 Likes Received: 2,779 in 2,241 posts Likes Given: 7,635 Joined: Jul 2019 Reputation: 97 Welcome  Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (27-Apr-2024, 08:30 PM)AirbusFPV Wrote: Do you think its possible the Capacitor is damaged? I guess you have nothing to lose by changing the capacitor but I'd be surprised if that was causing the issue you are having. I think all you can really do is just fly it, but take care and don't fly too far out until you are 100% confident that everything is OK when it is actually flying. If you're not happy about doing that or don't want to take any chances then just swap out the ESC board for a new one. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (28-Apr-2024, 05:02 PM)SnowLeopardFPV Wrote: I guess you have nothing to lose by changing the capacitor but I'd be surprised if that was causing the issue you are having.
I think all you can really do is just fly it, but take care and don't fly too far out until you are 100% confident that everything is OK when it is actually flying. If you're not happy about doing that or don't want to take any chances then just swap out the ESC board for a new one. Unfortunately The drone doesn't fly at all, When I go to arm the motors refuse to start spinning. But in Betalight the controller is still sending all the information to arm and dis arm like normal. • Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 It's possible that you have a bad connection on the FC-to-ESC wiring harness. Try re-seating both connectors by unplugging and re-plugging them. And while they are out, use a magnifying glass to check inside the sockets for any bent or damaged pins.
Do the motors spin if you use the sliders in the Motors tab of Betaflight Configurator? Remember that you need a LiPo plugged in to do that. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (28-Apr-2024, 10:30 PM)SnowLeopardFPV Wrote: It's possible that you have a bad connection on the FC-to-ESC wiring harness. Try re-seating both connectors by unplugging and re-plugging them. And while they are out, use a magnifying glass to check inside the sockets for any bent or damaged pins.
Do the motors spin if you use the sliders in the Motors tab of Betaflight Configurator? Remember that you need a LiPo plugged in to do that. Ill give that a shot and yes all the motors spin normally when I hook up the drone to betaflight. • Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 (28-Apr-2024, 10:32 PM)AirbusFPV Wrote: Ill give that a shot and yes all the motors spin normally when I hook up the drone to betaflight. If the motors spin from Betaflight Configurator then the ESC-to-FC harness connections should be OK, but re-seat / check them anyway just to eliminate that as a possible cause. Maybe something else is preventing your quad from arming. Plug the FC into your computer and in Betaflight Configurator go to the CLI tab. Then do the following:- 1. With the arming switch in the disarmed position run the "status" command and post the results back here. 2. With the arming switch in the armed position run the "status" command and post the results back here. Don't forget that you need to make sure you have the throttle all the way to its bottommost position before you try to arm the quad. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (28-Apr-2024, 10:42 PM)SnowLeopardFPV Wrote: If the motors spin from Betaflight Configurator then the ESC-to-FC harness connections should be OK, but re-seat / check them anyway just to eliminate that as a possible cause.
Maybe something else is preventing your quad from arming. Plug the FC into your computer and in Betaflight Configurator go to the CLI tab. Then do the following:-
1. With the arming switch in the disarmed position run the "status" command and post the results back here.
2. With the arming switch in the armed position run the "status" command and post the results back here.
Don't forget that you need to make sure you have the throttle all the way to its bottommost position before you try to arm the quad. Disarmed - # # Building AutoComplete Cache ... Done! # # status MCU F722 Clock=216MHz, Vref=3.28V, Core temp=47degC Stack size: 2048, Stack address: 0x20010000 Configuration: CONFIGURED, size: 3644, max available: 16384 Devices detected: SPI:1, I2C:1 Gyros detected: gyro 1 locked dma GYRO=ICM42688P, ACC=ICM42688P, BARO=DPS310 OSD: MAX7456 (30 x 13) BUILD KEY: 128aa7787d0e5deacbe047998ecf198d (4.4.3) System Uptime: 74 seconds, Current Time: 2024-04-28T21:50:23.947+00:00 CPU:5%, cycle time: 125, GYRO rate: 8000, RX rate: 248, System rate: 10 Voltage: 0 * 0.01V (0S battery - NOT PRESENT) I2C Errors: 0 FLASH: JEDEC ID=0x00ef4019 32M Arming disable flags: BADRX CLI MSP ARMSWITCH Armed - # # Building AutoComplete Cache ... Done! # # staTUS MCU F722 Clock=216MHz, Vref=3.28V, Core temp=48degC Stack size: 2048, Stack address: 0x20010000 Configuration: CONFIGURED, size: 3644, max available: 16384 Devices detected: SPI:1, I2C:1 Gyros detected: gyro 1 locked dma GYRO=ICM42688P, ACC=ICM42688P, BARO=DPS310 OSD: MAX7456 (30 x 13) BUILD KEY: 128aa7787d0e5deacbe047998ecf198d (4.4.3) System Uptime: 27 seconds, Current Time: 2024-04-28T21:51:32.550+00:00 CPU:5%, cycle time: 125, GYRO rate: 8000, RX rate: 242, System rate: 10 Voltage: 0 * 0.01V (0S battery - NOT PRESENT) I2C Errors: 0 FLASH: JEDEC ID=0x00ef4019 32M Arming disable flags: CLI MSP • Posts: 21,227 Threads: 584 Likes Received: 8,955 in 6,626 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Looking at your status output, the first output shows that you powered on the quad or the transmitter with the arm switch already in the ARM position when they bound together which is the reason for the BADRX and the ARMSWITCH arming disable flags. Then the second output shows that you moved the arm switch to the DISARM position.
Please do the same again but this time make sure you have the ARM switch in the DISARMED position when you power on your transmitter and the quad, then run the "status" command. Then move the ARM switch to the ARM position and run the "status" command again and repost the output of both back here. • Posts: 12 Threads: 2 Likes Received: 0 in 0 posts Likes Given: 4 Joined: Apr 2024 Reputation: 0 (29-Apr-2024, 12:00 AM)SnowLeopardFPV Wrote: Looking at your status output, the first output shows that you powered on the quad or the transmitter with the arm switch already in the ARM position when they bound together which is the reason for the BADRX and the ARMSWITCH arming disable flags. Then the second output shows that you moved the arm switch to the DISARM position.
Please do the same again but this time make sure you have the ARM switch in the DISARMED position when you power on your transmitter and the quad, then run the "status" command. Then move the ARM switch to the ARM position and run the "status" command again and repost the output of both back here. I see what your saying here's the results with your instructions. Disarmed - # status MCU F722 Clock=216MHz, Vref=3.28V, Core temp=45degC Stack size: 2048, Stack address: 0x20010000 Configuration: CONFIGURED, size: 3644, max available: 16384 Devices detected: SPI:1, I2C:1 Gyros detected: gyro 1 locked dma GYRO=ICM42688P, ACC=ICM42688P, BARO=DPS310 OSD: MAX7456 (30 x 13) BUILD KEY: 128aa7787d0e5deacbe047998ecf198d (4.4.3) System Uptime: 23 seconds, Current Time: 2024-04-28T23:04:50.673+00:00 CPU:5%, cycle time: 125, GYRO rate: 8000, RX rate: 255, System rate: 10 Voltage: 0 * 0.01V (0S battery - NOT PRESENT) I2C Errors: 0 FLASH: JEDEC ID=0x00ef4019 32M Arming disable flags: BADRX CLI MSP ARMSWITCH Armed- # status MCU F722 Clock=216MHz, Vref=3.28V, Core temp=45degC Stack size: 2048, Stack address: 0x20010000 Configuration: CONFIGURED, size: 3644, max available: 16384 Devices detected: SPI:1, I2C:1 Gyros detected: gyro 1 locked dma GYRO=ICM42688P, ACC=ICM42688P, BARO=DPS310 OSD: MAX7456 (30 x 13) BUILD KEY: 128aa7787d0e5deacbe047998ecf198d (4.4.3) System Uptime: 12 seconds, Current Time: 2024-04-28T23:05:33.443+00:00 CPU:5%, cycle time: 124, GYRO rate: 8064, RX rate: 243, System rate: 9 Voltage: 0 * 0.01V (0S battery - NOT PRESENT) I2C Errors: 0 FLASH: JEDEC ID=0x00ef4019 32M Arming disable flags: CLI MSP • |
