Did you happen to use the RX11 and TX9 version of the firmware? It happens that I had a problem in my build script, and that one did not build correctly. I did not test it either, as my BLE module had the other connection. It should be fixed in VESC Tool 1.12. It is building now and should appear in around 20 minutes from when I write this reply. Can you give it a try?
Hi I was able to flash a 16K rx11 tx9 nrf from the new vesc tool 1.12. Module is discoverable and read and write to vesc through the module is all good.
I have tested my 16k module with Rx:11 and Tx:9. Flashed with 1.12 FW. I was able to connect, read and write app config a well motor config. Logging seems too heavy for my phone and causes BT connection drop from time to time.
One minor thing - at some point i was able to use this nice controll feature and play with different ways to controll the motor. Now i hear only short click but motors does not spin. Minor thing, usefull for education
I bought a NRF51822 from ebay couple days ago and programmed it with my VESC HW4.12. Everything is working perfectly and it is so easy to programm the NRF with the VESC. Thank you for this cool piece of software =)
At the moment I am working on a wireless remote control. I am planning to use a Wii Nunchuck combined with a NRF51, but it could take a while till I'll finish it because of work and laziness xD
This is bringing me to my question. Is it possible to control the VESC with NRF51 using your VESC Tool on my Android phone? I would be realy cool if I could just open the app and use something like a slide bar at my screen to accelerate and decelerate ^^ and it could be a good backup solution if the battery of your remote is dying =)
I think there is no slider implemented in the mobile VESC Tool to control the motor because its a bit unsafe to use the touchscreen for precise throttle commands. And some people would abuse that feature as their primary remote which could result in some accidents. At least that is my guess why there isn't that option available.
I could connect via the SWD port and program but now i dont think the firmware supplied in the vesc tool has the right pins for rx / tx - i think the board uses p3 and p4.
What do i need to do to get it working?
EDIT: I just tried again - connecting pins 3 and 4 on the module to the tx/rx (tx module to rx vesc etc.) and i got it working with the firmware 16mhz RX 1 TX 2
Its a good little module if anyone is looking for one.
Works with VESC HW 4.12 and the 3.57 firmware and VESC-Tool app.
I think its only 16k RAM so has limited firmware fuctions (wont work with Bluetooth remote?)
Yeah I see the problem with the imprecise throttle commands too. A slider was just the first thing that came to my mind. Maybe two buttons (+ and -) to set speed in discreet steps could be an option.
Though there is no way to prevent that people would use this feature as primary remote, but this is every ones own decision^^ I think a good working well thought-out system could also work on a touchscreen
I see you released the firmware for NRF51 modules On Git, but I can’t seem to find the firmware for NRF52. Is that publicly available yet? I’d very much love to tinker with it.
i am trying to make BLE module work with VESC tool android app.
I have bought this one https://www.aliexpress.com/item/32892343351.html?spm=a2g0s.9042311.0.0.2...
' 32-bit ARM Cortex M0 processor 128-bit AES hardware encryption processor 256kB flash / 32kB RAM ''
I have maytech 100amps VESC so i cant connect to VESC windows tool to flash my NRF51 module so i am trying to flash with STLink 32 but i cant make it done.
Is there anyone who has pre built file that i can flash via STlink 32 + openocd on linux ?
I am also trying to get my BLE module (NRF51822) working, tried first to program it with a ST-LINK V2 with this as result:
bash upload_merged
Open On-Chip Debugger 0.9.0 (2018-01-24-01:05)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 1000 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : Unable to match requested speed 1000 kHz, using 950 kHz
Info : clock speed 950 kHz
Info : STLINK v2 JTAG v31 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.212598
Info : nrf51.cpu: hardware has 4 breakpoints, 2 watchpoints
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x0001b200 msp: 0x20004000
Warn : Unknown device (HWID 0x00000058)
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
auto erase enabled
Info : Padding image section 0 with 2112 bytes
Info : Padding image section 1 with 32 bytes
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : "set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000001e msp: 0xfffffffc
wrote 128000 bytes from file hex/nrf51_vesc_ble_wt.hex in 5.431079s (23.016 KiB/s)
** Programming Finished **
** Verify Started **
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0xfffffffc
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0xfffffffc
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0xfffffffc
verified 125560 bytes in 0.826215s (148.408 KiB/s)
** Verified OK **
** Resetting Target **
shutdown command invoked
It's almost the same as a post on page 1, after this I could not find any bluetooth module on my phone. Also a remark that in the hex directory is 'nrf51_vesc_ble_wt.hex' version and in the script file 'nrf51_vesc_ble.hex'. I don't know if this is a problem ?
Found out in this topic that you can also use the VESC as a programmer, but could not find a target, there is also a button extra in the VESC tool 'Connect NRF5X' but it stated that my hardware is not capable if I use that, but somewhere stated here from Benjamin is that the Hardware version (4.12) doesn't matter, is this correct ? Thought maybe it was broken, but connected it again to the ST-LINK, but same result, so I think it is still oké, because there is some communication.
Try now with some other wiring.
[EDIT] Thank you for all the work you put in to this Benjamin.
It is already solved, I used the binary 'nrf51_vesc_ble_16k_16m_rx11_tx9_led3.bin' in the build_all directory and immediately after programming it with the ST-LINK, it appeared on my phone. Thought there was another problem, because when I changed the App settings to ADC it didn't work anymore, took me a while to find out the UART has to be active, in the back of my mind I thought the communication with the module would always be active.
Now have to find out to change the code so the uart is also active with a custom application, there is no option in the app settings like 'ADC and UART', have to find out.
Strange thing still is that I couldn't program it with the SWD from the VESC.
Hi Benjamin, I was curious as to why the METR Pro could connect to Windows using the NRF52 series, but the NRF51 series with your firmware needs Linux. Is it possible to get a NRF52 series to connect via Windows?
This bluetooth issue is irritating.
FWIW, my regular DX-BT18 off of aliexpress works between VESC and windows VESC-Tool for me, even realtime data is ok. It fails with android app or MacOSx VESC-Tool.
I use BT as serial bridge in many different applications to and from PCs and mobiles, this is the first time for me to find the communication over BT requiring a hacked/modified/broken BT module firmware.
Very confusing, especially it working with windows+VESC-Tool but nothing else. With my limited understanding of the few facts I have so far found for this decision I fail to applaud this design solution, yet. Anyone can shed more light here, please?
This bluetooth issue is irritating.
FWIW, my regular DX-BT18 off of aliexpress works between VESC and windows VESC-Tool for me, even realtime data is ok. It fails with android app or MacOSx VESC-Tool.
I use BT as serial bridge in many different applications to and from PCs and mobiles, this is the first time for me to find the communication over BT requiring a hacked/modified/broken BT module firmware.
Very confusing, especially it working with windows+VESC-Tool but nothing else. With my limited understanding of the few facts I have so far found for this decision I fail to applaud this design solution, yet. Anyone can shed more light here, please?
I'm currently working on a firmware for the ESP32 to use it as a BLE-UART-Bridge. I lalready got it working with the VESC tool app for android. I still have problems with 3rd-party apps for iOs like "Yours Truly" and "metr.at". The don't find the VESC when scanning. I'm wondering that they can't see the VESC although the VESC tool app can. I have no idea why this is the case. Does anyone have an idea?
I am facing same issue as you. I am using vesctool 3.0 on Mac and NRF51822 . I am not sure what do you mean by these commands. When i try to connect using VESC tool. it just give me an error "could not connect to target"
Testet. Unfortunately my nRF51 16k is not discoverable flashed by Vest Tool 1.11
I had to go back to FW from Vesc Tool 1.10 - and nRF apeared again
Did you happen to use the RX11 and TX9 version of the firmware? It happens that I had a problem in my build script, and that one did not build correctly. I did not test it either, as my BLE module had the other connection. It should be fixed in VESC Tool 1.12. It is building now and should appear in around 20 minutes from when I write this reply. Can you give it a try?
Hi I was able to flash a 16K rx11 tx9 nrf from the new vesc tool 1.12. Module is discoverable and read and write to vesc through the module is all good.
I will do as soon as i get to my board
Just tried with the new 1.12 version, i still get the "could not recognize target" when i try to connect with SWD prog..
Terminal log:
AP 0: IDR=04770021 CFG=00000000 BASE=f0000003 CSW=03000040
0xe000e000: Generic IP component - Cortex-M0 SCS (System Control Space)
-> cortexm_probe
0xe0001000: Generic IP component - Cortex-M0 DWT (Data Watchpoint and Trace)
0xe0002000: Generic IP component - Cortex-M0 BPU (Breakpoint Unit)
0xf0002000: Debug component - Unknown (PIDR = 0x4000bb9a3)
I have tested my 16k module with Rx:11 and Tx:9. Flashed with 1.12 FW. I was able to connect, read and write app config a well motor config. Logging seems too heavy for my phone and causes BT connection drop from time to time.
One minor thing - at some point i was able to use this nice controll feature and play with different ways to controll the motor. Now i hear only short click but motors does not spin. Minor thing, usefull for education
Hi,
should the windows-version of the VESC-tool already work with BLE devices?
Appearently this should work now with QT ( https://forum.qt.io/topic/91117/bluetooth-low-energy-windows/10 ). I have even paired my bluetooth adapter ( https://www.trampaboards.com/vesc-connect-wireless-dongle-p-25516.html ) manually using windows-internal controls; the dropdown in the VESC tool still stays empty, though.
Hi Benjamin,
I bought a NRF51822 from ebay couple days ago and programmed it with my VESC HW4.12. Everything is working perfectly and it is so easy to programm the NRF with the VESC. Thank you for this cool piece of software =)
At the moment I am working on a wireless remote control. I am planning to use a Wii Nunchuck combined with a NRF51, but it could take a while till I'll finish it because of work and laziness xD
This is bringing me to my question. Is it possible to control the VESC with NRF51 using your VESC Tool on my Android phone? I would be realy cool if I could just open the app and use something like a slide bar at my screen to accelerate and decelerate ^^ and it could be a good backup solution if the battery of your remote is dying =)
I think there is no slider implemented in the mobile VESC Tool to control the motor because its a bit unsafe to use the touchscreen for precise throttle commands. And some people would abuse that feature as their primary remote which could result in some accidents. At least that is my guess why there isn't that option available.
I just brought these tiny modules https://www.amazon.ca/gp/product/B07NRT9VRV/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
YTX51822-S01 - https://cooltech-hk.store/products/nordic-51822-low-cost-bluetooth-low-energy-module-ble4-0
I could connect via the SWD port and program but now i dont think the firmware supplied in the vesc tool has the right pins for rx / tx - i think the board uses p3 and p4.
What do i need to do to get it working?
EDIT: I just tried again - connecting pins 3 and 4 on the module to the tx/rx (tx module to rx vesc etc.) and i got it working with the firmware 16mhz RX 1 TX 2
Its a good little module if anyone is looking for one.
Works with VESC HW 4.12 and the 3.57 firmware and VESC-Tool app.
I think its only 16k RAM so has limited firmware fuctions (wont work with Bluetooth remote?)
Yeah I see the problem with the imprecise throttle commands too. A slider was just the first thing that came to my mind. Maybe two buttons (+ and -) to set speed in discreet steps could be an option.
Though there is no way to prevent that people would use this feature as primary remote, but this is every ones own decision^^ I think a good working well thought-out system could also work on a touchscreen
Thank you Benjamin for your fantastic work.
I see you released the firmware for NRF51 modules On Git, but I can’t seem to find the firmware for NRF52. Is that publicly available yet? I’d very much love to tinker with it.
Thank you. 😊
i am trying to make BLE module work with VESC tool android app.
I have bought this one
https://www.aliexpress.com/item/32892343351.html?spm=a2g0s.9042311.0.0.2...
' 32-bit ARM Cortex M0 processor 128-bit AES hardware encryption processor 256kB flash / 32kB RAM ''
I have maytech 100amps VESC so i cant connect to VESC windows tool to flash my NRF51 module so i am trying to flash with STLink 32 but i cant make it done.
Is there anyone who has pre built file that i can flash via STlink 32 + openocd on linux ?
I am also trying to get my BLE module (NRF51822) working, tried first to program it with a ST-LINK V2 with this as result:
It's almost the same as a post on page 1, after this I could not find any bluetooth module on my phone. Also a remark that in the hex directory is 'nrf51_vesc_ble_wt.hex' version and in the script file 'nrf51_vesc_ble.hex'. I don't know if this is a problem ?
Found out in this topic that you can also use the VESC as a programmer, but could not find a target, there is also a button extra in the VESC tool 'Connect NRF5X' but it stated that my hardware is not capable if I use that, but somewhere stated here from Benjamin is that the Hardware version (4.12) doesn't matter, is this correct ? Thought maybe it was broken, but connected it again to the ST-LINK, but same result, so I think it is still oké, because there is some communication.
Try now with some other wiring.
[EDIT] Thank you for all the work you put in to this Benjamin.
It is already solved, I used the binary 'nrf51_vesc_ble_16k_16m_rx11_tx9_led3.bin' in the build_all directory and immediately after programming it with the ST-LINK, it appeared on my phone. Thought there was another problem, because when I changed the App settings to ADC it didn't work anymore, took me a while to find out the UART has to be active, in the back of my mind I thought the communication with the module would always be active.
Now have to find out to change the code so the uart is also active with a custom application, there is no option in the app settings like 'ADC and UART', have to find out.
Strange thing still is that I couldn't program it with the SWD from the VESC.
Hi Benjamin, I was curious as to why the METR Pro could connect to Windows using the NRF52 series, but the NRF51 series with your firmware needs Linux. Is it possible to get a NRF52 series to connect via Windows?
Hi Folks,
I need a little help with NRF51822 Windows desktop VESC Tool connection.
My setup:
WT51822-S4AT 256k/16k module flashed via SWD actual firmware: nrf51_vesc_ble_16k_16m_rx1_tx2_led3.bin
ESC VESC A200S V2.1 actual firmware 4.1
VESC Tool 2.02 running on Winows 10
Problem:
I Can't connect to VESC Tool via BLE, the dropbox is empty. In windows I can connect and pair to BLE adapter, but VESC Tool not see the BLE module.
In the mobile APP (Android 7.1) no issues all works fine, only in Windows APP I had this issue.
Can someone point me what I'm doing wrong.
Thanks.
UP,
nobody solved this connection issue through BLE to vesc tool?
Meantime updated to newest firmware ver. 4.02, vesc tool to ver. 2.03.
No succes, BLE not show up in drop down menu.
In mobile version still all works fine.
This solved my problem too.
Just copy the file in the hex directory and run upload_merged
Thank you!
This bluetooth issue is irritating.
FWIW, my regular DX-BT18 off of aliexpress works between VESC and windows VESC-Tool for me, even realtime data is ok. It fails with android app or MacOSx VESC-Tool.
I use BT as serial bridge in many different applications to and from PCs and mobiles, this is the first time for me to find the communication over BT requiring a hacked/modified/broken BT module firmware.
Very confusing, especially it working with windows+VESC-Tool but nothing else. With my limited understanding of the few facts I have so far found for this decision I fail to applaud this design solution, yet. Anyone can shed more light here, please?
dancing with bikes
Please removed . I don't see a delete button..
Justin nguyen
noone knows or noone cares?
dancing with bikes
Hi,
I'm currently working on a firmware for the ESP32 to use it as a BLE-UART-Bridge. I lalready got it working with the VESC tool app for android. I still have problems with 3rd-party apps for iOs like "Yours Truly" and "metr.at". The don't find the VESC when scanning. I'm wondering that they can't see the VESC although the VESC tool app can. I have no idea why this is the case. Does anyone have an idea?
David
Hello,
I am facing same issue as you. I am using vesctool 3.0 on Mac and NRF51822 . I am not sure what do you mean by these commands. When i try to connect using VESC tool. it just give me an error "could not connect to target"
Mahesh
Pages