Jump to content

New Pics And New Exhaust Clip

thecraft

Recommended Posts

thecraft Senior Enthusiast

thecraft

Posted
Posted

I just got a set of new Cooper Discoverer ATR tires yesterday, and today I washed the truck and took some new pics. I love these tires, even though I haven't got to really test them yet. They made the truck look completely different. You can see all the pics at my CarDomain: http://www.cardomain.com/ride/2584396 I also have higher res. pics if anybody cares.

 

I also got a better exhaust clip now too: http://www.youtube.com/watch?v=T2VaxCj3SYw

 

What sucks is that in just five miles between where I washed my truck and where I took these pics, I manage to hit about five millions bugs and sling up some mud on the drivers side of the truck. :sigh: The chrome on my grille is also starting to peel off. :(

 

I also installed this Lightning Audio bass package last week. I wasn't looking for a system that would piss off all my neighbors, I just wanted something that would fill out the low end in my music. It did just that, and it sounds pretty good for the money. I do need to get a different box that fits underneath the seat though.

 

Here are some of the pics, more are on my CarDomain page above:

2584396_104.jpg 2584396_106.jpg

2584396_111.jpg 2584396_112.jpg

2584396_118.jpg 2584396_119.jpg

pennzoil29 Senior Enthusiast

pennzoil29

Posted
Posted
Man you have been busy with that thing!!! Sounds and looks great!

 

+1. I like how the birds ad/lib when you pulled away. :sigh:

thecraft Senior Enthusiast

thecraft

Posted
  • Author
Posted

Thanks for the comments.

 

Man you have been busy with that thing!!! Sounds and looks great!

 

+1. I like how the birds ad/lib when you pulled away. :sigh:

 

I liked that too. I just need to remember to shut off the A/C next time I get an exhaust clip, the mic picked up a lot of whine from the compressor.

Archived

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

Go to topic listing

  • 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, 2,136 Guests (See full list)

  • Latest Articles

  • Posts

    • 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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