Automotive brake control

1 . A method for automotive braking control, the method comprising:

monitoring, via embedded software, the status of predetermined vehicle conditions of a vehicle;

in response to detecting, via the embedded software, the activation of one or more of the predetermined vehicle conditions, wherein activation of one or more of the predetermined vehicle conditions comprises one or more of: the speed of a vehicle falling beneath a threshold speed, no depression of the brake pedal, the steering wheel being turned within a threshold distance from a left lock or right lock position, and the vehicle entering four-wheel drive:

monitoring the vehicle, via embedded software, to detect a plurality of possible in-vehicle selection sequences, wherein the plurality of possible in-vehicle selection sequences each comprise one or more button presses preconfigured by the user via a personal computing application to cause a plurality of possible brake control schemes, and wherein each of the plurality of possible brake control schemes are preconfigured by the user via the personal computing application to comprise a sequence, duration, and brake actuation force level by which to actuate one or more particular brakes of the vehicle;

in response to detecting, via the embedded software, one of the plurality of possible in-vehicle selection sequences executed by a user:

based on the detected one of the plurality of possible in-vehicle selection sequences:

sending, via the embedded software, a brake actuation command to an anti-lock brake module (ABM) of the vehicle; and

based on the brake actuation command:

 actuating, via the ABM, a brake control scheme to actuate the one or more particular brakes of the vehicle in accordance with the sequence, duration, and brake actuation force level preconfigured for the detected one of the plurality of possible in-vehicle selection sequences.

2 . The method of claim 1 , further comprising: in response to detecting, via the embedded software, a second one of the plurality of possible in-vehicle selection sequences executed by the user:

in response to determining that the brake control scheme is currently actuated:

sending, via the embedded software, a brake disablement command to the ABM of the vehicle; and

based on the brake disablement command:

disabling, via the ABM, the brake control scheme.

3 . The method of claim 1 , further comprising:

in response to detecting, via the embedded software, that none of the predetermined vehicle conditions are activated:

in response to determining that the brake control scheme is currently actuated:

sending, via the embedded software, a brake disablement command to the ABM of the vehicle; and

based on the brake disablement command:

disabling, via the ABM, the brake control scheme.

4 . The method of claim 1 , wherein the one or more button presses are of buttons located on the dashboard of the vehicle, the steering wheel of the vehicle and key fobs associated with the vehicle.

5 . The method of claim 1 , wherein preconfiguring the personal computing application comprises:

receiving, via a user interface screen, a user selection of whether or not to enable brake control;

receiving, via the user interface screen, a user selection of which brake control scheme of multiple brake control schemes correspond to certain in-vehicle button presses;

receiving, via the user interface screen, a user selection of which vehicular brakes to actuate and how much to actuate the vehicular brakes in response to certain in-vehicle button presses;

receiving, via the user interface screen, a user selection of which dash indicator is employed to indicate that brake control is enabled;

receiving, via the user interface screen, a user selection to test the control over actuation of one or more vehicular brakes;

storing, in the memory, the user selection of whether or not to enable brake control;

storing, in the memory, the user selection of which vehicular brakes to actuate and how much to actuate the vehicular brakes in response to certain in-vehicle button presses;

storing, in the memory, the user selection of which dash indicator is employed to indicate that brake control is enabled;

storing, in the memory, the user selection of which brake control scheme of multiple brake control schemes correspond to certain in-vehicle button presses;

testing the control over actuation of one or more vehicular brakes; and

upon receiving, from a server, updates to the system firmware, updating the system firmware.

6 . The method of claim 1 , wherein the embedded software detects the plurality of possible in-vehicle selection sequences by broadcasting information relating to the plurality of possible in-vehicle selection sequences on a communication bus of an automotive vehicle, wherein the communication bus is a controller area network (CAN) bus.

7 . The method of claim 1 , wherein the embedded software detects the plurality of possible in-vehicle selection sequences by polling one or more of a steering column module (SCM) and a wireless control module (WCM) of the vehicle by transmitting an I/O read request and awaiting a response.

8 . The method of claim 7 , wherein polling one or more of the SCM and the WCM of the vehicle by transmitting an I/O read request and awaiting a response further comprises:

transmitting, via the embedded software, to one or more of the SCM and the WCM, a command to start a diagnostic session;

