Methods and apparatus to facilitate remote-controlled maneuvers

Abstract

Methods and apparatus are disclosed to facilitate remote-controlled maneuvers. An example vehicle comprises: wheels, a transceiver, and a processor and memory. The processor is in communication with a remote device via the transceiver and is configured to: determine whether first and second buttons of the remote device are pressed based on signals from the remote device, if the first and second buttons are released, stop rotation of the wheels, and communicate a message regarding the released first and second buttons to the remote device.

Description

TECHNICAL FIELD

The present disclosure generally relates to automated vehicle features and, more specifically, remote-controlled vehicle maneuvers.

BACKGROUND

In recent years, vehicles have been equipped with automated vehicle maneuvering features such as parallel parking assistance, trailer-hitching assistance, braking assistance, etc. Automated vehicle maneuvering features often make vehicles more enjoyable to drive, alert drivers to potential obstructions, and/or assist drivers in making relatively precise maneuvers. Information from automated vehicle maneuvering features is often presented to a driver via an interface of a vehicle.

SUMMARY

The appended claims define this application. The present disclosure summarizes aspects of the embodiments and should not be used to limit the claims. Other implementations are contemplated in accordance with the techniques described herein, as will be apparent to one having ordinary skill in the art upon examination of the following drawings and detailed description, and these implementations are intended to be within the scope of this application.

An example vehicle is disclosed. The vehicle comprises: wheels, a transceiver, and a processor and memory. The processor is in communication with a remote device via the transceiver and is configured to: determine whether first and second buttons of the remote device are pressed based on signals from the remote device, if the first and second buttons are released, stop rotation of the wheels, and communicate a message regarding the released first and second buttons to the remote device.

An example method is disclosed. The method comprises: determining, with a processor, whether first and second buttons of a remote device are pressed based on signals from the remote device; stopping, with the processor, rotation of wheels of a vehicle if the first and second buttons are released; and communicating, with the processor, a message regarding the released first and second buttons to the remote device.

An example system is disclosed. The system comprises: a remote device and a vehicle. The remote device comprises a display and physical first and second buttons and is configured to display a graphical interface. The graphical interface has a virtual steering knob and a direction selector. The vehicle comprises wheels, a transceiver, and a processor and memory. The processor and memory are in communication with the remote device via the transceiver and are configured to: control the wheels based on inputs made to the remote device via the graphical interface; determine whether the first and second buttons are pressed based on signals from the remote device; if the first and second buttons are released, stop rotation of the wheels; and communicate a message regarding the released first and second buttons to the remote device.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention, reference may be made to embodiments shown in the following drawings. The components in the drawings are not necessarily to scale and related elements may be omitted, or in some instances proportions may have been exaggerated, so as to emphasize and clearly illustrate the novel features described herein. In addition, system components can be variously arranged, as known in the art. Further, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 is a side schematic view of a vehicle operating in accordance with the teachings of this disclosure in an environment.

FIG. 2 is a top schematic view of the vehicle of FIG. 1.

FIG. 3 is a block diagram of the electronic components of the vehicle of FIG. 1.

FIG. 4 is a more detailed block diagram of the interface generator of FIG. 3.

FIG. 5 illustrates an example remote vehicle maneuvering interface generated by the interface generator of FIG. 3.

FIG. 6 illustrates an example test mode interface generated by interface generator of FIG. 3.

FIG. 7 is a flowchart of a method to control the vehicle of FIG. 1 during a remote-controlled maneuver, which may be implemented by the electronic components of FIG. 3.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

While the invention may be embodied in various forms, there are shown in the drawings, and will hereinafter be described, some exemplary and non-limiting embodiments, with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated.

Automated vehicle maneuvering features include parallel parking assistance, trailer-hitching assistance, trailer reversing assistance, and braking assistance, among others. Parallel parking assistance detects and steers a vehicle into a parallel parking spot. Trailer-hitching assistance detects and steers a vehicle to a trailer hitch coupler. Trailer reversing assistance modulates driver steering input to reverse a hitch trailer along a desired path. Braking assistance automatically slows and/or stops a vehicle when a pedestrian or other obstruction is detected near a vehicle.

