Issue with Arm: "Arm/PreArm: Logging failed" Error

Hello,

I’m experiencing an issue with my drone that prevents it from arming. Here’s what happens:

  1. When the battery is not connected and I try to arm using the arm switch, the error message appears:
  • “Arm: Logging failed”
  • “Arm: Battery 1 low voltage failsafe”
  1. When the battery is connected, the quadcopter remains unarmed and gives the following messages:
  • “Battery failsafe”
  • “Arm: Logging failed”

My Setup and Observations:

  • Battery: I’m using a brand-new 4S, 3300mAh LiPo battery.
  • Failsafe Settings and Initial Tune Parameters: Shown in the attached images.
  • Battery Voltage: The battery voltage seems fine.
  • Connections: All connections between the battery and the power module are secure.

What I Tried:

  • I found some troubleshooting tips online and applied them, but the issue persists.
  • Turning off arming checks allowed me to arm the quadcopter, but I’d prefer to resolve the root cause rather than bypassing the checks.

I’d appreciate any suggestions or guidance on how to resolve this issue.

Thank you in advance!

Best regards,
Michail.

You either

Have no voltage monitor or
Voltage monitor is incorrectly configured or
Voltage monitor is incorrectly connected

It’s hard to say without more information from you

1 Like

Hello again,
Since I don’t fully understand what you mean, could you please explain what exactly you want me to provide.

I am also attaching below an image of the HUD, showing the battery status.

Explain in excruciating detail what hardware do you have and how it is connected to each other.

What FC?
What battery monitor?
Connected via CAN? I2C? Analog?

Hardware Setup:

The hardware I’m using is as follows:

Frame: HR0686 F450 drone chassis
Motors: HS2637 2212 920KV Brushless Motor
Flight Controller - ESC: SpeedyBee F405 V4 BLS 55A 30x30 FC & ESC Stack
GPS: ublox NEO-7M
Receiver: Flysky FS-A8S
Controller: Flysky FS-i6
Camera: ESP32-CAM module (ESP32-CAM with ESP32-CAM MB adapter)
Battery: Gens Ace LiPo Soaring 3300mAh 14.8V 30C 4S1P XT90

Connections:

Motors to ESC:
    The four motors are connected directly to the ESC.

Power to ESC:
    I connected an XT-60 male plug to power the ESC. Since my battery has an XT-90 connector, I used an XT-60 female to XT-90 male adapter.

Connections to Flight Controller:

  1. GPS to FC
4V5 (SpeedyBee F405 V4) -> VCC (uBlox NEO-7M as GPS)  
G (SpeedyBee F405 V4) -> GND (uBlox NEO-7M as GPS)  
SDA (SpeedyBee F405 V4) -> SDA (uBlox NEO-7M as GPS)  
SCL (SpeedyBee F405 V4) -> SCL (uBlox NEO-7M as GPS)  
R6 (SpeedyBee F405 V4) -> TXD (uBlox NEO-7M as GPS)  
T6 (SpeedyBee F405 V4) -> RXD (uBlox NEO-7M as GPS)  
  1. Receiver to FC
4V5 (SpeedyBee F405 V4) -> VCC (Flysky FS-A8S)  
G (SpeedyBee F405 V4) -> GND (Flysky FS-A8S)  
SBUS (R2) (SpeedyBee F405 V4) -> i-BUS/S.BUS (Flysky FS-A8S)  
  1. Camera to FC
5V (SpeedyBee F405 V4) -> 5V (ESP32-CAM module)  
G (SpeedyBee F405 V4) -> GND (ESP32-CAM module)  
R3 (SpeedyBee F405 V4) -> U0T (ESP32-CAM module)  
T3 (SpeedyBee F405 V4) -> U0R (ESP32-CAM module)  

These are all the connections I have made on my drone.

Additional Notes:

I should note that before flashing ArduPilot, I had used iNav, which I have now removed. When I was using iNav, I didn’t encounter any issues with failsafe or the battery.

Thank you again in advance for your help!

I think I might have made a mistake in what I mentioned earlier because the message ‘PreArm: Battery 1 low voltage failsafe’ appears when I don’t have the battery connected.

The issue is that it shows ‘PreArm: Logging failed’ (before I switch to arm) and ‘Arm: Logging failed’ (after I switch to arm), which prevents me from arming my drone. When I disable ARMING_CHECK, I can arm the drone and test the motors, but there is a slight delay.

Note: In my previous answer I said that I had previously uploaded Inav and followed the steps presented on the site below to remove it and flash the ArduPilot.
https://ardupilot.org/copter/docs/common-loading-firmware-onto-chibios-only-boards.html

