Autosport Labs

Looking for some help getting basic SAE PIDs up.

I recently purchased a used RaceCapture\Track, basically so I could start playing around with RaceCapture and decide if I wanted to put a RaceCapture Pro in my project 01 Acura ITR.

Since my ITR is still a bare shell I wanted to test the unit on my 2010 Acura TSX but the unit came with the Legacy OBD2 cable, no big deal I ordered the updated CAN cable. Once that came it I hooked everything up again in the TSX and tried to pull some basic data (RPM). After several attempts I couldn't get anything out of it (aside from built in gps\accel\etc). I figure the was faulty and set it aside.

Black Friday deals come up I see 15%off on RCP and decided to pull the trigger. RCP arrived, pull it out connect it to the TSX same thing. w/ CAN @ 500hz I get an amber light on the RCP showing CAN is connected. Import the OBD2 mapping for RPM, nothing, log set to trace just shows the PID timing out. Also tried to set the 06 s2000 direct can mappings to see if that would pull any thing and get basically the same thing but CAN timeout.

The only thing I've managed to do is freak out the Dash in the TSX and set off every warning. I've also tried connecting (racecapture\track) to a friends 2018 Civic EX hatch and got the same timeouts.

I'm guessing I'm not doing something right any suggestions? I'm not sure my math is really up to sniffing out CAN messages via the logging script, it seems like I should at least be able to pull SAE standard PIDs right?

Any help is appreciated.

Thanks,

Still no luck getting rpm.

Found another thread on Honda PIDs and that 29 bit mode is required. I was excited that could be an answer but still seeing the same timeouts in logs.
viewtopic.php?t=4671
This thread also seems to reference a requirement for a different broadcast/ecu value? Unsure how to easily implement in current software.

Also tried rebooting between writing config, doesn’t seem to have any impact.

Ok so I may have found some info. It looks like Honda uses a non-standard request formatted as below:

message.id = 0x18DB33F1;
message.len = 8; // message will always be 8 bytes
message.extended = true;
message.data[0] = 0x02; // 2 bytes of data in message
message.data[1] = 0x01; // Get current data
message.data[2] = pid; // The PID to retrieve (replace with appropriate hex value for the PID)
message.data[3] = 0x09; // Not sure why, but the last 5 bytes need to be set this way
message.data[4] = 0x13;
message.data[5] = 0x00;
message.data[6] = 0x20;
message.data[7] = 0xE0;


https://community.carloop.io/t/handling ... mat/239/21

If I'm correct then it sounds like this isn't something that RCP will support out of the box it would have to be scripted? I guess I'll have to see if I can find an example and test. If anyone has a sample or an idea how to easily implement please let me know.

Found an old firmware post where 29bit seems to have been first introduced which required the CAN ID to be set to 0 but this seems to clear the 29bit flag on the PID settings so I'm guessing this is old information.

When 29bit flag is set I do see the CAN ID setting to 417001744 (0x18DAF110 hex) Which is what I see referenced as the correct ID. I can't tell if the required 5 bytes are also being set or if there's something else that needs to be configured that I'm missing.

Just tried to run the CANlogger script, no luck there either, simply returns No CAN Data.

When CAN channel 1 is set to 500k I do get a lit fast flashing CAN light on the RCP.
If I set CAN to 1M I set off all my dash warnings.
If I set CAN below to 250k or below I only get a solid CAN light on RCP.
Enabling\Disabling CAN Termination doesn't seem to have any impact.

I tested the CAN cable with a multimeter and can see that rj45 to OBD, pin 2 maps to pin 6 pin and 3 to 14 as expected and this matches what the service manual shows for CAN H\L.

Not sure what's next. :S

I went back over the attempt to log the CAN signal. I realized I had the CAN channel value set to 1 (channel 2) when, it should have been 0 (Channel 1).

Adjusted and this time I got some data (shared below, during this time I was alternating between holding the throttle to keep rpm ~2k and letting it drop back to idle).

I'll have to see if there's a primer somewhere on trying to decode some of this and try to figure out what I'm seeing now that I know I'm getting data.

Is there a way to timestamp and capture extended logging or would I need to switch to hyperterminal for more flexibility?

Confused that it would be this hard to get even the basic SAE data that other "scanners" seem to pick up with ease (not an attack on the product, I purchased due to diy nature), still worried that I'm missing something basic).

I also realize this is a total aside to my actual project which will be running the Hondata, which seems simpler, better documented then the OEM ECU CAN. But now I'm curious to see if I can get it to read basics from my TSX\newer Honda ECUs.



Log output:
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 1.0,
[476.0]: 2.0, 2.0, 35.0, 20.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 2.0, 35.0, 35.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 1.0,
[476.0]: 2.0, 1.0, 222.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 16.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 222.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 222.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 16.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 222.0, 46.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 47.0,
[476.0]: 2.0, 1.0, 139.0, 8.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 139.0, 23.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 47.0,
[476.0]: 2.0, 1.0, 139.0, 38.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 139.0, 53.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 62.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 16.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 62.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 1.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 77.0, 0.0, 0.0, 30.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 1.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 1.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 16.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 26.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 41.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[476.0]: 2.0, 1.0, 31.0, 56.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[476.0]: 2.0, 1.0, 31.0, 11.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[476.0]: 2.0, 0.0, 0.0, 27.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[476.0]: 2.0, 0.0, 0.0, 42.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[476.0]: 2.0, 0.0, 0.0, 57.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[476.0]: 2.0, 0.0, 0.0, 12.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[476.0]: 2.0, 0.0, 0.0, 27.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[476.0]: 2.0, 0.0, 0.0, 42.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[476.0]: 2.0, 0.0, 0.0, 57.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 77.0, 0.0, 0.0, 45.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[476.0]: 2.0, 0.0, 0.0, 12.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 75.0, 0.0, 0.0, 16.0,
[476.0]: 2.0, 0.0, 0.0, 27.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 61.0,
[476.0]: 2.0, 0.0, 0.0, 42.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 0.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 31.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[356.0]: 0.0, 0.0, 0.0, 88.0, 76.0, 0.0, 0.0, 46.0,
---------------
Switched off
---------------
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,
[476.0]: 0.0, 0.0, 0.0, 59.0,
[476.0]: 0.0, 0.0, 0.0, 14.0,
[476.0]: 0.0, 0.0, 0.0, 29.0,
[476.0]: 0.0, 0.0, 0.0, 44.0,

