Jump to content

Help me identify my suspension lift

LBZdrty
 Share

Recommended Posts

LBZdrty New Member

LBZdrty

Posted
Posted

So I bought a 2006 Silverado 2500hd not too long ago. I had two lb7's that I absolutely loved but wanted the external injectors, 6 speed trans, etc. This truck was lifted when I purchased it and decided I wanted to put better upper control arms in as well as fresh ball joints and beefy tie rods like I had done with my previous trucks. The problem began when I started the upper control arm swap, I noticed the cam alignment pins were broke off for the upper control arm drop brackets but I had to get to work and whatnot so I drilled the passengers side pins out and pressed in new factory pins hoping that would fix the issue, when I set up the appointment for the alignment I asked them to do the cam pins and they said they would. Go to pick up my truck when it was all done at the shop, I went straight to the cam pins, STILL NOT REPLACED. So I went back the next day and asked what was up and they said you don't need them for lift kits like I have because you can put a pry bar in the pockets and adjust it that way. I argued that that's not what our deal was and that they need to be put in and it better not ruin the new set of tires I was getting mounted and balanced the next day. They claimed everything would be perfect but because I had "too many new parts" to properly align it I would have to come back after 1,000 miles which I have never heard of in my life but I agreed to do it for the sake of my new 35's. It pulled hard to the right, brought it back at 800 miles, they called me and said I need to find a fabricator to custom build me new control arm drop brackets because I need the pins.. so I have a super lift extended front driveshaft and some components are nearly identical to my other truck that just so happened to come with a superlift as well. Call up superlift many times over the course of a few weeks, finally get ahold of someone and told him what I have for a truck and I want all 4 drop brackets, sent them to me and I open the box and I got two brackets not 4. Not only did I get half of what I ordered, the parts don't match up to what I have. Call back and ask what the deal is and they said they sent me what I need. Got their email and sent them comparison pictures as they requested and now I can't get them to answer emails or phone calls once again. I really need to get the truck properly aligned so I'm hoping someone can help me identify the lift kit because apparently it isn't a superlift like I had thought. I will attach pictures of everything, thanks in advance and I apologize for such a long post!PXL_20201023_224255325.jpgPXL_20201023_224247918.jpgPXL_20201023_224238842.jpgPXL_20201023_224226405.jpgPXL_20201013_160044260.jpgPXL_20201013_155938501.jpg

 

Sent from my Pixel 2 XL using Tapatalk

 

 

newdude Senior Enthusiast

newdude

Posted
Posted

Is there a name stamped on any of the lift components?  All the ones on the market right now at least have their brand name somewhere on the cross member or the torsion bar drop side brackets (that white plate on the side of your frame with the holes in it).

 

 

LBZdrty New Member

LBZdrty

Posted
  • Author
Posted
Is there a name stamped on any of the lift components?  All the ones on the market right now at least have their brand name somewhere on the cross member or the torsion bar drop side brackets (that white plate on the side of your frame with the holes in it).
 
 
I haven't seen a single thing anywhere unfortunately

Sent from my Pixel 2 XL 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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...