VEHICLE CONTROL SYSTEM

A refuse vehicle can include a battery, a display device, a door, and a control system. The batter can power the refuse vehicle. The display device can display one or more user interfaces. The control system can include one or more memory devices. The one or more memory devices can store instructions that can cause, when executed by one or more processors, the one or more processors to determine a state of charge of the battery, detect that the door has moved from a first position to a second position, and transmit a control signal to the display device causing the display device to display a user interface including the state of charge of the battery.

BACKGROUND

Refuse vehicles collect a wide variety of waste, trash, and other material from residences and businesses. Operators of the refuse vehicles transport the material from various waste receptacles within a municipality to a storage or processing facility (e.g., a landfill, an incineration facility, a recycling facility, etc.).

SUMMARY

One embodiment relates to a refuse vehicle. The refuse vehicle can include a battery. The battery can power the refuse vehicle. The refuse vehicle can also include a display device. The display device can display one or more user interfaces. The refuse vehicle can also include a door. The refuse vehicle can also include a control system. The control system can include one or more memory devices. The one or more memory devices can store instructions. The instructions, when executed by one or more processors, can cause the one or more processors to determine a state of charge of the battery. The instructions can also cause the one or more processors to detect that the door has moved from a first position to a second position. The instructions can also cause the one or more processors to transmit, responsive to detecting that the door has moved from the first position to the second position, a control signal to the display device causing the display device to display a user interface including the state of charge of the battery. The display device can display the user interface for a predetermined amount of time.

In some embodiments, the instructions can also cause the one or more processors to determine that the battery is electrically coupled with a power source. The instructions can also cause the one or more processors to transmit, responsive to detecting that the battery is electrically coupled with the power source, a second control signal to the display device causing the display device to update the user interface to include an indication that the battery is charging.

In some embodiments, the display device can be disposed within a center console of the refuse vehicle.

In some embodiments, the user interface can include an indication that the refuse vehicle is electrically coupled with a power source, and a prompt to decouple the refuse vehicle from the power source prior to operation of the refuse vehicle.

In some embodiments, the instructions can also cause the one or more processors to determine that the refuse vehicle is in a first operation status. The instructions can also cause the one or more processors to transmit, based on the first operation status and responsive to detecting that the door has moved from the first position to the second position, the control signal to the display device.

In some embodiments, the refuse vehicle can also include a sensor and an implement. The instructions can also cause the one or more processors to receive, from the sensor, a set operational data associated with the refuse vehicle. The instructions can also cause the one or more processors to determine, using the set of operational data, that the refuse vehicle is operating in a first mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a second control signal to the display device causing the display device to update the user interface to include a first view of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a third control signal to the implement, wherein the third control signal prevents operation of the implement.

In some embodiments, the instructions can also cause the one or processors to receive, from the sensor, a second set of operational data associated with the refuse vehicle. The instructions can also cause the one or more processors to determine, using the second set of operational data, that the refuse vehicle is operating in a second mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the second mode; a fourth control signal to the display device causing the display device to update the user interface to include a second view of the refuse vehicle. The first view of the refuse vehicle and the second view of the refuse vehicle can be different.

In some embodiments, the instructions can also cause the one or more processors to determine that that refuse vehicle is operating in a second mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the second mode, a fourth control signal to the implement, wherein the third control signal enables operation of the implement.

In some embodiments, the refuse vehicle can include a sensor and an audio device. The instructions can also cause the one or more processors to receive, from the sensor, a set of operational data associated with operation of the refuse vehicle. The instructions can also cause the one or more processors to determine, using the set of operation data and a predetermined set of operational data, a difference that indicates a deviation in operation of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to determination of the difference, a second control signal to the audio device causing the audio device to produce an audible alert to indication the deviation in the operation of the refuse vehicle.

In some embodiments, the refuse vehicle can include a climate system. The climate system can control an environmental condition of the refuse vehicle. The refuse vehicle can also include a steering wheel. The steering wheel can include an input device. The input device can be associated with an aspect of the environmental condition of the refuse vehicle. The instructions can also cause the one or more processors to detect a first interaction with the input device, the first interaction indicating a value pertaining to the aspect of the environmental condition of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to detecting the first interaction, a second control signal to the climate system causing the climate system to control the environmental condition of the refuse vehicle to reflect the value pertaining to the aspect of the environmental condition of the refuse vehicle.

In some embodiments, the refuse vehicle can include an implement. The implement can perform an action associated with operation of the refuse vehicle. The refuse vehicle can also include a steering wheel. The steering wheel can include an input device. The input device can pertain to an aspect of the action associated with the operation of the refuse vehicle. The instructions can also cause the one or more processors to detect a first interaction with the input device, the first interaction indicating a request to perform the action associated with the operation of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to detecting the first interaction, a second control signal to the implement causing the implement to perform the action associated with the operation of the refuse vehicle.

In some embodiments, the refuse vehicle can include a brake system. The refuse vehicle can also include an input device. The input device can activate, responsive to a first interaction with the input device, the brake system. The input device can also deactivate, responsive to a second interaction with the input device, the brake system.

In some embodiments, the input device can include at least one of a button or a switch.

One embodiment relates to a refuse vehicle. The refuse vehicle can include a display device. The display device can display one or more user interfaces. The refuse vehicle can also include a sensor, an implement, and a control system. The control system can include one or more memory devices. The one or more memory devices can store instructions. The instructions, when executed by one or more processors, can cause the one or more processors to receive, from the sensor, a set operational data associated with the refuse vehicle. The instructions can also cause the one or more processors to determine, using the set of operational data, that the refuse vehicle is operating in a first mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a first control signal to the display device causing the display device to display a user interface that includes a first view of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a second control signal to the implement. The second control signal can prevent operation of the implement.

In some embodiments, the instructions can also cause the one or more processors to receive, from the sensor, a second set of operational data associated with the refuse vehicle. The instructions can also cause the one or more processors to determine, using the second set of operational data, that the refuse vehicle is operating in a second mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the second mode; a third control signal to the display device causing the display device to update the user interface to include a second view of the refuse vehicle. The first view of the refuse vehicle and the second view of the refuse vehicle can be different.

In some embodiments, the refuse vehicle can include a battery. The batter can power the refuse vehicle. The refuse vehicle can also include a door. The instructions can also cause the one or more processors to determine a state of charge of the battery. The instructions can also cause the one or more processors to detect that the door has moved from a first position to a second position. The instructions can also cause the one or more processors to transmit, responsive to detecting that the door has moved from the first position to the second position, a third control signal to the display device causing the display device to update the user interface to include the state of charge of the battery. The display device can display the user interface for a predetermined amount of time.

In some embodiment, the instructions can also cause the one or more processors to determine that the battery is electrically coupled with a power source. The instructions can also cause the one or more processors to transmit, responsive to detecting that the battery is electrically coupled with the power source, a fourth control signal to the display device causing the display device to update the user interface to include an indication that the battery is charging.

One embodiment relates to a refuse vehicle. The refuse vehicle can include a sensor, an audio device, a climate system, a steering wheel, and a control system. The climate system can control an environmental condition of the refuse vehicle. The steering wheel can include an input device. The input device can be associated with an aspect of the environmental condition of the refuse vehicle. The control system can include one or more memory devices. The one or more memory devices can store instructions. The instructions, when executed by one or more processors, can cause the one or more processors to receive, from the sensor, a set of operational data associated with operation of the refuse vehicle. The instructions can also cause the one or more processors to determine, using the set of operation data and a predetermined set of operational data, a difference that indicates a deviation in operation of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to determination of the difference, a control signal to the audio device causing the audio device to produce an audible alert to indication the deviation in the operation of the refuse vehicle. The instructions can also cause the one or more processors to detect a first interaction with the input device, the first interaction indicating a value pertaining to the aspect of the environmental condition of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to detecting the first interaction, a second control signal to the climate system causing the climate system to control the environmental condition of the refuse vehicle to reflect the value pertaining to the aspect of the environmental condition of the refuse vehicle.

In some embodiments, the refuse vehicle can also include an implement. The implement can perform an action associated with operation of the refuse vehicle. The input device can pertain to an aspect of the action associated with the operation of the refuse vehicle. The instructions can also cause the one or more processors to detect a second interaction with the input device. The second interaction can indicate a request to perform the action associated with the operation of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to detecting the second interaction, a third control signal to the implement causing the implement to perform the action associated with the operation of the refuse vehicle.

