wait so you don’t have to buy a wiiceiver if you have a VESC?
No. You can solder the receiver of the nunchuck straight to the vesc.
so are my connections 3 post up, correct?
2 Likes
I am trying to figure out myself. From what I read, these are what I found out. Members with more experience, please confirm.
Pin 1: Green SCL/RX. (closest to motor wires) Pin 2: Blue SDX/TX Pin 3: ADC - Do not use Pin 4: Black GND Pin 5: Red 3.3v Pin 6: 5V -Do not use Pin 7: ADC2 - Do not use (closest to battery wires) @BigAl: We have our pin orders in reverse. I am following the picture you posted. Cheers,
Ok @sgaana and @elkick thanks to both of you for your help.
this is where I stand at the moment.
Firmware 2.5 installed on both VESCs, canbus jumper installed, Nyko receiver installed like the picture above (blue LED blinking) (BTW thanks elkick).
Both VESCs have the blue and green LEDs lit. One of them is also blinking RED.
I’m able to connect using the BLDC Tool, my problem is it doesn’t respond to input from the Nyko.
Thanks for your help Al…
Assuming the Nunchuk receiver is connected to the master VESC, you need to enable it twice: first in the general app tab and second in the side Nunchuk tab. After that, you need to klick “write config” and then “reboot” (reboot is important!).
The blue led on the receiver should stay on when connected with the transmitter, not blinking.
SLAVE VESC needs Controller ID „1“ and „Send Status over CAN“ configured. Nothing else (except motor detection).
MASTER VESC has Controller ID “0”, and app configuration like described. And connected receiver, motor detection done, etc.
@elkick OK, so I now know which is master, it has the Nyko receiver connected to it but the blue LED on the receiver is blinking, is there a way to reset the receiver or some other type of kick start?
Also, whats the deal with the slave VESC flashing red? any ideas?
Thanks Al…
I assume that you connected the can bus with the middle pins only (which would be correct)? Also, just check again that the cables to the Nunchuk receiver are connected in the right way. Powering off/on the VESCs sometimes help to reset things. And always make sure to klick reboot (after “write config”) when changing values.
Ok, I got the receiver to stop blinking, one VESC seems to be responding, the slave does not. YES the canbus is correct. I’ve been at this all day, kinda going crazy!
any idea what the flashing red LED means?
thanks Al…
Did you do the motor detection on the slave VESC? And confirmed that it has ID 1 and “send status over can” enabled?
@elkick yes, those are all done. All of a sudden everything shut off. I don’t know what happened but I suspect the battery just went below the allowable voltage. I had not charged the battery from new. So I have it charging now, hopefully with a full charge everything will turn back on. Assuming it does, I’m going to reflash the firmware on the slave. I read on another post that might be the issue. Thanks again for all of your help!
Al…
@elkick Well the battery is now 100% charged. Neither VESC is turning on. If I look under the VESC there is a red LED that is dimly lit. Anyone have any ideas what I should do next?
Thanks Al…
Correcting my previous post after inputs from @chaka and @elkick.
Pin 1 Do not use
Pin 2: Green SCL/RX. (closest to motor wires)
Pin 3: Blue SDX/TX
Pin 4: Do not use
Pin 5: Black GND
Pin 6: Red 3.3v
Pin 7: Do not use (closest to battery wires)
Hello BigAl
The red led is a fault LED. Have you tried typing faults into the terminal window of the BLDCTool?
Thank you @scoobiext. Just typed “fault” into the terminal window and this is the response “No faults registered since startup”
Al…
I only once had this strange behavior as well, it was related to a power connector not being plugged in strong enough and the VESC didn’t receive enough power (voltage). Also it might be an idea to check the battery for voltage supply at the end where the VESCs are connected: are all those soldering spots ok, connectors ok and all the cells providing the voltage they should?