My optomistic self would hope at some point Ford's OTA updates gets worked out or at least dealerships get enough experience that we won't have to keep doing to this. But in reality you are probably right that this will be a continuous thing, just gets expensive after a while for licenses.
I believe it is the CCM that is getting borked and although I'm not sure to label it confirmed, it is verified so far that all borked CCM modules were using the nano.
ipma can be updated with the nano. The issue is the modules on the network the ipma creates have trouble. Those modules are on an independent can network.. it seems any module updated on that network with the nano goes purple because it can’t seem to communicate reliably. The mongoose does
I know it was mentioned somewhere , but I dropped the adapter baud rate to 9600 and had pretty good luck so far. Nothing purple and wth is borked? ?
It's a less caustic term for you know what.
There is definitely the possibility that a future Nano firmware/driver update will fix it. An update to FDRS or modules could potentially fix it as well. Updates could also break it completely.
You can also use it with Forscan, so it's a good diagnostic tool to have available even if you aren't using it for module updates or replacements.
Sub expired, can you look at my history? Or tell me what version is the latest. Was a couple weeks ago. But I recall something.It's a less caustic term for you know what.
So are you saying with the lowered baud rate that you successfully updated the CCM with the nano?
I too have had great luck with the nano until that pesky CCM update failed
Was when I lowered it.
The CCM update wasn't available before last Friday, I don't think.
So my VXDiag Nano is already set at 9600 baud and my CCM "borked". Did you change the baud rate in Windows device manager? (Not fdrs) Or was there another location?
