I have a few friends who use Traqmate, G2X, and a few other systems. Has anyone found a good way to compare data from various systems? A software package to do the top 3 or 4 would be great if anyone wants to write one.

 

Marty,

I've talked with both Racepak and Traqmate about doing this exact thing. Long story short is that while they CAN do it, they aren't going to as having independent data file types helps sell units. Sucks, but it is understandable.

 

I have seen that both (plus a few other companies) do export the raw data to CSV. Maybe I can work up a template to atleast graph it there.

 

There does appear to be a software package that will take almost all formats called Dashview, but I've never used it before.

 

What data are you looking for ?

As far as raw data is concerned, they'll be pretty much equal.

The deciding factor should be the analysis software. If you can't use it easily, it'll be a waste of money.

I have the Race Technologies DL1. http://www.race-technology.com/description_8_956.html

Download the software for free. I have some track data for you if you want.

 

right, raw data is easy, and almost all export to csv with several common factors like GPS location and bearings.

What I have been trying to find is analysis software that can either take several types of binary files (TQM, BIN, GXP, VBO, etc) or can take the raw data and provide a good interface for comparison.

BTW, to date I found TraqVision (also free) to be the easiest tool with a heck of a lot of power right out of the box, but still doesn't support other system imports.

I am now working with a software engineer (not Traqmate) now that may have something soon. I'll keep everyone informed. So far he has gotten Racepak, Perfomance Box, and most of DL1 files working. He has also gotten OBDII data sync working. This will run on PC or Win M 6.1 smart phones.

 

Well, as I said over on SCCAForums, I'm updating AXAnalyst to support Traqmate files and GPS velocity CSV files, and it already supports accelerometer-based CSV files.

I agree with Kolia -- if the software takes work to get the essential information, then it's distracting from the process of getting the information. AXAnalyst is designed around the ideas that you don't have a lot of time to review a run before your next run (I've used it at practice days where we've only had 12 cars in a run group) and you don't need to have another driver to compare against (the main selling point for GPS-based systems, as far as I've seen).

If it just becomes another "gadget" then you're wasting your money. I use AXAnalyst to help me find where my errors are and to help me drive better.

 

I didn't realize it was you.

I found several packages that will allow comparisons of segments, total laps and overall gps and accelerometer data. But they require their own propriatary formats. It would be great if there was one that did it with ease with raw CVS data.

That's why I am starting to work with another author who has a similar product already out. How's the AXAnalyst going?

 

It's working really well for everyone who is using it. One person who has recently gotten it has reduced their "deficit" to their competition by something like four seconds since they started with it about 6 weeks ago.

I'd like to support more "native" formats -- and better yet, the devices directly (I already do that with the GTechPro RR). I've already got "generic" acceleration CSV support, and am adding "generic" GPS velocity CSV support (and specifically Traqmate CSV support).

Having the data is important, but if the software gets in the way, it's useless. At this year's Packwood NT, my co-driver and I were both able to quickly address areas for improvement between our first and second runs by looking at the data (but I'm much more familiar with the Z's capabilities and its "feel" so I did improve a bit more). I originally "tuned" the software by running at a practice with only 12 cars in a run group, and I was able to take care of all of my "normal" stuff (tires, engine) plus retrieve and analyze data directly from my GTechPro (which is why I'd really like to directly support more hardware, since most software requires quite a few steps to get data into a usable form).

I think that AXAnalyst is the quickest and most intuitive software available, and my customers seem to agree. So far, it has been able to "coach" me to be a significantly better driver -- and I can say that because the tutorial runs (where the software teaches you what to look for and what *not* to do!) come from my runs recorded early in 2007 -- and in 2007 I pulled myself into 10th place in the nation (15th after day one) at the Solo National Championships. I had a great co-driver (first350), but more importantly, I had the data that told me where I needed to improve after my first -- and second -- runs (and that was even with the "abbreviated" time in grid due to the distance between the grid and course).

While the video version does take a bit more time, that is primarily because it takes advantage of equipment that you probably already have, rather than forcing you to purchase specialized equipment (generally for a LOT more money). I've found the data-overlaid-video useful as well for more detailed examination (and later sharing). For a camera, I've used a Sony Handicam, a Canon DV camcorder, and this year I'm using a Sanyo Xacti -- basically I've "graduated" to progressively lighter cameras. I put the camera in the back window so that I can see what I'm doing and align that with the data. I've also set up the camera so that I could use the rear-view mirror to watch my eyes in order to verify where I'm looking as well.