What do you mean by same app parameters? I made sure the master was the master and the slave was the slave.
I’ve reset to factory settings by upgrading the firmware multiple times, tried to reconfigure each alone, and made master control be PPM and UART while the slave PPM should be “off” without any changes
O recently had the same issue, I just didn’t used the newest firmware. I had to check a setting in vesc tool, something like communication for both via can. Worst case you could maybe try split ppm.
@Komamtb I tried several different ones (almost 75% of them) all giving me the same results.
-Do you know what firmaware you ran to get it to work?
-And please can you send me a screenshot of where that communication for both via can would be? because i read on the @Trampa website the instructions specifies to not split the PPM communication to both VESC’s when programming.
Just tried this and pretty sure just broke both of my VESCS…
Now i cant get a motor detection and the VESC is making an exremely loud noise when i press the forward/reverse feature in the VESC tool.
Im pretty sure the VESC tool just fried both of my VESCS. I did everything according to the instructions posted on the vesctool website. this is ridiculous. i dont even want to purchase another vesc because i am afraid if i use this software again the same thing is going to happen. i dont understand why i cant downgrade back to the old vesc tool where this was easier and i dident have to use this “FOC Motor Detection”… it just fried 2 of my perfect vescs
Lol today marks the 4th day ive been up past 3am trying to get this to work
But the LED’s blinking are not in sync when i was doing the detection earlier.
Now i cant even do a motor detection because it says “detection timed out”
I cant even do anything with these vescs anymore besides use them as a paper weight.
This new vesc tool firmware update bricked my vescs. This is great.
Not sure what to do at the moment as there is nothing i can do to get either of my vescs to work now. it is clearly a software issue because everything was working flawless before i did any of this firmware update.
You probably just wrote the standard parameters and deleted the motor detection. Before changing values, press READ configuration first. Then change the value and press WRITE. So try to do the detection again.
If the Wizard doesn’t work there is either a FW issue or a Hardware issue. Your devices are third party ESCs and not genuine VESCs, so I don’t know how reliable CAN works. You can check if you can log into the slave via the master, using CAN forward. If that works, the CAN chip is working.
If CAN is working and you still have trouble, you can set the IDs manually and manually activate CAN forward. You can also do a manual motor detection for each motor. No one forces you to use the Wizard.
Last thing to mention. A lot of third party ESCs don’t have a 60v tolerant CAN chip. These devices need to be powered simultaneously, otherwise the CAN chip blows up in a dual configuration.
Nope, i dident delete the motor detection, i followed the instructions on the vesc tool website step by step as you can see in the video i made above.
3rd party or not, i used these exact dual vescs on this exact same setup using vesctool 0.95 with no issues. this 3rd party vesc is from TB which is a reliable source and i never had any issues with the vescs purchased from there so we can get that part out of the way as the CAN chip functions properly.
As far as firmware issue, ive tried every single FW there is to offer but it wont change anything. I just purchased 2 new TB vescs in the meantime to see if that is the issue with hardware(although it really should not be as everything was working 100% before the software update).
Im not sure how to set the ID’s manually and manually activate CAN forward.
Also i am not sure how to do a manual motor detection with the new vesc tool binding the dual motors and this forum has no information on it either as i tried tirelessly searching for answers. the wizard was much easier before when it would say when to plug in the master and when to plug in the slave. this is extremely difficult with the lack of information on how to use the software, can you please share some details on how to do this? I am extremely worried at this point
Thank you so much! One of my vescs came back to life! I used the Ackmaniac ESC Tool and it was exactly what i was looking for!
Im convinced that during the “FOC motor wizard” on the newest vesc tool software somehow broke my both motor and vesc because now one of my motors (on the same side as the broken vesc) wont spin as freely as it used to as it has some resistance similar to when a motor burns out. As well as my vesc, after setting up using the Ackmaniac ESC Tool one of the vescs had a blinking red LED rather than green. But i know this isnt from using the Ackmaniac Tool, it was from last night when i kept trying to use the FOC motor wizard one of the motor detections made my motor make the weirdest noise like all the magnets came loose or something (not what really happened but you get the idea).
In the mean time, i purchased 2 new vescs and a new motor so i can get back up and running.
Any idea on what the red LED blinking even after motor setup can be mean on the VESC?
Not 100%. What you could do is look in the faults Tab if you see anything (or enter “faults” in the termina) Although i think the vesc clears the faults after a power cycle. Worth a shot.
have you done the shorted phases test yet?
For the RED blinking vesc, can you still connect to it properly?
Just gave it a shot but you are right, the vesc will clear all faults after a power cycle, plus i re-did the firmware update to clear anything and still no luck.
I also plugged the non-working vesc in the working motor, completely redoing the motor setup and app setup as a single vesc system just to test the individual vesc and still the vesc is blinking red LED after i do the motor/app config.
Yes, i have and everything seems good. the motor is actually working, just making a very weird white noise that is not smooth like the other motor and this dident happen until after the FOC motor wizard.
Yes, i can still completely connect to the vesc properly with full success, thats what is confusing me into thinking its not a DRV error (which is usually what happens after running 12S on FOC).
By the way i want to thank all of you so much for helping me out. i really appreciate it so much.
Lol after what i just expierenced with FOC i think im contemplating sitting this one out but i cant resist
im super jealous though i need to figure out how to use the FOC mode witout destroying everything . Once i get my new vesc and motor in the mail from TB i will try FOC again using the Ackmaniac ESC Tool. I’m sure that everything will run smoothly then.
But in the mean time i need to figure out how to connect the VESC Wand using the Ackmaniac ESC Tool, is this possible?
Just noticed your reply. The DRV chip on the VESC was burned out from what I believe to be one of the motor phase wires accidently came apart when riding causing a short.
I replaced the TB VESC with a Flipsky VESC that I found on amazon and everything worked
