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.