[Nikodim]

The real problem is not with us clients, but with Mazda itself.
When You buy your first Mazda car, 99% of clients have no idea what kind of features they're missing in that car. Also the Mazda disribuitors are not interested to sell the trims which they lack at the moment, actually they do everything they can go sell their existing trim out.
The understanding of how much features are missing in the acquired car comes only with time & experience in that car.
But Mazda policy does not permit to install additional missing features officially & exactly for that (and no other) reason we have this thread here. Actually there's a lot of people here who could pay more money for the better trim. But that trim either is not available in this country, or is missing on the market for a long period.

It is understandable also the company's desire to sell more their cars, but I for instance, am not ready to buy another car with one only feature more than I have already. The cost difference between the trims isn't really to much, and the DIY price is not much different from the trims' cost difference.

Indeed, this thread here has been started due to the deficiency of Mazda service & it's purpose is more to hasten Mazda to change their policy to the correct direction & start installing the additional features officially.
I personally would never buy the M3 BP Mazda generation with the policy like this. Also, I like my present vehicles even with the missing features & that is the best reason why I would not buy the BP.
I personally see the BP as the dead end for M3 line, even with every their improvement, exactly for their wrong service policy

 

[Nikodim]

For those who badly suffer from lack of information I've composed few excerpts in PDF format from M3 2017(?active at the moment on Mazda server) Workshop Manual. As with my previous attachments disregard the junk extension .CSV & open the file in PDF viewer.
Here attached follows the first one

 

[Nikodim]

Discovered the ELECTRIC PARKING BRAKE bit:
720-04-12 B3b1=
1 - EPB;
0 - No EPB

Also:
720-04-12 B3b0=1 - Every MX-5 ONLY

 

[Nikodim]

So, when You have decided to replace your SCBS type of FSC-2g. with A-SCBS type having acquired the second hand camera, You have to pay attention at the follwing FSC-2g. features:

In M3 706-01-03 B0B1=
0000 - SCBS,
???? - A-SCBS.

In M6 706-01-03 B0B1=
2020 - SCBS,
2021 - A-SCBS.

In M2/CX-3 706-01-03 B0B1=
4040 - SCBS,
4440 (4540 in case of GSH7-67-XCX..) - A-SCBS

In CX-5KF 706-01-03 B0B1=
6060 - SCBS,
6160 (6563) - A-SCBS.

In CX-8 706-01-03 B0B1=
8080 - SCBS,
8180 - A-SCBS.

In CX-9 706-01-03 B0B1=
C0C0 - SCBS,
C5C2 - A-SCBS.

In MX-5 706-01-03 B0B1=
E0E0 - A-SCBS

Unfortunately no details about M3 2019 A-SCBS since their AsBuilts are not available for analysing.

But, I have a suspicion that in addition to that You have to replace also your DSC module to the other one with Pedestrian support. No confirmation to that at the moment due to nobody did it before

 

[Nikodim]

Consider kindly a small correction to 720-04-16 B2 byte:

 

[Nikodim]

More than that!
With 706-01-01 B1 of FSC-1g. also everything is very easy:

Wagon --> B1=20,
Hatchback --> B1=30,
Sedan --> B1=10

 

[Nikodim]

The new discovery, & one more fortress fallen in FSC-1g.!
706-01-01 B3 corresponds to Market Regions BF01.
This way:
706-01-01 B3=10 --> BF01=11/14,
706-01-01 B3=20 --> BF01=21/24,
706-01-01 B3=30 --> BF01=31/34,
706-01-01 B3=50 --> BF01=51/54,
706-01-01 B3=60 --> BF01=61/64,
706-01-01 B3=70 --> BF01=71/74.

Don't believe me? Check yourself with any vehicle with FSC-1g.!

 

[Nikodim]

Herewith included is the database compilation of 200 Mazda vehicles with original LAS support in order to assist users choosing the correct setting value in 720-04-16 line.

At the first glance You might think - "everything looks to be easy: LHD --> 720-04-16 x4xx, RHD --> 720-04-16 x2xx". But in reality in some cases also some additional factors influence, like the Headlight type, Headlight levelling, AT/MT, sometimes even the type of TPMS (not included here).