In some embodiments, the refuse vehicle can also include an implement. The instructions can also cause the one or more processors to receive, from the sensor, a second set operational data associated with the refuse vehicle. The instructions can also cause the one or more processors to determine, using the second set of operational data, that the refuse vehicle is operating in a first mode. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a third control signal to a display device causing the display device to update the user interface to include a first view of the refuse vehicle. The instructions can also cause the one or more processors to transmit, responsive to determining that the refuse vehicle is operating in the first mode, a fourth control signal to the implement, wherein the fourth control signal prevents operation of the implement.

DETAILED DESCRIPTION

According to an exemplary embodiment, a vehicle (e.g., a refuse vehicle, etc.) of the present disclosure includes a chassis, a cab coupled to the chassis, a body assembly coupled to the chassis and positioned rearward of the cab, a plurality of rear axle assemblies coupled to the chassis, and a plurality of fenders coupled to the body assembly (rather than being coupled to the chassis) and positioned proximate the plurality of rear axle assemblies. Such a fender arrangement provides various advantages. For example, benefits of mounting to the body assembly include reduced mounting bracket weight since such a mounting arrangement provides a more direct load path. As another example, finding frame or chassis “real estate” for fender mounting brackets can be difficult when a vehicle platform has multiple different wheelbase variants.

Overall Vehicle

Referring toFIGS.1and2, a reconfigurable vehicle (e.g., a vehicle assembly, a truck, a vehicle base, etc.) is shown as vehicle10, according to an exemplary embodiment. As shown, the vehicle10includes a frame assembly or chassis assembly, shown as chassis20, that supports other components of the vehicle10. The chassis20extends longitudinally along a length of the vehicle10, substantially parallel to a primary direction of travel of the vehicle10. As shown, the chassis20includes three sections or portions, shown as front section22, middle section24, and rear section26. The middle section24of the chassis20extends between the front section22and the rear section26. In some embodiments, the middle section24of the chassis20couples the front section22to the rear section26. In other embodiments, the front section22is coupled to the rear section26by another component (e.g., the body of the vehicle10).

As shown inFIG.2, the front section22includes a pair of frame portions, frame members, or frame rails, shown as front rail portion30and front rail portion32. The rear section26includes a pair of frame portions, frame members, or frame rails, shown as rear rail portion34and rear rail portion36. The front rail portion30is laterally offset from the front rail portion32. Similarly, the rear rail portion34is laterally offset from the rear rail portion36. This spacing may provide frame stiffness and space for vehicle components (e.g., batteries, motors, axles, gears, etc.) between the frame rails. In some embodiments, the front rail portions30and32and the rear rail portions34and36extend longitudinally and substantially parallel to one another. The chassis20may include additional structural elements (e.g., cross members that extend between and couple the frame rails).

In some embodiments, the front section22and the rear section26are configured as separate, discrete subframes (e.g., a front subframe and a rear subframe). In such embodiments, the front rail portion30, the front rail portion32, the rear rail portion34, and the rear rail portion36are separate, discrete frame rails that are spaced apart from one another. In some embodiments, the front section22and the rear section26are each directly coupled to the middle section24such that the middle section24couples the front section22to the rear section26. Accordingly, the middle section24may include a structural housing or frame. In other embodiments, the front section22, the middle section24, and the rear section26are coupled to one another by another component, such as a body of the vehicle10.

In other embodiments, the front section22, the middle section24, and the rear section26are defined by a pair of frame rails that extend continuously along the entire length of the vehicle10. In such an embodiment, the front rail portion30and the rear rail portion34would be front and rear portions of a first frame rail, and the front rail portion32and the rear rail portion36would be front and rear portions of a second frame rail. In such embodiments, the middle section24would include a center portion of each frame rail.

In some embodiments, the middle section24acts as a storage portion that includes one or more vehicle components. The middle section24may include an enclosure that contains one or more vehicle components and/or a frame that supports one or more vehicle components. By way of example, the middle section24may contain or include one or more electrical energy storage devices (e.g., batteries, capacitors, etc.). By way of another example, the middle section24may include fuel tanks. By way of yet another example, the middle section24may define a void space or storage volume that can be filled by a user.

A cabin, operator compartment, or body component, shown as cab40, is coupled to a front end portion of the chassis20(e.g., the front section22of the chassis20). Together, the chassis20and the cab40define a front end of the vehicle10. The cab40extends above the chassis20. The cab40includes an enclosure or main body that defines an interior volume, shown as cab interior42, that is sized to contain one or more operators. The cab40also includes one or more doors44that facilitate selective access to the cab interior42from outside of the vehicle10. The cab interior42contains one or more components that facilitate operation of the vehicle10by the operator. By way of example, the cab interior42may contain components that facilitate operator comfort (e.g., seats, seatbelts, etc.), user interface components that receive inputs from the operators (e.g., steering wheels, pedals, touch screens, switches, buttons, levers, etc.), and/or user interface components that provide information to the operators (e.g., lights, gauges, speakers, etc.). The user interface components within the cab40may facilitate operator control over the drive components of the vehicle10and/or over any implements of the vehicle10.

The vehicle10further includes a series of axle assemblies, shown as front axle50and rear axles52. As shown, the vehicle10includes one front axle50coupled to the front section22of the chassis20and two rear axles52each coupled to the rear section26of the chassis20. In other embodiments, the vehicle10includes more or fewer axles. By way of example, the vehicle10may include a tag axle that may be raised or lowered to accommodate variations in weight being carried by the vehicle10. The front axle50and the rear axles52each include a series of tractive elements (e.g., wheels, treads, etc.), shown as wheel and tire assemblies54. The wheel and tire assemblies54are configured to engage a support surface (e.g., roads, the ground, etc.) to support and propel the vehicle10. The front axle50and the rear axles52may include steering components (e.g., steering arms, steering actuators, etc.), suspension components (e.g., gas springs, dampeners, air springs, etc.), power transmission or drive components (e.g., differentials, drive shafts, etc.), braking components (e.g., brake actuators, brake pads, brake discs, brake drums, etc.), and/or other components that facilitate propulsion or support of the vehicle.

In some embodiments, the vehicle10is configured as an electric vehicle that is propelled by an electric powertrain system. Referring toFIG.1, the vehicle10includes one or more electrical energy storage devices (e.g., batteries, capacitors, etc.), shown as batteries60. As shown, the batteries60are positioned within the middle section24of the chassis20. In other embodiments, the batteries60are otherwise positioned throughout the vehicle10. The vehicle10further includes one or more electromagnetic devices or prime movers (e.g., motor/generators), shown as drive motors62. The drive motors62are electrically coupled to the batteries60. The drive motors62may be configured to receive electrical energy from the batteries60and provide rotational mechanical energy to the wheel and tire assemblies54to propel the vehicle10. The drive motors62may be configured to receive rotational mechanical energy from the wheel and tire assemblies64and provide electrical energy to the batteries60, providing a braking force to slow the vehicle10.

The batteries60may include one or more rechargeable batteries (e.g., lithium-ion batteries, nickel-metal hydride batteries, lithium-ion polymer batteries, lead-acid batteries, nickel-cadmium batteries, etc.). The batteries60may be charged by one or more sources of electrical energy onboard the vehicle10(e.g., solar panels, etc.) or separate from the vehicle10(e.g., connections to an electrical power grid, a wireless charging system, etc.). As shown, the drive motors62are positioned within the rear axles52(e.g., as part of a combined axle and motor assembly). In other embodiments, the drive motors62are otherwise positioned within the vehicle10.

In other embodiments, the vehicle10is configured as a hybrid vehicle that is propelled by a hybrid powertrain system (e.g., a diesel/electric hybrid, gasoline/electric hybrid, natural gas/electric hybrid, etc.). According to an exemplary embodiment, the hybrid powertrain system may include a primary driver (e.g., an engine, a motor, etc.), an energy generation device (e.g., a generator, etc.), and/or an energy storage device (e.g., a battery, capacitors, ultra-capacitors, etc.) electrically coupled to the energy generation device. The primary driver may combust fuel (e.g., gasoline, diesel, etc.) to provide mechanical energy, which a transmission may receive and provide to the front axle50and/or the rear axles52to propel the vehicle10. Additionally or alternatively, the primary driver may provide mechanical energy to the generator, which converts the mechanical energy into electrical energy. The electrical energy may be stored in the energy storage device (e.g., the batteries60) in order to later be provided to a motive driver.

