Jump to content

CMarkmann

Members
  • Posts

    53
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by CMarkmann

  1. Saturday -https://www.youtube.com/watch?v=6aOqky63lPg Sunday - https://www.youtube.com/watch?v=PeLK7xl_0OM
  2. https://www.scca.com/events/2004759-2024-tire-rack-scca-phoenix-national-tour-arizona-motorsports-park Event schedule and all supplemental tech / event info is toward the bottom of the page.
  3. Had a great day Saturday on a fun course, and really enjoyed the challenge of the weather and working on adapting to the evolving course condition during B group. Big thanks to Lance for getting me off the wait list on Friday so I could join the fun! Comp - 44.376 TO - 43.563
  4. 46.447, and will echo the comments about how much I enjoyed this course.
  5. The NASA group leaves race cars and trailers overnight basically every weekend they run at AMP. The organizer charges a fee to entrants so they can pay for security, but there's no restriction other than people not being allowed to camp at the property.
  6. Thanks Kim. Post wasn't super clear about availability timing. In previous years, this has only been advertised as available during Jan/Feb events. Was hoping to pre-tech my car for next year since I don't have any changes planned over the holiday break!
  7. Is 2024 annual tech available at the Dec event tomorrow, or not until next year?
  8. First event running the car on 245s, and still figuring out how much I can push it now, but it felt really good. Have some thoughts on what to adjust for next month. Fastest Comp run was a 49.2. I think the car had a 48 in it, but I didn't grab 3rd through the first set of offsets on this run, and spent a lot of time on the rev limiter there. Mistake on my 4th run meant I couldn't prove it... I got down to 49.05 in TO even though the surface grip felt lower.
  9. Addition to my prior post; currently run group assignments are assigned through the grid number stuck to the entrants car. Now... we are expecting people to know which group they're in, as well as for grid to know they belong there or not without just looking at their windshield. Possible solution is to have grid carry a copy of run group listing with entrant numbers to audit who is there before sending them to starter. This would be the primary checkpoint to keep a "bad" number from getting to timing in the incorrect run group.
  10. Basically what Mark said; grid position no longer matters other than for two driver cars. Spitballing this since I've been put on the spot: Timing is already mostly automated for run order based on pre-fill from registration info. New procedure will have added column (or replaced column since grid position no longer needed) for driver's competition number. Timing worker will need to enter competition numbers through first runs of each group in order to run through each assigned run group's field, and then it will move back to the top as in current practice. Reserve existing grid spaces 1-8 (estimate) for 2 driver cars, instruct grid person to send second drivers at pre-determined interval of run group (say... around 14 or 16 like we do now). Make a sign and use green cones to cordon that area off. Much less confusion for cone calls since observers and course workers will be calling in car numbers instead of guessing whether that CAM car is a Chevy or a Buick. "Station 4, 1 cone on car 592" vs "1 cone on that blue hatchback"
  11. Disagree with this not being feasible for a local region. San Diego region had a successful system for this where you registered your regional competition number annually (with a fee to have your Solo Card and ownership of that number). The SCCA magazine (which we should all be receiving with our memberships) has advertisements in the back for multiple vendors supplying numbers that fill this need. If people are spending $1000/year on tires, it's not a huge ask to improve the running of the event to have somebody spend $60 on numbers. Roll the annual number registration in with annual tech. For newer entrants, temporary 4 digit numbers were assigned and the paper + painters tape method was required. Eventually, they decide that they want to "look the part" at the events and buy numbers as well. This seems to come up every few years, and I haven't understood the pushback to improvement, other than just being resistant to change.
  12. "Make the suspension adjustable and they will adjust it wrong -- look what they can do to a Weber carburetor in just a few moments of stupidity with a screwdriver." - Colin Chapman
  13. The flipside bad news to that is that Discount Tire won't touch wheel/tire fitments that are outside of the listed widths on the spec sheets, which makes fitments typically favored by autocrossers a problem for you to solve elsewhere. I had to deal with this first hand when they wouldn't touch 225s mounted on a 15x9 anymore. That mentality has also seemed to spread to Tire Rack as well, and things that I used to be able to just click and have show up at my door now have them giving follow-up phone calls to confirm I'm really sure that I want to put tires that size on my car.
  14. Close it up. Big thanks to the community for the generosity of their time to help me with this!
  15. I'm looking to move up in tire size and want to trial fit a 245/40 to my 15x9" wheel on my Miata to understand what (if any) clearance limitations I'll have with this setup on my car. Looking to buy/barter/borrow either a Rival S or RT660 in this size to mount and do some investigation. Hoping somebody has a used one that I can take off their hands and dispose of...
  16. Pulling an ABS fuse would probably kill any of the brake-based LSD and torque vectoring functions that rely on the wheel speed signals and individual corner brake pressure application to work.
  17. Had a lot of fun on this course, but never quite felt like I figured out the longer double element corners that would've had me making a smoother single steering input instead a bunch of smaller bites. I definitely had trouble sighting my way into the last right and confidently setting my entry trajectory with the brakes. I got a bit frustrated and really hit a wall at the mid 50s. I ran, in sequence, 50.63, 50.50, 50.90 (first TO, cooler tires), 50.60, 50.55, 50.58, so it's too bad we weren't doing bracket racing. Other than that, I'm not disappointed to be done with these 2018 BFGs, and hope to start getting actual feedback and pace from the tires again in the fall. Fast comp is shared below, and decided to post my more entertaining 4th TO run that's a bit slower than my 3rd. There may have been a low 50 there if I'd cleaned up a few mistakes.
  18. Wow, somebody grab this. Buy a whole stack of STR parts, and you get a free car to go with them.
  19. The second day was a bit frustrating for me because I felt like I was executing things well, but the lap times really weren't reflecting what I thought they should have been until the last run. Firing up the excuse machine: I ran in A on Saturday versus D on Sunday, and I think the surface temp difference with the high sun didn't play well with my tires; I think my mid-2018 date code Rivals with 130+ runs on them may finally be cooked and ready to send off after the April event as they really didn't seem to be giving good grip until I got them properly hot at the end of the run group. I ended up at a 47.2 on my last run, and that really felt ragged and overdriving from inside the car.
  20. Really enjoyed working things out to execute this course well. It took me until my 4th run to pick up the right visual cues for executing the long sweeper through the middle of the course as a single feature rather than breaking it into multiple bites and inputs. Unfortunately, my camera borked that run, so here's video of the 46.4 on my 3rd run rather than the 45.0 I ran after I got things figured out.
  21. @aweZome28 The long sweeper through the middle of the course this weekend had the fastest people pulling over 1g for at least 7 seconds. That's more than enough time to starve the oil pickup without appropriate countermeasures.
  22. You should be fine. This seems like it's almost exclusively a Lotus problem.
×
×
  • Create New...