Hardware Management

This chapter contains information on how to install, set-up and manage communication unit hardware like VOCOM.

Safe handling of USB cable

Always release the USB cable from the VOCOM unit when it is not used.

Never store the cable by twisting it around the VOCOM unit.

../images/T0137486.jpg

The recommended minimum bending radius of the cable is about 6 cm. (See comparison with a CD).

../images/T0137487.jpg

VOCOM I

Connecting VOCOM I

Get started by starting up the laptop and put vehicle ignition ON.

Check if correct cables are used. The different product classes use different interfaces and adapter cables to connect. The tables below show what interface and corresponding adapter cables to connect to different product classes.

Note: The tables may not be applicable to all markets.

Model / Interface 88890300 88890020

FH(4) - FM(4) / FL(3) - FE(3)

88890253

88890026

FH – FM

88890306

88890027

FL - FE

88890253

88890026

PC => Interface

88890313

No Volvo spare part


Model / Interface 88890300 8889020

Direct Programming cable

88890306 (FCI cable)

88890027

VMAC I,II,III / VE98 (6pin)

88890302 (88890315) + 88890257 (9pin to 6pin adapter)

88890034 + 88890257 (9pin to 6pin adapter)

US04 to US10 (9pin)

88890302 > 88890315

88890034

US10 + OBD2013 and newer

88890253

88890026

USB cable

88890313

Generic USB cable


Installing VOCOM I

This is how it should appear the first time you connect the communication unit to a computer.

The pictures in the installation instruction serves as illustrations, the actual dialogues and pop-ups may look different depending on which communication unit and Windows you are using.

A small window in the lower right corner will state Installing device driver software.

../images/T0093324.jpg

After a while, a small pop-up appears in the lower right corner and states that new hardware has been installed and is ready to use.

../images/T0094165.jpg

LEDs description

The communication unit has a number of different coloured LEDs. These LEDs show the status of the communication unit and indicate warnings, etc. Refer to the table below for an overview.

../images/T9079048.jpg

LED Icon Description

Green

../images/T0093271.jpg

The communication unit receives power via the USB port. The LED flashes during communication. If this LED and the red Critical Error flash, the internal software is faulty or is missing completely. Call your helpdesk for assistance.

Green

../images/T0093272.jpg

The communication unit receives power via the product cable.

Blue

../images/T0093273.jpg

WLAN active. The LED shows the strength of the radio traffic. The various strengths are indicated by the LEDs illumination ratio between ON and OFF. The more frequently the LED illuminates, the better the radio traffic.

Yellow

../images/T0093275.jpg

The LED illuminates when SmartCable is connected.

Yellow

../images/T0093274.jpg

This could depend on two occurrences:

  • An error has been detected in the communication unit. See Fault code description on how to read the information. Connect the USB cable between the computer and the communication unit before reading. These errors are not critical.
  • The communication unit is outside the approved temperature range, -40°C (-40°F) to +85°C (+185°F). Warm or cool the unit by placing it in a room at normal temperature.

    Note: If the unit is equipped with a WLAN function, the temperature range is 0°C (32°F) to +45°C (113°F). When the USB cable is connected, WLAN is disconnected and -40°C (-40°F) to +85°C (+185°F) applies instead.

Red

../images/T0093276.jpg

A critical error has been detected in the communication unit. Perform the following actions:

  1. See Fault code description on how to read out the information. Connect the USB cable between the computer and the communication unit before reading.
  2. Contact your helpdesk for assistance.
  3. If the communication unit must be replaced, use the normal accessory warranty if the unit is less than 12 months old.

If this LED and the green Power USB / Communication flash, the internal software is faulty or is missing completely. Call your helpdesk for assistance.


LED Text on label Description

Green

Power USB / Communication

The communication unit receives power via the USB port. The LED flashes during communication. If this LED and the red Critical Error flash, the internal software is faulty or is missing completely. Call your helpdesk for assistance.