In yet other embodiments, the chassis20may further be configured to support non-hybrid powertrains. For example, the powertrain system may include a primary driver that is a compression-ignition internal combustion engine that utilizes diesel fuel.

Referring toFIG.1, the vehicle10includes a rear assembly, module, implement, body, or cargo area, shown as application kit80. The application kit80may include one or more implements, vehicle bodies, and/or other components. Although the application kit80is shown positioned behind the cab40, in other embodiments the application kit80extends forward of the cab40. The vehicle10may be outfitted with a variety of different application kits80to configure the vehicle10for use in different applications. Accordingly, a common vehicle10can be configured for a variety of different uses simply by selecting an appropriate application kit80. By way of example, the vehicle10may be configured as a refuse vehicle, a concrete mixer, a fire fighting vehicle, an airport fire fighting vehicle, a lift device (e.g., a boom lift, a scissor lift, a telehandler, a vertical lift, etc.), a crane, a tow truck, a military vehicle, a delivery vehicle, a mail vehicle, a boom truck, a plow truck, a farming machine or vehicle, a construction machine or vehicle, a coach bus, a school bus, a semi-truck, a passenger or work vehicle (e.g., a sedan, a SUV, a truck, a van, etc.), and/or still another vehicle.FIGS.3-13illustrate various examples of how the vehicle10may be configured for specific applications. Although only a certain set of vehicle configurations is shown, it should be understood that the vehicle10may be configured for use in other applications that are not shown.

The application kit80may include various actuators to facilitate certain functions of the vehicle10. By way of example, the application kit80may include hydraulic actuators (e.g., hydraulic cylinders, hydraulic motors, etc.), pneumatic actuators (e.g., pneumatic cylinders, pneumatic motors, etc.), and/or electrical actuators (e.g., electric motors, electric linear actuators, etc.). The application kit80may include components that facilitate operation of and/or control of these actuators. By way of example, the application kit80may include hydraulic or pneumatic components that form a hydraulic or pneumatic circuit (e.g., conduits, valves, pumps, compressors, gauges, reservoirs, accumulators, etc.). By way of another example, the application kit80may include electrical components (e.g., batteries, capacitors, voltage regulators, motor controllers, etc.). The actuators may be powered by components of the vehicle10. By way of example, the actuators may be powered by the batteries60, the drive motors62, or the primary driver (e.g., through a power take off).

The vehicle10generally extends longitudinally from a front side86to a rear side88. The front side86is defined by the cab40and/or the chassis. The rear side88is defined by the application kit80and/or the chassis20. The primary, forward direction of travel of the vehicle10is longitudinal, with the front side86being arranged forward of the rear side88.

Front-Loading Refuse Vehicle

Referring now toFIGS.3and4, the vehicle10is configured as a refuse vehicle100(e.g., a refuse truck, a garbage truck, a waste collection truck, a sanitation truck, a recycling truck, etc.). Specifically, the refuse vehicle100is a front-loading refuse vehicle. In other embodiments, the refuse vehicle100is configured as a rear-loading refuse vehicle or a front-loading refuse vehicle. The refuse vehicle100may be configured to transport refuse from various waste receptacles (e.g., refuse containers) within a municipality to a storage and/or processing facility (e.g., a landfill, an incineration facility, a recycling facility, etc.).

FIG.4illustrates the refuse vehicle100ofFIG.3configured with a liftable axle, shown as tag axle90, including a pair of wheel and tire assemblies54. As shown, the tag axle90is positioned reward of the rear axles52. The tag axle90can be selectively raised and lowered (e.g., by a hydraulic actuator) to selectively engage the wheel and tire assemblies54of the tag axle90with the ground. The tag axle90may be raised to reduce rolling resistance experienced by the refuse vehicle100. The tag axle90may be lowered to distribute the loaded weight of the vehicle100across a greater number of a wheel and tire assemblies54(e.g., when the refuse vehicle100is loaded with refuse).

As shown inFIGS.3and4, the application kit80of the refuse vehicle100includes a series of panels that form a rear body or container, shown as refuse compartment130. The refuse compartment130may facilitate transporting refuse from various waste receptacles within a municipality to a storage and/or a processing facility (e.g., a landfill, an incineration facility, a recycling facility, etc.). By way of example, loose refuse may be placed into the refuse compartment130where it may be compacted (e.g., by a packer system within the refuse compartment130). The refuse compartment130may also provide temporary storage for refuse during transport to a waste disposal site and/or a recycling facility. In some embodiments, the refuse compartment130may define a hopper volume132and storage volume134. In this regard, refuse may be initially loaded into the hopper volume132and later compacted into the storage volume134. As shown, the hopper volume132is positioned between the storage volume134and the cab40(e.g., refuse is loaded into a portion of the refuse compartment130behind the cab40and stored in a portion further toward the rear of the refuse compartment130). In other embodiments, the storage volume may be positioned between the hopper volume and the cab40(e.g., in a rear-loading refuse truck, etc.). The application kit80of the refuse vehicle100further includes a pivotable rear portion, shown as tailgate136, that is pivotally coupled to the refuse compartment130. The tailgate136may be selectively repositionable between a closed position and an open position by an actuator (e.g., a hydraulic cylinder, an electric linear actuator, etc.), shown as tailgate actuator138(e.g., to facilitate emptying the storage volume).

As shown inFIGS.3and4, the refuse vehicle100also includes an implement, shown as lift assembly140, which is a front-loading lift assembly. According to an exemplary embodiment, the lift assembly140includes a pair of lift arms142and a pair of actuators (e.g., hydraulic cylinders, electric linear actuators, etc.), shown as lift arm actuators144. The lift arms142may be rotatably coupled to the chassis20and/or the refuse compartment130on each side of the refuse vehicle100(e.g., through a pivot, a lug, a shaft, etc.), such that the lift assembly140may extend forward relative to the cab40(e.g., a front-loading refuse truck, etc.). In other embodiments, the lift assembly140may extend rearward relative to the application kit80(e.g., a rear-loading refuse truck). As shown inFIGS.3and4, in an exemplary embodiment the lift arm actuators144may be positioned such that extension and retraction of the lift arm actuators144rotates the lift arms142about an axis extending through the pivot. In this regard, the lift arms142may be rotated by the lift arm actuators144to lift a refuse container over the cab40. The lift assembly140further includes a pair of interface members, shown as lift forks146, each pivotally coupled to a distal end of one of the lift arms142. The lift forks146may be configured to engage a refuse container (e.g., a dumpster) to selectively couple the refuse container to the lift arms142. By way of example, each of the lift forks146may be received within a corresponding pocket defined by the refuse container. A pair of actuators (e.g., hydraulic cylinders, electric linear actuators, etc.), shown as articulation actuators148, are each coupled to one of the lift arms142and one of the lift forks146. The articulation actuators148may be positioned to rotate the lift forks146relative to the lift arms142about a horizontal axis. Accordingly, the articulation actuators148may assist in tipping refuse out of the refuse container and into the refuse compartment130. The lift arm actuators144may then rotate the lift arms142to return the empty refuse container to the ground.

Side-Loading Refuse Vehicle

Referring now toFIGS.5-8, an alternative configuration of the refuse vehicle100is shown according to an exemplary embodiment. Specifically, the refuse vehicle100ofFIGS.5-8is configured as a side-loading refuse vehicle. The refuse vehicle100ofFIGS.5-8may be substantially similar to the front-loading refuse vehicle100ofFIGS.3and4except as otherwise specified herein. As shown inFIG.8, the refuse vehicle100ofFIGS.5-7may be configured with a tag axle90.

Referring still toFIGS.5-8, the refuse vehicle100omits the lift assembly140and instead includes a side-loading lift assembly, shown as lift assembly160, that extends laterally outward from a side of the refuse vehicle100. The lift assembly160includes an interface assembly, shown as grabber assembly162, that is configured to engage a refuse container (e.g., a residential garbage can) to selectively couple the refuse container to the lift assembly160. The grabber assembly162includes a main portion, shown as main body164, and a pair of fingers or interface members, shown as grabber fingers166. The grabber fingers166are pivotally coupled to the main body164such that the grabber fingers166are each rotatable about a vertical axis. A pair of actuators (e.g., hydraulic motors, electric motors, etc.), shown as finger actuators168, are configured to control movement of the grabber fingers166relative to the main body164.

