Jump to content

Recommended Posts

Posted

Hey Guys,

New to the forum, and glad to be finally back into a truck after a few years.  So I just recently purchased a used 2015 denali 6.2 with 55k miles, and the previous owner installed a leveling kit.  Now the problem is that they did not install a relocation bracket for the magneride sensor.  I noticed that it seemed to ride rougher than my dads non denali and so I started doing more research on here and other places.  I had heard that if you didn't want to go the bracket route, you could have the dealer reset the shocks to zero in the computer so the truck knows its level.  Since I had just bought it a little over two weeks ago, I figured I would just take it back to the dealer and make them do it.  When I got there and meet with the suspension guy, he said hes done over 100 leveling kits, and hes's never had to put a bracket in there.  So he said he wanted to check the shocks to see if they were ok, and once he got it up on the lift, he then noticed that they were leaking and would need to be replaced.  He drove it and agreed that the ride was really stiff and said with the new shocks the ride should be 20x's better than before.  Since I didnt have to pay for anything I said absolutely, go ahead and replace the front struts.

 

Long story short, got the truck back, and yes the ride is definitely better, but it still feels fairly stiff.  So I was hoping that if someone on here had the brackets on their's they could hook me up with some dimensions and I could just make some of my own.  I called suspension maxx, but they told me they could only sell me the brackets if I had some sort of proof of purchase, but of course I don't because the previous owner is the one who purchased it.  

 

I appreciate any help or advice in advanced.

 

Thanks, Adam

20180823_194706.jpg

Posted

Hey Adam,

 

I have a set of suspension maxx brackets that I'll measure up in the morning.

 

Sent from my BBB100-1 using Tapatalk

 

 

 

 

Posted

Hope this helps. Depending on your lift height, that will tell you which holes you need to put in. 7c7f1fbaa344252cb4c1fd5eb6094c86.jpg

Sent from my BBB100-1 using Tapatalk

Posted

It looks like the m6 hole is 1" up and then the two bottom holes would be at .5 is that correct?  And again thank you for taking the time to measure it all up.

  • 2 years later...
Posted

Good evening. I just installed a 3” front leveling kit and 2” rear leveling kit on my 2017 Denali. I installed a relocation bracket for the MagnaRide, but I don’t think the spacing was enough for a 3”. My truck is riding extremely rough/bouncy. Any assistance would be greatly appreciated. 
 

John

  • 6 months later...
Posted

JP

Did you have any luck softening up the ride with 3" front and 2"  rear leveling setup?  I am thinking of doing the same to 2016 suburban ltz.  Any advice is appreciated.

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