Green

Power Product

The communication unit receives power via the product cable.

Blue

WLAN

WLAN active. The LED shows the strength of the radio traffic. The various strengths are indicated by the LEDs illumination ratio between ON and OFF. The more frequently the LED illuminates, the better the radio traffic.

Yellow

Error Warning

An error has been detected in the communication unit. See Fault code description on how to read the information. Connect the USB cable between the computer and the communication unit before reading. These errors are not critical.

Yellow

Temperature Warning

The communication unit is outside the approved temperature range, -40°C (-40°F) to +85°C (+185°F). Warm or cool the unit by placing it in a room at normal temperature.

Note: If the unit is equipped with a WLAN function, the temperature range is 0°C (32°F) to +45°C (113°F). When the USB cable is connected, WLAN is disconnected and -40°C (-40°F) to +85°C (+185°F) applies instead.

Red

Critical Error

A critical error has been detected in the communication unit. Perform the following actions:

  1. See Fault code description on how to read out the information. Connect the USB cable between the computer and the communication unit before reading.
  2. Contact your helpdesk for assistance.
  3. If the communication unit must be replaced, use the normal accessory warranty if the unit is less than 12 months old.

If this LED and the green Power USB / Communication flash, the internal software is faulty or is missing completely. Call your helpdesk for assistance.


Note: All LEDs light up during startup of the communication unit. This is to check that all the LEDs function.

Communication unit monitor

Communication Unit Monitor is an application that checks if the software and driver of the communication unit matches.

Icon Communication unit monitor status in taskbar
../images/T0034796.jpg

Displayed when Communication Unit Monitor is active.

../images/T0034797.jpg

Displayed when the software in the communication unit has to be updated.


When connecting a communication unit the Communication Unit Monitor checks if the software in the communication unit and the driver are compatible. If they are incompatible a message will be shown informing that the software has to be updated.

../images/T0034798.jpg

Fault tracing

Connection fault diagnosis

  1. Make sure the product is keyed on (check the instrument cluster to make sure that the battery voltage is ok).
  2. Check the vehicle cable (make sure none of the PINs are bent).
  3. Check that the communication unit is working properly (please see the documentation of the communication unit). For VOCOM users (see LEDs description):
    • Check that all the LED’s light up shortly when powering up the unit.
    • When connected only to the USB: The unit should flash the LED’s, and then light the "Power USB/ Communication"-LED.
    • When connected only to the vehicle: The unit should flash the LED’s, and then light the "Power Vehicle"-LED.
    • If the “Critical Error”-LED lit, make sure the latest version of Tech Tool is installed.
    • If the “Error”-LED is lit, read the description of the fault and take the necessary actions.
  4. Try with a different vehicle cable.
  5. Try with a different USB cable.
  6. Try with another communication unit or another PC.
  7. If using WLAN, check that the WLAN is working properly. Consult your local IT support for advanced checking of WLAN and read instructions in Tech Tool (see WLAN Mode).
  8. If none of the above solves the problem, contact support.

Known problems

The following problems can occasionally occur when using communication unit 88890020:

  • Powering up — Communication unit is not powering up when it is connected only to the computer. Some computers have problem to power supply the communication unit via USB. This problem is related to the 4 m long USB cable which may cause the voltage to drop. To solve this problem please connect product cable to power supply the communication unit. If that does not work, open the Device Manager (Control Panel/Administrative Tools/Computer Management/Device Manager) to see if there is an exclamation mark in front of the communication unit. Right click the communication unit and select Update Driver.
../images/T0093269.jpg

Fault code description

The fault codes for the communication unit are found in the Status dialogue. You find the Status option when you have chosen Configuration of a communication unit through the Settings dialogue. For more information see Settings. The table below lists the fault codes, their cause and corrective actions to solve them.

Error code Cause Action

1

Fault in application flash-memory

Send the communication unit for repair.

2

Fault in boot program flash-memory

Send the communication unit for repair.

