if you open the vesc tool after one hour, do you load the settings which where written on the vesc before, or just contiune with the stock default settings?
try this:
write your settings how you want them to be
download all settings to the vesc
switch off everything
close vesc tool
wait one hour (important 
jk)
switch on the vesc
open the vesc tool
connect vesc tool to your vesc
on the right side, push the button read motor settings
than
on the right side, push the button read ppm settings
now look what settings are displayed in the vesc tool.
1 Like
will do
I have been following your wobbly progression through this and the other forum and have come to a conclusion. You have no idea how to communicate. Not a clue. For example.
The first post was a description of a problem with your vesc6. In that post you tagged @Trampa not once but twice. This causes the impression that you want Frank to answer your question and solve your problem. Why a thread then? A thread brings down the forum on you.
Why not a pm? Hey Frank this is happening. How do I fix it?
Frank wouldn’t mind. Hes helpful and then you wouldn’t keep getting hammered at every turn. Before you decide to open a new thread for every little thing, think first and examine how or indeed who you would like to help you and then post accordingly.
6 Likes
VESC SIX Plus or VESC SIX?
Frank
1 Like
one of each
the 6 is fine
the 6 plus isnt
VESC 6 PLUS should only run with original VESC-Tool FW.
Best thing to do: Re-Program it via SWD Prog. Use the working VESC 6 to flash the non working VESC.
Interconnect both SWD ports (GND, IO, CLK only), cables not longer than 8cm. Power both units, open SWD Prog tab in VESC-Tool, hit connect, choose VESC 6, hit upload.
1 Like
k will try later
Rip both those VESC’s. It was good knowing you spawn of Benjamin 
3 Likes
why? both are working, he can just flash the firmware the normal way or just read the settings first instead of loading the default settings each time he connect to the vesc…
1 Like
Got the same issue, from the 1st Beta version, it happens sometimes… (luckily it was on my slave)
It happen under different original fw, it could be fine during a year, and them, blop, nothing more !
swapping master and slave already done etc …
I have reported this while ago, during the testing of the beta, but never get an answer to this!
Following!
PS : never happen with my ESCape yet 
or other VESC4.12
2 Likes
SWD PROG erases the entire chip, so that is a good way to make sure you have a clean install.
1 Like
Could simply be a problem with the STM chip. From 100.000 chips there are probably x with an issue.
Never mind trying to do it now
Keeps just coming up with error “erase timed out”
Seams like a software issue. You can connect two more cables: RST on SWD port and GND on COMM Port.
Short before flashing, you interconnect the loose cable ends shortly. This will activate chip reset (RST).
The timing is important, so you might need a few times to figure that out. We could recover a few units with messed FW in the past, using this method. If you have no luck, send us a mail to sort you out.
Also not: The SWD to SWD cable needs to be as short as possible. Max 8cm long.
Not really sure what you mean by
Additionally to interconnecting IO, CLK, GND of both VESCs,
you connect two cables (to RST and GND). This allows you reset the chip on the bad VESC.
Let the cable ends touch each other for a second (shortening RST with GND). You do that just a fraction of time before you press upload in the SWD Prog tab.
This way you reset the chip just before uploading new FW.
Ah ok
Tried a couple of times but cant get it to work
Did you try my suggestion as well?