Skip to content

Commit

Permalink
Note about voltage thresholds
Browse files Browse the repository at this point in the history
  • Loading branch information
MSECode committed Dec 1, 2023
1 parent 86c997d commit 19ba476
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/battery_boards/bat_board/bat_protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,8 @@ When one desire to update the `BAT` firmware version the correct `.hex` version
- `bat.hex` which is the version to be used on `iCub` and `ergoCub`

It should be noted that we are developing two different versions for the `BAT` because the `dcdc_management` phase is done different between `R1` and `iCub` or `ergoCub`.
Specifically, in `iCub` and `ergoCub` the management of the cpu and motors lines is done separately and they can work detached. Differently, in `R1` cpu and boards lines work always together.
Specifically, in `iCub` and `ergoCub` the management of the cpu and motors lines is done separately and they can work detached. Differently, in `R1` cpu and boards lines work always together.
Moreover, since `R1` and `iCub` and `ergoCub` works with different battery packs, the voltage thresholds are set differently on the two firmwares.

In general, as shown in the figures below (illustrating the connection between the BAT and EMS boards in the base of `R1/SN003`), the `BAT` can be connected to an EMS board through the `CAN` connector devoted to receiving the CAN frames sent out by the `BAT`.

Expand Down

0 comments on commit 19ba476

Please sign in to comment.