Long Coding Helper for Short Coding Decrypting

Long Coding Helper for Short Coding Decrypting

Several control modules will use an additive coding, or binary for the soft coding. A list of features or functions have a numeric value, add up the values to get the sum total and that is the coding. For example, the (7L) Touareg Central Electronics does this:

+0000001 = DRLs always ON, not optional in MFI
+0000002 = Driving Light for USA/Canada (Xenon Low Beams Off when High Beams are On)
+0000004 = Interior Comfort Lighting Enabled
+0000008 = Rain & Light Sensors Enabled
+0000016 = Coming Home Lights Enabled
+0000032 = Rear Fog Lamps Enabled
+0000064 = Front Fog Lamps Enabled
+0000128 = Xenon Lighting Installed/Enabled
+0000256 = Marker Lights for USA/Canada Enabled
+0001024 = Headlight Washers Enabled
+0002048 = Electric Fuel Pump Relay Block (Gasoline Engines Only!)
+0004096 = Wake-up Function (for Air Suspension)
+0008192 = Second Battery Enabled
+0016384 = Auxilliary Battery Enabled (V10 TDI only)
+0032768 = Low-line Seat Heating Enabled (No Memory Seats Only)
+0065536 = Electric Load Management Enabled
+0131072 = Rear Fog Disabled when Off-Roads Suspension Set (Japan Only)

Click to expand...

http://wiki.ross-tech.com/wiki/index.php/VW_Touareg_(7LA)_Central_Electronics

To come up with the soft coding, you add the numbers to what options or features the module supports. For example:

+0000001 = DRLs always ON, not optional in MFI
+0000002 = Driving Light for USA/Canada (Xenon Low Beams Off when High Beams are On)
+0000064 = Front Fog Lamps Enabled

Soft coding for this list would be 0000067. 1 + 2 + 64 = 67.

Now what if you want to break a soft coding number down? Here is a random Touareg Central Electronics scan I pulled up:

-------------------------------------------------------------------------------
Address 09: Cent. Elect. Labels: 7Lx-937-049-V1.clb
Part No: 7L6 937 049 K
Component: 2703
Coding: 0105695
Shop #: WSC 31414 000 00000
VCID: 448D574504EF3F3EF0B-5072
-------------------------------------------------------------------------------

So what features or functions are enabled to get a soft coding of 0105695? How can I break that down quickly? With Long Coding Helper. The Long Coding Helper file is installed in the same location as the VCDS software, C:\Ross-Tech\VCDS in most cases. Look for the "LCode.exe" file.



Open up Long Coding Helper, and on line 1), type in "+" and the coding value.



Long Coding Helper will show you the binary values that add up to the sum total you type in. So for the soft coding example 0105695 breaks down to:

+0000001 = DRLs always ON, not optional in MFI
+0000002 = Driving Light for USA/Canada (Xenon Low Beams Off when High Beams are On)
+0000004 = Interior Comfort Lighting Enabled
+0000008 = Rain & Light Sensors Enabled
+0000016 = Coming Home Lights Enabled

+0000064 = Front Fog Lamps Enabled
+0000128 = Xenon Lighting Installed/Enabled

+0001024 = Headlight Washers Enabled
+0002048 = Electric Fuel Pump Relay Block (Gasoline Engines Only!)
+0004096 = Wake-up Function (for Air Suspension)


+0032768 = Low-line Seat Heating Enabled (No Memory Seats Only)
+0065536 = Electric Load Management Enabled

Add those numbers up and you get 0105695.

If the Short Coding inserted is uneven number (like 0105695, 7 digits, not 8, 6 or 4), adding a "+" should not be necessary.
And IF a *.sxp should be available, it could be loaded and show that information there is room for.

Hi

How and what software does one use to create a *.sxp file. I have been trying to break down the short coding of the ABS module in the current Tiguan and have managed to isolate some of the values from the 30 plus Tiguan autoscans that I have collected over the past year or so. It would be nice to see them labeled when I enter the data into Longcoder. I have already created some custom xpl and lbl files for the Tiguan from the examples i found within the "labels" folder

Normal text editor, you can copy the explanation as Jeff showed above.
Here is the file: http://www.netech.dk/31/7L-09-07.sxp
I name it as: 7L (Touareg) 09 (Central Electronics) 07 (Coding - Could also be 10 Adaptation).

Ok thanks for that. The below is my first attempt and deciphering the coding of the face lifted Tiguan ABS controller 5N0 614 109

