Jump to content

Recommended Posts

  • 7 months later...
Posted

I just ordered and received a Range DFM disabler for my 2019 5.3.  While the unit seemed to function ok, I wanted to share something it did that I did not like.  I am by no means bad mouthing the company or product, but I believe that the fact it disables DFCO (deceleration fuel cut off),  should be revealed on their website.  This was a deal breaker for me.  I drive over the continental divide twice a day.  I plugged in the unit and headed up to the divide. Upon heading down the other side, I was constantly on my brakes, even on smaller hills and in 5th gear at 3000 RPM. I promptly unplugged it, and immediately began slowing down, even in 8th gear.  I can,t imagine using this in the mountains with a trailer.   I decided to send it back,as this was unacceptable to me.  I also noticed deceleration mileage was around 40 to 50 mpg, instead of maxed out at 99 mpg.  It actually felt like it was giving it a little bit of throttle.

 

I was curious  if the Range Pulsar LT does this as well.  I'm guessing it probably does.  If anyone knows for sure, please comment. 

Posted

I had the Range on my 2015 5.3, 6 speed, AFM, worked great. I now have a 2021 5.3, 8 speed with DFM. I sent the Range to the manufacturer and they modified it for the new truck. It also works great. I have not experienced the rough shifts since the dealer replaced the valve body.  I don't think the Range effects the shifts. I think the mileage is a little lower, but there is nothing else negative that I have noticed. 

Posted

Do you still have fuel cut off when decelerating? That is my complaint.  It had absolutely no engine braking. Even at 3000 rpm. I sent it back.  I only ran it 15 miles.  No strange shifting and it did keep the dfm from kicking in?

Posted

I plugged mine in for a few weeks after getting it.  Worked as should, but after unplugging, the auto/start feature is still disabled.  Has anyone ever seen that behavior?  2019 5.3L with 8 speed.

Posted
31 minutes ago, brewtus said:

Have you confirmed with RANGE that is how the Pulsar is supposed to function - no engine braking?

No, I didn't. I bought it off of Amazon and just returned. I thought about contacting them, but choose just to return it.

Posted
On 3/16/2022 at 3:04 PM, GSC52 said:

I plugged mine in for a few weeks after getting it.  Worked as should, but after unplugging, the auto/start feature is still disabled.  Has anyone ever seen that behavior?  2019 5.3L with 8 speed.

I haven't had this issue but I have noticed if I leave the unit plugged in and after a few trips I'll come to a stop and the auto start/stop will be activated. I just unplug the unit and plug it back in and its fixed. 

  • 3 weeks later...
Posted

I got a Range DFM disabler for my 2020 5.3L 8 speed. I noticed when i first start the truck it always chooses to use DFM for the first few miles including fuel cut off (99mpg) while on decel and then magically turns it off so it engages at random and i have no control over it. Does not do auto start/stop though.. Does anyone else have this problem? Do y'all unplug it safter every drive then plug it in when you drive again? After about 5 to 10 min it'll kick in and start working. I think the worst time to use DFM is when the engine is cold and that's why it drives me nuts and i end up putting it in L7 until the engine is up to temp then go into D... 

Posted

I wonder if they'll ever release a DFM delete for the 2.7 L3B. Since apparently it does deactivate cylinders even in a 4 banger. 

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

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