The Volvo Central Database
The Volvo central database
The Volvo central database has records of all the data of all the Volvo cars in the world from the 1999 model year onwards (Not including the S/V40).
There is one server in North America and one in Europe. There is also the main server where all the administrative work is carried out. This is to minimize the load on the other servers where all the software downloads are made. The system used in the Volvo central database is called multi master. This means that all the servers can react as master for reproduction. The updated information is continually copied between the servers.
The VADIS stations where software downloading is possible are connected to the Volvo central database via a local area network (LAN) or modem. If communication can not be established or if communication is broken between one server, there is an automatic connection to the other server, where all the information is kept temporarily.
The Volvo central database is the collective name for a number of different databases (see the illustration above). The databases are:
- The software archive
- The vehicle archive
- The action code database.
SAFE is the interface between VADIS and the databases and handles the file transfer between the databases and VADIS.
The Software archive contains all the software produced by Volvo.
The Vehicle archive contains all the vehicle unique information.
The system holds information about all the Control area network (CAN) control modules (not ABS), such as:
- Hardware numbers
- Software numbers, that is, files which are in each individual control module
- Control module serial numbers
- Vehicle configurations, what equipment a vehicle has, where the vehicle was built, the structure week and the VIN number
- Software ID side impact sensors (SRS (supplemental restraint system))
- PINs.
In addition the PIN codes for every vehicle are stored in the vehicle archive.
There are PIN codes in the following control modules:
- There are three PINs for the central electronic module
- One PIN in the engine control module (ECM)
- In the upper electronic module there or one or two PINs per remote control. On cars before structure week 0031, the PINs consist of 8 characters. On cars after structure week 0031, there are two PINs per remote control. One consists of 8 characters and the other of 16
- A PIN code for the earphone module (only with Volvo On Call function).
The PIN codes are downloaded to VADIS when a control module has been replaced, and a reload has been ordered for the control module via the replacement parts catalogue. The PIN codes are then used by VADIS (unseen by the user) to make the software in the control module function.
When a car is built in the factory the vehicle information is sent to the Vehicle archive where the vehicle configuration is stored. In addition all the vehicle unique PIN codes are sent to the Vehicle archive.
The vehicle database is updated after a download using VADIS. This occurs when a confirmation has been sent to the Volvo central database.
The Database for the action code controls which cars may have a particular type of upgrade. The database contains all action codes. The rules for creating an action code are in the database for action codes. An action code can contain more than 20 version options. The same action code can deliver different software dependent on which car is connected.
Action code
All software components (e.g. stored in the trip computer) have a Part Number and an action code. The action code is a one, two or three digit code which identifies a certain software package.
Any software package for the car can be ordered by using the action code. However, VADIS is configured so that if an action code for reloading is entered from the software manager, the mechanic will be linked to the replacement parts catalogue.
This does not apply to upgrades where these are missing from the replacement parts catalogue. A list containing the upgrade action codes can be found in the Technical Journals.
The following types of action code are available:
- Upgrading
- PIN code
- Reloading
- Complete reloading
- Add or remove functionality.
The upgrade action code is used to replace the software in a control module when there is a complaint and a solution to correct a characteristic. A list containing the upgrade action codes can be found in the Technical Journals.
The PIN type of action code is used to order a specific protected function. These are used for example for the immobilizer function when replacing the engine control module (ECM). Or for remote controls when replacing the upper electronic module.
Reloading type action codes are used when a control module has been replaced.
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.
Complete reloading should be used if a previous download has been interrupted. VADIS recommends a complete reload as part of the process of restoring the car to the download situation. What differentiates this type of action code is that no verification of the software occurs before downloading. The error flag check does not occur during a total reload and therefore a total reload action code is used when others have failed. For a description of error flags, see Software.
The adds or removes function type of action code is used to expand or decrease functionality in the car. This is mainly carried out by modifying the Car configuration file in the central electronic module. Modifying this file results in new functionality for the car. There are certain functions which also require software, such as when adding a control module to the car.
The "remove" function does not actually erase any software. It is a parameter in the Car configuration file which is reset so that the control modules in the Control Area Network (CAN) interpret the function as erased. There is only one occasion on which software is erased and that is immediately before new software is loaded to a control module. This is so that the earlier software does not interfere with the new software.
Non matching data
Occasionally there may be a deviation between the car and the Volvo central database. These deviations can either be an invalid configuration or a miss-match.
An invalid configuration can be caused by the ordered software not corresponding to the car. Or that the cancelled vehicle profile in VADIS and the car do not correspond. In order to avoid many of these problems use the "Obtain VIN" button in VADIS vehicle profile.
A miss-match is when information about the car hardware number, hardware serial number and the software serial number does not correspond to the Volvo central database.
In such a case the car is considered correct and the Volvo central database is updated with the car's hardware, software and serial numbers.
When a control module has been replaced and a reload of the software ordered, VADIS asks if the control module has been added to or replaced.
If the answer is NO a miss-match then occurs. The problem is that the control module may have already been preloaded with software from the supplier. This software might not be correct or does not function fully and will therefore not function when installed in the car.
Yes must be answered if any hardware has been replaced or added to. When one of the options has been selected, VADIS reads out all the hardware numbers and serial numbers of the car. The Volvo central database is updated with these, and the correct software supplied to the VADIS-station.
The importance of marking that the hardware has been replaced in VADIS can be shown using the following example.
The driver's door module has been replaced and is preloaded with software that does not correspond to the car. A miss-match occurs if the hardware is not marked as having been replaced. The Volvo central database will then be updated with the incorrect software. The incorrect software found in the database will be stored if the mechanic attempts to reorder a reload. The damage is already done because the incorrect software is in the Volvo central database. Only the helpdesk can correct the situation by manually updating the Volvo central database.
CAUTION: It is still possible to achieve a data miss-match but that is because the software of another control module does not correspond to the Volvo Central database. The control modules must only be replaced one at a time and reloads must be carried out between replacements.