Justin01

Perfect, thank you! I was trying to figure out how to get that level of detail to share with RaceChrono support. I even tried PC ELM to USB adapter with HUD ECU Hacker but couldn't get it to work

So, after some back and forth with RaceChrono support, they are telling me that only 1802 is coming across from the LinkECU, not the other two ID's (1803 or 1837). Which, tracks with what I pasted above in the Test 1, only 1802 is there. I still don't see any data in the app though, which it sounds like I should at least see 1802. I'm not sure why ID's 1803 and 1837 are not being seen though?

Well, I finally got to test it out while driving the car and I still am not getting anything on the RaceChrono side. When I was troubleshooting my other car, we had similar issues and the guys said there was a bug with RaceChrono that did not send an "ack" message when it received a CAN message. Somehow this was overloading RaceChrono and they would then just stop responding. Not sure if that is the same thing going on there or not. I'll take it up with RaceChrono support and see what they say.

I got test with just the key on tonight and it seems to be connected, but not all the data is populating. I will test it with start up tomorrow to get a better idea. Can you configure the CAN parameters to transmit the brake pressure? (or tell me how to do that) I forgot there is a brake position sensor up in the brake booster, I'm hoping the ECU actually see's that. Thanks!

Ok, yea I noticed the CAN port changes. Thanks, I will try to test it out tomorrow and get back to you with the results. Might not be until Friday though, but excited to see if this gets things working.

What parameters did you want to see? I'm not sure if my logging setup has what you want, but they are attached. Let me know if you want a redo. Terminal output of "ATMA" also attached, it looks like more data is coming across with these changes at least. Test1-PC Datalog - 2023-07-24 7;45;33 pm.llgx Test2-PC Datalog - 2023-07-24 7;48;31 pm.llgx

Dang, was hoping I screwed something up Tune is attached. Metz-e36 GJP CAN.pclx

Voltage for 5 & 6 = 3.39v Voltage for 5 & 14 = 1.767v Resistance 6 & 14 (hopefully I did this right?) = 122.9ohm

Per a recommendation from the RaceChrono support forums, I ran a monitor on the OBD device to see what was being sent out. I'm not sure how helpful this is or if I had the right settings in the terminal app, but it looks very different from my BMW Link to my GR86.

Port labeled CAN/RS232 --> OBDLink MX bluetooth adapter (one we're trying to setup) Port labeled CAN2 OBD --> AEM CAN Lambda Edit: I wonder if my tuner setup the AEM on both CAN ports for some reason...I don't remember doing that...

Yea, I did try the GR86 profile as well, no data from that either. The wiring is just mocked up right now, twisted together from the ECU CAN cable to the OBD adapter.

Dang, unfortunately that did not seem to work Same behavior, I can see data momentarily (sometimes) but no live data stream. Just to double check, I put the OBDLink MX adapter back on my GR86 and it is working fine. I also updated the firmware on it, as it was way out of date, but still same behavior on my BMW LinkECU. Could wiring be an issue? I have the OBD connector wired into the same switched 12v as my AEM wideband, both grounds are going to the engine ground on the front of the valve cover, CAN HI/LOW are wired per the Link documentation. I've seen some other posts on the forums with similar weird connection issues to OBD devices, but nothing stands out as a resolution.

Thanks! Made some progress with that, but I cannot seem to get a steady flow of data from the ECU/OBD adapter. OBD BT adapter stays connected, but data is not updating live. With the bit rate set to 500 kbit/s I could never see anything on the RaceChrono side. I dropped it down to 250 kbit/s and it worked momentarily, then stopped working again. See screenshot where I could see data coming from the sensors (I didn't have the car started when it worked, just key on). The oil and intake temps were accurate to what I saw in PCLink directly, but the fuel pressure should have shown around 42psi. A/F did not seem to register anything. First, I need to find out why it is not maintaining a connection though...

You might be right on the raw CAN, sorry for confusing the terminology. The OBDLink MX adapter is wired into the CAN1 port on my LinkECU. Below is RaceChrono help documentation on setting it up CAN bus logging, maybe this will help. As mentioned, I use the OBDLink MX bluetooth reader. Task #1 below is what I am trying to find out. With my GR86, people already did the reverse engineering to find out the CAN details. How do I log CAN-Bus? Theres two ways. Either by building a DIY device or with an OBDLink LX/MX/MX+ Bluetooth OBD-II reader. Notice if you’re on iOS, you’ll need the MX+ Bluetooth model. Find out the packet IDs (PIDs) and packet structure of the CAN-Bus messages on your vehicle’s bus. This is different on each vehicle, and will vary even between different models of the same manufacturer. You can either reverse engineer your bus using some dedicated tools/apps or find them already reverse engineered by others. This is a mandatory step before moving forwards. Enable “RaceChrono > Settings > Expert settings > Experimental devices” Add a CAN-Bus recording device “RaceChrono > Settings > Add other device > OBDLink LX/MX/MX+ Bluetooth (CAN-Bus)”, and then select your OBDLink device. Notice this will NOT work on any other reader. Also it will NOT work if you add the OBDLink with “Add OBD-II reader”, you need to use the “Add other device” to add the reader specifically as a CAN-Bus device. You can now add CAN-Bus channels to the vehicle profile in “RaceChrono > Settings > Vehicle profile”. When editing channels, Channel and Channel postfix field defines how the channel shows up in your RaceChrono sessions. Source data field is data for testing your equations. PID field defines which CAN-Bus message has the information. The equation field defines where the channel data is located in the message, and how it is translated to actual channel values.The equations are explained here

Hmm, interesting. The receiving device (RaceChrono) is CAN (see images above), it is just using the OBD2 adapter to connect via bluetooth to the app. Sorry if my post was confusing in that regard. I have all 3 of those things (oil/brake pressure, steering, etc) working with my GR86, which uses the same OBDLink MX adapter, connected to RaceChrono via bluetooth. The PID's and equations I use for that are here : GJP IO Box setting for RaceChrono - Google Docs Just trying to figure out how to replicate that with Link.