OBDII PIDs from CAN ID 2026 (0x7EA)

Discussion and research on OBDII integration, especially on OEM specific PIDs from Ford, GM, Chevrolet, BMW, Porsche, Audi, Toyota, Volkswagen, Mazda, Honda, Subaru, Mitsubishi and others.
Post Reply
EricZ
Posts: 3
Joined: Fri Sep 11, 2020 3:25 pm

OBDII PIDs from CAN ID 2026 (0x7EA)

Post by EricZ »

I've encountered issues accessing PIDs 8 and 9 on my 2008 Audi RS4 using my RaceCapture MK2 Track and the built in OBD channel setup. I have no issues with any PIDs that use CAN ID 2024.

On my Audi, I have confirmed the OBDII CAN messaging using Ross-Tech VCDS for the following channels:
PID 6: Long Term Fuel Trim Bank 1, Request uses Message ID 215 and the response uses Message ID 2024 only
PID 7: Short Term Fuel Trim Bank 1, Request uses Message ID 215 and the response uses Message ID 2024 only
PID 8: Long Term Fuel Trim Bank 2, Request uses Message ID 215 and the response uses Message ID 2026 only
PID 9: Short Term Fuel Trim Bank 2, Request uses Message ID 215 and the response uses Message ID 2026 only

RaceCapture will read PIDs 6 and 7 just fine along with any other PID that I have setup using Message ID 2024. As soon as I add a PID that uses Message ID 2026, RaceCapture does not work with these PIDs, but it also stops working with PIDs 6 and 7. It will continue to read other PIDs, such as 5 (Coolant temp), 12 (Engine speed), 16 (MAF), etc.

I have been able to direct CAN map all other data I need from the car, except MAF, STFT + LTFT for both banks as those are not available on the bus without requesting them either thru OBD PIDs or thru the proprietary Audi PID request method. I would much prefer to use the OBD PIDs for these parameters.

Any ideas on what to check or how to resolve?

aUzer
Posts: 11
Joined: Mon May 18, 2020 8:19 am

Re: OBDII PIDs from CAN ID 2026 (0x7EA)

Post by aUzer »

See the following post:
viewtopic.php?f=33&t=6288

Spoiler alert ... for non-extended PIDs, use mask 2031 to allow response from all possible controllers (I've suggested that this should be RC's default).

EricZ
Posts: 3
Joined: Fri Sep 11, 2020 3:25 pm

Re: OBDII PIDs from CAN ID 2026 (0x7EA)

Post by EricZ »

Thanks for the response! I read thru your linked post and I follow the logic, but its strange that the OBDII channel setup does not work with a 2026 Message ID when 2026 is entered in the CAN ID field?!?!

I tried setting the CAN ID to 2024 and Mask to 2031. This still works fine for 2024 messages, but does not work correctly when any 2026 messages are on the bus. See my screenshots below:

Settings for OBD PIDs 6, 7, 8 and 9:

Image

RaceCapture Screenshots below are CAN traffic filtered for Message IDs 2015, 2024 and 2026.

Enabled OBDII PIDs 6 and 7 with 2024 CAN IDs using the built in OBDII functions (GOOD):

Image

Corresponding OBD PID 6 & 7 request & receive from my VCDS tool (GOOD):

Image

Enabled OBDII PIDs 8 and 9 with 2026 CAN IDs using the built in OBDII functions (BAD):

Image

Corresponding OBD PID 8 & 9 request and receive from my VCDS tool (GOOD):

Image

Even though the PID 8 response is shown in the serial monitor, the RaceCapture Gauges do not display anything other than 0. The PID 9 response is never shown. Also, the unit seems to be unnecessarily flipping back and forth between standard format and extended format.

Post Reply