transmitting, via the embedded software, to one or more of the SCM and the WCM, a command to read the each in-vehicle selection sequence, along with the correct values to read the each in-vehicle selection sequence; and

transmitting, via the embedded software, to one or more of the SCM and the WCM, a periodic tester command to ensure the command to read the each in-vehicle selection sequence is running.

9 . The method of claim 1 , wherein sending, via the embedded software, the brake actuation command to the ABM of the vehicle, further comprises:

transmitting, via the embedded software, to the ABM, a command to start a diagnostic session;

transmitting, via the embedded software, to the ABM, one or more input/output control commands, wherein the one or more input/output control commands each specify one or more particular vehicle brakes and the actuation level of the each one or more particular vehicle brakes;

transmitting, via the embedded software, to the ABM, a periodic tester command to ensure the one or more input/output control commands are running; and

transmitting, via the embedded software, a command to end the diagnostic session.

10 . An onboard diagnostic plug-in dongle device, wherein the device aids in tight radius off-road turns by locking or dragging the inside rear tire of the direction turning, the device comprising:

a shell;

a plug;

a printed circuit (PC) board comprising:

a microcontroller;

a controller area network (CAN) controller;

a physical layer device (PHY);

a universal serial bus (USB) bridge and connector;

an indicator LED; and

a memory storing embedded program instructions that, when executed by microcontroller, cause the microcontroller to perform operations comprising:

monitoring, via embedded software, the status of predetermined vehicle conditions of a vehicle;

in response to detecting, via the embedded software, the activation of one or more of the predetermined vehicle conditions:

monitoring the vehicle, via embedded software, to detect in-vehicle selection sequences;

in response to detecting, via the embedded software, an in-vehicle selection sequence by a user:

 based on the in-vehicle selection sequence:

 sending, via the embedded software, a brake actuation command to an anti-lock brake module (ABM) of the vehicle; and

 based on the brake actuation command:

 actuating, via the ABM, a brake control scheme, wherein the brake control scheme is a particular sequence, duration, and brake actuation force level by which to actuate one or more particular brakes of the vehicle.

11 . The device of claim 10 , wherein the microcontroller executes the embedded software via the CAN controller and the PHY.

12 . The device of claim 10 , wherein the plug is an OBD2 plug, and wherein the plug is installed into the OBD2 diagnostic connector of the vehicle.

13 . The device of claim 10 , wherein the plug is installed by unplugging the vehicle security gateway (SGW) module of the vehicle and plugging the device in its place, directly or via an extension cable.

14 . The device of claim 10 , wherein the onboard diagnostic plug-in dongle device further comprises a bypass module that bypasses the security gateway (SGW) of the vehicle.

15 . The device of claim 10 , wherein the microcontroller communicates with a personal computing application via the USB bridge and connector.

16 . A non-transitory computer readable medium comprising instructions that, when executed by the microcontroller of an onboard diagnostic plug-in dongle, cause the microcontroller to perform operations comprising:

monitoring, via embedded software, the status of predetermined vehicle conditions of a vehicle;

in response to detecting, via the embedded software, the activation of one or more of the predetermined vehicle conditions, wherein activation of one or more of the predetermined vehicle conditions comprises one or more of: the speed of a vehicle falling beneath a threshold speed, no depression of the brake pedal, the steering wheel being turned within a threshold distance from a left lock or right lock position, and the vehicle entering four-wheel drive:

monitoring the vehicle, via embedded software, to detect a plurality of possible in-vehicle selection sequences, wherein the plurality of possible in-vehicle selection sequences each comprise one or more button presses preconfigured by the user via a personal computing application to cause a plurality of possible brake control schemes, and wherein each of the plurality of possible brake control schemes are preconfigured by the user via the personal computing application to comprise a sequence, duration, and brake actuation force level by which to actuate one or more particular brakes of the vehicle;

in response to detecting, via the embedded software, one of the plurality of possible in-vehicle selection sequence by a user:

based on the detected one of the plurality of possible in-vehicle selection sequences:

sending, via the embedded software, a brake actuation command to an anti-lock brake module (ABM) of the vehicle; and

based on the brake actuation command:

 actuating, via the ABM, a brake control scheme, to actuate the one or more particular brakes of the vehicle in accordance with the sequence, duration, and brake actuation force level preconfigured for the detected one of the plurality of possible in-vehicle selection sequences.