# What is the Updated and Stable PX4 Release for Pixhawk 2.4.8

**URL:** <https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659>\
**Category:** PX4 Autopilot\
**Created:** [May 20, 2025, 8:24pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659 "2025-05-20T20:24:40Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kadir\_Elmas](https://discuss.px4.io/user_avatar/discuss.px4.io/kadir_elmas/32/19455_2.png) [@Kadir\_Elmas](https://discuss.px4.io/u/Kadir_Elmas)\
**Post date:** [May 20, 2025, 8:24pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/1 "2025-05-20T20:24:40Z")

</div>

Hello, I have a **Pixhawk 2.4.8** and I’m experiencing some issues. My board frequently shows _ **sensor errors** _ , and I believe I need to upload a different firmware version to fix these problems.

Currently, the firmware version shown in **QGroundControl** is **1.15.4** , and the board is detected as **FMUv2**. However, when I attempt to update the firmware—similar to what is described in this discussion:

> **[Pixhawk 2.4.8 Firmware?](https://discuss.ardupilot.org/t/pixhawk-2-4-8-firmware/53185/10)**
>
> Hello, Thanks to all the contributors, their help proved extremely useful! I found this thread searching for a solution to upgrade two boards that refused to be recognized by the mission planner firmware update tool. I have no tools to know why...

—it still installs **FMUv3** , even though my hardware is **FMUv2**. After flashing, the **vehicle version** still shows **FMUv2** , not FMUv3, even though FMUv3 was supposedly uploaded.Like screenshoot below.

When I try to follow the suggestion from the link to update the **bootloader** using the **SYS\_BL\_UPDATE** parameter, I cannot find this parameter in my system. It simply doesn’t appear in QGroundControl.

So my questions are:

1. Are **v1.15.4** and **FMUv3-FMUv2** just different labels for the same firmware, or are they **truly different firmware targets**?
2. How can I ensure that the **correct firmware** is flashed to my **Pixhawk 2.4.8**?
3. What is the **most stable and reliable PX4 firmware version** for Pixhawk 2.4.8, especially for use in **fixed wing vehicles**?

If there is a **custom or legacy firmware** specifically built for boards like Pixhawk 2.4.8, I’d appreciate it if someone could share a **direct link** or explain how to compile or download it manually.

Thanks in advance for your help!

 ![firmware-update](https://discuss.px4.io/uploads/default/original/3X/7/e/7e8287ff0f3332bb22f2baaf8eadf760165a4f1f.jpeg)  
 ![some-of-the-sensor-errors](https://discuss.px4.io/uploads/default/original/3X/4/3/43f0b6e263f4f6f0ccb16522faa1705a71b660f0.png)

Additionally, for reference, here is the **log file** from when I **armed the vehicle (not during flight)** , which might help in diagnosing the issue:

> **[Pixhawk 2.4.8 LOGS - Google Drive](https://drive.google.com/drive/folders/1ZT97YrWQOo-BeTGqsWEvlJxQs9Gp93mP?usp=sharing)**

---

<div class="post-metadata">

**Author:** ![dakejahl](https://discuss.px4.io/user_avatar/discuss.px4.io/dakejahl/32/20420_2.png) [@dakejahl](https://discuss.px4.io/u/dakejahl)\
**Post date:** [May 20, 2025, 8:41pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/2 "2025-05-20T20:41:26Z")

</div>

> [@Is Pixhawk 2.4.8 fully supported by px4?](https://discuss.px4.io/t/is-pixhawk-2-4-8-fully-supported-by-px4/27180/2):
>
> pixhawk 2.4.8 its fully supported by PX4. there are two versions… px4fmuv2 and px4fmuv3. If your board its equipped with the stm32f427vit6 rev3 your board will be flashes with px4fmuv3. Pixhawk 4 released by holybro its px4fmuv5

Sounds like there are two variations of the 2.4.8 which have different processors, one with 1MB flash and the other with 2MB. Regarding sensors errors, can you share a log file? Upload to [https://review.px4.io/](https://review.px4.io/) and share a link. You can enable logging from boot with SDLOG\_MODE

---

<div class="post-metadata">

**Author:** ![Kadir\_Elmas](https://discuss.px4.io/user_avatar/discuss.px4.io/kadir_elmas/32/19455_2.png) [@Kadir\_Elmas](https://discuss.px4.io/u/Kadir_Elmas)\
**Post date:** [May 20, 2025, 8:51pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/3 "2025-05-20T20:51:28Z")

</div>

Thank you for your response.  
I just saw your message right after I updated my post.  
I’ve added the log files at the end of the post, as you suggested.

These logs were recorded after I managed to arm the vehicle with some effort by slightly bending the wings, just to get past the error.  
Please note that the logs were taken while the vehicle was armed but not during flight.

---

<div class="post-metadata">

**Author:** ![dakejahl](https://discuss.px4.io/user_avatar/discuss.px4.io/dakejahl/32/20420_2.png) [@dakejahl](https://discuss.px4.io/u/dakejahl)\
**Post date:** [May 20, 2025, 9:14pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/4 "2025-05-20T21:14:31Z")

</div>

Please share a link to the log which has the “sensor errors”, I don’t have time to go through all of your logs on drive and download/upload them to flight review. Providing as much detail as possible for the exact log in question will help me help you.

---

<div class="post-metadata">

**Author:** ![Kadir\_Elmas](https://discuss.px4.io/user_avatar/discuss.px4.io/kadir_elmas/32/19455_2.png) [@Kadir\_Elmas](https://discuss.px4.io/u/Kadir_Elmas)\
**Post date:** [May 20, 2025, 9:29pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/5 "2025-05-20T21:29:17Z")

</div>

Sorry about that.Thanks for the clarification.  
Here is the direct link to the log that includes the **sensor errors** :

> **[Flight Review](https://review.px4.io/plot_app?log=8ff3c317-44d0-4135-92e4-e01e02aadcae)**

---

<div class="post-metadata">

**Author:** ![dakejahl](https://discuss.px4.io/user_avatar/discuss.px4.io/dakejahl/32/20420_2.png) [@dakejahl](https://discuss.px4.io/u/dakejahl)\
**Post date:** [May 20, 2025, 9:50pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/6 "2025-05-20T21:50:40Z")

</div>

It looks like your 5V input voltage is unstable. Which power module are you using? Since 1.15 the low voltage check has been reduced from 4.8V to 4.7V, however your 5V input is very noisy.

 ![image](https://discuss.px4.io/uploads/default/original/3X/4/8/48f77b15a337966af5f666ddad34b3ecd822f6df.png)

---

<div class="post-metadata">

**Author:** ![Kadir\_Elmas](https://discuss.px4.io/user_avatar/discuss.px4.io/kadir_elmas/32/19455_2.png) [@Kadir\_Elmas](https://discuss.px4.io/u/Kadir_Elmas)\
**Post date:** [May 21, 2025, 3:45am UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/7 "2025-05-21T03:45:59Z")

</div>

That might be expected because in the latest logs I was getting **occasional power losses** in addition to the **sensor errors**. I have since **replaced my power module cable** , but I haven’t had the chance to test it in a new flight yet.

However, I do have a **previous flight log** from before I started experiencing the power cable issues.  
Here is the earlier log:

> **[Flight Review](https://review.px4.io/plot_app?log=7b1aa036-63ac-4dbe-8c21-a955a67b2ec3)**

I just want to be sure — is the issue **only** caused by **voltage instability** , or could there be something else contributing to the sensor errors?

---

<div class="post-metadata">

**Author:** ![dakejahl](https://discuss.px4.io/user_avatar/discuss.px4.io/dakejahl/32/20420_2.png) [@dakejahl](https://discuss.px4.io/u/dakejahl)\
**Post date:** [May 22, 2025, 12:24am UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/8 "2025-05-22T00:24:20Z")

</div>

That log has the same error messages about avionics power. Scroll to the bottom of the page and take a look at the **Logged Messages**. What do you mean by “sensor errors”?

---

<div class="post-metadata">

**Author:** ![Kadir\_Elmas](https://discuss.px4.io/user_avatar/discuss.px4.io/kadir_elmas/32/19455_2.png) [@Kadir\_Elmas](https://discuss.px4.io/u/Kadir_Elmas)\
**Post date:** [May 22, 2025, 3:20pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/9 "2025-05-22T15:20:28Z")

</div>

I’m using a **Pixhawk 2.4.8** with a **Power Module v1.0**.  
I measured the **voltage at the Pixhawk power input** using the multimeter shown in **Photo 2** , and I got a reading of **5.26V**.  
The battery I’m using is a **4S1P 22000mAh LiPo** , nominal voltage **14.8V**. During the measurement, the battery voltage was **16.36V**.

While connected to QGroundControl (including GPS), I’ve done multiple calibration attempts, yet I’ve been consistently getting the following **sensor-related error messages** :

- _Compass inconsistent by (some) degrees_ → This is the most frequent one.
- _Height estimate not stable_ → This appears occasionally.

Additionally, I want to note that the **power socket on my Pixhawk** is **physically damaged** , as shown in the attached photo.  
I’m wondering if that could also be contributing to the issue.

 ![the-power-module](https://discuss.px4.io/uploads/default/original/3X/c/3/c3e492b73c9f5a40dc3cac2c7f525d9d4c4335bb.jpeg)

 ![the-measurement-way](https://discuss.px4.io/uploads/default/original/3X/a/c/ac59777e09d30899d9352c09fe00265aef8e3aaa.jpeg)

 ![pixhawk-power-input-socket](https://discuss.px4.io/uploads/default/original/3X/9/b/9b6ea65cf4d762380c7d591ac51924ea44940766.jpeg)

---

<div class="post-metadata">

**Author:** ![dakejahl](https://discuss.px4.io/user_avatar/discuss.px4.io/dakejahl/32/20420_2.png) [@dakejahl](https://discuss.px4.io/u/dakejahl)\
**Post date:** [May 22, 2025, 6:21pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/10 "2025-05-22T18:21:40Z")

</div>

The power monitor is analog, the noisy voltage is likely just noise. Although it’s possible the 5V output has ripple that a DC measurement on your multi-meter isn’t going to see. You can bypass the power errors by setting CBRK\_SUPPLY\_CHK.

The compass inconsistent usually indicates a poor/missing calibration or an incorrect rotation between the internal and external magnetometer.

The height estimate not stable would indicate noisy sensor data from either your baro or GPS or both.

To be completely honest this hardware is cheap and of very low quality and I would recommend using higher quality components if your budget allows. It will save you a lot of headache.

---

<div class="post-metadata">

**Author:** ![system](https://discuss.px4.io/uploads/default/original/3X/7/3/73ce918bdcd64854de904f0c8d9ab70ca9723f2a.png) [@system](https://discuss.px4.io/u/system)\
**Post date:** [August 20, 2025, 6:22pm UTC](https://discuss.px4.io/t/what-is-the-updated-and-stable-px4-release-for-pixhawk-2-4-8/45659/11 "2025-08-20T18:22:23Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