3

Fault in parameter flash-memory

Send the communication unit for repair.

4

Parameter flash-memory worn out

Send the communication unit for repair.

5

Internal RAM error

Send the communication unit for repair.

6

External RAM error

Send the communication unit for repair.

7

A fault occurs when accessing to the USB chip.

Send the communication unit for repair.

8

A fault occurs when accessing to the temperature sensor.

Send the communication unit for repair.

9

The serial SDIO bus cannot be accessed.

Send the communication unit for repair.

10

The serial SPI bus cannot be accessed.

Send the communication unit for repair.

11

There is a fault in the CPU.

Send the communication unit for repair.

12–19

There is a hardware fault.

Send the communication unit for repair.

20

A power fault has been detected by the communication unit.

Check the communication unit power supply first. If the power supply is OK, send the communication unit for repair.

21

Supply voltage is too low.

Check the voltage to the communication unit.

22

Supply voltage is too high.

Check the voltage to the communication unit.

23

The temperature is too low.

Warm up the communication unit and try again.

24–25

The temperature is too high.

Let the communication unit cool down and try again.

26–29

There is a fault in the environment around the communication unit.

Contact helpdesk for additional information.

30

There is no USB power supply.

Check the USB cable. If it is OK, send the communication unit for repair.

31

Power surge on USB-port #1

The USB unit on port 1 is consuming too much power and has been turned off.

32

Power surge on USB-port #2

The USB unit on port 2 is consuming too much power and has been turned off.

33

An unsupported USB unit on port #1

The USB unit on port 1 is not supported by this software. Change the software or acquire a supported unit.

34

An unsupported USB unit on port #2

The USB unit on port 2 is not supported by this software. Change the software or acquire a supported unit.

35–39

There is a fault with the USB connections.

Contact helpdesk for additional information.

40

SD card not supported

Change SD card.

41

Fault when accessing SD card

A fault occurred when reading or writing to the SD card. Change SD card.

42

SD card FULL

Empty the SD card or replace with another card.

43–49

There is a fault with the SD card.

Contact helpdesk for additional information.

50

There is no WLAN card.

Send the communication unit for repair.

51

The WLAN card is not functioning correctly.

Send the communication unit for repair.

52

No access points accessible

Move the communication unit to position with better reception.

53

WLAN signal strength too low

Move the communication unit to position with better reception.

54

The WLAN manager has detected a fault.

Restart the communication unit.

55

A fault was detected during network verification.

Check the configuration and make sure that the network has the correct parameter settings.

56–59

The WLAN manager has detected a fault

Contact helpdesk for additional information.

60

A fault occurred during the verification process.

Check the verification method and the security keys in question.

61

A fault occurred during the encryption process.

Check the encryption method and the security keys in question.

62–65

A fault occurred in security management.

Contact helpdesk for additional information.

66

A fault occurs when accessing to the TCP/IP port.

The port may already be open for transfer. Restart the communication unit.

67

The is a TCP/IP conflict in the network.

Change TCP/IP number to avoid this problem.

68

A time-out occurred while waiting for a TCP/IP packet.

Communication broken. This fault code is only intended for fault tracing. Continue using the communication unit as usual.

69

A fault is reported from the TCP/IP stack.

Restart the communication unit.

70–75

There is a fault related to the TCP/IP stack.

Contact helpdesk for additional information.

76

A fault has occurred in the SAE J1708 communication.

Check the network for short-circuits. If there are none, change the communication unit.

77

A fault has occurred in the ISO 9141 communication.

Check the network for short-circuits. If there are none, change the communication unit.

78

A fault has occurred in the ISO 9141 5 volt communication.

Check the network for short-circuits. If there are none, change the communication unit.

79

A fault has occurred in the CAN communication.

Check the network for short-circuits. If there are none, change the communication unit.

80

Wrong logon ID

Wrong logon ID given at start of communication.

81–89

There is a general fault.