Traditionally, with trailer reversing assistance, a vehicle determines steering and counter-steering angles while traveling in reverse to push a hitched trailer along a curved path. The driver is instructed to input steering commands via a knob mounted in the vehicle instead of via the steering wheel. An algorithm determines how to angle the steered wheels for the vehicle to move the hitched trailer along the curved path input by the driver via the knob. However, this precludes the driver from monitoring the trailer's and the vehicle's approach toward curbs and/or other obstacles (e.g., pedestrians, animals, etc.) that may be blocked from view from inside the vehicle.

This disclosure provides methods and apparatus to remotely control vehicle maneuvers. By remotely controlling vehicle maneuvers, a driver may monitor a vehicle's surroundings from outside the vehicle while reversing a trailer. By monitoring a vehicle's surroundings, the vehicle may be stopped before the vehicle and/or the trailer contact an obstacle.

FIG. 1 is a side schematic view of a vehicle 110 operating in in an environment 100. FIG. 2 is a top schematic view of the vehicle 110.

As shown in FIGS. 1 and 2, the environment 100 includes a roadway 101, an obstacle 102 (shown as a curb), a pedestrian 103 (shown as a child) the vehicle 110, a remote device 170, a driver 180, and a trailer 160. The vehicle 110 and the trailer 160 are hitched together. An arrow 111 shown in FIG. 1 indicates that the vehicle 110 and trailer 160 are traveling in reverse. In the example of FIG. 1, the driver 180 is outside the vehicle 110 to monitor the vehicle's 110 progress. The driver 180 controls the vehicle's 110 movement along a path 190 via the remote device 170. The vehicle 110 steers itself for joined the trailer 160 and the vehicle 110 to follow the path 190 indicated by the driver 180.

The vehicle 110 may be a standard gasoline powered vehicle, a hybrid vehicle, an electric vehicle, a fuel cell vehicle, and/or any other mobility implement type of vehicle. The vehicle 110 includes parts related to mobility, such as a powertrain with an engine, a transmission, a suspension, a driveshaft, and/or wheels, etc. The vehicle 110 may be non-autonomous, semi-autonomous (e.g., some routine motive functions controlled by the vehicle 110), or autonomous (e.g., motive functions are controlled by the vehicle 110 without direct driver input). As shown in FIG. 1 the vehicle 110 includes wheels 112, sensors 120, a towing hitch 130, a transceiver 140, and an on board computing platform (OBCP) 150.

The trailer 160 includes is configured to receive and secure with the towing hitch 130. Thus, the trailer 160 may be swingably connected to the vehicle 110 via the towing hitch 130.

The vehicle 110 is in communication with the remote device 170 via the transceiver 140.

The sensors 120 may be arranged in and around the vehicle 110 in any suitable fashion. The sensors 120 may be mounted to measure properties around the exterior of the vehicle 110. Additionally, some sensors 120 may be mounted inside the cabin of the vehicle 110 or in the body of the vehicle 110 (such as, the engine compartment, the wheel wells, etc.) to measure properties in the interior of the vehicle 110. For example, such sensors 120 may include accelerometers, odometers, tachometers, pitch and yaw sensors, wheel speed sensors, microphones, tire pressure sensors, and biometric sensors, etc. In the illustrated example, the sensors 120 are object-detecting and range-finding sensors (e.g., a camera, lidar, radar, ultrasonic, etc.). In some examples, the sensors 120 are mounted at the front and rear of the vehicle 110. The sensors 120 detect objects (e.g., the trailer 160, the driver 180, etc.) about the vehicle 110. In other words, the sensors 120 generate obstruction information and range finding information for the vehicle 110.

The example transceiver 140 includes antenna(s), radio(s) and software to broadcast messages and to establish connections between the vehicle 110 and the remote device 170.

