Aim Datachannels
 

I wanted to start a thread on the Aim advanced Datalogger and what they can read from the factory

I wanted to start by pointing to the latest specs I have found the Aim system can log for our cars seems to be version 1.06

Channels currently AVAILABLE on AiM loggers connected to "Toyota" "GT86/SCION_FRS":


• RPM
• Vehicle speed
• Pedal position sensor
• Brake pressure
• Steering angle
• Brake switch
• Engine Coolant Temperature
• Intake air temperature
• Manifold air pressure
• Ambient Air Temperature
• Barometric pressure
• Lambda value
• Throttle position
• First Catalyser temperature
• Clutch switch
• Front left wheel speed
• Front right wheel speed
• Rear left wheel speed
• Rear right wheel speed
• Oil temperature
• Engaged gear

I hope Aim will add more channels in the future.

CHANNEL NOT yet available on the Aim System...AND useful for track users

• Gas level - PID ?
• ABS light - PID ?
• Traction control light(s) - PID ?
• Check Engine Light - CEL - PID ?

CHANNEL NOT yet available on the Aim System... may NOT be useful

• TBD

DATA that may be interesting but requiring new sensor

• Fuel Pressure - see PST for custom sensor.
• All sorts of temperature: brakes, tires ... - see PST for custom sensor
• Suspension travel - see PST for custom sensor

If you want something added, e-mail them the PID, and they'll include it in the next update. There's a lot of stuff that *can* be added, but isn't necessarily important.

Are you currently using a Solo DL?

i asked several time for a precise fuel level and i beleive i sent them the PID for it that i found somewhere here on the forum but looks like they didn't think it was important enough...

At least i was able to make them add individuals speed sensors.

They should be correcting all the temperatures also in the next update which were all like 10 deg off, only the water temp was corrected but they almost all had a offset.

@puma, your answer make me feel that we should definitely continue updating this thread and follow up on the new PID we want them to add.

I am actually on the fence about buying the Aim MXS or MXL ... BUT ... I feel that they could have added a lot more PID, that would have made the buying decision a lot easier.

If Aim can update the PIDs, with our help, I believe Aim could greatly improve their sales with the BRZ/FRS crowd.

Anyways let's hear the PID and the data you would want to see. I'll update the initial post. Feel free to post PID you have and think would be useless as well. We could maintain both useful PID and useless PID in this thread.



@Captain Snooze, when I see all the work @PST had to do to get the ABS information, ouch.. It would be so much easier if Aim could have added the ABS PID !!!

@puma First thanks for pushing for the wheel speed, the is the only reason why @PST was able to calculate the ABS turning on/off. If you can share here the PID you requested to Aim and also how did you make your request, contact form ? that would help.

@CSG Mike If you have any PID you know of and want to share here that would be great. I know indeed many PID are useless, but gas level, abs, traction control and CEL lights are a BIG deal, we need to get these added!

Fuel level would be a huge benefit for other cars, not just ours. We would LOVE to be able to sell our customers on an Aim kit to replace ALL the gauges. It's annoying to have to tell them, "No, we'll have to leave that Stack fuel gauge there."

There ARE some plans in the works for a separate interface device to log ABS events.


@Beastronix, what about making a fuel level interface device? If you give us a 0-5VDC analog signal that plugs in, we'd be throwing money at you. :D

That being said, here's my ABS engagement channels. It might be helpful to compile everyone's custom channels in one place (that they're willing to share). Feel free to use this format:

Ch:ABS_ENGAGE
Desc: Shows ABS events based off of brake line pressure and wheel speed rate of change
Ch. Req:OBD2, dFrontWheelSpeed, dRearWheelSpeed
Notes: Accuracy restricted by low refresh rate (10Hz) across OBD network.
Ch:ABS_Front
Desc: Shows front axle ABS events based off of brake line pressure and wheel speed rate of change
Ch. Req:OBD2, dFrontWheelSpeed
Notes: Accuracy restricted by low refresh rate (10Hz) across OBD network.
Ch:ABS_Rear
Desc: Shows rear axle ABS events based off of brake line pressure and wheel speed rate of change
Ch. Req:OBD2, dRearWheelSpeed
Notes: Accuracy restricted by low refresh rate (10Hz) across OBD network.
Ch:dFrontWheelSpeed
Desc: Shows rate of change of average front wheel speed with respect to time.
Ch. Req:OBD2
Notes: Accuracy restricted by low refresh rate (10Hz) across OBD network.
Ch:dRearWheelSpeed
Desc: Shows rate of change of average rear wheel speed with respect to time.
Ch. Req:OBD2
Notes: Accuracy restricted by low refresh rate (10Hz) across OBD network.

@puma, is there really a PID for fuel level ? I saw on the electrical schematic that the cluster has dedicated wires just for the fuel level (see attached).

@PST, thanks for the inside info, this thread is a good place to also discuss setup of the Aim custom channel.

@PST, I see that there is a fuel pressure sensor (see attached), that may actually be accessible through PID in the CAN bus, no ?

What do you mean "accessible through PID?"

From the wiring schematics:

Fuel pressure sensor
Connector C10 pin 3 white and blue wire
-> to ->
Connector AC1 pin 16
-> to ->
ECM
Connector A34 pin 9 violet and black wire

So if the Engine Control Module (ECM), behind the passenger dash, connect to the fuel pressure sensor, I assume it MAY have its own PID ?

I get that part, but PID is a feedback loop mechanism for control systems. The fuel pressure in this car is not a closed-loop system. There's a fixed pressure regulator in the pump assembly, there's no PID involved.

Jake

Glad the professional are on board ;) i'm just an humble explorator :thanks:

