Technica Engineering 100base-t1_SPY User Manual

Download

Page 1

User Manual

Version 1.2

September 2017

BroadR-Reach – Standard Ethernet

100BaseT1_SPY

Page 2

Page 1 of 43

The user can download the latest firmware and documentation for the 100BASET1_SPY here:

http://www.technica-engineering.de/SPY

Note: This User Manual version is related to 100BASET1_SPY Firmware version 1.12.

Page 3

Page 2 of 43

Index

1 Feature List ..................................................................................................................................... 3

2 Warranty and Safety Information ................................................................................................... 4

3 Pinning ............................................................................................................................................ 5

3.1 Power connector (top left) ...................................................................................................... 6

3.2 BroadR-Reach connectors ....................................................................................................... 7

3.3 RJ45 Ethernet connectors ....................................................................................................... 8

3.4 SMA Connector ........................................................................................................................ 8

4 Status LEDs and Pushbutton ........................................................................................................... 9

5 Configuration Website .................................................................................................................. 10

5.1 Website Home ....................................................................................................................... 11

5.2 System Information Tab ........................................................................................................ 11

5.3 Control Panel Tab .................................................................................................................. 12

5.4 Switch Status Tab .................................................................................................................. 13

5.4.1 Global Configuration: .................................................................................................... 13

5.4.2 Spy Multiplexer .............................................................................................................. 14

5.4.3 Gigabit Ethernet Ports ................................................................................................... 15

5.4.4 BroadR-Reach Port ........................................................................................................ 16

5.4.5 CAN Port ........................................................................................................................ 18

5.4.6 LIN Port .......................................................................................................................... 22

5.4.7 FlexRay Port ................................................................................................................... 25

6 Structure of an Ethernet 100BASET1_SPY RAW frame ................................................................ 26

6.1 Structure of the BroadR-Reach payload ................................................................................ 28

6.2 Structure of the CAN payload ................................................................................................ 29

6.3 Structure of the LIN payload ................................................................................................. 30

6.4 Structure of the FlexRay payload .......................................................................................... 32

6.5 100BASET1_SPY LUA Installation Guide ................................................................................ 33

7 UseCases ....................................................................................................................................... 35

7.1 100BaseT1_SPY UseCase ....................................................................................................... 35

8 Hardware Variants ........................................................................................................................ 36

8.1 BroadR-Reach Analog Filter ................................................................................................... 36

8.2 Debug connector ................................................................................................................... 36

8.3 Startup Time .......................................................................................................................... 37

9 Application Firmware Update ....................................................................................................... 38

10 Frequently Asked Questions – FAQ .............................................................................................. 41

11 Contact .......................................................................................................................................... 42

Page 4

Page 3 of 43

1 Feature List

The Technica Engineering 100BaseT1_SPY samples data Frames directly on the bus without influence of the original network. The data Frames are enhanced with additional information as an exact timestamp and the bus port the data was originally sent on. All data can be recorded on a PC or datalogger for detailed offline analysis. Timestamps are in 0.04 μs resolution and synchronous to all connected lines. Optionally other UseCases (Frame Generator, Fault Injection, Data Manipulation, Trigger Generator, … ) can be upgraded.

Features:

 12x BroadR-Reach Ports Fullduplex 100 Mbit/s  1x FlexRay Channel A (option for transmission of StartUp & Sync Frames)  5x CAN / CAN-FD Ports  1x LIN, 1x SMA Trigger  4x Gigabit Ethernet Ports for Logging data output  1x Fast Ethernet Port for status output, configuration and webserver access  1x SD Card for configuration and storage of trigger events  Stainless steel case

Power requirement: 12 Volt DC Nominal (7-16 Volt) Power consumption: 10 Watt Size: 147 x 124 x 26mm Weight: 0,9 kg International Protection: IP 2 0 Operating Temperature: -40 to +80 °Celsius

Page 5

Page 4 of 43

2 Warranty and Safety Information

Before operating the device, read this manual thoroughly and retain it for your reference. The latest firmware and documentation can be downloaded for the 100BASET1_SPY through the following link:

http://www.technica-engineering.de/SPY

Use the device only as described in this manual. Use only in dry conditions. Do not apply power to a damaged device.

Do not open the device. Otherwise warranty will be lost.

This device is designed for engineering purpose only. Special care has to be taken for operation. Do not use this device in a series production car. As this device is likely to be used under rough conditions, warranty is limited to 1 year. Manufacturer liability for damage caused by using the device is excluded.

Page 6

Page 5 of 43

3 Pinning

The pinning of the ECU connectors is listed on the label on top of the device. The Tyco Electronics (TE) Nano Micro Quad Lock System (NanoMQS) is used.

Name

Part Number

20POS

NANOMQS

REC HSG

CODE A

2141404-1

NANOMQS

RECEPTACLE TERMINAL

2-1703930-1

http://www.te.com/usa-en/product-2141404-1.html http://www.te.com/usa-en/product-2-1703930-1.html http://www.te.com/usa-en/product-4-1579014-0.html

http://de.farnell.com/te-connectivity/2-1703930-1/contact-socket-crimp/dp/2528666

Official Crimp Tool:

TE CONNECTIVITY CS11K NANO-MQS, 0.13-0.35 SQ.M TE Internal Number: 4-1579014-0

Distributor: Börsig GmbH Siegmund-Loewe-Str. 5 74172 Neckarsulm www.boersig.com

Page 7

Page 6 of 43

3.1 Power connector (top left)

