The invention relates generally to systems for conducting agricultural operations, and in particular, to a system for avoiding collisions between autonomous vehicles conducting agricultural operations by establishing a hierarchy between vehicles and modifying paths of lower priority vehicles traveling toward collisions based on the hierarchy.
Agricultural operations in large fields often require significant amounts of resources and careful planning in order to provide the most effective results. Depending on the type of field and/or season, one or more tractors, tillers, harvesters, sprayers, balers or other implements may be required to efficiently perform various agricultural operations. Moreover, such operations may be required to be performed in certain orders, such as harvesting before tilling, or tilling before planting.
However, various hazards may occur which may compromise even the most careful planning. Such hazards may include one agricultural vehicle traveling toward a collision with another agricultural vehicle in the field. This situation may occur, for example, when one agricultural vehicle is required to deviate from a planned path in order to avoid a collision with an unexpected obstacle, and the deviation inadvertently puts the vehicle on a collision path with another vehicle. Consequently, what is needed is an improved system for deploying agricultural equipment to perform necessary operations in a field which may help to reduce the possibility of collisions.
The present invention provides a system for conducting agricultural operations in a field using autonomous vehicles in which a collision avoidance mechanism may be provided. The system may include providing a mission plan for autonomous vehicles to conduct agricultural operations, establishing a hierarchy for the vehicles, and monitoring for an event conditions indicating vehicles are traveling toward a collision with respect to one another. Upon receiving an event condition, the system may revise the mission plan to adjust a path of one of the vehicles based on the hierarchy in order to avoid the collision.
Autonomous vehicle control systems typically include a localized control system on the vehicle itself, and a back-office/base station command and control system located at another location away from the vehicle. The back office/base station is typically connected to the vehicle via a long range radio communication system (which may allow communication >1 mile). If there are multiple vehicles in the system, they may also be interconnected via a short range communication system (which may allow communication <1 mile). A localized base station might also be located in the field which could also connect to the short range communication system. In one aspect, the back-office/base station and/or localized base station could be implemented by an autonomous vehicle.
The back office is typically where the majority of data used for mission planning and construction is stored. This data could comprise, for example, of Geographical Information System (GIS) maps of a farm/fields, an equipment library (including information providing an equipment inventory, equipment geometries and/or specifications), equipment break-down/service status, weather maps/forecasts, yield maps, soil maps, nutrient maps, prescription maps/rates (such as for fertilizer, seed, manure, herbicide, and the like), radio coverage maps, satellite images, historical data (which may be records from prior years or seasons), and so forth. The equipment library in particular may contain information on all of the equipment which may be available to complete a mission (such as tractors, implements, harvesters, sprayers, and the like, on the farm).
Each vehicle which may be used in agricultural operations, or actively involved in agricultural operations, may be placed in a hierarchy (ranked). This hierarchy may be used for conflict resolution to determine which vehicle has the right of way and which vehicle will give way.
As part of the optimization, the back office/base station may also execute a collision avoidance process. The purpose of this process is to make sure vehicles performing the same or similar operations are not put in a situation where they could collide and cause damage to one another. A collision could occur, for example, if vehicles are travelling in opposite directions on the same path or adjacent paths. This condition can be analyzed when a mission is constructed, and may also be run in real time as there may be problems which cause deviations from the initial mission plan. As the mission is updated and re-optimized due to deviations, the collision avoidance process may be executed again. To avoid a collision, the collision avoidance process may analyze a current pass of each vehicle and a next planned pass of each vehicle, and may compare this analysis to the current pass and next planned passes of all vehicles performing operations in the same field. If it discovers that any vehicles may pass in opposite directions on the same or adjacent paths, the collision avoidance process may re-plan the path for one of the vehicles involved in the potential collision. When a potential collision is identified, a vehicle with a lower rank in the hierarchy may execute one of several possible avoidance strategies, such as moving to a new path/pass that will avoid the collision, or stopping and waiting at the end of a current pass. If a collision avoidance maneuver is executed, it is likely that as a result the remaining portion of the mission may benefit from a re-construction and re-optimization.
One path planning scenario may be to have two or more vehicles performing the same operation, working in the same field together use a leader-follower approach. The lead vehicle may run ahead while one or more following vehicles operate on adjacent passes. If there are multiple following vehicles, each may follow the lead vehicle in a staggered pattern, such as follower 1 adjacent to and behind the leader, follower 2 adjacent to and behind follower 1, and so forth. At the headlands, or areas at each end of the field, the lead vehicle may move over a number of passes equivalent to the total number of vehicles to avoid any potential collisions by being on adjacent passes in opposite directions of travel. Each follower may then move into the same relative position for the next pass.
For a single vehicle working in a field, or for a field carved into a number of blocks/areas equivalent to the number of vehicles operating in the field, each individual vehicle may be assigned its own block/area. Accordingly, each vehicle may follow a pre-assigned coverage plan (alternating, “skip N,” adjacent, lands, or the like). Collision avoidance processes may only need to be run on the boundaries between blocks/areas.
If an obstacle is known or detected on one of the vehicle passes and requires a deviation/avoidance path that overlaps or crosses over another vehicle pass in the field then the vehicle performing the avoidance path will have to check the new path against the paths of other nearby vehicles to make sure there is no potential for collision.
In addition, when there are multiple vehicles in the same field performing different operations, it may be important that certain field operations be performed in a specific order. Accordingly, a vehicle performing a first field operation may be required to cover an area before a vehicle performing a second field operation covers the same area. The field map for the second field operation may have, for example, three operational regions: no coverage; covered by the first field operation only; and covered by both the first and second field operations. The operational field shape and size for the vehicle performing the second field operation may evolve as the vehicle performing the first field operation covers the field. The mission plan for the second field operation may consider, for example: total field area, area covered by first field operation, planned future path(s) for first field operation, pass width(s) of first field operation, pass width(s) of second field operation, work rate (acres/hour) of first field operation, work rate of second field operation, and so forth. From a pass-to-pass stand point, the second vehicle will have to check and make sure that the first operation has already been performed over the area of the second vehicle's next planned pass. If not, then the second vehicle will have to plan a new pass on an area already covered by the first field operation, or wait until the first vehicle has covered enough area to plan a new pass.
In certain aspects, autonomous vehicles may be mixed with human operated vehicles, and the system may be managed and controlled from another vehicle in the field instead of from a remote base station. Such variations are within the scope of the invention.
Specifically then, in one aspect, a method for conducting an agricultural operation including: (a) providing a mission plan for first and second autonomous vehicles, the mission plan including first and second paths for the first and second autonomous vehicles to travel while performing first and second agricultural operations, respectively; (b) establishing a hierarchy in which the first autonomous vehicle is prioritized above the second autonomous vehicle; (c) monitoring for an event condition reported by at least one of the first and second autonomous vehicles, the event condition being a detection of the first and second autonomous vehicles traveling toward a collision with respect to one another; and (d) upon receiving the event condition, providing a revised mission plan for the second autonomous vehicle in which the revised mission plan adjusts the second path of the second autonomous vehicle based on the hierarchy to avoid the collision.
Another aspect may provide a system for managing an agricultural operation, the system including a processor executing a program stored in a non-transient medium operable to: (a) provide a mission plan for first and second autonomous vehicles, the mission plan including first and second paths for the first and second autonomous vehicles to travel while performing first and second agricultural operations, respectively; (b) establish a hierarchy wherein the first autonomous vehicle is prioritized above the second autonomous vehicle; (c) monitor for an event condition reported by at least one of the first and second autonomous vehicles, the event condition being a detection of the first and second autonomous vehicles traveling toward a collision with respect to one another; and (d) upon receiving the event condition, provide a revised mission plan for the second autonomous vehicle in which the revised mission plan adjusts the second path of the second autonomous vehicle based on the hierarchy to avoid the collision.
Other aspects, objects, features, and advantages of the invention will become apparent to those skilled in the art from the following detailed description and accompanying drawings. It should be understood, however, that the detailed description and specific examples, while indicating preferred embodiments of the present invention, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the present invention without departing from the spirit thereof, and the invention includes all such modifications.
Preferred exemplary embodiments of the invention are illustrated in the accompanying drawings in which like reference numerals represent like parts throughout.
Referring now to
The vehicle 10 may also include a long range antenna 16 for communicating with a base station (which may be >1 mile) and a short range antenna 18 for communicating with other vehicles and/or a localized base station in the field (which may be <1 mile). Such communications may be accomplished via radio communications transmitted and received on varying bands.
Referring now to
The control system 20 may also be in communication with a communication system 34, a drive system 36, and an agricultural operation control system 38. The communication system 34 may allow communication with the base station via the long range antenna 16 and/or communication with other vehicles and/or a localized base station via the short range antenna 18. The drive system 36 may allow for general operation of the vehicle 10 by the control system 20 without the physical presence of a human operator, such as braking, accelerating, steering, shifting, and the like. The agricultural operation control system 38 may allow for general operation of the agricultural machinery 14 by the control system 20, such as collecting an agricultural product (such as for harvesting), dispensing an agricultural product (such as for planting or spraying), actuating an agricultural product (such as for cutting or raking) and the like.
Referring now to
For conducting agricultural operations in the field 50, vehicles 10, labeled “A,” “B,” “C” and “D” in
Each vehicle 10 may autonomously travel a path 60 in the field 50 while performing an agricultural operation according to the mission plan. The paths 60 may be bounded by a field line 62 (which may also include a fence) and/or demarcated sections of the field 50, such as a first section 64 for the first team 56 to operate, and a second section 66 for the second team 58 to operate. In one aspect, the vehicles 10 may operate systematically in rows, back and forth, each row having a width “W” determined to accommodate the vehicles 10 for maximum farming production. The mission plan may take into account known or expected obstacles in the field 50, such as trees 70, a local base station 72, or a water formation 74, such that the paths 60 may be arranged in advance with turns 76 to avoid such obstacles in completing rows of a section.
While the vehicles 10 are conducting their agricultural operations, they may each provide progress information to the base station 52. The progress information may indicate progress with respect to the agricultural operation the vehicle 10 has been assigned. Accordingly, such progress information may include reporting a current position of the vehicle 10 with respect to the path 60, reporting an amount of agricultural product collected, reporting an amount of agricultural product dispensed, and so forth. For example, vehicle A may report its precise GPS location corresponding to nearing completion of the third row of the first section 64 with a specific amount of crop harvested, and vehicle B may report its precise GPS location corresponding to a distance behind vehicle A, nearing completion of the first row of the first section 64, with tilling in progress. Upon completion of the agricultural operations, the vehicles 10 may exit the field 50 at one or more predetermined egress points 78.
Referring now to
In one aspect of the invention, the base station 52 may conduct agricultural operations in the field 50 via the computer processing system 100. The computer processing system 100 may store multiple data structures 110 in a computer readable non-transient medium, such as a Random Access Memory (RAM), Flash memory or disk for conducting the agricultural operations. The computer processing system 100 may also execute a program 112 stored in the same or different computer readable non-transient medium to provide the mission plan for the vehicles 10, receive progress information from the vehicles 10, monitor for event conditions, which may be reported by the vehicles 10, and provide revised mission plans for the vehicles 10 as necessary.
All relevant data for mission planning and construction may be initially collected in the data structures 110. The data structures 110 may include: one or more maps 120, which may include GIS maps of the field 50, yield maps, soil maps, nutrient maps, prescription maps/rates (such as for fertilizer, seed, manure, herbicide, and the like), radio coverage maps, satellite images, and the like; weather maps 122, which may include weather forecast data received over the WAN; an inventory record 124 of the vehicles 10 and/or other equipment available in the system, which may include for each vehicle 10 an equipment break-down, such as a unique identifier 126, a selected agricultural operation 128, an equipment type 130, a relative hierarchy or rank 132 with respect to other vehicles 10, and/or a maintenance status 134 or service schedule; an equipment library 136, including information providing equipment geometries and/or specifications for each type of vehicle 10 in the inventory record 124 corresponding to the equipment type 130; and historical data 138, which may include mission reports reported by vehicles 10 from previous agricultural operations.
The data structures 110 may also include data structures which may receive user input for generating mission plans (such as via the I/O terminal 106) including, for example, an operation selection field 140, weights 142 and constraints 144. The operation selection field 140 may allow a user to select desired one or more desired agricultural operations to complete for accomplishing a particular mission plan, such as spraying, tilling, harvesting, baling, raking and/or planting. A user may also select a desired order for such agricultural operations, such as harvesting (selected as “1”) to be completed in areas first followed by tilling (selected as “2”), with inapplicable operations left unselected.
The weights 142 and the constraints 144 may be used in the mission planning and construction to control the optimization of the mission plan. Values for each of the weights 142 may be assigned. The weights 142 may include, for example: an importance of completion time (or overall time for mission execution) (“Time”); an importance of agricultural efficiency of a mission goal (such as planting accuracy, harvest losses or spraying accuracy) (“Efficiency”); an importance of power/torque reserve during operation (“Power”); and so forth. The sum of all of the weights 142 will normally be equal to one.
The constraints 144 could include, for example: requiring a maximum speed while performing a field operation (such as harvesting, planting, tillage or unloading on-the-go) (“Speed 1”); requiring a maximum speed during headland turns (areas at each end of the field) (“Speed 2”); requiring a maximum harvest loss limit (“Loss”); requiring a maximum force exertion (“G1”) and/or maximum force duration (“G2”) for motion of the vehicles 10 (such as for management of a power hop or working on rough ground); requiring a minimum turning radius on headlands (“Turn”); requiring a maximum power/torque limit (“Power”); and so forth.
The data structures 110 may also include data structures to be communicated to the vehicles 10 and/or to be updated based on information received by the vehicles 10 including, for example, a mission plan 150, progress monitors 152, an event log 154, mission revisions 156 and mission reports 158. The mission plan 150 providing a mission plan for an autonomous vehicle, the mission plan may provide the paths for each of the vehicles 10 and/or other equipment to travel while performing particular agricultural operations in the field, including as described above by way of example in
One or more mission revisions 156 may be provided by the system from time to time to update one or more portions of the mission plan 150 (such as specific paths for specific vehicles) and/or to replace all of the mission plan 150. Mission revisions 156 may typically be provided, for example, upon receiving an event condition being tracked in the event log 154. Mission revisions 156 may typically adjust paths of one or more vehicles 10 to resolve event conditions being monitored, though mission revisions 156 may be provided for other reasons.
Each of the aforementioned data structures 110 may be updated from time to time, such as via the gateway 104 and the WAN, to provide updated information, such as current weather reports, updated equipment data, and the like.
Referring now to
Next, in block 182, the mission plan is transmitted to the vehicles 10 required to complete the mission plan at the appropriate times. The vehicles 10 then deploy in the field and travel their assigned paths while performing their assigned agricultural operations.
When there are multiple vehicles 10 in the same field performing different operations, it may be important that certain field operations be performed in a specific order. Accordingly, a vehicle 10 performing a first field operation may be required to cover an area before a vehicle performing a second field operation covers the same area. The field map for the second field operation may have, for example, three operational regions: no coverage; covered by the first field operation only; and covered by both the first and second field operations. The operational field shape and size for the vehicle performing the second field operation may evolve as the vehicle performing the first field operation covers the field. The mission plan for the second field operation may consider, for example: total field area, area covered by first field operation, planned future path(s) for first field operation, pass width(s) of first field operation, pass width(s) of second field operation, work rate (acres/hour) of first field operation, work rate of second field operation, and so forth.
Next, in block 184, while the vehicles 10 are deployed, the vehicles 10 may report progress information to the base station, which may include, for example, a position of each vehicle 10 with respect to its assigned path, an amount of agricultural product collected, an amount of agricultural product dispensed, and so forth. The base station receiving the progress information may track the progress information for providing optimizations in subsequent mission revisions.
Next, while monitoring for event conditions, in decision block 186 the base station determines if an event condition has been reported. During execution of a mission, there may be events which cause deviations from the initial mission plan, such as equipment break down, an obstacle detected that stops a vehicle, a grain tank being full on harvester, and so forth. When such a deviation from the current mission plan occur the current mission may need to be re-constructed and re-optimized with an updated set of constraints, such as an area already covered, a particular piece of equipment unavailable due to a break-down, and so forth. Event conditions may typically be reported by vehicles 10, though other mechanisms may be provided for reporting event conditions, such as the local base station 72, or a weather update via the gateway 104 and the weather map 122.
If an event condition has been reported, the process may proceed to block 188 in which a revised mission plan may be provided. The revised mission plan may adjust the path of one or more of the vehicles 10 to resolve the event condition. The revised mission plan may also provide an optimization based on current agricultural conditions, such as those reported by the progress information in block 184. The revised mission plan may be communicated to only the vehicles 10 necessary to implement the revised mission plan or may be communicated to all of the vehicles 10 for greater consistency.
Next, in block 190, as part of the optimization, the base station may also execute a collision avoidance process. To avoid a collision, the collision avoidance process may analyze a current pass of each vehicle and a next planned pass of each vehicle, and may compare this analysis to the current pass and next planned passes of all vehicles performing operations in the same field. If it discovers that any vehicles may pass in opposite directions on the same or adjacent paths, the collision avoidance process may re-plan the path for one of the vehicles involved in the potential collision. When a potential collision is identified, a vehicle with a lower rank in the hierarchy may execute one of several possible avoidance strategies, such as moving to a new path/pass that will avoid the collision, or stopping and waiting at the end of a current pass. Having provided a mission revision to resolve the event condition and having verified collision avoidance, the process may return again to block 184 for receiving progress information, then decision block 186 for determining if an event condition has been reported.
However, following decision block 186, if an event condition has not been reported, the process may proceed to decision block 190 in which the base station determines if the mission has been completed. The base station may make this determination by applying one or more factors, including comparing progress information received from the vehicles 10 to the current mission plan, monitoring a completion time and/or monitoring for mission reports from the vehicles 10. If the mission has been completed, in block 192, the base station may receive mission reports from the vehicles 10, each mission report indicating completion of the mission by a particular vehicle 10. Mission reports may include final progress information, a date/time stamp and/or a report of sensor readings from sensors described above with respect to
Referring now to
Referring now to
Multiple mission revisions may be presented as options and/or adjustments may be made before communicating to vehicles 10 for execution, similar to providing a mission plan as described above with respect to
Referring now to
Referring now to
Referring now to
Next, in block 262, to avoid a collision, the collision avoidance process may analyze a current pass of each vehicle, and in block 264, a next planned pass of each vehicle. The passes may be analyzed and compared to determine if any vehicles may pass in opposite directions on the same or adjacent paths. In decision block 266, if it is discovered that any vehicles may pass in opposite directions on the same or adjacent paths, the collision avoidance process may proceed to block 268 in which the path for a lower ranked vehicle in the hierarchy may be redirected to avoid the potential collision in a revised mission. Redirection of the vehicle with lower rank in the hierarchy may include, for example, moving the vehicle to a new path/pass that will avoid the collision, or stopping the vehicle and waiting at the end of a current pass. Next, in block 270, remaining portions of the mission plan may be analyzed for re-construction and re-optimization, which may be based on current agricultural conditions such as those provided by the progress information of vehicles in the system. If an optimization may be realized, the revision plan may be further updated.
The present invention may be part of a “safety system” used to protect human life and limb in a field, construction or other environment. Nevertheless, the term “safety,” “safely” or “safe” as used herein is not a representation that the present invention will make the environment safe or that other systems will produce unsafe operation. Safety in such systems depends on a wide variety of factors outside of the scope of the present invention including: design of the safety system, installation and maintenance of the components of the safety system, and the cooperation and training of individuals using the safety system. Although the present invention is intended to be highly reliable, all physical systems are susceptible to failure and provision must be made for such failure.
Although the best mode contemplated by the inventors of carrying out the present invention is disclosed above, practice of the above invention is not limited thereto. It will be manifest that various additions, modifications and rearrangements of the features of the present invention may be made without deviating from the spirit and the scope of the underlying inventive concept.
Number | Name | Date | Kind |
---|---|---|---|
5111401 | Everett, Jr. et al. | May 1992 | A |
5170352 | McTamaney et al. | Dec 1992 | A |
5280431 | Summerville et al. | Jan 1994 | A |
5375059 | Kyrtsos et al. | Dec 1994 | A |
5610821 | Gazis | Mar 1997 | A |
5646844 | Gudat | Jul 1997 | A |
5974348 | Rocks | Oct 1999 | A |
5987383 | Keller | Nov 1999 | A |
6128574 | Diekhans | Oct 2000 | A |
6167337 | Haack | Dec 2000 | A |
6246932 | Kageyama | Jun 2001 | B1 |
6292725 | Kageyama | Sep 2001 | B1 |
6463374 | Keller | Oct 2002 | B1 |
6484078 | Kageyama | Nov 2002 | B1 |
6611755 | Coffee | Aug 2003 | B1 |
6728607 | Anderson | Apr 2004 | B1 |
6745126 | Pavlak | Jun 2004 | B1 |
6799100 | Burns | Sep 2004 | B2 |
6941201 | Sudou | Sep 2005 | B2 |
7277028 | Janke | Oct 2007 | B1 |
7499776 | Allard | Mar 2009 | B2 |
7587260 | Bruemmer et al. | Sep 2009 | B2 |
7742860 | Diekhans | Jun 2010 | B2 |
7873617 | Wippersteg | Jan 2011 | B2 |
7899584 | Schricker | Mar 2011 | B2 |
7966106 | Sudou | Jun 2011 | B2 |
8020657 | Allard et al. | Sep 2011 | B2 |
8050863 | Trepagnier et al. | Nov 2011 | B2 |
8082097 | Hilliar Isaacson | Dec 2011 | B2 |
8095279 | Greiner | Jan 2012 | B2 |
8125529 | Skoskiewicz | Feb 2012 | B2 |
8195342 | Anderson | Jun 2012 | B2 |
8200428 | Anderson | Jun 2012 | B2 |
8396597 | Anderson | Mar 2013 | B2 |
8428829 | Brunnert | Apr 2013 | B2 |
8437901 | Anderson | May 2013 | B2 |
8452448 | Pack et al. | May 2013 | B2 |
8478493 | Anderson | Jul 2013 | B2 |
8548664 | Uchida | Oct 2013 | B2 |
8589013 | Pieper | Nov 2013 | B2 |
8639408 | Anderson | Jan 2014 | B2 |
8744626 | Johnson | Jun 2014 | B2 |
8755976 | Peters | Jun 2014 | B2 |
8788121 | Klinger | Jul 2014 | B2 |
8818567 | Anderson | Aug 2014 | B2 |
8868304 | Bonefas | Oct 2014 | B2 |
8983707 | Everett | Mar 2015 | B2 |
9188986 | Baumann | Nov 2015 | B2 |
9392746 | Darr | Jul 2016 | B2 |
9420737 | Spiller | Aug 2016 | B2 |
9772625 | Gilmore | Sep 2017 | B2 |
9858818 | Shibata | Jan 2018 | B2 |
9968024 | Haneda | May 2018 | B2 |
20010044697 | Kageyama | Nov 2001 | A1 |
20020072850 | McClure | Jun 2002 | A1 |
20020135467 | Koike | Sep 2002 | A1 |
20020165645 | Kageyama | Nov 2002 | A1 |
20020165649 | Wilhelm Rekow et al. | Nov 2002 | A1 |
20030060968 | MacPhail | Mar 2003 | A1 |
20030187577 | McClure | Oct 2003 | A1 |
20050273253 | Diekhans | Dec 2005 | A1 |
20060047418 | Metzler | Mar 2006 | A1 |
20060178825 | Eglington | Aug 2006 | A1 |
20060249321 | Cook | Nov 2006 | A1 |
20070035416 | Tanaka | Feb 2007 | A1 |
20070239337 | Anderson | Oct 2007 | A1 |
20080059007 | Whittaker | Mar 2008 | A1 |
20090088916 | Elgersma et al. | Apr 2009 | A1 |
20100017046 | Cheung | Jan 2010 | A1 |
20100042247 | Starr | Feb 2010 | A1 |
20100042257 | Starr | Feb 2010 | A1 |
20100076631 | Mian | Mar 2010 | A1 |
20100094499 | Anderson | Apr 2010 | A1 |
20100163621 | Ben-Asher | Jul 2010 | A1 |
20100201829 | Skoskiewicz | Aug 2010 | A1 |
20100324771 | Yabushita | Dec 2010 | A1 |
20110112730 | Rekow | May 2011 | A1 |
20110295424 | Johnson | Dec 2011 | A1 |
20120095651 | Anderson | Apr 2012 | A1 |
20120174445 | Jones | Jul 2012 | A1 |
20120316725 | Trepagnier | Dec 2012 | A1 |
20130046525 | Ali | Feb 2013 | A1 |
20130238170 | Klinger | Sep 2013 | A1 |
20130325242 | Cavender-Bares | Dec 2013 | A1 |
20150025752 | Tolstedt | Jan 2015 | A1 |
20150094944 | Baumann | Apr 2015 | A1 |
20150173297 | Pitzer | Jun 2015 | A1 |
20150336669 | Kantor | Nov 2015 | A1 |
20150362922 | Dollinger | Dec 2015 | A1 |
20160021813 | Matthews | Jan 2016 | A1 |
20160057920 | Spiller | Mar 2016 | A1 |
20160071410 | Rupp | Mar 2016 | A1 |
20160117936 | Klinger et al. | Apr 2016 | A1 |
20160148511 | Shibata | May 2016 | A1 |
20160157428 | Pitzer | Jun 2016 | A1 |
20160157431 | Pitzer | Jun 2016 | A1 |
20170082452 | Sumizawa | Mar 2017 | A1 |
20170102702 | Ishijima | Apr 2017 | A1 |
20170138732 | Pettersson | May 2017 | A1 |
20170160748 | Nakagawaa | Jun 2017 | A1 |
20170276492 | Ramasamy | Sep 2017 | A1 |
20170280614 | Turpin | Oct 2017 | A1 |
20170292854 | Zhang | Oct 2017 | A1 |
20170311534 | Rusciolelli | Nov 2017 | A1 |
20170318735 | Foster | Nov 2017 | A1 |
20180024549 | Hurd | Jan 2018 | A1 |
Number | Date | Country |
---|---|---|
1369013 | Dec 2003 | EP |
1840690 | Oct 2007 | EP |
2177965 | Apr 2010 | EP |
Entry |
---|
Scott A. Shearer et al.; “Trends in the Automation Field Machinery”; Biosystems and Agricultural Engineering; pp. 1-22; University of Kentucky, Lexington, USA (2010). |
NPL—Mousazadeh; “A technical review on navigation systems of agricultural autonomous off-road vehicles”; website—<http://www.sciencedirect.com/science/article/pii/S0022489813000220>; pp. 1-2; Apr. 2013: US. |
NPL—Vougioukas; “A distributed control framework for motion coordination of teams of autonomous agricultural vehicles”; website—http://www.sciencedirect.com/science/article/pii/S153751101200150X; pp. 1-3; Oct. 2012; US. |
Number | Date | Country | |
---|---|---|---|
20170316692 A1 | Nov 2017 | US |