That's not good. Let me have a look.

 

Our current merchant system supports VISA and Mastercard only. Diners will be supported when Europe starts buying. The up-front and recurrent costs to support Amex were extremely high, so we chose not to support Amex, initally at least.

Norm,
We have some significant changes in the works to support AIM. Its impressive that you have uncovered most of the wrinkles with the AIm data. Our release support will do the parsing without requiring the user to go as deep as you have gone!

 

Tony,

Thanks for the info. I look forward to your upcoming release.

Norm

 

Tony, Greg,

Another question. I now have the AIM part working where it shows speed, rpm & g properly.
But lap times do not get displayed. I am guessing that it has to do with the fact that I now have linear continuous time meaning each lap does not restart at 0 seconds. I had to do that to make the current setup work. So how does it determine a given lap time ? Does it take end time minus start time ? Using distance reset to 0 to note when the lap has ended ?

Thx,
Norm

 

Norm,
The AIM lap time problem is one of the AIM-specific issues we need to solve for v1.2.
We have a considerable group of features based on an accurate track map and on knowing position on track for every data sample. This is easy with a GPS-based system like RaceTechnology, but not so easy with AIM where there are two limitations:
- AIM approximates postion based on speed and lateral G
- AIM does not output the xy coordinates that result from their approximation.
There are a few approaches that we can use to generate lap time, and we are testing the error potential for several to decide which is the best to use. More on this as we progress toward a solution.
Remember that the new support features for AIM will preserve the lap time numbers in the AIM data. We simply increment out timestamp to generate a linear time increment, but the lap time numbers are still available for us to use.

 

Tony,

Makes sense.

Thx,
Norm

 

Guess I'm jumping in a little late but I was in Indianapolis this whole past week. We would be interested in doing more to get your product to work with MoTeC data, so please email me and I might be able to assist. I don't have much video but tons of data. We also have a new software analysis package coming out this year and video is on the list of things to include. Since I can't get you the exact .ld file information you'll either have to export data via .csv or we could program a converter for you? I have a contact person for you in Australia that can help.

-Christopher
chris@motec.com

 

Chris:

Would you be interested in starting a discussion on things we would like in data analysis? If yes, I'll start a new thread.

 

This is of interest to me as I have a Motec but many of the guys are also using AIM. We would love to be able to overlay and compare data between drivers but currently cannot. I appreciate any help in this area very much!

 

Chris,
Thanks for the offer. Your CEO was fairly insistent that we continue the discussion started at PRI. WIll email you to get the ball rolling.

 

CC,
I think you might see that change in the GCircle behavior that you wanted. No promises, but you can be sure we have taken a look and have a plan for v1.2.

 

Not THAT would be a great product/tool. Comparing data is one of the best things you can do and to be able to do that cross-system would be a real hot button for a lot of people.

That said, I believe that MoTeC has a tool for that. Any comments Chris?

 

For data analysis you might want to visit this discussion group:
http://p081.ezboard.com/fs2racingfrm4
It is a data acquisition discussion group setup by Veracity Data.

Comparing data between a fast and a slow driver is very eye opening. Almost all data systems can do this.

As for Motec, we have a new analysis program called I2 coming out this year. It was shown at PRI. Video is something that will become integrated but won't be ready till summer time. Until then we would like to find other solutions, and perhaps these might be solutions we can integrate. I know many other systems do this currently but no one does it perfectly, as there are many ways to go about it.

Chris Brown
chris@motec.com

 

All,

fyi...

Here is more detail on the new AIM CAN Bus video overlay system. This is directly from the hardware and firmware engineers at AIM :

Norm

"Hi Norm,

Maybe I was around to take a look to ur competitor...
The video system (DAVID) is at the final stage of
production. It takes two cameras and record on an
external unit (your min-DV camera for example).
DAVID also takes input from digital / analog channel
and from an ECU (we support many ECU but your
need to be compatible).
The data recorded can be downloaded with our Race
Studio 2 software. We'll also produce a version of
DAVID without the data logger. This version is cheaper
and will be usefull fo our customer that have a data logger
(for example for that already have an MXL).
All this should be ready at the end of February.
For further details please ask to Ivan Spagnolatti
and Ale Corti that are the designers of DAVID.

Bye, Ivan"

 

Yaaaaaahoooo!!!! Too cool!