For M3 everything looks to be opposite: LHD --> x2, RHD --> x4. But beware the other factors!
For M2/CX-5/CX-8 models also the choise only between two options: RHD --> x2, LHD --> x4.
CX-3/MX-5 have dropped completely out of research due to no vehicles found with LAS support.
For M6 everything is much more complicated, as the choise there increases with two options more: x6 & x8, where also some additional factors influence the choise (those are really complicated!)
For CX-9, again, everything looks to be easy: LHD --> x8, RHD --> x6. But the other factors may influence also.
Whoever finds that this research helped - report, please.
Whoever finds theese results wrong - report it also, just to know & try to investigate for eventual reason.
Good luck & successful mods!

 

[Nikodim]

And now, the NEW SENSATION!
Having checked over 1000 VINs with different configurations, today I've finally bumped into guess what???

THE ORIGINAL HALO HEADLIGHTS WITH ORIGINAL HBC/LDWS ACTIVATED !!!

Which I have been looking since a long time.
And more than that, I've found two VINs with this config

 

[Nikodim]

Second. As a literacy campaign, I would like to get some of You acquainted with Mazda concept of CCC BF-blocks.
As a matter of fact it's much easier to manipulate & compare vehicles configurations in this concept.
To start with, You can find them yourselves in the next excerpt:

Spoiler: BF-blocks example in IC file saved from Forscan

;Block 3
7200301012C
;Block 4
72004011A4F0080FF14
7200402FFFFFFC100EB
72004034A4D31474A87
720040431C1015735AE
720040539463132C1D3
7200406023037323804
72004073300C1033861
7200408003888940087
7200409C10400000801
72004102C0000BF0127
720041121000000005D
720041200BF0220001E
720041300000117BF15
7200414033000020074
72004150000BF043235
72004168000000000C1
7200417BF059004009A
7200418784F00BF06CF
7200419200000100074
720042000BF07000011
720042100200000BF2B
720042208212009009F
72004230000BF093046
720042400002000006F
7200425BF102000003F
7200426200003BF1144
7200427000000000052
72004280053

