Table of Contents
Advertisement
FX
-J1939 User's Manual
3U
BFM No.
BFM #506,
#507
BFM #508
BFM #509
BFM #510
BFM #511
BFM #3000 HFFFF
BFM #3001
to #3010
BFM #1900,
#1901
BFM #1902 H0005
BFM #1903
to #1906
*1.
The Configuration values equal the Values displayed in Offline.
*2.
The low byte "nn" is replaced by the current node address of the FX
not own a valid address due to an address conflict or if the address claiming was not completed, HFE
is shown.
2) Tx/Rx User messages and one RUN>STOP message configured and Remote Address to ECU Name
assignment for Node B
BFM No.
BFM #500,
#501
BFM #502
BFM #503
BFM #504
BFM #505
BFM #506,
#507
BFM #508
BFM #509
BFM #510
BFM #511
BFM #3000 H88
BFM #3001 K1
BFM #3002 K5
BFM #3003 K127
BFM #3004 K0
BFM #3005 K0
BFM #3006 K1
BFM #3007 K2047
BFM #3008 K0
BFM #3009 HFFFF
BFM #3010 H001F
BFM #1900,
#1901
BFM #1902 H0005
BFM #1903
to #1906
*3.
The Configuration values equal the Values displayed in Offline.
*4.
The low byte "nn" is replaced by the current node address of the FX
not own a valid address due to an address conflict or if the address claiming was not completed, HFE
is shown.
*5.
The 2nd byte "mm" displays the node address currently in use. When the node address becomes
invalid (e.g. due to the address change from H88 > H89 in this example), the address is set to HFE.
60
*1
Configuration Effect
Configuration
HB280
RX Message
K-1
PGN HB280 with 8 data
H88
bytes
Source must be node H88
K0
K8
No ECU name assigned
H0000
Run>STOP message
*2
H0CB3.88nn
PGN HB388
(Target address H88)
Sent with priority 6 and 5
Any data
data bytes
*3
Configuration Effect
Configuration
HB188
TX Message
PGN HB188
K2
(Target address H88)
K6
Sent with priority 6 and 8
K100
data bytes every second.
K8
HB280
RX Message
K-1
PGN HB280
H88
with 8 data bytes
Source must be node H88
K0
K8
Node "B" identified by
"ECU Name Node B"
Is assigned to node
Address H88 in the
configuration:
Any TX destination "H88"
is assigned to node "B"
Any Rx source "H88" is
assigned to node "B"
Run>STOP message
*4
H0CB3.88nn
PGN HB388
(Target address H88)
Sent with priority 6 and 5
Any data
data bytes
6.2 [BFM #500 to #973] Configuration Area
Behaviour If Node "B" Sends Address
Display in Online
No change:
!!The source must still be H88!!
Node "B" will transmit any messages with
the new node address H89 >>
communication fails!
Same as in
Configuration/Offline
n.a.
No change:
RUN>STOP message destination is still
H88.
!!High chance that node "B" will not receive
this message!!
-J1939. If the FX
3U
Behaviour If Node "B" Sends Address
Display in Online
Target address is changed from H88 to
H89.
Same as in
Configuration/Offline
Source is changed from H88 to H89,
messages from Node "B" will still be
received.
BFM #3000
Any address claim using the "ECU Name
Displays H8088 until node
Node B" is causing an adjustment of all
"B" sends a valid address
messages exchanged with node "B".
claim, afterwards the
All messages sent to address H88 before,
current node address (e.g.
are sent to address H89 now.
H89) is displayed Other
All Messages received from address H88,
BFMs same as in
are expected to be sent from address H89
Configuration/Offline
now.
*4*5
H0CB3.mmnn
New address of node "B" is used as
destination
H0005
Node "B" will receive the RUN>STOP
message.
Any data
-J1939. If the FX
3U
6 J1939 Communication Mode
Claim for Address H89
-J1939 does
3U
Claim for Address H89
-J1939 does
3U
Advertisement
Table of Contents