Power supply for the device is supplied by Pin 18 (12Volt) and Pin 20 (Ground). Requirements for the 100BASET1_SPY itself: 12 Volt DC up to 1 Ampere (typical 600mA)

Warning: If a voltage higher than 16 Volt is applied, the device will be damaged!

A wakeup-line may be connected on pin 5. The wakeup-line should have the same voltage level as the power supply (12 Volt). A high level on one of these pins wakes up the ECU from sleep mode and keeps it active. Alternatively, the “Prevent sleep” checkbox in the control panel of the website can be enabled.

The CAN interfaces can be used to communicate with the Microcontroller by CAN and CAN-FD bus.

The LIN interface can be used to communicate with the Microcontroller by LIN bus.

The FlexRay interface can be used to communicate with the Microcontroller by FlexRay bus. In the default software there is no data transmission specified.

Page 8

Page 7 of 43

Function

GND Reference for Trigger

Host Trigger Line

LIN Bus

FlexRay Channel A BP

Wake Line

FlexRay Channel A BM

CAN D / 5 Minus (Low)

CAN E / 1 Plus (High)

CAN D / 5 Plus (High)

CAN E / 1 Minus (Low)

n.c.

CAN C / 2 Plus (High)

CAN B / 4 Minus (Low)

CAN C / 2 Minus (Low)

CAN B / 4 Plus (High)

n.c.

CAN A / 3 Minus (Low)

Battery +12 Volt Input

CAN A / 3 Plus (High)

Battery Ground Input

3.2 BroadR-Reach connectors

The pins marked with (P) or (M) are used for the BroadR-Reach ports. The user has to connect the (P) pin to the (P) pin of the periphery device. The user has to connect the (M) pin to the (M) pin of the periphery device.

Note: If these two pins are swapped, the link LED may be lit on the BroadR-Reach slave side, but no

data transmission will be possible.

Middle Connector

Function

GND Reference for Trigger

FPGA Trigger Line OUT1

n.c. 4 n.c.

BroadR-Reach Port 3A / 5, P (Positive)

BroadR-Reach Port 3B / 6, P (Positive)

BroadR-Reach Port 3A / 5, M (Negative)

BroadR-Reach Port 3B / 6, M (Negative)

n.c.

BroadR-Reach Port 2A / 4, P (Positive)

BroadR-Reach Port 2B / 3, P (Positive)

BroadR-Reach Port 2A / 4, M (Negative)

BroadR-Reach Port 2B / 3, M (Negative)

n.c.

BroadR-Reach Port 1A / 1, P (Positive)

BroadR-Reach Port 1B / 2, P (Positive)

BroadR-Reach Port 1A / 1, M (Negative)

BroadR-Reach Port 1B / 2, M (Negative)

Outer Connector

Function

GND Reference for Trigger

FPGA Trigger Line IN1

n.c. 4 n.c.

BroadR-Reach Port 6A / 9, P (Positive)

BroadR-Reach Port 6B / 12, P (Positive)

BroadR-Reach Port 6A / 9, M (Negative)

BroadR-Reach Port 6B / 12, M (Negative)

n.c.

BroadR-Reach Port 5A / 8, P (Positive)

BroadR-Reach Port 5B / 11, P (Positive)

BroadR-Reach Port 5A / 8, M (Negative)

BroadR-Reach Port 5B / 11, M (Negative)

n.c.

BroadR-Reach Port 4A / 7, P (Positive)

BroadR-Reach Port 4B / 10, P (Positive)

BroadR-Reach Port 4A / 7, M (Negative)

BroadR-Reach Port 4B / 10, M (Negative)

Page 9

Page 8 of 43

3.3 RJ45 Ethernet connectors

There are four RJ45 Standard Ethernet connectors of the front side for Gigabit Ethernet. There is one RJ45 Standard Ethernet connector of the front side for Fast Ethernet (100 Bit/s)

3.4 SMA Connector

There is one shielded SMA Connector for one Trigger Input/Output Line.

Page 10

Page 9 of 43

4 Status LEDs and Pushbutton

The 100BASET1_SPY has several status LEDs at the front side of the case.

The “Host” LED1 can toggle at three different speeds: Slow toggle (approx. 0.5 sec) during normal operation to show that the microcontroller is running in normal mode. Fast toggle (approx. 0.1 sec) when the microcontroller is in bootloader mode. The bootloader mode is used for firmware update only (see below in this manual). The user cannot access the website when the device is in bootloader mode. When the device is in Bootloader-Update Mode the LED toggles with moderate frequency (approx.

0.25 sec).

The “Host” LED2 should be normally off. If it toggled at high speed (approx. 0.1 sec) an error has been detected by the Host.

The “FPGA” LED2 can toggle at two different speeds: Slow toggle (approx. 0.5 sec) during normal operation to show that the FPGA is running in normal mode. Fast toggle (approx. 0.1 sec) : TBD

The “FPGA” LED1 should be normally off. If it toggled at high speed (approx. 0.1 sec) an error has been detected by the FPGA.

The 12 port status LEDs 1A to B6 monitor the link status of the corresponding port. The LEDs are lit when there is BroadR-Reach link detected.

Note: There is an issue when P/N of the bus are swapped. The LED may be on in this case on BroadR-

Reach slave side, but there will be no data transmission possible.

The built-in LEDs in RJ45 connector shows the status of the gigabit ports. The left (orange LED) is lit by a link-up. The right (yellow) will blink on data traffic.

