Possibly Related Threads…

***TheNine90*** · 12-01-2023, 09:10 AM,

Im looking for a way to disable CC messages using CC-ID codes through coding. Similar to how sos is coded out by changing 5th byte from FF and F7 in CC_AKTIVIERUNG_5.

Is there a way to map the codes to the CC_AKTIVIERUNG in the cafd? Or cc messages that are under specific CC_AKTIVIERUNG block?

***iyade46*** · 12-01-2023, 12:38 PM,

(12-01-2023, 09:10 AM)TheNine90 Wrote: Im looking for a way to disable CC messages using CC-ID codes through coding. Similar to how sos is coded out by changing 5th byte from FF and F7 in CC_AKTIVIERUNG_5.

Is there a way to map the codes to the CC_AKTIVIERUNG in the cafd? Or cc messages that are under specific CC_AKTIVIERUNG block?

what fault you wana disable i can find you what CC-ID for that system

***TheNine90*** · (This post was last modified: 12-01-2023, 14:05 PM by TheNine90.)

I have a complete list of the CC-ID. I want to know how it relates to the fdl and how to work it out. Also how to delete individual CC message.

You can choose any CC-ID and illustrate how figure out it location in the fdl and to disable it.

***Node*** · (This post was last modified: 12-01-2023, 14:38 PM by Node.)

IMHO general idea is that there is 1 bit for each CC-ID and all of them are sequential.

AFAIK SOS failure is CC-ID 299.

Each group has 8 bytes so 64 (= 8 * 8) bits total.

299 / 64 = 4.xxx so it's 5th group (as groups are counted from 1: 4 + 1 = 5).

299 - 64 * 4 = 43 so it's 43rd bit in 5th group.

43 / 8 = 5.xxx so it's 5th byte (as bytes are counted from 0: 5 + 0 = 5).

43 - 5 * 8 = 3 so it's 3rd bit (as bits are also counted from 0)

3rd bit has value of 8 (= 2 ^ 3) so FF - 8 = F7. Well, to be more precise - works when bit WAS SET ONLY. Normally you would do NOT-AND operation which works always. So initial value FF & (~8). ~8 = F7. FF & F7 = F7.

ELEMENTARY!!!

***TheNine90*** · 12-01-2023, 19:39 PM,

Thanks for the explanation.

***elthox*** · 13-01-2023, 10:24 AM,

(12-01-2023, 14:31 PM)Node Wrote: IMHO general idea is that there is 1 bit for each CC-ID and all of them are sequential.

AFAIK SOS failure is CC-ID 299.

Each group has 8 bytes so 64 (= 8 * 8) bits total.

299 / 64 = 4.xxx so it's 5th group (as groups are counted from 1: 4 + 1 = 5).

299 - 64 * 4 = 43 so it's 43rd bit in 5th group.

43 / 8 = 5.xxx so it's 5th byte (as bytes are counted from 0: 5 + 0 = 5).

43 - 5 * 8 = 3 so it's 3rd bit (as bits are also counted from 0)

3rd bit has value of 8 (= 2 ^ 3) so FF - 8 = F7. Well, to be more precise - works when bit WAS SET ONLY. Normally you would do NOT-AND operation which works always. So initial value FF & (~8). ~8 = F7. FF & F7 = F7.

ELEMENTARY!!!

Assuming cc-id 256, how this math will work?

256 - 64 * 4 = 0
0 / 8 = 0
0 - 0 * 8 = 0

***Node*** · (This post was last modified: 13-01-2023, 11:20 AM by Node.)

(13-01-2023, 10:24 AM)elthox Wrote:
(12-01-2023, 14:31 PM)Node Wrote: IMHO general idea is that there is 1 bit for each CC-ID and all of them are sequential.

AFAIK SOS failure is CC-ID 299.

Each group has 8 bytes so 64 (= 8 * 8) bits total.

299 / 64 = 4.xxx so it's 5th group (as groups are counted from 1: 4 + 1 = 5).

299 - 64 * 4 = 43 so it's 43rd bit in 5th group.

43 / 8 = 5.xxx so it's 5th byte (as bytes are counted from 0: 5 + 0 = 5).

43 - 5 * 8 = 3 so it's 3rd bit (as bits are also counted from 0)

3rd bit has value of 8 (= 2 ^ 3) so FF - 8 = F7. Well, to be more precise - works when bit WAS SET ONLY. Normally you would do NOT-AND operation which works always. So initial value FF & (~8). ~8 = F7. FF & F7 = F7.

ELEMENTARY!!!

Assuming cc-id 256, how this math will work?

256 - 64 * 4 = 0
0 / 8 = 0
0 - 0 * 8 = 0

So it will be 0'th bit in byte 0 smile

0'th bit value is 2^0 = 1, so FF & (~1) = FE (assuming initial value was FF).

***elthox*** · 13-01-2023, 12:58 PM,

