GM WORLDWIDE ENGINEERING STANDARDS
Template For ENG STDS
GMW17753
© Copyright 2017 General Motors Company All Rights Reserved
January 2017
Page 4 of 16
3.3.2 ISO15765_FD_PS Message Structure. The message structure used for ISO15765_FD_PS is identical to
ISO15765_PS (SAE J2534-1, V04.04) with the exception of:
1. The Pass-Thru Interface shall permit the usage of Mixed Format Frames on an ISO15765_FD_PS
channel. This allows the simultaneous reception and transmission of ISO15765_FD_PS messages and
unformatted CAN FD frames on the ISO15765_FD channel. In Mixed mode, the ProtocolID (in the
PASSTHRU_MSG structure) is used to identify if the ISO_15765 transport layer is applicable for the
associated message.
2. API calls that cause a message transmission of an ISO15765_FD_PS message shall limit the maximum
frames size to the value defined by CAN_FD_TX_DATA_LENGTH. All frames containing more than 8
(eight) data bytes shall be padded out to the next valid frame boundary with the value of
ISO15765_PAD_VALUE. Frames with less than 8 (eight) data bytes may also be padded out to 8 (eight)
data bytes if the TxFlag ISO15765_FRAME_PAD is set.
• ProtocolID: Shall be set to ISO15765_FD_PS.
• DataSize: The minimum value for the <DataSize> of an ISO15765_FD_PS message is dependent on the
<TxFlag> ISO15765_ADDR_TYPE. See Table 5.
Table 5: <DataSize> ISO15765_FD_PS
ISO15765_ADDR_TYPE Minimum Value of <DataSize> Maximum Value of <DataSize>
0 4
4128
Note 1
1 5
4128
Note 1
Note 1: The maximum value for the <DataSize> of an ISO15765_FD_PS message is limited by the Pass-Thru message structure to
4128 bytes. However, it is possible for an application to transmit and receive larger messages through an extended message buffer.
• TxFlags: The following table identifies the valid TxFlags for an ISO15765_FD_PS message. Setting any
other Flag for a CAN_FD_PS message will cause the Pass-Thru Interface to return an ERR_INVALID_MSG.
See Table 6.
Table 6: <TxFlags> ISO15765_FD_PS
Definition Bit Value
CAN_FD_BRS 24 0 = All the frames of the message shall be transmitted with the data phase at the
arbitration speed.
Note 1
1 = All the frames of the message shall be transmitted with the data phase at the
CAN_FD_DATA_PHASE_RATE.
Note 1
CAN_FD_FORMAT 25 0 = All the frames of the message shall be transmitted using the CAN 2.0 format.
1 = All the frames of the message shall be transmitted using the CAN FD format.
CAN_29BIT_ID 8 As defined by CAN in J2534, V04.04.
ISO15765_ADDR_TYPE 7 As defined by CAN in J2534, V04.04.
ISO15765_FRAME_PAD 6 As defined by CAN in J2534, V04.04 for frames less than 8 (eight) data bytes.
Frames with more than 8 (eight) data bytes shall use default CAN FD padding.
(The frames are padded to the next CAN FD frame boundary.)
Note 1: This flag will be ignored unless CAN_FD_FORMAT flag is set to 1.
• RxStatus: Table 7 identifies the valid RxStatus bits for a received message and shows which bits are used
as indications.
Copyright General Motors Company
Provided by IHS Markit under license with General Motors Company
Sold to:SHANGHAI DING AUTOMATION LLC. [213189100001] - CHANGMAO.WU@DING-AUTO.COM
Not for Resale,2018-02-13 01:36:59 UTC
Reproduction, distribution or publication of these standards is expressly prohib
--``````,,,,,,`,``,`,``-`-``,```,,,`---