ECU module programming guide using FDRS

[Bob_Mac]

So what’s the current thinking? Is it a problem specific to the Nano or is FDRS having difficulty digesting the J2534 protocol? Put a different way, has anyone used a J2534 device that didn’t trigger the corruption problem? I know @iceman77 plans to test the Mongoose but I don’t think he’s done it yet.

I'm still in the mindset that it's FDRS and how it's handling the J2534 protocol and not specific to the Nano but all J2534 devices. I just spoke with a friend who's a Master Ford Tech and he believes it may be speed related and how fast/slow the data is sent. Lastly, FORScan see the modules fine when using the Nano...

Sponsored

 

[tonesto7]

I'm still in the mindset that it's FDRS and how it's handling the J2534 protocol and not specific to the Nano but all J2534 devices. I just spoke with a friend who's a Master Ford Tech and he believes it may be speed-related and how fast/slow the data is sent. Lastly, FORScan sees the modules fine when using the Nano...

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.
My data is back to looking good again. My truck must have sent in the latest data.

 

[JEB]

@Bob_Mac and @tonesto7 — you seem to be saying two different things. Is it the speed of the J2534 devices generally or is it the speed of the Nano in particular? It sounds to me like the problem is still the Nano if @tonesto7 ’s UCDS device isn’t corrupting data.

 

[Bob_Mac]

@Bob_Mac and @tonesto7 — you seem to be saying two different things. Is it the speed of the J2534 devices generally or is it the speed of the Nano in particular? It sounds to me like the problem is still the Nano if @tonesto7 ’s UCDS device isn’t corrupting data.

Not 100% sure at this point but, the Nano works fine with FORScan so I'm still thinking it's FDRS. Still investigating...

 

[Bob_Mac]

@Bob_Mac and @tonesto7 — you seem to be saying two different things. Is it the speed of the J2534 devices generally or is it the speed of the Nano in particular? It sounds to me like the problem is still the Nano if @tonesto7 ’s UCDS device isn’t corrupting data.

He is still getting corruption but not on the level the Nano has...

 

[JEB]

Not 100% sure at this point but, the Nano works fine with FORScan so I'm still thinking it's FDRS. Still investigating...

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.

 

[Bob_Mac]

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.

You're now thinking what I I'm thinking! I just messaged @tonesto7 to see what his port settings are and to do some more testing with changes that may help things out... You're not adding to complexity

 

[Snakebitten]

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.

 

[Bob_Mac]

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.

Interesting, can you Message me the exact process so I can test and update the doc?

Edit: Don't you mean the BCM (BodyCM)?

 

[nicholsbradley]

Question can I pre download all the updates I need without installing after each one? Reason asking internet super slow we’re I live , but have faster at my job.

 

[antho]

I posted a few days ago wondering this. I have issues with CAN FD and the VXnano.

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.

 

[Bob_Mac]

Question can I pre download all the updates I need without installing after each one? Reason asking internet super slow we’re I live , but have faster at my job.

You should be able to but not tested. Files will be used only when you click on Run

 

[Bob_Mac]

I posted a few days ago wondering this. I have issues with CAN FD and the VXnano.

Wondering? Speed issue?

 

[antho]

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.


BEGIN ~~ ReadPartNumDIDsProcess
BEGIN ~~ PingModule
BEGIN ~~ BargraphDisplayV2
Comms ok with module
STMin is NOT overriden, current value = 65535
This VCI does not support CAN FD
END ~~ PingModule
BEGIN ~~ ReadPartNumDids
F188 (HEX) = 4D4C33542D3134483032312D45414A000000000000000000
F188 (ASCII) = ML3T-14H021-EAJ
9140 (HEX) = 5A5535542D3134483339342D58585830303030300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

 

[JScaro]

Well making headway now. Got some updates done but of course can't get rid of the GSM update and the APIM won't kick start from USB.
Now I need to work on my TRM DTC. My truck didn't come with the controller but I added it and had Ford program it - well thought they did. It has a DTC and I'm attaching some screen shots. I have the PDF with the steps to program it through FDRS but that didn't take care of the DTC.
Any Advice on which ones to proceed with?