Morello

Somewhat off-topic, but for those who don't mind a little extra work to save the coin, I am able to create the following with my Android phone, a 10Hz bluetooth receiver, an old gopro, and a USB-OTG cable. I have my phone mounted next to the radio so it's out of the way.

For data-logging, it's perfect. I have my phone plugged into the megasquirt over USB, logging with MSDroid. It spits out MSL files I can read in tunerstudio. Racechrono is logging the GPS/laptime information from the bluetooth receiver. I can combine them with the video using RaceRender on my PC. A little extra work, but for the handful of track days I do it's fine. The only functional restriction I can see is that I'm limited to showing either lap information or ECU information (not both) on the phone screen during a session, but that's fine since I'm not competing.

psreynol

that looks fantastic! nice work and thanks for posting!

my track day didn't go very well. despite the new tires the car is still significantly slower compared to times prior the the corner balance and alignment. the car does not want to turn in, it pushes and so I'm forced to toss it in and then with moderate throttle at track out it over steers enough to be noticeable and I'm fighting it hard . the car is also down on power and I noticed big smoke from the tail pipe when I exit the track.at the end of the second session, on the pit in road, I free revved (clutch in blip) and got a bunch of smoke but it goes away quickly (any ideas). 2 plips and it is gone... clearly I have some work to do but I drove home under my own power and had fun with my friends so over all I can't complain.. great weather and I was able to chase down or stay with some truly glorious cars. oh well, fact is the times were not very good so the loss a video showing a slow car driving slow with fast cars driving slow is not much of a loss. either way, bet I hurt some feelings hehe. a good friend, head instructor with a spec miata said he watched my car (while following me) and said my car looked extremely unsettled. I changed everything.... driving style, shocks, tire pressure, with very limited success. I'll start with raising the rear, it was suggested here I'm .5 inch low. after I evaluate the settings, perhaps adjust the alignment, perhaps I need to up the spring rate but I don't think will solve my issue. well if it were easy, everyone would do it!

despite being assured by the shop the aim would plug and play with the stock ecu, the aim solo 2 dm would not pull rpm from the stock ecu so would not log times( the new one has a stock default to require 2 conditions 500rpm and gps movement) so in theory I could remove the required rpm feed but I did not have the laptop to make the required changes. frustrating but im going to call aim and see if we can figure it out. the software is a bit of a pain as well and from taking to several users at the track the first gen works effortlessly. I appreciate my setup might be a bit different and this is a new product but unfortunately the users might need to help flush some bugs. if you are in the market for easy, plug and play consider the aim solo 1. the 2 owners I know are very pleased with its performance both the DL and the simple solo 1.

Gee Emm

I pulled the trigger on a Solo2DL, arrived this week.

One thing I missed was that it ONLY connects to a PC by WiFi, I had read it as being also used WiFi to connect. And the manual made it look like a complicated process (to me anyway). Feeling somewhat out of my depth I fired up the Solo, and my PC (Surface3), looked at the WiFi connections, there was the Solo, clicked, and bingo, connected. Had a bit of a play, seems pretty straight forward to config, but no connection to my ECU yet. The uploading/downloading by WiFi isn't rocketship fast, but probably fast enough for practical purposes when configuring, I'll wait and see what downloading a data file from a session is like before finalising judgement, that is when time will really matter.

I feel for you with the 'customers as bug finders', but to be fair finding that you don't have an RPM signal should have been identified on set-up, and you could then change the paramenters and/or check for a fix to the missing RPM data somewhat at leisure. I presume you have taken this up with the vendor? And hopefully got a decent resolution ... ?

PUBLIC SERVICE ANNOUNCEMENT
Haha! Speaking of bug finders ... just discovered that the OS for the #2 is different, so all ECU maps have to be ported ... and Autronic hasn't been done yet. Better check before putting your money out there, not much point in buying expensive useless electronics. OK, it will work as a lap timer (I think), but if that was all I wanted I would not have bought this.

psreynol

so here is my my last video, several others on my channel. I'm actually running solo I dl because I found some issues with solo2 that need to be worked out. I think they might be focused on getting the Iphone app released. I really miss the ease of use looking at the g force map and other stuff on harrys but the data package offered by the aim is awesome and will prove helpful once I learn how to use it. just the video alone has helped me identify problems so I think the investment will be worthwhile, the auto record function is fantastic but I need to tweak the settings.

if you wonder why no one else is on track it's because most people left at noon due to the oppressive heat. I was wiping the sweat off my hands so the wheel wouldn't get knocked out of my hands. so not super clean laps but it is what it is.

