Jump to content

Auto X'd For The First Time

Schmids5.3l

By Schmids5.3l
in Racing, Strip, & Track

Recommended Posts

Schmids5.3l Senior Enthusiast

Schmids5.3l

Posted
Posted

What a friggen blast!!! I didn't actually drive, but rode. It was a 1984 Nissan 300zx. It has a naturally aspirated 3L V6, makes 220 at the wheels with wide race tires. The car is gutted and has 2 seats, weighs somewhere in the lower 2000lb range. The engine itself has a custom Isky cam, he bought 7 NASCAR rods that a team used for a few test laps and sold, ported heads & intake, headers, etc. It probably makes closer to 250whp with skreet tires, next season the heads are getting CNC ported with a sheet metal intake.

 

It was freakin' fun as hell!! The entire time your stomach is heavy, and you are wondering how the car isn't upside down or spinning out of control or something. The car would run 12's in the 1/4 as it sits considering power to weight. It was completely bad ass and a huge thrill. If any of you have a friend that does this I highly recommend riding. I rode with an old guy, he has been doing this since 2001. He sure the hell could drive.

Zembonez Senior Enthusiast

Zembonez

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :)

tobias Senior Enthusiast

tobias

Posted
Posted
No pics or video?

 

 

 

FAIL! :)

Autocrossing is FUN! Especially in a Japanese car. :omg:

 

 

:sick:

 

 

 

 

 

 

 

 

 

 

 

 

:drool:

VMax2007 Senior Enthusiast

VMax2007

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :)

 

 

Yeah, and you don't have to worry about interior pieces falling off and hitting you in the head, right? :drool:

Zembonez Senior Enthusiast

Zembonez

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :)

 

 

Yeah, and you don't have to worry about interior pieces falling off and hitting you in the head, right? :omg:

 

LOL!

 

Sorry... couldn't resist. :drool:

geektoad Senior Enthusiast

geektoad

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :drool:

 

 

No. I promise I had more fun that 95% of people in Japanese cars. And it ran 12.1 on top of it :)

 

nats3.jpg

 

 

 

nats1.jpg

 

nats2.jpg

Zembonez Senior Enthusiast

Zembonez

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :drool:

 

 

No. I promise I had more fun that 95% of people in Japanese cars. And it ran 12.1 on top of it :)

 

nats3.jpg

 

 

 

nats1.jpg

 

nats1.jpg

 

That's cool!

 

Cool thing about AutoX is that you can have fun in just about anything. I've thrashed several Miatas in a few ProSolo SCCA events. Against the "pros" I wasn't terribly competitive but I finished mid pack every time. Main thing is the fun that was had!

VMax2007 Senior Enthusiast

VMax2007

Posted
Posted
No pics or video?

 

 

 

FAIL! :sick:

Autocrossing is FUN! Especially in a Japanese car. :omg:

 

 

No. I promise I had more fun that 95% of people in Japanese cars. And it ran 12.1 on top of it :drool:

 

nats3.jpg

 

 

 

nats1.jpg

 

nats1.jpg

 

 

 

OWNED!!! :)

geektoad Senior Enthusiast

geektoad

Posted
Posted

The ProSolo format is badass! the mix of autox and bracket racing is a hoot for sure :sick:

Schmids5.3l Senior Enthusiast

Schmids5.3l

Posted
  • Author
Posted

I'll try to get pics of the car sometime, this was a last minute adventure. They do this locally once or twice a month, so there will be pics next time :sick:

 

Fastest car there was a 3rd gen Camaro with a 355/TH350 w/ manual valve body, but he's an older fella too and has been doing it for years. I believe his best time was 48.xx seconds before I left, the 300zx I rode in ran a 51.08 with me in it, which was it's best time at that point. There were around 4 Corvettes, a few older Camaro's from the 70's up to the early 90's, a WRX STI, a couple RX7's, a few Nissan's (one was a turbo 350z), might have been 2 Mustangs, and some BMW's, one had a roots blower. There were a few classic Porches and whatnot as well. I guess roots blowers are popular in this sport due to the instant low end tq and power they make.

svensk Senior Enthusiast

svensk

Posted
Posted

Yeah that looks like a hoot. Just about everyone in my Dept. is in to that now. Everyone has their "toy" they been working on all winter. Two turbo miatas, wrx sti, MR2, 2.5 Forester etc.

Too bad they don't let you bring a full size truck out there... :D I'd have to us the Altima, but it's unfortunately front wheel drive which sucks for that stuff.

Schmids5.3l Senior Enthusiast

Schmids5.3l

Posted
  • Author
Posted

There were 2 Miata's there, one had FI, those cars can take some turns! But yes ride with someone in your dept, it's fun!! At one point I was worried this car was going to flip over and do some barrel rolls lol! I've never been in a car going that fast and taking turns...in control.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...