Apparatus, system and method for operating an intelligent vehicle using separate devices - Patents.com

JP2024509342A5Inactive Publication Date: 2024-12-09INTELLIGENT RACING INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023535547
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-02-10
Filing Date
2022-02-09
Publication Date
2024-12-09
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing solutions for programming autonomous vehicles using mobile devices are complex and expensive, preventing widespread accessibility and practical application of artificial intelligence and programming skills.

Method used

A system that integrates a user's mobile device with a remote control vehicle using a chassis and circuitry, enabling AI programming and manual override, with virtual reality interfaces for enhanced user experience.

Benefits of technology

Provides a cost-effective and accessible means for users to practice AI programming and control remote vehicles, offering both manual and autonomous operation with real-time feedback, enhancing user engagement and learning.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Disclosed herein is a system for providing autonomous driving of a radio-controlled vehicle through a surrounding environment, which may include a modular device having at least one sensor configured to generate a signal related to a characteristic of the surrounding environment, a bed plate configured to be mechanically coupled to the RC vehicle, and a modular control circuit configured to be mechanically coupled to the bed plate and communicatively coupled to the modular device, the modular control circuit communicatively coupled to hardware of the RC vehicle and configured to control the RC vehicle in response to commands received from the modular device.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 148,040, filed February 10, 2021, entitled “METHOD AND SYSTEM FOR INTELLIGENT VEHICLES USING EXISTING MOBILE DEVICES,” the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates generally to automated vehicles and, more specifically, is directed to improved devices, systems, and methods that use a separate user device for automated driving of a vehicle. Summary of the Invention

[0003] In some embodiments, methods and systems are disclosed for providing an autonomous vehicle using sensors from a separate user device. In some embodiments, a system is presented for locating a user device on a remote control vehicle and controlling the remote control vehicle using sensors from the user device. In some embodiments, the system includes a unique chassis that is attached to an existing remote control vehicle so that the user's separate device can be attached to the remote control vehicle. In some embodiments, circuitry is included that provides an interface from the user's separate device to the remote control vehicle. The circuitry may provide a hardware layer to the system, and in some embodiments, a firmware layer is also included that links the hardware components together. In some embodiments, artificial intelligence programming is provided to the user's separate device to instruct how to utilize sensors in the user's separate device to control or drive the remote control vehicle. In some embodiments, manual control of the remote control vehicle is also included and can be used to override or supplement the control on the user's separate device.

[0004] In some embodiments, a system is deployed to provide autonomous driving of a remote-controlled (RC) vehicle using a user's mobile device. The mobile device may include at least one sensor and a wired or wireless interface. The system may include a chassis configured to be attached to the RC vehicle. The chassis may include a slot configured to carry a user's smartphone and circuitry configured to communicatively couple to the RC vehicle and transmit signals to operate the RC vehicle. The circuitry may include an interface for connecting to the wired or wireless interface of the user's mobile device and may be configured to receive commands from the user's mobile device that may be routed to the RC vehicle.

[0005] In some embodiments of the system, the circuitry is further configured to receive commands from a user's mobile device utilizing the at least one sensor.

[0006] In some embodiments, the system further includes a virtualization layer represented by software or firmware configured to provide a platform for programming artificial intelligence (AI) for controlling the RC vehicle.

[0007] In some embodiments of the system, the virtualization layer includes a simulator abstraction module, an autonomous driving abstraction module, and a vehicle hardware abstraction module.

[0008] In some embodiments of the system, the virtualization layer is configured to provide a platform for programming the AI ​​via a software simulator connected to the simulator abstraction module, the software simulator operating on a user device separate from the user's mobile device.

[0009] In some embodiments, the system further includes an interface to a virtual reality (VR) or augmented reality (AR) device that the user can wear to enable the user to see the camera view of the user's mobile device while the mobile device is attached to the RC vehicle when the RC vehicle is moving.

[0010] In some embodiments of the system, the VR or AR interface is configured to use the visual data streaming capabilities of the user's mobile device to provide live visual streaming to the VR or AR device.

[0011] In some embodiments of the system, the circuitry is further configured to communicate with a manual interface to the RC vehicle.

[0012] In some embodiments of the system, the circuitry is further configured to send commands to the RC vehicle based on input received from the manual interface.

[0013] In some embodiments of the system, the circuitry includes a safe mode component configured to override commands received from a user's mobile device. [Brief description of the drawings]

[0014] Certain embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

[0015] [Figure 1] FIG. 1 illustrates a system for operating an intelligent vehicle using separate devices in accordance with at least one non-limiting embodiment of the present disclosure.

[0016] [Diagram 2] FIG. 2 illustrates a functional block diagram of the system of FIG. 1 in accordance with at least one non-limiting embodiment of the present disclosure.

[0017] [Diagram 3] FIG. 3 illustrates a block diagram of a software architecture employed by the devices of the system of FIG. 1 in accordance with at least one non-limiting embodiment of the present disclosure;

[0018] [Figure 4] FIG. 4 illustrates a block diagram of the virtualization layer of FIG. 3 in accordance with at least one non-limiting embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Examples of methods, devices, and systems (e.g., machines) are presented for controlling a driving vehicle using an existing user's mobile device and programming the control of the driving vehicle with artificial intelligence via the user's mobile device. As an entry point for a broader audience to become familiar with artificial intelligence (AI) and computer programming, a remote control (RC) vehicle with an AI-controlled interface can provide a fun and tangible entry point. In many cases, the hardware and software required for programming, especially AI practice, is very complex, and current solutions provide expensive barriers that prevent these skills from being experienced by a broad audience. Aspects of the present disclosure provide a solution for connecting a user's existing mobile device, such as a smartphone, to an existing RC vehicle, such as a regular RC car on the market, and programming the RC with autonomous driving and control with minimal additional equipment.

