Jump to content

2021 3500HD in bed 5thwheel plug...

THE YETI
 Share

Recommended Posts

THE YETI Enthusiast

THE YETI

Posted
Posted

I posted in what I later realized was an older thread and figured I might as well start my own.  And sorry but I'm cutting and pasting on my phone so sorry if the txt size and style varies...

 

  My question is will a CURT Manufacturing 56070 (basically the 7 foot plug and play connecter that you plug in to the factory bumper plug and run the harness up to the side of the bed and normally drill a hole and mount an in bed plug) work in conjunction with a Hopkins 40975 (basically from my research so far, the plug end that will mount in place of the plug at the back of my bed on my 2021 3500HD)

 

So basically what I'm asking is if I mount this hopkins part in the factory spot in the bed will the curt part plug in to it and I'll be good to go?  I've already ordered the curt part as I've used it a couple times before.  But I ordered it before I got my new truck and then saw it had this plug in the bed for what must be a factory install plug.  I'll attach links to the parts I'm talking about strictly to save you research on what I'm talking about...

 

https://www.amazon.ca/gp/aw/d/B0031GHBSE?ref=ppx_pt2_mob_b_prod_image

 

And....

 

 

https://www.amazon.ca/gp/aw/d/B001NYYREC?ref=ppx_pt2_mob_b_prod_image

 

 

Thanks in advance for any help...

THE YETI Enthusiast

THE YETI

Posted
  • Author
Posted

Well,  since I haven't got an answer yet.  I figured I would order it anyway.  Looking at pics and some research of sorts I'm thinking they should work together.  Whether I have to take something apart or not, we will see.  I'll be the guinea pig and post back with results for anyone else that may run in to this question too.

  • Like 1
THE YETI Enthusiast

THE YETI

Posted
  • Author
Posted (edited)

Curt harness showed up so had that installed in 5 mins or less. Had a bedliner put in before I got the truck and they went right over the plug in the bed so the hardest part was getting the plug out.  Took the tail light off and then had to end up cutting around it through the bedliner just to pop it out.  At least they out it on thick. Now I know.  Either way. Have the loom and end zip tied to the tie down point while I wait for the hopkins plug end. Should be here hopefully Tuesday or Wednesday.  Should be able to just plug in the CURT piece and snap the Hopkins piece in place and be done if all works out the way I figure it should.  I'll let ya's know soon as I get it...

Edited by THE YETI
THE YETI Enthusiast

THE YETI

Posted
  • Author
Posted

Hopkins plug showed up, and just as I suspected. They work together just fine.  The hopkins plug didn't fit the in bed factory location perfectly at first but a quick adjustment or bending of the one side of the 'clip' and it popped in to place.  So best of both worlds without having to splice any wires and cause an extra splice for corrosion or issues by combing these two products.  Haven't tested the plug to my trailer yet to make sure I didn't get a defective one. But I'm sure it'll be good to go.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • 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

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...