Hi!

Canbus frames are mostly manufacturer specific and the plugin can record them so a DBC file can be made or adjusted. You will need to know what each frame id is (without the manufacturers aid, this has to be manually worked out most times)

DBC files for toyotas are on: https://github.com/commaai/opendbc which can then be directly imported into the extrended PID editor (in the settings) - the DBC file itself is text and will give you a good idea what the canbus frames contain

Thanks, I realized this. But wanted the rules for dissection of frame (where is the pid and where is the payload), so I can try to figure out which frame provides the gear position.

According to the docs I read the frame starts with a few bytes indicating pid then length of data bytes then a crc.

However, what I see above is inconsistent with this rule.

Hi!

These are not MID/PIDs, they are can frames which are broadcast frames at a set rate on the vehicle bus - they bear no relation to mode 21, 22, or 01 PID requests

The can frame starts with the frame id (the first part of the frame) then the payload after that and are usually 8 bytes or shorter in length.

There is no 'rule' for it as such as the data is usually crammed into the frame as bits, bytes, etc - this is why DBC files usually work at the bit level

HI,

Thanks for this.. So I guess sniffing this is not the right path.

Hi!

It's probably more useful to use the PID scanner part of the plugin and let it trundle through some more 21 and 22 PIDs (then you will have a list, with data which is likely what you want that you can export)

Then it's a case of either monitoring that PID for changes (open door, close door, look for a change kind of thing) or finding the relevant documentation from the manufacturer (if you have access to that)

HI Ian,

Thanks much. I will post my findings (if any) on the forum. Would be nice to have a sticky thread for each brand so we could collectively publish our findings in one place..