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