This invention relates to robots, and more particularly to autonomous coverage robots.
Autonomous robots are robots which can perform desired tasks in unstructured environments without continuous human guidance. Many kinds of robots are autonomous to some degree. Different robots can be autonomous in different ways. An autonomous coverage robot traverses a work surface without continuous human guidance to perform one or more tasks. In the field of home, office and/or consumer-oriented robotics, mobile robots that perform household functions such as vacuum cleaning, floor washing, patrolling, lawn cutting and other such tasks have been widely adopted.
An autonomous coverage robot will encounter many obstacles while operating. In order to continue operating, the robot will need to continually avoid obstacles, and in cases where trapped by fabric, string, or other entangling soft media, free itself.
In one aspect, an autonomous coverage robot includes a chassis, a drive system mounted on the chassis and configured to maneuver the robot, an edge cleaning head carried by the chassis, and a controller carried by the chassis. The edge cleaning head is driven by an edge cleaning head motor and may rotate about a non-horizontal axis. The edge cleaning head extends beyond a lateral extent of the chassis to engage a floor surface while the robot is maneuvered across the floor. The edge cleaning head may be disposed on or near a peripheral edge of the robot. A brush control process, independent of drive processes, on a controller that controls robot operation is configured to monitor motor current associated with the edge cleaning head. The brush control process on the controller is also configured to reverse bias the edge cleaning head motor in a direction opposite to the previous cleaning direction after detecting a spike (e.g., transient or rapid increase in motor current) or in general an elevated motor current motor (to substantially neutrally rotate and/or be driven to rotate at the same speed as a an unwinding cord, string, or other tangled medium), while continuing to maneuver the robot across the floor performing uninterrupted coverage or cleaning of the floor or other motion behaviors. In one implementation, the brush control process on the controller, following an elevated edge cleaning head motor current, reverse biases the edge cleaning head motor (to substantially neutrally rotate and/or be driven to rotate at the same speed as a an unwinding cord, string, or other tangled medium) and subsequently or concurrently passes a signal to a drive motor control process, directly or indirectly via a supervising process, so that the unwinding may occur at the same time that the robot drives substantially backwards, alters a drive direction, and moves the robot forward.
In one implementation, the edge cleaning head includes a brush with bristles that extend beyond a peripheral edge of the chassis. In one example, the edge cleaning head includes at least one brush element having first and second ends, the bush element defining an axis of rotation about the first end normal to the work surface. The edge cleaning head may rotate about a substantially vertical axis. In one instance, the edge cleaning head includes three brush elements, where each brush element forms an angle with an adjacent brush element of about 120 degrees. In another instance, the edge cleaning head comprises six brush elements, where each brush element forms an angle with an adjacent brush element of about 60 degrees.
In another implementation, the edge cleaning head comprises a rotatable squeegee that extends beyond a peripheral edge of the chassis. The rotatable squeegee may be used for wet cleaning, surface treatments, etc.
In yet another implementation, the edge cleaning head includes a plurality of absorbent fibers that extend beyond a peripheral edge of the chassis upon rotation of the cleaning head. The plurality of absorbent fibers may be used like a mop to clean up spills, clean floors, apply surface treatments, etc.
The robot may include multiple cleaning heads (e.g., two or three) carried by the chassis. In one example, the robot further includes a main cleaning head carried by the chassis, a cleaning head extending across a swath covered by the robot, which forms the main work width of the robot, and which may be driven to rotate about a horizontal axis to engage a floor surface while the robot is maneuvered across the floor. The main cleaning head may include a cylindrical body defining a longitudinal axis of rotation parallel to the work surface, bristles disposed on the cylindrical body, and flexible flaps disposed longitudinally along the cylindrical body. The brush control process on the controller is configured to reverse bias the rotation of the main cleaning head (to substantially neutrally rotate and/or be driven to rotate at the same speed as a an unwinding cord, string, or other tangled medium), in response to an elevated main cleaning head motor current, while a motion control process independently continues to maneuver the robot across the floor. In another example, the robot includes two main cleaning brushes carried by the chassis and driven to rotate about a horizontal axis to engage a floor surface while the robot is maneuvered across the floor. The two main cleaning brushes may be driven to rotate in the same or opposite directions.
In another aspect, a method of disentangling an autonomous coverage robot includes placing the robot on a floor surface, the robot autonomously traversing across the floor surface in a forward direction of the robot while rotating about a non-horizontal axis an edge cleaning head carried by the chassis and driven by an edge cleaning head motor. The edge cleaning head extends beyond a lateral extent of the chassis while engaging the floor surface. The robot independently provides a reverse bias for the edge cleaning head motor (to substantially neutrally rotate and/or be driven to rotate at the same speed as a an unwinding cord, string, or other tangled medium), in response to an elevated edge cleaning head motor current while continuing to maneuver across the floor surface.
In one implementation, the brush control process on the controller of the robot determines movement of the robot in the forward direction before (independently of robot motion control) reversing the rotation of the edge cleaning head in response to an elevated cleaning head motor current. The brush control process of the robot may (independently of robot motion control) reverses the rotation of the edge cleaning head in response to an elevated edge cleaning head motor current for a period of time. In one example, after the brush control process reverses the rotation of the edge cleaning head, the brush control process may directly or through a supervising process pass a signal to the motion control process of the robot to move in a reverse direction, alter a drive direction, and moves in the drive direction.
In another implementation, the robot also includes a main cleaning brush carried by the chassis, which may be driven to rotate about a horizontal axis to engage the floor surface while the robot is maneuvered across the floor. The robot independently reverses the rotation of the main cleaning brush in response to an elevated main cleaning head motor current while continuing to maneuver across the floor surface. The brush cleaning process of the robot may also determine movement of the robot in the forward direction before independently reversing the rotation of the main cleaning brush in response to an elevated main cleaning brush motor current. Furthermore, the brush cleaning process of the robot may also reverse the rotation of the main cleaning brush for a certain period of time or in intervals.
In another aspect, an autonomous coverage robot includes a drive system, a bump sensor, and a proximity sensor. The drive system is configured to maneuver the robot according to a heading (turn) setting and a speed setting. The bump sensor is responsive to a collision of the robot with an obstacle in a forward direction. The proximity sensor is responsive to an obstacle forward of the robot at a proximate distance but not contacting the robot, e.g., 1-10 inches, preferably 1-4 inches. The motion control processes of the drive system may also be configured to reduce the speed setting in response to a signal from the proximity sensor indicating detection of a potential obstacle, while continuing a cleaning or coverage process, including advancing the robot according to the heading setting. Furthermore, the motion control processes of the drive system may also be configured to alter the heading (turn) setting in response to a signal received from the bump sensor indicating contact with an obstacle.
In some instances, the motion control processes of the drive system may be configured to alter the heading setting in response to the signals received from the bump sensor and one or more side proximity sensors to follow a perimeter of the obstacle. In other instances, the drive system may be configured to alter the heading (turn) setting in response to the signals received from the bump sensor and the proximity sensor to direct the robot away from the obstacle. In one example, the drive system is configured to maneuver the robot at a torque (e.g., motor current or motor resistance) setting and the drive system is configured to alter the motor current or motor resistance setting in response to a signal received from the bump sensor indicating contact with an obstacle. The drive system may increase the motor current or motor resistance setting in response to a signal received from the bump sensor indicating contact with an obstacle.
The proximity sensor may include a plurality of sets of at least one infrared emitter and receive pair, directed toward one another to converge at a fixed distance from one another, substantially as disclosed in “Robot obstacle detection system”, U.S. Pat. No. 6,594,844, herein incorporated by reference in its entirety. Alternatively, the proximity sensor may include a sonar device. The bump sensor may include a switch, a capacitive sensor, or other contact sensitive device.
The robot may be placed on the floor. In yet another aspect, a method of navigating an autonomous coverage robot with respect to an object on a floor includes the robot autonomously traversing the floor in a cleaning mode at a full cleaning speed. Upon sensing a proximity of the object forward of the robot, the robot reduces the cleaning speed to a reduced cleaning speed while continuing towards the object until the robot detects a contact with the object. Upon sensing contact with the object, the robot turns with respect to the object and cleans next to the object, optionally substantially at the reduced cleaning speed. The robot may follow a perimeter of the object while cleaning next to the object. Upon leaving the perimeter of the robot, the robot may increase speed to a full cleaning speed. The robot may maintain a substantially constant following distance from the object, may maintain a following distance smaller than the extent of extension of an edge cleaning head or brush beyond a following side of the robot body, or may substantially contact the object while cleaning next to the object in response to the initial, reduced cleaning speed contact with the object. In one example, the following distance from the object is substantially a distance between the robot and the object substantially immediately after the contact with the object. In another example, the following distance from the object is between about 0 and 2 inches.
In one instance, the robot performs a maneuver to move around the object in response to the contact with the object. The maneuver may include the robot moving in a substantially semi-circular path, or a succession of alternating partial spirals (e.g., arcs with progressively decreasing radius) around the object. Alternatively, the maneuver may include the robot moving away from the object and then moving in a direction substantially tangential to the object.
Upon sensing a proximity of the object forward of the robot, the robot may decrease the full cleaning speed to a reduced cleaning speed at a constant rate, an exponential rate, a non-linear rate, or some other rate. In addition, upon sensing contact with the object, the robot may increase a torque (e.g., motor current) setting of the drive, main brush, or side brush motors.
In yet another aspect, an autonomous robot includes a chassis, a drive system mounted on the chassis and configured to maneuver the robot, and a floor proximity sensor carried by the chassis and configured to detect a floor surface below the robot. The floor proximity sensor includes a beam emitter configured to direct a beam toward the floor surface and a beam receiver responsive to a reflection of the directed beam from the floor surface and mounted in a downwardly-directed receptacle of the chassis. The floor proximity sensor may be a substantially sealed unit (e.g., in the downward direction) and may also include a beam-transparent cover having a forward and rearward edge disposed across a lower end of the receptacle to prohibit accumulation of sediment, “carpet fuzz”, hair, or household dust within the receptacle. The cover may include a lens made of an anti-static material. The forward edge of the cover, i.e., the edge of the cover in the direction of robot motion, at the leading edge of the robot, is elevated above the rearward edge. The lower surface of the receptacle may be wedge shaped. In one example, the floor proximity sensor includes at least one infrared emitter and receiver pair, substantially as disclosed in “Robot obstacle detection system”, U.S. Pat. No. 6,594,844.
In one implementation, the drive system of the robot includes at least one driven wheel suspended from the chassis and at least one wheel-floor proximity sensor carried by the chassis and housed adjacent one of the wheels, the wheel-floor proximity sensor configured to detect the floor surface adjacent the wheel. The drive system may also include a controller configured to maneuver the robot away from a perceived cliff in response a signal received from the floor proximity sensor. In some instances, the drive system includes a wheel drop sensor housed near one of the wheels and responsive to substantial downward displacement of the wheel with respect to the chassis. The drive system may include a validation system that validates the operability of the floor proximity sensors when all wheels drop. The validation is based on the inference that all wheels dropped are likely the result of a robot being lifted off the floor by a person, and checks to see that all floor proximity sensors do not register a floor surface (either no reflection measured, or a reflection that is too strong). Any sensor that registers a floor surface or a too strong reflection (e.g., indicating a blocked sensor) is considered blocked. In response to this detection, the robot may initiate a maintenance reporting session in which indicia or lights indicate that the floor proximity sensors are to be cleaned. In response to this detection, the robot will prohibit forward motion until a validation procedure determines that all floor proximity sensors are clear and are functional. Each wheel-floor and wheel drop proximity sensors may include at least one infrared emitter and receiver pair.
Like reference symbols in the various drawings indicate like elements.
Drive system 104 includes a left drive wheel assembly 112, a right drive wheel assembly 114 and a castor wheel assembly 116. Drive wheel assemblies 112, 114 and castor wheel assembly 116 are connected to chassis 102 and provide support to robot 106. Controller 108 may provide commands to the drive system to drive wheels 112 and 114 forward or backwards to maneuver robot 100. For instance, a command may be issued by controller 108 to engage both wheel assemblies in a forward direction, resulting in forward motion of robot 100. In another instance, a command may be issued for a left turn that causes left wheel assembly 112 to be engaged in the forward direction while right wheel assembly 114 is driven in the rear direction, resulting in robot 100 making a clockwise turn when viewed from above.
Other configurations of edge cleaning heads may also be used with robot 100. For example, an edge cleaning head may have three evenly-spaced brush elements separated by 120 degrees.
Control of the direction and speed of the robot 100 may be handled by motion control behaviors selected by an arbiter according to the principles of behavior based robotics for coverage and confinement, generally disclosed in U.S. Pat. Nos. 6,809,490 and 6,781,338, herein incorporated by reference in their entireties (and executed by controller 108), to reduce the speed magnitude of robot 100 when proximity sensor 134 detects a potential obstacle. The motion behaviors executed by the controller 108 may also alter the velocity of robot 100 when kinetic bump sensors 132 detect a collision of robot 100 with an obstacle. Accordingly, referring to
The robot 100 employs a behavioral software architecture within the controller 103. While embodiments of the robot 100 discussed herein may use behavioral based control only in part or not at all, behavior based control is effective at controlling the robot to be robust (i.e. not getting stuck or failing) as well as safe. The robot 100 employs a control and software architecture that has a number of behaviors that are executed by an arbiter in controller 103. A behavior is entered into the arbiter in response to a sensor event. In one embodiment, all behaviors have a fixed relative priority with respect to one another. The arbiter (in this case) recognizes enabling conditions, which behaviors have a full set of enabling conditions, and selects the behavior having the highest priority among those that have fulfilled enabling conditions. In order of decreasing priority, the behaviors are generally categorized as escape and/or avoidance behaviors (such as avoiding a cliff or escaping a corner), and working behaviors (e.g., wall following, bouncing, or driving in a straight line). The behaviors may include: different escape (including escaping corners, anti-canyoning, stuck situations, “ballistic” temporary fire-and-forget movement that suppress some avoid behaviors, e.g., as disclosed in U.S. Pat. No. 6,809,490) cliff avoiding, virtual wall avoiding (a virtual wall may be a beacon with a gateway beam), spot coverage (covering in a confined pattern such as a spiral or boustrophedon patch), align (turning in place, using side proximity sensors to align with a forward obstacle encountered while obstacle following, e.g., an inside corner), following (representing either or both of substantially parallel or bump following along an obstacle using a side proximity sensor or bumper that extends to the side of the robot), responding to a bump in order to “bounce” (a behavior that occurs after the robot bumps an object), and drive (cruising). Movement of the robot, if any, occurs while a behavior is arbitrated. If more than one behavior is in the arbiter, the behavior with a higher priority is executed, as long as any corresponding required conditions are met. For example, the cliff avoiding behavior will not be executed unless a cliff has been detected by a cliff detection sensor, but execution of the cliff avoiding behavior always takes precedence over the execution of other behaviors that also have satisfied enabling conditions.
The reactive behaviors have, as their enabling conditions or triggers, various sensors and detections of phenomena. These include sensors for obstacle avoidance and detection, such as forward proximity detection (multiple), forward bump detection (multiple), cliff sensors (multiple), detection of a virtual wall signal (which may instead be considered a coverage trigger). Sensors of these types are be monitored and conditioned by filters, conditioning, and their drivers, which can generate the enabling conditions as well as record data that helps the behavior act predictably and on all available information (e.g., conversion to one-bit “true/false” signals, recording of likely angle of impact or incidence based on strength or time differences from a group of sensors, or historical, averaging, frequency, or variance information).
Actual physical sensors may be represented in the architecture by “virtual” sensors synthesized from the conditioning and drivers. Additional “virtual” sensors that are synthesized from detectable or interpreted physical properties, proprioceptive or interpreted upon the robot 100, such as over-current of a motor, stasis or stuck condition of the robot 100 (by monitoring a lack of odometry reading from a wheel encoder or counter), battery charge state via coulometry, and other virtual sensors.
In addition, reactive behaviors can act according to enabling conditions that represent detected phenomena to be sought or followed. A beam or wireless (RF, acoustic) signal can be detected without direction; or in some cases with direction. A remote beam or marker (bar code, retro-reflective, distinctive, fiducial, or natural recognized by vision landmark) giving a direction can permit homing or relative movement; without direction the robot 100 can nonetheless move to servo on the presence, absence, and/or relative strength of a detected signal. The reflection of a beam from the robot 100, edge, or line can be similarly detected, and following behaviors (such as obstacle following by the robot 100) conducted by servoing on such signal. A debris or artifact signal can be collected by monitoring debris or objects collected by or traversed by the robot, and that signal can be an enabling condition for a reactive behavior controlling a spot coverage pattern.
The robot 100 maintains concurrent processes, “parallel” processes that are not generally considered reactive behaviors. A scheduler may be necessary to allocate processor time to most other processes, e.g., including the arbiter and behaviors, in a co-operative or other multitasking manner. If more threading is available, less processes may be managed by the scheduler. As noted, filters and conditioning and drivers, can interpret and translate raw signals. These processes are not considered reactive behaviors, and exercise no direct control over the motor drives or other actuators. In addition, in the present embodiment, brush motor controller(s) control the main and side brushes, although these may alternatively be controlled by dedicated brush behaviors and a brush control arbiter.
In accordance with another example, the gentle touch routine 902 may employ an infrared proximity detector 134 that should go off (i.e., when a receiver receives from a reflection originating in the overlapping space of an emitter and receiver angled toward one another) from about 1 to 10 inches (preferably, from 1 to 4 inches. This distance is selected in order to be within the effective range of the IR proximity or cross-beam sensor 134, yet with sufficient time to slow the mobile robot 100 before a collision with a detected obstacle). Conventional proximity sensors return a signal strength depending on obstacle albedo; cross-beam sensors 134 can be thresholded for various albedos intruding in the specific distance from the sensor where the receiver and emitter's beam/field cross. Additionally, slowing down based on a proximately detected wall may be suppressed in or turned off by the user, independently of the bump sensor 132. Controller 108 may slow the robot's descent substantially in a steady reduction then cruise slowly. Controller 108 may execute an S-curve slowly over about 3 inches, can slow down steadily but at an accelerating or decelerating rate over about 3 inches. During escape behaviors, for example, panic, stasis, stuck, anti-canyoning, the robot may essentially can be turn off the proximity sensors 134—usually by not using the proximity sensors 134 as an enabling condition for any escape behavior or some avoidance behaviors
Drive system 104 may be configured to reduce the speed setting in response to a signal from proximity sensor 134 which indicating detection of a forward obstacle, while continuing to advance the robot 100 and work the floor or surface according to the existing heading setting. Drive system 104 may be configured to alter the heading setting in response to a signal received from bump sensor 132 that indicates contact with an obstacle. For example, drive system 104 may be configured to alter the heading setting in response to the signals received from the bump sensor 132 and the proximity sensor 134 such that robot 100 follows a perimeter of the obstacle. In another example, drive system 104 may be configured to change heading to direct robot 104 away from the obstacle.
Proximity sensors 134 may include one or more pairs of infrared emitters and receivers. For instance, a modulated emitter and a standard receiver may be used. A light pipe (not shown), collimating or diffusing optics, Fresnel or diffractive optics, may be used in some implementations to eliminate blind spots by providing a more uniform light pattern or a light pattern more concentrated or more likely to be detected in high probability/high impact areas, such as the immediate forward direction. Alternatively, some implementations may make use of sonar or other types of proximity sensors.
In some implementations, kinetic bump sensor 132 may include a mechanical switch 130. In some implementations, bump sensor 132 may include a capacitive sensor. Other types of contact sensors may also be used as well.
Drive system 104 may be configured to maneuver robot 100 at a torque (or motor current) setting in response to a signal received from bump sensor 132 which indicates contact with an obstacle. For instance, drive system 104 may increase the torque (or motor current) setting in response to a signal received from the bump sensor indicating contact with an obstacle.
In another example method of navigating an autonomous coverage robot with respect to an object on a floor, robot 100 may be initially placed on the floor (or may already be on the floor, e.g., if the robot starts itself from a charging dock) with robot 100 autonomously traversing the floor in a cleaning mode at a full cleaning speed. If robot 100 senses a nearby object in front of robot 100, it reduces the cleaning speed (e.g., to a reduced cleaning speed) and continues moving toward the object and working/cleaning the floor until detecting impact, which is likely to be with the object but may be another object. Upon sensing impact with an object, robot 100 turns with respect to the object that it bumped and cleans next to, i.e., along, the object. Robot 100 may, for instance, follow the object's perimeter while cleaning along or next to the object. In another instance, robot 100 may maintain a somewhat constant following distance from the object while cleaning next to the object in response to the contact with the object. The following distance from the object may be a distance between robot 100 and the object immediately after the contact with the object, for instance, 0 to 2 inches. The distance is optionally less than the distance that the side or edge brush unit 106a extends beyond the side of the robot.
Robot 100 may, in some instances, perform a maneuver to move around the object in response to the contact with the object. For example, robot 100 may move in a somewhat semi-circular path around the object, or a succession of alternating partial spirals (e.g., arcs with progressively decreasing radius). In another instance, robot 100 may move away from the object and then move in a direction that is somewhat tangential to the object.
Robot 100 may decrease the cleaning speed to a reduced speed at a constant rate, for instance, at a non-linear or exponential rate. The full cleaning speed of robot 100 may be about 300 mm/s and the reduced cleaning speed of robot 100 may be about 100 mm/s.
In cases where the floor proximity sensor 140 is properly placed on a floor, light emitted from emitter 148 reflects off the floor and back to receiver 150, resulting in a signal that is readable by controller 108. In the event that the floor proximity sensor 140 is not over a floor, the amount of light received by receiver 150 is reduced, resulting in a signal that may be interpreted by controller 108 as a cliff.
The caster wheel housing 162 carries the caster wheel 164, the wheel drop sensor 166, and wheel-floor proximity sensor 168. The caster wheel 164 turns about a vertical axis and rolls about a horizontal axis in the caster wheel housing 162.
The wheel drop sensor 166 detects downward displacement of the caster wheel 164 with respect to the chassis 102. The wheel drop sensor 166 determines if the caster wheel 164 is in contact with the work surface.
The wheel-floor proximity sensor 168 is housed adjacent to the caster wheel 164. The wheel-floor proximity sensor 168 detects the proximity of the floor relative to the chassis 102. The wheel-floor proximity sensor 168 includes an infrared (IR) emitter and an IR receiver. The IR emitter produces an IR signal. The IR signal reflects off of the work surface. The IR receiver detects the reflected IR signal and determines the proximity of the work surface. Alternatively, the wheel-floor proximity sensor 168 may use another type of sensor, such as a visible light sensor. The wheel-floor proximity sensor 808 prevents the coverage robot 100 from moving down a cliff in the work surface, such as a stair step or a ledge. In certain implementations, the drive wheel assemblies 114, 116 each include a wheel-floor proximity sensor.
In some instances, drive system 104 may further include a validation system that validates the operability of the floor proximity sensors when all wheels drop. The validation is based on the inference that all wheels dropped are likely the result of a robot being lifted off the floor by a person, and checks to see that all floor proximity sensors do not register a floor surface (either no reflection measured, or a reflection that is too strong). Any sensor that registers a floor surface or a too strong reflection (e.g., indicating a blocked sensor) is considered blocked. In response to this detection, the robot may initiate a maintenance reporting session in which indicia or lights indicate that the floor proximity sensors are to be cleaned. In response to this detection, the robot will prohibit forward motion until a validation procedure determines that all floor proximity sensors are clear and are functional. For example, a mechanical switch sensor may be positioned above castor wheel 168 at a location 176 that causes it to close when the castor is depressed (e.g. it is pushed upwards by the floor), thus providing a alternate signal to controller 108 that castor wheel 164 is on the floor.
Occasionally, an autonomous coverage robot may find itself entangled with an external object, such as frills on the end of a rug or shoe laces dangling from a untied shoe. A method of disentangling an autonomous coverage robotic (such as robot 100) may initially include placing robot 100 on a floor surface, which should be considered to include instances when the robot starts itself from a dock (e.g., after a significant delay, but nonetheless having been placed on the floor). Robot 100 autonomously moves forward across the floor surface while operating the cleaning heads 106a, 106b. Robot 100 may reverse bias edge cleaning head motor 118 in response to a measured increase (e.g., spike or increase above threshold, rapid increase of a predetermined slope) in motor current while continuing to maneuver across the floor surface in an unchanged direction, working and/or cleaning the floor without interruption.
In some instances, robot 100 may move forward before (independently of forward motion control by the motion behaviors) reverse biasing the rotation of edge cleaning head 106a in response to an elevated cleaning head motor current. Robot 100 may independently reverse the rotation of edge cleaning head 106a in response to an increased edge cleaning head 106a motor current for a period of time. The time period for increased current may be specified, for instance, in seconds. After reverse biasing the rotation of edge cleaning head 106, robot 100 may move in a reverse direction, alter its direction of travel, and move in the new direction.
In particular combination, the robot includes a main cleaning head 106b extending across the middle of the robot, e.g., in a direction transverse to the robot working path or substantially in a direction parallel to the main drive wheels, as well as an edge cleaning head which is arranged at the lateral side of the robot, in a position to extend the edge cleaning head beyond the perimeter of the robot in the side direction so as to clean beside the robot (as opposed to solely underneath the body of the robot). The main cleaning head 106b includes at least one rotationally driven brush 111, and the edge cleaning head 106a includes at least one rotationally driven brush 120.
As shown in
The reverse bias does not rapidly rotate the motor in the reverse direction so as to avoid winding the same entangled cord, string, or tassel about the brush in the opposite direction. Instead, the brush motor control process 930 applies a slight bias, sufficient to keep the rotation of the brush near neutral. When the robot 100 moves forward, the cord, string, or tassel pulling on the brush to unwind the entanglement will only transmit an attenuated torque in the reverse direction to the motor (e.g., because of a reduction gearbox between the motor and brush permitting back-driving the gearbox at a reversed mechanical advantage), but, combined with the reverse bias, the attenuated torque results in assisted but slow unwinding of the entangled brush, of increasing speed as more tension is applied by the cord or string, e.g., as the robot moves further away from the site where the cord or string or tassel is fixed.
The reverse bias continues until a time out or until no pulling or jamming load (e.g., no entanglement) is detected on the motor, whereupon the process ends and the cleaning head resumes normal rotation in a direction to clean the surface.
The edge brush 120 of the edge cleaning head 106a is subject to substantially the same control in an edge brush motor control process 960, in which the edge brush 120 rotation is reverse biased 962 in a similar fashion (also shown in
Accordingly, both main 106b and edge 106a brushes are controlled independently of one another and of robot motion, and each may disentangle itself without monitoring or disturbing the other. In some instances, each will become simultaneously entangled, and independent but simultaneous control permits them to the unwound or self-clearing at the same time. In addition, by having the brush motor under reactive control (not awaiting a drive motor state or other overall robot state) and with only a slight reverse bias, the brush will be available to unwind as soon as any rapid current rise is detected, catching an entanglement earlier, but will not move in reverse by any amount sufficient to cause a similar entangling problem in the opposite direction.
In some instances, because the motion control is independent of and does not monitor the brush state, the robot 100 continues to move forward and the cleaning head 106b begins to reverse bias the rotation of main cleaning head 111 after the robot 100 has proceeded some amount forward. In some instances, robot 100 may reverse the rotation of main cleaning head 111 in response to an elevated cleaning head motor current for a period of time. After reversing the rotation of main cleaning head 111, robot 100 may move in a reverse direction, alter a drive direction, and move in the drive direction.
If the movement of rollers 202 is blocked or obstructed to a predetermined or a settable extent, the cleaning head 201 may be stopped, allowing robot 200 to reverse direction with roller 202 minimally powered in the reverse direction sufficiently enough to release the obstruction. For example, if a cord has become wound about roller 202, the roller 202 may be disengaged and allowed to turn so that the cord unwinds as robot 200 retreats. Robot 200 may then resume operation of roller 202 in the original direction of rotation and resume robot motion in the original direction.
In this example, if the movement of either rollers 202 or 212 is blocked or obstructed to a predetermined or a settable extent, cleaning head 201 may be stopped, allowing robot 200 to reverse direction with rollers 202, 212 minimally powered in the reverse direction sufficiently enough to release the obstruction. For example, if a cord becomes wound about either roller 202 or 212, the roller 202 or 212, or both, may be disengaged and allowed to turn so that the cord unwinds as robot 200 retreats. Robot 200 may then resume operation of rollers 202, 212 in the original direction of rotation and resume robot motion in the original direction.
If the movement of rollers 244, 246 is blocked or obstructed to a predetermined or a settable extent, rollers 202, 212 may be stopped, allowing robot 240 to advance forward, as shown by arrow 260, with the rollers 202, 212 minimally powered in the reverse direction sufficiently enough to release obstruction, and resume operation of the roller motor in the original direction of rotation.
If the movement of agitating rollers 276, 278 is blocked or obstructed to a predetermined or a settable extent, the roller motor(s) may be stopped or temporarily activated in the opposite direction in an attempt to remove the blockage or obstruction. The roller motor(s) may then resume operation in the original direction of rotation.
Rollers 304, 306 may dynamically lift and push dirt and debris 307 towards a primary air duct 308 which is integrated within a brush chamber 312. Dirt and debris that are passed over by rollers 304, 306 may encounter a secondary air duct 310 located be hind the rollers. A suction stream generated by an air suction motor (not shown) may convey the collected dirt and debris via the ducts 308, 210 to a container 314. Associated electronic control devices provide control to drive motors for turning and changing direction of robot 300, and also for directional control of the agitating rollers 304, 306.
If the movement of the agitating rollers 304, 306 is blocked or obstructed, then the control device do one or more of stopping or minimally powering the roller motor(s) in the reverse direction, then resume operating the roller motor in the original direction of rotation. Simultaneously, robot 300 may at least momentarily reverse its direction or imparting a twisting motion about its axis and then resuming motion in its original direction.
If the movement of the agitating rollers 304, 306 is blocked or obstructed, the control device may stop or minimally power the roller motor(s) in the reverse direction reverse, then resume operating the roller motor in the original direction of rotation. Simultaneously, robot 300 may at least momentarily reverse its direction or imparting a twisting motion about its axis and then resuming motion in its original direction.
Other robot details and features combinable with those described herein may be found in the following U.S. patent applications filed concurrently herewith, entitled “AUTONOMOUS COVERAGE ROBOT NAVIGATION SYSTEM” having assigned Ser. No. 11/633,869; “MODULAR ROBOT” having assigned Ser. No. 11/633,886; and “ROBOT SYSTEM” having assigned Ser. No. 11/633,883, the entire contents of the aforementioned applications are hereby incorporated by reference.
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 following claims. Accordingly, other implementations are within the scope of the following claims.
This U.S. patent application claims priority under 35 U.S.C. 119(e) to a U.S. provisional patent application filed on Dec. 2, 2005, entitled “ROBOT NETWORKING, THEMING AND COMMUNICATION SYSTEM” and having assigned Ser. No. 60/741,442, the entire contents of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3457575 | Bienek | Jul 1969 | A |
3550714 | Bellinger | Dec 1970 | A |
3674316 | De Brey | Jul 1972 | A |
3756667 | Bombardier | Sep 1973 | A |
3809004 | Leonheart | May 1974 | A |
3937174 | Haaga | Feb 1976 | A |
4099284 | Shinozaki et al. | Jul 1978 | A |
4119900 | Kremnitz | Oct 1978 | A |
D258901 | Keyworth | Apr 1981 | S |
4306329 | Yokoi | Dec 1981 | A |
4369543 | Chen et al. | Jan 1983 | A |
4492058 | Goldfarb | Jan 1985 | A |
4513469 | Godfrey et al. | Apr 1985 | A |
D278732 | Ohkado | May 1985 | S |
4556313 | Miller, Jr. et al. | Dec 1985 | A |
4618213 | Chen | Oct 1986 | A |
4620285 | Perdue | Oct 1986 | A |
4626995 | Lofgren et al. | Dec 1986 | A |
4674048 | Okumura | Jun 1987 | A |
4679152 | Perdue | Jul 1987 | A |
4696074 | Cavalli et al. | Sep 1987 | A |
D292223 | Trumbull | Oct 1987 | S |
4700301 | Dyke | Oct 1987 | A |
4700427 | Knepper | Oct 1987 | A |
4716621 | Zoni | Jan 1988 | A |
4733430 | Westergren | Mar 1988 | A |
4733431 | Martin | Mar 1988 | A |
4756049 | Uehara | Jul 1988 | A |
4777416 | George, II et al. | Oct 1988 | A |
D298766 | Tanno | Nov 1988 | S |
4782550 | Jacobs | Nov 1988 | A |
4813906 | Matsuyama | Mar 1989 | A |
4815157 | Tsuchiya | Mar 1989 | A |
4829626 | Harkonen | May 1989 | A |
4832098 | Palinkas | May 1989 | A |
4854000 | Takimoto | Aug 1989 | A |
4887415 | Martin | Dec 1989 | A |
4893025 | Lee | Jan 1990 | A |
4901394 | Nakamura et al. | Feb 1990 | A |
4912643 | Beirne | Mar 1990 | A |
4918441 | Bohman | Apr 1990 | A |
4919224 | Shyu et al. | Apr 1990 | A |
4919489 | Kopsco | Apr 1990 | A |
4933864 | Evans et al. | Jun 1990 | A |
4956891 | Wulff | Sep 1990 | A |
4962453 | Pong et al. | Oct 1990 | A |
4971591 | Raviv | Nov 1990 | A |
4974283 | Holsten et al. | Dec 1990 | A |
4977639 | Takahashi et al. | Dec 1990 | A |
5001635 | Yasutomi et al. | Mar 1991 | A |
5002145 | Waqkaumi et al. | Mar 1991 | A |
5022812 | Coughlan et al. | Jun 1991 | A |
D318500 | Malewicki | Jul 1991 | S |
5033291 | Podoloff et al. | Jul 1991 | A |
5062819 | Mallory | Nov 1991 | A |
5086535 | Grossmeyer et al. | Feb 1992 | A |
5093955 | Blehert et al. | Mar 1992 | A |
5094311 | Akeel | Mar 1992 | A |
5105502 | Takashima | Apr 1992 | A |
5109566 | Kobayashi et al. | May 1992 | A |
5115538 | Cochran et al. | May 1992 | A |
5136750 | Takashima et al. | Aug 1992 | A |
5142985 | Stearns | Sep 1992 | A |
5163202 | Kawakami et al. | Nov 1992 | A |
5165064 | Mattaboni | Nov 1992 | A |
5173881 | Sindle | Dec 1992 | A |
5204814 | Noonan et al. | Apr 1993 | A |
5239720 | Wood et al. | Aug 1993 | A |
5261139 | Lewis | Nov 1993 | A |
5277064 | Knigga et al. | Jan 1994 | A |
5279672 | Belker, Jr. et al. | Jan 1994 | A |
5284522 | Kobayashi et al. | Feb 1994 | A |
5293955 | Lee | Mar 1994 | A |
5303448 | Hennessey et al. | Apr 1994 | A |
5310379 | Hippely | May 1994 | A |
5319828 | Waldhauser et al. | Jun 1994 | A |
5321614 | Ashworth | Jun 1994 | A |
5324948 | Dudar et al. | Jun 1994 | A |
5341540 | Soupert et al. | Aug 1994 | A |
5353224 | Lee et al. | Oct 1994 | A |
5363935 | Schempf | Nov 1994 | A |
5369347 | Yoo | Nov 1994 | A |
5369838 | Wood et al. | Dec 1994 | A |
5410479 | Coker | Apr 1995 | A |
5435405 | Schempf | Jul 1995 | A |
5440216 | Kim | Aug 1995 | A |
5444965 | Colens | Aug 1995 | A |
5446356 | Kim | Aug 1995 | A |
5451135 | Schempf | Sep 1995 | A |
5454129 | Kell | Oct 1995 | A |
5455982 | Armstrong et al. | Oct 1995 | A |
5465525 | Mifune et al. | Nov 1995 | A |
5467273 | Faibish et al. | Nov 1995 | A |
5497529 | Boesi | Mar 1996 | A |
5505072 | Oreper | Apr 1996 | A |
5507067 | Hoekstra et al. | Apr 1996 | A |
5515572 | Hoekstra et al. | May 1996 | A |
5534762 | Kim | Jul 1996 | A |
5537017 | Feiten et al. | Jul 1996 | A |
5539953 | Kurz | Jul 1996 | A |
5542146 | Hoekstra et al. | Aug 1996 | A |
5548511 | Bancroft | Aug 1996 | A |
5551525 | Pack et al. | Sep 1996 | A |
5553349 | Kilstrom et al. | Sep 1996 | A |
5555587 | Guha | Sep 1996 | A |
5560077 | Crotchett | Oct 1996 | A |
5568589 | Hwang | Oct 1996 | A |
D375592 | Ljunggren | Nov 1996 | S |
5611106 | Wulff | Mar 1997 | A |
5611108 | Knowlton et al. | Mar 1997 | A |
5613261 | Kawakami et al. | Mar 1997 | A |
5621291 | Lee | Apr 1997 | A |
5622236 | Azumi et al. | Apr 1997 | A |
5634237 | Paranjpe | Jun 1997 | A |
5634239 | Tuvin et al. | Jun 1997 | A |
5650702 | Azumi | Jul 1997 | A |
5652489 | Kawakami | Jul 1997 | A |
5682313 | Edlund et al. | Oct 1997 | A |
5709007 | Chiang | Jan 1998 | A |
5717169 | Liang et al. | Feb 1998 | A |
5735959 | Kubo et al. | Apr 1998 | A |
5756904 | Oreper | May 1998 | A |
5761762 | Kubo et al. | Jun 1998 | A |
5777596 | Herbert | Jul 1998 | A |
5781960 | Kilstrom et al. | Jul 1998 | A |
5787545 | Colens | Aug 1998 | A |
5794297 | Muta | Aug 1998 | A |
5812267 | Everett, Jr. et al. | Sep 1998 | A |
5819008 | Asama et al. | Oct 1998 | A |
5831597 | West et al. | Nov 1998 | A |
5839156 | Park et al. | Nov 1998 | A |
5839532 | Yoshiji | Nov 1998 | A |
5841259 | Kim et al. | Nov 1998 | A |
5867800 | Leif | Feb 1999 | A |
5905209 | Oreper | May 1999 | A |
5916008 | Wong | Jun 1999 | A |
5926909 | McGee | Jul 1999 | A |
5933102 | Miller | Aug 1999 | A |
5933913 | Wright et al. | Aug 1999 | A |
5935179 | Kleiner et al. | Aug 1999 | A |
5940927 | Haegermarck et al. | Aug 1999 | A |
5940930 | Oh et al. | Aug 1999 | A |
5942869 | Katou | Aug 1999 | A |
5943730 | Boomgaarden | Aug 1999 | A |
5943733 | Tagliaferri | Aug 1999 | A |
5959423 | Nakanishi et al. | Sep 1999 | A |
5968281 | Wright et al. | Oct 1999 | A |
5983448 | Wright et al. | Nov 1999 | A |
5984880 | Lander | Nov 1999 | A |
5989700 | Krivopal | Nov 1999 | A |
5991951 | Kubo | Nov 1999 | A |
6000088 | Wright et al. | Dec 1999 | A |
6032542 | Warnick | Mar 2000 | A |
6041471 | Charky et al. | Mar 2000 | A |
6049620 | Dickinson et al. | Apr 2000 | A |
6055702 | Imamura | May 2000 | A |
6065182 | Wright et al. | May 2000 | A |
6076025 | Ueno | Jun 2000 | A |
6076226 | Reed | Jun 2000 | A |
6088020 | Mor | Jul 2000 | A |
6099091 | Campbell | Aug 2000 | A |
6101671 | Wright et al. | Aug 2000 | A |
6108269 | Kabel | Aug 2000 | A |
6125498 | Roberts et al. | Oct 2000 | A |
6142252 | Kinto et al. | Nov 2000 | A |
6167587 | Kasper et al. | Jan 2001 | B1 |
6192548 | Huffman | Feb 2001 | B1 |
6226830 | Hendriks et al. | May 2001 | B1 |
6230362 | Kasper et al. | May 2001 | B1 |
6243913 | Frank et al. | Jun 2001 | B1 |
6259979 | Holmquist | Jul 2001 | B1 |
6263539 | Baig | Jul 2001 | B1 |
6272936 | Oreper | Aug 2001 | B1 |
6327741 | Reed | Dec 2001 | B1 |
6370453 | Sommer | Apr 2002 | B2 |
6400048 | Nishimura | Jun 2002 | B1 |
6401294 | Kasper | Jun 2002 | B2 |
6412141 | Kasper et al. | Jul 2002 | B2 |
6437227 | Theimer | Aug 2002 | B1 |
6442476 | Poropat | Aug 2002 | B1 |
6444003 | Sutcliffe | Sep 2002 | B1 |
6481515 | Kirkpatrick et al. | Nov 2002 | B1 |
6493612 | Bisset | Dec 2002 | B1 |
6493613 | Peless et al. | Dec 2002 | B2 |
6496754 | Song et al. | Dec 2002 | B2 |
6496755 | Wallach et al. | Dec 2002 | B2 |
6504610 | Bauer | Jan 2003 | B1 |
6525509 | Petersson et al. | Feb 2003 | B1 |
6532404 | Colens | Mar 2003 | B2 |
D474312 | Stephens | May 2003 | S |
6571415 | Gerber et al. | Jun 2003 | B2 |
6571422 | Gordon | Jun 2003 | B1 |
6574536 | Kawagoe et al. | Jun 2003 | B1 |
6580246 | Jacobs | Jun 2003 | B2 |
6601265 | Burlington | Aug 2003 | B1 |
6605156 | Clark et al. | Aug 2003 | B1 |
6611120 | Song et al. | Aug 2003 | B2 |
6611738 | Ruffner | Aug 2003 | B2 |
6658693 | Reed, Jr. | Dec 2003 | B1 |
6671592 | Bisset et al. | Dec 2003 | B1 |
6690134 | Jones et al. | Feb 2004 | B1 |
6741054 | Koselka et al. | May 2004 | B2 |
6748297 | Song et al. | Jun 2004 | B2 |
6756703 | Chang | Jun 2004 | B2 |
6781338 | Jones et al. | Aug 2004 | B2 |
6809490 | Jones et al. | Oct 2004 | B2 |
6830120 | Yashima et al. | Dec 2004 | B1 |
6841963 | Song et al. | Jan 2005 | B2 |
6883201 | Jones et al. | Apr 2005 | B2 |
6901624 | Mori et al. | Jun 2005 | B2 |
D510066 | Hickey et al. | Sep 2005 | S |
6938298 | Aasen | Sep 2005 | B2 |
6956348 | Landry et al. | Oct 2005 | B2 |
6965209 | Jones et al. | Nov 2005 | B2 |
6971140 | Kim | Dec 2005 | B2 |
6985556 | Shanmugavel | Jan 2006 | B2 |
6993954 | George | Feb 2006 | B1 |
6999850 | McDonald | Feb 2006 | B2 |
7024278 | Chiapetta et al. | Apr 2006 | B2 |
7030768 | Wanie | Apr 2006 | B2 |
7057120 | Ma et al. | Jun 2006 | B2 |
7085624 | Aldred et al. | Aug 2006 | B2 |
7206677 | Hulden | Apr 2007 | B2 |
20010020200 | Das et al. | Sep 2001 | A1 |
20010025183 | Shahidi | Sep 2001 | A1 |
20010047231 | Peless et al. | Nov 2001 | A1 |
20020011813 | Koselka et al. | Jan 2002 | A1 |
20020016649 | Jones | Feb 2002 | A1 |
20020120364 | Colens | Aug 2002 | A1 |
20020156556 | Ruffner | Oct 2002 | A1 |
20020173877 | Zweig | Nov 2002 | A1 |
20030019071 | Field et al. | Jan 2003 | A1 |
20030025472 | Jones et al. | Feb 2003 | A1 |
20030060928 | Abramson et al. | Mar 2003 | A1 |
20030067451 | Tagg | Apr 2003 | A1 |
20030120389 | Abramson et al. | Jun 2003 | A1 |
20030137268 | Papanikolopoulos et al. | Jul 2003 | A1 |
20030192144 | Song et al. | Oct 2003 | A1 |
20030216834 | Allard | Nov 2003 | A1 |
20030233177 | Johnson et al. | Dec 2003 | A1 |
20040020000 | Jones | Feb 2004 | A1 |
20040030448 | Solomon | Feb 2004 | A1 |
20040030449 | Solomon | Feb 2004 | A1 |
20040030450 | Solomon | Feb 2004 | A1 |
20040030571 | Solomon | Feb 2004 | A1 |
20040031113 | Wosewick et al. | Feb 2004 | A1 |
20040049877 | Jones et al. | Mar 2004 | A1 |
20040068351 | Solomon | Apr 2004 | A1 |
20040068415 | Solomon | Apr 2004 | A1 |
20040068416 | Solomon | Apr 2004 | A1 |
20040076324 | Burl et al. | Apr 2004 | A1 |
20040088079 | Lavarec et al. | May 2004 | A1 |
20040111184 | Chiappetta et al. | Jun 2004 | A1 |
20040117064 | McDonald | Jun 2004 | A1 |
20040134336 | Solomon | Jul 2004 | A1 |
20040134337 | Solomon | Jul 2004 | A1 |
20040148731 | Damman et al. | Aug 2004 | A1 |
20040156541 | Jeon et al. | Aug 2004 | A1 |
20040158357 | Lee et al. | Aug 2004 | A1 |
20040200505 | Taylor et al. | Oct 2004 | A1 |
20040204792 | Taylor et al. | Oct 2004 | A1 |
20040211444 | Taylor et al. | Oct 2004 | A1 |
20040236468 | Taylor et al. | Nov 2004 | A1 |
20040244138 | Taylor et al. | Dec 2004 | A1 |
20050000543 | Taylor et al. | Jan 2005 | A1 |
20050010331 | Taylor et al. | Jan 2005 | A1 |
20050021181 | Kim et al. | Jan 2005 | A1 |
20050067994 | Jones | Mar 2005 | A1 |
20050156562 | Cohen et al. | Jul 2005 | A1 |
20050166354 | Uehigashi | Aug 2005 | A1 |
20050204717 | Colens | Sep 2005 | A1 |
20050251292 | Casey et al. | Nov 2005 | A1 |
20060010638 | Shimizu | Jan 2006 | A1 |
20060060216 | Woo | Mar 2006 | A1 |
20060089765 | Pack et al. | Apr 2006 | A1 |
20060190133 | Konandreas et al. | Aug 2006 | A1 |
20070244610 | Ozick et al. | Oct 2007 | A1 |
Number | Date | Country |
---|---|---|
437024 | Jul 1991 | EP |
0 861 629 | Sep 1998 | EP |
0 930 040 | Jul 1999 | EP |
1 331 537 | Jul 2003 | EP |
1 331 537 | Jul 2003 | EP |
1331537 | Jul 2003 | EP |
2 828 589 | Aug 2001 | FR |
2 283 838 | May 1995 | GB |
2 404 330 | Feb 2005 | GB |
62-120510 | Jun 1987 | JP |
62120510 | Jun 1987 | JP |
62-154008 | Jul 1987 | JP |
62154008 | Jul 1987 | JP |
63-183032 | Jul 1988 | JP |
63-241610 | Oct 1988 | JP |
2-6312 | Jan 1990 | JP |
2026312 | Jan 1990 | JP |
03-051023 | Mar 1991 | JP |
06-327598 | Nov 1994 | JP |
7-295636 | Nov 1995 | JP |
7295636 | Nov 1995 | JP |
08-089451 | Apr 1996 | JP |
08-152916 | Jun 1996 | JP |
9-179625 | Jul 1997 | JP |
9185410 | Jul 1997 | JP |
9206258 | Aug 1997 | JP |
11-508810 | Aug 1999 | JP |
11508810 | Aug 1999 | JP |
11-510935 | Sep 1999 | JP |
11510935 | Sep 1999 | JP |
2001-258807 | Sep 2001 | JP |
2001-275908 | Oct 2001 | JP |
2001-525567 | Dec 2001 | JP |
2002-78650 | Mar 2002 | JP |
2002-204768 | Jul 2002 | JP |
22204768 | Jul 2002 | JP |
2002-532178 | Oct 2002 | JP |
3356170 | Oct 2002 | JP |
2002-323925 | Nov 2002 | JP |
22323925 | Nov 2002 | JP |
2002-355206 | Dec 2002 | JP |
2002-360471 | Dec 2002 | JP |
2002-360482 | Dec 2002 | JP |
22360479 | Dec 2002 | JP |
2003-10076 | Jan 2003 | JP |
2003-5296 | Feb 2003 | JP |
2003-036116 | Feb 2003 | JP |
2003-38401 | Feb 2003 | JP |
2003-38402 | Feb 2003 | JP |
2003-505127 | Feb 2003 | JP |
23052596 | Feb 2003 | JP |
2003036116 | Feb 2003 | JP |
2003-061882 | Mar 2003 | JP |
2003-310489 | Nov 2003 | JP |
WO 9526512 | Oct 1995 | WO |
WO9526512 | Oct 1995 | WO |
WO 9715224 | May 1997 | WO |
WO 9740734 | Nov 1997 | WO |
WO 9741451 | Nov 1997 | WO |
WO9740734 | Nov 1997 | WO |
WO9741451 | Nov 1997 | WO |
WO 9928800 | Jun 1999 | WO |
WO 9938056 | Jul 1999 | WO |
WO 9938237 | Jul 1999 | WO |
WO 9943250 | Sep 1999 | WO |
WO 0004430 | Jan 2000 | WO |
WO0004430 | Jan 2000 | WO |
WO0004430 | Apr 2000 | WO |
WO 0036962 | Jun 2000 | WO |
WO 0038026 | Jun 2000 | WO |
WO0038026 | Jun 2000 | WO |
WO0038029 | Jun 2000 | WO |
WO 0078410 | Dec 2000 | WO |
WO 0106904 | Feb 2001 | WO |
WO 0106905 | Feb 2001 | WO |
WO0106904 | Feb 2001 | WO |
WO 0239864 | May 2002 | WO |
WO 0239868 | May 2002 | WO |
WO0239868 | May 2002 | WO |
WO 02058527 | Aug 2002 | WO |
WO 02062194 | Aug 2002 | WO |
WO 02067744 | Sep 2002 | WO |
WO 02067745 | Sep 2002 | WO |
WO 02074150 | Sep 2002 | WO |
WO 02075356 | Sep 2002 | WO |
WO 02075469 | Sep 2002 | WO |
WO 02075470 | Sep 2002 | WO |
WO02067744 | Sep 2002 | WO |
WO02075356 | Sep 2002 | WO |
WO02075469 | Sep 2002 | WO |
WO02075470 | Sep 2002 | WO |
WO 02101477 | Dec 2002 | WO |
WO02101477 | Dec 2002 | WO |
WO02101477 | Dec 2002 | WO |
WO 03026474 | Apr 2003 | WO |
WO 03040845 | May 2003 | WO |
WO 03040846 | May 2003 | WO |
WO03040546 | May 2003 | WO |
WO 2004006034 | Jan 2004 | WO |
WO2004004533 | Jan 2004 | WO |
WO2004005956 | Jan 2004 | WO |
WO2004058028 | Jan 2004 | WO |
WO2005077244 | Jan 2004 | WO |
WO2006068403 | Jan 2004 | WO |
WO 2004025947 | Mar 2004 | WO |
WO 2005055795 | Jun 2005 | WO |
WO 2005083541 | Sep 2005 | WO |
2006046400 | May 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20070234492 A1 | Oct 2007 | US |
Number | Date | Country | |
---|---|---|---|
60741442 | Dec 2005 | US |