Actually we have a converted VW T5 with different non OI components. Now we're in the process to add an OI mainboard to get rid of the original ECU with the side effect of getting back some original functionality. So far so good. One of the projects this year will be to add OI CCS and maybe to do an inverter swap from 3rd party to Tesla.
My question is, how will be the communication to all these OI boards? Is there one master board which communicates to the other boards or is it necessary to contact every board by it's own?
Multiple OI Boards Communication
-
tom91
- Posts: 2391
- Joined: Fri Mar 01, 2019 9:15 pm
- Location: Bristol
- Has thanked: 206 times
- Been thanked: 563 times
-
johu
- Site Admin
- Posts: 6708
- Joined: Thu Nov 08, 2018 10:52 pm
- Location: Kassel/Germany
- Has thanked: 367 times
- Been thanked: 1536 times
- Contact:
Re: Multiple OI Boards Communication
In plain CAN there are no main/sub hierarchies. Some call it a real time data base, as data can be put on there by any node and read by any node.
So if you want OI CCS to receive a current setpoint from OI VCU you have to make sure the VCU transmits and the CCS receives on the same channel (haha, like radios back in the day). "Channel" is COB Id, position and length in message and data format (e.g. offset or gain, little endian/big endian).
CANOpen on the other hand is more main/sub oriented. Traditionally the ESP32 is considered main node as it requests and receives specific data items from all other nodes.
So if you want OI CCS to receive a current setpoint from OI VCU you have to make sure the VCU transmits and the CCS receives on the same channel (haha, like radios back in the day). "Channel" is COB Id, position and length in message and data format (e.g. offset or gain, little endian/big endian).
CANOpen on the other hand is more main/sub oriented. Traditionally the ESP32 is considered main node as it requests and receives specific data items from all other nodes.
Support R/D and forum on Patreon: https://patreon.com/openinverter - Subscribe on odysee: https://odysee.com/@openinverter:9
-
bewo
- Posts: 20
- Joined: Sun Jan 14, 2024 9:06 pm
- Location: Germany NRW
- Has thanked: 1 time
- Been thanked: 3 times
Re: Multiple OI Boards Communication
Ok, thanks for the answers.
@tom91: First of all the plan is to combine the OI mainboard V3 and the OI CCS controller.
I hope I understand it right. The goal is to bring all new EV hardware like mainboard, CCS, BMS.... to the drive train can bus. Beforehand I have to be sure, that there are no duplicate CAN messages in the bus otherwise I have other problems.
Now if I use the ESP32 CAN interface, which is connected to the drive train CAN bus as well, this interface organize the communication to all other OI boards, right?
@tom91: First of all the plan is to combine the OI mainboard V3 and the OI CCS controller.
I hope I understand it right. The goal is to bring all new EV hardware like mainboard, CCS, BMS.... to the drive train can bus. Beforehand I have to be sure, that there are no duplicate CAN messages in the bus otherwise I have other problems.
Now if I use the ESP32 CAN interface, which is connected to the drive train CAN bus as well, this interface organize the communication to all other OI boards, right?