Jump to content

Recommended Posts

Posted

All

 

Newbie here looking for some help.

 

My 2006 Avalanche with 180K has the dreaded cam chirp.  I isolated it down by removing the accessory belts and the chirp remained and increased with engine speed.  Doing some on-line research as to what I will need to do a cam and lifter swap in this 5.3, done a few on my 350 small block in the Vette but the LS motor is new to me for a tear down.  Anyway trying to do research on a cam and lifters because since I'm in there maybe there is a bit of extra power I can squeeze out without affecting drivability .  As this is our weekend highway cruiser to the lake I need to keep the better half in my good graces and keep it as close to stock running as possible.  I do use the truck to tow the boat and a trailer regularly so I was looking at possibly getting a cam that may give me a bit of a boost in low to mid end torque.  I can easily get a replacement LM7 stock cam and new lifters and be quite happy with the truck back to bone stock.  While towing I'm never pushing the rig to high RPM's and it lives life below 4K RPM most of the time.   However there seems to be a few cams out there that may give a bit of a boost without the having to upgrade springs and get a tune.  Looking at a good used LQ9 from a 6.0 that if I'm right will give a bit of increase and idle like the stock LM7 cam.  Also looking at the Crane TruckMax "drop in" cam at 200/208 that they say works with stock tune.

Any advise out there on these low lift cams?  Biggest thing I'm looking for is to keep the idle smooth and possibly pick up some increase in torque for towing.   

Thanks in advance

Posted

You could look at the Brian Tooley Racing Stage 1 truck cam.

Should keep you close to stock but a little bump in power.

I'd look in to upgrading the valve springs to the "beehives" and adding the trunion kit to the rockers if you are going to push any more RPM.

I put the Stage 2 in my 5.3 -> 5.7 LS1 build and it's got a definite lope, but great bottom to mid range power.

I pull a 6000# travel trailer and daily drive the truck.

Sent from my moto g(6) using Tapatalk

Posted

I agree with the above, I would still do new valve springs and the trunion upgrade even on a small camshaft. It's good piece of mind if you ask me. Most small camshaft can do LS6 springs.

 

You'd have to stay on the small side if you wish to use the stock tune, anything larger will want a real tune done to help dial things in. If you're in the twin cities metro I could help with a 6.0 swap tune or a small camshaft upgrade, those would be pretty easy to tune.

  • Like 1
Posted
8 hours ago, CamGTP said:

I agree with the above, I would still do new valve springs and the trunion upgrade even on a small camshaft. It's good piece of mind if you ask me. Most small camshaft can do LS6 springs.

 

You'd have to stay on the small side if you wish to use the stock tune, anything larger will want a real tune done to help dial things in. If you're in the twin cities metro I could help with a 6.0 swap tune or a small camshaft upgrade, those would be pretty easy to tune.

My goal really is to have this truck continue to idle a close to stock smooth as possible.  It cannot have the cam lope of a bigger cam as my wife drives the truck as well and hates the idle of the Vette we have.

When you say small camshaft, is the BTR Stage 1 on the easily tunable side to get the idle smoothed out?  It looks like that cam offers a bit more lift and duration but nothing too extreem.  

From research it looks like the LQ9 cam does not offer too much gain over the LM7 but since I have to go into the motor anyway the price of a used LQ9 is not breaking the bank for little gain.

I'm on the NW corner of the metro area in MG, not too far from you.

  • Like 1
Posted

Yeah a stage 1 camshaft is a good small one. You could go with a BTR or even a Texas Speed camshaft, either one should be just fine. With a tune it's probably an easy 20-25hp gain.

  • Like 1
Posted (edited)
On 10/5/2020 at 6:11 AM, 86Pacecar said:

My goal really is to have this truck continue to idle a close to stock smooth as possible.  It cannot have the cam lope of a bigger cam as my wife drives the truck as well and hates the idle of the Vette we have.

In my opinion, you're looking for something like the Brian Tooley Torque Cam, designed specifically for trucks.  Probably a better choice than any Stage 1,2,3 for your application.

 

As long as your replacement cam doesn't have too much lift, the stock springs will probably perform well, beyond the life of the vehicle.  Beehives usually can't make the same claim.

 

Welcome to the world of $400 cams.  Look on the bright side.  You don't really have to change your factory springs.

 

 

 

 

 

Edited by GhostWriter
  • Like 1
  • 2 months later...
Posted

Well got the cam and lifters swapped out,  I went with a used LQ9 cam and new lifters.  Runs like new again!

I guess I waited too long once I heard the first bit of chirping from the old cam

 

lifters.jpg

cam 1.jpg

cam 4.jpg

cam 2.jpg

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

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...