Data Logger

[MountainRunner]

I was reading Duncan's post on datalogging and thought I would share the info on my latest project with you guys.

I am building a race logger to compliment my Engine Monitor. You plug the two together and you get data logging onto a USB Key along with a heap more channels. If you have a GTR using my 4WD Controller you can also plug that in and log the LatG, LongG, 4WD Torgue gauge through the serial link.

You can use the logger stand alone if you have a different display or just want logging channels etc.

I am writing desktop software to setup the loggers and do the data analysis. Currently it does the full setup and creates EXCEL files for analysis. I will write the graphics analysis package once the hardware is all done.

I am on the second prototype of the design and am hoping to be testing the unit soon, its a progressive development of my Engine Monitor design so it has proven itself in the Auto / Racing environment (vibration and heat being the killers). Not having my car running the last few months has slowed down testing etc. ( did show a few guys the first prototype late last year at a track day, I am currently upgrading the processor and USB interface boards since that design).

Below are the basic specs of the units and a sample configuration for discussion.

I'd love to hear ideas and feedback on the project. (Tech only here, should have trader to represent me soon for other info)

Paul

Engine Monitor Goes up on dash for display. (Finished project)

Oil temperature

Oil pressure (option to profile alarm points with RPM, not just one setting of low pressure)

Water temperature

Intake temperature

R.P.M.

Battery voltage

2 Stage shift light

Warning light

Warning buzzer

Data logging output (data link)

Race Logger Pro (almost ready for testing)

Engine Monitor data link to log all channels.

4WD Controller data link to log all channels.

Plus:

6 Analog sensor channels

2 Wheel speed rate channels

2 Digital channels

1 Battery voltage channel

4 Digital output channels

USB stick memory - Log for as long as you like, just swap keys or use a huge one.

Race Logger Extreme (Race Logger Pro with expansion board - have hardware, write software after pro is finished)

Engine Monitor data link to log all channels.

4WD Controller data link to log all channels.

10 Analog sensor channels

2 Wheel speed rate channels

2 Digital channels

1 Battery voltage channel

1 Exhaust temp sensor channel

1 GPS data channel

1 Serial expansion channel

4 Digital output channels

USB stick memory - Log for as long as you like, just swap keys or use a huge one.

Sample Configuration Using all channels for hypothetical

Using the serial link from my Engine Monitor you can log:

Engine Mon, 2Hz, Water Temp

Engine Mon, 2Hz, Oil Temp

Engine Mon, 20Hz, Oil Pressure

Engine Mon, 10Hz, Intake Temp

Engine Mon, 20Hz, R.P.M.

Channel 1, 20Hz, Boost

Channel 2, 20Hz, Fuel Pressure

Channel 3, 20Hz, Steering Angle

Channel 4, 20Hz, Lateral G

Channel 5, 20Hz, Longitudinal G

Channel 6, 20Hz, Throttle Pos

Channel 7, 2Hz, Gearbox Temp

Channel 8, 2Hz, Rear Diff Temp

Channel 9, 2Hz, Front Diff Temp

Channel 10, 2Hz, Ambient Temp

Rate Channel 1, 20Hz, Wheel Speed 1

Rate Channel 2, 20Hz, Wheel Speed 2

Digital Channel 1, Lap Pulse (on demand)

Digital Channel 2, Brake Pedal (on demand if switch)

Thermo Channel, 10Hz, Exhaust Temp

GPS Channel, 5Hz, Latitude

GPS Channel, 5Hz, Longitude

GPS Channel, 5Hz, Speed

Battery Volts, 10Hz

If using my 4WD Controller you can plug the serial link into the logger and also log:

4WD Controller, 20Hz, Lateral G

4WD Controller, 20Hz, Longitudinal G

4WD Controller, 20Hz, 4WD Torque

[Roy]

Good work.

It may pay to have someone look at the appearance of the models. If its going to be a success then the real test will be how cool will the dashes look?

The wank value is half their appeal

These look cool but are pretty big and bulky

I went for the MyChron because it was within my budget and most importantly was compact enoigh tto be easily mounted on the steering column without having to play or remove the standard dash cluster.

Also, how hard would it be to get 4 wheel speed sensors? LOL...sorry about all this rambling. JUst so cool that you are able to do this

[Duncan]

