Jump to content

Recommended Posts

Posted

I had 285/75r17 on a 17x9.5 rim on my truck when I bought it with a 2.5 leveling kit with no rubbing.  Now I have it with a 33x12.50 on a 22x12" rim with a -51 back spacing with 2.5 leveling kit and 1.5" body lift.  I rubbed bad until I did the norcal mod.  Now it will rub if I'm turning sharp across a ditch or something.  

00b0b_7qqW6zmORVL_600x450.jpg

IMG_0544.JPG

  • 3 weeks later...
Posted

I’m excited, I finally get to get my setup installed on Monday.  I was surprised Firestone was going to be open on Labor Day, but that’s good for me.  Ck157’s with a 33x12.5. 

 

Posted
Got them on. Just thought I would share. 
E599E41D-B061-485F-9651-166673B03156.thumb.jpeg.3bd5e7849411f15ecd0801a56569a162.jpeg
Looks good fatty [emoji106]
Where did you get the rubber?
Never heard of Venom.

Sent from my Pixel 3 using Tapatalk

Posted

It’s actually venom power terrain hunter xt. I really like the tread pattern. I used priority tire. Some others carry them online. They had the best price. They run small. I didn’t know it at the time. They measure 32x12. I might have gotten 35’s from them had I known. Which would have meant a new lift of some sort. 

Posted (edited)

My garage height is really limiting my options come time when I get new tires. Availability also is. Not much available in a P rated tire in the 33" range. I am not at all interested in a A/T or an M/T tire. Too heavy for me. My truck will never see mud. I have another truck I can get dirty if I need too.

Best I can do is a 2" level with 305-45-22.

3/4" taller and 3/4" wider than 285-45-22

This should clear no rubbing I hope. NorCal mod is easy though.

Pretty sure this only going to raise the front 2-3/8" .

I have about 3" clearance the way it sits on the 285-45-22.

My other option is to say f the garage and go with a 4"-6" lift and 34"-35" tires. I'm keeping my 22's either way.

I like to park in my garage though. 

Edited by dieselfan1
Posted (edited)

5caa682090b38_20190407_115555sun(3)comp.thumb.jpg.55e2b7b32a9bf84be3cce9ca259327fb.jpgFattyz - Looks good.

 

Dieselfan1 - I'm running the 33x12.5-r22 on a 10 wide rim. Of the choices with a stock rim the 305/45r22 would probably be the way to go. Much lighter than the other options like 10~15lbs per tire. The 33x12.50r22 is noticeably heavier and you get punished in all performance aspects, with the exception of they off road better/ride slightly better.. 

 

 

 

 

Edited by kennerz
  • Like 1
  • 4 years later...

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