Internet gateway and firewall
Network
Wired connection
VIDA station
Volvo Cars Access Point
Wi-Fi connected vehicle
DHCP server

Page 12 of 24

2017-10-17

Service Manager Bulletin 00-337
Routed local networks
Infrastructure setups with a routed network or VLAN separation are possible, for example to separate
wired and wireless network traffic in sub networks, or to put vehicles in a separate sub network. The
access points can then be connected to one of the sub networks and the VIDA stations to the other one.
An example of a routed local network is found in the figure below:

Fig. 5 Example of a routed local network
1. Internet
2. Internet gateway and firewall
3. Router
4. VIDA station
5. Sub network 1
6. Sub network 2
7. Wired connection
8. Volvo Cars Access Point
9. Wi-Fi connected vehicle
10. DHCP server
NOTE: If VIDA and vehicles exist in different sub networks, VIDA has to be configured with the
broadcast domain where the vehicles exist. For more information, see chapter 6.1.3 Internal router
firewall ports on page 19.
2017-10-17

Page 13 of 24

Service Manager Bulletin 00-337
5.1.3

Switches and switch ports

The dealership needs to have switches with available Ethernet sockets to plug in the Volvo Cars access
points as well as any networked Ethernet connected vehicle. It is highly recommended for simple
installation and maintenance that the switch features PoE 802.3af standard as the Volvo Cars access
points are powered this way.
The vehicles do not need PoE (and will not be harmed if PoE is unintentionally enabled).
The ports* must be configured as access ports and must be open without authentication.
* Ports to which Volvo Cars Global Wi-Fi service access points are connected must be configured as access ports, i.e. be open without
requiring IEEE 802.1x authentication.

5.1.4

Port performance

Router, switches and network interface cards speed must support at least 100 Mbit/s.
5.1.5

IP address assignment