what a great project! good luck with it, am happy to help with testing if you want too....

For me, perfect setup would be:

Dash shows revs with shift warning lights. big and easy to read. Also has Low Oil Pressure warning light, High Oil Temp Light, High Water Temp light (all nice and big). Speed and lap time is helpful if there is space.

Gauges show volts, oil temp, water temp, oil pressure, fuel pressure, afr, boost

Data logger holds 2 sets of interesting data

Speed, Revs, Gear, TPS, Brake, Lat and Long G, Attessa %, GPS position, boost, lap time for displays like trackvision.net

AFR, Oil temp, Oil pressure, Water temp, knock level from PFC, Revs, gear, voltage for tuning and engine health

Not sure how realistic that is, but for me that's how a state/club racer would want to use one. Real problem is I understand how much work and development goes into these, and if its over about $1200-1500 I think it wil be too expensive for all except professionals (who are running motec anyway)

[MountainRunner]

Roy you are right about wank value and appearance being half of the appeal, I have personally found this to be mostly true for less race orientated guys. The more serious a racer is the less they care about how it looks and the more interested they get in how it works. Stuff like readibility of the display, how the alarms are shown, what inputs are monitored etc.

Its interesting with those units above you will notice they are single colour (with good contrast) and have the info displayed in plain text except for the RPM graph. The warning LED's are simple and bright to get your attention. I view them as functionally well designed. If you look at other less race orientated electronics the market there want full colour screens that show pictures of your mates drifting, changable face plates for stylish looks, graphical gauges etc. Both valid ends of the market with different needs / wants.

The dashes shown above are at the top of the market and they cost accordingly. The full cost is sometimes also overlooked as there are many aspects of the purchase 1. Buy the unit, 2. Buy all the sensors you need (cost can vary a lot depending on what you want to monitor and the quality of the sensors you use), 3. Installation (if you cannot do it yourself), 4. Data Analysis Software etc.

My first project was my Engine Monitor. I built it after seeing guys loose their engines at the track and I didn't want to have the same happen to me. It monitors Water Temp, Oil Temp, Oil Pressure, Intake Temp, Battery Volts and R.P.M with two stage shift light. It is fast to react to alarm conditions and holds them for example high G cornering oil surge is a problem and your never going to see it on a gauge. Firstly your watching the road and secondly a dash gauge is too slow to reach. My engine monitor detects oil pressure loss in millseconds and will hold the alarm for 5sec so you can see it and acknowledge it (I have acknowledge button to silence the alarms, but display still shows condition).

Another thing engine builders say is that the low pressure alarm is often 2 late. It is set low so you don't have a continuous alarm when idling around. For example, say it is set to 10psi, when your on the track and start loosing oil pressure due to pump failure at 8500RPM you probably want to know before it gets to 10psi. So I added a feature that lets you plot 4 points of oil pressure vers RPM, so at high RPM you can get a warning as soon as something goes wrong.

The display shows the values of oil pressure, oil temp, water temp, intake temp. I try and get the guys to mount it above the centre console so you can glance at it without taking your eyes off the road. This is the safest and best way to use the unit. If an alarm goes off, glance left and the display reads "HIGH OIL TEMP" with the value, you press acknoledge button to silence and you correct the problem.

I have not designed my units to replace the car dash but to supplement it. Its been an interesting project. I have found guys who have lost an engine usually see the value much quicker than those who haven't. The unit doesn't datalog itself but has a laptop output for logging. It also plugs into the logger I am now building to expand the channels.

Here is a link with some install pics etc: http://www.timeattack.com.au/forum/viewforum.php?f=15

(Not as pretty as the above units but it does the job)

Duncan, I will be looking to work with a few guys who are likely to get out and use the unit to give valuable feedback. Your list of desired inputs are fine and are a subset of my above list to some degree (only PFC knock is difficult and gear selection you would calculate from RPM and Speed). My suggested configuration is only one possible way to use the input channels as they are just analog inputs afterall and can be connected accordingly.

[Sydneykid]

I applaud your efforts and look forward to the outcomes. Some random thoughts gleamed from over 15 years experience with data logging;

1. Sensors, plugs and wiring harnesses cost way more than the dash/logger itself. For example the Pi S3 dash and data logger in the Nissan SuperTourer cost $4K (inc software) while the sensors and harnesses cost $20K.

