8.
Troubleshooting
This section is intended to help you get back on track if
the VCI appears to be operating abnormally. In addition,
the most likely cause for the condition is given as well
as other possible causes and recommendations on how
to isolate or eliminate the problem.
8.1
VCI Does Not Pass Power On Self-
Test (POST)
Most Likely Cause:
R
Internal problem in the VCI.
Recommendations:
R
Connect the VCI to a PC using USB and perform the
recovery procedure.
8.2
VCI Error LED Lights After Power On
Most Likely Cause:
R
A problem has been detected during power on.
Recommendations:
R
Power down the VCI and verify that it has the same
problem when you power up again.
R
Connect the VCI to a PC using USB and perform the
recovery procedure.
8.4
VCI Fails to Power Up
The VCI should power up as soon as external power is
applied. If the VCI does not turn on, first check the wall
plug or power cable connections. Try supplying power to
the VCI from different power sources— the vehicle DLC
connector, USB, or the optional AC/DC 12-volt adapter.
Recommendations:
R
Check that the cables are securely attached to the
VCI and the connector pins are clean.
R
If connecting to the vehicle DLC connector, try pow-
ering via USB.
R
If connecting to the optional AC/DC 12-volt adapter,
try powering from the vehicle DLC connector.
R
Verify power at the DLC connector and the optional
AC/DC 12-volt adapter.
8.5
VCI Turns Off Immediately When Dis-
connected from the Vehicle
The VCI should stay on for a factory set time if power is
lost during engine cranking or after it is disconnected from
power (vehicle DLC or AC/DC 12-volt power adapter).
Recommendations:
R
Power up the VCI and verify that it has the same
problem when power is removed.
Robert Bosch GmbH
8.3
VCI Manager Software on the PC Un-
able to Communicate with the VCI
VCI Manager software must be installed on the PC, and
the VCI must be powered up before it will communicate
using USB. The VCI must also be configured for wireless
communication before it will communicate with your
wireless network. The VCI connects first using USB, if
available; if USB is not available, the VCI connects using
wireless.
Recommendations:
R
Check that the cables are securely attached to the
VCI, the VCI has completed its power up sequence,
the connector pins are clean, and the VCI Manager
software is running.
R
If connecting using USB, check that the VCI USB
connection is detected by Windows:
$
Connect the VCI to the PC USB port, then power
up the VCI.
$
From the Windows Control Panel, open the Net-
work and Dial-up Connections window.
$
Check for device name "ETAS USB Remote NDIS
Network Device". If not running, then either the
USB driver has not been loaded on the PC or the
VCI is not powered and connected to the USB.
Check all USB ports on the PC and verify that the
VCI is powered on.
R
If connecting using wireless Ethernet, make sure
that wireless communication is enabled and the IP
configuration is properly set using the VCI Manager
software:
$
Check that the USB cable is not plugged in. USB
connection takes precedence over wireless.
$
Check that the wireless card is properly seated in
the VCI.
$
Contact your IT department and check that your
PC is detecting the wireless access point, and
the correct security settings have been configu-
red for the VCI.
R
Contact your IT department for the correct VCI
settings.
R
If the VCI Manager is still not able to communicate
with the VCI, perform the Recovery Procedure.
| MTS 6516 VCI | 29
en
|
1699200075 B
2017-06-20