The OBD-II port (less commonly know as DLC - Data Link Connector), will have pins 6 and 14 sending regular OBD-II signals upon request. If you still want to hack your car’s CAN bus and you are not seeing messages, this reference will help you find it on quite a few makes and models and easily accessible CAN bus locations: http://www.jablotron.com/files/canbus/mcb-02_en.pdf
1 Like
Many OEMs are firewalling and/or removing other CAN access from the OBDII connector. Only OBD/UDS functions will be available. Write functions may well require authentication of sorts (and the right tools).
This is going to take a long while to kick in. Firewall is pretty pointless on the current configurations, as there are too many places to jack into. They will need to replace or encrypt the can bus itself, which would take years to agree on a standard. It would have a huge knock on effect on the after-care for vehicles and after market parts. Theres always going to be certain areas that the have to leave open on the OBD side also, for example emissions and diagnostics data otherwise half the world would grind to a hault. Its a interesting problem, id expect to see alot of core engine ECU’s go encrypted perhaps with a ECU dedicated to OBD / Diagnostics though a firewalled type of connection. There are some interesting draft proposals kicking about for exactly this. I guess the more we move towards automated driverless machines, the greater the need for locking down the data bus is going to be.
Expect the 9 yards of security to happen, especially for AD vehicles. CAN will go the way of CAN-FD or Automotive Ethernet simply because of the increased data requirements imposed by both the computing and security requirements.
1 Like