I’ve been tinkering with my ZhiDou D1 and built a simple diagnostic display using an ESP32 microcontroller.
It connects to the car’s CAN bus and displays key parameters like speed, voltage, current, and temperature in real time.
The goal was to make something compact, easy to mount, and affordable — basically a plug-and-play way to keep an eye on what’s going on under the hood.
It should work more or less on the D2 model as well. The only issue is that the page showing individual cell voltages won’t be fully correct in this version—it currently displays only the first 24 cells, while the D2 model has more.
I’ve sent it to someone who has a D2 model, and they’ll be testing it soon.
Currently it works only with D1 model as D2/D2s has different pinout and a bit different can messages for errors.
It is possible to update this diagnostic display for it but it has to be different version created.
Hi vavrkok,
we're working on some kind of web app, that would make it easier for our team of cca 15 people to share our two Zhidou D2 cars without the need of handing over the physical keys. We are looking into the options the CAN bus interface of the car could give us, but any documentation or publicly available information about these cars' CAN bus is very limited. I thought you probably could provide some help to us, as your diagnostic display can read many information from the CAN bus. I know this display is intended for D1, but as you wrote here, the communication in the D2 is similar, at least in some ways.
What data would we like to receive from the bus (not neccesarily all, but the more, the better):
- current car lock status (locked/unlocked), or catching the lock/unlock signals during the change is happening would also be possible
- traction battery information (primarily its charge level (soc) and whether it's currently charging or not)
- odometer and/or trip meter values
- lead gel 12V battery voltage, if possible
If sending data to CAN bus is even safe and a good idea, what we would like to send:
- locking and unlocking the door (this could be bypassed by integrating one of the car keys into the communication module we are developing for the car and electronically triggering the key's buttons)
- zeroing the trip meter (again could by bypassed by disassembly of the instrument cluster display module with the zero button and having a physical connection of our communication module to that button)
Do you have any documentations, websites or any other resources for both the D1 or the D2 you could share with us that we could find helpful? We would be grateful for really anything.
If you have a CAN reading device, try reading the CAN communication and send us a list of addresses and we can compare it with the communication from ZD D1
