MountainRunner

Hi, Just go to the website www.TimeAttack.com.au and fill out the Join Now page. That way I will get all the details I need. Also if you want, send me an email to pruzic@tpg.com.au and I will send you the booking info. Hope to see you there. Paul

When I was speaking to Keith he asked me to make it street cars and under 92db. I guess if you had a race car that was at that level it might be ok. To clarify all these questions etc, I asked Keith to setup noise testing at my March 25 track day. So the guys who are booked into that day can get their cars tested and clarify any questions. Paul

Only 3 weeks to go. Still spots for anyone who wants to get involved.

There are noise restrictions and it is for street cars only at this stage.

Hey Guys, I have been talking to Keith from Queensland Raceway and they are planning on having the calendar for Lakeside sorted out late next week. At this stage nobody has been given any firm dates. The Time Attack day will be the next private track event held at Lakeside. We are also up the top of the priority list for dates this year. Paul

Congrats, sponsorship will help you focus on the sport and sharpen the skills !!

Round 2 will be run in the afternoon of the March 25 track day on the SPRINT Circuit. Don't forget you can drop a round on the Sprint track and a round on the Clubman track and still be in for full points, so its not too late to get involved. We have finalised the series sponsors and every driver will be getting a free 100% cotton long sleeve T-Shirt. The series logo is embroided on the front with the sponsors logo's screen printed on the back. Should look great. The points from Round 1 are below. The EVO guys attacked the series hard in round 1 with 15 starters and took the top 5 spots in street class. Many of the Skyline guys didn't have cars ready in time. Hopefully round 2 will see a balance of the results. If your keen to get involved, go to www.TimeAttack.com.au and click the Join Now link. For full details on the series Click This Link For full details on round 2 Click This Link ROUND 1 RESULTS AWD RACE CLASS 12, 0:59.67, RN, Russell R32 GTR 10, 1:03.53, MG, Mathew R32 GTR AWD STREET CLASS 12, 1:02.61, BC, Brendan EVO IX 10, 1:02.69, MR, Mark EVO IX 09, 1:02.83, TY, Terry EVO IX 08, 1:03.51, RL, Rohan EVO TME 07, 1:04.92, MS, Mick EVO IX 06, 1:05.12, NW, Nathan R34 GTR 05, 1:05.58, SA, Shane GTiR 04, 1:06.02, BC, Ben EVO III 02, 1:06.94, RD, Robert EVO TME 01, 1:07.06, IB, Ian WRX FORCED INDUCTION STREET CLASS 12, 1:05.78, JC, Jenny 911 Turbo 10, 1:14.70, AR, Anthony 180SX

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

Yes I saw those units also, they are in the current issue of Racecar Engineering magazine. Its a pain they don't have logging as it takes away from the usefulness of them. It is like the in tyre pressure and temperature system you can get now with the mini transmitters in the valve stem. Again no logging. I will be attacking those in the near future as well so they log into my system. Having said that, the $300US is still heaps cheaper then the individual sensors that you would usually buy at several hundred each. Especially if you do all 4 corners at 3 sensors a corner. But on the other hand, the $300US one would be difficult to use if you wanted to log all 4 tyres at once as you would have the 4 screens on the dash. You definately would have to video them then.

You like those pics, check these out. Got the rest from the photographer. http://www.timeattack.com.au/forum/viewtopic.php?p=659#659

Here is a link to a bunch of pics http://www.timeattack.com.au/forum/viewtopic.php?t=165 Keep an eye out in that section as the photographer I hired should have more images up there shortly. Paul

Hi Guys, Another one of my projects is progressing so I thought I would put up some info for discussion. This is a three sensor tyre pyro for measuring the surface temperature accross the tyre tread as the car is racing. This is used to setup the camber, as you have live data at each corner and the straights of the race track. The problem with measuring the tyre temps in the pit lane is that most info is lost as the temp has equalised accross the tread. For exmaple, look at QLD Raceway, turn 1 could be the most important on the outside left, but you have 5 other turns plus the pit straight by the time you measure the temps, so all data for turn 1 is lost. (I am not saying it is not also valuable to collect tyre temps in the pits as this gives other valuable data on tyre useage). You need three sensors per tyre (possibly 4 if the tyre has a large deflection on the rim under heavy cornering loads) to measure the temperature movement on the tread. Plus its usually a good idea to measure surface temp as well for reference. The unit I built has three sensors (see at the bottom of the pic) which go into the processor box that outputs serial data that goes to a laptop or my race logger. You would use one per corner of the car for a full setup. Here is a pic of the prototype. I am hoping to test it on a car soon.

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.

