WO2022147618A1

WO2022147618A1 - Redundant power over data wire network system for electric energy source management

Info

Publication number: WO2022147618A1
Application number: PCT/CA2022/050012
Authority: WO
Inventors: Alexandre Gourari; John Joseph Wojtkowicz; David Stubbs
Original assignee: Neutron Automotive Controls Inc.
Priority date: 2021-01-08
Filing date: 2022-01-06
Publication date: 2022-07-14

Abstract

Vehicles and power banks use electric energy source management systems to manage sets of electric energy source (EES) devices. Examples of EES devices include battery cells, fuel cells, solar cells and electric generators. An EES management system includes EES nodes and a command node that are connected together with electrically conductive cables in a daisy chain ring topology to provide seamless and redundant communication. The nodes also supply power to each other over the data lines. A command node or an EES node can have multiple sources of electrical power from the network of nodes, which provides redundant power supply. In the event of breakage or failure in the network, the recipient EES node still receives the message with no data delay and with no data loss due to redundant communication and redundant power supply.

Description

REDUNDANT POWER OVER DATA WIRE NETWORK SYSTEM FOR ELECTRIC ENERGY SOURCE MANAGEMENT

CROSS-REFERENCE TO RELATED APPLICATION

[001] This application claims priority to United States Provisional Patent Application No. 63/135,308, filed on January 8, 2021 , and titled “Redundant Power Over Data Wire Network System For Electric Energy Source Management”, the entire contents of which are herein incorporated by reference.

TECHNICAL FIELD

[002] The following generally relates to a redundant power over data wire network system, and related devices, for electric energy source management.

DESCRIPTION OF THE RELATED ART

[003] Vehicles (e.g., trucks, buses, cars, marine vehicles, aircraft, etc.) are becoming more electrically driven. For example, electric motors are being used as primary drivers or secondary drivers for motive force instead of combustion engines. This requires a larger battery system to provide electrical power. Larger battery systems typically include many battery cells that are connected together to provide the current draw and voltage levels used by motors and other electrical devices (e.g., heating, cooling, braking, actuators, etc.).

Battery management systems are used to manage the large number of batteries. These battery management systems are also used in power or utility grids, such as for power generators, power banks, buildings and facilities.

[004] In vehicles and other battery applications mentioned above, sets of battery cells are managed by battery nodes. These battery nodes are managed by a command node, sometimes called an electronic control unit (ECU) or host node. Battery nodes and the host node are in data communication together via a wired network, typically copper or some other electrical conductor. The nodes require electrical power to operate. It is herein recognized that if power to a node is disrupted (e.g., power loss), or if a wire breaks, or if an intermediate communication component is damaged, then a battery node and its corresponding set of battery cells are cut off from the wired network. This could cause the operation of a given node to fail, and could also cause the overall electric energy management system to fail.

[005] Similar problems of are experienced when coordinating other types of electric energy sources. For example, electric generators, fuel cells, solar cells, etc. are used in vehicles and electric energy management grids. [006] It is therefore desirable to herein provide an electric energy management system that is safer and maintains responsiveness even during technical failures. BRIEF DESCRIPTION OF THE DRAWINGS [007] Embodiments will now be described by way of example only with reference to the appended drawings wherein: [008] FIG. 1 A is a schematic diagram of a redundant electric energy source management system, according to an example embodiment. [009] FIG. 1 B is a schematic diagram of a redundant battery management system, according to an example embodiment. [0010] FIG. 1C is a schematic diagram of a redundant fuel cell management system, according to an example embodiment. [0011] FIG. 1D is a schematic diagram of a redundant solar cell management system, according to an example embodiment. [0012] FIG. 2A is a schematic diagram of a redundant electric energy source management system, including the redundancy modules of the nodes sending or receiving power over the data lines, according to an example embodiment. [0013] FIG. 2B is a schematic diagram of a redundant electric energy source management system, including one or more electric energy source nodes distributing power, according to another example embodiment. [0014] FIG. 3A is a schematic diagram of an electric energy source node in a redundant electric energy source management system, and that facilitates at least receiving power over data lines, according to an example embodiment. [0015] FIG. 3B is a schematic diagram of an electric energy source node similar to the electric energy source node shown in FIG. 3A, and further receiving power from a locally connected electric energy source, according to an example embodiment. [0016] FIG. 3C is a schematic diagram of an electric energy source node in a redundancy electric energy source management system, and that facilitates at least obtaining power from the connected electric energy source and then transmitting power over data lines, according to an example embodiment. [0017] FIG. 3D is a schematic diagram of an electric energy source node in a redundancy electric energy source management system that facilitates obtaining power from the connected electric energy source and from one of the two data ports, as well as transmitting power over the other one of the two data ports, according to an example embodiment. [0018] FIG. 4A is a schematic diagram of a command node in a redundant electric energy source management system, and that facilitates transmitting power over data lines, according to an example embodiment. [0019] FIG. 4B is a schematic diagram of a command node in a redundant electric energy source management system, and that facilitates receiving power over data lines, according to an example embodiment. [0020] FIG. 5 is a schematic diagram of processor system for a redundancy module configured for a software Ethernet architecture, according to an example embodiment. [0021] FIG. 6 is a schematic diagram of processor system for a redundancy module configured for a hardware Ethernet architecture, according to an example embodiment. [0022] FIG. 7 is a schematic diagram of processor system for a redundancy module configured for a software non-Ethernet architecture, according to an example embodiment. [0023] FIG. 8 is a schematic diagram of two daisy chain loops connected together using a quad-port redundancy module, forming a redundant electric energy source management system, according to an example embodiment. [0024] FIG. 9 is a schematic diagram of a quad-port redundancy module that facilitates power over data lines, according to an example embodiment. [0025] FIG. 10 is a schematic of a quad-port processor system used in a quad-port redundancy module, including components for a software Ethernet architecture, according to an example embodiment. [0026] FIG. 11 is a schematic of a quad-port processor system used in a quad-port redundancy module, including components for a hardware Ethernet architecture, according to an example embodiment. [0027] FIG. 12 is a schematic diagram of a vehicle that includes an electric energy source management system, according to an example embodiment. [0028] FIG. 13 is a schematic diagram of a power bank that includes an electric energy source management system, according to an example embodiment. DETAILED DESCRIPTION

[0029] It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the example embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the example embodiments described herein. Also, the description is not to be considered as limiting the scope of the example embodiments described herein.

[0030] Within this specification, different structural entities (which may variously be referred to as “nodes”, “units”, “circuits”, “systems”, “processors”, “module”, “interface”, other components, etc.) may be described or claimed as “configured” to perform one or more tasks or operations. This formulation - [entity] configured to [perform one or more tasks] - is used herein to refer to structure (i.e., something physical, such as an electronic circuit).

More specifically, this formulation is used to indicate that this structure is arranged to perform one or more tasks during operation. A structure can be said to be “configured to” perform some task even if the structure is not currently being operated. A “processor configured to generate and transmit a message via a data port” is intended to cover, for example, an integrated circuit that has circuitry that performs this function during operation, even if the integrated circuit in question is not currently being used (e.g., a power supply is not powering it). Thus, an entity described or recited “configured to” perform some task refers to something physical, such as a device, circuit, memory storing program instructions executable to implement the task, etc. This phrase is not used herein to refer to something intangible. Thus, the “configured to” construct is not used herein refer to a software entity, such as an application programming interface (API).

[0031] The term “configured to” is not intended to mean “configurable to.” An unprogrammed Field Programmable Gate Array (FPGA), for example, would not be considered to be “configured to” execute some specific operation, although it may be “configurable to” perform that specific operation and may be “configured to” execute that specific function after programming.

[0032] Reciting in the appended claims that a structure is “configured to” perform one or more tasks is intended not to be interpreted as having means-plus-function elements. [0033] Throughout the specification and the claims, the following terms take at least the meanings explicitly associated herein, unless the context clearly dictates otherwise. The term "or" is intended to mean an inclusive "or." Further, the terms "a," "an," and "the" are intended to mean one or more unless specified otherwise or clear from the context to be directed to a singular form.