The OBCP 150 controls various subsystems of the vehicle 110. In some examples, the OBCP 150 controls power windows, power locks, an immobilizer system, and/or power mirrors, etc. In some examples, the OBCP 150 includes circuits to, for example, drive relays (e.g., to control wiper fluid, etc.), drive brushed direct current (DC) motors (e.g., to control power seats, power locks, power windows, wipers, etc.), drive stepper motors, and/or drive LEDs, etc. In some examples, the OBCP 150 processes information from the sensors 120 to execute and support remote-control vehicle maneuvering features and automated vehicle maneuvering features. Using steering commands from the remote device 170, the OBCP 150 determines steering and countersteering angles for the wheels 112 to move the trailer 160 along the path 190 indicated by the driver 180, stops the vehicle 110 if the driver 180 releases a keep-alive switch on the remote device 170, and/or determines whether to prompt the driver 180 to review the vehicle's 110 surroundings, and/or stops the vehicle 110 if a connection with the remote device is lost.

In the examples of FIGS. 1, 2, 5, and 6, the remote device 170 is a smartphone. The remote device 170 may also be, for example, a cellular telephone, a tablet, a key fob, etc. The remote device 170 includes a transceiver to send and receive messages from the transceiver 140. The remote device 170 also includes accelerometers and pitch and yaw sensors to determine an orientation of the remote device 170. The remote device 170 includes a touch sensitive display 172, and volume up and down buttons 174, 176. The driver 180 remotely controls the vehicle 110 via inputs to the display 172. The volume up and down buttons 174, 176 serve as keep-alive switches during remote control of the vehicle 110. In some examples, the display 172 also serves as a keep-alive switch during remote control of the vehicle 110. In other words, the remote device 170 generates orientation information, movement request information, and keep-alive information. The remote device 170 transmits the orientation information, the movement request information, and the keep-alive information to the vehicle 110 as wireless signals.

In operation during a remote-controlled vehicle maneuver, the remote device 170 serves as a user interface for the driver 180 to control movement of the vehicle 110 along a simplified path 190. More specifically, the OBCP 150 determines and controls steering of the vehicle 110 to move the trailer 160 and the vehicle 110 along the path 190. In other words, the driver 180 inputs the desired path 190 to the vehicle 110 via the remote device 170 and the vehicle 110 converts the desired path 190 into steering angles of the wheels 112 to steer and countersteer both the trailer 160 and the vehicle 110 along the path 190. In some examples, the driver 180 may control the speed of the vehicle 110 via the remove device 170.

FIG. 3 is a block diagram of the electronic components 300 of the vehicle 110. FIG. 4 is a more detailed block diagram of an interface generator 340 of FIG. 3. FIG. 5 illustrates an example remote vehicle maneuvering interface generated by the interface generator 340. FIG. 6 illustrates an example test mode interface generated by interface generator 340.

As shown in FIG. 3, the first vehicle data bus 302 communicatively couples the sensors 120, the OBCP 150, and other devices connected to the first vehicle data bus 302. In some examples, the first vehicle data bus 302 is implemented in accordance with the controller area network (CAN) bus protocol as defined by International Standards Organization (ISO) 11898-1. Alternatively, in some examples, the first vehicle data bus 302 may be a Media Oriented Systems Transport (MOST) bus, a CAN flexible data (CAN-FD) bus (ISO 11898-7), or an Ethernet bus. The second vehicle data bus 304 communicatively couples the OBCP 150 and the transceiver 140. The remote device 170 is in wireless communication with the transceiver 140. The second vehicle data bus 304 may be a MOST bus, a CAN bus, a CAN-FD bus, or an Ethernet bus. In some examples, the OBCP 150 communicatively isolates the first vehicle data bus 302 and the second vehicle data bus 304 (e.g., via firewalls, message brokers, etc.). Alternatively, in some examples, the first vehicle data bus 302 and the second vehicle data bus 304 are the same data bus.

The OBCP 150 includes a processor or controller 310 and memory 320. In the illustrated example, the OBCP 150 is structured to include a back-up assister 330 and the interface generator 340. Alternatively, in some examples, the back-up assister 330 and the interface generator 340 may be incorporated into another electronic control unit (ECU) with its own processor 310 and memory 320.

In operation, the back-up assister 330 determines steering and countersteering angles to push the trailer along the simplified path 190 in reverse. The back-up assister 330 communicates with the steering of the vehicle 110 to turn the wheels 112 of the vehicle 110 at appropriate points based on predetermined dimensions of the vehicle 110, the trailer 160, and the towing hitch 130 and on image data from the sensors 120. The back-up assister 330 communicatively connects the powertrain of the vehicle 110 with the remote device 170. Thus, the remote device 170 may remotely control the rotational speed and direction of the wheels of vehicle 110.