Check out the pictures I have so far of the day http://www.timeattack.com.au/forum/viewtopic.php?t=165

I was talking with QR management today and they no longer take the LS2 CAMS license. You need to have the AASA license which you can buy on the day from the front desk. See you guys tomorrow.

lol, thanks for that. I will get the record updated.

Ryan its Qld Raceway. Currenty the only track we run at until Lakeside becomes available. Paul

Yes all rounds are on weekdays, the calendar has been updated on the website for the year: 2008 Series Calendar If you think you can make it to a round sometime during the year let me know in advance so I can secure you a spot. Also, anyone who has run with us in the last few events, the Hall Of Fame and the Top Ten have now also been updated. Paul

Hey Russ, how did you go getting the R32 ?

I had this posted in the QLD / Events section but after spending more time here in the motorsport section I think it might be a more appropriate place to post it. Round 1 is only just over a week away on Tuesday Feb 5. I have also added Motorkhana to the event and it will be run all day in the carpark between the pit bays and the sheds. For those who remember my big electronic sign and timing beams I have converted that system to do Motorkana so the crowd can see the elapsed time live. Time Attack Series 2008 Event: There will be a 6 round series, requiring each driver to complete 3 Sprint Track Rounds and 3 Clubman Track Rounds. There will be 4 half track days for each of the clubman and sprint tracks that will be eligible for points. The best 3 of the 4 of these half days completed by a driver will count as point’s rounds for that driver (A driver can miss a round on each track and still be competitive). (The series is points based; therefore all drivers are welcome to any event as always) The winners of each class, and the place holders, will be presented trophies at the end of the year. Class Structure: A: Street Class B: Open Class Division 1 (A, B): AWD - Battles of GT-R vers EVO vers WRX vers GT-4 etc Division 2 (A, B): Forced Induction - Battles of 4/6/8 Cly 2WD Turbos, Rotaries, Skylines, BA's etc Division 3 (A, B): V8 Naturally Aspirated - Classic Ford vers Holden with some Toyota power Division 4 (A, B): Naturally Aspirated ( but not V-8 ) - All 4 and 6 cylinder cars including Rotaries General Rules: Nitrous prohibited. Roll Cage Permitted in all classes. The same driver must drive the same vehicle for the duration of the series. The combination of vehicle and driver shall collect points. Modifications must not be made which reclassify the vehicle during the series. Points are not transferable between classes. A: Street Class: The Vehicle must be constructed by a major manufacture. Must have a rear exiting exhaust system with a muffler. Must be road registered. Must have OEM glass. Must have OEM doors. Must have both front seats (can have a race seat and a standard seat) and basic interior in the front half of the cabin. (Removal of carpet, stereo etc and liner allowed but not the dash) Must not have in cabin adjustable brake bias / pedal box. Must have DOT approved street legal tyres. Tyres must not have “For race use only” or “Not for highway use” marked on them. The tyres cannot be grooved slicks etc (See tyre register thread for further details) B: Open Class: All cars that do not fit into the Street Class and comply with the general rules. Points Allocation: 1st = 12 points 2nd = 10 points 3rd = 9 points 4th = 8 points 5th = 7 points 6th = 6 points 7th = 5 points 8th = 4 points 9th = 2 points 10th = 1 point A minimum of 5 laps must be completed at a round to be eligible for points. Tyre Register: For the street class tyres must be grooved and some wet weather capability. Slicks are allowed in race class. There is a tyre register so there is no confusion as to what category a tyre belongs. Click this link -> http://www.timeattack.com.au/forum/viewtopic.php?t=139 If you have a tyre that is marginal please contact pruzic@tpg.com.au for a ruling. Otherwise you may be reclassified on the day. Rulings: The organisers decision shall be final. No dispute shall be entered. First Event: February 5 Want to Get Involved, fill out the Join Form at: http://www.timeattack.com.au/mailing.php And I will email you out all the details.

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.

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

Excellent. We need more GTR's. I have 15 EVO's booked on the day now. Can't wait to see how the motorkhana goes as well. The idea is that inbetween runs on the circuit you can do a motorkhana run as well.

Sounds like a plan. The EVO count keeps going up, those guys want to dominate the AWD class. I am also going to run Motorkahna at the Feb 5 track day. I have converted my electronic timing system from lap timing to khanna timing. I have a beam for the start, and another for the end. Timing at 1/1000 of a sec. Plus my big electronic sign will show the elapsed time live to the crowd.

The guy I use is down the coast. PM me if you are after the details.