Electric refuse vehicles (i.e., battery-powered refuse vehicles) include one or more energy storage elements (e.g., batteries) that supply energy to an electric motor. The electric motor supplies rotational power to the wheels of the refuse vehicle to drive the refuse vehicle. The energy storage elements can also be used to supply energy to vehicle subsystems, like the lift system or the compactor.
One exemplary embodiment relates to a refuse vehicle. The refuse vehicle includes a chassis supporting a plurality of wheels, a battery supported by the chassis and configured to provide electrical power to a first motor, wherein rotation of the first motor selectively drives at least one of the plurality of wheels, a vehicle body supported by the chassis and defining a receptacle for storing refuse therein, and an electric power take-off system coupled to at least one of the chassis and the vehicle body. The electric power-take-off system includes a second motor configured to convert electrical power received from the battery into hydraulic power an inverter configured to provide electrical power to the second motor from the battery, a heat dissipation device coupled to the inverter, wherein the heat dissipation device is configured to cool the inverter, a first sensor configured to detect thermal energy within the inverter, and a controller configured to receive data from the first sensor and provide operating parameters to the heat dissipation device, wherein the controller is further configured to determine if the data from the first sensor is greater than a critical operating condition and shut down the electric power take-off system in response to determining that the data from the first sensor is greater than the critical operating condition.
Another exemplary embodiment relates to a refuse vehicle. The refuse vehicle includes a chassis supporting a plurality of wheels, a chassis battery supported by the chassis and configured to provide electrical power to a first motor, wherein rotation of the first motor selectively drives at least one of the plurality of wheels, a vehicle body supported by the chassis and defining a receptacle for storing refuse therein, and an electric power take-off system coupled to the chassis. The electric power take-off system includes a secondary battery, a second motor configured to convert electrical power received from the chassis battery into hydraulic power, an inverter configured to provide electrical power to the second motor from at least one of the chassis battery or the secondary battery, a heat dissipation device in thermal communication with the inverter. The heat dissipation device includes a fluid pump configured to pump cooling fluid through a plurality of conduits in thermal communication with the inverter, a first sensor configured to detect a fluid flow rate of cooling fluid at least one of the plurality of conduits and a second sensor configured to detect the temperature of the cooling fluid in at least one of the plurality of conduits. The refuse vehicle further includes a controller configured to receive data from the first sensor and second sensors and provide operating parameters to the heat dissipation device in response to receiving the data from the first and second sensor, wherein the controller is further configured to determine if the data from the first sensor is greater than a critical operating condition and shut down the electric power take-off system in response to determining that the data from the first sensor is greater than the critical operating condition.
Another exemplary embodiment relates to a method. The method includes providing power to one or more components a system of a refuse vehicle. The refuse vehicle includes a chassis supporting a plurality of wheels, a chassis battery supported by the chassis and configured to provide electrical power to a first motor, wherein rotation of the first motor selectively drives at least one of the plurality of wheels, a vehicle body supported by the chassis and defining a receptacle for storing refuse therein, and an electric power take-off system coupled to at least one of the chassis and the vehicle body, the electric power take-off system including a second motor configured to convert electrical power received from the chassis battery into hydraulic power, an inverter configured to provide electrical power to the second motor from the chassis battery, a heat dissipation device coupled to the inverter, wherein the heat dissipation device is configured to cool the inverter, a first sensor configured to detect thermal energy within the inverter, and a controller configured to receive data from the first sensor and provide operating parameters to the heat dissipation device, providing, by the controller, initial operating parameters to the one or more components of the system, receiving, by the controller, data from the first sensor, determining, by the controller, if the data from the first sensor is greater than a critical operating condition, and shutting down the one or more components of the system, by the controller, in response to determining the data received is greater than the critical operating condition.
The invention is capable of other embodiments and of being carried out in various ways. Alternative exemplary embodiments relate to other features and combinations of features as may be recited herein.
The disclosure will become more fully understood from the following detailed description, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements, in which:
Before turning to the figures, which illustrate the exemplary embodiments in detail, it should be understood that the present application is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.
Referring to the FIGURES generally, the various exemplary embodiments disclosed herein relate to electric refuse vehicles. Electric refuse vehicles, or E-refuse vehicles, include an onboard energy storage device, like a battery, that provides power to a motor that produces rotational power to drive the vehicle. The energy storage device, which is commonly a battery, can be used to provide power to different subsystems on the E-refuse vehicle. The energy storage device is also configured to provide hydraulic power to different subsystems on the E-refuse vehicle through an electric power take-off (E-PTO) system. Generally, power take-off (PTO) mechanisms are included on refuse vehicles to convert energy from a power source, such as an engine, to other systems on the truck, such as a hydraulic lifting system. However, here, the E-PTO system receives electrical power from the energy storage device and provides the electrical power to an electric motor. The electric motor drives a hydraulic pump that provides pressurized hydraulic fluid to different vehicle subsystems, including the compactor and the lifting system.
The E-PTO system may include an E-PTO controller. The E-PTO controller may monitor various systems within the refuse vehicle, including the E-PTO system. The E-PTO controller may receive data from sensors within the system, compare the data to expected values under normal operating conditions, adjust the operation parameters of components of the system, and determine if a critical operating condition exists based on the sensor data. Further, the E-PTO controller may shut down the system and/or the refuse vehicle in response to detecting a critical operating condition.
Referring to
According to an exemplary embodiment, the refuse vehicle 10 is configured to transport refuse from various waste receptacles within a municipality to a storage or processing facility (e.g., a landfill, an incineration facility, a recycling facility, etc.). As shown in
Referring again to the exemplary embodiment shown in
Referring to the exemplary embodiment shown in
Referring to
Still referring to
The refuse vehicle 10 can be considered a hybrid refuse vehicle as it includes both electric and hydraulic power systems. As depicted in
With continued reference to
The disconnect 200 further allows an all-electric vehicle chassis to be retrofit with hydraulic power systems, which can be advantageous for a variety of reasons, as hydraulic power systems may be more responsive and durable than fully electric systems. In some examples, the E-PTO system 100 includes a dedicated secondary battery 108 that is configured to supply electrical power to the E-PTO system 100 if the disconnect 200 is tripped, such that the secondary vehicle systems can remain optional even when the E-PTO system 100 is not receiving electrical power from the batteries 23. In some examples, the E-PTO system 100 operates independently of the battery 23, and includes its own dedicated secondary battery 108 that supplies DC electrical power to the inverter 110, which converts the DC electrical power to AC electrical power that can then be supplied to the electric motor 104. In still further embodiments, the dedicated secondary battery 108 is directly coupled to the electric motor 104 and supplies DC electrical power directly to the electric motor 104. With the secondary battery 108 present within the E-PTO system 100, the E-PTO system can be agnostic to the chassis type, and can be incorporated into all-electric, hybrid, diesel, CNG, or other suitable chassis types.
In certain embodiments, a heat dissipation device 112 is coupled to the inverter 110. The heat dissipation device 112 (e.g., a radiator, fan, etc.) is configured to draw heat away from the inverter 110 to reduce the risk of overheating. In certain embodiments, the heat dissipation device 112 is coupled to the inverter 110 via conduits. The conduits may be configured to transport a cooling fluid to and from the inverter 110. For example, the heat dissipation device may include a fluid pump configured to pump cooling fluid through the conduits. In certain embodiments, sensors may be positioned within or adjacent to the conduits. For example, the sensors may be configured to determine the flow rate of the cooling fluid through the conduits and/or the temperature of the cooling fluid flowing through the conduits, as will be discussed further below. It should be appreciated that the heat dissipation device 112 may also be coupled to various other components of the refuse vehicle 10.
Referring now to
In certain embodiments, each sensor 350 is configured to record data related to one or more onboard devices 360. For example, one or more a thermal sensors 350 may detect and record the temperature of the heat dissipation device 112 and/or the inverter 110. Further, one or more sensors 350 may be within or adjacent to the conduits that connects the heat dissipation device 112 to the inverter 110. In this example, the sensors 350, may determine the temperature (e.g., thermocouples, resistance temperature detectors, thermistors, semiconductor based on integrated circuits, etc.) and/or the fluid flow rate (e.g., a Coriolis meter, a differential pressure meter, a magnetic meter, a multiphase meter, a turbine meter, an ultrasonic meter, a vortex meter, a positive displacement meter, an electromagnetic flow meter, etc.) of the cooling fluid in the conduits. In certain embodiments, more than one sensor 350 is used to record data related to a single onboard device 360. For example, a thermal sensor 350 may detect and record the temperature of the inverter 110 and an electric flow sensor 350 may be used to record the current going into and/or out of the inverter 110.
In various embodiments, the E-PTO controller 320 is communicably coupled to sensor(s) 350, such that the data recorded by the sensor(s) 350 may be saved and analyzed. The E-PTO controller 320 is also communicably coupled to the onboard device(s) 360 such that the E-PTO controller 320 may control the onboard device(s) 360 (e.g., by sending operating parameters to the onboard devices). In certain embodiments, the E-PTO controller 320 includes a network interface circuit 301 configured to enable the E-PTO controller 320 to exchange information over a network. The network interface circuit 301 can include program logic that facilitates connection of the E-PTO controller 320 to the network (e.g., a cellular network, Wi-Fi, Bluetooth, radio, etc.). The network interface circuit 301 can support communications between the E-PTO controller 320 and other systems, such as a remote monitoring computing system. For example, the network interface circuit 301 can include a cellular modem, a Bluetooth transceiver, a radio-frequency identification (RFID) transceiver, and a near-field communication (NFC) transmitter. In some embodiments, the network interface circuit 301 includes the hardware and machine-readable media sufficient to support communication over multiple channels of data communication.
The E-PTO controller 320 is shown to include a processing circuit 302 and a user interface 314. The processing circuit 302 may include a processor 304 and a memory 306. The processor 304 may be coupled to the memory 306. The processor 304 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. The processor 304 is configured to execute computer code or instructions stored in the memory 306 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).
The memory 306 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory 306 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memory 306 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memory 306 may be communicably connected to the processor 304 via processing circuit 302 and may include computer code for executing (e.g., by the processor 304) one or more of the processes described herein.
The data collection circuit 308 is configured to collect and store data collected by the sensor(s) 350. For example, the data collection circuit 308 may collect data during operation of the refuse vehicle 10, and store the data. Further, the collection circuit 308 is configured to store operating parameters that the E-PTO controller 320 may provide to onboard devices 360 to control the onboard devices 360. For example, the E-PTO controller 320 may provide operating parameters to the heat dissipation device 112 such that the E-PTO controller 320 may control the cooling fluid flow rate through the conduits. The operating parameters, for example, may be used to control the fluid pump within the heat dissipation device 112. For example, the operating parameters may increase or decrease the pumping rate of the fluid pump, thereby increasing or decreasing the flow rate of cooling fluid through the conduits. The data collection circuit 308 may also store normal operating conditions corresponding to each sensor 350. For example, the normal operating conditions may include a range of values measured by each sensor 350 that indicates an onboard device 360 is operating properly. For example, if initial operating parameters are provided to an onboard device 360, the normal operating conditions may be the expected senor 350 reading taken with respect to that onboard device 360. Further, the data collection circuit 308 is configured to store threshold measurements for each sensor 350. Each sensor 350 may have a different threshold measurement. In certain embodiments, the threshold measurement may represent both an upper threshold measurement (i.e., the upper bound) and a lower threshold measurement (i.e., a lower bound), such that a sensor 350 measurement below the lower bound or above the upper bound may be indicative of a critical event. The threshold measurement may represent a maximum (i.e., upper bound) and/or minimum acceptable (i.e., lower bound) value that may be detected by a sensor 350. The threshold measurement may depended on each onboard device's 360 demands (i.e., the onboard device 360 that the sensor 350 is monitoring). For example, a sensor 350 may be used to measure the cooling fluid temperature exiting the heat dissipation device 112. A predetermined threshold measurement may be defined for the sensor 350 and if the sensor 350 measures a reading above that threshold measurement, the E-PTO controller 320 may detect a critical operation. For example, the predetermined threshold measurement for the sensor 350 may represent the maximum acceptable temperature that the cooling fluid may safely reach without risking damage to the inverter 110 or the heat dissipation device 112. In another example, a sensor 350 may be used to measure the flow rate of the cooling fluid through the inverter 110. The threshold measurement for the sensor 350 may correspond with the minimum acceptable flow rate of the cooling fluid. For example, if the flow rate dropped below the threshold measurement, the inverter 110 or heat dissipation device 112 may be damaged.
The detection circuit 310 is configured to receive signals from sensor(s) 350 and compare this data to the data stored by the data collection circuit 308. For example, the detection circuit 310 may be able to identify if various components in a system (e.g., the E-PTO system 100, the lifting system 30, the compactor 50, subsystems 106, etc.) is in compliance (i.e., operating within the normal operating condition bounds). The detection circuit 322 is also configured to determine if a sensor 350 reading exceeds the threshold measurement. For example, detection circuit 310 may determine the presence of a critical operating condition if a sensor 350 detects the temperature of the inverter 110, or a region thereof, exceeds a predetermined threshold temperature. In some embodiments, detection circuit 310 detects a location of a critical operating condition. For example, detection circuit 310 may determine a critical operating condition is occurring in the inverter 110 because a sensor 350 detecting a temperature over the threshold temperature located proximate the inverter 110. In some embodiments, if the detection circuit 310 detects a critical operating condition, the critical operating condition, and the circumstances surrounding it, is communicated to the alerting circuit 312.
Alerting circuit 312 is configured to perform one or more operations in response to receiving an indication of a critical operating condition. In some embodiments, alerting circuit 312 presents an indication of the critical operating condition to an operator of refuse vehicle 10. For example, alerting circuit 312 may control a user interface 314 to display a warning to an operator of refuse vehicle 10.
The user interface 314 is configured to present information to and receive information from a user. In some embodiments, user interface 314 includes a display device (e.g., a monitor, a touchscreen, hud, etc.). In some embodiments, user interface 314 includes an audio device (e.g., a microphone, a speaker, etc.). In various embodiments, user interface 314 receives alerts from alerting circuit 312 and presents the alerts to an operator of refuse vehicle 10. For example, user interface 314 may receive a visual alert from alerting circuit 312 and display a graphic on a display device to alert an operator of refuse vehicle 10 of a critical operating condition and the location of the critical operating condition associated with the refuse vehicle 10.
In some embodiments, alerting circuit 312 operates refuse vehicle 10. For example, alerting circuit 312 may cause the E-PTO system 100 to shut down in response to a critical operating condition being detected with respect to a component of the E-PTO system 100. For example, if the cooling fluid flow rate through the inverter 110 is sensed (i.e., by a sensor 350) to be below a threshold measurement (i.e., as determined by the detection circuit 310), the alerting circuit 312 may cause the entire E-PTO system 100 to be shut down. Further, the alerting circuit 312 may cause the entire refuse vehicle 10 to shut down in response receiving an indication of a critical operating condition. Additionally or alternatively, alerting circuit 312 may transmit one or more notifications. For example, alerting circuit 213 may transmit a notification to the network interface circuit 301, such that a notification may be sent via the network to a fleet monitoring system that monitors the status of various refuse vehicles 10.
Referring now to
Once power is provided to the system as a part of process 402, initial operating parameters may be provided to the system components as a part of process 404. For example, the E-PTO controller 320 may provide initial operating parameters to the system components. The initial operating parameters may correspond with expected performance characteristics of the system. For example, an initial operating parameter may be provided to the heat dissipation device 112 that defines a specific power input into a pump included in the heat dissipation device. The specific power input may correspond with an expected cooling fluid flow rate through the heat dissipation device 112. For example, a greater specific power input (i.e., as defined by the operating parameter) into the pump may lead to a higher the expected cooling fluid flow rate through the heat dissipation device 112. The initial operating parameters may be predetermined based on modeling, testing, and/or prior performance of the system.
After the initial operating parameters are provided to the system components, the E-PTO controller 320 checks to see if the system is in compliance at process 406. For example, the E-PTO controller 320 controller may receive data from sensor(s) 350 monitoring the various components of the system. The detection circuit 310 may then compare the data from the sensor(s) to normal operating conditions stored in the data collection circuit 308 to determine if the sensor readings are within the normal operating conditions bounds. If so, the system may be determined to be in compliance at decision 408. If not, the system may be determined to not be in compliance at decision 408. If the system is in compliance, power may continue to be supplied to the system as a part of process 420, allowing the system to continue to operate. Data may continue to be collected by the sensor(s) 350, and the process 400 may return to process 406 such that the E-PTO controller 320 may continue to monitor the system to ensure that the system is in compliance.
If the detection circuit 310 determines that the system is not in compliance at decision 408, the process 400 may proceed to process 410. At process 410, the source of the irregularity is determined. For example, the E-PTO controller 320 may be able to determine the source of irregularity based on which sensor(s) 350 are collecting data outside the normal operation bounds. For example, if a heat sensor 350 is configured to measure the temperature of the inverter 110, and the inverter 110 temperature exceeds the normal operating temperature upper bound, then the detection circuit 310 may determine the source of the irregularity to be the heat dissipation device 112 because the heat dissipation device 112 is configured to cool the inverter 110. However, the detection circuit 310 may also analyze the data from sensors 350 configured to monitor the heat dissipation device 112. For example, if a flow meter sensor 350 indicates that the fluid flow rate of the cooling fluid is within the normal operating bounds and a heat sensor 350 indicates that the cooling fluid is at a temperature within the normal operating bounds, then the detection circuit 310 may determine that the source of irregularity is the inverter 110. Once the source of irregularity is determined as a part of process 410, the irregularity is analyzed at process 412.
Process 412 includes analyzing the irregularity. For example, the detection circuit 310 may compare the irregular data received from the sensor 350 and compare this to the expected data for normal operating conditions. The detection circuit 310 may then analyze the irregularity to determine if the data is greater than the upper bound of normal operating conditions or less than the lower bound of normal operating conditions. Once this is determined, the detection circuit 310 may determine updated operating parameters at process 414. For example, if a heat sensor 350 coupled to the inverter provides the detection circuit 310 with a temperature reading that is greater than the upper bound of the normal operating conditions, analyzing this irregularity at process 412 may indicate that a higher cooling fluid flow rate from the heat dissipation device 112 may be needed. Thus, the detection circuit 310 may update the operating parameter for the heat dissipation device 112 to increase the amount of power being supplied to the pump within the heat dissipation device 112 such that the cooling fluid flow rate increases, which may be confirmed by a flow rate sensor 350 in the conduit connecting the heat dissipation device 112 to the inverter 110. After updating the operating parameters, the detection circuit 310 may continue to monitor data from the sensor(s) 350. This data may then be analyzed at decision 416 to determine if a threshold is exceeded (i.e., a critical operating condition exists). For example, an upper critical operating condition bound and a lower critical operating condition bound may exist for each sensor 350. The upper critical operating bound may be higher than the upper normal operating bound and the lower critical operating bound may be less than the lower normal operating bound.
If it is determined that the threshold is not exceed at decision 416, the process 400 returns to decision 408 to determine if the system is in compliance. If not, process 410, 412, and 414 may be repeated, thereby creating a feedback loop (e.g., a PID feedback control loop) in an attempt to bring the system within the bounds of the normal operating conditions. However, if it is determined that a threshold is exceeded at decision 416, the detection circuit 310 may send an indication of the critical operating condition to the alerting circuit 312. The alerting circuit may then cause the system or any components thereof to shut down as a part of process 418. Further, the alerting circuit 312 may cause the entire refuse vehicle 10 to shut down in response to receiving an indication of a critical operating condition.
Referring now to
The motor control process 500 may begin at process 501. For example, an operator of the refuse vehicle 10 may input controls to activate the prime mover 20 as a part of operating the refuse vehicle 10. Upon receiving the input to control the prime mover 20 at process 501, the E-PTO controller 320 may ensure that the motor is off (e.g., operating at 0 RPMs) at process 502. For example, based on data received from one or more sensors 350, the E-PTO controller 320 may determine if the motor is off. For example, the refuse vehicle 10 may include a sensor 350 configured to read an output (e.g., RPMs) of the prime mover 20. If the data from the one or more sensors indicates that the motor is not off, the E-PTO controller 320 may provide a command (e.g., to the inverter 110) to shut down the motor. If the one or more sensors 350 indicate that the motor is already off, then the motor control process 500 may proceed to process 504.
At process 504, system compliance (e.g., compliance of the onboard device(s) 360) is verified before starting the motor. For example, based on data from one or more sensors 350, the E-PTO controller 320 may determine whether the system is in compliance before starting the motor. In this sense, process 504 may be the same or similar to process 406 described above. Process 504 may include checking a plurality of system parameters for compliance based on the data received from the one or more sensors 350. For example, the E-PTO controller 320 may receive data from one or more sensor 350 that is thermally coupled to the inverter 110 and/or a cooling system (e.g., a heat dissipation device 112). For example, the E-PTO controller 320 may determine whether the temperature of the inverter is lower than a safe critical temperature (e.g., 80 degrees Celsius). If the E-PTO controller 320 determines that one or more system parameters are not in compliance, the motor may be shut down and the motor control process 500 may return to process 502. However, if the system parameters are in compliance, the motor control process 500 may proceed to process 506.
At process 506, the motor is begins turning on (e.g., operating at greater than 0 RMPs). For example, the E-PTO controller 320 may provide command instructions to the prime mover 20 (e.g., by controlling the inverter 110) in response to determining that one or more systems (e.g., the onboard device(s) 360) are in compliance. In response to determining system compliance (e.g., inverter temperature is less than 80 degrees Celsius), the E-PTO Controller 320 may cause the motor to start. A sensor 350 may be coupled to the motor such that a motor output (e.g., the motor RPMs) may be monitor. The motor output data may be provided to the E-PTO controller 320 such that performance of the motor may be monitored by the E-PTO controller 320. For example, the E-PTO controller 320 may control the inverter 110 and monitor the motor output of the prime mover 20. In this sense, a feedback control loop is formed to control the prime mover 20 and the motor included in the prime mover 20.
At process 508, the motor continues to operate in the on condition. For example, the motor may be a part of the prime mover 20, which is being used during a lifting event. As a part of the lifting event, the motor may provide the power needed to perform the necessary lifting. During process 508, several events may cause the motor to turn off (i.e., the motor control process 500 returns to process 502). For example, if the vehicle 10 includes an engine, and the engine ignition is on, the E-PTO controller 320 may cause the motor to shut down in response. In this sense, the motor may not operate when the vehicle 10 is being driven. Similarly, if the E-PTO controller 320 determines that the vehicle 10 is moving (e.g., the speed exceeds a pre-determined threshold), the E-PTO controller 320 may cause the motor to shut down in response. Further, if an operator of the vehicle 10 inputs a manual stop (e.g., an emergency stop), the E-PTO controller 320 may cause the motor to shut down. Further, if the E-PTO controller 320 determines that the prime mover 20 is no longer in use (e.g., the access door to the refuse storage compartment is closed), the E-PTO controller 320 may cause the motor to shut down in response.
At process 510, the motor enters shut down mode. For example, the E-PTO controller 320 may gradually reduce the power supply to the motor (e.g., via the inverter 110) until the engine output is zero (e.g., the engine RPMs read by a sensor 350 is zero or substantially 0). For example, if the E-PTO controller 320 determines that one or more systems are no longer in compliance, the E-PTO controller 320 may cause the motor to enter shut down mode. For example, if the cooling system (e.g., the heat dissipation device 112) is determined to be over a critical temperature or if there is an inadequate volume of cooling fluid flowing through cooling system, then the E-PTO controller 320 may cause the motor to enter shut down mode. Further, the operator of the vehicle 10 may input a stop command into the E-PTO controller 320 (e.g., via a graphical user interface), which may cause the motor to enter shut down mode. Furthermore, if the motor output drops below a critical value (e.g., RPMs below 2,400) for a critical time period (e.g., 2 seconds), then the E-PTO controller 320 may cause the motor to enter shut down mode. The engine output may be monitored by the E-PTO controller 320 (e.g., by analyzing data from one or more sensor 350) to ensure the engine output is zero. Once the motor output is zero, the motor control process 500 returns to process 502.
Referring now to
The thermal management process 600 may begin at process 601. For example, at process 601, the vehicle 10 and/or any of the onboard devices 360 may be off. After process 601, the thermal management process 600 proceeds to process 602. At process 602, the thermal management system is off. For example, the E-PTO controller 320 may have caused the thermal management system to shut down, or the thermal management system may not have been active by the E-PTO controller. Alternatively, the entire vehicle 10 may be off. According to various embodiments, at process 602, the pump (e.g., a thermal pump that is a part of the heat dissipation device 112) may be in the off state. The pumps status may be determined by the E-PTO controller 320 based on data from one or more sensors 350 (e.g., a flow sensor configured to measure the fluid flow rate of cooling fluid through the pump, a pump output sensor configured to measure the pump output in RPMs, etc.)
At process 604, the thermal management system begins to start up. Process 604 may include turning on the vehicle 10 ignition and/or any of the onboard devices 360. For example, once the vehicle 10 and/or any of the onboard devices 360 are turned on, the E-PTO controller 320 may cause the thermal management system to turn on to maintain safe operating conditions of the vehicle 10. Process 604 may further involve activating the pump (e.g., a thermal pump that is a part of the heat dissipation device 112). For example, the E-PTO controller 320 may cause the pump to turn on. As a part of starting up, the E-PTO controller may gradually ramp up the power to the pump. According to various embodiments, at process 604, the pump ramps up the pump output to 40% of a maximum pump output in two seconds. According to various embodiments, one or more sensors 350 may be coupled to the pump such that the E-PTO controller 320 can determine a pump output (e.g., fluid flow rate, RPMs, etc.).
At process 606, the thermal management system continues to operate. For example, as the vehicle 10 ignition remains on and communication between the E-PTO controller 320 and the pump is maintained, the thermal management system may continue to operate. According to various embodiments, the E-PTO controller 320 may monitor the pump output (e.g., cooling fluid flow rate) to ensure the thermal management system is in compliance. For example, according to various embodiments, the E-PTO controller 320 will ensure that the fluid flow rate of the cooling fluid through the thermal management system is above a minimum threshold (e.g., 5 liters per minute). Once this minimum flow rate is confirmed by the E-PTO controller 320, the E-PTO controller 320 may cause the pump to modulate the pump output (e.g., RPMs) based on a detected fluid flow rate (e.g., as detected by one or more sensors 350) to increase the fluid flow rate of the cooling fluid to an operating flow rate (e.g., to 10 liters per minute). According to various embodiments, as the E-PTO controller 320 confirms that the thermal management system is running and in compliance, the E-PTO controller will allow the inverter 110 and motor to be turned on (e.g., as a part of motor control process 500 described above.).
At process 608, a thermal management system error is detected. For example, at process 608, communication between the E-PTO controller 320 and some or all components of the thermal management system (e.g., the heat dissipation device 112, the pump, a fan, etc.) may be lost, the fluid flow rate of the cooling fluid in the thermal management system may drop below the minimum threshold (e.g., 5 liters per minute), and/or the temperature of the cooling fluid may be above a threshold temperature (e.g., 60 degrees Celsius) may cause a thermal management system error to be detected. For example, one or more sensors 350 may provide data to the E-PTO controller 320 such that the E-PTO controller 320 may determine if a thermal management error system error exists.
In response to determining a thermal management system error exists, the E-PTO controller 320 may turn off the inverter 110 and the motor coupled to the invertor (e.g., process 520). For example, if the ignition is turned off, the thermal management control process 600 may proceed to process 610 as is discussed further below.
Alternatively, if the ignition of the vehicle remains on and the inverter 110 and the motor are still on, the E-PTO controller 320 may modulate the pump included in the thermal management system to cause a change in the fluid flow rate of the cooling fluid in the thermal management system in response to detecting a thermal management system error. Further, the E-PTO controller 320 may monitor the temperature of the cooling fluid in the thermal management system. For example, if the cooling fluid temperature is below a first threshold (e.g., 30 degrees Celsius), then the thermal management control process 600 may proceed to process 612 as discussed further below. However, if the cooling fluid temperature is above a critical threshold (e.g., 50 degrees Celsius), then the thermal management control process 600 may proceed to process 610 as is discussed further below.
According to various embodiments, the thermal management control process 600 may return to process 606 after a thermal management system error is detected if the E-PTO controller 320 subsequently determines that the thermal management system returns to compliance. For example, if the E-PTO controller 320 determines that communication between the E-PTO controller 320 and some or all components of the thermal management system (e.g., the heat dissipation device 112, the pump, a fan, etc.) has been restored, the fluid flow rate of the cooling fluid in the thermal management system is above the minimum threshold (e.g., 5 liters per minute), and/or the temperature of the cooling fluid may be below a threshold temperature (e.g., 60 degrees Celsius), the thermal management control process 600 may return to process 606 and the thermal management system may continue to operate.
At process 610, the thermal management system begins a delayed shut down. As a part of the delayed shut down, some or all components of the thermal management system may gradually be ramped down in power and eventually shut down. For example, an operator of the vehicle may enter an input (e.g., into a graphical user interface) which may cause the E-PTO controller 320 to begin a delayed shut down of the thermal management system. Further, process 610 may begin once the E-PTO controller 320 determines that the vehicle ignition has been shut down for a period of time (e.g., 1 minute). Further, process 610 may begin once the E-PTO controller 320 determines that the inverter 110 and the motor have not been running for a period of time (e.g., 5 minutes) and the coolant temperature is above a critical temperature (e.g., 50 degrees C.). Furthermore, process 610 may begin once the E-PTO controller 320 determines that the inverter 110 and the motor are not running and the coolant temperature is below a threshold (e.g., 30 degrees Celsius). In this example embodiment, the thermal management may shut down instantly, as opposed to a delayed shut down.
After process 610, the thermal management system may completely shut down at process 612. At process 612, the E-PTO controller 320 may cause the entire thermal management system to shut down. For example, the E-PTO controller 320 may shut down the pump. Further, the E-PTO controller 320 may shut down the inverter 110 and/or the motor. Furthermore, the E-PTO controller 320 may shut down the fan. According to various embodiments, the E-PTO controller 320 will only shut down the fan if the ignition is off as a part of process 610.
Although this description may discuss a specific order of method steps, the order of the steps may differ from what is outlined. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accompli shed with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.
As utilized herein, the terms “approximately”, “about”, “substantially”, and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the invention as recited in the appended claims.
It should be noted that the term “exemplary” as used herein to describe various embodiments is intended to indicate that such embodiments are possible examples, representations, and/or illustrations of possible embodiments (and such term is not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
The terms “coupled,” “connected,” and the like, as used herein, mean the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent, etc.) or moveable (e.g., removable, releasable, etc.). Such joining may be achieved with the two members or the two members and any additional intermediate members being integrally formed as a single unitary body with one another or with the two members or the two members and any additional intermediate members being attached to one another.
References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below,” “between,” etc.) are merely used to describe the orientation of various elements in the figures. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
It is important to note that the construction and arrangement of the electromechanical variable transmission as shown in the exemplary embodiments is illustrative only. Although only a few embodiments of the present disclosure have been described in detail, those skilled in the art who review this disclosure will readily appreciate that many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.) without materially departing from the novel teachings and advantages of the subject matter recited. For example, elements shown as integrally formed may be constructed of multiple parts or elements. It should be noted that the elements and/or assemblies of the components described herein may be constructed from any of a wide variety of materials that provide sufficient strength or durability, in any of a wide variety of colors, textures, and combinations. Accordingly, all such modifications are intended to be included within the scope of the present inventions. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the preferred and other exemplary embodiments without departing from scope of the present disclosure or from the spirit of the appended claims.
This Application is a continuation of U.S. patent application Ser. No. 17/327,336, filed May 21, 2021, which claims priority to U.S. Provisional Patent Application No. 63/084,415, filed Sep. 28, 2020, the content of which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6105984 | Schmitz et al. | Aug 2000 | A |
6516914 | Andersen et al. | Feb 2003 | B1 |
6757597 | Yakes et al. | Jun 2004 | B2 |
6882917 | Pillar et al. | Apr 2005 | B2 |
6885920 | Yakes et al. | Apr 2005 | B2 |
7164977 | Yakes et al. | Jan 2007 | B2 |
7277782 | Yakes et al. | Oct 2007 | B2 |
7302320 | Nasr et al. | Nov 2007 | B2 |
7357203 | Morrow et al. | Apr 2008 | B2 |
7379797 | Nasr et al. | May 2008 | B2 |
7392122 | Pillar et al. | Jun 2008 | B2 |
7439711 | Bolton | Oct 2008 | B2 |
7448460 | Morrow et al. | Nov 2008 | B2 |
7451028 | Pillar et al. | Nov 2008 | B2 |
7520354 | Morrow et al. | Apr 2009 | B2 |
7521814 | Nasr | Apr 2009 | B2 |
7689332 | Yakes et al. | Mar 2010 | B2 |
7711460 | Yakes et al. | May 2010 | B2 |
7756621 | Pillar et al. | Jul 2010 | B2 |
7848857 | Nasr et al. | Dec 2010 | B2 |
7931103 | Morrow et al. | Apr 2011 | B2 |
7937194 | Nasr et al. | May 2011 | B2 |
8000850 | Nasr et al. | Aug 2011 | B2 |
8139109 | Schmiedel et al. | Mar 2012 | B2 |
8333390 | Linsmeier et al. | Dec 2012 | B2 |
8337352 | Morrow et al. | Dec 2012 | B2 |
8561735 | Morrow et al. | Oct 2013 | B2 |
8864613 | Morrow et al. | Oct 2014 | B2 |
8947531 | Fischer et al. | Feb 2015 | B2 |
9008913 | Sears et al. | Apr 2015 | B1 |
9045014 | Verhoff et al. | Jun 2015 | B1 |
9061169 | Linsmeier | Jun 2015 | B2 |
9114804 | Shukla et al. | Aug 2015 | B1 |
9132736 | Shukla et al. | Sep 2015 | B1 |
9174686 | Messina et al. | Nov 2015 | B1 |
9315210 | Sears et al. | Apr 2016 | B2 |
9376102 | Shukla et al. | Jun 2016 | B1 |
9420203 | Broggi et al. | Aug 2016 | B2 |
9428042 | Morrow et al. | Aug 2016 | B2 |
9452750 | Shukla et al. | Sep 2016 | B2 |
9493921 | Amin et al. | Nov 2016 | B2 |
9656640 | Verhoff et al. | May 2017 | B1 |
9707869 | Messina et al. | Jul 2017 | B1 |
9821789 | Shukla et al. | Nov 2017 | B2 |
9981803 | Davis et al. | May 2018 | B2 |
10029556 | Morrow et al. | Jul 2018 | B2 |
D843281 | Gander et al. | Mar 2019 | S |
10220725 | Rush et al. | Mar 2019 | B2 |
10315643 | Shukla et al. | Jun 2019 | B2 |
10392000 | Shukla et al. | Aug 2019 | B2 |
10414067 | Datema et al. | Sep 2019 | B2 |
10434995 | Verhoff et al. | Oct 2019 | B2 |
10457134 | Morrow et al. | Oct 2019 | B2 |
D869332 | Gander et al. | Dec 2019 | S |
D871283 | Gander et al. | Dec 2019 | S |
10544556 | Amin et al. | Jan 2020 | B2 |
D888629 | Gander et al. | Jun 2020 | S |
10800605 | Rocholl et al. | Oct 2020 | B2 |
10843379 | Rocholl et al. | Nov 2020 | B2 |
10843549 | Morrow et al. | Nov 2020 | B2 |
D905713 | Linsmeier et al. | Dec 2020 | S |
10859167 | Jax et al. | Dec 2020 | B2 |
D907544 | Wall et al. | Jan 2021 | S |
10901409 | Datema et al. | Jan 2021 | B2 |
D909934 | Gander et al. | Feb 2021 | S |
10940610 | Clifton et al. | Mar 2021 | B2 |
10987829 | Datema et al. | Apr 2021 | B2 |
10997802 | Koga et al. | May 2021 | B2 |
11001135 | Yakes et al. | May 2021 | B2 |
11001440 | Rocholl et al. | May 2021 | B2 |
11007863 | Yakes et al. | May 2021 | B2 |
11021078 | Rocholl et al. | Jun 2021 | B2 |
11042745 | Wildgrube et al. | Jun 2021 | B2 |
11042750 | Wildgrube et al. | Jun 2021 | B2 |
11046329 | Clifton et al. | Jun 2021 | B2 |
11052899 | Shukla et al. | Jul 2021 | B2 |
11059436 | Wildgrube et al. | Jul 2021 | B2 |
11097617 | Rocholl et al. | Aug 2021 | B2 |
20030195680 | Pillar | Oct 2003 | A1 |
20050113988 | Nasr et al. | May 2005 | A1 |
20050113996 | Pillar et al. | May 2005 | A1 |
20050119806 | Nasr et al. | Jun 2005 | A1 |
20060065451 | Morrow et al. | Mar 2006 | A1 |
20060066109 | Nasr | Mar 2006 | A1 |
20060106521 | Nasr et al. | May 2006 | A1 |
20070088469 | Schmiedel et al. | Apr 2007 | A1 |
20080059014 | Nasr et al. | Mar 2008 | A1 |
20080071438 | Nasr et al. | Mar 2008 | A1 |
20080150350 | Morrow et al. | Jun 2008 | A1 |
20090194347 | Morrow et al. | Aug 2009 | A1 |
20100116569 | Morrow et al. | May 2010 | A1 |
20100301668 | Yakes et al. | Dec 2010 | A1 |
20110312459 | Morrow et al. | Dec 2011 | A1 |
20120205178 | Heine | Aug 2012 | A1 |
20130196806 | Morrow et al. | Aug 2013 | A1 |
20150283894 | Morrow et al. | Oct 2015 | A1 |
20160001765 | Shukla et al. | Jan 2016 | A1 |
20160145880 | Mapelli | May 2016 | A1 |
20160176297 | Kouvo | Jun 2016 | A1 |
20160257293 | Takahashi et al. | Sep 2016 | A1 |
20160297417 | Shukla et al. | Oct 2016 | A1 |
20160338221 | Rush et al. | Nov 2016 | A1 |
20160361987 | Morrow et al. | Dec 2016 | A1 |
20170008507 | Shukla et al. | Jan 2017 | A1 |
20180072303 | Shukla et al. | Mar 2018 | A1 |
20180265289 | Davis et al. | Sep 2018 | A1 |
20180345783 | Morrow et al. | Dec 2018 | A1 |
20190039407 | Smith | Feb 2019 | A1 |
20190185077 | Smith et al. | Jun 2019 | A1 |
20190193934 | Rocholl et al. | Jun 2019 | A1 |
20190291711 | Shukla et al. | Sep 2019 | A1 |
20190322321 | Schwartz et al. | Oct 2019 | A1 |
20190344475 | Datema et al. | Nov 2019 | A1 |
20190351883 | Verhoff et al. | Nov 2019 | A1 |
20190381990 | Shukla et al. | Dec 2019 | A1 |
20200039341 | Morrow et al. | Feb 2020 | A1 |
20200230841 | Datema et al. | Jul 2020 | A1 |
20200230842 | Datema et al. | Jul 2020 | A1 |
20200262366 | Wildgrube et al. | Aug 2020 | A1 |
20200265656 | Koga et al. | Aug 2020 | A1 |
20200316816 | Messina et al. | Oct 2020 | A1 |
20200317083 | Messina et al. | Oct 2020 | A1 |
20200346547 | Rocholl et al. | Nov 2020 | A1 |
20200346556 | Rocholl et al. | Nov 2020 | A1 |
20200346557 | Rocholl et al. | Nov 2020 | A1 |
20200346657 | Clifton et al. | Nov 2020 | A1 |
20200346854 | Rocholl et al. | Nov 2020 | A1 |
20200346855 | Rocholl et al. | Nov 2020 | A1 |
20200346856 | Rocholl et al. | Nov 2020 | A1 |
20200346857 | Rocholl et al. | Nov 2020 | A1 |
20200346858 | Buege et al. | Nov 2020 | A1 |
20200346859 | Buege et al. | Nov 2020 | A1 |
20200346860 | Buege et al. | Nov 2020 | A1 |
20200346861 | Rocholl et al. | Nov 2020 | A1 |
20200346862 | Rocholl et al. | Nov 2020 | A1 |
20200347659 | Rocholl et al. | Nov 2020 | A1 |
20200347661 | Rocholl et al. | Nov 2020 | A1 |
20200347857 | Clifton et al. | Nov 2020 | A1 |
20200348681 | Clifton et al. | Nov 2020 | A1 |
20200348764 | Clifton et al. | Nov 2020 | A1 |
20200398670 | Rocholl et al. | Dec 2020 | A1 |
20200398695 | Rocholl et al. | Dec 2020 | A1 |
20200398697 | Rocholl et al. | Dec 2020 | A1 |
20200398772 | Wildgrube et al. | Dec 2020 | A1 |
20200399057 | Rocholl et al. | Dec 2020 | A1 |
20200399058 | Rocholl et al. | Dec 2020 | A1 |
20210031611 | Yakes et al. | Feb 2021 | A1 |
20210031612 | Yakes et al. | Feb 2021 | A1 |
20210031649 | Messina et al. | Feb 2021 | A1 |
20210054942 | Jax et al. | Feb 2021 | A1 |
20210069934 | Rocholl et al. | Mar 2021 | A1 |
20210088036 | Schubart et al. | Mar 2021 | A1 |
20210107483 | Shively et al. | Apr 2021 | A1 |
20210124347 | Datema et al. | Apr 2021 | A1 |
20210143663 | Bolton | May 2021 | A1 |
20210162630 | Clifton et al. | Jun 2021 | A1 |
20210188076 | Morrow et al. | Jun 2021 | A1 |
20210206372 | Shively et al. | Jul 2021 | A1 |
20210213642 | Datema et al. | Jul 2021 | A1 |
20210221216 | Yakes et al. | Jul 2021 | A1 |
20210225095 | Koga et al. | Jul 2021 | A1 |
20210229320 | Datema et al. | Jul 2021 | A1 |
20210229755 | Schwartz et al. | Jul 2021 | A1 |
20210229908 | Rocholl et al. | Jul 2021 | A1 |
Number | Date | Country | |
---|---|---|---|
20220097527 A1 | Mar 2022 | US |
Number | Date | Country | |
---|---|---|---|
63084415 | Sep 2020 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17327336 | May 2021 | US |
Child | 17509773 | US |