Jump to content

80-90s GMC Jimmys, Chevy Blazers, and OLDs Bravada

Sonic

Recommended Posts

Sonic Enthusiast

Sonic

Posted
Posted

They are my personal favorite trucks.

Ive had the pleasure of driveing all 3 of them.

But how are they for owning them?

Are they good trucks, do they last awhile, all that good stuff. :devil::lurk::devil:

95whtZR2 Enthusiast

95whtZR2

Posted
Posted

I owned a 1994 GMC s15 jimmy 4x4. It was a nice vehicle, it was leather and all power. Ran very well, I had 164k miles on it when I traded it in for my 1995 Zr2. My brother had a 1989 s10 blazer 2dr, 4x4, that was nice. He just sold it with 143k on it for $2000. He had to replace the head gasket about 6 mos. ago, and that was the only major problem- besides his 4 wheelin incident in which it ruined his CV axles, ball joints, 1 tie rod end, and who knows what else on the front susp. Overall both of these vehicles held up good considering it my brother was 17 when he bought his blazer and he is now 22, and I 18 when I bought my jimmy, and sold it when I was 19. So these vehicles were put through the worst years for anyone to drive, and they both came out smelling like roses in the long run. I highly recommend these trucks to anyone- just as long as you know the sprak plug replacement method... :devil::devil:

 

 

 

Tom

 

 

BTW, I believe there are pics of both below...(unless sendaframe is being stupid again)

 

EDIT: Oh and my jimmy ran a 17.2 in the quarter- totally stock, which I don't think is too bad for a 4x4...

o4yukonxl Enthusiast

o4yukonxl

Posted
Posted

I have a 92 S10 4WD 4.3 CPI with 186K. I just replaced the ball joints, tie rods, injection, and upgraded the front disc brakes. This thing runs great, reasonably fast, and has 4WD. The brakes were the weak link and I upgraded to dual piston calipers. If you want to go faster, just install a V8.

blue2kzr2 Enthusiast

blue2kzr2

Posted
Posted

Like 95whtzr2, I had a 94 Jimmy that I traded in to buy my 2000 S-10. Mine wasn't LOADED but it had what I wanted.

 

In 53,000 miles (62,000-115,000) here are the major repairs I had done.

 

Intake gaskets

Fuel tank/pump (at different times cha ching)

heater core

injector (I had the W motor, only applies on that motor)

Alternator

Rear axle bearings

 

That's it besides misc. wear items like the brakes, battery, belt, shocks, tires and one CV axle due to a ripped boot. I also had some rust repairs done, and had some body panels replaced due to accidents.

 

That was one TOUGH truck, sustained $6,000 damage in 2 separate accidents and never showed signs of having been repaired or ever being in an accident.

 

I liked the truck so much, and felt confident in my safety while behind the wheel, that I bought another S-truck, what's that tell ya? Oh yeah, it was also fairly easy to work on, and I haven't taken my newer truck to a shop for a mechanical repair except those that were covered by the used-car warranty.

St_Anger Enthusiast

St_Anger

Posted
Posted

I had an '89 Jimmy 4x4, which was an awesome truck... But I ended up selling to buy my '92 Rustang that I was going to build into a street machine (BIG mistake).

  • 2 weeks later...
Sonic Enthusiast

Sonic

Posted
  • Author
Posted
I had an '89 Jimmy 4x4, which was an awesome truck... But I ended up selling to buy my '92 Rustang that I was going to build into a street machine (BIG mistake).

 

 

 

 

AHHH STANG??? IT BURNSSSSSSSS!! :thumbs:

Corvette and Vipers anytime.

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...