[0034] In this specification, numerous specific details have been set forth. It is to be understood, however, that implementations of the disclosed technology may be practiced without these specific details. In other instances, well-known methods, structures, and techniques have not been shown in detail in order not to obscure an understanding of this description. References to “for example”, "some examples," "other examples," "one example," "an example," "various examples," "one embodiment," "an embodiment," "some embodiments," "example embodiment," "various embodiments," "one implementation," "an implementation," "example implementation," "various implementations," "some implementations," etc., indicate that the implementation(s) of the disclosed technology so described may include a particular feature, structure, or characteristic, but not every implementation necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrases "in one example," "in one embodiment," or "in one implementation" does not necessarily refer to the same example, embodiment, or implementation, although it may.

[0035] As used herein, unless otherwise specified the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0036] It is herein recognized that many of the communication systems in energy source management systems (e.g., battery cell management systems, fuel cell management systems, solar cell management systems, other energy cells, etc.) connect nodes together using wiring.

[0037] It is also herein recognized that nodes in an electric energy source management system, such as a battery management system, require electric power to control the draw of electric power, or to control the charging of electric power, or to monitor an electric energy source, or a combination thereof. A loss in power supply to a given node in such a management system would typically cause the given node to fail, and could even also cause the overall management system to fail. [0038] A failure in power to a given node would result in delays in data transmission and processing, which can affect an electric energy source management system’s operation, especially when reacting in emergency situations where timing can be critical. For example, breakage in wiring or damage in communication devices can delay data transmission and delay processing of data.

[0039] It is also herein recognized that US Patent Application Publication no. 2019/0006723 to Martin et al. describes a daisy chain network of nodes for a battery management system. However, its network does not provide power redundancy.

[0040] US Patent no. 9,182,438 to Martin et al. describes a battery management system with a host connected to each client in a unidirectional (i.e. one direction) daisy-chain loop that begins and ends, at the host. The host transmits all commands to a first client on a daisy-chain loop, and each client retransmits all data it receives on a byte-to-byte basis. The connections include five wires: a first serial data wire, a second serial data wire for redundancy, an isolated power wire, an isolated ground wire, and a fault wire. Each client battery module can generate a fault signal that is sent over the fault wire. Electronics, such as the processor and the ASIC, on-board a client battery module are powered by energy available from the associated battery module, while interface elements on the client battery module are powered from the host using the power wire and ground wire. Each of the client battery modules have their interface elements connected in a parallel circuit configuration off the main power wire and the ground wire. For example, for n=8 clients, there are 8 parallel circuits stemming off the power wire and the ground wire.

[0041] The configuration in US Patent no. 9,182,438 requires many wires. Furthermore, breakage in a power wire connecting to a client battery module would stop the client battery module from interfacing entirely with the daisy chain loop. Furthermore, a breakage in the power wire that forms the main daisy chain loop would make all the client battery modules inoperable, as all the respective interface elements would be without power. It is also herein recognized that if a client battery module’s associated battery cannot provide power (e.g., insufficient power, damaged battery, sudden power drops, etc.), then the processor and the ASIC of that client battery module are without power.

[0042] It is also herein recognized that existing communication networks typically have 50 milliseconds to 30 seconds to recover from a failure or breakage. It is further herein recognized that reducing this delay or providing seamless operation, even in the event of a failure or breakage, improves safety and operational responsiveness.

[0043] It also herein recognized that more redundancy of power distribution to energy nodes and command nodes in an electrical energy source management system is better. Vehicles that use batteries or fuel cells, or both, are mobile, and it is desirable to operate a battery cell management system, or fuel cell management system, or both, in the field with little maintenance even if damaged. Therefore, a safe and robust electric energy source management system is desirable for vehicles.

[0044] The same issues arise for generator systems and power banks, which can sometimes operate in environmentally harsh and remote conditions. Generator systems and power banks can be damaged during shipping, setup and over time due to environmental events (e.g., accidents, weather, impacts from other objects, etc.). Therefore, a safe and robust electric energy source management system is desirable for generator systems and power banks.

[0045] Therefore, in an example embodiment, an electric energy source management system provides redundant power over the same data wires that transmit data to energy source nodes so they can remain operational in the event of power interruption. In a further example aspect, the electric energy source management system supplies redundant power and redundant data to energy source nodes, which enables seamless operation should a wire break or a node fail. In a further example aspect, electric energy source management system provides redundant power amongst nodes using a daisy chain network of nodes, where each node includes two independent data ports that receive or transmit power, or both.

[0046] It is also herein noted that supplying power over data wires allows for reducing the number of wires and as a result make vehicles lighter. For example, this saves fuel or energy. It is recognized that the weight of a wiring harness in a modern car is a significant contributor to the weight of the car as a whole.

[0047] Turning to FIG. 1A, an example of an electric energy source management system 100 is provided, which includes electric energy source 101a connected to an energy source node 102a. Multiple electric energy source nodes 102a, 102b, 102n are connected together in an electrical communication network with a command node 106, in a daisy chain ring topology. In an example aspect, electric energy source nodes 102a, 102b, 102n are respectively connected to a set of electric energy sources 101a, 101b, 101 n.

[0048] In an example aspect, the electric energy sources in the system include: battery cells, fuel cells, solar cells, electric generators, or a combination thereof. It will be appreciated that battery cells, fuel cells and solar cells are typical examples of energy cells. Electric energy sources, for example, generate electricity or store electricity, or both. Vehicles, power grids, and power banks typically include battery cells. In some example embodiments, vehicles, power grids, and power banks include an electric energy source management system that combines battery cells with one or more other types of electric energy sources (e.g., fuel cells, solar cells, electric generator, etc.).

[0049] Electric energy source node 102a includes a redundancy module 104a and an electric energy source interface 103a. The redundancy module 104a provides data processing and redundant communication in the electrical communication network. In an example aspect, the redundancy module 104a also includes power systems to transmit the power from the electric energy source 101a over data wires C1 or C2, or both. In another example aspect, the redundancy module 104a also includes power systems to receive electrical power over the data wires C1 or C2, or both. The electric energy source interface 103a connects to the electric energy source 101a.

[0050] Similarly, electric energy source node 102b includes a redundancy module 104b and electric energy source interface 103b; and electric energy source node 102n includes a redundancy module 104n and electric energy source interface 103n.

[0051] The term “electric energy source” is herein also referred to as EES.

[0052] The EES interface, for example, includes circuitry that connects to the EES.

[0053] The command node 106 includes a redundancy module 104e and an Electronic Control Unit (ECU) 105. In other example embodiments, the command node includes a Battery Control Unit (BCU), and the redundancy module 104e is instead connected to the BCU.

[0054] In the example shown, a data cable C1 connects between the redundancy module 104a of the EES node 102a and the redundancy module 104e of the command node 106. Another data cable C2 connects between the redundancy module 104a of the EES node 102a and the redundancy module 104b of the EES node 102b. Another data cable C3 connects between the redundancy module 104b of the EES node 102b and the redundancy module 104n of the EES node 102n. Another data cable C4 connects between the redundancy module 104n of the EES node 102n and the redundancy module 104e of the command node 106. Data is transmitted in both directions at the same time in a given cable. The cables are electrically conductive data wires, and electrical power and data are transmitted together over the same wires.

[0055] In an example aspect, each cable includes at least two electrical wires to transfer data. It will be appreciated that different interfaces have different numbers of wires (e.g., more than two wires).

[0056] The data cables C1 , C2, C3, C4 also transfer power between nodes in the daisy chain loop. A redundancy module in a given node filters out the data from the power. [0057] In an example embodiment, a given node can receive power from different sources in order to remain operational, or provide operating power to a neighboring node. In an example embodiment, a given node is configured to switch between different modes, including two or more of: receiving power over a data cable; and transmitting power over a data cable.

[0058] In an example embodiment, an EES node receives power over one or both data cables.

[0059] In another example embodiment, an EES node receives power from any one or more of: a first data cable connected to the EES node, a second data cable connected to the EES node, and an electric energy source connected to the EES node.

[0060] In another example embodiment, an EES node obtains power from its electric energy source, and transmits the power over one or both data cables.

[0061] In another example embodiment, an EES node obtains power from its EES and transmits power over one or both data wires, and can switch to a mode to receive data over one or both data lines. For example, an EES node detects that no electrical power is coming from a given data port from a neighboring node, and, in response, initializes transmission of electrical power to the neighboring node. In another example, an EES node detects that its own electrical power source is failing, and activates a receiving mode to receive electrical power from a neighboring node.