In operation, the interface generator 340 connects with the remote device 170, determines an orientation of the remote device 170, determines whether keep-alive switches are being held, determines whether a travel direction change is requested, determines whether a connection with the remote device 170 is adequately robust, determines whether to end back-up assistance, and converts commands from the remote device 170 for use by the back-up assister 330. The interface generator 340 makes these determinations based on signals from the remote device 170 and obstruction information and range finding information from the sensors 120.

The processor or controller 310 may be any suitable processing device or set of processing devices such as, but not limited to: a microprocessor, a microcontroller-based platform, a suitable integrated circuit, one or more field programmable gate arrays (FPGAs), and/or one or more application-specific integrated circuits (ASICs). The memory 320 may be volatile memory (e.g., RAM, which can include non-volatile RAM, magnetic RAM, ferroelectric RAM, and any other suitable forms); non-volatile memory (e.g., disk memory, FLASH memory, EPROMs, EEPROMs, non-volatile solid-state memory, etc.), unalterable memory (e.g., EPROMs), read-only memory, and/or high-capacity storage devices (e.g., hard drives, solid state drives, etc.). In some examples, the memory 320 includes multiple kinds of memory, particularly volatile memory and non-volatile memory.

The memory 320 is computer readable media on which one or more sets of instructions, such as the software for operating the methods of the present disclosure can be embedded. The instructions may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions may reside completely, or at least partially, within any one or more of the memory 320, the computer readable medium, and/or within the processor 310 during execution of the instructions. The memory 320 stores interface data 350 and connection data 360.

As shown in FIGS. 5 and 6, the interface data 350 includes graphical rendering data to display a graphical interface 500 via the display 172 of the remote device 170. In the example of FIG. 5, the graphical interface 500 is under a run mode and includes a virtual steering knob 510, a direction selector 520, an image requester button 530, a help requester button 540, a dynamic illustration 550, a speed selector 560, a message field 570, and an exit button 580. The virtual knob 510 is twisted by the driver touching and rotating the virtual knob 510 via the touch sensitive display 172. In some examples, the virtual knob 510 is configured to return to a neutral position when the driver 180 ceases touching the virtual know 510 (e.g., snap back to center, etc.). In some examples, the virtual knob 510 serves as a keep-alive switch in addition or as an alternative to the volume up/down buttons 174, 176. In such examples, the driver must touch and hold the virtual knob 510 to enable movement of the vehicle 110. The direction selector 520 shifts the vehicle 110 between forward movement and reverse movement. The image requester button 530 requests images from the front and/or rear camera sensors 120 to display on the display 172. The dynamic illustration 550 includes representations of the vehicle 110 and the trailer 160. In the dynamic illustration 550, the trailer pivots relative to the vehicle as the virtual knob 510 is rotated. The pivot angle between the trailer and the vehicle of the dynamic illustration 550 indicates in what direction the trailer 160 will be moved and/or is being moved by the vehicle 110. In other words, graphical interface 500 provides vehicle controls for the vehicle 110 and movement information for the trailer 160 to the driver 180.

As shown in FIG. 6, the interface data 350 includes testing data to test the display 172 and the volume up and down buttons 174, 176 as keep-alive switches. As shown in the example of FIG. 6, the graphical interface 500 is under a keep-alive switch test mode and includes an instructional prompt 610 and testing prompts 620. The instructional prompt 610 instructs the driver to press the volume up and down buttons 174, 176 according to the testing prompts 620. During the test, the driver 180 presses the volume up and down buttons 174, 176 as directed by the testing prompts 620. In the example of FIG. 6, the testing prompts 620 scroll along the display 172. As shown in FIG. 6, the test mode prompts the driver 180 to press the volume up and down buttons 174, 176 individually or simultaneously for varying lengths of time.

