The following negative response codes shall be implemented for this service. The circumstances under which each response code would occur are documented in Table 131. The listed negative responses shall be used if the error scenario applies to the server.
--``,`,,,,,,`,,,`,``,,`,,```,`,`-`-`,,`,,`,`,,`---
Table 131 — Supported negative response codes
NRC Description Mnemonic
0x12 sub-functionNotSupported SFNS
This NRC shall be sent if the sub-function parameter is not supported.
0x13 incorrectMessageLengthOrInvalidFormat IMLOIF
This NRC shall be sent if the length of the message is wrong.
0x22 conditionsNotCorrect CNC
This NRC shall be returned if the criteria for the requested LinkControl are not met.
0x24 requestSequenceError RSE
This NRC shall be returned if the client requests the transition of the mode of operation without a preceding verification step, which specifies the mode to transition to.
0x31 requestOutOfRange ROOR
This NRC shall be returned if
the requested linkControlModeIdentifier is invalid;
the specific modeParameter (linkRecord) is invalid;
9.11.5 Message flow example(s) LinkControl
9.11.5.1 Example #1 - Transition baudrate to fixed baudrate (PC baudrate 115200 kBit/s) 9.11.5.1.1 Step#1: Verify if all criteria are met for a baudrate switch
Table 132 defines the LinkControl request message flow example #1 - step #1.
Table 132 — LinkControl request message flow example #1 - step #1 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = verifyModeTransitionWithFixedParameter, suppressPosRspMsgIndicationBit = FALSE
0x01 VMTWFP
#3 linkControlModeIdentifier = PC115200Baud 0x05 BI_PC115200
Table 133 defines the LinkControl positive response message flow example #1 - step #1.
Table 133 — LinkControl positive response message flow example #1 - step #1 Message direction server → client
Message Type Response
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Response SID 0xC7 LCPR
#2 linkControlType = verifyModeTransitionWithFixedParameter 0x01 VMTWFP
9.11.5.1.2 Step#2: Transition the baudrate
Table 134 defines the LinkControl request message flow example #1 - step #2.
Table 134 — LinkControl request message flow example #1 - step #2 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = transitionMode,
suppressPosRspMsgIndicationBit = TRUE
0x83 TM
There is no response from the server(s). The client and the server(s) have to transition the baudrate of their communication link.
9.11.5.2 Example #2 - Transition baudrate to specific baudrate (150kBit/s) 9.11.5.2.1 Step#1: Verify if all criteria are met for a baudrate switch Table 135 defines the LinkControl request message flow example #2 - step #1.
Table 135 — LinkControl request message flow example #2 - step #1 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = verifyModeTransitionWithSpecificParameter, suppressPosRspMsgIndicationBit = FALSE
0x02 VMTWSP
#3 linkRecord [ modeParameterHighByte ] (150kBit/s) 0x02 MPHB
#4 linkRecord [modeParameterMiddleByte ] 0x49 MPMB
#5 linkRecord [modeParameterLowByte ] 0xF0 MPLB
Table 136 defines the LinkControl positive response message flow example #2 - step #1.
Table 136 — LinkControl positive response message flow example #2 - step #1 Message direction server → client
Message Type Response
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Response SID 0xC7 LCPR
#2 linkControlType = verifyModeTransitionWithSpecificParameter 0x02 VMTWSP
9.11.5.2.2 Step#2: Transition the baudrate
Table 137 defines the LinkControl request message flow example #2 - step #2.
--``,`,,,,,,`,,,`,``,,`,,```,`,`-`-`,,`,,`,`,,`---
Table 137 — LinkControl request message flow example #2 - step #2 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = transitionMode,
suppressPosRspMsgIndicationBit = TRUE
0x83 TM
There is no response from the server(s). The client and the server(s) have to transition the baudrate of their communication link.
9.11.5.3 Example #3 - Transition FlexRay cycle design to 'Programming'
The following example reflects a scenario, where a FlexRay network cycle design is transitioned into an optimized 'programming' mode (e.g., utilizing an enhanced dynamic segment for programming).
9.11.5.3.1 Step#1: Verify if all criteria are met for a scheduler switch Table 138 defines the LinkControl request message flow example #3 - step #1.
Table 138 — LinkControl request message flow example #3 - step #1 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = verifyModeTransitionWithFixedParameter, suppressPosRspMsgIndicationBit = FALSE
0x01 VMTWFP
#3 linkControlModeIdentifier = ProgrammingSetup 0x20 PROGSU
Table 139 defines the LinkControl positive response message flow example #3 - step #1.
Table 139 — LinkControl positive response message flow example #3 - step #1 Message direction server → client
Message Type Response
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Response SID 0xC7 LCPR
#2 linkControlType = verifyModeTransitionWithFixedParameter 0x01 VMTWFP
9.11.5.3.2 Step#2: Transition to programming scheduler
Table 140 defines the LinkControl request message flow example #3 - step #2.
--``,`,,,,,,`,,,`,``,,`,,```,`,`-`-`,,`,,`,`,,`---
Table 140 — LinkControl request message flow example #3 - step #2 Message direction client→ server
Message Type Request
A_Data byte Description (all values are in hexadecimal) Byte Value Mnemonic
#1 LinkControl Request SID 0x87 LC
#2 linkControlType = transitionMode,
suppressPosRspMsgIndicationBit = TRUE
0x83 TM
There is no response from the server(s). The client and the server(s) have to transition the cycle design of the FlexRay communication link.