(Contents)

Troubleshooting

During use and install (setup) of the UVS-Out interface, you can get messages from Autoline.

What do you want to do?

First Time Using Vehicle Information Interface Parameters

The first time the Vehicle Information Interface Parameters are accessed, it is possible to fill the parameters with default values.

The person who sets up the system is most of the time the user who opens this program the first time.

Below the steps to follow are displayed.

  1. When you select the Vehicle Information Interface Parameters option, a message can be displayed.

    Create file: File 'MB.MS.fdokp' does not exist, would you like to create it?

    To have the defaults automatically filled when creating the file, please click NO and the Error loading parameters message is displayed.

    To have no defaults filled, please click Yes to create the file. Now you need to setup the defaults in the parameters of the UVS-Out interface manually.

  2. The Error loading parameters message is displayed.

    Error loading parameters: Unable to open MB.MS.fdokp

    Click OK to continue.

  3. After clicking OK, the following message is displayed.

    FDOK parameter file not found!: FDOK Settings parameter file is not found, create the parameter file and set to default values?

    Click Create file to continue.

  4. The following message is displayed.

    RETURN to resume: FDOK parameters created, program will be reloaded.

    Click OK to continue.

First Time Using UVS-Out Mappings

The mapping tables are automatically filled, during installation of UVS-Out. This is done by checking the mapping of the relevant information in UVS-In files of Autoline and store the best fit in the UVS-Out files.

Nevertheless, the first time anyone accesses the mapping tables the following message can be displayed.

UVS-Out mapping table not found!: Mapping table not found, create the file?

To fill the mapping tables of UVS-Out automatically with the UVS-In mapping files, please click Create file.

Warning: Be aware to check the UVS-Out mapping tables because these are based on a 1 to 1 match, whereas the UVS-In files are based on an M to 1 match.

NO MAPPING FOUND In UVS-Out Request

When you request vehicle information from UVS-Out, it is possible that not all Vehicle data in UVS-Out is mapped to the concerning data in Autoline.

If an UVS-Out code is found that should be mapped to a valid Autoline-code, //mapping found to is displayed next to the UVS-Out Code and description in the Grid of the Retrieve Vehicle Information form.

If no mapping is found, //NO MAPPING FOUND is displayed next to the UVS-Out Code and description in the Grid of the Retrieve Vehicle Information form.

In case no mapping is found you have to set up the concerning UVS-Out code in the Mapping tables.

The mapping tables contain the mapping from special codes used in the UVS-Out system into the required and valid codes that Autoline is using.

Wrong Chassis Number

A message is displayed when you have selected a vehicle with a non-valid chassis number. The Chassis number must have a minimum of 17 digits.

Wrong chassis number!: The current chassis number is not a valid one for retrieving vehicle information from UVS-Out. A valid chassis number should contain at least 17 characters with alpha and numeric characters.

Click OK to continue and correct the chassis number.

Error UVS-Out

When the requested vehicle information could not be retrieve a message is displayed with the explanation of the failed request.

Error UVS-Out: The requested vehicle information could not be retrieved from UVS-Out. Error message: Message displayed that is given by UVS-Out.

Click OK to continue, analyse and solve the message.