Contact helpdesk for additional information.


VOCOM II

VOCOM II Hardware

../images/T0123698.jpg

Installing VOCOM II

Connect the VOCOM II device to the USB port of the PC. The device is ready to communicate when the PC communication status LED is lighting green.

When connecting a new VOCOM II device for the first time the Windows device driver setup will run:

../images/T0123700.jpg

Note: When connecting a VOCOM II device for the first time, the device installation could take several minutes due to the Windows specific “driver installation” feature.

During the device driver installation you will see a corresponding task bar notification. If the device driver installation has been successfully completed, a task bar notification will be shown:

../images/T0123701.jpg

../images/T0123699.jpg

If for some reason the device driver fails to install, try again by disconnecting VOCOM II from the USB port and connecting it to a different USB port or by restarting the computer.

Note: For proper operation of the VOCOM II hardware the following firewall rules have to be set up. For the standard Windows firewall the VOCOM II Windows installer will add these rules automatically during the installation process.

Rule Settings
VOCOM II CAST
  • Direction: inbound
  • Protocol: UDP
  • Port: 427
VOCOM II HTTP
  • Direction: outbound
  • Protocol: TCP
  • Port: 80
VOCOM II RP1210
  • Direction: outbound
  • Protocol: TCP
  • Port: 27015
VOCOM II J2534
  • Direction: outbound
  • Protocol: TCP
  • Port: 2534
IPv6 Enabled

VOCOM II Config Application

The Config Application provides all features necessary to configure and update VOCOM II devices.

The VOCOM II Config Application is started from Settings >Communication unit tab > Configuration. Or from the Windows Start menu: Start > All Programs > VOCOM II Configuration Application

You can access Settings from the Tech Tool menu or from the shortcut in the Tech Tool tool bar in the Product tab.

For each available VOCOM II device there is a single device list containing information regarding:

  • Product Variant
  • Serial Number
  • Device Name
  • Connection Type (USB: Wire symbol, WLAN: Radio symbol)
  • Paring status
  • Device status
  • Software Update status
../images/T0137623.jpg

Each VOCOM II device available will be listed on the Device Listing that is always visible at the left side of the application.

Note: This is the default tab when opening the application or when selecting another device in the list.

Note: The devices list is continuously updated and will update the connection type as they change or show new devices as they become available.

Firmware Update

Firmware is automatically updated when the device is connected via USB. A message in the tool bar will let you know when a firmware update is being done.

Note: Do not disconnect the VOOCOM II during a firmware update.

Basic VOCOM II Setup

Note: Please make sure that the VOCOM II is connected via USB and ready to operate.

Open the VOCOM II Config Application and perform the basic device setup. The basic VOCOM II device setup involves the following steps:

  • Device name assignment
  • Device ID mapping for RP1210 (optional)
  • Pairing the device with the local host PC

Device Name

It is possible to give a custom name to each device in order to facilitate its identification.

By default the Device Name is set to Vocom2-[serial number], e.g. Vocom2–12345678.

To change the Device name you need to:

  1. Click on Edit button.
    ../images/T0139364.jpg

  2. Enter the desired Device Name.
    ../images/T0139365.jpg

  3. Click on Save button.
    ../images/T0139366.jpg

Note: The Device name will be displayed in the Device Listing.

DeviceID Mapping for RP1210

The RP1210 Device Mapping is optional. The assignment of an RP1210 DeviceID to a connected VOCOM II device is accomplished as follows:

  1. Open the Mapping page and select a connected VOCOM II device.
  2. By default the first USB-connected VOCOM II device is assigned DeviceID 1, and the first WLAN connected VOCOM II device is assigned DeviceID 2. DeviceIDs 3 to 8 are initially unassigned.
  3. After initial mapping has been done, you can use DeviceID 2 in RP1210_ClientConnect to open a diagnostic connection to this device when it is connected to the host PC via WLAN.
  4. If you change the Mode parameter of this mapping to “Any” you can also connect to this device (via DeviceID 2) when it is connected via USB.

