Autonomous Behaviors for a Remote Vehicle

• US 20110106339A1
• Filed: 11/01/2010
• Published: 05/05/2011
• Est. Priority Date: 07/14/2006
• Status: Active Grant

• Current Assignee: Flir Detection, Inc. (Teledyne Technologies Incorporated)
• Original Assignee: iRobot Corporation
• Inventors: Jamieson, Josef P., Sawyer, Tyson, Shein, Andrew, Phillips, Emilie, Powers, Aaron
• Granted Patent: US 8,108,092 B2
• Time in Patent Office: Days
• US Class Current: 701/2
• CPC Class Codes: G01C 21/20 Instruments for performing navigational calculations G01C21/24, G01C21/26 take precedence
• CPC Class Codes: G05D 1/0033 by having the operator tracking the vehicle either by direct line of sight or via one or more cameras located remotely from the vehicle
• CPC Class Codes: G05D 1/0274 using mapping information stored in a memory device navigation using map-matching G01C21/30
• CPC Class Codes: G05D 1/0278 using satellite positioning signals, e.g. GPS

Abstract

A method for enhancing operational efficiency of a remote vehicle using a diagnostic behavior. The method comprises inputting and analyzing data received from a plurality of sensors to determine the existence of deviations from normal operation of the remote vehicle, updating parameters in a reference mobility model based on deviations from normal operation, and revising strategies to achieve an operational goal of the remote vehicle to accommodate deviations from normal operation. An embedded simulation and training system for a remote vehicle. The system comprises a software architecture installed on the operator control unit and including software routines and drivers capable of carrying out mission simulations and training.

Claims

1-18. -18. (canceled)

19. A system for implementing a retrotraverse behavior for a remote vehicle configured to communicate with an operator control unit, the system comprising:

a control system on the remote vehicle including a memory and a processor, the processor being configured to run the retrotraverse behavior, the retrotraverse behavior including or in communication with a waypoint routine that maintains a list of time stamped waypoints stored in the memory and separated by at least a minimum difference in time and distance,

wherein one of the waypoint routine and the retrotraverse behavior generates a return path interconnecting previously-traversed waypoints in reverse order of timestamps.

20. The system of claim 19, wherein the memory is a doubly-linked, indexed list sorted chronologically by timestamp.

21. The system of claim 19, wherein the retrotraverse behavior is implemented automatically when communication with the operator control unit is lost.

22. The system of claim 19, wherein the retrotraverse behavior is implemented when a command is received from the operator control unit.

23. The system of claim 19, wherein one of the waypoint routine and the retrotraverse behavior maintains a list of previously-performed retrotraverses by recording a list of start time and end time pairs for each retrotraverse period of time.

24. The system of claim 23, wherein the retrotraverse behavior excludes waypoints recorded during previously-performed retrotraverses.

25. The system of claim 24, wherein the retrotraverse behavior excludes waypoints recorded during previously-performed retrotraverses by excluding waypoints recorded between the start time and end time pairs for each previously-performed retrotraverse.

26. The system of claim 23, wherein the retrotraverse behavior excludes waypoints that were traversed during previously-performed retrotraverses.

27. The system of claim 19, wherein the retrotraverse behavior utilizes a lookahead vector to allow smooth navigation along an intended path of travel.

28. The system if claim 27, wherein the retrotraverse behavior only utilizes lookahead vectors that lie within a predetermined distance of each waypoint along the intended path of travel.

29. The system if claim 27, wherein, when utilizing a lookahead vector, the retrotraverse behavior avoids taking shortcuts that bypass waypoints.

30. The system of claim 27 wherein, when utilizing a lookahead vector, the retrotraverse behavior utilizes a radius of interception to determine whether the remote vehicle has reached a waypoint.

31. The system of claim 27 wherein, when utilizing a lookahead vector, the retrotraverse behavior utilizes a perpendicular plane to determine whether the remote vehicle has passed a waypoint.

32. The system of claim 19, wherein the retrotraverse behavior navigates the remote vehicle along the return path.

33. The system of claim 32, wherein the retrotraverse behavior selects a forward or backward direction for navigating the remote vehicle along the return path based on a determination of which direction requires the least rotation.

34. The system of claim 19, wherein the retrotraverse behavior determines the remote vehicle'"'"'s position using odometry.

35. The system of claim 34, wherein the retrotraverse behavior also determines the remote vehicle'"'"'s position using a global positioning system, ties global positioning system data to odometry data, and uses a Kalman filter to provide confidence in the remote vehicle'"'"'s position based on the odometry data and the global positioning system data.

36. The system of claim 19, wherein the retrotraverse behavior determines the remote vehicle'"'"'s position by maintaining a global map and placing the remote vehicle'"'"'s coordinates within the global map.

37. The system of claim 36, wherein the retrotraverse behavior maintains a destination point within the global map and adjusts the remote vehicle'"'"'s heading to navigate the remote vehicle toward the destination point.

38. The system of claim 19, wherein the retrotraverse behavior uses one or more of a global positioning system or navigation beacon points to determine the remote vehicle'"'"'s position.