Welcome to the OBD 11 Web page

 

 

Before you start – TAKE A BACKUP

· MK3 Coding Page

· Battery Change

 

OBD 11 Is a bit of software that connects to your VAG car via a specific OBD2 Dongle that allows you subject to setup to make changes to the cars setup, what and how stuff works, record live data and has various Gauges so you can check on specific items whilst the car is working.   For the purpose of this web site I will only show and discuss changes to my 2014 Cupra 280. Any coding shown that you use will be at your own risk.

 

Information:

 

There are currently two separate OBD2 dongles available for OBD11 one is the Legacy one that only supports Android phones, the second will support both Android and IOS and will be expanded to support other makes of cars (Currently BMW).

 

 

Within the application you have the following functions (again we are just talking about the 280 here) for the following control units:

 

01 – Engine Control Module 1 – Live Data here

02 – Transmission Control Module – for the dsg not sure about manual gearbox – Live Data here

03 – Brakes 1 – Live Data here

08 – Air Conditioning – Live Data here

09 – Central Electrics – otherwise called BCM in VCDS world – Live Data here

13 – Adaptive Cruise Control – Live Data here

14 – Wheel Dampening Electronics – Live Data here

15 – Airbag – Live Data here

16 – Steering Column Electronics – Live Data here

17 – Dash Board – Live data here

19 – Gateway – Live data here

32 – Lock Electronics – otherwise known as the front dif – Live Data here

42 – Door Electronics Driver Side – Live Data here

44 – Steering Assistance – Live Data here

52 – Door Electronics Passenger Side – Live Data here

55 – Headlight Regulation – Live Data here

5F – Information Control Unit 1 – Live Data here

76 – Parking Assistance – Live Data here

A5 – Front Sensors Driver Assistance System – Live Data here

A9 – Actuator For Structure Borne Sound – Just turn it off. – Live Data here

 

1/ Ability to scan the car – Running a scan this will identify any issues that the control systems have, some may be shown on your cars screen but many will not.

 

2/ Long coding – for each control unit you have switches that are setup in Long coding and also Adaptions, the screen will show you for each byte a list of the bits and if they are ticked or not. The data is held in hexadecimal format so you can just change the hex code or tick and save the individual bits.

 

3/ Adaptions – As above but these switches allow you to turn stuff on or off or change the way it works.

 

4/ Live data – this can be used in one of two ways, firstly as a simple screen display so that for example you can see the Engine Revs, Car Speed and Intake air temp all together, Secondly you can use the Chart function which allows you to record this data and export it as a .CSV File for further analysis.

 

Thanks to DV52 once again for this following explanation (which made perfect sense to me):

All modern cars can be considered to be nothing more than a number of control systems connected to an engine and a set of wheels (yes this is a gross simplification, I agree!). Most control systems in a car are what's called "closed-loop systems". And ALL these control systems operate the same- they all perform a very basic task: They have an internal process that produces an output signal based on feedback and an input signal(s) - often feedback comes from a sensor/transducer of some sort.

DV52 Picture (thanks)



In all modules that operate control systems (i.e control modules) and regardless of the vehicle, there are really 3 x aspects that are able to be modified:

1/ Firmware
2/ Adaptation channels
3/ long coding

Firmware is like the heart-beat of the module's life-force: this is the internal software that operates the procedures for controlling some aspect(s) of the car. Firmware determines how the module will operate and the module's firmware relies on "inputs" to tell it about the external world: how the car is physically configured and what "parameters" the module is to use in certain circumstances (like how to turn ON/OFF each of the car's 35 x exterior lights). Some diagnostic cables like VCP can change firmware, but not OBD11, or VCDS.

The "inputs" that the firmware relies upon are "2 (Adaption)" and "3 (Long coding)" above. Now, I'm not sure what particular distinction VW officially uses between "adaptation channels" and "long coding", but my guess from observations is as follows:

Long coding are the software switches that tell the firmware what physical sensors/physical switches are installed in the car. For example, when a light-sensor is installed, a long coding Byte/Bit has to be set to tell the control module firmware to start measuring the sensor output and to do stuff to control the car's lighting.
Adaptation channels are generally different sorts of "inputs" that tell the module how-to-behave. For example, Leuchte programming is done by changing adaptation channels - these channels tell the module what function to allocate to each lamp and what level of illumination to give to that lamp.

 

Basic Settings

thanks again to DV52 for definition

Basic settings are just another form of "input" to the closed-loop system. Speaking generally again, the more sophisticated sensors on a car need a initial set of parameters to to establish a reference point. The module's firmware uses this data as a "starting-point" for the feedback process in later operation.

For example, changing some adaptation channel values in the BCM will lose the level-horizon settings for the range-control motors on the headlights. The Basic settings procedure (for the modules @ address hex55) re-establishes the sensor's setting for level-ground. When these modules are taken from stock at the VW factory - each car goes through this basic setting procedure to establish zero degree tilt - as a reference setting. Once the module knows where zero-tilt is, it can accurately measure +ve/-ve angles.

and Readiness

thanks again to DV2 for definition

Readiness is a group of "parameters" (usually 8 x binary Bits) in the engine module which indicate the health of the car's emission systems. A state of 0 means "fail" and 1 means "passed". Whenever you bulk clear DTCs, ALL 8 x bits are set to the "fail" state - if your car doesn't have all 8 x emission test capabilities, those Bits will automatically be reset to 1.

Live Data

As the name implies these are just labels that allow you to watch and record (via charts and online screen) the live data where it is supported on your car

Read more: http://forum.obdeleven.com/thread/3262/control-unit-setup#ixzz5yOwP9qiO For an older version of the data setup

 

How to section.

 

I have moved this information to https://www.vwvortex.com/threads/obd11-hidden-features.9487991/

 

 

Coding

 

MK3 Coding Page

 

 

Warnings

 

Please make sure you run a backup before any changes