No VIDA Communication with Vehicle – 2003-2019 Volvo

SEOCONTENT-START

VOLVO CAR
SERVICE AND PARTS BUSINESS
Technical Journal
TITLE:
No VIDA communication with vehicle
REF NO:
TJ 34165.1.1
ISSUING DEPARTMENT:
Technical Service
CAR MARKET:
United States and Canada
PARTNER:
3 US 7510 Volvo Car USA
ISSUE DATE:
2019-04-30
STATUS DATE:
2019-05-06
FUNC GROUP:
3975
FUNC DESC:
Mobile data services, general Page 1 of 4
Produced in the USA and available as an electronic document. Hard copy documents are printed in USA on recycled paper containing
a minimum of 50% wastepaper and 10% post-consumer waste.
© 2019 VOLVO CAR USA, LLC
“Right first time in Time”
Attachment
File Name File Size
TJ 34165_2.jpg 0.1261 MB
TJ34165.JPEG 0.1450 MB
Vehicle Type
Type Eng Eng
Desc Sales Body Gear Steer Model Year Plant Chassis range Struc Week
Range
2XX 2016-8999 – 201505-999952
5XX 2019-9999 – 201746-999952
CSC Customer Symptom Codes
Code Description
22 Diagnostic communication/Wired diagnostic connection to vehicle does not work
23 Diagnostic communication/WiFi diagnostic connection to vehicle does not work
24 Diagnostic communication/Remote diagnostic connection to vehicle does not work
VST Operation Number
DTC Diagnostic Trouble Codes
Rows beginning with * are modified
Note! If using a printed copy of this Technical Journal, first check for the latest online version.
Page 2 of 4 2019-05-06
Technical Journal 34165.1.1
Text
DESCRIPTION:
VCM = Vehicle Connectivity Module
OBD = On-Board Diagnostics
DiCE = Diagnostic Communication Equipment
VOE = Vehicle Over Ethernet
CAN = Controller Area Network
This TJ serves as a guide with steps to follow if it is not possible to connect the car to VIDA via OBD
connector with an ethernet cable, please see advice under “Service”.
SERVICE:
Please follow these instructions if there is a problem connecting a car to VIDA:
A. – Refer to SPJ 33451 regarding vehicles not showing up in the Connected Vehicles list. Rule out all
scenarios in this SPJ before proceeding.
B. – Inspect the OBD connector and VOE adapter pins and terminals for any sign of damage. Also
ensure that the terminals on the vehicle’s OBD socket have adequate tension (recommend using terminal
probe kit 9513036).
C. – If the pins are okay, please try to connect with another known working ethernet cable, VOE adapter
and computer.
D. – If it is still not possible to communicate with the car, the VCM may be in a “blocked” mode. Some
VCM’s can be restored with DiCE and VIDA by following the steps below:
1. Connect the car to VIDA using DICE.
2. The DiCE interface LED should be lit up on the unit.
3. If the VIN number is received by VIDA and a connection is established using DiCE, try to reset the
VCM in the Advanced Test menu and toggling Programming Mode On and Off (See attached TJ34165.
JPEG)
4. Disconnect the DiCE and attempt to connect VIDA using the Ethernet/VOE adapter.
5. If communication is still not possible with the Ethernet cable, remove & re-install fuse CF35 OR
perform a battery reset to power-reset the VCM.
6. If there is still no connection between the car and VIDA, try swapping the VCM with a known good
VCM from a donor car to see if communication is possible. It is only necessary to plug in the donor
VCM to the problem vehicle: Do NOT reload the donor VCM.
* – If communication is restored using the donor unit, re-install the original VCM and check for
communication once again. If communication is restored with the original unit, do not replace the VCM
and continue diagnostics with the original unit.
– If communication is restored using the donor unit, and communication is not possible with the original,
the VCM should be replaced according to VIDA instructions.
2019-05-06 Page 3 of 4
Technical Journal 34165.1.1
7. If there is no communication with the swapped VCM, please check the wiring between the OBD
connector and VCM for shorts/opens. (See VIDA wiring diagram for Diagnostic CAN/Diagnostic
Socket, OBD II).
If none of the above steps help to restore communication to the vehicle, please submit a TIE report
according to instructions under Vehicle Report.
VEHICLE REPORT:
Yes, please submit a Vehicle Report if the service solution described in this TJ has no effect. Use
concern area “Vehicle Report” and sub concern area “Support needed”, use function group 3975.
Please attach VIDA Diagnostic logs to the Vehicle Report (see attachment TJ 34165_2.jpg for
description of which files are needed).
To view TJ attachment continue to next page. This TJ has two attachments.
Page 4 of 4 2019-05-06
Technical Journal 34165.1.1

SEOCONTENT-END