[0062] Data is transmitted over the same data cables. In an example aspect, the data cable transfers data at over 10 Megabytes per second (Mbps). In another example aspect, the cable transfers data at approximately 100 Mbps or more. In another example aspect, the cable transfers data at approximately 1 Gigabyte per second (Gbps) or more. In another example aspect, the cable transfers data at approximately 10 Gbps or more.

[0063] In an example aspect, the cables are electrically conductive Ethernet cables. It will be appreciated that other types of electrically conductive wires can be used for data transmission.

[0064] The EES node 102a processes data in relation to the EES 101a, and monitors operational parameters of the EES 101a.

[0065] Examples of operational parameters for battery cells include the status of voltages, currents and temperatures with the battery cells, state of charge (SOC), and state of health (SOH). The EES node also monitors its own power supply, which may be obtained from the EES 101 a, or via a data wire C1 or C2, or a combination thereof. Other operations include monitoring and recording history logs of when and how many times the battery cells were charged and discharged, temperature profiles, cooling operations, heating operations, etc. The battery node may also isolate the battery cells, for example, in cases of emergency or for based on other conditions. It will be appreciated that the operational parameters will vary according to the type of EES.

[0066] It will be appreciated that the EES node 102a can carry various monitoring and control operations in relation to the EES 101a. In an example aspect, the EES node 102a also sends status messages and warning messages to other nodes in the EES management system 100. In an example aspect, the EES node 102a also receives command messages and executes operations based on the command messages. In another example aspect, the EES node 102a also generates and sends command messages to other nodes in the EES management system 100. Other currently known and future known operations performed by EES nodes are applicable to the principles described herein. It will be appreciated that the other EES nodes 102b, 102n operate in a similar manner to EES node 102a.

[0067] The command node 106 receives data from the EES nodes in the vehicle system or the EES power grid. The command node also provides commands to the EES nodes.

For example, the command messages include one or more of adjusting current settings, adjusting voltage settings, adjusting charge settings, adjusting discharge settings, adjusting load balancing, requesting status data, etc. In an example aspect, command messages sent by the command node also include one or more of: activating cooling operations, activating heating operations, activating isolation switches to isolate or connect EES devices, etc. Other currently known and future known operations performed by a command node are applicable to the principles described herein.

[0068] The command node 106, for example, is also in data communication (e.g., wired or wireless) with an external data source 107. The external data source can be another device, another sensor, another ECU, another network, a server system, etc.

[0069] In an example embodiment of the EES management system, an EES node 102a can receive power from one or more of the corresponding EES 101a, from the command node 106 via C1 , or from the EES node 102b via C2. If one of the three power sources fail, it can receive power from the other two power sources. In this way, the EES node 102a remains operational. In other words, the nodes in the EES management system 100 support each other to provide power, should one of the nodes experience a power failure.

[0070] In another example aspect of this EES management system, data travels in both directions at the same time across the electrical communication network amongst the nodes. [0071] For example, when the command node 106 sends a command message to an EES node 102b, the command node duplicates the command message and then sends one instance of the command message along the cable C1 and sends the other instance of the command message the cable C4 at the same time, or at approximately the same time. The command message travels along C1 ; then to the EES node 101a, via the redundancy module 104a; then travels along C2; then arrives at the EES node 102b. The command message also travels along C4; then to the EES node 102n, via the redundancy module 104n; then travels along C3; then arrives at the EES node 102b. In this way, the redundancy module 104b of the EES node 102b, under nominal redundancy operations, receives the command message from both directions at approximately the same time, or within some expected time range of each other. If one of the cables or connections is broken or damaged (e.g., C1), then the EES node 102b still receives the command message along another path (e.g., C4 and C3) with no loss of data and with no time delay. Similarly, if one of the intermediate EES nodes is damaged (e.g., EES node 102a’s redundancy module 104a is damaged), then the EES node 102b still receives the command message along another path (e.g., C4 and C3) with no loss of data and with no time delay.

[0072] In another example aspect, a message from a given EES node is transmitted by its redundancy module in both directions at the same time, or approximately the same time, under nominal conditions. For example, EES node 102b, via its redundancy module 104b, transmits a message to the command node 106. The redundancy module 104b duplicates the message, and then transmits one instance of the message along the cable C2 and transmits another instance of the message along the cable C3 at the same time, or approximately at the same time. Under nominal conditions, the command node 106 receives two instances of the message originating from the EES node 102b, via the cable C1 and the cable C4. The message instances from both directions are received at the command node 106 at approximately the same time, or within some expected time range of each other, under nominal conditions. However, if a cable or connection fails, then the command node still receives at least one instance of the message without any loss of data and without any time delay. Similarly, if an intermediate node is damaged, then the command node still receives at least one instance of the message without any loss of data and without any time delay.

[0073] In an example aspect, the redundancy module in the daisy chain ring topology provides 0 microsecond (ps) recovery time, no data delay, and no data loss (e.g., 0% data packet loss) in the event of a Network or node connection failure.

[0074] In another example aspect, each node on the electrical communication network has at least two data ports that are inserted into the network with a ring topology. In another example aspect, data packets (e.g., messages or portions of messages) are transmitted by a sender node in both directions of the ring at the same time, which is also herein called packet duplication. Intermediate nodes in the ring forward the data packets in the ring. In another example aspect, the receiver node removes the packets from the ring. In another example aspect, the sender node removes the packets travelled the whole ring before coming back to the sender (e.g., also called packet filtering). Under nominal conditions (e.g., no errors or failures), the destination node receives two copies of the packet and discards the duplicate.

[0075] In another example aspect, a cable break or a port failure at a node is detected, while data still is transmitted with no loss and with no delay in the EES management system 100. In another example aspect, EES nodes emit comm-check or status packets (e.g., messages), which include data about the port status; these status packets are used to update configuration information and detect broken links.

[0076] In another example aspect, the EES nodes and the one or more command nodes operate using a cut-through mode. For example, a given intermediate node begins transmitting a pass-through packet even before the whole packet is received, once it has been detected that destination address is not the given intermediate node address, therefore the packet is to be forwarded. In other words, this type of dynamic first-in-first-out processing, allows data to be more quickly transported through the electrical communication network.

[0077] In another example aspect, the EES nodes and the one or more command nodes operate using a store-and-forward mode. For example, a given intermediate node receives and stores the whole packet, defines the destination address, and then determines whether to forward the packet or process the packet, or both.

[0078] It will be appreciated the nodes in the network can operate using one or more modes.

[0079] It will be appreciated that although three EES nodes 102a, 102b, 102n are shown in FIG. 1 A, there may be more or less EES nodes in implementation. Furthermore, other types of nodes (e.g., nodes for sensors, nodes for actuator control, etc.) may be connected to the same network for EES management systems.

[0080] FIGs. 1 B, 1 C and 1 D show different examples of an EES management system, which vary based on the one or more types of electric energy source.

[0081] Turning to FIG. 1B, an example embodiment of a battery management system 110 is shown. The battery nodes 112a, 112b, 112n respectively include battery cell interfaces 113a, 113b, 113n. The battery cell interfaces are respectively connected to the battery cells 111a, 111b, 111 n. Each of the battery nodes include a redundancy module.

The battery nodes are arranged in a daisy chain configuration and are in communication with a command node 106. The electrical power from the battery cells can be used to power a battery node, and the electrical power can be distributed with the data over the same data wires to power a neighboring battery node.

[0082] Turning to FIG. 1C, an example embodiment of a fuel cell management system 120 is shown. The system 120 includes a fuel cell node 122, which includes a fuel cell interface 123, which in turn is connected to a fuel cell stack 121. The system 120 also includes a fuel supply node 125, which includes a fuel supply interface 126. The fuel supply interface 126 is connected to the fuel supply (or fuel supplies) system 124. For example, the fuel supply system 124 includes the valves and pump system that control the supply of fuel and air to the fuel cell stack 121. The system 120 also includes a battery node 128. The battery node 128 includes a battery cell interface 129. The battery node 128, via the battery cell interface 129, is connected to the battery cells 127. It will be appreciated that there may be multiple fuel cell nodes respectively managing multiple fuel cell stacks. It will also be appreciated there may be multiple fuel supply nodes respectively managing multiple fuel supply systems. It will also be appreciated there may be multiple battery nodes respectively managing multiple sets of battery cells. Each of the nodes in the systems 120 includes redundancy module. In an example aspect, the command node 106 provides data and electrical power over C1 to the fuel cell node 122. The fuel cell node 122 can also receive power from its own fuel cell stack 121. Should there be a failure in the power supply from the fuel cell stack, the fuel cell node will still receive electrical power to operate from the command node 106. The battery node 128 transfers the electrical power from the battery cells 127 to provide electrical power and data over the same data wire in C3 to the fuel supply node 125. ,

