General
Each control module
requires a number of software files in order to function. Most of these
are downloaded via VIDA, but in certain cases they are already in the
system.
The files are stored in the Volvo central database and can be ordered via the replacement parts catalogue.
The exceptions are individual configurations which are not in the
replacement part catalogue. These must be ordered using an action code
via the software manager in VIDA. The part numbers are given in the
Technical Journal.
Extended information about files in the control modules
The following is a technical explanation of which files are in the control modules.
The information is not necessary for a mechanic to be able to repair
the car. The information is presented here for those who wish to have a
greater understanding of how the system functions.
The following types of software files are included:
Primary boot loader
Secondary boot loader
Application file
Signal configuration file
Market file (driver information module (DIM) only)
Language file (driver information module (DIM) only)
Car configuration file (central electronic module (CEM) only)
Local configuration file (central electronic module (CEM) and rear electronic module (REM) only).
Most of the control modules
on the controller area network (CAN) can download software via VIDA.
All control modules need an application file and a signal configuration
file to function. Not all control modules receive these two files when
downloading software using VIDA.
In addition most of the control modules require a secondary boot load file to download the software to the control module.
Primary boot loader
The aim of the primary boot loader is to allow the download of software to a control module.
Secondary boot loader
The secondary boot loading file is a collection of instructions which
work together with the primary boot loader to download the software
package into the control module. It then has no other function.
Application file
The application file is the software which contains the control module functions. If software is updated because of quality improvements for example, a new application file is required.
Signal configuration file
All the control modules
on the controller area network (CAN) must have the correct signal
configuration file downloaded to communicate with each other. The file
specifies which signals should be transmitted, where and which signals
should be read, 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 is two S80 model cars. One car is structure week 0135, the
other has a structure week after 0135. The application file for these
cars is the same, however the signal configuration files are different.
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. This is download into
the central electronic module (CEM). This is loaded to indicate to VIDA
that downloading has started. This file loads twice. The file is
downloaded first and last in the download sequence. The first file sets
an error flag and the second file resets the error flag. If the
download is interrupted before the whole package has been downloaded, a
user message is posted indicating that the vehicle is only half loaded.
The car configuration file is also downloaded to the central electronic
module (CEM) to store general information about the car. The file is
also used so that the car can continue in different 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. This information is distributed to the 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 (CEM) reads out instructions
from the car configuration file about how the seatbelt warning should
function. The software sets itself for this function. In this way the
number of variants of the software has decreased by half. In total
there are over 100 parameters stored in the car configuration file.
Each parameter can assume at least two values.
The car configuration file can be read off using VIDA. The file can
contain a lot of information about the car which is useful for the
mechanic such as the VIN, structure week and the configuration of the
car. Structure week and week of manufacture are not necessarily the
same week. Week of manufacture is the week that the car was built in
the factory. The contents of the car are guided by the structure week.
A structure week can stretch over several weeks of manufacture. An
example of this is the new upper electronic module (UEM), which was
introduced for 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 (DIM).
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. A
number of market parameters, such as trip computers and service
reminder indicator (SRI), can also be modified to the customer's
requirements. This is carried out via VIDA vehicle communication.
Other market settings, such as fog lamps, cannot be reset because of legal requirements.
NOTE: Customer parameters are only programmed locally in one control module. Certain parameters have already been reprogrammed at the factory.
