long coding

[Aspen]

Hi All,

I have done an auto scan of all mudules. And now want to change the long coding so that the car chirps when alarming / disarming with the remote.

The thing is, I know how to change the long coding. And what it currently is, but I don't understand it. Not one bit. what do all the nikbers mean?

I have got the link to the page that has all the coding options etc and what bits are what etc. And I'm stuck.

This is the original coding from my car
1980200002186D0985054C9FC637

so what does what and what do i change? anyone?

 

[VWAddict]

The long-coding is broken down into 'letters and numbers' because it's easier to read than a mind-numbingly lengthy series of ones and zeroes.

Each number/letter represents four ones and zeroes. There are sixteen possible combinations available using ones and zeroes; and each combination is represented by a character:

0000 = 0 (zero)
0001 = 1
0010 = 2
0011 = 3
0100 = 4
0101 = 5
0110 = 6
0111 = 7
1000 = 8
1001 = 9
1010 = 10
1011 = 11
1100 = 12
1101 = 13
1110 = 14
1111 = 15

Now, to represent this number using standard numeric representation, only TEN of the combinations can be shown using a single character... specifically zero through nine. For the other six (ten through to fifteen inclusive) we'd need two characters... so to save space, we use "hexadecimal" notation. (Hint: for more information or a potentially better explanation than I can give, google "Hexadecimal"!)

In memory storage, a "Byte" -as a unit of memory storage- is a set of eight binary 'positions' which can each be either a one or a zero.

each 'Byte' in the long coding bage is displayed as two hexadecimal characters, because it's easier to read, say, remember, and type "9C" without making mistakes than it is to say "10011100".

Taking 9C as an example, the 'byte' 10011100 is broken down into two 'Nibbles', 1001 and 1100 respectively. -Looking at the following table, you can see that 9 is a way of saying "1001" and C is a way of saying "1100".

0000 = 0 (zero)
0001 = 1
0010 = 2
0011 = 3
0100 = 4
0101 = 5
0110 = 6
0111 = 7
1000 = 8
1001 = 9
1010 = A
1011 = B
1100 = C
1101 = D
1110 = E
1111 = F

Does this make any sense to you? (I'm not always very good at explaining things so that they're easier to understand... quite often my attempts to explain just confuse people further!!!)

Keith

PS: my first post here...

 

[VWAddict]

So... looking at your long-coding,

1980200002186D0985054C9FC637

It may not seem particularly easy to understand, but -believe it or not- that's an EASIER way of expressing the binary coding...

Taking the first ten hex characters of your long-coding and looking at what they represent:

1 = 0001
9 = 1001
8 = 1000
0 = 0000
2 = 0010
0 = 0000
0 = 0000
0 = 0000
0 = 0000
2 = 0010

...So your first ten digits represent the first five 'bytes', the first forty bits of the binary code... which would look like this:

0001100110000000001000000000000000000010....

hopefully you can see that -even though it may LOOK pretty confusing- it's actually LESS confusing than if you had to keep track of all the ones and zeroes, and make edits in the middle of THAT confusing string...

Keith

 

[Aspen]

yeah it's making sense. I think.

I just need to relate this to what I now want the long coding to read. To achieve the results I want, I.e the chirp when the key fob is used.

I'll let you know how I get on in doing untold damge to my new car. lol

 

[bearthebruce]

What version of VCDS/VAG-COM are you using? If you are using a current version - 7XX or higher, then you could use the Long Coding helper to get through all of this:
http://www.ross-tech.com/vag-com/tour/recode_screen.html

Scroll to bottom of the page and you will see the Long Coding helper. It was distributed with VAG-COM for quite a while and then later was integrated into the package. With it, the job of modifying the coding for a module like yours is greatly simplified.

If you are running version 409 in shareware, it might be a good idea to ask a buddy who has the full current version to stop by to help you out.

 

[VWAddict]

I think that as you flip through the bytes individually in the long coding page (it's either the up/down arrows or the left/right arrows on the keyboard... -I forget which) you'll see the byte which you're on highlighted in a different colour... -yellow perhaps... -I forget.

Anyhow, if you're talking about an 8P platform A3 (which is what I also have), then I think you might see some options appearing and disappearing in tick-boxes towards the lower part of the window. -Sometimes it's easier to just use these, specially if you have a simple "on/off" command that you want to change.

Ao, if you see a tick box for (for example) "chirp, alarm arming when locking" ...or some similar wording... you can click on that tick-box to toggle the "tick" on and off alternately. -There will also be a "chirp, alarm arming when UNlocking" also.

As you topggle the bits on and off, you should see the hexadecimal character changing with each change to reflect the new binary information. (at least, you do with the version which I have!)

If in any doubt, take screenshots or photographs, and note EVERY change, making clear which is the OLD figure, so if you get lost, you can RETURN to how it was at the start.

As it happens, I just DISABLED the chirp which my (USA-spec) A3 (8P) came enabled with... -It's a feeble sort of 'peep' instead of the actual horn, and I live in a quiet neighborhood, so I don't like unneccesary noise... Funny that you want the exact opposite!

Plus, I also added the window roll-down and roll-up from the remote key... VERY useful when the inside of the car is hotter than an oven...

Keith