[0083] Turning to FIG. 1D, an example embodiment of a solar cell management system 130 is shown. The system 130 includes solar cell nodes 132a, 132b, which respectively include solar cell interfaces 133a, 133b. One or more solar panels 131a are connected to the solar cell interface 133a, and one or more solar panels 131b are connected to the solar cell interface 133b. The system 130 further includes a battery node 135 that is connected to a set of battery cells 134. In particular, the battery node 135 includes a battery cell interface 136 which connects to the battery cells 134. It will be appreciated there may be multiple battery nodes respectively managing multiple sets of battery cells. The solar cell nodes, the battery cell nodes, and the command node in the system 130 each include a redundancy module. It will be appreciated that electrical power can be transmitted amongst the nodes using the data cables C1 , C2, C3, C4.

[0084] It will be appreciated that the configuration of the EES management system may vary based on the type of device used to generate the electricity or store the electricity, or both.

[0085] Turning to FIG. 2A, an example embodiment of an EES management system is provided that transmits power to nodes over the electrical communication network. The EES management system includes two EES nodes 201 a, 201 b and a command node 202 connected using electrically conductive data cables in a daisy ring configuration. Each node includes at least two line connectors LC1 , LC2 and the cables transmit data and power between the nodes. The command node 202 is connected to an external power supply or a battery 203. Electrical power from the external power supply or battery 203 passes through the command node 202, and the command node transmits the electrical power, along with data, over one or more electrically conductive cables to one or more EES nodes 201a, 201b. EES node 201a is in data communication with the electric energy source 101a. EES node 201b is in data communication with the electric energy source 101b.

[0086] The EES management system facilitates power transmission over the data lines. In the example shown in FIG. 2A, the external power supply or battery 203 supplies power to the EES nodes 201a, 201b using the data lines of the electrical communication network.

[0087] In an example aspect, a cable C204 includes data wires C204a and C204b that transmit data and electrical power between the command node 202 and the EES node 201a. In an example aspect, one of the data wires 204a and 204b transmits power and the other one of the data wires 204a and 204b provides a DC current return.

[0088] In an alternative example aspect, the DC current supply and return are provided by wires within the same set of wires C204a. Further, the one or more wires C204b does not facilitate power transmission over data wires. It will be appreciated that there are different configurations for supplying power over the data wires.

[0089] Similar to the cable C204, a cable 205 includes multiple wires (e.g., C205a and C205b) that transmit data between the EES node 201b and the command node. One or more of these data wires are used supply power from the command node to the EES node 201 b, and one or more of these data wires provides a DC return.

[0090] The cable 206 between the EES nodes 201a, 201b also includes data wires 206a and 206b that transmits data between the two nodes. In an example aspect, electrical power is also transferred between the EES nodes over one or more of the data wires. In another example aspect, only data is transferred between the EES nodes.

[0091] FIG. 2B shows a similar EES management system as the system shown in FIG. 2A. In the example of FIG. 2B, however, power for the energy sources 101a, 101b respectively provide electrical power to the EES nodes 201a, 201b. Furthermore, electrical power from the EES nodes 201 a, 201 b is transmitted over the electrically conductive data cables to the command node 202. In other words, the command node 202 receives electrical power through its line connectorl (LC1), which is connected to cable C204, or through its line connector2 (LC2), which is connected to cable C205, or through both line connectors.

[0092] In this configuration, if electrical power from the EES node 201a fails to reach the command node 202, then electrical power from the EES node 201b will still be transmitted to the command node 202. In other words, even if there is a failure to provide power from one of the EES nodes 201a, 201 b, the redundant supply of power from the other one of the EES nodes 201 a, 201 b will ensure that the command node 202 still receives electrical power via at least one of the cables C204 or C205.

[0093] Using the EES node 201a as an example, an example reason for failing to transmit electrical power from the EES node includes damage to the cable C204 or a connection point of the cable C204. In another example aspect, electrical power fails to be delivered from the EES node 201a to the command node because the EES node 201a is damaged or has a failure. In another example aspect, electrical power fails to be delivered from the EES node 201a to the command node because the energy source 101a fails to deliver power to the EES node 201a. It will be appreciated that these failures could apply to the EES node 201b.

[0094] In another example embodiment, of FIG. 2B, the redundant power distribution also benefits neighboring nodes, not limited to the command node. An EES node supplies power to a neighboring EES node to which it is connected via a cable. For example, the EES node 201a provides redundant electrical power to EES node 201b via the electrically conductive data cable C206. In this way, if the energy source 101b fails to provide power to the EES node 201b, the EES node 201b can still receive electrical power via the cable C206 to power the operations of the EES node 201 b.

[0095] In another example, the EES node 201 b provides redundant electrical power to EES node 201a via the electrically conductive data cable C206. In this way, if the energy source 101a fails to provide power to the EES node 201a, the EES node 201a can still receive electrical power via the cable C206 to power the operations of the EES node 201a. In other words, the EES node can receive electrical power from both the energy source (e.g., a battery, solar cell, fuel cell, etc.) and through its data port. The electrical power can be received by the EES node from the different sources at the same time, or at a different times. In another example aspect, the EES node is configured to accept electrical power from the energy source 101a or via the data port to obtain continuous electrical power.

[0096] The examples shown in FIGs. 2A and 2B show two EES nodes 201a, 201b. It will be appreciated that in other embodiments of an EES management system, there are many more EES nodes that form a daisy chain network.

[0097] FIGs. 3A, 3B, 3C, 3D, 4A and 4B shows example embodiments of nodes in an EES management system that transmit or receive power for redundancy in power supply. Although shown in isolation to better show components therein, it will be appreciated that these example nodes are connected with other nodes in a daisy chain ring configuration, according to an example embodiment of the EES management system.

[0098] Turning to FIG. 3A, an example embodiment of an EES node 201a is provided, which is configured for receiving power over the data lines. The one or more other EES nodes 201b in the same daisy chain loop have the same configuration.

[0099] The node 201a includes an energy cell interface 103a and a redundancy module 301. The redundancy module 301 includes a processor system 330, a first isolator 310 (herein called isolatorl), a second isolator 311 (herein called isolator2), a first line connector 312 (herein called line connector 1), and a second line connector 313 (herein called line connector 2).

[00100] In an example aspect, the line connectors 312, 313 receive and transmit electrical signals from and to the network. The term “line connector” is also herein referred to as a “data port”.

[00101] In an example aspect, the isolators 310, 311 provide direct current (DC) electrical isolation between the components in the redundancy module and the network. The isolation may also be called galvanic isolation. For example, an isolator can be a transformer. Other examples of isolators include opto-couplers and capacitors. The purpose of the isolators is to pass data through while preventing DC flow between the line connectors and the processor system. These isolators are sometimes called network isolators.

[00102] The redundancy module 301 further includes a first power filter 314 and a second power filter 315, which are connected to a power ORing circuit 316, and which in turn is connected to a power supply 317. The ORing circuit combines or merges electrical power from different sources together and transmits the power to another destination (e.g., the local power supply 317). This local power supply 317 transmits the electrical power to components in the EES node 201a. In an example aspect, the power supply 317 obtains sufficient power to power all the components in the EES node 201a. The power filters block high frequency data and only allow DC power to pass through.

[00103] The first power filter 314 receives the electrical power from line connectorl 312, filters the electrical power, and transmits the filtered electrical power to the ORing circuit 316. The second power filter 315 receives the electrical power from line connector2 313, filters the electrical power, and transmits the filtered electrical power to the ORing circuit 316.

[00104] In FIG. 3A, the EES node 201a can receive power via one or both of the two separate line connectors 312, 313. If electrical power is unavailable from one of the line connectors 312 and 313 (e.g., by design or by unexpected failure), then the power supply 317 can obtain power from the other one of the line connectors 312 and 313. This provides power redundancy in the system.

[00105] In an example aspect, one of the line connectors 312, 313 is connected to a cable which in turn connected to a node without a power supply source. Although the given line connector does not receive electrical power, the given line connector and its connected cable is still used by the EES node to receive data or transmit data (or both).

