Bluetooth connection is an amazing feature and we got really quickly dependent…
So lately i was messing arround with my test board (flipcheap 4.12), and i said to myself : “hey! this is the perfect time for using that unity BLE module who seats on my desk since i got my Metr receiver!”
I quickly soldered some jumper cables, plugged it, enjoyed the bluetooth detection (unity BLE 1.1), installed the VESC app and tryed to connect …
well, basically it says that the connection is successfull but that it can’t read the firmware version (wich is not a problem on the windows software)
Uart is enabled, baudrate is 115200 bdp, i’m alimented in 3v3, the esc does it’s work without problem…
(tryed to switch the ADC and ADC2 connections that i was not 100% sure of, doesn’t change a thing)
(isn’t the BLE module using only TX and RX anyway ?)
On the module side: i get led2 solid green, and led1 slowly flashing blue, nothing else
no, I realised I had other ble modules laying around and I lost interest,
I don’t remember exactly it was a long time ago, there was two possible explanations :
I’ve read somewhere that the unity needs a different ble firmware than other vesc compatible hardware, so maybe you could manage toflash it ?
it could have been a compatibility issue with the vesc configurator
ok, I’m far far from being an expert and this is the result of a wild guess and some googling, maybe @b264 have the answer ?
from what I’m seeing on github Vedder code works with nrf51 and nrf52 chips
the xiaoxiang bms BLE seems to be based on the CC2541 so it’s not likely than it is doable without “a bit” of codding
maybe you can post a picture of the bms’ module so we know for sure what chip it’s based on ?