Jump to content

Plastic Nipple Broke On 99 Sierra

sierraingws

By sierraingws
in Ask A GM Technician

Recommended Posts

sierraingws New Member

sierraingws

Posted
Posted

99 Sierra 2500, 200K, 6.0, auto, AC, 4wd, Last week one of the plastic nipples the heater hose is connected to at the firewall broke while driving. I have begun the dash removal process (sheesh, what a pain), and have new core coming, but some disscussions here make me think that the plastic piece is NOT part of the core. If so, how can I get it off without removing the core (and the whole dang dash)? The hoses were connected with pinch type clamps. AFAIK everything is stock. \

Thanks

gm4yrs Enthusiast

gm4yrs

Posted
Posted

The heater hose disconnects, are removable. You will need a quick-disconnect tool, to slide in, from the back of the connector, then pull toward you, to release it. You can buy the Lisle brand, at Pep Boys. It has 6 different sizes, and are longer that fuel disconnects. Put your dash, back together.

sierraingws New Member

sierraingws

Posted
  • Author
Posted

Thanks. After looking at it some more I could see that there was indeed a piece slid over the metal end of the heater core. I cut it off with a sawzall blade, applied some heater hose stretcher and sliped the hose over the (now) metal end. If you ask me, this is the silliest thing I have seen in the 10 yrs I have had this truck. Adding a plastic piece that requires a special tool is a goofy solution to a packaging problem- that is that the metal end of the core is tucked a bit under the cowl and behind the engine.

Now to put the interior back together.

Thanks again.

Archived

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

Go to topic listing

  • Latest Articles

  • Posts

    • Chuck FB
      Joke Thread

      By Chuck FB · Posted

      This video may not be the exact content for the joke thread but its a lot of laughs so here it is, I've only watched a portion of it so far but if anyone is looking for some light hearted good soap box driving action, its here. As a note in the upper left of the screen it shows the number out of 100 to refer back to any particular vehicle for comment !.    https://www.facebook.com/reel/1351928276956715
    • 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.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...