Forum Discussion
BurbMan
Apr 22, 2015Explorer II
Campfire Time wrote:
But changing parameters like air/fuel mixture or taking off the torque management in the software is far different than modifying the code. So in the long run I think their stance will fall flat.
You are correct, the problem is say you have a 2 year old truck and go in a change a bunch of settings and it won't pass the smog check....manufacturers are on the hook with Fed law to warranty emissions equipment for 50k miles or something like that.
Not one to propose new laws, but we need to keep up with the technology. I would like to see all the vehicle's parameters changeable by the user without any special diagnostic equipment, but then the mfr should be 100% off the hook if the vehicle won't pass smog check, or the airbags don't work, or the motor blows up. Making those changeable variables instead of hard-coded numbers would allow the user to diagnose and repair without accessing or decompiling the code, kind of like Windows or like the BIOS on a laptop. I can change whatever I need to change to make it work best for my application without having to hack in and view the code to overwrite hard-coded variables. I can add memory, a second hard drive, etc.
OEMs need to look at look at making their vehicles' software more serviceable without restricting user repair access. They should be looking for better ways to support their customers rather than going to war with them.
Reason the aftermarket for tires, rims, aux fuel tanks, etc., is so big, because nobody uses their truck the same way, you customize it for your application. OEMs should be advertising the flexibility of their vehicles not how they are gonna sue you if you try to diagnose a check engine light yourself.
About Travel Trailer Group
44,052 PostsLatest Activity: Oct 29, 2025