2017 F-250 SD PS Can't write...

Car configuration discussions and experience sharing
Post Reply
pkarhoff
Posts: 5
Joined: Wed Jun 21, 2017 8:39 pm
Vehicle: F250 6.7L HO Diesel 2024 Tremor Platinum

2017 F-250 SD PS Can't write...

Post by pkarhoff »

Greetings all. I tried to write 720-07-02 to E in order to enable DPF% to screen. Unfortunately I got, "Service procedure has been interrupted" when writing. I tried a couple of different options in different modules all with the same results. I have the extended license and use the OBDLink MX Bluetooth. I tried a friend's USB wired OBD interface, also with the same results. I have the latest version of Forscan installed on an Alienware 13 R3 running Windows 10 Pro (1703). Anyone have any ideas on what I may be doing wrong? Thanks for the help.

Respectfully,
Phillip
Last edited by pkarhoff on Sun Jun 25, 2017 6:11 pm, edited 1 time in total.
pkarhoff
Posts: 5
Joined: Wed Jun 21, 2017 8:39 pm
Vehicle: F250 6.7L HO Diesel 2024 Tremor Platinum

Re: 2017 F-250 SD PS Can't write...

Post by pkarhoff »

A quick update for some 2017 SD owners... I can write to every other module I've tried. However, I cannot write any option in the IPC As Built nor the IPC regular. I am not sure if Ford updated the code on my pickup the last time I had it in for service so I cannot verify if this is what is causing the "interrupted" error in IPC As Built. Others have been able to write IPC, specifically for the DPF% so I suspect it was something related to newer code on my pickup.

Regards,
Phillip

2017 F-250 Lariat FX4 6.7PS
MFG Date 10/16
domesticdiesel
Posts: 1
Joined: Tue Jun 27, 2017 3:21 am
Vehicle: 2017 Ford F250 6.7 diesel

Re: 2017 F-250 SD PS Can't write...

Post by domesticdiesel »

I am having the same problem. I am going to try and force the as built data with the Ford IDS scan tool.
John
pkarhoff
Posts: 5
Joined: Wed Jun 21, 2017 8:39 pm
Vehicle: F250 6.7L HO Diesel 2024 Tremor Platinum

Re: 2017 F-250 SD PS Can't write...

Post by pkarhoff »

I confirmed this with the FORScan folks that it is a known issue and should be fixed in the next update.

On another note, I have confirmed that if you edit anything under BdyCM as built it will disable the correct tracking with a KARR SWAT for some reason. The alarm still works but the position update will not auto-check-in and when a position request is submitted from the SWAT console on the Web it will give a last known location that is approximately 10 to 24 hours out of date.

I am looking to see what is happening exactly so I can try and fix. My first supposition is that the SWAT box uses the built in NAV/GPS from the pickup and then uses its own CDMA/LTE radio to transmit the location. When anything is modified to the BdyCM it changes how the pickup reports from its own GPS and the SWAT box doesn't understand. More to come...

Respectfully,
Phillip
Post Reply