Can't write any changes, pretty sure I'm doing everything right

[Will2]

Latest version of Forscan (2.3.62)
Tried 3 different adapters (OBDLink EX, vLinker FS, cheap ELM327 generic)
All Windows drivers/settings good
All FORscan settings good (license installed, adapter settings checked, etc.)

I just can't successfully write changes. Attempted BCM 726-57-01 (cigarette plug timeout) and BCM 726-15-01/02 (tire circumference).

It'll even show "100%" on the bottom progress bar, the car restarts on its own, but the log will show "Service procedure has been interrupted" and no changes save.

Base Ecoboost, manufactured ~June 2024. Maybe something changed in manufacturing? Newest Forscan not compatible? I have FordPass connected features enabled, not sure if that would hamper things.

Sponsored

 

[smurfslayer]

did you save the logs like FORSCAN tells you? The logs can sometimes reveal something (plain text) and there’s an accompanying binary.

Were you able to make changes before?
Are you able to update other modules ? With .62, you should be clear to update IPC, try enabling continuous gear display, it’s quick, easy and simple to understand.

Any DTC’s showing?

 

[Will2]

did you save the logs like FORSCAN tells you? The logs can sometimes reveal something (plain text) and there’s an accompanying binary.

Were you able to make changes before?
Are you able to update other modules ? With .62, you should be clear to update IPC, try enabling continuous gear display, it’s quick, easy and simple to understand.

Any DTC’s showing?

Didn't save logs but I'll go try that. On the cheapest generic ELM327 adapter the progress bar would only get to 79% and it did give some more text after the "procedure interrupted". On the vLinker and OBDLink (the 2 officially recommended by Forscan) there was not additional text.

No DTCs and no error messages.

 

[JAM486HP]

Following...
I'm having the same issue when trying to do a "PCM Reset All Adaptations"

 

[smurfslayer]

man that sounds a lot like the issue I had updating the IPC with v ... .61 LMS if I can dig up the logs on mine.

 

[smurfslayer]

Your logs should be saved to \This PC\AppData\Roaming\FORScan\log

left column is the date, next one is the time then an identifier column followed by the log entry.

I was getting a bunch of STN Adapter profiling: nn ms followed by Disconnected from ELM.
See if you can get that log snippet and see what it tells us. Also, try updating IPC.

 

[Will2]

Got another vLinker and tried again. Same thing. Logs don't give any more info. No other errors of any sort. Totally stock car.

I could paste the whole log, but most of it is useless, just "Read block #1... #2... No changes in block 1, skipped... No changes in block 2, skipped..." until:

(ERR) [13:07:47.882] Service procedure has been interrupted

There is no further text.

I tried both AS BUILT (raw hex code entry mode) and not AS BUILT (I think people call this "easy mode"). Same error on both.

I might try an older version of FORScan since most of the posts on this forum are from months ago from people presumably using older versions.

 

[smurfslayer]

Have you tried other modules besides BCM?

 

[bbarnett]

I have the same problem. I can write to several other modules without issue, but the bdycm won't write a single thing.

Can anyone else using forscan confirm an ability to write to the bodycm on the 2024?

I didn't even realise it at first, until I started to check after a write attempt and noticed no change.

 

[smurfslayer]

I don’t think anything I tried wrote to BCM. What are you trying to do?

 

[bbarnett]

The cool folks at forscan took my debug log, tweaked, and forscan now works to write to the bodycm!

Tested a trial build yesterday, wrote about 20 times when trying to get around something, worked great.

Apparently .64 will "be out soon", with those changes. Good times.

 

[smurfslayer]

The cool folks at forscan took my debug log, tweaked, and forscan now works to write to the bodycm!

Tested a trial build yesterday, wrote about 20 times when trying to get around something, worked great.

Apparently .64 will "be out soon", with those changes. Good times.

Next time I have an issue with it, I’m reaching out to you!
I didn’t even get a response

Great work

 

[sunnydhama]

The cool folks at forscan took my debug log, tweaked, and forscan now works to write to the bodycm!

Tested a trial build yesterday, wrote about 20 times when trying to get around something, worked great.

Apparently .64 will "be out soon", with those changes. Good times.

Will the new update work with older cars with BCM that is not updated, I got a job1 car (manufactured in 2023 late)

 

[Will2]

The cool folks at forscan took my debug log, tweaked, and forscan now works to write to the bodycm!

Tested a trial build yesterday, wrote about 20 times when trying to get around something, worked great.

Apparently .64 will "be out soon", with those changes. Good times.

Awesome news! Excited to try it out

 

[5.0ALM]

Apparently .64 will "be out soon", with those changes. Good times.

2.3.64 was released back on the 18th.

https://forscan.org/download.html

Sponsored