I wasn't trying to call you out or anything, just wanted to make sure I wasn't missing something. :D

The only problem with FLI is that it's a raw reading, so it'll read *all over the place* when you're moving/driving. What you see on your dash is an interpolated average.

FLI is available on the AIM via generic canbus, but it's a relatively useless reading...

can we do the interpolation calculation in real time in the dash ? sorry newbie here, I am not sure what the AIM dash can do yet ... still learning.

Negative. There's actually some problems with the linear offset calculations we found in Race Studio 3 that will be fixed in the next update, I'm told.

Jake

I'm sure I could sniff this out. Giving a plug-in signal won't be an issue either... I'll add this to the list. I just returned from 86Expo and plan on collecting the ABS data for output asap.

The #1 item on my list was getting around limitations on when you're allowed to enable the pedal dance. That has been solved :) I have the VSC module going to standby instantly when the car starts. Doesn't matter if it has been sitting for 2 weeks or if it's -10 degrees out. So, for track/race cars... we can say goodbye to that waiting nonsense. The Speed Academy guys should have a video up soon with this in action.

I'll migrate this over to the ABS system while I also collect the engagement data and will then look into the fuel data.

I'm definitely interested in getting more data from the Aim Solo DL. Particularly fuel pressure (looks like that is not available) and oil pressure (which I also believe is not measured) for vehicle health.

As CSG Mike pointed out, fuel level will be all over the place when you're on the track, because the fuel is sloshing around when you corner and brake (and not so much when you accelerate). I'm interested to know how a fuel level reading could be useful.

ABS I get, and PST's calculation is a great way to get that for now.

I'd like to understand why CEL is important. If the CEL comes on, then pull off the track and use an OBD2 reader to pull/reset the code.

As you become a more experienced driver on the track you'll find you can get more out of the car by doing the "pedal dance" and turning off the traction control. At that point, gathering traction control data from the Aim seems redundant. Before disabling it you could also probably figure that out by looking at wheel speed in a corner - I would have thought TC intervention would be fairly obvious.

@philooo - what sort of things are you looking to learn from your data, and how are you applying them to the decisions you are making when setting up or driving the car? I'm interested in getting more out of my Aim so the more I can learn, the better.

as far as fuel level, i just found it here on the forum and passed along to them, it is in a thread about a special obd reader, something like scangauge or something? Bunch of PID in there, i don't know anything about those so i won't be of much help for that.

Just sending the request and info to info@aimsports.com does the job, i usually go through Roger@aim or who ever is in charge to answer at info@aim

The idea behind replacing every single light on the dash, is to get rid of the dash cluster and ONLY USE the Aim display. Mainly to have a cleaner look inside the car.

Once you put the Aim MXG in front of the OEM cluster you can't see the it at all. So if you are on track and the CEL light comes on, you will not be able to see it.

Again here I am talking about Aim MXL2/MXS/MXG. Look at my other thread here, about these display on how they fit on the dash

I am just trying to decide which Aim device I should buy and mainly decide between the MXS (OEM cluster visible), or the MXG (OEM cluster blocked). I need to know if we can improve the amount of data collected by Aim and get rid of the OEM cluster. Right now it seems the answer is ... no :(

About how to use the data to setup you car, I think @PST are the king at the topic.

Ah - that makes a lot more sense! And having the ability to add sensors for measuring suspension travel and other items that are not natively read by the CAN bus would be good too.

@Beastronix will your module work with a standalone ecu like Motec for example?

i beleive if you keep the OEM ecu you can't remove the cluster because of the immobilizer, car won't start.

once you remove all the plastic part around the poem cluster, it is a rather thin 1.5" piece of plastic, that could be tucked behind the dash easily.

hopefully someone will be able to disable the immobilizer someday ;)

