Patent Application
20240034280
The present disclosure relates generally to autonomous vehicles (AVs) and, more specifically, to cleaning sensors of AVs.
An AV is a vehicle that is capable of sensing and navigating its environment with little or no user input. An autonomous vehicle may sense its environment using sensing devices such as Radio Detection and Ranging (RADAR), Light Detection and Ranging (LIDAR), image sensors, cameras, and the like. An autonomous vehicle system may also use information from a global positioning system (GPS), navigation systems, vehicle-to-vehicle communication, vehicle-to-infrastructure technology, and/or drive-by-wire systems to navigate the vehicle. As used herein, the phrase “autonomous vehicle” includes both fully autonomous and semi-autonomous vehicles.
To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
Overview
The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for all of the desirable attributes disclosed herein. Details of one or more implementations of the subject matter described in this Specification are set forth in the description below and the accompanying drawings.
As described herein, AV sensors can be cleaned by using fluid, including gas and liquid. In some embodiments, gas (e.g., ambient air, etc.) may be used to clean or cool AV sensors. For example, gas can be sprayed towards one or more surfaces of an AV sensor to clean contaminants on the surface(s) of the AV sensor. The gas may remove one or more contaminants (e.g., rain, cleaning liquid, dirt, etc.) from a surface of the AV sensor. Alternatively or additionally, the gas may facilitate dissipation of heat generated by the AV sensor or another part of the AV during the operation of the AV. During the cleaning or cooling process, the view of the AV sensor may not be occluded.
An example fluid cleaning system of the present disclosure may include one or more fans and one or more flow channels associated with one or more AV sensors. A fan may be localized to the AV sensors. For example, the fan may be fixed at a location that is proximate to one or more AV sensors. The fan can blow air or other types of gases towards the one or more AV sensors. A flow channel (e.g., an air duct, etc.) may provide a flow passage for air to flow from a fan to an AV sensor. The air duct may have one end connected or proximate to the fan and another end connected or proximate to the AV sensor. An example fluid cleaning system may include a compressor, which may compress ambient air. The compressed air may be stored in a pressure tank that can maintain a certain pressure or pressures, which may be higher than the ambient air pressure. The compressed air may flow from the pressure tank, e.g., through one or more flow channels, towards one or more AV sensors.
In some embodiments, a fluid for cleaning one or more sensors of an AV may be warmed up by utilizing heat generated by one or more other parts of the AV. An example part may be a battery, motor, engine, sensor (the sensor to be cleaned or another sensor), etc. The heat generated by a part may be an unintended or even undesired result of an operation of the part. For instance, a battery can generate heat during its operation. However, the heat may impair performance or lifetime of the battery or another part. Heating the fluid with such heat not only can enhance the cleaning effect of the fluid but also can cool down the part and avoid overheating of the part (or another part influenced by the heat).
An example fluid cleaning system of the present disclosure may include a reservoir storing a cleaning fluid (also referred to as “fluid”). The fluid can be used to clean AV sensors, e.g., sensors at the exterior of AVs. The fluid can also be used to clean other AV parts, e.g., wind shield, mirror, and so on. To clean a sensor, the fluid may be sprayed onto one or more surfaces of the sensor, e.g., by a spraying nozzle. A surface may be a window, an enclosure, a lens, a filter, and so on. Before the fluid is sprayed, the fluid can be heated by using one or more heat sources. The fluid can flow between the reservoir, heat sources, and spraying nozzles through various flow channels formed in association with the AV.
An example heat source is a heat exchanger. The heat exchanger can transfer heat from an AV part to the fluid. In some embodiments, the heat exchanger includes a container or a flow channel with thermally conductively walls. Heat can be transferred from the part to the fluid when the fluid is in the heat exchanger. Another example heat source is a heater that generates heat intended for heating the fluid. An example heater may be a local heater to the sensor to be cleaned, e.g., the heater is closer to the sensor than the reservoir. With such a local heater, the loss of heat due to fluid flow from the reservoir to the spraying nozzle can be minimized. Another example heater can be inside the reservoir. For instance, the heater can be immersed in the fluid. Yet another example heater may be a local heater to another AV part to be cleaned by the fluid, e.g., the wind shield. The local heater can be closer to the other AV part than the sensor. As the fluid has a higher temperature, the cleaning effect can be better, e.g., as hotter fluid can dissolve more contaminants, or dissolve contaminants faster, than colder fluid.
A fluid cleaning cycle (i.e., a cycle of using a fluid to clean an AV sensor) may be controlled by the onboard computer of the AV. In some embodiments, the onboard computer may control a heat source. The onboard computer may control a temperature of the heat source, a duration of time that the fluid is being heated by the heat source, fluid flowing into the heat source, fluid flowing out of the heat source, and so on. The onboard computer may also control a spraying nozzle that sprays a cleaning fluid, e.g., by actuating a solenoid relay in a manifold. For instance, the onboard computer can control the amount of cleaning fluid sprayed by the spraying nozzle, a flowing speed of the fluid in or at the spraying nozzle, and so on. The onboard computer may also control a flow channel. For instance, the onboard computer can control a flow rate of the fluid flowing in the flow channel, a valve associated with the flow channel, and so on.
As will be appreciated by one skilled in the art, aspects of the present disclosure, in particular aspects of AV sensor calibration, described herein, may be embodied in various manners (e.g., as a method, a system, a computer program product, or a computer-readable storage medium). Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Functions described in this disclosure may be implemented as an algorithm executed by one or more hardware processing units, e.g., one or more microprocessors, of one or more computers. In various embodiments, different steps and portions of the steps of each of the methods described herein may be performed by different processing units. Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer-readable medium(s), preferably non-transitory, having computer-readable program code embodied, e.g., stored, thereon. In various embodiments, such a computer program may, for example, be downloaded (updated) to the existing devices and systems (e.g., to the existing perception system devices or their controllers, etc.) or be stored upon manufacturing of these devices and systems.
The following detailed description presents various descriptions of specific certain embodiments. However, the innovations described herein can be embodied in a multitude of different ways, for example, as defined and covered by the claims or select examples. In the following description, reference is made to the drawings where like reference numerals can indicate identical or functionally similar elements. It will be understood that elements illustrated in the drawings are not necessarily drawn to scale. Moreover, it will be understood that certain embodiments can include more elements than illustrated in a drawing or a subset of the elements illustrated in a drawing. Further, some embodiments can incorporate any suitable combination of features from two or more drawings.
The following disclosure describes various illustrative embodiments and examples for implementing the features and functionality of the present disclosure. While particular components, arrangements, or features are described below in connection with various example embodiments, these are merely examples used to simplify the present disclosure and are not intended to be limiting.
In the Specification, reference may be made to the spatial relationships between various components and to the spatial orientation of various aspects of components as depicted in the attached drawings. However, as will be recognized by those skilled in the art after a complete reading of the present disclosure, the devices, components, members, apparatuses, etc. described herein may be positioned in any desired orientation. Thus, the use of terms such as “above”, “below”, “upper”, “lower”, “top”, “bottom”, or other similar terms to describe a spatial relationship between various components or to describe the spatial orientation of aspects of such components, should be understood to describe a relative relationship between the components or a spatial orientation of aspects of such components, respectively, as the components described herein may be oriented in any desired direction. When used to describe a range of dimensions or other characteristics (e.g., time, pressure, temperature, length, width, etc.) of an element, operations, or conditions, the phrase “between X and Y” represents a range that includes X and Y.
In addition, the terms “comprise,” “comprising,” “include,” “including,” “have,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a method, process, device, or system that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such method, process, device, or system. Also, the term “or” refers to an inclusive or and not to an exclusive or.
As described herein, one aspect of the present technology is the gathering and use of data available from various sources to improve quality and experience. The present disclosure contemplates that in some instances, this gathered data may include personal information. The present disclosure contemplates that the entities involved with such personal information respect and value privacy policies and practices.
Other features and advantages of the disclosure will be apparent from the following description and the claims.
The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for all of the desirable attributes disclosed herein. Details of one or more implementations of the subject matter described in this Specification are set forth in the description below and the accompanying drawings.
Example AV System
The fleet management system 120 receives service requests for the AVs 110 from the user devices 130. As shown in
In some embodiments, a user device 130 executes an application allowing a user 135 of the user device 130 to interact with the fleet management system 120. For example, a user device 130 executes a browser application to enable interaction between the user device 130 and the fleet management system 120 via a network. In another embodiment, a user device 130 interacts with the fleet management system 120 through an application programming interface (API) running on a native operating system of the user device 130, such as IOS® or ANDROID™. The application may be provided and maintained by the fleet management system 120. The fleet management system 120 may also update the application and provide the update to the user device 130.
In some embodiments, a user 135 may make various service requests to the fleet management system 120 through a user device 130. A user device 130 may provide its user 135 a user interface (UI), through which the user 135 can make service requests. For instance, a user 135 may make ride requests (e.g., a request to pick up a person from a pickup location and drop off the person at a destination location), delivery requests (e.g., a request to delivery one or more items from a location to another location), or requests for other services that the AVs 110 can provide. The UI may allow users 135 to provide locations (e.g., pickup location, destination location, etc.) or other information that would be needed by AVs 110 to provide services requested by the users 135.
The AV 110 may be a fully autonomous automobile, but may additionally or alternatively be any semi-autonomous or fully autonomous vehicle; e.g., a boat, an unmanned aerial vehicle, a driverless car, etc. Additionally, or alternatively, the AV 110 may be a vehicle that switches between a semi-autonomous state and a fully autonomous state and thus, the AV may have attributes of both a semi-autonomous vehicle and a fully autonomous vehicle depending on the state of the vehicle. In some embodiments, some or all of the vehicle fleet managed by the fleet management system 120 are non-autonomous vehicles dispatched by the fleet management system 120, and the vehicles are driven by human drivers according to instructions provided by the fleet management system 120.
The AV 110 may include a throttle interface that controls an engine throttle, motor speed (e.g., rotational speed of electric motor), or any other movement-enabling mechanism; a brake interface that controls brakes of the AV (or any other movement-retarding mechanism); and a steering interface that controls steering of the AV (e.g., by changing the angle of wheels of the AV). The AV 110 may additionally or alternatively include interfaces for control of any other vehicle functions, e.g., wind shield wipers, headlights, turn indicators, air conditioning, etc.
As shown in
The onboard computer 150 is connected to the sensor suite 140 and functions to control the AV 110 and to process sensed data from the sensor suite 140 and/or other sensors in order to determine the state of the AV 110. Based upon the vehicle state and programmed instructions, the onboard computer 150 modifies or controls behavior of the AV 110. The onboard computer 150 is preferably a general-purpose computer adapted for I/O communication with vehicle control systems and sensor suite 140, but may additionally or alternatively be any suitable computing device. The onboard computer 150 is preferably connected to the Internet via a wireless connection (e.g., via a cellular data connection). Additionally or alternatively, the onboard computer 150 may be coupled to any number of wireless or wired communication systems.
The onboard computer 150 can also maintain the sensor suite 140. In some embodiments, the onboard computer 150 monitors conditions of sensors in the sensor suite 140. For instance, the onboard computer 150 can maintain cleanness of sensors. The cleanness of sensors can be important to performance of the AV 110. For instance, the cleanness of a sensor can influence the accuracy in the detection of the sensor, which can further influence the performance of the AV 110 as the AV 110 operates based on the detection of the sensor. The onboard computer 150 may determine whether a sensor needs cleaning and in response to determining that the sensor needs cleaning, the onboard computer 150 can control a fluid cleaning system to clean the sensor. Examples of the fluid cleaning system include the fluid cleaning system 400, 500, 600, 700, 800, 900, and 1000 described below in conjunction with
In some embodiments, the onboard computer 150 may determine that a sensor needs cleaning based on detection of contamination (e.g., dust, dirt, fingerprints, moisture, bug splatter, birth feces, mud splatter, etc.) of the sensor, e.g., by using sensor data captured by the sensor itself, sensor data captured by one or more other sensors, or some combination thereof. In alternative embodiments, the onboard computer 150 may request sensor cleaning on a regular basis. For instance, the onboard computer 150 may determine a schedule of cleaning a sensor and request sensor cleaning based on the schedule. Certain aspects regarding the onboard computer 150 are described below in conjunction with
The fleet management system 120 manages the fleet of AVs 110. The fleet management system 120 may manage one or more services that provides or uses the AVs, e.g., 3D printing service, ride service, delivery service, and so on. The fleet management system 120 selects one or more AVs (e.g., AV 110A) from a fleet of AVs 110 to perform a particular service or other task, and instructs the selected AV to provide the service. The fleet management system 120 may also send the selected AV information that the selected AV may use to complete the service. The fleet management system 120 also manages fleet maintenance tasks, such as fueling, inspecting, calibrating, and servicing of the AVs. As shown in
Example Sensor Suite
The exterior sensors 210 detect objects in an environment around the AV 110. The environment may include a scene in which the AV 110 operates. Example objects include persons, buildings, traffic lights, traffic signs, vehicles, street signs, trees, plants, animals, or other types of objects that may be present in the environment around the AV 110. An exterior sensor 210 may be affixed to an exterior surface of the AV 110, e.g., either directly (e.g., the exterior sensor 210 is attached on the exterior surface of the AV 110) or indirectly (e.g., the exterior sensor 210 is affixed to a structure that is attached on the exterior surface of the AV 110).
In some embodiments, the exterior sensors 210 include exterior cameras having different views, e.g., a front-facing camera, a back-facing camera, and side-facing cameras. One or more exterior sensors 210 may be implemented using a high-resolution imager with a fixed mounting and field of view. One or more exterior sensors 210 may have adjustable field of views and/or adjustable zooms. In some embodiments, the exterior sensors 210 may operate continually during operation of the AV 110. In an example embodiment, the exterior sensors 210 capture sensor data (e.g., images, etc.) of a scene in which the AV 110 drives. In other embodiment, the exterior sensors 210 may operate in accordance with an instruction from the onboard computer 150 or an external system, such as the fleet management system 120. Some of all of the exterior sensors 210 may capture sensor data of one or more objects in an environment surrounding the AV 110 based on the instruction.
The LIDAR sensor 220 measures distances to objects in the vicinity of the AV 110 using reflected laser light. The LIDAR sensor 220 may be a scanning LIDAR that provides a point cloud of the region scanned. The LIDAR sensor 220 may have a fixed field of view or a dynamically configurable field of view. The LIDAR sensor 220 may produce a point cloud that describes, among other things, distances to various objects in the environment of the AV 110.
The RADAR sensor 230 can measure ranges and speeds of objects in the vicinity of the AV 110 using reflected radio waves. The RADAR sensor 230 may be implemented using a scanning RADAR with a fixed field of view or a dynamically configurable field of view. The RADAR sensor 230 may include one or more articulating RADAR sensors, long-range RADAR sensors, short-range RADAR sensors, or some combination thereof.
The interior sensors 240 detect the interior of the AV 110, such as objects inside the AV 110. Example objects inside the AV 110 include passengers, client devices of passengers, components of the AV 110, items delivered by the AV 110, items facilitating services provided by the AV 110, and so on. The interior sensors 240 may include multiple interior cameras to capture different views, e.g., to capture views of an interior feature, or portions of an interior feature. The interior sensors 240 may be implemented with a fixed mounting and fixed field of view, or the interior sensors 240 may have adjustable field of views and/or adjustable zooms, e.g., to focus on one or more interior features of the AV 110. The interior sensors 240 may transmit sensor data to a perception module (such as the perception module 330 described below in conjunction with
In some embodiments, some or all of the interior sensors 240 may operate continually during operation of the AV 110. In other embodiment, some or all of the interior sensors 240 may operate in accordance with an instruction from the onboard computer 150 or an external system. The interior sensors 240 may include a camera that can capture images of passengers. The interior sensors 240 may also include one or more microphones that can capture sound in the AV 110, such as a conversation made by a passenger.
The contaminant detector 250 detects contamination of one or more other sensors in the sensor suite 140, such as one or more exterior sensors 210, one or more LIDAR sensors 220, one or more RADAR sensors 230, one or more interior sensors 240, or some combination thereof. The contaminant detector 250 may detect contaminants accumulated on a sensor, such as on a portion, a surface, or a component of a sensor. Additionally or alternatively, the contaminant detector 250 may detect contaminants in an environment surrounding a sensor. For instance, the contaminant detector 250 can detect objects in the environment that can contaminate the sensor and undermine performance of the sensor. Such objects may also be referred to as contaminants. Example contaminants include dirt, dust, dirt, moisture, or other objects that can contaminate the sensor and undermine performance of the sensor. The contaminant detector 250 may capture sensor data indicating a contaminant level of the environment.
The contaminant detector 250 may be associated with one or more other sensors of the sensor suite 140 and detect contaminations for the one or more other sensors. The contaminant detector 250 may be affixed on the one or more other sensors or be physically separately from the one or more other sensors. In some embodiments, the contaminant detector 250 is one of the exterior sensors 210 or one of the interior sensors 240.
Example Onboard Computer
The map datastore 310 stores a detailed map of environments through which the AV 110 may travel. The map datastore 310 may store environmental features captured by exterior sensors (e.g., the exterior sensor 210) of the AV 110. In some embodiments, the map datastore 310 may also store environmental features captured by other AVs. In some embodiments, the map datastore 310 includes data describing roadways, such as locations of roadways, connections between roadways, roadway names, speed limits, traffic flow regulations, toll information, etc. The map datastore 310 may further include data describing buildings (e.g., locations of buildings, building geometry, building types), and data describing other objects (e.g., location, geometry, object type) that may be in the environments of an AV. The map datastore 310 may also include data describing other features, such as bike lanes, sidewalks, crosswalks, traffic lights, parking lots, signs, billboards, etc. In some embodiments, the map datastore 310 stores map data for a city or region in which the AV 110 is located.
Some of the map datastore 310 may be gathered by the AV 110. For example, images obtained by exterior sensors (e.g., the exterior sensor 210) of the AV 110 may be used to learn information about the AV′ environments. The output of the exterior sensors may be processed to identify particular conditions in the environment, such as road conditions, weather conditions, etc. In some embodiments, certain map data (e.g., conditions that are expected to be temporary) may expire after a certain period of time. In some embodiments, data captured later by the AV 110 or a different AV may indicate that a previously-observed feature is no longer present (e.g., weather has been changed, construction work zone has been removed, etc.) and in response, the map data may be removed from the map datastore 310.
The sensor interface 320 interfaces with the sensors in the sensor suite 140. The sensor interface 320 is configured to receive data captured by sensors of the sensor suite 140, including data from exterior sensors mounted to the outside of the AV 110, and data from interior sensors mounted in the passenger compartment of the AV 110. The sensor interface 320 may have subcomponents for interfacing with individual sensors or groups of sensors of the sensor suite 140, such as a camera interface, a LIDAR interface, a RADAR interface, a microphone interface, etc.
The sensor interface 320 may also request data from the sensor suite 140, e.g., by requesting that a sensor capture data in a particular direction or at a particular time. For example, the sensor interface 320 may request an interior sensor (e.g., the interior sensor 240) to detect one or more features in the AV 110 periodically to monitor status of the features and to facilitate timely replacement of a feature if the feature malfunctions. As another example, in response to the perception module 330 or another module determining that a feature in the AV 110 malfunctions, the sensor interface 320 instructs the interior sensor to capture additional data (e.g., dimensions, shape, etc.) of the feature, e.g., by zooming in and focusing on the feature.
The perception module 330 identifies objects and/or other features captured by the sensors of the AV 110. For example, the perception module 330 identifies objects in the environment of the AV 110 and captured by one or more exterior sensors (e.g., the sensors 210-230). The perception module 330 may include one or more classifiers trained using machine learning to identify particular objects. For example, a multi-class classifier may be used to classify each object in the environment of the AV 110 as one of a set of potential objects, e.g., a vehicle, a pedestrian, or a cyclist. As another example, a pedestrian classifier recognizes pedestrians in the environment of the AV 110, a vehicle classifier recognizes vehicles in the environment of the AV 110, etc. The perception module 330 may identify travel speeds of identified objects based on data from the RADAR sensor 230, e.g., speeds at which other vehicles, pedestrians, or birds are traveling. As another example, the perception module 33—may identify distances to identified objects based on data (e.g., a captured point cloud) from the LIDAR sensor 220, e.g., a distance to a particular vehicle, building, or other feature identified by the perception module 330. The perception module 330 may also identify other features or characteristics of objects in the environment of the AV 110 based on image data or other sensor data, e.g., colors (e.g., the colors of Christmas lights), sizes (e.g., heights of people or buildings in the environment), makes and models of vehicles, pictures and/or words on billboards, etc.
The perception module 330 may further process data from captured by interior sensors (e.g., the interior sensors 240 of
In some embodiments, the perception module 330 fuses data from one or more interior sensors 240 with data from exterior sensors (e.g., exterior sensors 210) and/or map datastore 310 to identify environmental objects that one or more users are looking at. The perception module 330 determines, based on an image of a user, a direction in which the user is looking, e.g., a vector extending from the user and out of the AV 110 in a particular direction. The perception module 330 compares this vector to data describing features in the environment of the AV 110, including the features' relative location to the AV 110 (e.g., based on real-time data from exterior sensors and/or the AV's real-time location) to identify a feature in the environment that the user is looking at.
While a single perception module 330 is shown in
The control module 340 controls operations of the AV 110, e.g., based on information from the sensor interface 320 or the perception module 330. In some embodiments, the control module 340 controls operation of the AV 110 by using a trained model, such as a trained neural network. The control module 340 may provide input data to the control model, and the control model outputs operation parameters for the AV 110. The input data may include sensor data from the sensor interface 320 (which may indicate a current state of the AV 110), objects identified by the perception module 330, or both. The operation parameters are parameters indicating operation to be performed by the AV 110. The operation of the AV 110 may include perception, prediction, planning, localization, motion, navigation, other types of operation, or some combination thereof. The control module 340 may provide instructions to various components of the AV 110 based on the output of the control model, and these components of the AV 110 will operation in accordance with the instructions. In an example where the output of the control model indicates that a change of traveling speed of the AV 110 is required given a prediction of traffic condition, the control module 340 may instruct the motor of the AV 110 to change the traveling speed of the AV 110. In another example where the output of the control model indicates a need to detect characteristics of an object in the environment around the AV 110 (e.g., detect a speed limit), the control module 340 may instruct the sensor suite 140 to capture an image of the speed limit sign with sufficient resolution to read the speed limit and instruct the perception module 330 to identify the speed limit in the image.
The sensor cleaning module 350 manages cleaning of one or more sensor in the sensor suite 140. In some embodiments, the sensor cleaning module 350 may manage the cleaning of a category of sensors, e.g., optical sensors or other types of sensors. The sensor cleaning module 350 may control operation of one or more fluid cleaning systems for cleaning sensors. Example fluid cleaning systems including fluid cleaning systems 400, 500, 600, 700, and 800 described below in conjunctions with
The sensor cleaning module 350 may determine whether a sensor (e.g., a surface of a sensor) needs cleaning. In some embodiments, the sensor cleaning module 350 uses sensor data to determine whether a sensor needs cleaning. The sensor data may be from the sensor itself or another sensor, e.g., the contaminant detector 250 in
The sensor cleaning module 350 may determine a contamination condition of the sensor based on the sensor data. In an example, the sensor cleaning module 350 may identify, from the sensor data, contaminants accumulated on the sensor. The identification of the contaminants may alternatively be done by the perception module 330, which can provide information of the identification to the sensor cleaning module 350. The sensor cleaning module 350 may determine whether the contamination condition of the sensor meets a threshold condition, e.g., a threshold number of contaminants, a threshold concentration of contaminants (e.g., number per unit area or unit volume), and so on. In response to determining that the contamination condition of the sensor meets the threshold condition, the sensor cleaning module 350 determines that the sensor needs cleaning. In another example, the sensor cleaning module 350 may determine a performance of the sensor based on the sensor data. The performance may be an accuracy, brightness, signal-to-noise ratio, or other attributes of the sensor data. The sensor cleaning module 350 can compare the performance of the sensor with a corresponding predetermined performance (e.g., required performance, expected performance, etc.) of the sensor and in response to determining that the performance of the sensor does not meet the predetermined performance, the sensor cleaning module 350 determines that the sensor needs cleaning.
In addition or alternative to sensor data, the sensor cleaning module 350 may use other data to determine whether a sensor needs clean. For instance, the sensor cleaning module 350 may determine a frequency of cleaning a sensor. The frequency indicates how often the sensor needs cleaning. The sensor cleaning module 350 may determine the frequency based on one or more attributes of the sensor (e.g., pose (position, orientation, or both) of the sensor, material of the sensor, sensitivity to contaminants, etc.), one or more attributes of the environment surrounding the sensor (e.g., cleanness of the environment, weather of the environment, etc.). The sensor cleaning module 350 can maintain a record of historical cleanings of the sensor and/or determine a time for the next cleaning. The sensor cleaning module 350 can determine that the sensor needs cleaning when the determined time is reached.
The sensor cleaning module 350 may control one or more heat sources that heat a fluid used to clean sensors. A heat source may be a heat exchanger (e.g., the heat exchanger 440, 540, 545, 645, 945A, or 945B described below in conjunctions with
The sensor cleaning module 350 may also control a spraying nozzle that sprays a fluid. The onboard computer can control the amount of fluid sprayed by the spraying nozzle, spraying direction, distance from the spraying nozzle to the sensor to be cleaned, flowing speed of the fluid in or at the spraying nozzle, and so on. The onboard computer may also control a flow channel. For instance, the onboard computer can control a flow rate of the fluid flowing in the flow channel, a valve associated with the flow channel, and so on.
The sensor cleaning module 350 may also determine whether a sensor is sufficiently cleaned after a cleaning cycle, e.g., based on sensor data from the sensor itself or the contaminant detector 250. The sensor cleaning module 350 may determine whether the amount of contaminants accumulated on the sensor meets a threshold, or determine whether a performance of the sensor meets a threshold. In response to determining that sensor is sufficiently cleaned, the sensor cleaning module 350 may provide a notification to the sensor interface 320 and the sensor interface 320 can instruct the sensor to capture data to be used by the perception module 330 or control module 340 to control operation of the AV 110. In response to determining that sensor is not sufficiently cleaned, the sensor cleaning module 350 may repeat the cleaning cycle until the sensor is sufficiently cleaned.
In some embodiments, the sensor cleaning module 350 may determine that a sensor is insufficiently cleaned after one or more cleaning cycles. In response to determining that the sensor is insufficiently cleaned, the sensor cleaning module 350 may determine (or instruct the control module 340 to determine) whether the AV 110 can operate with the insufficiently cleaned sensor. For instance, the sensor cleaning module 350 or control module 340 may determine whether the safety and/or passenger comfort meets a threshold safety and/or passenger comfort if the AV 110 operates with the insufficiently cleaned sensor. The sensor cleaning module 350 or control module 340 may consider various factors, such as the type of service being provided or to be provided by the AV 110, the navigation route of the AV 110, the function of the sensor, availability of other sensors, and so on. In embodiments where it is determined that the AV 110 can operate with the insufficiently cleaned sensor, the control module 340 may allow the AV 110 to proceed as normal. The control module 340 may instruct the AV 110 to complete a trip but return for service after the trip is done. In embodiments where it is determined that the AV 110 cannot operate with the insufficiently cleaned sensor, the control module 340 may instruct the AV 110 to navigate to a safe spot (e.g., safely pull over, drive to a nearby parking lot, etc.) or to stop immediately.
Example Fluid Cleaning Systems
The reservoir 420 stores the fluid to be used to clean the sensors 410 and a wind shield 450 of the vehicle. The fluid may include water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. The reservoir 420 may include an opening, through which the fluid can flow into the reservoir 420. The fluid can be used to clean the wind shield 450 and/or the sensors 410. In some embodiments, a portion of the fluid is used to clean the wind shield 450, and another portion of the fluid is used to clean the sensors 410. In other embodiments, the fluid can be used to clean other sensors or other parts of the AV 110. The fluid can be warmed up before it is used to clean the wind shield 450 and the sensors 410. With warmer fluid, the cleaning effect can be enhanced.
As shown in
The heat exchanger 440 is associated with a part 430 of the AV 110. The heat exchanger 440 receives the fluid from the reservoir 420 through the flow channel 470. The heat exchanger 440 can transfer heat generated by the part 430 to the fluid. In some embodiments, the heat exchanger 440 includes a container that can store the fluid, e.g., temporarily. The fluid, while being in the container, can receive heat generated by the part 430. The part 430 may be a component or subsystem of the AV 110, such as battery, motor, engine, or other parts of the AV 110 that can generate heat during operations of the AV 110. In some embodiments, the heat is a byproduct of the part 430 during an operation of the part 430. The generation of the heat may not be an intended function of the part 430. Rather, the heat may be an unintended or even undesired result of the operation of the part 430. Too much heat may even impair performance of the part 430 or another part that is adjacent to the part 430 that can receive the heat. By using the heat generated by the part 430 to warm up the fluid can not only enhance the effect of cleaning the sensors 410 with the fluid but also cool down the part 430 to avoid overheating of the part 430 (or overheating of one or more other parts that are adjacent to the part 430). In some embodiments, even when the amount of fluid in the reservoir 420 is too low to spraying fluid onto the sensors 410 or wind shield 450, circulation of the fluid (e.g., flow of the fluid from or back to the reservoir 420) can still be used to cool down the part 430. The heat exchanger 440 is connected to the flow channel 480, through which the fluid, after being heated by the heat exchanger 440, can flow to the spraying nozzles 415 and spraying nozzles 460.
The temperature of the heat exchanger 440 may be the same or similar to the temperature of the part 430. The heat exchanger 440 may be placed at a hot spot in or outside the part 430. The hot spot is a spot that can have a higher temperature than other spots of the part 430 or other parts of the AV 110 (e.g., the reservoir 420) during operations of the AV 110. In some embodiments, the heat exchanger 440 is partially or wholly enclosed by the part 430. Alternatively, the heat exchanger 440 may be outside the part 430. For instance, the heat exchanger 440 can be attached on an exterior surface of the part 430, and the exterior surface of the part 430 can be thermally conductive to transfer heat from the part 430 to the heat exchanger 440.
The flow channel 480 connects the heat exchanger to the spraying nozzles 415 and spraying nozzles 460. For purpose of simplicity and illustration, the flow channel 480 is shown as dashed lines in
In some embodiments, the fluid cleaning system 400 includes a single valve that may be upstream from the spraying nozzles 460 and 415 so that the spraying nozzles 460 and 415 may all spray fluid at the same time. In other embodiments, the spraying nozzles 460 and 415 may be controlled by separate valves and can spray fluid at different times, e.g., based on the cleaning need of the sensors 410 and the windshield 450. The two spraying nozzles 415 may be associated with separate valves so that they can spray fluid onto the sensors 410 at different times, which can facilitate the detection of one sensor 410 while the other sensor 410 is being cleaned so that the two sensors 410 are not blinded at the same time. A predetermined pressure may be established by a pump associated with the reservoir 420. There may be a pressure build delay, e.g., a period of time between the activation of the pump and the opening of the valve(s) to allow flow. The fluid cleaning system 400 may also include one or more check valves that allow one-way flow, so that the corresponding flow channel(s) can be “primed” with pressure to minimize the delay to build pressure from pump activation. Additionally or alternatively, the pressure build delay can be minimized by having a pressure monitor within the flow channels and periodically having the reservoir pump rebuild pressure in the flow channels if it bleeds of (although it is protected by check valves, there might be a slow bleed).
Each spraying nozzle 415 is associated with a sensor 410. In other embodiments, a spraying nozzle 415 may be associated with multiple sensors 410. The spraying nozzle 415 can spray fluid from the heat exchanger 440 onto a surface of the sensor 410. The surface may be a surface of an enclosure of the sensor 410, a surface of a window of the sensor 410, an optical surface (e.g., lens, filter, etc.) of the sensor 410, or other types of surfaces. Even though not shown in
The spraying nozzles 460 are associated with the wind shield 450. Each spraying nozzle 460 can spray fluid from the heat exchanger 440 onto a portion of the wind shield 450. Even though not shown in
The reservoir 520 stores the fluid to be used to clean the sensors 510. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. The reservoir 520 may include an opening, through which the fluid can flow into the reservoir 520. The fluid can be used to clean the sensors 510 and the wind shield 550. In some embodiments, a portion of the fluid is used to clean the wind shield 550, and another portion of the fluid is used to clean the sensors 510. In other embodiments, the fluid can be used to clean other sensors or other parts of the AV 110. The fluid can be warmed up before it is used to clean the wind shield 550 and the sensors 510. With warmer fluid, the cleaning effect can be enhanced. The reservoir 520 is connected to the flow channel 570. For purpose of simplicity and illustration, the flow channel 570 is shown as a dotted line in
The heat exchanger 540 is associated with a part 530 of the AV 110. The heat exchanger 540 receives the fluid from the reservoir 520 through the flow channel 570. The heat exchanger 540 can transfer heat generated by the part 530 to the fluid. The part 530 may be a battery, motor, engine, or other parts of the AV 110 that can generate heat during operations of the AV 110. In some embodiments, the heat is a byproduct of the part 530 during an operation of the part 530. The generation of the heat may not be an intended function of the part 530. Rather, the heat may be an unintended or even undesired result of the operation of the part 530. Too much heat may even impair performance of the part 530 or another part that is adjacent to the part 530 that can receive the heat. By using the heat generated by the part 530 to warm up the fluid can not only enhance the effect of cleaning the sensors 510 with the fluid but also cool down the part 530 to avoid overheating of the part 530 or one or more other parts that are adjacent to the part 530. The heat exchanger 540 is connected to the flow channel 580, through which the fluid, after being heated by the heat exchanger 540, can flow to the spraying nozzles 515 and spraying nozzles 560.
The temperature of the heat exchanger 540 may be the same or similar to the temperature of the part 530. The heat exchanger 540 may be placed at a hot spot in or outside the part 530. The hot spot is a spot that can have a higher temperature than other spots of the part 530 or other parts of the AV 110 (e.g., the reservoir 520) during operations of the AV 110. In some embodiments, the heat exchanger 540 is partially or wholly enclosed by the part 530. Alternatively, the heat exchanger 540 may be outside the part 530. For instance, the heat exchanger 540 can be attached on an exterior surface of the part 530, and the exterior surface of the part 530 can be thermally conductive to transfer heat from the part 530 to the heat exchanger 540.
The flow channel 580 connects the heat exchanger 540 to the spraying nozzles 560. For purpose of simplicity and illustration, the flow channel 580 is shown as dashed lines in
The spraying nozzles 560 are associated with the wind shield 550. Each spraying nozzle 560 can spray fluid from the heat exchanger 540 onto a portion of the wind shield 550. Even though not shown in
The heat exchanger 545 is associated with the sensors 510. The heat exchanger 545 can receive heat from one or both of the sensors 510 and transfer the heat to fluid inside the heat exchanger 545. In some embodiments, the heat exchanger 545 contacts one or both of the sensors 510. The temperature of the heat exchanger 545 may be the same or similar to the temperature of the sensors 510. The heat exchanger 545 may be placed at or near areas of the sensors 510 where most heat is generated. This can keep the fluid as hot as possible being the fluid is being sprayed to clean the sensors 510. In
The heat exchanger 545 receives the fluid from the reservoir 520 through the flow channel 575. The heat exchanger 545 can transfer heat generated by one or both of the sensors 510 to the fluid. In some embodiments, the heat is a byproduct of the sensors 510 during an operation of the sensors 510. The generation of the heat may not be an intended function of the sensors 510. Rather, the heat may be an unintended or even undesired result of the operation of the sensors 510. Too much heat may even impair performance of the sensors 510 or another part that is adjacent to the sensors 510 that can receive the heat. By using the heat generated by the sensors 510 to warm up the fluid can not only enhance the effect of cleaning the sensors 510 with the fluid but also cool down the sensors 510 to avoid overheating of the sensors 510 or one or more other parts that are adjacent to the sensors 510. The temperature of the fluid is increased in the heat exchanger 545, e.g., to a temperature that is the same or similar as the temperature of a sensor 510. The heat exchanger 545 is connected to the flow channel 585, through which the fluid, after being heated by the heat exchanger 545, can flow to the spraying nozzles 515.
The flow channel 585 connects the heat exchanger 545 to the spraying nozzles 515. For purpose of simplicity and illustration, the flow channel 585 is shown as dashed lines in
Each spraying nozzle 515 is associated with a sensor 510. The spraying nozzle 515 can spray fluid from the heat exchanger 545 onto a surface of the sensor 510. The surface may be a surface of an enclosure of the sensor 510, a surface of a window of the sensor 510, an optical surface (e.g., lens, filter, etc.) of the sensor 510, or other types of surfaces. Even though not shown in
The fluid cleaning system 500 have multiple advantages. For example, undesired heat generated from the sensors 510 is used to enhance cleaning efficacy by heating it. This also helps to cool the sensors 510 via this thermal transfer. As another example, the heat exchanger 540 is closer to point of use and therefore, can count for any cooling as the fluid travels through the flow channel 575, even if it was already heated in heat exchanger 540 or even in the reservoir 510.
The reservoir 620 stores the fluid to be used to clean the sensors 610. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. The reservoir 620 may be the same or similar as the reservoir 520. The heat exchanger 640 is associated with a part 630 of the AV 110. The heat exchanger 640 receives the fluid from the reservoir 620 through the flow channel 670. The heat exchanger 640 can transfer heat generated by the part 630 to the fluid. The part 630 may be the same or similar as the part 530. The heat exchanger 640 may be the same or similar as the heat exchanger 540. The flow channel 680 connects the heat exchanger 640 to the spraying nozzles 660. The spraying nozzles 660 are associated with the wind shield 650. The spraying nozzles 660 may be the same or similar as the spraying nozzles 560. Also, the flow channels 670 and 680 may be the same or similar as the flow channels 570 and 580, respectively.
The heat exchanger 645 is associated with the sensors 610. The heat exchanger 645 can receive heat from one or both of the sensors 610 and transfer the heat to fluid inside the heat exchanger 645. The heat exchanger 645 may be the same or similar as the heat exchanger 545 in the fluid cleaning system 500. The flow channel 685 connects the heat exchanger 645 to the spraying nozzles 615. Each spraying nozzle 615 can spray fluid from the heat exchanger 645 onto a surface of the corresponding sensor 610. The spraying nozzles 615 may be the same or similar as the spraying nozzles 515 in the fluid cleaning system 500.
Different from the fluid cleaning system 500, in the fluid cleaning system 600, the heat exchanger 645 is connected to the heat exchanger 640 through the flow channel 685. With such as design, the fluid for cleaning the sensors 610 are doubled heated: first in the heat exchanger 640, and then in the heat exchanger 645. By heating the fluid twice, the fluid sprayed by the spraying nozzles 615 in
The reservoir 720 stores the fluid to be used to clean the sensors 710 and a wind shield 750. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. A portion of the fluid may be used to clean the sensors 710, and another portion of the fluid may be used to clean the wind shield 750. The reservoir 720 may be the same or similar as the reservoir 420.
The reservoir 720 is connected to the local heater 730 through the flow channel 770. The local heater 730 is local as to the wind shield 750. For instance, the local heater 730 is closer to the wind shield 750 than the sensors 710. The local heater 730 can generate heat, e.g., intended heat, to increase a temperature of fluid when the fluid flows through or stays in the local heater 730. The heated fluid can then flow to the spraying nozzles 760 through the flow channel 780. The spraying nozzles 760 can spray the fluid onto the wind shield 750 to clean the wind shield. The spraying nozzles 760 may be the same or similar as the spraying nozzles 560. The flow channel 780 may be the same or similar as the flow channel 580.
The reservoir 720 is also connected to the local heaters 745A and 745B (collectively referred to as “local heaters 745” and “local heater 745”) through the flow channel 775. The local heaters 745 are local as to the sensors 710. For instance, the local heaters 745 are closer to the sensors 710 than the wind shield 750. In particular, the local heater 745A is associated with the sensors 710A and 710B, the local heater 745B is associated with the sensors 710C and 710D. Each local heater 745 can generate heat, e.g., intended heat, to increase a temperature of fluid when the fluid flows through or stays in the local heater 745. The fluid heated by the local heater 745A flows from the local heater 745A to the spraying nozzles 715A and 715B through the flow channel 785A. The fluid heated by the local heater 745B flows from the local heater 745B to the spraying nozzles 715C and 715D through the flow channel 785B. A local heater 745 may be controlled in a way that the local heater 745 is activated when a fluid flow into the local heater 745 is detected, e.g., by a flow sensor associated with the local heater 745. In other embodiments, a local heater 745 may be activated or deactivated by the sensor cleaning module 350, e.g., to maintain a desired temperature of the fluid flowing through the local heater 745. A local heater 730 or 745 may be integrated with or into a manifold that distributes fluid.
The spraying nozzles 715 can spray the heated fluid onto surfaces of the sensors 710 to clean the sensors. The spraying nozzles 715 may be the same or similar as the spraying nozzles 415. An advantage of using the local heaters 730 and 770 is that the heat loss caused by flow of the fluid along long flow channel lengths can be minimized so that the efficiency of the local heaters 730 and 770 can be maximized.
The reservoir 820 stores the fluid to be used to clean the sensors 810 and a wind shield 850 of the AV 110. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. A portion of the fluid may be used to clean the sensors 810, and another portion of the fluid may be used to clean the wind shield 850. The reservoir 820 may be the same or similar as the reservoir 420.
The reservoir 820 is connected to the heat exchanger 840, which is associated with a part 830, through the flow channel 870. The part 830 may be the same or similar as the part 430. The heat exchanger 840 may be the same or similar as the heat exchanger 440. The flow channel 870 may be the same or similar as the flow channel 470. The spraying nozzles 860 receive heated fluid from the heat exchanger 840 through the flow channel 880. The spraying nozzles 860 can spray the heated fluid onto the wind shield 850 to clean the wind shield 850. The spraying nozzles 860 may be the same or similar as the spraying nozzles 560. The flow channel 880 may be the same or similar as the flow channel 580.
The reservoir 820 is also connected to the local heaters 845A and 845B (collectively referred to as “local heaters 845” and “local heater 845”) through the flow channel 875. The local heaters 845 are local as to the sensors 810. For instance, the local heaters 845 are closer to the sensors 810 than the wind shield 850. In particular, the local heater 845A is associated with the sensors 810A and 810B, the local heater 845B is associated with the sensors 810C and 810D. Each local heater 845 can generate heat, e.g., intended heat, to increase a temperature of fluid when the fluid flows through or stays in the local heater 845. The fluid heated by the local heater 845A flows from the local heater 845A to the spraying nozzles 815A and 815B through the flow channel 885A. The fluid heated by the local heater 845B flows from the local heater 845B to the spraying nozzles 815C and 815D through the flow channel 885B. The spraying nozzles 815 can spray the heated fluid onto surfaces of the sensors 810 to clean the sensors. The spraying nozzles 815 may be the same or similar as the spraying nozzles 415. An advantage of using the local heaters 845 is that the heat loss caused by flow of the fluid can be minimized so that the efficiency of the local heaters 830 and 870 can be maximized.
The reservoir 920 stores the fluid to be used to clean the sensors 910 and a wind shield 950. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. A portion of the fluid may be used to clean the sensors 910, and another portion of the fluid may be used to clean the wind shield 950. The reservoir 920 may be the same or similar as the reservoir 420.
The reservoir 920 is connected to the local heater 930 through the flow channel 970. The local heater 930 is local as to the wind shield 950. For instance, the local heater 930 is closer to the wind shield 950 than the sensors 910. The local heater 930 can generate heat, e.g., intended heat, to increase a temperature of fluid when the fluid flows through or stays in the local heater 930. The heated fluid can then flow to the spraying nozzles 960 through the flow channel 980. The spraying nozzles 960 can spray the fluid onto the wind shield 950 to clean the wind shield. The spraying nozzles 960 may be the same or similar as the spraying nozzles 560. The flow channel 980 may be the same or similar as the flow channel 580.
The local heater 930 is also connected to the heat exchangers 945A and 945B (collectively referred to as “heat exchangers 945” and “heat exchanger 945”) through the flow channel 975. The heat exchanger 945A is associated with the sensors 910A and 910B. The heat exchanger 945B is associated with the sensors 910C and 910D. Each heat exchanger 945 can receive heat from one or both of the corresponding sensors 910 and transfer the heat to fluid inside the heat exchanger 945. A heat exchanger 945 may be the same or similar as the heat exchanger 545 in the fluid cleaning system 500. The flow channel 985A connects the heat exchanger 945A to the spraying nozzles 915A and 915B. The flow channel 985B connects the heat exchanger 945B to the spraying nozzles 915C and 915D. Each spraying nozzle 915 can spray fluid from the heat exchanger 945 onto a surface of the corresponding sensor 910. The spraying nozzles 915 may be the same or similar as the spraying nozzles 515 in the fluid cleaning system 500.
In the embodiments of
The reservoir 1020 stores the fluid to be used to clean the sensors 1010 and a wind shield 1050 of the vehicle. The fluid includes water. In some embodiments, the fluid may also include methanol, ethanol, ethylene glycol, other chemicals that have cleaning effects, or some combination thereof. The reservoir 1020 may include an opening, through which the fluid can flow into the reservoir 1020. The fluid can be used to clean the wind shield 1050 and the sensors 1010. In some embodiments, a portion of the fluid is used to clean the wind shield 1050, and another portion of the fluid is used to clean the sensors 1010. In other embodiments, the fluid can be used to clean other sensors or other parts of the AV 110. The fluid can be warmed up before it is used to clean the wind shield 1050 and the sensors 1010. With warmer fluid, the cleaning effect can be enhanced.
The reservoir heater 1030 is inside the reservoir 1020. The reservoir heater 1030 can generate heat, e.g., intended heat, to warm up fluid in the reservoir 1020. In some embodiments, the reservoir heater 1030 is partially or wholly immersed in the fluid. The fluid can be in contact with the reservoir heater and be heated by the reservoir heater. In alternative embodiments, the reservoir heater 1030 may be separated from the fluid, e.g., through a wall or a container, which can be thermally conductive and deliver heat from the reservoir heater 1030 to the fluid.
The reservoir is connected to the flow channel 1080 that connects the reservoir 1020 to the spraying nozzles 1015 and spraying nozzles 1060. A portion of the fluid, after heated by the reservoir heater 1030 can flow from the reservoir 1020 to the spraying nozzles 1015 through a part the flow channel 1080. Another portion of the fluid, after heated by the reservoir heater 1030 can flow from the reservoir 1020 to the spraying nozzles 1060 through another part of the flow channel 1080. The spraying nozzles 1015 can spray the fluid onto surfaces of the sensors 1010 and clean the sensors 1010. The spraying nozzles 1060 can spray the fluid onto the wind shield 1050 and clean the wind shield 1050. The flow channel 1080 may be the same or similar as the flow channel 480. The spraying nozzles 1015 may be the same or similar as the spraying nozzles 415. The spraying nozzles 1060 may be the same or similar as the spraying nozzles 460.
Example Fleet Management System
The service interface 1110 provides interfaces that allows users (e.g., users 135) to request services that can be provided by AVs associated with the fleet management system 120. In some embodiments, the service interface 1110 provides the interfaces to user devices, such as user devices 130. For example, the service interface 1110 may provide one or more apps or browser-based interfaces that can be accessed by users, such as the users 135, using user devices. The service interface 1110 enables the users to submit service requests provided or enabled by the fleet management system 120 through the interfaces.
The service datastore 1120 stores data associated with services managed by the fleet management system 120. The service datastore 1120 may store information associated with services that the fleet of AVs can provide. The service datastore 1120 may store historical service data. For instance, the service datastore 1120 may also store service requests that have been made by users. The service datastore 1120 may also store information of services that is being performed or has been completed, such as status of service, time when the service was completed, and so on. In some cases, the service datastore 1120 may further include future service data, e.g., a future service that a user has scheduled with the fleet management system 120. In some embodiments, service data stored in the service datastore 1120 may be associated with user accounts maintained by the fleet management system 120. A user may make service requests or access information of historical service requests through the account of the user.
The map datastore 1130 stores a detailed map of environments through which the fleet of AVs may travel. The map datastore 1130 may include some or all data stored in map datastores of the AVs, e.g., the map datastore 310. Some of the map datastore 1130 may be gathered by a fleet of AVs. For example, images obtained by exterior cameras of the AVs may be used to learn information about the AVs' environments. The images may be processed to identify particular features in the environment. Such features may include road conditions, such as road curve, bumps, traffic lights, traffic cones etc. The fleet management system 120 and/or AVs may have one or more image processing modules to identify features in the captured images or other sensor data. This feature data may be stored in the map datastore 1130. In some embodiments, certain feature data (e.g., features that are expected to be temporary) may expire after a certain period of time. In some embodiments, data captured by an AV 110 (e.g., a different AV) may indicate that a previously-observed feature is no longer present (e.g., a traffic cone has been removed) and in response, the fleet management system 120 may remove this feature from the map datastore 1130.
The vehicle manager 1140 manages and communicates with the fleet of AVs 110. The vehicle manager 1140 assigns the AVs 110 to various tasks (e.g., service tasks) and directs the movements of the AVs 110 in the fleet. In some embodiments, the vehicle manager 1140 may direct the movements of the AVs 110 in the fleet based on data in the map datastore 1130. In some embodiments, the vehicle manager 1140 may instruct AVs 110 to drive to other locations while not servicing a user, e.g., to improve geographic distribution of the fleet, to anticipate demand at particular locations, etc. The vehicle manager 1140 may also instruct AVs 110 to return to an AV 110 facility for fueling, inspection, maintenance, or storage. The vehicle manager 1140 may perform some or all of the functions of the onboard computer 150 that are described above in conjunction with
In some embodiments, the vehicle manager 1140 selects AVs from the fleet to perform various tasks and instructs the AVs to perform the tasks. In some embodiments, the vehicle manager 1140 selects an AV 110 based on availability of the AV 110. For example, the vehicle manager 1140 may determine that the AV 110 is available based on a determination that the AV 110 the AV 110 is not performing any task or is going to perform any task that has been assigned to the AV 110. In cases where a service request specifies a time window for the service, the vehicle manager 1140 may determine that the AV 110 is available in the time window. The vehicle manager 1140 may select one of the available AVs based on other factors, such as physical proximity.
The vehicle manager 1140 or another system may maintain or access data describing each of the AVs in the fleet of AVs 110, including current location, service status (e.g., whether the AV 110 is available or performing a service; when the AV 110 is expected to become available; whether the AV 110 is schedule for future service), fuel or battery level, etc. The vehicle manager 1140 may select AVs for service in a manner that optimizes one or more additional factors, including fleet distribution, fleet utilization, and energy consumption. The vehicle manager 1140 may interface with one or more predictive algorithms that project future service requests and/or vehicle use, and select vehicles for services based on the projections.
The vehicle manager 1140 transmits instructions dispatching the selected AVs. In particular, the vehicle manager 1140 instructs a selected AV 110 to drive autonomously to a location. For instance, the vehicle manager 1140 may generates a navigation instruction based on the location and provide the navigation instruction to the selected AV, which will then navigate to the location accordingly. The navigation instruction may include the location itself, a navigation route from another location to the location, road condition information, motion parameters, other types of navigation information, or some combination thereof.
Example Gas System
In some embodiments, the fan 1210 may direct air into the flow channel 1220. The air may be ambient air, e.g., air surrounding the fan 1210. In other embodiments, the air may be compressed ambient air or heated ambient air. In other embodiments, the fan 1210 may direct other types of gas into the flow channel 1220.
The flow channel 1220 may include an air duct. In some embodiments, one or more heat exchangers may be arranged on the flow channel 1220, e.g., on a wall of the flow channel 1220. In other embodiments, the wall of the flow channel 1220 itself may be a heat exchanger. In some embodiments, heat may be transferred from the sensors 1240 to the fluid inside the flow channel 1220, which is represented by the dashed arrows in
A spray assembly 1230 may be connected to the flow channel 1220 and spray the fluid from the flow channel 1220 onto the corresponding sensor 1240. Even though each sensor 1240 has a different spray assembly 1230 in
In some embodiments, the compressor 1310 may receive gas and compress the gas, e.g., to a predetermined pressure or a predetermined pressure range. The gas may be ambient air, e.g., air surrounding the compressor 1310. In other embodiments, the air may be heated ambient air. The reservoir 1315 may receive and store the gas after the compression. In some embodiments, the reservoir 1315 maintains the predetermined pressure or predetermined pressure range. The reservoir 1315 may be a pressure tank.
The compressed gas may flow into the flow channels 1320 from the reservoir 1315. In some embodiments, a flow channel 1320 may be associated with one or more valves that can be used to control the flow or flow rate of the gas in the flow channel 1320. A flow channel 1320 may include an air duct. In some embodiments, one or more heat exchangers may be arranged on a flow channel 1320, e.g., on a wall of the flow channel 1320. In other embodiments, the wall of the flow channel 1320 itself may be a heat exchanger. In some embodiments, heat may be transferred from the sensors 1340 to the fluid inside the flow channel 1320, which is represented by the dashed arrows in
A spray assembly 1330 may be connected to a flow channel 1320 and spray the fluid from the flow channel 1320 onto the corresponding sensor 1340. Even though each sensor 1340 has a different spray assembly 1330 in
air.
Other Implementation Notes, Variations, and Applications
It is to be understood that not necessarily all objects or advantages may be achieved in accordance with any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objects or advantages as may be taught or suggested herein.
In one example embodiment, any number of electrical circuits of the figures may be implemented on a board of an associated electronic device. The board can be a general circuit board that can hold various components of the internal electronic system of the electronic device and, further, provide connectors for other peripherals. More specifically, the board can provide the electrical connections by which the other components of the system can communicate electrically. Any suitable processors (inclusive of digital signal processors, microprocessors, supporting chipsets, etc.), computer-readable non-transitory memory elements, etc. can be suitably coupled to the board based on particular configuration needs, processing demands, computer designs, etc. Other components such as external storage, additional sensors, controllers for audio/video display, and peripheral devices may be attached to the board as plug-in cards, via cables, or integrated into the board itself. In various embodiments, the functionalities described herein may be implemented in emulation form as software or firmware running within one or more configurable (e.g., programmable) elements arranged in a structure that supports these functions. The software or firmware providing the emulation may be provided on non-transitory computer-readable storage medium comprising instructions to allow a processor to carry out those functionalities.
It is also imperative to note that all of the specifications, dimensions, and relationships outlined herein (e.g., the number of processors, logic operations, etc.) have only been offered for purposes of example and teaching only. Such information may be varied considerably without departing from the spirit of the present disclosure, or the scope of the appended claims. The specifications apply only to one non-limiting example and, accordingly, they should be construed as such. In the foregoing description, example embodiments have been described with reference to particular arrangements of components. Various modifications and changes may be made to such embodiments without departing from the scope of the appended claims. The description and drawings are, accordingly, to be regarded in an illustrative rather than in a restrictive sense.
Note that with the numerous examples provided herein, interaction may be described in terms of two, three, four, or more components. However, this has been done for purposes of clarity and example only. It should be appreciated that the system can be consolidated in any suitable manner. Along similar design alternatives, any of the illustrated components, modules, and elements of the figures may be combined in various possible configurations, all of which are clearly within the broad scope of this Specification.
Note that in this Specification, references to various features (e.g., elements, structures, modules, components, steps, operations, characteristics, etc.) included in “one embodiment”, “example embodiment”, “an embodiment”, “another embodiment”, “some embodiments”, “various embodiments”, “other embodiments”, “alternative embodiment”, and the like are intended to mean that any such features are included in one or more embodiments of the present disclosure, but may or may not necessarily be combined in the same embodiments.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. Note that all optional features of the systems and methods described above may also be implemented with respect to the methods or systems described herein and specifics in the examples may be used anywhere in one or more embodiments.
This application is a continuation-in-part of (and claims the benefit of priority to) U.S. application Ser. No. 17/815,674, filed Jul. 28, 2022, and entitled “SYSTEM AND METHOD FOR CLEANING SENSORS OF AUTONOMOUS VEHICLES WITH HEATED FLUID,” the content of which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17815674 | Jul 2022 | US |
| Child | 18354535 | US |