Starting to actually look at the data (above) something still seems to be pretty wrong.

There's primary ids (based on first byte?) 356 and 476.
Byte values for 356 all show as 0,0,0,88,x,x,x,x

Assuming I'm missing some values (polling only @ 1000, per default) it looks like 356 follows a pretty clear pattern of values, 0, 31, 46, 61 (there are a couple 62 values but otherwise this pattern seems to hold)
476 as well appears to simply cycle through a fixed set of values.
Neither data set seems to provide anything that would reflect real world variance of accelerator\rpm manipulation. :S

May have found a resource to give me some direction in pulling some data (this is more CAN mapping specific now)

https://www.sans.org/reading-room/white ... ring-37825

Looks like a security white paper used a 2011 Civic LX as a test vehicle. Lays down many relevant IDs and even explains why I saw the repeated values on 476 (seems this is a cycle indicating vehicle moving or not)

Will still need to play with formulas but they do seem to have speed and rpm.

I’ll have to pop them in and see what RCP pulls!

Well, this thread might be better moved to CAN Mapping. Though I do want to swing around at some point and see if I can pick up OBD2 from the TSX CAN. My working theory is that it needs a more custom request based on the information I linked earlier.

But on to the good news!
I can confirm Speed on id 344. I believe offset 5, 1 bytes, raw /100, convert kph>mph
RPM is on id 476. I was able to configure as well but initially did improperly to include offset 1, 4 bytes, Raw /65500 where I believe it should be only offset 1, 2 bytes, Raw

I'm going to start trying to validate a number of other items including throttle position(at pedal?), Brake, not sure if this is actually a pressure sensor/pedal position, or simply on / off.

I'm guessing values will be similar for many Honda\Acura cars ~2010.

Ok so now I have: (all are big)
RPM 10Hz 476 1(2) Raw
Speed 10hz 344 4(2) Raw/100 kph>mph
Throttle Pedal Position 10hz 314 1(1) Raw*100/255

I may also have Brake on\off but need to confirm throttle pedal on\off doesn't interfere

Splitting this up to appropriate subforums
CAN specific info will be on a new thread here viewtopic.php?p=29130#29130

I'll share updates on getting OBDII pids on this existing thread.

Ok, I'm pretty sure I've figured out why I'm not able to get OBDII data from my 2010 TSX (probably the '18 Honda Civic I tested too).

When setting up OBDII mapping you can enable 29bit mode on the PID page.
When 29-bit mode is set and saved, the CAN ID changes to 417001744.
In my case however I can see responses actually come back with ids 417001745 and 417001757 (both seem to respond with the same info).

This shouldn't be a major issue since you can change the CAN ID right?

Unfortunately, as soon as you update the CAN ID and save, when you go back and check the PID 29 bit mode is now disabled. (confirmed I don't pick up data).
I saw in one of the past firmware version that an Auto-Detect mode was supposed to work by clearing out the value and setting the CAN ID to 0 but this also seems to disable 29bit mode, at least on the latest firmware 2.14.

Confirmed if I set 417001745 in CAN mapping I get data but I get all OBDII responses on the same Mapping since it's not filtered to the PID.

I'm still trying to figure it out but it does appear I can add a mask without disabling 29bit mode. The first attempt was with a mask of 224 which I'm pretty sure is entirely incorrect (for anything but a ip mask). After a bit more reading I've set 536870904 (1FFFFFF8) and will test that this evening.

If a mask doesn't do the trick I'll try to see if I can lua script a query, capture, and mapping to a virtual channel.


@mods, @Brentp any ideas on how to get the CAN ID updated for 29-bit mode?
Should this be filed as a bug or am I missing something?

Hi, thanks for logging all of your research here.

We've found out that nearly all hondas use 29 bit OBDII, a rarity in the industry.

You *should* be able to just remove all of your OBDII channels, then load the standard OBDII channel preset (essential OBDII channels) and then go into each one and select "29 bit" - that should automatically update the CAN IDs for each channel and it will listen on the extended IDs automatically.

Regarding the CAN log you pasted below - is that from a Hondata system, or data that's broadcasted from your ECU in the background?

We recently did some reverse engineering on a ford Mustang: https://www.autosportlabs.com/reverse-e ... el-speeds/

If that's data being broadcasted from the ECU, you might be able to grab that data instead vs using OBDII - the streaming data is almost always a better option as it does not use the slower "request/reply" behaviour of OBDII.

Right now everything is coming from my primary driver, a 2010 TSX, while I build the ITR (scheduled to go out for paint in a couple weeks). Just getting familiar with the system, and hoping to be able to share some knowledge with others in the Honda Communities I hang out on.

I posted in bug reporting, issues I’m seeing with 29-bit mode. When I log the CAN network I can see 29bit OBD2 responses to the queries, but the preset OBD2 channels won’t pull in the data (29bit mode enabled). It looks like it’s not actually detecting the ID the channel config always shows the same (wrong in this case id) and if I manually correct it disables 29-bit mode.

Hi,

Thanks for the follow up.

What app version and what firmware version are you using when you're testing? Firmware version is reported in the upper right when it is connected.