The connection data 360 may include thresholds and/or ranges for wireless signal flight times, strengths, arrival angles, and/or reception times. Wireless signals from the remote device 170 that are below the thresholds and/or outside of the ranges are indicative of a poor or otherwise improper connection with the vehicle 110. It should be understood and appreciated that the interface data 350 depicted in FIGS. 3, 5, and 6 is an example and that a graphical interface 500 in the memory 320 may include additional vehicle controls, dynamic illustrations, instructional prompts 610, testing prompts 620, etc. It should also be understood that the interface data 350 and the connection data 360 may be updated. Updates to the interface data 350 and/or the connection data 360 may be performed via the transceiver 140, an infotainment head unit (IHU), and/or an on board diagnostics (OBD) port of the vehicle 110.

The terms “non-transitory computer-readable medium” and “tangible computer-readable medium” should be understood to include a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The terms “non-transitory computer-readable medium” and “tangible computer-readable medium” also include any tangible medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a system to perform any one or more of the methods or operations disclosed herein. As used herein, the term “tangible computer readable medium” is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals.

As shown in FIG. 4, the interface generator 340 includes a data receiver 410, an input detector 420, an orientation determiner 430, a command convertor 440, an image retriever 450, and a feedback generator 460.

In operation, the data receiver 410 receives obstruction information and range finding information sent by the sensors 120. More specifically, the data receiver 410 receives images, reflections, and echoes of obstructions behind the vehicle 110 captured by the sensors 120. The data receiver 410 also receives orientation information, movement request information, and keep-alive information from the remote device 170. Additionally, the data receiver 410 receives strengths, arrival times, and/or arrival angles of the wireless signals from the remote device 170. The data receiver 410 establishes a wireless connection between the vehicle 110 and the remote device 170.

In operation, the input detector 420 detects and sorts movement requests, orientation change signals, image requests, quit requests, and keep-alive signals from the remote device 170. More specifically, the input detector 420 detects whether the volume up and/or down buttons 174, 176 and the virtual knob 510 are being held by the driver 180. In some examples, both the volume up and down buttons 174, 176 must be pressed to permit (e.g., keep alive) remote maneuvering of the vehicle 110. In some examples, both the volume up and down buttons 174, 176 and the virtual knob 510 must be pressed to permit (e.g., keep alive) remote maneuvering of the vehicle 110. In some examples, at least two of the virtual knob 510, the volume up button 174, and the volume down button 176 must be pressed to permit (e.g., keep alive) remote maneuvering of the vehicle 110. The input detector 420 sends the orientation change signals to the orientation determiner 430. The input detector 420 sends the movement requests, quit requests, the keep-alive determination to the command convertor 440. The input detector 420 sends the movement requests and the image requests to the image retriever 450.

Additionally, in operation, the input detector 420 determines whether the connection between the remote device 170 and the vehicle 110 is robust enough to remotely control the vehicle 110. Methods by which the input detector 420 determines connection strength include, for example, time-of-flight analysis, signal strength analysis, angle of arrival analysis, dead reckoning, etc. For example, the input detector 420 may compare signal flight times, strengths, arrival angles, and/or reception times to the connection data 360 stored in the memory 320.

In operation, the orientation determiner 430 determines whether to rotate the graphical interface 500 in the display 172 based on the orientation change signals. More specifically, the orientation determiner 430 analyzes signals from the accelerometers of the remote device 170 to determine whether the driver 180 has moved the remote device 170 from one hand to another, rotated the remote device 170, is holding the remote device 170 at his or her side, etc. In other words, the orientation determiner 430 makes an orientation determination of whether to flip the graphical interface 500 such that the graphical interface 500 is correct side up as viewed by the driver 180. In some examples, the graphical interface 500 is correct side up when the message field 570 is legible and/or the virtual knob 510 is next to the volume up and down buttons 174, 176. If the graphical interface 500 is incorrectly oriented in the display 172, the orientation determiner 430 transmits reorientation commands to the remote device 170.

In operation, the command convertor 440 converts movement requests from the remote device 170 into signals usable by the back-up assister 330. Movement requests include signals to control rotation of the wheels 112, steer the wheels 112, stop the vehicle 110, and/or shift the vehicle 110. More specifically, the command convertor 440 transforms the movement requests from information protocols used by the remote device 170 into information protocols used by a physical steering knob, shifter, and brake and accelerator pedals for delivery to the back-up assister 330. Additionally, the command convertor 440 sends stop commands to the back-up assister 330 based on quit requests, the keep-alive determination, and/or the connection determination from the input detector 420.

