Nvm I was being stupid.
Anybody know why I’m getting this issue?
1 Like
that message pops up for any reason the firmware can’t be read.
most often “bad connection” of some sort. crappy BLE, BLE dongle not connected to uart, crappy usb cable. … talking to non vesc, …
Maybe not part of the design but why not use a usb passthrough? Luckily my board has passthrough and BT but i mainly use the passthrough whenever i need to make a change.
Okay so its a brand new BT module, definitely plugged into uart, I shouldnt be having interference/blocking issues, so I dont know what it could be.
Is it possible the rx/tx were switched even tho I bought both from makerx so I would assume they are meant to be compatible.
Is there any reason I could be having issues from plugging in the ppm cable to the uart Port the BLE is connected to?
Is it because I changed input mode to PPM and it needs to be PPM and UART?
Because I don’t always have my computer and I like to tweak settings on the fly
1 Like
Imo the desktop vesc tool app is more prone to mistakes than the mobile one; from a purely human input perspective.
1 Like
Is it because I changed input mode to PPM and it needs to be PPM and UART?
Yes, I’m fairly certain nothing on the UART port works unless you have UART turned on, so if you’re using UART and a PPM remote, you need to use PPM and UART.
I was going to say if you have BT, you can use BT on the computer, but that issue will probably require connecting by USB to fix.
Is there any reason I could be having issues from plugging in the ppm cable to the uart Port the BLE is connected to?
Depending on what went where, it’s possible, but fairly unlikely. As long as you don’t somehow put a voltage larger than 5 V on the pins, things will survive most of the time, AFAIK, and it should be hard to short 5 V to ground or anything with a PPM receiver.
Edit: And to be clear, by nothing working I mean the signaling won’t work. The power and ground still work so the module will turn on, but it won’t be able to communicate with the ESC, causing issues like the one you’re having.
1 Like
I would definitely switch to UART + PPM since that is the right mode, but also I want to mention I get that error a lot on a board where the BLE module is just pretty flaky - tested across different VESCs - for that case rebooting will sometimes fix it, but I gave up eventually and just USB on that one.
Surprisingly I’ve had the least problems with Flipsky BLE modules but they haven’t been in service long.
Yeah I agree.
If you disabled uart (PPM mode only). and you have a BLE dongle connected to that uart. you will get that “can’t read firmware” message. using PPM + UART will likely fix.
1 Like
Yeah I came to the same conclusion as I was typing it out. Was a bit of a rush job and didn’t think about them when I was doing it.
1 Like
I’ve done that exact mistake.