Aim MXP 1.3 vs Aim solo 2 dl

Hey all,

I am currently building a parts list of stuff I need for my electronics package upgrade on my time attack WRX.

I currently use racechrono on my phone but want a step up with a windows based UI as i am finding lots of issues getting data and video off phones and onto a PC UI in a timely manner.

I have a link g4x PNP and want to get driver telemetry, i have looked into Motec and AIM and for me, AIM looks to be a better option for my budget.

I'm trying to do research into the telemetry data that that AIM 1.3 race dashes put out but i can't find a good answer.

Would I be better off going for a race dash with logging or a Solo 2 and a non logging dash?

A dash would be an upgrade for the future as I would like everything directly in front of me and dont need to deal with gauges when doing other kinds of events (Longer tarmac rallies and such).

Whats peoples opinions as i know i have much to learn and this is the next step into data acquisition and analysis.

Thanks!

Hello Samuel,

Interesting project.

There are a couple of way to approach this, If you just want a logger to get data for analysis later in Racestudio then you can use one of AIM's CAN based loggers. These are expandable to get analogue inputs and output to any AIM display. Even AIM's older EVO4 is pretty good and for this.

The SOLO2 DL is a small display GPS laptimer that will give you good GPS data and predictive laptime with CAN input from your ECU and its also compatible with expansion modules for additional analogue sensors etc.

the MX dash series is a different product range that integrates the same functionality as a SOLO2 DL and the expansion channels together in one unit but it is more expensive, i believe the Link dash is a rebranded AIM MX unit so i may be easier to stay in the Link family...

Its also worth mentioning that the AIM Smarty Cam can be added into any package or be a standalone data acquisition with CAN input from the ECU.

But fundamentally if the logger has CAN it will pull all the channels from the ECU or whatever CAN module is connected to it - TPMS etc, anything else would typically be a 0-5v analogue sensor signal. The GPS sensor will usually incorporate an accelerometer and gyro giving you lat/log/up/down accel with pitch/roll/yaw so from that you can work out braking and acceleration forces (X/Y scatter plot) as well as over/understeer and evaluate the suspension somewhat.

I'd take a look through the spec sheet to make sure the baud rates are acceptable for each product - for GPS I'd be wanting 20/25hz as a minimum and 100hz for accelerometer/gyro data. If you plan to add damper pots, wheel speed etc. then shoot for 200hz minimum. Its also worth pointing out that the available CAN data can sometimes be too slow to to be useful especially it its coming from and OEM or OBD data stream I've seen throttle position as low as 1hz before so bare that in mind.

Telemetry is a ship-to-shore live data broadcast and i don't think AIM does this, Motec do as do the the more high end systems but i think in your application you just need traditional data acquisition for post event analysis.

It all depends on what you want to achieve, simple GPS data is sometime enough to improve laptime whereas better data acquisition will also improve the vehicle, I've even coached riders with basic GoPro GPS data and the Race Technology software and had good results.