13brv3

Thanks for the info on the Aim Solo 2. I've been looking for a logger that doesn't use GPS only like my VBOX Sport. The roads I drive around on have enough trees to make the VBOX data noisy, particularly for long G forces. It appears the Solo 2 has accelerometers, and GPS, and your G readings looked really smooth, so I'm assuming the new AIM is not using GPS for G force calculations like the VBOX does.

One thing I haven't been able to figure out from the manual is whether you can view live readings while driving. I'd love to have live lateral G's shown while driving, but the manual just isn't specific enough about what you can do with the display. Are there options to view data other than lap times in real time?

Thanks,
Rusty

psreynol

Actually I was not able to get the solo 2 dl to work properly with the Miata ecu (rpm signal at a minimum for auto start & record), nor could I get it to work with the my old tec2 electromotive stand alone( serial rs232). it should work with either/ both but some of the channel map re-releases have been delayed due to some problems when they migrated lap-timer setup from race studio 2 (solo 1) to race studio 3( solo II). the video I posted was recorded with a solo 1 dl and the smarty cam which has g force, accelerometers built into the camera. Solo1 dl will pull the basics temps, TPS, rmp, map, from a miata ECU.
AIm just released a new dash (mxm), the new solo II/DL and are said to be working on the I phone app so they have a lot on their plate. if you are running a newer ECU, i'm hopeful you will have better luck, but I wont recommend the solo 2 dl until I've verified it will at least get rpm from the stock miata ecu. the ECU compatibility list on-line I believe is for the solo 1dl, because when you enter the setup in race studio 3 many previous offerings in RS 2 are not available as of today in rs3. they have frequent updates so hopefully more phone calls will get us toward the front of the line. The solo 1/1 dl is a very fine product and to answer your question, you can view the accelerometers from the smarty cam in numbers form on the solo1 dl but it would not be easy to eye glance peak numbers imo without a graphical display or a peak recall function. perhaps call them about this. I don't really look at it while driving, hence my focus on the need for a hands off auto start/record.

13brv3

Thanks for the excellent reply. It sounds like the Solo2 is still a works in progress. I'm running a MS3 Pro PNP, so I don't know if that would communicate or not, but I wasn't really planning to get the DL version, or connect it to the MS3. RaceRender will import the MS3 logs directly, so the only problem is synchronizing them.

I did send an email to the AIM folks before I ran across your posts, but I haven't heard back from them yet. My last hope for the VBOX Sport is an external antenna that will be here tomorrow, but I'll be surprised if that helps much with the area I'm in.

Thanks,
Rusty

psreynol

one point of note is that the new solo 2 and solo 2 DL use both GPS satellite standards and is said to have much better accuracy and connection speed. if you are running a obscured course, the new solo might be of value. depending on your needs, it might make sense to log the engine stuff separately via the MS and use the solo 2 for lap times ( they claim to have superior GPS). if you have a signal to match, say 3 quick blips before you launch, it should be pretty easy to overlay the data in race studio 2. I cant say for sure but I would not dismiss AiM based on my situation, you just need to verify if the solo 2 can pick up a rpm signal from the MS. call them and ask about gps performance gains around dense trees with the solo 2. I think they will claim it overs the best coverage due to using more satellites. if the solo does not work, perhaps you must use a dash with a roof mounted antenna

13brv3

Thanks for the reply. I did also hear from AIM yesterday, and they told me something I didn't really expect. The Solo 2 (basic) has only GPS, so it calculates G forces rather than measuring them directly. It will not display the G's in real time.

The Solo 2 DL uses GPS and internal acc/gyro to make the measurements, and it will display real time G's. In addition, they said the DL is expected to collect data from the MS, though the software is not yet available for the connection. It is expect soon though. This sounds like the best option, though more expensive of course.

I have an external antenna on the way for the VBOX Sport, since that's the only other option to try without buying new gear. I'll be pleasantly surprised if it makes a difference though. I'll stick it to the middle of the trunk lid since that's about the only option for a steel surface.

Thanks,
Rusty

schmoo

I've been running a dated MXL Pro with a SmartyCAM HD GP for a few years now and couldn't be happier with it. AIM's service and support have been amazing.

The MXL pulls data from my Hydra over CAN and I love not having to glance at gauges, instead relying on alarms lights.

I've got steering angle sensor and brake pressure sensor left to install.

Gee Emm

