Anyone figured out where to get the CAN bus data for AIM/etc. data loggers?

[DocWalt]

The connector used on the body harness for the ASC:

https://www.te.com/usa-en/product-1318386-1.html

Here's the list of wire-to-wire connectors that are compatible (note you'll need to buy the right pins)

https://www.te.com/usa-en/product-CA...ible=1318386-1

[DocWalt]

Constant B12 works, and the IGN wire is +12 when ignition is on (not in ACC, it seems)

[timurrrr]

Originally Posted by DocWalt

*none* of the old CAN IDs work.

LMAO

Originally Posted by DocWalt

I'll document things on a spreadsheet, feel free to move things to your page, I have no issues with that at all

Thank you so much! I'll do that once I get my own 2022 car and verify them.
I'll also do my best to find out the IDs and encoding for other channels I'm interested in.

[DocWalt]

Parts list for the ASC connector/patch harness:

Male connector (plugs into factory harness):
- AMP/TE Connectivity Connector Housing P/N: 1376106-1 (Quantity 1)
- AMP/TE Connectivity Pins P/N: 1376109-1 (Quantity 8) - I'd suggest ordering a couple of spares though in case you mess up crimping

Female connector (same as factory harness if you're making a patch)
- AMP/TE Connectivity Connector Housing P/N: 1318386-1 (Quantity 1)
- AMP/TE Connectivity Pins P/N: 1123343-1 (Quantity 8) - I'd suggest ordering a couple of spares though in case you mess up crimping

I used this wire: https://www.amazon.com/gp/product/B0...0?ie=UTF8&th=1

I used this RJ45 breakout (for RaceCapture Track Mk2, you'll use something else for other devices): https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

Use something like this to crimp the connectors. It's fiddly and annoying but way cheaper than the "right" tool: https://www.amazon.com/Qibaok-Termin.../dp/B089LW7MWT

If you're wiring to a breakout like I was, this will work to make the ferrules on the wires. Way nicer to insert than stranded wire twisted together or whatever: https://www.amazon.com/TICONN-Insula...dp/B09F94TPRV/

My patch harness (made a second for a friend that I owe a favor to):



My RaceCapture "install" after I routed the RJ45 cable along the passenger side rocker under the carpet, down in front of the seat, and out the flap that exposes the chassis VIN.



Data into SoloStorm!



Matching temps on the dash for comparison:

[timurrrr]

Awesome, thank you so much @DocWalt!

Now if anyone can find an easier way, like that hidden connector behind the head unit that some of us used on the 1st gen...

[DocWalt]

Originally Posted by timurrrr

Awesome, thank you so much @DocWalt!

Now if anyone can find an easier way, like that hidden connector behind the head unit that some of us used on the 1st gen...

It doesn't get much easier to access than the ASC connector. Taking the radio out on a Gen 2 is "tear the entire damn dash apart" soooo.....

[timurrrr]

Since I've figured out the most relevant parts of the CAN bus logging (not without @DocWalt's help!), I decided to document them on my various GitHubs.

Connections:
https://github.com/timurrrr/ft86/blo...an_bus/gen2.md
[will also have more data on various CAN IDs in the future]

IDs and equations for the most useful data channels:
https://github.com/timurrrr/RaceChro...b/ft86_gen2.md

How to make a DIY CAN bus reader if you don't want to spend $$$ on an AIM:
https://github.com/timurrrr/RaceChronoDiyBleDevice
[The project is being actively updated with 2022 specific tweaks.]

Demo:

[DocWalt]

Thanks for taking it and running! Glad to help get the ball rolling with some of my local friends helping out
If RaceCapture ever gets little-endian data working properly I can keep helping sniff data out!

[andys_garage]

Originally Posted by timurrrr

Since I've figured out the most relevant parts of the CAN bus logging (not without @DocWalt's help!), I decided to document them on my various GitHubs.

IDs and equations for the most useful data channels:
https://github.com/timurrrr/RaceChro...b/ft86_gen2.md

Really appreciate the instructions here, and I look forward to making one of these for myself.


I saw in the config you limited some channels to 25 Hz. Is there a risk of saturating the bluetooth connection? (also asked this on github) I think 100Hz swa, throttle pedal/valve, wheel speeds, brake pressure would be interesting to explore

[DocWalt]

Originally Posted by DocWalt

Thanks for taking it and running! Glad to help get the ball rolling with some of my local friends helping out
If RaceCapture ever gets little-endian data working properly I can keep helping sniff data out!

RaceCapture guys got me a beta firmware with little-endian working properly, so I can get back to work on this after nationals

[geraldjust]

Originally Posted by timurrrr

Awesome, thank you so much @DocWalt!

Now if anyone can find an easier way, like that hidden connector behind the head unit that some of us used on the 1st gen...

Just saw this sorry. But yes! the connector in the back is on Toyotas at-least. I see it on toyotas schematics but but on subarus. But both cars should have it. its a little weird though, that connector connects to the Telematics unit and the head unit, into the Gateway ECU. But its not directly connected to the Body network, or the Primary network either. But doing a ton of testing that i know some data filters from Body Network-> to this network. So you might be able to pick up some data there.

[timurrrr]

Originally Posted by andys_garage

Really appreciate the instructions here, and I look forward to making one of these for myself.


I saw in the config you limited some channels to 25 Hz. Is there a risk of saturating the bluetooth connection? (also asked this on github) I think 100Hz swa, throttle pedal/valve, wheel speeds, brake pressure would be interesting to explore

Replied on https://github.com/timurrrr/RaceChro...evice/issues/9 so that it can be found easier by other DIYers.