[0020] In some embodiments, the hardware includes a chassis that mounts on top of the RC car and includes a slot to hold a user's smartphone. Circuitry coupled to the chassis interfaces with sensors on the attached smartphone, such as cameras, LIDAR, touch screens, microphones, speakers, positioning systems, Wi-Fi, Bluetooth, cellular systems, etc., to communicate instructions to the RC car. Software downloadable to the smartphone enables the user to do AI programming, and is used to control the RC car by accessing the smartphone's sensors and sending commands to circuitry coupled to the attached chassis. In this way, using only an existing smartphone and the hardware and software of the present disclosure, a user can implement AI algorithms in the RC car to perform autonomous driving. The user can then practice their AI programming skills, refining and perfecting the use of sensors and algorithms in a practical way with immediate feedback. This allows for a cost-effective and more easily accessible solution, introducing more people to AI and programming in general.

[0021] In some embodiments, the exemplary hardware and software components may be applied to other existing vehicles, such as aerial robots, legged robots, or robotic arms. A user's smartphone, when coupled to a robot, may provide sensing capabilities that provide input for use in AI programs. The hardware and software interfaces of the present disclosure may connect the smartphone's sensors and programs by a user to control the robot.

[0022] In some embodiments, the circuitry coupled to the attached chassis also allows for a manual override, such as a switch, and receives input from an RC manual control device, typically provided with the purchase of the RC vehicle. Manual control can increase safety by making the RC vehicle easier to acquire, increase feedback, and provide flexibility in the number of ways the RC vehicle can be used. For example, while in line of sight, manual control of the RC vehicle can be used, but when out of line of sight, AI control of the RC vehicle provided by the attached smartphone can be used.

[0023] In some embodiments, software downloaded to the smartphone provides a virtual reality interface that allows the user to see what the smartphone's camera sees when attached to an RC car. The software may utilize the camera data and transmit it to a VR device worn by the user, allowing the user to experience the movement of the RC car while it is being driven autonomously or manually.

[0024] In some embodiments, the AR and VR principles described herein may also be implemented in gaming scenarios such as e-sports or handheld consoles. Peer-to-peer racing with multiple vehicles and users' respective mobile devices may be linked together in a real-world setting utilizing the intelligent RC vehicles of the present disclosure. Each user may participate using the perspective from the camera of their mobile device.

[0025] In some embodiments, a device for mounting a mobile device to another robot is also provided. Similar to the chassis provided herein, another similar mounting device can be attached to the other robot to utilize the user's mobile device sensors. The principles described herein allow the user to control another type of robot in an AR or VR environment. Additionally, the virtualization layer disclosed below may allow the other type of robot to be autonomously controlled using sensors from a separate device, such as the user's mobile device.

[0026] Referring now to FIG. 1, a system 100 for operating an intelligent vehicle 102 using a separate device 104 is illustrated in accordance with at least one non-limiting embodiment of the present disclosure. According to the non-limiting embodiment of FIG. 1, the system 100 may include the vehicle 102 itself along with a chassis 106 configured to house the separate device 104. Without loss of generality, the device 104 may be positioned to have a forward, aft, and / or other three-dimensional orientation relative to the system 100. As shown in FIG. 1, the vehicle 102 may include one or more wheels 108 configured to enable the vehicle 102 to traverse a terrain. For example, the vehicle 102 of FIG. 1 may include a form factor similar to that of a remotely controlled vehicle. However, according to other non-limiting embodiments, the vehicle 102 may include other components (e.g., engines, nose cones, rotors, propellers, fins, wings, air cushions, seals, etc.) such that the vehicle 102 may alternatively and / or additionally be configured to traverse other mediums including air, water, and / or space, among others. In other words, according to other non-limiting embodiments, the vehicle 102 may be configured as a remotely controlled drone, an aircraft, a helicopter, a rocket, a boat, a submarine, and / or a hovercraft, among other vehicle types.

[0027] With further reference to FIG. 1 , the system 100 may also include a chassis 106 configured to house the device 104 that is structurally and / or functionally separate from the vehicle 102 itself. In other words, the device 104 of FIG. 1 may be commercially secured by a user for a primary purpose other than the operation of the vehicle 102. In particular, the device 104 may be configured for wireless and / or wired communication with other devices and may include one or more sensors 104 configured to detect features of the surrounding environment surrounding the device 104. For example, according to a non-limiting embodiment of FIG. 1 , the device 104 may include a user's smartphone configured for wireless communication over an ad-hoc (e.g., Bluetooth, near field communication, RFID, etc.) and / or infrastructure network (e.g., cellular, WiFi, radio, etc.) network and may include one or more sensors 110, such as a camera, configured to visually detect features in the surrounding environment and generate image data associated with the detected features. It should be understood that the device 104 of FIG. 1 may include any number of antennas, processors, memory, receivers, transmitters, and / or transceivers to enable the aforementioned functions. However, according to other non-limiting embodiments, the device 104 may include a tablet, a personal digital assistant, a laptop computer, and / or a smartwatch, among other devices configured for sensing and computing purposes. According to still other non-limiting embodiments, the device 104 may include other sensors configured to detect other features within the surrounding environment, including, among other things, a light detection and ranging sensor ("LIDAR") configured to characterize and / or map the surrounding environment, a microphone configured to detect sonic vibrations, a gyroscope configured to detect mechanical vibrations, and / or an infrared camera configured to detect thermal vibrations within the surrounding environment. Without loss of generality, the sensor 110 of FIG. 1, or any of the other sensors referenced with respect to other non-limiting embodiments, may be positioned to face forward, backward, or in other three-dimensional orientations relative to the vehicle 100.

[0028] With further reference to FIG. 1 , the chassis 106 may be geometrically configured to accommodate and secure the device 104 to the vehicle 102. For example, according to a non-limiting embodiment of FIG. 1 , the chassis 106 may define a slot 112 of a geometric shape corresponding to the device 104 and may include one or more walls 114 configured to secure the device 104 to the vehicle 102 and prevent it from becoming detached from the vehicle 102 in response to vibrations resulting from operation of the vehicle 102. The chassis 106 may be integral to the vehicle 102 and / or may be configured for selective mechanical and / or electrical coupling to the vehicle 102. For example, according to a non-limiting embodiment of FIG. 1 , the chassis 106 may include a mount 116 configured as a faceplate having one or more coupling elements 118 configured to mechanically secure the chassis 106 and the device 102 mounted within the chassis 106 to the vehicle 102. According to some non-limiting embodiments, the coupling elements 118 may be holes and / or tapped insertions configured to receive screws and / or bolts that connect the chassis 106 to the vehicle 102 .

