Page 3 of 4

Re: Beta testing Forscan for Windows

Posted: Thu Oct 27, 2016 8:04 am
by fblasot
Hi,
with forscan 2.3.4 and my focus mk3.5 2015 is missing from configuration modules IPC and BCM "as built format" (central config and backup are present), other modules like APIM "as built format", are working good.
What I'm missing ?
Thanks.

Re: Beta testing Forscan for Windows

Posted: Thu Nov 03, 2016 9:57 am
by Dragunov
When u try to activate the possibility to disable/enable the DRL, something goes wrong.

U can disable them, but not enable them anymore.

He already changed it back to the original setting, but no respond.

Code he changed: Line 720-02-01 BBA0 so A becomes E

Forscan changes 726-16-02 automatically, when u activate 720-02-01.

I wonder if this is a bug, I guess so, cause Forscan changes code where we don't want it!

Re: Beta testing Forscan for Windows

Posted: Thu Dec 08, 2016 3:11 pm
by ivofe
Pats programming Ford connect 2004 works.

Diagnostic Ford connect works.

Diagnostic Ford Galaxy 2014 Diesel works.

Re: Beta testing Forscan for Windows

Posted: Sat Jan 07, 2017 7:27 am
by dazst250
jason wrote:Hi BrudnyHenryk,

Do you know which bytes are used with OPS( Optical Parking System) setting(s) of SYNC2 (APIM) Direct Config?

Thanks a lot,
Jason

BrudnyHenryk wrote:Known APIM Direct Config settings:

Sync2 navigation:
APIM Direct Config:
7D0-01-02 0009 0604 806D Without Navigation
7D0-01-02 0409 0604 8071 With Navigation

Sync2 climate control:
APIM Direct Config:
7D0-04-01 0103 0200 00E2 with climate control
7D0-04-01 0103 0201 00E3 without climate control

Checksum:
Last two bits are checksum in hex. If the checksum is higher than two digits, only last two digits are the result. For example:
7D0-04-01 0103 0200 00E2
07+D0+04+01+01+03+02+00+00=E2
Ive been looking through most of the PAM park assist module and APIM and these are what ive managed to fathom out.

736 - Park Assist Module

736-01-01 0x00 0000 4=Rear only and C=front and rear

736-01-01 00x0 0000 4=Manual trans and 5=Auto trans

736-01-01 0000 x000 0=LED parkaid switch off and 1=LED parkaid switch on (this doesn't activate the actual switch just the LED for it)

736-01-01 000x 0000 Trailer tow package(tailboard lights) C=ON 8=OFF, 9=Towbar and D=both

Then on different block line

736-03-01 0x00 0000 6=Rear only and 0=front and rear

7D0 - APIM

7D0-04-02 000x 1=Rear only and 7=front and rear (this is for the graphic on the APIM)

Im still testing some of these bits so if anyone else has info for other things on the Park Assist system please feel free to note them down

Re: Beta testing Forscan for Windows

Posted: Mon May 01, 2017 5:53 am
by rensoman59
Hello,

Apologies for potentially posting in wrong thread, I would like to request beta tester lifelong license.

Re: Beta testing Forscan for Windows

Posted: Tue May 02, 2017 9:48 pm
by KRIS-CAR
Hello,Apologies for the possibility of posting in wrong thread, somebody may be useful to vbf files.Unfortunately, the file is too big to give a link to https://mega.nz/#!A9ghQDgQ!2wDg5Mmk1OpR ... t2kyUCzw28
Sorry for my bad english

Re: Beta testing Forscan for Windows

Posted: Fri Dec 29, 2017 2:00 am
by yiwinter
Hello,Which bit is to control the voice control's position in steering wheel? using button or a spanner (the old steering wheel).

Re: Beta testing Forscan for Windows

Posted: Thu Jan 04, 2018 10:01 am
by zhoujun
jason wrote:Hi BrudnyHenryk,

Do you know which bytes are used with OPS( Optical Parking System) setting(s) of SYNC2 (APIM) Direct Config?

Thanks a lot,
Jason
only two byte need to be changed on APIM for OPS
BEFORE ENABLE OPS
7D0-01-01 0328 6182 10F7
7D0-01-02 040C 1A80 0C90
7D0-02-01 4348 0106 40AC
7D0-02-02 8200 0800 0065
AFTER ENABLE OPS
7D0-01-01 0B28 6182 10F7 --->plus 8 for the second byte : 3(original)+8=B(after)
7D0-01-02 040C 1A80 0C90
7D0-02-01 4348 0106 40AC
7D0-02-02 8200 2800 0065 ----->change from 0(original) to 2(after) for the fifth byte

Re: Beta testing Forscan for Windows

Posted: Mon Aug 20, 2018 11:37 pm
by VIS
zhoujun wrote:
Thu Jan 04, 2018 10:01 am
jason wrote:Hi BrudnyHenryk,

Do you know which bytes are used with OPS( Optical Parking System) setting(s) of SYNC2 (APIM) Direct Config?

Thanks a lot,
Jason
only two byte need to be changed on APIM for OPS
BEFORE ENABLE OPS
7D0-01-01 0328 6182 10F7
7D0-01-02 040C 1A80 0C90
7D0-02-01 4348 0106 40AC
7D0-02-02 8200 0800 0065
AFTER ENABLE OPS
7D0-01-01 0B28 6182 10F7 --->plus 8 for the second byte : 3(original)+8=B(after)
7D0-01-02 040C 1A80 0C90
7D0-02-01 4348 0106 40AC
7D0-02-02 8200 2800 0065 ----->change from 0(original) to 2(after) for the fifth byte


With regards to the ops is that for rear view camera only or parking sensors display too?

I’ve noticed on the 2015 st focus with sync 2 the second byte is 9 and change to a B for the camera activation? Your second byte being a 3, does that also change to a B to activate camera? Is it change to B regardless of what the second digit is? or is the 5th byte needed too for camera?
What if it’s sync 3 with the second byte 8? Still B?
Or A?
One thing I’ve noticed on 2018 Fiesta with sync3 that if you change byte 2 being 8 to a B for camera, camera functions correctly but the auto day night doesn’t seem to function?
Maybe sync 3 requires different digit?
Thanks

Re: Beta testing Forscan for Windows

Posted: Sun Jan 13, 2019 9:50 pm
by Tabakaz
Hello for everyone.
Sorry if i post not in correct place. Just really fresh at forscan :)

I need help. I installed rear park sensors for my Fiesta 2013 1.0 Ecoboost. But allready in the darkness. I managed to pop car icon on a screen, after 2-3 sec it gone... Im assuming i need to do some changes on bcm? If could somebody advice or link me, would be perfect !!
Cheers !!!!