The Rotary DIP Switch has four modes: 1: TBD 2: TBD 3: TBD 4: TBD

Page 11

Page 10 of 43

5 Configuration Website

The user can access the configuration website with a standard web browser.

Note: Firefox is recommended; Chrome is not recommended.

Connect your PC to the “Host” RJ45 connector. The default IP address of the device is 192.168.0.49 and subnet mask 255.255.255.0 If IP address has been changed, The user can reset it to default as described in chapter 9 of this manual.

For example set the configuration PC to IP address 192.168.0.100 and subnet mask to 255.255.255.0

Note: Please, make sure that the Internet Protocol Version 6 (TCP/IPv6) option is disabled.

Page 12

Page 11 of 43

5.1 Website Home

With the first access to the website The home screen will be shown. Please select one of the tabs for further configuration.

5.2 System Information Tab

Page 13

Page 12 of 43

On the tab „System Information“ some status information about the device is displayed. The user can check the version number of the application firmware and the bootloader or the unique MAC adress of the device. The version number registers of the switch and phy chips are displayed for information only. The MAC adress should be the same as on the label on the bottom of the device.

The IP adress of the host microcontroller (Webserver) can be changed here. If the user wants to use multiple devices in one network, an unique IP adress for each device must be set here.

Note: Before installing a new firmware, please restore the IP Address to the default one:

192.168.0.49. In order to restore the IP, please see Section 9.

5.3 Control Panel Tab

On the „Control Panel“ tab The user can soft-reset (restart) the system.

Also the configuration settings of the device can be imported and exported to a file (*.bin) on a computer connected to the RJ45 Port. The user have to restart the device for usage of the new configuration.

The user can reset the configuration settings to default. All the configuration stored will be revert to its defaults values.

If you do not want to use a WakeUp line, The user can enable the “Prevent sleep” checkbox (default). This will keep the device running without entering the sleep mode.

Page 14

Page 13 of 43

5.4 Switch Status Tab

The main configuration of the switch is done in the „Switch Status“ tab. Here the user can configure details about each port and get some status information about the ports and switch states.

On the left side of the page the user can see an overview of all available ports. A blue bar at the side of a port label indicates an active link.

5.4.1 Global Configuration:

When the user click on „Switch Status“ tab and no port or switch is still selected, Global configuration will appear.

Page 15

Page 14 of 43

5.4.2 Spy Multiplexer

Click on the central „Spy“ label to configure general Spy Multiplexer settings.

Enable header for logging ports: This option enables the Header Mode of the 100BASET1_SPY.

For BroadR-Reach Ports the original Ethernet frames will be wrapped in a new Ethernet Frame. This new frame will contain additional data (timestamp, ingress port, …) and the original RAW frame. The new Frame will be transmitted through the selected Gigabit Port. See frame format information in Chapter 6.

For CAN, LIN and FlexRay frames the wrapper is necessary for the data to be recognized as Ethernet frame.

Note: When the user makes any change in the configuration of any port, the Save Configuration

option will appear. Select the Restart after saving option before saving configuration.

Page 16

Page 15 of 43

5.4.3 Gigabit Ethernet Ports

There are four Gigabit Ethernet Ports for data logging output at the front of the device. On the website the user can see the status by clicking on the GB-A to GB-D labels on the left side.

Detected speed: Shows the result of link negotiation. Speed and half/full duplex information.

BroadR-Reach Inputs: This is a configuration status information. It shows which BroadR-Reach ports

are connected to the selected Gigabit port.

Auxiliary Inputs: This shows which CAN, LIN and FlexRay ports are connected to the selected Gigabit

port.

Page 17

Page 16 of 43

5.4.4 BroadR-Reach Port

The BR-1A to BR-6B labels on right side allow the user to configure BroadR-Reach Port settings:

BroadR-Reach mode: Here the user can select Master/Slave Mode of the selected Port. On each

BroadR-Reach link there has to be one master and one slave device. Please set the “BroadR-Reach mode” to the opposite of what the device which is connected to this port.

Output level: The “Output Level” is the amplitude level of the BroadR-Reach signal. The user can set

Full level (Fullout = default) or half amplitude.

Note: Both devices of one BroadR-Reach link have to use the same level. Otherwise the user will get

an instable link. FullOut Level is always recommended.

Page 18

Page 17 of 43

Test Mode: For BroadR-Reach Ports it is possible to set a BroadR-Reach Physical Layer Test Mode.

There are five test modes defined in the BroadR_Reach Specification to check the compliance of a port.

Warning: When a test mode has been selected there is no communication possible for this port.

Note: For compliance testing an oscilloscope with special test software is necessary.

Output to: The BroadR_Reach Ports are always connected A-B for each channel pair. This setting

allows a copy of the A-B communication to be sent to a Gigabit port. Choose here which Gigabit port will be connected with the selected BroadR-Reach port.

BR PAIR ID: Specifies the multiplexing between two BroadR-Reach ports. For example, if the user

wants to connect BR1A with BR5A, BR PAIR ID in both ports must have the same value.

Note: If more than two BroadR-Reach ports have the same BR PAIR ID, only the two first ports will be

connected. For example, if BR1A, BR1B and BR2A have the same BR PAIR ID, only BR1A and BR1B will be connected between them.

Note: The BR PAIR ID value must be greater than 0. If two BroadR-Reach ports have this field set to 0,

those ports will be not connected.

TX/RX Packets: These two counters show the number of transmitted and received packets through

the selected BroadR-Reach port.

Page 19

Page 18 of 43

