Jump to content

2004 Silverado 1500 emissions not ready

Luke Morgan
 Share

Recommended Posts

Luke Morgan New Member

Luke Morgan

Posted
Posted

My truck won't pass emissions. It shows "not ready" for the Evap system, catalyst, and an o2 sensor. I drove it for about 500 miles between tests. I got looking at the vehicles history and it looks like the "not ready" issue has been ongoing for this truck? Any ideas?

Chris Senior Enthusiast

Chris

Posted
Posted

There is a drive cycle that has to be followed to make them set and it is a pain in the ass. Look it up. Try it. If that doesn't work I don't know. I've tested with the Evap not ready.

working on it Enthusiast

working on it

Posted
Posted

There is a drive cycle that has to be followed to make them set and it is a pain in the ass. Look it up. Try it. If that doesn't work I don't know. I've tested with the Evap not ready.

I had multiple problems to solve before my HHR was ready to test. I had parked it a year earlier, when the sticker expired. I fixed ABS sensor, MAP sensor, fuel cap leak, and finally the Evap vent solenoid. I had to restart the DRIVE CYCLE 5 times before I was done, and even so, I couldn't get the EVAP not ready to go away. Total 1100 miles; 200 after last repair. Texas passed it with the Evap still unset. I followed this Drive cycle :post-12584-0-58104600-1484959408_thumb.gif Good luck with your problem; I just got a P0135 code this afternoon, as well, on my '04 2500HD. I cleared the code, and will see if it sets again. I have 8 months to complete that next drive cycle!

post-12584-0-58104600-1484959408_thumb.gif

post-12584-0-58104600-1484959408_thumb.gif

post-12584-0-58104600-1484959408_thumb.gif

working on it Enthusiast

working on it

Posted
Posted

Some scanners can force to evap leak test

Not any of mine. I started with scanning apps: Torque Pro, then OBDWiz using two OBD dongles : a BAFX then an OBDLink LX (used the BAFX until I needed the LX to use the OBDWiz app). Both pps & dongles use a smartphone or tablet to give me the live data and OBD readiness status. I bought an Innova 3100i scan-tool to verify the apps' data, and to read my ABS faults (the apps cannot), I bought the 3100i for cheap ($75), but wish I'd ante'd up another $100 to get the 3130 bidirectional tool. That one will run the EVAP test.

5829BMG Enthusiast

5829BMG

Posted
Posted

Drove one 600 miles and couldn't get it ready. Disconnected the battery touched the two terminals together to drain capacitors then reconnected and drove 10 miles trying to follow drive cycle as best as possible and it passed all systems ready. Try it and see what happens.

Chris Senior Enthusiast

Chris

Posted
Posted

Not any of mine. I started with scanning apps: Torque Pro, then OBDWiz using two OBD dongles : a BAFX then an OBDLink LX (used the BAFX until I needed the LX to use the OBDWiz app). Both pps & dongles use a smartphone or tablet to give me the live data and OBD readiness status. I bought an Innova 3100i scan-tool to verify the apps' data, and to read my ABS faults (the apps cannot), I bought the 3100i for cheap ($75), but wish I'd ante'd up another $100 to get the 3130 bidirectional tool. That one will run the EVAP test.

I have the 3160d. I think I got it for $90 on amazon a couple years ago

  • 5 years later...
working on it Enthusiast

working on it

Posted
Posted (edited)
On 1/20/2017 at 7:11 PM, Chris said:

Some scanners can force to evap leak test

Welp, you're right; five years later, I finally have a scantool that will force the Evap test (but the I/M monitor still shows Evap as incomplete, though the "tests" all reported "ok"). I used a Foxwell NT510 Elite, that I bought with dual programming (for GM and BMW) in January '21. First time I tried it on the 2500HD, though. I'm about to get the yearly inspection on Monday or Thursday, so I was checking the monitors (one incomplete monitor is OK in Texas), so I scanned/tested the truck today.

 

It showed nine powertrain faults, of which none showed up on my Innova 3100i scantool. Some of them were evap codes (there before I fiddled with the active tests), some were cruise control (which I added years ago, so the ECM might not recognize), and a few were transmission-related (I have first gear slippage starting); of course I wanted to, but couldn't clear them, fearing a repeat of the extended drive cycle nightmare I had in 2017. I'll clear them after the inspection!

Edited by working on 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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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 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?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      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
    • davester
      Replacement Radiator

      By davester · Posted

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