Skip to content

Conversation

@Apehaenger
Copy link
Collaborator

@Apehaenger Apehaenger commented Feb 9, 2026

Please see: xtech/fw-openmower-v2#38

Summary by CodeRabbit

Release Notes

  • New Features

    • Added charger input current monitoring to power service.
  • Improvements

    • Enhanced power service initialization with configurable system current parameter.
    • Refined power message field naming for clarity.
  • Configuration Updates

    • Adjusted charging current settings for Sabo hardware.

…ield

- add new callback and message field for charger_input_current
- rename dcdc_in_current field to dcdc_input_current for consistency
- update corresponding register setter name to SetRegisterSystemCurrentLimit
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 9, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/v2-power-management

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

- rename method `SetRegisterSystemCurrentLimit` to `SetRegisterSystemCurrent` for clarity
- update Sabo hardware charge current parameter from 3.0 to 2.5 to align with FW
@Apehaenger Apehaenger marked this pull request as ready for review February 10, 2026 20:56
Apehaenger added a commit to xtech/fw-openmower-v2 that referenced this pull request Feb 10, 2026
)

I do like to charge at max. possible power.
To achieve this I've to respect docks PSU current, which is on save
defaults, but might be changed via PowerService-Register.
In addition I need to estimate the power which get already burned by the
mower. This is mainly the current into the DCDC's and got already
implemented in an earlier PR.
There remains some unmeasured (blind) power going into the ESCs which
get handled (together with a measurement inaccuracy estimation) as
safety-reserve.
This is how I achieved this (feel free to judge/comment if there's a
better approach):

- [x] Add charger methods `readAdapterCurrent()` and
`setAdapterCurrent()`
- [x] Add PowerService functions to get configured charge currents and
adapter current limits
- [x] Add a PowerService::SetPowerManagementCallback() method so that a
robot is capable to add his individual power management settings, based
on his available sensors
- [x] Add a Sabo specific SaboRobot::OnPowerManagement() dynamic power
management callback

**Related PRs**:
xtech/definitions-open-mower#18
ClemensElflein/open_mower_ros#267

_Remark:_
The BQ2579 implementation didn't got tested by me due to missing device.
Someone need to check/test!
@Apehaenger Apehaenger merged commit 2973a31 into v2 Feb 10, 2026
1 check passed
@Apehaenger Apehaenger deleted the feat/v2-power-management branch February 10, 2026 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant