logging is not going to work because as of now, solodl doesn't communicate with the car's ecu, either you set it up wrong or connection is bad but logging is not going to work until you fix this.

I am in point-to-point mode.

I am not aware of how/where to adjust S/F tolerance. Is this done on the unit or on the PC using software?




also, since we're on this subject, what is the "track width" field for and how does it affect the data acquisition?

The tracks are, for lack of a better word, a "line" of location data points. The track width is how much tolerance there is for deviation from that width in which the AIM considers you to be "on track". It also affects where it thinks your set start/finish point is, so you may want to lower it, but it also requires you to have more satellites locked in for accurate readings. Make sure the AIM has a clear view of the sky.

Puma, I have used someone elses solo DL in my car a couple of months ago and it worked fine. I guess I need to figure out how to clear contents and reload software and see if that will correct the problem.

These are great. While I use RaceChrono(android app), as opposed to the Solo, it outputs a file format that allows me to use the AIM software for analysis, I found these videos quite helpful.
If I were looking for a standalone datalogger it would be the Solo DL. I think AIM really hit a home run with the solo units.

Also thanks to CSG for providing support like this. :thumbup:

EDIT:I was actually incorrect, the software I use is Circuit tools, not AIM. They are similar in enough ways that the videos were helpful.

Mike, my car is totally stock except for tires and oil cooler. And, its a 2014 BRZ.

It definitely sounds like it may be an OBDII port issue if everything is loaded up on the unit properly.

Here is the next test.

Leave the unit turned off, plug in the OBDII connector to the OBDII Port, then plug in the silver connector to the AIM Solo DL Unit (the port without the cap) and see if your AIM unit turns on and is "charging" from the OBDII port. That will at least let us know if there is power coming from the OBDII port to the unit.

-mike

Mike, it turns on as soon as I plug in the connector.

Ok so it is getting power at least from OBDII.

If the proper channels are loaded onto the unit, it could be an OBDII port issue.

-Mike Paisan

http://www.pbase.com/paisan/image/153798190.jpg
Maintaining, Modifying and Educating TriState Enthusiasts since 2001.
Like us on Facebook! | E-mail: sales@azpinstalls.com | 725 Fairfield Ave | Kenilworth, NJ 07033 | 908.248.AZP1 (2971) |AIM: AZP Installs
"Race Tested, Enthusiast Approved!"

@jdp530

Hmmm... do you know anyone else locally with an FRS or BRZ you can plug the unit into?

I will have a chance to run in another car this weekend.

Keep us posted!

I sometimes have issues with my OBD2 port, probably from doing too many EcuTek flashes. :bellyroll: My workaround is to use an OBD2 extension cable between the car and the AIM Solo cable, and that seems to do the trick.

I couldn't resolve the ECU data issues even with the help of the AIM guys so I am returning it so they can check it out. I had the latest software and firmware updates. AIM customer service looked at the screens and couldn't see anything wrong with config.