Search results

Well I know what I'm doing tonight.

Update. At this point I should have started my own thread on this :crackup: After a few key cycles I got a service engine light. I had errands to run and the wife was giving me the impatient look so I just flashed it back to factory tune file and cleared the codes. I may experiment a bit later...

I was able to update the PCM today. I loaded the High Output version of the 6.7 Powerstroke file via ForScan. So that answers the question on "can it be done". It started fine and there were no DTC's. I ran some rather unscientific testing as that's all I had time for this morning. I have a...

Not yet. I updated a couple of other modules today and downloaded the latest HO PCM file. I may give it a try this weekend. I'll be sure to follow up with the results. I will likely log the boost, fuel pressure, etc before and after to see if it appears to have had any effect.

I’ve successfully updated my 24 F350 multiple times with the Mongoose and FDRS. Works great. My next adventure is going to be attempting to load the High Output strategy file on my Standard Output diesel via ForScan unless someone can tell me why it won’t work.

I was able to PMI the failed interface with the Mongoose. Amazon for the win on the overnight delivery. Ok ... Ok ... I'm now a believer in the cult of the Mongoose. :crackup:

Got it. The trash can wasn't there until I checked a box. Thanks!!

How do you do that?

Ok So it sounds as though if you have a version that works for you, there's no requirement to be on the latest version? The reason I ask is that last time I ran updates, stuff worked pretty flawlessly. This time, darn near everything that required the interface to update versus USB failed...

Do you guys always update to the latest version of FDRS before running updates? I think I was running 41.5.2 and just upgraded to 43.6.5 but I saw complaints about the new version. Any feedback?

I just called the renewal hotline listed on the Helm website. Interestingly I just launched TorGuard which allows me to appear to be anywhere I want glabally via chosen server. I picked Dallas and now I no longer get the error. It could be my local firewall or possibly something else in the path...

I’m in the US and I also have the same issue. I just called them and made the purchase over the phone. I wish I knew the root cause.

Sorry if this has been asked and answered before but do the FDRS updates and OTA follow the same release cycle ... meaning if my truck doesn't show any OTA updates, will FDRS make a difference? I'm debating on getting another FDRS subscription since there's an APIM update (1286) I've seen...

Well I don't work for Ford so at least my opinion is speculation, but I don't think Ford is looking to cut out dealers in favor of owners. I think it's quite the opposite and they simply tolerate the tech savvy owners who decide to fix stuff themselves. Ford is mandated by law to open up access...

Also bear in mind, Ford doesn't really intend for owners to update their vehicles every time there's a new patch released. FDRS wasn't designed to be used by owners, but rather dealers and independent service shops with tools, training and support by Ford.

There are dozens of modules/computers in these vehicles that need updates periodically (Engine, transmission, Sync, HVAC, ABS, telematics, etc). Some of them support USB and others the traditional cable method. I'm not sure of the exact logic Ford uses but it could be based upon both size of the...

Thanks @JEB for actually answering the question. It's a NASTF username and password with VSP access level.

So ... it's a password or username and password prompt? You're not really answering my question.

I'm asking because FDRS has password protected functions for BCM on some vehicles. It's a known password which is why I'm asking what sort of prompt it is.

For those being presented with a login for the BCM, what kind of prompt is it? Password only or Username and Password? Any screenshots?