Updating, I am told that the new OS for the Solo2/Solo2DL/MXM and all the other new dashes needs a firmware update to read (all? or only Autronic?) ECUs via serial (at least, that is what I need so can't speak for CAN connections). Further told this will be available end September (possibly earlier). My dealer offered me a refund, but I am going to keep it and set it up for the non-ECU functions in the meantime as I have events in early September.

13brv3

I tried the external antenna for the VBOX Sport today, and it was a complete waste of money. Obstructions are of course a limitation of GPS only units, though certainly GPS chipsets and filtering can make a difference. There's every reason to hope that the Solo 2 GPS is better than the VBOX Sport, but I'll stick with the DL model for the internal sensors if I end up getting an AIM unit.

For now, I discovered that the Shadow Dash MS app has the phone acc sensors included in the log. They seem to do a passable job, so I'll just mount the phone straight and level, and use those for now. I'll keep an eye on the Solo 2 DL to see when they get ECU interface working.

Thanks again for the info.
Rusty

Gee Emm

As I will be using my DL in mere Solo2 mode (no ecu connection) pending a firmware upgrade (see above above), I opened it up last night to look at the setup so I can at least get some data at my next event/s.

I changed the 'logging starts' conditions to simply speed and set all other functions to lap timer displays (eg no shift light, lights signal lap time delta instead). I found it pretty user friendly, at that level, but I have hardly scratched the surface yet. One thing I will be interested in, is how long the internal battery lasts. With no connection to a power source I will be totally dependent on the internal battery, and will bring the 240v power supply to the track as backup.

wildo

iTrader: (1)

There are two different hardware architectures in AIM's line-up. The newer pieces of hardware use Race Studio 3 for configuration. The older systems use Race Studio 2.

Original Solo & Solo DL = RaceStudio 2. Same with the older loggers.

New Solo 2 and Solo 2 DL = RaceStudio 3. Same with the newer loggers (MXS, MXG, MXL2, MXm, MXS 1.2, MXG 1.2).

The Original Solo and Solo DL are configured with Race Studio 2. These loggers support all of the ECUs listed on AIM's website. The Solo 2 and Solo 2 DL are on the new hardware version, and are configured with Race Studio 3. All of the ECU formats/protocols supported by the old hardware must be re-written for the new hardware.

It's my understanding that AIM is about done with CAN based ECU protocols.
Next up is K-Line / ODB-II applications.
Then comes serial / RS-232.

That means that for now, the only MegaSquirt ECUs that are supported with the new Solo DL2, are MegaSquirts with CAN output. That means the v1 MSPNP is not compatible with the Solo DL 2. If the v2 or MS3 PNP support CAN, then they should be compatible.

If you'd like to know if your ECU is currently supported by RaceStudio 3, install Race Studio 3 and click on the ECU tab. It will list all of the ECUs that are supported.

If you install Race Studio 2, and click on the ECU tab, you will see many more ECUs listed here than in Race Studio 3. It is my understanding that eventually, the Race Studio 3 list will include every ECU listed in Race Studio 2.

To make things even more confusing, AIM released the MXS 1.2 and MXG 1.2, with an even newer hardware set. The MXS, MXS 1.2, MXG, and MXG 1.2 use Race Studio 3 for configuration, but the ECU protocol list is different. There are ECUs that are currently compatible with the MXS and MXG, that have yet to be ported to MXS 1.2 and MXG 1.2.

Bottom line is that ECU protocol compatibility is currently inconsistent across a few different types of AIM hardware. If you are planning on picking up an AIM logger you should verify your ECU is supported before buying the logger. I almost sold my Solo DL and picked up a Solo DL2, but would have been hosed, as I have a v1 MSPNP. To verify your ECU is supported on the logger you want to buy, install it's appropriate version of Race Studio (probably Race Studio 3), and configure the logger all the way through, including selecting your ECU, and the way you connect to it (several ECUs have a variety of different protocols).

AIM has done a very poor job in communicating these changes. I know a few racers who have purchased the latest AIM product and found that their ECUs are not (yet) supported. Very frustrating.

Three Screen shots show:
Race Studio 2 Support for Solo DL, MegaSquirt with 3 varieties: MS1 (serial/RS-232), MS2 (CAN), MS3 (CAN)
Race Studio 3 Support MXS, MSG, MegaSquirt with 3 varieties: MS1 (serial/RS-232), MS2 (CAN), MS3 (CAN)
Race Studio 3 Support Solo DL 2, MXS 1.2, MXG 1.2, Megaquirt with only 1 variety: CAN simpl bcast

Gee Emm

Thanks Wildo, cat for you! You have confirmed the information I was given, with added detail! You're damn right about frustrated users, in this case make that 'angry and frustrated'! It goes beyond that, based on their website, currently (at least) they could be in the gun for making 'false and misleading' claims about the product, something our consumer protection legislation takes pretty seriously.

Based on my interaction with the dealer here, that means the whole OS upgrade for the Solo2DL (and kin) will be finished by the end of September. My dealer told me he has asked Italy for the Autronic/serial protocol to be prioritised, as they have a number of users here, and if that happens it will accelerate the timeline for that specific application.

My understanding is that the availability will be continuously updated (Edit: bearing in mind that it is the holiday season there), so if you like me are sweating on one particular update, do this at regular intervals. Your RS3 will be updating itself each time you do this.

That is what I was told too.

Agree.

It may be no coincidence, but there is a nearly $60AUD discount on the S2DL here, and having paid full price for a device with crippled functionality, that makes me just a little bit cranky. That seems to be a cue for another phone call to the dealer ...

psreynol

I've talked to Aim North America several time, to various people and each has slightly different perspectives. If you choose to believe that everything will be ported or fixed by September fine, but consider that despite the best of intentions some times the legacy integration never materializes. For example they indicated that a big release was very likely to occur prior to the summer vacation starting AUG 6th for two week but that release did not happen. I don't know how they do things over in Italy but my sense is that it gets done when it gets done and NA really has no idea or influence. very frustrating for NA sales and support I imagine. vendors are keenly aware and will take it back due to the fact Aim has made no effort to document the dependency between what ECUs are claimed to work in solo 1 vs solo 2. furthermore I got protocol information from a ecu maker and their protocol does not match, doe not seem to match what aim has on file. with 1500 ish ECUS to manage it is likely that we may find that some compatibility issues exist beyond what we are talking in terms of race studio 2- vs 3 and the associated hardware. racers are pretty understanding about stuff not working out of the gate but Aims apparent unwillingness to document the compatibility issues with what may or may not work on the solo 1 vs solo 2 is very likely going to severally hurt their reputation in the long run. They have a solid product, but at this price point the wave of super pissed people is only going to grow as they ship more units.

Gee Emm

Good news update! My Solo2DL is now updated with the Autronic protocols. I think that any new protocol applies across all the new gen devices (eg MXM).

If you have been waiting on this, it would be worth checking (open RS3, and wait for it to check for updates - mine was very slow to get to the point where it can download). I can't say that all ECU protocols are available, my dealer inferred there was a priority list so you need to beat on your dealer if yours is not available.

Like psreynol, I was slightly sceptical about the delivery date, but kudos to Aim for making it. That recovers most of the bad taste in it not being available when the device was released.

Gee Emm

I see SADFab have a visor mounted Ram mount ball on their website http://sadfab.com/prod%20miata%203d%20other.html. I have lodged an order, given I was looking closely at that location for attaching the generic bolt-on one that is available from Ram. It is printed, but hopefully strong enough to hold a Solo suspended vertically below.

Gee Emm

For Reasons, I have not been to the track for far too long. In turn that has meant the Solo has been left in the box. However, with an upcoming back-to-back Supersprint and Club track days, the Solo was dug out and the connection to the ECU set up.

Except, not.

Nothing we can do will get the Solo to talk to the Autronic via the 3.5mm three wire stereo jack-to-DB9 serial connector. We are using just two wires as per Aim documentation (data out and ground), the other is data into the ECU from the Solo which is not required.

Aim talks about bridging other pins in the DB9 connector, except they are dead pins, unconnected to anything in the ecu or the Solo. The dealer reckons these need to be bridged as that tells the ecu to transmit data, but as they are not in any way, directly or indirectly connected to anything, this seems to be a furphy. But what would I know, I am no tech geek ...

So, has anyone used a SoloDL or SoloDL2 in serial mode for data capture from an ecu? If so, have you any insights into serial wiring issues, or any trick in RS3 that we may be overlooking?

We will have another go in a couple of weeks when I am back in town, so anything that I can learn from others' experiences would be most helpful.

Thanks in anticipation!

AussieMSM

Have you tried connecting the “in” wire anyway just to see? I would have thought there’d need to be some kind of handshake between the devices.
My ECU to Solo DL serial connection requires RX, TX & Ground. Transmits data via serial perfectly fine and fast too.