5.4.5 CAN Port

The CAN-A to CAN-E labels on the left allow the user to configure:

Output to: Allows to select which Gigabit port will be used to output logging data of selected CAN

port. To activate the port logging, the Header must be enabled in the Spy Multiplexer page (see Chapter 5.4.2.)

CAN Type: Allows to select between CAN or CAN-FD operation mode.

CAN mode: Allows to select if the CAN port is working as Spy or Slave. In both modes, the

100BASET1_SPY will logg the information. In the Spy mode the device will be passive and send no ACK signals.

Bit Rate: Allows to select the CAN 2.0. Bit Rate. Available options: 62500bps, 100kbps, 125kbps,

250kbps, 500kbps, 1Mbps.

In CAN-FD transmission mode, FD Rate will be selectable. In CAN-FD, the Bit Rate determines the Arbitration-Phase Bit Rate in CAN-FD protocol, while the FD Rate determines the Data-Phase Bit Rate in CAN-FD protocol. The available options in FD Rate are 2Mbps and 5Mbps.

Page 20

Page 19 of 43

Note: The CAN ports are able to work like receivers and transmitter at the same time.

Note: In the case of CAN-FD, the selected Bit Rate must be always 500kbps or 1Mbps. The device

does not work with Bit Rate lower than those values.

Note: Please set the Bit Rate and FD Rate to the same value of what the device is connected to this

port.

Note: If the 5Mbps FD Rate needs to be used, , please be sure that the transceiver of the opposite

device can work with rates higher than 2Mbps.

Page 21

Page 20 of 43

5.4.5.1 CAN Transmission data use case

In the CAN SPY or SLAVE mode, any of the 100BASET1_SPY CAN port can act as transmitters according with the CAN protocol communication. In this case, a specific Ethernet frame received from any of the Gigabit ports will be sent through a specific CAN Port. The following table shows the structure of the Ethernet CAN Transmission data frame used for this purpose:

Note: The Direction field specifies if the frame is being received (Direction 0x01) or transmitted

(Direction 0x00).

Note: The Message Type field specifies if the frame is used like a Data Frame (0x00) or a CAN Event

Frame (0x01). The Ethernet frame format used in the Data Frame case is described in the table above. The purpose of the CAN Event Frame is described in the next section.

Note: The value of the Port Number depends on the CAN port where the user wants to send the CAN

frame. Its values can be the following:

Port

Value

CAN A

0x01

CAN B

0x02

CAN C

0x03

CAN D

0x04

CAN E

0x05

Note: The value of the ID will determine if the CAN frame is standard (lower than 0x0FFF) or extend-

ed (higher than 0x07FF).

Note: According with the CAN/CAN-FD specification, only 16 Lengths can be set. The values in hexa-

decimal that can be used in the Length field are the following:

Length (bytes)

Value in Length field (hexadecimal)

From 0 to 8

0x00 to 0x08

0x0C

0x10

0x14

0x18

0x20

0x30

0x40

Field Name

No. Of Bytes

Value

Destination MAC Address

FF:FF:FF:FF:FF:FF

Source MAC Address

It depends on the source Ethernet Adapter

Ethertype

0x2085

Direction

0x00 (TX Frame)

Message Type

0x00 (Data Frame) or 0x01 (CAN Event Frame)

Port number

From 0x01 to 0x05

CAN ID

Length

In bytes

CAN Payload

0 to 64

Its length depends on the Length field

Page 22

Page 21 of 43

Note: When the Length field is 0x00, the CAN frame will be sent like a remote frame. In CAN-FD there

is not remote frames according with the CAN-FD specification.

Note: 100BASET1_SPY is able to sent CAN frames with ID priority. When a burst of three messages is

received in the Ethernet port, the device will send them according with their priority, following the CAN specification.

5.4.5.2 CAN Transmission Event Message

When a CAN frame is sent through a CAN port, an Ethernet Frame is sent through the Gigabit Port specified in the Output To field for that CAN port (see section 5.4.5). This CAN Event Message contains information about the state of the transmission, as is described in the following table:

Note: The Transmission Status field contains the following information about the CAN transmission

state:

7 6 5 4 3 2 1

Reserved

COLLISION

Reserved

RTR

Reserved

SENT

Reserved

ACK

o ACK: A ‘1’ value in this bit indicates if there was an acknowledge during the transmission of

the CAN frame.

o SENT: A ‘1’ value in this bit indicates if the CAN frame was transmitted successfully. o RTR: A ‘1’ value in this bit indicates if the CAN frame is a remote frame. o COLLISION: A ‘1’ value in this bit indicates if there was a collision with another frame during

the transmission. If there is a collision, the SENT field will be ‘0’.

Field Name

No. Of Bytes

Value

Destination MAC Address

FF:FF:FF:FF:FF:FF

Source MAC Address

It depends on the source Ethernet Adapter

Ethertype

0x2085

Direction

0x00 (TX Frame)

Message Type

0x01 (CAN Event Frame)

Port number

From 0x01 to 0x05

Frame Length

Length of the Ethernet Frame

Transmission Status

Information about the state of the transmission

CAN ID

CAN ID transmitted

Page 23

Page 22 of 43

5.4.6 LIN Port

By clicking on the LIN port label allows to configure:

Output to: This allows the user to select which Gigabit port will be connected to the LIN port. To

activate the port logging, the Header must be enabled in the Spy Multiplexer page (see Chapter

5.4.2.)

LIN mode: Allows to select if the LIN port is working as Master, Spy or in Slave mode.