[00106] In another example aspect, the line connectorl 312 is connected to a cable C318 comprising multiple electrically conductive data wires for transmitting and receiving data. In an example aspect, one or more of the data wires are also used for transmitting electrical power, and at least one or more other data wires are used for DC return.

[00107] The line connector2 313 is connected to a cable C319, which is like C318.

[00108] Turning to FIG. 3B, another example embodiment of an EES node 201a is provided, which also receives power from the electric energy source 101a, to which it is connected. The energy cell interface 103a is connected to the electric energy source 101a using a data connection 320 for communicating digital data or analog data or both. The electric energy source 101a transmits electrical power using an electrical connection 324 to the ORing circuit 316. In other words, the power supply 317 for the EES node 201a can receive operating power from one or more of: the line connectorl 312, the line connector2 313, and the electric energy source 101a.

[00109] Turning to FIG. 3C, an example embodiment of an EES node configured for transmitting power over the data lines. [00110] The energy cell interface 103a is connected to the electric energy source 101a using a data connection 320 for communicating digital data or analog data or both. The electric energy source 101a transmits electrical power using an electrical connection 321 to a first power supply 322. The first power supply 322 supplies electrical power to all the components of the EES node 201a. The first power supply also supplies power to a first power filter 323, and the first power filter 323 transmits power to the line connectorl 312 so that the cable C318 can transmit power to a neighboring node in the EES management system.

[00111] In an example embodiment (although not shown), the first supply 322 is connected to a second power filter 326, which transmits power via the line connector2 313.

[00112] Alternatively, the EES node 201a includes a second power supply 325 that receives electrical power through an electrical connection 324 to the electric energy source 101a. The second power supply 325 can also supply power to all the components in the EES node 201 a as redundant power supply. In another example aspect, the second power supply 325 supplies electrical power to the second power filter 326, and the second power filter 326 provides electrical power to the line connector2 313, which in turn transmits power via the data cable C319.

[00113] The EES node in FIG. 3C can therefore take electrical power from the electric energy source 101a and transmit power over one of both of its data lines to one or both of its neighboring nodes.

[00114] It will be appreciated that by having two separate and isolated line connectors (also herein called data ports) 312, 313, a failure or damage to one of the line connectors will not adversely affect the other line connector. This provides robustness in power redundancy.

[00115] Turning to FIG. 3D, another example embodiment of an EES node 201a is provided and is configured to both receive and transmits power over data lines. The EES node 201a shown in FIG. 3D can receive redundant electrical power from its connected electric energy source 101a, or from a neighboring node via its line connectorl 312, or both. The EES node also can transmit electrical power to another neighboring node via its line connector2313. When multiple ones of these EES nodes (which have the same configuration shown in FIG. 3D) are setup in a daisy chain network, each given EES node is capable of receiving power from two separate sources and is able to be a redundant supply to another neighboring node.

[00116] In particular in FIG. 3D, the EES node 201a receives power from the electric energy source 101 a to which it is connected via a power cable 321. The power cable 321 is connected to a power ORing circuit 316, and the power ORing circuit 316 is connected to the power supply 316.

[00117] Electrical power is also transmitted to the EES node 201a over the data cable C318 and received at the EES node 201a via the line connectorl 312. A first power filter 323 filters the electrical power from the data and transmits the electrical power to the ORing circuit 322. The ORing circuit 322 provides the electrical power to the power supply 316.

[00118] The power supply 316 is configured to provide electrical power to all the components of the EES node 201a. The power supply 316 also transmits electrical power to a second power filter 326, which supplies the electrical power to the line connector2 313.

The line connecto2 312 can transmits electrical power over the data cable C319, for example, to a neighboring node in the other direction of the daisy chain.

[00119] In an example embodiment, a daisy chain network includes multiple ones of these EES nodes connected together, each EES node receives power from it left side neighbor or from its own connected electric energy source (or both), and can transmit power to its right side neighbor. It will be appreciated that the direction of power flow in the daisy chain can be switched. For example, the power components positions can be swapped between line connectorl and line connector2 in the EES node.

[00120] If an EES node in the daisy chain network critically fails or is critically damaged, the other EES nodes continue to receive power from their own electric energy source or EES neighboring node, or both. If an EES node’s connected electric energy source 101 is low on power or is unable to deliver power to the EES node, then the EES node can receive power from its line connector (e.g., provided from a neighboring EES node).

[00121] Turning to FIG. 4A, an example embodiment of a command node 202 is shown. The redundancy module 401 at the command node 202 has a similar architecture. More generally, the processor system 330 is in data communication with an ECU 404, or some other controller, or display device, or another network connection.

[00122] The redundancy module 401 shown in FIG.4A is configured to transmit power over data lines. The command node in FIG. 4A is connected to an external power supply or a battery 203.

[00123] The redundancy module 401 also includes a first power supply 406, which is electrically connected to a first power filter 408, and the first power filter is electrically connected to the line connectorl 312. Electrical power from the external power supply or battery 203 passes to the first power supply 406, passes through the first power filter 408, and then passes out the first line connectorl 312 for transmission over the electrically conductive data cable C410. It will be appreciated that data and power can be transmitted and received over the same wires in cable C410.

[00124] The redundancy module 401 further includes a second power supply 407 and a second power filter 409, which transmits power through the line connector2 313. The second power supply 407 receives power from the external power supply or battery 203. Data and power can be transmitted via the electrically conductive data cable C411.

[00125] It will be appreciated that other architectures for a command node to transmit power over data lines are also applicable.

[00126] Turning to FIG. 4B, another example embodiment of a command node 202 is provided for receiving power over the data lines in the cables C410, C411. This command node has a software Ethernet architecture. A first power filter 421 is connected to the line connectorl 312, and the first power filter is connected to a power ORing circuit 423. A second power filter 422 is connected to the line connectors 313, and the second power filter is connected to the power ORing circuit 423. Electrical power received through the line connectorl 312 or the line connector2 313, or both, is transmitted via one or both filters 421 , 422 and then to the power ORing circuit 423. The electrical power from the power ORing circuit is then transmitted to the local power supply 424 of the command node 202. The power supply 424 supplies electrical power to the components of the command node. Using this example architecture, the command node receives power over the data lines from one or more neighboring nodes (e.g., two different EES nodes). If electrical power received through one of the line connectors stops or fails, then the command node can continue to receive power through the other one of its line connectors.

[00127] FIGs. 5 to 7 show different embodiments of a processor system 330.

[00128] FIG. 5 shows an example embodiment of a software Ethernet processor system, which includes a MCU 502 and two PHY devices 508, 509. In an example aspect, PHY (e.g., PHY1 508 and PHY2 509 in the redundancy module) refer to the physical layer transceiver, and is also referred to as a PHY chip. The PHY is an electronic circuit (e.g., an integrated circuit) that converts MAC layer data into a format suitable for transport over a physical layer or physical medium, such as an electrically conductive cable.

[00129] The MCU 502 includes an analog to digital converter (ADC) port 504, general purpose input output (GPIO) port 505, a media access control 1 (MAC1) port 506, and a media access control 2 (MAC2) port 507. The GPIO port 505 sends and receives digital data to and from the EES interface 103a. The ADC port 504 receives analog data from the EES interface and converts the analog data to digital data. Digital data is sent or received via the MAC1 port or the MAC2 port, or both. [00130] In an example aspect, the MCU reads data about the electric energy source, checks data against limits, issues warnings, etc.

[00131] In an example aspect, MAC1 506 is in data communication with PHY1 508,

PHY1 508 is in data communication with the isolatorl 310, the isolatorl is in data communication with the line connectorl 312, and the line connectorl 312 is connected to a cable C1. Data can be transmitted in both directions along the channel formed by C1 , line connectorl 312, isolatorl 310, PHY1 508 and MAC1 506.

[00132] In another example aspect, MAC2507 is in data communication with PHY2 509, PHY2 509 is in data communication with isolator2 311 , isolator2 is in data communication with line connector2 313, and line connector2 313 is connected to a cable C2. Data can be transmitted in both directions along the channel formed by C2, line connector2313, isolator2 311 , PHY2 509 and MAC2 507.

[00133] In an example aspect, the data connection between MAC1 and PHY1 uses one of a media-independent interface (Mil), reduced media-independent interface (RMII), and reduced gigabit media-independent interface (RGMII). It will be appreciated that other currently known and future known interfaces between a MAC and PHY layer can be used. These data connections also apply to PHY2 509 and MAC2 507.

