Jump to content

Number of Cranks on Cold Start?


Ekordas

Recommended Posts

Posted

It usually takes a couple of cranks to fire mine up first thing in the morning. But as it was stated already. That's normail and it's just the direct injection.

Posted

Don't think the issue is direct injection. It's direct injection "when cold" You guys up north are having the issues..

My truck has never needed more than 1 bump of the key. But I also haven't started it with the temp under 30 degrees.

 

Seems these 2014 just don't like real cold weather. Glad I live in Florida

Posted

Just to be clear, with guys talking about bumps and cranks and whatever else. It still only have to turn the key once, NOT hold it. Then, it takes a couple of turns of the starter/motor to prime it and fire her up - aka, cranks. On my previous work truck, it use to start the same way when the fuel pump was starting to lose a little priming pressure. Wasn't a big deal on that one and it's a concern on the '14 either.

Posted

Direct Injection engines may have slightly longer cold crank times than that of port fuel engines.

Direct Injection systems run at higher pressures, and the mechanical pump on the engine must build up the required pressure before the first injection event occurs.

The below are typical Direct Injection engine crank times on GASOLINE

Start up Coolant Temperature Crank Time

Above 10° C up to 1.5 sec

Between 10°c (50F) and (- 10°c 14F) up to 2.5 sec

Between (-10°c 14F) and (-20°c -4F) up to 3.5 sec

Between (-20°c -4F) and (-25°c -13F) up to 5 sec

Between (-25°c -13F) and (-30°c -22F) up to 7 sec

Posted

tbarn, you're just up the road from me!

 

I'd say that seems about right compared to what I've experienced as well.

Posted

Mine takes about 10 cranks and then puffs black smoke... This is after sitting for 5 hours or more usually, depending on temp outside.. Its been pretty much consistently -20 Celsius or colder since i bought my truck a couple weeks ago. Im going to try just turning the key to prime it first next time.

Posted

Direct Injection engines may have slightly longer cold crank times than that of port fuel engines.

Direct Injection systems run at higher pressures, and the mechanical pump on the engine must build up the required pressure before the first injection event occurs.

The below are typical Direct Injection engine crank times on GASOLINE

Start up Coolant Temperature Crank Time

Above 10° C up to 1.5 sec

Between 10°c (50F) and (- 10°c 14F) up to 2.5 sec

Between (-10°c 14F) and (-20°c -4F) up to 3.5 sec

Between (-20°c -4F) and (-25°c -13F) up to 5 sec

Between (-25°c -13F) and (-30°c -22F) up to 7 sec

Hmmm, I wonder about mine now. Just got it a month age and we were hiiting low teen's every night and I noticed then it seemed to have long crank times, like 3-5 seconds before firing. Guess I'll have to time it next time it gets cold.

Archived

This topic is now archived and is closed to further replies.

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