You are here

Two Vesc6 MKV twin arrays ESC's - BMS CAN BUS connectivity

4 posts / 0 new
Last post
Spaceman
Spaceman's picture
Offline
Last seen: 5 days 6 hours ago
VESC BronzeVESC Free
Joined: 2022-03-03 05:06
Posts: 9
Two Vesc6 MKV twin arrays ESC's - BMS CAN BUS connectivity

Hello all, 

Newly introduced to the VESC project and everything ESC and apologies (due to no search feature in the forum) and if the question has been raised in the past? 

Is there any possibility of connecting a CAN BUS from a BMS into a twin array VESC6 MKV.  As both CAN BUS connections are already utilized by pairing the two ESC's, is there any work around such as a CAN BUS HUB,  recommendations to network the extra BMS CAN.

 

 

 

frank
Offline
Last seen: 2 days 13 hours ago
VESC BronzeVESC FreeVESC GoldVESC OriginalVESC PlatinumVESC Silver
Joined: 2016-12-27 20:19
Posts: 847

Depends on your BMS. The VESC-Can protocol is not a standard CAN or CAN-Open protocol.

Spaceman
Spaceman's picture
Offline
Last seen: 5 days 6 hours ago
VESC BronzeVESC Free
Joined: 2022-03-03 05:06
Posts: 9

Hi Frank,

 Researching into purchasing a BMS 10s > 12s 80amp there about to meet close to the motor 190Kv and ESC specifications / discharge current, asking the question before buying something not compatible.

Any recommendations on a BMS that will communicate with the VESC battery management system?   Hardware product request for the future that can be listed for purchase from VESC website.  Happy to purchase the HD60T if that simplify things for CAN BUS connection. 

Aware there are smart BMS units already on the market, Although it is a very neat software feature implemented in the VESC to monitor and calculate the whole system. 

Reading further into the threads after noting your reference that the CAN BUS is not a standard protocol - CANBUS communication documentation, CAN bus protocol upgrade thoughts, and VESC BMS Hardware Reference Design. 

Closest references I think to a compatible BMS unit is the maxkgo BMSMINI12 based around a LTC6811 and STM32 MCU. Is this correct and will it require a firmware code plug uploaded to talk with the VESC and a HD60T to simplify the CAN BUS connection.

I know it can be simplified with a basic BMS but want to go the extra effort for regenerative braking control, monitoring, and cut of protection if this is something the VESC BMS feature can control ? 

Keep it simple.

Spaceman
Spaceman's picture
Offline
Last seen: 5 days 6 hours ago
VESC BronzeVESC Free
Joined: 2022-03-03 05:06
Posts: 9

Greetings Earthlings, 

 Hopefully this message obtains a reply from out of the void in regards to adding nodes in a CAN BUS network.

Now a little up to speed with 2 wire CAN BUS networks minus the maths.

 https://www.nxp.com/docs/en/supporting-information/AH1021_Application_Hi...

Appears some calculations maybe required for the BUS impedance matching . Noted the VESC hardware has a 220 Ohm resistor between H/L - Schematic DVR8301, Rev 6,  2019 - 10 - 16. 

https://vesc-project.com/sites/default/files/Benjamin%20Posts/VESC_6_mk5...

What configuration is the norm for these VESC ?

Pair of 120 Ohms on each end (Clamp-30/15 network) with matching capacitors to GND 1Mbit/s, or spilt termination concept as our VESC bit rate is only up to 500 Kbit/s that will sample reflection and ringing a lot better?

Is there a PCB impedance matching board on the market this two wire system can terminate inline to easily and neatly connecting our nodes together? 

Or am I looking into it to much? Just join the BMS BUS wires together on to the twin array VESC , 220 ohm is good to go? Not sure what the MAXKGO factory resistance is between the H/L -and take a wild guess being the same impedance matching value resistor in circuit?  

Decided on the MAXKGO 6S-12S 200A Smart BMS instead of the 75 Amp due to the peak load of the two VESC6 in array ( answered my own question in above reply after down loading the MaxkGo-BMS Tool V5.0 - and seeing Vesc Emit status protocal. 

Apologies for the noob question,  

I know nothing about everything  

 

 

 

 

 

 

 

Keep it simple.