Skip to content

Conversation

@Apehaenger
Copy link
Collaborator

… system current name

- add new field with id 15 for charger input current monitoring
- rename 'System Current' to 'System Current Limit' for clarity in register definitions
@Apehaenger Apehaenger merged commit dad32a9 into main Feb 10, 2026
1 check passed
@Apehaenger Apehaenger deleted the feature/power-management branch February 10, 2026 21:31
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!
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