Archived: the OG noob question thread! 😀

[mikEEE]

for you… my best

[mikEEE]

some nigg has got to know my awnsr ( tryna get some one this pandemic antion before its done)

[Nexo]

I am trying to flash FW on my red-blinking FOCBOX (DRV fault when motor detection was started), I planned to load 4.2 FW

I can see now, that upload is going but it will take ages, it is slooowly moving in 0.1% steps, took 15mins to get to 10%

any ideas about that?

[xsynatic]

from what FW are you coming?

[Nexo]

vesc tool says… FW 3.103

[xsynatic]

Got it.

@xsynatic

Jumping from Ack 3.103 to 4.1 takes that long, even for me.

If you jump from Ack 3.103 to 3.66 for example it takes seconds and then from 3.66 to 4.1 it also takes just seconds like it should. But 3.103 to 4.1 takes literally hours.

Get yourself an older version of the vesc tool and flash that first. Then go from there to the latest fw or whatever you want to use.

Precompiled VESC Tool Archive

Since each build of the VESC Tool is compatible with only a few particular versions of the VESC Firmware, every now and then we find ourselves searching around for a place to download a precompiled executable of one of the older versions. When faced with this situation you either have to find it by googling, ask around on the forum, or download the source code and compile it yourself. All of these take time and can turn a simple task into a real pain. To remedy this, we have decided to crowdsour…

[Nexo]

heard about it, I started from vesc 1.25 and FW 3.62, went quite good, took few seconds, but it is still showing this FW 3.103 and upload takes forever now

[xsynatic]

can you upload a pic showing your firmware tab?

[Nexo]

[xsynatic]

so you are still using the 4.2FW tool?

If you abort the upload seen in the picture, disconnect and use the 1.25 tool and try it again, does it work or does it also take forever?

[Nexo]

when I am using 1.25 update is going really well and it says that update was succesful but vesc tool says FW 3.103 anyway. I am a bit confused. It seems like even after update that FW 3.103 remains untouched

[xsynatic]

does the vesc tool disconnect from the vesc after the update is done? (windows should make the disconnect sound)

after the update you restarted the board?

[Nexo]

i can not remember if it did “that” sound
i waited like 15sec then i did manual reset of vesc
no effect

[mutantbass]

what snacks? I might be able to help you

[xsynatic]

I’m looking for these chips. I just found them a few weeks ago but now Lays has removed it completely from the German market. Lays sold me that Poland still carries them.

[Nexo]

double checked: it is not making any sound, so it is not rebooting (disconnecting)

[kadeanderson]

Rundown real quick:
Exactly as followed…

Ran motor detection on main vesc
Ran app configuration on both vesc

Forgot to run motor detection on slave vesc
Went back and ran motor detection on slave

Are we good to go?

[mutantbass]

how many packets?

[xsynatic]

jk

depends on the shipping cost i’d say.

[xsynatic]

Sounds like a bent shaft doesn’t it?

sound disappears at higher speed