BMS support
OPHION application supports multiple Battery Management Systems (BMS). The BMS should monitor battery state and enable dynamic current limitation in error conditions via the controller. This prevents dangerous situations where BMS power cutoff during operation could occur - the controller can gradually limit power before a BMS-initiated cutoff.
- Contact us if you need support for additional BMS types.
- BMS CAN messages are documented in the BMS CAN messages section.
Dynamic DC-side current limitation requires non-zero values for /driver/limiter/ibpos and /driver/limiter/ibneg.
Preparation
All BMS connections use CAN bus. Ensure matching CAN speeds between BMS and controller, and proper CAN termination.
Controllers use 1 Mbps CAN speed by default. To modify controller CAN speed, refer to: msgconf
Common BMS Settings
These settings apply to all BMS types.
/bms/bmstype
| Value | BMS name | Description |
|---|---|---|
| 0 | No BMS | BMS is not used. |
| 1 | siliXcon BMS | No additional configuration required. |
/bms/bmsopts
Only applicable when
bmstypeis non-zero.
| Value | Name | Description |
|---|---|---|
| 1 | STOP without BMS | BMS required for motor operation. Controller stops without BMS on CAN. |
| 2 | After first disconnect, STOP | Stop vehicle after BMS disconnection. Allows operation without BMS until first connection. Requires bit 0. |
| 4 | Disable limiters from BMS | Disable BMS limitations while maintaining BMS requirement for vehicle operation |
siliXcon BMS
bmstype = 1
SiliXcon BMS transmits all required information automatically without additional configuration.