You are here

"Could not read Firmware version" when connecting via Bluetooth

15 posts / 0 new
Last post
ligi
ligi's picture
Offline
Last seen: 5 days 2 hours ago
VESC Free
Joined: 2020-08-21 08:21
Posts: 24
"Could not read Firmware version" when connecting via Bluetooth

I am having problems getting bluetooth to work. I would love to see my speed (somehow do not find this in the vesc tool on linux. But I know it works on the android app.

The bluetooth module gets power (measured 3.3v) And it gets seen when scanning - but when connecting: it connects but then gives me this error:

Screenshot_20201117-051313.png

Anyone knows what could go on here? Can I somehow see the speed in the vesc tool on linux? Also the LED of the BT module is not lighting in any way - ist this ha hint on what is going on?

 

nocivo
Offline
Last seen: 1 year 1 month ago
Joined: 2021-03-30 23:18
Posts: 2

i'm having the same problem, any solution yet ?

 

nocivo
Offline
Last seen: 1 year 1 month ago
Joined: 2021-03-30 23:18
Posts: 2

upgrade the firmware to 75_300_r3 and it worked for me 

 

JulianVesc
Offline
Last seen: 3 years 3 months ago
Joined: 2021-05-29 11:08
Posts: 2

Hello,
Unfortunately I am also having this problem. Switching comms to ADC&UART did not help.

Context:
I just got a VESC6MKV from Trampa including the BLE dongle (NRF52840) and the magic wand. I am now trying to connect the wand to the VESC but have no luck at all. I have tried to connect the wand via the MAC OSX VESC tool as a NFR Controller, but without success, therefore I am trying Android now.

 

Setup:
The VESC is flashed to firmware 5.2
Hareware is 60_MK5
BLE dongle (Trampa VESC-ConnectNRF52840, V2.0 , M/N: BL654, R2.0) connected to COMM
Android VESC tool (3.00) from the Google App store

Steps to Reproduce:

  1. With the Android VESC tool of the Google App store scan the BLE conncetions
  2. I do see a device called VESC 52840 [D8: ... :75]
  3. Select VESC 52840 [D8: ... :75] from dropdown
  4. Hit the CONNECT button

Actual Results:

  1. red LED on the dongle lights up for about 3 seconds
  2. At the bottom of the App it reads: "Connected (BLE) to [D8: ... :75]"
  3. red LED on dongle turns off
  4. Message in App: "Read Firmware Version - Could not read firmware version. Make sure that the selected port really belongs to the VESC".
  5. At the bottom of the App it reads: "Not connected"

Expected Results:

  1. Connection gets established
  2. I can continue setting up the wand

Questions I have

  1. Can the dongle be broken?
  2. What is the correct firmware for my BLE dongle?
  3. Where do I find the correct firmware for BLE dongle?
  4. Is the new VESC firmware (5.2) too new for the VESC App (3.00)?

thumb_Vescdebugging.png

Any help or hints welcome! I have already spent hours on this and cannot find any way to get this to work.

JulianVesc
Offline
Last seen: 3 years 3 months ago
Joined: 2021-05-29 11:08
Posts: 2

Addendum:
I assume that the above fix upgrading to the firmware 75_300_r3 will not work as I am dealing with a VESC 60 MKV. The factory bootloader I have not touched just ran the update to 5.2 through OSX VESC Tool.

spacewalker
Offline
Last seen: 1 year 8 months ago
Joined: 2020-06-10 12:30
Posts: 29

this is a issue  with  VESC configuration,   

enable UART   from settings,   go to Bt  and add   UUID , then  do PAIR  and add that UUID   manually to your APP  

 

Martin

STG
Offline
Last seen: 2 years 10 months ago
Joined: 2022-02-28 19:47
Posts: 1

Hello,

i have the same issue. Trampa VESC 6, Firmware 5.3 (from the vesc tool). I've added the uuid manualy like the post above says, but there is still the same problem: after connected to the board, the app shows "Read firmware version.could not read firmware version.make sure that the selected port belongs to the vesc"

cir7
Offline
Last seen: 2 months 2 weeks ago
VESC Free
Joined: 2020-06-06 12:16
Posts: 5

Same issue here! I bought Trampa BLE dongle and can't connect to the VESC app as I'm getting the error: "Read Firmware Version - Could not read firmware version. Make sure that the selected port really belongs to the VESC". Did Trampa check the BLE compatibility with the latest firmware?

xxx1den1xxx
Offline
Last seen: 7 months 3 weeks ago
Joined: 2022-05-31 19:56
Posts: 1

'I am having problems getting bluetooth to work. I would love to see my speed (somehow do not find this in the vesc tool on linux. But I know it works on the android app.

The bluetooth module gets power (measured 3.3v) And it gets seen when scanning - but when connecting: it connects but then gives me this error:'

if Could not read Firmware version

I solve the problem! Just change green and orange wire (tx and rx) on bluetooth module. It worked for me. app is working now.

kvasik
Offline
Last seen: 1 year 4 weeks ago
Joined: 2020-11-15 14:28
Posts: 1

Thanks.
Change tx and rx it works!

111 222

The_Hackintosh
Offline
Last seen: 2 months 2 weeks ago
Joined: 2023-12-22 20:33
Posts: 1

I have the same BT module, but my desktops can connect but mobile cant. Should i flip them regardless?

electricfox
electricfox's picture
Offline
Last seen: 1 hour 5 min ago
VESC Original
Joined: 2019-01-01 17:11
Posts: 139

No, it should connect with PC and phone. Make sure to disconnect manually from PC before trying to connect to your phone.

BrianN
Offline
Last seen: 10 months 3 weeks ago
Joined: 2024-01-24 12:28
Posts: 1

I had the same problem connecting to Bluetooth on a makerbase 75200.  I connected it via USB to a laptop and that seem to reset whatever got it stuck.  After connecting via USB, which worked perfectly on the first attempt, it then failed on a second attempt, at which time I realized it had reconnected to Bluetooth

slosson
Offline
Last seen: 7 months 3 weeks ago
Joined: 2024-06-14 02:16
Posts: 1

bro!!!!! Thank you this worked for me as well!!!!!!! OMG HAPPY DANCE

 

<p>Sloss1n</p>

Gmcruz463
Gmcruz463's picture
Offline
Last seen: 2 weeks 4 days ago
VESC Free
Joined: 2022-11-13 07:30
Posts: 2

hey,

ive tried all the steps above and nothing is working .... i cannot use my usb port do to it being istalled incorrectly from the factory so ive never used it via mac or windows at least not this product ... ive previously switched the RX and the TX wires and that did the job but now imout of options because it doesnt read at all 

Giovanni Cruz