The grabber assembly162is movably coupled to a guide, shown as track170, that extends vertically along a side of the refuse vehicle100. Specifically, the main body164is slidably coupled to the track170such that the main body164is repositionable along a length of the track170. An actuator (e.g., a hydraulic motor, an electric motor, etc.), shown as lift actuator172, is configured to control movement of the grabber assembly162along the length of the track170. In some embodiments, a bottom end portion of the track170is straight and substantially vertical such that the grabber assembly162raises or lowers a refuse container when moving along the bottom end portion of the track170. In some embodiments, a top end portion of the track170is curved such that the grabber assembly162inverts a refuse container to dump refuse into the hopper volume132when moving along the top end portion of the track170.

The lift assembly160further includes an actuator (e.g., a hydraulic cylinder, an electric linear actuator, etc.), shown as track actuator174, that is configured to control lateral movement of the grabber assembly162. By way of example, the track actuator174may be coupled to the chassis20and the track170such that the track actuator174moves the track170and the grabber assembly162laterally relative to the chassis20. The track actuator174may facilitate repositioning the grabber assembly162to pick up and replace refuse containers that are spaced laterally outward from the refuse vehicle100.

Concrete Mixer Truck

Referring now toFIG.9, the vehicle10is configured as a mixer truck (e.g., a concrete mixer truck, a mixer vehicle, etc.), shown as mixer truck200. Specifically, the mixer truck200is shown as a rear-discharge concrete mixer truck. In other embodiments, the mixer truck200is a front-discharge concrete mixer truck.

As shown inFIG.9, the application kit80includes a mixing drum assembly (e.g., a concrete mixing drum), shown as drum assembly230. The drum assembly230may include a mixing drum232, a drum drive system234(e.g., a rotational actuator or motor, such as an electric motor or hydraulic motor), an inlet portion, shown as hopper236, and an outlet portion, shown as chute238. The mixing drum232may be coupled to the chassis20and may be disposed behind the cab40(e.g., at the rear and/or middle of the chassis20). In an exemplary embodiment, the drum drive system234is coupled to the chassis20and configured to selectively rotate the mixing drum232about a central, longitudinal axis. According to an exemplary embodiment, the central, longitudinal axis of the mixing drum232may be elevated from the chassis20(e.g., from a horizontal plane extending along the chassis20) at an angle in the range of five degrees to twenty degrees. In other embodiments, the central, longitudinal axis may be elevated by less than five degrees (e.g., four degrees, etc.). In yet another embodiment, the mixer truck200may include an actuator positioned to facilitate adjusting the central, longitudinal axis to a desired or target angle (e.g., manually in response to an operator input/command, automatically according to a control system, etc.).

The mixing drum232may be configured to receive a mixture, such as a concrete mixture (e.g., cementitious material, aggregate, sand, etc.), through the hopper236. In some embodiments, the mixer truck200includes an injection system (e.g., a series of nozzles, hoses, and/or valves) including an injection valve that selectively fluidly couples a supply of fluid to the inner volume of the mixing drum232. By way of example, the injection system may be used to inject water and/or chemicals (e.g., air entrainers, water reducers, set retarders, set accelerators, superplasticizers, corrosion inhibitors, coloring, calcium chloride, minerals, and/or other concrete additives, etc.) into the mixing drum232. The injection valve may facilitate injecting water and/or chemicals from a fluid reservoir (e.g., a water tank, etc.) into the mixing drum232, while preventing the mixture in the mixing drum232from exiting the mixing drum232through the injection system. In some embodiments, one or more mixing elements (e.g., fins, etc.) may be positioned in the interior of the mixing drum232, and may be configured to agitate the contents of the mixture when the mixing drum232is rotated in a first direction (e.g., counterclockwise, clockwise, etc.), and drive the mixture out through the chute238when the mixing drum232is rotated in a second direction (e.g., clockwise, counterclockwise, etc.). In some embodiments, the chute238may also include an actuator positioned such that the chute238may be selectively pivotable to position the chute238(e.g., vertically, laterally, etc.), for example at an angle at which the mixture is expelled from the mixing drum232.

Fire Truck

Referring now toFIG.10, the vehicle10is configured as a fire fighting vehicle, fire truck, or fire apparatus (e.g., a turntable ladder truck, a pumper truck, a quint, etc.), shown as fire fighting vehicle250. In the embodiment shown inFIG.10, the fire fighting vehicle250is configured as a rear-mount aerial ladder truck. In other embodiments, the fire fighting vehicle250is configured as a mid-mount aerial ladder truck, a quint fire truck (e.g., including an on-board water storage, a hose storage, a water pump, etc.), a tiller fire truck, a pumper truck (e.g., without an aerial ladder), or another type of response vehicle. By way of example, the vehicle10may be configured as a police vehicle, an ambulance, a tow truck, or still other vehicles used for responding to a scene (e.g., an accident, a fire, an incident, etc.).

As shown inFIG.10, in the fire fighting vehicle250, the application kit80is positioned mainly rearward from the cab40. The application kit80includes deployable stabilizers (e.g., outriggers, downriggers, etc.), shown as outriggers252, that are coupled to the chassis20. The outriggers252may be configured to selectively extend from each lateral side and/or the rear of the fire fighting vehicle250and engage a support surface (e.g., the ground) in order to provide increased stability while the fire fighting vehicle250is stationary. The fire fighting vehicle250further includes an extendable or telescoping ladder assembly, shown as ladder assembly254. The increased stability provided by the outriggers252is desirable when the ladder assembly254is in use (e.g., extended from the fire fighting vehicle250) to prevent tipping. In some embodiments, the application kit80further includes various storage compartments (e.g., cabinets, lockers, etc.) that may be selectively opened and/or accessed for storage and/or component inspection, maintenance, and/or replacement.

As shown inFIG.10, the ladder assembly254includes a series of ladder sections260that are slidably coupled with one another such that the ladder sections260may extend and/or retract (e.g., telescope) relative to one another to selectively vary a length of the ladder assembly254. A base platform, shown as turntable262, is rotatably coupled to the chassis20and to a proximal end of a base ladder section260(i.e., the most proximal of the ladder sections260). The turntable262may be configured to rotate about a vertical axis relative to the chassis20to rotate the ladder sections260about the vertical axis (e.g., up to 360 degrees, etc.). The ladder sections260may rotate relative to the turntable262about a substantially horizontal axis to selectively raise and lower the ladder sections260relative to the chassis20. As shown, a water turret or implement, shown as monitor264, is coupled to a distal end of a fly ladder section260(i.e., the most distal of the ladder sections260). The monitor264may be configured to expel water and/or a fire suppressing agent (e.g., foam, etc.) from a water storage tank and/or an agent tank onboard the fire fighting vehicle250, and/or from an external source (e.g., a fire hydrant, a separate water/pumper truck, etc.). In some embodiments, the ladder assembly254further includes an aerial platform coupled to the distal end of the fly ladder section260and configured to support one or more operators.

ARFF Truck

Referring now toFIG.11, the vehicle10is configured as a fire fighting vehicle, shown as airport rescue and fire fighting (ARFF) truck300. As shown inFIG.11, the application kit80is positioned primarily rearward of the cab40. As shown, the application kit80includes a series of storage compartments or cabinets, shown as compartments302, that are coupled to the chassis20. The compartments302may store various equipment or components of the ARFF truck300.

The application kit80includes a pump system304(e.g., an ultra-high-pressure pump system, etc.) positioned within one of the compartments302near the center of the ARFF truck300. The application kit80further includes a water tank310, an agent tank312, and an implement or water turret, shown as monitor314. The pump system304may include a high pressure pump and/or a low pressure pump, which may be fluidly coupled to the water tank310and/or the agent tank312. The pump system304may to pump water and/or fire suppressing agent from the water tank310and the agent tank312, respectively, to the monitor314. The monitor314may be selectively reoriented by an operator to adjust a direction of a stream of water and/or agent. As shown inFIG.11, the monitor314is coupled to a front end of the cab40.

Boom Lift