[00134] The data connection between PHY1 and the Line Connectorl uses an Ethernet line interface. Examples of Ethernet line interfaces include 100BASE-T1 and 1000BASE-T1. Other examples of currently known and future known Ethernet line interfaces over electrically conductive wires or cables are applicable. The same type of data connection is used between PHY2 and the Line Connector2.

[00135] FIG. 6 shows an example embodiment of processor system 330 configured with a hardware Ethernet architecture. It includes a MCU 602, a programmable hardware device 604, and PHY devices 608, 609. In an example embodiment, the programmable hardware device 604 is a field programmable gate array (FPGA) device, or is an application-specific integrated circuit (ASIC) device. The programmable hardware device includes a MAC1 port 620, a MAC2 port 610 and a MAC3 port 611. The MAC2 port 610 of the device 604 is in data communication with PHY1 608, which in turn is data communication with isolatorl 310, and which in turn is in data communication with line connectorl 312. Similarly, the MAC3 port 611 of the device 604, PHY2 609, isolator2 311 , and line connector 313 are in data communication with each other.

[00136] In an example aspect, a memory device 605 is in data communication with the programmable hardware device 604. [00137] The MCU 602 includes a MAC1 port 614, a GPIO port 613, and an ADC port 612. The MAC1 port 614 of the MCU 602 is in data communication with the MAC1 port 620 of the programmable hardware device 604. The GPIO port 613 is in data communication with the EES interface 103a. The ADC port 612 is also in data communication with the EES interface 103a. The ADC port 612 receives analog data from the EES interface 103a and converts it to digital data.

[00138] In an example aspect, a memory device 603 is in data communication with the MCU 502.

[00139] In an example aspect, the data connection between MAC2 and PHY1 uses one of Mil, RMII, and RGMII. It will be appreciated that other currently known and future known interfaces between a MAC and PHY layer can be used. These data connections also apply to PHY2 609 and MAC3 611.

[00140] The data connection between PHY1 and the Line Connectorl uses an Ethernet line interface. Examples of Ethernet line interfaces include 100BASE-T1 and 1000BASE-T1. Other examples of currently known and future known Ethernet line interfaces over electrically conductive wires or cables are applicable. The same type of data connection is used between PHY2 and the Line Connector2.

[00141] FIG. 7 shows an example embodiment of a processor system 330 configured with a software architecture that is in alternative to Ethernet. Data is transmitted using a universal asynchronous receiver/transmitter (UART) device, or a controller area network (CAN) bus, or a serial peripheral interface (SPI) bus, over electrically conductive data cables. The processor system 330 includes a MCU 702 with two data ports 708 and 709. The data port 708 is in data communication with a transceiver 710, and the transceiver 710 is in data communication with an isolatorl 310. The isolatorl 310 is in data communication with a line connectorl 312. Similarly, the other data port 709 is in data communication with another transceiver 711 , and the other transceiver 711 is in data communication with another isolator2 311. The other isolator2 311 is in data communication with a line connector2313.

[00142] In an example aspect, the data ports 312 and 313 are UART data ports and receive and transmit data according to the UART protocol. In another example aspect, the data ports are CAN data ports and receive and transmit data using a CAN bus architecture.

In another example aspect, the data ports are SPI data ports and receive and transmit data using a SPI protocol. [00143] The MCU 702 also includes a GPIO port 717 that exchanges data with the EES interface. The MCU also includes an ADC port 716 to receive analog data from the EES interface and converts the same to digital data.

[00144] In an example embodiment, the transceivers 710 and 711 are separate from the MCU 702 as shown in FIG. 7. In an alternative embodiment, the MCU 702 has built-in transceivers 710, 711.

[00145] In an example aspect, a memory device 718 is in data communication with the MCU 702.

[00146] Turning to FIG. 8, an example embodiment of an EES management system is provided that includes two or more daisy chain rings. The daisy chain rings are connected to each other using a quad-port redundancy module. Two or more daisy chain rings help to limit the effect of a fault or breakage. For example, the fault or a breakage in one daisy chain ring would have less or no effect on the nodes in another daisy chain ring. Power can be distributed amongst nodes in the daisy chain ring. In a further example aspect, a quad- port redundancy module that connects two rings together also receives electrical power through the data wires.

[00147] It will be appreciated that the features described with respect to an EES management system that has one daisy chain ring also apply to an EES management system that includes two or more daisy chain rings.

[00148] In FIG. 8, an example embodiment of an EES management system is shown that includes two daisy chain rings 809 and 810 that are connected together using a quad-port redundancy module 808. One ring 809 includes the EES nodes 804a, 803a, 802a that are respectively connected to EES devices 804b, 803b, 802b. Examples of EES devices include battery cell stacks, fuel cell stacks, solar panels, electric generators, etc. The ring 809 also include a command node 801.

[00149] Another ring 810 includes the EES nodes 805a, 806a, 807a that are respectively connected to EES devices 805b, 806b, 807b.

[00150] The command node 801 transmits messages and receives messages to the nodes in the ring 809 and to the nodes in the ring 810. Messages between a given node in the ring 810 and the command node 801 are transmitted via the quad-port redundancy module 808. Other messages from the ring 809 may also be transmitted via the quad-port redundancy module 808 to a given node in the ring 810, and back to a given node in the ring 809. [00151] The nodes and the quad-port redundancy module are connected to each other using electrically conductive data cables. The quad-port redundancy module includes four data ports that respectively connect to four cables. Two data ports connect to one ring 809 and another two data ports connect to another ring 810. A quad-port redundancy module can receive electrical power through any one or more of its four data ports, as power is distributed along with the data on the same wires in a data cable.

[00152] In an example aspect, a quad-port redundancy module receives a message via one of its four data ports. The quad-port redundancy module then replicates the message and transmits the replicated instances of the message via its three other data ports. In an example aspect, the instances of the message are transmitted at the same time.

[00153] In an example aspect, a quad-port redundancy module receives a message via one of its four data ports. The quad-port redundancy module then replicates the message and transmits the replicated instances of the message via two other data ports at the same time. In an example aspect, the one data port that received the message is connected to one ring, and the two other data ports that transmit the messages are connected to another ring.

[00154] In an example aspect, a quad-port redundancy module receives a message via one of its four data ports. The quad-port redundancy module then replicates the message and transmits the replicated instances of the message via at least one of the other data ports. For example, the data port that received the message and the other data port that transmits the message are in the same ring. In another example, the data port that received the message and the other data port that transmits the message are in different rings.

[00155] In an example aspect, the quad-port redundancy module receives electrical power via one or more of the four cables connected to its data ports. Data and electrical power are transmitted together on the same wires. The electrical power can be transmitted, for example, from one or more neighboring connected EES nodes 804a, 805a, 807a, or from the command node 801 , or a combination thereof. It will be appreciated that the quad-port redundancy module receive electrical power from one or multiple sources using the same wiring for receiving and transmitting data. Therefore, even if one of the electrical power sources fail to provide sufficient power to a quad-port redundancy module, another electrical power source is available to provide the electrical power used to operate the quad-port redundancy module.

[00156] Turning to FIG. 9, an example embodiment of a quad-port redundancy module 808 is shown, which includes four line connectors (e.g., also called data ports) 901 , 902,

915, 916 that respectively connect to four cables. [00157] The line connectors 901 and 902 respectively connect to isolators 920 and 921 ; the isolators 920 and 921 respectively connect to a quad-port processor system 940. Similarly, the line connectors 915 and 916 respectively connect to isolators 922 and 923; and the isolators 922 and 923 respectively connect to the quad-port processor system 940. The quad-port processor system 940 replicates messages, determines the one or more data ports to transmit one or more replicated message, and then accordingly transmits the replicated one or more messages via the one or more determined data ports.

[00158] Each of the line connectors 901 , 902, 915 and 916 is respectively connected to a power filter 931 , 932, 933, 934, and these power filters are connected to a power ORing circuit 935. The circuit 935 is connected to a local power supply 936. In other words, power can be received via any one or more of the line connectors, filtered by the power filter, and then transmitted to the local power supply 936. The local power supply 936 retransmits the power to the components in the quad-port redundancy module. In an example aspect, the entire set of components of the quad-port redundancy module 808 can therefore be powered using the power received via one or more of the line connectors.

