Jump to content

GREAT news! DFM disable coming soon


Recommended Posts

  • Replies 242
  • Created
  • Last Reply
Posted

Well I'm glad these issues are coming out now, it's unlikely they will be able to do much about it with just a DFM disable chip.  

 

This would likely take a full re-program to fix that piece. 

Posted

So is the overall consensus positive?  Mine is arriving today but I won't be home from Jamaica until tomorrow night, so I won't really be able to test it till Wednesday...

Posted

So far it has been perfect. After I went to 295/75r18 tires and added my corsa exhaust my truck would feel shaky/lurchy when the DFM was kicking in and didn’t ride smooth. With the range it has been flawless and that feeling is completely gone. Stop/start has not kicked in once and the truck feels way better overall. I have 300 miles on the unit so far and not a single issue. 

Posted

Do they offer a fix that disables both the Auto Stop/Start feature AND the AFM so I cna also run on a 8 cylinders full time and not switch back and forth?  Also,can anyone tell me if they are still offering BETAtesting a a discounted price?

Thanks!

Posted

Still waiting on the dealer to finish diagnosing and fix my vibration. Going out of town tomorrow so it's going to be at least the middle of next week before I can try mine. Feel kind of bad that I will have had the beta unit for 3 weeks and haven't been able to try and it give any feedback 

Posted
On 2/26/2020 at 12:07 AM, RaStahmann said:

I signed up for the beta yesterday and received my Range unit today (I'm about 75 miles from them). I'll tell you this is a game changer! Today I drove about 50 miles combined flat and canyon driving. As @Robwcormackmentioned the auto stop/start light stays on in the switch but it never engages.

 

The DFM disable is the best part. The main muffler on my 2020 AT4 6.2 CarbonPro is removed (leaving the two small rear mufflers) and when the DFM would kick in the sound was horrible. Now that the DFM never kicks in the truck sounds great all of the time, and in Sport mode when decelerating the truck will actually downshift. Driving down the canyon it will hold gear better and provide more engine braking (and better sound) than I noticed before when DFM was active. I'll have to go drive the same section with the unit unplugged for comparison.

 

Remote start still works fine

 

At one point today the truck actually felt like it was slightly surging and trying to activate the DFM but never did. I'll have to see if I can replicate it again to provide my feedback to Powerteq.

 

 

Just curious, which Range product did you get?  I am thinking what I want to do is to disable it from switching back and forth between 4 and 8 cylinders and keep it in 8 cylinder mode full time.  The biggest thing I want to do is stopp the irritating Auto Start/Stop feature at every traffic light.  Does the one you have do both functions?  Also, can you send a link where I can sign up for the Beta testing?

THANKS! 

Posted
13 hours ago, jail4u677 said:

Just curious, which Range product did you get?  I am thinking what I want to do is to disable it from switching back and forth between 4 and 8 cylinders and keep it in 8 cylinder mode full time.  The biggest thing I want to do is stopp the irritating Auto Start/Stop feature at every traffic light.  Does the one you have do both functions?  Also, can you send a link where I can sign up for the Beta testing?

THANKS! 

The Range unit does both. The old non beta unit would work to disable AFM and the auto stop/start (most recent version). The new beta unit adds the DFM disable. When Range was still a small company based out of Colorado they had a unit meant for fleet use that would only disable the auto start/stop. Not sure if you can still gewt that after they were bought out at the end of last year.

 

Jay

Posted
48 minutes ago, Jay P said:

The Range unit does both. The old non beta unit would work to disable AFM and the auto stop/start (most recent version). The new beta unit adds the DFM disable. When Range was still a small company based out of Colorado they had a unit meant for fleet use that would only disable the auto start/stop. Not sure if you can still gewt that after they were bought out at the end of last year.

 

Jay

Thanks for the info.  

Posted

After several weeks running mine, I still have not noticed any problems running the range.

Posted
On 2/28/2020 at 3:55 PM, RaStahmann said:

I'm experiencing this as well. Feels like the truck is trying to go into DFM mode but just doesn't quite get there.

 

 

Me too.  Also the surging but only at 35-40 mph when light throttle

Posted

so today I learned that the auto stop start disabling feature doesn't work if your gas light comes on.  As soon as I got gas and cranked back up, was back to working right.  I did turn the truck off and on a couple times before getting gas to see if it was that.  

Posted

Drove it for a bit and didn't feel any of the surging... Auto Start/stop was disabled despite the light being on on the switch.  power delivery felt good, nothing felt out of place... I assume that the motor and trans will continue to sample and learn as I drive and if anything smooth out even more?

Archived

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

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...