EVmodeler
Well-Known Member
- First Name
- Doug
- Joined
- Oct 30, 2020
- Threads
- 10
- Messages
- 132
- Reaction score
- 291
- Location
- SW Virginia
- Vehicles
- Mach-E AWD ER IB Job 1
- Occupation
- Engr Prof emeritus
- Thread starter
- #1
I have a 2021 AWD ER premium Job 1.
I have 2 OBD2 Vgate adapters, one for Bluetooth LE, and an older one for WiFi.
My OBD2 adapters and apps used to work; I had not used them for a while, then they stopped connecting to ECU.
The adapters do connect to ELM327 either over BTLE or WiFi, but not ECU.
I have tried Car Scanner, Forscan viewer and other apps on my iPhone 15, IOS 17.5
I also tried my Foxwell hardwired OBD2 tool. Only 5 modules show up ($07E series), but I just used the generic OBD2 as I don't have the Ford specific firmware.
I had the 10k mi checkup (multi point inspection and rotate tires), HVBJB 23S56 recall, and state inspection done by my Ford dealer June 14.
For the HVBJB recall, it says "accessed diagnostic port, performed control module update, cleared DTCs, verified no codes returned".
The change in behaviour may have happened after the recall work or an OTA update - last update was 24-PU0301-BLM-PE June 1.
I tried disconnecting the 12V battery ground for over 10 min, but no change.
I can dm my VIN, if that helps.
@Mach-Lee @Mike G @rugedraw any ideas? Thanks for your help.
I have 2 OBD2 Vgate adapters, one for Bluetooth LE, and an older one for WiFi.
My OBD2 adapters and apps used to work; I had not used them for a while, then they stopped connecting to ECU.
The adapters do connect to ELM327 either over BTLE or WiFi, but not ECU.
I have tried Car Scanner, Forscan viewer and other apps on my iPhone 15, IOS 17.5
I also tried my Foxwell hardwired OBD2 tool. Only 5 modules show up ($07E series), but I just used the generic OBD2 as I don't have the Ford specific firmware.
I had the 10k mi checkup (multi point inspection and rotate tires), HVBJB 23S56 recall, and state inspection done by my Ford dealer June 14.
For the HVBJB recall, it says "accessed diagnostic port, performed control module update, cleared DTCs, verified no codes returned".
The change in behaviour may have happened after the recall work or an OTA update - last update was 24-PU0301-BLM-PE June 1.
I tried disconnecting the 12V battery ground for over 10 min, but no change.
I can dm my VIN, if that helps.
@Mach-Lee @Mike G @rugedraw any ideas? Thanks for your help.
Sponsored