System Overview

General







A control module can be reprogrammed in two ways using VADIS. Either by downloading other software or by changing a customer parameter (via vehicle communication).

The customer parameters are functions in certain control modules which can be modified or adjusted to the customer's wishes, for example the temperature of the heated seats or the duration of the interior lighting. It is important to read off the customer parameters before ordering software, these parameters are only stored in the control module and not in the Volvo central database.

Customer parameters are reset to the default value when new software is downloaded and must be reprogrammed after the download.

Reading off and programming the customer parameters is carried out using VADIS vehicle communication.

A fault in the car is normally due to a hardware fault, such as: loose connections, oxidation, open-circuit, short-circuit or other faults that can cause incorrect function.

Software does not wear out. The function of the software does not degrade over time. However an unexpected aspect of the software may occur because of the difficulty of testing all the possible combinations in such a complex system. Software may also be required to be upgraded by statutory requirement or when moving into another market.

It is recommended that VADIS symptom input is used when fault-tracing where suitable tests are suggested, even for faults which do not generate a diagnostic trouble code (DTC).

History







In earlier cars each control module handled a specific function. Cars with a trip computer required an extra control module to run the trip computer functions. If a problem arose in a control module it was replaced, regardless of whether the fault was a hardware or a software fault.

As the number of variants and functions in the car has increased, it became ungainly and uneconomical to have a control module for each function. This required a new type of electrical system. This new electrical system uses distributed functionality, Controller area network (CAN) communication and re-programmable control modules.

Distributed functionality means that a function does not need to be connected to a single control module. A single function can be divided between several different control modules.

An example of this is the lock and alarm on the S80. The lock and alarm system function is distributed between the central electronic module, the upper central electronic module, the driver's information module, driver's door module, passenger door module and the rear electronic module.

The Controller area network (CAN) is a digital high speed network, which allows the control modules in the car to send a large amount of information in an extremely short time.

Re-programmable control modules allow increased functionality programming, without needing to replace the control module. This reduces customer repair costs.

Software downloading has a number of advantages:
- To obtain a new function, for example to add a trip computer to a car without a trip computer a new lever is installed and a new Car configuration file is downloaded into the central electronic module. The control modules in the remainder of the car use the Car configuration file to function in a particular way. The software in the driver information module, for example, reads off whether the trip computer information is to be displayed or not depending on the car's level of equipment
- Fewer control module variants. A good example is the engine control module (ECM). There are 60 different engine variants, which previously required 60 different replacement parts needing to be held in stock. Using software downloads three different hardware types can manage all the variants
- Adapting for the market. The application file for the driver information module can be the same for all markets. However, different market files can be downloaded to distinguish different market requirements
- Language. The language in the combined instrument panel can be changed by downloading different language files to the driver information module
- Makes faster introduction of improved functionality possible
- Time saving when working with a particular type of fault. Previously it was necessary to replace a control module where a software upgrade can now be downloaded instead.

Software







General
Each control module requires a number of software files in order to function. The majority of these are downloaded via VADIS.

The files are stored in the Volvo central database and can be ordered via the replacement parts catalogue. The exceptions are the upgrades which are not included in the replacement part catalogue, which must be ordered using an action code via the software manager in VADIS. The action codes are given in the Technical Journal.

More detailed information about files in the control modules
The following is a technical description of which files are found in the control modules. The information is not absolutely necessary for mechanics to repair the car. The information is presented for those who wish to gain a greater understanding of how the system functions.

The following types of software files are available:
- Primary boot loader
- Secondary boot loader
- Application file
- Signal configuration file
- Market file (driver information module only)
- Language file (driver information module only)
- Car configuration file (central electronic module only)
- Security configuration file (central electronic module only)
- Local configuration file (central electronic module and rear electrical module only).

The control modules on the Controller area network (CAN) can download software via VADIS. The exceptions are the ABS control module and the differential electronic module which do not support software downloading.

All control modules need an Application file and a Signal configuration file to function. However, not all control modules receive these two files when downloading software using VADIS.

The RTI (road traffic information) control module, downloads its application from the RTI (road traffic information) disk and the SRS (supplemental restraint system) control module, has the application file supplied with the hardware.

In addition most of the control modules require a secondary boot load file to download the software to the control module. The climate control module, the central electronic module and the road traffic information (RTI) do not need this file when downloading.

Primary boot loader
The purpose of the primary boot loader is to make it possible to download software to a control module. This is described in Software downloading.

Secondary boot loader
The secondary boot loader is a collection of instructions which work together with the primary boot loader in order to download the software package to the control module. It then has no other function.

Application file
The application file is the software which contains control module functions. Only one new application file is required if a piece of software is updated in order to, for example, improve quality.

Signal configuration file
All the control modules on the Control area network (CAN) must have the correct Signal configuration file downloaded to communicate with each other. The file specifies which signals are to be sent and where and which signals are to be read off and where they can be found. This file ensures that all the control modules speak the same language. This means that an Application file need not be modified if the Controller area network (CAN) environment in the car is modified.

An example of this, two S80's. One with structure week 0135 and one with structure week after 0135. The application file is the same for the two cars, but they have different signal configuration files.

Car configuration file and Security configuration file
The Car configuration file and the Security configuration file are always downloaded to the car when downloading via VADIS. The first file to be downloaded is the Car configuration file to the central electronic module. This is loaded to indicate to VADIS that downloading has started. This file is downloaded twice. This file is downloaded first and last in the download sequence. An error flag is stored the first time and restored the second time. If the download is interrupted before the whole package has been downloaded, a user message is posted saying that the vehicle is only half loaded.