In operation, the image retriever 450 retrieves images from the front and/or rear camera sensors 120 based on image requests made via the image requester button 530 and/or shift requests made via the direction selector 520. More specifically, after receiving an image request, the image retriever 450 engages the front and/or rear camera sensors 120 to direct images of the environment 100 about the vehicle to the display 172. A driver 180 may request these images to look for obstructions while remotely maneuvering the vehicle 110. In some examples, the image retriever 450 may transmit images of the environment 100 to the display 172 whenever a shift request is made by the driver 180. In other words, the image retriever 450 prompts the driver 180 to check for obstructions that may not be visible from the driver's 180 vantage point (e.g., the child 103 shown in FIG. 1) before changing the travel direction of the vehicle 110.

In operation the feedback generator 460 generates feedback based on the keep-alive determinations and the connection determinations. More specifically, the feedback generator 460 generates audio messages and/or visual messages warning a driver 180 that remote vehicle maneuvering is unavailable because the volume up and down buttons 174, 176 have been released and/or because the connection between the vehicle 110 and the remote device 170 is poor or otherwise improper. Further, the feedback generator 460 transmits the messages for display via the display 172. In some examples, the messages are shown in the message field 570. FIG. 7 is a flowchart of a method 700 to remotely maneuver the vehicle 110, which may be implemented by the electronic components 300 of FIG. 3. The flowchart of FIG. 7 is representative of machine readable instructions stored in memory (such as the memory 320 of FIG. 3) that comprise one or more programs that, when executed by a processor (such as the processor 310 of FIG. 3), cause the vehicle 110 to implement the example back-up assister 330 and interface generator 340 of FIGS. 3 and 4. Further, although the example program(s) is/are described with reference to the flowchart illustrated in FIG. 7, many other methods of implementing the example interface generator 340 may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.

Initially, at block 702, the data receiver 410 establishes a connection between the vehicle 110 and the remote device 170. As discussed above, the data receiver 410 receives wireless signals from the remote device 170.

At block 704, the orientation determiner 430 orients the graphical interface 500 in the display 172. More specifically, the orientation determiner 430 determines whether to rotate the graphical interface 500 in the display 172 based on orientation information from accelerometers of the remote device 170, as discussed above.

At block 706, the input detector 420 determines whether the wireless signals from the remote device 170 include keep-alive inputs. More specifically, the input detector 420 analyzes the wireless signals from the remote device 170 to determine whether the driver 180 is maintaining pressure on the volume up and/or down buttons 174, 176, as discussed above. It should be understood and appreciated that the volume up and down buttons 174, 176 act as keep-alive switches. In other words, to keep the vehicle 110 under remote maneuvering, the driver 180 must press one or more of the volume up and down buttons 174, 176.

If, at block 706, the input detector 420 determines that the wireless signals from the remote device 170 include keep-alive inputs, the method 700 proceeds to block 708.

If, at block 706, the input detector 420 determines that the wireless signals from the remote device 170 do not include keep-alive inputs, the method 700 proceeds to block 718.

At block 708, the command convertor 440 converts movement requests from the remote device 170 into commands for the back-up assister 330. More specifically, the command convertor 440 transforms the movement requests from the remote device 170 information protocol to the back-up assister information protocol, as discussed above. The method 700 then proceeds to block 710.

At block 710, the back-up assister 330 maneuvers the vehicle 110. More specifically, the back-up assister 330 steers and rotates the wheels 112 according to the movement requests from the remote device 170, as discussed above. The method 700 then proceeds to block 712.

At block 712, the input detector 420 determines whether the connection between the remote device 170 and the vehicle 110 is robust. More specifically, the input detector 420 accesses connection data 360 stored in the memory 320 and compares signal flight times, strengths, arrival angles, and/or reception times to the connection data 360, as discussed above.

If, at block 712, the input detector 420 determines that the connection between the remote device 170 and the vehicle 110 is robust, the method 700 proceeds to block 732.

If, at block 712, the input detector 420 determines that the connection between the remote device 170 and the vehicle 110 is not robust, the method 700 proceeds to block 714.