[0029] According to a non-limiting embodiment of FIG. 1 in which the chassis 106 is configured for selective mechanical and electrical coupling, the chassis 106 can be attached to any commercially available remotely controlled vehicle, such as the vehicle 102 of FIG. 1. As such, the chassis 104 can be manufactured separately from the vehicle 102 via a variety of materials and processes. For example, according to some non-limiting embodiments, the chassis 106 and / or the mount 116 can be manufactured by three-dimensional printing, plastic molding, and / or being machined from wood or metal (e.g., via computer numerical control ("CNC") methods, etc.). The mount 116 can be configured to mechanically interface with the bed plate 120 via a number of slots 122 disposed throughout the bed plate 120. Similar to the chassis 196 and / or the mount 116, the bed plate 120 can be manufactured by three-dimensional printing, plastic molding, and / or being machined from wood or metal (e.g., via computer numerical control ("CNC") methods, etc.). Additionally, each of the slots 122 disposed throughout the bed plate 120 may be configured to function as a mechanical and / or electrical interface such that the device 104 may be effectively integrated into the mechanical and electrical systems of the vehicle 102. For example, a first slot (not visible) of the plurality of slots 122 may be configured to accommodate the chassis 106, while a second slot (not visible) of the plurality of slots 122 may be configured to accommodate a control circuit 124, such as a microprocessor or logic-based controller, among others. The bed plate 120 may further include one or more electrical connections 126 (e.g., circuits, wires, connectors, etc.) configured to establish electrical communication between the device 104 and the control circuit 124. One such electrical connection 126 (not visible) may be specialized and dimensionally positioned within the chassis 106 such that the electrical connection 126 aligns with a particular data connection (e.g., Lightning cable, Micro Universal Serial Bus ("USB"), USB-C, etc.) on the device 104, thereby enabling the device 104 to send and receive signals to and from the control circuit 124.Of course, according to other non-limiting embodiments, the device 104 may be configured to wirelessly communicate signals to and from the control circuitry 124, for example, via an ad-hoc link (e.g., Bluetooth, NFC, etc.). According to the non-limiting embodiment of FIG. 1, the device 104 may be a smartphone, such as, for example, an Apple iPhone, or a Google Android, and the control circuitry 124 may be an Arduino microcontroller. Thus, the chassis 106, mount 116, bedplate 120, and slot 122 of FIG. 1 may be geometrically and electrically configured to accommodate such devices.

[0030] Minor modifications may be implemented to the vehicle 102 of FIG. 1 to allow it to operate effectively. For example, the vehicle 102 of FIG. 1 may be rewired via one of the slots 122 a pulse width modulated (PWM) signal from a remote control receiver specific to the "off the shelf" vehicle 102 to a control circuit 124 mounted on the bed plate 120. One or more electrical connections 126 (e.g., circuits, wires, connectors, etc.) are configured to establish electrical communication between the device 104 and the control circuit 124 such that the control circuit 124 can receive control signals from the device 104 and forward them to a chassis 128 of the vehicle 102 according to a user selection and / or intended use. According to some non-limiting embodiments, the control circuit 124 may be configured to selectively accept one of a plurality of signals it receives for forwarding to the chassis 128 of the vehicle 102 for operation, as discussed in further detail herein.

[0031] In other words, the device 104 of FIG. 1 may be configured to communicate with the control circuitry 124, which may be configured to communicate with the chassis 128 of the vehicle 102 via one or more electrical connections 126. Additionally, the chassis 106 may be specifically configured for the device 104 such that the desired sensors 110 of the device 104 are preferably positioned to aid a user using the device 104 to assist in manually and / or autonomously driving the vehicle 102. According to FIG. 1, the slots 112 defined by the chassis 106 may accommodate the device 104 such that the one or more sensors 110 are in a desired position relative to the vehicle 102. For example, if the one or more sensors 110 are cameras of the device 104, the chassis 106 may be configured such that the device 104, when properly installed, may serve as a visual input for manual and / or automated driving of the vehicle. Thus, the system 100 of FIG. 1 may enable manual and / or automated driving of the vehicle 102 without the need for additional sensors. In this manner, the system 100 of FIG. 1 may enable increased and more efficient access to the operation of a manual and / or motor vehicle 102 for the average consumer.

[0032] According to some non-limiting embodiments, the control circuitry 124 may be communicatively coupled to an operating platform for the vehicle 102, or to a memory configured to store software capable of assisting in the operation of the vehicle 102. For example, the software may be installed on the memory of the device 104 to provide the control circuitry 124 and the vehicle 102 with various degrees of functionality necessary for desired operation. According to some non-limiting embodiments, the software may be a mobile application downloaded by a user via the device 104 from an "app store" or other acquisition means. The platform contemplated by the present disclosure and implemented via the system 100 of FIG. 1 may generally provide functionality in the form of at least three tasks: 1) the software may instruct the device 104 to acquire image data and / or motion data utilizing one or more sensors 110 (e.g., via a camera, a microelectromechanical system ("MEMS") gyroscope, an accelerometer, an inertial measurement unit ("IMU"), etc.); and 2) the software may instruct the device 104 to transmit the generated data to a remote computing device, such as another device of the user, for rendering. and 3) the software can make autonomous driving decisions for the system 100 based on a number of artificial intelligence and / or machine learning algorithms that utilize the data of the sensors 110 locally without the aid of remote computing resources not on board the device 104, and can further control the device 104 to issue commands in accordance with the autonomous driving decisions to control the vehicle 102. In other words, the device 104 and software can generate and provide to the user a first-person view of the operating environment from the perspective of the vehicle 102, such that the software can enable the user to operate the vehicle beyond line of sight. In this manner, the system 100 of FIG. 1 can be implemented to generate a virtual immersive feeling of an on-board driving position.

