I agree. I think it's more related to the speed of the VCX Nano. My UCDS adapter hasn't had the corruption others have. I only have the ML3T- the part number in the Sync Module.
Not to add unnecessary complexity, but are we potentially talking about two different speeds? The Nano might be perfectly fine for FDRS and FORscan from a read/write perspective. And that appears to be the case. But the corruption seems to be occurring not at this stage but at the stage where data is transmitted back to the Ford servers and stored in the “as-built” database. If the Nano device communicates with the server at a speed/baud rate that the FDRS server doesn’t like, it strikes me that it could work fine locally for programming but still be a problem at the post-programming part of the procedure where data is sent back. Just a thought.
Interesting, can you Message me the exact process so I can test and update the doc?I spent some time on this frigid day (45 is cold in the tropics) in the cab applying the IPC update I saw browsing yesterday. Maybe I wasn't paying attention to all the previous posts regarding, but it used a different routine than any that I had remembered from my previous FDRS sessions.
Similar to APIM and TCU, FDRS requested a USB stick and it downloaded the file(s) and loaded wrote them to the stick. It then requested Engine ON and displayed the ever familiar set of instructions to insert USB and blah blah blah. Exactly the same instructions as the previous updates.
I inserted the stick, Sync screen acknowledged the stick, indexed it, then stated updating in progress. THIS time I knew to touch the screen and enjoy the progress bar. (Thanks again!)
It finished the copying and then nothing. More than double the estimated 12 minutes and still nothing. Being less intimidated than I used to be, I shut down and restarted the truck. Nothing except the indexing.
Then I did what I had not ever done before..... I lied to FDRS and clicked YES to the success question. FDRS then established communicates with the truck and started showing the progressive steps of writing the update to the module! I don't think I remember an update that the USB portion was JUST for loading the updates to onboard storage and then FDRS applying the update. Also note THAT is NOT reflected in the FDRS screen instructions or the Sync screen prompts!
After the success without waiting forever for what FDRS implied, I then applied a new GWM update that I wasn't expecting. It went smoothly and I got instant kickoff and no restart loop. My truck is starting to act like it isn't haunted anymore.
I do now have a DTC in my IPC that has something to do with losing communication with the BMC. Clearing and testing isn't fixing it, but the IPC test is like watching a Fireworks show.
You should be able to but not tested. Files will be used only when you click on Run
Wondering? Speed issue?
Yeah. If i use the VXnano in forscan it wont see the SODCMC or SODCMD module. I also found issues in my FDRS datalog which is releated to my HEX data being all jacked up in FDRS.
