Jump to content

Rear Door Wont Open From Inside

DACIII

By DACIII
in Troubleshooting & Recalls

 Share

Recommended Posts

DACIII New Member

DACIII

Posted
Posted

Sorry in advance for the long post just want to cover everything. A couple months ago I replaced my door speakers in my truck and after putting everything back realized a flashing yellow light for my child safety lock when my truck starts. Now my truck rear drivers side door wont open from inside it opens from outside. I believe the door thinks its on child safety mode but i don't know. I took the panel off the door this weekend and when I take the cable out for the handle I can turn child safety on and off no problem usually it would blink if i turned it on. I then pulled the cable with my hand where the ball is and I could hear the door engaging  so then I closed the door and got in and pulled the ball and the door opened. I figured out when i put the cable back attached to the door is when it doesn't want to work but,  I put the door panel back on and tried again and it worked so then I drove out of garage and got my wife to try to open door from outside so she pulled handle and it wouldn't open even though the truck was unlocked so then I hit child safety and then it went back to doing the blinking again but then allowed her to open door but then it went back to not allowing exit from inside. 

ksenter Enthusiast

ksenter

Posted
Posted

I apolgize.  Was washing my truck today and realized the toggle I was referring to is not present.  I was thinking of my wifes pathfinder.  Again, my apologies.

  • 3 years later...
hunterb01 New Member

hunterb01

Posted
Posted

I am having the same issue.  I have a 2014 silverado LT. The child lock blinks when the truck is switched on and the rear driver door will not open from the inside. I switched the truck on and pressed the child lock button and it quit blinking, allowing me to open from inside. Then I pressed the button again and it won’t allow me to open from the inside and it’s back to blinking. I have pulled the door panel, fuses, scanned for any codes and everything checks out.  I am absolutely stumped and I really don’t want to take it to the dealer. Can anyone help me?

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