Jump to content

Recommended Posts

  • 4 months later...
Posted

I had noticed that my remote also had unusual wear on my 2014 Not quite as bad as OP but it was getting pretty ugly. I do use a Neutrogena original hand cream and that is what I thought at the time might have affected the remote? Traded it in a month or so ago so no way to post a pic....

Posted (edited)

My one employee picked up a low mileage used 2014 and his fob although not as bad as the op looks quite similar. In fact we test drove a few 2014's on his hunt and all of them has screwed up looking fobs with peeling and fading. My 2015 is sitting at 25000 miles and it's, fob looks new so... I don't know lol.

 

For programming it may be interesting if Dorman releases a tool for it. I just added fobs to the used 2004 Malibu we have and that same kit works on vehicles through 2012 or later all of which require dealer programming. They aren't the kind you can do lock cycle sequences to program with like my 05 Sierra as an example. The car has command start among all your other normal functions. It's just a stick you plug in the obd port and then press and hold lock and unlock simultaneously. Beats paying GM or finding a locksmith.

 

Sent from my PURE XL using Tapatalk

Edited by 1994Vmax
  • 5 years later...
Posted

I just bought a 2017 Silverado with 4400 miles. both of the remotes look like they are from a 200,000 mile truck. the rubber on them are sticky like they are melting. when i was searching the net for a truck I noticed the ads that had pictures of the remotes looked the same way. even though the miles were low. 

  

Posted
10 hours ago, jimsmith1957 said:

I just bought a 2017 Silverado with 4400 miles. both of the remotes look like they are from a 200,000 mile truck. the rubber on them are sticky like they are melting. when i was searching the net for a truck I noticed the ads that had pictures of the remotes looked the same way. even though the miles were low. 

  

Bought one of these off of Amazon, $12.95. Not too bad of quality. The factory ones do not last long for some reason.

 

KeylessOption Keyless Entry Remote Control Car Key Fob Case Shell Button Pad Outer Cover for GMC Chevy M3N-32337100

81qgzq1fWgL._AC_SL1500_.jpg

Posted

My 2016 key fob buttons are beginning to wear, but nothing like the OP!! His fobs look like they boofed into a prison many times... I want to go with something like this:

image.png.dac3b3eed324b02a56133a2f8033d551.png

 

I just sent AJT Design an email to see  if they can sell fobs with different color buttons like this one, I like the RED panic and BLUE remote start. $39 on AJTdesign-llc.com.

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

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