The Car configuration file is also downloaded to the central electronic module to store general information about the car. The file is also used to continue the car in particular modes. The file is generated in the factory just before the car is completed and is delivered by the Volvo central database when the software is ordered. The file is unique. No two cars have the same Car configuration file. This file contains the car's VIN number, structure week and variant information. The information is distributed to other control modules via the Controller area network (CAN).

An example of how the Car configuration file functions can be illustrated through the seat belt warning function. There are two different market requirements for how the seat belt warning should function. The central electronic module reads the instructions from the car configuration file for how the seat belt warning should function. The software is stored for this function. The number of software variants have therefore been reduced by half. In total there are over 100 parameters stored in the car configuration file. Each parameter can accept two values each.

The car configuration file can be read off using VADIS. This file can produce a lot of useful information for the mechanic, such as, the VIN number, structure week, and the configuration of the car. The structure week and the week of manufacture is not necessarily the same week. The week of manufacture is the week in which the car was manufactured in the factory. The content of the car is guided by the structure week A structure week can extend over many manufacture weeks. An example of this is the new upper electronic module, introduced in structure week 0031.

Market, language and local configuration files
The market-, language- and local configuration files are different types of data files which contain parameters which guide the software.

The language file contains information about how the different text messages should be displayed in the text display in the combined instrument panel. There is a Language file for each language. This file downloads to the driver information module.

The Market file contains information about when the service reminder indicator (SRI) should light and all the other market specific settings, such as units in the trip computer and temperature gauges. One section of market parameters, such as the trip computer and service reminder indicator (SRI), can be changed after a request from the customer. Other market settings, such as fog lamps, cannot be changed due to statutory requirements.

Ordering Software







The ordering procedures for software can differ in different markets. This only describes ordering software via VADIS.

Generally software downloading can be separated into two steps. The software must first be ordered and sent from the Volvo central database to the VADIS station. The software must then be downloaded from VADIS to the car.

Each Volvo replacement part has a part number. This also applies to software. Software is listed in the replacement parts catalogue just as other replacement parts are.

Each file in a control module has a Part Number. This Part Number can be read off the car by reading off the control module ID via the VADIS vehicle communication.

NOTE: It cannot be emphasized enough that the Part Numbers are not used in the replacement parts catalogue. These are unique numbers found on every file in the software package. The Part Number is used to determine if a software update has been carried out or not for a specific control module.

It is important to note that the files included in the software package are not a choice made by the mechanic. The content of the software package is decided by the software designer when the system is designed.

Upgrades are not included in the replacement parts catalogue but must be ordered via VADIS - software manager. Also see Action code.
The reason for this is that upgrades must be accessible very quickly. They cannot wait for a replacement parts catalogue to be updated and a new VADIS disc to be distributed.

When ordering the software the mechanic must understand the difference between ordering from a Part Number and ordering from an action code.

When ordering from a Part Number, for example, when reloading, an exact copy of the software stored in the Volvo central database is sent. It does not matter if one or more software updates have been carried out for this software. An exact copy of the car software is sent and downloaded to the car.

After reloading the software, the car will have the same software as before the download. There are certain exceptions.

When ordering from action codes, i.e. when upgrading, the car is updated with new software. As soon as the upgrade has been downloaded into the control module, the Volvo central database is updated with the new configuration.

If a reload is carried out at a later date, the later version of the software is downloaded.

Software is ordered as follows:
The mechanic specifies the software to be ordered and for which car (model and chassis number). This can be done either from the replacement parts catalogue (by Part Number) or via the software manager (by action code).

A message asking whether a control module has been replaced is displayed via a dialog window in VADIS. If the mechanic answers that a control module has been replaced, it is requested to connect VADIS to the car. This is so that the hardware number and the serial number can be read off before ordering software.

If, however, the mechanic answers that the control module has not been replaced, the system assumes that the car and Volvo central database correspond. A verification that confirms that this is the case is made just before downloading. This is described in more detail in Software download operation.

If the verification displays that the car and the database do not correspond, a miss-match occurs. Also see Non matching data.

It is possible to reload the same software package again without making out a new order. By obtaining the same software package that previously failed.

In all cases a check is made in the Volvo central database that the desired software is applicable to the relevant car. If any of the checks are not approved an error message "INVALID" is displayed. The mechanic must deduce what the fault is and reorder the software once the fault has been remedied.

Hint: Help can be accessed by clicking on "Components" to see which type of fault occurs in the relevant software package.

Upgrading using the action code is only applicable for a limited number of VIN numbers. For example, an action code might only function on S80 chassis number 0-29667 (The Volvo central database uses structure week 9815-9849).

In this way it is possible to control which software should be sent to the car. All the parameters available in the Car configuration file can be included as conditions in an action code. In principle an action code can only work in one specific vehicle.

Downloading can start when the software has been supplied to the VADIS station and is accessible.

CAUTION: Software downloading is limited in that only one new control module can be replaced at a time. It is therefore important that only one control module is replaced, and that one reload is carried out for that control module before replacing the next control module. If two control modules are replaced at the same time, an incorrect configuration will be sent to the Volvo central database. The car cannot be reset without help from the helpdesk, which can take several days.