Referring now toFIG.12, the vehicle10is configured as a lift device, shown as boom lift350. The boom lift350may be configured to support and elevate one or more operators. In other embodiments, the vehicle10is configured as another type of lift device that is configured to lift operators and/or material, such as a skid-loader, a telehandler, a scissor lift, a fork lift, a vertical lift, and/or any other type of lift device or machine.

As shown inFIG.12, the application kit80includes a base assembly, shown as turntable352, that is rotatably coupled to the chassis20. The turntable352may be configured to selectively rotate relative to the chassis20about a substantially vertical axis. In some embodiments, the turntable352includes a counterweight (e.g., the batteries) positioned near the rear of the turntable352. The turntable352is rotatably coupled to a lift assembly, shown as boom assembly354. The boom assembly354includes a first section or telescoping boom section, shown as lower boom360. The lower boom360includes a series of nested boom sections that extend and retract (e.g., telescope) relative to one another to vary a length of the boom assembly354. The boom assembly354further includes a second boom section or four bar linkage, shown as upper boom362. The upper boom362may includes structural members that rotate relative to one another to raise and lower a distal end of the boom assembly354. In other embodiments, the boom assembly354includes more or fewer boom sections (e.g., one, three, five, etc.) and/or a different arrangement of boom sections.

As shown inFIG.12, the boom assembly354includes a first actuator, shown as lower lift cylinder364. The lower boom360is pivotally coupled (e.g., pinned, etc.) to the turntable352at a joint or lower boom pivot point. The lower lift cylinder364(e.g., a pneumatic cylinder, an electric linear actuator, a hydraulic cylinder, etc.) is coupled to the turntable352at a first end and coupled to the lower boom360at a second end. The lower lift cylinder364may be configured to raise and lower the lower boom360relative to the turntable352about the lower boom pivot point.

The boom assembly354further includes a second actuator, shown as upper lift cylinder366. The upper boom362is pivotally coupled (e.g., pinned) to the upper end of the lower boom360at a joint or upper boom pivot point. The upper lift cylinder366(e.g., a pneumatic cylinder, an electric linear actuator, a hydraulic cylinder, etc.) is coupled to the upper boom362. The upper lift cylinder366may be configured to extend and retract to actuate (e.g., lift, rotate, elevate, etc.) the upper boom362, thereby raising and lowering a distal end of the upper boom362.

Referring still toFIG.12, the application kit80further includes an operator platform, shown as platform assembly370, coupled to the distal end of the upper boom362by an extension arm, shown as jib arm372. The jib arm372may be configured to pivot the platform assembly370about a lateral axis (e.g., to move the platform assembly370up and down, etc.) and/or about a vertical axis (e.g., to move the platform assembly370left and right, etc.).

The platform assembly370provides a platform configured to support one or more operators or users. In some embodiments, the platform assembly370may include accessories or tools configured for use by the operators. For example, the platform assembly370may include pneumatic tools (e.g., an impact wrench, airbrush, nail gun, ratchet, etc.), plasma cutters, welders, spotlights, etc. In some embodiments, the platform assembly370includes a control panel (e.g., a user interface, a removable or detachable control panel, etc.) configured to control operation of the boom lift350(e.g., the turntable352, the boom assembly354, etc.) from the platform assembly370or remotely. In other embodiments, the platform assembly370is omitted, and the boom lift350includes an accessory and/or tool (e.g., forklift forks, etc.) coupled to the distal end of the boom assembly354.

Scissor Lift

Referring now toFIG.13, the vehicle10is configured as a lift device, shown as scissor lift400. As shown inFIG.13, the application kit80includes a body, shown as lift base402, coupled to the chassis20. The lift base402is coupled to a scissor assembly, shown as lift assembly404, such that the lift base402supports the lift assembly404. The lift assembly404is configured to extend and retract, raising and lowering between a raised position and a lowered position relative to the lift base402.

As shown inFIG.13, the lift base402includes a series of actuators, stabilizers, downriggers, or outriggers, shown as leveling actuators410. The leveling actuators410may extend and retract vertically between a stored position and a deployed position. In the stored position, the leveling actuators410may be raised, such that the leveling actuators410do not contact the ground. Conversely, in the deployed position, the leveling actuators410may engage the ground to lift the lift base402. The length of each of the leveling actuators410in their respective deployed positions may be varied in order to adjust the pitch (e.g., rotational position about a lateral axis) and the roll (e.g., rotational position about a longitudinal axis) of the lift base402and/or the chassis20. Accordingly, the lengths of the leveling actuators410in their respective deployed positions may be adjusted to level the lift base402with respect to the direction of gravity (e.g., on uneven, sloped, pitted, etc. terrain). The leveling actuators410may lift the wheel and tire assemblies54off of the ground to prevent movement of the scissor lift400during operation. In other embodiments, the leveling actuators410are omitted.

The lift assembly404may include a series of subassemblies, shown as scissor layers420, each including a pair of inner members and a pair of outer members pivotally coupled to one another. The scissor layers420may be stacked atop one another in order to form the lift assembly404, such that movement of one scissor layer420causes a similar movement in all of the other scissor layers420. The scissor layers420extend between and couple the lift base402and an operator platform (e.g., the platform assembly430). In some embodiments, scissor layers420may be added to, or removed from, the lift assembly404in order to increase, or decrease, the fully extended height of the lift assembly404.

Referring still toFIG.13, the lift assembly404may also include one or more lift actuators424(e.g., hydraulic cylinders, pneumatic cylinders, electric linear actuators such as motor-driven leadscrews, etc.) configured to extend and retract the lift assembly404. The lift actuators424may be pivotally coupled to inner members of various scissor layers420, or otherwise arranged within the lift assembly404.

A distal or upper end of the lift assembly404is coupled to an operator platform, shown as platform assembly430. The platform assembly430may perform similar functions to the platform assembly370, such as supporting one or more operators, accessories, and/or tools. The platform assembly430may include a control panel to control operation of the scissor lift400. The lift actuators424may be configured to actuate the lift assembly404to selectively reposition the platform assembly430between a lowered position (e.g., where the platform assembly430is proximate to the lift base402) and a raised position (e.g., where the platform assembly430is at an elevated height relative to the lift base402). Specifically, in some embodiments, extension of the lift actuators424moves the platform assembly430upward (e.g., extending the lift assembly404), and retraction of the lift actuators424moves the platform assembly430downward (e.g., retracting the lift assembly404). In other embodiments, extension of the lift actuators424retracts the lift assembly404, and retraction of the lift actuators424extends the lift assembly404.

Vehicle Control System

FIG.14depicts a block diagram of a system1400, according to an exemplary embodiment. Each system and/or component of the system1400can include one or more processors, memory, network interfaces, and/or user interfaces. The memory can store programming logic that, when executed by the processor, controls the operation of the corresponding computing system or device. The memory can also store data in databases. The network interfaces can allow the systems and/or components of the system1400to communicate wirelessly. The various components in the system1400can be implemented via hardware (e.g., circuitry), software (e.g., executable code), or any combination thereof. Systems, devices, and components inFIG.14can be added, deleted, integrated, separated, and/or rearranged.

The system1400can include the vehicle10. The vehicle10can be at least one of the vehicles described herein. The vehicle10can include at least one control system1403, at least one sensor1440, at least one display device1445, at least one audio device1450, at least one power source1455, at least one input/output (I/O) device1460(e.g., I/O device1460), and at least one climate control1465. The components of the vehicle10and/or the system1400can be electrically coupled with one another. For example, the control system1403can be electrically coupled with the sensor1440. The components of the vehicle10and/or the components of the system1400can also communicate with, interact with, and/or otherwise interface with one another via a controller area network (CAN). For example, the control system1403can communicate, via a CAN, with the display device1445.

The sensor1440can be and/or include an accelerometer, a tachometer, a speedometer, a GPS device/sensor, a temperature sensor, a voltmeter, an ammeter, a radar sensor, a camera, a pressure sensor, a tactile sensor, a photodetector, a motion sensor, a proximity sensor, and/or among other possible sensors and/or devices. For example, the sensor1440can be a tactile sensor. The sensor1440can provide operational data associated with the vehicle10to the control system1403. The operational data associated with the vehicle10can be and/or include at least one of a speed of the vehicle10, an acceleration of the vehicle10, a location of the vehicle10, an operator input (e.g., an input provided by an operator of the vehicle10), images pertaining to the vehicle10(e.g., images of the vehicle10and/or an area including the vehicle10that are generated and/or provided by a camera), and/or an environmental condition of the vehicle10(e.g., a temperature of the cab interior42).

