ADTF_DEVICE_TOOLBOX  3.11.3 (ADTF 3.16.2)
Vector Ethernet Device Plugin

Vector Ethernet Device Receiver

Plugin Information
Plugin Filenamevector_ethernet_device_streaming_services.adtfplugin
Plugin Descriptionvector_ethernet_device_streaming_services.plugindescription
Plugin NameVector Ethernet Device Plugin
LicenseADTF
Support Mailsupport@digitalwerk.net
Homepage URLwww.digitalwerk.net
Plugin Versions
Plugin Version3.11.3
Plugin File Version1.0
adtf::devicetb3.11.3
adtf3.16.2
adtf::ucom3.1.0
Component Information
NameVector Ethernet Device Receiver
CIDvector_ethernet_device_receiver.streaming_source.devicetb.cid
DescriptionUse this Streaming Source to receive Ethernet data using a Vector XL Driver Library compatible device.
TypeFilter
Properties
NameValueTypeDescriptionSubproperties
attachment_namecStringName of virtual or physical port definition in Network Config Tool. Names are only recongized in the scope of the specified network. Virtual points must be reserved exclusively for a single instance of the ADTF launcher! Virtual points may be safely shared by multiple instances of this source within ADTF. For 'Switch' attachment points, only a single Virtual Port is created application wide within ADTF.
attachment_type0tInt32Type of attachment point.Value List:
Physical = 0
Virtual = 1
Switch (dynamic virtual port) = 2
networkEthernet1cStringName of network definition in Network Config Tool.
Output Pins
NameStream TypeDescription
ethernet_rx_out adtf/devicetb/ethernet Raw Ethernet sample streams containing all frames received on the attachment point of the Vector Device.
ethernet_tx_out adtf/devicetb/ethernet Raw Ethernet sample streams containing all frames sent on the attachment point of the Vector Device. When combined with a transmitter on the same attachment point, this is effectively the transmission protocol.
Dynamic Pins
Dynamic Input Pinsfalse
Dynamic Output Pinsfalse
Dynamic Input Binding Pinsfalse
Dynamic Output Binding Pinsfalse
Required Interfaces
IID
kernel.penguin.services.adtf.iid
reference_clock.penguin.streaming.adtf.iid
Output Pin Stream Types
Pin Nameethernet_rx_out
Meta Type Nameadtf/devicetb/ethernet
Stream Type Properties
NameValueTypeDescriptionSubproperties
md_data_serializedtruetBool
md_definitions
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<adtf:ddl xmlns:adtf="adtf">
<structs>
<struct name="tEthernetSampleHeader" version="1" ddlversion="4.0">
<element name="tmTimestampBeginNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="0" byteorder="LE"/>
</element>
<element name="tmTimestampEndNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="8" byteorder="LE"/>
</element>
<element name="nErrorCode" type="tInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="16" byteorder="LE"/>
</element>
<element name="nFrameCheckSequence" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="20" byteorder="LE"/>
</element>
<element name="nFrameSize" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="24" byteorder="LE"/>
</element>
<element name="aFrameData" type="tUInt8" arraysize="nFrameSize">
<deserialized alignment="1"/>
<serialized bytepos="28" byteorder="LE"/>
</element>
</struct>
</structs>
</adtf:ddl>
cString
md_structtEthernetSampleHeadercString
Pin Nameethernet_tx_out
Meta Type Nameadtf/devicetb/ethernet
Stream Type Properties
NameValueTypeDescriptionSubproperties
md_data_serializedtruetBool
md_definitions
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<adtf:ddl xmlns:adtf="adtf">
<structs>
<struct name="tEthernetSampleHeader" version="1" ddlversion="4.0">
<element name="tmTimestampBeginNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="0" byteorder="LE"/>
</element>
<element name="tmTimestampEndNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="8" byteorder="LE"/>
</element>
<element name="nErrorCode" type="tInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="16" byteorder="LE"/>
</element>
<element name="nFrameCheckSequence" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="20" byteorder="LE"/>
</element>
<element name="nFrameSize" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="24" byteorder="LE"/>
</element>
<element name="aFrameData" type="tUInt8" arraysize="nFrameSize">
<deserialized alignment="1"/>
<serialized bytepos="28" byteorder="LE"/>
</element>
</struct>
</structs>
</adtf:ddl>
cString
md_structtEthernetSampleHeadercString

Vector Ethernet Device Transmitter