Now configure it correctly using ArduPilot methodic configurator software.

1 Like

Post a link to the .bin log file from this event.

  • For some reason when I go to the DataFlash Logs tab, in order to download the logs from the event, it says:
    Getting list of log files…
    No logs to download

    I saw that in many cases you need a sd card in order to save the logs, but I inserted a sd card, after I formed it in FAT32, and still says no logs to download.

  • For what you said amilcarlucas I am trying it as I upload the post. To be honest with you, because Im new in drones and ardupilot in general, I didnt know that there was such a thing. I am going to give it a try and I will update you.

Thank you in advance.

Yes you do. If it Arms it should create a log.

  1. Question for the Ardupilot methodic configurator:

Im trying to go through the steps from the Quick start guide the methodic configurator(Quick start guide | MethodicConfigurator).

Im a bit stuck because I don’t know what vehicle template to select(and yes I saw that you say it doesnt need to fully match my vehicle). My main concern is that when I press the Create vehicle configuration from template, it says as a flight controller that it is the speedybee f405 mini v3(and it is locked so i cant change it) and I said in a previous post I have the speedybee f405 v4.

I’m worried because when I went (based on this Loading Firmware onto boards without existing ArduPilot firmware — Copter documentation, as i also said earlier) to do the “Download the ArduPilot firmware” step, it said “look for the directory with the name that most closely matches the autopilot”. There the only names that were closer to mine were the following:
SpeedyBeeF405Mini
SpeedyBeeF405Mini-heli
SpeedyBeeF405WING
SpeedyBeeF405WING-heli

And therefore since Im working with a quadcopter, I chose the SpeedyBeeF405Mini.

Have I done something wrong?

  1. Also not to make a second post, what can I do about my problem with logs and logging failed, do you have any idea, since I can’t download logs, since the drone won’t arm?

Thank you in advance for your help

Some F4 boards get overloaded when they are booting. Make sure the SD card is good, and you can use your computer to reformat it. Then try this:

ARMING_CHECKS,1
INS_LOG_BAT_MASK,0
LOG_BACKEND_TYPE,1
LOG_FILE_BUFSIZE,8
SRTL_POINTS,0

No, That is the correct one.

The ArduPilot FW version for both v3 and v4 is the same as you seen already.

I tried to change these parameters and IT WORKED, I was able to arm my drone.
Here are the values that I had in these specific parameters before I changed them:

ARMING_CHECKS, 1
INS_LOG_BAT_MASK, 0
LOG_BACKEND_TYPE, 4
LOG_FILE_BUFSIZE, 16
SRTL_POINTS, 300

I still don’t have any logs to download, but as you can see in the screenshot, the PreArm and Arm: Logging failed messages disappeared. I should also note that my sd card is 16gb. I saw, and correct me if im wrong, that it is better to have a smaller storage sd card(4,8 gb).

Last im going to finish the steps for. the Ardupilot methodic configurator.

Thanks again in advance and thanks also for the fix.

This is only correct for a board that doesn’t have an Sd card. The default parameters should have been right if the firmware matched the board. But hey it’s a SpeedyBee. Or more appropriate on the forum a NeedyBee :slight_smile:

So the problem is that the firmware that is flashed in the board, which for the speedybee mini, isn’t matching with the board that I have, which is the speedybee f405 v4?

And if so, what do you think is the best solution in my problem? Should I erase the data from the chip and flash it again?
I’m asking because I don’t want to do a short term fix and then after a while I get the same thing again or something else related to it.

Also how can I not have any logs to download, even though I armed the drone?

Finally, I have a general question, not related to any of these. Which would you say is a good, not so expensive, flight controller? Because I thought this speedybee board was good, but you got me thinking with the NeedyBee comment.

Thank you again so much in advance.

There is firmware for that board. It’s right here: NeedyBee F4V4
Download the .apj file and use Mission Planners “load custom firmware” to flash it.

Matek H743 (various versions), Holybro Kakute H7 (couple versions).

1 Like

I’ll also give the nod of approval to Matek. I’ve used many of their boards (F4 and H7) and they’ve worked well. I haven’t used the Kakute boards, but I’ve used enough other Holybro products that I’d take @dkemxr’s word for it.

Yes, smaller cards are better, but trying to find a good quality card under 16gb or 8gb isn’t worth the struggle. You don’t need a fancy, high speed card. Pretty much any good quality will do the job.

1 Like

I stand corrected. Thanks @dkemxr
@HowdyCandy once you upload the correct firmware, the ardupilot methodic configurator will automatically detect it.

1 Like

Delete, posted in wrong thread.