[0033] The design of the software can be portable or flexible so that the software can be modified to allow for changes in which control circuitry can effectively control the vehicle 102, or a robotic system disposed on the vehicle 102, without adding significant costs to expensive modifications. As previously mentioned, the software can be executed by a device 104, such as a smartphone, configured to perform a wide range of autonomous tasks at the command of the software and / or user input, limited only by the hardware design and capabilities of the device 104 and / or one or more sensors 110 on the chassis 128 of the vehicle 102. Thus, the software can facilitate automated operation of the vehicle 102. Additionally and / or alternatively, the software can provide a user with the ability to override commands generated by the software, thereby facilitating manual operation of the vehicle 102. Furthermore, the inclusion of a separate device 104 and control circuitry 124 allows the control circuitry 124 to override commands transmitted to the robotic chassis, thereby facilitating instantaneous switching of vehicle operation between autonomous and manual control. More specifically, the software on the device 104 may simply pass through the manual control commands issued by the user to the control circuitry 124 without further modification. This allows the user to directly control the vehicle 102. Secondly, the software on the device 104 may completely override the manual control commands issued by the user, in effect allowing some AI algorithms to take full control of the vehicle 102. This includes fully autonomous driving scenarios without human oversight, and emergency safety override scenarios, such as stopping the vehicle 102 before an imminent collision. Finally, the software on the device 104 may modify the manual control commands issued by the user by augmenting additional control commands. In some autonomous driving scenarios, this allows the user to control the vehicle 102 through software for enhanced safety or performance, such as autopilot features including dynamic cruise control, collision avoidance, automatic lane changing, and automatic parking.However, in some e-sports scenarios, software on the device 104 may add control constraints to limit the performance of the vehicle 102 according to some gameplay, thus making the vehicle 102 more difficult for the user to control. For example, in a virtual reality environment, the position of the vehicle 102 may collide with a virtual obstacle (such as a virtual puddle or a virtual sand trap). Software synchronized with the virtual reality environment may reduce the drivability of the throttle or steering of the vehicle 102, effectively creating a challenge for the user to control the vehicle 102 when the user perceives a virtual obstacle in the virtual reality environment.

[0034] 2, a functional block diagram of the system 100 of FIG. 1 is shown illustrating various interactions between the aforementioned system 100 components in accordance with at least one non-limiting embodiment of the present disclosure. As previously mentioned, the chassis 128 of the vehicle 102 (FIG. 1) may provide the infrastructure that supports the operation of the vehicle 102 (FIG. 1), including various other components such as motors 212 and servo mechanisms 214 configured to receive command signals 202 (e.g., PWM signals, etc.) from the control circuitry 124 and generate telemetry that can be sent back to the control circuitry 124 via telemetry signals 202. This functional configuration is illustrated by the block diagram of FIG. 2. As previously mentioned, the control circuitry 124 may include an Arduino® type microcontroller coupled to the chassis 128 of the vehicle 102 (FIG. 1), which may be wired to control the motors 212 and / or servos 214 of the vehicle 128. Thus, the control circuitry 124 can receive vehicle 102 (FIG. 1) telemetry 202 from various components of the RC to provide continuous control and operation of the vehicle 102 (FIG. 1). The chassis 128 can also support positioning of a separate device 104, such as a user's smartphone. As previously described, the device 104 can be communicatively coupled to the control circuitry 124 via a wired or wireless connection, via the aforementioned electrical connection 126 (FIG. 1) and / or Bluetooth. The device 104 can provide command signals 204 to the control circuitry 124 via a wired and / or wireless connection based on data generated by its sensors 110 (FIG. 1), such as a camera. The device 104, and more specifically, the software implemented by the device 104, can include an artificial intelligence platform, such as a neural network, or a machine learning platform, such as a supervised, unsupervised, or augmented algorithm configured to operate the vehicle 102 autonomously. According to some non-limiting embodiments, the vehicle 102 may still be manually operated via a radio control receiver 210, which may be configured to send commands 204 and receive telemetry 202 from the control circuitry 124.

[0035] Overall, the foregoing features of the present disclosure allow for the integration of a stock vehicle 102 (FIG. 1) chassis 128 with a separately manufactured chassis 106 (FIG. 1), bed plate 120 (FIG. 1), control circuitry 124, and equipment 104 to form an improved vehicle 102 (FIG. 1) that is less expensive, more portable, and significantly more powerful, and provides a technological improvement over conventional stock vehicles 102 (FIG. 1).

[0036] Referring now to FIG. 3, a block diagram illustrating only some of the technical improvements provided by the system 100 of FIG. 1 is illustrated in accordance with at least one non-limiting embodiment of the present disclosure. According to the non-limiting embodiment of FIG. 3, the system 100 (FIG. 1) can utilize the capabilities of the device 104 to provide an augmented reality ("AR") and / or virtual reality ("VR") experience to the vehicle 102 (FIG. 1). The software can include an AR / VR game layer 302, a simulation layer 304, and / or a virtualization layer 306. The AR / VR game layer 302 can generate an augmented or virtual game based on image data 308 received from the device 104. The simulation layer 304 can generate a simulation of the vehicle 102 (FIG. 1) and the surrounding environment based on telemetry 310 received from the device 104. The virtualization layer 306 can generate an autonomous driving code 312 based on image data 308 and / or telemetry 310 received from the device 104. The generated code 312 may be downloaded to the device 104 and implemented to perform and / or improve autonomous driving of the vehicle 102 (FIG. 1).

