Values, configuration settings, and other stored information which can be read from the ECU, edited and then rewritten back. Read settings can also be stored as a standard HTML page for reference. These pages can then later be re loaded and re written back to the ECU. Please note that some values may be read only due to the fact that they are supplied from the ECU’s ROM or are internally calculated.
PROGRAMMING RECORDS (Flash type ECUs only)
The ECU has an area of memory allocated for programming history records. Each record, which is a fixed length, contains the VIN number, programming date, assembly number, Homologation number and some unused hexadecimal data. Whenever a new record is added, it is placed after the last record and then becomes the active record which diagnostic equipment such as TestBook reads to obtain information about what an ECU is currently programmed with to see if there are any updates required to be programmed into it. It also uses the absence of any records to indicate a new ECU, which is the only time it allows a vehicle configuration change as from then on it uses the last Assembly number to dictate the maps uses to update the ECU with. It does not appear to verify that the actual maps in the ECU are those indicated by the Assembly number shown in the last / Active programming record, or read previous records. It is not diagnostically possible to erase or modify existing programming records. The space calculates to a possible total of 178 records, however, given that other ECU's such as the Motronic 5.2.1 are limited to only 14 records before the ECU can no longer be updated and must be replaced, which ultimately results in additional ECU sales. It is therefore likely that the ECU may well not accept the programming of all 178 possible spaces.
The page shows a space for a New Record Entry, to be filled in for programming, the Active Record, which is the actually the last record, is then shown under that and is provided here as a duplicate of the last record simply to save having to scroll to the bottom of a possibly long list to get to the last record and the used Programming Records from 1 to the last one used. This page also gives access to the map database by clicking on "MAP DATABASE" button at the bottom of the page.
- VIN number: This is the vehicle's VIN number and it can be programmed only when an ECU is reprogrammed by a Test Book.
- Programming date: This is the date the ECU was programmed.
- Assembly number: This is the Assembly number.
- Homolog. number: This is the recorded emission control test number (Homologation) which is allocated to the ECU configuration / fuel tune map set by the respective authority.
- Unused data: Data that currently has no known usage but as something is required to be supplied when programming a new record; it has to be filled in. We suggest that you use the same data taken from the last programming record, which can be typed in manually or cut and pasted in using CTRL-C and CTRL-V key combinations.
- Database Data: By clicking on this link, it will open a special database that allows you to see and browse all the known Assembly numbers and their respective information about them. The Database will open with the record highlighted for the Assembly number from the active / last programming record For more information on how to use this map database, see Map Database.
READ VEHICLE VARIANT DATA FROM ECU TO FILE
This function is unique to our system and is typically and specifically not provided by most diagnostic equipment developers because it provides capability which conflicts with their other services of selling, on a per ECU basis, customised / updated / enhanced ECU map data. It gives the capability to independently read and save the vehicle configuration map data from any flash programmable type TD5 ECU as standard hexadecimal file. It is strongly recommended to save the original map file before erasing the ECU and reprogramming another map file into an ECU. This can then be reprogrammed into the ECU if you want to return the ECU to the original state. The map file will be saved on your Vehicle Server under an automatically incremental file name that is prefixed TD5V which can be changed later if desired. The file name is shown during the reading process as well as a bar indicator and progress report. The file can be transferred from the server onto your PC with the software module manager. For details of the procedure, see Vehicle Server Software Module Manager.
Important Note: This function is provided for lawful use only, and no responsibility is accepted or assumed by us for the legalities that may be relevant in the usage, re usage or distribution of possibly copyrighted data obtained using this function.
READ VEHICLE FUEL DATA FROM ECU TO FILE
This function is identical to the "Read Vehicle Variant Data from ECU to File" function except it reads the Vehicle Tune data and saves it as a file prefixed with TD5F.
PROGRAM VEHICLE DATA FROM FILES TO ECU
Clicking on this link causes the vehicle explorer to communicate with the Vehicle Server to obtain a list of all of the map files on the vehicle server which can be programmed into the ECU. It will then automatically open a page with three choices:
- ERASE MAP DATA FROM ECU
Before programming the ECU, the existing map data in the ECU must first be erased. Also note that before erasing the maps you need to switch ignition off for 15 seconds then click on ERASE MAP DATA FROM ECU. Although we could have provided an all in one function to erase and then program ECU's like TestBook. The erase function has been provided separately for two reasons. Firstly it allows the user the choice of which of the two map files is programmed first, not that order is important as long as both maps are programmed, but secondly and much more importantly: in the eventuality of a programming error, the ECU's operating system will be only half programmed and the ECU will no longer function or communicate correctly, including the support of many diagnostic functions used and required by all other equipment such as Land Rovers own TestBook. This would normally mean throwing the ECU away and using another new one. However since we specialise in producing equipment which has does not have any limitations incorporated that accidentally or otherwise may lead to additional sales of expensive ECU's, this function uniquely provides the capability to force the erasing of all map data from the ECU regardless of its operational status allowing it to be reprogrammed again. This procedure does not erase the programming history records.
Attention! this procedure erases both vehicle variant and fuel tune maps from the ECU.
- PROGRAM SELECTED MAP TO ECU
In order to program any maps into an ECU, you must first erase the existing variant and fuel tune maps by selecting "ERASE MAP DATA FROM ECU".
Then you must program a valid vehicle Variant Map followed immediately by a fuel tune map without erasing between them. Although any maps can be selected from the list, other than in the pairing shown in the Maps Database. For any given assembly number, it may be that the two maps may be interlinked and will operate correctly in the ECU only as a matching pair or that only certain fuel tune maps will function with a given Vehicle Variant map and vice versa. However, since experimenting by changing the maps does not have to involve using another of the limited amount of programming records; it will be possible to try any number of possibilities. For the extremely adventurous, The maps are stored in a standard hexadecimal format which is not encrypted and so can easily be modified using external programs.
To program a map, select, from the drop down menu, the vehicle variant or fuel tune map that you want to use to program into the ECU and then click on the button itself around the list box. The Vehicle Server will start programming the ECU and give you a status report of progress as it does so. The order of programming either fuel tune or vehicle variant maps first is not important but if either programming cycle is interrupted or is unsuccessful then the ECU will require erasing again before the two maps are reprogrammed. Maps can be copied over onto the server from the PC or previously read and saved ones can be used. The system automatically determines if maps are Vehicle Variant or Fuel Tune and verifies that they are TD5 ECU maps.
- MAP DATABASE
By clicking on this, it opens the Map Database utility. The database contain information about all the known maps. Details about how to use the database you can find residing the "Map Database" chapter.
|
LUCAS TD5 PROGRAMMING (LAND ROVER) - System Overview
LUCAS TD5 PROGRAMMING (LAND ROVER) - Known Fitments
LUCAS TD5 PROGRAMMING (LAND ROVER) - Physical Details
LUCAS TD5 - Pin Outs