Actually in this example You can see not only BF-blocks but also C100 - C104 blocks where in C100-C102 is your (or the other's) VIN number placed.
These blocks can be easily converted from Mazda Asbuilt Search Page into excel line of your database, where You can manipulate & compare not by bits but by bytes already. Any byte can be also easily converted into bits (what I personally do in my mind already).
Find attached here also are a couple of screenshots from my database.
The difference with your conventional method of using the IC lines to compare is that with BF-blocks You can sort them, use different & multiple filters for blocks to compare or find some interesting patterns

 

[Nikodim]

A couple more patterns noticed in vehicles' CCC database (around 200 records).

HBC/LDWS features:

In vehicles with ALH - the IC pattern always gets 720-04-19 A2..
for FSC-2g. -- 706-01-01 6C80..
for FSC-1g. -- 706-01-01 A.. (couldn't believe it may happen with FSC-1g. !!!)

In vehicles with ALS/AFS - the IC pattern always gets 720-04-19 92..
for FSC-2g. -- 706-01-01 6C80..

In vehicles with ALS/AFS - the IC pattern always gets 720-04-19 22..
for FSC-1g. -- 706-01-01 2.. (for FSC-1g. that is normal)


HBC/LDWS/LAS features:

In vehicles with ALH - the IC pattern always gets 720-04-19 B0..
for FSC-2g. -- 706-01-01 6C80 X000 72xx & 706-01-02 84XX ..
for FSC-1g. -- 706-01-01 B820 XXXX 00xx & 706-01-02 8C81 0000 XXXX (noticed in one CX-9!)

In vehicles with ALS/AFS - the IC pattern always gets 720-04-19 C0..
for FSC-2g. -- 706-01-01 6C80 X000 72XX & 706-01-02 84XX ..
for FSC-1g. -- settings never noticed!

Now there're 2 outcomes of that research:
1-st. - is it really possible to have LAS working with FSC-1g. (like the example in CX-9/2017) or was there something special in that case?
2-nd. - it has become clear that in settings for FSC-1g.:
706-01-01 2XXX - indicates support of HBC feature,
706-01-02 2C81 - 2C indicates support of LDWS feature & 81 - HBC feature

 

[Nikodim]

For those who suffer from incorrect operation of LKAS(LAS) here attached is it's description in Workshop Manual. You can figure out yourself what is causing the incorrect operation(non operation) of LKAS. As the .pdf extension is not accepted in attachments You have to cut off here the .doc extension & open the file in PDF viewing program

 

[Nikodim]

Your direction of thinking is correct.
Every pressing of TPMS button doesn't reset the warning. Neither that button is the ON/OFF button. Every pressing does the new situation with every wheel speed of rotation re-learning into memory for the later analysis when any wheel changes it's speed.
Exactly due to that reason the enabling of TPMS in IC feature is useless without installing the button, because there's no other way to force re-learning

 

[Nikodim]

The easy table to determine what kind of bits to use in order to enable LAS in 720-04-16 B0=

x2 -
M2 (LHD/RHD);
M3 (LHD);
CX5-KE (RHD);
M6 (LHD-WGN[2018-2020]);
M6 (LHD-SD[2015-2017]);
CX5-KF (RHD);
CX8 (RHD).

x4 -
M3 (RHD);
CX5-KE (LHD);
M6 (LHD-SD[2018-2020]);
M6 (LHD-WGN[2016-2017]);
CX5-KF (LHD);
CX8 (LHD).

x6 -
M6 (RHD-WGN[2018-2020]);
M6 (RHD-SD[2015-2017];
CX9 (RHD).

x8 -
M6 (RHD-WGN[2015-2017]);
M6 (RHD-SD[2018-2020]);
CX9 (LHD).


P.S. I have never met even one of the MX-5/CX-3 vehicles with LAS enabled.
Whoever find it kindly inform me.

 

[Nikodim]

FYI

Mazda As-Built Search Engine

has shifted also to new page which can be accessed from any browser (and not IE6 only as earlier):
Mazda As-Built Search Engine

 

[Nikodim]

And it is just a coinsidence that for FSC-1g. with
706-01-01 B3=10 the LDWS starts functioning with >40kmph. Probably that speed in Japan is accepted as standard for LDWS

 

[Nikodim]

I didn't really expect that RHD/LHD discovery (which doesn't indeed interest anybody) in reality can lead to more discoveries.
This time, while investigating the connection between 706-01-02 & 720-04-16, the research resulted again into RHD/LHD rule.
Here comes the compilation of this research results, from which it becomes clear which value to use in FSC-1g. 706-01-02 line, with couple exceptions (added)

 

[Nikodim]

I've checked the settings of all them 30 VIN (available to me) examples with FSC-1g. (in CX-5/CX-9/M6), supporting LAS & found only two with AFLS, all the others are equipped with ALH. And really they have the difference (comparing to ALH equipped) in FSC settings.
Example: CX-9 (AFLS) JM3TCBEYXH0133284 with 706-01-01 C820 5220 0069; 706-01-02 7081 0000 7071 (4WD, MRCC).
The others with ALH - are as follows:
CX-5 (ALH) 706-01-01 B120 6130 0071, 706-01-02 8C82 0000 708E (4WD);
CX-5 (ALH) 706-01-01 B120 6230 0072, 706-01-02 8C82 0000 708E (4WD, MRCC);
CX-5 (ALH) 706-01-01 B120 9110 0081, 706-01-02 8C81 0000 708D (2WD);
CX-5 (ALH) 706-01-01 B120 A210 0092, 706-01-02 8C81 0000 708D (4WD, MRCC);

CX-9 (ALH) 706-01-01 B820 5270 00A9, 706-01-02 8C81 0000 708D (4WD, MRCC);
CX-9 (ALH) 706-01-01 B820 9250 00C9, 706-01-02 8C81 0000 708D (2WD, MRCC);

M6 (ALH) 706-01-01 B220 9210 0083, 706-01-02 8C82 0000 708E (2WD, MRCC);
M6 (ALH) 706-01-01 B210 9210 0073, 706-01-02 8C82 0000 708E (2WD, MRCC);
M6 (ALH) 706-01-01 B210 9250 00B3, 706-01-02 8C81 0000 6885 (2WD, MRCC);
M6 (ALH) 706-01-01 B210 A210 0083, 706-01-02 8C82 0000 708E (4WD, MRCC);
M6 (ALH) 706-01-01 B220 9110 0082, 706-01-02 8C82 0000 708E (2WD).

Now, due to everything described above & some additional investigation performed, the considerations are:
1. For FSC-1g. the digit in senior semi-byte of 706-01-01 B0 byte should exactly correspond to what expected to be in 720-04-19 B0 senior semi-byte (like 706-01-01 CXXX ---> 720-04-19 C0XX; or 706-01-01 2XXX ---> 720-04-19 2XXX, or 706-01-01 4XXX ---> 720-04-19 41XX, or 706-01-01 AXXX ---> 720-04-19 A2XX, etc.);
2. The junior semi-byte of 706-01-01 B0 byte is Mazda model dependant & corresponds to the value according to the following pattern: M2 --> 5; M3 --> 3; M6 --> 2; CX-3 --> 7; CX-5 --> 1; CX-9 --> 8; MX-5 --> 6.
3. Also, all of them cases of LAS enabled with FSC-1g. & ALH result into 706-01-02 8CXX 0000 70XX(68XX).
4. The only two cases of LAS enabled with FSC-1g. & AFLS are - 706-01-02 70XX 0000 70XX.

According to these considerations for your LAS enabling in CX-5 with FSC-1g. the recommendations would be:
720-04-19 C0XX...;
706-01-01 C1XX...;
706-01-02 70XX 0000 70XX.

In case when your FSC-1g. refuses to accept 706-01-01 C1XX.. - my only explanation is that your FSC model isn't really suitable for LAS support.
Good luck & entertainment!

 

[Nikodim]

Procedure to fill the new vehicle in to the new line of "CCC Research" tab as follows:
1. N_PAD - in notepad mark the entire block of "CCC_DATA" the same way as You did before in order to fill the 720-04-XX block in IC tab, then on keyboard with "CTRL+C" copy this block into memory.
2. CCCC_1 - in "CCC Converter" tab, having choosen the cell B1, paste that block from memory into B1 cell by keyboard combination "CTRL+V".
3. CCCC_2 - in "CCC Converter" tab mark the block L3-L32 (for M3/M6/CX-5/CX-9 enough to mark L3-L16). Again use the keyboard combination "CTRL+C" to copy block into memory.
4. CCCC_3. After that choose the cell O3 in "CCC Converter" tab & with the right mouse button click call the menu for "Paste Special" procedure.
5. CCCC_4, where from the "Paste Values" sub-menu choose & click on the "Values (V)" icon. This way the O3-O32 column gets filled only with data values (instead of formulas, present earlier).
6. CCCC_5. Then mark there the entire block O3-O32 & with "CTRL+C" copy it into the memory.
7. CCCR_6. In "CCC Research" tab choose the cell in new line of C column & with right mouse button click call again the "Paste Special" sub-menu.
8. CCCR_7. Where from the upper "Paste" division choose & click the last icon with the hint "Transpose (T)".
9. CCCR_8. This way all the cells of 720-04-XX block in the new line get filled in.
That's it.
Unfortunately, all the other data in the new line up to the moment can be filled in only manually, as the automated procedure is rather complicated.

 

[Nikodim]

New candies for You!

My freshest investigation cleares the mystic of LAS enabling in IC & which part plays the 720-04-16 line (BF04 block) in it.

Now I'm 100% sure that the junior semi-byte b0,b1,b2,b3 of 720-04-16 B0 byte is really responsible only for LAS activation with values x2/x4/x6/x8 in this byte, and all of them 4 cases do the same job (activate LAS) in different vehicles equipped with FSC-2g. cameras. Some other vehicles of CX-5 & CX-9 equipped with FSC-1g. also supporting LAS dropped out of the results of investigation, but they also confirm these results (a couple additional lines in them can complement the research later.
In the compilation of research results every vehicle of my CCC database with 720-04-19 B0/C0/D1 took part, as only they affect to the aforesaid semi-byte. The vehicles with 720-04-19 22/41/90/92/A2 are useless as they impose no effect to this semi-byte.
To compilation included are all the BF-blocks which may influence this semi-byte. The tables are filtered & sorted by effects from C103, C104 & value of semi-byte in red.

I have to admit that You may notice a couple of conflicts there between x2 VS x4 table and x6 VS x8 table, but if You look & analyse attentively - You will see the solution.

Whoever likes to dispute on the matter - You're welcome