Skip to end of metadata
Go to start of metadata


AUTOSAR DLT Protocol Standard

The DLT standard used in the GENIVI DLT implementation is based on AUTOSAR DLT Standard.

[[AUTOSAR DLT Standard][1]]

The GENIVI DLT standard extends the AUTOSAR protocol specification by some extensions and some smaller modifications.

This Specification describes thesse modifications and extensions.

GENIVI Standardised Ids

The following ECU IDs are predefined in GENIVI:

ECU IDDescription
DLTVThese messages are generated by the DLT Viewer
DLOGThese messages are generated by the Data Logger

The following Application IDs are predefined in GENIVI:

Application IDDescription
DLTSDLT System

Serial Transport Header

Overview

DLT Control Messages Extension

Overview

GENIVI DLT uses some additional control messages, which are not defined in the DLT standard. This chapter describes the additional control messages used in the GENIVI DLT implementation.

NameService Id
Unregister Context0xf01
Connection Info0xf02
Timezone0xf03
Marker0xf04

Unregister Context

Connection Info

Timezone

Marker

Segmented Network Protocol

Overview

The DLT Messages in GENIVI are limited to a message size of 2048 Bytes. If you want to trace bigger Network messages, these message has to be segmented into smaller messages. GENIVI DLT implemnets are segmentation protocol for Network messages

Network Trace API

The following API is used to trace network messages smaller than 2048 Bytes including the DLT message Header. If the message is bigger the message is not send.

DLT_TRACE_NETWORK(CONTEXT,TYPE,HEADERLEN,HEADER,PAYLOADLEN,PAYLOAD)

The following API can be used to trace network messages bigger than 2048 Bytes including the DLT message Header. If the message is bigger than 2048 Byte the message is truncated to the maximum DLT message size.

DLT_TRACE_NETWORK_TRUNCATED(CONTEXT,TYPE,HEADERLEN,HEADER,PAYLOADLEN,PAYLOAD)

The following API can be used to trace network messages bigger than 2048 Bytes including the DLT message Header. If the message is smaller than 2048 Bytes the message is send in a single Network trace message. If it is longer than 2048 Bytes is is segmented into several smaller messages, see segmentation protocol below.

DLT_TRACE_NETWORK_SEGMENTED(CONTEXT,TYPE,HEADERLEN,HEADER,PAYLOADLEN,PAYLOAD)

Network Trace Protocol

For sending network messages the DLT message type network is used as defined in the AUTOSAR DLT standard. Dependent on the size of the network message, the message is send in a single message or segmented into several messages.

Single Network Message

The single network trace message consists of two payload parameters wit the type raw buffer. The first one is the header, the second one is the payload.

NoParameterTypeDescription
1HeaderRaw DataThe Header block of the network message
2PayloadRaw DataThe Payload block of the network message

Truncated Network Message

The truncated network message has the folowing message format:

NoParameterTypeDescription
1IdentifierStringIdentifier of the message with content "NWTR"
2HeaderRaw DataThe Header block of the network message
3Payload SizeUINT32The original size of the payload message
4Truncated PayloadRaw DataThe truncated payload

Segmented Network Message

The following message is send as the first message of a segmented message. This message contains the header of the network message and further information about the whole network message. For each segmented message of a network message the Indentifier must be unique.

NoParameterTypeDescription
1IdentifierStringIdentifier of the message with content "NWST"
2HandleUINT32Unique handle for each Network message
3HeaderRaw DataThe Header block of the network message
4Payload SizeUINT32The original size of the payload message
5Number of chunksUINT16The number of payload chunks to be send
6Chunk Max SizeUINT16The size of a single payload chunk, the last chunk can be smaller

The payload of the network message is segmented into several chunks. Each chunk has a fixed size defined in the first message. The last chunk of the message can be smaller. A sequence counter is used for each network message chunk.

NoParameterTypeDescription
1IdentifierStringIdentifier of the message with content "NWCH"
2HandleUINT32Unique handle for each Network message
3Sequence numberUINT16The sequence number of the Chunk starting by zero and increased for each chunk
4Payload chunkRaw DataThe payload chunk

A final message terminates the network transport of a segmented network message.

NoParameterTypeDescription
1IdentifierStringIdentifier of the message with content "NWEN"
2HandleUINT32Unique handle for each Network message

Tracing DBus Protocol

The type variable must be set to the value DLT_NW_TRACE_IPC.

The DBus message data must be send via the the payload parameter. The header parameter can be stay empty. Optionally the DBus message can be split up into Header and Payload block.

File Transfer protocol

(No information here yet)



  • No labels