Management method of master and slave devices and management system of multi-battery module

Abstract

The invention provides a master-slave device management method and a multi-battery module management system. The method is applied between at least one master device and a plurality of slave devices, and the master device transmits door opening information to the plurality of slave devices through a bus, so that the door opening information received by the bus in the at least one slave device is set to be in a door opening state. Therefore, the master device transmits the command information to the plurality of slave devices through the bus, and the slave devices set to be in the open state can execute the command information. The battery management module can transmit door opening information and command information to a plurality of battery modules so as to achieve the purpose of appointing at least one battery module to execute the command information. Therefore, on the premise that the master equipment and the slave equipment are connected in the same hardware line and / or the slave equipment has the same ID, the master equipment can still specify the specific slave equipment to execute the specific command information.

Description

Technical Field

[0001] The present application relates to a management method of electronic devices, and more particularly to a management method of a master-slave device that is applied to multiple slave devices and has device identification. Background Art

[0002] In the existing master-slave architecture system, the master device needs a dedicated hardware line to electrically connect each slave device to transmit the control command of the master device to the slave device, or the slave devices need to have their own identification data according to the communication protocol. In terms of the controller area network communication protocol, the master device and all slave devices are connected by a bus, and each slave device needs to use a unique identifier (ID) as identification data. The control command of the master device requires the identification data of the slave device, and the corresponding slave device will execute the control command.

[0003] However, as the functions of electronic systems become more diverse and complex, more master devices are connected to more and more slave devices. However, the wiring space of hardware lines is limited, and the more hardware lines there are, the more difficult it is to wire them. In addition, the number of identification data of communication protocols is limited. For example, the identifier of the Controller Area Network (CAN or CAN bus) protocol is represented by 11 bits, which makes the expansion of the system more difficult. Summary of the invention

[0004] In view of the problems of the prior art, the purpose of the present application is to specify that a specific slave device is converted from the current normal state to the door-opening state (e.g., waiting for firmware update state) before transmitting command information through the master device, even if the slave device uses the same ID. Therefore, when the slave device in the door-opening state receives the command information, it will start to execute the command information; conversely, when the slave device in the non-door-opening state receives the command information, it will not execute the command information.

[0005] According to the purpose of the present application, a method for managing master-slave devices is provided, comprising the following steps: the master device configures a plurality of different identification information corresponding to a plurality of slave devices; the master device sends door opening information to the corresponding slave device on the bus according to the identification information; the slave device that receives the door opening information changes its own state to the door opening state, wherein the slave device's own state is preset to a normal state; the master device sends command information to a plurality of slave devices on the bus; the slave device in the door opening state executes the command information.

[0006] Alternatively, a slave device maintaining a normal state will ignore the command information.

[0007] Optionally, the command information is firmware update information, hardware diagnostic information, or software diagnostic information.

[0008] In addition, the present application further provides a management system for multiple battery modules, which includes: a bus, multiple battery modules and a management module. Multiple battery modules are connected to the bus, and the battery modules are in a normal state. When the battery modules receive the door opening information, their own state changes from the normal state to the door opening state. The battery modules in the door opening state execute the command information, and the battery modules in the normal state ignore the command information. The management module is connected to the bus, and the management module configures an identification information for each battery module via the bus. The management module generates the door opening information according to one of the multiple identification information, and sends it to the corresponding battery module via the bus. The management module sends the command information to the battery module in the door opening state via the bus.

[0009] Optionally, each battery module is provided with original identity information, and the management module ignores the original identity information.

[0010] Optionally, the normal state of the battery module includes a discharge state, a charge state and a battery dormant state.

[0011] Optionally, the command information is battery module firmware update information or battery module diagnostic information.

[0012] The beneficial effects that can be claimed in this application include:

[0013] (1) Before transmitting command information to the slave device, the master device first transmits door opening information to designate at least one slave device to be in the door opening state to the slave device, so that the designated slave device can be converted from any state to the door opening state, and when the slave device in the door opening state receives the command information, the slave device will start to execute the command information.

[0014] (2) Under the master-slave architecture of the present application, the slave device can be connected to the master device with the same hardware circuit, and the master device still has the effect of specifying any slave device to execute a command.

[0015] (3) Under the master-slave architecture of the present application, slave devices may have the same ID in any communication protocol, and the master device may also be able to specify any slave device to execute a command.

[0016] (4) A management system for multiple battery modules using the battery management module of the present application can expand the scalability of the current system without making excessive changes to the existing architecture, and can also save a lot of hardware circuit changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a block diagram of the management system of the master and slave devices of this application;

[0018] Figure 2 A flowchart of the method for managing master and slave devices of the present application;

[0019] Figure 3 A first block diagram of the management system of multiple battery modules of the present application;

