Jump to content

Anothah Mainah joins the crew w/ some questions...

SS77

By SS77
in New Member Introductions

Recommended Posts

SS77 Enthusiast

SS77

Posted
Posted

Hi all. I'm a Mainah on hiatus currently living in CT. Been her for 11 years, but I'll go back soon...

 

Some quick truck questions:

 

I'm about to buy a 2003 Chevy 1500 Silverado 4x4 with the 5.2 Vortec. It only has 19K miles but the real tires are bald and the engine has a hiccup. Book is still $22K, but I'm getting it for $15K. Is it worth it? What should I ook for with wear? Are there any consistant problems with the 03? What should be my expected MPG for the 6' foot bed on the highway? Better to remove tailgate? Man, i have a bunch of questions...is there a FAQ for this truck?

 

Thanks all and I look forward to your responses!

 

Steve

carneyman Senior Enthusiast

carneyman

Posted
Posted

Welcome! :D I'd say that is a pretty good deal. Better do a thorough check of the truck first though. Check for signs of it being in a wreck (frame repairs and the like), cause you won't want that.

Buggle_96 Enthusiast

Buggle_96

Posted
Posted

5.3 vortec maybe?

 

Dont remove the tailgate you will get worse mpg. Sounds like a decent price, what do you mean hiccup? Air filter just need changed or something?

SS77 Enthusiast

SS77

Posted
  • Author
Posted
5.3 vortec maybe?

 

Dont remove the tailgate you will get worse mpg.  Sounds like a decent price, what do you mean hiccup?  Air filter just need changed or something?

 

 

 

 

First off: Wow, I'm such a n00b. As a long time enthusiast of another make I'm realizing what a fool i must be. I did mean a 5.3, however I just requested a copy of the build sheet only to find out it is a 4800. lol! Anywho...

 

The engine hiccup is pretty much just an unsteady idle when the rpm dip about every 5 secs or so. I just checked out the body work and there was no sign of frame damage, but there was a little overspray on the brake lines along the frame under the gas filler area. No damage anywhere, so they must have replaced the fiberglass and repainted.

 

After driving it, I noticed the steering feels a little loose and the rear end was clunky (drove over a small curb). When I grabbed & tugged out on the rear wheel I felt a little play, not movement but enough to tell something was worn in the rear.

 

And as I mentioned before, the rear tires are bald. Someone was squawking this thing before trading it in.

 

Thoughts?

Worktruck Enthusiast

Worktruck

Posted
Posted

Howdy and welcome to the forum. Boy 2 new Maina's in as many days. Kinda scary. I would get the VIN and see if one of the nice fellas here would do CarFax for ya. With that little mileage and a loose feeling rear end there is something wrong. I have an 02 Sierra with 85K and the rear end is nice and tight. And I tow daily. I also have the 4.8 and my only complaint is that if it had a little more power I'd get better mileage. I'd look her over really well. Bald tires at 19K would be a flag for me. Good Luck.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...