The display device1445can be and/or include a screen, a monitor, a visual display device, a television, a video display, a liquid crystal display (LCD), a light emitting diode (LED) display, an infotainment system, a mobile device, and/or among other possible displays and/or devices. For example, the display device1445can be an LCD. The display device1445can generate, produce, provide and/or otherwise display a user interface. For example, the display device1445can display a user interface that includes images of the vehicle10that were provided by the sensor1440.

The audio device1450can be and/or include a speaker, a microphone, a headphone, and/or among other possible audio and/or sound devices. For example, the audio device1450can be a speaker. The audio device1450can produce, provide, generate and/or otherwise create an audible signal.

The power source1455can be and/or include an energy storage device (e.g., a battery, capacitors, ultra-capacitors, etc.). For example, the power source1455can be and/or include the batteries60. The power source1455can electrically couple with an energy generation device. For example, the power source1455can electrically couple with a charging station and/or a device that can provide electrical power and/or electrical energy to the power source1455. The electrical energy can be stored by the power source1455for use in powering the vehicle10.

The I/O device1460can be and/or include a joystick, a button, a toggle switch, a handle, a lever, a steering wheel, a key, a keypad, a console, a mouse, a keyboard, a knob, a dial, a vehicle shifter, a smart phone, a computer, a wearable device, and/or among other possible I/O devices. For example, the I/O device1460can be a joystick. An operator of the vehicle10can interact with, interface with and/or otherwise engage with the I/O device1460. For example, the operator can select a vehicle mode button on a joystick (e.g., the I/O device1460). The operating engaging with the I/O device1460can result in the I/O device1460communicating with the control system1403and/or a component of the system1400.

The climate control1465can be and/or include a vehicle climate control system, an HVAC system, a heater, a fan, an air conditioner, and/or among other possible devices and/or systems. For example, the climate control1465can be a vehicle climate control system. The climate control1465can change, adjust, maintain and/or otherwise control an environmental condition of the vehicle10. For example, the climate control1465can control the temperature within the interior cab42.

The control system1403can include at least one processing circuit1405. The processing circuit1405can include at least one processor1407and memory1409. The memory1409can be one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing and/or facilitating the various processes described herein. For example, the memory1409can store instructions and the instructions can cause the processor1407to perform functionality similar to that one the control system1403and/or a component thereof. The memory1409can be or include non-transient volatile memory, non-volatile memory, and non-transitory computer storage media. The Memory1409can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described herein. The memory1409can be communicably coupled with the processor1407. The memory1409can also be electrically coupled with the processor1407. The memory1409can include computer code or instructions for executing one or more processes described herein. The processor1407can be implemented as one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), a group of processing components, and/or other suitable electronic processing components.

The control system1403can also include at least one communication component1410, at least one State of Charge manager1415(e.g., SoC manager1415), at least one mode manager1420, at least one operator manager1425, at least one interface generator1430, and at least one controller1435. The communication component1410can interact with, interface with and/or otherwise communicate with at least one component included in the system1400. For example, the communication component1410can communicate with the display device1445.

The communication component1410can receive, from the sensor1440, data that was generated, collected, detected, obtained and/or otherwise acquired by the sensor1440. For example, the sensor1440can detect data pertaining to the charging of the power source1455. The communication component1410can provide, responsive to receiving the data from the sensor1440, the data to the SoC manager1415.

The SoC manager1415can, using the data that was received from the communication component, determine a State of Charge (SoC) of the power source1455. The SoC of the power source1455can be and/or include a current value, a calculated value, and/or a predicted value. The SoC manager1415can provide, responsive to determining the SoC of the power source1455, the SoC of the power source1455to the interface generator1430.

The interface generator1430can receive, from the SoC manager1415, the SoC of the power source1455. The interface generator1430can generate a user interface and/or otherwise generate information that can be used to generate a user interface. For example, the interface generator1430can provide signals to a display device (e.g., the display device1445) that causes the display device to display a user interface that includes information generated by the interface generator1430.

The interface generator1430can include the SoC of the power source1455in the signals that are provided to the display device. The interface generator1430can, responsive to generating the user interface, communicate with the communication component1410. For example, the interface generator1430can provide, to the communication component1410, the user interface and/or the signals associated with the user interface. The communication component1410can, responsive to communicating with the interface generator1430, provide the user interface to the display device1445. The display device can, responsive to receiving the user interface, produce, provide, and/or otherwise display the user interface that was generated by the interface generator1430.

The SoC manager1415can determine whether the vehicle10and/or the power source1455is electrically coupled with a charging station and/or other possible Electric Vehicle Supply Equipment (EVSE). For example, the SoC manager1415can receive from the communication component1410data that was detected by the sensor1440. The data can include information about an amount of current flowing from a charging port of the vehicle10to the power source1455. The SoC manager1415can, using the data, determine that the power source1455is charging. For example, the SoC manager1415can determine that the amount of current flowing from the charging port to the power source1455is above a predetermined threshold and the current being above the predetermined threshold can indicate that the power source1455is being charged. Similarly, the SoC manager1415can determine, responsive to the sensor1440providing data that indicates a switch has been actuated, that the power source1455is being charged. For example, a power cord that is electrically coupled with the charging station can, responsive to electrically coupling with the power source1455, actuate a switch. The sensor1440can detect the actuation of the switch and the sensor1440can provide information, to the SoC manager1415, including the detection of the actuation of the switch.

The mode manager1420can determine a mode of the vehicle10. The vehicle10can have at least one drive mode, at least one collection mode, and at least one dump mode. The current mode (e.g., drive mode, collection mode, or dump mode) can determine what components, devices, and/or systems of the vehicle10are activated and/or deactivated. For example, the arms142can be deactivated and/or otherwise locked (e.g., inoperable) when the vehicle10is in drive mode. The deactivation of the arms142, while the vehicle10is in drive mode, can prevent accidental and/or incidental utilization of the arms142. For example, while in drive mode that I/O device1460that controls the arms142if engaged would not result in activation of the arms142.

The mode manager1420can use data received from the sensor1440(e.g. a speed of the vehicle10) and/or data received from the I/O device1460(e.g., selection of a button included with the I/O device1460). For example, the mode manager1420can receive a current speed of the vehicle10. The mode manager1420can compare the current speed of the vehicle10with at least one predetermined threshold. The mode manager1420can use the comparison of the current speed of the vehicle10with the predetermined threshold to determine the mode of the vehicle. For example, the current speed of the vehicle10can be 28 miles per hour (MPH) and a predetermined threshold for drive mode can be 20 MPH. To continue this example, the mode manager1420can determine that the current speed of the vehicle10is above the predetermined threshold resulting in the mode manager1420determining that the vehicle10is in drive mode.

The mode manager1420can, responsive to determining the mode of the vehicle10, communicate with the controller1435. For example, the mode manager1420can provide, to the controller1435, an indication that the vehicle10is in the drive mode. The controller1435can interact with, interface with and/or otherwise control at least one component of the vehicle10. For example, the controller1435can control the tailgate actuator138. The controller1435can, responsive to receiving the indication that the vehicle10is in drive mode, deactivate the tailgate actuator138. For example, if an operator of the vehicle10were to interact with the I/O device1460, associated with the tailgate actuator138, the tailgate actuator138would not respond to the interaction (e.g., the tailgate actuator138would not move the tailgate136). The controller1435can also deactivate lift systems, hydraulics and/or pneumatic circuits (e.g., conduits, valves, pumps, compressors, gauges, reservoirs, accumulators, etc.) that are to move components of the vehicle10. For example, the controller1435can, responsive to receiving the indication that the vehicle10is in drive mode, deactivate the lift arm actuators144.

The mode manager1420can, responsive to determining that the vehicle10is in the drive mode, communicate with the interface generator1430. The mode manager1420can provide, to the interface generator1430, the indication that the vehicle10is in drive mode. The interface generator1430can generate and/or otherwise collect information (e.g., camera views provided by the sensors1440, vehicle speed, vehicle location, pickup location, etc.) that can be included in a user interface. For example, the interface generator1430can communicate with the sensors1440and the sensors1440can provide to the interface generator1430camera views (e.g., an aerial view of the vehicle10, a360view of the vehicle10, a rear right view of the vehicle10, etc.). The interface generator1430can, responsive to communicating with the sensors1440, provide the collected information to the display device1445. The display device1445receiving the information can cause the display device1445to display the user interface that was generated by the interface generator1430.