[00159] FIGs. 10 and 11 show different example embodiments of quad-port processor systems 940. FIG. 10 is software Ethernet implementation, and FIG. 11 is a hardware Ethernet implementation.

[00160] Turning to FIG. 10, a quad-port processor system 940 is configured with a software Ethernet architecture. The processor system 940 includes a first MCU 1005 connected to a second MCU 1009, and PHY devices. In particular, PHYs 1003 and 1004 respectively connect to MAC ports 1006 and 1007 of the first MCU 1005.

[00161] The first MCU 1005 includes MAC ports 1006 and 1007, and a high-speed bus port 1008.

[00162] The second MCU 1009 includes MAC ports 1011 and 1012, and a high-speed bus port 1010. The first MCU 1005 and the second MCU 1009 are in data communication with each other using high-speed bus ports 1008 and 1010.

[00163] MACs 1011 and 1012 of the second MCU 1009 are respectively connected to PHYs 1013 and 1014, and the PHYs 1013 and 1014 are respectively connected to isolators 922 and 923. These isolators 922 and 923 are respectively connected to line connectors 915 and 916.

[00164] In an example aspect, one or both of the MCUs are in data communication with one or more memory devices 1017, 1018. [00165] In an example aspect, connections between a PHY and a MAC include Mil, RMII, RGMII, SGMII or some other interface.

[00166] In another example aspect, the high-speed bus between the MCUs includes an external bus, an Ethernet connection, a peripheral component interconnect express (PCIE) connection, or a universal serial bus (USB) connection, etc.

[00167] Turning to FIG. 11 , a hardware Ethernet architecture of a quad-port processor system 940 is shown, which includes a chip 1110 and PHY devices 1113, 1114, 1106, 1107. In particular, PHY devices 1106 and 1107 are respectively connected to MAC ports 1108 and 1109 of the chip 1110. PHY devices 1113 and 1114 are respectively connected to MAC ports 1111 and 1112 of the chip 1110. The chip 1110 is a FPGA device or an ASIC device.

[00168] It will be appreciated that the PHY devices 1113, 1114, 1106, 1107 are respectively connected to the isolators 922, 923, 901 , 902.

[00169] In an example aspect, the chip 1110 is in data communication with a memory device 1120.

[00170] Other architectures can be used for the quad-port processor system 940, not limited to Ethernet architectures.

[00171] FIG. 12 shows an example embodiment of a vehicle 1200 that includes an EES management system 1201. Example embodiments of the EES management system described above are used to provide a power redundant system to manage the nodes that control energy source devices for a vehicle, thereby provide reliability and safety for the operation of the vehicle. For example, multiple sets of energy cells (e.g., battery cells, fuel cells, etc.) are included in the vehicle and that are part of the EES management system 1201. The EES management system 1201 provides electric power to different subsystems in the vehicle, including, for example, one or more electric motors for the primary drive system 1202 and the electric power steering system 1203. Although the vehicle 1200 is shown as a car, it will be appreciated that other types of vehicles (e.g., trucks, construction vehicles, buses, transport vehicles, aircraft, drones, boats, submarines, trains, etc.) can include the EES management system 1201.

[00172] The EES management system described herein can also be used in other systems, including and not limited to power supply units, power banks, micro-power grids.

[00173] FIG. 13, for example, shows an EES management system 1301 in a form of a power bank that can be integrated with other electric energy sources 1 A.G. and used to provide power to one or more electric loads 1302. Multiple ones of these EES management systems 1301 in the form of power banks can be connected together to form a micro-power grid.

[00174] In an example aspect, the devices and systems described herein provide redundant power and redundant communications in battery management systems so that no single point failure can cause potential damage or, even loss of life in the case of vehicles.

In another example aspect, the devices and systems described herein take a different approach to safety, changing away from “fail-safe shutdown state”. Instead, the devices and operations described herein facilitate a “fail-safe operation state” that would keep communication alive to support transition to a safe state.

[00175] Below are general example embodiments and example aspects.

[00176] In an example embodiment, a redundant EES management system includes: a command node and EES nodes connected in a daisy chain ring with electrically conductive data wires that transmit both data and electrical power; the command node and the EES nodes each comprising a redundancy module; the redundancy module comprising a processor and two data ports; and the command node comprising two power filters respectively in electrical connection with the two data ports, and the command node transmitting or receiving electrical power through one or more of the data ports at the same time as transmitting a first and a second instance of a message in different directions at the same time using the two data ports.

[00177] In an example aspect, the command node receives the electrical power from at least a neighboring EES node connected to one of the two data ports, and the electrical power is used to operate the command node.

[00178] In another example aspect, the command node transmits the electrical power to at least a neighboring EES node connected to one of the two data ports, and the electrical power is used to operate the neighboring EES node.

[00179] In an example embodiment, a redundant EES management system includes: a command node and EES nodes connected in a daisy chain ring with electrically conductive data wires that transmit both data and electrical power; the command node and the EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; each of the EES nodes is data connected to a corresponding electric energy source; and a given EES node comprises two power filters respectively in electrical connection with its two data ports, and the given EES node transmits or receives the electrical power through one or more of the two data ports at the same time as transmitting a first and a second instance of a message in different directions at the same time using the two data ports. [00180] In an example aspect, the given EES node receives the electrical power from a corresponding given electric energy source to which it is connected and transmits the electrical power via one or both of the two data ports.

[00181] In another example aspect, the electrical power from the corresponding given electric energy source is used to power all components on the given EES node.

[00182] In another example aspect, the given EES node receives electrical power via one or both of its two data ports for powering all components of the given EES node.

[00183] In another example aspect, the given EES node receives the electrical power from a corresponding given electric energy source to which it is connected and receives the electrical power from one or both of the two data ports, the electrical power used to power the given EES node. In an example aspect, the given EES node receives the electrical power from the corresponding given electric energy source at a different time compared to receiving the electrical power from the one or both of the two data ports. In an alternative example aspect, the given EES node receives the electrical power from the corresponding given electric energy source at a same time as receiving the electrical power from the one or both of the two data ports.

[00184] In an example embodiment, an EES node includes: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first and a second data ports that are respectively connected to a first and a second isolators, the first and the second isolators respectively connected to a first and a second PHY devices, and the first and the second PHY devices are respectively connected to a first and a second media access control (MAC) ports; the redundancy module further comprising a micro controller unit (MCU) that comprises the first and the second MAC ports and a data port that is data linked to the EES interface; a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

[00185] In an example embodiment, an EES node includes: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first and a second data ports that are respectively connected to a first and second media access control (MAC) ports of a chip device, the chip device further comprising a third MAC port; the redundancy module further comprising a micro controller unit (MCU) that comprises a MAC port, the MAC port of the MCU data linked to the third MAC port of the chip device, and the MCU further comprising a data port that is data linked to the EES interface; a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

[00186] In an example embodiment, an EES node includes: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first and a second data ports that are respectively connected to a first and a second transceiver devices, and the first and the second transceiver devices are respectively connected to a first and a second data port on a micro controller unit (MCU), wherein the first and the second data ports on the MCU are one of a UART interface, a CAN bus interface and an SPI interface; a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

[00187] In an example embodiment, an EES management system includes: two daisy chain rings formed by multiple nodes that are interconnected using electrically conductive data cables, and the multiple nodes comprise one or more EES nodes and one or more command nodes; and a quad-port redundancy module that interconnects the two daisy chain rings, the quad-port redundancy module comprising four data ports and a processor, and two of the four data ports are connected to one of the two daisy chain rings and other two of the four data ports are connected to the other one of the two daisy chain rings; and the quad-port redundancy module further comprises a power supply and four power filters that are respectively electrically connected to the four data ports, and electrical power received via one or more of the four data ports is filtered and transmitted to the power supply, which powers to the quad-port redundancy module.

[00188] In an example aspect, the quad-port redundancy module further comprises a power ORing circuit; the four power supplies are connected to the power ORing circuit; and, the power ORing circuit is connected to the power supply.

[00189] In an example embodiment, an EES management system with redundant power supply, includes: a command node and EES nodes connected in a daisy chain ring with electrically conductive data cables; the command node and the EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; and wherein a given EES node in the daisy chain ring receives electrical power and data via one or both of its two data ports, and the EES node filters the electrical power from the data and internally distributes the electrical power for powering all components of the given EES node.