After changing the Device Mapping table, click on Save and then on Close. No Restart is necessary.

Tech Tool users do not need to change anything in DeviceID Mapping. Tech Tool always uses DeviceID 1.

Pairing the device with the local host PC

In order perform RP1210-based diagnostic communication and software updates over WLAN, the corresponding VOCOM II device has to be paired with the host PC.

Note: (Re-) Pairing is only possible for USB-connected VOCOM II devices.

  1. Click on the Edit button.
    ../images/T0139364.jpg

  2. Click on the Pair button.
    ../images/T0139367.jpg

  3. Enter your computer name (Client Name). By default your Windows computer name is used
    ../images/T0124144.jpg

Note: The current paired computer is always displayed in the black status bar in the Client ID field.

Device Error List

The device error codes can be seen on the Status tab.

../images/T0139363.jpg

WLAN Setup

Note: Please make sure that the VOCOM II is connected via USB and is ready to operate.

Open the VOCOM II Config Application and perform the WLAN configuration. To open the WLAN configuration page of a particular device you have to perform the following steps:

  • Open the Available Devices list in VOCOM II Config Application.
  • Select the VOCOM II device you want to configure for WLAN operation.
  • In the Device Context page click Connection.
  • The WLAN Configuration page will be shown:
    • The WLAN Infrastructure Mode is normally used in a workshop environment where there is already an existing infrastructure network.
    • The WLAN Direct mode is used when the laptop needs to be directly connected to a VOCOM II device via WLAN, e.g. when using it in the field without the existence of a infrastructure network.

      Note: WiFi-Direct is a feature for other client platforms (e.g. Android) and should not be used on Windows platforms since it is not properly supported yet.


      ../images/T0139368.jpg

Note: WLAN configuration changes will only take place after restarting the device.

After configuring the VOCOM II WLAN interface and restarting the device, unplug the USB cable. Make sure the VOCOM II is powered from ECTA/OBD connector.

  • The VBAT indicator (battery symbol) should be lighting green.
  • The WLAN indicator (antenna symbol) should be lighting blue.
  • The WLAN signal strength indicators (LED bar) should be lighting.

When the WLAN connection has been successfully established, then the WLAN signal strength is indicated by the 4 LED bars.

WLAN RX/TX activity is indicated by flashing WLAN- and PC-Comm status indicators.

WLAN Infrastructure Mode

In VOCOM II Config Application’s WLAN Configuration page select Infrastructure and click the Network Settings drop down box. The current WLAN Infrastructure settings will be shown.

Enter the name of your WLAN network (i.e. the SSID of the existing network) into the Network Name / SSID field of the WLAN Infrastructure Configuration page.

From Encryption and Authentication menus select a combination of Encryption-methods and WLAN-Authentication methods which is supported by your network.

The default setting is WPA+WPA2 / WPA-PSK for password based authentication and encryption, which is normally used for small “personal” wireless networks. This WLAN Infrastructure Mode is commonly called “WPA-Personal”.

Other available/configurable authentication/encryption methods for WLAN Infrastructure Mode are EAP-TLS and EAP-PEAP, providing certificate based authentication through central servers, which is normally the case for larger company networks. These infrastructure modes are commonly called “WPA Enterprise”.

Network Settings for WPA-PSK

For WPA-Personal mode the following network parameter have to be set.

Network name / SSID

The name (SSID) of the network

Encryption

Should be set to WPA + WPA2

Authentication

Must be set to WPA-PSK

Password

The network password (pre-shared key)


Network Settings for EAP-TLS / EAP-PEAP

For WPA-Enterprise mode the following network parameter have to be set.

Network name / SSID

The name (SSID) of the network

Encryption

Should be set to WPA + WPA2

Authentication

Must be set to either EAP-TLS or EAP-PEAP. If necessary, ask your network administrator which authentication type is supported by your network

