2010 MAC/Met Council Autocross Schedule

[s1ngletracker]

I may or may not end up going... car probably isn't going to be ready for it :(

[Tachyon]

I may or may not end up going... car probably isn't going to be ready for it :(

What needs to be done?

[s1ngletracker]

I was supposed to have shane tune it this week, which ended up getting cancelled... I had him burn me a 'safe' chip but for some reason its phantom knocking like crazy with this EEPROM ECU that I am using...

[AJ]

COM event = be prepared to stand around for 12 hours and race for 12 minutes. Just a heads up

12 to 13 hours, really? That's not even close man. Even with higher volume MAC events you're standing about 3, maybe 4 hours tops if you are working cones. I'd say 3 is closer if they don't have the population needed to only need people to work one heat each.

From the one COM event and one MAC event I have been to, the COM event was just run very cumbersome, lots of down time between run groups, etc. lots of wasted time. I was literally there for 13 hours and didn't even stick around to work the corners for the last few run groups. (Yes, I was that jackass)

MAC runs their events much more efficient IMO.

It's more laid back, but it's a lot of the same people in the end who help run and design the course.

This weekend there is about 60 signed up so far, I'm sure they will be closer to 70 or 80 with walk ups if the weather is good, and the first COM event I ran this year was a fucking blast. Course was fast and I was done and home by 4pm ish. Spend maybe 2 total hours working cones (1 hr each heat).

Anyone who goes this weekend will have a blast, it's the last weekend for DCTC for the year for auto x at least.

Here is one of my videos from M5, that was a fun course!

http://www.youtube.com/watch?v=jLYcHN5aEm8

[Tachyon]

I was supposed to have shane tune it this week, which ended up getting cancelled... I had him burn me a 'safe' chip but for some reason its phantom knocking like crazy with this EEPROM ECU that I am using...

If I even put a knock sensor on my setup it would report 'knock' practically 100% of the time (Bosch sensor).

If you know it's phantom, is there a way with your setup to prevent the car from pulling timing?

[s1ngletracker]

So when I use a non-EEPROM turbo ECU, i only get a few counts at higher RPMs... which I think might be legitimate knock (though I cannot hear it... I don't have a trained ear for that) But when I use an EEPROM ECU with stock chip, or a chipped ECU with Shane's basemap, I get phantom knock like crazy, car pulls timing all over the place.

Car has a 4G64 with 14b... wastegate boost - 10lbs. In theory it shouldn't be knocking...

And now I can't get my old piece of shit palm pilot to load MMCD, so i'm up shits creek on even being able to verify anything.

[s1ngletracker]

anyone wanna go in my stead and say you're me?