At block 714, the command convertor 440 instructs the back-up assister 330 to stop the vehicle 110. More specifically, the command convertor 440 commands the back-up assister 330 to stop rotating the wheels 112 based on the poor connection determination, as discussed above. The method 700 proceeds to block 716.

At block 716, the feedback generator 460 generates feedback regarding the stopped vehicle 110. More specifically, the feedback generator 460 transmits a message to the remote device 170 informing the driver 180 of the poor connection, as discussed above. The method 700 then returns to block 702.

At block 732, the orientation determiner 430 determines whether the orientation of the graphical interface 500 is correct side up based on accelerometer information from the remote device, as discussed above.

If, at block 732, the orientation determiner 430 determines that the orientation of the graphical interface 500 is correct side up, the method 700 returns to block 706.

If, at block 732, the orientation determiner 430 determines that the orientation of the graphical interface 500 is not correct side up, the method 700 returns to block 704.

Referring back to block 718, the command convertor 440 instructs the back-up assister 330 to stop the vehicle 110. More specifically, the command convertor 440 commands the back-up assister 330 to stop rotating the wheels 112 based on the driver 180 releasing one or more of the keep-alive volume up and down buttons 174, 176, as discussed above. The method proceeds to block 720.

At block 720, the input detector 420 determines whether the driver 180 sent a quit request via the exit button 580 of the graphical interface 500, as discussed above.

If, at block 720, the input detector 420 determines that the driver 180 sent a quit request, the method proceeds to block 722.

If, at block 720, the input detector 420 determines that the driver 180 did not send a quit request, the method proceeds to block 724.

At block 722, the input detector 420 ends the connection with the remote device 170 to close the graphical interface 500. The method then returns to block 702.

At block 724, the input detector 420 determines whether the driver 180 sent a shift request via the direction selector 520 of the graphical interface 500, as discussed above.

If, at block 724, the input detector 420 determines that the driver 180 sent a shift request, the method proceeds to block 726.

If, at block 724, the input detector 420 determines that the driver 180 did not send a shift request, the method proceeds to block 730.

At block 726, the image retriever 450 prompts the driver 180 to review images of the surroundings of the vehicle 110. More specifically, the image retriever engages the camera sensors 120 to transmit images to the remote device 170, as discussed above. The method 700 then proceeds to block 728.

At block 728, the command convertor 440 converts the shift request into a command usable by the back-up assister 330 and sends the command to the back-up assister 330, as discussed above. The method 700 then returns to block 706.

At block 730, the feedback generator 460 generates feedback regarding the stopped vehicle 110. More specifically, the feedback generator 460 transmits a message to the remote device 170 informing the driver 180 of the released keep-alive volume up and down buttons 174, 176, as discussed above. The method 700 then returns to block 706.

In this application, the use of the disjunctive is intended to include the conjunctive. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to “the” object or “a” and “an” object is intended to denote also one of a possible plurality of such objects. Further, the conjunction “or” may be used to convey features that are simultaneously present instead of mutually exclusive alternatives. In other words, the conjunction “or” should be understood to include “and/or”. The terms “includes,” “including,” and “include” are inclusive and have the same scope as “comprises,” “comprising,” and “comprise” respectively.

From the foregoing, it should be appreciated that the above disclosed apparatus and methods may aid drivers by allowing drivers to remotely control vehicle maneuvers while preventing accidental and/or unintentional vehicle movement. By allowing drivers to remotely control their vehicles, drivers may more closely observe the vehicle maneuver. In instances where the vehicle maneuver is assisted guidance of a hitched trailer, the driver may observe whether the trailer is approaching obstacles (e.g., pedestrians, curbs, posts) that would otherwise be difficult to see from inside the vehicle. Thus, remote control of the assisted trailer guidance may prevent contact between the vehicle and/or the trailer and obstacles. It should also be appreciated that the disclosed apparatus and methods provide a specific solution—remote trailer guidance assistance—to a specific problem—potential contact of vehicles and/or hitched trailers with obstacles during maneuvers. Further, the disclosed apparatus and methods provide an improvement to computer-related technology by increasing functionality of a processor to receive a plurality of types of inputs from a remote device, detect and sort the input types, orient a graphical interface displayed via the remote device based on the inputs, convert the input types for use in hitched trailer guidance, retrieve images from sensors, and generate feedback for display via the remote device based on the inputs.

