Hello,
do you think it would be possible to make a CAN <> BLE gateway ?

Hi there! Love the project :)

Is it possible to pull the Forward, Backward, Brake, and Buzzer statuses through CAN instead of GPIO? This would reduce the amount of wire connections needed if one uses the CAN bus version.

The footpad state should be visualized in the lightbar

I'm wondering if this was right:

when i use it, i wait some long time, (discus with my frien).
front and back ligth go off (idle time).
i put my foot on, and nothing change, the back and front alway off, and the litghbar dont go to blue. the board steel ok i can ride.

i need a restart (switch off /on) to recover the litgh.

The current firmware does only support passive piezo buzzer. Add support for active buzzers also.

I tried to launch that project on ESP32-C2, but board won't connect to VESC via UART

Any way to debug that?

hello,
could you publish the PCB schematics on the github ?
Regards,
F.

Some users reported flickering idle light. This happens when the light pattern is repeated, e.g. rainbow light.
The root cause is the resetting of all pixels, which was introduced with the battery indicator idle light pattern in 2.2.1.

I'd like to use the rESCue s3 with the COB LED's. What PIN's of the s3 are connected to the optional light connectors 1 & 2 Dout?
Could we use them for the Mosfet control. If so I request to implement it as a standard.

Hi. So i saw, that it gives brakelight Support. Is it possible to make it usable in Germany with a static breaklight (Like Cars) instead of flashing light?

UART currently isn't working on the rESCue s3.

The COB firmware image stays in a boot loop-

Add support for changing the odd/even pattern from the app rather recompiling the firmware

Great coneption! Sadly, seemingly my incompetence does not permit me to get the BLE bridge working.
I flash the esp successfully, I am connected to the uart on the VESC (I had an nrf working properly there), I am soldered to GPIO 16 &17, I have APP set to UARD on my single ubox. I can successfully connect to the flashed ESP, but get "make sure port belongs to vesc".
What could I be doing wrong? I have just to be sure swapped the tx-rx cables a couple of times to no success.

I am currently using 16 Molicel P42A cells in my onewheel build (4200mAh per cell) and in the app, the max capacity slider is 4000mAh. Would it be possible to make the max of the slider be 5000mAh instead of 4000mAh?

When I setup rescue app I specified 0 pins (cause I have no leds at all, I want to use it as BLEproxy rn)

Now I have bootloop with this

09:51:29.384 > ets Jun  8 2016 00:22:57
09:51:29.387 >
09:51:29.387 > rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
09:51:29.393 > configsip: 0, SPIWP:0xee
09:51:29.393 > clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
09:51:29.401 > mode:DIO, clock div:2
09:51:29.401 > load:0x3fff0030,len:1184
09:51:29.404 > load:0x40078000,len:13232
09:51:29.407 > load:0x40080400,len:3028
09:51:29.411 > entry 0x400805e4
09:51:30.672 > Guru Meditation Error: Core  1 panic'ed (IntegerDivideByZero). Exception was unhandled.
09:51:30.678 >
09:51:30.678 > Core  1 register dump:
09:51:30.680 > PC      : 0x400d6b97  PS      : 0x00060a30  A0      : 0x800d736f  A1      : 0x3ffcb4c0  
09:51:30.689 > A2      : 0x3ffbbfc8  A3      : 0x3ffc38c4  A4      : 0x000000ff  A5      : 0x00000000
09:51:30.697 > A6      : 0x3f400547  A7      : 0x3ffc3860  A8      : 0x00630000  A9      : 0x00000064  
09:51:30.706 > A10     : 0x00000000  A11     : 0x00000000  A12     : 0x000003e8  A13     : 0x00000043
09:51:30.711 > A14     : 0x7ff00000  A15     : 0x7ff0cccc  SAR     : 0x00000020  EXCCAUSE: 0x00000006  
09:51:30.719 > EXCVADDR: 0x00000000  LBEG    : 0x40085c39  LEND    : 0x40085c41  LCOUNT  : 0x00000027
09:51:30.728 >
09:51:30.728 >
09:51:30.728 > Backtrace: 0x400d6b94:0x3ffcb4c0 0x400d736c:0x3ffcb4e0 0x400ea2e6:0x3ffcb510
09:51:30.736 >
09:51:30.736 >
09:51:30.736 >
09:51:30.736 >
09:51:30.736 > ELF file SHA256: 0a949e50ce96eca6
09:51:30.738 >
09:51:30.889 > Rebooting...

repeating at serial

this is stacktrace decoding

The buffer size of the JSON Object is too small.

The current implementation uses active-high logic which needs a NPN transistor.
Enhance the firmware to also support active-low logic for PNP transistors

