Jump to content

Recommended Posts

Posted (edited)

I join forums for all of the vehicles I own.  This is my first American vehicle and truck.  2018 Silverado LT Z71 Redline Edition.  I bought a a few days ago.    I originally had a FJ cruiser, but I wanted something with a bed.  Thankfully the FJ held on to so much of it's value that it made getting this decked out truck easy.

IMG_20190501_225649_038-540x540.jpg

Screenshot_20190501-223600_Gallery-540x262.jpg

IMG_20190501_225649_037-540x540.jpg

Edited by jaimeastin
  • Like 3
  • Thanks 1
Posted
On 4/13/2019 at 5:46 PM, mitchely03 said:

wash day

xg3lhief23s21.jpg

I've seen your truck recently.  Drawing a blank where we were at the time.  Kids play a traveling game, "translate the personal tags," left yours at "NO SPICY," and commented "whatever that means."

Posted

Bought it yesterday. Got tired of leasing and found a good deal on a low mile 2014.bf7bb77eb875094d2829137934424aff.jpg

 

Sent from my SM-G965U using Tapatalk

 

 

 

 

 

 

  • Like 1
Posted
3 hours ago, Ravenkeeper said:

I've seen your truck recently.  Drawing a blank where we were at the time.  Kids play a traveling game, "translate the personal tags," left yours at "NO SPICY," and commented "whatever that means."

Hahha that’s awesome. It’s a joke between my friends and I with spicy food I can’t really it. And how a lot of the social majority make fun of white people and spicy food. I always laugh when I see people behind me. It always goes the same way. They are looking, squint, point and then laugh ? 

  • Haha 1
Posted
1 minute ago, mitchely03 said:

Hahha that’s awesome. It’s a joke between my friends and I with spicy food I can’t really it. And how a lot of the social majority make fun of white people and spicy food. I always laugh when I see people behind me. It always goes the same way. They are looking, squint, point and then laugh ? 

Got it. I'm kind of right there with you.  My son keeps testing his tolerances for SPICY, all the time.  One of these days, I'm going to take him to CoCo Ichibanya (Curry House), in Long Beach.  Use to have that all the time in Okinawa, could only tolerate up to "Level 4." 

Posted

3ed9fb20690172afd2a25ce6296858da.jpg13ec44fa3e983d1ed244ea8b3de5828b.jpg35bf7092436f5345cd49935ea214b657.jpg

Got a new toy to tow. She towed it pretty well even in some severe winds and traversing some hilly terrain. MPG could be better than 9.5 but I didn’t expect anything more really.


Sent from my iPhone using Tapatalk

  • Like 4
Posted

Just purchased a 2018 Sierra 4wd.  Love the truck!  Currently only at 388 miles.  It’s a year old and while sitting at the dealer it was rarely test driven.

 

i came out of a 2007  F-150 reg cab/SB/V-6.  It pulled the camper, but with little to no power.  I knew that this truck would obviously tow it much better, but blown away by how much so.  Two thumbs up for the factory brake controller.

C9A67C4C-FE90-419B-88E4-FBDBCF77E03D.jpeg

135766D0-2445-4C44-B3C0-B9FCDC0C2A65.jpeg

  • Like 3

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   4 Members, 0 Anonymous, 1,858 Guests (See full list)


  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...