Hello. I'm trying to connect to the vesc by hm-10 module. Everything is wired like on image below. Red led on module is blinking quite slowly. VESC tool mobile is recognizing module, but after clicking "connect" nothing happens, just red led stops blinking and flash constantly for about 1 sec. Tried on 2 phones- Xiaomi mi 5s plus and Huawei p9 lite- both the same. After many tries i got such information (2nd image below). What i can do now? Is anyone knows what that error means?
You are here
Problem with Bluetooth connection (HM-10)
Mon, 2018-07-30 15:56
#1
Problem with Bluetooth connection (HM-10)
Same thing as squdowx.
jzy1115 post makes no sense to me to be honest because changing to PPM and Uart does nothing. I use 2 vesc and BL dongle is connected to Slave.
jzy1115
Everything on this app is possibly to save AFTER connection, while we can't even connect via bluetooth to modul. APP CFG means vesc app configuration, . not this android app configuration.
The UUID of VESC tool is different from HM10, and my VESC tool is modified by UUID.
I used the official source code to modify the UUID and recompile it.
AFAIK, Vesc Tool mobile app is only compatible with NRF51 with custom FW written by Ben ( https://github.com/vedderb/nrf51_vesc ).
http://www.trampaboards.com/vesc-connect-wireless-dongle-p-25516.html
works out of the box.
Frank
Hi, trying to follow the instructions on https://github.com/vedderb/nrf51_vesc to program some generic NRF51822 boards.
The upload_merged script meant to offer a precompiled hex references a hex/nrf51_vesc_ble.hex that isn't provided
There's only a nrf51_vesc_ble_wt.hex which probably doesn't apply to the pictured BT module.
Any help would be much appreciated!
-- Edit : Found that file in the GIT history. Hopefully that does the job
Hi,
my nrf51822 was also not working with this hex file and is not recognize by the vesc-tool. It is a "Waveshre Core51822" Module, ordered by the german shop eckstein. It is a module with 256k flash and 16k memory. i got it up and running by programming the nrf51_vesc_ble_32k_16m_rx11_tx9_led3.bin file from the build_all folder with the following command:
openocd -f openocd.cfg -c "program build_all/nrf51_vesc_ble_16k_16m_rx1_tx2_led3.bin verify reset exit"
using a st-link 2
Maybe this will work for you also
Regards
Georg