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

Rumor is that the AIM data logger can't see any CAN bus data on the OBD-II port.
Given what Subaru has done on other models, my intuition is that now we would need
to find another place to get to the CAN bus, and possibly even splice some cables.
This has already been the norm on many other cars, e.g. Porsches.

Have anyone explored data logging on 2022's yet?
One wild idea I have is that perhaps the connector that goes into the ASC ECU probably has the CAN H/L pins in it.

Also my intuition is that the CAN IDs and encoding for most of the high-level data
should be mostly the same between 2022+ and 2013–2020.

@timurrrr Have you tried the option connector behind the stereo?


I've heard anecdotally that two of the pins are for CAN, but don't what's actually accessible or useful via there

• Edit: wrong generation

I hooked my RaceCapture up last night and loaded the gen1 car preset and got nothing.

https://i.imgur.com/ItyAlDT.jpg

On the automatics, you can tap into the Eyesight camera. Not sure what type of data you'll get out of that though. Assuming they build the manuals similar to the automatic, there might be a hidden Eyesight wire by the rear mirror.

I've been using it on my '17 for a while.
Are you talking about '13–'20's or '22's specifically?

Reminds me of this video I saw before:

Has anyone confirmed that the hidden extra connector is there on 2022's, and it's not just for speakers?

Hooked up to what connector?

btw, if anyone is in the SF Bay Area and is willing to let me fiddle with their car to figure out the CAN bus protocol, let me know!

OBD under the dash

Got it. Referenced the wrong gen

I'll be playing with this on my car as soon as it gets here. I helped sniff the CAN data for the ND, so we'll hopefully get this sorted out too. It would be pretty annoying to not have the CAN data on the OBD2 port, but oh well. Should be available on the ASC connector.

I'm really hoping something just changed in the formulas and we just don't know it yet. Would be really weird I feel to not be able to get them from the OBD and would have no idea how to get that info into my RC and SoloStorm then LOL

Lots of manufacturers don't expose CAN on the OBD2 port, like Honda & BMW. Seems pointless but lots of folks worry way too much about security of the OBD2 port (omg my car is going to be hacked!) and lots of other folks do dumb things and cause issues with cheapo OBD2 dongles so it makes sense for manufacturers to not expose the CAN wiring.


Assuming it's actually on the OBD2 port it'll be figured out fairly quickly for the basics (steering angle, brake pressure, accelerator pedal position, etc. The more complicated stuff like wheel speeds will need more logging than I have time to do.

If it's not on the OBD2 port we'll just need to come up with somewhere to tap into the CAN wiring. ASC just seems like an easy place to do it with a likely readily available connector to plug in instead of ASC.

The following pins on the OBD-II connector are populated: 1, 4, 5, 6, 8, 14, 15, 16.

I'm pretty sure the OBD-II connector has a CAN bus available, since this is the required protocol in the latest revisions of the OBD-II protocol for emissions-related stuff.

However, manufacturers are free to provide a separate CAN bus for the OBD-II port connected to a dedicated ECU with very limited functionality, e.g. only answering emissions-related OBD-II requests. The "main" CAN bus that most other ECUs (engine, ABS, ESC, etc.) are talking over may be "isolated" from the OBD-II port, with that dedicated ECU acting like a gateway.

Sweet! Please keep us posted.
I can add whatever you find to https://github.com/timurrrr/RaceChronoDiyBleDevice then.

Got my car Friday, finally had time to hook up the RaceCapture and poke around. Looks like the new twin is using SSM and we'll need to invest a lot of time to grab the extra data over CAN because you need to send a request to the ECU for the data. I don't have the time at the moment, but maybe over winter. RaceCapture's interfaces for this are... annoying.

What did you plug into? OBD-II port?

Yes. The CAN bus is there, but we just need to use SSM to interact with it which is... annoying at best.

Like this, except I don't have an AP to let me sniff the data...

https://forum.autosportlabs.com/viewtopic.php?t=5936

This might be an interesting lead, but my gut feeling is that plugging in somewhere other than the OBD-II port and listening to data already on the CAN bus will yield better results.
That's definitely something I'll try once I get my 2022.

Yeah, that would definitely be easier and *way* less annoying. When I have time, I'll try to find the right connector to plug into the active sound computer. I'm super busy with work & holiday stuff so not happening soon for me sadly.

Is there any info on the connector, pinout, etc.? Any part numbers?

How is this? Don't know the plug number.

Awesome, thanks!
Wiring diagrams like this usually have a separate image explaining what connector it is, is there anything on this page or earlier/later page explaining what "i121" is?

It's basically just a rectangular looking plug. I'll add the image to the other post later today, when I can get to the file.

Where did you get the wiring details? I'd love to see the full electrical diagram for the gen 2 cars.

I got RPM, TPS, brake pressure, and steering wheel angle from the ASC connector today :)

I'll put together a google sheet with the data when I get a chance. I have a ton more CAN data to test and see what does what, it's going to take me a while to get much more data, I don't have very much time to dedicate to this.


A friend of mine is looking into what connectors to use to make a T harness to keep ASC or just plug directly into the ASC cable. I did a little hacky thing to test, would not recommend haha.

Yeeeees!

Have you tried all CAN IDs from this page?
https://github.com/timurrrr/RaceChro...can_db/ft86.md

Can you please document which ones work and more importantly which ones DON'T work?
If you're familiar with how to work with GitHub, feel free to send me a pull request to add a ft86_gen2.md page to the same directory with whatever details you find.

Very much interested in that too! Is there ACC power pin in that connector?

Look at the diagram I posted above. IG = ACC

*none* of the old CAN IDs work. I'll document things on a spreadsheet, feel free to move things to your page, I have no issues with that at all :)

There seems to be an ACC pin, I haven't investigated that yet as I was powering the RaceCapture from USB (the wiring diagram shows it as mentioned above, but I didn't actually confirm)

https://docs.google.com/spreadsheets...it?usp=sharing

I need to double check a bunch of this data, feel free to play with it on your own time. I'd like people to not make a mess of the spreadsheet, but if you do... it's on you haha

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

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

LMAO :bonk:

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.

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):

https://i.postimg.cc/zf5XSZTb/image.png

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.

https://i.postimg.cc/htnfMdBt/image.png

Data into SoloStorm!

https://i.postimg.cc/y8cghCrc/image.png

Matching temps on the dash for comparison:

https://i.postimg.cc/fbvVFjsb/image.png

Awesome, thank you so much @DocWalt! :bow::bow::bow::bow:

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..... :)

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:
https://www.youtube.com/watch?v=R1ucTVodH9Q

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!

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

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

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.

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