Any RMSolo DL1 users?

[aleliaert]

We picked up a Race Technology DL1 datalogger and plan on using it this season at local events. Anyone doing the same?

It might be fun to exchange files, compare notes, etc. Mmmm data. :)

[Chris_Swearingen]

Thats some serious hardware. :eek:

I would be happy to share data from my lowly GTech PRO RR and if I can figure it out overlay that with some engine management data from the EMU.

We could probably compare max g's etc, but I don't know if I can get the GTech data formatted well enough to compare segment times with the fancy GPS based stuff you have. But I am certainly willing to try.

[aleliaert]

I was thinking that line and braking points would be the easiest things to compare, given different cars. To compare data with an accelerometer-only system, we might have to get our hands dirty... Does it attempt to reconstruct a map from the accelerometer data?

Just pick up a DL1, join the bandwagon. :)

[Chris_Swearingen]

The GTech doesn't try to create a map, however the Geez cube software and another product I am helping beta test both take GTech data and recreate maps from it.

My biggest drawback at this point is accessing the data at an event site. I don't own a laptop with a serial port and the GTech doesn't like my USB to serial port converter. Which reminds me, time to post for one in the classifieds.

[Built-By-Bones]

We picked up a Race Technology DL1 datalogger and plan on using it this season at local events. Anyone doing the same?

It might be fun to exchange files, compare notes, etc. Mmmm data. :)

Congrats Aaron, that is awesome. Now you and Jenn have an excuse to do the Evo Xtreme school where we will teach you how to use the DL1 to improve your driving between runs. Join us in El Toro june 2 and 3, check the blackwatch racing site for details.

For low end data systems, less than $5K, it is really hard to beat the Race Technologies stuff. A few quirks care of the British programmers, who come from a road racing background, but a superb system.

look me up at the next local event and I will give you some tips.

Grant Barclay

[aleliaert]

look me up at the next local event and I will give you some tips.
Grant Barclay

That would be great. While powerful, the included software doesn't seem to be optimized for quick between-run analysis. I heard about the "start of run"/"end of run" naming trick for the markers, which helps but it still seems like a lot of work to bring a new data set in and compare to existing ones. If you have more tips, I'm all ears!

I've seen the MaxQData in action (Kevin Dietz at Nats) and the ease of use was very appealing. If Race-Technology doesn't make a "killer app" for autoX use (I'm not holding my breath after reading some of the manufacturers' responses on their forums), maybe the user community can roll one themselves. I've worked on a bit of attitude and orbit analysis software for spacecraft, and the number crunching in this case should be easy in comparison. Finding time to write extra-curricular code, not so easy...

The Evo Xtreme school sounds like fun. Jen and I hope to take another school this year... "El Toro" sounds like a place with good Mexican food. :)

[Built-By-Bones]

Killer mexican food for sure, it is southern California after all.

The MaxQ system is probably the best cheap data system (not including the cost of a PDA) available, and can be handy for between run analysis. I have spoken extensively with the owner of the company, and I think the idea is to use MaxQ for Evo phases 1 and 2 to provide instant in car timing. This would make Evo less dependant on local regions having to supply timing equipment.

The downside to the MaxQ is that the data is presented in a different style to most other systems. Not a big problem, if you only ever use MaxQ. Most all other systems use X and Y graphs, and present their data in similar formats making analysis between systems easier.

One really neat feature of the Race Technologies stuff is the Time Slip feature. You can instantly see the difference between two drivers, or two runs, and see where the one run is faster than the other.

I definitely want to chat at some point if you are a code monkey, because I see the oppurtunity to develop a program that would do a lot of the analysis automatically. I have plans to hold a local data analysis theory session at some point this season, probably in conjunction with the Generic gang.

[Chris_Swearingen]

Here are some examples of my data logging from last event.
From the beta software I am helping test. I may need to recalibrate my GTech based on the interesting map. Anyone want to buy some art?:p

It takes some fiddling to get a handle on what you are seeing and its a little hard to tell from the screen shots. I can tell better on the GTech pass software where I got ahead on the red(4th) run verses the black(1st run). You have to kind of guess where that was on the course with the GTech.

http://www.systemstrategies.com/miata/data_acquisition/axanalyst_run_1_and_4_April15.bmp
GTech PASS software
http://www.systemstrategies.com/miata/data_acquisition/gtech_run_1_and_4_April15.bmp

[Chris_Swearingen]

My best run in red ~.6 slower than Clay in black. Different styles, similar results up to about the red 42 second mark where I appearently lost speed in what I deem to be the kink before the crossover. Clay stretches out from there and I get just a little back at the finish.

I have some calibration problems with the Gtech, rpm is reading about 750 prm high, lateral and longitudinal g's didn't start at zero so you have to mentally shift the scale.
http://www.systemstrategies.com/miata/data_acquisition/ChrisRedClayBlack_29April.bmp

[Built-By-Bones]

Chris,

I am not familiar with the G-Tech stuff so correct me if I am wrong. I am assuming this is the system I see advertised on TV, and you are using their analysis software.

From the g-readings, it appears that the unit may not have been mounted exactly parallel with the vehicle centerline. Notice the disparity between left and right turns. On occasion the left turns will register slightly higher because of driver location in the vehicle. I could be wrong, and apologize if I am.

A note about the course drawing, this software displays the course in a format similar to the MaxQ system. All very well for novice users, but that display is terrible if you are used to any other form of data system. I cannot stand it when programmers try to present more information than is needed onto the display. Most data geeks agree that the the course map should be just that - the course map. Conventional X/Y graphs make it easier to read and understand data, and compare data.

I see the advantages of both, but honestly if you ever upgrade to another system other than the MAxQ you will have to "unlearn" those bad features first.

Grant