Search results

Does the device show connected (Connected to Device) in FDRS on the bottom right corner?

I'm still making updates to the doc. I though it was apparent but, I'll add more to it if it helps.

Connect to the positive battery terminal first then the ground post last.

Is that directed to me?

Next step towards or needed for BC?

I'm assuming yes but, I did the cloud regardless at the start and then I did the scan...

No issues connecting, sorry.

Update: I neglected to add I did do a Network Scan after the comparisons and everything was still good! Ok everyone, my theory about the corruption issue being FDRS or Ford appears to be correct and not the J2534 adapters. I copied the JSON file which showed errors from the other day when...

No issue here...

Ditto!

First I'm hearing of this... I think you're the first to post about the email.

So you didn't get prompted to return the USB back to the computer which is the same as my experience. I'll add that to the doc that "It may" prompt you to add the stick back into the computer...

I'm thinking it may be related to my theory above, after the Restart this is where the CANBUS picks up the data that was stored in the truck from the USB and the USB data is used for comparison against the Software P/N, Strategy, etc. and what's in the module once the update is complete.

I agree and I never put the USB back into the computer. FDRS reads the module info directly from the truck when you acknowledge the "Did the update install successfully" and didn't prompt for inserting back into the computer.

Agreed

Another thing and I'm hoping @iceman77 chimes in. I don't believe the door opening and door closing applies any longer, this was part of an earlier TSB procedure and I never followed that and all my updates completed. I say it due to FDRS telling you to leave the stick in and that "You can drive...

I'm in the process of doing that and making other changes. I'll be using dates as the version control. iceman77 did update the first post with the link I provided you, last version took a crap for whatever reason.

My theory is this, the update is complete when it hits 100% but, I think that when you restart that's when the update is applied and then the CANBUS takes over hence the lengthy time it takes to complete. @iceman77 thoughts?

Nice...

And there you have it, thx @iceman77 ! Putting that in the doc!