The center wire needs to be cut on just one. Leave it on your master vesc, it powers the receiver.
When @onloop says that we need to click the send status over CAN for the slave. Just to make it clear, u need to tick or no tick it? haha sorry for my bad English.
When I cut the slave, red wire, the receiver didn’t get power at all. Maybe I’m doing it the wrong way.
[quote=“chaka, post:43, topic:142”] Leave it on your master vesc, [/quote] Unless you have a ubec/sbec around. The center wire powers the receiver and the power should come from only one source.
haha i dont know about BEC/SBEC. I have 2 VESC and 2.4GHz mini controller.
and this is my BLDC setting for master and slave:
and I am planning to make the VESC on the right my master and left is my slave VESC
What @chaka is saying is that you cut the red wire coming from one of the VESC and leave the other connected. You see, the red wire is what feeds power to the receiver. You only need the power to come from one of the VESC, it doesn’t matter which VESC the power comes from but the receiver should only receive power from one of the VESCs.
Hope that helps. Al…
If you’re using CAN bus in a master/slave configuration, the receiver should only be connected to the master.
First you need to make sure both VESC’s are working properly by connecting each one to the BLDC tool and using the arrow keys on your keyboard to run the motor. Once you’re sure they are both OK, you can set up CAN bus:
- Connect master to BLDC, give the master ID 0, configure the PPM settings (write conf) for your receiver and test to see if your motor runs. Don’t connect the slave to the master yet. Put your transmitter aside.
- Connect the slave to BLDC and give it ID 1 and tick " send status over CAN" - (write conf).
- Disconnect the slave from BLDC.
- Connect both VESC’s with the CAN bus cable.
- Cycle the power on both VESC’s off an on.
- Reconnect the master to BLDC and tick “CAN Fwd” on the upper right of your screen, enter ID 1 To receive data from slave.
- Goto the realtime data tab, tick “activate sampling” and verify there’s data coming back from the slave. You should see the graphs move. If they don’t, there’s no communication.
- Now take your transmitter and pull the trigger to see if both motors spin.
Hope this helps
So according to Raptor board, the dual vesc setup with non-Nyko Kama (or NunChuck) receiver should be like this?
No need to connect both vesc’s receiver side? Then how to know or decide which side is master one?
Another proof which shows only need one side connecting to receiver?!
Correct, If you’re using CANbus, the receiver is connected to the master only. The app for the receiver is configured only in the master. The master takes care of the control of the slave.
Thanks, that means WITH the CANbus setup, the one connected to the receiver becomes the master one?
So is that possible to do a different way on dual Vesc which like old esc setup that “without CANbus then connected both receiver side with the ‘Y’ bridge then take one side’s middle wire out”
Learned those setup from : http://2bfly.com/knowledgebase/electronic-speed-controls/multi-engine-esc-wiring/
you have to program the master and slave in the BLDC tool software.
or you can set them up as 2 individual ESCs and use a Y if you prefer that.
Okay! So there are not big differences, are they? I mean these two setup.
If you use a Y connection You won’t have traction control but I’m pretty sure you wont miss it. You won’t be able to get realtime data from both vescs over the same usb connection either, you’ll need to plug into each vesc separately to look at realtime data. It will make config straightforward though, you can set both vescs up identically.
Very helpful info mate. Thank god I’ve asked those question. Didn’t even know that before. Then now I know what setup I’m going to run in future. Cheers!
I heard that the VESC is open source which raises the questions.
- does the VESC have extra I/O pins available, and if so is there a way to program these pins.
- does anyone have a schematic for the VESC, would like to take a look at the hardware
I have noticed with my dual VESC’s (via canbus) that if I’m on cruise control and I load up one wheel the motor spins up harder to try and overcome the load, but if I load the other wheel it just stops. I have tried turning on and off traction control option and it doesn’t seem to make a difference. its the motor attached to the slave VESC that stops under load.
is there some sort of setting that I’m missing?
found the issue, it looks like it was a faulty canbus cable.