As another example, the mode manager1420can determine that the vehicle10is in a collection mode. The mode manager1420can determine that the vehicle10is in the collection mode responsive to receiving information (e.g., operational data) associated with the vehicle10. For example, the sensors1440can provide, to the mode manager1420, a speed of the vehicle10, operator input, vehicle location, and/or among other possible operational data associated with the vehicle10. The mode manager1420can determine, using the operational data, that the vehicle10is in the collection mode. For example, the mode manager1420can compare the vehicle speed with a predetermined threshold associated with collection mode. To continue this example, the vehicle speed can be 5 MPH and the predetermined threshold for collection mode can be 8 MPH. In this example, the mode manager1420can determine that the vehicle10is in collection mode responsive to the vehicle speed being smaller than the predetermined threshold.

As another example, the mode manager1420can use the vehicle speed of the vehicle10and operator input to determine that the vehicle10is in collection mode. For example, the mode manager1420can determine that speed of the vehicle10is below the predetermined threshold for collection mode and the mode manager1420can determine that the operator of the vehicle10is also interacting with the I/O device1460(e.g., move a joystick that controls the arms142). In this example, if the vehicle10was previously operating in drive mode, the mode manager1420can determine that the vehicle10is now operating in collection mode. The mode manager1420can, responsive to determining that the vehicle10has switched from drive mode to collection mode, communicate with the controller1435. The mode manager1420can provide, to the controller1435, an indication that the vehicle10is now operating in collection mode. The controller1435can, responsive to receiving the indication that the vehicle10is operating in collection mode, reactive components that were deactivated in drive mode and/or unlock components that were locked during drive mode. For example, the arms142can be locked during drive mode and the controller1435can send a signal to the arms142that causing the arms142to be unlocked while the vehicle10is in collection.

The mode manager1420can provide, to the interface generator1430, the indication that the vehicle10is in collection mode. The interface generator1430can generate and/or otherwise collect information (e.g., camera views provided by the sensors1440, vehicle speed, vehicle location, pickup location, etc.) that can be included in a user interface. For example, the interface generator1430can communicate with the sensors1440and the sensors1440can provide to the interface generator1430camera views (e.g., an aerial view of the vehicle10, a360view of the vehicle10, a rear right view of the vehicle10, etc.). The interface generator1430can, responsive to communicating with the sensors1440, provide the collected information to the display device1445. The display device1445receiving the information can cause the display device1445to display the user interface that was generated by the interface generator1430.

The display device1445can have a first view (e.g., a first user interface displayed by the display device1445) when the vehicle10is in the drive mode (e.g., a first mode). The display device1445can have a second view (e.g., a second user interface displayed by the display device1445) when the vehicle10is in collection mode (e.g., a second mode). The mode manager1420determining whether the vehicle10is in collection mode or drive mode can determine which view is displayed by the display device1445. For example, the first view can have a first set of vehicle views (e.g., an aerial view and a hopper view) and the second view can have a second set of vehicle views (e.g., a side view and a rear right view).

As another example, the mode manager1420can use operator input to determine if the vehicle10is in collection mode and/or dump mode. For example, the vehicle10can be in collection mode and while in collection mode the operator of the vehicle10can interact with the I/O device1460associated with the tailgate136. The mode manager1420can, responsive to determining that the operator of the vehicle10is using tailgate136, determine that the vehicle10is in dump mode. For example, the sensors1440can detect that the operator interacting with the I/O device1460and the sensor1440can send a signal to the mode manager1420. The mode manager1420can then determine that the vehicle10is in dump mode.

The operator manager1425can determine when the operator of the vehicle10is entering, exiting, and/or otherwise interacting with the doors44. For example, the operator manager1425can determine when the operator of the vehicle10opens the door44. The opening and/or closing of the doors44can determine what user interface is displayed by the display device1445. For example, while the vehicle10is off and the vehicle is charging (e.g., power is being provided to the power source1455from a charging station) and responsive to the door44being opened, the operator manager1425can communicate with the interface generator1430. The operator manager1425can provide an indication that the door44has been opened. The interface generator1430can generate a user interface that includes information pertaining to the charging of the vehicle10. For example, the user interface can include information generated by the sensors1440and/or the SoC manager1415(e.g., SoC of the vehicle10, whether the vehicle is charging, etc.). The interface generator1430can communicate to the display device1445. The interface generator1430can provide, to the display device1445, the information pertaining to the charging of the vehicle10. The display device1445receiving the information can cause the display device1445to display a user interface that includes the information. The display device1445can display the user interface for a predetermined amount of time. For example, the display device1445can display the user interface for 30 seconds. As another example, the display device1445can display the user interface for 1 minute. The display device1445can also display the user interface until the operator of the vehicle10closes the door44.

The operator manager1425can detect, track, and/or otherwise monitor operation of the vehicle10. The operator manager1425can receive, from the sensor1440, information pertaining to the vehicle10. The information can include operational data of the vehicle10. For example, the information can include a distance between the vehicle10and an object (e.g., a curb, a lane in the road, a vehicle, and/or among other objects). The operator manager1425can compare the operational data to a predetermined set of operational data. For example, the operator manager1425can compare the distance between the lane in the road and the vehicle10with a predetermined distanced. The operator manager1425can determine that the difference indicates a deviation in the operation of the vehicle10. For example, the operator manager1425can determine that vehicle is departing the lane in the road.

The operator manager1425can communicate, responsive to determining the deviation in the operation of the vehicle, with the controller1435. The operator manager1425can provide, to the controller1435, an indication of the deviation in the operation of the vehicle. The controller1435can communicate with and/or otherwise interact with at least one of the audio device1450and/or the display device1445. For example, the controller1435can send a signal to the audio device1450that causes the audio device to produce an audible alert. The audible alert can include the deviation in the operation of the vehicle10. For example, the audible alert can indicate a lane departure warning. The audible alert can include at least one of a collision warning, a blind spot warning, a component error warning (e.g., the lift arm142is experiencing a malfunction, etc.), and/or among other possible alerts.

FIG.15depicts a perspective view of the cab interior42, according to an exemplary embodiment. The cab interior42can include the display device1445and the I/O device1460.FIG.15depicts the cab interior42including both a first display device1445as an instrument cluster display and a second display device1445as a center console display. The first display device1445and/or second display device1445can display at least one user interface. For example, the first display device1445can display a user interface having a first view of the vehicle10while the vehicle10is in collection mode and the second display device1445can display a user interface having a first view of the vehicle10. The first view displayed by the first user device1445can be different that the first view displayed by the second user device1445.

FIG.15also depicts the cab interior42including both a first I/O device1460as a steering wheel and a second I/O device1460as a joystick. The operator of the vehicle10can interact with the second I/O device1460to engage and/or otherwise operate at least one component of the vehicle10. For example, the operator of the vehicle10can use the second I/O device1460to active the tailgate actuator138. Additionally, the operator of the vehicle10engaging with the second I/O device1460can result in the sensors1440detecting the interaction. The sensors1440can, responsive to detecting the interaction, communication with the control system1403. The control system1403and/or a component thereof can receive the communication from the sensor1440. For example, the mode manager1420can receive, from the sensor1440, the detection of the interaction. The mode manager1420can determine, based on the interaction, that the vehicle10is in dump mode.

FIG.16depicts a perspective view of a steering wheel (e.g., the first I/O device1460shown inFIG.15), according to an exemplary embodiment. The first I/O device1460can have a plurality of zones (e.g., zones1601,1602and1603). Each zone can have a plurality of buttons (e.g., buttons1605). Each button can result the vehicle10and/or a component thereof performing a certain function, task and/or action. A role (e.g., an action that results from interacting with buttons1605) of each button1605can be configured, customized and/or otherwise established by the operator of the vehicle10. For example, the operator of the vehicle10can establish the buttons1605of the zone1602can control an environmental condition of the vehicle10(e.g., the buttons1605can raise and/or lower the temperature of in the interior cab42, adjust the HVAC fan speed, turn on or off the defrost, etc.). To continue this example, a first button1605in the zone1602can toggle, adjust, modify and/or other control HVAC modes (e.g., face, face and feet, feet, feet and defrost, defrost, auto, off, etc.), a second button1605in the zone1602can toggle, adjust, modify, and/or otherwise control blower speed (e.g., high, medium, low, etc.) and a third button1605of the zone1602can toggle, adjust, modify and/or otherwise change the temperature of the interior of the cable42(e.g., change temperature from 70 degrees Fahrenheit to 68 degrees Fahrenheit). The buttons1605of the zone1602can be and/or include separate I/O devices1460. The interaction with the buttons1605can result in the climate control1465receiving signals from the control system1403causing the climate control1465to adjust the environmental conditions of the interior cab42.