[00190] In an example embodiment, an EES management system with redundant power supply, includes: a command node and EES nodes connected in a daisy chain ring with electrically conductive data cables, each of the EES nodes connected respectively to a corresponding EES device; the command node and the EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; and wherein a given EES node receives electrical power from its corresponding given EES device, and the given EES node uses the electrical power for powering components of the given EES node and to output the electrical power along with data via one or both of its respective two data ports.

[00191] It will be appreciated that any module or component exemplified herein that executes instructions may include or otherwise have access to non-transitory computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, memory chips, magnetic disks, optical disks. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, code, processor executable instructions, data structures, program modules, or other data. Examples of computer storage media include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), solid-state ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the computing devices or nodes, or accessible or connectable thereto. Any application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media.

[00192] It will be appreciated that different features of the example embodiments of the system and methods, as described herein, may be combined with each other in different ways. In other words, different devices, modules, operations, functionality and components may be used together according to other example embodiments, although not specifically stated. [00193] The steps or operations in the flow diagrams described herein are just for example. There may be many variations to these steps or operations according to the principles described herein. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified.

[00194] It will also be appreciated that the examples and corresponding system diagrams used herein are for illustrative purposes only. Different configurations and terminology can be used without departing from the principles expressed herein. For instance, components and modules can be added, deleted, modified, or arranged with differing connections without departing from these principles.

[00195] While certain example implementations of the disclosed technology have been described in connection with what is presently considered to be the most practical and various implementations, it is to be understood that the disclosed technology is not to be limited to the disclosed example implementations, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the claims appended hereto.

Claims

Claims:

1. A redundant electric energy source (EES) management system comprising: a command node and a plurality of EES nodes connected in a daisy chain ring with electrically conductive data wires that transmit both data and electrical power on the same data wires; the command node and the plurality of EES nodes each comprising a redundancy module; the redundancy module comprising a processor and two data ports; and the command node further comprising two power filters respectively in electrical connection with the two data ports, and the command node transmitting or receiving electrical power through one or more of the two data ports at the same time as transmitting a first instance and a second instance of a message in different directions at a same time using the two data ports.

2. The redundant EES management system of claim 1 , wherein the command node receives the electrical power from at least a neighboring EES node connected to one of the two data ports, and the electrical power is used to operate the command node.

3. The redundant EES management system of claim 1 , wherein the command node further comprises a power supply and a power ORing circuit; and wherein the two power filters are connected to the power ORing circuit, and the power ORing circuit is connected to the power supply.

4. The redundant EES management system of claim 1 , wherein the command node transmits the electrical power to at least a neighboring EES node connected to one of the two data ports, and the electrical power is used to operate the neighboring EES node.

5. The redundant EES management system of claim 1 further comprising a processor, an isolator electrically connected to the processor, one of the two power filters is electrically connected to both the isolator and one of the two data ports, and a power supply is electrically connected to one of the two power filters; and wherein the power supply supplies the electrical power to the one of the two power filters, and the one of the two power filters transmits the electrical power through the one of the two data ports.

6. The redundant EES management system of claim 1 wherein each of the plurality of EES nodes is data connected to a corresponding electric energy source.

7. A redundant electric energy source (EES) management system comprising: a command node and a plurality of EES nodes connected in a daisy chain ring with electrically conductive data wires that transmit both data and electrical power on the same data wires; the command node and the plurality of EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; each of the plurality of EES nodes is data connected to a corresponding electric energy source; and a given EES node comprises two power filters respectively in electrical connection with its two data ports, and the given EES node transmits or receives the electrical power through one or more of the two data ports.

8. The redundant EES management system of claim 7 wherein the given EES node receives the electrical power from a corresponding given electric energy source to which it is connected and transmits the electrical power via one or both of the two data ports.

9. The redundant EES management system of claim 8 wherein the electrical power from the corresponding given electric energy source is used to power the given EES node.

10. The redundant EES management system of claim 7 wherein the given EES node receives the electrical power via one or both of the two data ports for powering the given EES node.

11 . The redundant EES management system of claim 10, wherein the given EES node further comprises a power supply and a power ORing circuit; and wherein the two power filters are connected to the power ORing circuit, and the power ORing circuit is connected to the power supply.

12. The redundant EES management system of claim 7 wherein the given EES node receives the electrical power from a corresponding given electric energy source to which it is connected and receives the electrical power from one or both of the two data ports, the electrical power used to power the given EES node; and, wherein the given EES node receives the electrical power from the corresponding given electric energy source at a different time compared to receiving the electrical power from the one or both of the two data ports.

13. The redundant EES management system of claim 7 wherein the given EES node receives the electrical power from a corresponding given electric energy source to which it is connected and receives the electrical power from one or both of the two data ports, the electrical power used to power the given EES node; and, wherein the given EES node receives the electrical power from the corresponding given electric energy source at a same time as receiving the electrical power from the one or both of the two data ports.

14. The redundant EES management system of claim 7 wherein the corresponding electric source is a battery.

15. The redundant EES management system of claim 7 wherein the corresponding electric source comprises at least one of a battery, a solar cell, and a fuel cell.

16. An electric energy source (EES) node in an EES management system, the EES node comprising: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first data port and a second data port that are respectively connected to a first isolator and a second isolator, the first isolator and the second isolator respectively connected to a first PHY device and a second PHY device, and the first PHY device and the second PHY device are respectively connected to a first media access control (MAC) port and a second MAC port; the redundancy module further comprising a micro controller unit (MCU) that comprises the first MAC port and the second MAC port, and a data port that is data linked to the EES interface; a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

17. An electric energy source (EES) node in an EES management system, the EES node comprising: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first data port and a second data port that are respectively connected to a first media access control (MAC) port and second MAC port of a chip device, the chip device further comprising a third MAC port; the redundancy module further comprising a micro controller unit (MCU) that comprises a MAC port, the MAC port of the MCU is data linked to the third MAC port of the chip device, and the MCU further comprising a data port that is data linked to the EES interface; a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

18. An electric energy source (EES) node in an EES management system, the EES node comprising: an EES interface connected to a redundancy module, the EES interface configured to connect with an EES device; the redundancy module comprising a first data port and a second data port that are respectively connected to a first transceiver device and a second transceiver device, and the first transceiver device and the second transceiver device are respectively connected to a first data port and a second data port on a micro controller unit (MCU), wherein the first data port and the second data port on the MCU are one of a universal asynchronous receiver transmitter (UART) interface, a controller area network (CAN) bus interface and a serial peripheral interface (SPI); a power supply and a power filter; and wherein the power supply receives electrical power from the EES device to supply the electrical power to the power filter, and the power filter is connected to at least one of the first data port and the second data port to output the electrical power configured to power a connected neighboring node in the EES management system.

19. An electric energy source (EES) management system comprising: two daisy chain rings formed by multiple nodes that are interconnected using electrically conductive data cables, and the multiple nodes comprise one or more EES nodes and one or more command nodes; and a quad-port redundancy module that interconnects the two daisy chain rings, the quad-port redundancy module comprising four data ports and a processor, and two of the four data ports are connected to one of the two daisy chain rings and other two of the four data ports are connected to the other one of the two daisy chain rings; and the quad-port redundancy module further comprises a power supply and four power filters that are respectively electrically connected to the four data ports, and electrical power received via one or more of the four data ports is filtered and transmitted to the power supply, which powers to the quad-port redundancy module.

20. The EES management system of claim 19 wherein: the quad-port redundancy module further comprises a power ORing circuit; the four power filters are connected to the power ORing circuit; and, the power ORing circuit is connected to the power supply.

21. An electric energy source (EES) management system with redundant power supply, comprising: a command node and a plurality of EES nodes connected in a daisy chain ring with electrically conductive data cables; the command node and the plurality of EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; and wherein a given EES node in the daisy chain ring receives electrical power and data via one or both of the two data ports, and the given EES node filters the electrical power from the data and internally distributes the electrical power for powering the given EES node.

22. An electric energy source (EES) management system with redundant power supply, comprising: a command node and a plurality of EES nodes connected in a daisy chain ring with electrically conductive data cables, each of the plurality of EES nodes connected respectively to a corresponding EES device; the command node and the plurality of EES nodes each comprising a redundancy module, the redundancy module comprising a processor and two data ports; and wherein a given EES node receives electrical power from a corresponding given EES device, and the given EES node uses the electrical power for powering the given EES node and to output the electrical power along with data via one or both of its respective two data ports.