🌴 Go-FOC DV6 / PRO <High Current Dual ESC >

[Evwan]

Leave it on 5.2 and be happy. Not worth the risk.

[GeneParmesan]

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?

[skrzypol]

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?

@Evwan

Leave it on 5.2 and be happy. Not worth the risk.

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

[JeffyJ]

@sleepless

Sounds like a bootloader issue

Did this. Still failed

@tech.shit

The one on the MakerX website reports the wrong version. I had this exact same issue.

Well that’s dumb

@tech.shit

You also want to do each side separately and then power cycle after.

Did this. Seemed to work but when I turned off and back on it was back to 5.2

@jaykup

Two people (that I know of) are running this custom 5.3 firmware and haven’t reported anything strange.

Where do I find the 5.03 custom FW file then do you know?

[skrzypol]

@JeffyJ

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:

Go-FOC DV6 3-12S Dual drive ESC for electric Skateboard Base On VESC6

@jaykup

Two people (that I know of) are running this custom 5.3 firmware and haven’t reported anything strange.

Can you contact me with that people please? Are they on this forum?

[JeffyJ]

@skrzypol

The link is from the official website:

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…

Noob question thread! 2020_Summer

Someone else was saying that maybe the 5.3 firmware they uploaded to the DV6 Pro is only showing 5.2 so that’s why I’m curious. I can build it at 5.3 based on the code changes he figured out if that’s the case. I was curious and loaded the MakerX DV6 Pro 5.3 binary they released to my VESC 6 just to see what the firmware version would read. [image] lol. So apparently @tech.shit wasn’t totally failing at updating his firmware. It was “sticking” and he was just replacing 5.2 with 5.2. G…

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.

[tech.shit]

@skrzypol

that people

I am that people

[jaykup]

@skrzypol

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

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.

[rusins]

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

[skrzypol]

@jaykup

Hopefully that clears some of it up.

Gods, that clears all dear sir, thank you!

@jaykup

Vedder seems to be using 5.03 to signify that it’s the beta, and 5.3 to signify that it’s the final release

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!

@jaykup

If you already tried to use their new files

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.

[jaykup]

@skrzypol

@jaykup

Vedder seems to be using 5.03 to signify that it’s the beta, and 5.3 to signify that it’s the final release

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!

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.

[ShutterShock]

Not sure if better or worse…

It has always been super confusing

[xsynatic]

We talked about that last year i think. 5.01/02/03 and 5.1/2/3 are the same, the vesc tool just removes the 0. I can’t find where we talked about it. @b264 was it with you when you published the vari tool?

E:

@b264

@ShutterShock

But it lists it as 5.1 in Vesc tool, should that have been 5.01

Software versioning is funny.

In between each period, it’s treated as its own number. 01 = 1

Don’t ask why; I don’t know.

It’s confusing. 5.10 is more than 5.2 and 5.05 is more than 5.2 and 5.2 is less than 5.03.

[tech.shit]

Although, you are technically right. 5.03 is sort of the beta for 6.00

[skrzypol]

@b264

It’s confusing. 5.10 is more than 5.2 and 5.05 is more than 5.2 and 5.2 is less than 5.03.

Sooo… we have (in asc order):

• 5.2, stock FW which comes with the DV6Pro - is it working fine? I assume, amps are limited to 100A, right?
• 5.3, custom by @jaykup, used by him and @tech.shit - any test drives yet? @tech.shit, are breaks working?
• 5.03, custom by MakerX, reported to not work, as it is the wrong version or the wrong file uploaded, yes?

[xsynatic]

@skrzypol

5.2, stock FW which comes with the DV6Pro - is it working fine? I assume, amps are limited to 100A, right?

As far as i know, yes.

@skrzypol

5.03, custom by MakerX, reported to not work, as it is the wrong version or the wrong file uploaded, yes?

The custom 5.3 fw by makerX reports the version 5.2, thus getting troubled by vesc tool.

Jaykup modified it so it properly shows 5.3.

@jaykup correct?

---

I will definitely not buy a vesc that requires custom fw all the time. I don’t want to be locked by their firmware. If they submit it and Vedder merges it so it can use official fw, then yes. That goes for everyone, be it makerx, spintend, flipsky or who else.

[brown5tick]

@skrzypol

5.2, stock FW which comes with the DV6Pro - is it working fine? I assume, amps are limited to 100A, right?

They ship it with a firmware that doesn’t properly support its hardware!?

[jaykup]

As far as I understand it:

• DV6 PRO ships with the correct 5.02/5.2 using different shunt resistances and setting a 180A max limit.
• MakerX releases 5.03/5.3 but it loads as 5.02/5.2. Don’t know what it actually is.
• I compiled 5.03/5.3 for the DV6 PRO by changing the shunt resistances and setting a 180A max limit.

For anyone interested this is the difference between the VESC 6 firmware and the DV6 PRO

@BrushlessHipster

Take hw_60.h and change

#define HW_NAME "Go-FOC DV6 Pro"

#define CURRENT_SHUNT_RES (0.0005 / 2)

#define HW_LIM_CURRENT			-180.0, 180.0
#define HW_LIM_CURRENT_IN		-180.0, 180.0
#define HW_LIM_CURRENT_ABS		0.0, 200.0

[tech.shit]

My brakes weren’t working because of an unrelated hardware issue, I’ve fixed it since posting about it.

@jaykup custom 5.3 works just fine for me, I haven’t had a chance to test out the new features yet though. RT data is cool on the dials on desktop.

[tech.shit]

@brown5tick

They ship it with a firmware that doesn’t properly support its hardware

Yes, many ESC makers do this including Spintend