ArduPilot / ArduPilot/MissionPlanner

New Pixhawk 6C ConfigBatteryMonitoring Not Working Correctly

Open
#2,948 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

#### Issue details
This battery monitor setting isn't working properly for HW Ver: `10: Pixhawk 6C/Pix32 v6`
It would switch to HW Ver : `1: APM2- 2.5 non 3DR` Automatically after switching tab.

https://user-images.githubusercontent.com/46874772/215253185-296475bf-7885-4a5f-b99c-e5f039f76033.mp4

Looking at the parameters below, it also did not change accordingly.

https://user-images.githubusercontent.com/46874772/190566214-fa35fe84-4ef8-49c1-95ef-1822798d3ab0.mp4

It should be the value below.

HW Ver: Pixhawk 6C/Pix32 v6

- BATT_VOLT_PIN: 8
- BATT_CURR_PIN: 4

#### Version
Mission Planner 1.3.79

_**HW Ver: 10: Pixhawk 6C/Pix32 v6**_ was added via https://github.com/ArduPilot/MissionPlanner/commit/2c336fef6da34160c5334123ebde6bc97cb12b83 & https://github.com/ArduPilot/MissionPlanner/commit/299c56d10f8c4a7bd2eabd2434f2f99f3cff440e

#### Platform
[ X ] All

#### Hardware type
Pixhawk 6C + PM02

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing commits 2c336fef6da34160c5334123ebde6bc97cb12b83 and 299c56d10f8c4a7bd2eabd2434f2f99f3cff440e, which added the Pixhawk 6C/Pix32 v6 hardware version. Reproduce the battery-monitor configuration issue in Mission Planner 1.3.79 by switching tabs, then compare the selected hardware version and BATT_VOLT_PIN/BATT_CURR_PIN values with the expected 10, 8, and 4. Done means the setting remains Pixhawk 6C/Pix32 v6 and the parameters update correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.