2. The real key is the software, track mapping, lap timing, segmentation, corner speed analysis, G Force hystograms, maths tables, best possible lap etc etc. That's what makes analysis possible.

3. Speed and ease of use of the software is very important, you need to be able to download the data and start making meaningfull analysis within minutes. Show the driver (if it isn't you) in a user friendly interface what the issues are and then make suggestions on what to improve. That's were you get the real benefits from data logging and analysis.

4. This is the best book on Data Logging that I have in my library, I strongly suggest that if you don't already have a copy, get one,

5. One of the best features I have found (as a driver) is the different screens. For example, during a race much of the information that I need is totally different to the information that I need in a qualifying (SuperSprint, Time Attack). One button push changes screens on the Pi.

6. That is followed by the simplicity of the display, for example I don't need to see the oil pressure displayed all the time. The only time I want oil pressure displayed is if it goes below a preset value (20 psi in my case), then the warning light flashes and it displays the reason for the warning. Displays that have more than 4 or 5 pieces of data permanently up are simply too hard to read. The KISS principle applies here.

For qualifying the default screen is the shift light and RPM bar graph of course plus the lap time, KPH and boost.

In a race the default screen is the shift light and RPM bar graph obviously, plus the lap # and the lap time that's all that really interests me.

In a car with sequential shift, we run gear position at all times of course.

Cheers

Gary

[MountainRunner]

Hi Gary, Thanks for your feedback.

The best info always comes from the guys with experience "at the coal face". My current Engine Monitor was finished until I had some racers use it. lol. You learn so much from these guys. For example, my monitor shows 4 values on the screen when all is ok, when there is an alarm it only shows the alarm condition such as "Low Oil Pressure". As you say using the KISS principal. The driver doesn't have to figure out what went wrong, it is there. We then added the acknowledge button to silence the alarms (light, buzzer) to stop annoying the driver once he has seen the condition.

The point about guys understanding the total cost of a logger is very valid. Most units are only priced as the unit. Any sensors past the basic temps are not cheap to add. Plus looms and connectors. The Engine Monitor I price with loom and sensors so all that is left is the install. But it makes it "seem" more expensive I think.

I have addressed the speed of data collection issue by using the USB interface. You plug a USB Key into the unit and it logs straight onto the key. At the end of a session you pull the key out and plug it into your laptop. No downloading required.

Gary, did the data rates I put in the example above seem right to you, are these typical of how you would setup your logger at a race?

The data analysis software will be the key and I think it will be a work in progress, developing it with the users and improving it. Currently the desktop software lets you setup the unit and it converts the data from the key to CSV format for loading into EXCEL. This allows basic data analysis and allowed me to do the debugging task. The next staep will be to determine the screens needed and start coding them up.

I have now ported the data logger to the new microprocessor and hardware platform. (very excited). So I will now be looking at doing a small production run for beta testing. Then have to start to define screens and get the analysis software underway.

Here is a picture of the Logger FYI.

[Sydneykid]

I can't remember all of the sampling rates as they vary from car to car, but in general what you have looks OK to me. In fact some are overkill.

20Hz, Oil Pressure - I use 10Hz

10Hz, Intake Temp - I use 2/5Hz

20Hz, Boost - I use 10Hz

20Hz, Fuel Pressure - I use 5Hz

That gives me more memory for logging suspension travel, we use 25/50Hz for that on the F3. The new Bosch loggers in the 2008 Dallaras are supposed to do 100Hz on the shock travel logging. That's import for the all important high frequency shock tuning.

Cheers

Gary

[MountainRunner]

Thanks Gary, I will have a look at letting 4 of the channels have high speed capability. That way it will be possible to do the shock logging if needed. I don't want to build any limitations into the system at this early stage.

Given what you have said above, I may make some of the channels only have slower capability (such as 5Hz, or 10Hz) thus freeing up the processor for the dedicated high speed channels. Or I might allow the joining of two channels to double the data rate.

Another option is to allow all channels to be set at higher rates and have a warning once the maximum system rate is reached. That could give the best flexibility.

I have almost got the GPS interface working which is the last step for the beta test logger. Once this is done and I implement the info from the above discussion I should be able to give final system specs.

Paul

[JimmyRickard]

I went for the MyChron because it was within my budget and most importantly was compact enoigh tto be easily mounted on the steering column without having to play or remove the standard dash cluster.

Also, how hard would it be to get 4 wheel speed sensors? LOL...sorry about all this rambling. JUst so cool that you are able to do this

hey mate just wondering how you have found this device so far. looking at getting a data logger and this seems to be the most cost effective. i had the same unit on my go kart and it worked pretty well. How much did you end up paying for it? And do you have any photos of it installed?

Cheers!

[Duncan]

good timing on the bump....I'm pretty sure Paul is sending out the first batch of these dataloggers pretty soon.

I have ordered one and am pretty happy with how they are looking

[Roy]

The MyChron Gold has been a good thing. Only catch was about a year ago i was flashing it with an update and my laptop battery died half way through it. The AiM usint doesnt protect its start of software, so it would nto reboot. I had to send it off to be re-flashed byt the factory in Italy

[INVRTD]

awsome thread, currently paticipating in my university open wheeler team, hopw to learn a bit from this thread, we use a motec setup and dash.

the plan is currently to add wireless telemetry so the driver can concentrate on driving notworrying about the engine etc

[JimmyRickard]

The MyChron Gold has been a good thing. Only catch was about a year ago i was flashing it with an update and my laptop battery died half way through it. The AiM usint doesnt protect its start of software, so it would nto reboot. I had to send it off to be re-flashed byt the factory in Italy

I rang AiM yesterday and they quoted me $1950 for it, which I think is ridiculous. The MyChron 4 on my Go kart was $600 and as far as I can tell it's not much different. The MXL dash is $1800 (without memory), and for a whopping 8MB you pay $2700. Are there any other cheaper alternatives? I need one with a display of some kind to give alerts on oil pressure etc. but spending anything over $1200 just seems like a waste of money.

[MountainRunner]

Your right Duncan. The first batch are now being built in Melbourne. I should have them pretty soon. I will update the specification on here shorlty as well.

The Display I am building is also progressing. It connects to the logger to expand the channels and add data logging to it. Plus it has the alarm outputs (light and buzzer) and 2 stage shift light. Again I will update the specs for it soon.

[Duncan]

and I'm willing to bet it is a bit cheaper than $2k too.

[MountainRunner]

Yes thats for sure. I want this unit to make data logging / dash display affordable to everyone. I have not crunched the final numbers yet as I'm waiting for build quotes etc. but it will be much better than $2K for the whole lot.

Also don't forget the price of systems does not buy you the loom / sensors or installation either !!

[MountainRunner]

Hi, Its been a while since my last update. Thanks for the prompt Darren

Last night the first RaceLogger of the first beta test batch of 12 units left my workshop and was installed into a daily driven test car. It will be setup over the next day or so and we will gather and check data. The plan now is to do a final check over this unit and once we see all is good the remaining beta test units will be released. This will probably happen within a week. There are testers on this forum as well as guys with other makes / models / experience of racing.

I have designed the setup parameters of the logger so that the intelligence of the user can be employed to get the best performance from the unit given their needs. This means that instead of limiting the capability such that if you turn everything on to maximum it will happily work fine but the overall system is restricted, the user can decide what is important and crank up that performance.

The current specs of the RaceLogger are:

Analog Data Channels:

Number of Inputs: 10

Voltage Range: 0v to 5v

Sampling Rate Options:

Channel 1 – 6: 2Hz, 5Hz, 10Hz, 20Hz

Channel 7 – 10: 2Hz, 5Hz, 10Hz, 20Hz, 25Hz

Moving Average: 2 Sample Moving Average Option

Calibration: 12 Point Calibration

Serial Data Output: Off, 1Hz, 2Hz (for display on EM PRO II)

Channel Configuration:

4 x Sensor Driver Inputs (1k internal driver)

6 x Voltage Sense Inputs

Included 5v 100mA supply for use with powered sensors.

Rate Digital Data Channels:

Number of Inputs: 2

Voltage Range: 0v to 16v (car battery)

Sampling Rate Options: 2Hz, 5Hz, 10Hz, 20Hz

Rate Modes:

Pulse Counter (fast rates)

Pulse Width Measure (slow rates)

Output Divider: Pulse divider (1 – 32)

Report Type:

Pulses per Second

Pulses per Minute (RPM)

Serial Data Output: Off, 1Hz, 2Hz (for display on EM PRO II)

State Change Digital Channels:

Number of Inputs: 2

Voltage Range: 0v to 16v (car battery)

Sampling Rate Options:

2Hz, 5Hz, 10Hz, 20Hz

Low to High Edge

High to Low Edge

Change of State

Report Option:

+v = 1 (normal)

+v = 0 (inverted)

Serial Data Output: Off, 1Hz, 2Hz (for display on EM PRO II)

Battery Voltage Channel:

Voltage Range: 0v to 16v (car battery)

Sampling Rate Options: 2Hz, 5Hz, 10Hz

Serial Data Output: Off, 1Hz, 2Hz (for display on EM PRO II)

GPS Data Channel:

GPS Input Module Values:

Lateral Position

Longitudinal Position

GPS Speed

Sample Rate: 1Hz or 5Hz (depending on module)

Logging Memory:

Data is logged directly to a USB memory stick.

Logging Options:

Start Logging:

On Power Start New File

(Starts new file as soon as logger has power and has booted)

On Time Delay Start New File

(set time delay in sec after power-up: 1 to 60sec)

On RPM Start New File (set RPM start/stop threshold)

(RPM must be on Rate Channel 1 or from EM Pro II)

On Speed Start New File (set Speed start/stop threshold)

(Speed must be on Rate Channel 2 or from GPS)

Laptop Interfaces:

USB: Connect using USB to Configuration Laptop

RS-232 Serial: Optional to connect using EM PRO II port to Laptop’s without USB

Alarm / User Outputs:

Digital Outputs: 4

Output Type: Open Collector to Ground

Alarms:

Less than value alarms can be set

Greater than value alarms can be set

All Analog Channels

All Rate Channels

Digital Channel alarm in a state

Operation:

Assign the alarm condition to any of the digital outputs. Alarms can share digital outputs.

Alarms can turn on from one to all four digital outputs.

Data Link Options:

Ruzic Engineering EM Pro II

Serial communications link to the EM Pro II

Add EM Pro II data channels to the data logging of the Race Logger.

Race Logger uses the EM Pro II screen to display additional information.

Sampling Rate Options: 1Hz, 2Hz, 5Hz, 10Hz, 20Hz

All of the EM Pro II Data Channels can be logged by Race Logger:

Additional EM Pro II Features:

2 Stage shift light

Warning light

Warning buzzer

Alarm acknowledge button

Ruzic Engineering 4WD Controller

Serial communications link to the 4WD Controller.

Add all the 4WD Controller data channels to the data logging of the Race Logger.

Sampling Rate Options: 1Hz, 2Hz, 5Hz, 10Hz, 20Hz

4WD Controller Data Channels Logged by Race Logger:

Lateral G Force

Longitudinal G Force

4WD Torque Split Reading

[djr81]

Link to a relatively new release. It has some handy features - mostly the bad lap/good lap/best lap idiot light which may be useful for qualifying, sprints etc.

http://www.starlane.com/en_news.htm

For what little it is worth, IMHO the most useful parameters for a data logger to analyse driver behaviour are:

GPS coords, ie lat & long but also heading if available. This allows you to work out accelerations but needs atleast 10Hz logging rate to work well.

RPM.

Throttle % (easy to get out of a GTR as it feeds the ATTESSA system)

Steering wheel angle (Again already used on GT-Rs)

Torque split.

This lot will tell you a great deal about car behaviour & enough about what the driver is doing to affect it. Having some functionality in the logger unit itself to assess the current lap you are on can be a great help too. Mostly this involves sector splits & tracking whether the lap you are on is ahead and/or behind & by how much.

Good software is also critical.

Best of luck with it. Your ATTESSA controller is a nice bit of kit & works well.

Edited October 9, 2008 by djr81

[Rekin]

sounds very interesting any updates on it?

Im looking for a unit which can monitor oil temp, water temp, oil pressure sensors.

Will you be producing any sensors for oil pressure etc?

[Duncan]

yes mate it does all that, and Paul has chased down a couple of options for sensors that are compatible. I am waiting on data logger and engine monitor for my race car, sounds like he is making good progress getting them all sorted out