[0020] Figure 4 This is a second block diagram of the management system of multiple battery modules of the present application. DETAILED DESCRIPTION

[0021] The embodiments of the present application will be further explained below with the help of the relevant drawings. As much as possible, the same reference numerals represent the same or similar components in the drawings and the specification. It is understood that the components not specifically shown in the drawings or described in the specification are known to those skilled in the art. Those skilled in the art may make various changes and modifications based on the contents of the present application.

[0022] Figure 1 This is a block diagram of the management system architecture of the master and slave devices of this application. Please refer to Figure 1 , the master-slave device management system 1 includes: a bus 10, a master device 12 and a plurality of slave devices 14. When the master-slave device management system 1 is started, the master device 12 identifies the plurality of electrically connected slave devices 14 through the bus 10, and the master device 12 configures different identification information to the plurality of slave devices 14. When it is necessary to specify one of the plurality of slave devices 14 to execute command information, the master device 12 first sends the door opening information to the corresponding slave device 14 according to the identification information, so that the corresponding slave device 14 changes its own state to the door opening state. Therefore, after the master device 12 transmits the command information to the slave device 14, the slave device 14 in the door opening state will execute the command information.

[0023] The door opening information is that the master device 12 instructs the slave device 14 to stop the current state (for example, stop the sleep state) and make the slave device 14 enter the door opening state.

[0024] The door open state is a state in which, after receiving the door open information from the device 14, the device is waiting to receive and execute command information (for example, executing a firmware update).

[0025] According to some implementations, since the door opening information has recorded the designated identification information, so that the corresponding slave device 14 changes its state to the door opening state, when the master device 12 transmits the door opening information, it can be transmitted to all electrically connected slave devices 14 at the same time or only to the slave device 14 corresponding to the designated identification information.

[0026] Furthermore, when some slave devices 14 receiving the door opening information have changed their own state to the door opening state, the master device 12 transmits the command information to all electrically connected slave devices 14 at the same time or only to the slave devices 14 corresponding to the designated identification information, so as to make the slave devices 14 in the door opening state execute the command information.

[0027] In addition, before the master device 12 transmits the door opening information, the master device 12 configures different identification information for all electrically connected slave devices 14. For example, the master device 12 sequentially assigns each slave device 14 with a serial number as identification information, and the serial number is a number from 0001 to 9999. The master device 12 randomly assigns each slave device 14 with a serial number, but each serial number is only assigned to one slave device 14.

[0028] Figure 2 This is a flowchart of the method for managing a master-slave device of the present application, and provides a method for managing a master-slave device. The method of this embodiment can be used Figure 1 The master-slave device management system 1 is used. The detailed process of the method of this embodiment is described below with the components in the master-slave device management system 1.

[0029] First, in step S210 , the master device 12 starts to operate.

[0030] In step S220, the master device 12 configures corresponding different identification information according to each connected slave device 14. For example, the master device 12 assigns identification information numbered 0001 and 0002 to the two electrically connected slave devices 14, respectively.

[0031] In step S230, the master device 12 transmits the door opening information to the corresponding slave device 14 according to the identification information, so as to change the state of the corresponding slave device 14 to the door opening state. For example, the master device 12 transmits the door opening information to each slave device 14, and the identification information of the door opening information is numbered 0001, so as to change the state of the slave device 14 numbered 0001 to the door opening state.

[0032] In step S240, the master device 12 transmits command information to the slave devices 14. For example, the master device 12 transmits command information to each slave device 14. The command information may be, for example, a diagnostic instruction or firmware update information.

[0033] In step S250, the slave device 14 that receives the command information is in the door-opening state. If yes, the process jumps to step S262. Otherwise, if the slave device 14 is not in the door-opening state, the process jumps to step S264. For example, the slave device 14 numbered 0001 is converted to the door-opening state according to the door-opening information, and the slave device 14 numbered 0002 continues to maintain the original state.

[0034] In step S262, the slave device 14 in the door open state will execute the command information. Specifically, when the slave device 14 numbered 0001 receives the door open information provided by the master device 12, it will be set to the door open state and stop the current execution state in real time to execute the command information sent by the master device 12.

[0035] In step S264, the slave device 14 that is not in the door-opening state does not execute the command information. For example, since the battery module 34 numbered 0002 is not in the door-opening state and continues to maintain the normal state, the slave device 14 numbered 0002 will not execute the subsequent received command information.