The Volvo Cars access points, as well as the vehicles connecting to the network through the Volvo Cars
access points, are dependent on IP addresses. These are assigned by DHCP when connecting to the
selected switch ports. Therefore each network segment where these devices are connected shall provide
a DHCP service. The DHCP server must also provide IP addresses to the default-gateway and the DNS
server.
In addition, the DHCP must provide a sufficient range of IP addresses to be used by the vehicles that
connect to the Volvo Cars access points.
Peer-to-peer connected vehicles also need to get IP addresses. These vehicles are assigned IP addresses
through address autoconfiguration (“auto-IP”). For IPv4, the vehicle and computer will get an address in
the 169.254.0.0/24 range. Make sure that any VIDA computer used to connect peer-to-peer to a vehicle
is set such that auto-IP is enabled (i.e. that a static IP address is not set on the Ethernet port.
5.1.6

Other network components

Other network components such as firewalls, routers, switches, proxy servers may exist in the network
as long as the above component and topology requirements are fulfilled. Also make sure that necessary
firewall rules are applied that allows internet and vehicle communication in accordance with chapter
6.1.2 Internal gateway firewall ports on page 18 and chapter 6.1.3 Internal router firewall ports on
page 19.

Page 14 of 24

2017-10-17

Service Manager Bulletin 00-337
5.2

LAN

5.2.1

Ethernet connectivity requirements

VDS protocol-based vehicles can be connected directly to a VIDA workstation with a standard Ethernet
cable using network connectors for a peer-to-peer connection for diagnostics and software download.
The vehicles will also (together with the introduction of wireless access) have the possibility to connect
by Ethernet to the LAN.
In this case the vehicle is connected to a LAN switch, usually by means of a network socket provided for
this purpose. In this connection any VIDA workstation connected to the LAN can reach this vehicle.
Volvo Cars recommends to install dedicated Ethernet sockets at suitable places in the workshop where a
vehicle needs to get wired access to the LAN network.
The following components are required:
Mandatory components
•

VOE (Volvo OBD to Ethernet) adapters, Volvo special tool number 9513108.

Fig. 6 VOE adapter*
* The image is showing a generation 2 adapter. Generation 1 (red and black) (9513062) should no longer be used

•
•

Ethernet network input for each VIDA workstation for peer-to-peer connection. It can either be a PCI
network card or a USB Ethernet adapter.
Ethernet cable type CAT5, CAT5e or CAT6. There is a Volvo special tool available with part number
9513095. This cable tolerates a cold environment.

Fig. 7 Ethernet cable
2017-10-17

Page 15 of 24

Service Manager Bulletin 00-337
Optional components
•
•

An Ethernet cable tester (not a Volvo special tool) is not mandatory but strongly recommended.
USB Ethernet adapters (not a Volvo special tool) for internet connection when a peer-to-peer
connected vehicle occupies the VIDA workstation’s Ethernet port.

NOTE: The connection may differ and depends on the manufacturer of the USB Ethernet adapter.
During development phase, Volvo Cars found the following adapters to be best suited for this task and
are therefore recommended.
D-link 2.0 Fast Ethernet Adapter DUB-E100
Amazon Boom 77HMUO USB 3.0 10/100/1000 Gb
There may be other adapters with similar properties, but since they are not tested by Volvo Cars they are
not recommended.

Fig. 8 USB Ethernet adapter
NOTE: The peer-to-peer option needs to be available and the necessary equipment is always mandatory.
The other two connectivity mechanisms (Wi-Fi and networked Ethernet) require additional equipment
and configuration at the workshop.
5.3

Wi-Fi

5.3.1

Volvo Cars Global Wi-Fi service

The Volvo Cars Global Wi-Fi service is a service developed by Volvo Cars. It provides up to three
wireless networks:
•
•
•

Volvo Cars Diagnostic Wi-Fi (mandatory)
Volvo Cars Guest Wi-Fi (Not available in US / Canada)
Volvo Cars Vehicle Connectivity Wi-Fi (optional)

The vehicle will be manually connected to the Volvo Cars Diagnostic Wi-Fi by conducting a command
on the vehicle’s remote control key. The command is performed by pressing the lock button three times
within three seconds. Once connected, the vehicle will be visible in VIDA and the system will work as if
the vehicle was connected by cable.
The Volvo Cars Guest Wi-Fi is offered to give a harmonized retail experience for Volvo customers
visiting the dealership. (Not Available in US / Canada)

Page 16 of 24

2017-10-17

Service Manager Bulletin 00-337
The Volvo Cars Vehicle Connectivity Wi-Fi will provide access to Internet for the vehicles. The
network can be used for the following:
•
•
•

Demonstration of vehicle connectivity functionality in the showroom
Sales personnel can load apps and other data to vehicles in the showroom
Service technicians can load apps and other data into vehicles in the workshop

For more information about the Volvo Cars Vehicle Connectivity Wi-Fi, see chapter 3.4.2 Alternative 2:
Through workshop internet gateway on page 6.
One of the mandatory components for the Volvo Cars Diagnostic Wi-Fi are the Volvo Cars access points.
VCUSA, along with our vendor Capricorn, will assist the dealership with the actual mounting according
to the agreed floor plan. The Volvo Cars access point controller platform is cloud-based and centrally
configured and managed, also for authentication through RADIUS.
The subscription service will include wireless networks for the vehicles for workshop diagnostic and
software download purposes from VIDA. The SSID for the vehicles
will be broadcasted and named VCCarDW-. A local setup for wireless connections for vehicle
diagnostics is not possible due to security reasons.
For more information about the Volvo Cars Global Wi-Fi service, dealers should contact their national
sales company.

2017-10-17

Page 17 of 24

Service Manager Bulletin 00-337
6 CONFIGURATION SPECIFICATIONS
6.1
6.1.1

Firewall and proxy configuration
Universal Resource Locators and DNS

VIDA will use several URLs - all will be on *.volvocars.biz. Make sure that *.volvocars.biz is not
blocked by a proxy or firewall.
Service
VIDA Prerequisites
VIDA Production
VIDA Admin
TIE
VIDA Services
Volvo Cars password server
VIDA large SWDL

URL
http://vidainstaller.volvocars.biz/client-installer
http://vida-prod.volvocars.biz
http://vidaca.volvocars.biz/AdministrationWeb
https://tie.volvocars.biz
http://vidaresources.volvocars.biz
https://vcamlogin.volvocars.biz
http://swdl.volvocars.biz

Port
80
80
80
443
80
443
80

The Wi-Fi solution requires the ability to open up external URLs by DNS.
6.1.2

Internal gateway firewall ports

Both VIDA workstations and access points will have a gateway IP address configuration to reach the
internet. It is recommended that vehicles connected by Ethernet to the network also have a possible route
to the internet. However, this is not enabled yet.
The access points need to have a direct route through the internet firewall and will not be able to handle
a proxy configuration.
The following outbound ports in an Internet firewall need to be open:
Protocol
TCP
TCP
TCP
TCP
UDP
UDP

Page 18 of 24

Port number
80
443
7734
7752
7351
123

Usage
For VIDA to reach central
systems.
For access points to reach the
cloud controller.

2017-10-17

Service Manager Bulletin 00-337
6.1.3

Internal router firewall ports

For VIDA and the vehicles to be able to communicate over an internal router, any routers used in
the network needs to allow communication on TCP port 13400 and UDP port 13400 as well as
corresponding traffic between the sub networks. These two communication ports are essential in the
communication between VIDA and the vehicles for diagnostic and software download communication.
Especially subnet directed broadcast has to be allowed through routers on TCP port 13400, as this is
the way VIDA discovers vehicles on a different sub network. For best performance, subnet directed
broadcast should also be supported for UDP port 13400.
There are two different methods for VIDA to discover vehicles:
1. Sequential scanning (always works)
2. Directed broadcast (better performance in LANs where routers support subnet directed broadcasts)
The broadcast IP addresses to use for subnet directed broadcast are configured in VIDA Admin. In the
same place in VIDA Admin, the IP addresses for sequential scanning are also configured.
NOTE: For safety reasons, the subnet directed broadcast for DoIP mentioned above must be limited
to the same physical workshop network and not across multiple locations. This way, the risk is limited
that a vehicle is remotely controlled from one location to another, with unpredictable consequences.
Necessary firewall rules or layer 3-based access list must be enabled to block such traffic between
workshops.
NOTE: Many routers have subnet directed broadcast turned off by default, and some cannot even be
turned on.
6.2

NTP sync

It is mandatory to use NTP synchronization for all the network devices and servers.
6.3

Microsoft Windows user account

In order to install VIDA, the user account for Microsoft Windows has to be set to administrator.
NOTE: It is not possible to run VIDA while logged in to the operating system with a guest account. Try
to avoid having a domain policy that will override the normal rights for the supported user accounts.
Some restrictions might make VIDA not work. For example, a user must have right to change the
registry since VIDA requires that when adding a DiCE. It is strongly recommended that all VIDA users
log in as administrators with full admin rights.

2017-10-17

Page 19 of 24

Service Manager Bulletin 00-337
7 VEHICLE COMMUNICATION TOOLS
NOTE: Vehicle communication tools are used to perform diagnostic readouts, diagnostic fault tracing
and software downloads on D2 and GGD protocol-based vehicles. For VDS protocol-based vehicles,
VIDA does not need to be connected to the vehicle through a communication tool.
A vehicle communication tool transfers data from a VIDA workstation to the correct receiver in the
vehicle.
VIDA supports DiCE and J2534 devices. Volvo Car Corporation recommends DiCE for vehicle
communication with D2 and GGD protocol-based vehicles.
7.1

DiCE

DiCE uses a Bluetooth connection to transfer information between VIDA and the vehicle. A USB cable
can be used as an alternative to the Bluetooth connection.
Please note that no third party Bluetooth dongles can be used with DiCE, only Volvo Cars DiCE
equipment can be used.
Multiple DiCEs
You can have more than one DiCE connected to VIDA at the same time. This makes it possible to
download software to more than one vehicle simultaneously.

Page 20 of 24

2017-10-17

Service Manager Bulletin 00-337
8 ABBREVIATIONS
AES-CCMP – AES Counter mode CBC MAC Protocol
CAT – Category (cable)
CAN HS – Controller Area Network High Speed
CAN MS – Controller Area Network Middle Speed
D2 – Volvo Diagnostics II
DHCP – Dynamic Host Configuration Protocol
DiCE – Diagnostic Communication Equipment
DMS – Dealer Management System
DoIP – Diagnostics over IP
GGD – Generic Global Diagnostic Specification
IP – Internet Protocol
LAN – Local Area Network
NAS – Network Attached Storage
NTFS – New Technology File System
NTP – Network Time Protocol
OBD – On Board Diagnosis
PoE – Power over Ethernet
PCI – Peripheral Component Interconnect
RADIUS – Remote Authentication Dial In User Service
RAM – Random Access Memory
SSID – Service Set Identifier
TCP – Transmission Control Protocol
TIE – Technical Information Exchange
UDP – User Datagram Protocol
USB – Universal Serial Bus
URL – Universal Resource Locator
VDS – Volvo Diagnostics and Software download
VLAN – Virtual Local Area Network
WPA – Wi-Fi Protected Access

2017-10-17

Page 21 of 24

Service Manager Bulletin 00-337
9 HISTORY LOG
9.1

320US03

The Android recommendation has been removed.
9.2

320US04

Adjustments and corrections have been made throughout the document.
Obsolete information has been removed.
9.3

320US05

Volvo Cars central Wi-Fi service is now called Volvo Cars Global Wi-Fi service.
Chapter LAN and Wi-Fi requirements has been rewritten.
The SSID for the vehicles has been changed.
The document has been restructured.
9.4

320US06

Clarification has been added for the network traffic between TCP port 13400 and UDP port 13400.
Information added regarding Windows 10 and that it will have full support from 1st of July 2016.
Added a note about a recommended USB Ethernet adapter to chapter Ethernet Connectivity
Requirements.
9.5

320US07

Clarified what a shared drive is.
9.6

320US08

Chapter 3 and 5 have been restructured to make a logical separation between general LAN and WiFi requirements and respective requirements for LAN and Wi-Fi in correlation with the vehicle
communication.
Chapter Alternative 3: Via personal SIM card has been added.
Updates regarding recommended web browser.
Updates regarding recommended processor.
Recommended specification for VIDA used for parts and service information access only has been
removed. All VIDA users are now recommended to use the same specification.
9.7

320US09

Some minor changes regarding bandwidth in the Mandatory specifications for VIDA workstation chapter
have been added.
Page 22 of 24

2017-10-17

Service Manager Bulletin 00-337
9.8

320US10

Added information that the vehicle will be manually connected to the Volvo Cars Diagnostic Wi-Fi.
Updated information regarding requirements and specifications. Also added information regarding
retail infrastructure, e.g. four methods to be implemented and three terms a Volvo Car Dealership must
provide. New information was taken from the Dealer Development Platform (DDP).
Erased information regarding Windows 8.
Added information that support for Windows 7 will end 2019-01-01.
The term Menu Pricing was changed to Operations and Packages
Rebuilt and clarified chapter 5.3.1 regarding Volvo Cars Global Wi-Fi Service. Rebuilt and clarified
chapter 6.1.3 regarding Internal router firewall ports.
Minor grammatical changes were carried out throughout the text.

2017-10-17

Page 23 of 24

Service Manager Bulletin 00-337
10 INDEX
A

N

Abbreviations....................................................21
Access points....................................................11
Adobe Acrobat Reader......................................10

Network storage..................................................9
NTP synchronization.........................................19

C

Operations and Packages..................................10

Cable type, Ethernet..........................................15
Connection types.................................................4
Connection types for VDS protocol-based
vehicles...............................................................4
Connectivity scenarios........................................4

O

S
Screen resolution.................................................9
Software download requirements.......................8
T

D

TIE....................................................................10

D2 and GGD protocol.........................................3
Dealer Management System.............................10
DHCP server.....................................................11
Diagnostic requirements.....................................8
DiCE.................................................................20
Display resolution...............................................9
DMS..................................................................10

U

E
Ethernet requirements.......................................15
I
Installer package.................................................8
Internet................................................................9
IsoView.............................................................10

Universal Resource Locators............................18
URLs.................................................................18
V
VDS protocol......................................................3
VDS protocol-based vehicles..............................4
Vehicle communication tools............................20
VIDA Admin.....................................................10
Volvo Cars Global Wi-Fi service......................16
W
Windows user account......................................19
Windows version.................................................9
Workstation requirements...................................8

M
Mandatory infrastructure components................9
Mobile internet....................................................9

Page 24 of 24

2017-10-17