Examples described herein relate to remote control of devices, and more specifically, to implementing remotely controlling devices in a virtualized environment.
Various kinds of remotely controllable devices exist. For example hobbyists often operate “RC” devices in the form of cars, trucks, airplanes and helicopters. Such devices typically receive commands from a controller device, and after movement (e.g., direction or velocity) based on the input. Some devices use software-based controllers, which can be implemented in the form of an application running on a device such as a smart phone or a tablet.
According to some embodiments, a computing device is operated to process image data in order to track a movement or position of a self-propelled device.
Still further, in some embodiments, a self-propelled device is tracked, and position information determined from tracking the self-propelled device is integrated with a virtual environment. The virtual environment can include facets that are based on the position and/or state of the object, as well as on other aspects of the real-world environment as determined from tracking and/or communicating with the self-propelled device.
In an embodiment, image data is generated by a camera component. The camera component can be provided as part of, or alternatively coupled to, a computing device that acts as a controller for a self-propelled device. From the image data, a location of the self-propelled device can be determined (e.g., relative to the computing device). Content can be generated based at least in part on the location of the self-propelled device as the self-propelled device is moved or otherwise operated through the controller.
In some variations, sensor input is received from the self-propelled device. In particular, the sensor input can be indicative of the position of the self-propelled device. By way of example, the self-propelled device can include a gyroscope, an inertial mass unit (IMU), a GPS, an accelerometer, a light sensor, and/or proximity sensor. The sensor information communicated from the self-propelled device can include readings or output from the sensors. Additionally, the sensor information communicated from the self-propelled device can be in raw form, or in processed form (e.g., numerical values determined from a combination of sensors).
According to another embodiment, a computing device operating as a controller can obtain image data from a camera component. The computing device can determine a location of the self-propelled device relative to the camera based on the image data. A virtual content may be generated on the computing device based at least in part on the location of the self-propelled device.
As used herein, the term “substantially” means at least almost entirely. In quantitative terms, “substantially” means at least 80% of a stated reference (e.g., quantity of shape).
In similar regard, “spherical” or “sphere” means “substantially spherical.” An object is spherical if it appears rounded, contoured or elliptical to a user. Objects which include, for example, half-domes, quarter-domes, elliptical (dimension of one axis larger than another) can be considered spherical as used herein.
As described by various embodiments, SPD 10 can be operated to move under control of another device, such controller 100. In some embodiments, SPD 10 is configured with resources that enable one or more of the following: (i) maintain self-awareness of orientation and/or position relative to an initial reference frame after the device initiates movement; (ii) process control input programmatically, so as to enable a diverse range of program-specific responses to different control inputs; (iii) enable another device to control its movement using software or programming logic that is communicative with programming logic on the self-propelled device; and/or (iv) generate an output response for its movement and state that it is software interpretable by the control device.
With further reference to
In operation, controller 100 may include a camera interface 134, which obtains image data 113 depicting a real-time state of the SPD 10 in a scene that is captured by the camera of the controller 100. In one embodiment, the camera interface 134 receives image data that represents a series of images (or a video) of the scene in which the SPD 10 is present (e.g., moving under control of the controller 100). The object detector 120 can include image processing logic to analyze the image data 113, and to identify objects of interest from the image data 113. In particular, the object detector 120 can process the image data 113 in order to identify a depiction of the SPD 10, and optionally, a depiction of objects or landmarks in the scene that are deemed to be of interest.
In some implementations, the object detector 120 includes image analysis logic for analyzing image data 113 for presence of spheres, half spheres or portions thereof (e.g., quadrant of sphere). Thus, object detector 120 can include image processing logic for locating a shape that is indicative of SPD 10 (e.g., detect circle or portion thereof that is indicative of a spherical aspect of the SPD 10). Other characteristics such as illumination (e.g., LED illumination) or structural features of the SPD 10 can also be used to both detect the SPD 10, or to detect an orientation or other aspect of the SPD 10 in its environment. The object detector 120 can also include image processing resources that are configured to detect other specific kinds of objects other than spheres, such as objects typically encountered in the real world environment of SPD 10. These can include, for example, wall structures, table legs, or surfaces (e.g., carpet, grass etc.).
In one implementation, object detector 120 uses dimensional analysis to determine, from the image data 113, a relative position or distance of the SPD 10 from controller 100. In particular, one embodiment provides for the SPD 10 to be spherical. The object detector 120 can use dimensional analysis by comparing a dimension of the depiction for the SPD 10 (e.g., circle or portion thereof) with a reference dimension for the spherical housing of the self-propelled device.
In one variation, the controller 100 can also use local sensor information 109, provided from sensor devices resident on the computing device of controller 100. For example, local sensor information 109 can be provided by an accelerometer, gyroscope, magnetometer, or Global Positioning System (GPS) device that is resident on the computing device of the controller 100. As an addition or alternative, some implementations provide for the controller 100 to use the relative height of the controller 100 (e.g., distance from ground), and/or the orientation of the controller 100 with respect to a horizontal plane, in order to determine position information for the SPD 10.
As an addition or alternative, SPD 10 can communicate sensor input 11 to the controller 100. The sensor input 11 can correspond to, for example, information determined from an inertial mass unit (“IMU”), gyroscope, accelerometer, magnetometer, or GPS. The sensor input 11 can be either raw data, or data processed on the SPD 10 before being communicated to the controller 100. In variations, the controller 100 includes sensor logic 128, either with the object detector 120, or as a separate logical component (e.g., plug-in), to handle device sensor input 111 (corresponding to sensor input 11 provided from the SPD 10). The sensor logic 128 can determine sensor location information 115, corresponding to information that is indicative, probative or otherwise relevant to a position, relative location, or physical state of the SPD 10. Sensor location information 115 can be used by the object detector 120, in combination with image data 113, to determine a relative position for the SPD 10. The information determined for the SPD 10 can include, for example, a distance of the SPD 10 from the controller or reference point in either 1-, 2- or 3-dimensions, or a coordinate of the SPD 10 within a particular reference frame. The information determined from the SPD 10 can also be indicative of a physical state of the device (e.g., LED on device is on, device is going downhill or has hit obstruction, etc.).
In other variations, the position information for the SPD 10 can be communicated by the SPD to the controller 100 via a wireless link (e.g., Bluetooth). For example, the SPD 10 may be self-aware by way of its own geo-aware resources. In particular, the SPD 10 can include sensors and devices such as an accelerometer, a Global Positioning System (GPS) unit, a gyroscope and/or a magnetometer.
The object detector 120 can communicate raw position information 117 to one or more content output components of the controller 100. In one implementation, a coordinate mapping component 122 maps the raw position information 117 to coordinate positions 121 of an alternative reference frame that is specific to a particular virtual environment. The alternative reference frame can be generated and maintained through, for example, the content generation component 124, as part of a virtual environment. The content generation component 124 may independently use content input from, for example, a content library 125 in order to generate aspects of a virtual environment.
In some variations, the content generation component 124 can obtain virtual environment parameters 129 for use in creating specific virtual environments. For example, specific games or gaming scenarios may carry alternative virtual parameters 129. The virtual environment parameters 129 can, for example, (i) map raw position information 117 to virtual coordinates, (ii) convert detected objects into graphical representations (e.g., transfer real-world object into an anime gaming feature), and (iii) provide rules for a physics engine (e.g., application of Newtonian using virtual reference frame). Using the virtual environment parameters 129 and the content library 125, content generation component 124 can update the virtual environment using the raw position information 117 determined from tracking the position of the SPD 10. For example, a graphic representation of the SPD 10 can be reflected in the virtual environment, based on the position information and the alternative coordinate system provided by the coordinate mapping component 122.
As an addition or alternative, the content generation component 124 can include logic to (i) flag certain coordinates (e.g., determined from, or corresponding to raw position information 117) as landmarks or points of interest for future use in a virtual environment, and/or (ii) access a data store of historical content (“historical content store 127”) that is based on prior landmarks or points of interest.
The content generation component 124 can provide content output 123 for user interface 110. The user interface 110 can create a presentation that depicts the content output 123. The user interface 110 can also include or modify the content output 123 to allot for input from the user that can affect operation of the SPD 10, as well as to permit manipulation of the content presented. For example, the user interface 110 can include a framework of graphic features that the user can interact with in order to (i) after a virtual aspect provided from content generation component 124, and/or (ii) adjust performance or operation (e.g., speed up, change direction, stop, execute sequence, spin etc.) of the SPD 10.
In more detail, the user interface 110 can include the command interface 112 to enable the user to control the SPD 10. For example, the command interface 112 can correspond to one or more features or aspects of the virtual environment that allow the user to enter input for purpose of controlling movement, operations and other aspects of the SPD 10. As described elsewhere, subsequent control of SPD 10 (e.g., movement) can also affect the virtual environment.
Methodology
With reference to
A location of a self-propelled device is detected from the scene (220). According to some embodiments, the image data is used to detect a location of the self-propelled device within a given scene. For example, in order to locate the SPD 10, the image processing logic can include object-type specific detectors to locate (i) shapes, such as circles, semi-circles, or portions thereof, in implementations in which the SPD 10 is a sphere, (ii) surface color (e.g., white), (iii) surface ornamentation or mark (e.g., visual code), or (iv) specific characteristic structural features. The image processing logic can also include object-type specific detectors to identify, from the image data objects that are likely to be found in the environment of the SPD 10. For example, object detector 120 can implement image processes to detect walls, rugs, specific kinds of floorings, pet dishes, steps, or lighting conditions that may be present in the environment of the SPD 10.
As an addition or alternative, controller 100 can use sensor data 109, communicated from the SPD 10, in order to determine the position of the SPD in a given scene. For example, SPD 10 can include resources for being aware of its position relative to, for example, controller 100. U.S. patent application Ser. No. 13/342,853, which is incorporated by reference herein, describes various sensor inputs and logic for enabling a device such as SPD 10 be self-aware of its location.
Content is generated based on the location of the SPD 10 (230). In particular, various kinds of virtual content can be generated that are based on movement, physical presence of other aspects of SPD 10 in the real-world environment. In one implementation, the content provided includes a map or other depiction of physical space (232). For example, the SPD 10 can be operated in a room, and a graphic map of the room, or of an alternative environment (e.g. gaming environment, such as a race track) can be generated that is based on the position of the SPD 10.
As an addition or alternative, the generated content can correspond to a virtual environment (234), such as, for example, in environment in which the SPD 10 has a virtual representation, and the surrounding environment is based partly on the real-world environment of the SPD 10. A set of virtual parameters can be determined as part of generating content. For example, a virtual map can be structured, and/or used as a framework or basis for conducting other events and aspects of a virtual environment. The virtual map can be determined from, for example, a path of the SPD, identified landmarks and other events, then translated into an alternative reference frame for the specific virtual environment.
With respect to
In an embodiment, the location of the self-propelled device is recorded as the object moves about its scene (320). Thus, the self-propelled device can be tracked as it moves about. A path can be determined for the self-propelled device based on its past locations in a given timeframe.
The locations of the self-propelled device can be recorded over a given duration (330). For example, the device can be operated in a given time frame, and the movement of the device can be sampled by way of image processing. The self-propelled device can also be tracked so that the device's path can be determined for the given time period. The path or recorded locations of the self-propelled device can then be integrated into a virtual environment. More generally, the position of the self-propelled device can be integrated with content that is otherwise independent of the real-world environment of the self-propelled device.
In particular, some embodiments provide for recording landmarks that the self-propelled device experiences (332). Landmarks can include, for example, a starting point, an obstruction such as a wall or table leg, variations of the underlying surface in which to self-propelled device operates (e.g., type of flooring), variations in lighting (e.g., well lighted place versus dark place), and variations in the gradient of the underlying surface.
As another addition our variation, the recorded path of the self-propelled device can be used to generate a map (334). The map can define geographic parameters that are translated into a virtual environment. For example, the walls of the room can be translated into a track. The path of the object can also be translated into a virtual path. The map can also include the landmarks, as determined in (332).
Example
A field of view for a camera component 404 of the device 400 can monitor the region 411 for movement or changes to the physical state of the self-propelled device 410. The region 411 can also extend beyond the field of view. For example, the region 411 can encompass multiple rooms or an extended path traversed by the self-propelled device.
In the example of
According to some embodiments, the self-propelled device can be moved in the real world amongst obstacles, and landmarks or points of interest. A region 411 in which the self-propelled device 410 is moved in the real-world can also be mapped into the virtual environment, and some landmarks or points of interest within the region 411 can be reflected in alternative forms in the virtual environment. For example, real-world obstruction such as walls 415 can be reflected as an obstacle 422 (e.g., one that is smaller in size) in the virtual environment. As another example, a charging dock 418 can be used as a landmark for the self-propelled device in maintaining a point of reference for future use. For example, the location of the charging dock 418 can be recorded and mapped to a virtual garage 428.
In some embodiments, mobile device 400 uses a camera to track the object in a given real-world region. The position of the object in the given region can be reflected in the corresponding virtual environment. Each virtual environment in use on the mobile device 400 can map to the real world based on a set of transformations. Thus, for example, mobile device 400 can use its camera to track the self-propelled device 410, and the position of the self-propelled device (as well as other physical information) can be used to coordinate the position of a virtual object of interest in a corresponding virtual environment.
Additionally, the self-propelled device 410 can be shaped so that it is readily detectable from image data. Still further, the self-propelled device 410 can be shaped so that the relative depth or distance from the mobile device 400 can be determined based on dimensional analysis of the detected shape versus a reference. For example, as shown by an example of
Optionally, the mobile device 400 can use sensor input from the self-propelled device, as an alternative or addition to using image data. The self-propelled device can communicate, for example, information determined from the IMU of the device. This information can enable the device to determine its own location relative to a particular reference frame. The device 400 can signal the information to the mobile device 400 using a wireless link.
Controller Hardware Diagram
In one embodiment, the computing device 500 includes one or more processors 510, memory resources 520, a display device 530, one or more communication sub-systems 540 (including wireless communication sub-systems), and one or more sensors 560. According to different implementations, the communication sub-systems 540 enables the computing device 500 to exchange wireless communications with a self-propelled device using wireless communication mediums and protocols (e.g., WI-FI, BLUETOOTH, Infrared). In some embodiments, the computing device 500 can also include one or more input mechanisms 550 (e.g., a button, a switch, a touch-sensitive input device).
The processor 510 can be configured with software and/or other logic to perform one or more processes, steps and functions described with the various examples described herein, such as described by
In performing operations of the controller, the processor 510 may utilize various forms of input. In particular, processor 510 can receive user input via the input mechanisms (e.g., touch sensor integrated with display, buttons, voice input etc.). Furthermore, the processor 510 can also receive sensor input from one or more sensors 560 that are included with the computing device 500. Examples of sensors 560 include accelerometers, proximity sensors, capacitive sensors, light sensors, magnetometers, inertial mass unit (or IMU) or gyroscopes. As described with an example of
In one embodiment, the processor 510 can control the display device 530 to provide virtual or “augmented reality” content. As described with other examples, such content may include alternative graphic representations of a self-propelled device, as well as virtual elements or facets which are affected by real-world events, particularly relating to the position, movement and state of the self-propelled device that is under control of the computing device 500.
Self-Propelled Device
In some examples, the self-propelled device 600 includes a housing 610 that is substantially spherical. In variations, the housing can be elliptical, semi-spherical, or include spherical portions. Other suitable geometric shapes may also be used. However, one advantage provided by using a spherical shape for the housing 610 is that the shape of the device remain symmetrical when viewed from various angles. This facilitates using image analysis for purpose of locating the object by relative position or distance.
With reference to
It is contemplated for embodiments described herein to extend to individual elements and concepts described, independently of other concepts, ideas or system, as well as to combinations of elements recited anywhere in this application. Although numerous examples are described in detail with reference to the accompanying drawings, it is to be understood that the embodiments extend beyond the described examples. Furthermore, it is contemplated that a particular feature described either individually or as part of an embodiment can be combined with other individually described features, or parts of other embodiments, even if the other features and embodiments make no mention of the particular feature.
This Application is a Continuation-in-Part of U.S. patent application Ser. No. 13/342,853, entitled “SELF-PROPELLED DEVICE WITH ACTIVELY ENGAGED DRIVE SYSTEM”, filed Jan. 3, 2012, which claims benefit of priority to the following: U.S. Provisional Application No. 61/430,023, entitled “METHOD AND SYSTEM FOR CONTROLLING A ROBOTIC DEVICE, filed Jan. 5, 2011; U.S. Provisional Application No. 61/430,083, entitled “SYSTEM AND METHOD FOR ESTABLISHING 2-WAY COMMUNICATION FOR CONTROLLING A ROBOTIC DEVICE”, filed Jan. 5, 2011 and U.S. Provisional Application No. 61/553,923, entitled “A SELF-PROPELLED DEVICE AND SYSTEM FOR CONTROLLING SAME”, filed Oct. 31, 2011; all of the aforementioned priority applications being hereby incorporated by reference in their respective entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3683216 | Post | Aug 1972 | A |
4996468 | Field et al. | Feb 1991 | A |
5297981 | Maxim et al. | Mar 1994 | A |
6227933 | Michaud et al. | May 2001 | B1 |
6246927 | Dratman | Jun 2001 | B1 |
6458008 | Hyneman | Oct 2002 | B1 |
6459955 | Bartsch et al. | Oct 2002 | B1 |
6573883 | Bartlett | Jun 2003 | B1 |
6615109 | Matsuoka et al. | Sep 2003 | B1 |
6764373 | Osawa et al. | Jul 2004 | B1 |
6785590 | Kasuga et al. | Aug 2004 | B2 |
6786795 | Mullaney et al. | Sep 2004 | B1 |
6945843 | Motosko | Sep 2005 | B1 |
6980956 | Takagi et al. | Dec 2005 | B1 |
7069113 | Matsuoka et al. | Jun 2006 | B2 |
7130741 | Bodin et al. | Oct 2006 | B2 |
7170047 | Pal | Jan 2007 | B2 |
7173604 | Marvit et al. | Feb 2007 | B2 |
7258591 | Xu et al. | Aug 2007 | B2 |
7340077 | Gokturk et al. | Mar 2008 | B2 |
7344430 | Hasty et al. | Mar 2008 | B2 |
7432718 | Ishihara et al. | Oct 2008 | B2 |
7526362 | Kim et al. | Apr 2009 | B2 |
7714880 | Johnson | May 2010 | B2 |
7822507 | Ishihara et al. | Oct 2010 | B2 |
7847504 | Hollis | Dec 2010 | B2 |
7853357 | Sawada et al. | Dec 2010 | B2 |
7979162 | Niemela et al. | Jul 2011 | B2 |
8025551 | Torres et al. | Sep 2011 | B2 |
8038504 | Wong | Oct 2011 | B1 |
8099189 | Kaznov et al. | Jan 2012 | B2 |
8128450 | Imai | Mar 2012 | B2 |
8128500 | Borst et al. | Mar 2012 | B1 |
8142287 | Podoloff | Mar 2012 | B2 |
8180436 | Boyden et al. | May 2012 | B2 |
8197298 | Willett | Jun 2012 | B2 |
8258917 | Cai et al. | Sep 2012 | B2 |
8274406 | Karlsson et al. | Sep 2012 | B2 |
8275544 | Wells et al. | Sep 2012 | B1 |
8326469 | Phillips et al. | Dec 2012 | B2 |
8330639 | Wong et al. | Dec 2012 | B2 |
8352643 | Birnbaum et al. | Jan 2013 | B2 |
8355818 | Nielsen et al. | Jan 2013 | B2 |
8364136 | Hoffberg et al. | Jan 2013 | B2 |
8392065 | Tolstedt et al. | Mar 2013 | B2 |
8396611 | Phillips et al. | Mar 2013 | B2 |
8417384 | Togawa et al. | Apr 2013 | B2 |
8456298 | Valtonen | Jun 2013 | B2 |
8571781 | Bernstein et al. | Oct 2013 | B2 |
8577595 | Zhao et al. | Nov 2013 | B2 |
8670889 | Kaznov | Mar 2014 | B2 |
20030093182 | Yokoyama | May 2003 | A1 |
20040002843 | Robarts et al. | Jan 2004 | A1 |
20040182614 | Wakui | Sep 2004 | A1 |
20040186623 | Dooley et al. | Sep 2004 | A1 |
20050004723 | Duggan et al. | Jan 2005 | A1 |
20050186884 | Evans | Aug 2005 | A1 |
20050226192 | Red et al. | Oct 2005 | A1 |
20050264472 | Rast | Dec 2005 | A1 |
20060095158 | Lee et al. | May 2006 | A1 |
20060101465 | Kato et al. | May 2006 | A1 |
20060164261 | Stiffler | Jul 2006 | A1 |
20060241812 | Jung | Oct 2006 | A1 |
20060271251 | Hopkins | Nov 2006 | A1 |
20070034734 | Yoeli | Feb 2007 | A1 |
20070085706 | Feyereisen et al. | Apr 2007 | A1 |
20070112462 | Kim et al. | May 2007 | A1 |
20070249422 | Podoloff | Oct 2007 | A1 |
20070259592 | Imai et al. | Nov 2007 | A1 |
20070282484 | Chung et al. | Dec 2007 | A1 |
20080009965 | Bruemmer et al. | Jan 2008 | A1 |
20080033641 | Medalia | Feb 2008 | A1 |
20080077284 | Swope | Mar 2008 | A1 |
20080121097 | Rudakevych et al. | May 2008 | A1 |
20080174268 | Koo et al. | Jul 2008 | A1 |
20080174448 | Hudson | Jul 2008 | A1 |
20080240507 | Niwa et al. | Oct 2008 | A1 |
20080263628 | Norman et al. | Oct 2008 | A1 |
20080267450 | Sugimoto et al. | Oct 2008 | A1 |
20080269949 | Norman et al. | Oct 2008 | A1 |
20090033623 | Lin | Feb 2009 | A1 |
20090055019 | Stiehl et al. | Feb 2009 | A1 |
20090057238 | Garti | Mar 2009 | A1 |
20090073034 | Lin | Mar 2009 | A1 |
20090081923 | Dooley et al. | Mar 2009 | A1 |
20090171516 | Reich | Jul 2009 | A1 |
20090198371 | Emanuel et al. | Aug 2009 | A1 |
20090204261 | Strand et al. | Aug 2009 | A1 |
20090222148 | Knotts et al. | Sep 2009 | A1 |
20090226035 | Iihoshi et al. | Sep 2009 | A1 |
20090256822 | Amireh et al. | Oct 2009 | A1 |
20090262074 | Nasiri et al. | Oct 2009 | A1 |
20090265671 | Sachs et al. | Oct 2009 | A1 |
20090278932 | Yi | Nov 2009 | A1 |
20090284553 | Seydoux | Nov 2009 | A1 |
20100004798 | Bodin et al. | Jan 2010 | A1 |
20100010669 | Lee et al. | Jan 2010 | A1 |
20100032224 | Liu | Feb 2010 | A1 |
20100063652 | Anderson | Mar 2010 | A1 |
20100066676 | Kramer et al. | Mar 2010 | A1 |
20100084513 | Gariepy et al. | Apr 2010 | A1 |
20100090661 | Chen et al. | Apr 2010 | A1 |
20100106344 | Edwards et al. | Apr 2010 | A1 |
20100145236 | Greenberg et al. | Jun 2010 | A1 |
20100169098 | Patch | Jul 2010 | A1 |
20100172287 | Krieter | Jul 2010 | A1 |
20100183195 | Sharma | Jul 2010 | A1 |
20100234993 | Seelinger et al. | Sep 2010 | A1 |
20100241289 | Sandberg | Sep 2010 | A1 |
20100261526 | Anderson et al. | Oct 2010 | A1 |
20100305778 | Dorneich et al. | Dec 2010 | A1 |
20100305781 | Felix | Dec 2010 | A1 |
20100312917 | Allport | Dec 2010 | A1 |
20100324753 | Okumatsu | Dec 2010 | A1 |
20110003640 | Ehrman | Jan 2011 | A9 |
20110018731 | Linsky et al. | Jan 2011 | A1 |
20110018794 | Linsky et al. | Jan 2011 | A1 |
20110022196 | Linsky et al. | Jan 2011 | A1 |
20110035054 | Gal et al. | Feb 2011 | A1 |
20110050940 | Lanz et al. | Mar 2011 | A1 |
20110060492 | Kaznov | Mar 2011 | A1 |
20110065488 | Okamura et al. | Mar 2011 | A1 |
20110071652 | Brown et al. | Mar 2011 | A1 |
20110071702 | Wang et al. | Mar 2011 | A1 |
20110082566 | Herr et al. | Apr 2011 | A1 |
20110087371 | Sandberg et al. | Apr 2011 | A1 |
20110153885 | Mak et al. | Jun 2011 | A1 |
20110184590 | Duggan et al. | Jul 2011 | A1 |
20110213278 | Horak et al. | Sep 2011 | A1 |
20110234488 | Ge et al. | Sep 2011 | A1 |
20110250967 | Kulas | Oct 2011 | A1 |
20110273379 | Chen et al. | Nov 2011 | A1 |
20110291926 | Gokturk et al. | Dec 2011 | A1 |
20110313568 | Blackwell et al. | Dec 2011 | A1 |
20110320830 | Ito | Dec 2011 | A1 |
20120009845 | Schmelzer | Jan 2012 | A1 |
20120035799 | Ehrmann | Feb 2012 | A1 |
20120065747 | Brown et al. | Mar 2012 | A1 |
20120083945 | Oakley et al. | Apr 2012 | A1 |
20120083962 | Sato et al. | Apr 2012 | A1 |
20120106783 | Chang et al. | May 2012 | A1 |
20120143482 | Goossen et al. | Jun 2012 | A1 |
20120146775 | Kudo et al. | Jun 2012 | A1 |
20120149359 | Huang | Jun 2012 | A1 |
20120167014 | Joo et al. | Jun 2012 | A1 |
20120173018 | Allen et al. | Jul 2012 | A1 |
20120173047 | Bernstein et al. | Jul 2012 | A1 |
20120173049 | Bernstein et al. | Jul 2012 | A1 |
20120185115 | Dean | Jul 2012 | A1 |
20120193154 | Wellborn et al. | Aug 2012 | A1 |
20120197439 | Wang et al. | Aug 2012 | A1 |
20120215355 | Bewley et al. | Aug 2012 | A1 |
20120244969 | Binder | Sep 2012 | A1 |
20120291926 | Misra et al. | Nov 2012 | A1 |
20120298049 | Cook et al. | Nov 2012 | A1 |
20120298430 | Schroll et al. | Nov 2012 | A1 |
20120306850 | Balan et al. | Dec 2012 | A1 |
20120307001 | Osako et al. | Dec 2012 | A1 |
20120309261 | Boman et al. | Dec 2012 | A1 |
20120311810 | Gilbert et al. | Dec 2012 | A1 |
20130050069 | Ota | Feb 2013 | A1 |
20130065482 | Trickett | Mar 2013 | A1 |
20130109272 | Rindlisbacher | May 2013 | A1 |
20130143482 | Regier | Jun 2013 | A1 |
20130265225 | Nasiri et al. | Oct 2013 | A1 |
20140371954 | Lee et al. | Dec 2014 | A1 |
Number | Date | Country |
---|---|---|
101 46 862 | May 2002 | DE |
03182290 | Aug 1991 | JP |
09254838 | Sep 1997 | JP |
2000218578 | Aug 2000 | JP |
2008-040725 | Feb 2008 | JP |
10-2008-040725 | Aug 2008 | KR |
10-2008-0073626 | Aug 2008 | KR |
10-2008-0092595 | Oct 2008 | KR |
10-2009-0000013 | Jan 2009 | KR |
10-0969873 | Jul 2010 | KR |
WO-9725239 | Jul 1991 | WO |
WO-2006049559 | May 2006 | WO |
WO-2012094349 | Jul 2012 | WO |
Entry |
---|
Non-Final Office Action mailed May 13, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 17 pages. |
Non-Final Office Action mailed Jun. 3, 2013, for related U.S. Appl. No. 13/342,914, filed Jan. 3, 2012, 32 pages. |
Koshiyama et al., Machine Translation for JP 2000-218578, Aug. 8, 2000, 11 Pages. |
Non-Final Office Action mailed Jun. 13, 2013, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 36 pages. |
GearBox Ball Prototype Jun. 29, 2010, Pictures from Video [online]. Orbotix, Inc., Jun. 30, 2010, 91 pages. Retrieved from the internet:<URL: http://www.youtube.com/watch?v=qRBM7bAaXpU>. |
Notification of Transmittal of International Search Report and The Written Opinion of the International Searching Authority mailed Aug. 28, 2013, for related PCT Application No. PCT/US2013/041023 filed May 14, 2013, 11 pages. |
Non-Final Office Action mailed Dec. 20, 2013, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 28 pages. |
Liu, Dalian et al., “Motion Control of a Spherical Mobile Robot by Feedback Linearization,” 7th WC on IC&A, Jun. 27, 2008,Chongqing, China, pp. 965-970. 6 pages. |
Shu, Guanghui et al., “Motion Control of Spherical Robot Based on Conservation of Angular Momentum,” IEEE Intl Conf on Mechatronics & Automation, Changchun, China, pp. 599-604. 6 pages, Aug. 9-12, 2009. |
Joshi, Vrunda et al., “Design, modeling and controllability of a spherical mobile robot”, 13th Natl Conf on Mechanisms &Machines (NaCoMM07) IISc, Bangalore, India, Dec. 13, 2007, pp. 1-6. |
Harmo, Panu et al., “Moving Eye—Interactive Telepresence over Internet with a Ball Shaped Mobile Robot,” Automation TechLab, Finland, Oct. 2, 2001. 6 pages. http://automation.tkk.fi/files/tervetaas/MovingEye4.pdf. |
Halme, Aarne, et al., “Motion Control of a Spherical Mobile Robot”, Helsinki, IEEE AMC '1996, pp. 259-264. 6 pages. |
Non-Final Office Action mailed Apr. 29, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 47 pages. |
Final Office Action mailed Jun. 6, 2014, for related U.S. Appl. No. 13/342,908, filed Jan. 3, 2012, 32 pages. |
U.S. Appl. No. 61/362,005, Schmelzer, filed Jul. 7, 2010, 10 pages. |
Non-Final Office Action mailed Oct. 16, 2012, for related U.S. Appl. No. 13/342,853, filed Feb. 19, 2013, 10 pages. |
Non-Final Office Action mailed Apr. 9, 2013, for related U.S. Appl. No. 13/342,892, filed Jan. 3, 2013, 19 pages. |
Notification of Transmittal of International Search Report and The Written Opinion of The International Searching Authority mailed Dec. 3, 2012, for related PCT Application No. PCT/US2012/020115 filed Jan. 3, 2012, 11 pages. |
Non-Final Office Action mailed Apr. 16, 2013, for related U.S. Appl. No. 13/342,884, filed Jan. 3, 2013, 20 pages. |
Notice of Allowance mailed Apr. 19, 2013, for related U.S. Appl. No. 13/342,853, filed Feb. 19, 2013, 11 pages. |
Notification of Transmittal of International Search Report and The Written Opinion of The International Searching Authority mailed Oct. 15, 2013, for related PCT Application No. PCT/US2013/050327 filed Jul. 12, 2013, 13 pages. |
Final Office Action mailed Nov. 15, 2013, for related U.S. Appl. No. 13/342,892, filed Jan. 3, 2013, 21 pages. |
Final Office Action mailed Nov. 18, 2013, for related U.S. Appl. No. 13/342,884, filed Jan. 3, 2013, 19 pages. |
Final Office Action mailed Nov. 18, 2013, for related U.S. Appl. No. 13/342,874, filed Jan. 3, 2012, 21 pages. |
Final Office Action mailed Nov. 13, 2013, for related U.S. Appl. No. 13/342,914, filed Jan. 3, 2012, 30 pages. |
European Search Report and European Search Opinion mailed Nov. 6, 2014, for related EP Application No. 12731945.7 filed Jul. 26, 2013. 7 pages. |
International Search Report and The Written Opinion mailed Dec. 17, 2014, for Application No. PCT/US2014/059973 filed Sep. 10, 2014, 13 pages. |
U.S. Appl. No. 61/362,005, filed Jul. 7, 2010, Schmelzer, Richard. |
“Roll, Pitch, and Yaw 1/ How Things Fly”, How Things Fly website, date unknown, retrieved from https://howthingsfly.si.edu/flight- dynamics/roll-pitch-and-yaw. |
Number | Date | Country | |
---|---|---|---|
20130173089 A1 | Jul 2013 | US |
Number | Date | Country | |
---|---|---|---|
61430023 | Jan 2011 | US | |
61430083 | Jan 2011 | US | |
61553923 | Oct 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13342853 | Jan 2012 | US |
Child | 13766455 | US |