Either do a screenrecord or move your phone close to the monitor instead of zooming in from all the way back.
Maybe even record how you flash the firmware. We need infos of what is happening
2 Likes
Here
Thatâs useless because your poking in the archive again.
Stop
Using
The
Archive
If you need to film your screen with your phone make sure to film in landscape
3 Likes
I donât understand. How else can I download 410/411/412?
Just wanted to leave here
flipsky beta value :3455
radium beta value: 3950
I canât find them anywhere on the forum.
I think you can download the vesc tool-firmware bundle from here Precompiled VESC Tool Archive
3 Likes
What do you mean by download? You donât need to download anything other than vesc tool. If you mean upload it to the esc, you literally do exactly what is shown in xsynaticâs image with the arrows. You:
- Open vesc tool.
- connect the ESC
- Click âfirmwareâ
- If not already on âincluded filesâ, click âincluded filesâ. I think you should be there by default.
- Click â410 & 411 & 412â
- Click âVESC_default.binâ if itâs not already selected, but it probably will be.
- Click the upload/write button, which, for whatever reason, has an arrow pointing down.
That is literally all you need to do.
Also, Iâll be kind of surprised if it works at this point. I would expect it to have catastrophically failed already since youâve tried to run it already with the wrong firmware. You couldnât do much more to try to break it if you were literally trying. It seems like it hasnât failed catastrophically yet somehow, though.
7 Likes
The 410/411/412 doesnât show up in the included firmware tab, no firmware does. I am going to this reinstall Vesc tool and see if that changes anything.
In the firmware tab, try checking the âshow non-default firmwareâ box
2 Likes
Are you on âincluded filesâ because in your previous videos, it didnât look like you were? Itâs hard to tell what is going on, though. A single screenshot would have been more useful.
2 Likes
this is no joke.
1 Like
Iâm curious how risky this really is. I would think it would be more runtime failure from things like abs max current set too high or something.
I think the per hw firmware is mostly just hw max for the various limits?
things I wouldnât expect to blow up on detection?
or are there things like different features enabled in the hw config that might cause somethign to blow up on detection?
but Iâm mostly guessing. would be interesting to understand more.
2 Likes
Continuing the discussion from Beginner Question Thread! 2023 Edition:
the focbox unity was the first of those⌠it had a forked firmware. that was different.
Then @Deodand worked with Vedder and got changes into the upstream code that does indeed treat the two sides of a single mcu dual board as two vescs over can. even tho they arenât quite.
so yeah itâs the case for single mcu ones.
1 Like
And for things like hardware values (shunt resistance, adc voltage divider), what is the gate drive circuitry, etc.
If by chance the two ESCs are fairly similarly built it might survive on wrong firmware, but the chances of blowing things up are really high, especially if you donât know what you are doing. And even if it seems to work at detection things might terribly once actually spinning the motor⌠Especially at higher speeds and currents
3 Likes
Anybody understand this problem?
Seems to be set to the right settings, but the bms thinks the cells are overvolted even though they clearly are not, they are pretty much dead; so the pack wonât charge.
Whatâs that app?
âxioxiangbmsâ. i feel like it an overkill solar come from the same code base, theyâre so similar.
thereâs 4 apps. 2 have all the settings access. overkill solar, and xiaoxiangbms. and 2 are like BMS lite apps, and i forget them 'cause i deleted them.
1 Like
I like it when the @xsynatic is so riled up heâs forcefully helping. 
6 Likes