[0037] According to a non-limiting embodiment of FIG. 3, the device 104 may be configured to stream captured video data via its one or more sensors 110 (FIG. 1), and may stream the captured video data via a wired or wireless connection to a head mounted display (not shown) worn by a user. The software executed by the device 104 may also transmit telemetry data associated with the vehicle 102 (FIG. 1) in real time to a user's remote computing device (not shown) for generating an AR and / or VR experience, or for alternative use in connection with a vehicle 102 (FIG. 1) simulation provided by the software. For example, such telemetry data may include six degrees of freedom position, velocity, acceleration, and / or steering angle associated with the vehicle 102 (FIG. 1), among other types of telemetry data. Regardless of whether the vehicle 102 (FIG. 1) is operated autonomously or manually, the user can experience, via the receiver 210 (FIG. 2), what the vehicle 102 (FIG. 1) is experiencing via one or more sensors 110 of the device 104 (FIG. 1) when the device 104 (FIG. 1) is mounted on the vehicle 102 (FIG. 1). The user can also experience driving in a virtual simulation environment generated based on telemetry data provided by the vehicle 102 (FIG. 1) via a virtual simulation vehicle 102 (FIG. 1) generated by the vehicle 102 (FIG. 1) telemetry. Similarly, the telemetry data generated by the system 100 (FIG. 1) can be used to update code or train artificial intelligence and / or machine learning algorithms to improve the simulation, as described in more detail herein.

[0038] It can be difficult to program code on a device 104, such as a smartphone, to perform a particular autonomous task. Indeed, programming applications to precisely control a robotic system, such as the vehicle 102 of FIG. 1, can be difficult because such applications are typically not programmed into the phone itself, but rely on a more capable personal computer to program the code. Furthermore, the code typically undergoes a "deployment" procedure in which it is installed on the device 104. However, because the device 104, as contemplated by the present disclosure, is integrated with the vehicle 102 (FIG. 1), the device 104 travels with the vehicle 102 (FIG. 1) and is separate from the personal computer that can program the device 104 with updates. Obviously, this complicates the introduction and testing of autonomous code and code updates that can improve the means by which the device 104 is implemented to operate the vehicle 102 (FIG. 1). However, the system 100 (FIG. 1) contemplated by the present disclosure solves this problem through a virtualization layer 306 that is deployed through the device 104. According to some non-limiting aspects, the virtualization layer 306 may include middleware to allow the vehicle 102 (FIG. 1) control code to be programmed and thoroughly tested on a simulator system.

[0039] 4, a block diagram of a software architecture 400 including the virtualization layer 306 of FIG. 3 is illustrated in accordance with at least one non-limiting embodiment of the present disclosure. According to the non-limiting embodiment of FIG. 4, the architecture 400 includes, among others, a simulation and / or visualization stack 402, a machine learning library stack 404, and a vehicle hardware stack 406. Additionally, apart from the virtualization layer 306, the architecture 400 may further include an autonomous driving algorithm library 405. As such, the virtualization layer 306 may be configured to obtain and send data to the autonomous driving algorithm library 405 from the software simulator 304, the machine learning library 408, and hardware from the vehicle 102 (FIG. 1), such as actuators 410 and / or sensors 412.

[0040] According to a non-limiting embodiment of FIG. 4, the virtualization layer 306 may include a simulator abstraction 414, an autonomous driving abstraction 416, and / or a vehicle hardware abstraction 416. Optionally, the virtualization layer 306 may include an abstraction of the device 104 (FIG. 1), or may be further configured to at least receive signals generated by one or more sensors 110 (FIG. 1) on the device 104 (FIG. 1). In this manner, the virtualization layer 306 may communicate with the software simulator 304, various machine learning libraries 402, and / or the vehicle 102 (FIG. 1) itself. In this manner, the virtualization layer 306 may generate operational code and / or automation algorithms, as well as updates, for the vehicle 102 (FIG. 1) that may be deployed to the device 104 (FIG. 1) without required code changes. In other words, the virtualization layer 306 can abstract and virtualize the behavior of the vehicle 102 ( FIG. 1 ) and the surrounding environment through which the vehicle 102 ( FIG. 1 ) traverses, and can interface with the software simulator 304, machine learning library 402, and / or hardware system 404 of the vehicle 102 ( FIG. 1 ). The virtualization layer 306 can utilize these inputs to communicate with the autonomous driving software stack 420, which can utilize the virtual inputs to implement and / or improve the environment mapping engine 422, environment perception engine 424, motion planning engine 426, and / or controller 428 of the autonomous driving algorithm library 405.

[0041] By combining the low cost design of adding a smartphone as a robot's "brain," the system's compatibility with most RC cars and potentially other robotic systems, and the ease of use of the software deployment and testing process using a virtualization solution, aspects of the present disclosure provide a groundbreaking user experience for consumers to easily add intelligence to "non-smart" or "dumb" robotic systems.

[0042] Various aspects of the subject matter described herein are set forth in the following numbered clauses.

[0043] Clause 1: 1. A system for providing autonomous driving of a radio-controlled (RC) vehicle using a user's mobile device, the system comprising: a chassis configured to be mounted on the RC vehicle, the chassis including a slot configured to carry a user's smartphone, the mobile device including at least one sensor and a communications interface; and circuitry configured to communicatively couple to the RC vehicle and transmit signals to operate the RC vehicle, the circuitry including an interface for connecting to a communications interface of the user's mobile device, the circuitry configured to receive commands from the user's mobile device that can be routed to the RC vehicle.

[0044] Clause 2: The system of claim 1 , wherein the circuitry is further configured to receive commands from a user's mobile device utilizing the at least one sensor.

[0045] Clause 3: 3. The system of any of clauses 1 or 2, further comprising a virtualization layer represented by software or firmware configured to provide a platform for programming artificial intelligence (AI) for controlling the RC vehicle.

[0046] Article 4: The system of any of clauses 1 to 3, wherein the virtualization layer includes a simulator abstraction module, an autonomous driving abstraction module, and a vehicle hardware abstraction module.

[0047] Article 5: The system of any of clauses 1 to 4, wherein the virtualization layer is configured to provide a platform for programming the AI ​​via a software simulator connected to the simulator abstraction module, and the software simulator is operated on a user device separate from the user's mobile device.

[0048] Article 6: The system of any of clauses 1-5, further including an interface to a virtual reality (VR) or augmented reality (AR) device wearable by the user to enable the user to view a camera view of the user's mobile device while the mobile device is attached to the RC vehicle when the RC vehicle is moving.

