Lightning Software Updates using FDRS

[mr.Magoo]

What I don't understand is: Wtf do they care?

Selling Licenses ?
I mean, technically we could create a forum account and do a group buy and then we all share the same login.

So this might be their way of keeping tabs on how/where the software is used.

Sponsored

 

[rugedraw]

Selling Licenses ?
I mean, technically we could create a forum account and do a group buy and then we all share the same login.

So this might be their way of keeping tabs on how/where the software is used.

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 happened (is happening) to Mike, they specifically said their problem was with VINs from outside markets being run through his FDRS account. Not to mention, FDRS users ask to see what pending updates they may have so they can buy a license to do them.

It would be much easier for Mike, myself and anyone else who does this if customers can call the Ford 800 number and ask them to check what pending updates are there from them. The OTA customer service reps have PTS access, so they can easily provide this info to owners.

Whatever......I digress. Worry about the things you can control.

 

[RyZac]

Does FDRS tell if the 24B56 parking sensors update was performed? I sent my truck to the dealer last Fall for this. They had the truck from Friday-Monday. When the tech could not get it completed overnight after charging they needed to keep it until Monday. When I was called to say all done Mondayafternoon, the paperwork just says " recall incomplete and sent back to shop".

just got the window OTA and patiently waiting for BC 1.4

 

[Maineiac12]

I thought I should let folks know that two days ago my Ford account that I use to login to FDRS was suspended.

Today I got an explanation of why:

"Running VINS outside of your country will cause your account to be suspended. Going forward, you should not do this. We have re-enabled your account with a password reset. If we see the same activity, it will be suspended again."

So I'm still okay with doing VIN lookups, but I must now restrict myself to only looking up VINs that are US based. So if you're based in Canada I'd ask that you find somebody there who can provide that ability going forward.

This is the second time my account has been suspended...but it's the first time I was provided an explanation as to why (the first time it was my Ford owner/Fordpass account that I was using with FDRS as well, and it just got turned back on after a week). So I set up a separate account to use with FDRS...and this time I got an explanation and a warning.

Just so you know....

So you got suspended for using your FordPass login in FDRS? That’s what I’ve been doing. Should I create a separate account to be safe?

 

[mr.Magoo]

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.

Well, if people are getting creative with VPNs to circumvent country restrictions Ford might just have implemented a check on vehicle location, but that seems like a lot of work and wouldn't necessarily work when people switch off location sharing. Guess we'll have to wait and see.

Oh, and just incase someone misinterprets my previous statement about a group buy, I'm not suggesting we, or anyone, should in any way shape or firm do it.

 

[rugedraw]

So you got suspended for using your FordPass login in FDRS? That’s what I’ve been doing. Should I create a separate account to be safe?

He did that too. Still got suspended.

 

[PJnc284]

If Ford would do their job and wasn't slow as molasses with updates, the average person wouldn't even need fdrs or pts. They should be happy though that people are willing to check or update on their own so the dealers aren't hammered by people calling them.

 

[rugedraw]

Does FDRS tell if the 24B56 parking sensors update was performed? I sent my truck to the dealer last Fall for this. They had the truck from Friday-Monday. When the tech could not get it completed overnight after charging they needed to keep it until Monday. When I was called to say all done Mondayafternoon, the paperwork just says " recall incomplete and sent back to shop".

just got the window OTA and patiently waiting for BC 1.4

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.

 

[chl]

I got a window bounce update the other night - my pet peeve about OTA updates - they seem to cause a skipping of the next scheduled charge.


1) after getting the notice an update was available, I parked my truck, plugged it into the FCSP, and then scheduled the update to install immediately - it said it would take 40 minutes and it was around 10pm - it gave me a 2 minutes countdown and then started updating after I turned off the truck;
2) I wanted to charge my truck that night beginning at 1 am well after the update so I thought there would be no conflict - 1am is the preferred time I have set in the truck menu previously when the cost is lower, alas...
3) the next morning I discovered the truck had not charged overnight.

I do not understand why an update that occurs 2-1/2 hours BEFORE the scheduled charge start has to FTU...

Guess I have to babysit the charging to be sure it starts as scheduled...

 

[sstevetx]

Picked up a 2 day license and got most of my updates caught up. Had a PCM, ABS, PSCM, SOBDMC, RFA, ACM, TRM, BECM, GFM2, SOBDM, SOBDMB, DDM and PDM available. I was able to run all of them successfully except the RFA which errored out (below). Has anyone seen this error before and/or knows how to get around it?

