Jump to content

Recommended Posts

Posted
1 hour ago, mikeyk101 said:

Sorry, a little off topic but... That's an odd outcome. I've been using my RANGE AFM disabler for several years now and it never had an effect on transmission temps or give me any other problems. Well maybe when it was time for emission testing but that's easily solved. What did help for trans temp was swapping out the Transmission thermostat to the updated ones. Mine still seems to run a little warmer than others have reported but stays in the 150-175⁰ range. It only went up considerably north of 200⁰ when I was towing my toy hauler up a steep grade for several miles. Other than that, it has pretty much stayed at a much more reasonable temp. But taking it out and seeing lower temps would confirm that something was going on.

Do you have a 5.3 or 4.3? I have searched and searched for what exactly the AFM disabler does to keep it out of v4 mode, and what several people have told me is that it tricks your computer into sensing a heavy load to trigger the v4 off. If that is what's happening then there is no way the torque converter is not behaving differently.  It may be that it effects the 4.3 differently than the 5.3, or may be something in the new firmware that doesn't agree with the 4.3. When my TQ went out I did the thermal bypass and added 2 transmission coolers, along with the new TQ but my temps still went very high. I thought I would just pull the range out and try it, and my temps dropped tremendously.  I pulled a big load over an hour mostly uphill and my trans temps never got over 169. However with the range in the same trip unloaded id be going past 240. Very Crazy! I have a friend that has a Range on his 5.3 and its been on for years just like you with no problems.   

  • Like 1
Posted

Yes, I do have a 5.3l. And I was doubting you at all in your experience. It just seemed strange but you could be right about the 4.3 vs 5.3. I would assume that if it was tricking the truck into believing it was under load, gas mileage should also suffer but I haven't really notice much difference in V8 using Range vs normal V8/V4.

 

But very interesting...

  • Like 1
Posted
7 hours ago, Jayselectricco said:

Do you have a 5.3 or 4.3? I have searched and searched for what exactly the AFM disabler does to keep it out of v4 mode, and what several people have told me is that it tricks your computer into sensing a heavy load to trigger the v4 off. If that is what's happening then there is no way the torque converter is not behaving differently.  It may be that it effects the 4.3 differently than the 5.3, or may be something in the new firmware that doesn't agree with the 4.3. When my TQ went out I did the thermal bypass and added 2 transmission coolers, along with the new TQ but my temps still went very high. I thought I would just pull the range out and try it, and my temps dropped tremendously.  I pulled a big load over an hour mostly uphill and my trans temps never got over 169. However with the range in the same trip unloaded id be going past 240. Very Crazy! I have a friend that has a Range on his 5.3 and its been on for years just like you with no problems.   

 

How much difference is there in rpm running a steady, say 60 mph between Range and no Range device? 

  • Like 1
Posted
12 hours ago, Grumpy Bear said:

 

How much difference is there in rpm running a steady, say 60 mph between Range and no Range device? 

That's a really good question.  I am not really sure what the rpm difference was, but I know it was driving differently. I actually liked the way the transmission shifted better with the range plugged in. I do remember it being below 2k in high gear running 65-70 about the same as it is now, but it was definitely shifting different. 

Posted
2 hours ago, Jayselectricco said:

That's a really good question.  I am not really sure what the rpm difference was, but I know it was driving differently. I actually liked the way the transmission shifted better with the range plugged in. I do remember it being below 2k in high gear running 65-70 about the same as it is now, but it was definitely shifting different. 

 

I thought perhaps the converter was not locking up. That will generate some heat. 😉 

Posted
51 minutes ago, Grumpy Bear said:

 

I thought perhaps the converter was not locking up. That will generate some heat. 😉 

That would make sense, the range was causing the converter to not lock up and that's what burnt my torque converter up. The new would have been next if I hadn't of pulled it. 

  • 2 years later...
Posted

So I have a 2015 Chevy Silverado 1500 4.3 flex fuel I bought the truck and it has 340,000 miles on it. I replaced the oil pump on it and the oil pressure switch, but I was wanting to know does it have a filter behind the oil pressure switch because it keeps popping up low oil pressure stop engine.

  • 1 month later...
Posted

Hey brother, I'm having the exact same problem with the engine temperature and oil pressure on my 2016 Sierra 4.3 4x4. Any updates? I'm going to replace the thermostat, oil pressure sensor, and temperature sensor to see how it goes.

Posted

Hey brother, I'm having the exact same problem with the engine temperature and oil pressure on my 2016 Sierra 4.3 4x4. Any updates? I'm going to replace the thermostat, oil pressure sensor, and temperature sensor to see how it goes.

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