Jump to content

Pics Of My Truck


Recommended Posts

Posted
I was looking for some pictures and found the first pics of my truck

 

from day one :dunno: (back in November 09)

 

to day four :dunno: (also back in November 09)

 

Nice truck SWBRC look cool.... Sorry bout that fender dude.

 

 

from day 30 :P

 

as it sits today :cool:

 

Nice wheels

 

Love that tire/wheel combo! Cheyenne FTW!

 

Silverado's sold new in Mexico are Cheyenne's..........

 

Jbo

Posted

How many meds did you take to deal with your 4 day old truck getting smashed up?

 

 

Looks great now!

Posted
Who was the Jerkface who sideswiped your Cheyenne!?! lets hope he Paid for the repairs!

 

it was parked on the street outside my girl's house when we heard the crash

the guy was trying to get away but he's minivan was stuck to my truck

he didn't have insurance because in Mexico is not mandatory but he accepted the responsibilty

however he never paid, so I place a demand with the police and he got arrested three days ago

he spent one nigth and one day in jail

after that his family paid my insurance company for the damage and I should be receiving a check for what I paid in ten days or so

 

so yes, he paid after spending sometime in jail...

Posted
How many meds did you take to deal with your 4 day old truck getting smashed up?

 

 

Looks great now!

 

 

I got drunk to forget about it, haha, I was really sad and angry at the same time

it was fixed at the chevrolet dealer and they did a good job

you can hardly tell that it was in an accident but it'll come up in the record when I try to sell it

Posted
Who was the Jerkface who sideswiped your Cheyenne!?! lets hope he Paid for the repairs!

 

it was parked on the street outside my girl's house when we heard the crash

the guy was trying to get away but he's minivan was stuck to my truck

he didn't have insurance because in Mexico is not mandatory but he accepted the responsibilty

however he never paid, so I place a demand with the police and he got arrested three days ago

he spent one nigth and one day in jail

after that his family paid my insurance company for the damage and I should be receiving a check for what I paid in ten days or so

 

so yes, he paid after spending sometime in jail...

 

 

I bet the Minivan in question was Jap Scrap! I Don't want to think about it being the Industry Leader! (Caravan FTW!)

Posted
Who was the Jerkface who sideswiped your Cheyenne!?! lets hope he Paid for the repairs!

 

it was parked on the street outside my girl's house when we heard the crash

the guy was trying to get away but he's minivan was stuck to my truck

he didn't have insurance because in Mexico is not mandatory but he accepted the responsibilty

however he never paid, so I place a demand with the police and he got arrested three days ago

he spent one nigth and one day in jail

after that his family paid my insurance company for the damage and I should be receiving a check for what I paid in ten days or so

 

so yes, he paid after spending sometime in jail...

 

 

I bet the Minivan in question was Jap Scrap! I Don't want to think about it being the Industry Leader! (Caravan FTW!)

 

 

It was a Pontiac Montana, I really didn't see how bad it was with all the tears in my eyes, haha

I noticed that our tires were stuck, that's why the guy couldn't run

 

by the way, he told me that he dropped his cell phone and when he tried to reach for it he stopped looking at the road ans that's when it happened

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • 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.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...