; (5N) Tiguan #3 ABS Module 5N0 614 109
+0000001 = ?
+0000002 = ?
+0000004 = ?
+0000008 = ?
+0000016 = ?
+0000032 = ?
+0000064 = ?
+0000128 = Not logged Yet
+0000256 = Park Assist Fitted/Installed
+0000512 = Not logged Yet
+0001024 = XDS?
+0002048 = RHD Model
+0004096 = Indirect TPMS Module 4C Fitted/Installed
+0008192 = Off Road Mode?
+0016384 = Coasting Function
+0032768 = Blue Motion Stop Start Fitted/Installed

Have no idea what the first 7 values do any suggestions?

Is there a list a list available for the code descriptions?

jasons6930 said:

Is there a list a list available for the code descriptions?

Click to expand...

If you are after a list of descriptions for every possible controller on every possible car then you aren't going to get that because there are ton of them and each has it's own label file. If you take a look in the "C:\Ross-Tech\VCDS\Labels" folder you will see how many files there actually are, each containing a different set of labels for a controller or type of controller. Some of them you can view in notepad because they are just in plain text format, but others are in binary format (probably also encrypted) so you won't be able to see the contents of those.

If you are simply after descriptions for the controllers in your own car then the easiest way to have a record of all the settings is to open the controller screen for each of your controllers and go into the "Coding- 07" screen. Then go into the Long Coding Helper screen (where the option exists to do so) and for each byte take a screenshot and/or document the values in a spreadsheet. This will obviously take some time to do for all the controllers in your car but it's the only real option from a consumer perspective. Getting adaptation descriptions is a bit easier because you can just do an complete dump of the adaptation map values to a CSV file for each of your controllers.

Thanks Gary,

Reason I ask is that for the door controllers we just get a soft code value and not a long coding helper.

With that I used the vcds decode tool but it does not give descriptions.

I'll post up a screen shot later to show you what I mean.

jasons6930 said:

Reason I ask is that for the door controllers we just get a soft code value and not a long coding helper.

With that I used the vcds decode tool but it does not give descriptions.

I'll post up a screen shot later to show you what I mean.

Click to expand...

I think I know what you mean. It's the Recode screen with a short "Software Coding" value on. These don't always have a Coding Helper but if you click on the code a balloon should pop up with the possible available coding options (see screenshots below). If no balloon appears then it means that the coding values are either unknown or undocumented so you are on your own unless you can find someone who has already worked out what some or all of the individual byte values do.

Yes that's the balloon I don't get when I hover in the box.

the decoding tool breaks out all the + numbers but it does not give a description of what the numbers are.

Looks like I might be in my own then.

Jason, let's discuss this in your existing topic - while this here may seem related to your problem, it is not.

http://forums.ross-tech.com/showthread.php?10190-Door-Entry-Exit-Lights

Yes fair enough!

Is there anyway to convert short coding into long coding and vice versa? For instance, a long coded trans module in a 16 Touareg tdi so i can code it to a eurospec trans.

04_sti said:

Is there anyway to convert short coding into long coding and vice versa? For instance, a long coded trans module in a 16 Touareg tdi so i can code it to a eurospec trans.

Click to expand...

A codable module either uses long coding or short coding. Long coding is shown as a sting of bytes in hexadecimal. Short coding is a decimal number. Certainly you could convert hex to decimal or vice versa, but doing so would not change the options that can and can't be changed via coding.

-Uwe-

Uwe,

I guess what I’m after is why can’t I simply covert a known short code that these Aisin trans likes, maybe not this specific trans module, however an earlier module that accepted a known short code, and input that into my trans module after converting it into hex. Does that not make sense or not possible?

Sorry if this is a very basic question for a much more advanced issue, but there are plenty of known module short codes for these earlier year Touareg 3 series, that accepted short coding, whereas the latter models/years now require long coding. Just help me understand please lol

04_sti said:

Sorry if this is a very basic question for a much more advanced issue, but there are plenty of known module short codes for these earlier year Touareg 3 series, that accepted short coding, whereas the latter models/years now require long coding. Just help me understand please lol

Click to expand...

Control modules and the coding schemes they use change over time. Unfortunately, there isn't really anything documented coding-wise for the last generation of T'reg TCUs.

-Uwe-

Uwe said:

Control modules and the coding schemes they use change over time. Unfortunately, there isn't really anything documented coding-wise for the last generation of T'reg TCUs.

-Uwe-

Click to expand...

Anyway I can help change that?

You may need to accept, that the function you're looking for does not exist for your car/tcm. Beyond that, you could always start a topic with your specific request (explaining what you want to achieve and include an actual scan from the vehicle itself, so we can double check if we have some info that just didn't make it into the "public" documentation.

Is it possible to use Lcode stand-alone and read a .clb file? It works just fine in VCDS, but if I use it stand-alone to look up coding options of a module based on a part number, it only shows .lbl files...