As used here, the terms “module” and “unit” refer to hardware with circuitry to provide communication, control and/or monitoring capabilities, often in conjunction with sensors. “Modules” and “units” may also include firmware that executes on the circuitry.

The above-described embodiments, and particularly any “preferred” embodiments, are possible examples of implementations and merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) without substantially departing from the spirit and principles of the techniques described herein. All modifications are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims

1. A vehicle comprising:

wheels;

a transceiver; and

a processor and memory in communication with a remote device via the transceiver and configured to:

determine that a first button and a second button of the remote device are pressed based on signals from the remote device;

determine that a graphical interface of the remote device is pressed based on signals from the remote device; and

cause, based on a determination that the first button, second button, and graphical interface of the remote device are all being pressed at the same time, a rotation of the wheels.

2. The vehicle of claim 1, wherein the processor is configured to rotate the wheels when the first and second buttons are pressed by a driver.

3. The vehicle of claim 1, wherein the processor is configured to:

determine whether a connection strength between the transceiver and the remote device is below a threshold stored in the memory; and

if the connection strength is below the threshold, the processor is configured to stop rotation of the wheels.

4. The vehicle of claim 1, further comprising a camera in communication with the processor, wherein the processor is configured to transmit an image from the camera to the remote device based on a shift request from the remote device.

5. The vehicle of claim 1, wherein the processor is configured to:

determine whether a graphical interface for remote control of the vehicle displayed via the remote device is oriented correct side up; and

if the graphical interface is incorrectly oriented, transmit a reorientation command to the remote device.

6. The vehicle of claim 5, wherein the graphical interface includes a virtual knob to control steering of the wheels.

7. The vehicle of claim 1, wherein the first and second buttons are physical volume up and volume down buttons, respectively.

8. A method comprising:

determining, with a processor, that a first button and a second button of a remote device are pressed based on signals from the remote device;

determining, with the processor, that graphical interface of the remote device is pressed based on signals from the remote device; and

causing, based on a determination that the first button, second button, and graphical interface of the remote device are all being pressed at the same time, a rotation of wheels of vehicle.

9. The method of claim 8, further comprising rotating, with the processor, the wheels when the first and second buttons are pressed.

10. The method of claim 8, further comprising;

determining, with the processor, whether a connection strength between a transceiver of the vehicle and the remote device is below a threshold; and

stopping, with the processor, rotation of the wheels if the connection strength is below the threshold.

11. The method of claim 8, further comprising transmitting, with the processor, an image from a camera of the vehicle to the remote device based on a shift request from the remote device.

12. The method of claim 8, further comprising:

determining, with the processor, whether a graphical interface for remote control of the vehicle displayed via the remote device is oriented correct side up based on orientation information from the remote device; and

transmitting, with the processor, a reorientation command to the remote device if the graphical interface is incorrectly oriented.

13. The method of claim 12, wherein the graphical interface includes a virtual knob to control steering of the wheels.

14. The method of claim 8, wherein the first and second buttons are physical volume up and volume down buttons, respectively.

15. A system comprising:

a remote device comprising a display and physical first and second buttons and configured to display a graphical interface having a virtual steering knob and a direction selector; and

a vehicle comprising:

wheels;

a transceiver; and

a processor and memory in communication with the remote device via the transceiver and configured to:

control the wheels based on inputs made to the remote device via the graphical interface;

determine that the first button and second button are pressed based on signals from the remote device;

determine that the graphical interface of the remote device is pressed based on signals from the remote device; and

cause, based on a determination that the first button, second button, and graphical interface of the remote device are all being pressed at the same time, a rotation of the wheels.

16. The system of claim 15, wherein the processor is configured to rotate the wheels when the physical first and second buttons are pressed by a driver.

17. The system of claim 15, wherein the processor is configured to:

determine whether the graphical interface is oriented correct side up in the display; and

if the graphical interface is incorrectly oriented, transmit a reorientation command to the remote device.

18. The system of claim 17, wherein the vehicle further comprises a camera in communication with the processor and the processor is configured to transmit an image from the camera to the remote device based on a shift request made via the direction selector.