Jump to content

Recommended Posts

Posted

Good morning , two days ago when I was leaving work to start my truck. I got this whine or squeaking sound when I turned the key over to start my truck it just whines until I turned it off, tried it again a few seconds later the same thing, I turned it off again, tried to crank it once again and it did crank this time. I’ve never heard this noise before so I did some research and all I kept getting was transmission whining information. This was not a transmission whine. I did more research and found a video. I can post it down later in the comments but I’m the video this guy took his starter to autozone to get tested and as they were testing it. It made the exactly same whine or squeak or whistle as my truck had made. So now I know that weird sound is my starter. Did some more research. That sound is the starter not engaging with the flywheel or pinwheel (plz correct me if I’m wrong) so yesterday morning it cranked up fine, I sat in my truck for maybe 5 mins like every morning and headed to the gas station to get my cup of coffee, turned off my truck , go get my coffee, tried to fire my truck up and it wouldn’t start, no squeak no whistle or no cry from what I know now to be my starter. I wiggle a few cables on my battery, good connections, no visible corrosion, I even had someone say, that battery looks pretty new??‍♂️. I’ve had the truck for almost 2 years now , never changed the battery . Year is 2014 so yeah I called my sister for a jump start and it took five minutes and I was back running. It was pretty early like 7 am on a Sunday Autozone nor Walmart tire center was open so I went back home and tried to wait it out until one of them opened , I went to start my truck and it crank but it seemed pretty weak, i did that maybe 6 times and I said F it let me go to work. I went to work, lunch break I got a small whistle from the start but it cranked went to the store and back...after work I had the same thing started cried one the first turn but it did crank the second turn with no cry from the starter. Made it home did more research and went to bed, this morning I went out to go to work and no crank few clicks , I tried maybe 4 times then I took a video.

i will post the YouTube video with time stamp as well as my video I recorded this morning after trying to crank it. Can someone point me in the right direction.

 

PS Happy Holidays 

Posted
29 minutes ago, stevejones said:

I that wall of text I see the words "new" & "battery" several times.  However, I don't see "new battery" at all...

Huh?

Posted
50 minutes ago, Don1500 said:

Huh?

I believe stevejones was saying the same thing that came to my mind and that is to get your battery checked. Nothing you said would discourage me from first suspecting a poor battery.   Welcome to this forum.  You will find a lot of good advice here especially if you keep your posts short and to the point.

  • Thanks 1
Posted (edited)

Thanks for the hospitality, this is my first truck and I’m trying to learn everything I can about it. Sorry for the long post. I didn’t wanna leave out any details. So I should get my battery tested ? The starter whistling isn’t a problem?

Edited by Don1500
Spelling
Posted

No need for apologies.

 

Assuming the battery is original, go get a new one.  6 years out of a battery is a good life.  Even if it's not the source, you'll likely be needing one in the not-so-distant future.

 

And don't skimp on the replacement.

Posted
13 minutes ago, stevejones said:

No need for apologies.

 

Assuming the battery is original, go get a new one.  6 years out of a battery is a good life.  Even if it's not the source, you'll likely be needing one in the not-so-distant future.

 

And don't skimp on the replacement.

Thanks will do, gonna go home and remove it and take it to the nearest autozone. Hopefully it has enough juice for them to test it 

Posted

Hey I’m back, I bought a battery got the platinum one , the test crank it cranked up fine , I let it run for a couple of minutes and turn it off to see would it crank back up, so I turned it off and tried to crank it and i got the starter spinning sound. Tried it a few more times and nothing no crank still, I popped the hood just to give it a look for maybe 30 secs went back in my truck to try once again before I came in for the night and it cranked. So I’ll just try in the AM to see if It will crank. I also have a video 

Posted

If the battery in new, then most likely it’s the starter. Starter failures are pretty common on these trucks. Some have also noticed connection problems at the starter, either way a starter replacement would handle both issues.

  • Like 1
Posted (edited)
51 minutes ago, Don1500 said:

Ok I will get a starter tomorrow, thanks again 

 

51 minutes ago, Don1500 said:

Ok I will get a starter tomorrow, thanks again 

Yes, you have 2014 it's most likely the starter.  You will not have problem after the newer designed one when they changed the motor mounts time frame?  I can't remember....my god!  They are on p/n 4 or 5 on the vacuum pump...don't worry you will go down that road too!

Edited by mookdoc6
  • Like 1
Posted

 

2 minutes ago, mookdoc6 said:

 

Yes, you have 2014 it's most likely the starter.  You will not have problem after the newer designed one when they changed the motor mounts time frame?  I can't remember....my god!  They are on p/n 4 or 5 on the vacuum pump...don't worry you will go down that road too!

 

2 minutes ago, mookdoc6 said:

 

Yes, you have 2014 it's most likely the starter.  You will not have problem after the newer designed one when they changed the motor mounts time frame?  I can't remember....my god!  They are on p/n 4 or 5 on the vacuum pump...don't worry you will go down that road too!

I have no idea what p/n 4 or 5 means? 
 

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   4 Members, 0 Anonymous, 1,691 Guests (See full list)

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...