ECU module programming guide using FDRS

[Bob_Mac]

Too bad the VCM 3's are hard to find and cost a ton of money. It sounds like that might be the best option to see everything without issues if you can afford it.

I may just buy one... getting frustrated that FDRS states it supports the J2534 Pass-Through Protocol and we see something different.

Sponsored

 

[BlackSheep]

@Jesse-Infotainment ’s is rock-solid. But I think the cheapest I’ve seen is about $1500. If cloud corruptions are the only negatives to the J2534 devices, I’ll just have to live with it. I’m not sure there are any negatives other than potentially knocking out OTA updates.

And you can remind me I said that when something catastrophic happens.

I'm curious, what if any modules we can't see or update with VCX Nano, etc.

 

[iceman77]

@Jesse-Infotainment ’s is rock-solid. But I think the cheapest I’ve seen is about $1500. If cloud corruptions are the only negatives to the J2534 devices, I’ll just have to live with it. I’m not sure there are any negatives other than potentially knocking out OTA updates.

And you can remind me I said that when something catastrophic happens.

Yes, it sucks that J2534 pass-through interfaces corrupt AB data in cloud, but the work around is rather easy. Just don’t do network scan and let FDRS download cloud based vehicle info into the tool

 

[JEB]

Yes, it sucks that J2534 pass-through interfaces corrupt AB data in cloud, but the work around is rather easy. Just don’t do network scan and let FDRS download cloud based vehicle info into the tool

Unless your cloud AB data is already corrupted, which mine appears to be. Truck still hasn’t phoned in a correction and it’s been a week since I last did a network scan.

 

[Lodans]

Unless your cloud AB data is already corrupted, which mine appears to be. Truck still hasn’t phoned in a correction and it’s been a week since I last did a network scan.

Are we sure that it does upload the data to the cloud. It has been a month since I used FDRS and my data in the cloud is still corrupted.

 

[iceman77]

Are we sure that it does upload the data to the cloud. It has been a month since I used FDRS and my data in the cloud is still corrupted.

Yes I am sure! At least my old Job 1 truck did it. It took 2-3 days though.

 

[Thekameleon]

trying to do APIM update. OK I downloaded the files onto a USB that was exFat formatted. Have the ignition and engine on. safely removed USB stick. Then plugged it in USB in dash under heating cooling power control. Nothing happens though. I see it sees the USB on SYNC but not screen that says the system is updating. I have waited 30 minutes

 

[abd79]

Just wanted to chime in on the suspected corruption of Software P/N in FDRS. I can say without a doubt it is not adaptor related. I have tested this now 12 times in the following manner;

1. No adaptor connected to the computer
2. I Deleted the vehicle profile in FDRS and restarted FDRS
3. I Re-entered VIN number and downloaded vehicle information from Ford
4. Every time I do this the part number for the APIM changes, It is always one of the following for me;
- "ML3T-"
- "FFF1-14D358-FF"
- "MU5 T-14G676-EJ"

So I believe we are chasing ghosts here and the problem is actually either FDRS or on Fords Servers not the VX or other adaptors.

 

[Thekameleon]

Just wanted to chime in on the suspected corruption of Software P/N in FDRS. I can say without a doubt it is not adaptor related. I have tested this now 12 times in the following manner;

1. No adaptor connected to the computer
2. I Deleted the vehicle profile in FDRS and restarted FDRS
3. I Re-entered VIN number and downloaded vehicle information from Ford
4. Every time I do this the part number for the APIM changes, It is always one of the following for me;
- "ML3T-"
- "FFF1-14D358-FF"
- "MU5 T-14G676-EJ"

So I believe we are chasing ghosts here and the problem is actually either FDRS or on Fords Servers not the VX or other adaptors.

I ve seen the ML3T- and FFF1-14D358-FF myself

 

[JEB]

Just wanted to chime in on the suspected corruption of Software P/N in FDRS. I can say without a doubt it is not adaptor related. I have tested this now 12 times in the following manner;

1. No adaptor connected to the computer
2. I Deleted the vehicle profile in FDRS and restarted FDRS
3. I Re-entered VIN number and downloaded vehicle information from Ford
4. Every time I do this the part number for the APIM changes, It is always one of the following for me;
- "ML3T-"
- "FFF1-14D358-FF"
- "MU5 T-14G676-EJ"

So I believe we are chasing ghosts here and the problem is actually either FDRS or on Fords Servers not the VX or other adaptors.

The APIM is an anomaly. Ford acknowledged it was having problems with the APIM. There are deeper corruptions in other modules that affect data other than the software version you see on the FDRS summary screen. They aren’t ghosts.

 

[Darkjeep]

I learned that I can corrupt any and all data with the nano. I even broke my newest upgrade to hdradio. FML.

 

[JEB]

I learned that I can corrupt any and all data with the nano. I even broke my newest upgrade to hdradio. FML.

The difficulty is pinning down the actual problem. Ford is used to using older and different protocols with IDS. J2534 is relatively new for them. FDRS is supposed to be compatible with J2534 but there’s growing evidence that there’s still a problem. We’re trying to figure out if it’s the Nano specifically, Ford’s implementation of the J2534 protocol generally or a combination of the two. It’s probably more the latter but the Nano might be contributing to the problem.

 

[Darkjeep]

I did have more issues in forscan with nano than with super cheap off brand elm device. I might need someone to tell me how many modules I updated so I can apply older as built data. I only did a two day licence.

 

[abd79]

The APIM is an anomaly. Ford acknowledged it was having problems with the APIM. There are deeper corruptions in other modules that affect data other than the software version you see on the FDRS summary screen. They aren’t ghosts.

Not saying there couldn't be ghosts still but when I look at my as built data downloaded before I even tied the nano on to the truck the only things I'm seeing different for me is where the software update has changed a few bits in some block to support it or new functionality, new complete blocks available, changes I've made in ForScan and the anomaly with the part numbers and the odd space between characters. For the most part my AB data hasn't been changed and can't see any corruption from the 12+ updates I've done over the past 2 days. Maybe I've just been lucky and need to go knock on wood.

 

[JEB]

Not saying there couldn't be ghosts still but when I look at my as built data downloaded before I even tied the nano on to the truck the only things I'm seeing different for me is where the software update has changed a few bits in some block to support it or new functionality, new complete blocks available, changes I've made in ForScan and the anomaly with the part numbers and the odd space between characters. For the most part my AB data hasn't been changed and can't see any corruption from the 12+ updates I've done over the past 2 days. Maybe I've just been lucky and need to go knock on wood.

I’m not going to parse all of this, but you need to realize that something that might seem trivial like the “odd space between characters” might be enough to knock out the whole module if you ever needed to download the as-built data to reprogram your module. It might be enough to throw off the Ford updating systems and disqualify you for future OTAs. That’s the point. It’s a corruption, and even though it might not look like much to you we have no idea what it will do in practice.

Sponsored