Certificate file

Encrypted client certificate in PKCS12 format

Certificate password

Password for decrypting the client certificate, if certificate password is required

User name

User / identity for which the certificate has been issued


Note: For EAP-TLS configuration, the Password field of the Network Settings page must be empty.

In order to upload and install the selected client certificate on the VOCOM II (which needs this certificate for later authentication on the network’s Radius server), click Certificate/Install button.

After successful upload and installation of a certificate on the VOCOM II, the currently installed client certificate will be listed in the Network Settings page.

IP Address Settings

Clicking the IP settings drop down bar from in WLAN Infrastructure settings displays the IPv4 and IPv6 address assignment configuration parameters for the VOCOM II WLAN interface for Infrastructure Mode operation.

DHCP is the default IPv4 and IPv6 address assignment method in WLAN Infrastructure mode.

Note: Your network router has to support DHCP in this case.

  • A static IPv4 and/or IPv6 address assignment can be configured by selecting Use IP address from IPv4 protocol and/or IPv6 protocol drop down bar.
  • The Gateway field is optional and can be left empty. The Gateway field will be usually set to the IP address or DNS of the network router.
  • The Nameserver field is optional and can be left empty. The Nameserver field is necessary when a DNS name is used for the Gateway. It is also used in connection with VG Wireless Mode setup.

In the case of IPv4 protocol there is a third IP address assignment option: APIPA (Automatic Private IP Addressing).

In this case, the VOCOM II WLAN interface will be assigned a link-local IPv4 address from (reserved) address range 169.254.x.x.

The APIPA-based IP address assignment should be used for WLAN Infrastructure Mode when your network router does not support DHCP and you do not want to assign a static IPv4 address.

Note: After changing the WLAN settings, click Save and then Restart in order to set the new WLAN configuration on the VOCOM II device and to re-start the WLAN interface with the new settings.

WLAN Direct Mode

When VOCOM II is in WLAN Direct Mode the VOCOM II creates its own wireless network that you can use to connect your PC.

Note: Direct mode is only supported for the 2.4 GHz band.

In order to configure the VOCOM II WLAN interface for Direct mode operation you have to perform the following steps:

  1. Make sure the VOCOM II device is connected via USB.
  2. Select the VOCOM II device from the Available Devices list.
  3. Open the Connection settings and select WLAN — Direct mode.

For WLAN Direct mode the following parameters have to be set:

Network settings

SSID

A user configurable name for the VOCOM II network to be created. This is the name the computer will see as the network name when searching for a network to connect to.

Broadcast SSID

Enable/Disable SSID broadcast, if disabled the network will not be discoverable by the computer, the SSID name will then need to be manually entered.

Channel

2.4 GHz WLAN channel to be used

Clients

Opt. parameter, max. number of clients, 0 means: unlimited

Password

A user configurable password for the VOCOM II created network. This password should be used when connecting your PC to the VOCOM II created network.

IP Settings

IPv4 and/or IPv6 network configuration

Note: After changing the WLAN settings, click Save and then Restart in order to set the new WLAN configuration on the VOCOM II device and to re-start the WLAN interface with the new settings.

Using both VOCOM I and VOCOM II

In order to use VOCOM I and VOCOM II it is necessary to have the desired driver correctly selected in TT Settings:

../images/T0139369.jpg

Note: For USB usage, no configuration is needed besides having the correct driver selected.

For WLAN usage further configuration is required both for VOCOM I or VOCOM II devices.

VOCOM I WLAN configuration is made inside Tech Tool. See WLAN Mode chapter. When more than one VOCOM I device is configured for WLAN, it is also required to have the correct device selected in order to inform the application to which device it shall connect to.

VOCOM II WLAN configuration is made outside Tech Tool using VOCOM II Configuration Application. See WLAN Setup chapter. When more than one VOCOM II device is configured for WLAN, it is also required to have the correct device selected in order to inform the application to which device it shall connect to.