Page 1 of 4

Beta testing Forscan for Windows

Posted: Thu May 12, 2016 6:23 pm
by BrudnyHenryk
I'm testing direct config on beta 2.3.1and:
APIM direct config (Sync2) works fine for:
Ford Focus MK3 (2012)
Ford Focus MK3.5 (2016)
Ford Mondeo MK5 (2016)
Ford C-Max MK2 (2015)
Ford Kuga MK2 (2015)

Re: Beta testing Forscan for Windows

Posted: Thu May 12, 2016 6:45 pm
by BrudnyHenryk
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

Re: Beta testing Forscan for Windows

Posted: Mon May 16, 2016 3:24 am
by jason
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

Re: Beta testing Forscan for Windows

Posted: Fri May 20, 2016 7:58 am
by yanxunniurou
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
Same question,to await......

Re: Beta testing Forscan for Windows

Posted: Wed May 25, 2016 9:19 am
by BrudnyHenryk
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
Speed camera warnings:
7D0-02-02 1000 0000 00EB no speed camera warnings.
7D0-02-02 1008 0000 00F3 warning of speed cameras.
7D0-02-02 1009 0000 00F4 (to be tested).

Re: Beta testing Forscan for Windows

Posted: Wed May 25, 2016 9:27 am
by BrudnyHenryk
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

Speed camera warnings:
7D0-02-02 1000 0000 00EB no speed camera warnings.
7D0-02-02 1008 0000 00F3 warning of speed cameras.
7D0-02-02 1009 0000 00F4 (to be tested).
Rear view camera:
7D0-02-01 524F 0005 0080 no camera.
7D0-02-01 524F 0006 0081 camera.

Re: Beta testing Forscan for Windows

Posted: Thu May 26, 2016 5:57 am
by ten3or
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
Also works on Ford Explorer (2013).
But no information about current street on the IPC in a mode without target.

Re: Beta testing Forscan for Windows

Posted: Mon May 30, 2016 10:21 pm
by Pir8
BrudnyHenryk wrote:
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

Speed camera warnings:
7D0-02-02 1000 0000 00EB no speed camera warnings.
7D0-02-02 1008 0000 00F3 warning of speed cameras.
7D0-02-02 1009 0000 00F4 (to be tested).
Rear view camera:
7D0-02-01 524F 0005 0080 no camera.
7D0-02-01 524F 0006 0081 camera.
Is this info confirmed? would changing 2nd byte in 7D0-02-01 enable rear view camera function?
7D0-02-01 524F 0005 0080 no camera.
7D0-02-01 524F 0006 0081 camera.

I keep getting different answers to this question.....

Re: Beta testing Forscan for Windows

Posted: Wed Jun 01, 2016 10:59 am
by ClockWorK
The big thing to remember (aside from the fact that most of us are also on XDA), is that we are modifying BITs. Not bytes. Some of the posts on XDA don't make that clear.
(like, on the nav, we're not changing a byte from 0 to 4 -- we're changing 1 bit within a byte. We're changing 00000000 to 00000100. The other 7 bits might be for totally different things.)

Changing one bit to test probably won't hurt anything. But I recommend backing up your modules data with FORScan just to be safe. And have your .AB from file from Ford handy too. Worst case, you might get some DTC codes if you turn on a feature that your car can't support.

I'm pretty sure the bit I identified is for enabling/disabling the guide-lines that are displayed on the camera image when backing up. Not for the camera itself.


(not responsible if you change a bit and it makes your car explode, brick, turn into a pumpkin, or transform into a robot)

Re: Beta testing Forscan for Windows

Posted: Tue Jun 07, 2016 8:52 pm
by Livnitup
2016 F-150

720-01-01 2F0F 1064 7651 Auto Engine Off & Auto High Beam option in productivity screen present
720-01-01 1F0F 1064 7641 Auto Engine Off option absent
720-01-01 2F00 1064 7642 Auto High Beam option absent
720-01-02 221B 50B7 DTE Calculation option present in productivity screen
720-01-02 121B 50A7 DTE Calculation option absent in productivity screen
720-02-01 4DE0 3C31 1CE0 Daytime Lights option present in Settings, Adv Settings, Vehicle, Lighting
720-02-01 4DA0 3C31 1CC0 Daytime Lights option absent in Settings, Adv Settings, Vehicle, Lighting
720-07-02 0400 0034 Trailer Light Status option in productivity screen present
720-07-02 0300 0033 Trailer Light Status option in productivity screen absent

Sync 3:
7D0-03-01 0000 0003 00DE Changes highlighted menu choice to different colors (Audio, Climate, Phone, Nav, Apps, Settings) from the standard blue