Iām on the computer trying to get 5.3 installedā¦
Wish me luck.
I had similar issues with 5.3FW. Had success hard wired into PC except for the remote input. I had to run the detection for my remote through my phone App over bluetooth otherwise I got this message too.
You got the pro one as well?
Got the button working?
The button will turn the board on but it wonāt turn it off. I know thereās a setting somewhere in the FW to do so but I havenāt tried to find it yet as I have a loop key as well.
I think I got itā¦
Seems I got it working at this very moment.
Uses the PC to upload the special firmware for 5.03
Then the PC tool crashed.
Went over to the phone.
Ran detection ok.
Set up the ppm remote ok.
Set up the power to shut off after 5 minutes.
Which makes the button work.
I have everything plugged into the right side.
Maybe you should have the BT module in the main/left side? I noticed mine would confuse vesc idās when plugged into the right
That is where I started it atā¦
So much weird shit happened while I was trying to do the set up when it has 6.0 and I was trying over the phoneā¦
I had the blue tooth and controller on both sides.
Do you have the Pro version?
Which firmware are you running?
I have not taped everything down, so I could move it.
But I am also a little sketched out to do anything different since i just had it behave ok on a couple of tries.
Which side do you have the remote on? Are you running PPM?
Is your power button working?
Iām still waiting on my pro. This was with a d75. It was a lot less glitchy on 5.3 with the old vesctool and now with the new one Ive given up on using Bluetooth altogether. I ended up mounting a USB socket on my enclosure and only use bt to look at real-time data.
Sucks that itās still an issue with the new firmware.
Please find the firmware of DV6 PRO here, and upload it through VESC TOOL custom firmware.
The previously released firmware 5.2, and the firmware included in the 6.00 vesc tool will also work, but the switch function will not work.
Hey @YUTW123. In the past I ran two regular dv6s over CAN with GND CAN L and CAN H connected on 5.2FW. It ran reasonably well but was very underpowered compared to what Iām about to attempt.
Iāve since read numerous times that CAN L and CAN H is all that should be used. So now Iām a little confused. Iām very close to running my new 4wd race setup so would love a definitive answer if possible.
Iām about to connect an original DV6 pro (with no power button) with custom 5.3FW with a DV6 with regular FW.
The previous DV6 P does not support the switch button, but it is still possible to use the firmware on the download page.
Regarding CAN communication, it is recommended to use shielded twisted-pair wires to connect the two ESCs (as shown in the picture). This can greatly improve signal stability
Thatās great. Thanks for the info. So this would mean just CAN H and CAN L ![]()
Shield connected to GNDļ¼will better
So that metal wrap should be connected to GND at each end?
Do you guys sell the bus cables like that?
I havnt started plugging mine into the pc yet so nows a good time to know if i need to source one of these
Jaycar (only for Ozzy peeps sorry) have this but itās not twisted so not sure if as good?..
@JeffyJ I am in aus but i may as well just get some shielding and make my own
Oh i know. Thatās why i replied to u with that link haha. It was stated for everyone else
Iām curious why donāt we use this on all data/communication wires inside the enclosure?
Surely the power running through battery and phase wires is enough to cause EMI
I feel like wire shielding can even make some remotes more reliable.
Geez itād be nice if these things werenāt so buggy.
So 5.3 on mine. Didnāt touch that.
Motor detection all good, switch working. Unplug the computer put it all back together now switch doesnāt work.
Go into settings itās set to always on. Donāt know why that changed. Try to change it to off after 10 with Bluetooth and now I get drv faults.
Reload the saved config and it drops one side. ![]()
So I guess Iāll be opening it all up plugging in again and re doing firmware.
Whatās up with this bullshit

