Jump to content

I'm taking my truck to the track tonight

ZZebes

By ZZebes
in Racing, Strip, & Track

Recommended Posts

ZZebes Senior Enthusiast

ZZebes

Posted
Posted

well i decided i am gonna go down to houston raceway park and run my truck for s**ts and giggles, i will post times when i get back, but with a 3.23 i dont think my 60 times are gonna be pretty. i have to leave the tailgate on since i dont have a place to put it. so wish me luck.

svensk Senior Enthusiast

svensk

Posted
Posted

If you remove your tailgate you are actually causing more wind resistance than if you left it up. The Mythbusters tried that experiment and came that conclusion because an airbubble forms in your bed when the tailgate is in the up position forcing the air directly over it.

I really don't think it would make any impact on your 1/4, and trap speeds but it's an interesting piece of info none the less.

carneyman Senior Enthusiast

carneyman

Posted
Posted
If you remove your tailgate you are actually causing more wind resistance than if you left it up. The Mythbusters tried that experiment and came that conclusion because an airbubble forms in your bed when the tailgate is in the up position forcing the air directly over it.

I really don't think it would make any impact on your 1/4, and trap speeds but it's an interesting piece of info none the less.

 

 

 

 

Yeah, but that mostly affected gas mileage. Lose the extra weight and it might make a difference in the quarter, where you are runnin' full throttle anyway. Probably not much of a difference though. Some people put extra weight in the back for traction, so who knows.

 

Anyways, have fun. :)

carneyman Senior Enthusiast

carneyman

Posted
Posted
Yeah, I think I would also remove my back bench seat as well for the race.

 

 

 

 

 

might as well take out the passenger seat too...take the bed off too...actually, that might not be a bad idea, if you've got the equipement (ie cherry picker)

ZZebes Senior Enthusiast

ZZebes

Posted
  • Author
Posted

Well i just got back and i ended up running a 17.119 at 85.79

I will say in my defense that this is my first time running this truck ever, and my reaction time was .682 and my 60' was 3.033

 

so any criticism is constructive criticism.

Wingnut Senior Enthusiast

Wingnut

Posted
Posted
Well i just got back and i ended up running a 17.119 at 85.79

I will say in my defense that this is my first time running this truck ever, and my reaction time was .682 and my 60' was 3.033

 

so any criticism is constructive criticism.

 

 

 

 

No criticism needed...You have a pickup. If somebody gives you sh*t about the time, tell him to strap a 4000lb boat to his Rustang and THEN run you.

 

:)

linda Enthusiast

linda

Posted
Posted
Well i just got back and i ended up running a 17.119 at 85.79

I will say in my defense that this is my first time running this truck ever, and my reaction time was .682 and my 60' was 3.033

 

so any criticism is constructive criticism.

 

 

 

 

 

Those times are nothing to cringe about. I know for a fact with a little more practice you can get those 60' times in the mid 2's no problem. That in turn will give you a better 1/4 time. High 16's for you should be no problem. Good run.

TieRod Enthusiast

TieRod

Posted
Posted
Yeah, I think I would also remove my back bench seat as well for the race.

 

 

 

 

 

might as well take out the passenger seat too...take the bed off too...actually, that might not be a bad idea, if you've got the equipement (ie cherry picker)

 

 

 

 

 

 

If your worried about weight, you are not making enough HP.

ZZebes Senior Enthusiast

ZZebes

Posted
  • Author
Posted
Well i just got back and i ended up running a 17.119 at 85.79

I will say in my defense that this is my first time running this truck ever, and my reaction time was .682 and my 60' was 3.033

 

so any criticism is constructive criticism.

 

 

 

 

No criticism needed...You have a pickup. If somebody gives you sh*t about the time, tell him to strap a 4000lb boat to his Rustang and THEN run you.

 

:)

 

 

 

 

 

I will say that the car i raced was in fact a V6 rustang

 

I pulled up and they had me against an old grand national with tubs, so they realigned me with this kid in a V6 rustang with big exhaust and a lot of neon, he did a burnout and everthing and looked over at me and asked if i was ready to lose and i just smiled and looked ahead and chewed his ass up. we got back to the staging area and i kindly said "so when am i gonna lose?" and drove off. so it was a fun experience none the less.

jackster06Z71 Enthusiast

jackster06Z71

Posted
Posted

if it werent for punks with there rustangs with spoilers and civics with the v-tech stickers that add 15 hp, then i woulnt laugh as much, sometimes we need those guys with out a clue. my favorite ones are when they have there civics or other imports with bodys kits that every piece is a different color primer , and some how they have a hot ass g/f that laughs when we beat them with our trucks :cheers: i love it

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...