The disclosure relates to the field of battery electrical vehicles (BEVs). In particular, the disclosure relates to a method and system for managing power supply during charging operation of BEVs.
Multiple customers are using their electrical grid network to pre-cool or maintain the temperature of transport refrigeration boxes. Most customers have not designed their facilities for the large power draw from the electrical grid. Also, most of the time, the customers switch all units ON around the same timeframe. Such a significant draw on the grid may have a negative impact a network and possibly result in a grid shutdown.
Also, today's refrigeration units on thermal engine trucks don't offer any smart management of the standby operation when they are connected to the electrical grid. The rise of the BEVs will result in a need to optimize the power available on the electrical grid, leading to a need to optimize the logics of recharge to extend battery life or reduce nominal powers draw.
It would be advantageous to provide a method and system that may automatically manage the power supply to the BEVs having transport refrigeration units (TRUs) or to the TRUs batteries.
This summary is provided to introduce a selection of concepts in a simplified format that are further described in the detailed description of the invention. This summary is not intended to identify key or essential inventive concepts of the invention, nor is it intended for determining the scope of the invention.
Disclosed herein is a vehicle charging system for managing power supply during charging operation of a plurality of BEVs. The system includes a master device connected to a primary grid network. The master device includes at least one processor and a communication interface. The at least one processor is configured to establish a communication with each of a plurality of slave devices installed in the plurality of BEVs and receive input data in real-time via the communication interface from the plurality of slave devices. The input data includes information related to a power level consumed by each of a plurality of Transport Refrigeration Units (TRUs) of the plurality of BEVs during the charging operation, a corresponding operation mode of the plurality of TRUs, a current state of each of the plurality of TRUs. The at least one processor is further configured to calculate total power currently utilized by the plurality of TRUs based on the received input data. After the calculation of the total power, the at least one processor is further configured to determine a probability whether the calculated total power exceeds a maximum allowed power provided by the primary grid network during the charging operation in case a new charging request is received from a new slave device. Further, based on the determined probability, the at least one processor is configured to regulate a power allocation of a group of TRUs among the plurality of the TRUs such that the total calculated power remains below a saturation point of the maximum allowed power.
In one or more embodiments, the at least one processor may be further configured to receive, based on a user input, a priority request from at least one slave device of the plurality of slave devices for authorization to utilize an excess amount of power from the primary grid network in comparison to an allocated power of the at least one TRU. Thereafter, the at least one processor may be further configured to authorize the at least one TRU for utilizing the excess amount of power from the primary grid network in case the total calculated power is within the saturation point of the maximum allowed power.
In one or more embodiments, the at least one processor may be further configured to estimate, based on the authorization, each of a remaining time to reach a setpoint and a remaining time required for a full recharge of the BEV associated with the at least one slave device from which the priority request is received. Thereafter, the at least one processor may be further configured to control a graphical user interface (GUI) of the BEV or TRU associated with the at least one slave device to display each of the estimated remaining time to reach the setpoint and the estimated remaining time required for the full recharge.
In one or more embodiments, the at least one processor may be further configured to estimate a remaining time required for a full recharge of each of the plurality of BEVs based on the total calculated power, and then controls the GUI of each of the plurality of BEVs to display each of the estimated remaining time required for the full recharge.
In one or more embodiments, the master device is connected with the plurality of slave devices in one of a point-to-point configuration or a multipoint configuration.
In one or more embodiments, the at least one processor may be further configured to regulate, based on the determined probability, the power allocation for each of the plurality of TRUs in a case where the master device is connected with the plurality of slave devices in the multipoint configuration.
In one or more embodiments, the established communication corresponds to one of an electrical-based communication, a Controlled Area Network (CAN) based communication, a Power Line Communication (PLC), or wireless communication.
In one or more embodiments, the regulation of the power allocation corresponds to a command from the master device to a group of slave devices among the plurality of slave devices to reduce or increase a power intake from the primary grid network to avoid power overloading.
In one or more embodiments, the input data is received periodically from each of the plurality of the slave devices. The corresponding operation modes may include a cooling mode, a heating mode, a standby mode of the plurality of TRUs, a null mode, or a recharge mode of a battery of corresponding BEVs. The null mode corresponds to a ventilation mode. The current state of each of the plurality of TRUs corresponds to one of an ON state or an OFF state.
Also disclosed is a method for managing power supply during charging operation of a plurality of BEVs. The method includes establishing a communication with each of a plurality of slave devices installed in the plurality of BEVs and then receiving input data in real-time via the communication interface from the plurality of slave devices. The input data includes information related to a power level consumed by each of a plurality of Transport Refrigeration Units (TRUs) of the plurality of BEVs during the charging operation, a corresponding operation mode of the plurality of TRUs, a current state of each of the plurality of TRUs. The method further includes calculating a total power currently utilized by the plurality of TRUs based on the received input data. Thereafter, the method further includes determining a probability whether the calculated total power exceeds a maximum allowed power provided by the primary grid network during the charging operation in case a new charging request is received from a new slave device. The method further includes regulating, based on the determined probability, a power allocation of a group of TRUs among the plurality of the TRUs such that the total calculated power remains below a saturation point of the maximum allowed power.
In one or more embodiments, the method may further include receiving, based on a user input, a priority request from at least one slave device of the plurality of slave devices for authorization to utilize an excess amount of power from the primary grid network in comparison to an allocated power of the at least one TRU. The method may further include authorizing the at least one TRU for utilizing the excess amount of power from the primary grid network in case the total calculated power is within the saturation point of the maximum allowed power.
In one or more embodiments, the method may further include estimating, based on the authorization, each of a remaining time to reach a setpoint and a remaining time required for a full recharge of the BEV associated with the at least one slave device from which the priority request is received. The method may further include controlling the GUI of the BEV associated with the at least one slave device to display each of the estimated remaining time to reach the setpoint and the estimated remaining time required for the full recharge.
In one or more embodiments, the method may further include estimating a remaining time required for a full recharge of each of the plurality of BEVs based on the total calculated power and thereafter controlling the GUI of each of the plurality of BEVs to display each of the estimated remaining time required for the full recharge.
In one or more embodiments, the master device is connected with the plurality of slave devices in one of a point-to-point configuration or a multipoint configuration.
In one or more embodiments, the method may further include regulating, based on the determined probability, the power allocation for each of the plurality of TRUs in a case where the master device is connected with the plurality of slave devices in the multipoint configuration.
In one or more embodiments, the regulation of the power allocation corresponds to a command from the master device to a group of slave devices among the plurality of slave devices to reduce or increase a power intake from the primary grid network to avoid power overloading.
To further clarify the advantages and features of the method and system, a more particular description of the method and system will be rendered by reference to specific embodiments thereof, which are illustrated in the appended drawing. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting its scope. The invention will be described and explained with additional specificity and detail with the accompanying drawings.
These and other features, aspects, and advantages will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the invention. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
It should be understood at the outset that although illustrative implementations of embodiments are illustrated below, the system and method may be implemented using any number of techniques. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “one or more,” but not all” or “all” would all fall under the definition of “some.” The term “some embodiments” may refer to one embodiment or one or more embodiments or all embodiments. Accordingly, the term “some embodiments” is defined as meaning “one embodiment, or more than one embodiment, or all embodiments.”
The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the spirit and scope of the claims or their equivalents.
More specifically, any terms used herein such as but not limited to “includes,” “comprises,” “has,” “have” and grammatical variants thereof do not specify an exact limitation or restriction and certainly do not exclude the possible addition of one or more features or elements, unless otherwise stated, and must not be taken to exclude the possible removal of one or more of the listed features and elements, unless otherwise stated with the limiting language “must comprise” or “needs to include.”
The term “unit” used herein may imply a unit including, for example, one of hardware, software, and firmware or a combination of two or more of them. The “unit” may be interchangeably used with a term such as logic, a logical block, a component, a circuit, and the like. The “unit” may be a minimum system component for performing one or more functions or may be a part thereof.
Unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.
Embodiments will be described below in detail with reference to the accompanying drawings.
The system 100 may have different customer grid configurations.
Referring now to
The master device 405 is the main component of the system 400A and controls the entire power supply management operation between the customer electrical station 403 and the slave devices 407 in different types of charging operation modes of the BEVs. The master device 405 manages power allocation to the TRUs, BEVs recharge operations, and other charging operations.
When the users of the BEVs start the TRUs or provide input regarding a change of the charging operation mode, then, in that case, the master device 405 may regulate a power allocation of a group of TRUs among the plurality of the TRUs such that the total consumption of power remains below a saturation point of the maximum limit of the apparent power. The master device 405 may also regulate the power allocation for each of the plurality of TRUs in a case where the master device 405 is connected with each of the slave devices 407 in the multipoint grid configuration.
The HMI (1 to N) may include a graphical user interface to receive the user inputs from the users of the BEVs when the users interact with the HMIs. The user input may include a change of a charging operation mode or a priority request for a power supply. The charging operation mode may include a mode to charge a battery of the TRU, a direct power supply to the TRU to cool or heat the refrigeration compartment of the BEVs to a set point, or a mode in which charging of a battery of the TRU along with the direct power supply to the TRU may be requested by at least one user of the BEV concurrently.
Referring now to
The functionalities of the components of the system 400B are the same as that of the components of the system 400A and therefore a detailed explanation is omitted herein for the sake of brevity. The only difference between the system 400A and the system 400B is the grid configuration. In the system 400B, the master device 405B is connected to the respective slave devices 407B in a split manner. The functionalities of the master device 405 of system 400A and the master device 4058 of the system 400B are the same and therefore the functionalities and operations of the system are described herein with respect to the master device 405 without deviating from the scope of the disclosure.
The microprocessor 505 uses the I/O interface 501 for data input and data output required in the management of the power supply to the TRUs, battery of the BEVs, power supply for boost mode, etc.
The CAN bus 503 allows the microprocessor 505 of the master device 405 to communicate with each of the slave devices 407 without a host computer. CAN bus protocols uses the onboard diagnostics (OBD)-n vehicle diagnostics standard.
The microprocessor 505 is connected with each of the I/O interface 501, CAN bus 503, the PLC unit 507, and actuation units 509 for receiving data inputs and processing them to perform control operations in various charging operation modes of the BEVs. The microprocessor 505 may analyze the data input from the slave devices 407 installed in the fleet of the TRUs and may allocate power for one or more charging operation modes of one or more BEVs. This data exchange may be performed by the microprocessor 505 either through one of hard signal inputs/output based wired connection, CAN bus communication with BEVs or TRUs, the powerline communication, or remote (Wifi/Bluetooth).
The microprocessor 505 may also regulate a power allocation of a group of TRUS among the plurality of the TRUs such that the total power consumption during the charging operation mode of BEVs remains below a saturation point of the maximum power subscription allowed.
The microprocessor 505 may also regulate the power allocation for each of the plurality of TRUs in a case where the master device 405 is connected with the slave devices 407 in the multipoint grid configuration.
The PLC unit 507 is configured to perform power line communication using power cable hardware to communicate between the TRUs and the master device master device 405. The TRUs may have a dual transmitter/receiver and the PLC unit 507 may establish the communication between the master device and the TRUs by using a protocol. Through the protocol, the PLC unit 507 may exchange power level, unit mode type, etc. The PLC unit 507 may also transmit data to the slave devices 407 using power cables such as power lines. In the case of using power lines, power and data transmission can be done with a single cable, which can reduce the types of cables in the network. The PLC unit 507 modulates the data before the transmission, and the modulated signal is superimposed on the AC or DC power supply voltage. The PLC unit 507 can be used on AC power lines as well as on DC power lines. As a non-limiting example, on DC power lines, the PLC unit 507 can be used for storage batteries, lighting, EV charging, etc.
The actuation units 509 correspond to a hardware device that is capable of providing power to the TRUs or for cutting-off power to the TRUs. In particular, the actuation units 509 is an on/off device like a contactor. The contactor is directly managed by the microprocessor 505 or 505B. The microprocessor 505 or 505B may activate or deactivate the contactor in accordance with the unit mode type. Also, the actuation units 509 are configured to receive power supply from the customer electrical station 403.
The wireless communication device 511 corresponds to wireless communication device configured of WI-FI®, Bluetooth®, ZigBee®, 6LoWPAN, etc). The wireless communication device 511 also allows the microprocessor 505 of the master device 405 to communicate with each of the slave devices 407 without a host computer.
The physical electronic connection interface 513 is configured to receive power from a plug having the standby cable from the primary grid network 401. In particular, the physical electronic connection interface 513 corresponds to an interface with high AC voltage (for example, a typical network with: 400 VAC/3 phases/50 Hz or 230 VAC/1 phase/50 Hz or 12 VDC, 24 VDC power supply).
The functionalities of the components of the master device 405B are the same as that of the components of the master device 405 and therefore a detailed explanation is omitted herein for the sake of brevity. The only difference between the master device 405B and the master device 405 is the grid configuration in which they are connected. In the system 400B, the master device 405B is connected to the respective slave devices 407B in a split manner. The functionalities of the microprocessor 505B of the master device 405B are the same as that of the microprocessor 505 of the master device 405 and therefore a description illustrating the functionalities and operations of the microprocessor 505B is omitted herein for ease of explanation.
Similarly,
Further,
Referring now to
At step 1101 of method 1100, the microprocessor 505 establishes a communication with each of the slave devices 407 installed in the BEVs via one of the communication configurations described above. In particular, communication between the master device 405 and each of the slave devices 407 is established using through one of hard signal inputs/output based wired connection, CAN bus communication with BEVs or TRUs, the powerline communication, or the remote (Wifi/Bluetooth) connection. The flow of the method 1100 now proceeds to (step 1103).
At step 1103, the microprocessor 505 receives input data from the slave devices 407 in real-time via the established communication. The microprocessor 505 may receive the input data periodically from each of the slave devices 407. As a non-limiting example, the input data may include information related to a power level consumed by each of the TRUs of the BEVs during charging operation modes, a corresponding operation mode of the TRUs, and a current state of each of the TRUs. The charging operation modes may include but are not limited to, a mode to charge the battery of the TRUs, a direct power supply to the TRUs to cool or heat the refrigeration compartment of the BEVs to a right set point, a mode in which charging of a battery of the TRU along with the direct power supply to the TRU may be requested by at least one user of the BEV concurrently.
The corresponding operation modes of the TRUs may include but are not limited to, a cooling mode, a heating mode, a null mode, a recharge mode of a battery of the corresponding TRUs, or a standby mode of the plurality of TRUs. The current state of each of the TRUs corresponds to one of an ON state or an OFF state. The flow of the method 1100 now proceeds to (step 1105).
At step 1105, after the reception of the input data, the microprocessor 505 calculates, based on the received input data, the total power that is currently utilized by the TRUs that are connected to the master device 405 through the slave devices 407. As a non-limiting example, let's consider the user starts the TRU 1, TRU 2, TRU 5, TRU 6, and TRU 8 by providing user input to the respective HMI 1, HMI 2, HMI 5, HMI 6, and HMI 8, after the establishment of the communication between the master device 405 and the slave devices 407. Then, in such case, the microprocessor 505 may calculate the total power that is currently utilized by the TRUs (TRU 1, TRU 2, TRU 5, TRU 6, and TRU 8) that were started by the respective users. The flow of the method 1100 now proceeds to (step 1107).
At step 1107, once the total power utilized by the TRUs that are connected to the master device 405, the microprocessor 505 determines a probability whether the calculated total power exceeds the maximum power subscription allowed by the primary grid network 401 during the charging operation each time when a new charging request is received from a newly connected slave device. The flow of the method 1100 now proceeds to (step 1109).
At step 1109, based on a result of the determination of step 1107, the microprocessor 505 regulates a power allocation of a group of TRUs among the TRUs connected to the master device 405 such that the total calculated power remains below a saturation point of the maximum power subscription allowed by the primary grid network. The regulation of the power allocation by the microprocessor 505 may correspond to a command from the master device 405 to a group of slave devices among the slave devices 407 to reduce or increase a power intake from the primary grid network 401 to avoid power overloading.
In one or more embodiments, based on a result of the determination of the probability, the microprocessor 505B may also regulate the power allocation of the group of TRUs each of the TRUs in a case where the master device 405B is connected with the slave devices 407B in the multipoint grid configuration or the split grid configuration.
Due to regulation of the power allocation by the microprocessor 505 or 505B, the network overload stress does not increase beyond the maximum limit of the apparent power and the power supply to the BEVs having the TRUs is maintained below the saturation point. As an example,
In one or more embodiments, the microprocessor 505 or 505B may also provide widgets on the GUI of the HMIs for receiving the priority request from the users to prioritize a pulldown and/or recharge of the battery of a TRU among a large fleet of TRUS running on the power of the same electrical grid. When the slave devices 407 are connected to the electrical grid via the master device 405 or 405B, the microprocessor 505 or 505B controls the GUI of the HMIs to display widgets that give an estimation of the remaining time of recharge based on live measurement of current power supply level for BEVs operation mode or recharge of the TRUs or other usage. When a user provides an input to the system 400A or 400B by interacting with the displayed widget, it triggers a boost operation.
Further,
In one or more embodiments, the microprocessor 505 may estimate, based on the provided authorization, each of a remaining time to reach a setpoint and a remaining time required for a full recharge of the battery of BEV or the TRUs, associated with the at least one slave device 407 from which the priority request is received. Further, the microprocessor 505 may also control the GUI of the HMI associated with the at least one slave device of the slave devices 407 to display each of the estimated remaining time to reach the setpoint and the estimated remaining time required for the full recharge of the battery.
According to yet another embodiment, the microprocessor 505 may estimate a remaining time required for the full recharge of the battery of each of the BEVs based on the total calculated power. Further, the microprocessor 505 may also control the GUI of each of the HMIs installed in the BEVs to display each of the estimated remaining time required for the full recharge of the battery.
As can be seen in
Further, it can be seen in
As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts.
The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.
Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.
This application claims the benefit of U.S. Provisional Patent Application No. 63/385,826 filed on Dec. 2, 2022, which is incorporated by reference herein in its entirety.
Number | Date | Country | |
---|---|---|---|
63385826 | Dec 2022 | US |