Jump to content

Recommended Posts

Posted

Update on the afm disable from range..it works for those who need it and don't have a tuner shop near. i agree with cowpie . i don't have a truck for fuel mileage and want all 8 cylinders lit. so i ditched 5.3 afm  motor (sadly) i loved my 07  gmc sle new body 1500 crew cab. stepped up to the 2013 gmc  2500hd crewcab 6.0 L96 /6l90 much happier now with this truck. i was out growing the 1500 anyway . 2 quads on diamondback atv deck and 22 foot travel trailer demanded a 2500 at least (17500 gcvwr) @65 mph cruzin like a caddie on route 66 now.

  • 3 months later...
Posted

Has anyone checked codes after a Range installation to see if there were indeed any codes to indicate it's use?

  • 2 weeks later...
Posted (edited)

I just “installed” the Range AFM disabler today, and it has made the truck definitely more pleasant to drive. Aside from my catback exhaust, I just like how the truck seems to hesitate and struggle with gears less without the v4 mode. I drove around in different scenarios, and I can see losing some mileage on the highway, but much of my driving is 40-50 with rolling hills and the AFM just annoyed me by constantly engaging -disengaging.  I also noticed that I got fewer weird, hesitating down shifts when coming to a stop with AFM disabled. Truthfully this is a small sample size of miles based upon one day, but I love the truck even more as long as the Range device continues  to work as it did today. I know the price is up there, but I like the idea of unplugging it when I need to go to the dealer. Just my two cents for now.  I paid 189 with free shipping directly from Range in order to get the newest version. So far so good. I’ll update in a few weeks. Take care. 

Edited by Jchoi
  • 1 month later...
  • 1 year later...
  • 7 months later...
Posted

I have a 2018 Silverado 5.3L, is there a difference in performance between the red and blue AFM disablers from range?

Posted
On 7/18/2020 at 11:32 AM, dean laginess said:

I have a 2018 Silverado 5.3L, is there a difference in performance between the red and blue AFM disablers from range?

No difference other than color.  They all work the same

  • 1 year later...
Posted

I drive a 2009 GMC1500 sle crew cab I’ve had it on my truck for about 6 months I haven’t tried towing yet because my boats sits in stoorahe on lake havasu year round I’ve noticed a lot of difference in performance and fuel mileage it didn’t affect mikes at all, I also have a hypertech speedometer programmer installed in the truck along with the red range afm didabler no more hesition on a cell no more hunting for a gear the shifts are firm no complaint her my truck also has 5.3 with 342 and 6spd trans it woke it right up

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