Jump to content

Recommended Posts

Posted

I posted a while back about a parasitic battery drain on our 2000 Suburban. It's an LT 1500 4x4, which my wife inherited from her Mom. I put in an Optima Yellow Top, and didn't have an issue for a few weeks. Then the issue returned. I'm sure the battery just masked it for a while. Prior to that, we went through 3 batteries in about 5 years. Since then, I've kept a battery tender on it to keep it charged. We don't drive it much, so I haven't spent a lot of time troubleshooting.

Inspection time is coming up next month, so I've been driving it around lately. I noticed every so often the AC blower would slow down dramatically, all the lights dimmed, and the volt meter dropped to 9. It would last for only a second or two. I timed it while idling, and it happened about every 2 minutes 22 seconds. The RPMs never changed, so clearly it's electrical.

 

The alternator has tested good multiple times at the parts store, but since it's intermittent that doesn't mean much. I replaced the alternator with a new high output one (which is what it came with since it has pretty much all the accessories). I idled it in the driveway yesterday and the electrical only dropped once in 45 minutes. I was pretty optimistic for the first 19 minutes, but my heart sank when it did it again. 

 

I've gone through the exercise of pulling fuses, but no joy. I also replaced the AC blower motor a week ago. Apparently at some point while it was sitting for a while some mice built a pretty significant nest in the void above the blower, and the bearings were shot in the blower. Anyway, I know the blower motor isn't the culprit. The rear AC blower isn't currently working, but I doubt that is the issue since it shouldn't cause issues when the vehicle is off. However, knowing there have been mice in there opens up all kinds of potential causes. 

 

I'm not looking forward to the prospect of pulling the dash to inspect all the wiring, but I realize it may come to that. All the wiring in the engine compartment seems fine. I'll plan a day to let it run and see if I can find a definitive pattern to the electrical draw or interruption, and then start pulling fuses again. I've already removed power from the DVD player and power inverter, so those should be in the clear. If I still can't figure it out by that point, I may spend the money and replace the computer. I hate just throwing money at it, but it is very sentimental to my wife so I'll do whatever is necessary to get it fixed. 

Posted (edited)

any codes? the 2 minute thing could be a circuit breaker resetting or the thermal limiter on an electric motor. Does the a/c work? maybe a compressor issue if it doesn't .

Edited by richard wysong
Posted

What all cycles on a rotational schedule? I know the A/C compressor cycles a lot on or off, I know it's part of the defrost thing, it dries the air so it defrosts more efficiently, that also contributes to keeping mold and mildew levels lower. I WOULD SUSPECT every motor you got, blower front and rear, wiper motor, windshield washer pump motor, bad grounds and shorts can make anything on the vehicle operate irrationally. Man I do not envy this trouble shooting safari!

Posted

The AC was serviced recently, and works fine (except the rear blower, which I mentioned in my post). But I'll run the same test idling in the driveway with the AC (and everything else) turned off this weekend. I'll post the results.

Posted

There are no codes present, and haven't been in quite some time. We had some sensors replaced a couple of years ago, but this issue predates that.

Posted

I used an ODB2 scanner and no codes are present. I've also had it at 2 different shops and they found nothing.

Posted

Tech-2 time Ken.  Or in your case you might want an MDI with GDS software so it will work on your 2016 as well.  

 

You use this tool to see which modules are still awake and how much power they are drawing.  I don't have a GMT800 anymore so I don't know which menu to check that or perform the parasitic draw test.

 

OBDII scan tool only queries the engine module, not the chassis or brake.

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   6 Members, 0 Anonymous, 1,706 Guests (See full list)

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