[0049] Article 7: The system of any of clauses 1-6, wherein the VR or AR interface is configured to provide live visual streaming to the VR or AR device using visual data streaming capabilities of the user's mobile device.

[0050] Article 8: The system of any of clauses 1-7, wherein the circuitry is further configured to communicate with a manual interface to the RC vehicle.

[0051] Article 9: The system of any of clauses 1-8, wherein the circuitry is further configured to send commands to the RC vehicle based on input received from the manual interface.

[0052] Article 10: 10. The system of any of clauses 1-9, wherein the circuitry includes a safe mode component configured to override commands received from a user's mobile device.

[0053] Article 11: 1. A system for providing autonomous driving of a radio-controlled (RC) vehicle through an ambient environment, the system comprising: a modular device including at least one sensor configured to generate a signal related to a characteristic of the ambient environment; a bed plate configured to be mechanically coupled to the RC vehicle, the bed plate including a plurality of slots; a modular control circuit configured to be mechanically coupled to the bed plate via a first slot of the plurality of slots, the modular control circuit configured to be communicatively coupled to the modular device, the modular control circuit configured to be communicatively coupled to hardware of the RC vehicle and to control the RC vehicle in response to commands received from the modular device; and a chassis configured to be mechanically coupled to the bed plate via a second slot of the plurality of slots, the chassis further configured to receive and removably secure the modular device to the RC vehicle.

[0054] Article 12: 12. The system of claim 11, wherein the modular device includes a processor and a memory configured to store an algorithm that, when executed by the processor, causes the processor to receive signals from the sensors; determine characteristics of the surrounding environment detected by the sensors based on the signals received from the sensors; generate command signals based at least in part on the determined characteristics of the surrounding environment; and transmit the generated command signals to a control circuit, the generated command signals causing the control circuit to autonomously operate the RC vehicle in a manner predetermined by the algorithm.

[0055] Article 13: 13. The system of claim 11 or 12, wherein the memory of the modular device is further configured to store a virtualization layer that, when executed by the processor, causes the processor to receive a second signal from the sensor, determine a second characteristic of the surrounding environment detected by the sensor, and autonomously modify an algorithm stored in the memory of the modular device based at least in part on the determined second characteristic of the surrounding environment without interrupting autonomous operation of the RC vehicle.

[0056] Article 14: The system of any of clauses 11-13, wherein the memory of the modular device is further configured to store a simulation layer that, when executed by the processor, causes the processor to generate a simulated RC vehicle within a simulated surrounding environment based at least in part on the signals received from the sensor.

[0057] Article 15: The system of any of clauses 11-14, wherein the simulation layer, when executed by the processor, causes the processor to receive telemetry from the RC vehicle, and wherein generation of the simulated RC vehicle and the simulated surrounding environment is further based on the telemetry received from the RC vehicle.

[0058] Article 16: 16. The system of any of clauses 11-15, wherein the telemetry includes at least one of six degrees of freedom position of the RC vehicle, velocity of the RC vehicle, acceleration of the RC vehicle, and steering angle of the RC vehicle, or a combination thereof.

[0059] Article 17: 17. The system of any of clauses 11-16, further comprising a head mounted display configured to be worn by a user of the system, the head mounted display configured to display the simulated RC vehicle within the simulated surrounding environment.

[0060] Article 18: 11. A method for autonomously operating a radio-controlled (RC) vehicle through a surrounding environment, the method comprising: selectively coupling a modular device to the RC vehicle, the modular device including at least one sensor configured to generate a signal related to a characteristic of the surrounding environment; selectively coupling a modular control circuit to the RC vehicle; receiving a signal from the sensor via a remote computing device; determining, via the remote computing device, a characteristic of the surrounding environment detected by the sensor based on the signal received from the sensor; generating, via the remote computing device, a command signal based at least in part on the determined characteristic of the surrounding environment; transmitting, via the remote computing device, the generated command signal to the modular control circuit; and autonomously operating the RC vehicle in accordance with the received command signal via the modular control circuit.

[0061] Article 19: 19. The method of claim 18, further comprising: generating, via the remote computing device, a simulated RC vehicle within the simulated surrounding environment based at least in part on the signals received from the sensor; and displaying, via a head mounted display communicatively coupled to the remote computing device, the simulated RC vehicle within the simulated surrounding environment.

[0062] Article 20: The system of either clause 18 or 19, further including receiving telemetry from the RC vehicle via the remote computing device, and updating the simulated RC vehicle and the simulated surroundings based at least in part on the telemetry received from the RC vehicle.

[0063] Article 21: 21. The method according to any one of clauses 18 to 20, comprising receiving, via the modular device, a manually implemented command signal from a user of the RC vehicle; and modifying, via a platform executed by the modular device, the manually implemented command signal based on an autonomously generated parameter characteristic of the simulated surrounding environment.

[0064] Article 22: 22. The method according to any of clauses 18 to 21, wherein the autonomously generated parameters are generated based on signals received from sensors and correspond to determined characteristics of the surrounding environment.

[0065] Article 21: 21. The method of any of clauses 18 to 20, wherein the autonomously generated parameters include generated properties of a simulated ambient environment that are not present in the ambient environment.

[0066] All patents, patent applications, publications, or other disclosure materials mentioned herein are incorporated herein by reference in their entirety, as if each individual reference were expressly incorporated by reference. All references and any material, or portions thereof, that are said to be incorporated herein by reference are incorporated herein, but only to the extent that the incorporated material does not contradict any existing definitions, descriptions, or other disclosed material set forth in this disclosure. Accordingly, and to the extent necessary, the present disclosure set forth herein takes precedence over any conflicting material incorporated herein by reference, and this disclosure is expressly set forth in this application reference.