[0036] Figure 3 This is a first architecture block diagram of the multi-battery system of the present application. Figure 3 Multi-battery system 3 can be applied Figure 2 A method for managing master and slave devices. In the present embodiment, the master device 12 may be a management module 32, and the slave device 14 may be a battery module 34. The management module 32 is connected to the plurality of battery modules 34 via a bus 30. When the management module 32 is connected to the plurality of battery modules 34 via bus 30 signals, the management module 32 will configure different identification information for each battery module 34. When the management module 32 wishes to instruct at least one of the plurality of battery modules 34 to execute command information, the management module 32 transmits door opening information to at least one of the plurality of battery modules 34 via the bus 30, so that at least one of the plurality of battery modules 34 is set to an open door state waiting for the execution of the specified command information. Furthermore, the management module 32 transmits command information to at least one of the plurality of battery modules 34 via the bus 30, so that the battery module 34 in the open door state executes the command information.

[0037] The management system 3 of multiple battery modules in this embodiment can be applied to the existing battery management system (Battery Management System, BMS). Under the architecture of the battery management system, at least one battery cell, a supporting shell (Holder) and a conductive plate (Connecting Plate) constitute a battery pack (Battery Pack); at least one battery pack, a circuit board and a carrier constitute a battery module. Each battery pack will be monitored and sampled by a battery monitoring unit (Battery Monitoring Unit, BMU). Each battery module will be controlled by a battery control unit (Battery Control Unit, BCU). Therefore, in this embodiment, the management module 32 can be set in the battery control unit to transmit the door opening information to the corresponding battery module 34.

[0038] For example, the management system 3 of multiple battery modules is applied to an electric motorcycle or an electric bicycle. The management module 32 is set in the meter device of the electric motorcycle or the electric bicycle. The multiple battery modules are the main battery and the auxiliary battery of the electric motorcycle or the electric bicycle. Specifically, the management module 32 is set in the meter device of the electric bicycle, and the door opening information is transmitted to the main battery module 42 or the auxiliary battery module 44 through the management module 32.

[0039] Figure 4 This is a second architecture block diagram of the multi-battery system of the present application. Figure 4 The multi-battery system 3 is Figure 3 Another implementation aspect. In this embodiment, one of the multiple battery modules in the management system 3 of multiple battery modules is used as the main battery module 42 for transmitting door opening information, and the remaining battery modules will be used as auxiliary battery modules 44. And the main battery module 42 must be electrically connected to all auxiliary battery modules 44. Therefore, the management module 32 is set in the main battery module 42, and the main battery module 42 uses the management module 32 to transmit the door opening information and command information to the auxiliary battery module 44. Specifically, the management module 32 is set in the header device of the electric bicycle, and the door opening information is transmitted to the main battery module 42 through the management module 32, and the door opening information is transmitted to the auxiliary battery module 44 (usually a backup battery) through the main battery module 42. Therefore, the door opening information provided by the header device of the electric bicycle can change the main battery module 42 or the auxiliary battery module 44 to the door opening state.

[0040] According to the above implementation, the management module 32 can set corresponding identification information for each electrically connected battery module 34. The above identification information can be set according to the default parameters of the management module 32, for example: the identification information is statically coded or dynamically coded.

[0041] According to some implementation aspects, when the management module 32 of the management system 3 of multiple battery modules is used to set the identification information, the following implementation aspects may also be included.