As another example, the operator of the vehicle10can establish that the buttons1605of the zone1601can control components of the vehicle10. For example, a first button1605of the zone1601can activate, deactivate, move and/or otherwise control the tailgate actuator138, a second button1605of the zone1601can activate, deactivate, move and/or otherwise control the arms142, and a third button1605of the zone1601can activate, deactivate, move and/or otherwise control the lift actuator172. The buttons1605of the zone1601can be and/or include separate I/O devices1460. The interaction with the buttons1605can result in the controller1435sending signals to the components of the vehicle10that correspond to the button1605engaged by the operator of the vehicle10.

FIG.17depicts a perspective view of a panel1703, according to an exemplary embodiment. The panel1703can be housed within the interior cab42. The panel1703can include the second I/O device1460(e.g., the joystick). The panel1703can also include at least one button1705. The button1705can active and/or deactivate the braking components (e.g., brake actuators, brake pads, brake discs, brake drums, etc.) and/or brake system of the vehicle10. The button1705can be and/or include the I/O device1460. The operator engaging with the button1705can result in the I/O device1460communicating with the control system1403. For example, the operator manager1425can receive, from the I/O device1460, an indication that the operator of the vehicle10has engaged the button1705. The operator manager1425can communicate to the controller1435the indication and the controller1435can deactivate and/or activate the brake system of the vehicle10.

FIG.18depicts a user interface1800depicting a charge cycle for an electric vehicle, according to an exemplary embodiment. The user interface1800can depict a charge cycle for the vehicle10. For example, the user interface1800can be a user interface that is generated by the interface generator1430and displayed by the display device1445. The user interface1800can include the SoC of the vehicle10, an icon including a warning to unplug the vehicle before operating, and a graphical representation of the vehicle10.

The user interface1800can be generated responsive to the operator of the vehicle10opening the door44. For example, the operator manager1425can determine that the door44has been opened and the operator manager1425can provide, to the interface generator1430, an indication that the door44has been opened. The interface generator1430can then generate a user interface (e.g., the user interface1800) including information pertaining to the charging of the vehicle10. The information can include the SoC of the vehicle10. The interface generator1430can provide the user interface1800to the display device1445. The display device1445receiving the user interface1800can cause the display device1445to display the user interface1800.

FIG.19depicts a perspective view of a display device1905including a user interface1910, according to an exemplary embodiment. The display device1905can be the display device1445. For example, the display device1905can be the second display device1445(e.g., the center console display depicted inFIG.15). The user interface1910can be generated by the interface generator1430. The user interface1910can be generated responsive to the mode manager1420determining that the vehicle10is in collection mode. The information shown in the user interface1910can be information generated, provided and/or otherwise created by components in the system1400. The user interface1910can include at least one view of the vehicle10. For example, the user interface1910can include a side view of the vehicle10and a hopper view of the vehicle10. The views can be views that are provided by the sensors1440. The user interface1910can also include a text box that includes the current mode of the vehicle10.FIG.19depicts an example of the text box indicating that collection mode has been initiated. The user interface1910can also include a text box that includes collection information.FIG.19depicts an example of the collection information including an estimated vehicle speed and an estimated distance to an object (e.g., a garbage can). WhileFIG.19depicts the user interface1900including a side view and a hopper view, the user interface1900can include at least one of an aerial view, a360view, a rear right view, a rear left view, a rear view, a side right view, a side left view, a front right view, a front left view, a front view and/or among other possible views.

FIG.20depicts a perspective view of the display device1905including a user interface2000, according to an exemplary embodiment. The user interface2000can be generated by the interface generator1430. The user interface2000can be generated responsive to the mode manager1420determining that the vehicle10is in drive mode. The information shown in the user interface2000can be information generated, provided and/or otherwise created by components in the system1400. The user interface2000can include at least one view of the vehicle10. For example, the user interface2000can include a side view of the vehicle10and a360view of the vehicle10. The views can be views that are provided by the sensors1440. The user interface2000can also include a text box that includes the current mode of the vehicle10.FIG.20depicts an example of the text box indicating that drive mode has been initiated. The user interface2000can also include a text box that includes drive information.FIG.20depicts an example of the drive information including an estimated vehicle speed and an estimated time to next pickup. WhileFIG.20depicts the user interface2000including a side view and a360view, the user interface2000can include at least one of an aerial view, a360view, a rear right view, a rear left view, a rear view, a side right view, a side left view, a front right view, a front left view, a front view and/or among other possible views.

FIG.21depicts a perspective view of the display device1905including a user interface2100, according to an exemplary embodiment. The user interface2100can be generated by the interface generator1430. The user interface2100can be generated responsive to the mode manager1420determining that the vehicle10is in dump mode. The information shown in the user interface2100can be information generated, provided and/or otherwise created by components in the system1400. The user interface2100can include at least one view of the vehicle10. For example, the user interface2100can include a360view of the vehicle10and a hopper view of the vehicle10. The views can be views that are provided by the sensors1440. The user interface2100can also include a text box that includes the current mode of the vehicle10.FIG.21depicts an example of the text box indicating that dump mode has been initiated. The user interface2100can also include a text box that includes collection information.FIG.21depicts an example of the collection information including an estimated vehicle speed and an estimated distance to an object (e.g., a garbage can). WhileFIG.21depicts the user interface2100including a360view and a hopper view, the user interface2100can include at least one of an aerial view, a360view, a rear right view, a rear left view, a rear view, a side right view, a side left view, a front right view, a front left view, a front view and/or among other possible views.

FIG.22depicts a perspective view of a display device2205including a user interface2200, according to an exemplary embodiment. The display device2205can be the display device1445. For example, the display device2205can be the first display device1445(e.g., the instrument cluster display depicted inFIG.15). The user interface2200can be generated by the interface generator1430. The user interface2200can be generated responsive to the mode manager1420determining that the vehicle10is in collection mode. The information shown in the user interface2200can be information generated, provided and/or otherwise created by components in the system1400. The user interface2200can include at least one view of the vehicle10. For example, the user interface2200can include a360view of the vehicle10and a side view of the vehicle10. The views can be views that are provided by the sensors1440. The user interface2200can also include a text box that includes the current mode of the vehicle10.FIG.22depicts an example of the text box indicating that collection mode has been initiated. The user interface2200can also include a text box that includes collection information.FIG.22depicts an example of the collection information including an estimated vehicle speed and an estimated distance to an object (e.g., a garbage can). WhileFIG.22depicts the user interface22including a360view and a side view, the user interface2200can include at least one of an aerial view, a360view, a rear right view, a rear left view, a rear view, a side right view, a side left view, a front right view, a front left view, a front view and/or among other possible views.

FIG.23depicts a perspective view of the display device2205including a user interface2300, according to an exemplary embodiment. The user interface2300can be generated by the interface generator1430. The user interface2300can be generated responsive to the mode manager1420determining that the vehicle10is in drive mode. The information shown in the user interface2300can be information generated, provided and/or otherwise created by components in the system1400. The user interface2300can include at least one view of the vehicle10. For example, the user interface2300can include a360view of the vehicle10. The views can be views that are provided by the sensors1440. The user interface2300can also include a text box that includes the current mode of the vehicle10.FIG.23depicts an example of the text box indicating that drive mode has been initiated. The user interface2300can also include a text box that includes drive information.FIG.23depicts an example of the drive information including an estimated vehicle speed and an estimated time to next pickup. WhileFIG.23depicts the user interface2300including a360view, the user interface2300can include at least one of an aerial view, a360view, a rear right view, a rear left view, a rear view, a side right view, a side left view, a front right view, a front left view, a front view and/or among other possible views.