User Control Device for Transporters
The user-controlled device with UCP and integrated sensors allows personal vehicles to autonomously navigate through complex environments, addressing safety and reliability issues by handling obstacles, stairs, and doors, and interacting with elevators.
Patent Information
- Application Number
- JP2023217946
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2016-04-14
- Filing Date
- 2023-12-25
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2037-04-13
AI Technical Summary
Existing personal vehicles lack the ability to automatically detect and react to important environmental features, such as obstacles, stairs, doors, and elevators, compromising safety and reliability in navigation.
A user-controlled device equipped with a User Control Processor (UCP) that integrates sensors and processors to automatically navigate through environments by receiving user input, processing sensor data, and generating movement commands to handle obstacles, climb stairs, pass through doors, and interact with elevators, using technologies like SLAM and PCL for environmental mapping.
Enhances the safety and reliability of personal vehicles by enabling them to autonomously navigate complex environments, including obstacle avoidance, stair climbing, door passage, and elevator usage, providing enhanced user control and convenience.
Smart Images

Figure 0007584616000001 
Figure 0007584616000002 
Figure 0007584616000003
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application was filed on April 14, 2016 and is related to a USER CONTROL DEVICE This application claims the benefit of U.S. Provisional Application No. 62 / 322,522 (Attorney Docket No. R52), entitled FOR A TRANSPORTER, which is incorporated herein by reference in its entirety.
[0002] The present teachings generally relate to personal vehicles, and more particularly to user control devices for vehicles with enhanced requirements for safety and reliability. Currently, personal vehicles can ascend and descend stairs. Such devices can include multiple wheels that can rotate about an axis fixed to a cluster arm. The cluster arm can rotate about an axis so that the wheels can rest on a succession of stairs. Currently, users can enter or exit a car or other enclosed vehicle, and can load or unload a personal vehicle into or from an enclosed vehicle. [Background technology]
[0003] What is needed is a user controlled device that can automatically determine the location of important features of the personal vehicle's environment and can cause the personal vehicle to automatically react to the important features. Summary of the Invention [Means for solving the problem]
[0004] The user control device of the present teachings may include a user control processor (UCP) assist that provides enhanced functionality to a user of a personal vehicle, such as, but not limited to, a transporter of the present teachings, for example, but not limited to, assisting a user of the transporter to avoid obstacles, pass through doors, climb stairs, enter elevators, and park / carry the transporter. The UCP assist may receive user input and / or input from a platform processor (PBP) that may control the transporter and enable activation of an automatically or manually selected processing mode. The command processor may enable the invoked mode by generating a movement command based at least on previous movement commands, data from the user, and data from the sensor. The command processor may receive user data, which may include a signal from a joystick that may provide an indication of a desired direction and speed of movement of the transporter. The user data may also include a mode selection to which the transporter may be transitioned. Modes such as door mode, restroom mode, extended staircase mode, elevator mode, dynamic storage mode, and static storage / charging mode may be selected. Any of these modes can include a move to position mode, or the user can directly command the transporter to move to a location. The UCP assist can generate commands, such as move commands, which can include, but are not limited to, speed and direction, and the move commands can be provided to the PBP, which can transmit this information to the wheel motor drive and cluster motor drive.
[0005] The sensor data can be collected by a sensor handling processor, which may include, but is not limited to, a transporter geometry processor, a point cloud library (PCL) processor, a simultaneous localization and mapping (SLAM) processor, and an obstacle processor. Movement commands can also be provided to the sensor handling processor. The sensors can provide environmental information, which may include, for example, but is not limited to, geometric information about the obstacles and the transporter. The sensors can include at least one time-of-flight sensor, which may be mounted anywhere on the transporter. Multiple sensors can be mounted on the transporter. The PCL processor can collect and process the environmental information and produce PCL data, which can be processed by the PCL library.
[0006] The transporter geometry processor of the present teachings can receive transporter geometry information from the sensor, perform any processing necessary to prepare the transporter geometry information for use by the mode-dependent processor, and provide the transporter geometry information to the mode-dependent processor. The transporter geometry can be used to automatically determine whether the transporter can fit into and through a space, such as, for example, a staircase structure and a door. The SLAM processor can determine navigation information based on, for example, but not limited to, user information, environmental information, and movement commands. The transporter can navigate within a path set at least in part by the navigation information. The obstacle processor can locate obstacles and distances to the obstacles. Obstacles can include, but are not limited to, doors, stairs, cars, and miscellaneous features in the vicinity of the transporter's path.
[0007] A method for obstacle processing of the present teachings may include, but is not limited to, receiving a movement command and user information, receiving and segmenting PCL data, identifying at least one plane in the segmented PCL data, and identifying at least one obstacle in the at least one plane. The method for obstacle processing may further include determining at least one situation identifier based on at least the obstacle, the user information, and the movement command, and determining a distance between the transporter and the obstacle based on at least the situation identifier. The method for obstacle processing may also include accessing at least one permission command associated with the distance, the obstacle, and the situation identifier. The method for obstacle processing may still further include accessing an automatic response to the permission command, mapping one of the movement command and the permission command, and providing the automatic response associated with the movement command and the mapped permission command to a mode-dependent processor.
[0008] The obstacles can be stationary or moving. The distance can include a fixed amount and / or can be a dynamically varying amount. The movement commands can include, but are not limited to, a follow command, a through obstacle command, a go by obstacle command, and a not follow obstacle command. The obstacle data can be stored and retrieved, for example, locally and / or in a cloud-based storage area. The method can optionally include storing the obstacle data and enabling access to the stored obstacle data by a system external to the transporter. The method for obstacle processing can optionally include collecting sensor data from a time-of-flight camera mounted on the transporter, analyzing the sensor data using a point cloud library (PCL), tracking the moving object using SLAM based on the location of the transporter, identifying planes in the obstacle data, and providing an automatic response associated with the mapped clearance command to the mode-dependent processor. The method for obstacle processing can optionally receive a resume command and provide an automatic response associated with the movement command and the mapped clearance command to the mode-dependent processor following the resume command. The automatic response may include a rate control command.
[0009] The obstacle processor of the present teachings may include, but is not limited to, a nav / PCL data processor. The nav / PCL processor may receive movement commands and user information, and may receive and segment PCL data from the PCL processor, identify a plane in the segmented PCL data, and identify obstacles in the plane. The obstacle processor may include a distance processor. The distance processor may determine a situation identifier based on the user information, the movement commands, and the obstacles. The distance processor may determine a distance between the transporter and the obstacles based at least on the situation identifier. The moving object processor and / or the stationary object processor may access an authorization command associated with the distance, the obstacles, and the situation identifier. The moving object processor and / or the stationary object processor may access an automatic response from an automatic response list associated with the authorization command. The moving object processor and / or the stationary object processor may access the movement command and map one of the movement command and the authorization command. The moving object processor and / or the stationary object processor may provide the automatic response associated with the movement command and the mapped authorization command to the mode dependent processor. Movement commands can include follow, pass, by, move to a fixed position, and not follow commands. The Navi / PCL processor can store obstacles in local storage and / or on a storage cloud, and can enable access to the stored obstacles by systems external to the transporter.
[0010] A method of the present teachings for navigating stairs can include, but is not limited to, receiving a stair command and receiving environmental information from a sensor and / or obstacle processor mounted on the transporter. The method for navigating stairs can include locating a stair structure in the environmental information based on the environmental information, and receiving a selection of one of the stair structures located by the sensor and / or obstacle processor. The method for navigating stairs can also include measuring a characteristic of the selected stair structure and locating an obstacle on the selected stair structure, if applicable, based on the environmental information. The method for navigating stairs can also include locating a last stair of the selected stair structure based on the environmental information, and providing a movement command and moving the transporter on the selected stair structure based on the measured characteristic, the last stair, and the obstacle, if applicable. The method for navigating stairs can continue providing the movement command until the last stair is reached. The characteristics can include, but are not limited to, a stair riser height, a riser surface texture, and a riser surface temperature of the selected stair structure. If the surface temperature is outside the threshold range and the surface texture is outside the static friction settings, an alert can be generated.
[0011] The method can optionally include locating at least one stair structure based on GPS data, building a map of the selected stair structure using SLAM, saving the map, and updating the map while the transporter is moving. The method can optionally include accessing a geometry of the transporter, comparing the geometry to at least one characteristic of the selected stair structure, and modifying the movement of the transporter based on the comparing. The characteristics can include, but are not limited to, a height of at least one riser of the selected stair structure, a surface texture of the at least one riser, and a surface temperature of the at least one riser. The method can optionally include generating an alert if the surface temperature is outside a threshold range and the surface texture is outside a static friction setting. The threshold range can include, but is not limited to, a temperature below 33° F. The static friction setting can include, but is not limited to, a carpet texture. The method can optionally include determining a topography of an area surrounding the selected staircase structure based on the sensor data and generating an alert if the topography is not flat. The method can optionally include accessing a set of extreme situations.
[0012] The staircase navigation processor of the present teachings may include, but is not limited to, a staircase structure processor that receives at least one staircase command included in the user information, and a staircase structure locator that receives environmental information from a sensor mounted on the transporter, for example, through an obstacle processor. The staircase structure locator may locate a staircase structure in the environmental information based on the environmental information, and may receive a selection of selected staircase structures. The staircase characteristic processor may measure characteristics of the selected staircase structure, and may locate obstacles on the selected staircase structure, if applicable, based on the environmental information. The staircase movement processor may locate the last staircase of the selected staircase structure based on the environmental information, and may provide a movement command to the movement processor based on the characteristics, the last staircase, and the obstacles, if applicable, to instruct the transporter to move on the selected staircase structure. The staircase structure locator may locate a staircase structure based on GPS data, and may build and store a map of the selected staircase structure. The map may be stored for use locally and / or by other devices not associated with the transporter. The stair structure processor can access the geometry of the transporter, compare the geometry to characteristics of the selected stair structure, and modify navigation of the transporter based on the comparison. The stair structure processor can optionally generate an alert if a surface temperature of a riser of the selected stair structure is outside a threshold range and a surface texture of the selected stair structure is outside a static friction setting. The stair movement processor can determine a topography of an area surrounding the selected stair structure based on the environmental information, and can generate an alert if the topography is not flat. The stair movement processor can access a set of extreme conditions that can be used to modify movement commands generated by the stair movement processor.
[0013] When the transporter crosses the threshold of the door, where the door may include a door swing, a hinge location, and a doorway, the method of the present teachings for navigating the door may include receiving and segmenting environmental information from a sensor mounted on the transporter. The environmental information may include a geometry of the transporter. The method may include identifying a plane in the segmented sensor data and identifying a door in the plane. The method for navigating the door may include measuring the door based on the environmental information. The method for navigating the door may include determining the door swing and providing a movement command and moving the transporter for access to the door handle. The method for navigating the door may include providing a movement command as the door opens and moving the transporter away from the door a distance based on the door measurement. The method for navigating the door may include providing a movement command and moving the transporter forward through the doorway. The transporter may maintain the door in an open position if the door swing is toward the transporter.
[0014] The method of the present teachings for processing sensor data can determine the hinge side of the door, the direction and angle of the door, and the distance to the door through information from the sensor. The movement processor of the present teachings can generate commands to the PBP such as start / stop left turn, start / stop right turn, start / stop forward movement, start / stop backward movement, and can facilitate the door mode by stopping the transporter, canceling a goal that the transporter may be completing, and centering the joystick. The door processor of the present teachings can determine whether the door is, for example, a push door, a sliding door, or a sliding door. The door processor can determine the width of the door based on the current position and orientation of the transporter, and can determine the x / y / z location of the door pivot point. If the door processor determines that the number of valid points in the image of the door derived from the set of obstacles and / or PCL data is above a threshold, the door processor can determine the distance from the transporter to the door. The door processor can determine whether the door is moving based on successive samples of PCL data from the sensor processor. In some configurations, the door processor can assume that the side of the transporter is at the same height as the handle side of the door and can use that assumption to determine the width of the door, along with the location of the door pivot point. Based on the door swing and the door width, the door processor can generate commands to move the transporter through the door. The transporter itself can hold the door open while the transporter crosses the door threshold.
[0015] In some configurations, the transporter can automatically negotiate use of restroom facilities. Restroom and restroom stall doors can be located as discussed herein, and the transporter can be moved to a location relative to the door as discussed herein. Fixtures in the restroom can be located as obstacles as discussed herein, and the transporter can automatically position itself near the fixtures to provide the user with access to, for example, a toilet, sink, and changing station. The transporter can automatically navigate to exit restroom stalls and restrooms through door and obstacle handling as discussed herein. The transporter can automatically traverse door thresholds based on the transporter's geometry.
[0016] For example, but not limited to, the method of the present teachings for automatically storing a transporter in a vehicle, such as a wheelchair accessible van, can aid a user in independent use of the vehicle. When the user exits the transporter and enters the vehicle, potentially as the vehicle's driver, the transporter can remain parked outside the vehicle. If the transporter is to be carried by the user in the vehicle for later use, the dynamic parking mode of the present teachings can provide a movement command to the transporter to store itself, either automatically or in response to a command, and to be retrieved at the vehicle door. The transporter can be instructed to store itself, for example, through a command received from an external application. In some configurations, a computer-driven device, such as a cell phone, laptop, and / or tablet, can be used to run one or more external applications and generate information that can ultimately control the transporter. In some configurations, the transporter can automatically proceed to the dynamic parking mode after the user exits the transporter. The movement commands can include commands to locate the vehicle door into which the transporter will enter to be stored and commands to direct the transporter to the vehicle door. The dynamic parking mode can determine an error condition, such as, for example, but not limited to, if the vehicle door is too small for the transporter to enter, and the dynamic parking mode can alert the user of the error condition, for example, but not limited to, through an audio alert through an audio interface and / or a message to one or more external applications. If the vehicle door is wide enough for the transporter to enter, the dynamic parking mode can provide vehicle control commands to instruct the vehicle to open the vehicle door. The dynamic parking mode can determine when the vehicle door is open and whether there is space for the transporter to be stored.The dynamic parking mode can invoke methods for obstacle handling to help determine the status of the vehicle doors and whether there is room in the vehicle to store the transporter. If there is enough room for the transporter, the dynamic parking mode can provide a movement command to move the transporter into a storage space in the vehicle. Vehicle control commands can be applied to command the vehicle to lock the transporter in place and close the vehicle doors. When the transporter is needed again, one or more external applications can be used, for example, to return the transporter to the user. The status of the transporter can be recalled and vehicle control commands can command the vehicle to unlock the transporter and open the vehicle doors. The vehicle doors can be located and the transporter can be moved through the vehicle doors, for example, to a passenger door commanded by one or more external applications. In some configurations, the vehicle can be tagged at a fixed location, such as, for example, a vehicle entrance door, where the transporter can be stored.
[0017] The method of the present teachings for storing / recharging the transporter can potentially assist the user to store and potentially recharge the transporter while the user sleeps. After the user steps off the transporter, a command can be initiated by one or more external applications to move the transporter, possibly without an occupant, to a storage / docking area. In some configurations, a mode selection by the user while the user is using the transporter can initiate an automatic storage / docking function after the user steps off the transporter. When the transporter is needed again, a command can be initiated by one or more external applications to direct the transporter to the user. The method for storing / recharging the transporter can include, but is not limited to, locating at least one storage / charging area and providing at least one movement command to move the transporter from a first location to the storage / charging area. The method for storing / recharging the transporter can include locating a charging dock in a storage / charging area, providing at least one movement command, and coupling the transporter and the charging dock. The method for storing / recharging the transporter can optionally include providing at least one movement command and moving the transporter to a first location when the transporter receives a start-up command. If the storage / charging area does not exist, or if the charging dock does not exist, or if the transporter cannot be coupled with the charging dock, the method for storing / recharging the transporter can optionally include providing at least one alert to a user, providing at least one movement command, and moving the transporter to a first location. The method of the present teachings for negotiating with an elevator while maneuvering the transporter can assist a user in ascending and descending the elevator while aboard the transporter.When the elevator is located, for example, automatically, and the user selects the desired elevator direction, and when the elevator arrives and the doors open, a movement command can be provided to move the transporter into the elevator. The elevator geometry can be determined and a movement command can be provided to move the transporter to a location that allows the user to select a desired activity from an elevator selection panel. The location of the transporter can also be appropriate for exiting the elevator. When the elevator doors open, a movement command can be provided to move the transporter and exit the elevator completely. The present invention provides, for example, the following: (Item 1) 1. A method for responding to at least one obstacle while steering a transporter, comprising: receiving at least one movement command and user information; receiving and segmenting obstacle data; identifying at least one plane within the segmented obstacle data; identifying the at least one obstacle within the at least one plane; determining at least one situation identifier based at least on the at least one obstacle, the user information, and the at least one movement command; determining a distance between the transporter and the at least one obstacle based on at least the at least one situation identifier; accessing at least one authorization command associated with the distance, the at least one obstacle, and the at least one situation identifier; accessing at least one automated response to said at least one movement command; mapping one of the at least one movement command and the at least one authorization command; moving the transporter based at least on the at least one movement command and the at least one automatic response associated with the mapped authorization command; A method comprising: (Item 2) 2. The method of claim 1, wherein the at least one obstacle includes at least one moving object. (Item 3) 2. The method of claim 1, wherein the distance comprises a dynamically varying amount. (Item 4) 2. The method of claim 1, wherein the at least one movement command includes at least one obstacle passage command. (Item 5) 2. The method of claim 1, further comprising analyzing the obstacle data using a point cloud library (PCL). (Item 6) 3. The method of claim 2, further comprising tracking the at least one moving object using simultaneous localization and mapping (SLAM) with detection and tracking of moving objects (DATMO) based on the location of the transporter. (Item 7) 1. A transporter, the transporter automatically responding to at least one obstacle encountered while maneuvering the transporter, the transporter comprising: a Nav / PCL processor that receives at least one movement command and user information, the Nav / PCL processor receiving and segmenting PCL data from a PCL processor, the Nav / PCL processor identifying a plane within the segmented PCL data, and the Nav / PCL processor identifying at least one obstacle within the plane; a distance processor that determines a situation identifier based on at least the user information, the at least one movement command, and the at least one obstacle, the distance processor determining a distance between the transporter and the at least one obstacle based on at least the situation identifier; an object processor that accesses an authorization command associated with the distance, the at least one obstacle, and the situation identifier, the object processor accessing an automatic response associated with the authorization command, the object processor accessing the at least one movement command, and mapping the at least one movement command to at least one of the authorization commands; at least one mode dependent processor that receives the at least one movement command and an automatic response associated with the mapped authorization command, the at least one mode dependent processor enabling mode specific processing; A transporter comprising: (Item 8) The transporter described in item 7, wherein the Navi / PCL processor includes steps of storing the at least one obstacle in a storage cloud and enabling an external system of the transporter to access the at least one stored obstacle. (Item 9) 1. A method for enabling a transporter to navigate stairs, comprising: receiving at least one stair command; receiving environmental information from sensors mounted on the transporter; locating at least one staircase structure based on the environmental information; receiving a selection of a selected staircase structure from the at least one staircase structure; measuring at least one characteristic of the selected staircase structure based on the environmental information; locating at least one obstacle on the selected staircase structure, if applicable, based on the environmental information; locating a last stair of the selected stair structure based on the environmental information; providing the at least one movement command based at least on the measured at least one characteristic, the last staircase, and, if applicable, the obstacle, to move the transporter on the selected staircase structure; A method comprising: (Item 10) 10. The method of claim 9, further comprising locating the at least one staircase structure based on GPS data. (Item 11) 10. The method of claim 9, further comprising using SLAM to build a map of the selected staircase structure. (Item 12) 10. The method of claim 9, wherein the at least one characteristic includes a surface texture of the at least one riser. (Item 13) 1. A transporter for navigating stairs, comprising: a stair structure processor for receiving at least one stair command contained within the user information; a staircase locator that receives environmental information from a sensor mounted on the transporter, the staircase locator locating the staircase within the environmental information and receiving a selected staircase option; a staircase characteristic processor for measuring at least one characteristic of the selected staircase structure, the staircase characteristic processor locating an obstacle on the selected staircase structure, if applicable, based on the environmental information; a stair movement processor for locating a last stair of the selected stair structure based on the environmental information, the stair movement processor providing at least one movement command based on the at least one characteristic, the last stair, and, if applicable, the obstacles to instruct the transporter to move on the selected stair structure; A transporter comprising: (Item 14) 1. A method for negotiating a door in a transporter, the door including at least one handle, a door swing, and a doorway, the method comprising: receiving and segmenting environmental information from sensors mounted on the transporter, the environmental information including a geometry of the transporter; identifying at least one plane within the segmented environment information; identifying a door in the at least one plane; measuring the door based on the segmented environment information; providing a first of the at least one movement command to move the transporter for access to the at least one handle; if the door swings toward the transporter, providing a second one of the at least one movement command as the door opens to move the transporter away from the door a distance based on the measured door; providing a third of the at least one movement command to move the transporter forward through the doorway; A method comprising: (Item 15) Item 15. The method of item 14, wherein the sensor comprises a time-of-flight sensor. (Item 16) 1. A transporter for negotiating with a door, the door including at least one handle, a door swing, and a doorway, the transporter comprising: a sensor processor that determines the hinge side of the door and the direction and angle of the door from the sensor data; a movement processor for generating at least one movement command to move the transporter; a door processor that determines a characteristic of the door, the door processor determining a distance from the transporter to the door, the door processor determining a width of the door, the door processor generating at least one movement command to move the transporter through the door based on the door swing and the door width; A transporter comprising: (Item 17) 1. A method for storing a transporter within a vehicle, the vehicle having a storage compartment, the storage compartment having a door, the method comprising: receiving and segmenting sensor data from sensors mounted on the transporter; identifying at least one plane within the segmented sensor data; identifying a door in the at least one plane; measuring the door, including a width of the door; generating an alert if the door is smaller than a preselected size related to a size of the transporter; positioning the transporter for access to the door, the positioning being based on a width of the door; and generating a signal to open the door; moving the transporter forward through the doorway; generating a signal to close said door; A method comprising: (Item 18) 20. The method of claim 17, further comprising generating a signal to lock the transporter within the vehicle. (Item 19) 13. A method for storing a transporter, the transporter including a sensor, the method comprising: locating at least one storage / charging area by processing sensor data from said sensors; providing at least one movement command to move the transporter from the preselected location to the at least one located storage / charging area; locating a charging dock within the storage / charging area by processing the sensor data; providing at least one movement command to couple the transporter and the charging dock; A method comprising: (Item 20) 1. A method for negotiating with an elevator while maneuvering a transporter, the transporter including a sensor, the elevator including an elevator threshold and an elevator door, the method comprising: locating the elevator by processing sensor data from the sensors; providing at least one first movement command to move the transporter through the elevator doors, over the elevator threshold, and into the elevator; determining a geometry of the elevator by processing the sensor data; providing a second at least one movement command to move the transporter to a floor selection / exit location relative to the elevator threshold; providing at least one third movement command when the elevator doors are open to move the transporter through the elevator doors, across the elevator threshold, and completely out of the elevator; A method comprising: [Brief description of the drawings]
[0018] The present teachings may be more readily understood by reference to the following description taken in conjunction with the accompanying drawings.
[0019] [Figure 1] FIG. 1 is a schematic diagram of a transporter of the present teachings. [Figure 2A] 2A-2D are schematic block diagrams of components of a transporter of the present teachings. [Figure 2B] 2A-2D are schematic block diagrams of components of a transporter of the present teachings. [Figure 2C] 2A-2D are schematic block diagrams of components of a transporter of the present teachings. [Figure 2D] 2A-2D are schematic block diagrams of components of a transporter of the present teachings. [Figure 3A] 3A-3B are schematic block diagrams of the mode processing of the present teachings. [Figure 3B] 3A-3B are schematic block diagrams of the mode processing of the present teachings. [Figure 4] FIG. 4 is a schematic block diagram of the electronic components of the transporter of the present teachings. [Figure 5A] FIG. 5A is a line drawing representation of an exemplary visual interface of the present teachings. [Figure 5B] FIG. 5B is a line drawing representation of an exemplary manual interface of the present teachings. [Figure 6] FIG. 6 is a line drawing representation of an example manual interface switch / button of the present teachings. [Figure 6A] FIG. 6A is a schematic diagram of a user control device case of the present teachings. [Figure 6B1] 6B1 and 6B2 are schematic diagrams of the manual interface cover and UCP assisted connection of the present teachings. [Figure 6B2] 6B1 and 6B2 are schematic diagrams of the manual interface cover and UCP assisted connection of the present teachings. [Figure 6B3] 6B3 and 6B4 are schematic diagrams of a UCP assist holder of the present teachings. [Figure 6B4] 6B3 and 6B4 are schematic diagrams of a UCP assist holder of the present teachings. [Figure 6C1] 6C1 and 6C2 are schematic diagrams of a UCP assisted connection device of the present teachings. [Figure 6C2] 6C1 and 6C2 are schematic diagrams of a UCP assisted connection device of the present teachings. [Figure 6D1] 6D1 and 6D2 are schematic diagrams of a mounting board for a UCP assisted connection device of the present teachings. [Figure 6D2] 6D1 and 6D2 are schematic diagrams of a mounting board for a UCP assisted connection device of the present teachings. [Figure 6D3] 6D3 and 6D4 are schematic diagrams of a UCP assisted connection device mounted on a mounting board for the UCP assisted connection device. [Figure 6D4] 6D3 and 6D4 are schematic diagrams of a UCP assisted connection device mounted on a mounting board for the UCP assisted connection device. [Figure 6D5] 6D5 and 6D6 are schematic diagrams of another configuration of a UCP assisted connection device of the present teachings. [Figure 6D6] 6D5 and 6D6 are schematic diagrams of another configuration of a UCP assisted connection device of the present teachings. [Figure 6E] FIG. 6E is a line drawing of a sensor positioning configuration for a transporter of the present teachings. [Figure 7A] 7A-7E are charts of communication packet information of the present teachings. [Figure 7B] 7A-7E are charts of communication packet information of the present teachings. [Figure 7C] 7A-7E are charts of communication packet information of the present teachings. [Figure 7D] 7A-7E are charts of communication packet information of the present teachings. [Figure 7E] 7A-7E are charts of communication packet information of the present teachings. [Figure 8] FIG. 8 is a graph of a manual interface response template of the present teachings. [Figure 9]FIG. 9 is a control flow diagram of the process of the present teachings. [Figure 10] FIG. 10 is a schematic block diagram of the UCP Assist components of the present teachings. [Figure 11A1] 11A1-11A2 are schematic block diagrams of a method of obstacle detection of the present teachings. [Figure 11A2] 11A1-11A2 are schematic block diagrams of a method of obstacle detection of the present teachings. [Figure 11B] FIG. 11B is a schematic block diagram of the obstacle detection components of the present teachings. [Figure 12A] 12A-12D are computer-generated representations of a transporter configured with a sensor. [Figure 12B] 12A-12D are computer-generated representations of a transporter configured with a sensor. [Figure 12C] 12A-12D are computer-generated representations of a transporter configured with a sensor. [Figure 12D] 12A-12D are computer-generated representations of a transporter configured with a sensor. [Figure 13A] FIG. 13A is a schematic block diagram of the extended stair climbing method of the present teachings. [Figure 13B] FIG. 13B is a schematic block diagram of the components of the enhanced stair climbing system of the present teachings. [Figure 14A1] 14A1-14A2 are schematic block diagrams of a door passage method of the present teachings. [Figure 14A2] 14A1-14A2 are schematic block diagrams of a door passage method of the present teachings. [Figure 14B] FIG. 14B is a schematic block diagram of the door passage components of the present teachings. [Figure 15A] FIG. 15A is a schematic block diagram of a restroom navigation method of the present teachings. [Figure 15B] FIG. 15B is a schematic block diagram of the restroom navigation components of the present teachings. [Figure 16A1]16A1-16A2 are schematic block diagrams of the dynamic storage method of the present teachings. [Figure 16A2] 16A1-16A2 are schematic block diagrams of the dynamic storage method of the present teachings. [Figure 16B] FIG. 16B is a schematic block diagram of the dynamic storage components of the present teachings. [Figure 17A] FIG. 17A is a schematic block diagram of the storage / charging method of the present teachings. [Figure 17B] FIG. 17B is a schematic block diagram of the storage / charging components of the present teachings. [Figure 18A] FIG. 18A is a schematic block diagram of the elevator navigation method of the present teachings. [Figure 18B] FIG. 18B is a schematic block diagram of the elevator navigation components of the present teachings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] Configurations of user control devices of the present teachings are discussed in detail below in connection with a transporter, for example, but not limited to, a wheelchair. Various types of transporters can interface with a user control device. The user control device can communicate with the transporter via an electrical interface, which can facilitate communication and data processing between the user interface device and a controller that can control the movement of the transporter. The user control device can perform automated actions based on the environment in which the transporter operates and the desired movement of a user of the transporter. External applications can enable monitoring and control of the transporter.
[0021] 1, the transporter 120 can include, but is not limited to, a user control device 131, a seat 105, a chassis 104, a base 160, a first wheel 101, a second wheel 102, a third wheel 103, and a cluster 121. The UCD 131 can receive user and sensor inputs and provide that information to the base 160. The UCD 131 can include, but is not limited to, a UCP 130 and a UCP assist 145. The UCP assist can also be positioned independently of the UCP 130 and can be positioned anywhere on the transporter 120, including, but is not limited to, the side and rear of the transporter 120. The base 160 can control, for example, the movement of the wheels 101 and 102, the cluster 121, and the seat 105 based on inputs from the UCD 131 and other factors, including, but not limited to, automated enforcement of requirements for safety and reliability.
[0022] 1, the transporter 120 can operate in functional modes, such as, for example, but not limited to, a standard mode 201 (FIG. 3A) in which the transporter 120 can operate with drive wheels 101 and caster wheels 103, and a standard mode 217 (FIG. 3A) in which the transporter 120 can operate with drive wheels 101 / 102, can be dynamically stabilized through on-board sensors, and can operate with an elevated chassis 104, casters 103, and seat 105. The transporter 120 can also operate in a balance mode 219 (FIG. 3A) in which the transporter 120 can operate with drive wheels 102, can have an elevated seat 105, and can be dynamically stabilized through on-board sensors. The transporter 120 can further operate in a stair mode 215 (FIG. 3A) in which the transporter 120 can ascend and descend stairs using the wheel cluster 121 (FIG. 1) and can be dynamically stabilized. The transporter 120 can still further operate in a remote mode 205 (FIG. 3A) in which the transporter 120 can operate on the drive wheels 101 / 102 and can be unused. The transporter 120 can optionally operate in a docked mode 203 (FIG. 3A) in which the transporter 120 can operate on the drive wheels 101 / 102 and the caster wheels 103, thereby lowering the chassis 104. Some of the modes of the transporter 120 are described in U.S. Patent No. 6,343,664, entitled "Operating Modes for Stair Climbing in Cluster-wheel Vehicle," issued February 2, 2002, which is incorporated herein by reference.
[0023] 2A-2D, the board 160 (FIG. 1) can include, but is not limited to, at least one processor 43A-43D (FIG. 2C / 2D), at least one motor drive 1050, 19, 21, 25, 27, 31, 33, 37 (FIG. 2C / 2D), at least one inertial system 1070, 23, 29, 35 (FIG. 2C / 2D), and at least one power controller 11A / B (FIG. 2B). The board 160 (FIG. 1) can be communicatively coupled to, for example, but not limited to, the UCD 131 (FIG. 2A) via, for example, but not limited to, an electronic communication means 53C and a protocol such as, for example, a controller area network (CAN) bus protocol. The UCD 131 (FIG. 2A) can optionally be communicatively coupled to an electronic device 140A (FIG. 2A), such as, for example, but not limited to, a computer, such as a tablet and a personal computer, a phone, and a lighting system, and can possibly execute an external application 140 (FIG. 4). The UCD 131 (FIG. 2A) can include at least one manual interface, such as, for example, but not limited to, a joystick 133 (FIG. 5B) and at least one push button 141A / B / C (FIG. 6), at least one visual interface, such as, for example, a display (FIG. 5A), and optionally at least one UCP assist 145 (FIG. 4). The UCD 131 (FIG. 2A) can optionally be communicatively coupled to a peripheral control module 1144, a sensor assistance module 1141, and an autonomous control module 1142 / 1143. Communication can be enabled, for example, but not limited to, by a CAN bus protocol and an Ethernet protocol. Other protocols can also be used.
[0024] Continuing to primarily refer to Figures 2A-2D, in some configurations, each at least one processor 43A-43D (Figures 2C / 2D) may include, but is not limited to, at least one cluster motor drive unit 1050, 27 (Figures 2C / 2D), at least one right wheel motor drive unit 19, 31 (Figure 2C), at least one left wheel motor drive unit 21, 33 (Figures 2C / 2D), at least one seat motor drive unit 25, 37 (Figures 2C / D), and at least one inertial sensor pack 1070, 23, 29, 35 (Figures 2C / 2D). The base 160 may further include at least one cluster brake 57, 69 (FIGS. 2C / 2D), at least one cluster motor 83, 89 (FIGS. 2C / 2D), at least one right wheel brake 59, 73 (FIGS. 2C / 2D), at least one left wheel brake 63, 77 (FIGS. 2C / 2D), at least one right wheel motor 85, 91 (FIGS. 2C / 2D), at least one left wheel motor 87, 93 (FIGS. 2C / 2D), at least one seat motor 45, 47 (FIGS. 2C / 2D), at least one seat brake 65, 79 (FIGS. 2C / 2D), at least one cluster position sensor 55, 71 (FIGS. 2C / 2D), and at least one manual brake release device 61, 75 (FIGS. 2C / 2D).
[0025] 2A-2D, the base 160 (FIG. 2C) can be used to drive a cluster 121 (FIG. 1) of wheels 101 / 102 (FIG. 1) forming a ground-contacting module. The ground-contacting module can be mounted on the cluster 121 (FIG. 1), and each wheel 101 / 102 (FIG. 1) of the ground-contacting module can be driven by a wheel motor drive, such as, for example, the right wheel motor drive 19 (FIG. 2C) or the redundant right wheel motor drive B31 (FIG. 2D). The cluster 121 (FIG. 1) can rotate about a cluster axis, and the rotation is governed, for example, by the cluster motor drive 1050 (FIG. 2C) or the redundant cluster motor drive B27 (FIG. 2D). For example, but not limited to, at least one of sensors such as at least one cluster position sensor 55 / 71 (FIGS. 2C / 2D), at least one manual brake release sensor 61 / 75 (FIGS. 2C / 2D), at least one motor current sensor (not shown), and at least one inertial sensor pack 17, 23, 29, 35 (FIGS. 2C / 2D) can sense the status of the transporter 120 (FIG. 1).
[0026] 2A-2D, the processors 43A-43D (FIGS. 2C / 2D) can be electronically coupled to the UCD 131 (FIG. 2A) to receive control inputs and to other controllers to control the peripheral and special functions of the transporter 120 (FIG. 1). The communications 53A-53C (FIG. 2B) between the UCD 131 (FIG. 2A), the power supply controllers 11A / 11B (FIG. 2B), and each of the processors 43A-43D (FIGS. 2C / D) can follow any protocol, including but not limited to the CAN bus protocol. At least one Vbus 95, 97 (FIG. 2B) can connect at least the power supply controllers 11A / B (FIG. 2B) to the board 160 (FIG. 2C) and, through an external Vbus 107 (FIG. 2B), to components external to the board 160 (FIG. 2C). In some configurations, processor A1 43A (FIG. 2C) can be the master of CAN bus A 53A (FIG. 2B). The slaves on CAN bus A 53A (FIG. 2B) can be processor A2 43B (FIG. 2C), processor B1 43C (FIG. 2D), and processor B2 43D (FIG. 2D). In some configurations, processor B1 43C (FIG. 2D) can be the master of CAN bus B 53B (FIG. 2B). The slaves on CAN bus B 53B (FIG. 2B) can be processor B2 43C (FIG. 2D), processor A1 43A (FIG. 2C), and processor A2 43B (FIG. 2C). UCD 131 (FIG. 2A) can be the master of CAN bus C 53C (FIG. 2B). The slaves on CAN bus C 53C (FIG. 2B) can be power supply controller 11A / B (FIG. 2B), processor A1 43A (FIG. 2C), processor A2 43B (FIG. 2C), processor B1 43C (FIG. 2D), and processor B2 43D (FIG. 2D). The master node (either processors 43A-43D (FIG. 2C / D) or UCD 131 (FIG. 2A)) can send data to or request data from the slaves.
[0027] Now referring primarily to Figures 2C / 2D, in some configurations, the base 160 can include a redundant processor set A / B 39 / 41 that can control the cluster 121 (Figure 1) and rotate the drive wheels 101 / 102 (Figure 1). The right / left wheel motor drives A / B 19 / 21, 31 / 33 can drive the right / left wheel motors A / B 85 / 87, 91 / 93 that drive the right and left wheels 101 / 102 (Figure 1) of the transporter 120 (Figure 1). The wheels 101 / 102 (Figure 1) can be coupled to drive together. Turning can be accomplished by driving the left wheel motor A / B 87 / 93 and the right wheel motor A / B 85 / 91 at different ratios. Cluster motor drive A / B 1050 / 27 can drive cluster motor A / B 83 / 89, which can rotate the wheel base in a forward / rearward direction, allowing the transporter 120 (FIG. 1) to remain level while the front wheels 101 (FIG. 1) are higher or lower than the rear wheels 102 (FIG. 1). Cluster motor A / B 83 / 89 can keep the transporter 120 (FIG. 1) level when going up or down a curb, and can repeatedly rotate the wheel base to go up and down stairs. Seat motor drive A / B 25 / 37 can drive seat motor A / B 45 / 47, which can raise or lower the seat 105 (FIG. 1).
[0028] 2C / 2D, the cluster position sensor A / B 55 / 71 can sense the position of the cluster 121 (FIG. 1) of the wheels 101 / 102 (FIG. 1). Signals from the cluster position sensor A / B 55 / 71 and the seat position sensor A / B 67 / 81 can be communicated between the processors 43A-43D and used by the processor set A / B 39 / 41 to determine, for example, signals to be sent to the right wheel motor drive A / B 19 / 31, the cluster motor drive A / B 15 / 27, and the seat motor drive A / B 25 / 37. Independent control of the cluster 121 (FIG. 1) and the drive wheels 101 / 102 (FIG. 1) can enable the transporter 120 (FIG. 1) to operate in several modes, thereby enabling the processors 43A-43D to switch between modes, for example, in response to local terrain. Mode switching can occur, for example, automatically and / or at the request of a user.
[0029] 2C / 2D, the inertial sensor packs 1070, 23, 29, 35 can sense, for example, but not limited to, the orientation of the transporter 120 (FIG. 1). Each processor 43A-43D can include an accelerometer and a gyroscope within the inertial sensor packs 1070, 23, 29, 35. In some configurations, each inertial sensor pack 1070, 23, 29, 35 can include, but is not limited to, four sets of three-axis accelerometers and three-axis gyroscopes. The accelerometer and gyro data can be fused on each of the processors 43A-43D. Each processor 43A-43D can produce a gravity vector that can be used to calculate the orientation and inertial rotation rate of the base 160 (FIG. 1). The fused data can be shared across the processors 43A-43D and can be subject to threshold criteria. The threshold criteria can be used to improve the accuracy of the device orientation and inertial rotation rate. For example, fused data from any of the processors 43A-43D that exceeds a certain threshold can be discarded. The fused data from each of the processors 43A-43D within a preselected limit can be averaged or processed in any other manner, for example, but not limited to. The inertial sensor packs 1070, 23, 29, 35 can include sensors such as, for example, but not limited to, the ST®microelectronics LSM330DLC, or any sensor that provides a 3D digital accelerometer and a 3D digital gyroscope, or any sensor that can further measure gravity and body ratios. The sensor data can be subjected to processing, for example, but not limited to, filtering to improve control of the transporter 120 (FIG. 1).
[0030] Still further and continuing primarily with reference to FIGS. 2C / 2D, the substrate 160 (FIG. 1) may include, for example and without limitation, an ALLEGRO TMSensors may include, but are not limited to, Hall sensors, such as an ACS709 current sensor IC, or any sensor capable of sensing at least a preselected number of motor currents, having bidirectional sensing, having a user selectable overcurrent fault setting, and capable of handling peak currents above a preselected fault limit. Cluster position sensors A / B55 / 71, seat position sensors A / B67 / 81, and manual brake release sensors A / B61 / 75 may include, but are not limited to, Hall sensors.
[0031] Referring now primarily to FIG. 3A, in some configurations, the base processor 100 (FIG. 4) may support at least one operating mode, and the active controller 64A may enable navigation between the modes. The at least one operating mode may include, but is not limited to, a standard mode 201 (described with respect to FIG. 1), an extended mode 217 (described with respect to FIG. 1), a balance mode 219 (described with respect to FIG. 1), a staircase mode 215 (described with respect to FIG. 1), a docked mode 203 (described with respect to FIG. 1), and a remote mode 205 (described with respect to FIG. 1). The service modes may include, but are not limited to, a restore mode 161, a failsafe mode 167 (FIG. 3B), an update mode 169 (FIG. 3B), a self-test mode 171 (FIG. 3B), a calibration mode 163, a power-on mode 207 (FIG. 3B), and a power-off mode 209 (FIG. 3B). With respect to recovery mode 161, if a power outage occurs when transporter 120 (FIG. 1) is not in one of a set of preselected modes, such as, but not limited to, standard mode 201, docked mode 203, or remote mode 205, transporter 120 (FIG. 1) can enter recovery mode 161 to safely reposition transporter 120 (FIG. 1) to the drive position of standard mode 201. During recovery mode 161, infrastructure processor 100 (FIG. 4) can select and activate certain components, such as, for example, seat motor drive A / B 25 / 37 (FIGS. 2C / 2D) and cluster motor drive A / B 1050 / 27 (FIGS. 2C / 2D). Functionality can be limited to, for example, controlling the position of seat 105 (FIG. 1) and cluster 121 (FIG. 1).
[0032] Referring now primarily to FIG. 3B, the transporter 120 (FIG. 1) can be transitioned to a fail-safe mode 167 when the transporter 120 (FIG. 1) can no longer operate effectively. In the fail-safe mode 167, at least some active operations can be stopped to protect against potentially erroneous or uncontrolled movement. The transporter 120 (FIG. 1) can be transitioned from a standard mode 201 (FIG. 3A) to an update mode 169 to enable communication with an external application 140 (FIG. 4), which may be running outside of the base 160 (FIG. 1), for example, but not by way of limitation. The transporter 120 (FIG. 1) can be transitioned to a self-test mode 171 when the transporter 120 (FIG. 1) is first powered up. In the self-test mode 171, the electronics within the base 160 (FIG. 1) can perform self-diagnostics and can synchronize with each other. In some configurations, system self-tests may be performed to check the integrity of the system that is not easily testable during normal operation, such as, for example, a memory integrity verification test and a disable circuit test. While in self-test mode 171, operational functions may be disabled.
[0033] 4, the transporter control system 200A may include at least one base processor 100 and at least one power controller 11 that may bidirectionally communicate with a system serial bus messaging system 130F via a serial bus 143, but are not limited to this. The system serial bus messaging 130F may bidirectionally communicate with an I / O interface 130G, an external communication 130D, a UCP 130, and a UCP assist 145. The UCP 130 and the UCP assist 145 may access the peripherals, processors, and controllers through interface modules, which may include, but are not limited to, an input / output (I / O) interface 130G, a system serial bus (SSB) messaging interface 130F, and an external communication interface 130D. In some configurations, the I / O interface 130G may transmit / receive messages to / from at least one of, for example, but not limited to, an audio interface 150, an electronic interface 149, a manual interface 153, and a visual interface 151. The audio interface 150 can transmit data from, for example, the UCP 130 to an audio device, such as, for example, a speaker, which may, for example, issue an alert when the transporter 120 (FIG. 1) requires attention. The electronic interface 149 can transmit / receive messages to / from, for example, but not limited to, the sensors 147. The sensors 147 can include, but are not limited to, time-of-flight cameras and other sensors. The manual interface 153 can transmit / receive messages to / from, for example, but not limited to, the joystick 133 (FIG. 5B) and / or the switches / buttons 141 / B / C (FIG. 6), and / or information lighting, such as LED lights, and / or the display 137 (FIG. 5A), having, for example, a touch screen. The UCP 130 and the UCP assist 145 can transmit / receive information to / from the I / O interface 130G, the system serial bus messaging 130F, the external communications 130D, and each other.
[0034] 4, system serial bus interface 130F can enable communication between UCP 130, UCP assist 145, base processor (PBP) 100 (also shown, for example, as processor A1 43A (FIG. 2C), processor A2 43B (FIG. 2C), processor B1 43C (FIG. 2D), and processor B2 43D (FIG. 2D)), and power controller 11 (also shown, for example, as power controller A11A (FIG. 2B) and power controller B11B (FIG. 2B)). Messages described herein can be exchanged between UCP 130, UCP assist 145, and PBP 100 using, for example, but not by way of limitation, system serial bus 143. The external communication interface 130D can enable communication between, for example, the UCP 130, the UCP Assist 145, and the external application 140 using wireless communication 144, such as, for example, but not limited to, BLUETOOTH® technology. The UCP 130 and the UCP Assist 145 can transmit / receive messages to / from sensors 147, which can be used to enable automatic and / or semi-automatic control of the transporter 120 (FIG. 1).
[0035] 5A, 5B, and 6, the switches and buttons 141A / B / C (FIG. 6) associated with the transporter 120 (FIG. 1) can generate signals to the I / O interface 130G (FIG. 4) upon activation. The signals can be decoded and debounced, for example, by the UCP 130 (FIG. 4) and / or the PBP 100 (FIG. 4). Examples of functions that can be enabled by the switches / buttons 141A / B / C (FIG. 6) can include, but are not limited to, seat 105 (FIG. 1) height, seat 105 (FIG. 1) tilt, mode selection, drive settings menu selection, joystick 133 (FIG. 5B) override, selection confirmation, power off request, alarm status acknowledgement, and horn activation. Alerts, such as flashing icons, can be provided to bring a user's attention to a condition. The conditions may include, but are not limited to, low battery, service required, temperature out of range, manually disabled parking brake that may prevent user requested power off, and critical faults, warnings, or alerts. The switches / buttons 141A / B / C (FIG. 6) may have functionality that is context dependent and may have secondary functionality, for example, if the switch / button 141A / B / C (FIG. 6) is pressed for a period of time. Certain switches / buttons 141A / B / C (FIG. 6) may be disabled, for example, when a mode change occurs and / or a battery charger is connected. When the joystick 133 (FIG. 5B) is disabled, certain other functions may be disabled, for example, but are not limited to, mode selection, drive menu selection, and adjustment of the seat 105 (FIG. 1). Disabled switches / buttons 141A / B / C (FIG. 6) may be re-enabled under certain conditions, for example, when the associated switch / button 141A / B / C (FIG. 6) is released. In some configurations, button 141C (FIG. 6) can provide a way to indicate power on and can also provide an indication of device status and / or a means of acknowledging device status. In some configurations, button 141B (FIG. 6) can provide, for example, emergency flashers and / or a power on flasher.In some configurations, button 141A (FIG. 6) may provide a means to activate the horn and / or confirm a selection.
[0036] Referring now primarily to FIG. 6A, the UCD holder 133A can house a manual and visual interface, such as, for example, a joystick 133 (FIG. 5B), a display 137 (FIG. 5A), and associated electronics. A connector 133C (FIG. 6B2) can allow for connection to a UCP assist 145 (FIG. 4). In some configurations, the UCP assist holder 145A can be attached to the visual / manual interface holder 145C without tools. The UCP assist holder 145A can house the UCP assist 145, which can include a sensor 147A (FIG. 12A). The sensor 147A (FIG. 12A) can include, but is not limited to, a TEXAS INSTRUMENTS® OPT8241 time-of-flight sensor, or any device that can provide a three-dimensional location of data sensed by the sensor 147A (FIG. 12A). The UCP assist holder 145A and connector 133C (FIG. 6B2) may be located anywhere on the transporter 120 (FIG. 1) and may not be limited to being mounted on the visual / manual interface holder 145C.
[0037] 6B1 and 6B2, the manual / visual interface holder 145C can include, but is not limited to, a visual interface viewing window 137A (FIG. 6B1) available on a first side 133E (FIG. 6B1) of the manual / visual interface holder 145C, and a manual interface mounting hole 133B (FIG. 6B1). A connector 133C (FIG. 6B2) can be provided on a second side 133D (FIG. 6B2) of the manual / visual interface holder 145C. Any of the viewing window 137A (FIG. 6B1), the manual interface mounting hole 133B (FIG. 6B1), and the connector 133C (FIG. 6B2) can be located on any portion of the manual / visual interface holder 145C, or can be absent entirely. The manual / visual interface holder 145C, visual interface viewing window 137A (FIG. 6B1), manual interface mounting hole 133B (FIG. 6B1), and connector 133C (FIG. 6B2) can be of any size. The manual / visual interface holder 145C can be constructed from any material suitable for mounting to the visual interface viewing window 137A (FIG. 6B1), manual interface mounting hole 133B (FIG. 6B1), and connector 133C (FIG. 6B2). The angle 145M can be associated with various orientations of the UCD holder 133A and can therefore be of various values. The UCD holder 133A can have a fixed orientation or can be hinged.
[0038] 6B3 and 6B4, the UCP assist holder 145A can include, but is not limited to, a filter hole 136G and a lens hole 136F that provide visibility to, for example, but is not limited to, a time-of-flight sensor optical filter and lens, such as, but is not limited to, a TEXAS INSTRUMENTS® OPT8241 3D time-of-flight sensor. The UCP assist holder 145A can be of any shape and size and can be constructed from any material depending on the mounting location on the transporter 120 and, for example, the sensor, processor, and power supply provided in the UCP assist holder 145A. The rounded edges on the holes 136G and 136F, on the casing 136E, and on the holder 145A can be replaced by any shape of edge. The hole 136H can house the control electronics.
[0039] 6C1 and 6C2, the connector 133C can include, but is not limited to, connector leads 133G (FIG. 6C1) on a first side 133H (FIG. 6C1) of the connector and connector pins 133F that can protrude from a second side 133I (FIG. 6C2) of the connector. The connector leads 133G (FIG. 6C1) and connector pins 133F can be any size and shape, and there can be any number of connector leads 133G (FIG. 6C1) and connector pins 133F. Additionally, there can be any number of connectors 133C.
[0040] Now referring primarily to FIGS. 6D1 and 6D2, the mounting board 134J can include, but is not limited to, pin holes 134D, mounting holes 134C, and alignment features 134B. The first side 134A of the mounting board can be the same as the second side 134E of the mounting board, or the first side 134A of the mounting board can have different features than the second side 134E of the mounting board. The mounting holes 134C, pin holes 134D, and alignment features 134B can be of any size and / or shape, and there can be any number of mounting holes 134C, pin holes 134D, and alignment features 134B. The mounting board 134J can be used to mount the connector 133C (FIGS. 6C1 / 6C2). In some configurations, the mounting board 134J can include pin holes 134D that can accommodate connector pins 133F (FIGS. 6C1 / 6C2). The mounting board 134J can be provided in multiple parts and shapes for receiving the connector 133C (FIGS. 6C1 / 6C2).
[0041] 6D3 and 6D4, the connector pins 133F can be inserted into the pin holes 134D to mount the connector 133C on the mounting board 134J. The connector leads 133G can protrude from a first side 134A (FIG. 6D3) of the mounting board, and the connector pins 133F can protrude from a second side 134E (FIG. 6D4) of the mounting board. The connector 133C can be positioned anywhere on the mounting board 134J and can cross multiple mounting boards 134J. Multiple connectors 133C can be mounted on the mounting board 134J.
[0042] 6D5 and 6D6, in some configurations, the second configuration connector 139D can be mounted on the mounting board 134J (FIG. 6D1) and can mount the UCP assist holder 145A (FIG. 6A). The arcuate conductor 139A on the first side 139E of the second configuration connector can form a hole 139B into which a mating connector (not shown) from the UCP assist holder 145A (FIG. 6A) can be inserted. The second side 139F of the second configuration connector can include a protrusion of the second configuration connector pin 139C, which can be inserted into the mounting board 134J (FIG. 6D1).
[0043] Referring now primarily to FIG. 6E, the transporter 120 (FIG. 1) can be mated with any number of sensors 147 (FIG. 4) in any configuration. In some configurations, some of the sensors 147 (FIG. 4) can be mounted on the transporter back 122 to accomplish specific goals, such as backup safety. A stereo color camera / illuminator 122A, an ultrasonic beam range finder 122B, a time-of-flight camera 122D / 122E, and a single-point LIDAR sensor 122F can be mounted and can cooperate to sense obstacles behind the transporter 120 (FIG. 1), for example, but not limited to. The PBP 100 (FIG. 4) and / or the UCP assist 145 (FIG. 4) can receive messages, which can include information from the cameras and sensors, and enable the transporter 120 (FIG. 1) to react to things that may occur outside the user's field of view. The transporter 120 (FIG. 1) can also include a reflector 122C, which can be optionally fitted with additional sensors. The stereo color camera / light 122A can also be used as a tail light. Other types of cameras and sensors can also be mounted on the transporter 120 (FIG. 1). Information from the cameras and sensors can be used to enable a smooth transition to balance mode 219 (FIG. 3A) by providing information to UCP assist 145 (FIG. 4) and enabling UCP assist 145 (FIG. 4) to locate any obstacles that may impede the transition to balance mode 219 (FIG. 3A).
[0044] Referring now primarily to FIG. 7A, the SSB 143 (FIG. 4) can provide communication, for example, through the use of the CAN bus protocol. Devices connected to the SSB 143 (FIG. 4) can be programmed to respond to / listen for specific messages received, processed, and transmitted by the SSB messaging 130F (FIG. 4). The messages can include packets that can include, but are not limited to, 8 bytes of data and a CAN bus device identification that can identify the source of the packet. Devices receiving CAN bus packets can ignore invalid CAN bus packets. When an invalid CAN bus packet is received, the receiving device can take alternative actions, for example, depending on the current mode of the transporter 120 (FIG. 1), the previous CAN bus message, and the receiving device. The alternative actions can, for example, maintain the stability of the transporter 120 (FIG. 1). The bus master of the SSB 143 (FIG. 4) can transmit a master synchronization packet 901 to establish a bus alive sequence on a frame basis and synchronize time references.
[0045] Referring now primarily to FIG. 7B, the user control panel packet #1903 (FIG. 7A) can include 8 bytes and can have, for example, a packet format 701. The packet format 701 can include, but is not limited to, a status 701A, an error device identification 701B, a requested mode 701C, an out of control byte 701D, a commanded speed 701E, a commanded turn rate 701F, a seat control byte 701G, and a system data 701H. The status 701A can include, but is not limited to, possibilities such as self test in progress, device OK, non-fatal device failure (data OK), and fatal device failure, where the receiving device may ignore the data in the packet. If the UCP 130 receives, for example, a device failure status, the UCP 130 can post the error to, for example, a graphical user interface (GUI) on the display 137 (FIG. 5A). The error device ID 701B can include a logical ID of the device for which the received communication was determined to be erroneous. The Error Device ID 701B may be set to zero when no error is received.
[0046] Referring now primarily to FIG. 7C, the requested mode code 701C (FIG. 7B) can be defined such that a single bit error may not indicate another valid mode. For example, the mode codes can include, but are not limited to, self-test, standard, extended, stairs, balance, docked, remote, calibration, update, power off, power on, fail-sail, restore, flashing light, door, dynamic storage, static storage / charging, restroom, elevator, and extended stairs (the meanings of which are discussed herein). The requested mode code 701C can indicate whether the mode being requested should be processed to either (1) maintain the current mode or perform an authorized mode change, or (2) enable a situation-dependent process. In some configurations, a special situation can request automatic control of the transporter 120 (FIG. 1). For example, the transporter 120 (FIG. 1) can automatically transition from the stairs mode 215 (FIG. 3A) to the extended mode 217 (FIG. 3A) when the transporter 120 (FIG. 1) reaches the top of a staircase structure. In some configurations, the PBP 100 (FIG. 4) and / or the UCP assist 145 (FIG. 4) can modify the response of the PBP 100 (FIG. 4) to commands from the joystick 133 (FIG. 1), for example, but not by way of limitation, by setting the transporter 120 (FIG. 1) to a particular mode. In some configurations, the transporter 120 (FIG. 1) can be automatically set to a low-speed drive mode when the transporter 120 (FIG. 1) transitions from the stair mode 215 (FIG. 3A). In some configurations, the joystick 133 (FIG. 1) can be disabled when the transporter 120 (FIG. 1) automatically transitions from the stair mode 215 (FIG. 3A) to the extended mode 217 (FIG. 3A). Once a mode is selected by either UCP assist 145 (FIG. 4), such as, but not limited to, UCP 130 (FIG. 4) through user input, and / or PBP 100 (FIG. 4), mode availability can be determined based, at least in part, on current operating conditions.
[0047] Continuing to refer primarily to FIG. 7C, in some configurations, the user can be alerted if a transition is not allowed from the current mode to a user-selected mode. Certain modes and mode transitions can require user notification and possibly user assistance. For example, adjustment of the seat 105 (FIG. 1) may be required when positioning the transporter 120 (FIG. 1) for determination of the center of gravity of the transporter 120 (FIG. 1) along with the load on the transporter 120 (FIG. 1). The user can be prompted to perform a specific action based on the current mode and / or the mode in which the transition may occur. In some configurations, the transporter 120 (FIG. 1) can be configured for, for example, but not limited to, a fast, medium, medium decay, or slow speed template. The speed of the transporter 120 (FIG. 1) can be modified, for example, by using a speed template 700 (FIG. 8) that associates the output 703 (FIG. 8) (and wheel commands) with a joystick displacement 702 (FIG. 8).
[0048] 7D, the out of control byte 701D (FIG. 7B) can include bit definitions such as, but not limited to, power off OK 801A, drive select 801B, emergency power off request 801C, calibration status 801D, mode restrictions 801E, user training 801F, and joystick centering 801G. In some configurations, power off OK 801A can be defined to zero if power off is not currently enabled, drive select 801B can be defined to specify motor drive 1 (bit 6=0) or motor drive 2 (bit 6=1). In some configurations, emergency power off request 801C can be defined to indicate whether the emergency power off request is normal (bit 5=0) or an emergency power off request sequence is in progress (bit 5=1), and calibration status 801D can be defined to indicate a request for user calibration (bit 4=1). In some configurations, Mode Restrictions 801E can be defined to indicate whether there is a restriction for entering a particular mode. If the mode can be entered without restriction, bit 3 can be zero. If a restriction for entering the mode exists, for example but not limited to, a balance critical mode may require some restriction to maintain the safety of passengers on the transporter 120 (FIG. 1), bit 3 can be 1. User Training 801F can be defined to indicate whether user training is possible (bit 2=1) or not possible (bit 2=0), and Joystick Centering 801G can be defined to indicate whether the joystick 133 (FIG. 1) is centered (bits 0-1=2) or not centered (bits 0-1=1).
[0049] Referring again primarily to FIG. 7B, the commanded velocity 701E can be a value representing, for example, a forward or reverse velocity. A forward velocity can be, for example, a positive value and a reverse velocity can be a negative value. The commanded turn rate 701F can be a value representing a left or right commanded turn rate. A left turn can be a positive value and a right turn can be a negative value. The value can represent the speed difference between the left and right of the wheels 101 / 102 (FIG. 1) scaled equally to the commanded velocity 701E.
[0050] Referring again primarily to FIG. 7D, the joystick 133 (FIG. 1) may have multiple redundant hardware inputs. For example, signals such as commanded velocity 701E (FIG. 7B), commanded turn rate 701F (FIG. 7B), and joystick centering 801G may be received and processed. The commanded velocity 701E (FIG. 7B) and commanded turn rate 701F (FIG. 7B) may be determined from a first one of the multiple hardware inputs, and the joystick centering 801G may be determined from a second one of the hardware inputs. The value of the joystick centering 801G may indicate when a non-zero commanded velocity 701E (FIG. 7B) and a non-zero commanded turn rate 701F (FIG. 7B) are valid. For example, fault conditions for the joystick 133 (FIG. 1) in the X and Y directions may be detected. For example, each axis of the joystick 133 (FIG. 1) may be associated with dual sensors. Each sensor pair input (X (commanded velocity 701E (FIG. 7B)) and Y (commanded rate of turn 701F (FIG. 7B)) can be associated with an independent A / D converter, each with a voltage reference channel check input. In some configurations, commanded velocity 701E (FIG. 7B) and commanded rate of turn 701F (FIG. 7B) can be held at zero by a secondary input to avoid misalignment. If joystick centering 801G is within a minimum deadband or the joystick 133 (FIG. 1) is faulted, the joystick 133 (FIG. 1) can be indicated as a centering state. The deadband can indicate the amount of displacement of the joystick 133 (FIG. 1) that can occur before a non-zero output from the joystick 133 (FIG. 1) can appear. The deadband range can be set to include the electrical center position, which can be, for example, but not limited to, 45%-55% of the defined signal range.
[0051] Now referring primarily to FIG. 7E, the seat control byte 701G (FIG. 7B) can convey a seat adjustment command. The frame tilt command 921 can include values such as, for example, disabled, tilt forward, tilt back, and idle. The seat height command 923 can include values such as, for example, disabled, seat down, seat up, and idle.
[0052] Referring again to FIG. 7A, the user control packet 905 may include headers, message IDs, and data for messages traveling primarily to and from the external application 140 (FIG. 4), for example, but not limited to, over a BLUETOOTH connection. The PBP packet 907 may include data originated by the PBP 100 (FIG. 4) and directed to the PSC 11 (FIG. 4). The PBP A1 43A (FIG. 2C), for example, may be designated as the master of the SSB 143 (FIG. 4), and the PBP B1 43C (FIG. 2D), for example, may be designated as the secondary master of the SSB 143 (FIG. 4) when the PBP A1 43A (FIG. 2C) is no longer transmitting on the bus. The master of the SSB 143 (FIG. 4) may transmit the master synchronization packet 901 at a periodic rate, for example, but not limited to, every 20 ms + / - 1%. Devices communicating using SSB 143 (FIG. 4) can synchronize the transmission of messages to the start of a master synchronization packet 901.
[0053] Now referring primarily to FIG. 8, the joystick 133 (FIG. 1) can be configured to have different transfer functions for use under different conditions, for example, according to the user's capabilities. The velocity template (transfer function) 700 shows an example relationship between the physical displacement 702 of the joystick 133 (FIG. 1) and the output 703 of the joystick 133 (FIG. 1) after transfer function processing. The forward and rearward advancement of the joystick 133 (FIG. 1) can be interpreted as a forward longitudinal request and a rearward longitudinal request, respectively, from the perspective of the user at the seat 105 (FIG. 1), and can be equivalent to the X request value of the command velocity 701E (FIG. 7). The left and right advancement of the joystick 133 (FIG. 1) can be interpreted as a left turn request and a right turn request, respectively, from the perspective of the user at the seat 105 (FIG. 1), and can be equivalent to the Y request value of the command turn rate 701F. The joystick output 703 can be modified during certain conditions, such as, but not limited to, battery voltage conditions, seat 105 (FIG. 1) height, mode, joystick 133 (FIG. 1) fault conditions, and when a speed correction is requested by the PBP 100 (FIG. 4). The joystick output 703 can be ignored and the joystick 133 (FIG. 1) can be considered to be in a centering state, such as, but not limited to, when a mode change occurs, or while in update mode 169 (FIG. 3B), or when a battery charger is connected, or in stair mode, or when the joystick 133 (FIG. 1) is disabled, or under certain fault conditions.
[0054] With continued reference primarily to FIG. 8, the transporter 120 (FIG. 1) can be configured to suit a particular user. In some configurations, the transporter 120 (FIG. 1) can be tailored to user capabilities, for example, by setting speed templates and mode limits. In some configurations, the transporter 120 (FIG. 1) can receive commands from an external application 140 (FIG. 4) running on a device such as, for example, but not limited to, a mobile phone, a computer tablet, and a personal computer. The commands can provide, for example, default and / or dynamically determinable settings for configuration parameters. In some configurations, the user and / or attendant can configure the transporter 120 (FIG. 1).
[0055] 9, any of the UCP 130, UCP Assist 145, and / or PBP 100 may execute a power-on and processing sequence when the UCP 130 (FIG. 4) and / or PBP 100 (FIG. 4) and / or UCP Assist 145 (FIG. 4) receives a power-on indication 1017. The power-on process 1005 may include, for example, but not limited to, an integrity check that may be performed on stored data and various indicators. Memory tests may be performed, system and configuration parameters may be established in memory, and an operational ready state may be indicated, for example, but not limited to, by a lit LED. After the power-on process 1005, a transition may follow to a main loop process 1001 where sensor data 1003 may be received and processed, input messages 1027 may be received, and output messages 1013 may be generated periodically, for example, but not limited to, once per frame of the SSB 143 (FIG. 4). Device data 1009 and communication information 1011 can be accessed. Device data 1009 can include, but is not limited to, device status, which may display, for example, device diagnostic data. In some configurations, communication with an external application 140 (FIG. 4) can be provided to gather information, such as, but not limited to, application code version numbers, application code CRC values, and protocol map compatibility information. The UCP 130 (FIG. 4), UCP assist 145 (FIG. 4), and / or PBP 100 (FIG. 4) can execute a power down sequence in response to receiving a power off request 1015. For example, but not limited to, ongoing activities, such as, but not limited to, data logging and receiving data from, for example, switches / buttons 141A / B / C (FIG. 6) and joystick 133 (FIG. 1), can be disabled to provide a consistent termination. Configuration, usage, service, security, and other information can be accumulated and stored during the power off process 1007.
[0056] 10, the UCP Assist 145 can provide the user with enhanced functionality, such as, but not limited to, assisting the user to avoid obstacles, pass through doors, ascend and descend stairs, enter elevators, and park / carry the transporter 120 (FIG. 1). In general, the UCP Assist 145 can receive user input (e.g., UI data 633) and / or input from the PBP 100 (FIG. 4), such as, but not limited to, through messages from the user interface devices and sensors 147. The UCP Assist 145 can further receive sensor input, such as, but not limited to, through a sensor processing system 661. The output from the UI data 633 and the sensor processing system 661 can inform the command processor 601, for example, to invoke an automatically or manually selected mode. The command processor 601 can pass the output from the UI data 633 and the sensor processing system 661 to a processor, which can enable the invoked mode. The processor may generate the movement commands 630 based on at least the previous movement commands 630 , the UI data 633 , and output from the sensor processing system 661 .
[0057] 10, the UCP assist 145 can include, but is not limited to, a command processor 601, a movement processor 603, a simultaneous localization and mapping (SLAM) processor 609, a point cloud library (PCL) processor 611, a geometry processor 613, and an obstacle processor 607. The command processor 601 can receive user interface (UI) data 633 from a message bus. The UI data 633 can include, but is not limited to, signals from the joystick 133 (FIG. 1) that provide an indication of, for example, a desired direction of movement and speed of the transporter 120 (FIG. 1). The UI data 633 can also include selections of alternate modes, etc., into which the transporter 120 (FIG. 1) can be transitioned. In some configurations, in addition to the modes described with respect to Figures 3A / 3B, the UCP assist 145 can process mode selections such as, but not limited to, door mode 605A, restroom mode 605B, extended staircase mode 605C, elevator mode 605D, dynamic parking mode 605E, and static storage / charge mode 605F. Any of these modes can include a move to location mode, or a user can instruct the transporter 120 (Figure 1) to move to a location. The message bus 54 can receive control information for the transporter 120 (Figure 1) in the form of UI data 633, and can receive results of processing performed by the UCP assist 145 in the form of commands, such as move commands 630, which can include, but are not limited to, speed and direction. The movement commands 630 can be provided to the PBP 100 (FIG. 4), which can transmit this information to the wheel motor drives 19 / 21 / 31 / 33 (FIG. 2C / D) and the cluster motor drives 1050 / 27 (FIG. 2C / D) by way of the message bus 54. The movement commands 630 can be determined by the movement processor 603 based on information provided by the mode specific processors. The mode specific processors can determine the mode dependent data 657 based on information provided through the sensor handling processor 661, among other things.
[0058] Continuing to primarily refer to FIG. 10, the sensor handling processor 661 can include, but is not limited to, the transporter geometry processor 613, the PCL processor 611, the SLAM processor 609, and the obstacle processor 607. The movement processor 603 can provide movement commands 630 to the sensor handling processor 661 and provide the information necessary to determine future movements of the transporter 120 (FIG. 1). The sensors 147 can provide environmental information 651, which can include, for example, but is not limited to, geometric information about the obstacles 623 and the transporter 120 (FIG. 1). In some configurations, the sensors 147 can include at least one time-of-flight sensor, which can be mounted anywhere on the transporter 120 (FIG. 1). Multiple sensors 147 can be mounted on the transporter 120 (FIG. 1). The PCL processor 611 can collect and process the environmental information 651 and produce PCL data 655. PCL, a group of code libraries for processing 2D / 3D image data, can, for example, assist in processing the environment information 651. Other processing techniques can also be used.
[0059] Continuing to primarily refer to FIG. 10, the transporter geometry processor 613 can receive transporter geometry information 649 from the sensor 147, can perform any processing necessary to prepare the transporter geometry information 649 for use by the mode-dependent processor, and can provide the processed transporter geometry information 649 to the mode-dependent processor. The geometry of the transporter 120 (FIG. 1) can be used to automatically determine whether the transporter 120 (FIG. 1) can fit into and / or through a space, such as, for example, a staircase structure and a door. The SLAM processor 609 can determine navigation information 653 based on, for example, but not limited to, the UI data 633, the environmental information 651, and the movement commands 630. The transporter 120 (FIG. 1) can navigate, at least in part, within a path set by the navigation information 653. The obstacle processor 607 can locate an obstacle 623 and a distance 621 to the obstacle 623. The obstacle 623 can include, but is not limited to, doors, stairs, cars, and miscellaneous features near the path of the transporter 120 (FIG. 1).
[0060] 11A1 and 11A2, a method 650 for processing at least one obstacle 623 (FIG. 11B) while navigating a transporter 120 (FIG. 1) may include, without limitation, a step 1151 (FIG. 11A1) of receiving at least one movement command 630 (FIG. 11B), a step 1153 (FIG. 11A1) of receiving and segmenting PCL data 655 (FIG. 11B), a step 1155 (FIG. 11A1) of identifying at least one plane in the segmented PCL data 655 (FIG. 11B), and a step 1157 (FIG. 11A1) of identifying at least one obstacle 623 (FIG. 11B) in the at least one plane. The method 650 may further include a step 1159 (FIG. 11A1) of determining at least one situation identifier 624 (FIG. 11B) based on at least the at least one obstacle, the UI data 633 (FIG. 11B), and the movement command 630 (FIG. 11B), and a step 1161 (FIG. 11A1) of determining a distance 621 (FIG. 11B) between the transporter 120 (FIG. 1) and the at least one obstacle 623 (FIG. 11B) based on at least the at least one situation identifier 624 (FIG. 11B). The method 650 may also include a step 1163 (FIG. 11A1) of accessing at least one authorization command associated with the distance 621 (FIG. 11B), the at least one obstacle 623 (FIG. 11B), and the at least one situation identifier 624 (FIG. 11B). The method 650 may still further include a step 1163 (FIG. 11A1) of accessing at least one automatic response to the at least one authorized command, a step 1167 (FIG. 11A2) of mapping the at least one movement command 630 (FIG. 11B) to one of the at least one authorized command, and a step 1169 (FIG. 11A2) of providing the at least one movement command 630 (FIG. 11B) and the at least one automatic response associated with the mapped authorized command to a mode-dependent processor.
[0061] 11A1 and 11A2, the at least one obstacle 623 (FIG. 11B) can optionally include at least one stationary object and / or at least one moving object. The distance 621 (FIG. 11B) can optionally include a fixed amount and / or a dynamically varying amount. The at least one movement command 630 (FIG. 11B) can optionally include a follow command, a command to pass the at least one obstacle at least once, a command to move past the at least one obstacle, and at least one obstacle non-follow command. The method 650 can optionally include storing the obstacle data 623 (FIG. 11B) and enabling access to the stored obstacle data by an external system of the transporter 120 (FIG. 1), for example, stored in the cloud storage 607G (FIG. 11B) and / or the local storage 607H (FIG. 11B). The PCL data 655 (FIG. 11B) may optionally include sensor data 147 (FIG. 10). The method 650 may optionally include collecting sensor data 147 (FIG. 10) from at least one time-of-flight sensor mounted on the transporter 120 (FIG. 1), analyzing the sensor data 147 (FIG. 10) using a point cloud library (PCL), tracking at least one moving object using simultaneous localization and mapping (SLAM) with detection and tracking of moving objects (DATMO) based on the location of the transporter 120 (FIG. 1), identifying at least one plane in the obstacle data 623 (FIG. 11B) using, for example, but not limited to, random sample consensus and the PCL library, and providing at least one automated response associated with the mapped permission command to a mode-dependent processor. The method 650 may also optionally include receiving a resume command and, following the resume command, providing at least one movement command 630 (FIG. 11B) and at least one automatic response associated with the mapped authorization command to the mode-dependent processor. The at least one automatic response may optionally include a speed control command.
[0062] 11B, an obstacle processor 607 for processing at least one obstacle 623 while navigating the transporter 120 (FIG. 1) may include, without limitation, a nav / PCL data processor 607F that receives and segments PCL data 655 from the PCL processor 611, identifies at least one plane in the segmented PCL data 655, and identifies at least one obstacle 623 in the at least one plane. The obstacle processor 607 may further include a distance processor 607E that determines at least one situation identifier 624 based on at least the UI data 633, the at least one movement command 630, and the at least one obstacle 623. The distance processor 607E may determine a distance 621 between the transporter 120 (FIG. 1) and the at least one obstacle 623 based at least on the at least one situation identifier 624. The moving object processor 607D and / or the stationary object processor 607C can access at least one permitted command associated with the distance 621, the at least one obstacle 623, and the at least one situation identifier 624. The moving object processor 607D and / or the stationary object processor 607C can access at least one automatic response associated with the at least one permitted command from an automatic response list 627. The moving object processor 607D and / or the stationary object processor 607C can access at least one movement command 630, including, for example, a speed / signal command and a direction command / signal, and map one of the at least one movement command 630 and the at least one permitted command. The moving object processor 607D and / or the stationary object processor 607C can provide the at least one movement command 630 and at least one automatic response associated with the mapped permitted command to the mode dependent processor.
[0063] 11B, the stationary object processor 607C can optionally perform any special processing required when at least one stationary object is encountered, and the moving object processor 607D can optionally perform any special processing required when at least one moving object is encountered. The distance processor 607E can optionally process the distance 621, which can be a fixed and / or dynamically varying quantity. The at least one movement command 630 can optionally include a follow command, a pass command, a go by command, a move to a fixed position command, and a not follow command. The navigation / PCL processor 607F can optionally store the obstacles 623, for example, but not limited to, in the local storage device 607H and / or on the storage cloud 607G, and can enable the stored obstacles 623 to be accessed by an external system of the transporter 120 (FIG. 1), such as, for example, but not limited to, the external application 140 (FIG. 4). The PCL processor 611 can optionally collect sensor data 147 (FIG. 10) from at least one time-of-flight camera mounted on the transporter 120 (FIG. 1) and can analyze the sensor data 147 (FIG. 10) using a point cloud library (PCL) to provide PCL data 655. The moving object processor 607D can optionally use navigation information 653 collected by the simultaneous localization and mapping (SLAM) processor 609 based on the location of the transporter 120 (FIG. 1) to track at least one moving object, for example, but not limited to, using random sample consensus and the PCL library, and can provide at least one movement command 630 to the mode-dependent processor based on at least one automatic response associated with the mapped clearance command. The obstacle processor 607 can optionally receive a resume command and provide at least one movement command 630 to the mode-dependent processor based on at least one automatic response associated with the mapped clearance command following the resume command. At least one of the automatic responses can optionally include a rate control command.For example, if the joystick 133 (FIG. 1) indicates a direction that may position the transporter 120 (FIG. 1) in a collision course with an obstacle 623, such as a wall, the at least one automatic response may include speed control to protect the transporter 120 (FIG. 1) from the collision. The at least one automatic response may be overridden by a reverse user command, e.g., the joystick 133 (FIG. 1) may be disengaged and movement of the transporter 120 (FIG. 1) may be stopped. The joystick 133 (FIG. 1) may then be re-engaged to resume movement of the transporter 120 (FIG. 1) toward the obstacle 623.
[0064] 12A-12D, environmental information 651 (FIG. 10) can be received from sensors 147 (FIG. 10). Any of the PBP 100 (FIG. 4), the UCP 130 (FIG. 4), and / or the UCP assist 145 (FIG. 10) can process the process environmental information 651 (FIG. 10). In some configurations, the PCL processor 611 (FIG. 10) can use the sensors 147 (FIG. 10) to process the environmental information 651 (FIG. 10), i.e., point cloud library (PCL) functions accordingly, for example. As the transporter 120 (FIG. 1) moves along the travel path 2001 (FIG. 12D) around the potential obstacle 2001A, the sensor 147 (FIG. 10) can detect a box 2005 (FIG. 12C-12D) that may include data from the sensor 147 (FIG. 10), which may take the shape of a point cloud, i.e., a truncated cone 2003 (FIG. 12B-12D), in response. For example, but not limited to, a sample consensus method from PCL, such as, but not limited to, a random sample consensus method, can be used to find a plane between the point clouds. Any of the UCP 130 (FIG. 4), UCP Assist 145 (FIG. 10), and PBP 100 (FIG. 4) can create a projected cloud and determine point cloud correspondences from which the center of gravity of the projected cloud can be determined. The central reference point 148 can be used to determine the location of the environmental condition relative to the transporter 120. For example, whether the transporter 120 is moving toward or away from an obstacle or the location of a door hinge relative to the transporter 120 can be determined based on the location of the central reference point 148. The sensor 147 (FIG. 10) can include, for example, a time-of-flight sensor 147A.
[0065] 13A, a method 750 for enabling the transporter 120 (FIG. 1) to navigate stairs may include, but is not limited to, receiving at least one stair command 1251 and receiving environmental information 651 (FIG. 10) from a sensor 147 (FIG. 10) mounted on the transporter 120 (FIG. 1) through an obstacle processor 607 (FIG. 10). The method 750 may further include locating at least one of the stair structures 643 (FIG. 13B) in the environmental information 651 (FIG. 10) based on the environmental information 651 (FIG. 10) and receiving a selection of a selected stair structure 643A (FIG. 13B) from the at least one of the stair structures 643 (FIG. 13B) in the environmental information 651 (FIG. 10) in step 1255. The method 750 may still further include a step 1259 of measuring at least one characteristic 645 (FIG. 13B) of the selected stair structure 643A (FIG. 13B) and a step 1261 of locating an obstacle 623 (FIG. 13B) on the selected stair structure 643A (FIG. 13B) based on the environmental information 651 (FIG. 13B). The method 750 may also include a step 1263 of locating a last stair of the selected stair structure 643A (FIG. 13B) based on the environmental information 651 (FIG. 13B), and a step 1265 of providing a movement command 630 (FIG. 13B) to move the transporter 120 (FIG. 1) onto the selected stair structure 643A (FIG. 13B) based on the measured at least one characteristic 645 (FIG. 13B), the last stair, and the obstacle 623 (FIG. 13B), if applicable. At 1267, if the last stair has not been reached, the method 750 may continue to provide movement commands 630 (FIG. 13B) to move the transporter 120 (FIG. 1). The method 750 may optionally include locating at least one of the stair structures 643 (FIG. 13B) based on GPS data and building and storing a map of the selected stair structure 643A (FIG. 13B) using, for example, but not limited to, SLAM.The method 750 may also optionally include accessing a geometry 649 (FIG. 13B) of the transporter 120 (FIG. 1), comparing the geometry 649 (FIG. 13B) to at least one of the characteristics 645 (FIG. 13B) of the selected staircase structure 643A (FIG. 13B), and modifying the navigating step based on the comparing step. The at least one of the characteristics 645 (FIG. 13B) may optionally include a height of at least one riser, a surface texture of at least one riser, and a surface temperature of at least one riser of the selected staircase structure 643A (FIG. 13B). The method 750 may optionally include generating an alert if the surface temperature is outside a threshold range and the surface texture is outside a static friction setting. The threshold range may optionally include a temperature below 33° F. The static friction setting may optionally include a carpet texture. The method 750 may further include determining a topography of an area surrounding the selected staircase structure 643A (FIG. 13B) based on the environmental information 651 (FIG. 13B) and generating an alert if the topography is not flat. The method 750 may still further, optionally, include accessing a set of extreme situations.
[0066] Referring now primarily to FIG. 13B, automated navigation of stairs can be enabled by the staircase processor 605C to enable the transporter 120 (FIG. 1) to navigate stairs. The sensor 147 (FIG. 10) on the transporter 120 (FIG. 1) can determine whether the environmental information 651 (FIG. 10), if applicable, includes at least one staircase structure 643. In conjunction with any automatic determination of the location of the at least one staircase structure 643, the UI data 633 can include a selection of the staircase mode 215 (FIG. 3A), which can invoke an automatic, semi-automatic, or semi-manual staircase ascending or descending process. Either the automatic location of the at least one staircase structure 643 or the receipt of the UI data 633 can invoke the staircase processor 605C for enhanced staircase navigation functions. The stair processor 605C can receive data from the obstacle processor 607, such as, for example, at least one obstacle 623, a distance 621 to the at least one obstacle 623, a situation 624, navigation information 653, and geometry information 649 regarding the transporter 120 (FIG. 1). The navigation information can include, but is not limited to, a possible path traversed by the transporter 120 (FIG. 1). The at least one obstacle 623 can include, among other obstacles, at least one stair structure 643. The stair processor 605C can locate the at least one stair structure 643 and can determine, either automatically or otherwise, for example, but not limited to, a selected stair structure 643A based on the navigation information 653 and / or UI data 633 and / or transporter geometry information 649. For example, characteristics 645 of the selected stair structure 643A, such as riser information, distance 640 to the first stair and the next stair, can be used to determine. The stair processor 605C can determine a movement command 630 for the transporter 120 (FIG. 1) based on, for example, but not limited to, the characteristics 645, the distance 621, and the navigation information 647.The movement processor 603 can move the transporter 120 (FIG. 1) based on the movement command 630 and the distance to the next stair 640, and can transfer control to the sensor processing 661 after the stair from the selected stair structure 643A is traversed. The sensor processing 661 can either proceed to navigate the selected stair structure 643A or continue following the path set by the navigation information 653, depending on whether the transporter 120 (FIG. 1) has completed traversing the selected stair structure 643A. While the transporter 120 (FIG. 1) is traversing the selected stair structure 643A, the obstacle processor 607 can detect an obstacle 623 on the selected stair structure 643A, and the stair processor 605C can provide a movement command 630 to avoid the obstacle 623. The location of the obstacle 623 can be stored locally on the transporter 120 (FIG. 1) and / or external to the transporter 120 (FIG. 1) for future use.
[0067] Continuing to refer primarily to FIG. 13B, the stair processor 605C may include, but is not limited to, a stair structure processor 641B that receives at least one stair command included in the UI data 633, and a stair structure locator 641A that receives environmental information 651 (FIG. 10) through an obstacle processor 607 (FIG. 10) from a sensor 147 (FIG. 10) mounted on the transporter 120 (FIG. 1). The stair structure locator 641A may further locate at least one of the stair structures 643 in the environmental information 651 (FIG. 10) based on the environmental information 651 (FIG. 10), and may receive a selection of a selected stair structure 643A from at least one of the stair structures 643. The selected stair structure 643A may be stored in the storage device 643B for possible future use. The staircase characteristic processor 641C can measure at least one of the characteristics 645 of the selected staircase structure 643A and can locate at least one obstacle 623 on the selected staircase structure 643A based on the environmental information 651. The staircase movement processor 641D can locate the last stair of the selected staircase structure 643A based on the environmental information 651 and provide the movement processor 603 with a movement command 630 for the transporter 120 (FIG. 1) to move on the selected staircase structure 643A based on the measured at least one characteristic 645, the last stair, and at least one obstacle 623, if applicable. The staircase structure locator 641A can optionally locate at least one of the staircase structures 643 based on GPS data and can use SLAM to build and store a map of the selected staircase structure 643A. The map can be stored for local use of the transporter 120 (FIG. 1) and / or for use by other devices. The stair structure processor 641B can optionally access the geometry 649 of the transporter 120 (FIG. 1), compare the geometry 649 with at least one of the characteristics 645 of the selected stair structure 643A, and modify the navigation of the transporter 120 (FIG. 1) based on the comparison.The staircase structure processor 641B can optionally generate an alert if the surface temperature of the risers of the selected staircase structure 643A is outside a threshold range and the surface texture of the selected staircase structure 643A is outside a static friction setting. The staircase movement processor 641D can optionally determine the topography of the area surrounding the selected staircase structure 643A based on the environmental information 651 (FIG. 10) and can generate an alert if the topography is not flat. The staircase movement processor 641D can optionally access a set of extreme situations.
[0068] 14A1-14A2, a method 850 for negotiating a door 675 (FIG. 14B) while maneuvering a transporter 120 (FIG. 1), where the door 675 (FIG. 14B) may include a door swing, a hinge location, and a doorway, may include, but is not limited to, receiving and segmenting environmental information 651 (FIG. 10) from a sensor 147 (FIG. 10) mounted on the transporter 120 (FIG. 1). The environmental information 651 (FIG. 10) may include a geometry of the transporter 120 (FIG. 1). The method 850 may include identifying at least one plane in the segmented sensor data (FIG. 14A1) and identifying the door 675 (FIG. 14B) in the at least one plane (FIG. 14A1). The method 850 may further include a step 1357 (FIG. 14A1) of measuring the door 675 (FIG. 14B) and providing a door measurement. The method 850 may also include a step 1361 (FIG. 14A1) of determining a door swing. The method 850 may further include a step 1363 (FIG. 14A2) of providing at least one movement command 630 (FIG. 14B) and moving the transporter 120 (FIG. 1) as needed for access to a handle of the door 675 (FIG. 14B), and a step 1365 (FIG. 14A2) of providing at least one movement command 630 (FIG. 14B) and moving the transporter 120 (FIG. 1) a distance based on the door measurement as the door 675 (FIG. 14B) opens. If the door 675 (FIG. 14B) swings, the method 850 can include providing at least one movement command to move the transporter 120 (FIG. 1) relative to the door 675 (FIG. 14B), thus positioning the door 675 (FIG. 14B) for movement of the transporter 120 (FIG. 1) through the doorway. The method 850 can also include providing at least one movement command 630 (FIG. 14B) to move the transporter 120 (FIG. 1) forward through the doorway, with the transporter 120 (FIG. 1) maintaining the door 675 (FIG. 14B) in an open position, if the door swings toward the transporter 120 (FIG. 1).
[0069] 14B, the sensor processing 661 can determine the hinge side of the door 675, and the direction, angle, and distance of the door through information from the sensor 147 (FIG. 10). The movement processor 603 can generate commands to the PBP 100 (FIG. 4), such as start / stop turn left, start / stop turn right, start / stop move forward, start / stop move backward, and can facilitate the door mode 605A by stopping the transporter 120 (FIG. 1), canceling a goal that the transporter 120 (FIG. 1) is attempting to complete, and centering the joystick 133 (FIG. 1). The door processor 671B can determine whether the door 675 is, for example, a push door, a sliding door, or a sliding door. The door processor 671B can determine the current position and orientation of the transporter 120 (FIG. 1) and determine the x / y / z location of the door pivot point to determine the width of the door 675. If the door processor 671B determines that the number of valid points in an image of the door 675 derived from the obstacle 623 and / or the PCL data 655 (FIG. 10) is above a threshold, the door processor 671B can determine the distance of the door 675 from the transporter 120 (FIG. 1). The door processor 671B can determine whether the door 675 is moving based on successive samples of the PCL data 655 (FIG. 10) from the sensor processor 661. In some configurations, the door processor 671B can assume that the side of the transporter 120 (FIG. 1) is at the same height as the handle side of the door 675 and can use that assumption to determine the width of the door 675, along with the location of the door pivot point.
[0070] Continuing to refer primarily to FIG. 14B, if the movement of the door 675 is toward the transporter 120 (FIG. 1), the door movement processor 671D can generate and provide a movement command 630 to the movement processor 603 to move the transporter 120 (FIG. 1) backwards a predetermined or dynamically determined percentage amount that the door 675 is moving. The movement processor 603 can provide the movement command 630 to the UCP 130, which can receive the GUI data 633A and provide the GUI data 633A to the movement processor 603. If the door 675 is moving away from the transporter 120 (FIG. 1), the door movement processor 671D can generate a movement command 630 to instruct the transporter 120 (FIG. 1) to move forward a predetermined or dynamically determined percentage amount that the door 675 is moving. The amount the transporter 120 (FIG. 1) moves, either forward or backward, can be based on the width of the door 675. The door processor 671B can locate the side of the door 675 that provides the open / close function for the door 675 based on the location of the door pivot point. The door processor 671B can determine the distance to the plane in front of the sensor 147 (FIG. 4). The door movement processor 671D can generate a movement command 630 to instruct the transporter 120 (FIG. 1) to move through the door 675. The door movement processor 671D can wait a preselected amount of time for the movement of the transporter 120 (FIG. 1) to complete, and the door movement processor 671D can generate the movement command 630 and adjust the location of the transporter 120 (FIG. 1) based on the position of the door 675. The door processor 671B can determine the door angle and the door pivot point. The door processor 671B can determine if the door 675 is stationary, can determine if the door 675 is moving, and can determine the direction the door 675 is moving in. Once the door mode 605A is complete, the door movement processor 671D can generate a movement command 630 that can instruct the transporter 120 (FIG. 1) to discontinue movement.
[0071] Still further and continuing primarily with reference to FIG. 14B, a door mode 605A for negotiating a door 675 while maneuvering a transporter 120 (FIG. 1), where the door 675 may include a door swing, hinge location, and doorway, may include, but is not limited to, sensor processing 661 that receives and segments environmental information 651 from sensors 147 (FIG. 10) mounted on the transporter 120 (FIG. 1), where the environmental information 651 may include a geometry 649 of the transporter 120 (FIG. 1). The door mode 605A may also include a door locator 671A that identifies at least one plane in the segmented sensor data and identifies the door 675 in the at least one plane. The door processor 671B may include measuring the door 675 and providing door measurements 645A. The door movement processor 671D can provide at least one movement command 630 to move the transporter 120 (FIG. 1) away from the door 675 if the door measurement 645A is smaller than the transporter (FIG. 1) geometry 649. The door processor 671B can also include a step of determining a door swing, and the door movement processor 671D can provide at least one movement command 630 to move the transporter 120 (FIG. 1) forward through the doorway. The transporter 120 (FIG. 1) can open the door 675 and maintain the door 675 in an open position if the door swing is away from the transporter 120 (FIG. 1). The door movement processor 671D can provide at least one movement command 630 to move the transporter 120 (FIG. 1) for access to the handle of the door 675, and can provide at least one movement command 630 to move the transporter 120 (FIG. 1) away from the door 675 a distance based on the door measurement 645A as the door 675 opens. The door movement processor 671D can provide at least one movement command 630 to move the transporter 120 (FIG. 1) forward through the doorway. The transporter 120 (FIG. 1) can maintain the door 675 in an open position when the door swings toward the transporter 120 (FIG. 1).
[0072] 15A, the transporter 120 (FIG. 1) can automatically negotiate use of the restroom fixtures. The UCP assist 145 (FIG. 4) can automatically locate the restroom door, or restroom cubicle door if multiple doors are present, automatically generate a movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) through the door, and automatically position the transporter 120 (FIG. 1) relative to the restroom fixtures. After use of the restroom fixtures is completed, the UCP assist 145 (FIG. 4) can automatically locate the door, automatically generate a movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) through the door and exit the restroom cubicle and / or restroom. A method 950 for negotiating with a restroom stall in a restroom while aboard the transporter 120 (FIG. 1), where the restroom stall may have a door 675 (FIG. 15B), which may have a door sill and a door swing, may include, without limitation, a step 1451 of providing at least one movement command 630 (FIG. 15B) to cause the transporter 120 (FIG. 1) to cross the door sill and enter the restroom. The method 950 may also include step 1453 of providing at least one movement command 630 (FIG. 15B) to position the transporter 120 (FIG. 1) to access the door entry / exit handle, and step 1455 of providing at least one movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) away from the door 675 (FIG. 15B) as the door 675 (FIG. 15B) closes if the door swings toward the transporter 120 (FIG. 1). The method 950 may also include step 1457, if the door swings away from the transporter 120 (FIG. 1), providing at least one movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) toward the door 675 (FIG. 15B) as the door 675 (FIG. 15B) closes, and step 1459, providing at least one movement command 630 (FIG. 15B) to position the transporter 120 (FIG. 1) near the first restroom fixture.The method 950 may include step 1461 of providing at least one movement command 630 (FIG. 15B) to stop the transporter 120 (FIG. 1) and step 1463 of providing at least one movement command 630 (FIG. 15B) to position the transporter 120 (FIG. 1) proximate to a second restroom fixture. The method 950 may include step 1465 of providing at least one movement command 630 (FIG. 15B) to traverse a door threshold and exit the restroom stall.
[0073] Continuing to refer primarily to FIG. 15A, the step of automatically traversing a door threshold may optionally include, but is not limited to, receiving and segmenting environmental information 651 (FIG. 10) from a sensor 147 (FIG. 10) mounted on the transporter 120 (FIG. 1). The environmental information 651 (FIG. 10) may include the geometry of the transporter 120 (FIG. 1). The step of automatically traversing a door threshold may also optionally include identifying at least one plane in the segmented sensor data 1353 (FIG. 14A1) and identifying a door 675 (FIG. 14B) in the at least one plane 1355 (FIG. 14A1). The step of automatically crossing the door threshold may further optionally include step 1357 (FIG. 14A1) of measuring the door 675 (FIG. 14B) and providing the door measurement, and if the door measurement is smaller than the geometric shape 649 (FIG. 14B) of the transporter (FIG. 1), step 1359 (FIG. 14A1) of providing at least one movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) away from the door 675 (FIG. 14B). The step of automatically crossing the door threshold may also optionally include step 1361 (FIG. 14A1) of determining a door swing and, if the door swing is away from the transporter 120 (FIG. 1), step 1363 (FIG. 14A1) of providing at least one movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) forward through the doorway, causing the transporter 120 (FIG. 1) to open the door 675 (FIG. 14B), and maintaining the door 675 (FIG. 1) in an open position. The step of automatically crossing the door threshold may further optionally include step 1365 (FIG. 14A2) of providing at least one movement command 630 (FIG. 15B) to move the transporter for access to the door handle, and step 1367 (FIG. 14A2) of providing at least one movement command 630 (FIG. 15B) to move the transporter 120 (FIG. 1) away from the door 675 (FIG. 14B) a distance based on the door measurement as the door 675 (FIG. 14B) opens.The step of automatically crossing the door threshold may also optionally include a step 1369 (FIG. 14A2) of providing at least one movement command 630 (FIG. 15B) if the door swing is toward the transporter 120 (FIG. 1), moving the transporter 120 (FIG. 1) forward through the doorway, and having the transporter 120 (FIG. 1) maintain the door 675 (FIG. 14B) in an open position. The method 950 may optionally include a step of automatically locating a restroom and automatically driving the transporter 120 (FIG. 1) to the restroom. SLAM techniques may optionally be used to locate the destination, e.g., the restroom. The UCP assist 145 may optionally access a database of frequently visited locations, receive a selection of one of the frequently visited locations, and provide at least one movement command 630 (FIG. 15B), moving the transporter 120 (FIG. 1) to the selected location, which may include, but is not limited to, a restroom.
[0074] 15B, a restroom mode 605B for negotiating a restroom stall in a restroom while aboard the transporter 120 (FIG. 1), where the restroom stall may have a door, which may have a door threshold and a door swing, may include a door mode 605A that provides, but is not limited to, at least one movement command 630 to cause the transporter 120 (FIG. 1) to cross the door threshold and enter the restroom. The restroom may also include fixtures such as, but not limited to, a toilet, a sink, and a changing table. The entry / exit processor 681C may provide at least one movement command 630 to position the transporter 120 (FIG. 1) to access the door entry handle, and if the door swing is toward the transporter 120 (FIG. 1), may provide at least one movement command 630 to move the transporter away from the door as the door closes. The entry / exit processor 681C can provide at least one movement command 630 to move the transporter 120 (FIG. 1) toward the door 675 when the door swing of the door 675 is away from the transporter 120 (FIG. 1) as the door 675 closes. The stationary processor 681B can provide at least one movement command 630 to position the transporter 120 (FIG. 1) near a first restroom fixture and can provide at least one movement command to stop the transporter 120 (FIG. 1). The stationary processor 681B can also provide at least one movement command 630 to position the transporter 120 (FIG. 1) near a second restroom fixture. The entry / exit processor 681C can provide at least one movement command 630 to cross a door threshold and exit the restroom cubicle.
[0075] 16A1 and 16A2, a method 1051 for automatically storing the transporter 120 in a vehicle, such as, for example, but not limited to, a wheelchair accessible van, can aid a user in independent use of the vehicle. When the user gets off the transporter 120 (FIG. 1) and enters the vehicle, possibly as the driver of the vehicle, the transporter 120 (FIG. 1) can remain parked outside the vehicle. If the transporter 120 (FIG. 1) is to be carried by the user in the vehicle for later use, the dynamic parking mode 605E (FIG. 16B) can provide a movement command 630 (FIG. 16B) to the transporter 120 (FIG. 1) to cause the transporter 120 (FIG. 1) to store itself and to be retrieved at the door of the vehicle, either automatically or in response to a command. The transporter 120 (FIG. 1) can be instructed to store itself, for example, through a command received from an external application 140 (FIG. 4). In some configurations, a computer-driven device such as a cell phone, laptop, and / or tablet can be used to run one or more external applications 140 (FIG. 4) and generate information that may ultimately control the transporter 120 (FIG. 1). In some configurations, once the transporter 120 (FIG. 1) is placed in a parking mode, for example, by a user, the transporter 120 (FIG. 1) can automatically proceed to a dynamic parking mode 605E after the user exits the transporter 120 (FIG. 1). The movement command 630 (FIG. 16B) can include a command to locate a vehicle door that the transporter 120 (FIG. 1) will enter to be stored and a command to direct the transporter 120 (FIG. 1) to the door. The dynamic parking mode 605E (FIG. 16B) can determine an error condition, such as, but not limited to, if a door is too small for the transporter 120 (FIG. 1) to enter, and can alert the user of the error condition, such as, but not limited to, through an audio alert via the audio interface 150 (FIG. 4) and / or a message to the external application 140 (FIG. 4).If the door is wide enough for the transporter 120 (FIG. 1) to enter, the dynamic parking mode 605E (FIG. 16B) can provide vehicle control commands to instruct the vehicle to open the door. The dynamic parking mode 605E (FIG. 16B) can determine when the vehicle door is open and if there is space for the transporter 120 (FIG. 1) to be stored. The dynamic parking mode 605E (FIG. 16B) can call the obstacle handling 607 (FIG. 14B) to help determine the status of the vehicle door and if there is room in the vehicle to store the transporter 120 (FIG. 1). If the dynamic parking mode 605E (FIG. 16B) determines there is enough room for the transporter 120 (FIG. 1), the dynamic parking mode 605E (FIG. 16B) can provide a move command 630 (FIG. 16B) to move the transporter 120 (FIG. 1) into the storage space in the vehicle. The dynamic parking mode 605E (FIG. 16B) can provide vehicle control commands to command the vehicle to lock the transporter 120 (FIG. 1) in place and close the vehicle doors. When the transporter 120 (FIG. 1) is needed again, the external application 140 (FIG. 1) can be used to invoke the dynamic parking mode 605E, for example. The dynamic parking mode 605E (FIG. 16B) can recall the status of the transporter 120 (FIG. 1) and can begin processing by providing vehicle control commands to command the vehicle to unlock the transporter 120 (FIG. 1) and open the vehicle doors. The dynamic parking mode 605E (FIG. 16B) can again locate the vehicle doors or access the door location 675A, for example, from the local storage 607H (FIG. 14B) and / or the cloud storage 607G (FIG. 14B). The dynamic parking mode 605E (FIG. 16B) can provide a move command 630 (FIG. 16B) to move the transporter 120 (FIG. 1) through a vehicle door, for example, to a passenger door commanded by the external application 140 (FIG. 4). In some configurations, the vehicle can be tagged to a fixed location, such as an entry door for storage of the transporter 120 (FIG. 1).The dynamic parking mode 605E can recognize tags, such as, for example, but not limited to, fiducials, bar codes, and / or QR CODE®, and can perform the methods described herein as a result of recognizing the tags. Other tags can also be included, such as tags in storage compartments and tags on vehicle passenger doors to indicate proper storage locations. The tags can be RFID-enabled, for example, the transporter 120 (FIG. 1) can include an RFID reader.
[0076] 16A1 and 16A2, a method 1051 for automatically storing a transporter 120 in a vehicle can include, but is not limited to, providing at least one movement command 630 (FIG. 16B) to locate a vehicle door through which the transporter 120 (FIG. 1) will enter to be stored in a storage space within the vehicle, and providing at least one movement command 630 (FIG. 16B) to direct the transporter 120 (FIG. 1) to the door at 1553. If the vehicle door is wide enough for the transporter 120 (FIG. 1) to enter, at 1555, the method 1051 can include providing at least one vehicle control command to command the vehicle to open the door at 1557. If the door is opened at 1559, and if there is room in the vehicle to store the transporter 120 (FIG. 1) at 1561, the method 1051 may include step 1563 of providing at least one movement command 630 (FIG. 16B) to move the transporter 120 (FIG. 1) into the storage space in the vehicle. The method 1051 may include step 1565 of providing at least one vehicle control command to command the vehicle to lock the transporter 120 (FIG. 1) in place and close the vehicle door. If the vehicle door is not wide enough at 1555, or if the vehicle door is not opened at 1559, or if there is no space for the transporter 120 (FIG. 1) at 1561, the method 1051 may include step 1567 of alerting the user and step 1569 of providing at least one movement command 630 (FIG. 16B) to return the transporter 120 (FIG. 1) to the user.
[0077] Continuing to refer primarily to FIGS. 16A1 and 16A2, at least one movement command 630 (FIG. 16B) for storing the transporter 120 (FIG. 100) can be received from the external application 140 (FIG. 4) and / or automatically generated. The method 1051 can optionally include alerting a user of the error condition, for example, but not limited to, through an audio alert through the audio interface 150 (FIG. 4) and / or a message to the external application 140 (FIG. 4). The method 1051 can optionally invoke obstacle handling 607 (FIG. 14B) to assist in locating the vehicle doors, determining whether there is sufficient room in the vehicle to store the transporter 120 (FIG. 1), and locating any locking mechanisms in the vehicle. When the transporter 120 (FIG. 1) is needed again, i.e., when the user arrives at the destination in the vehicle, the external application 140 (FIG. 1) can be used, for example, to launch the transporter 120 (FIG. 1). The method 1051 can include recalling the status of the transporter 120 (FIG. 1) and can include providing vehicle control commands to command the vehicle to unlock the transporter 120 (FIG. 1) and open the vehicle doors. The method 1051 can include locating the vehicle doors or can include accessing the location of the vehicle doors, for example, from the local storage 607H (FIG. 14B) and / or the cloud storage 607G (FIG. 14B). The method 1051 can include providing a movement command 630 (FIG. 16B) to move the transporter 120 (FIG. 1) through the vehicle doors, for example, but not limited to, to a passenger door commanded by the external application 140 (FIG. 4).
[0078] 16B, the dynamic parking mode 605E may include, but is not limited to, a vehicle door processor 691D that may provide at least one movement command 630 to locate a door 675 of the vehicle through which the transporter 120 (FIG. 1) will enter to be stored in a storage space within the vehicle. The vehicle door processor 691D may also provide at least one movement command 630 to direct the transporter 120 (FIG. 1) to the door 675. If the door 675 is wide enough for the transporter 120 (FIG. 1) to enter, the vehicle command processor 691C may provide at least one vehicle control command to command the vehicle to open the door 675. If the door 675 is open and there is room within the vehicle to store the transporter 120 (FIG. 1), the spatial processor 691B may provide at least one movement command 630 to move the transporter 120 (FIG. 1) into the storage space within the vehicle. The vehicle command processor 691C can provide at least one vehicle control command to command the vehicle to lock the transporter 120 (FIG. 1) in place and close the vehicle doors 675. If the doors 675 are not wide enough, or if they do not open, or there is no space for the transporter 120 (FIG. 1), the error processor 691E can alert the user and provide at least one movement command 630 to return the transporter 120 (FIG. 1) to the user.
[0079] 16B, the vehicle door processor 691D can optionally recall the status of the transporter 120 (FIG. 1), and the vehicle command processor 691C can provide vehicle control commands to command the vehicle to unlock the transporter 120 (FIG. 1) and open the vehicle door 675. The vehicle door processor 691D can again locate the vehicle door 675 or access the location of the door 675, for example, from the local storage 607H (FIG. 14B) and / or the cloud storage 607G (FIG. 14B) and / or the door database 673B. The vehicle door processor 691D can provide a movement command 630 to move the transporter 120 (FIG. 1) through the door 675, for example, to a passenger door commanded by the external application 140 (FIG. 4).
[0080] Referring now primarily to FIG. 17A, a method 1150 for storing / recharging the transporter 120 (FIG. 1) can assist a user in storing and possibly recharging the transporter 120 (FIG. 1). For example, the transporter 120 (FIG. 1) can be recharged while the user sleeps. After the user steps off the transporter 120 (FIG. 1), a command can be initiated, for example, in the external application 140 (FIG. 4), to move the transporter 120 (FIG. 1), perhaps without an occupant, to a storage / docking area. In some configurations, a mode selection by the user while the user is using the transporter 120 (FIG. 1), can initiate an automatic storage / docking function after the user steps off the transporter 120 (FIG. 1). When the transporter 120 (FIG. 1) is needed again, a command can be initiated by the external application 140 (FIG. 4) to return the transporter 120 (FIG. 1) to the user. Method 1150 may include, but is not limited to, step 1651 of locating at least one storage / charging area, and step 1655 of providing at least one movement command 630 (FIG. 17B) and moving transporter 120 (FIG. 1) from a first location to the storage / charging area. Method 1150 may include step 1657 of locating a charging dock within the storage / charging area, and step 1663 of providing at least one movement command 630 (FIG. 17B) and coupling transporter 120 (FIG. 1) with the charging dock. Method 1150 may optionally include, upon transporter 120 (FIG. 1) receiving a start-up command, providing at least one movement command 630 (FIG. 17B) and moving transporter 120 (FIG. 1) to the first location.If, at 1653, a storage / charging area does not exist, or, at 1659, a charging dock does not exist, or, at 1666, the transporter 120 (FIG. 1) cannot be coupled to a charging dock, the method 1150 may optionally include step 1665 of providing at least one alert to a user and step 1667 of providing at least one movement command 630 (FIG. 17B) and moving the transporter 120 (FIG. 1) to the first location.
[0081] 17B, the static storage / charging mode 605F can include, but is not limited to, a storage / charging area processor 702A that can locate at least one storage / charging area 695, provide at least one movement command 630, and move the transporter 120 (FIG. 1) from a first location to the storage / charging area 695. The coupling processor 702D can locate a charging dock within the storage / charging area, provide at least one movement command 630, and couple the transporter 120 (FIG. 1) with the charging dock. The return processor 702B can optionally provide at least one movement command 630 to move the transporter 120 (FIG. 1) to the first location upon the transporter 120 (FIG. 1) receiving a start-up command. If the storage / charging area 695 does not exist, or if the charging dock does not exist, or if the transporter 120 (FIG. 1) cannot be coupled to the charging dock, the error processor 702E can optionally provide at least one alert to the user and provide at least one movement command 630 to move the transporter 120 (FIG. 1) to the first location.
[0082] 18A, a method 1250 for negotiating an elevator while maneuvering a transporter 120 (FIG. 1) can assist a user in ascending or descending an elevator 685 (FIG. 18B) while aboard the transporter 120 (FIG. 1). Sensor processing 661 can be used, for example, to locate the elevator 685 (FIG. 18B), or the elevator location 685A (FIG. 18B) can be determined from local storage 607H (FIG. 14B) and / or storage cloud 607G (FIG. 14B). Once the elevator 685 (FIG. 18B) is located and the user has selected the desired elevator direction, and once the elevator 685 (FIG. 18B) has arrived and the doors have opened, the elevator mode 605D (FIG. 18B) can provide a movement command 630 (FIG. 18B) to move the transporter 120 (FIG. 1) into the elevator 685 (FIG. 18B). The geometry of the elevator 685 (FIG. 18B) can be determined and a movement command 630 (FIG. 18B) can be provided to move the transporter 120 (FIG. 1) to a location that allows the user to select a desired activity from the elevator selection panel. The location of the transporter 120 (FIG. 1) can also be suitable for exiting the elevator 685 (FIG. 18B). Once the elevator doors are open, a movement command 630 (FIG. 18B) can be provided to move the transporter 120 (FIG. 1) and completely exit the elevator 685 (FIG. 18B). The method 1250 can include, without limitation, a step 1751 of locating the elevator 685 (FIG. 18B), which has an elevator door and an elevator threshold associated with the elevator door. The method 1250 can include a step 1753 of providing at least one movement command 630 (FIG. 18B) to move the transporter 120 (FIG. 1) through the elevator door and over the elevator threshold.The method 1250 can also include a step 1755 of determining the geometry of the elevator 685 (FIG. 18B) and a step 1757 of providing at least one movement command 630 (FIG. 18B) to move the transporter 120 (FIG. 1) to a floor selection / exit location relative to the elevator threshold. The method 1250 can also include a step 1759 of providing at least one movement command 630 (FIG. 18B) to move the transporter 120 (FIG. 1) across and beyond the elevator threshold and exit the elevator 685 (FIG. 18B).
[0083] 18B, the elevator mode 605D can include an elevator locator 711A that can locate the elevator 685, including, but not limited to, the elevator doors and the elevator threshold associated with the elevator doors. The elevator locator 711A can store the obstacles 623, the elevator 685, and the elevator location 685A, for example, in an elevator database 683B. The elevator database 683B can be located locally or remotely from the transporter 120. The entry / exit processor 711B can provide at least one movement command 630 to move the transporter 120 (FIG. 1) through the elevator doors and over the elevator threshold to either enter or exit the elevator 685. The elevator geometry processor 711D can determine the geometry of the elevator 685. The entry / exit processor 711B can provide at least one movement command 630 to move the transporter 120 (FIG. 1) to a floor selection / exit location relative to the elevator threshold.
[0084] The configuration of the present teachings is directed to computer systems for performing the methods discussed in the description herein, and computer-readable media containing programs for performing these methods. Raw data and results can be stored for future retrieval and processing, printed, displayed, transferred to another computer, and / or transferred to other locations. Communication links can be wired or wireless, for example, using cellular, military, and satellite communication systems. The components of system 200A (FIG. 4) can run, for example, on computers with various numbers of CPUs. Other alternative computer platforms can also be used.
[0085] The present configuration is also directed to software and / or firmware and / or hardware for performing the methods discussed herein, and computer readable media storing software for performing these methods. The various modules described herein can be performed by the same CPU, or by different CPUs that are tightly or loosely coupled. The various modules can be performed by specially designed integrated circuits. In compliance with the statute, the present configuration has been described in more or less specific terms with respect to structural and methodological features. However, it should be understood that the present configuration is not limited to the specific features shown and described, since the means disclosed herein comprise various forms for putting the present teachings into practice.
[0086] Methods 650 (FIGS. 11A1-11A2), 750 (FIGS. 13A), 850 (FIGS. 14A1-14A2), 950 (FIG. 15A), 1050 (FIGS. 16A1-16A2), 1150 (FIG. 17A), and 1250 (FIG. 18A) can be implemented, in whole or in part, electronically. Signals representing actions taken by elements of system 200A (FIG. 4) and other disclosed configurations can travel via at least one live communication network 143 / 144 (FIG. 4). Control and data information can be electronically executed and stored on at least one computer readable medium. The system can be implemented to execute on at least one computer node in at least one live communication network. At least one computer-readable medium in general form may include, for example, but is not limited to, a floppy disk, a flexible disk, a hard disk, a magnetic tape, or any other magnetic medium, a compact disk read-only memory or any other optical medium, a punch card, a paper tape, or any other physical medium with a pattern of holes, a random access memory, a programmable read-only memory, and an erasable programmable read-only memory (EPROM), Flash EPROM, or any other memory chip or cartridge, or any other medium from which a computer can read.
[0087] Although the present teachings are described above in terms of specific configurations, it should be understood that they are not limited to these disclosed configurations. Numerous modifications and other configurations will occur to those skilled in the art, which are intended to be and are covered by both this disclosure and the appended claims. It is intended that the scope of the present teachings should be determined by the proper interpretation and construction of the appended claims and their legal equivalents, as understood by those skilled in the art based on the present disclosure in this specification and the accompanying drawings.
Claims
1. 1. A system for controlling a transporter, the system comprising: A base processor; a user control processor (UCP) configured to communicate with the infrastructure processor; UCP Assist and The UCP assist comprises: Receiving user input; receiving input from the substrate processor; Assisting a user in overcoming a transportation challenge based on the user input and the input from the underlying processor. the UCP assist includes a plurality of processors, the plurality of processors being configured to enable invocation of a mode of the transporter by generating movement commands of the transporter for user selection based at least on previous movement commands of the transporter, the user input, and sensor data providing environmental information of the transporter.
2. 2. The system of claim 1, wherein the transportation task is selected from avoiding obstacles, passing through doors, climbing stairs, riding an elevator, parking the transporter, transporting the transporter, and combinations thereof.
3. The system of claim 1 , further comprising an interface module configured to transmit / receive messages to / from an audio interface, an electronic interface, a manual interface, a visual interface, and combinations thereof.
4. The system of claim 3 , wherein the audio interface is configured to transmit data from the UCP to an audio device.
5. The system of claim 4 , wherein the audio device includes a speaker configured to issue an alert.
6. The system of claim 3 , wherein the electronic interface is configured to transmit / receive the messages to / from a sensor.
7. The system of claim 6 , wherein the sensor comprises a camera.
8. The system of claim 1 , further comprising a sensor fixed relative to the transporter.
9. The system of claim 8 , wherein the sensor is configured to assist in navigating the transporter.
10. 9. The system of claim 8, wherein the sensor is configured to detect obstacles around the transporter and is selected from a stereo color camera, an ultrasonic beam range finder, a time-of-flight camera, a single point LIDAR sensor, and combinations thereof.
11. 10. The system of claim 8, wherein the sensor is configured to transmit messages to the infrastructure processor and / or the UCP assist, the messages configured to assist the transporter in reacting to activity outside the user's field of view.
12. The system of claim 1 further comprising a reflector comprising a sensor fixed relative to the transporter.
13. The system of claim 1 , further comprising a sensor comprising a camera configured to act as a tail light on the transporter.
14. 10. The system of claim 1, further comprising a sensor configured to communicate with the UCP assist and enable a transition of the transporter to a balance mode in which the transporter travels on two wheels.
15. The system of claim 3 , wherein the manual interface is configured to transmit / receive the message to / from a user interface.
16. The system of claim 1 , wherein the infrastructure processor comprises a redundant processor.
17. The system of claim 1 further comprising a power supply controller.
18. The system of claim 17 , wherein the power supply controller comprises a redundant controller.
19. The system of claim 3 , further comprising an external communications interface configured to enable communication between the UCP, the UCP Assist, and an external application.
20. 20. The system of claim 19, wherein the communication is wireless.
Citation Information
Patent Citations
Transportation vehicle and transportation method
JP2003305088A
Automated personal assistance system
US20120136666A1