Plugin Information
Plugin Filenamevector_ethernet_device_streaming_services.adtfplugin
Plugin Descriptionvector_ethernet_device_streaming_services.plugindescription
Plugin NameVector Ethernet Device Plugin
LicenseADTF
Support Mailsupport@digitalwerk.net
Homepage URLwww.digitalwerk.net
Plugin Versions
Plugin Version3.11.3
Plugin File Version1.0
adtf::devicetb3.11.3
adtf3.16.2
adtf::ucom3.1.0
Component Information
NameVector Ethernet Device Transmitter
CIDvector_ethernet_device_transmitter.streaming_sink.devicetb.cid
DescriptionUse this Streaming Source to receive Ethernet data using a Vector XL Driver Library compatible device.
TypeFilter
Properties
NameValueTypeDescriptionSubproperties
attachment_namecStringName of virtual or physical port definition in Network Config Tool. Names are only recongized in the scope of the specified network. Virtual points must be reserved exclusively for a single instance of the ADTF launcher! Virtual points may be safely shared by multiple instances of this source within ADTF. For 'Switch' attachment points, only a single Virtual Port is created application wide within ADTF.
attachment_type0tInt32Type of attachment point.Value List:
Physical = 0
Virtual = 1
Switch (dynamic virtual port) = 2
mac_spoofingfalsetBoolWhen enabled, force the Layer 2 source MAC address to be transmitted as specified. When disabled, let the Vector Device override the source MAC address to the address of the attachment point. Spoofing a MAC which already exists in the network segment may cause severe issues with switches!
networkEthernet1cStringName of network definition in Network Config Tool.
Input Pins
NameStream TypeDescription
ethernet_in adtf/devicetb/ethernet Raw Ethernet sample streams for transmission on Vector Device.
Runner
NameActivation TypeData TriggeredData InputThread TriggeredThread CyclicTimer TriggeredTimer IntervalDescription
process_ethernet_in91ethernet_in0000Default runner port for the input pin 'ethernet_in'
Dynamic Pins
Dynamic Input Pinsfalse
Dynamic Output Pinsfalse
Dynamic Input Binding Pinsfalse
Dynamic Output Binding Pinsfalse
Required Interfaces
IID
kernel.penguin.services.adtf.iid
reference_clock.penguin.streaming.adtf.iid
Input Pin Stream Types
Pin Nameethernet_in
Meta Type Nameadtf/devicetb/ethernet
Stream Type Properties
NameValueTypeDescriptionSubproperties
md_data_serializedtruetBool
md_definitions
<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>
<adtf:ddl xmlns:adtf="adtf">
<structs>
<struct name="tEthernetSampleHeader" version="1" ddlversion="4.0">
<element name="tmTimestampBeginNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="0" byteorder="LE"/>
</element>
<element name="tmTimestampEndNs" type="tInt64" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="8" byteorder="LE"/>
</element>
<element name="nErrorCode" type="tInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="16" byteorder="LE"/>
</element>
<element name="nFrameCheckSequence" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="20" byteorder="LE"/>
</element>
<element name="nFrameSize" type="tUInt32" arraysize="1">
<deserialized alignment="1"/>
<serialized bytepos="24" byteorder="LE"/>
</element>
<element name="aFrameData" type="tUInt8" arraysize="nFrameSize">
<deserialized alignment="1"/>
<serialized bytepos="28" byteorder="LE"/>
</element>
</struct>
</structs>
</adtf:ddl>
cString
md_structtEthernetSampleHeadercString

General Informations and preparations

These streaming services uses the network based access mode of the Vector API.

Note
If your device supports the channel-based access mode too, make sure you have chosen the network based access mode via the Vector Hardware Configuration tool.

The XL Driver Library can only open networks that have been previously configured on a Vector device. Therefore, before an XL API application can perform measurement or simulation on a device, you must write an appropriate network configuration to the device using the Vector Hardware Configuration tool and the Ethernet device configuration.

Note
Make sure you have already added a virtual port if you want to capture temporary from the switch or (additional) simulation data.

Installation

Like other Vector Device plugins this filter is Windows only.
Only install the Drivers for your Vector Device and you are good to go, the required libraries are shipped besides the adtfplugin.

Reference setup

Tested and implemented with VN5620 Vector Device via USB using driver version 22.10.20.

Using multiple ethernet devices

You can connect multiple Vector Ethernet devices and connect them via USB to your computer. Make sure the network names of the devices you have given in the Ethernet device configuration are different. For example D&D 2 of the Vector Ethernet device receivers in the ADTF Filter Graph and give them the correct properties like the network name, the measurement point name and the virtual port name. If you don't remember the names please have a look in the Vector Hardware Configuration Tool -> right click on the ethernet device -> Ethernet device configuration.