Hi,
I'm in the process of writing a mode feature and need to hook a button up.
Since I want my firmware to be compatible with all app (PPM, ADC...), mapping change across the mode selected.
I also use ADC3 for external temperature monitoring (and cutoff if too high).
Based on FW3.40, I obtain this mapping table :
| PPM | ADC1 | ADC2 | Rx | Tx | ADC3 | ||
| PPM | Acc/Brake | - | - | - | - | - | |
| PPM+UART | Acc/Brake | - | - | UART Rx | UART Tx | - | |
| ADC | _NONE | - | - | - | - | - | - |
| _CURRENT | - | Acc | - | Reverse | Cruise Control | - | |
| _CURRENT_REV_CENTER | - | Acc/Brake | - | Reverse | Cruise Control | - | |
| _CURRENT_REV_BUTTON | - | Acc | - | Reverse | Cruise Control | - | |
| _CURRENT_REV_BUTTON_BRAKE_ADC | - | Acc | Brake | Reverse | Cruise Control | - | |
| _CURRENT_NOREV_BRAKE_CENTER | - | Acc/Brake | - | Reverse | Cruise Control | - | |
| _CURRENT_NOREV_BRAKE_BUTTON | - | Acc | - | Reverse | Cruise Control | - | |
| _CURRENT_NOREV_BRAKE_ADC | - | Acc | Brake | Reverse | Cruise Control | - | |
| _DUTY | - | Acc | - | Reverse | Cruise Control | - | |
| _DUTY_REV_CENTER | - | Acc/Brake | - | Reverse | Cruise Control | - | |
| _DUTY_REV_BUTTON | - | Acc | - | Reverse | Cruise Control | - | |
| _PID | - | Acc | - | Reverse | Cruise Control | - | |
| _PID_REV_CENTER | - | Acc/Brake | - | Reverse | Cruise Control | - | |
| _PID_REV_BUTTON | - | Acc | - | Reverse | Cruise Control | - | |
| ADC + UART | _NONE | - | - | - | UART Rx | UART Tx | - |
| _CURRENT | Cruise control | Acc | - | UART Rx | UART Tx | - | |
| _CURRENT_REV_CENTER | Cruise control | Acc/Brake | - | UART Rx | UART Tx | - | |
| _CURRENT_REV_BUTTON | Reverse | Acc | - | UART Rx | UART Tx | - | |
| _CURRENT_REV_BUTTON_BRAKE_ADC | Cruise control | Acc | Brake | UART Rx | UART Tx | - | |
| _CURRENT_NOREV_BRAKE_CENTER | Cruise control | Acc/Brake | - | UART Rx | UART Tx | - | |
| _CURRENT_NOREV_BRAKE_BUTTON | Reverse | Acc | - | UART Rx | UART Tx | - | |
| _CURRENT_NOREV_BRAKE_ADC | Cruise control | Acc | Brake | UART Rx | UART Tx | - | |
| _DUTY | Cruise control | Acc | - | UART Rx | UART Tx | - | |
| _DUTY_REV_CENTER | Cruise control | Acc/Brake | - | UART Rx | UART Tx | - | |
| _DUTY_REV_BUTTON | Reverse | Acc | - | UART Rx | UART Tx | - | |
| _PID | Cruise control | Acc | - | UART Rx | UART Tx | - | |
| _PID_REV_CENTER | Cruise control | Acc/Brake | - | UART Rx | UART Tx | - | |
| _PID_REV_BUTTON | Cruise control | Acc | - | UART Rx | UART Tx | - | |
| NUNCHUK | - | - | - | - | - | - | |
| NRF | - | - | - | - | - | - | |
(BTW, this is really awesome to copy/paste Excel spreadsheet directly ! )
Here is the feature I would love to see :
In VESC Tool, it would be great to have a Mapping page that allow to map inputs such as cruise control, reverse, accel, brake, UART, and so on.
VESC Tool wise, it would be more complicated as it will require to check the consistency of user choice (for instance, disabing Rx/Tx mapping if UART activated).
This will help A LOT of people using ADC adding more flexibility in wiring and features configuration.
Thank you in advance,
Best Regards,
Clément
Greetings! Is this table still correct? Some of it does not make sense:
_CURRENT_REV_BUTTON_BRAKE_ADC Cruise control Acc Brake
_CURRENT_NOREV_BRAKE_ADC Cruise control Acc Brake
It seems with UART enabled (I want to use bluetooth) there is no reverse option with a second throttle, only cruise control. Is it a typo on poster's part, or a bug?
If it is just a typo, Is it safe to short 3.3 pin to ADC (or ADC2 for that matter) with a button to emulate cruise, while using _CURRENT_REV_BUTTON_BRAKE_ADC? I need reverse, cruise AND bluetooth.
If you ever do get a mapping thing working, it would be interesting to harness the additional ADCs of a networked controller too.