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.
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
Select your BMS type using this parameter:
Value | Description |
---|---|
0 | No BMS |
1 | siliXcon BMS (all variants) |
10 | Fish BMS |
30 | Akuenergy BMS [Available on request] |
/bms/bmsopts
Only applicable when
bmstype
is non-zero.
Bit | Description |
---|---|
0 | BMS required for motor operation. Controller stops if BMS not present on CAN. |
1 | Stop vehicle after BMS disconnection. (Allows initial operation without BMS, but requires BMS once connected) Requires bit 0. |
2 | Disable BMS limitations. BMS can be required for vehicle operation, but its limitations won't be enforced |
siliXcon BMS
bmsopts
= 1
SiliXcon BMS transmits all required information automatically without additional configuration.