RaceCapture not reading CAN information from AEM Infinity 6

Def · Post by **Def** » Sun Jan 29, 2017 8:12 pm

My Racecapture has never seemed to read data from my AEM Infinity 6 (now called the 506).

Is there something I should be setting up on the setup page? I looked it over for a solid 30 mins today and didn't find anything obvious. I did verify the AEMnet datarate is 500k baudrate, which is what I've set mine to.

Is there a diagnostic I can do?

jcforbes · Post by **jcforbes** » Tue Jan 31, 2017 5:03 pm

In the app under settings then scripting menu you can turn on "Poll log" and switch it to "debug". You should then be able to see what error message you get.

Post by **brentp** » Tue Jan 31, 2017 8:47 pm

You can also replace the current script you have with the simple logging script and see if you're getting any data at all from your AEM system. Try this:
https://wiki.autosportlabs.com/CAN_Bus_logger

...and let us know what you see. Thanks!

Def · Post by **Def** » Fri Feb 03, 2017 1:49 am

Thanks for the replies guys.

I have the latest Android RC app version 1.8.0 running on an 8" Fire tablet, and I see the Scripting menu before I connect to the RC wifi, but it disappears after I connect to the RC wifi. So I couldn't run the script linked. Any info on how to run a script while actually connected to the RC? Or do I need to connect via a wired USB connection while it's connected to the AEM Infinity via the RJ45 cable?

Here's some screenshots I took:

I'm trying to read 2 OBD2 channels, but the number of PID read fails scales with how many channels I'm trying to read (no real surprise there, thought I'd mention it though):

Based on a few messages received here in the log, I'd say it's reading CAN data based on it being a different length than it expected. I triple verified wiring according to what was posted in the wiki. CAN wires are terminated via an AEM mini-harness, which I think includes the resistors right by the ECU connector (there is a heat shrink segment right off the ECU pin for each wire, so I believe that's what it is):

Any other debug steps?

Def · Post by **Def** » Fri Feb 03, 2017 1:50 am

Sorry for the huge pics... didn't realize they wouldn't autoscale!

Post by **brentp** » Fri Feb 03, 2017 10:00 pm

Hi -

So, the OBDII subsystem is trying to read OBDII PIDs - that's what the errors are indicating.

Are you trying to read data from an OBDII ECU, or from the AEM?

If you're attempting to read from the AEM, then you'll want to turn OBDII *off* in the OBDII settings, as it will take over the CAN connection, blocking the script from receiving CAN data.

Hope this helps, let us know what you find out!

Def · Post by **Def** » Sun Feb 05, 2017 9:21 pm

Brent, thanks for the reply. I wasn't sure on that one, so I've previously tried both with it on and off (and yes, I'm writing after every setup change and reading to verify the config on the RC).

So I got some log screenshots with OBD2 turned *OFF* and CAN turned *ON*.

Maybe the thumbnails from IMGUR will work a bit better:

This log is continuous from the previous config (OBD2 on) to turning it off at RX message timeout:

This is changing the type of log from INFO to TRACE:

Any ideas? Is the next stop looking at the CAN info being received? Best way to do that? I'm assuming not an Android tablet right? I can't find a way to do that on the Android app - scripting setup submenu disappears when I connect to the RC wifi.

Post by **brentp** » Sun Feb 05, 2017 10:04 pm

You can run the simple CAN bus logger:
https://wiki.autosportlabs.com/CAN_Bus_logger

This will show if anything is being received by RCP on that CAN channel.

As before, ensure OBDII is off, and the baud rates match. Ensure that your CAN termination is correct. Worth noting, RCP has built-in CAN termination on it's end.

Def · Post by **Def** » Mon Feb 06, 2017 3:10 am

The scripting submenu goes away when I connect to the Racecapture wifi. See my screenshots for what it looks like when connected.

How do I run a script when connected?

Post by **brentp** » Mon Feb 06, 2017 3:47 am

I am sorry. I thought you were using a RaceCapture/Pro, which supports scripting.

Are you trying to use an OBDII emulation mode from your AEM infinity?

At the moment, RaceCapture only supports OBDII PID querying. Next firmware release we will be able to support direct ECU CAN mapping.

If your AEM can support CAN OBDII compatible emulation, then it should work in theory. You can confirm RaceCapture's OBDII operation by plugging the RaceCapture into an OBDII port of a 2008+ vehicle.

Sorry for the confusion. We'll be posting more about the upcoming firmware that supports direct ECU mapping.

Def · Post by **Def** » Mon Feb 06, 2017 7:34 pm

Oh... I wasn't aware this wasn't supported out of the box since it was touted as a feature on the Racecapture kickstarter.

Any ETA on the new firmware?

Post by **brentp** » Mon Feb 06, 2017 7:42 pm

It is, we were behind on rolling out every feature. It will be available for beta within a few weeks, we expect! It's an important feature and we're committed to it.

Here's a video previewing what it will be like from the RaceCapture end: https://www.youtube.com/watch?v=zc1Bi__0IDk