Search results

I'd be interested in doing the same. I'm sure he'll chime in when he gets a chance.

I think that may be hard coded into the APIM and/or IPMA and cannot be changed with FORScan. I can't say that with 100% certainty. Maybe @Livnitup would know?

You can also email FORScan support to make sure your VIN is in their database.

What codes is the truck reporting?

Yes, we'd be able to tell if it was done with PTS/FDRS. if they did the CSP you mentioned, you don't need to wait for the OTA. You can enable BC 1.4 yourself with FORScan.

He did that too. Still got suspended.

They would catch that almost instantly, imo. Once you start transferring an FDRS license from one computer to another and it connects to the mothership with different IP address, it's over. I agree that license sales are the only thing that makes sense here. However, in the case of what...

People in other countries where Ford is not supported use FDRS by going through a VPN to trick FDRS into thinking they are in the US. This works for x amount of time before their account gets suspended. So they have some measures in place to detect this. It is also easy enough to code FDRS...

Guess we'll have to lean on PTS until they f*ck that up, too. On a lighter note: It's about damn time.

Kind of. Once the OTA trigger is created on the server, you only have 7 days to start the vehicle so it pings the server back and accept the OTA. Once that happens, you then have 14 or 30 days for the OTA to install. 14 days if the OTA does not require the vehicle to be inhibited and 30 days if...

I would find a way to compress an audio clip from Ludacris' "move b*tch..... get out the way" song, but I'm a little ratchet, so don't mind me. ?

This goes beyond my scope of knowledge, but I think this may work. Worse case scenario, you'll lose the ability to update the PACM via OTA or FDRS, but imo, who cares? It's the PACM. If there is no kind of encryption on the audio file and you can modify it and reflash it on the bench, then...

To fix cameras at speed, make this change: IPMA 706-02-02 xxxF xxxx xx-- To trigger the front camera coming on with the proximity sensors, I don't remember where to go to make that change. I know there is a setting in FORScan for it and it is in the IPMA, but I don't remember where. Maybe...

No, not that I know of.

Gladly, but please remove your VIN from your request. Modules with pending updates are below. Your truck is on the latest Sync software and the ADAS modules are also on the latest version. In terms of the more important modules, you are up to date.

A PMI won't do anything. All you can do is deal with the annoyance.

I wish I would have seen you post before you had the truck towed to them, but it is what it is now.

Good catch.....I didn't notice that. Not sure what the 49 failure means, but in the case of the ABS code you have, 04 cites "system internal failure" when I highlight it. What is strange is the TSB cites code U3000 49 in the IPMA; not in the ABS. However, this is the TSB that it takes me to when...

The country code issues is a known issue and Ford created a specific ota to fix it. Not sure how it happened, but OTA history shows many failed update attempts because the truck never pinged back the server to accept it. The ota to fix the country code failed due with a direct hash configuration...

The truck is reporting the following code: The TSB referenced by the code is attached. It could be due to a loose camera connection between the IPMA and the camera itself. In terms of the connectivity issue, I think I found the problem. Assuming you are in the US, the country code in your...