Note: In the Master mode, the 100BASET1_SPY will send the information from Gigabit to LIN port,

when it receives a specific Ethernet frame (see Chapter 5.4.6.1).

Note: In the Spy mode, the 100BASET1_SPY will log the information - only if the Header is enabled in

Spy Multiplexer (see section 5.4.2) - through the Gigabit Port selected in the field Output to.

Page 24

Page 23 of 43

Note: In the Slave mode, the 100BASET1_SPY will answer to a request, that has been sent by a

Master, without logging the information through the selected Gigabit Port in Output to. The payload, length and ID for the slave response will be set through the Fast Ethernet Port in 100BASET1_SPY.

Lin Version: Allows to select LIN Version 1.3 or LIN Version 2.0. The difference between both modes

is the Checksum calculation method.

Bit Rate: Allows to select the LIN Bit Rate. Available options: 1200bps, 2400bps, 4800bps, 9600bps,

19200bps.

Note: The device which is connected to this port must have the same Bit Rate and Version.

5.4.6.1 LIN Master Mode

In the LIN Master Mode, the 100BASET1_SPY LIN port acts as the Master in the LIN protocol communication. In this case, a specific Ethernet frame received from any of the Gigabit ports will be sent through the LIN port. The following table shows the structure of the Ethernet LIN Master frame used for this purpose:

Note: In this mode, the devices connected to the 100BASET1_SPY LIN port must be configured as

Slave, with the same Bit rate and LIN version.

Note: If the Length field is set to 0x00, the frame will be sent without data, corresponding in this case

with a LIN Master Request, according to LIN specification.

Field Name

No. Of Bytes

Value

Destination MAC Address

FF:FF:FF:FF:FF:FF

Source MAC Address

It depends on the source Ethernet Adapter

Ethertype

0x2084

Direction

0x00 (TX)

Port number

0x01

LIN ID

LIN ID without parity protection

Length

In bytes

LIN Payload

1 to 8

Its length depends on the Length field

Page 25

Page 24 of 43

5.4.6.2 LIN Slave Mode

In the LIN Slave Mode, the 100BASET1_SPY LIN port acts as the Slave in the LIN protocol communication. In this case, the 100BASET1_SPY LIN port will answer to a Master LIN ID, according to an internal ID table. If the Master ID request is not in that table, there will not be any answer from 100BASET1_SPY LIN port. The information of that table can be updated setting the ID, the Length and the payload. The following table shows the structure of the Ethernet LIN Slave Configuration frame used for this purpose:

Note: The configuration must be set through the 100BASET1_SPY Fast Ethernet Port (Host).

Note: The IDs from 0x3C to 0x3F are reserved according to the LIN specification, and cannot be used.

Field Name

No. Of Bytes

Value

Destination MAC Address

FF:FF:FF:FF:FF:FF

Source MAC Address

It depends on the source Ethernet Adapter

Ethertype

0x1984

LIN Protocol Version

0x02

LIN Status

0x02 (LIN Slave Response Mode)

LIN TX/RX

0x00 (LIN TX)

LIN ID

From 0x00 to 0x3B

Length

From 0x01 to 0x08

Payload

1 to 8

Its length depends on the Length field

Page 26

Page 25 of 43

5.4.7 FlexRay Port

The FlexRay port allows the user to configure:

Output to: Allows to select which Gigabit port will be connected with theFlexRay port. To activate

the port logging, the Header must be enabled in the Spy Multiplexer page (see Chapter 5.4.2.)

Page 27

Page 26 of 43

6 Structure of an Ethernet 100BASET1_SPY RAW frame

In Switch Status, when the user selects a Gigabit Port in the Output To field, the packet received in the selected BroadR-Reach, CAN, LIN of FlexRay port will be logged through the selected Gigabit Port into an Ethernet RAW frame. The following picture shows the structure of an Ethernet 100BASET1_SPY RAW frame, in the case that the Header is enabled in the Spy Multiplexer page (see Chapter 5.4.2.).

Note: The data Frames are enhanced with additional information as an exact timestamp and the bus

port the data was originally sent on. Timestamps are in 0.04 μs resolution and synchronous to all connected lines.

Note: The Direction field specifies if the frame is being received (Direction 0x01) or transmitted

(Direction 0x00).

Note: In the case of BroadR-Reach port, there will be always an Ethernet frame in the selected

Gigabit port. If the Header is disabled in Spy Multiplexer (see section 5.4.2), the sent Ethernet frame will be and standard UDP RAW Ethernet frame. If that Header is enabled, the Ethernet frame will have the format shown in the table.

Note: The number of bytes of the payload depends on the Length field.

Destination

MAC

(6 bytes)

Source

MAC

bytes)

Ethernet

Type

(2 bytes)

Direction

(1 byte)

Time

Stamp

bytes)

Port

byte)

Extra

byte)

Length

bytes)

Payload

(BR,

CAN,

LIN, Flexray packet)

CRC

bytes)

Field Name

No. Of Bytes

Value

Destination MAC Address

FF:FF:FF:FF:FF:FF

Source MAC Address

00:50:C2:E4:30:00

Ethernet Type

See the table below

Direction

0x01 (RX frame)

Time Stamp

See the note below

Port

See the table below

Extra

0x00

Length

Payload

BR, CAN, LIN, FlexRay packets (see sections 6.1,

6.2, 6.3, 6.4 and 6.5)

CRC 4

Ethernet BRSPY Frame Header

Page 28

