Software
Software
General
Each control module requires a number of software files in order to function. The majority of these are downloaded via VIDA. 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 VIDA. 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 VIDA. 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 VIDA.
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 section 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 S80s. 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 VIDA. The first file to be downloaded is the Car configuration file to the central electronic module. This is loaded to indicate to VIDA 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 VIDA. 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.