My 3.4 DOHC powered red and black camo '88 Fiero Track Car
Moderator: Series8217
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
New seat! Got a Sparco Evo to replace my very very old (1999 build date, I think) Sparco Rev.
I also put new upholstery on the Corbeau A4 on the passenger side. Went from red seats to black ones. I might do custom upholstery at some point to spice things up a bit, but I'm liking the black for now.
It weighs 21.3 lbs including my 3mm thick steel mounts. I designed these mounts in CAD. First I test-fitted the seat with some cheap Amazon.com mounts, then I 3D scanned the seat and temporary mounts, designed the new brackets, and had them lasered and bent by Send Cut Send.
I also put new upholstery on the Corbeau A4 on the passenger side. Went from red seats to black ones. I might do custom upholstery at some point to spice things up a bit, but I'm liking the black for now.
It weighs 21.3 lbs including my 3mm thick steel mounts. I designed these mounts in CAD. First I test-fitted the seat with some cheap Amazon.com mounts, then I 3D scanned the seat and temporary mounts, designed the new brackets, and had them lasered and bent by Send Cut Send.
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: Track Days in the DOHC Fiero
Back to doing autocrosses and track days in my 88 this year. Since the last time I tracked the car, my setup has changed from 215/275 staggered Hankook RS3s and 12" rotors with stock calipers, to 265/315 staggered Nankang CR-S, C7 Brembo brakes, custom front and rear uprights, and Conti MK60E5 ABS.
Last weekend at Buttonwillow was overall very very wet but I had a few dry sessions on Saturday morning. My first session was refamiliarization with the track and learning the new characteristics of the car. By the middle of the second session I was really starting to pick up the pace and had a lot of confidence in the new setup.
I was set to probably run a new PB for the #13CW configuration: I ran flat out from Bus Stop to the braking point for Phil Hill then flat again until the braking zone for the sweeper. Soooo much grip. Then as my eyes scanned right to find the exit curbing I noticed a giant smoke cloud in my rear view mirror.
I pulled into the hot pits to find a film of oil on the muffler and most of the rest of the engine bay, but no obvious source.
Back in the paddock I took off my helmet and race suit and got a better look under the car. A constant stream of oil was pissing from the right side of the pan.
Turns out the one drop of oil per day I've had on my garage floor from a leak I can never find was actually a crack in the pan where an internal baffle is spot welded to the exterior metal. It broke through completely and went from a drop per day to a couple liters per hour.
I was able to jack up the car at an angle enough to get the oil level below the hole so I could clean it with brake cleaner and JB weld a patch. Found the perfect patch in my tow vehicle: a single Chinese Yuan coin. I borrowed some JB Quick from 7s Only (the race shop at the track), glued the coin over the hole, and then the rain came. I never got another dry lap all weekend.
Still, the car was great in both dry and wet. ABS on a Fiero is phenomenal. I truly believe the Mk60e5 is a race ABS system even without the "motorsports flash". I never felt it was holding me back, and even in the wet I could stab the brake pedal hard and trust that the system would find the grip wherever it was.
The Nankang CR-S is a pretty good tire but it is definitely not a rain tire. By Sunday the track was mostly flooded and the rain was pretty much constant all morning so I packed up and headed home to dry off and clean up.
Last weekend at Buttonwillow was overall very very wet but I had a few dry sessions on Saturday morning. My first session was refamiliarization with the track and learning the new characteristics of the car. By the middle of the second session I was really starting to pick up the pace and had a lot of confidence in the new setup.
I was set to probably run a new PB for the #13CW configuration: I ran flat out from Bus Stop to the braking point for Phil Hill then flat again until the braking zone for the sweeper. Soooo much grip. Then as my eyes scanned right to find the exit curbing I noticed a giant smoke cloud in my rear view mirror.
I pulled into the hot pits to find a film of oil on the muffler and most of the rest of the engine bay, but no obvious source.
Back in the paddock I took off my helmet and race suit and got a better look under the car. A constant stream of oil was pissing from the right side of the pan.
Turns out the one drop of oil per day I've had on my garage floor from a leak I can never find was actually a crack in the pan where an internal baffle is spot welded to the exterior metal. It broke through completely and went from a drop per day to a couple liters per hour.
I was able to jack up the car at an angle enough to get the oil level below the hole so I could clean it with brake cleaner and JB weld a patch. Found the perfect patch in my tow vehicle: a single Chinese Yuan coin. I borrowed some JB Quick from 7s Only (the race shop at the track), glued the coin over the hole, and then the rain came. I never got another dry lap all weekend.
Still, the car was great in both dry and wet. ABS on a Fiero is phenomenal. I truly believe the Mk60e5 is a race ABS system even without the "motorsports flash". I never felt it was holding me back, and even in the wet I could stab the brake pedal hard and trust that the system would find the grip wherever it was.
The Nankang CR-S is a pretty good tire but it is definitely not a rain tire. By Sunday the track was mostly flooded and the rain was pretty much constant all morning so I packed up and headed home to dry off and clean up.
Re: Track Days in the DOHC Fiero
Whew... Had me there for a sec... Thought you might be doing an engine upgrade sooner than expected, lol
Definitely makes me want to get abs up and working in future
Definitely makes me want to get abs up and working in future
- Shaun41178(2)
- Posts: 8583
- Joined: Fri Nov 19, 2004 7:12 pm
- Location: Ben Phelps is an alleged scammer
Re: Track Days in the DOHC Fiero
The dash caught my eye
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
Update for April 2024
After I had some autocrosses under my belt and a lot of new confidence in the car, I booked a weekend with NASA at Buttonwillow Raceway and got to work on the last few major items on my track prep list.
First on the list was recovery points. I checked my front tow loop and it was still in good shape. No work needed there.
I also added a new tow hook that bolts to the rear wing mounts, along with nicer wing mount hardware. No more shiny silver on this black and red car.
I also added a LifeLine 360 Novec fire suppression system... because Fiero.
This also required completing Rev A of my totally custom center stack. You will notice nothing is familiar here, because I replaced everything but the dash. The center vent stack HVAC control surround, and Fire suppression button panel are my design and 3D-printed in ABS. The center tunnel cover is aluminum wrapped in vinyl.
You might notice something else new behind the steering wheel... yep that's a digital dash. I'm using a Joying 10.25" head unit running RealDash, which connects to the CAN bus. I'll go into a LOT more detail on this in a later post, because there's a lot of custom work software and hardware work behind it.
I finished up the fire system install and got the digital dash working the same day I loaded my car onto a trailer to take to the track -- a weekend with NASA at Buttonwillow Raceway. That event is detailed in my other thread here.
Despite the oil pan leak and lots of rain, the track weekend was overall a success. Nothing I built or designed broke, the car was getting faster and faster, the ABS worked amazing even in the wet, and I'm really motivated to continue taking this car to the next level.
After I had some autocrosses under my belt and a lot of new confidence in the car, I booked a weekend with NASA at Buttonwillow Raceway and got to work on the last few major items on my track prep list.
First on the list was recovery points. I checked my front tow loop and it was still in good shape. No work needed there.
I also added a new tow hook that bolts to the rear wing mounts, along with nicer wing mount hardware. No more shiny silver on this black and red car.
I also added a LifeLine 360 Novec fire suppression system... because Fiero.
This also required completing Rev A of my totally custom center stack. You will notice nothing is familiar here, because I replaced everything but the dash. The center vent stack HVAC control surround, and Fire suppression button panel are my design and 3D-printed in ABS. The center tunnel cover is aluminum wrapped in vinyl.
You might notice something else new behind the steering wheel... yep that's a digital dash. I'm using a Joying 10.25" head unit running RealDash, which connects to the CAN bus. I'll go into a LOT more detail on this in a later post, because there's a lot of custom work software and hardware work behind it.
I finished up the fire system install and got the digital dash working the same day I loaded my car onto a trailer to take to the track -- a weekend with NASA at Buttonwillow Raceway. That event is detailed in my other thread here.
Despite the oil pan leak and lots of rain, the track weekend was overall a success. Nothing I built or designed broke, the car was getting faster and faster, the ABS worked amazing even in the wet, and I'm really motivated to continue taking this car to the next level.
Re: Track Days in the DOHC Fiero
Nice work. What ecm are you running?
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: Track Days in the DOHC Fiero
Still a work in progress. It will be in my next big build thread update.
Stock ECU for the LQ1.. 9396 with $DF code.
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
My big project for April/May was to finally add some true datalogging capability to the car, and put a cherry on top of the interior.
I picked up a Joying Android head unit, and permanently installed a USB CAN interface inside that works with the RealDash app --- a professional quality digital dash engine that runs on Android, Linux, and iOS and is fully customizable and programmable to do pretty much anything you want. It's basically a 2D game engine designed specifically for car dashboards.
I designed and 3D printed mounts to place the head unit "brain box" directly on the steering column, and the display in front of it.
I originally tried to hide the head unit under the left speaker grill, but it was tricky to find enough room even after I had 3D scanned that whole area with the dashboard removed. That's ok, this will get covered with a shroud anyway.
Here you can see the head unit without the display.
Since the dash communicates via CAN bus, which Fieros don't have, I needed to get all of my vehicle sensors onto CAN. For the MK60E5 ABS module, this was trivial -- it already outputs a plethora of data from its CAN interface, including:
- individual wheel speeds and brake pressure, so I can monitor brake bias in datalogs or in real time
- inline and lateral acceleration and yaw rate
- ABS control state (e.g in intervention or not)
For supplementary sensors such as water pressure, oil temperature, and fuel level, I'm using an AEM 30-2226 6 Channel CAN Module.
Engine data is a bit trickier. I'm still running the stock GM "9396" ECU from 1991, which is ancient and slow by today's standards... even by 1996 standards. This ECU does have a serial data output line. It's a single wire ALDL interface that operates at a baud rate of 8192. It's possible to connect this interface to a standard UART with just a few passive components -- a resistor and a diode to split the send/receive lines into the microcontroller. Using a Seeed Studio CANBedFD development board for it's CAN interface and automotive power supply, I implemented firmware for an ALDL-CAN bridge and connected my stock ECU to its UART. Now I have the full diagnostic data stream from the 1991 ECU on CAN so I can datalog it with pretty much anything -- including my dash.
You can find the ALDL-CAN bridge source code on my github: https://github.com/series8217/aldl-can-bridge
Very exciting to see live data streaming into the dash!
After I confirmed the electrical system was working and the display was in a good spot with real graphics running on it, I designed and 3D printed a shroud and sun shade. The print is a little rough as I only had time to print it with draft settings but I'll do a reprint this summer when my printer has some idle time.
I used the Porsche 992 GT3 R technical manual as a reference for the gauge layout. I have multiple pages including the race display shown here, as well as a warmup page (monitoring engine vitals, oil temp, water temp, water pressure, etc), a track map, chassis diagnostics (individual wheel speeds and brake pressure), etc. The diagnostic pages are very helpful for making sure systems are working properly after repairing or replacing components.
With the CAN bus sorted and RealDash working, I could log performance and diagnostic data, and see a lot of real-time information that previously required a GM or BMW scan tool. However, due to the way the Android OS isolates files between applications, it's a bit of a pain to get data logs off of the dash. Also, once you get the data off it has to be converted to a format compatible with race analysis software in order to get insights for improving vehicle and driver performance. All of these steps waste valuable time between track session. Time better spent looking at the data or working on the car.
As fortune would have it, another racer friend was in town to visit the same weekend as a Speed District track day at Buttonwillow. So he flew down with more datalogging gear and race safety equipment than normal luggage, and we headed to the track to test them all. At one point we had 4 different datalogging systems and 3 cameras on in the car. By the end of the weekend, one prevailed... Stay tuned!
I picked up a Joying Android head unit, and permanently installed a USB CAN interface inside that works with the RealDash app --- a professional quality digital dash engine that runs on Android, Linux, and iOS and is fully customizable and programmable to do pretty much anything you want. It's basically a 2D game engine designed specifically for car dashboards.
I designed and 3D printed mounts to place the head unit "brain box" directly on the steering column, and the display in front of it.
I originally tried to hide the head unit under the left speaker grill, but it was tricky to find enough room even after I had 3D scanned that whole area with the dashboard removed. That's ok, this will get covered with a shroud anyway.
Here you can see the head unit without the display.
Since the dash communicates via CAN bus, which Fieros don't have, I needed to get all of my vehicle sensors onto CAN. For the MK60E5 ABS module, this was trivial -- it already outputs a plethora of data from its CAN interface, including:
- individual wheel speeds and brake pressure, so I can monitor brake bias in datalogs or in real time
- inline and lateral acceleration and yaw rate
- ABS control state (e.g in intervention or not)
For supplementary sensors such as water pressure, oil temperature, and fuel level, I'm using an AEM 30-2226 6 Channel CAN Module.
Engine data is a bit trickier. I'm still running the stock GM "9396" ECU from 1991, which is ancient and slow by today's standards... even by 1996 standards. This ECU does have a serial data output line. It's a single wire ALDL interface that operates at a baud rate of 8192. It's possible to connect this interface to a standard UART with just a few passive components -- a resistor and a diode to split the send/receive lines into the microcontroller. Using a Seeed Studio CANBedFD development board for it's CAN interface and automotive power supply, I implemented firmware for an ALDL-CAN bridge and connected my stock ECU to its UART. Now I have the full diagnostic data stream from the 1991 ECU on CAN so I can datalog it with pretty much anything -- including my dash.
You can find the ALDL-CAN bridge source code on my github: https://github.com/series8217/aldl-can-bridge
Very exciting to see live data streaming into the dash!
After I confirmed the electrical system was working and the display was in a good spot with real graphics running on it, I designed and 3D printed a shroud and sun shade. The print is a little rough as I only had time to print it with draft settings but I'll do a reprint this summer when my printer has some idle time.
I used the Porsche 992 GT3 R technical manual as a reference for the gauge layout. I have multiple pages including the race display shown here, as well as a warmup page (monitoring engine vitals, oil temp, water temp, water pressure, etc), a track map, chassis diagnostics (individual wheel speeds and brake pressure), etc. The diagnostic pages are very helpful for making sure systems are working properly after repairing or replacing components.
With the CAN bus sorted and RealDash working, I could log performance and diagnostic data, and see a lot of real-time information that previously required a GM or BMW scan tool. However, due to the way the Android OS isolates files between applications, it's a bit of a pain to get data logs off of the dash. Also, once you get the data off it has to be converted to a format compatible with race analysis software in order to get insights for improving vehicle and driver performance. All of these steps waste valuable time between track session. Time better spent looking at the data or working on the car.
As fortune would have it, another racer friend was in town to visit the same weekend as a Speed District track day at Buttonwillow. So he flew down with more datalogging gear and race safety equipment than normal luggage, and we headed to the track to test them all. At one point we had 4 different datalogging systems and 3 cameras on in the car. By the end of the weekend, one prevailed... Stay tuned!
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
Beating the Heat
I managed to squeeze in two more events before the full heat of summer arrived.
At the end of May, my friend Shane Reetz (@trackdailycrx) was in town to hang out for a few days and co-drive my Fiero at Buttonwillow Raceway during a Speed District track day. Shane's track car is a tastefully modified and upgraded 2nd gen Honda CR-X that he tracks & autocrosses nearly every weekend in the PNW. He's also a performance driving coach and has a good handle on using data to improve driver and vehicle performance.
Buttonwillow Raceway Park from the sky, with the fresh black asphalt of Track 2 still curing in the foreground
Shane showed up with small bag of clothes and a giant bag of race gear and data logging equipment.
The event was Saturday morning, and we had Friday to prepare with a reasonably short checklist of items to complete:
After we got back from the Crest we filled the fuel tank, jacked up the front of the car to do one last check of the front brakes, and took a break for dinner. An hour later we returned to the garage and were assaulted with gasoline vapors. There was a giant puddle of fuel on the floor and a steady drip from the back of the fuel tank. 10pm...
We got the ass end of the car up in the air and quickly assessed the situation. The vent pipe on the back of the fuel tank was loose where it had been swaged/crimped by the factory. The only option to resolve it was to replace the tank. As luck would have it, I had purchased a new tank from Rodney last year to use for a future swap. By 1 am the new tank was in and filled and the car was on the trailer.
After 4 hours of sleep, we were on our way to Buttonwillow.
Track Day
If you are lucky enough to have Speed District events within driving distance of your home, you probably know how exceptional these events are. Unlike the racing + HPDE orgs that cram track day activities in with lots of club racing, Speed District hosts HPDE-only events with limited car counts and give drivers so many sessions per day you will pack up and go home due to exhaustion before you're out of track time. It's a great environment for testing, tuning, and driver development. Attendees also tend to be very fast and very courteous, so you're likely to have a few unimpeded laps per session as getting stuck in traffic isn't a problem.
It was going to be a long day and we had a lot to get done, so we loaded up on coffee and got to work.
The goal of the first session was a more thorough shakedown run for the chassis (the Crest drive was just to make sure the loggers and dash were working) and to get the tires up to temp, set hot pressures, and check brake temps. No problems there -- we bled 3 psi out to achieve a hot pressure of 29 psi, checked the rotor temps (they reached bedding temp), and confirmed the brake fluid was staying cool. No engine error codes, no ABS codes, all looked good on the car.
As for the data systems, the AIM Solo 2 DL had recorded a full trace, RaceChrono was looking good, my dash was logging but CircuitStorm never even started recorded and didn't trigger the GoPro either.
For the second session, Shane hopped into the passenger seat for his first ride around Buttonwillow in real life. He has set some great lap times in the simulator but some of the surface irregularities (especially the bumps/dips around Riverside and Sunset) are different. Still, a simulated Buttonwillow is accurate enough to serve as a refresher if you've been to the track before. Time in the sim also gives you a huge head start if you've never been to the track before, as there are multiple blind corners.
We found the issue with CircuitStorm -- sort of. If the GoPro goes to sleep, CircuitStorm won't be able to start it on its own and complains about the camera being off. Since I couldn't see or reach the tablet from the driver seat in my first session, I didn't know what was going on. With Shane sitting shotgun we he turned it on for this run.
For the next few sessions, air temp stayed under 90*F and we had no problems with oil or coolant temperatures. Shane adapted fairly quickly to the car and we were both setting reasonable lap times, but no personal bests and we were getting slower as the day went on. This is typical for sunny days as the track temperatures skyrocket by the afternoon and soft tires get greasy. However, neither of us could consistently brake for some of the corners on the track, and the steering alignment seemed to be getting progressively worse as the day went on.
So we dug into the data to try to figure out what was going on. The drawbacks of some of the systems became immediately clear, and I'll summarize here as there is really a clear winner.
CircuitStorm was too brittle and clunky to manage, and we couldn't get it to connect to the online Podium service which would have been a nice benefit. RaceChrono Pro is a nice tool if you're just looking to improve lap times and don't have a coach or need to develop the car. It's very easy to quickly compare laps and see what corners you need to work on. It also has a very useful lap timer display while you're in the car.
AIM Solo 2 DL and Race Studio 3 The AIM Solo 2 DL was the real star of the show. It started automatically when the car started moving, and recorded basically every CAN channel on the car at 10hz, plus it has built in GPS and accelerometers. When I pulled into the pit garage and turned off the car, the Solo 2 DL would stay on with its internal battery to allow downloading data to a laptop. Shane didn't even have to get up from his chair. The Solo 2 DL has a WiFi access point that you connect to from a laptop, and a few clicks later you have data loaded and visualized in a very professional tool.
The most immediately obvious issue was both of us were over-braking before most high speed corners, leaving a lot of cornering force and exit speed on the table. There were easily seconds to work off with improved technique. We were also inconsistent in braking into some turns -- particularly Off Ramp and Sunset -- and even overshooting the ideal turn-in point at times. It was something we noticed while driving but couldn't pin down what was going on.
It took some digging but I eventually found that in a few particular corners the brake pressure generated by the pedal (about 100 bar out of the master cylinder at peak force) didn't result in the same amount of longitudinal acceleration, and it wasn't due to ABS intervention. This meant the effective brake friction coefficient was going down. Sure enough, the thermal indicating paint on the brake rotors had turned a color that was literally off the charts of the operating temperature range for the racing brake pad compound I'm using.
The next event was two weeks away and with a guaranteed hotter air temperature, so brake ducting and improved braking technique would both be necessary. The first to get cool air to the center of the rotors so the cooling vanes can do their job, and the second to reduce the over-braking and the additional heat generation it causes.
There were more fixes to make too but I wouldn't discover those until the post-event teardown...
I managed to squeeze in two more events before the full heat of summer arrived.
At the end of May, my friend Shane Reetz (@trackdailycrx) was in town to hang out for a few days and co-drive my Fiero at Buttonwillow Raceway during a Speed District track day. Shane's track car is a tastefully modified and upgraded 2nd gen Honda CR-X that he tracks & autocrosses nearly every weekend in the PNW. He's also a performance driving coach and has a good handle on using data to improve driver and vehicle performance.
Buttonwillow Raceway Park from the sky, with the fresh black asphalt of Track 2 still curing in the foreground
Shane showed up with small bag of clothes and a giant bag of race gear and data logging equipment.
The event was Saturday morning, and we had Friday to prepare with a reasonably short checklist of items to complete:
- Mount AIM SOLO 2 DL and configure CAN protocol for ALDL->CAN bridge and BMW MK60E5 ABS
- Mount tablet for CircuitStorm app
- Mount GoPro
- Mount Android phone with RaceChrono Pro
- Mount Qstarz Bluetooth GPS on the windshield (for RaceChrono)
- Shakedown run up Angeles Crest Highway with all dataloggers on
- Fill the fuel tank
- Load the truck and put the car on the trailer
After we got back from the Crest we filled the fuel tank, jacked up the front of the car to do one last check of the front brakes, and took a break for dinner. An hour later we returned to the garage and were assaulted with gasoline vapors. There was a giant puddle of fuel on the floor and a steady drip from the back of the fuel tank. 10pm...
We got the ass end of the car up in the air and quickly assessed the situation. The vent pipe on the back of the fuel tank was loose where it had been swaged/crimped by the factory. The only option to resolve it was to replace the tank. As luck would have it, I had purchased a new tank from Rodney last year to use for a future swap. By 1 am the new tank was in and filled and the car was on the trailer.
After 4 hours of sleep, we were on our way to Buttonwillow.
Track Day
If you are lucky enough to have Speed District events within driving distance of your home, you probably know how exceptional these events are. Unlike the racing + HPDE orgs that cram track day activities in with lots of club racing, Speed District hosts HPDE-only events with limited car counts and give drivers so many sessions per day you will pack up and go home due to exhaustion before you're out of track time. It's a great environment for testing, tuning, and driver development. Attendees also tend to be very fast and very courteous, so you're likely to have a few unimpeded laps per session as getting stuck in traffic isn't a problem.
It was going to be a long day and we had a lot to get done, so we loaded up on coffee and got to work.
The goal of the first session was a more thorough shakedown run for the chassis (the Crest drive was just to make sure the loggers and dash were working) and to get the tires up to temp, set hot pressures, and check brake temps. No problems there -- we bled 3 psi out to achieve a hot pressure of 29 psi, checked the rotor temps (they reached bedding temp), and confirmed the brake fluid was staying cool. No engine error codes, no ABS codes, all looked good on the car.
As for the data systems, the AIM Solo 2 DL had recorded a full trace, RaceChrono was looking good, my dash was logging but CircuitStorm never even started recorded and didn't trigger the GoPro either.
For the second session, Shane hopped into the passenger seat for his first ride around Buttonwillow in real life. He has set some great lap times in the simulator but some of the surface irregularities (especially the bumps/dips around Riverside and Sunset) are different. Still, a simulated Buttonwillow is accurate enough to serve as a refresher if you've been to the track before. Time in the sim also gives you a huge head start if you've never been to the track before, as there are multiple blind corners.
We found the issue with CircuitStorm -- sort of. If the GoPro goes to sleep, CircuitStorm won't be able to start it on its own and complains about the camera being off. Since I couldn't see or reach the tablet from the driver seat in my first session, I didn't know what was going on. With Shane sitting shotgun we he turned it on for this run.
For the next few sessions, air temp stayed under 90*F and we had no problems with oil or coolant temperatures. Shane adapted fairly quickly to the car and we were both setting reasonable lap times, but no personal bests and we were getting slower as the day went on. This is typical for sunny days as the track temperatures skyrocket by the afternoon and soft tires get greasy. However, neither of us could consistently brake for some of the corners on the track, and the steering alignment seemed to be getting progressively worse as the day went on.
So we dug into the data to try to figure out what was going on. The drawbacks of some of the systems became immediately clear, and I'll summarize here as there is really a clear winner.
CircuitStorm was too brittle and clunky to manage, and we couldn't get it to connect to the online Podium service which would have been a nice benefit. RaceChrono Pro is a nice tool if you're just looking to improve lap times and don't have a coach or need to develop the car. It's very easy to quickly compare laps and see what corners you need to work on. It also has a very useful lap timer display while you're in the car.
AIM Solo 2 DL and Race Studio 3 The AIM Solo 2 DL was the real star of the show. It started automatically when the car started moving, and recorded basically every CAN channel on the car at 10hz, plus it has built in GPS and accelerometers. When I pulled into the pit garage and turned off the car, the Solo 2 DL would stay on with its internal battery to allow downloading data to a laptop. Shane didn't even have to get up from his chair. The Solo 2 DL has a WiFi access point that you connect to from a laptop, and a few clicks later you have data loaded and visualized in a very professional tool.
The most immediately obvious issue was both of us were over-braking before most high speed corners, leaving a lot of cornering force and exit speed on the table. There were easily seconds to work off with improved technique. We were also inconsistent in braking into some turns -- particularly Off Ramp and Sunset -- and even overshooting the ideal turn-in point at times. It was something we noticed while driving but couldn't pin down what was going on.
It took some digging but I eventually found that in a few particular corners the brake pressure generated by the pedal (about 100 bar out of the master cylinder at peak force) didn't result in the same amount of longitudinal acceleration, and it wasn't due to ABS intervention. This meant the effective brake friction coefficient was going down. Sure enough, the thermal indicating paint on the brake rotors had turned a color that was literally off the charts of the operating temperature range for the racing brake pad compound I'm using.
The next event was two weeks away and with a guaranteed hotter air temperature, so brake ducting and improved braking technique would both be necessary. The first to get cool air to the center of the rotors so the cooling vanes can do their job, and the second to reduce the over-braking and the additional heat generation it causes.
There were more fixes to make too but I wouldn't discover those until the post-event teardown...
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
Loving the updates dude, can't wait to see it here in a few weeks!
-
- Posts: 3006
- Joined: Mon May 24, 2010 5:34 pm
- Location: Aiken, SC
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
The amount of data you're tracking is awesome! Any thoughts on adding travel sensors to the suspension?
"I am not what you so glibly call to be a civilized man. I have broken with society for reasons which I alone am able to appreciate. I am therefore not subject to it's stupid laws, and I ask you to never allude to them in my presence again."
- Series8217
- 1988 Fiero Track Car
- Posts: 6065
- Joined: Thu Jun 02, 2005 9:47 pm
- Location: Los Angeles, CA
Re: My 3.4 DOHC powered red and black camo '88 Fiero Track Car
Yep, they're on the to do list, but I have some higher priorities to go after first.ericjon262 wrote: ↑Thu Jul 25, 2024 10:22 am The amount of data you're tracking is awesome! Any thoughts on adding travel sensors to the suspension?