I have an opportunity to start Tesla Cybertruck (Cyberbeast model) decoding soon with focus on BMS. I got a very contradictory information if the CyberTruck has CANbus at all.
Wiki says:
But also I found following opposite info in a different forum:The Cybertruck uses a central, bi-directional gigabit Etherloop network with CAN bus satellite networks to operate vehicle systems. The result is that data travels over the same network, as opposed to traditional CAN bus systems which require individual connections, reducing the amount of wiring in the vehicle. Audio travels over the same network, eliminating the need for audio-specific wiring. For comparison, while the number of endpoints increased 50% over the Model 3, the amount of cross-vehicle wiring was reduced by two-thirds.
And:Unless things have changed, Tesla doesn't use the OBDII port for data/diagnostics. Also, the vehicle communication network doesn't use a traditional CAN bus so you would need an ethernet device to interface with the network to even start to attempt to decode network traffic. After that, it might be technically possible, but you would probably run into some kind of end-to-end message security that would prevent any tampering of message modifications. So in short, technically within the realm of possibility, but difficult for any normal user.
Okay so it looks like newer Teslas do have an OBD port, but it's located in the center console rather than in the standard driver well location. These devices work by putting appropriate CAN messages/signals on the bus for the desired functionality. Say you want to open the glove box with one of these devices. Instead of hitting the glove box button, which is programmed to send put a signal on the bus to actuate the glovebox lock mechanism, this programmable button would send that signal, mimicking the built-in functionality.
The communication network on the Cybertruck is not CANbus based, but rather automotive ethernet based. Payload data could be similar/same from an ECU perspective, but rather than using CAN standards of communications, it's using IPs and MAC addresses. I haven't read, or there hasn't been a lot of details on exactly how Tesla is implementing it's ethernet communications, but it has been mentioned that it's a ring network (pathing redundancies) with zonal controllers. Again, you would need an ethernet interface device to rx/tx into the network, and all the relevant information regarding the rear and front steering messaging because not only would you have to emulate it, you would also have to prevent "normal" operation messages from rx/tx ing to and from those systems. Those types of messages are constantly being sent by their respective software stacks and sensors at very high frequencies. So from a non-Tesla implementation standpoint, in the realm of possibilities (in a lab) probably technically possible, but I would be impressed by any single engineer working out of their garage that could make the Cybertruck Crabwalk.
Seems that it makes no sense to start with OBD2 requests and probably I have to connect to wires with CAN-crocodile and read all messages flow. Also Cybertruck has a ring-topology wires which means I could find a correct pair of CAN-H/CAN-L wires at any ECU.
Another problem I noticed is that Cybertruck wires voltage is 48V, not 12V, and in theory it meant that any OBD loggers connected to OBD2 port will be damaged and broken. Link to news.
Based on that, I suggest to discuss following:
1. Is the Cybertruck really has no CANbus?
2. Is OBD2 port voltage supposed to be 48V as well as ethernet cabling?
3. If it has no CANbus (or not all needed signals in CANbus), does it make sense try to sniff ethernet traffic to decode it like CANbus? Any ideas/recommendations/concerns on that?