I think that says the VESC is on 3.1. But I’m both not sure that’s the vesc annd not the configurator and if that would be a problem. I had lots of trouble getting older vesc configurators installed I can try send you something for a 5.xx related one later
1 Like
Wasnt tgere a weird jump in fw around 4 or 5 where you could only update to 5 from the latest 4 or some shit like tgat?
1 Like
I’d be willing to bet that an answer to your problem lies within these threads @Dnollie.
Please stop trying to read/write configurations or do any more detections until you have the firmware sorted.
4 Likes
That’s a screenshot from your video
That’s a quote from one of the threads I linked.
Don’t wanna sound like a grumpy old man, but you’re gonna need to use some problem solving skills here to make this work, you can’t just expect to be spoon fed every step of the way.
This is a head start, good luck
1 Like
@Dnollie As Al said don’t mess with any settings, wizards or anything until you figured out the firmware. Vesc can sometimes be iffy about doing big firmware jumps, go into the archive and download an older version of the tool and update via that, then do jumps to higher firmwares bit by bit.
Remember to follow the firmware reboot instructions after flashing, they were a bit different back then (the tool tells you)
2 Likes
They are og focbox’s, I updated the firmware from its 4.00 or whatever up to dv6/d75/d100 from the makerx website and then back down to dv4s 5.03. I flashed both of them and they were recognized as dv4’s.
Haha well that’s not exactly what I’m going for, I’m just having a hard time because my level of understanding of all of this is so low compared to all you guys.
lmao sorry my mind works in gifs…
2 Likes
You got the steps. Put the ball in play and get to updating youngin
2 Likes
Unless you have a specific reason for doing so I wouldn’t use firmwares from a specific manufacturer’s website that isn’t the manufacturer of the thing you’re using. Putting the firmware for a different ESC on your ESC can cause things to break.
Also, I’ve only had significant problems with updating firmware once or twice, and a cheap st-link v2 off amazon was by far the easiest solution for me at that point. IIRC before a certain version to update through VESC Tool you need to load a new bootloader before updating firmware, but if you already have the bootloader and try to do it again or try to update before updating the bootloader it messes things up. At that point, or really at an point, you can rewrite the whole thing with an ST-Link for whatever version you want, and it should just work. I’ve only done it a couple times, though.
1 Like
I might try that. I’m only using makerx’s firmware because I don’t think I can find enertion firmware anywhere.
Most firmware is in the default VESC Tool itself. The Focbox unity is the one labelled unity. The older singles just use the default 410/411/412 firmware I think, but I’d definitely double check because I’m not 100% on that. Trying to put a different firmware is far more likely to break your ESC, especially if you run motor detection or anything, than to fix anything.
Edit: It looks like you’re using the singles, which like I said should be using the 410 & 411 & 412 firmware AFAIK.
1 Like
???
Why are you flashing firmware from different types of vescs?!
Og focbox are 410/411/412!!
1 Like
Yeah I am using OG focbox’s, yep they are 410/411/412, but vesc tool says that firmware is tool old to do anything, maybe older version of vesc tool with same old firmware? or ackmaniac?
I guess I misunderstood. @CarelessAquarist had said to use makerx firmware, because there was no other in vesc tool and I didn’t know where else to look, I flashed them with that firmware. I would just use OG firmware but it says it’s too old to run detection or anything.
Did you do what i asked you to do?
2 Likes
I haven’t had the chance too try it, but what firmware should I use if not makerx? I know i’ll change to a older vesc tool, but what firmware?
That is the firmware (and hardware revision)
Those come stock and preloaded in every vesc tool
You mentioned you flashed dv4s 5.03 firmware, if so try a normal/recent vesc tool and flash the stock 410/411/412 firmware so you’re on the latest version since you seem to have done the big firmware jump already (from very old to recent)
Remember the precompiled vesc tool archive if you ever need a different version
The recent vesc tools do have a firmware archive pre installed but sometimes the dedicated tool works better in my experience.
1 Like
As a beginner who bricked some old VESCs trying to update firmware (Trampa v6 MKI in my case) - direct SWD with an St-Link programmer was the way to go to bring them back.
Unfortunately the Enertions look like they don’t have an actual SWD port, just the connections on the board, so that’s a bit annoying but not too bad.
1 Like
So the plan is to download the newest vesc tool and then flash back down to 410/411/412. I just feel like it might say “the current firmware is too old to work with this version of vesc tool” because that is what it said when I first successfully connected it to the tool.