Jump to content

Recommended Posts

Posted

Hello everyone, I have a question about a problem with my 2005 Silverado 2500 hd 6.0l. For some background, I managed to get the truck back from a mechanic I had working on it but I had to have it towed back to the house. He was doing stuff that I didn't authorize him to do and I'm not sure what all was done. He said it wouldn't crank because there is a problem with the flywheel - which is something he wasn't supposed to be messing with anyway. The truck was running when I brought it to him to change out the wiring harness on the engine.

Anyway, I replaced a couple of things myself, the last one being the starter because it was bad. Now the starter works; it engages the flywheel and the flywheel turns but nothing is happening with the engine. It's not trying to crank at all. He may have replaced the flywheel because it looks good to me - all the teeth are good, nothing cracked or broken that I can see. But it's way to easy to turn. I can do it by hand with no problem.

I'm not a mechanic but I know that's not right. It's not engaging something to turn the crankshaft. The engine is not frozen; I can turn it from the front center pulley and everything moves fine. So what could be the problem?

I need to know what I should see when I remove the flywheel and torque converter. I've been looking but I haven't found the diagrams or videos I need to see for that. Can anyone point me in the right direction for those?

Posted

The flex plate would have to be completely broken for it to not turn the crankshaft along with it. That means the flexplate broke where it's bolted to the crankshaft itself. There is no way to get at those bolts with the transmission in place, so it's super unlikely that the mechanic removed them. The only thing keeping the flexplate in line would be the torque converter bolts holding it in place.

 

191325d1249606866-5-3-vortec-flexplate-d

 

 

Posted (edited)

Broken crankshaft is probably what it is, Pretty rare but I have seen 3 in my lifetime but never on a Chevy, could be as Cam says as well, much more likely

Edited by richard wysong
Posted

I suppose a crankshaft in two pieces is a possibility, but I'd pull the transmission and inspect the flywheel for being cracked where it bolts to the crankshaft.  They are notorious for it.  

Posted (edited)

I agree. The reason I thought crankshaft is that usually a cracked flywheel will make a lot of noise before it actually breaks, If you remove the inspection cover you will see the flywheel move back and forth with the torque converter if the flywheel is broken and if you remove the tc bolts that will confirm it before pulling the trans. I have had success  un bolting the bellhousing,trans mount and letting the engine and trans "hinge" enough to get in with a close tolerance Snap-On ratchet and un bolt and remove the flywheel. It saves a few hours of R&Ring the trans. There is no reason to remove the torque converter unless you are going to change it

Edited by richard wysong
Posted

What a mess! I think you should contact a lawyer... You'll need written proof of what that guy with a lot of wrenches (I won't glorify him with the title of "Mechanic") was authorized to do. I'd threaten to sue for the cost of repairs and for the loss of use of your vehicle (rental fee you would have paid for a like vehicle or damages.....if he doesn't come up with some amount of money I'd really consider taking him to court. Especially if this is his living and he has a business lic. to protect.

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...