Table of Contents
Advertisement
FX
-J1939 User's Manual
3U
6.2.2
Example J1939 communication mode use of RUN>STOP messages and remote
address to ECU name assignment
These examples show the use of the RUN>STOP Messages in J1939 communication mode.
Additionally, the function of the Remote Address to ECU Name assignment and its effect on user Messages
and the RUN>STOP Messages is shown.
The two examples show the behaviour for the configuration below. The FX
address H80 (BFM #27) and communicates with Remote Node "B." For easier understanding, the ECU Name
of node "B" is addressed with "ECU Name Node B" instead of repeating the Values (Arbitrary Address
Capable = yes, Industry Group = K5, Vehicle System = K127, Vehicle System Instance = K0, Function = K0,
Function Instance = K1, ECU Instance = K0, Manufacturer Code = K2047 and Identity Number = H1F.FFFF).
The first User Message (BFM #500 to #505) is configured with a TX Message, the second message (BFM
#506 to #511) is configured for reception. Any other user message (BFM #512 to #973) could be used instead
with the same effect.
For this example, only the two messages are expected to be present in the user message configuration. If
additional messages are configured, the behaviour of the module may differ from the described.
The first RUN>STOP message (BFM #1900 to #1906) is used in this example, but the second to fourth (BFM
#1907 to #1927) can be used with the same effect. In this example, only a single RUN>STOP message is
expected to be configured. If the other three messages are not disabled, behaviour may be different than
described.
Note
• There is no relation between the user message numbers, RUN>STOP messages or Remote Address to
ECU Name assignments. These examples would work the same if user message 4 and 30, Run>STOP
message 3 and Remote Address to ECU Name assignment 40 are used instead of the messages 1 and 2
used for all functions in these examples.
• Both setups have advantages and disadvantages. Ensure proper behaviour of your network according to
your applications behaviour and requirements.
• The RUN>STOP message in example 2 is not transmitted if the node "B" sends a can not claim message
(node "B" could not acquire a node address) or does not send an address claim at all. As long as no valid
address for node "B" is available (e.g. BFM #1900 "mm" = HFE), the message is not sent!
"A"
FX
-J1939
3U
Node address: H80
Network
1) Tx/Rx User messages and one RUN>STOP message configured, but no Remote Address to ECU Name
assignment
BFM No.
Configuration
BFM #500,
HB188
#501
BFM #502
K2
BFM #503
K6
BFM #504
K100
BFM #505
K8
"B"
Remote node
Node address: H88
ECU name:
Arbitrary address capable field: Yes
Industry group: 5
Vehicle system: 127
Vehicle system Instance: 0
Function: 0
Function instance: 1
ECU instance: 0
Manufacturer code: 2047
Identity number: H1FFFFF
*1
Configuration Effect
TX Message
PGN HB188
(Target address H88)
Sent with priority 6 and 8
data bytes every second.
6 J1939 Communication Mode
6.2 [BFM #500 to #973] Configuration Area
-J1939 (node "A") is using node
3U
Behaviour If Node "B" Sends Address
Display in Online
No change:
!!The target address of the TX message is
Same as in
still H88!!
Configuration/Offline
If node "B" expects now to receive PGN
HB189 (target address H89),
communication fails!
Claim for Address H89
59
1
2
3
4
5
6
7
8
9
10
Advertisement
Table of Contents
