ECU module programming guide using FDRS

[JEB]

Jesse uses VCM3 device and this device is not J2534 pass-through device. It uses J1708 and J1939 protocols instead

RIght. I remember now. The point I was making to Bob_Mac was that because not all programmers are creating corruptions, it remains unclear whether it is an FDRS problem, generally, a problem with the the use of J2534 with FDRS, or the use of the Nano in particular. Since the VCM3 seems to work without issue, it isn’t FDRS, generally. And your testing of the Mongoose should further narrow it down to either J2534 or the Nano.

Sponsored

 

[tonesto7]

Also, I would wonder how is your UCDS adapter recognized by FDRS. Is it indeed J2534 pass-through device, or perhaps this device supports other protocols (such as J1708 and J1939 as VCM3) ?

it shows up as a J2534. "UCDS-J2534"

 

[JEB]

it shows up as a J2534. "UCDS-J2534"

It was late when I thought I read this, but didn’t you say that you were seeing corruptions with the UCDS? If that’s so, that seems to add credence to the theory that using J2534 with FDRS is the problem right now. It’s not a Nano-specific bug.

 

[iceman77]

It was late when I thought I read this, but didn’t you say that you were seeing corruptions with the UCDS? If that’s so, that seems to add credence to the theory that using J2534 with FDRS is the problem right now. It’s not a Nano-specific bug.

His AB data looks solid, either though I recall his APIM reporting values such as FFF1-14F180-FE and I see this in his current AB as well. Not sure if this is part of J2545 NetworkScan corruption or something else

 

[JEB]

His AB data looks solid, either though I recall his APIM reporting values such as FFF1-14F180-FE and I see this in his current AB as well. Not sure if this is part of J2545 NetworkScan corruption or something else

I’ll be glad when you’ve had a chance to test the Mongoose.

There is definitely something odd happening with the APIM. I have logged into FDRS a couple of times today—cloud only, no network scan. Sometimes the software version is populated immediately after the vehicle ID, sometimes it isn’t. As I mentioned above, the FDRS team has said that it is aware of issues with vehicle ID in Sync 4-equipped vehicles and are working on it.

 

[antho]

This isnt actually effecting the modules but just the data sent back to ford from FDRS? Once the modules report their data ota that will fix the issue we are seeing in Fords reported data?

 

[Bob_Mac]

I’ll be glad when you’ve had a chance to test the Mongoose.

There is definitely something odd happening with the APIM. I have logged into FDRS a couple of times today—cloud only, no network scan. Sometimes the software version is populated immediately after the vehicle ID, sometimes it isn’t. As I mentioned above, the FDRS team has said that it is aware of issues with vehicle ID in Sync 4-equipped vehicles and are working on it.

Hence why I'm sticking to an FDRS issue but, time will tell. I just checked again (cloud only) and the APIM & TCU both show issues.

 

[Bob_Mac]

This isnt actually effecting the modules but just the data sent back to ford from FDRS? Once the modules report their data ota that will fix the issue we are seeing in Fords reported data?

I don't think it's affecting the modules but, the AsBuilt shows the same issues and would probably prevent any OTA's being pushed to us due to the corruption.

 

[antho]

I don't think it's affecting the modules but, the AsBuilt shows the same issues and would probably prevent any OTA's being pushed to us due to the corruption.

Thats what i was thinking. If Ford doesnt see the proper module info, It probably wont sent out an update for it.

 

[Bob_Mac]

Off Topic: Question for everyone, does anyone know what the 'ACM - Sound System Upgrade' does in the Programmable Features tab?

 

[JEB]

Thats what i was thinking. If Ford doesnt see the proper module info, It probably wont sent out an update for it.

That was something I was thinking about as well. Has anyone who performed a manual module update gotten an OTA (any OTA) after the update? I haven’t and I know 2.4.1 came out well after my first tour through FDRS in January.

 

[antho]

Off Topic: Question for everyone, does anyone know what the 'ACM - Sound System Upgrade' does in the Programmable Features tab?

@Bob_Mac Its for the Kicker Upgrade.

 

[speedracercjr]

I don't think it's affecting the modules but, the AsBuilt shows the same issues and would probably prevent any OTA's being pushed to us due to the corruption.

Don't suppose this corruption would also be causing the restart loop with a USB drive by chance?

 

[Jesse-Infotainment]

Amazing how far everyone has come.

 

[JEB]

This isnt actually effecting the modules but just the data sent back to ford from FDRS? Once the modules report their data ota that will fix the issue we are seeing in Fords reported data?

@iceman77 gave a good explanation of what is going on at Post 300. Reading it again did quite a bit to calm my nerves.

Sponsored