Jump to content

another passlock mystery

gmckid
 Share

Recommended Posts

gmckid Enthusiast

gmckid

Posted
Posted

Hi this is my first post,my truck is a 1999 gmc Sierra 2500 4x4 with 6.0 litre engine.I parked my truck for a few months and the battery went dead since the day I owned the truck the door locks never worked and I always used the factory key fob for locking and unlocking the doors.I have since swapped the door cylinder so I have a working drivers side lock that works with key.When the battery died I needed to get into the truck to open hood so I could service battery so I broke into truck.Now the truck starts immediately and then dies classic passlock symptoms.I have tried both relearn methods the 10 minute method and the 30 minute method.When the truck is sitting the security light is constantly on bright orange.When I try relearn procedures the security light alternates between flashing battery then back to security this continues and never stops flashing between the 2.I have always had battery charger hooked up to prevent battery dying.I dont know if this makes a difference I also pulled the abs fuse years ago

I doubt this is a factor but I thought the more info I give the better quality awnsers I may get.The other thing I would like to disclose is that my key fob has lost its programming and needs to be reprogrammed

to unlock doors,will this reprogram while passlock is active.Had fob checked at gm dealership it is functional.

 

Any help greatly appreciated.

  • Replies 32
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

bossier62guy Senior Enthusiast

bossier62guy

Posted
Posted (edited)

What did you do to break in the truck? Have you checked for trouble codes? The truck started and ran fine prior to parking it?

Edited by bossier62guy
gmckid Enthusiast

gmckid

Posted
  • Author
Posted

Good Morning,

Thanks for Reply.

 

Yes i have my own scanner it picks up the abs relay the other codes I have are through a couple of sub menus on scanner which are

above me the sub menu is BODY to SIR then I get

 

code 53-dis 4X signal interupt

code 36-passenger loop energy reserve feed

code 71-defective derm

code 83-driver reserve diode shorted

 

I do not understand these codes or there meaning or if they are par for the course for the passlock.

 

Truck was broken into by wedging passenger door open and sliding unlock lever.

 

Thanks in advance.

bossier62guy Senior Enthusiast

bossier62guy

Posted
Posted (edited)

Yes truck ran fine before parking,

 

Do you think a new key would fool system into relarn mode.

 

Not sure just yet.....I'm not seeing the relationship of you breaking into the door w/ having a Passlock issue. Breaking in will activate the Content Theft Deterrent system (horn sounding/lights flashing). The Passlock & Content Theft Deterrent systems are both part of the Theft Deterrent System. Something else had to have happened. I'm going to have to do a little more reading to see if I can come up w/ ideas.

 

There does seem to be an ignition switch disarm function. Let's see if we can figure out how to reset that.

Edited by bossier62guy
bossier62guy Senior Enthusiast

bossier62guy

Posted
Posted (edited)

Good Morning,

Thanks for Reply.

 

Yes i have my own scanner it picks up the abs relay the other codes I have are through a couple of sub menus on scanner which are

above me the sub menu is BODY to SIR then I get

 

code 53-dis 4X signal interupt

code 36-passenger loop energy reserve feed

code 71-defective derm

code 83-driver reserve diode shorted

 

I do not understand these codes or there meaning or if they are par for the course for the passlock.

 

Truck was broken into by wedging passenger door open and sliding unlock lever.

 

Thanks in advance.

A little "googling" the codes above seem to indicate that your truck has had the airbags deployed in the past.

Edited by bossier62guy
bossier62guy Senior Enthusiast

bossier62guy

Posted
Posted

Is this the relearn procedure you've been trying?

 

Time required, approximately 30 minutes.

 

1. Ensure that the battery is fully charged.
2. Use the scan tool to clear the DTCs.
3. Turn the ignition switch from the OFF position to the CRANK position allowing the vehicle to try and start. The vehicle will start and then stall.
4. Leave the ignition switch in the ON position while observing the security indicator.
5. When the security indicator turns off, which can take up to 10 minutes, turn the ignition switch off. Wait 10 seconds.
6. Repeat Steps 3-5 2 more times (3 times total).

 

The BCM and the PCM/VCM will learn the new code on the next start attempt.

gmckid Enthusiast

gmckid

Posted
  • Author
Posted

yes that is the procedure I used the problem is security light never turns off i have done this several times.The only thing that I haven't adhere to is having a decent battery it does have 12volts put is weak will not last overnight hence battery charger.

gmckid Enthusiast

gmckid

Posted
  • Author
Posted

Same thing security indicator will not turn off keeps flashing between security and battery

 

Will try again starting at step 1

gmckid Enthusiast

gmckid

Posted
  • Author
Posted

well I have tryed everything(well not everything) rechecked for codes, new battery,damn security light will not stop flashing during relearn and will stay constantly lit when truck unattended.

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

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...