Battery management apparatus and operating method thereof
A battery management apparatus according to an embodiment disclosed herein includes a microcontroller unit (MCU) for identifying whether a Modbus-communication connector is connected, identifying whether a controller area network (CAN)-communication connector is connected, and configuring a communication protocol based on identification results of the first identifying unit and the second identifying unit.
1 . A battery management apparatus, comprising:
a microcontroller unit (MCU) configured to:
identify whether a Modbus-communication connector is connected in a first identifying step;
identify whether a controller area network (CAN)-communication connector is connected in a second identifying step; and
configure a communication protocol based on identification results of the first identifying step and the second identifying step,
wherein, when both the Modbus-communication connector and the CAN-communication connector are connected, the communication protocol is automatically configured based on the CAN-communication connector, and
wherein, when the MCU determines that both the Modbus-communication connector and the CAN-communication connector are not connected, the MCU is configured to maintain the battery management apparatus in a standby state and check whether the Modbus-communication connector and the CAN-communication connector are connected at preset periods or in real-time.
2 . The battery management apparatus of claim 1 , wherein the MCU is configured to configure a Modbus-communication protocol when it is determined that the Modbus-communication connector is connected.
3 . The battery management apparatus of claim 1 , wherein the MCU is configured to configure a CAN-communication protocol when it is determined that the CAN-communication connector is connected.
4 . The battery management apparatus of claim 1 , wherein when the MCU determines that the CAN-communication connector is connected, an identifier (ID) is allocated in a daisy chain through CAN communication.
5 . The battery management apparatus of claim 4 , wherein when the MCU determines that the CAN-communication connector is not connected, the ID is allocated through Modbus-transmission control protocol (TCP).
6 . The battery management apparatus of claim 5 , wherein the MCU is configured to allocate the ID through the Modbus-transmission control protocol (TCP) using prestored command logic.
7 . The battery management apparatus of claim 4 , wherein the MCU allocates the ID after the battery management apparatus receives a wake-up signal through the CAN communication.
8 . The battery management apparatus of claim 1 , wherein the MCU is configured to determine that the Modbus-communication connector is connected based on whether power is supplied to an ethernet port.
9 . The battery management apparatus of claim 1 , wherein the MCU is configured to determine that the CAN-communication connector is connected based on whether power is received at a CAN port.
10 . An operating method of a battery management apparatus, the operating method comprising:
a first identifying operation of identifying whether a Modbus-communication connector is connected;
a second identifying operation of identifying whether a controller area network (CAN)-communication connector is connected; and
configuring a communication protocol based on identification results of the first identifying operation and the second identifying operation,
wherein, when both the Modbus-communication connector and the CAN-communication connector are connected, the communication protocol is automatically configured based on the CAN-communication connector, and
wherein, when both the Modbus-communication connector and the CAN-communication connector are not connected, the battery management apparatus is maintained in a standby state and a connection of the Modbus-communication connector and the CAN-communication connector are checked at preset periods or in real-time.
11 . The operating method of claim 10 , further comprising configuring a Modbus-communication protocol when the first identifying operation identifies that the Modbus-communication connector is connected.
12 . The operating method of claim 10 , further comprising configuring a CAN-communication protocol when the second identifying operation identifies that the CAN-communication connector is connected.
13 . The operating method of claim 10 , further comprising being allocated with an identifier (ID) in a daisy chain through CAN communication when the second identifying operation identifies that the CAN-communication connector is connected.
14 . The operating method of claim 13 , further comprising being allocated with the ID through Modbus-transmission control protocol (TCP) when the second identifying operation identifies that the CAN-communication connector is not connected.