Patent Grant
9498886
This disclosure relates to mobile human interface robots.
A robot is generally an electro-mechanical machine guided by a computer or electronic programming. Mobile robots have the capability to move around in their environment and are not fixed to one physical location. An example of a mobile robot that is in common use today is an automated guided vehicle or automatic guided vehicle (AGV). An AGV is generally a mobile robot that follows markers or wires in the floor, or uses a vision system or lasers for navigation. Mobile robots can be found in industry, military and security environments. They also appear as consumer products, for entertainment or to perform certain tasks like vacuum cleaning and home assistance.
One aspect of the disclosure provides a mobile human interface robot that includes a base defining a vertical center axis and a forward drive direction and a holonomic drive system supported by the base. The drive system has first, second, and third driven drive wheels, each trilaterally spaced about the vertical center axis and having a drive direction perpendicular to a radial axis with respect to the vertical center axis. The robot further includes a controller in communication with the holonomic drive system, a torso supported above the base, and a touch sensor system in communication with the controller. The touch sensor system is responsive to human contact. The controller issues drive commands to the holonomic drive system based on a touch signal received from the touch sensor system.
Implementations of the disclosure may include one or more of the following features. In some implementations, the touch sensor system is disposed at least in part on the torso. The robot may include an actuatable extendable leg disposed on the base and supporting the torso. The controller alters a height of the leg to alter a height of the torso in response to the received touch signal from the touch sensor system. The controller may instruct the leg to provide active assistance to a user height alteration of the torso in response to the received touch signal from the touch sensor system.
In some examples, the drive commands include reduced power assisted drive commands that propel the robot with assistance from a user in contact with the robot. The robot may include a neck disposed on the torso and a head supported by the neck. The neck can be configured to pan and tilt the head with respect to the torso. The controller may allow user articulation of the head in response to the received touch signal from the touch sensor system indicating head touching and maintains a pose of the head after completion of head touching. Moreover, the controller may articulate the head to face a location of contact on the robot in response to the received touch signal from the touch sensor system. In some examples, the robot includes a manipulation sensor disposed on at least one of the neck and the head for detecting user manipulation of the head.
In some implementations, the touch sensor system comprises at least one of a capacitive sensor, a contact sensor, a camera, a three-dimensional image sensor, and a switch. The touch sensor system may include contact sensors disposed on top, bottom, right, left, front, and back surfaces of the torso. Moreover, the touch sensor system may include at least one touch-responsive actuatable input positioned between 3 feet and 5 feet from a supporting surface of the robot.
The controller, in some examples, increases a movement resistance of at least a portion of the robot in a direction opposite to a received touch. In additional examples, the controller instructs the drive system to stop driving in response to the received touch signal from the touch sensor system.
In another aspect, a mobile human interface robot includes a base having a forward drive direction, a drive system supported by the base, and a robot computer supported by the base and capable of processing greater than 1000 million instructions per second (MIPS). The robot further includes at least one tablet computer detachably supported above the base and in wireless communication with the robot computer and a camera supported above the base and movable within at least one degree of freedom separately from the display.
In some implementations, the drive system includes first, second, and third driven drive wheels, each trilaterally spaced about a vertical center axis of the base and each having a drive direction perpendicular to a radial axis with respect to the vertical center axis. Each drive wheel may include first and second rows of rollers disposed about a periphery of the drive wheel. Each roller has a rolling direction perpendicular to a rolling direction of the drive wheel. Moreover, the rollers may each define an arcuate rolling surface. Together the rollers define an at least substantially circular rolling surface of the drive wheel.
In some examples, the camera is a volumetric point cloud imaging device positioned at a height of greater than 1 or 2 feet above a ground surface and directed to be capable of obtaining a point cloud from a volume of space that includes a floor plane in a direction of movement of the robot. In additional examples, the camera is a volumetric point cloud imaging device positioned to be capable of obtaining a point cloud from a volume of space adjacent the robot. The camera may be movable to view an area proximate a front edge of the base.
The tablet computer may include a touch screen having a display area of at least 150 square inches. Moreover, the tablet computer may move with at least one degree of freedom while attached to the robot. In some examples, the robot includes a display in electric communication with the robot computer. The tablet computer can be detachably receivable over the display. The display has an inactive state when the tablet computer is received over the display and an active state when the tablet computer is detached from the display.
In yet another aspect, a method of operating a mobile human interface robot includes receiving a touch signal from a touch sensor system of the robot in response to a user touching the robot. For a touching duration greater than a threshold period of time, the method includes driving the robot in a direction based on a location of contact on the robot. For a touching duration less than the threshold period of time, the method includes articulating an interface of the robot to at least substantially face the location of contact on the robot. For a touching duration less than the threshold period of time, the method includes issuing a zero velocity drive command.
In some implementations, the method includes issuing a drive command to a holonomic drive system to move the robot in a direction toward an opposite of the robot of the received touching, for a touching duration greater than the threshold period of time. The threshold period of time may be 0.25 seconds. The method may include at least one of panning and tilting a head of the robot with respect to a connected torso of the robot to at least substantially face the head toward the location of contact on the robot, for a touching duration less than the threshold period of time.
In some examples, the touch sensor system comprises at least one of a capacitive sensor, a contact sensor, a camera, a three-dimensional image sensor, and a switch.
In yet another aspect of the disclosure, a mobile human interface robot includes a drive system having at least one drive wheel driven by a corresponding drive motor, a localization system in communication with the drive system, a power source in communication with the drive system, the controller, and the localization system, and a touch response input supported above the drive system. Activation of the touch response input modifies delivery of power to the drive system to at least reduce a drive load of the drive motor on the corresponding at least one drive wheel.
In some implementations, activation of the touch response input ceases delivery of power to the drive system while allowing continued delivery of power to the localization system. In response to activation of the touch response input, the drive system may execute reduced power drive commands incapable alone of moving the robot and assisting user movement of the robot. Moreover, activation of the touch response input may cause decoupling of the at least one drive wheel from the corresponding drive motor. The touch response input may be positioned between about 3 feet and about 5 feet above a ground surface.
In some examples, the localization system includes a sensor system and a controller in communication with the drive system, the sensor system, the power source, and the hold button. The sensor system may include at least one of an inertial measurement unit, an odometer, a global positioning system, a laser scanner, a sonar proximity sensor, and a three-dimensional image sensor. In additional examples, the localization system includes at least one of a three image sensors, a laser scanner, one or more sonar proximity sensors, a drive wheel encoder for the at least one drive wheel, and drive wheel motor feedback.
The drive system, in some examples, includes first, second, and third holonomically driven drive wheels, each trilaterally spaced about a vertical axis of the robot and having a drive direction perpendicular to a radial axis with respect to the vertical axis;
The mobile human interface robot may also include a base supporting the drive system, an actuatable extendable leg disposed on the base, and a torso supported by the leg between about 3 feet and about 5 feet above a ground surface, the touch response input disposed on the torso. The touch responsive input may include at least one of a contact sensor, a capacitive sensor, an actuatable button, and a switch.
Another aspect of the disclosure provides a mobile human interface robot that includes a base defining a substantially trilaterally symmetric shape about a vertical center axis and having first, second, and third portions. The robot includes a holonomic drive system supported by the base. The drive system has first, second, and third drive wheels. Each drive wheel is trilaterally spaced about the vertical center axis and is supported by the corresponding first second and third base portions. Each drive wheel has a drive direction perpendicular to a radial axis with respect to the vertical center axis. The robot also includes a leg extending upward from the base and having a variable height, a torso supported by the leg, and a torso imaging sensor disposed on the torso. The torso defines a shoulder having a bottom surface overhanging the base. The torso imaging sensor is disposed on the bottom surface of the torso and points downward along a forward drive direction of the drive system. The torso imaging sensor captures three-dimensional images of a scene about the robot. The robot further includes a neck supported by the torso, a head supported by the neck, and a display supported by the head. The neck can pan and tilt the head with respect to the vertical center axis.
In some implementations, the display is releasably attached to the head. The display may include a locator for locating the display when detached from the head. In some examples, the display comprises tablet computer having a touch screen. Moreover, there will may include a tablet computer releasably attached to the head and/or other portions of the robot, such as the base, leg, and/or torso. In some implementations, the tablet computer is releasably received over the display. The robot may include a camera disposed on the head, which may be used for videoconferencing.
The robot may include a head imaging sensor mounted on the head and configured to capture three-dimensional images of a scene about the robot. The head imaging sensor may comprise a volumetric point cloud imaging device positioned to be capable of obtaining a point cloud from a volume of space adjacent the robot.
An arm may be disposed on the neck and supporting the head away from the neck. Moreover, the robot may include a manipulator arm disposed on the torso and an end effector disposed on a distal end of the manipulator arm. The manipulator arm may vary in length.
The details of one or more implementations of the disclosure are set forth in the accompanying drawings and the description below. Other aspects, features, and advantages will be apparent from the description and drawings, and from the claims.
Like reference symbols in the various drawings indicate like elements.
Mobile robots can interact or interface with humans to provide a number of services that range from home assistance to commercial assistance and more. In the example of home assistance, a mobile robot can assist elderly people with everyday tasks, including, but not limited to, maintaining a medication regime, mobility assistance, communication assistance (e.g., video conferencing, telecommunications, Internet access, etc.), home or site monitoring (inside and/or outside), person monitoring, and/or providing a personal emergency response system (PERS). For commercial assistance, the mobile robot can provide videoconferencing (e.g., in a hospital setting), a point of sale terminal, interactive information/marketing terminal, etc.
Referring to
The robot body 110, in the examples shown, includes a base 120, at least one leg 130 extending upwardly from the base 120, and a torso 140 supported by the at least one leg 130. The base 12.0 may support at least portions of the drive system 200. The robot body 110 also includes a neck 150 supported by the torso 140. The neck 150 supports a head 160, which supports at least a portion of the interfacing module 300. The base 120 includes enough weight (e.g., by supporting the power source 105 (batteries) to maintain a low center of gravity CGB of the base 120 and a low overall center of gravity CGR of the robot 100 for maintaining mechanical stability.
Referring to
In some implementations, the drive system 200 provides omni-directional and/or holonomic motion control of the robot 100. As used herein the term “omni-directional” refers to the ability to move in substantially any planar direction, i.e., side-to-side (lateral), forward/back, and rotational. These directions are generally referred to herein as x, y, and θz, respectively. Furthermore, the term “holonomic” is used in a manner substantially consistent with the literature use of the term and refers to the ability to move in a planar direction with three planar degrees of freedom, i.e., two translations and one rotation. Hence, a holonomic robot has the ability to move in a planar direction at a velocity made up of substantially any proportion of the three planar velocities (forward/back, lateral, and rotational), as well as the ability to change these proportions in a substantially continuous manner.
The robot 100 can operate in human environments (e.g., environments typically designed for bipedal, walking occupants) using wheeled mobility. In some implementations, the drive system 200 includes first, second, and third drive wheels 210a, 210b, 210c equally spaced (i.e., trilaterally symmetric) about the vertical axis Z (e.g., 120 degrees apart); however, other arrangements are possible as well. Referring to
Referring to
In the examples shown in
In some implementations of the drive system 200, each drive wheel 210a, 210b, 210 has a rolling direction DR radially aligned with a vertical axis Z, which is orthogonal to X and Y axes of the robot 100. The first drive wheel 210a can be arranged as a leading drive wheel along the forward drive direction F with the remaining two drive wheels 210b, 210c trailing behind. In this arrangement, to drive forward, the controller 500 may issue a drive command that causes the first drive wheel 210a to drive in a forward rolling direction and the second and third drive wheels 210b, 210c to drive at an equal rate as the first drive wheel 210a, but in a reverse direction.
In other implementations, the drive system 200 can be arranged to have the first and second drive wheels 210a, 210b positioned such that an angle bisector of an angle between the two drive wheels 210a, 210b is aligned with the forward drive direction F of the robot 100. In this arrangement, to drive forward, the controller 500 may issue a drive command that causes the first and second drive wheels 210a, 210b to drive in a forward rolling direction and an equal rate, while the third drive wheel 210c drives in a reverse direction or remains idle and is dragged behind the first and second drive wheels 210a, 210b. To turn left or right while driving forward, the controller 500 may issue a command that causes the corresponding first or second drive wheel 210a, 210b to drive at relatively quicker/slower rate. Other drive system 200 arrangements can be used as well. The drive wheels 210a, 210b, 210c may define a cylindrical, circular, elliptical, or polygonal profile.
Referring again to
Generally, telescopic arrangements include successively smaller diameter extrusions telescopically moving up and out of relatively larger extrusions at the base 120 in order to keep a center of gravity CGL of the entire leg 130 as low as possible. Moreover, stronger and/or larger components can be placed at the bottom to deal with the greater torques that will be experienced at the base 120 when the leg 130 is fully extended. This approach, however, offers two problems. First, when the relatively smaller components are placed at the top of the leg 130, any rain, dust, or other particulate will tend to run or fall down the extrusions, infiltrating a space between the extrusions, thus obstructing nesting of the extrusions. This creates a very difficult sealing problem while still trying to maintain full mobility/articulation of the leg 130. Second, it may be desirable to mount payloads or accessories on the robot 100. One common place to mount accessories is at the top of the torso 140. If the second leg portion 134 moves telescopically in and out of the first leg portion, accessories and components could only be mounted above the entire second leg portion 134, if they need to move with the torso 140. Otherwise, any components mounted on the second leg portion 134 would limit the telescopic movement of the leg 130.
By having the second leg portion 134 move telescopically over the first leg portion 132, the second leg portion 134 provides additional payload attachment points that can move vertically with respect to the base 120. This type of arrangement causes water or airborne particulate to run down the torso 140 on the outside of every leg portion 132, 134 (e.g., extrusion) without entering a space between the leg portions 132, 134. This greatly simplifies sealing any joints of the leg 130. Moreover, payload/accessory mounting features of the torso 140 and/or second leg portion 134 are always exposed and available no matter how the leg 130 is extended.
Referring to
The robot 100 may include one or more accessory ports 170 (e.g., mechanical and/or electrical interconnect points) for receiving payloads. The accessory ports 170 can be located so that received payloads do not occlude or obstruct sensors of the sensor system 400 (e.g., on the bottom and/or top surfaces 144, 146 of the torso 140, etc.). In some implementations, as shown in
An external surface of the torso 140 may be sensitive to contact or touching by a user, so as to receive touch commands from the user. For example, when the user touches the top surface 146 of the torso 140, the robot 100 responds by towering a height HT of the torso with respect to the floor (e.g., by decreasing the height HL of the leg(s) 130 supporting the torso 140). Similarly, when the user touches the bottom surface 144 of the torso 140, the robot 100 responds by raising the torso 140 with respect to the floor (e.g., by increasing the height HL of the leg(s) 130 supporting the torso 140). Moreover, upon receiving a user touch on forward, rearward, right or left portions of side surface 148 of the torso 140, the robot 100 responds by moving in a corresponding direction of the received touch command (e.g., rearward, forward, left, and right, respectively). The external surface(s) of the torso 140 may include a capacitive sensor in communication with the controller 500 that detects user contact.
Referring to
Referring again to
The head 160 may be sensitive to contact or touching by a user, so as to receive touch commands from the user. For example, when the user pulls the head 160 forward, the head 160 tilts forward with passive resistance and then holds the position. More over, if the user pushes/pulls the head 160 vertically downward, the torso 140 may lower (via a reduction in length of the leg 130) to lower the head 160. The head 160 and/or neck 150 may include strain gauges and/or contact sensors 165 (
With reference to
In some implementations, the robot 100 includes multiple web pad docks 302 on one or more portions of the robot body 110. In the example shown in
The interfacing module 300 may include a camera 320 disposed on the head 160 (see e.g.,
The robot 100 can provide videoconferencing (e.g., at 24 fps) through the interface module 300 (e.g., using a web pad 310, the camera 320, the microphones 320, and/or the speakers 340). The videoconferencing can be multiparty. The robot 100 can provide eye contact between both parties of the videoconferencing by maneuvering the head 160 to face the user. Moreover, the robot 100 can have a gaze angle of <5 degrees (e.g., an angle away from an axis normal to the forward face of the head 160). At least one 3-D image sensor 450 and/or the camera 320 on the robot 100 can capture life size images including body language. The controller 500 can synchronize audio and video (e.g., with the difference of <50 ms). In the example shown in
In some examples, the robot 100 can receive user inputs into the web pad 310 (e.g., via a touch screen), as shown in
The robot 100 can provide EMR integration, in some examples, by providing video conferencing between a doctor and patient and/or other doctors or nurses. The robot 100 may include pass-through consultation instruments. For example, the robot 100 may include a stethoscope configured to pass listening to the videoconferencing user (e.g., a doctor). In other examples, the robot includes connectors 170 that allow direct connection to Class II medical devices, such as electronic stethoscopes, otoscopes and ultrasound, to transmit medical data to a remote user (physician).
In the example shown in
Interactive applications executable on the controller 500 and/or in communication with the controller 500 may require more than one display on the robot 100. Multiple web pads 310 associated with the robot 100 can provide different combinations of “FaceTime”, Telestration, HD look at this-cam (e.g., for web pads 310 having built in cameras), can act as a remote operator control unit (OCU) for controlling the robot 100 remotely, and/or provide a local user interface pad.
In some implementations, the robot 100 includes a mediating security device 350 (
The Session Initiation Protocol (SIP) is an IETF-defined signaling protocol, widely used for controlling multimedia communication sessions such as voice and video calls over Internet Protocol (IP). The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty multicast) sessions including one or several media streams. The modification can involve changing addresses or ports, inviting more participants, and adding or deleting media streams. Other feasible application examples include video conferencing, streaming multimedia distribution, instant messaging, presence information, file transfer, etc. Voice over Internet Protocol (Voice over IP, VoIP) is part of a family of methodologies, communication protocols, and transmission technologies for delivery of voice communications and multimedia sessions over Internet Protocol (IP) networks, such as the Internet. Other terms frequently encountered and often used synonymously with VoIP are IP telephony, Internet telephony, voice over broadband (VoBB), broadband telephony, and broadband phone.
The robot 100 can provide various core robot features, which may include: mobility (e.g., the drive system 200); a reliable, safe, secure robot intelligence system, such as a control system executed on the controller 500, the power source 105, the sensing system 400, and optional manipulation with a. manipulator in communication with the controller 500. The control system can provide heading and speed control, body pose control, navigation, and core robot applications. The sensing system 400 can provide vision (e.g., via a camera 320), depth map imaging (e.g., via a 3-D imaging sensor 450), collision detection, obstacle detection and obstacle avoidance, and/or inertial measurement (e.g., via an inertial measurement unit 470).
The computing device 310 may be a tablet computer, portable electronic device, such as phone or personal digital assistant, or a dumb tablet or display (e.g., tablet that acts as a monitor for an atom-scale PC in the robot body 110). In some examples, the tablet computer can have a touch screen for displaying a user interface and receiving user inputs. The computing device 310 may execute one or more robot applications 1210, which may include software applications (e.g., stored in memory and executable on a processor) for security, medicine compliance, telepresence, behavioral coaching, social networking, active alarm, home management, etc. The computing device 310 may provide communication capabilities (e.g., secure wireless connectivity and/or cellular communication), refined application development tools, speech recognition, and person or object recognition capabilities. The computing device 310, in some examples utilizes an interaction/COMS featured operating system, such as Android provided by Google, Inc., iPad OS provided by Apple, Inc., other smart phone operating systems, or government systems, such as RSS A2.
The cloud 1220 provides cloud computing and/or cloud storage capabilities. Cloud computing may provide Internet-based computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For example, the cloud 1220 may be a cloud computing service that includes at least one server computing device, which may include a service abstraction layer and a hypertext transfer protocol wrapper over a server virtual machine instantiated thereon. The server computing device may be configured to parse HTTP requests and send HTTP responses. Cloud computing may be a technology that uses the Internet and central remote servers to maintain data and applications. Cloud computing can allow users to access and use applications without installation and access personal files at any computer with internet access. Cloud computing allows for relatively more efficient computing by centralizing storage, memory, processing and bandwidth. The cloud 1220 can provide scalable, on-demand computing power, storage, and bandwidth.
Cloud storage 1222 can be a model of networked computer data storage where data is stored on multiple virtual servers, generally hosted by third parties. By providing communication between the robot 100 and the cloudy 1220, information gathered by the robot 100 can be securely viewed by authorized users via a web based information portal.
The portal 1230 may be a web-based user portal for gathering and/or providing information, such as personal information, home status information, anger robot status information. Information can be integrated with third-party information to provide additional functionality and resources to the user and/or the robot 100. The robot system architecture 1200 can facilitate proactive data collection. For example, applications 1210 executed on the computing device 310 may collect data and report on actions performed by the robot 100 and/or a person or environment viewed by the robot 100 (using the sensing system 400). This data can be a unique property of the robot 100.
In some examples, the portal 1230 is a personal portal web site on the World Wide Web. The portal 1230 may provide personalized capabilities and a pathway to other content. The portal 1230 may use distributed applications, different numbers and types of middleware and hardware, to provide services from a number of different sources. In addition, business portals 1230 may share collaboration in workplaces and provide content usable on multiple platforms such as personal computers, personal digital assistants (PDAs), and cell phones/mobile phones. Information, news, and updates are examples of content that may be delivered through the portal 1230. Personal portals 1230 can be related to any specific topic such as providing friend information on a social network or providing links to outside content that may help others.
Referring again to
Referring to
There are several challenges involved in placing sensors on a robotic platform. First, the sensors need to be placed such that they have maximum coverage of areas of interest around the robot 100. Second, the sensors may need to be placed in such a way that the robot 100 itself causes an absolute minimum of occlusion to the sensors; in essence, the sensors cannot be placed such that they are “blinded” by the robot itself. Third, the placement and mounting of the sensors should not be intrusive to the rest of the industrial design of the platform. In terms of aesthetics, it can be assumed that a robot with sensors mounted inconspicuously is more “attractive” than otherwise. In terms of utility, sensors should be mounted in a manner so as not to interfere with normal robot operation (snagging on obstacles, etc.).
In some implementations, the sensor system 400 includes a set or an array of proximity sensors 410, 420 in communication with the controller 500 and arranged in one or more zones or portions of the robot 100 (e.g., disposed on or near the base body portion 124a, 124b, 124c of the robot body 110) for detecting any nearby or intruding obstacles. The proximity sensors 410, 420 may be converging infrared (IR) emitter-sensor elements, sonar sensors, ultrasonic sensors, and/or imaging sensors (e.g., 3D depth map image sensors) that provide a signal to the controller 500 when an object is within a given range of the robot 100.
In the example shown in
In some examples, the set of sonar proximity sensors 410 (e.g., 410a-410i) disposed around the base body 120 are arranged to point upward (e.g., substantially in the Z direction) and optionally angled outward away from the Z axis, thus creating a detection curtain 412 around the robot 100. Each sonar proximity sensor 410a-410i may have a shroud or emission guide 414 that guides the sonar emission upward or at least not toward the other portions of the robot body 110 (e.g., so as not to detect movement of the robot body 110 with respect to itself). The emission guide 414 may define a shell or half shell shape. In the example shown, the base body 120 extends laterally beyond the leg 130, and the sonar proximity sensors 410 (e.g., 410a-410i) are disposed on the base body 120 (e.g., substantially along a perimeter of the base body 120) around the leg 130. Moreover, the upward pointing sonar proximity sensors 410 are spaced to create a continuous or substantially continuous sonar detection curtain 412 around the leg 130. The sonar detection curtain 412 can be used to detect obstacles having elevated lateral protruding portions, such as table tops, shelves, etc.
The upward looking sonar proximity sensors 410 provide the ability to see objects that are primarily in the horizontal plane, such as table tops. These objects, due to their aspect ratio, may be missed by other sensors of the sensor system, such as the laser scanner 440 or imaging sensors 450, and as such, can pose a problem to the robot 100. The upward viewing sonar proximity sensors 410 arranged around the perimeter of the base 120 provide a means for seeing or detecting those type of objects/obstacles. Moreover, the sonar proximity sensors 410 can be placed around the widest points of the base perimeter and angled slightly outwards, so as not to be occluded or obstructed by the torso 140 or head 160 of the robot 100, thus not resulting in false positives for sensing portions of the robot 100 itself. In some implementations, the sonar proximity sensors 410 are arranged (upward and outward) to leave a volume about the torso 140 outside of a field of view of the sonar proximity sensors 410 and thus free to receive mounted payloads or accessories, such as the basket 340. The sonar proximity sensors 410 can be recessed into the base body 124 to provide visual concealment and no external features to snag on or hit obstacles.
The sensor system 400 may include or more sonar proximity sensors 410 (e.g., a rear proximity sensor 410j) directed rearward (e.g., opposite to the forward drive direction F) for detecting obstacles while backing up, The rear sonar proximity sensor 410j may include an emission guide 414 to direct its sonar detection field 412. Moreover, the rear sonar proximity sensor 410j can be used for ranging to determine a distance between the robot 100 and a detected object in the field of view of the rear sonar proximity sensor 410j (e.g., as “back-up alert”). In some examples, the rear sonar proximity sensor 410j is mounted recessed within the base body 120 an as to not provide any visual or functional irregularity in the housing form.
Referring to
The cliff proximity sensors 420 can detect when the robot 100 has encountered a falling edge of the floor, such as when it encounters a set of stairs. The controller 500 (executing a control system) may execute behaviors that cause the robot 100 to take an action, such as changing its direction of travel, when an edge is detected. In some implementations, the sensor system 400 includes one or more secondary cliff sensors (e.g., other sensors configured for cliff sensing and optionally other types of sensing). The cliff detecting proximity sensors 420 can be arranged to provide early detection of cliffs, provide data for discriminating between actual cliffs and safe events (such as climbing over thresholds), and be positioned down and out so that their field of view includes at least part of the robot body 110 and an area away from the robot body 110. In some implementations, the controller 500 executes cliff detection routine that identifies and detects an edge of the supporting work surface (e.g., floor), an increase in distance past the edge of the work surface, and/or an increase in distance between the robot body 110 and the work surface. This implementation allows: 1) early detection of potential cliffs (which may allow faster mobility speeds in unknown environments); 2) increased reliability of autonomous mobility since the controller 500 receives cliff imaging information from the cliff detecting proximity sensors 420 to know if a cliff event is truly unsafe or if it can be safely traversed (e.g., such as climbing up and over a threshold); 3) a reduction in false positives of cliffs (e.g., due to the use of edge detection versus the multiple discrete IR proximity sensors with a narrow field of view). Additional sensors arranged as “wheel drop” sensors can be used for redundancy and for detecting situations where orange-sensing camera cannot reliably detect a certain type of cliff.
Threshold and step detection allows the robot 100 to effectively plan for either traversing a climb-able threshold or avoiding a step that is too tall. This can be the same for random objects on the work surface that the robot 100 may or may not be able to safely traverse. For those obstacles or thresholds that the robot 100 determines it can climb, knowing their heights allows the robot 100 to slow down appropriately, if deemed needed, to allow for a smooth transition in order to maximize smoothness and minimize any instability due to sudden accelerations. In some implementations, threshold and step detection is based on object height above the work surface along with geometry recognition (e.g., discerning between a threshold or an electrical cable versus a blob, such as a sock). Thresholds may be recognized by edge detection. The controller 500 may receive imaging data from the cliff detecting proximity sensors 420 (or another imaging sensor on the robot 100), execute an edge detection routine, and issue a drive command based on results of the edge detection routine. The controller 500 may use pattern recognition to identify objects as well. Threshold detection allows the robot 100 to change its orientation with respect to the threshold to maximize smooth step climbing
The proximity sensors 410, 420 may function alone, or as an alternative, may function in combination with one or more contact sensors 430 (e.g., bump switches) for redundancy. For example, one or more contact or bump sensors 430 on the robot body 110 can detect if the robot 100 physically encounters an obstacle. Such sensors may use a physical property such as capacitance or physical displacement within the robot 100 to determine when it has encountered an obstacle. In some implementations, each base body portion 124a, 124b, 124c of the base 120 has an associated contact sensor 430 (e.g., capacitive sensor, read switch, etc.) that detects movement of the corresponding base body portion 124a, 124b, 124c with respect to the base chassis 122 (see e.g.,
Referring again to
The laser scanner 440 scans an area about the robot 100 and the controller 500, using signals received from the laser scanner 440, creates an environment map or object map of the scanned area. The controller 500 may use the object map for navigation, obstacle detection, and obstacle avoidance. Moreover, the controller 500 may use sensory inputs from other sensors of the sensor system 400 for creating object map and/or for navigation.
In some examples, the laser scanner 440 is a scanning LIDAR, which may use a laser that quickly scans an area in one dimension, as a “main” scan line, and a time-of-flight imaging element that uses a phase difference or similar technique to assign a depth to each pixel generated in the tine (returning a two dimensional depth line in the plane of scanning). In order to generate a three dimensional map, the LIDAR can perform an “auxiliary” scan in a second direction (for example, by “nodding” the scanner). This mechanical scanning technique can be complemented, if not supplemented, by technologies such as the “Flash” LIDAR/LADAR and “Swiss Ranger” type focal plane imaging element sensors, techniques which use semiconductor stacks to permit time of flight calculations for a full 2-D matrix of pixels to provide a depth at each pixel, or even a series of depths at each pixel (with an encoded illuminator or illuminating laser).
The sensor system 400 may include one or more three-dimensional (3-D) image sensors 450 in communication with the controller 500. If the 3-D image sensor 450 has a limited field of view, the controller 500 or the sensor system 400 can actuate the 3-D image sensor 450a in amide-to-side scanning manner to create a relatively wider field of view to perform robust ODOA. Referring to
In some implementations, the sensor system 400 includes additional 3-D image sensors 450 disposed on the base body 120, the leg 130, the neck 150, and/or the head 160. In the example shown in
A forward facing 3-D image sensor 450 disposed on the neck 150 and/or the head 160 can be used for person, face, and/or gesture recognition of people about the robot 100. For example, using signal inputs from the 3-D image sensor 450 on the head 160, the controller 500 may recognize a user by creating a three-dimensional map of the viewed/captured user's face and comparing the created three-dimensional map with known 3-D images of people's faces and determining a match with one of the known 3-D facial images. Facial recognition may be used for validating users as allowable users of the robot 100. Moreover, one or more of the 3-D image sensors 450 can be used for determining gestures of person viewed by the robot 100, and optionally reacting based on the determined gesture(s) (e.g., hand pointing, waving, and or hand signals). For example, the controller 500 may issue a drive command in response to a recognized hand point in a particular direction.
The 3-D image sensors 450 may be capable of producing the following types of data: (i) a depth map, (ii) a reflectivity based intensity image, and/or (iii) a regular intensity image. The 3-D image sensors 450 may obtain such data by image pattern matching, measuring the flight time and/or phase delay shift for light emitted from a source and reflected off of a target.
In some implementations, reasoning or control software, executable on a processor (e.g., of the robot controller 500), uses a combination of algorithms executed using various data types generated by the sensor system 400. The reasoning software processes the data collected from the sensor system 400 and outputs data for making navigational decisions on where the robot 100 can move without colliding with an obstacle, for example. By accumulating imaging data over time of the robot's surroundings, the reasoning software can in turn apply effective methods to selected segments of the sensed image(s) to improve depth measurements of the 3-D image sensors 450. This may include using appropriate temporal and spatial averaging techniques.
The reliability of executing robot collision free moves may be based on: (i) a confidence level built by high level reasoning over time and (ii) a depth-perceptive sensor that accumulates three major types of data for analysis—(a) a depth image, (b) an active illumination image and (c) an ambient illumination image. Algorithms cognizant of the different types of data can be executed on each of the images obtained by the depth-perceptive imaging sensor 450. The aggregate data may improve the confidence level a compared to a system using only one of the kinds of data.
The 3-D image sensors 450 may obtain images containing depth and brightness data from a scene about the robot 100 (e.g., a sensor view portion of a room or work area) that contains one or more objects. The controller 500 may be configured to determine occupancy data for the object based on the captured reflected light from the scene. Moreover, the controller 500, in some examples, issues a drive command to the drive system 200 based at least in part on the occupancy data to circumnavigate obstacles (i.e., the object in the scene). The 3-D image sensors 450 may repeatedly capture scene depth images for real-time decision making by the controller 500 to navigate the robot 100 about the scene without colliding into any objects in the scene. For example, the speed or frequency in which the depth image data is Obtained by the 3-D image sensors 450 may be controlled by a shutter speed of the 3-D image sensors 450. In addition, the controller 500 may receive an event trigger (e.g., from another sensor component of the sensor system 400, such as proximity sensor 410, 420, notifying the controller 500 of a nearby object or hazard. The controller 500, in response to the event trigger, can cause the 3-D image sensors 450 to increase a frequency at which depth images are captured and occupancy information is obtained.
In some implementations, the robot includes a sonar scanner 460 for acoustic imaging of an area surrounding the robot 100. In the examples shown in
Referring to
The second 3-D image sensor 450b is mounted on the head 160, which can pan and tilt via the neck 150. The second 3-D image sensor 450b can be useful for remote driving since it allows a human operator to see where the robot 100 is going. The neck 150 enables the operator tilt and/or pan the second 3-D image sensor 450b to see both close and distant objects. Panning the second 3-D image sensor 450b increases an associated horizontal field of view. During fast travel, the robot 100 may tilt the second 3-D image sensor 450b downward slightly to increase a total or combined field of view of both 3-D image sensors 450a, 450b, and to give sufficient time for the robot 100 to avoid an obstacle (since higher speeds generally mean less time to react to obstacles). At slower speeds, the robot 100 may tilt the second 3-D image sensor 450b upward or substantially parallel to the ground G to track a person that the robot 100 is meant to follow. Moreover, while driving at relatively low speeds, the robot 100 can pan the second 3-D image sensor 450b to increase its field of view around the robot 100. The first 3-D image sensor 450a can stay fixed (e.g., not moved with respect to the base 120) when the robot is driving to expand the robot's perceptual range.
In some implementations, at least one of 3-D image sensors 450 can be a volumetric point cloud imaging device (such as a speckle or time-of-flight camera) positioned on the robot 100 at a height of greater than 1 or 2 feet above the ground (or at a height of about 1 or 2 feet above the ground) and directed to be capable of obtaining a point cloud from a volume of space including a floor plane in a direction of movement of the robot (via the omni-directional drive system 200). In the examples shown in
Referring again to
The controller 500 may monitor any deviation in feedback from the IMU 470 from a threshold signal corresponding to normal unencumbered operation. For example, if the robot begins to pitch away from an upright position, it may be “clothes lined” or otherwise impeded, or someone may have suddenly added a heavy payload. In these instances, it may be necessary to take urgent action (including, but not limited to, evasive maneuvers, recalibration, and/or issuing an audio/visual warning) in order to assure safe operation of the robot 100.
Since robot 100 may operate in a human environment, it may interact with humans and operate in spaces designed for humans (and without regard for robot constraints). The robot 100 can limit its drive speeds and accelerations when in a congested, constrained, or highly dynamic environment, such as at a cocktail party or busy hospital. However, the robot 100 may encounter situations where it is safe to drive relatively fast, as in a long empty corridor, but yet be able to decelerate suddenly, as when something crosses the robots' motion path.
When accelerating from a stop, the controller 500 may take into account a moment of inertia of the robot 100 from its overall center of gravity CGR to prevent robot tipping. The controller 500 may use a model of its pose, including its current moment of inertia. When payloads are supported, the controller 500 may measure a load impact on the overall center of gravity CGR and monitor movement of the robot moment of inertia. For example, the torso 140 and/or neck 150 may include strain gauges to measure strain. If this is not possible, the controller 500 may apply a test torque command to the drive wheels 210 and measure actual linear and angular acceleration of the robot using the IMU 470, in order to experimentally determine safe limits.
During a sudden deceleration, a commanded load on the second and third drive wheels 210b, 210c (the rear wheels) is reduced, while the first drive wheel 210a (the front wheel) slips in the forward drive direction and supports the robot 100. If the loading of the second and third drive wheels 210b, 210c (the rear wheels) is asymmetrical, the robot 100 may “yaw” which will reduce dynamic stability. The IMU 470 (e.g., a gyro) can be used to detect this yaw and command the second and third drive wheels 210b, 210c to reorient the robot 100.
Referring to
MIMO can be sub-divided into three main categories, pre-coding, spatial multiplexing or SM, and diversity coding. Pre-coding is a type of multi-stream beam forming and is considered to be all spatial processing that occurs at the transmitter. In (single-layer) beam forming, the same signal is emitted from each of the transmit antennas with appropriate phase (and sometimes gain) weighting such that the signal power is maximized at the receiver input. The benefits of beam forming are to increase the received signal gain, by making signals emitted from different antennas add up constructively, and to reduce the multipath fading effect. In the absence of scattering, beam forming can result in a well defined directional pattern. When the receiver has multiple antennas, the transmit beam forming cannot simultaneously maximize the signal level at all of the receive antennas, and pre-coding with multiple streams can be used. Pre-coding may require knowledge of channel state information (CSI) at the transmitter.
Spatial multiplexing requires a MIMO antenna configuration. In spatial multiplexing, a high rate signal is split into multiple lower rate streams and each stream is transmitted from a different transmit antenna in the same frequency channel. If these signals arrive at the receiver antenna array with sufficiently different spatial signatures, the receiver can separate these streams into (almost) parallel channels. Spatial multiplexing is a very powerful technique for increasing channel capacity at higher signal-to-noise ratios (SNR). The maximum number of spatial streams is limited by the lesser in the number of antennas at the transmitter or receiver. Spatial multiplexing can be used with or without transmit channel knowledge. Spatial multiplexing can also be used for simultaneous transmission to multiple receivers, known as space-division multiple access. By scheduling receivers with different spatial signatures, good separability can be assured.
Diversity Coding techniques can be used when there is no channel knowledge at the transmitter. In diversity methods, a single stream (unlike multiple streams in spatial multiplexing) is transmitted, but the signal is coded using techniques called space-time coding. The signal is emitted from each of the transmit antennas with full or near orthogonal coding. Diversity coding exploits the independent fading in the multiple antenna links to enhance signal diversity. Because there is no channel knowledge, there is no beam forming or array gain from diversity coding. Spatial multiplexing can also be combined with pre-coding when the channel is known at the transmitter or combined with diversity coding when decoding reliability is in trade-off.
In some implementations, the robot 100 includes a third antenna 490c and/or a fourth antenna 490d and the torso 140 and/or the head 160, respectively (see e.g.,
Referring to
The applications 520 can be stored in memory of or communicated to the robot 100, to run concurrently on (e.g., a processor) and simultaneously control the robot 100. The applications 520 may access behaviors 600 of the behavior system 510b. The independently deployed applications 520 are combined dynamically at runtime and to share robot resources 530 (e.g., drive system 200, arm(s), head(s), etc.) of the robot 100. A low-level policy is implemented for dynamically sharing the robot resources 530 among the applications 520 at run-time. The policy determines which application 520 has control of the robot resources 530 required by that application 520 (e.g. a priority hierarchy among the applications 520). Applications 520 can start and stop dynamically and run completely independently of each other. The control system 510 also allows for complex behaviors 600 which can be combined together to assist each other.
The control arbitration system 510a includes one or more resource controllers 540, a robot manager 550, and one or more control arbiters 560. These components do not need to be in a common process or computer, and do not need to be started in any particular order. The resource controller 540 component provides an interface to the control arbitration system 510a for applications 520. There is an instance of this component for every application 520. The resource controller 540 abstracts and encapsulates away the complexities of authentication, distributed resource control arbiters, command buffering, and the like. The robot manager 550 coordinates the prioritization of applications 520, by controlling which application 520 has exclusive control of any of the robot resources 530 at any particular time. Since this is the central coordinator of information, there is only one instance of the robot manager 550 per robot. The robot manager 550 implements a priority policy, which has a linear prioritized order of the resource controllers 540, and keeps track of the resource control arbiters 560 that provide hardware control. The control arbiter 560 receives the commands from every application 520 and generates a single command based on the applications' priorities and publishes it for its associated resources 530. The control arbiter 560 also receives state feedback from its associated resources 530 and sends it back up to the applications 520. The robot resources 530 may be a network of functional modules (e.g. actuators, drive systems, and groups thereof) with one or more hardware controllers. The commands of the control arbiter 560 are specific to the resource 530 to carry out specific actions.
A dynamics model 570 executable on the controller 500 can be configured to compute the center for gravity (CG), moments of inertia, and cross products of inertia of various portions of the robot 100 for the assessing a current robot state. The dynamics model 570 may also model the shapes, weight, and/or moments of inertia of these components. In some examples, the dynamics model 570 communicates with the inertial moment unit 470 (IMU) or portions of one e.g., accelerometers and/or gyros) disposed on the robot 100 and in communication with the controller 500 for calculating the various center of gravities of the robot 100. The dynamics model 570 can be used by the controller 500, along with other programs 520 or behaviors 600 to determine operating envelopes of the robot 100 and its components.
Each application 520 has an action selection engine 580 and a resource controller 540, one or more behaviors 600 connected to the action selection engine 580, and one or more action models 590 connected to action selection engine 580. The behavior system 510b provides predictive modeling and allows the behaviors 600 to collaboratively decide on the robot's actions by evaluating possible outcomes of robot actions. In some examples, a behavior 600 is a plug-in component that provides a hierarchical, state-full evaluation function that couples sensory feedback from multiple sources with a-priori limits and information into evaluation feedback on the allowable actions of the robot. Since the behaviors 600 are pluggable into the application 520 (e.g., residing inside or outside of the application 520), they can be removed and added without having to modify the application 520 or any other part of the control system 510. Each behavior 600 is a standalone policy. To make behaviors 600 more powerful, it is possible to attach the output of multiple behaviors 600 together into the input of another so that you can have complex combination functions. The behaviors 600 are intended to implement manageable portions of the total cognizance of the robot 100.
The action selection engine 580 is the coordinating element of the control system 510 and runs a fast, optimized action selection cycle (prediction/correction cycle) searching for the best action given the inputs of all the behaviors 600. The action selection engine 580 has three phases: nomination, action selection search, and completion. In the nomination phase, each behavior 600 is notified that the action selection cycle has started and is provided with the cycle start time, the current state, and limits of the robot actuator space. Based on internal policy or external input, each behavior 600 decides whether or not it wants to participate in this action selection cycle. During this phase, a list of active behavior primitives is generated whose input will affect the selection of the commands to be executed on the robot 100.
In the action selection search phase, the action selection engine 580 generates feasible outcomes from the space of available actions, also referred to as the action space. The action selection engine 580 uses the action models 590 to provide a pool of feasible commands (within limits) and corresponding outcomes as a result of simulating the action of each command at different time steps with a time horizon in the future. The action selection engine 580 calculates a preferred outcome, based on the outcome evaluations of the behaviors 600, and sends the corresponding command to the control arbitration system 510a and notifies the action model 590 of the chosen command as feedback.
In the completion phase, the commands that correspond to a collaborative best scored outcome are combined together as an overall command, which is presented to the resource controller 540 for execution on the robot resources 530. The best outcome is provided as feedback to the active behaviors 600, to be used in future evaluation cycles.
Received sensor signals from the sensor system 400 can cause interactions with one or more behaviors 600 to execute actions. For example, using the control system 510, the controller 500 selects an action (or move command) for each robotic component e.g., motor or actuator) from a corresponding action space (e.g., a collection of possible actions or moves for that particular component) to effectuate a coordinated move of each robotic component in an efficient manner that avoids collisions with itself and any objects about the robot 100, which the robot 100 is aware of. The controller 500 can issue a coordinated command over robot network, such as an EtherIO network, as described in U.S. Ser. No. 61/305,069, filed Feb. 16, 2010, the entire contents of which are hereby incorporated by reference.
The control system 510 may provide adaptive speed/acceleration of the drive system 200 (e.g., via one or more behaviors 600) in order to maximize stability of the robot 100 in different configurations/positions as the robot 100 maneuvers about an area.
In some implementations, the controller 500 issues commands to the drive system 200 that propels the robot 100 according to a heading setting and a speed setting. One or behaviors 600 may use signals received from the sensor system 400 to evaluate predicted outcomes of feasible commands, one of which may be elected for execution (alone or in combination with other commands as an overall robot command) to deal with obstacles. For example, signals from the proximity sensors 410 may cause the control system 510 to change the commanded speed or heading of the robot 100. For instance, a signal from a proximity sensor 410 due to a nearby wall may result in the control system 510 issuing a command to slow down. In another instance, a collision signal from the contact sensor(s) due to an encounter with a chair may cause the control system 510 to issue a command to change heading. In other instances, the speed setting of the robot 100 may not be reduced in response to the contact sensor; and/or the heading setting of the robot 100 may not be altered in response to the proximity sensor 410.
The behavior system 510b may include a speed behavior 600 (e.g., a behavioral routine executable on a processor) configured to adjust the speed setting of the robot 100 and a heading behavior 600 configured to alter the heading setting of the robot 100. The speed and heading behaviors 600 may be configured to execute concurrently and mutually independently. For example, the speed behavior 600 may be configured to poll one of the sensors (e.g. the set(s) of proximity sensors 410, 420), and the heading behavior 600 may be configured to poll another sensor (e.g., the kinetic bump sensor).
Referring to
The torso touch teleoperation behavior 600a may issue assisted drive commands to the drive system 200 that allow the user to push the robot 100 while receiving drive assistance from the drive system 200 (e.g., partial velocity commands that by themselves cannot move the robot 100, but assist movement of the robot 100 by the user).
The torso touch teleoperation behavior 600a may receive sensor signals from the touch sensor system 480 (e.g., buttons, capacitive sensors, contact sensors, etc.), a portion of which may be disposed on the torso 140 (and elsewhere on the robot 100, such as the head 160). The torso touch teleoperation behavior 600a may position the torso 140 at a height HT of between 3 and 5 feet from the ground G, so as to place at least a portion of the touch sensor system 480 at an accessible height for a typical user.
in some implementations, the torso touch teleoperation behavior 600a recognizes user touching to place the robot 100 and particular pose. For example, when the user 1600 pushes down on the torso 140, the sensor system 400 detects the downward force on the torso 140 and sends corresponding signals to the controller 500. The torso touch teleoperation behavior 600a receives indication of the downward force on the torso 140 and causes the control system 510 to issue a command to decrease the length HL of the leg 130, thereby lowering the height HT of the torso 140. Similarly, when the user 1600 pushes/pulls up on the torso 140, the torso touch teleoperation behavior 600a receives indication of the upward force on the torso 140 from the sensor system 400 and causes the control system 510 to issue a command to increase the length HL of the leg 130, thereby increasing the height HT of the torso 140.
When the user 1600 pushes, pulls and/or rotates the head 160, the torso touch teleoperation behavior 600a may receive indication from the sensor system 400 (e.g., from strain gages/motion/contact sensors 165 on the neck 150) of the user action and may respond by causing the control system 510 to issue a command to move the head 160 accordingly and thereafter hold the pose.
In some implementations, the robot 100 provides passive resistance and/or active assistance to user manipulation of the robot 100. For example, the motors 138b, 152, 154 actuating the leg 130 and the neck 150 passive resistance and/or active assistance to user manipulation of the robot 100 to provide feedback to the user of the manipulation as well as assistance for moving relatively heavy components such as raising the torso 140. This allows the user to move various robotic components without having to bear the entire weight of the corresponding components.
The behavior system 510b may include a tap-attention behavior 600b (e.g., a behavioral routine executable on a processor) configured to focus attention of the robot 100 toward a user. The tap-attention behavior 600b may become active when the sensor system 400 detects that the torso 140 (or some other portion of the robot 100) has received contact (e.g., human contact) for less than a threshold time period (e.g., 0.25 seconds). Moreover, the tap-attention behavior 600b may only become active when the torso touch teleoperation behavior 600a is inactive. For example, a sensed touch on the torso 140 for 0.2 seconds will not trigger the torso touch teleoperation behavior 600a, but will trigger the tap-attention behavior 600b. The tap-attention behavior 600b may use a contact location on the torso 140 and cause the head 160 to tilt and/or pan (via actuation of the neck 150) to look at the user. A stop criteria for the behavior 600b can be reached when the head 160 reaches a position where it is looking in the direction of the touch location.
In some implementations, the behavior system 510b includes a tap-stop behavior 600c (e.g., a behavioral routine executable on a processor) configured to stop the drive system 200 from driving (e.g., bring the robot 100 to a stop). The tap-stop behavior 600c may become active when the sensor system 400 detects that the torso 140 has received contact (e.g., human contact) and issues a zero velocity drive command to the drive system 200, cancelling any previous drive commands. If the robot is driving and the user wants it to stop, the user can tap the torso 140 (or some other portion of the robot 100) or a touch sensor. In some examples, the tap-stop behavior 600c can only be activated if higher priority behaviors, such as the torso touch teleoperation behavior 600a and the tap-attention behavior 600b, are not active. The tap-stop behavior 600c may end with the sensor system 400 no longer detects touching on the torso 140 (or elsewhere on the robot 100).
Referring to
Removing high voltage power from the motors drive wheel motors 220a-c may release a drive torque on the drive wheels 210a-c. In some instances, it may be necessary to use mechanical hardware, such as a clutch, or other wheel engagement methodologies. Circuitry associated with the hold button 175 may need to prevent currents from flowing in the motors 220a-c due to externally applied torque when the robot 100 is manually moved by the user. A device, such as a relay, which opens the corresponding motor connections, can be used to prevent currents from flowing in the motors 220a-c due to externally applied torque when the robot 100 is manually moved by the user. Alternatively, a device which allows a motor DC bus raise will prevent motor currents from flowing. If this is done in a way where energy is only available from user moving the robot 100, then the drive wheel motors 220a-c may still be prevented from moving under a robot command, which can be an intent of the hold button 175.
In some implementations, activation of the hold button 175 but not cut power to the drive system 200, but rather places the drive system 200 into an assisted mode that biases the drive motors 220a-c in a manner that does no propel the robot 100 and only assists user movement of the robot 100.
The drive system 200 may be configured such that less than 50N lateral resistance is required to move the robot 100 at floor level. Moreover, the base 120 may be sized to have a wheel base of less than a 2 ft in any direction, and pushing the robot 100 with a 100N force at a height of 4 feet above the ground does not take the robot 100.
Referring to
Mounting the manipulator 180 to a mobility platform can ease this problem, since some degrees of freedom will be accounted for by the mobility of the platform itself. However, if the mobility paradigm is based on tracked or parallel wheeled approaches, the manipulator 180 will still require some joint articulation in order to able to move the end effector 182 in any direction while maintaining any orientation of the mobility platform. For example, if the manipulator 180 is pointing straight forward on a tracked vehicle and there is a desire to move the end effector 182 directly sideways while maintaining the orientation of the tracked vehicle, some articulation in the manipulator 180 is required without moving the tracked vehicle, as the tracked vehicle cannot move directly sideways (i.e., perpendicular to a drive direction of the tracks).
The holonomic drive system 200 in conjunction with the variable height of the torso 140 (via actuation of the leg 130) allows infinite degrees of freedom of movement of a non-articulated manipulator 180 disposed on the torso 140, so that the end effector 182 can be moved along any vector in true space, while maintaining any given robot orientation. Moreover, mounting the manipulator 180 on the head 160, which can be moved with the neck 150, provides additional movement and reach of the manipulator 180. The holonomic mobility of the base 120 provides x, y, and θz degrees of freedom. Vertical actuation of the leg 130 moves the torso 140 in the Z direction for a “z” degree of freedom. Therefore, the robot 100 can provide x, y, z, and θ movement of the end effector 182 without any articulation of the manipulator 180 itself.
In addition to the reduced cost and complexity of the manipulator 180, this approach greatly simplifies the computer processing necessary to control the end effector 182 in various directions. Resolved motion, or the ability to move an end effector 182 in a particular direction by controlling multiple joints with multiple degrees of freedom, requires complex logic and control algorithms. However, mounting the manipulator on the torso 140 of the disclosed robot 100 allows for independent control of each degree of freedom (x, y, z, and θz), rather than relying on controlling joints which impact more than one of those degrees, makes the math behind the resolved motion algorithms relatively easier. This further allows relatively lesser requirements for computer processor overhead, reducing cost and increasing reliability.
Traditionally, methods of opening and/or passing through a door or doorway for a robot include keeping a door open using a “chock” or using a multiple degree of freedom, large range of motion manipulator to continuously keep the door open (which requires custom corrugated motion) while the robot maneuvers through the doorway (e.g., using non-holonomic motion (y and θz only)). The holonomic drive system 200 allows the robot 100 to open a door (free hung or self-closing) and pass through the corresponding doorway.
Referring to
For opening/closing a relatively heavy door 1902 with a relatively small, lightweight robot 100, after disengaging the door knob 1904 (e.g., by turning the door knob or toggling the lever), maneuvering the robot 100 as close as possible to the door knob 1904 while decreasing an extension length of the manipulator 180 to minimize a distance between door knob 1904 and the base 120. The method further includes pushing up on the door knob 1904 (e.g., by lifting the torso 140, as by extending the leg 130) to increase the normal force on the drive wheels 210a-c, thereby increasing traction.
For negotiating past a self-closing door 1902 (from either direction), once the door 1902 is open, robot 100 is already close to the door 1902 and can rotate and/or traverse the base 120 to act as a chock. In some examples, the manipulator 180 includes a passive or active pan degree of freedom (DOF) to maintain contact between the end effector 182 and the door knob 1904. Once through the doorway 1900, the method includes releasing the end effector 182 and retracting the manipulator 180 (e.g., by using the x, y, and θz DOF's of the base 120) to smoothly pass through the doorway 1900 while maintaining continuous contact with the door 1902 and the robot base 120. No sliding contact motion against the door 1902 is required, thus avoiding scratching the robot 100 or the door 1902 and avoiding any friction therebetween, which would increase robot effort. Since the robot 100, in some implementations, maintains all associated components above the base 120 within a vertical volume defined by the base 120, the only contact with the door 1902 is with the base 120. Since the contact with the door 1902 is close to the ground, traction and stability of the robot 100 can be maximized.
In the example shown in
Referring to
Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor, and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” and “computer-readable medium” refer to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a. programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor.
Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single tile dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer readable media suitable for storing computer program instructions and data include all forms of non volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
Implementations of the subject matter described in this specification can be implemented in a computing system that includes aback end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the subject matter described is this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular implementations of the invention. Certain features that are described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multi-tasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results.
This U.S. patent application is a continuation of, and claims priority under 35 U.S.C. §120 from, U.S. patent application Ser. No. 13/032,370, filed on Feb. 22, 2011, which claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application 61/346,612, filed on May 20, 2010; U.S. Provisional Application 61/356,910, filed on Jun. 21, 2010; U.S. Provisional Application 61/428,717, filed on Dec. 30, 2010; U.S. Provisional Application 61/428,734, filed on Dec. 30, 2010; U.S. Provisional Application 61/428,759, filed on Dec. 30, 2010; and U.S. Provisional Application 61/429,863, filed on Jan. 5, 2011. The disclosures of these prior applications are considered part of the disclosure of this application and are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4223753 | Bradbury | Sep 1980 | A |
| 4413693 | Derby | Nov 1983 | A |
| 4638445 | Mattaboni | Jan 1987 | A |
| 4669168 | Tamura et al. | Jun 1987 | A |
| 4697472 | Hiyane | Oct 1987 | A |
| 4709265 | Silverman et al. | Nov 1987 | A |
| 4751658 | Kadonoff et al. | Jun 1988 | A |
| 4777416 | George, II et al. | Oct 1988 | A |
| 4797557 | Ohman | Jan 1989 | A |
| 4803625 | Fu et al. | Feb 1989 | A |
| 4847764 | Halvorson | Jul 1989 | A |
| 4875172 | Kanayama | Oct 1989 | A |
| 4942538 | Yuan et al. | Jul 1990 | A |
| 4953159 | Hayden et al. | Aug 1990 | A |
| 4974607 | Miwa | Dec 1990 | A |
| 4977971 | Crane, III et al. | Dec 1990 | A |
| 5006988 | Borenstein et al. | Apr 1991 | A |
| 5040116 | Evans, Jr. et al. | Aug 1991 | A |
| 5051906 | Evans, Jr. et al. | Sep 1991 | A |
| 5073749 | Kanayama | Dec 1991 | A |
| 5084828 | Kaufman et al. | Jan 1992 | A |
| 5130794 | Ritchey | Jul 1992 | A |
| 5148591 | Pryor | Sep 1992 | A |
| 5153833 | Gordon et al. | Oct 1992 | A |
| 5155684 | Burke et al. | Oct 1992 | A |
| 5157491 | Kassatly | Oct 1992 | A |
| 5193143 | Kaemmerer et al. | Mar 1993 | A |
| 5217453 | Wilk | Jun 1993 | A |
| 5224157 | Yamada et al. | Jun 1993 | A |
| 5231693 | Backes et al. | Jul 1993 | A |
| 5236432 | Matsen, III et al. | Aug 1993 | A |
| 5315287 | Sol | May 1994 | A |
| 5319611 | Korba | Jun 1994 | A |
| 5341242 | Gilboa et al. | Aug 1994 | A |
| 5341459 | Backes | Aug 1994 | A |
| 5350033 | Kraft | Sep 1994 | A |
| 5366896 | Margrey et al. | Nov 1994 | A |
| 5372211 | Wilcox et al. | Dec 1994 | A |
| 5374879 | Pin et al. | Dec 1994 | A |
| 5417210 | Funda et al. | May 1995 | A |
| 5436542 | Petelin et al. | Jul 1995 | A |
| 5441047 | David et al. | Aug 1995 | A |
| 5442728 | Kaufman et al. | Aug 1995 | A |
| 5462051 | Oka et al. | Oct 1995 | A |
| 5539741 | Barraclough et al. | Jul 1996 | A |
| 5544649 | David et al. | Aug 1996 | A |
| 5553609 | Chen et al. | Sep 1996 | A |
| 5572229 | Fisher | Nov 1996 | A |
| 5572999 | Funda et al. | Nov 1996 | A |
| 5594859 | Palmer et al. | Jan 1997 | A |
| 5636218 | Ishikawa et al. | Jun 1997 | A |
| 5652849 | Conway et al. | Jul 1997 | A |
| 5682199 | Lankford | Oct 1997 | A |
| 5684695 | Bauer | Nov 1997 | A |
| 5701904 | Simmons et al. | Dec 1997 | A |
| 5739657 | Takayama et al. | Apr 1998 | A |
| 5749058 | Hashimoto | May 1998 | A |
| 5749362 | Funda et al. | May 1998 | A |
| 5762458 | Wang et al. | Jun 1998 | A |
| 5767897 | Howell | Jun 1998 | A |
| 5786846 | Hiroaki | Jul 1998 | A |
| 5802494 | Kuno | Sep 1998 | A |
| 5836872 | Kenet et al. | Nov 1998 | A |
| 5867653 | Aras et al. | Feb 1999 | A |
| 5876325 | Mizuno et al. | Mar 1999 | A |
| 5911036 | Wright et al. | Jun 1999 | A |
| 5917958 | Nunally et al. | Jun 1999 | A |
| 5927423 | Wada et al. | Jul 1999 | A |
| 5949758 | Kober | Sep 1999 | A |
| 5954692 | Smith et al. | Sep 1999 | A |
| 5959423 | Nakanishi et al. | Sep 1999 | A |
| 5966130 | Benman, Jr. | Oct 1999 | A |
| 5974446 | Sonnenreich et al. | Oct 1999 | A |
| 6133944 | Braun et al. | Oct 2000 | A |
| 6135228 | Asada et al. | Oct 2000 | A |
| 6148100 | Anderson et al. | Nov 2000 | A |
| 6170929 | Wilson et al. | Jan 2001 | B1 |
| 6175779 | Barrett | Jan 2001 | B1 |
| 6201984 | Funda et al. | Mar 2001 | B1 |
| 6211903 | Bullister | Apr 2001 | B1 |
| 6219587 | Ahlin et al. | Apr 2001 | B1 |
| 6232735 | Baba et al. | May 2001 | B1 |
| 6233504 | Das et al. | May 2001 | B1 |
| 6256556 | Zenke | Jul 2001 | B1 |
| 6259806 | Green | Jul 2001 | B1 |
| 6259956 | Myers et al. | Jul 2001 | B1 |
| 6266162 | Okamura et al. | Jul 2001 | B1 |
| 6266577 | Popp et al. | Jul 2001 | B1 |
| 6289263 | Mukherjee | Sep 2001 | B1 |
| 6292713 | Jouppi et al. | Sep 2001 | B1 |
| 6304050 | Skaar et al. | Oct 2001 | B1 |
| 6321137 | De Smet | Nov 2001 | B1 |
| 6323942 | Bamji | Nov 2001 | B1 |
| 6325756 | Webb et al. | Dec 2001 | B1 |
| 6327516 | Zenke | Dec 2001 | B1 |
| 6330486 | Padula | Dec 2001 | B1 |
| 6330493 | Takahashi et al. | Dec 2001 | B1 |
| 6346950 | Jouppi | Feb 2002 | B1 |
| 6346962 | Goodridge | Feb 2002 | B1 |
| 6369847 | James et al. | Apr 2002 | B1 |
| 6408230 | Wada | Jun 2002 | B2 |
| 6430471 | Kintou et al. | Aug 2002 | B1 |
| 6430475 | Okamoto et al. | Aug 2002 | B2 |
| 6438457 | Yokoo et al. | Aug 2002 | B1 |
| 6452915 | Jorgensen | Sep 2002 | B1 |
| 6463352 | Tadokoro et al. | Oct 2002 | B1 |
| 6463361 | Wang et al. | Oct 2002 | B1 |
| 6466844 | Ikeda et al. | Oct 2002 | B1 |
| 6468265 | Evans et al. | Oct 2002 | B1 |
| 6491701 | Tierney et al. | Dec 2002 | B2 |
| 6496099 | Wang et al. | Dec 2002 | B2 |
| 6496755 | Wallach et al. | Dec 2002 | B2 |
| 6501740 | Sun et al. | Dec 2002 | B1 |
| 6507773 | Parker et al. | Jan 2003 | B2 |
| 6515740 | Bamji et al. | Feb 2003 | B2 |
| 6522906 | Salisbury, Jr. et al. | Feb 2003 | B1 |
| 6523629 | Buttz et al. | Feb 2003 | B1 |
| 6526332 | Sakamoto et al. | Feb 2003 | B2 |
| 6529765 | Franck et al. | Mar 2003 | B1 |
| 6529802 | Kawakita et al. | Mar 2003 | B1 |
| 6532404 | Colens | Mar 2003 | B2 |
| 6535182 | Stanton | Mar 2003 | B2 |
| 6535793 | Allard | Mar 2003 | B2 |
| 6540039 | Yu et al. | Apr 2003 | B1 |
| 6543899 | Covannon et al. | Apr 2003 | B2 |
| 6549215 | Jouppi | Apr 2003 | B2 |
| 6563533 | Colby | May 2003 | B1 |
| 6580246 | Jacobs | Jun 2003 | B2 |
| 6584376 | Van Kommer | Jun 2003 | B1 |
| 6604019 | Ahlin et al. | Aug 2003 | B2 |
| 6604021 | Imai | Aug 2003 | B2 |
| 6611120 | Song et al. | Aug 2003 | B2 |
| 6646677 | Noro et al. | Nov 2003 | B2 |
| 6650748 | Edwards et al. | Nov 2003 | B1 |
| 6684129 | Salisbury, Jr. et al. | Jan 2004 | B2 |
| 6691000 | Nagai et al. | Feb 2004 | B2 |
| 6710797 | McNelley et al. | Mar 2004 | B1 |
| 6728599 | Wang et al. | Apr 2004 | B2 |
| 6764373 | Osawa et al. | Jul 2004 | B1 |
| 6769771 | Trumbull | Aug 2004 | B2 |
| 6781606 | Jouppi | Aug 2004 | B2 |
| 6784916 | Smith | Aug 2004 | B2 |
| 6785589 | Eggenberger et al. | Aug 2004 | B2 |
| 6791550 | Goldhor et al. | Sep 2004 | B2 |
| 6799065 | Niemeyer | Sep 2004 | B1 |
| 6799088 | Wang et al. | Sep 2004 | B2 |
| 6804580 | Stoddard et al. | Oct 2004 | B1 |
| 6804656 | Rosenfeld et al. | Oct 2004 | B1 |
| 6810411 | Coughlin et al. | Oct 2004 | B1 |
| 6836703 | Wang et al. | Dec 2004 | B2 |
| 6839612 | Sanchez et al. | Jan 2005 | B2 |
| 6840904 | Goldberg | Jan 2005 | B2 |
| 6845297 | Allard | Jan 2005 | B2 |
| 6852107 | Wang et al. | Feb 2005 | B2 |
| 6853878 | Hirayama et al. | Feb 2005 | B2 |
| 6853880 | Sakagami et al. | Feb 2005 | B2 |
| 6871117 | Wang et al. | Mar 2005 | B2 |
| 6879879 | Jouppi et al. | Apr 2005 | B2 |
| 6892112 | Wang et al. | May 2005 | B2 |
| 6895305 | Lathan et al. | May 2005 | B2 |
| 6914622 | Smith et al. | Jul 2005 | B1 |
| 6925357 | Wang et al. | Aug 2005 | B2 |
| 6951535 | Ghodoussi et al. | Oct 2005 | B2 |
| 6958706 | Chaco et al. | Oct 2005 | B2 |
| 6965394 | Gutta et al. | Nov 2005 | B2 |
| 6995664 | Darling | Feb 2006 | B1 |
| 7030757 | Matsuhira et al. | Apr 2006 | B2 |
| 7092001 | Schulz | Aug 2006 | B2 |
| 7096090 | Zweig | Aug 2006 | B1 |
| 7115102 | Abbruscato | Oct 2006 | B2 |
| 7115849 | Dowski, Jr. et al. | Oct 2006 | B2 |
| 7117067 | McLurkin et al. | Oct 2006 | B2 |
| 7123285 | Smith et al. | Oct 2006 | B2 |
| 7123974 | Hamilton | Oct 2006 | B1 |
| 7123991 | Graf et al. | Oct 2006 | B2 |
| 7127325 | Nagata et al. | Oct 2006 | B2 |
| 7129970 | James et al. | Oct 2006 | B2 |
| 7133062 | Castles et al. | Nov 2006 | B2 |
| 7139642 | Kamoto | Nov 2006 | B2 |
| 7142945 | Wang et al. | Nov 2006 | B2 |
| 7142947 | Wang et al. | Nov 2006 | B2 |
| 7151982 | Liff et al. | Dec 2006 | B2 |
| 7154197 | Suita | Dec 2006 | B2 |
| 7154526 | Foote et al. | Dec 2006 | B2 |
| 7155306 | Haitin et al. | Dec 2006 | B2 |
| 7156809 | Quy | Jan 2007 | B2 |
| 7158317 | Ben-Eliezer et al. | Jan 2007 | B2 |
| 7158859 | Wang et al. | Jan 2007 | B2 |
| 7158860 | Wang et al. | Jan 2007 | B2 |
| 7161322 | Wang et al. | Jan 2007 | B2 |
| 7162338 | Goncalves et al. | Jan 2007 | B2 |
| 7164969 | Wang et al. | Jan 2007 | B2 |
| 7171286 | Wang et al. | Jan 2007 | B2 |
| 7174238 | Zweig | Feb 2007 | B1 |
| 7184559 | Jouppi | Feb 2007 | B2 |
| 7188000 | Chiappetta et al. | Mar 2007 | B2 |
| 7206627 | Abovitz et al. | Apr 2007 | B2 |
| 7215786 | Nakadai et al. | May 2007 | B2 |
| 7256708 | Rosenfeld et al. | Aug 2007 | B2 |
| 7262573 | Wang et al. | Aug 2007 | B2 |
| 7289883 | Wang et al. | Oct 2007 | B2 |
| 7321807 | Laski | Jan 2008 | B2 |
| 7340077 | Gokturk et al. | Mar 2008 | B2 |
| 7346429 | Goldenberg et al. | Mar 2008 | B2 |
| 7382399 | McCall et al. | Jun 2008 | B1 |
| 7432949 | Remy et al. | Oct 2008 | B2 |
| 7433024 | Garcia et al. | Oct 2008 | B2 |
| 7441953 | Banks | Oct 2008 | B2 |
| 7624166 | Foote et al. | Nov 2009 | B2 |
| 7706917 | Chiappetta et al. | Apr 2010 | B1 |
| 7924323 | Walker et al. | Apr 2011 | B2 |
| 20010002448 | Wilson et al. | May 2001 | A1 |
| 20010010053 | Ben-Shachar et al. | Jul 2001 | A1 |
| 20010034475 | Flach et al. | Oct 2001 | A1 |
| 20010037163 | Allard | Nov 2001 | A1 |
| 20010051881 | Filler | Dec 2001 | A1 |
| 20010054071 | Loeb | Dec 2001 | A1 |
| 20020015296 | Howell et al. | Feb 2002 | A1 |
| 20020027597 | Sachau | Mar 2002 | A1 |
| 20020049517 | Ruffner | Apr 2002 | A1 |
| 20020055917 | Muraca | May 2002 | A1 |
| 20020057279 | Jouppi | May 2002 | A1 |
| 20020058929 | Green | May 2002 | A1 |
| 20020059587 | Cofano et al. | May 2002 | A1 |
| 20020063726 | Jouppi | May 2002 | A1 |
| 20020073429 | Beane et al. | Jun 2002 | A1 |
| 20020082498 | Wendt et al. | Jun 2002 | A1 |
| 20020095238 | Ahlin et al. | Jul 2002 | A1 |
| 20020098879 | Rheey | Jul 2002 | A1 |
| 20020104094 | Alexander et al. | Aug 2002 | A1 |
| 20020111988 | Sato | Aug 2002 | A1 |
| 20020120362 | Lathan et al. | Aug 2002 | A1 |
| 20020130950 | James et al. | Sep 2002 | A1 |
| 20020141595 | Jouppi | Oct 2002 | A1 |
| 20020143923 | Alexander | Oct 2002 | A1 |
| 20020177925 | Onishi et al. | Nov 2002 | A1 |
| 20020183894 | Wang et al. | Dec 2002 | A1 |
| 20020184674 | Xi et al. | Dec 2002 | A1 |
| 20020186243 | Ellis et al. | Dec 2002 | A1 |
| 20030030397 | Simmons | Feb 2003 | A1 |
| 20030048481 | Kobayashi et al. | Mar 2003 | A1 |
| 20030050733 | Wang et al. | Mar 2003 | A1 |
| 20030060808 | Wilk | Mar 2003 | A1 |
| 20030069752 | LeDain et al. | Apr 2003 | A1 |
| 20030100892 | Morley et al. | May 2003 | A1 |
| 20030104806 | Ruef et al. | Jun 2003 | A1 |
| 20030114962 | Niemeyer | Jun 2003 | A1 |
| 20030135203 | Wang et al. | Jul 2003 | A1 |
| 20030144579 | Buss | Jul 2003 | A1 |
| 20030144649 | Ghodoussi et al. | Jul 2003 | A1 |
| 20030151658 | Smith | Aug 2003 | A1 |
| 20030171710 | Bassuk et al. | Sep 2003 | A1 |
| 20030174285 | Trumbull | Sep 2003 | A1 |
| 20030180697 | Kim et al. | Sep 2003 | A1 |
| 20030199000 | Valkirs et al. | Oct 2003 | A1 |
| 20030216834 | Allard | Nov 2003 | A1 |
| 20030220541 | Salisbury et al. | Nov 2003 | A1 |
| 20030231244 | Bonilla et al. | Dec 2003 | A1 |
| 20030232649 | Gizis et al. | Dec 2003 | A1 |
| 20040012362 | Tsurumi | Jan 2004 | A1 |
| 20040013295 | Sabe et al. | Jan 2004 | A1 |
| 20040019406 | Wang et al. | Jan 2004 | A1 |
| 20040024490 | McLurkin et al. | Feb 2004 | A1 |
| 20040041904 | Lapalme et al. | Mar 2004 | A1 |
| 20040065073 | Nash | Apr 2004 | A1 |
| 20040068657 | Alexander et al. | Apr 2004 | A1 |
| 20040078219 | Kaylor et al. | Apr 2004 | A1 |
| 20040080610 | James et al. | Apr 2004 | A1 |
| 20040088077 | Jouppi et al. | May 2004 | A1 |
| 20040093409 | Thompson et al. | May 2004 | A1 |
| 20040098167 | Yi et al. | May 2004 | A1 |
| 20040102167 | Shim et al. | May 2004 | A1 |
| 20040117065 | Wang et al. | Jun 2004 | A1 |
| 20040138547 | Wang et al. | Jul 2004 | A1 |
| 20040143421 | Wang et al. | Jul 2004 | A1 |
| 20040148638 | Weisman et al. | Jul 2004 | A1 |
| 20040153211 | Kamoto et al. | Aug 2004 | A1 |
| 20040157612 | Kim | Aug 2004 | A1 |
| 20040162637 | Wang et al. | Aug 2004 | A1 |
| 20040167666 | Wang et al. | Aug 2004 | A1 |
| 20040167668 | Wang et al. | Aug 2004 | A1 |
| 20040172301 | Mihai et al. | Sep 2004 | A1 |
| 20040174129 | Wang et al. | Sep 2004 | A1 |
| 20040175684 | Kaasa et al. | Sep 2004 | A1 |
| 20040179714 | Jouppi | Sep 2004 | A1 |
| 20040201602 | Mody et al. | Oct 2004 | A1 |
| 20040215490 | Duchon et al. | Oct 2004 | A1 |
| 20040230340 | Fukuchi et al. | Nov 2004 | A1 |
| 20050003330 | Asgarinejad et al. | Jan 2005 | A1 |
| 20050021182 | Wang et al. | Jan 2005 | A1 |
| 20050021183 | Wang et al. | Jan 2005 | A1 |
| 20050021187 | Wang et al. | Jan 2005 | A1 |
| 20050021309 | Alexander et al. | Jan 2005 | A1 |
| 20050024485 | Castles et al. | Feb 2005 | A1 |
| 20050027567 | Taha | Feb 2005 | A1 |
| 20050027794 | Decker | Feb 2005 | A1 |
| 20050028221 | Liu et al. | Feb 2005 | A1 |
| 20050035862 | Wildman et al. | Feb 2005 | A1 |
| 20050038416 | Wang et al. | Feb 2005 | A1 |
| 20050038564 | Burick | Feb 2005 | A1 |
| 20050052527 | Remy et al. | Mar 2005 | A1 |
| 20050065435 | Rauch et al. | Mar 2005 | A1 |
| 20050065659 | Tanaka et al. | Mar 2005 | A1 |
| 20050065813 | Mishelevich et al. | Mar 2005 | A1 |
| 20050068300 | Wang et al. | Mar 2005 | A1 |
| 20050071046 | Miyazaki et al. | Mar 2005 | A1 |
| 20050091684 | Kawabata | Apr 2005 | A1 |
| 20050099493 | Chew | May 2005 | A1 |
| 20050110867 | Schulz | May 2005 | A1 |
| 20050154265 | Miro et al. | Jul 2005 | A1 |
| 20050182322 | Grispo | Aug 2005 | A1 |
| 20050192721 | Jouppi | Sep 2005 | A1 |
| 20050204438 | Wang et al. | Sep 2005 | A1 |
| 20050216126 | Koselka | Sep 2005 | A1 |
| 20050219356 | Smith et al. | Oct 2005 | A1 |
| 20050267826 | Levy et al. | Dec 2005 | A1 |
| 20050283414 | Fernandes et al. | Dec 2005 | A1 |
| 20060007943 | Fellman | Jan 2006 | A1 |
| 20060013263 | Fellman | Jan 2006 | A1 |
| 20060013469 | Wang et al. | Jan 2006 | A1 |
| 20060013488 | Inoue | Jan 2006 | A1 |
| 20060029065 | Fellman | Feb 2006 | A1 |
| 20060047365 | Ghodoussi et al. | Mar 2006 | A1 |
| 20060052676 | Wang et al. | Mar 2006 | A1 |
| 20060052684 | Takahashi et al. | Mar 2006 | A1 |
| 20060064212 | Thorne | Mar 2006 | A1 |
| 20060082642 | Wang et al. | Apr 2006 | A1 |
| 20060087746 | Lipow | Apr 2006 | A1 |
| 20060095170 | Yang et al. | May 2006 | A1 |
| 20060098573 | Beer et al. | May 2006 | A1 |
| 20060103659 | Karandikar et al. | May 2006 | A1 |
| 20060104279 | Fellman et al. | May 2006 | A1 |
| 20060106493 | Niemeyer et al. | May 2006 | A1 |
| 20060122482 | Mariotti et al. | Jun 2006 | A1 |
| 20060142983 | Sorensen et al. | Jun 2006 | A1 |
| 20060161303 | Wang et al. | Jul 2006 | A1 |
| 20060173712 | Joubert | Aug 2006 | A1 |
| 20060178776 | Feingold et al. | Aug 2006 | A1 |
| 20060189393 | Edery | Aug 2006 | A1 |
| 20060195569 | Barker | Aug 2006 | A1 |
| 20060259193 | Wang et al. | Nov 2006 | A1 |
| 20060293788 | Pogodin | Dec 2006 | A1 |
| 20070021871 | Wang et al. | Jan 2007 | A1 |
| 20070046237 | Lakshmanan et al. | Mar 2007 | A1 |
| 20070064092 | Sandbeg et al. | Mar 2007 | A1 |
| 20070078566 | Wang et al. | Apr 2007 | A1 |
| 20070100498 | Matsumoto et al. | May 2007 | A1 |
| 20070114075 | Buehler et al. | May 2007 | A1 |
| 20070117516 | Saidi et al. | May 2007 | A1 |
| 20070120965 | Sandberg et al. | May 2007 | A1 |
| 20070135967 | Jung et al. | Jun 2007 | A1 |
| 20070142964 | Abramson | Jun 2007 | A1 |
| 20070152427 | Olsen | Jul 2007 | A1 |
| 20070192910 | Vu et al. | Aug 2007 | A1 |
| 20070197896 | Moll et al. | Aug 2007 | A1 |
| 20070198128 | Ziegler et al. | Aug 2007 | A1 |
| 20070199108 | Angle et al. | Aug 2007 | A1 |
| 20070250212 | Halloran et al. | Oct 2007 | A1 |
| 20070262884 | Goncalves et al. | Nov 2007 | A1 |
| 20070273751 | Sachau | Nov 2007 | A1 |
| 20070291109 | Wang et al. | Dec 2007 | A1 |
| 20070291128 | Wang | Dec 2007 | A1 |
| 20070293985 | Myeong et al. | Dec 2007 | A1 |
| 20080011904 | Cepollina et al. | Jan 2008 | A1 |
| 20080065268 | Wang et al. | Mar 2008 | A1 |
| 20080082211 | Wang et al. | Apr 2008 | A1 |
| 20080105481 | Hutcheson et al. | May 2008 | A1 |
| 20080106746 | Shpunt et al. | May 2008 | A1 |
| 20080201014 | Sonoura | Aug 2008 | A1 |
| 20080201017 | Wang et al. | Aug 2008 | A1 |
| 20080215987 | Alexander et al. | Sep 2008 | A1 |
| 20080229531 | Takida | Sep 2008 | A1 |
| 20080240502 | Freedman et al. | Oct 2008 | A1 |
| 20080253613 | Jones et al. | Oct 2008 | A1 |
| 20080255703 | Wang et al. | Oct 2008 | A1 |
| 20080281467 | Pinter | Nov 2008 | A1 |
| 20090055023 | Walters | Feb 2009 | A1 |
| 20090096783 | Shpunt et al. | Apr 2009 | A1 |
| 20090105882 | Wang et al. | Apr 2009 | A1 |
| 20090125147 | Wang et al. | May 2009 | A1 |
| 20090164045 | Deguire et al. | Jun 2009 | A1 |
| 20090177323 | Ziegler | Jul 2009 | A1 |
| 20090185274 | Shpunt | Jul 2009 | A1 |
| 20090226113 | Matsumoto et al. | Sep 2009 | A1 |
| 20090240371 | Wang et al. | Sep 2009 | A1 |
| 20090259339 | Wright et al. | Oct 2009 | A1 |
| 20100010672 | Wang et al. | Jan 2010 | A1 |
| 20100010673 | Wang et al. | Jan 2010 | A1 |
| 20100019715 | Roe et al. | Jan 2010 | A1 |
| 20100020078 | Shpunt | Jan 2010 | A1 |
| 20100034457 | Berliner et al. | Feb 2010 | A1 |
| 20100066587 | Yamauchi et al. | Mar 2010 | A1 |
| 20100070079 | Mangaser et al. | Mar 2010 | A1 |
| 20100073490 | Wang et al. | Mar 2010 | A1 |
| 20100115418 | Wang et al. | May 2010 | A1 |
| 20100118123 | Freedman et al. | May 2010 | A1 |
| 20100131103 | Herzog et al. | May 2010 | A1 |
| 20100185362 | Vialatte et al. | Jul 2010 | A1 |
| 20100191375 | Wright et al. | Jul 2010 | A1 |
| 20100268383 | Wang et al. | Oct 2010 | A1 |
| 20110035054 | Gal | Feb 2011 | A1 |
| 20110037866 | Iwamoto | Feb 2011 | A1 |
| 20110050841 | Wang et al. | Mar 2011 | A1 |
| 20110071702 | Wang et al. | Mar 2011 | A1 |
| 20110187875 | Sanchez et al. | Aug 2011 | A1 |
| 20110190930 | Hanrahan et al. | Aug 2011 | A1 |
| 20110218674 | Stuart et al. | Sep 2011 | A1 |
| 20110288682 | Pinter | Nov 2011 | A1 |
| 20110288684 | Farlow et al. | Nov 2011 | A1 |
| 20110292193 | Wang et al. | Dec 2011 | A1 |
| 20110301759 | Wang et al. | Dec 2011 | A1 |
| 20120264414 | Fung | Oct 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 2289697 | Nov 1998 | CA |
| 101866396 | Oct 2010 | CN |
| 101978365 | Feb 2011 | CN |
| 101106939 | Nov 2011 | CN |
| 0981905 | Jan 2002 | EP |
| 1262142 | Dec 2002 | EP |
| 1536660 | Jun 2005 | EP |
| 1806210 | Jul 2007 | EP |
| 1536660 | Apr 2008 | EP |
| 2263158 | Dec 2010 | EP |
| 2300930 | Mar 2011 | EP |
| 2431261 | Apr 2007 | GB |
| 07213753 | Aug 1995 | JP |
| 07248823 | Sep 1995 | JP |
| 08084328 | Mar 1996 | JP |
| 07257422 | Dec 1996 | JP |
| 08320727 | Dec 1996 | JP |
| 09267276 | Oct 1997 | JP |
| 10079097 | Mar 1998 | JP |
| 10143243 | May 1998 | JP |
| 10288689 | Oct 1998 | JP |
| 00032319 | Jan 2000 | JP |
| 00049800 | Feb 2000 | JP |
| 00079587 | Mar 2000 | JP |
| 00196876 | Jul 2000 | JP |
| 2000289985 | Oct 2000 | JP |
| 00188124 | Apr 2001 | JP |
| 01125641 | May 2001 | JP |
| 01147718 | May 2001 | JP |
| 01179663 | Jul 2001 | JP |
| 01198865 | Jul 2001 | JP |
| 01198868 | Jul 2001 | JP |
| 01199356 | Jul 2001 | JP |
| 02000574 | Jan 2002 | JP |
| 02035423 | Feb 2002 | JP |
| 02046088 | Feb 2002 | JP |
| 200285305 | Mar 2002 | JP |
| 02305743 | Oct 2002 | JP |
| 02355779 | Dec 2002 | JP |
| 04261941 | Sep 2004 | JP |
| 04524824 | Sep 2004 | JP |
| 05028066 | Feb 2005 | JP |
| 2008004078 | Jan 2008 | JP |
| 2009123061 | Jun 2009 | JP |
| 2009217363 | Sep 2009 | JP |
| 10064154 | Mar 2010 | JP |
| 10532109 | Sep 2010 | JP |
| 10246954 | Nov 2010 | JP |
| 060037979 | May 2006 | KR |
| 100019479 | Feb 2010 | KR |
| 100139037 | Dec 2010 | KR |
| WO-9306690 | Apr 1993 | WO |
| WO-9851078 | Nov 1998 | WO |
| WO-9967067 | Dec 1999 | WO |
| WO-0033726 | Jun 2000 | WO |
| WO-03077745 | Sep 2003 | WO |
| WO-03102706 | Dec 2003 | WO |
| WO-2004075456 | Sep 2004 | WO |
| WO-2006012797 | Feb 2006 | WO |
| WO-2006078611 | Jul 2006 | WO |
| WO-2007041038 | Apr 2007 | WO |
| WO-2007041295 | Apr 2007 | WO |
| WO-2008083489 | Jul 2008 | WO |
| WO-2008100272 | Aug 2008 | WO |
| WO-2008105634 | Sep 2008 | WO |
| WO-2008100272 | Oct 2008 | WO |
| WO-2009117274 | Sep 2009 | WO |
| WO-2009128997 | Oct 2009 | WO |
| WO-2009145958 | Dec 2009 | WO |
| WO-2010006205 | Jan 2010 | WO |
| WO-2010006211 | Jan 2010 | WO |
| WO-2010033666 | Mar 2010 | WO |
| WO-2010047881 | Apr 2010 | WO |
| WO-2010062798 | Jun 2010 | WO |
| WO-2010065257 | Jun 2010 | WO |
| WO-2010120407 | Oct 2010 | WO |
| WO-2010120707 | Oct 2010 | WO |
| WO-2011028589 | Mar 2011 | WO |
| WO-2011028589 | Apr 2011 | WO |
| WO-2011097130 | Aug 2011 | WO |
| WO-2011097132 | Aug 2011 | WO |
| WO-2011109336 | Sep 2011 | WO |
| WO-2011146254 | Nov 2011 | WO |
| WO-2011146259 | Nov 2011 | WO |
| WO-2011097132 | Dec 2011 | WO |
| WO-2011149902 | Dec 2011 | WO |
| Entry |
|---|
| Se, S.; Lowe, David G.; Little, J. (2001). “Vision-based mobile robot localization and mapping using scale-invariant features”. Proceedings of the IEEE International Conference on Robotics and Automation (ICRA). 2. pp. 2051. |
| Rothganger, F; S. Lazebnik, C. Schmid, and J. Ponce: 2004. 3D Object Modeling and Recognition Using Local Affine-Invariant Image Descriptors and Multi-View Spatial Constraints, ICCV. |
| Laptev, Ivan and Lindeberg, Tony (2004). “Local descriptors for spatio-temporal recognition”. ECCV'04 Workshop on Spatial Coherence for Visual Motion Analysis, Springer Lecture Notes in Computer Science, vol. 3667. pp. 91-103. |
| Ivan Laptev, Barbara Caputo, Christian Schuldt and Tony Lindeberg (2007). “Local velocity-adapted motion events for spatio-temporal recognition”. Computer Vision and Image Understanding 108: 207-229; Scovanner, Paul. |
| Ali, S; Shah, M (2007). “A 3-dimensional sift descriptor and its application to action recognition”. Proceedings of the 15th International Conference on Multimedia. pp. 357-360. |
| Iryna Gordon and David G. Lowe, “What and where: 3D object recognition with accurate pose,” Toward Category-Level Object Recognition, (Springer-Verlag, 2006), pp. 67-82. |
| Niebles, J. C. Wang, H. and Li, Fei-Fei (2006). “Unsupervised Learning of Human Action Categories Using Spatial-Temporal Words”. Proceedings of the British Machine Vision Conference (BMVC). Edinburgh. |
| Binotto A P D et al: “Real-time taks reconfiguration support applied to an UAV-based surveillance system”, Computer Science and Information Technology, 2008. IMCSIT 2008. International Multiconference on, IEEE, Piscataway, NJ, USA, Oct. 20, 2008, pp. 581-588, XP031406238, ISBN: 978-83-60810-14-9. |
| International Search Report for application No. PCT/US2011/059863 dated Nov. 22, 2012. |
| International Search Report for Application No. PCT/US2011/035488 dated May 13, 2013. |
| Muller A., et al. “A model-based object following system”, Intelligent Vehicles Symposium, 2009 IEEE, Piscataway, NJ, USA, Jun. 3, 2009. |
| Ho Seok Ahn, et. al. “PDA-based mobile robot system with remote monitoring for home environment”, IEEE Transactions on Consumer Electronics, IEEE Service Center, New York, NY, USA, vol. 55, No. 3, 1, Aug. 1, 2009. |
| Kathryn A Daltorio, et al. “An obstacle-edging reflex for an autonomous lawnmower”, Position Location and Navigation Symposium (PLANS), 2010 IEEE/ION, IEEE, Piscataway, NJ, USA, May 4, 2010. |
| International Search Report for Application No. PCT/US2011/035476 Dated May 17, 2013. |
| Jong-Hwan Kim et al., “Ubiquitous Robot: A New Paradigm for Integrated Sciences”, 2007 IEEE International Conference on Robotics and Automation—Apr. 10-14, 2007—Roma, Italy, IEEE, Piscataway, NJ, USA, Apr. 10, 2007. |
| De F O Araujo T et al, “MaeRobot: An Open Source Test Platform for Prototyping Robots”, Robotic Symposium, 2008, LARS '08. IEEE Latin American, IEEE, Piscataway, NJ, USA, Oct. 29, 2008. |
| Li Xiaopen et al., “Research an open control architecture of autonomous mobile robot with multi-layer and modularization”, Infomatics in Control, Automation and Robotics (Car), 2010 2nd International Asia Conference On, IEEE, Piscataway, NJ, USA, Mar. 6, 2010. |
| Hu Guanshan, “Neutral Networks Based on Information Fusion Using for Avoiding Obstacle Robot”, Information Engineering, 2009. ICIE '09. Wase International Conference On, IEEE, Piscataway, NJ, USA, Jul. 10, 2009. |
| Freire E O et al., “Prototyping a wheeled mobile robot embedding multiple sensors and agent-based control system”, Proc. 43rd IEEE Midwest Symposium on Circuits and Systems, Aug. 8, 2000. |
| Sung-Min Han et al., “Mobile robot navigation by circular path planning algorithm using camera and ultrasonic sensor”, Industrial Electronics, 2009. ISIE 2009. IEEE International Symposium On, IEEE, Piscataway, NJ, USA, Jul. 5, 2009. |
| Ruifeng Li et al., “The development of a general type of security robot”, Robotics and Biometrics, 2007. ROBIO 2007. IEEE International Conference ON, IEEE, Piscataway, NJ, USA, Dec. 15, 2007. |
| Pil Gyeom Kim el al., “Obstacle Avoidance of a Mobile Robot Using Vision System and Ultrasonic Sensor”, Aug. 21, 2007, Advanced Intelligent Computing Theories and Applications, With Aspects of Theoretical and Methodological Issues. |
| International Search Report for Application No. PCT/US2011/059980 dated May 14, 2013. |
| International Search Report for Application No. PCT/US2011/060935 Dated May 27, 2013. |
| Rajesh, Arumugam et al., “DAvinCi: A cloud computing framework fo service robots”, 2010 IEEE International Conference on Robotics and Automation: ICRA 2010; Anchorage, Alaska, USA, May 3-8, 2010, IEEE, Piscataway, NJ, USA, May 3, 2010. |
| Bistry, H., et al. “A cloud computing approach to complex robot vision tasks using smart camera systems”, Intelligent Robots and Systems (IROS), 2010 IEEE/RSJ International Conference On, Piscataway, NJ, USA, vol. 1-24, Oct. 18, 2010. |
| Nimmagadda, Y., et al. “Real-time moving object recognition and tracking using computation offloading”, Intelligent Robots and Systems (IROS), 2010 IEEE/RSJ International Conference On, IEEE, Piscataway, NJ, USA, Oct. 18, 2010. |
| International Search Report for Application No. PCT/US2011/059910 Dated May 29, 2013. |
| Ferriere L. et. al., “Design of omnimobile robot wheels”, Robotics and Automation, 1996. Proceedings., 1996 IEEE International Conference on Minneapolis, MN, Apr. 22028, 1996, New York, NY, IEEE, Apr. 22, 1996. |
| Kanda A. et. al., “Environment Recognition System Based on Multiple Classification Analyses for Mobile Robots”, Journal of Bionic Engineering, Sep. 1, 2008. |
| Freire E. O., et al. “Prototyping a wheeled mobile robot embedding multiple sensors and agentbased control system”, PROC. 43rd IEEE Midwest Symp. on Circuits and Systems, vol. 2, Aug. 8, 2000, pp. 926-929. |
| International Search Report for Application No. PCT/US2013/028208 dated Jul. 9, 2013. |
| Japanese Office Action for Application No. 2013-547475 dated Dec. 16, 2013. |
| Canadian Office Action for related Application No. 2,800,372 dated Apr. 2, 2014. |
| Australian examination report for related Application No. 2011256720 dated Mar. 27, 2014. |
| Adams, Chris, “Mobile Robotics Research Group”, Mobile Robotics Research Group, Edinburgh University, http://www.dai.ed.ac.uk/groups/mrg/MRG.html, Internet, Edinburgh. duplicate of 575084, 2000, pp. 1-2. |
| Ando, et al., “A Multimedia Self-service Terminal with Conferencing Functions”, IEEE, Jul. 5-7, 1995, pp. 357-362. |
| Android Amusement Corp., “What Marketing Secret . . . Renting Robots from Android Amusement Corp!”, (Advertisement), 1982. |
| Applebome, “Planning Domesticated Robots for Tomorrow's Household”, New York Times, http://www.theoldrobots.com/images17/dc17.JPG, Mar. 4, 1982, pp. 21, 23. |
| Baltus, et al., “Towards Personal Service Robots for the Elderly, Proceedings for the Elderly Workshop on Interactive Robots and Entertainment”, Computer Science and Robotics, 2000. |
| Bar-Cohen, et al., “Virtual reality robotic telesurgery simulations using MEMICA haptic system”, Internet, Mar. 5, 2001, pp. 1-7. |
| Bartholomew, “An Apothecary's Pharmacy”, http://classes.bnf.fr/ema/grands/034.htm, pp. 1230-1240. |
| Bauer, Jeffrey C. et al., “Service Robots in Health Care: The Evolution of Mechanical Solutions to Human Resource Problems”, Jun. 2003. |
| Bauer, John et al., “Remote telesurgical mentoring: feasibility and efficacy”, IEEE, 2000, pp. 1-9. |
| Bischoff, “Design Concept and Realization of the Humanoid Service Robot HERMES”, Field and Service Robotics, Springer, London, 1998, pp. 485-492. |
| Blackwell, Gerry, “Video: A Wireless LAN Killer App?”, Internet, Apr. 16, 2002, pp. 1-3. |
| Breslow, Michael J. et al., “Effect of a multiple-site intensive care unit telemedicine program on clinical and economic outcome an alternative paradigm for intensivist staffing”, Critical Care Med; vol. 32 No. 1, Jan. 2004, pp. 31-38. |
| Brooks, Rodney, “Remote Presence”, Abstracts from Flesh & Machines, How Robots Will Change Us, Feb. 2002, pp. 131-147. |
| Candelas, Herias et al., “Flexible virtual and remote laboratory for teaching Robotics”, FORMATEX 2006; Proc. Advance in Control Education Madrid, Spain, Jun. 2006, pp. 21-23. |
| Celt, et al., “The EICU: It's not just telemedicine”, Critical Care Medicine vol. 29, No. 8 (Supplement), Aug. 2001. |
| Cheetham, Anastasia et al., “Interface Development for a Child's Video Conferencing Robot”, 2000, pp. 1-4. |
| Cleary, et al., “State of the art in surgical robotics: Clinical applications and technology challenges”, Internet, Feb. 24, 2002, pp. 1-26. |
| CNN, “Floating ‘droids’ to roam space corridors of the future”, Internet, Jan. 12, 2000, pp. 1-4. |
| cnn.com/technology, “Paging R.Robot: Machine helps doctors with patients”, Internet, Sep. 30, 2003, 1-3. |
| Crowley, Susan L., “Hello to Our Future”, AARP Bulletin, http://www.cs.cmu.ed/-nursebot/web/press/aarp 99—14/millennium.html, Jan. 2000. |
| Dalton, “Techniques for Web Telerobotics”, PhD Thesis, University of Western Australia, http://telerobot.mech.uwa.edu.au/information.html, http://catalogue.library.uwa.edu.au/search, 2001, 27-62 pp. 149-191. |
| Davies, “Robotics in Minimally Invasive Surgery”, Internet, 1995, pp. 5/1-5/2. |
| Digiorgio, James, “Is Your Emergency Department of the 'Leading Edge?”, Internet, 2005, pp. 1-4. |
| Discovery Channel Canada, “Inventing the Future: 2000 Years of Discovery”, (Video Transcript), Jan. 2, 2000. |
| Elhajj, et al., “Supermedia in Internet-based telerobotic operations”, Internet, 2001, pp. 1-14. |
| Elhajj, et al., “Synchronization and Control of Supermedia Transmission Via the Internet”, Proceedings of 2001 International Symposium on Intelligent Multimedia Video and Speech Processing., Hong Kong, May 2-4, 2001. |
| Ellison, et al., “Telerounding and Patient Satisfaction Following Surgery”, pp. 523-530. |
| Fels, “Developing a Video-Mediated Communication System for Hospitalized Children”, Telemedicine Journal, vol. 5,vol. 5, No. 2, 1999. |
| Fetterman, “Videoconferencing over the Internet”, Internet, 2001, pp. 1-8. |
| Fiorini, P., et al, “Health Care Robotics: A Progress Report”, IEEE International Conference on Robotics and Automation, Apr. 1997, pp. 1271-1276. |
| Ghiasi, et al., “A Generic Web-based Teleoperations Architecture: Details and Experience”, SPIE Conference on Telemanipulator and Telepresence Technologies VI, Sep. 1999. |
| Goldberg, et al., “Collaborative Teleoperation via the Internet”, IEEE International Conference on Robotics and Automation, San Francisco, California, Apr. 2000. |
| Goldberg, “Desktop Teleoperation via the World Wide Web, Proceedings of the IEEE International Conference on Robotics and Automation”, htto://citeseer.ist.osu.edu/cache/oaoers/cs/5/fto:zSzzSzusc.eduzSzoubzSziriszS zraiders.odf/aol, 1995, pp. 654-659. |
| Goldberg, “More Online Robots, Robots that Manipulate”, Internet, Updated Aug. 2001, http://ford.ieor.berkeley.edu/ir/robots—a2.html, Aug. 2001. |
| Goldenberg, et al., “Telemedicine in Otolaryngology”, American Journal of Otolaryngology vol. 23, No. 1, 2002, pp. 35-43. |
| Goldman, Lea, “Machine Dreams”, Entrepreneurs, Forbes, May 27, 2002. |
| Gump, Michael D., “Robot Technology Improves VA Pharmacies”, Internet, 2001, pp. 1-3. |
| Hameed, Mohammed et al., “A Review of Telemedicine”, Journal of Telemedicine and Telecare., vol. 5, Supplement 1, 1999, pp. S1:103-S1:106. |
| Han, et al., “Construction of an Omnidirectional Mobile Robot Platform Based on Active Dual-Wheel Caster Mechanisms and Development of a Control Simulator”, Kluwer Acedemic Publishers, vol. 29, Nov. 2000, pp. 257-275. |
| Handley, et al., “RFC 2327—SDP:Session Description Protocol”, http://www.faqs.org/rfcs/rfc2327.html, Apr. 1998. |
| Hanebeck, et al., “ROMAN: A mobile Robotic Assistant for Indoor Service Applications”, Proceedings of the 1997 IEEE/RSJ International Conference on Intelligent Robots and Systems, 1997. |
| Harmo, et al., “Moving Eye-Interactive Telepresence Over Internet With a Ball Shaped Mobile Robot”, 2000. |
| Haule, et al., “Control Scheme for Delayed Teleoperation Tasks”, Proceedings of the Pacific Rim Conference on Communications, Computer and Signal Processing, May 17, 1995. |
| Hees, William P., “Communications Design for a Remote Presence Robot”, Jan. 14, 2002. |
| Holmberg, “Development of a Holonomic Mobile Robot for Mobile Manipulation Tasks”, International Conference on Field and Service Robotics, Pittsburgh, PA, Aug. 1999. |
| Int'l Communication Union, “ITU-T H.323 Packet-based multimedia communications”, http://www.itu.int/rec/T-REC-H.323-199802-S/en, Feb. 1998. |
| Ishiguro, “Integrating a Perceptual Information Infrastructure with Robotic Avatars: A Framework for Tele-Existence”, Proceeding of IEEE Conference on Intelligent Robots and Systems, 1999, pp. 1032-1038. |
| Ishihara, et al., “Intelligent Microrobot DDS (Drug Delivery System) Measured and Controlled by Ultrasonics”, IEEE/RSJ, vol. 2, Nov. 3-5, 1991, pp. 1145-115. |
| Ivanova, Natali, “Masters thesis: Internet Based Interface for Control of a Mobile Robot”, Department of Numerical Analysis and Computer Science, 2003, 59 pages. |
| Jenkins, et al., “Telehealth Advancing Nursing Practice”, Nursing Outlook, vol. 49, No. 2, Mar./Apr. 2001. |
| Johanson, “Supporting video-mediated communication over the Internet”, Chalmers University of Technology,Dept of Computer Engineering, Gothenburg, Sweden, 2003. |
| Jouppi, et al., “Mutually-Immersive Audio Telepresence”, Audio Engineering Society Convention Paper presented at 113th Convention, Oct. 2002. |
| Jouppi, Norman et al., “First Steps Towards Mutually-Immersive Mobile Telepresence”, CSCW, 02, New Orleans LA, Nov. 16-20, 2002. |
| Kanehiro, Fumio et al., “Virtual Humanoid Robot Platform to Develop Controllers of Real Humanoid Robots without Porting”, IEEE, 2001, pp. 3217-3276. |
| Kaplan, A. E. et al., “An Internet Accessible Telepresence”, {aek keshav nls jhy}@research.att.com, At&T Bell Laboratories, Murray Hill, N.J., pp. 1-7. |
| Keller, et al., “Raven Interface Project”, http://upclose.lrdc.pitt.edu/people/louw—assets/Raven—Slides.pps, Fall 2001. |
| Khatib, “Robots in Human Environments”, Proc. International Conference on Control, Automation, Robotics, and Vision ICRACV2000, Singapore, Dec. 2000, pp. 454-457. |
| Kuzuoka, et al., “Can the GestureCam Be a Surrogate?”, Proceedings of the Fourth European Conference on Computer-Supported Cooperative Work, Sep. 10-14, pp. 181-196. |
| Lane, “Automated Aides”, Newsday, http://www.cs.cum.edu/nursebot/web/press/nd4380.htm, Oct. 17, 2000. |
| Lee, et al., “A novel method of surgical instruction: International telementoring”, Internet, 1998, pp. 1-4. |
| Lim, Hun-Ok et al., “Control to Realize Human-like Walking of a Biped Humanoid Robot”, IEEE, 2000, pp. 3271-3276. |
| Linebarger, John M. et al., “Concurrency Control Mechanisms for Closely Coupled Collaboration in Multithreaded Virtual Environments”, Presence, Special Issue on Advances in Collaborative VEs, 2004. |
| Loeb, et al., “Virtual Visit: Improving Communication for Those Who Need It Most”, Stud Health Technol Inform.; 94: 2003 pp. 302-308. |
| Long, “HelpMate Robotics, Inc. (Formerly Transitions Research Corporation) Robot Navigation Technology”, NIST Special Publication, http://www.atp.nist.gov/eao/sp950-1/helpmate.htm, Mar. 1999, pp. 950-951. |
| Luna, Nancy, “Robot a new face on geriatric care”, OC Register, Aug. 6, 2003. |
| Mack, “Minimally invasive and robotic surgery”, Internet IEEE, 2001, pp. 568-572. |
| Mair, “Telepresence—The Technology. And Its Economic and Social Implications”, IEEE Technology and Society, 1997. |
| Martin, Anya, “Days Ahead”, Assisted Living Today, vol. 9, Nov./Dec. 2002, pp. 19-22. |
| McCardle, et al., “The challenge of utilizing new technology in design education”, Internet, 2000, pp. 122-127. |
| Meng, et al., “E-Service Robot in Home Healthcare”, Proceedings of the 2000 IEEE/RSJ, International Conference on Intelligent Robots and Systems, 2000, pp. 832-837. |
| Michaud, “Introducing Nursebot”, The Boston Globe, http://www.cs.cmu.edu/nursebot/web/press/globe 3 01/index.html, Sep. 11, 2001, pp. 1-5. |
| Montemerlo, “Telepresence: Experiments in Next Generation Internet”, CMU Robotics Institute, http://www.ri.cmu.edu/creative/archives.htm (Video/Transcript), Oct. 20, 1998. |
| Murphy, “Introduction to A1 Robotics”, A Bradford Book, 2000, p. 487. |
| Nakajima, et al., “A Multimedia Teleteaching System using an Electronic Whiteboard for Two Way Communication of Motion Videos and Chalkboards”, IEEE, 1993, pp. 436-441. |
| Nomadic Technologies Inc., “Nomad XR4000 Hardware Manual”, Release 1.0, Mar. 1999. |
| Nt'l Energy Res Sci Comp Ctr, “Berkeley Lab's Rage Telepresence Robot Captures R&D100 Award”, http://www.nersc.gov/news/newsroom/RAGE070202.php, Jul. 2, 2002. |
| Ogata, et al., “Development of Emotional Communication Robot: WAMOEBA-2r—Experimental evaluation.”, IEEE, 2000, pp. 175-180. |
| Ogata, et al., “Emotional Communication Robot: WAMOEBA-2R—Emotion Model and Evaluation Experiments”, Internet, 1999, pp. 1-16. |
| Oh, et al., “Autonomous Battery Recharging for Indoor Mobile Robots”, Proceedings of Australian Conference on Robotics and Automation, http://users.rsise.anu.edu.au/rsl/rsl—papers/ACRA2000/Auto—Recharge—Paper. pdf, 2000. |
| Ojha, A. K., “An application of Virtual Reality in Rehabilitation”, IEEE, Apr. 10-13, 1994, pp. 4-6. |
| Paulos, et al., “A World Wide Web Telerobotic Remote Environment Browser”, http://vive.cs.berkeley.edu/capek, 1995. |
| Paulos, “Designing Personal Tele-embodiment”, IEEE International Conference on Robotics and Automation http://www.prop.org/papers/icra98.pdf, 1998. |
| Paulos, “PRoP: Personal Roving Presence”, ACM:CHI Proceedings of CHI '98, http://www.prop.org/papers/chi98.pdf, 1998, p. 6. |
| Paulos, et al., “Ubiquitous Tele-embodiment: Applications and Implications”, International Journal of Human Computer Studies, vol. 46, No. 6, Jun. 1997, pp. 861-877. |
| Paulos, “Video of PRoP 2 at Richmond Field Station”, www.prop.org Printout of Home Page of Website and two-page Transcript of the audio portion of said PRoP Video, May 2001. |
| Paulos, Eric J., “Personal Tele-Embodiment”, UC Berkeley, Fall 2001. |
| Pin, et al., “A New Family of Omnidirectional and Holonomic Wheeled Platforms for Mobile Robots”, IEEE, vol. 10, No. 4, Aug. 1994. |
| Rovetta, et al., “A New Telerobotic Application: Remote Laparoscopic Surgery Using Satellites and and optical fiber Networks for Data Exchange”, International Journal of Robotics Research, Jun. 1, 1996, pp. 267-279. |
| Roy, et al., “Towards Personal Service Robots for the Elderly”, Internet, Mar. 7, 2002, 7 pgs. |
| Salemi, et al., “MILO: Personal robot platform”, Internet, 2005, pp. 1-6. |
| Sandt, Frederic et al., “Perceptions for a Transport Robot in Public Environments”, IROS, 1997. |
| Schaeffer, “Care-O-bot: A System for Assisting Elderly or Disabled Persons in Home Environments”, Proceedings of AAATE-99, http://morpha.de/download/publications/IPA, 1999. |
| Schulz, “Web Interfaces for Mobile Robots in Public Places”, Robotics & Automation Magazine, IEEE, vol. 7, Issue 1, Mar. 2000. |
| Shimoga, et al., “Touch and force reflection for telepresence surgery”, IEEE, 1994, pp. 1049-1050. |
| Siegwart, “Interacting Mobile Robots on the Web”, Proceedings of the 1999 IEEE International Conference on Robotics and Automation, May 1999. |
| Simmons, “Xavier: An Autonomous Mobile Robot on the Web”, IEEE Robotics and Automation Magazine, 1999, pp. 43-48. |
| Spawar Systems Center, “Robert”, San Diego, CA, http://www.nosc.mil/robots/land/robart/robart.html, 1998, pp. 1-8. |
| Stephenson, Gary, “Dr. Robot Tested at Hopkins”, Internet, Aug. 5, 2003, pp. 1-2. |
| Stoianovici, et al., “Robotic Tools for Minimally Invasive Urologic Surgery”, Internet, Dec. 2002, pp. 1-17. |
| Suplee, “Mastering the Robot”, The Washington Post, http://www.cs.cmu.edu-nursebotlweb/press/wash/index.html, Sep. 17, 2000, p. A01. |
| Tahboub, Karim A. et al., “Dynamics Analysis and Control of a Holonomic Vehicle With Continously Variable Transmission”, Journal of Dynamic Systems, Measurement and Control ASME vol. 124, Mar. 2002, pp. 118-126. |
| Tendick, et al., “Human-Machine Interfaces for Minimally Invasive Surgery”, IEEE, 1997, pp. 2771-2776. |
| Thrun, et al., “Probabilistic Algorithms and the Interactive Museum Tour-Guide Robot Minerva”, Internet, 2000, pp. 1-35. |
| Tzafestas, et al., “VR-based Teleoperation of a Mobile Robotic Assistant: Progress Report”, Internet, Nov. 2000, pp. 1-23. |
| Urquhart, Kim , “InTouch's robotic Companion ‘beams up’ healthcare experts”, Medical Device Daily, vol. 7, No. 39, Feb. 27, 2003, p. 1,4. |
| Weiss, et al., “Telework and video-mediated communication: Importance of real-time, interactive communication for workers with disabilities”, California State University Northridge http://www.csun.edu/cod/conf/1999/proceedings/session0238.html, pp. 1-4. |
| West, et al., “Design of Ball Wheel Mechanisms for Omnidirectional Vehicles with Full Mobility and Invariant Kinematics”, Journal of Mechanical Design , vol. 119, Jun. 1997, pp. 153-161. |
| Yamasaki, et al., “Applying Personal Robots and Active Interface to Video Conference Systems”, Internet, 1995, pp. 243-248. |
| Yamauchi, “PackBot: A Versatile Platform for Military Robotics”, Internet, 2004, pp. 1-10. |
| Yong, et al., “Robot task execution with telepresence using virtual reality technology”, Internet, 1998, pp. 1-8. |
| Zamrazil, Kristie, “Telemedicine in Texas: Public Policy Concerns”, House Research Organization Focus Report, Texas House of Representatives, http://www.hro.house.state.tx.us/focus/telemed.pdf, May 5, 2000, pp. 76-22. |
| Zipperer, Lorri, “Robotic dispensing system”, 1999, pp. 1-2. |
| Zorn, Benjamin G., “Ubiquitous Telepresence”, http://www.cs.colorado.edu/-zorn/utlvision/vision.html, May 5, 1996. |
| Moravec, Hans. “Robots, Re-Evolving Mind”, Carnegie Mellon University Robotics Institute, Dec. 2000. |
| U.S. Office Action for U.S. Appl. No. 13/032,312, filed Feb. 22, 2011. |
| Office Action for U.S. Appl. No. 13/032,370 dated Feb. 13, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20150073598 A1 | Mar 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61429863 | Jan 2011 | US | |
| 61428717 | Dec 2010 | US | |
| 61428734 | Dec 2010 | US | |
| 61428759 | Dec 2010 | US | |
| 61356910 | Jun 2010 | US | |
| 61346612 | May 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13032370 | Feb 2011 | US |
| Child | 14546192 | US |
