TJN: OK - sorry, but I need to launch into a little hexadecimal maths theory.
So as you probably already know, the Bytes on these control modules are stated as what's called a "hexadecimal Pair". Hence a Byte value of hex12 is actually hex1 & hex2 (these used to be called the "upper nibble" and the "lower nibble" - Byte/nibble, get it?)
Also, and again as you probably already know, each Byte is made of 8 x Bits - so each hexadecimal number requires 4 x Bits. And, for a Byte, the Bits are read from the right side to the left side so that Bit0 is on the extreme RHS and Bit7 is on the extreme LHS. A string of Bits is called a "Binary" number
So the binary equivalent for the Byte values are as follows (remember that Bit 0 is on the extreme RHS) - I've put a space in the Bit sequence to represent each hexadecimal number. but `OBD11/VCDS doesn't do this:
Byte value =Binary value
hex00=0000 0000
hex01=0000 0001
hex02=0000 0010
hex03=0000 0011
......
hex10=0001 0000
hex11=0001 0001
hex12=0001 0010
......
hexFF=1111 1111
What's all this mean - I hear you asking? Well, in OBD11 speak and as shown above - a Byte value of hex12 is equivalent to ticking Bit 1 and Bit 4 and leaving all other Bits un-ticked.
Don
PS: If the stuff above makes sense, then the VCDS screen below should also make sense (I hope)