As long as the other ECUs are still as is, compatibility shouldn't be an issue. I'd of course like to do some logging & testing once this little project is full steam, but even if changes are needed they shouldn't be hard to accommodate.

Did you guys look at the GT86 rally car? I think in the catalog, they offer a similar option, or it might be integrated into the ecu.

^^^duh. With a standalone you wouldnt need the pedal dance anyways....

Was your first question concerning ABS & Fuel data outputs previously mentioned? Trying to make sure I'm on the right page :)

Seems like someone else is looking for fuel level for the RACEPAK system here
@Poodles mentioned " in Torque, the fuel sensor is PID 2129"...if Torque app can get fuel level, I assume the $$$ Aim should be able to do it :S

It can. It's a raw reading, and is useless in the real world, without interpolation.

Can one of you EEs explain to me why Torque calls these channels PIDs? Does it stand for something other than Proportional Integral Derivative? I keep seeing people use PID for things other than feedback loops and I'm not sure where it's coming from.

Jake

Sorry if this is a thread jack but this is the only active thread on AIM that I see on the forum. Just installed my MXS and when I connect the USB cable to my Surface 3 nothing happens in Race Studio 3 - says no device detected. Is there something special I need to do?

*EDIT* Manually installed the USB drivers from the AIM folder and re-connected all plugs - it now works!

Anyone find a way to display the following:
- Display AFR as a calculation of LAMBDA?
- Use a warning light when a DTC has triggered?
- Display boost as a differential between barometric pressure and MAP?

Regarding the math channels, I'd reach out to Aim tech support directly. It's theoretically possible, but when I tried to have our MXL2 do some onboard corrections for the IR temp sensors, I discovered a bug in the math channels. Linear corrections were spitting out random gibberish, and they were able to reproduce it.

DTCs would require more CAN integration, and that's something that's going to have to come directly from Aim. Lots of people have been asking for it, so I'm sure it's on their radar. I imagine it's a tough nut to crack, so it's going to take a while to make sure it's complete and something they can sell as a product.

Are you saying that the readings fed over the OBD2 Canbus for oil temp, water temp and intake air temp are not accurate and need to have a "correcting factor" applied to them?


If so, how is the correcting factor determined?

Sorry to necro an old thread, but it's one of the top results when searchig for the fuel level PID for our cars, and now that I found more data I realized the thread is misleading.

I logged the standard OBD PID for the fuel level and the custom OBD PID 0x2129 during the recent track day at Buttonwillow.

It very much looks like 0x2129 is interpolated.
In fact, having looked at my data over a few track sessions, I haven't found any issues with that data. Basically the fuel level is just constant when I'm parked, drops fairly linearly over time when I'm on the track, and stays constant after as I come back to the paddock and do my cool down.

Having that evidence, I feel like the 0x2129 can be very much trusted at the track.
I wouldn't rely on it being precise up to +-1 liter, so don't try using it to estimate how many miles you have till the next gas station... but it looks more than good enough to estimate the average fuel burndown rate.

Here's how the data looks like.
Yellow — standard PID, green — 0x2129, cyan line — lat G's.

https://i.imgur.com/FBrRzI6.png

https://i.imgur.com/mxo9h2p.png

https://i.imgur.com/DRG2GV6.png

Well, that is a nice find, it gives me some hope that I can run a Haltech IC7 and have a working fuel level.

The stock cluster has some kind of formula involving the level sensor and amount of fuel injected to derive a displayed value, if fuel injected amount is not supplied then the car will be bone dry at an apparent 1/3rd tank on the cluster. This applies to Gen 1, I know nothing about Gen 2.

You can do two things. stick the OEM cluster in the back or something and then hace the IC7 mounted infront of it. Or two, you can hook up the fuel level sensor directly to the IC7. But it wont be as fancy to give you a accurate reading like the OEM. Yeah OEM use both fuel injection timing and a average of the level sensor to determine the real level. without the injection Pulse with the oem cluster would have a funky operation that at 1/4th tank the gas would be actually empty. But this isnt a issue if you hook up the IC7 directly to the sensor. As long as it had a good algorithm for averaging the sensor input reading.