Jump to content

Recommended Posts

Posted (edited)

Hello everyone, I'm new to this forum so forgive me if this topic is a repeat. I couldn't find a thread,  anyways I recently lifted...

 

 

 

 

Edited by Frank Ybarra
Punctuations.
Posted

So....Fabtech, Cognito and BDS...the three biggest names that engineer and build these kits are ALL telling you to take an inch out of the rear block and you still want a bunch of keyboard jockeys to tell you some knucklehead butchered a setup stacking and it was right as rain? 

 

🤔

 

Take the inch and get happy

Posted

I bet that info was in the installation guide too...   That is a good looking ride, but I'm glad I don't have to climb into it every day...   ")

Posted
1 hour ago, Grumpy Bear said:

So....Fabtech, Cognito and BDS...the three biggest names that engineer and build these kits are ALL telling you to take an inch out of the rear block and you still want a bunch of keyboard jockeys to tell you some knucklehead butchered a setup stacking and it was right as rain? 

 

🤔

 

Take the inch and get happy

They also didn't recommend me using 12 wide wheels. Theres a difference between what the manufacturer recommends and what can actually be done safely. I just thought someone has been in this situation recently and wanted input... unfortunately taking an inch off the rear isn't gonna make me happy.

Posted
2 hours ago, Frank Ybarra said:

They also didn't recommend me using 12 wide wheels. Theres a difference between what the manufacturer recommends and what can actually be done safely. I just thought someone has been in this situation recently and wanted input... unfortunately taking an inch off the rear isn't gonna make me happy.

 

 That recommendation comes with a good deal of insight attached to it. 

Like. I recommend a parachute when jumping from a plane at 30K feet. 

It may not make you 'happy' but it will be 'safe".

 

I'm wondering what you consider safe.

 

The don't recommend the 12" wheels as a 'safe' scrub radius can not be maintained. Just because a thing can be done and even is done doesn't make it safe or even smart. 

 

You had to put a tape to it to even know it was not dead level.?

 

As far as getting 'input' I gave you some. You didn't like that either so....what you really want is 'agreement'. That I'm not going to do. If you didn't know how your wheels affected scrub then you also do not know how the lift altered every angle in the dynamics of the alignment. Effect on dampening.  Something BDS carefully considered before putting a kit out that would get them in some pretty hot water if they built it without regard for YOUR safety and their liability. 

 

  • Like 1
Posted
33 minutes ago, Grumpy Bear said:

 

 That recommendation comes with a good deal of insight attached to it. 

Like. I recommend a parachute when jumping from a plane at 30K feet. 

It may not make you 'happy' but it will be 'safe".

 

I'm wondering what you consider safe.

 

The don't recommend the 12" wheels as a 'safe' scrub radius can not be maintained. Just because a thing can be done and even is done doesn't make it safe or even smart. 

 

You had to put a tape to it to even know it was not dead level.?

 

As far as getting 'input' I gave you some. You didn't like that either so....what you really want is 'agreement'. That I'm not going to do. If you didn't know how your wheels affected scrub then you also do not know how the lift altered every angle in the dynamics of the alignment. Effect on dampening.  Something BDS carefully considered before putting a kit out that would get them in some pretty hot water if they built it without regard for YOUR safety and their liability. 

 

 

So I'm gonna raise the front either way. I wasn't looking for agreement. I was hoping to hear from someone else who was in this similar position.  And worse case if no one had, then I thought maybe seeing how my next steps would help someone else. But I now realize why I don't do forums and why I shouldn't have started this topic. Sorry guys. Godspeed .

Thanks Grumpy 

Posted (edited)
13 hours ago, Frank Ybarra said:

Hello everyone, I'm new to this forum so forgive me if this topic is a repeat. I couldn't find a thread,  anyways I recently lifted my Sierra with a 6" BDS kit and after driving it for 150 miles I brought out the measuring tape. It's 1.25" lower in the front than the rear. I called BDS and they tell me that the kit is engineered to maintain a similar factory rake. Well I want the truck to sit level without having to drop the rear, which I know is the 'easy' fix. Has anyone encountered this problem?

 

Its not a problem, it's designed to be that way.  If you want to remove the rake, either drop the rear with a smaller block or add a spacer to the front.   Adding a spacer to the front is easy peasy, but I would check with BDS to make sure that adding a spacer to their kit doesn't void any of their warranties though.  Honestly though, I HIGHLY doubt you, or anyone else, would notice a 1" adjustment on that truck.  

Edited by Gangly
  • Thanks 1
Posted

It already looks nose high from the side as it sits. Guess stacking kits is the way to go since you know what is safest. Buy a spacer off ebay, throw it on and call it a day. Make sure to adjust your headlights down too so you aren't blinding traffic. 

 

Tyler

Posted
2 hours ago, Frank Ybarra said:

 

So I'm gonna raise the front either way. I wasn't looking for agreement. I was hoping to hear from someone else who was in this similar position.  And worse case if no one had, then I thought maybe seeing how my next steps would help someone else. But I now realize why I don't do forums and why I shouldn't have started this topic. Sorry guys. Godspeed .

Thanks Grumpy 

 

Ever play chess Frank? You never move just one piece on the board. Every move moves that piece and opens or closes another's ability to move.  Raising or lowering a vehicle has that exact same effect. Tis the very reason these companies hire engineers and use C.A.D. to do all the what if's. Guys that ignore their advice break things like ball joints then complain the builder makes crap or worse. Like your day in court explaining to some judge why your truck made some wonky move that killed somebody. "No sir, not my fault. I took forum advice and THEY said it would be fine". Play that back in you noggin Frank and yes it will sound as stupid coming from you as it did as I typed it. Get a grip. 

 

Nobody here is going to run simulations for your BDS didn't already and come to any different conclusion than they did. Best your going to get is what you've already gotten. 

Posted

No one is stopping you. Have at. 

 

"Hey guys will someone try this wine and see if it's poison so I can have some".

 

Be your own cup bearer. It is what your asking.

 

"Can someone whose gone against the advice of three major kit builders and tell me if you broke anything or hurt anyone doing it and how you did it"? 

🤔

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

    • 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.
    • 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.
    • 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?
    • I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...