Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Battery charge not shown in Android apps #136

corot opened this Issue · 1 comment

1 participant


No description provided.

@corot corot was assigned

Fixed with two changes:

  • I modified diagnostics.yaml to remove the node name (by adding remove_prefix: mobile_base)
  • We send Current Charge and Capacity diagnostic values. See /kobuki_node/src/node/diagnostics.cpp


  • As "Current (A)", we send 0 when the robot is unplugged and 3.14 if charging/charged. 3.14 is the current supplied by our basic charger. So if this changes, or the docking base differs, this value will be false. This is not terrible because we identify properly when the robot is charging, but just a bit amateurish.

  • As "Capacity (Ah)" we always send 2.2, what is that of the 4S1P battery, because by now we cannot identify the battery at use in our driver. This is not terrible too, because of the way we calculate the charge percent, explained below.

  • As "Charge (Ah)" we send the capacity multiplied by the charge percent and divided by 100. As we obtain this percent from the voltage, all this tricky Amperage values don't affect the charge shown to the user, that is correct despite the validity of all these hardcoded values.

@corot corot closed this
@corot corot was unassigned by bit-pirate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.