so i need to tweak my vesc because im selling my board but i cant get the vesc tool to open.
The first download it opened then i did the mandatory acceptance but once that box closed the vesc tool disapeared from my screen.
it is still opened but window is nowhere on the screen and if i put cursor on it to preview the window it shows just a white screen.
(tried android version, opened on my android but wont connect to usb so im kinda double fucked.)
ive seen other post about the white screen issue but no resolution.
tried uninstalling and reinstall.
tried with antivirus off.
tried opening in admin mode.
updated my entire pc.
did all those steps together.
nothing.
im at a loss and out of tricks. Any one had this issue and resolved it?
where can i get info and instructions?
updated firmawre for first motor and did other things that said once done i could edit things via can–bus for my dul esc (flipsky 6.6 plus) but when i turn on the button CAN it says i must update firmware but once i go into firmware it disconnects and says can’t find usb.
do i need to connect to the usb 2 on my vesc? or am i doing something wrong?
You need to read a lot more before you start changing things.
If you select things that are incompatible, you can break the ESCs.
Ackmaniac firmware is a fork of older Vedder firmware and they are not compatible. Either one works fine. But you need to know what you want first and foremost, then you need to figure out how to accomplish it.
so do i do it for both esc one after the other?
when i used the vesc tool last summer (used it once and now cant figure out how it works lol) i plugged in my usb into slot 1 (the master) and was able to edit everything without having to change usb.
since this an older version type deal do i have to unplug from 1 and plug in 2 to update firmware?
i dont have a firmware choice. it does it automatically.
in the motor setup only 1 motor spun (unlike last summer when both would spin) is that normal? thats if i have to double the entire setup process for both escs even tho its a dual
I am not sure that the suggestion to install an entirely different version of the tool/firmware is the best one to address the issue that the OP is having.
I can open VESC-Tool v2.00/v2.02 without issue, my first guess is it might be something related to your OS itself rather than the software.
PS: Firmware flashing over canbus can have unpredictable results depending on which version youre going to/from. I would suggest flashing each ESC individually if you are currently troubleshooting, introduces less variables. My recommendation would be looking into why 2.03 wont load rather than bandaid fixing it with an entirely different set of software though.
ive tried versions 2.03 down to 1 and they all do the same thing.
i figured it might be because i have a win update but after doing it and restarting pc multiple times nothing changed.
Didnt do shit.
Dont get it. Worked fine last summer and its the same freaken pc.
Window is opened but translucent (which means i cant see it and do shit.) When i put my mouse to preview it its all white.
Back at the AK one, do i have to update my firmware by doing it separately for the dual esc? Do it in plug 1 first (which is done) and do it in plug 2? Since can-bus mode isnt working for some reason.(also only 1 motor spins during motor setup even though i chose the dual esc with master option)
Ack will need to have bootloader/firmware flashed individually on each (plug 1 and plug 2). Read through the tutorial linked above if thats the route you choose to take.
On the other topic: Your PC last summer is not the same PC it is today, because updates happen.
This unfortunately sounds like an issue/corruption with your OS. Which version of windows are you running? Have you confirmed that there is an exception for the vesc-tool program in your Windows Firewall? (this is not the same as antivirus). I am able to load these same versions on Windows 10 with latest updates on my end, and v2.03 is running on my linux laptop.
The official VESC-Tool on android is also an option.
@Deodand think this startup crash could be related to the call-home for version check?
