Search results

Hi, Some on this forum have issues where BodyCM 726-97-** values do not exist in Forscan, even with the latest BCM update. These values are required to enable WAL(walk away locks). Trying to debug, so one thought is; is it due to convertibles? So would anyone with a convertible be able to...

* removed emergency-brake nag * got rid of seat belt chimes, displays, nagging * got rid of door open chime, start car chime, startup chime, and other senseless sounds * forced warning/notice alert sounds to come through 'instrument cluster' instead of sound system (much quieter, less...

Fair enough, well at least I know it's not a country/build thing. Thanks

Roket, you once said that you can turn off AEB/emerg braking in your console, go away, come back a day later, and it still stays off. It doesn't for me. It auto-reengages. I've seen others report this. I wonder -- is this country specific, or is it bcm1/2 specific? Can you confirm... that...

I did not see that yesterday AM, and it was -15C. I've had lots of below 4C, and did not see it as well. Although, come to think of it, most cars I've had don't warn BELOW a certain temp. Like if it's -15C, there's not much of a need for a warning.

Hmm. I may after the holidays, don't want to risk something untoward happening. Seems weird to have such a late car not updated, and further, the dealer not updating prior to sell. But I'm sure it could happen.

2024. Window sticker says 09 09 24, and my dealer took delivery first days of October. It's gotta be one of the last builds for 24?

Roket, I can't imagine I have job1 code.. that would be highly bizarre for a car completed in late September. I wonder if I have a weird job3.

NOTE: I recalled I have my ford asbuild data, which I downloaded just in case. Just to be sure it wasn't forscan I checked. My car ends at 726-96-01, then jumps to 727-01-01.

Ok, good to know, thanks. Roket, can you confirm that your forscan goes to 97?! This is highly bizarre.

Very strange. Many cannot at all write to the BCM with forscan, version .63. I cannot imagine my car, which was completed in late September, would have 'job 1' BCM or what not. Well thanks, but hopefully someone else can check in to 100% verify that their bdycm ends at 96 or not in forscan...

Huh. Did you use a mongoose?? Because forscan (for me, and most others I've seen) cannot even write to the bdycm at all, until this new update re: 64. (Maybe this broke with the new bdycm update? Rev1/2 or whatever?) But my point is, how *can* it work, when forscan stops at 96? Could you...

I wonder if we'll see pants sold with faraday pockets. :P

A bit of news, I sent my debug log for bdycm writes to the forscan guys, and they sent me back a build which allows writes to the bdycm! As I said in another thread, they said .64 will be out soon and it will include this fix! (I asked if I could post the link/etc, but they said no, please...

This thread is so weird to me. I have two problems. 1) The brightness is never saved, and always defaults to 100% full on vehicle start. This is dumb. Why even have a setting, if it will just revert and you have to use it every single time. In any other car I've bought, this setting is...

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.

https://www.mustang6g.com/forums/threads/forscan-codes-s550-mustangs.98260/page-3#post-2155503 In the above there is talk about using forscan to disable it. That's for the S550, but the 650 should be the same? Here's info from the spreadsheet in the forscan forum on this site. It does look...

That seems quite strange. With all the options I see via forscan, you'd think all market requirements could be covered by country specific settings in various configs. Not saying you're wrong, it's just weird though.

I did not notice until a few weeks ago, as I was new to forscan, but writes to the bodycm do not work currently with the 2024. So my IPC changes do the trick, hide the nag, but MyTwoCents's suggestion for the ParkBrakeChime have not been tested yet. It may also work.

Info: when I initially setup forscan, I had the ABS pump fuse pulled. The IPMa/b module is on the same fuse (it seems). This meant that the database of stored, accessible modules was saved without the IPMa/b, and it never showed up again. Deleting the profile and re-learning the vehicle...