Jump to content

Recommended Posts

Posted

I love everything about my 2020 Chevy Silverado 1500 LT 4WD except for the low idle RPM (500) when in park or at a stoplight.  The engine doesn't cut out, but it acts like it wants to and the cabin vibrates just enough to be extremely irritating.  I've talked to 2 dealerships about the issue and asked if they could increase the RPMs to approx. 600-650 RPMs, but they both declined saying that 500 RPMs is the factory setting and therefore no need to change. Any suggestions?  Would increasing the idle RPMs eliminate the slight vibration and provide a smoother idle?  All suggestions are welcome.

Posted (edited)

Actually Disregard - I was going to comment on a hand held tuner but just realized tuning isn't available yet on the 2019 +  For what it's worth I have  the diablo tuner on my 2017 and have the idle RPM set at +100 for same reasons you mention and is perfect now. Sorry couldn't be of more help. 

Edited by reardiff
Posted

Nothing to worry about.  No need to change.  

 

If you really truly most definitely wanted to, it would set you back about $2000 for an unlocked ECM and HP Tuners credits.

Posted (edited)
31 minutes ago, newdude said:

If you really truly most definitely wanted to, it would set you back about $2000 for an unlocked ECM and HP Tuners credits.

Why $2000? Wouldn't it just be $300 for a HP MPVI2, and 10 credits for a 2020 Silverado 5.3/6.2? So around $800. 

That should unlock the ECM and allow for idle RPM programing. 

 

BTW: my 2018 6.2L with 50k idles at 500, and is so smooth I sometimes wonder if it is on at stops. If yours vibrates, I'd wonder if there is a problem (fouled spark plugs, plugged injectors, clogged air, etc).  

Edited by ftwhite
Posted

If it doesn't idle correctly they dealer should be diagnosing and correcting the cause.  (and I don't mean covering it up by changing the idle from gm spec)

 

Clearly they don't all idle roughly as described. 

 

Posted

When I test drove two different trail boss with the 6.2 one idled smooth as glass and one was really bad.  Right before my at4 bit it (valve spring).... The idle quality was crap.  Definitely not normal

Posted (edited)
11 hours ago, ftwhite said:

Why $2000? Wouldn't it just be $300 for a HP MPVI2, and 10 credits for a 2020 Silverado 5.3/6.2? So around $800. 

That should unlock the ECM and allow for idle RPM programing. 

 

BTW: my 2018 6.2L with 50k idles at 500, and is so smooth I sometimes wonder if it is on at stops. If yours vibrates, I'd wonder if there is a problem (fouled spark plugs, plugged injectors, clogged air, etc).  

 

New ECMs are way different than your 2018.  You have to buy an unlocked ECM from HP Tuners and then the 10 credits.  Its $1400 just for the unlocked ECM.  

 

L84 & L87 – E90 Modified ECM Exchange Service – HPTuners

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

 

New ECMs are way different than your 2018. 

Good point.

So maybe OP can call one of the 'plug in' tune companies (SuperChips, Diablo, etc) and see if they have a solution. Since some of their solutions just override ECM values in "real-time" and are advertised as working on 2019+, maybe they have a config that can set the idle speed? They disable DFM/AFM that way. 

Or, find a dealer that is willing to set the idle speed.

Or, find a non-dealer with GM approved equiptment. 

 

Just thoughts. 

Posted (edited)

Vibration at idle...

I still think it is in need of a repair.

 

https://gm-techlink.com/?p=14637

Vibration or Rough Idle in Drive or Park

April 13, 2021

A rough idle or vibration at idle may be present with the transmission in Drive or Park on some 2019-2021 Silverado and Sierra models equipped with the 5.3L V8 engine (PRO L82, L84) or 6.2L V8 engine (RPO L87). (Fig. 15) The idle condition may be most noticeable when the engine is completely warmed up and accessories are off. There may be several possible causes: misfire or an engine concern, wrong fuel used, idle speed fluctuation, or engine mount pre-load.

 

F15-rough-3-C.pngFig. 15

 

To correctly diagnose the potential sources of the idle condition, use the CH-51450 PicoScope oscilloscope following the procedures outlined in #PIP5798.

Begin diagnosis by checking for stored DTCs. Any DTCs should be addressed first. Also confirm there are not any illuminated warning lamps on the instrument cluster.

Next, monitor fuel trim readings and cylinder misfires to confirm there are not any engine concerns. Note the idle speed at this time.

In addition, if premium fuel is required, confirm that it is being used instead of regular fuel.

Perform an analysis using the PicoScope with a single axis sensor or a tri-axis sensor to measure the vibration disturbance frequency at the seat track. (Fig. 16) If the measurement is above the acceptable threshold, perform the Engine and Transmission Mount Settling Process covered in #PIP5798.

 

F16-rough-2.pngFig. 16

 

Any engine mount-to-frame bolts removed during this process must be replaced with new bolts. Both the left-hand and right-hand engine mounts need to be seated to the vehicle frame at the same time to ensure the best alignment. Do not use an impact wrench. Torque the new bolts to specification in sequence. (Fig. 17)

 

F17-rough-1.pngFig. 17

 

If the disturbance frequency measurement does not improve after completing the settling process, replace the powertrain mounts. Before replacing engine mounts, check that the exhaust system is not bound up and that the rear transmission mount is clear of any debris and not damaged. Either of these can result is a higher than normal PicoScope measurement.

TIP: If the vibration condition was corrected following the procedures in #PIP5798, print and attach the “before and after” PicoScope measurements to the repair order. If the vibration condition is still not acceptable after completing the settling process or replacing the engine mounts, open a TAC case and attach your files to the case. Refer to #PIP5601A to upload the files.

For parts information and complete details on the Engine and Transmission Mount Settling Process, refer to #PIP5798.

 

Edited by redwngr
  • Thanks 1
Posted

I realize this isn't totally related, but I had a similar issue on my 2014 Sierra.  They attempted the alignment, then had to swap one of the mounts.  The truck only had maybe a few thousand miles on it, and did it from day one.  After the fix, you couldn't tell the engine was running.  Just my $0.02

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   3 Members, 0 Anonymous, 2,173 Guests (See full list)

  • Latest Articles

  • Posts

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

  • Popular Contributors

×
×
  • Create New...