Vector InformatikGmbH
Ingersheimer Straße 24
D-70499 Stuttgart
The information and data given in this user manual can be changed without prior notice. No part of this manual may be reproduced in any
form or by any means without the written permission of the publisher, regardless of which method or which instruments, electronic or
mechanical, are used. Alltechnicalinformation, drafts, etc. are liable to law of copyright pr otection.
In this chapter you find the following information:
1.1 About this User Manual9
1.1.1 Warranty10
1.1.2 Registered Trademarks10
1.2 Important Notes11
1.2.1 Safety Instructions and Hazard Warnings11
1.2.2 Disclaimer12
1.2.3 Licenses12
VN5000 ManualVersion 2.58
1 Introduction
1.1About this User Manual
ConventionsIn the two following charts you will find the conventions used in the user manual
regarding utilized spellings and symbols.
StyleUtilization
boldBlocks, surface elements, window- and dialog names of the soft-
ware. Accentuation of warnings and advices.
[OK]
File|Save
Source Code
HyperlinkHyperlinks and references.
<CTRL>+<S>Notation for shortcuts.
SymbolUtilization
File name and source code.
This symbol calls your attention to warnings.
Push buttons in brackets
Notation for menus and menu entries
Here you can obtain supplemental information.
Here you can find additional information.
Here is an example that has been prepared for you.
Step-by-step instructions provide assistance at these points.
Instructions on editing files are found at these points.
This symbol warns you not to edit the specified file.
VN5000 ManualVersion 2.59
1.1.1 Warranty
1 Introduction
Restriction
of warranty
We reserve the right to change the contents of the documentation and the software
without notice. Vector Informatik GmbH assumes no liability for correct contents or
damages which are resulted from the usage of the documentation. We are grateful for
references to mistakes or for suggestions for improvement to be able to offer you
even more efficient products in the future.
1.1.2 Registered Trademarks
Registered
trademarks
All trademarks mentioned in this documentation and if necessary third party
registered are absolutely subject to the conditions of each valid label right and the
rights of particular registered proprietor. All trademarks, trade names or company
names are or can be trademarks or registered trademarks of their particular proprietors. All rights which are not expressly allowed are reserved. If an explicit label of
trademarks, which are used in this documentation, fails, should not mean that a name
is free of third party rights.
► Windows, Windows 7, Windows 8.1, Windows 10
are trademarks of the Microsoft Corporation.
VN5000 ManualVersion 2.510
1.2Important Notes
1.2.1 Safety Instructions and Hazard Warnings
Caution!
In order to avoid personal injuries and damage to property, you have to read and
understand the following safety instructions and hazard warnings prior to installation and use of this interface. Keep this documentation (manual) always near the
interface.
1.2.1.1 Proper Use and Intended Purpose
Caution!
The interface is designed for analyzing, controlling and otherwise influencing control systems and electronic control units. This includes, inter alia, bus systems like
CAN, LIN, K-Line, MOST, FlexRay, Ethernet, BroadR-Reach and/or ARINC 429.
1 Introduction
The interface may only be operated in a closed state. In particular, printed circuits
must not be visible. The interface may only be operated (i) according to the instructions and descriptions of this manual; (ii) with the electric power supply designed
for the interface, e.g. USB-powered power supply; and (iii) with accessories manufactured or approved by Vector.
The interface is exclusively designed for use by skilled personnel as its operation
may result in serious personal injuries and damage to property. Therefore, only
those persons may operate the interface who (i) have understood the possible
effects of the actions which may be caused by the interface; (ii) are specifically
trained in the handling with the interface, bus systems and the system intended to
be influenced; and (iii) have sufficient experience in using the interface safely.
The knowledge necessary for the operation of the interface can be acquired in
work-shops and internal or external seminars offered by Vector. Additional and
interface specific information, such as „Known Issues“, are available in the „Vector
KnowledgeBase“on Vector´s website at www.vector.com. Please consult the
„Vector KnowledgeBase“for updated information prior to the operation of the interface.
VN5000 ManualVersion 2.511
1.2.1.2 Hazards
1 Introduction
Caution!
The interface may control and/or otherwise influence the behavior of control systems and electronic control units. Serious hazards for life, body and property may
arise, in particular, without limitation, by interventions in safety relevant systems
(e.g. by deactivating or otherwise manipulating the engine management, steering,
airbag and/or braking system) and/or if the interface is operated in public areas
(e.g. public traffic, airspace). Therefore, you must always ensure that the interface
is used in a safe manner. This includes, inter alia, the ability to put the system in
which the interface is used into a safe state at any time (e.g. by „emergency shutdown“), in particular, without limitation, in the event of errors or hazards.
Comply with all safety standards and public regulations which are relevant for the
operation of the system. Before you operate the system in public areas, it should
be tested on a site which is not accessible to the public and specifically prepared
for performing test drives in order to reduce hazards.
1.2.2 Disclaimer
Caution!
Claims based on defects and liability claims against Vector are excluded to the
extent damages or errors are caused by improper use of the interface or use not
according to its intended purpose. The same applies to damages or errors arising
from insufficient training or lack of experience of personnel using the interface.
1.2.3 Licenses
1.2.3.1 Google Protocol Buffer
Reference
This device uses the Google Protocol Buffer. The license information can be found
in the separate text file on the Vector Driver Disk in \Docu-mentation\Licenses.
1.2.3.2 Petteri Aimonen Nano Protocol Buffer
Reference
This device uses the Petteri Aimonen Nano Protocol Buffer. The license information can be found in the separate text file on the Vector Driver Disk in \Docu-mentation\Licenses.
VN5000 ManualVersion 2.512
2 General Information
2General Information
In this chapter you find the following information:
2.1 Manual Validity14
2.2 Examples of Usage15
2.2.1 Transparent Ethernet Monitoring15
2.2.2 Remaining Bus Simulation17
2.2.3 Standalone Media Converter18
2.2.4 Diagnostics over IP19
2.2.5 Port Mirroring20
VN5000 ManualVersion 2.513
2.1Manual Validity
Note
This manual is valid for the VN5000 interface family with effect from device driver
version 11.2.
Note
Driver version 11.2 introduces the network-based Ethernet configuration but still
supports the previous channel-based configuration (legacy mode).
This manual focuses on the new network-based Ethernet configuration. Therefor,
the mode of the VN5610 (A) or VN5640 interface has to be changed with the
Vector Hardware Config tool (see section Ethernet Device Configuration on page
116).
Note
The network-based Ethernet configuration requires at least CANoe V12.0 SP4 or
CANape V18!
2 General Information
Reference
For previous driver versions and the channel-based configuration, please refer to
the separate VN5610A or the VN5640 manual on the Vector Driver Disk:
\Documentation\VN5000 Interface Family\....
VN5000 ManualVersion 2.514
2 General Information
ETH Port 1
PC
USB/ETH
CANalyzer.Ethernet/CANoe.Ethernet
VN5000
ETH Port 2
Sensor
bypassing
Sensor
ECUECU
SensorSensorSensor
SWITCH
Sensor
ECU
SWITCH
2.2Examples of Usage
2.2.1 Transparent Ethernet Monitoring
MonitoringThe VN5000 network interface can be used for Ethernet monitoring between an ECU
and a connected sensor without influencing the Ethernet bus (Test Access Point). In
this particular setup the VN5000 network interface receives and forwards incoming
data packages transparently from one port to the other. The VN5000 network interface
offers up to six TAP (Test Access Point) paths which can be used in parallel.
Setup
Figure 1: TAP Ether net data
This allows applications such as CANalyzer.Ethernet or CANoe.Ethernet to trace Ethernet data with accurate time stamps.
The latency values depend on PHY characteristics, used MII interface and
VN5000 specific TAP handling.
Note
For a network tap, you have to connect the VN5000 interface between the ECUs.
In the event of a fault or when the VN5000 is switched off, the network connection
between the ECUs will be interrupted. This can lead to malpractice of the vehicle.
Time stamp clock for
Ethernet and CAN
The VN5000 network interface uses a common time stamp clock for Ethernet and
CAN events. So if the measurement setup is extended by a CAN network, the generated CAN time stamps are always in sync with the Ethernet time stamps which
helps analyzing the network.
Figure 2: Extended measuring setup
Note
Additional Vector network interfaces can be synchronized by software, hardware
or IEEE 1588 (see section Time Synchronization on page 135).
VN5000 ManualVersion 2.516
2.2.2 Remaining Bus Simulation
PC
CANalyzer.Ethernet/CANoe.Ethernet
CAN
ECU
CAN
CH3
CAN
CH4
VN5000
Time Stamp Clock
ECUECU
Sensor
CANoe
ETH SIM #1
Sensor
SWITCH
CANoe
ETH SIM
#1
CANoe
ETH SIM
#2
CANoe
CAN SIM
#2
CANoe
CAN SIM
#1
ECU
CANoe
ETH SIM #2
CAN
Gateway
CANoe
CAN SIM #1
CANoe
CAN SIM #2
USB/ETH
ETH Port 1
ETH Port 2
2 General Information
Developing
networks
Setup
The VN5000 network interface is able to send and receive data packages on separate
Ethernet ports as well as events on two separate CAN channels. With this, the
VN5000 network interface is a perfect choice for the remaining bus simulation during
the development of complex networks.
Figure 3: Simulated nodes
Note
For the remaining bus simulation CANoe.Ethernet is required.
VN5000 ManualVersion 2.517
2.2.3 Standalone Media Converter
VN5000
Media Converter
PC/Standard Ethernet Logger
Port 1
Port 2
100BASE-TX
100BASE-T1
SensorSensor
ECU
SWITCH
2 General Information
Physical layer
conversion
The Ethernet ports of the VN5000 network interface can be configured independently.
That way the VN5000 network interface can be used as a media converter between
an ECU using the 100BASE-T1/1000BASE-T1 Ethernet standard and any standard
Ethernet equipment (e.g. loggers) using 100BASE-TX/1000BASE-T. The VN5000 network interfaces offer up to four media converters which can be used independently.
Setup
Figure 4: Media converter
Media converterDeviceCount
VN5610(A)1
VN56202
VN54301
VN56404
VN52403
VN56504
VN5000 ManualVersion 2.518
2 General Information
PC
CANalyzer.Ethernet/CANoe.Ethernet
CAN
ECU
CAN
CH3
CAN
CH4
ETH Port 1
VN5000
Time Stamp Clock
CANoe
ETH SIM
#1
ECU
CANoe
ETH SIM #1
CAN
Gateway
USB/ETH
IO
100BASE-TX
DoIP Activation
2.2.4 Diagnostics over IP
DoIP activation lineFor diagnostics over IP, the VN5000 network interface supports, beside the neces-
sary 100BASE-TX port, an digital IO channel which has a DoIP activation line according to the ISO specification (ISO DIS 13400-3). The activation level can be set by the
VN5000 network interface to switch the ECU to diagnostic mode.
Setup
Figure 5: Simulated nodes
VN5000 ManualVersion 2.519
2 General Information
ETH Port 1
VN5000
ETH Port 2
Sensor
bypassing
ECU
SWITCH
ETH Port 3
ETH Port 4
bypassing
Sensor
ECU
SWITCH
ETH Port 13
ETH
Logger
2.2.5 Port Mirroring
Note
This feature is only supported on VN5240, VN5430, VN5640 and VN5650.
DescriptionThe VN5000 network interface supports mirroring of incoming packets of selected
source port to a specific target port. For example, this mirroring feature can be used to
attach an Ethernet logger to the target port. Additionally, the outgoing logging traffic
can be reduced by setting protocol filters.
Setup
Figure 6: Ethernet port 13 configured as target, port 1...4 as source
Note
The configuration is done in Vector Hardware Config.
VN5000 ManualVersion 2.520
3 VN5610A
3VN5610A
In this chapter you find the following information:
3.1 Scope of Delivery22
3.2 Introduction22
3.3 Connectors Ethernet Side24
3.3.1 Connectors USB Side25
3.3.2 LEDs27
3.3.3 Technical Data28
3.4 Accessories32
VN5000 ManualVersion 2.521
3.1Scope of Delivery
ContentsThe delivery includes:
► VN5610(A) Ethernet/CAN interface
► Vector Power Supply 12 V / 1.25 A (part number 05024)
► USB 2.0 cable (part number 05011)
3.2Introduction
3 VN5610A
About the
VN5610(A)
The VN5610(A) is a Vector network interface which supports the Ethernet physical
layer 10BASE-T, 100BASE-T1 (OPEN Alliance BroadR-Reach), 100BASE-TX and
1000BASE-T. 100BASE-T1 is a physical layer especially used in automotive electronics.
Figure 7: VN5610 Ethernet/CAN Interface
Figure 8: VN5610A Ethernet/CAN Interface
The VN5610(A) enables the transparent monitoring and logging of Ethernet data
streams and CAN events with minimal latency times and high resolution time
stamps.With this, the VN5610(A) enables a variety of applications such as simple
bus analyses, complex remaining bus simulations as well as diagnostic and calibration (e.g. with CANalyzer.Ethernet/CANoe.Ethernet).
HighlightsCommon features of VN5610 and VN5610A:
► Support of two independent Ethernet ports,
available as 2x RJ45 or 1x D-SUB9
► Support of standard Ethernet (10BASE-T/100BASE-TX/1000BASE-T)
► Support of two independent CAN/CAN FD channels,
available as 1x D-SUB9
► High resolution time stamps for Ethernet frames
VN5000 ManualVersion 2.522
► High resolution time stamps for CAN/CAN FD frames
► Software, hardware and IEEE 1588 time synchronization
of multiple Vector network interfaces
► Internal three-way-routing in/monitor/out
► Robustness, power supply and temperature ranges
suitable for automotive and industrial applications
DifferencesDifferences between VN5610 and VN5610A:
VN5610
► Support of BroadR-Reach physical layer
VN5610A
► Support of 100BASE-T1 (OPEN Alliance BroadR-Reach)
► Support of one digital input/output (e.g. for DoIP Activation Line)
The Ethernet configuration must be done in Vector Hardware Config.
3.3.1 Connectors USB Side
ACTSPEED
31
2
1
2
Digital Input/Ouput
Isolation
455R
Ri
50R
50R
Vcc
GND_ISO
Passive
Network
From Processor
To Processor
GND_ISO
10k
Device connectors
Figure 10: Connectors on the USBside
► Power/sync (Binder connector)
The VN5610A has one power/sync connector (Binder type 711) which can be used
for time synchronization of different Vector devices (see section Time Synchronization on page 135) or for power.
PinAssignment
1Power supply (6 V … 50 V DC, typ. 12 V)
2Synchronization line
3Ground
3 VN5610A
► IO CH5 (Lemo connector)
The VN5610A has a Lemo connector (type 302) for dedicated digital input/output
tasks (e.g. as DoIP Activation Line). Use the VX1362B adapter cable to access
the pins (see accessories manual, part number 22258). The pin assignment is as
follows:
PinAssignment
1Digital input/output (see technical data)
2Ground
Figure 11: Digital input /output
VN5000 ManualVersion 2.525
3 VN5610A
5
4
3
2
1
6
789
Not connected
Reserved
1051cap CAN High
1051cap GND
1051cap CAN Low
1051cap CAN Low
1051cap GND
1051cap CAN High
CH3
CH4
Not connected
Note
The VN5610A requires at least 8 V to power up. Afterwards the power supply can
be reduced to 6 V for operation (typ. 12 V DC). The need of an external power supply depends on the Ethernet configuration (see table).
Ethernet
Configuration
Disabled100BASE-T1100BASE-TX1000BASE-T
Port 1
Port 2
DisabledOOOO
100BASE-T1OOXX
100BASE-TXOXXX
1000BASE-TOXXX
O: bus-powered (also when both CAN channels in use), X: external power supply recommended.
Note: CAN itself requires no external power supply.
► USB
Connect your PC and the VN5610A over USB to install and to use the device with
measurement applications (CANoe, CANalyzer). Use the USB 2.0 compliant
cable found in the delivery (USB extension cables may generate faults between
the PC and the device). Connect the device directly to a USB port at your PC or
use a USB hub with its own power supply (self-powered). The device can also be
powered via this connector.
► Host (Ethernet)
Alternative host connection over Ethernet (1000BASE-T). For configuration, see
section Getting Started on page 154.
► CAN CH3/4 (D-SUB9)
D-SUB connector with two CAN channels. Use the CANcable 2Y to access both
channels on separate D-SUB9 connectors (see accessories manual, part number
05075).
PinAssignment
1CH4 CAN Low
2CH3 CAN Low
3CH3 GND
4Reserved.
Please do not use.
5Not connected
6CH4 GND
7CH3 CAN High
8CH4 CAN High
9Not connected
VN5000 ManualVersion 2.526
3.3.2 LEDs
LEDs on top side
3 VN5610A
Figure 12: LEDs on VN5610(A)
► Activity (Ethernet CH1/CH2)
Same as LED ACT at RJ45 connectors. LED illuminates if there is an Ethernet
link or blinks if there is Ethernet activity at CH1/CH2.
ColorDescription
GreenLink to RJ45.
YellowLink to D-SUB9.
► Master (Ethernet CH1/CH2)
Illuminates if CH1/CH2 is configured as Master.
ColorDescription
GreenPHY is configured as master on RJ45.
YellowPHY is configured as master on D-SUB9.
► Status
Multicolored LED indicating the device status.
ColorDescription
GreenBlinks 4x at power up and illuminates afterwards.
Blinks quicker during an update progress. Please wait for the automatic reboot of the device (approx. 30 s) after the update has been finished.
RedAn error has occurred. Please disconnect the power supply as well as
the USB cable. Re-connect the power supply and the USB cable and
try again.