Page 27 of 43

Note: In the case of CAN, LIN and FlexRay, the generated Ethernet frame will be sent only if the

Header is enabled in Spy Multiplexer (see section 5.4.2).

The following table shows the values of Ethertype field:

Protocol

Value

BroadR-Reach

0x2082

FlexRay

0x2083

LIN

0x2084

CAN

0x2085

The following table shows the values of Port field when Ethertype is 0x2082 (BroadR-Reach frames):

Port

Value

BR 1A

0x01

BR 1B

0x02

BR 2A

0x03

BR 2B

0x04

BR 3A

0x05

BR 3B

0x06

BR 4A

0x07

BR 4B

0x08

BR 5A

0x09

BR 5B

0x0A

BR 6A

0x0B

BR 6B

0x0C

The following table shows the values of Port field when Ethertype is 0x2085 (CAN frames):

Port

Value

CAN A

0x01

CAN B

0x02

CAN C

0x03

CAN D

0x04

CAN E

0x05

In the case that the Ethertype value is 0x2083 (FlexRay frames) or 0x2084 (LIN frames), the Port field will be 0x01.

Page 29

Page 28 of 43

6.1 Structure of the BroadR-Reach payload

The following table shows the structure of a BroadR-Reach payload encapsulated in a 100BASET1_SPY RAW frame:

Note: The Zero Padding length depends of the Length Field. There will be Zero Padding if Payload

length is less than the minimum RAW Ethernet Payload size (46 bytes).

The following image shows an example of a BroadR-Reach payload frame encapsulated in a 100BASET1_SPY RAW frame, with header:

Field Name

No. Of Bytes

Value

Destinacion MAC Address

Source MAC Address

Length

Payload

Its length depends on Length Field

CRC 4

Zero Padding

Page 30

Page 29 of 43

6.2 Structure of the CAN payload

The following table shows the structure of a CAN payload encapsulated in a 100BASET1_SPY RAW frame:

Note: The Control Field byte contains the following information about the CAN reception state:

7 6 5 4 3 2 1

Reserved

CRC

Reserved

IDE

Reserved

RTR

Reserved

ACK

o ACK: A ‘1’ value in this bit indicates if there was an acknowledge during the reception of the

CAN frame.

o RTR: A ‘1’ value in this bit indicates if the CAN frame is a remote frame. In this case, the

LENGTH field will be 0x00, and there is no any payload.

o IDE: A ‘1’ value in this bit indicates if the CAN frame ID is in standard (11 bits) or extended

format (29 bits).

o CRC: A ‘1’ value in this bit indicates if there was any CAN CRC error during the reception of

the CAN frame.

Note: The Zero Padding length depends of the Length Field. There will be Zero Padding if CAN

Payload length is less than the minimum RAW Ethernet Payload size (46 bytes). There is zero padding if CAN Length is less than 48 bytes.

The following image shows an example of a CAN payload frame encapsulated in a 100BASET1_SPY RAW frame, without zero padding:

Field Name

No. Of Bytes

Value

Control Field

Contains information about the CAN reception state

Identifier

Received CAN Identifier

LENGTH

Length of the CAN frame payload (in bytes)

PAYLOAD

0 to 64

Received Can Payload

CRC 3 Received CAN CRC

Zero Padding

Page 31

Page 30 of 43

6.3 Structure of the LIN payload

The following table shows the structure of a LIN payload encapsulated in a 100BASET1_SPY RAW frame:

Note: The Error Field byte contains the following information about the LIN reception state:

7 6 5 4 3 2 1

Reserved

Parity

Error

Reserved

Collision

Error

Reserved

Checksum

Error

o Checksum Error: A ‘1’ value in this bit indicates if there was a checksum error during the re-

ception of the LIN frame.

o Collision Error: A ‘1’ value in this bit indicates if there was a collision during the reception of

the LIN frame. In this case, the received payload is not valid.

o Parity Error: A ‘1’ value in this bit indicates if there is a parity error in the Protected ID.

Note: If 100BASET1_SPY LIN Port is working as SPY/SLAVE, the length will be 0x00 and there will not

be payload is there is not any slave response to the LIN Master ID.

Field Name

No. Of Bytes

Value

Error Field

Contains information about the LIN reception error state

Identifier

Received LIN Identifier

LENGTH

Length of the LIN frame payload (in bytes)

PAYLOAD

1 to 8

Received LIN Payload

Checksum

Received LIN checksum

Zero Padding

Page 32

Page 31 of 43

Note: The Zero Padding length depends of the Length Field. There will be Zero Padding if LIN Payload

length is less than the minimum RAW Ethernet Payload size (46 bytes). There is always zero padding in LIN case due to the LIN maximum length (8 bytes).

The following image shows an example of a LIN payload frame encapsulated in a 100BASET1_SPY RAW frame, in the case of a SLAVE response to a MASTER ID request:

The following image shows an example of a LIN payload frame encapsulated in a 100BASET1_SPY RAW frame, in the case that there is not any SLAVE response to a MASTER ID:

Page 33

Page 32 of 43

6.4 Structure of the FlexRay payload

The following table shows the structure of a FlexRay payload encapsulated in a 100BASET1_SPY RAW frame:

Note: A single Payload encapsulated in a 100BASET1_SPY RAW Ethernet Frame can have several IDs

(See example below). For every single ID, LENGTH gives the length of the payload for that specific ID.

Note: DIRECTION specifies if the frame is received (DIRECTION ‘0’) or transmitted (DIRECTION ‘1’) for

