When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I say we start a spreadsheet for failures and warranty denials based on Forscan changes. Kind of like what Epic posted on features. Who wants to start? Maybe even one person from the 200+ pages of F150 guys making changes? Naw. Maybe someone here? Anyone? Bueller?
I agree, the sky isn't falling. But I wanted people to know exactly what they were getting into. There are certain risks, and they should be prepared to accept them.
I don't know of any warranty denials to date, but I also have to imagine that this is largely flying under the radar at the moment. Blindly saying your warranty will be 100% ok I think is unproven, only Ford can determine that and I'm willing to bet if you called them up and asked they wouldn't exactly be ok with it. Just because it hasn't happened yet, doesn't mean it won’t. Think back to the infancy of tuners, it took the manufactures awhile to catch on then too. This is no different, we are just ahead of them for the moment. The argument can be made that tuners are more dangerous because they change fuel parameters, etc. which leads to premature failure. I'd argue that Ford doesn't care about the premature failures directly, they care about their liability, whether that be in warranty dollars, or anything else. This is a potential liability for them that they will want to mitigate.
Knowing all of this I still chose to change those bits, but my situation is different from everyone else’s. I’m just trying to inform people so they can make an educated decision for themselves.
But I’m just a French model on the internet, choose to believe what you will.
Comparing to a tuner is apples to oranges. Your not making the truck do something it wasn't designed to do. The options that are being changed are also capable with Ford software. Some were disabled for marketing reasons. Others are enabled or disabled based on region. IE: DRL's in CA vs. the US. There is no liability to mitigate as a vehicle failure isn't possible from said changes. Liability for something like having your fogs on at the same time as your high beams lies with the person making the change. Not Ford.
Lastly, while this may be newish to Ford, it's been going on for a very long time with no negative results with other brands. Take BMW for example. Guys have been coding their cars for years. Here is a thread much like the F150 one or the one Epic just started. http://f15.bimmerpost.com/forums/sho....php?t=1033991 The software is not Forscan but another that does the same for BMW. Most of the options have been figured out by now so it's not Hex but rather plain English... well, plain German options. Now, these guys are far more paranoid about warranty issues than SD owners. So bad that many won't even change their own oil. Yet, never a warranty issue or bricked car to stir the collective pot there.
So as to your French model status, yep. That's about it. Same as mine....
I've got a VM configured and running and FORScan connected, but I apparently need an extended license to get far enough to disable hyper flash. Any experience on how long it takes to get that far? I've requested a forum account.
Less than 24 hours. Once admin approves your forum membership, you can generate your extended license and get to work. It is only good for 2 months but you can easily generate a new on then to keep using the program...
Less than 24 hours. Once admin approves your forum membership, you can generate your extended license and get to work. It is only good for 2 months but you can easily generate a new on then to keep using the program...
Thanks. Got it up. Haven't worked out bulb outtage, though.
Originally Posted by rocket_scientist
If you use a usb adapter you should be able to use virtualbox and the passthrough. Never tried usb with qemu but I'm not sure there's a bridge for it. I do a lot of qemu-based simulators for embedded systems as part of my job, but I've never used KVM to run a windows machine. I use virtualbox for that.
Yeah, in my brilliance I hadn't actually enabled KVM. Was using qemu w/o KVM, adding KVM solved that very quickly.
go to forscan.org. Create an account on the forum, wait a day or two to be accepted. Download the software from that site, install and follow the instructions on the site to get the extended license.
which software version is the one we need for these ’17 trucks?
thanks
I installed it and used it to turn off the annoying double horn honk and enable fog lights with high beams. Nice. Any chance on ForScan enabling reverse camera views without shifting into reverse and front camera view while driving?
I installed it and used it to turn off the annoying double horn honk and enable fog lights with high beams. Nice. Any chance on ForScan enabling reverse camera views without shifting into reverse and front camera view while driving?
Mine did that when I put it in 4x4. Camera stayed on for 5 minutes. Pretty sure it was not suppose to nor right but my truck seems to have its own personality.
Mine did that when I put it in 4x4. Camera stayed on for 5 minutes. Pretty sure it was not suppose to nor right but my truck seems to have its own personality.
@Sleepyguy, can you give me some more details about the camera staying on for 5 minutes? Did the truck ever go faster than 5mph/10kph in this time? Do you have ForScan? If so your truck might be the key to unlocking the camera on while at any speed settings. Very intrigued to see what you have to say!