I've tried this with the same result. I've never had the option show up. I also never received the DTC you saw which is very odd it did that.
BTW on '13-'16 you have to hit 100% full before it will show the option according to the Ford manual. 11's-12's are 85%

I have a '13

That's right, I had forgotten about '13~'16 needing to hit 100%

I thought it was strange to get the DTC also. It does lead me to think that their needs to be another setting in combination to make the OCR work.

Thank you for your input. All the information we gather can help solve this mystery.

Mike, Keith and everyone else contributing to this, Thank You .

I reprogrammed the DRL to turn signals and all works as advertised.

While I was at it, my DPF is at 90% so I figured I would play around with those settings and at least duplicate other results .

My DPF screen was enabled by my dealership.
720-01-01 EA21 BA83 FFF0

However, I am unable to change it. If I change the last set from FFF0 to FF70, it will write successfully but immediately reverts to FFF0. Any other changes to the second set or last set (BA82 7FEF or anything else) results in a write fail. It gets to 50% then reports a connection failure.

I get the same error if I go into IPC module (not as built) and attempt to change force regen from enabled to disabled.

Not sure if I am experiencing another operator headspace and timing issue or if this is a legitimate problem but I the moment, I am unable to test the theory.

Bob

Thanks Bob for helping test out our theories.

Enter these settings.
720-01-01 EA21 BA82 7FEF
Edit: just reread your post and seen that these settings are giving you the write error.

Just a quick explaination, the reason that the setting you tried to enter kept changing back is FORScan was replacing your changed setting due to the software doing the hex math and fixing the check sum values.

On the 1st post of this thread, Just Strokin (Larry) linked to the Fusion forum. Their opening post Does a GREAT job of explaining things. Much better than I ever could.

Edit: not sure why you are getting a write failure(?) I don't remember having any problems entering and saving.

Hth,
Mike

I get write failures on some things as well. maybe I just have a cheap-o ELM adapter. I know mine was $5...

Very possible. This is what I am using. I have not had any problems with it reading or writing.

https://www.amazon.com/gp/aw/d/B006N...7OL&ref=plSrch

I kinda like my 10 year old USB ELM-OBDII adapter. I like the hard wired over wireless for your stated reasons. I am not using TorqPro so do not need wireless any more

same one I'm running have not had an issue

I have tried two different bluetooth OBDII adapters and get the same error. Both adapters are cheap ones so that could be the issue. If the attachments come through, one is starting the write process and the other is the error I get. Hopefully I can come up with another adapter and try again.

Bob

I have read in some of the other FORScan forums that some individuals have issues with the inexpensive adapters due to connection issues. I don't remember which adapters they said to stay away from. The one I use was highly recommended, so I went that route.

This is like the one I use. I think a hard wired insterface might be more stable than WIFI or Bluetooth.

ELM327 USB OBD2 Auto car Diagnostic Tool Car Code Readers Scanner Tool Supports | eBay

https://cimg4.ibsrv.net/gimg/www.for...f03ca2adc8.jpg

Things to be aware of in any of these OBD scanners: the original is called ELM because that company in Canada first developed the code used in the single chip micro. On the first couple of revisions, they didn't bother to blow the security fuses, and it was quickly copied by the Chinese. ELM has since moved on to newer versions, fixed bugs, etc. but have protected their code. 99.9% of the ones you buy on the web are copies and clones of the 1st or 2nd ELM revision, of various (and often dubious) quality. Most of the people making and selling them have no idea how they work, or what bugs and problems could be in the implementation they copied. Some have hacks to fix problems, which themselves create problems. It is almost impossible to buy a genuine ELM based product. The ODBLink is not an ELM clone, but a new implementation that mimics the ELM command set. This allows it to do what the ELM can do (and look compatible to lost of existing software) and also do quite a bit more. It is probably the best one to get (and the most expensive). It is also one of the few that can scan all of the busses in the Ford, not just the primary one. I have purchased several of the clones and taken them apart. You find a range of implementations, some look like they were soldered together by chimps, others are not too bad looking. None of them was a higher revision than ELM 2.1, and several at the same supposed ELM revision behaved quite differently. They are very cheap to buy, but be prepared to buy a few, to find one that actually works.

swarf_rat,
Great info, shows why the inexpensive adapters have write issues. Thanks for sharing!!
Mike

Hey everyone,
I found an address setting that was common among three different trucks with OCR. One of the trucks is the one Larry found. Two others are trucks that I found with OCR. In a hurry this morning to get out the door. I will post up the VIN's on the other two trucks this afternoon.

The 726-03-01 addresses that were common among the OCR truck were one bit different among non-OCR trucks. Decided to try these settings since my DPF is at 95%

720-01-01 EA21 BA82 7FEF, OCR trucks
726-03-01 0201 0000 34, OCR trucks

720-01-01 EA21 BA83 FF70, My truck
726-03-01 0201 0001 35, My truck

My truck didn't like the 726-03-01 and would not accept those values from the OCR trucks.

Here is what it did take;
726-03-01 0101 0000 33

So far no DTC's...

Keep trying, we are all waiting anxiously....

Has anyone found a way in Forescan to adjust the fuel mileage correction factors? Mine is slightly optimistic and I would like to adjust it.