https://metr.at/faq#q32 What pins of the JST connector are necessary for Metr Pro to work?
Only four pins: 3.3V, GND, TX and RX need to be connected. The cable uses 7 wires to match ESCs 7 pin connector. We can not provide a cable with missing wires and we donāt really have time to remove them. You canāt power the module with 5V.
If you have something sharp you can carefully rearrange pins in JST connector one by one.
Nevertheless, Iām worried about this FW version. Can anyone confirm or contradict the presence of the bugs in the DV6 PRO 5.03 mod? Because @YUTW123 is not respondingā¦ 
Tried installing custom FW yesterday unsuccessfully. Had version 5.2, tried uploading custom DV6 PRO file one side at a time via USB and it would seem to work and show 5.3. When I disconnected then turned esc off and then back on, then reconnected to vesc tool it was back to 5.2.
I refreshed bootloader first too.
Ran out of time so gave up. Maybe need to upgrade to 5.3 first then try custom FW file 
.
Sounds like a bootloader issue
Use the custom file by @jaykup
The one on the MakerX website reports the wrong version. I had this exact same issue.
You also want to do each side separately and then power cycle after.
With the ~month long Chinese New Year going on I wouldnāt expect a response until mid-late Feb.
As far as we can tell, itās only the hardware configuration part of the firmware that was changed. MakerX changed the shunts on this unit with lower resistance ones so they run cooler. The firmware just needs that resistance value to accurately measure the current. The other change is to raise the maximum allowable current limits compared the regular VESC 6 firmware.
I think when they posted the 5.3 binary, they accidently uploaded the 5.2 binary, or compiled it incorrectly.
Two people (that I know of) are running this custom 5.3 firmware and havenāt reported anything strange.
Nothing weird happened on my ācustomā 5.3 yet, besides not being able to use metr Expert Mode on day 1 but itās worked fine since.
I just picked up a dv4 for a friend. Im gonna set it up then itll pretty much stay as is. Should I update the FW or just leave it be?
Leave it on 5.2 and be happy. Not worth the risk.
Youāre right, it is 5.2. I assumed it was something older for some reason. Could this be the reason Iām having trouble connecting to vesctool on pc if I downloaded the new version for use with my stormcore?
So you mean 5.3 posted in noob questions thread (MakerX_DV6_PRO_5.3_UNOFFICIAL_jaykup.bin)?
Sorry for asking, but Iām getting confused because after posting this bin by @jaykup you have written you have a problem with breaks - or that was on another FW?
What do you mean? 5.2 is stock FW that comes with the DV6PRO? As far as I understand 5.2 doesnāt have the required modification for the max amp and other things.
I have no idea why makerX has written on their page that their 5.03 mod is required, and I read it is not a 5.03 really but 5.2 indeed?
Ooooh, help me to get out of this maze. This is my first build and I want to be sure it will work 
Did this. Still failed
Well thatās dumb 
Did this. Seemed to work but when I turned off and back on it was back to 5.2
Where do I find the 5.03 custom FW file then do you know?
https://drive.google.com/file/d/1-OFkWbNUdvaoxpzLMdFi-aAycK7J7GMT/view?usp=drivesdk
The link is from the official website:
Can you contact me with that people please? Are they on this forum?
Tried that version already and it didnāt work.
Iāve had success now with the file @jaykup put up. Will try link it hereā¦
Click on link and scroll down to file labelled:
(MakerX_DV6_PRO_5.3_UNOFFICIAL_jaykup.bin)
It still did some weird stuff and I thought it didnāt work but went ahead and did the other side of the esc anyway. Got some strange freezes and thought it was stuffed. Then couldnāt seem to connect to vesc tool at all. I turned everything off and back on and it was updated. Ran motor detection and all working. Still yet to test ride.
I am that people
It is very confusing, it took me a long time to figure out the VESC firmware maze.
Versioning: 5.02/5.2 and 5.03/5.3 are the same thing. The official version is a 3 digit X.XX number. There is a bug in the VESC tool where it removes the zero. In the code, the firmware version is stored in two variables, major (5) and minor (03). When it prints those variables in the tool, it uses ā%dā instead of ā%02dā, which results in the leading zero on the minor version being removed.
Stock vs custom firmware: All VESCs can run the latest firmware as long as there is a hardware configuration for it. The hardware config is code that gets compiled into the firmware and tells the firmware how to use that specific hardware. Things like if it has a DRV chip or not, low vs high side shunts, shunt resistance values, number of UART/PPM ports and how they are connected, max amp values, etc. The core of the firmware (how it actually drives the motor) doesnāt change.
*There are always exceptions for people who build really custom VESC hardware, but thatās not relevant to the DV6 PRO
Most manufactures simply copied the official VESC 6 hardware design so it could use the regular āHW_60ā firmware, which is just the core firmware configured for the VESC 6. That way manufacturers didnāt have to maintain and release new firmware versions, it could just work with the regular tool.
MakerXās DV6 just runs the regular VESC 6 āHW_60ā firmware. The DV6 PRO can handle more power than a regular VESC 6, and it measures current differently so it needed a new hardware configuration.
What MakerX should have done is written a hardware configuration for the DV6 PRO and submit that to Vedderās github for the firmware & tool. That way when the 5.3 firmware was released, it would show up as an option in the tool. Instead they released it on their website, and appear to have released an old version or a non-working file by mistake. So I took what @BrushlessHipster figured the hardware config should be and compiled a 5.3 version for the DV6 PRO.
Hopefully that clears some of it up. If you just want to get your first build going, the easiest thing to do is stick with the default 5.2 firmware that the DV6 PRO ships with. If you already tried to use their new files and now it doesnāt work right, the 5.3 I posted would be a good option to fix it.
This explanation is super helpful, thanks! Should help the community submit PRs for these 3rd party vescs ourselves, or at the very least come up with binaries for later FW versions 
Gods, that clears all dear sir, thank you!
I believe there is a special place in hell for such a practicesā¦ 
I mean, I appreciate his work, vesc project is remarkable, but cmon, that is not the way to version software!
Nope, sheās a virgin. Iām still missing the battery and enclosure, so way to go before I would be able to test it. Sadly.
Turns out I was still confused! The zero isnāt for beta, it only gets removed in the VESC tool due to a bugā¦ smh
Edited my post.