(13-01-2023, 11:19 AM)Node Wrote:
(13-01-2023, 10:24 AM)elthox Wrote:
(12-01-2023, 14:31 PM)Node Wrote: IMHO general idea is that there is 1 bit for each CC-ID and all of them are sequential.

AFAIK SOS failure is CC-ID 299.

Each group has 8 bytes so 64 (= 8 * 8) bits total.

299 / 64 = 4.xxx so it's 5th group (as groups are counted from 1: 4 + 1 = 5).

299 - 64 * 4 = 43 so it's 43rd bit in 5th group.

43 / 8 = 5.xxx so it's 5th byte (as bytes are counted from 0: 5 + 0 = 5).

43 - 5 * 8 = 3 so it's 3rd bit (as bits are also counted from 0)

3rd bit has value of 8 (= 2 ^ 3) so FF - 8 = F7. Well, to be more precise - works when bit WAS SET ONLY. Normally you would do NOT-AND operation which works always. So initial value FF & (~8). ~8 = F7. FF & F7 = F7.

ELEMENTARY!!!

Assuming cc-id 256, how this math will work?

256 - 64 * 4 = 0
0 / 8 = 0
0 - 0 * 8 = 0

So it will be 0'th bit in byte 0
0'th bit value is 2^0 = 1, so FF & (~1) = FE (assuming initial value was FF).

Got it. So in another scenario, 250 would have:
7th group
FF FF FF FF FF FF FF FB

***Node*** · (This post was last modified: 13-01-2023, 13:23 PM by Node.)

(13-01-2023, 12:58 PM)elthox Wrote:
(13-01-2023, 11:19 AM)Node Wrote:
(13-01-2023, 10:24 AM)elthox Wrote:
(12-01-2023, 14:31 PM)Node Wrote: IMHO general idea is that there is 1 bit for each CC-ID and all of them are sequential.

AFAIK SOS failure is CC-ID 299.

Each group has 8 bytes so 64 (= 8 * 8) bits total.

299 / 64 = 4.xxx so it's 5th group (as groups are counted from 1: 4 + 1 = 5).

299 - 64 * 4 = 43 so it's 43rd bit in 5th group.

43 / 8 = 5.xxx so it's 5th byte (as bytes are counted from 0: 5 + 0 = 5).

43 - 5 * 8 = 3 so it's 3rd bit (as bits are also counted from 0)

3rd bit has value of 8 (= 2 ^ 3) so FF - 8 = F7. Well, to be more precise - works when bit WAS SET ONLY. Normally you would do NOT-AND operation which works always. So initial value FF & (~8). ~8 = F7. FF & F7 = F7.

ELEMENTARY!!!

Assuming cc-id 256, how this math will work?

256 - 64 * 4 = 0
0 / 8 = 0
0 - 0 * 8 = 0

So it will be 0'th bit in byte 0
0'th bit value is 2^0 = 1, so FF & (~1) = FE (assuming initial value was FF).

Got it. So in another scenario, 250 would have:
7th group
FF FF FF FF FF FF FF FB

Yes. (except 7th byte, not group smile

, in the 4th group)

***elthox*** · 19-01-2023, 12:57 PM,

Hi Node,

How would you operate among the below codes? so basically when there are multiple codes for the same message.

CC-ID 253
Parking Brake Failed
CC-ID 239
Parking Brake Failed
CC-ID 240
Parking Brake Failed
CC-ID 241
Parking Brake Failed
CC-ID 242
Parking Brake Failed
CC-ID 243
Parking Brake Failed

Possibly Related Threads…
Thread		Author	Replies	Views	Last Post
	Brake Pads Warning Disable -Racing purpose	marcdts	2	130	19-04-2024, 19:59 PM Last Post: bmchicago
	Flash CAS 3 for disable ELV	UnFan	3	192	19-04-2024, 08:20 AM Last Post: ravager
	Requesting FSC enabling codes for BMW F40	BMWF01	3	180	10-04-2024, 10:10 AM Last Post: RuleNormaliai
	E60 disable active steering	BimmerSLO	4	406	05-03-2024, 19:32 PM Last Post: BimmerSLO
	NEED FA CODES FROM VIN E92	tigre	1	110	28-02-2024, 17:41 PM Last Post: nBlacky
	G01 disable Seat Belt Tightening after drive away	BusyBox	5	449	13-02-2024, 13:03 PM Last Post: BusyBox
	Solved ✔ F56, disable Keyless Entry by coding	Edward1968	5	696	07-02-2024, 19:48 PM Last Post: Edward1968
	Solved ✔ Cas3 black disable elv	sokisoki3	6	590	25-01-2024, 11:35 AM Last Post: sokisoki3
	G06 2020 radiator shutters disable?	biktel	7	496	04-01-2024, 13:16 PM Last Post: huk_00
	Ride height sensor - disable	carat10_2	9	1,393	22-12-2023, 23:22 PM Last Post: maksymw

Contact Us