[0067] Various exemplary and exemplary embodiments are described. The embodiments described herein are understood to provide exemplary features of various details of the various embodiments of the present disclosure, and therefore, unless otherwise specified, to the extent possible, one or more features, elements, components, ingredients, components, structures, modules, and / or aspects of the disclosed aspects can be combined, separated, substituted, and / or rearranged with or relative to one or more other features, elements, components, ingredients, components, structures, modules, and / or aspects of the disclosed aspects without departing from the scope of the present disclosure. Thus, one skilled in the art will recognize that various substitutions, modifications, or combinations of any of the exemplary embodiments can be made without departing from the scope of the claims. Moreover, one skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the various embodiments of the present disclosure upon review of this specification. Thus, the present disclosure is not limited by the description of the various embodiments, but by the scope of the claims.

[0068] Those skilled in the art will recognize that the terms used herein, particularly in the appended claims (e.g., the body of the appended claims), are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "at least having," and the term "includes" should be interpreted as "includes but not limited to"). It will be further understood by those skilled in the art that where recitation of a specific number of claims is intended, such intention will be expressly recited in the claim, and in the absence of such recitation, no such intention exists. For example, as an aid to understanding, the following appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce the recitation of claims. However, the use of such phrases should not be construed as implying that the introduction of a claim recitation with the indefinite article "a" or "an" limits any particular claim containing such an introduced claim recitation to those claims that include only one such recitation, even when that same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a" and / or "an" should typically be construed to mean "at least one" or "one or more"), nor should the use of definite articles used to introduce claim recitations.

[0069] Moreover, even when a particular number of introduced claim recitations is explicitly recited, one of ordinary skill in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., an explicit recitation of "two recitations" without other qualifiers typically means at least two recitations, or more than two recitations. Furthermore, in such cases where a convention similar to "at least one of A, B, and C, etc." is used, such structure is generally intended in the sense that one of ordinary skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together). Even when the convention is "A, B, or C etc." is used, in examples, generally such constructions are intended in the sense that one of ordinary skill in the art would understand this convention (e.g., a system having at least one of A, B, and C includes, but is not limited to, systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together). It will be further understood by those of ordinary skill in the art that typically disjunctive words and / or phrases presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibility of including one of the terms, either of the terms, or both terms, unless the context dictates otherwise. For example, the phrase "A or B" is typically understood to include the possibilities of "A" or "B" or "A and B."

[0070] With respect to the appended claims, one of ordinary skill in the art will appreciate that the operations recited therein may generally be performed in any order. Also, while the claim recitations are presented in a sequence, it should be understood that the various operations may be performed in other orders than those described, or may be performed simultaneously. Examples of such alternative orderings may include overlapping, interleaving, interrupting, reordering, incremental, preparatory, supplementary, simultaneous, reverse, or other various orderings, unless the context dictates otherwise. Moreover, unless the context dictates otherwise, terms such as "responsive to," "related to," or other past tense adjectives are generally not intended to exclude such variations.

[0071] It should be noted that any reference to "one embodiment," "one aspect," "one example," "one example," etc. means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment," "in one embodiment," "in one example," and "in one example" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0072] As used herein, the singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0073] Directional expressions used herein, such as, but not limited to, top, bottom, left, right, lower, upper, front, back, and variations thereof, relate to the orientation of the elements as shown in the accompanying drawings and do not limit the scope of the claims, unless expressly stated otherwise.

[0074] The term "about" or "approximately" as used in this disclosure, unless otherwise specified, refers to an acceptable error for a particular value as determined by one of ordinary skill in the art, which depends in part on how the value is measured or determined. In certain embodiments, the term "about" or "approximately" refers to within 1, 2, 3, or 4 standard deviations. In certain embodiments, the term "about" or "approximately" refers to within 50%, 200%, 105%, 100%, 9%, 8%, 7%, 6%, 5%, 4%, 3%, 2%, 1%, 0.5%, or 0.05% of a given value or range.

[0075] In this specification, unless otherwise indicated, all numerical parameters are to be understood as being predicated and, in all instances, the numerical parameters should be modified by the term "about" given the inherent variability characteristic of the underlying measurement technique used to determine the numerical value of the parameter. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter set forth in this specification should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques.

[0076] Any numerical range recited herein includes all subranges deduced within the recited range. For example, a range of 1 to 100 includes all subranges between the recited minimum of 1 and the recited maximum of 100 (including the boundaries), i.e., the minimum is equal to or greater than 1, and the maximum is equal to or less than 100. Also, all ranges recited herein include the endpoints of the recited range. For example, a range "1 to 100" includes the endpoints 1 and 100. Any maximum numerical limitation recited herein is intended to include all lower numerical limitations assumed therein, and any minimum numerical limitation recited herein is intended to include all higher numerical limitations assumed therein. Accordingly, applicants reserve the right to amend this specification, including the claims, to explicitly recite any recited subrange within the explicitly recited range. All such ranges are inherently described herein.

[0077] Any patent application, patent, non-patent publication, or other disclosure material mentioned herein and / or listed in any application data sheet is incorporated herein by reference and, to the extent that it does not conflict with the present specification. Accordingly, and to the extent necessary, the present disclosure as expressly set forth herein takes precedence over any conflicting material incorporated herein by reference. Any material or portion thereof that is said to be incorporated herein by reference but that conflicts with existing definitions, statements, or other disclosure material set forth herein is incorporated only to the extent that no conflict arises between the incorporated material and the existing disclosure material.

[0078] The terms "comprise" (and any form of comprise, such as "comprises" and "comprising"), "have" (and any form of have, such as "has" and "having"), "include" (and any form of include, such as "includes" and "including"), and "contain" (and any form of contain, such as "contains" and "containing") are open-ended linking verbs. As a result, a system that "includes," "has," "includes," or "contains" one or more elements possesses those one or more elements, but is not limited to possessing only those one or more elements. Similarly, an element of a system, device, or apparatus that "includes," "has," "includes," or "contains" one or more features possesses those one or more features, but is not limited to possessing only those one or more features.

