Jump to content

Recommended Posts

  • 4 weeks later...
Posted (edited)

How "seamless" is your AFM?

Mine, not so much. Granted this is the first vehicle I've owned with cylinder deactivation, it just doesn't seem right to me. It's honestly like it's downshifting when it goes from V4 to V8 at a hill or gust of headwind. And V8 to V4 isn't much better. There is a very noticeable (but not huge) jerk exactly like the transmission is shifting up or down. Have not tried in manual mode yet but will next time I'm out and about.

Edited by MotoMedic
Added Topic Tags
  • Like 2
Posted

If i'm not paying attention, I would never know it switched. If I anticipating it going to V8 to V4, I will notice a slight engagement.

Posted

If i'm not paying attention, I would never know it switched. If I anticipating it going to V8 to V4, I will notice a slight engagement.

 

Same for me.

Posted (edited)

Not noticable unless I look at the dash V4/V8 light.

 

My dads old 07 Suburban had it and that was also seamless.

 

I also had a 2010 Camaro and that was also seamless too.

 

Some win, some lose.

Edited by fondupot
Posted

Some systems are rougher activating and deactivating than others. And for those who think it is rough, it does not any better with age and use.

Posted

Not noticable unless I look at the dash V4/V8 light

same here but with the bigger tires and lift it hardly goes into V4

  • Thanks 1
Posted

Can't feel the shift at all, even when I anticipate it. The dash justs changes to V4. It is better than it was on my 2013.

  • Like 1
  • Thanks 1
Posted (edited)

Not noticeable before MF exhaust. Definitley hear it now, not so pleasant but tolerable.

Edited by mzodarg
  • Like 1
Posted

with the bigger tires and lift it hardly goes into V4

 

This is the biggest problem I'm having with it

Posted

On our Tahoe (08) only knew when it kicked inbuilt watching the dash. It was seamless. Camaro had :) AFM it was seemless except for the audible noise through the exhaust.

 

 

Ryan

Posted

If it wasn't for the dummy light on the info gauge, I'd have no idea it was in V-4. Mine is smooth. Sorry to hear your's isn't.

Posted (edited)

Not noticable unless I look at the dash V4/V8 light

 

Same here by last vehicle had MDS (Hemi) and I did not notice it switching either but it did not have any lights or anything to indicate that it was switching between the two separate displacements.

Edited by reldridg

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

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