Jump to content

Beat A Hemi Ram 3 Times


Schmids5.3l

Recommended Posts

Posted

On the way to the car meet tonight I did some ricer roll racing against a 2003 Reg Cab Short Bed 2wd 5.7 Ram. The first 2 runs were @ 65 & 70. The first run he got the jump big time, and I pulled to his front bumper and let off at the end of 2nd gear. 2nd run we left at the same time and his front bumper was at my rear bumper shortly after I shifted into 3rd probably around 90. The third race was from 50 mph, both leaving at the same time. At the end of 2nd (85? mph) I had half a length to a length. All races were done on an abandoned highway in Mexico. His best time at the track is a 14.69 I believe @ 92 stock truck, with a 2.1 short time.

Posted
On the way to the car meet tonight I did some ricer roll racing against a 2003 Reg Cab Short Bed 2wd 5.7 Ram. The first 2 runs were @ 65 & 70. The first run he got the jump big time, and I pulled to his front bumper and let off at the end of 2nd gear. 2nd run we left at the same time and his front bumper was at my rear bumper shortly after I shifted into 3rd probably around 90. The third race was from 50 mph, both leaving at the same time. At the end of 2nd (85? mph) I had half a length to a length. All races were done on an abandoned highway in Mexico. His best time at the track is a 14.69 I believe @ 92 stock truck, with a 2.1 short time.

Holy fWon that's a quick truck stock! :thumbs: I expected you to beat him, but I didn't think he'd be that close. Thank God for Zippy. :D

Posted
Holy fWon that's a quick truck stock! :thumbs: I expected you to beat him, but I didn't think he'd be that close. Thank God for Zippy. :D

 

Definitely, I was pulling on him every race, just not that fast! That truck definitely has balls!! I kind of expected what happened, he's only 3-4mph slower in the 1/4, his extra cubes and TQ are kind of trumped by his weight, so the extra little bit of HP/tune and less weight I had ftw!

 

edit: I had no idea reg cab short bed 2wd Hemi's ran 14.6's stock? Aren't they like 14.8-15.1ish?? I dig raced a Rumble Bee a long time ago and held my own. He spun off the line some but he never caught up? SCT doesn't make tuners for those trucks until 04...unless he has a superchips hand held...He has a 12 second Fox body and a Big Block Jr dragster, I don't see him keeping this thing stock. :nono:

Posted

Glad you beat the Hemi.

My brother has one, either a 2007 or 2008. Not sure which.

He thinks it is about the fastest thing on the planet. :D:thumbs:

 

He has challenged Darkanion's 2007 Denali to a dragrace.

 

I want to see the Hemi get beat...BAD...by the GMC. :nono::lol::D

Posted
Glad you beat the Hemi.

My brother has one, either a 2007 or 2008. Not sure which.

He thinks it is about the fastest thing on the planet. :thumbs::nono:

 

He has challenged Darkanion's 2007 Denali to a dragrace.

 

I want to see the Hemi get beat...BAD...by the GMC. :lol::D:D

 

 

Only if his trany can stay in 1 piece :D

Posted
Was the giggle gas used?

Hell no!!! Motor to motor! That wouldn't have been a race on spray :D

 

Glad you beat the Hemi.

My brother has one, either a 2007 or 2008. Not sure which.

He thinks it is about the fastest thing on the planet. :D:D

 

He has challenged Darkanion's 2007 Denali to a dragrace.

 

I want to see the Hemi get beat...BAD...by the GMC. :D:D:D

 

Tuned 6 speed Denali's are hitting high 13's low 14's in the 1/4, he should be fine :shakehead:

Posted
Only if his trany can stay in 1 piece :shakehead:

 

You want a run, Mr. Smartypants?

 

I didn't think so...

 

Now, quit trying to derail every thread you go into, 'k? Thanks!

Posted
Was the giggle gas used?

Hell no!!! Motor to motor! That wouldn't have been a race on spray :shakehead:

 

 

Good..I was about to say something about yer slow ass if you did.... :D

Posted
lets go, Im down for a run, if you put the stock tune back first :shakehead:

 

 

I think you may have your hands full even with tuned 5.3 against a stock tuned SD.

 

 

Mike are you sure about those times? Because a Tundra 5.7 runs in the 14.6-14.8 range stock and I know a stock Dodge Hemi is not running with a Tundra.

Posted
lets go, Im down for a run, if you put the stock tune back first :shakehead:

 

 

I think you may have your hands full even with tuned 5.3 against a stock tuned SD.

 

 

Mike are you sure about those times? Because a Tundra 5.7 runs in the 14.6-14.8 range stock and I know a stock Dodge Hemi is not running with a Tundra.

 

 

I dont mind losing, as long as its to a GM truck

Posted
Was the giggle gas used?

Hell no!!! Motor to motor! That wouldn't have been a race on spray :shakehead:

 

 

Good..I was about to say something about yer slow ass if you did.... :D

 

 

lol, I'd quit at that point and disappear until there was a 6l in the truck.

Posted
are you sure about those times? Because a Tundra 5.7 runs in the 14.6-14.8 range stock and I know a stock Dodge Hemi is not running with a Tundra.

 

RCSB Tundra's are in the lower 14's stock. The crew cab 4x4's are probably high 14's. The 5.7 Ram I raced was the same configuration as mine, RCSB 2wd. I don't think it should run 14.69's stock either though, so he's probably got a hand held or something he's keeping secret. :shakehead:

Posted
lets go, Im down for a run, if you put the stock tune back first :shakehead:

 

 

I think you may have your hands full even with tuned 5.3 against a stock tuned SD.

 

 

Mike are you sure about those times? Because a Tundra 5.7 runs in the 14.6-14.8 range stock and I know a stock Dodge Hemi is not running with a Tundra.

 

 

I dont mind losing, as long as its to a GM truck

 

 

Hey Felix, I hope to have my exhaust on this week or weekend. I will let you know when I have the mufflers in my possession if you are still interested.

 

Sorry to thread jack.

Archived

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

  • Latest Articles

  • Posts

    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...