I did do the rotary shift mod, but I don't think that would be related to this. I did try to do a PMI on the GSM to see if it would work on the rotary shifter, but it errored out with "invalid hardware". I tried stating I didn't have the original module and then again stating I did. I was able to do a VIN Write successfully.

EDIT: Temporarily put the original shifter back in and it made no difference. Tried a PMI on the RFA as well. I'll next try a PMI on the ACM like rugedraw suggested below.

RFA error while doing update:

RFA error in vehicle history:

 

[rugedraw]

Picked up a 2 day license and got most of my updates caught up. Had a PCM, ABS, PSCM, SOBDMC, RFA, ACM, TRM, BECM, GFM2, SOBDM, SOBDMB, DDM and PDM available. I was able to run all of them successfully except the RFA which errored out (below). Has anyone seen this error before and/or knows how to get around it?

I did do the rotary shift mod, but I don't think that would be related to this. I did try to do a PMI on the GSM to see if it would work on the rotary shifter, but it errored out with "invalid hardware". I tried stating I didn't have the original module and then again stating I did. I was able to do a VIN Write successfully.

RFA error while doing update:

RFA error in vehicle history:

Strange. I looked through 419-01C in the workshop manual and I don't see anything there that helps. Your truck is not reporting any codes for that; only a U1A00 on the APIM. Try doing a PMI on the ACM (select no when FDRS asks if it is the original module) to see if that APIM code clears.

As far as the RFA, try turning off the truck and let it sit for a half hour. Reboot the laptop and try to update the RFA again.

 

[sstevetx]

Strange. I looked through 419-01C in the workshop manual and I don't see anything there that helps. Your truck is not reporting any codes for that; only a U1A00 on the APIM. Try doing a PMI on the ACM (select no when FDRS asks if it is the original module) to see if that APIM code clears.

As far as the RFA, try turning off the truck and let it sit for a half hour. Reboot the laptop and try to update the RFA again.

@rugedraw , I appreciate the suggestion. I did the PMI on the ACM successfully. As for the RFA, I disconnected the battery for 10 minutes and then tried again with the same error. I tried a PMI and it failed as well as reading the configuration option. I tried RFM initialization too which mentions BCM and RFA, but it failed to get a security key. Do you think the RFA update failure could be an access issue related to my independent operator login? I know they locked down BCM updates to dealers last year.

I also gave Forscan a shot and rebooted the RFA. I then downloaded the RFA factory configuration defaults and tried to do a force write, but it said the process was interrupted.

Everything seems to work ok as far as I can tell, so I may just leave this as a future problem.

 

[rugedraw]

@rugedraw , I appreciate the suggestion. I did the PMI on the ACM successfully. As for the RFA, I disconnected the battery for 10 minutes and then tried again with the same error. I tried a PMI and it failed as well as reading the configuration option. I tried RFM initialization too which mentions BCM and RFA, but it failed to get a security key. Do you think the RFA update failure could be an access issue related to my independent operator login? I know they locked down BCM updates to dealers last year.

I also gave Forscan a shot and rebooted the RFA. I then downloaded the RFA factory configuration defaults and tried to do a force write, but it said the process was interrupted.

Everything seems to work ok as far as I can tell, so I may just leave this as a future problem.

I don't think so. I have seen people here and on the Mach E forum have issues trying to update the RFA. I am not sure of the workaround, tbh, but I don't think the login type is the issue.

Did the PMI on the ACM clear the APIM code?

 

[sstevetx]

I don't think so. I have seen people here and on the Mach E forum have issues trying to update the RFA. I am not sure of the workaround, tbh, but I don't think the login type is the issue.

Did the PMI on the ACM clear the APIM code?

I didn't check afterwards and when I tried the RFA later it caused a ton of APIM errors. I ended up doing a clear all DTC and then nothing showed up in the errors after power cycling and checking again.

 

[chl]

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 into raising a red flag on their side if a VIN from another country is ran through FDRS using a US based account. Or, as @B177y mentioned, an above-average amount of VINs are ran through a single FDRS account.

What I don't understand is: Wtf do they care? They can see everything that is done. FDRS records every single key-stroke. The truth is, we can't use FDRS for anything that would constitute a nefarious activity or to experiment with software on our vehicles. That's what FORScan is for, which IMO, is infinitely superior to FDRS in function. FDRS is easy in the sense that it does everything for you, but let's be honest: It is slow, unstable and very demanding of a computer's resources.

It's about copyright and perhaps patent laws which are territorial.
So for example, software, movies, whatever, may be licensed and protected from copying in the US but not in other countries.

The intellectual property owner has a duty to protect their right or they could lose them. And publicly traded companies have a fiduciary duty to their shareholders to do the same.

Sponsored