Jump to content

Recommended Posts

Posted
Looks good, the fitment looks real good,  i have to put shells on too   but hot a good use for my old truck,  so open pickup and also enclosed.  Lol. 
20190530_212130.thumb.jpg.5b6d0d293a5ca91ff9f9ffc1533d0b33.jpg
Now that's how you make a trailer....

Sent from my Pixel 2 using Tapatalk

  • Like 2
Posted

This is my 5th leer 100 xl and have to say I'm a little disappointed in the quality. The pop out window on one side won't close all the way (inch gap), and there is a spot on the cap edge where the paint is peeling up.5454b51f4acf5ffb50c46a79cbaa6c04.jpg3270d74b760b811db51fb5f12dac859e.jpg

Sent from my Pixel 2 using Tapatalk

  • Like 1
Posted

I'm also glad I removed the trail boss stickers. Makes for a cleaner looking cap install. Those stickers are up high and it probably would have overlapped

Sent from my Pixel 2 using Tapatalk

Posted

Here is your before and after hitch height. Parked in the same exact parking spot which is fairly level. Before pic is almost full tank, after pic is less about 4 gallons of gas.

Looks the weight of the leer cap will lower the rear about an honest 1/2 inch.7c906c352f5d590080aa064f2d06eec4.jpg

Sent from my Pixel 2 using Tapatalk

  • Like 1
Posted

Looks good!  Definitely won't overlap the TrailBoss sticker, comes close but not enough to cover it up-

57783251929__47F9B81E-04A8-4974-A228-B2692E0C2390.jpg

Posted
Looks good!  Definitely won't overlap the TrailBoss sticker, comes close but not enough to cover it up-
57783251929__47F9B81E-04A8-4974-A228-B2692E0C2390.thumb.jpg.d3b112fab67c872a0be9a0904a0c7172.jpg
I also removed the leer letters off back glass. Not a big fan of decals.

Sent from my Pixel 2 using Tapatalk

Posted

After a couple days on my truck there have been times I looked at the cap and liked it and other angles I didn't really care for it. I guess the cap on my 16 z71 had such clean body lines that it spoiled me a bit. This new truck has a curved roof and the 3rd brake light spoiler that just make for an awkward transition to the cap. I'm getting used to it, but if I didn't need a cap, I'd probably prefer the look without it.

Sent from my Pixel 2 using Tapatalk

Posted

Had it up on the interstate going 75 into a 30 mph crosswind. Pretty disappointed. It sounded like a hurricane between the truck rear window and cap front window. Loud enough I could hear it over the radio and hum of the duratac tires. Because the leading edge of the cap is cupped and sits slightly higher than the sloping third brake valence I think it creates weird turbulence behind the rear window. Didn't seem as bad with wind at my back.

If I leaned my head towards the back seat and turned the radio off it definitely sounds like constant wind noise. Never had that on my other leer caps. Don't think there is any way to remedy it either. Probably pretty annoying if you had an adult sitting in the back seat.

6bb3cc0dccc4907eae2f73cce3c02fa0.jpg

Sent from my Pixel 2 using Tapatalk

Posted

That sucks about the wind noise, as soon as I saw a T1 with a cap I wondered if there would be issues with that. The only way I can see you 'fixing' that is to create a much tighter gap between the cab and the cap... Maybe some plastic or rubber gasket material?

Posted
That sucks about the wind noise, as soon as I saw a T1 with a cap I wondered if there would be issues with that. The only way I can see you 'fixing' that is to create a much tighter gap between the cab and the cap... Maybe some plastic or rubber gasket material?
Yeah between that and the leaking front and side window in the rain last night I wish I could just return it to be honest. I thought about a gasket of some sort but doubt it would look good. I already have the cap pushed forward as far as it will go without the cap touching the paint in the rear.

Sent from my Pixel 2 using Tapatalk

  • Like 1
Posted

Listened careful with radio off on the way to work this morning. No crosswinds at all this time, and soon as you hit 60 you start to hear wind noise in the back window. By 70 mph you can hear it with the radio on. Just kind of sounds like a window is cracked open a bit. Anyone else with the leer cap notice wind noise on the highway?

Sent from my Pixel 2 using Tapatalk

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

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