Jump to content

GREAT news! DFM disable coming soon


Recommended Posts

Posted
On 2/19/2020 at 4:38 PM, hotrodz37 said:

 

Awesome, keep us posted! Appreciate you being the guinea pig haha

 

Also curious to see if like with the AFM disable it, as a byproduct, disables start/stop as well which would be sweet. 

It disables stop/start as well

  • Replies 242
  • Created
  • Last Reply
Posted

Crap!  I just realized something....my Amp Research steps are plugged into my OBD2 port!  I guess I'll just have to unplug them and plug in the Range every time I get in the truck.  I wonder if it would work with one of the OBD2 port splitters?  

Posted
2 hours ago, Mudcon said:

I have been testing it for the last 4 days. So far so good. 

That's good news.  

 

How differently does the truck drive with DFM disabled? 

 

Do you have stock exhaust? If not, how does it sound when driving? 

Posted
21 minutes ago, DuRsT said:

That's good news.  

 

How differently does the truck drive with DFM disabled? 

 

Do you have stock exhaust? If not, how does it sound when driving? 

The main thing I noticed is the little bogg is gone if I am crusing 45-60 and start up a hill. I assum it was from DFM kicking off but it is going. I have the gm performance exhaust on my 6.2.  I only hear the exhaust when I get down on it. The gm performance exhaust is pretty quite at crusing speeds. 

Posted
8 minutes ago, DuRsT said:

Nice.  Automatically kills auto stop as well? 

Yes, no more mashing that damn button...lol

Posted
18 hours ago, lapoolboy said:

Crap!  I just realized something....my Amp Research steps are plugged into my OBD2 port!  I guess I'll just have to unplug them and plug in the Range every time I get in the truck.  I wonder if it would work with one of the OBD2 port splitters?  

Yes the amp splitter works great. I use the range start/stop disable and both the steps and range device work great. 
Amp splitter is beautiful quality compared to others. 
Tom

Posted
Crap!  I just realized something....my Amp Research steps are plugged into my OBD2 port!  I guess I'll just have to unplug them and plug in the Range every time I get in the truck.  I wonder if it would work with one of the OBD2 port splitters?  


Have a chance to try yours out yet?@lapoolboy


Sent from my iPhone using Tapatalk
Posted

Hey all, day 2 with my beta unit and I must say so far so good. I can hear from my exhaust that I am in V8 all the time and  also I can feel the difference in the pedal. There is no more lag of cylinders turning back on when I hit the gas its just power all the time. I have not been on the highway much but the 40 miles highway so far show that the MPG is about the same as before with DFM on. I have tried it with both remote start and normal starting and everything seems to be just fine. I am not seeing the blue light on the range when the truck is off, so it would seem that there is no power to the OBD II port but time will tell for that. Tomorrow (Sunday) I am going on a 300 mile drive which is do frequently and I know the MPG and the ride well so that will be a good comparison. Oh and no more hitting the button to turn off auto stop/start. So at least for me on day 2 of beta I am loving this product. 

Posted

Good to hear things are going well. Mines still stuck sitting in the box as my truck still vibrated yesterday when I went in to test drive to see if I was happy with the latest fix they offered me. Hopefully just a few more days till I can try it out. 

Posted
21 hours ago, Bob Ross said:

Hey all, day 2 with my beta unit and I must say so far so good. I can hear from my exhaust that I am in V8 all the time and  also I can feel the difference in the pedal. There is no more lag of cylinders turning back on when I hit the gas its just power all the time. I have not been on the highway much but the 40 miles highway so far show that the MPG is about the same as before with DFM on. I have tried it with both remote start and normal starting and everything seems to be just fine. I am not seeing the blue light on the range when the truck is off, so it would seem that there is no power to the OBD II port but time will tell for that. Tomorrow (Sunday) I am going on a 300 mile drive which is do frequently and I know the MPG and the ride well so that will be a good comparison. Oh and no more hitting the button to turn off auto stop/start. So at least for me on day 2 of beta I am loving this product. 

Good to hear. this has been one of the things keeping me from getting a new truck. I currently have a 4.8 because it was the only engine option without AFM at the time.

 

I am anxious to see fuel economy numbers without the DFM on 5.3L and 6.2L trucks. I was leaning toward the 2500hd to get a non AFM/DFM engine.

 

Please update us with numbers. 

 

Thanks for your efforts testing this.

Chris

Posted
On 2/22/2020 at 2:30 PM, hotrodz37 said:

 


Have a chance to try yours out yet?@lapoolboy


Sent from my iPhone using Tapatalk

 

Still don't have it....not sure where it shipped from, but I should have it first of the week.

Posted
1 hour ago, lapoolboy said:

Still don't have it....not sure where it shipped from, but I should have it first of the week.

Ogden Utah. Came UPS.

 

Jay

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