Autosport Labs

We've created a default configuration that uses the direct CAN mapping tech released in 1.9.0. Details here:
https://www.autosportlabs.com/aim-smart ... tegration/

If you're running the current AIM integration let us know how it works!

This is awesome!!

thanks! try it out and let us know how it works for you

Sorry to dig up an older thread...

I am having trouble with a few of the channels not working properly, specifically Fuel, and battery. They both read a static large number in the 32000s.

My setup is as follows, I have an Aim Solo DL with a SmartyCam as my primary data logger, connected with an AIM data bus. I have a Racecapture/Track connected with the aim integration cable to the data hub.

I did find a discrepency in the racecapture wiki while trying to figure this out. The AIM smartyCam integration page has the fuel channel ID as 1060 and on the CAN database it has it as 1070. I did try that channel and it did not work.

SmartyCam integration: https://wiki.autosportlabs.com/AIM_SmartyCam_CAN
CAN Bus database: https://wiki.autosportlabs.com/CAN_Bus_database

Any help on this would be appreciated. I know this is not a standard configuration setup, so any help would be wonderful!

[EDIT]: I was thinking about the problem some more and I wanted to see what harm could potentially come from trying to poll the CAN ID associated with the bmw e46 (didnt mention above but this is an e46 330ci chassis) can id for fuel, which according to the wiki would be 1555. Thoughts?

If you can access the OEM can bus, then you can certainly read that data as well, with a separate mapping. Perhaps use CAN2 on RCP?