a specific ID. In the case of FlexRay, this field will be 0. The device is not able to transmit FlexRay frames.

The following image shows an example of a FlexRay payload frame encapsulated in a 100BASET1_SPY RAW frame. In this case, the payload contains information about 6 different IDs with the same cycle time.

Field Name

No. Of Bytes

Value

CYCLE

Time cycle in which the frame was received

MESSANGE WORD LENGTH

Length of the whole FlexRay frame payload

FRAME ID

Received Frame IDs

DIRECTION

Frame Direction

FRAME WORD LENGTH

Length of the FlexRay frame payload for a specific ID

PAYLOAD

Depends of LENGTH field

Page 34

Page 33 of 43

6.5 100BASET1_SPY LUA Installation Guide

In order to dissect the 100BASET1_SPY RAW Ethernet Frames, a LUA file for Wireshark is available on Technica Engineering website. To install the LUA file in Wireshark, the user must follow the next steps:

1. Close Wireshark in case that the program is running on PC.

2. Download the .ZIP file that contains all the LUA files, through this website:

http://www.technica-engineering.de/wp-content/uploads/2015/09/BroadR-Reach-SPYWireshark-Dissector.zip

3. Extract the downloaded ZIP file. This file should contain the following LUA files:

100BASET1_SPY_ETH_wrapper_BR.lua 100BASET1_SPY_ETH_wrapper_CAN.lua 100BASET1_SPY_ETH_wrapper_FR.lua 100BASET1_SPY_ETH_wrapper_LIN.lua

4. Copy or move the four LUA files in Wireshark plugins folder. The path should be: C:\Program

Files\Wireshark\plugins\(Wireshark Version Number).

Note: Wireshark Version Number depends on the the Wireshark version installed on PC.

Page 35

Page 34 of 43

5. In order to copy or move the LUA files to the specified Wireshark plugins folder,

Administrator rights will be needed. In that case, the following window should appear. Press Continue to proceed with the copy.

6. Run Wireshark.

Page 36

Page 35 of 43

7 UseCases

7.1 100BaseT1_SPY UseCase

The traffic of two BroadR-Reach ECUs is forwarded through the 100BASET1_SPY with a constant delay of only 2us. The delay is independent of the frame size of the Ethernet packets. There is no time jitter on the delay. The used bandwidth has no influence on the delay.

The traffic of two pairs of BroadR-Reach (so a total of four ports) of forwarded to one Gigabit Port. The PC/Datalogger is not able to send data. The RJ45 Ports are output only. Each RJ45 Port outputs only one 100 Mbit Stream of one of the ECUs.

This setup (Four on One) is implemented three times in one 100BASET1_SPY. So a total of 12 BroadRReach Ports and 3 Gigabit Ports are used for this.

Page 37

Page 36 of 43

8 Hardware Variants

8.1 BroadR-Reach Analog Filter

All filter versions are compatible with each other.

The Broadcom BCM89811 PHY with integrated low pas filter is used. For EMC and Bus termination the following filter is mounted on BrodR-Reach lines:

8.2 Debug connector

There is a debug connector on the front side of the case near the SD card slot. This small connector is only for customer service purpose.

Warning: Do not connect anything to this port.

Page 38

Page 37 of 43

8.3 Startup Time

TBD

Note: On the RJ45 gigabit ports the Linkup time is about 3 to 4 seconds. This is because of IEEE Auto

Negotiation which has to be done in gigabit mode.

Page 39

Page 38 of 43

9 Application Firmware Update

The user can download the latest firmware and documentation for the 100BASET1_SPY here:

http://www.technica-engineering.de/SPY

Note: If The user updates the application the bootloader should also be updated to the latest ver-

sion.

Warning: Not following these instructions may cause erroneous states of the device. The user will

have to send it back to Technica Engineering for repair. Technica Engineering may charge support fees for this service.

Note: The user needs to have administration privileges on a Windows PC to be able to do the firm-

ware update on the 100BASET1_SPY

The application firmware of the device may be updated by the following process:

1. Power up the device by a stable 12 Volt DC power supply. Do not switch off the power supply

during the update process.

2. It is recommended to connect the Wake-up line (Pin 8 of the black MQS connector) to 12 Volt

of the same power supply to make sure the ECU is awake during update.

3. Disconnect all other Ethernet, CAN, FlexRay, LIN and BroadR-Reach links from the

100BASET1_SPY.

4. Disable the Firewall of the Windows PC. Set the network device of the PC to the same subnet

as the 100BASET1_SPY. (For example 192.168.0.100 and 255.255.0.0)

5. Check that your firmware package The user received from Technica Engineering contains the

following files: redtool.exe microcontroller.crc.srec redboot.srec spy.srec UpdateAll.bat

The user will need to have java installed on the PC.

6. Check that the “Host” LED toggles slowly (so the device is running in application mode).

7. Check that the website at 192.168.0.49 can be accessed (or whatever the IP address of the

100BASET1_SPY is configured for).

8. Run UpdateAll.bat file in Administrator mode.

Note: First, the device will be in bootloader mode. The Host LED1 is blinking fast when in this

mode.

Note: during the update process the Host LED1 will stop to blink. This is a normal condition.

Do not reset the device! The update process will last about one minute. When the update is finished the Host LED will toggle slowly again.

Page 40

Page 39 of 43

9. The user can re-activate your Windows firewall after successful update.

. . .