[0042] Static coding: The battery modules 34 are numbered according to existing and fixed information, for example: (1) the battery modules 34 installed in a specific battery slot are numbered according to the existing battery slot; (2) the battery modules 34 are numbered according to the batch number (Lot#) or item number (Cat#); (3) the battery modules 34 are numbered according to the microcontroller identification number that is paired with the battery modules 34, for example, the microcontroller numbers the battery modules 34 by serial number.

[0043] Dynamic coding: The battery modules 34 are numbered according to the change information, for example: (1) the battery modules 34 are numbered according to their health status as determined by the battery management system; (2) the battery modules 34 are numbered according to their firmware versions; (3) the battery modules 34 are numbered according to their usage time.

[0044] Furthermore, the management module 32 gives each battery module 34 unique identification information, which can be executed in the initialization process each time the management system 3 of multiple battery modules is turned on. Alternatively, the management module 32 can have a storage function. When the management module 32 confirms that the electrically connected battery modules 34 have not been changed, the management module 32 uses the stored identification information corresponding to each battery module 34 as a medium for identifying each battery module 34.

[0045] When the management module 32 needs to designate one of the multiple battery modules 34 to execute a specific command information, the management module 32 will write the identification information of the designated execution command information into the door opening information and transmit it to all battery modules 34 or the battery modules 34 corresponding to the identification information, so that the corresponding battery module 34 changes its own state to the door opening state. For example, the management module 32 can be connected to an external computer device by signal to receive information specifying the update of a specific battery module 34 (e.g., information for updating the firmware of the battery module 34 numbered 0001) in a wired or wireless manner. Therefore, the management module 32 sets multiple identification information in advance to specify that a specific battery module 34 needs to be updated with a door opening command.

[0046] According to some implementations, based on the management module 32 setting different identification information for each battery module 34, the management module 32 can further transmit the corresponding identification information to the corresponding battery module 34, so that each battery module 34 records its own identification information. Therefore, when the battery module 34 receives the door opening information, it can determine whether the identification information in the door opening information matches its own identification information, and when it matches, the battery module 34 enters the door opening state.

[0047] According to another embodiment, the door opening information sent by the management module 32 may record the identification information of one or more battery modules 34. And the management module 32 may transmit the door opening information recording the specified identification information to all the battery modules 34 connected by the signal. For example, the management module 32 configures the battery module 34 with the specified number 0001 as the door opening state, and transmits the door opening information to all the battery modules 34. Alternatively, the management module 32 only transmits the door opening information with specific identification information to the corresponding battery module 34. For example, the management module 32 only transmits the door opening information to the battery module 34 with the number 0001.

[0048] Therefore, when the battery module 34 receives the door opening information, the state that may be included may be, for example:

[0049] (1) The battery module 34 with number 0001 identifies whether the identification information of the door opening information includes the number 0001. If yes, the battery module 34 with number 0001 will change to a door opening state to wait for the execution of the command information subsequently transmitted by the management module 32.

[0050] (2) The battery module 34 with number 0002 receives the identification information of the door opening information as number 0001. Since the battery module 34 with identification information of number 0002 is not identified in the door opening information, the battery module 34 with number 0002 is maintained in the normal state. The battery module 34 in the normal state will not execute the command information subsequently transmitted by the management module 32.

[0051] According to the above implementation, the present application allows the battery module 34 to use the bus to connect to the management module 32, that is, there is no need to design dedicated lines individually, even if multiple battery modules 34 have the same original identity information, such as the original identity information is the identifier of the controller local area network communication protocol, because these original identity information are ignored by the master device, the master device uses the identification information to change the state of the slave device itself. Therefore, whether the management module 32 transmits the door opening information or the command information, it can be transmitted to all electrically connected battery modules 34, but only the battery module 34 in the door opening state will execute the command information.

[0052] In summary, the beneficial effects of the management module 32 of the management system 3 of multiple battery modules applied in the present application include:

[0053] (1) It is not necessary to set up a dedicated line connection management module 32 for each battery module 34 .

[0054] (2) Under the same communication protocol architecture, such as a controller area network, each battery module 34 does not need to individually occupy an identifier in the communication protocol.

[0055] (3) The management module 32 is used to give each battery module 34 unique (different) identification information, and the identification information is stored in the management module 32 or an electrically connected electronic component (such as a memory). Therefore, the management module 32 uses the known identification information of each battery module 34 to specify that the corresponding battery module 34 changes the current state to the open state.

[0056] The above is only an example to illustrate the preferred implementation mode of the present application, and is not intended to limit the scope of implementation. All simple replacements and equivalent changes made according to the claims and description of the present application are within the protection scope of the present application.

Claims

1. A method for managing master and slave devices, characterized in that: The following steps are involved: The master device is configured with different identification information corresponding to the plurality of slave devices; The master device sends the door opening information to the corresponding slave device on the bus according to the identification information; The slave device receiving the door opening information changes its own state to the door opening state, wherein the own state of the slave device is preset to a normal state; The master device sends command information to the plurality of slave devices on the bus; and The slave device in the door-open state executes the command information.

2. The method for managing master and slave devices according to claim 1, characterized in that: The slave device maintaining the normal state will ignore the command information.

3. The method for managing master and slave devices according to claim 1, characterized in that: The command information is firmware update information, hardware diagnosis information or software diagnosis information.

4. A management system for multiple battery modules, characterized in that: include: One bus; A plurality of battery modules are connected to the bus, the state of the battery modules themselves is a normal state, and when the battery modules receive the door opening information, the state of the battery modules themselves changes from the normal state to the door opening state, the battery modules in the door opening state execute the command information, and the battery modules maintaining the normal state ignore the command information; as well as A management module is connected to the bus. The management module configures an identification information for each battery module via the bus. The management module generates the door opening information according to one of the multiple identification information and sends it to the corresponding battery module via the bus. The management module sends the command information to the battery module in the door opening state via the bus.

5. The management system for multiple battery modules according to claim 4, characterized in that: Each of the battery modules is provided with original identity information, and the management module ignores the original identity information.

6. The management system for multiple battery modules according to claim 4, characterized in that: The normal state of the battery module includes a discharging state, a charging state, and a battery dormant state.

7. The management system for multiple battery modules according to claim 4, characterized in that: The command information is battery module firmware update information or battery module diagnostic information.

Images