[0079] The foregoing detailed description describes various forms of apparatus and / or processes through the use of block diagrams, flow charts, and / or examples. Where such block diagrams, flow charts, and / or examples include one or more functions and / or operations, it will be understood by those skilled in the art that each function and / or operation within such block diagrams, flow charts, and / or examples, individually and / or collectively, can be implemented by a wide range of hardware, software, firmware, or substantially any combination. Those skilled in the art will recognize that some aspects of the forms disclosed herein can be equivalently implemented in integrated circuits, in whole or in part, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or substantially any combination thereof, and that designing circuitry and / or writing software and / or firmware code is within the skill of those skilled in the art in light of this disclosure. Further, those skilled in the art will appreciate that the mechanisms of the subject matter described herein can be distributed as one or more program products in a variety of forms, and that the illustrative forms of the subject matter described herein apply regardless of the particular type of signal-bearing medium used to actually effectuate the distribution.

[0080] The instructions used to program the logic to implement the various disclosed aspects may be stored in memory within the system, such as dynamic random access memory (DRAM), cache, flash memory, or other storage device. Additionally, the instructions may be distributed over a network or via other computer readable media. Thus, a machine readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including, but not limited to, a floppy disk, an optical disk, a compact disk read only memory (CD-ROM), a magneto-optical disk, a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a magnetic or optical card, a flash memory, or any tangible machine readable storage used in transmitting information over the Internet via electrical, optical, acoustic, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, non-transitory computer-readable media includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0081] As used in any embodiment herein, the term "control circuitry" may refer to, for example, hardwired circuitry, programmable circuitry (e.g., a computer processor, including one or more individual instruction processing cores, processing units, processors, microcontrollers, microcontroller units, controllers, digital signal processors (DSPs), programmable logic devices (PLDs), programmable logic arrays (PLAs), or field programmable gate arrays (FPGAs)), state machine circuitry, firmware that stores instructions executed by the programmable circuitry, and any combination thereof. The control circuitry may be embodied, collectively or individually, as circuitry that forms part of a larger system, e.g., an integrated circuit (IC), an application specific integrated circuit (ASIC), a system on a chip (SoC), a desktop computer, a laptop computer, a tablet computer, a server, a smartphone, etc. Thus, "control circuitry" as used herein includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program to at least partially execute a process and / or a device described herein, or a microprocessor configured by a computer program to at least partially execute a process and / or a device described herein), electrical circuitry forming a memory device (e.g., in the form of random access memory), and / or electrical circuitry forming a communication device (e.g., a modem, a communication switch, an optoelectronic device).Those skilled in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.

[0082] As used in any aspect herein, the term "logic" may refer to an application, software, firmware, and / or circuitry configured to perform any of the operations described above. Software may be embodied as a software package, code, instructions, instruction sets, and / or data recorded on a non-transitory computer-readable storage medium. Firmware may be embodied as hard-coded (e.g., non-volatile) code, instructions, or instruction sets, and / or data in a memory device.

[0083] As used in any aspect of this specification, the terms "component," "system," "module," etc. may refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution.

[0084] As used in any aspect of the present specification, an "algorithm" refers to a self-consistent sequence of steps leading to a desired result, where the "steps" refer to the manipulation of physical quantities and / or logical states, although not necessarily in the form of electrical or magnetic signals that can be stored, moved, combined, compared, and otherwise manipulated. These signals are commonly referred to as bits, values, elements, symbols, characters, terms, numbers, or the like. These and similar terms may be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities and / or states.

[0085] Unless otherwise indicated, the terms "processing," "computing," "calculating," "determining," "presenting," "displaying," or similar words discussed herein refer to the actions or processes of the machine 1100 (e.g., a computer) that manipulate or transform data represented as physical (e.g., electronic, magnetic, or optical) quantities in one or more memories (e.g., volatile memory, non-volatile memory, or any suitable combination thereof), registers, or other mechanical components that receive, store, transmit, or display information. Additionally, as is common in patent documents, the terms "a" or "an" are used herein to include one or more instances unless otherwise indicated. Finally, as used herein, the conjunction "or" refers to a non-exclusive "or" unless otherwise indicated.

[0086] The present disclosure is illustrative and not limiting. Further modifications will be apparent to those skilled in the art in view of the present disclosure and are intended to fall within the scope of the appended claims.

Claims

1. A system for providing automated driving of a radio-controlled (RC) vehicle using a user's mobile device, the mobile device including at least one sensor and a communication interface, the system comprising: a chassis configured to be mounted on the RC vehicle, the chassis configured to carry a mobile device of the user, the chassis including a slot, the mobile device of the user being a smartphone; a circuit communicatively coupled to the RC vehicle and configured to transmit signals to operate the RC vehicle; The system, wherein the circuitry includes an interface for connecting to the communications interface of the user's mobile device and is configured to receive commands from the user's mobile device that are routed to the RC vehicle.

2. The system of claim 1 , wherein the circuitry is further configured to receive commands from a mobile device of the user that utilize the at least one sensor.

3. 3. The system of claim 1 or 2, further comprising a virtualization layer represented by software or firmware stored in memory configured to cause a processor to provide a platform for programming artificial intelligence (AI) for controlling the RC vehicle.

4. 4. The system of claim 3, wherein the virtualization layer includes a simulator abstraction module, an autonomous driving abstraction module, and a vehicle hardware abstraction module.

5. 5. The system of claim 4, wherein the virtualization layer is further configured to cause the processor to provide the platform for programming an AI via a software simulator connected to the simulator abstraction module, the software simulator operating on a user device separate from the user's mobile device.

6. The system of any one of claims 1 to 5, further comprising an interface to a virtual reality (VR) or augmented reality (AR) device wearable by the user such that the user can see a camera view of the user's mobile device while the mobile device is attached to the RC vehicle when the RC vehicle is moving.

7. The system of claim 6 , wherein the VR or AR interface is configured to use visual data streaming capabilities of the user's mobile device to provide live visual streaming to the VR or AR device.

8. The system of any one of claims 1 to 7, wherein the circuitry is further configured to communicate with a manual interface to the RC vehicle.

9. The system of claim 8 , wherein the circuitry is further configured to send commands to the RC vehicle based on inputs received from the manual interface.

10. The system of any one of claims 1 to 9, wherein the circuitry includes a safe mode component configured to override commands received from a mobile device of the user.