The Bosch 2.2 software was truly hideous. However, the 3.1 system as a whole was a vast improvement. CF memory storage made data downloads much easier than download leads and what not. A straightforward swap of CF cards allowed the car to be back on circuit without waiting for data to download. The WinDarab software was a huge step forward and supported pretty much everything you'd want to do. What was most impressive though, was the Bosch ECU and chassis hardware (great build quality) and its integration with the Bosch range of software, especially if you also used Lapsim. Its biggest drawback was its high cost and use of dongles.
The AIM software is very good, especially being free. MOTEC, as you say, is very engine oriented. I haven't used Digitech. Stack and Astratec aren't really worth discussing anymore, AIM far surpass them in the budget market. Pi is very good, but can't really compete in the budget market. A Pi2 is not even close to AIM's low-end products.
Back to karting and I'm of the opinion that AIM have the products best suited and best priced for the market. What you need to ask yourself is what data you will find useful, and what data you can record come race day. I always found track maps of limited value but g-force traces essential. For karts I'd be looking at (in this order):
Engine Revs Laptimes Water Temp (if water-cooled class and allowed) Head Temp (if air-cooled class and allowed) Lat/Long G's
The rest would be great but not essential:
Wheel Speed (front wheel pickup, rear wheel speed can be calculated on a maths channel) Throttle Steering Brake Pressure
On one of our race cars we had strain gauges. It would be great to position these on the rear axle and various areas of the chassis, if only as an academic excercise. From an "advanced" point of view, the ability to add custom sensors and plot their repsonse is invaluable. The AIM range of products support this (assuming the channels are available). I'm not sure about the other karting products.
Dave
|
|