If anyone can help I appreciate it.
Thanks.
are you looking this db? https://github.com/dalathegreat/leaf_can_bus_messages
this db is pretty confusing and not helpful, since its not really clear what is the msgID in the OBDII request you can send to the car or what is the msgID in the response you get. I just needed to know how the OBDII frame is divided, eg. when you send the request 0210C0 to the LEAF, what does 02 means, 10, etc.ginetto wrote: ↑Thu Nov 19, 2020 1:57 pmare you looking this db? https://github.com/dalathegreat/leaf_can_bus_messages
If you look up the message id in the .dbc file it will show how the frame for that message is divided and encoded? or are you referring to something higher level like UDS?pottorf wrote:I just needed to know how the OBDII frame is divided,
Yeah, I checked their implementation and the only thing I want to know is where did they get those PID numbers, for VIN, QC, starting at line 54.Dala wrote: ↑Fri Nov 27, 2020 1:48 amManually decrypting it is your only option. Check how OVMS has done their implementation on active polling https://github.com/openvehicles/Open-Ve ... anleaf.cpp
No clue. You could take a CAN-dump with an OBD2 adapter connected running Leafspy. That way you would also get the PIDs for different functions.pottorf wrote: ↑Fri Nov 27, 2020 9:29 amYeah, I checked their implementation and the only thing I want to know is where did they get those PID numbers, for VIN, QC, starting at line 54.Dala wrote: ↑Fri Nov 27, 2020 1:48 amManually decrypting it is your only option. Check how OVMS has done their implementation on active polling https://github.com/openvehicles/Open-Ve ... anleaf.cpp
Hi Dala! I loved your 'very boring' videoDala wrote: ↑Wed Nov 18, 2020 5:52 amI recently did some reverse engineering on the ZE1 EV-CAN, made a very boring youtube video on the process. I don't recommend you watch this one.
https://www.youtube.com/watch?v=ty1VYmNWXFc