-------------------------------------------------------C:\_Altera_SPY2\Calypso_FW\100BASET1_SPY-Release-v1.1 Connect new device. Make sure firewall is disabled.

-------------------------------------------------------Drücken Sie eine beliebige Taste . . .

Process started.....

======================================================== Old Bootloader Version: ======================================================== Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Non-certified release, version 2.0 - built 09:57:49, Jul 28 2015 Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Testing TFTP server tftpServer ready. Port: 69 tftpServer: 127.0.0.1 requested file redboot-updater.srec [****************************************] TFTP transfer finished TFTP server ok Loading test file... tftpServer: 192.168.0.49 requested file redboot-updater.srec [***********************TFTP transfer finished Test File loaded successfully Updating application Erasing flash... Flash erased Loading file... tftpServer: 192.168.0.49 requested file redboot-updater.srec [****************************************] TFTP transfer finished File loaded successfully Run application... Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Testing TFTP server tftpServer ready. Port: 69 tftpServer: 127.0.0.1 requested file redboot.srec [****************************************] TFTP transfer finished TFTP server ok Loading test file... tftpServer: 192.168.0.49 requested file redboot.srec [************************TFTP transfer finished Test File loaded successfully Updating redboot Erasing flash... Flash erased Loading file... tftpServer: 192.168.0.49 requested file redboot.srec [****************************************] TFTP transfer finished File loaded successfully Run application... ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NEW Bootloader Version: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Non-certified release, version 2.0 - built 17:04:51, Aug 19 2015 Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Testing TFTP server

Page 41

Page 40 of 43

tftpServer ready. Port: 69 tftpServer: 127.0.0.1 requested file microcontroller.crc.srec [****************************************] TFTP server ok Loading test file... TFTP transfer finished tftpServer: 192.168.0.49 requested file microcontroller.crc.srec [***TFTP transfer finished ] Test File loaded successfully Updating application Erasing flash... Flash erased Loading file... tftpServer: 192.168.0.49 requested file microcontroller.crc.srec [****************************************] TFTP transfer finished File loaded successfully Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Testing TFTP server tftpServer ready. Port: 69 tftpServer: 127.0.0.1 requested file spy.srec [****************************************] TFTP server ok Updating FPGA Erasing flash... TFTP transfer finished Flash erased Loading file... tftpServer: 192.168.0.49 requested file spy.srec [****************************************] TFTP transfer finished File loaded successfully Connecting to 192.168.0.49:9000 (1). Connected Sending ^C Run application at address 0x1006b40... Drücken Sieeine beliebige Taste . . .

In the case that the IP Address of the device is changed, the user can restore the IP to the default one following the next steps:

1. Follow steps 1 to 7 described before.

2. Open a DOS-Box in Administrator mode and go to the local folder where the firmware ZIP

files were extracted.

3. Execute the following commands:

redtool.exe -t <IP Address of the device> -e

Note: The device will be in bootloader mode. The Host LED1 is blinking fast when in this

mode.

redtool.exe -t <IP Address of the device> -r

Note: The device will be in Application mode. The LEDs will work as usual again.

redtool.exe -t <IP Address of the device> - a 192.168.0.49

Page 42

Page 41 of 43

10 Frequently Asked Questions – FAQ

Q: What is the delay time for Ethernet packets through the 100BASET1_SPY? A: The propagation delay of the 100BASET1_SPY is constant 2us between two BroadR-Reach Ports

in SPY mode.

Q: Is AVB supported? A: As the delay through the 100BASET1_SPY between two BroadR-Reach ports in only 2 us and

constant the 100BASET1_SPY will not influence a AVB time synchronous network negatively.

Q: After a firmware update the host LED 2 is still blinking fast. What to do? A: The firmware update failed and the host is still in bootloader mode. Please restart the device and try to update the application again as described in this manual.

Q: One of the BroadR-Reach is marked as red in the website, and I can see the message “The port is not working”. Where is the problem? A: It can be a hardware or software problem. In this last case, The user only need to restart the device. If the problem continues after restarting, is a hardware problem, and The user should contact us for more support.

Q: Why is the Ethernet Configuration Port not blinking? A: Please, check the Ethernet Adapter configuration, and follow the instructions as described in this manual, assigning the correct IP and subnet mask values.

Q: After updating the firmware version, the FPGA LED 2 is not blinking. A: There was an error during the firmware installation, and the FPGA has no software, and the next message will be shown on the webpage of the device:

Failed to flash the FPGA. Please try updating the board again!

In this case, please wait a few seconds until the HOST LED 1 is blinking and there is link up on Host Ethernet Port, and then update again the firmware version.

Q: The device is not able to log in Wireshark, even if the website configuration seems to be right. A: Some Ethernet Adapters must have the VLAN & Packet Priority option disabled. Please, change this configuration, going to Ethernet Adapter Properties/Advanced/Packet Priority & VLAN. If this option is enabled, just disabled. Otherwise, it should be enabled.

Please, check also that there is not any IP Address configured on the Ethernet Adapter, and the Windows Firewall is disabled.

Note: This last solution does not work with Intel Ethernet Adapters.

Q: I have problems with the website user interface. A: The website is tested with Firefox and Internet Explorer. Firefox is preferred. Chrome is not supported.

Page 43

Page 42 of 43

11 Contact

In the „Contact Tab“ information is displayed how to contact us if The user need service.

If The user have any questions regarding this product, please feel free to contact us:

Technica Engineering GmbH Leopoldstr. 236 80807 München Germany

Fax: +49-89-34290265

[email protected]

www.technica-engineering.de