Data loggers. What do you use?

[Justo]

I'm looking a buying a data logger to use for track days and maybe even hill climbs. I figure that there is far more to be gained by tuning my driving technique and current set up than by spending money on go fast bits.

I'm after something that can do timing, measure g forces, compare different runs and is easy to use.

I like the race technology DL1 (http://www.race-technology.com/dl1_2_27.html). I have download the software and had a play with it and it works really well.

I am not a pro race team so my budget is about the $1000 mark (the DL1 is about $1500).

Has anybody got a DL1? what is it like?
If not what are you using and what do like or dislike about it?

[neal]

Mate try the tech section you will get more responce there

[big_zop]

I am interested in doing something quite similar so have done a little bit of research on the topic. Not being able to find suitable data loggers has been my major issue so i have been limited by this.

What i have done is create a spreadsheet that lists all the parameters you are after so that you can see what everything offers across the board, along with a list of what you want and need and take into account anything in the future. Then put what your wants/needs are in terms of dollars - like cost per input, displays, data storage and capacity, software and it should help.

One system i found quite useful and cheap, especially if you dont need as many inputs is the Traqmate V2.10 from www.traqmate.com . This system uses a GPS based track beacon which can be set on the spot with the complete version or in the software for the basic IIRC. The best part about the Traqmate is that it is easily set up for open ended tracks (tracks with a different start and end point) ie hillclimbs, and I cant seem to find much on the DL1 being able to do so.

While you might be able to get by on basic measurements that you mention (g-force, speed, times), you will find that once you get around the volume that more information will help you. One thing that may help you out with understanding data is to play a racing simulator that can allow you to log the data from a race. I did this for my thesis to look at driver performance with GTR2 which outputs data that can be read by the Motec i2 program (which was handy because our FSAE team used a Motec ECU). Having all the information already available makes it easy to tell if there is enough on your car to give good analysis - like seeing individual wheel lockups or poor throttle control causing excessive wheelspin or if they are lifting through a crest, too much steering angle input causing excessive slip angle on the front tyres.

[DX20VT]

I use Performance Box,

All GPS based and works really well.
Logs speed, laptimes, g forces, etc,
and the program that comes with it lets you overlay laps over each other,
and heaps of stuff.

And am just about to upgrade the Link ECU in my car to enable data logging of the engine control stuff too, which will be good to play with.

[merc-blue]

spend a grand on a driver training day, you will gain more than a logger will. particularly a cheap one.
I have done 4 driver training days with various clients and can assure you will gain more with a day of tuition than a lifetime looking at data from a base DL1 setup

just because you can pull data out of the car doesnt mean it will help.
you need to be able to interpret the data and also than make the correct changes not car setup and more difficultly your style.

IMO performance box is a gimick. you want wheel speeds steering yaw TPS and wheel position sensors not the data a performance box can give you

you can feel more than enough of the cars dynamic to setup the car for even racing a state or national series, more car speed will be gained in making sure your car is doing what your are expecting it to be doing under you than trying to tweak it so it does.
EG have you mapped your wheel position? do you understand your front geo?
Getting into data is a stepping your game to a new level and if the basics arent spot on yet you will just be going in circles confussing yourself

[DX20VT]

IMO performance box is a gimick. you want wheel speeds steering yaw TPS and wheel position sensors not the data a performance box can give you

Probably is, and I only really use 1/2 the features,

main thing I use it for is laptime on the go,
and for analysing why some laps are fater than others, by seeing what corners I went thru to slow compared to my fastest laps.

[merc-blue]

Yeah thats all its useful for. aspt that i dont see it as a real logger,
You cant really tell why you were slower through a corner. i normaly can remember mistakes i make
But when you want to know the raw basics of what made you faster througha particular corner or section that proper logging is required.
EG a performance box cant really tell you that on your slow lap you braked late and started turning in a touch early with still a small amount of brake pressure applied
and you understeered slightly which pushed you wide of the apex and killed your run out because you had to wait for the car to come around before getting on the throttle.

But then again you would preobly be able to remember that coner and have felt the understeer and known you probly brakes abit to late you wouldnt know the exact amount by which it happened but you would probly have felt it.

At club level stuff. track days hillclimbs (in aus) etc.
Felling understeer in a corner and knowing you need to make a change to the car or yourself to rectify it i feel is enough.
where as to properly diagnose the issue
Is a very expensive full data setup, and further still your car may not be equipt to make the changes nessicary at the accuracy which the data prescribes

By all means if you want to keep track of individual laps and have some record of them because you lose your memory in the moment its a great way to jog your memory and help you disect each gear change and application of brakes.
But as far as being a tool to prescribe changes to your car or style your going to need to spend a decent wad

[amichie]

I use a little national instruments usb a/d gadget. Runs upto about 48ksps and has about 4 * 12bit analogue and 8 digital channels.

[Justo]

big_zop: I haven't seen the traqmate before, I'll have a look at the specs. I might do the spreadsheet idea like you have done to make it a bit easier to collect and compare info.

Dx20vt: I have haven't looked at the performance box as I was told by sum one I know that they weren't totally happy with it. his words were "It does what I want, but I probly wouldn't buy one if I had the choice again".

merc-blue: I agree with you about the driver training, perhaps I should start there and then invest in a data logger (both at the same time would be interesting but I'm unable to afford that). I do still think that a data logger would be a good way (after driver training and driving time) to help to improve my skills as I know how to interpret the data and I know people that can give me advice if I need help.

An engineer of a fujitsu V8 team once told me "Theres no point in putting the car on the track if we are not collecting any data on what is happening to it. Even if the car comes last or doesn't finnish at all we are still able to collect usable data to improve for the next session". I figure that data you can refer back to and compare is better than trusting the old ass dyno.

[DX20VT]

An engineer of a fujitsu V8 team once told me "Theres no point in putting the car on the track if we are not collecting any data on what is happening to it. Even if the car comes last or doesn't finnish at all we are still able to collect usable data to improve for the next session". I figure that data you can refer back to and compare is better than trusting the old ass dyno.

Probably true,
but also no point collecting data if you have no idea what to do with it afterwards.
I have done a bit with complex data logging on Motec etc etc,
By my capabilities are to wire it up, set it up, download it and display it on the screen.
I have no idea on how to read it and tell what adjustments are required to make the car better, so for me all that stuff is no good. And I only run in a class a bit up from club level,
nowhere near NZV8 or championship class status.

What i can change is my driving style, as I have had a few scares on a couple of corners at tracks, and just need to regain confidence in the car and not lift off on a couple of corners, and I will lower my personal best lap record again.

So the best bet is to decide what you want to log, why you want to log it,
what you can do with the data you have gained,
and then buy something to suit.

[MWP]

I use a little national instruments usb a/d gadget. Runs upto about 48ksps and has about 4 * 12bit analogue and 8 digital channels.

Tell me more...
What do you monitor with it?
What does the software allow you to analyze, or does it just dunp data you need to then graph in excel, etc?

[merc-blue]

An engineer of a fujitsu V8 team once told me "Theres no point in putting the car on the track if we are not collecting any data on what is happening to it. Even if the car comes last or doesn't finnish at all we are still able to collect usable data to improve for the next session". I figure that data you can refer back to and compare is better than trusting the old ass dyno.

Totally different game, i never sent a duratec formula ford out on a testing day without data.
But i dont spose you have a spaceframed, perpously built race car do you?
You will be tracking somthing that initially was designed and built for the road.

Im a true beliver that the best way to get faster is spend time with your ass in the seat and getting guidance from blokes who are fast.

I took a mate who is a very very fast driver and has been racing for over 20 years around winton and he gave me a 2 hour debrief and notes about improvements to myself, after only about10 laps.
I had made no adjustments to that car previous to that it was only setup to what we belived would be a pretty neutral setup.