I got my dual 4.12 flipsky running and when i do motor detection, both motors work fine. Im having issues with my remote only running one of the motors at the end… So i do motor detection on one hub, run input wizard and set it as the master. Everything working great so far.
I then do the other motor, run motor detection and its good. I set it up as the slave and at the very end only one of the two motors spins when i accelerate on the remote… Any help would be appreciated. Im using a nano x with koowheel hubs and using @mmaner settings for the flipsky dual…
can you change settings on the slave when connected to the master via the CAN button in the VESC Tool?
if no, than something wrong with your CAN bus or the settings for the CAN communication.
i don´t have a dual 4.20, but there should be a switch to toggle between dual and single mode.
it´s located in the middle up, close to the capacitors.
make sure the switch is in the left position.
double check that in your vescs the can communication is enabled and that the master is 0 and the slave is 1.
the wizzard should set this up for you usually, but … who knows…
if that´s not working, try to connect them via CAN bus cable if you have one to hand.
if it´s working after, than there is a problem with the internal CAN bus on the PCB probably
There is no can cable port but there is a can switch on it you can turn can on or off by that switch it may be defaulted to off when they send it from the factory.
That’s why I recommended that he should try if he get connection via external can cable.
If that’s the case the switch or the connection on the pcb faulty
Make sure the one set up as a master should have the ppm cable connect to the Nano X receiver. The other one doesn’t come with a cable, so if you set it up as a master, chances are thing won’t work.
Also, make sure the Can bus ID of the slave and master is different. Usually the master is 0, and slave is 1.
Problem solved. Used a canbus and it worked first time… also honestly it could have been my fault as well. I did update one side of the vesc and never updated the other until tonight so it could have been running two different version. Doh! Either way it works now. Thanks for all the help guys