I am trying to connect Vesc tool app V6.05, as soon as i connect ble, ESP32 gets reset and if i connect vesc tool V1.25 app everything works fine. can you help me with this issue. here is the error when i connect with new vesc tool

rst:0xc (sw_cpu_reset),boot:0x13 (spi_fast_flash_boot) configsip: 0, spiwp:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:dio, clock div:1 load:0x3fff0018,len:4 load:0x3fff001c,len:1044 load:0x40078000,len:10124 load:0x40080400,len:5856 entry 0x400806a8

Add an option to rESCue to turn on / off the lights while riding

FreeSK8 is scanning for CAN-IDs after establishing a BLE connection. This doesn't work with rESCue and makes FreeSK8 staying in a loop

Add support for this great piece of hardware

Hello,

I am trying to understand how VESC Tools use the 2 BLE characteristics for Serial...

21:35:47.338 > BLH - BLE connecting
21:35:47.828 > BLH - onAuthenticationComplete desc : success
21:35:47.830 > Client ID: 0, Address: cc:21:19:9e:7f:c8, Subvalue 1, Characteristics beb5483e-36e1-4688-b7f5-ea07361b26a0
21:35:47.832 > Client ID: 0, Address: cc:21:19:9e:7f:c8, Subvalue 1, Characteristics beb5483e-36e1-4688-b7f5-ea07361b26a6
21:35:47.833 > Client ID: 0, Address: cc:21:19:9e:7f:c8, Subvalue 1, Characteristics beb5483e-36e1-4688-b7f5-ea07361b26af
21:35:47.834 > Client ID: 0, Address: cc:21:19:9e:7f:c8, Subvalue 1, Characteristics beb5483e-36e1-4688-b7f5-ea07361b26a5
21:35:47.835 > Client ID: 0, Address: cc:21:19:9e:7f:c8, Subvalue 1, Characteristics 6e400003-b5a3-f393-e0a9-e50e24dcca9e
21:35:47.991 > BLH - onRead : 6e400003-b5a3-f393-e0a9-e50e24dcca9e
21:35:47.993 > BLH - Read VESC_CHARACTERISTIC_UUID_TX_UUID
21:35:47.993 > onRead to characteristics: 6e400003-b5a3-f393-e0a9-e50e24dcca9e
21:35:47.993 > onRead - value:  -  - length: 0
21:35:47.994 >
21:35:48.186 > BLH - onRead : 6e400002-b5a3-f393-e0a9-e50e24dcca9e
21:35:48.187 > BLH - Read VESC_CHARACTERISTIC_UUID_RX_UUID
21:35:48.188 > onRead to characteristics: 6e400002-b5a3-f393-e0a9-e50e24dcca9e
21:35:48.189 > onRead - value:  -  - length: 0
21:35:48.189 >

On my side, it's weird because it tries to read datas.

But from my understanding, it should first send a write to push serial to VESC (write with VESC_CHARACTERISTIC_UUID_TX_UUID) in order to get an answer (then read with VESC_CHARACTERISTIC_UUID_RX_UUID).

Could you tell me what am I missing please ?

Regards,
F.

I am trying to connect esp32 with a flipsky vesc, but cannot get esp to work. I connected it only through UART because I do not have CAN bus transceiver.

Hello,
it worked before, but now, it can't detect other VESC in CAN bus.
did you try the latest officiel android VESCTool release ?
Regards,
F.

When half of the footpad is stepped on, the amount of LEDs that turn on to show what footpad is pressed does not adjust depending on the size of the strip used. When an even number of LEDs is specified it should divide the strip in half and use that, and when an odd number of LEDs is specified it should subtract 1, divide the number of LEDs in half and then use that amount.

What would make a lot of sense would be to add an option in the settings menu on the app to customize how many LEDs are used for that detection and the padding in the middle of the two halves.

Hardware-Version: v3.1 (old board biggest one)

the lightbar footpad sensor VISUAL indications are not working on firmware versions 2.4.1 and up to 2.5.4

I reverted back to 2.3.3 and then they work.

Implement support for SK6812 RGBW LEDs as used e.g. by the Onewheel Pint.

Hello,
very nice project !
I am curious about the piezo buzzer.
it works with an audible noise even in the enclosure with 3.3V ?
did you measure the current ? not drawing to much current from ESP pin ?
Regards,
F.

We want to change the color of the front- and backlight not only for idle mode, it should also work while riding and when changing direction.

Floatwheel / Balance Pro turns on while charging, so it makes sense to turn off the lights when in idle state for longer than xx seconds.

Make the MTU size configurable to override e.g. values from handshake. Sometimes the negotiation during handshake doesn't work well.

Specifically when trying to edit the battery configuration in the device settings, the option get reset every time the menu is opened instead of recalling the current settings. This becomes annoying quickly when you want to change only a single setting and upon saving, notice that the other options in the menu have been set back to default.