Jump to content

Recommended Posts

Posted

How is the auto seat adjust supposed to work in my 2015 LTZ Silverado? When I open the drivers door the seat (most times) moves forward before I can sit in it, it usually moves back when I shut off the truck. Sometimes it does not go forward and I have to pusH the #1 button on the seat controls on the door. Is this controlled by the body control module? Do I need to replace the BCM? There are no codes set for the BCM.

Posted

You could reprogram it so it doesn't move automatically. I don't think it is supposed to move until the key is in the ignition

Posted
13 hours ago, dna9656 said:

How is the auto seat adjust supposed to work in my 2015 LTZ Silverado? When I open the drivers door the seat (most times) moves forward before I can sit in it, it usually moves back when I shut off the truck. Sometimes it does not go forward and I have to pusH the #1 button on the seat controls on the door. Is this controlled by the body control module? Do I need to replace the BCM? There are no codes set for the BCM.

Do you have the easy exit feature turned on?

Posted (edited)

I have no idea if it's turned on or not. When I open the door the seat goes in one direction or the other, usually backwards. It moves forward before I sit down or it just stays backed up all the way.

Edited by dna9656
Spelling, punctuation
Posted (edited)
On 8/26/2024 at 1:22 PM, dna9656 said:

I have ni idea if it's turned on or not. When I open the door the seat goes in one direction or the other, usually backwards. It moves forward before I sit down or it just stays backed up all the way.

 Settings > Vehicle > Seating Position. Enable Seat Entry Memory. Enable Seat Easy Exit.

 

The other thing to check is, what key fob are you using? Each one will have it's own memory settings if they were both set up with the seats.

Edited by JimCost2014
  • Like 1
Posted

What Jim above said. Also, your dash display will show which FOB you're using...i.e. Driver 1, Driver 2....

My wife is short so if I use her key it pushes me into the steering wheel & I have to stop it or get crushed. I started coloring the FOBs to ID mine & hers.

  • Like 1
Posted (edited)

I got one key fob when I bought the truck, I suppose I should get another one.

Edited by dna9656
Spelling, punctuation
  • Like 1
  • 1 month later...
Posted

I got a key made at Ace Hardware, this is THE place to get a key made, way less $ than anyone else!

Posted
1 hour ago, dna9656 said:

I got a key made at Ace Hardware, this is THE place to get a key made, way less $ than anyone else!

You will see if it is the correct key when you do this.

 

 

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 2,189 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...