Jump to content

Recommended Posts

Posted

Looking to replace my upper control arms and I want to get upgraded ones. Im not running a lift, but I do plan on moving my 5100's up 1 notch. So basically stock height +1. Most of the ones I'm finding are for a 2"-4" lift and aren't clear in the description if they work with stock height. Any brands I should avoid ? Thanks in advance. 506e28d7aaa428824ab8b9b18101b50c.jpg

 

Sent from my SM-G973U using Tapatalk

 

 

Posted

IMO I would avoid the tubular style. They just look weak.

I'm running Kryptonite UCA'S on my 9" McGaughys lift. They are stout. Replaceable ball joints and lifetime warranty. Around $500 

IMG_20200426_143946_01.jpg

tapatalk_share_-911989951_compressed (1).jpeg

Posted (edited)
8 hours ago, dieselfan1 said:

IMO I would avoid the tubular style. They just look weak.

 

 

 

Looks and performance are two seperate things. While boxed UCA's definitely do look better, tubular UCA's from reptuble companies like Dirt King or Camburg will be made from 4130 chromoly which is far from weak. 

 

Your UCA's look much weaker than the tubular UCAs on my LT kit, probably are to! 

 

Edited by AZ_RADO_RNR
Posted (edited)

99.75 % of people on here and just in general will never do anything to force a UCA failure on any reputable brand. It really comes down to aesthetics and how much you are planning on going through ball joints (press in vs bolt in). Most failures are usually just a flaw in manufacturing mostly by human error, specificly joint fab. Monday job vs Friday. I’ve seen maybe three compromised welds fail and upper or lower control arms in the 18 years that I’ve been building custom vehicles. And the only time I’ve seen one bent was through collision. I have run beltech, djm, tci and porter built on lowered and bagged trucks and Cognito and McGaughys on lifted.. never a failure in one.. all just what look I was going for at the time. 

Edited by CovetedStyle
  • Like 1
Posted
14 hours ago, AZ_RADO_RNR said:

 

Looks and performance are two seperate things. While boxed UCA's definitely do look better, tubular UCA's from reptuble companies like Dirt King or Camburg will be made from 4130 chromoly which is far from weak. 

 

Your UCA's look much weaker than the tubular UCAs on my LT kit, probably are to! 

 

They are far from weak. Kryptonite rules the 3/4 -1 ton front end parts world. Do your research Junior. You want weak leave the stock UCA'S on it.

Posted (edited)

Both of y’all should send me your uca’s and I’ll test them, I’ll send the weaker ones back ? 

Edited by Frankielozano214
  • Haha 1
Posted

Factory UCA's and ball joints. Near factory angles once I got the right spring, N2 pressure and pre-load dialed in.

Inch more travel too. 

 

DSCF3007.thumb.JPG.37919c94e2c090f4693d34128dc9b8f9.JPG

  • Like 2
Posted

I'm running the kryptonite UCAs as well I like em pretty good.

The bolt in balljoints are nice feature imo. They look nice and the angles are perfect on my 2.5in level. All the bushings and balljoints have zerks on em for greasing. I don't do much wheeling so I can't comment on their toughness. Paid just under 500 on eBay from Rudy's diesel.

Sent from my Pixel 2 XL using Tapatalk

  • Like 1
  • 6 months later...
Posted
On 6/4/2020 at 2:13 PM, AZ_RADO_RNR said:

 

Looks and performance are two seperate things. While boxed UCA's definitely do look better, tubular UCA's from reptuble companies like Dirt King or Camburg will be made from 4130 chromoly which is far from weak. 

 

Your UCA's look much weaker than the tubular UCAs on my LT kit, probably are to! 

 

looks like your thread got off topic; sorry!  I was also looking into this.  I'm running 5100 on the third setting.  I don't think we have any option other than stock.  Most are for 2.5" of lift or more.  The angle of the ball joint won't be correct.  I only was looking into this b/c I wanted to add a greaseable ball joint; I don't like the ones that come from the factory with no zerk fittings.

Posted

With my extended travel Fox 2.5 and dirt king UCA I have just under 10 inches of wheel travel. I would get the icons with the delta joint if I was buying them now. They were not out when I bought mine. But since you are running Bilsteins without extra travel you will not need the increased ball joint angles. Get a set that you like the look of that has a sealed ball joint. I have to lube my uniballs about every other month.

  • 3 weeks later...
Posted

I have an RC 2" leveling kit and Cognito UCA's with the bolt in ball joint.  I love being able to grease the ball joint and the UCA pivots.  

Posted

I am running the FabTech upper control arms with the uniball and they have been doing good and i take my truck in the dirt alot

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