6 Allocation of Buffer Memories
6.23 [BFM #750 to #859] Emergency Message Buffer
121
FX
3U
-CAN User's Manual
1
Introduc
tion
2
Specifi
cations
3
Inst
allati
on
4
Wi
rin
g
5
Introduc
tion of
Functions
6
All
ocation of
B
uff
er
Memor
ies
7
Interface and
D
evice P
rofile
(40
5 mode)
8
Lift Appl
icati
on
P
ro
file
(417 M
ode)
9
CAN
Layer 2
Mode
10
Comm
and
Interface
6.23
[BFM #750 to #859] Emergency Message Buffer
The FX
3U
-CAN will store the Emergency messages which are received from the bus to an internal buffer. This
buffer can store up to 22 emergency messages and is separated into an 11 message stack buffer (BFM #750
to #804) and an 11 message ring buffer (BFM #805 to #859). The stack buffer will store the first 11
emergency messages received after Power On or after the Emergency message buffer was cleared the last
time. The ring buffer will store the next eleven Emergency messages; all further received Emergency
telegrams will overwrite the oldest message in the ring buffer. The stack buffer will not be overwritten.
Note
To ensure that the EMCY data is handled in a consistent way, it is necessary to set in BFM #20 bit 0 or 12 to
ON before reading the EMCY data (FROM).
When clearing the entire buffer, write H0 to BFM #750.
BFM No.
Name
Description
High Byte
Low Byte
BFM #750
Node ID
stack
buffer
The Node-ID number which sent the emergency message to the network is displayed.
BFM #751
EMERGENCY data
Emergency error code
*1
(oldest message)
BFM #752
EMERGENCY data
1st byte of Manufacturer-specific error
code
*2
Error register
→
For Error register (object H1001),
refer to Subsection 5.6.2
BFM #753
EMERGENCY data
3rd byte of Manufacturer-specific error
code
*2
2nd byte of Manufacturer-specific error
code
*2
BFM #754
EMERGENCY data
5th byte of Manufacturer-specific error
code
*2
4th byte of Manufacturer-specific error
code
*2
...
..
...
..
...
..
BFM #800
Node ID
The Node-ID number which sent the emergency message to the network is displayed.
BFM #801
EMERGENCY data
Emergency error code
*1
BFM #802
EMERGENCY data
1st byte of Manufacturer-specific error
code
*2
Error register
→
For Error register (object H1001),
refer to Subsection 5.6.2
BFM #803
EMERGENCY data
3rd byte of Manufacturer-specific error
code
*2
2nd byte of Manufacturer-specific error
code
*2
BFM #804
EMERGENCY data
5th byte of Manufacturer-specific error
code
*2
(newest message)
4th byte of Manufacturer-specific error
code
*2
(newest message)
BFM #805
Node ID
ring
buffer
The Node-ID number which sent the emergency message to the network is displayed.
(oldest message)
BFM #806
EMERGENCY data
Emergency error code
*1
BFM #807
EMERGENCY data
1st byte of Manufacturer-specific error
code
*2
Error register
→
For Error register (object H1001),
refer to Subsection 5.6.2
BFM #808
EMERGENCY data
3rd byte of Manufacturer-specific error
code
*2
2nd byte of Manufacturer-specific error
code
*2
BFM #809
EMERGENCY data
5th byte of Manufacturer-specific error
code
*2
4th byte of Manufacturer-specific error
code
*2
...
..
...
..
...
..
BFM #855
Node ID
The Node-ID number which sent the emergency message to the network is displayed.
BFM #856
EMERGENCY data
Emergency error code
*1
BFM #857
EMERGENCY data
1st byte of Manufacturer-specific error
code
*2
Error register
→
For Error register (object H1001),
refer to Subsection 5.6.2
BFM #858
EMERGENCY data
3rd byte of Manufacturer-specific error
code
*2
2nd byte of Manufacturer-specific error
code
*2
BFM #859
EMERGENCY data
5th byte of Manufacturer-specific error
code
*2
(newest message)
4th byte of Manufacturer-specific error
code
*2
(newest message)
Содержание FX3U-CAN
Страница 1: ...FX3U CAN USER S MANUAL ...
Страница 2: ......
Страница 6: ...Safety Precautions Read these precautions before use 4 MEMO ...
Страница 227: ......