USER’S MANUAL
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block
Foreword
• This manual contains text, diagrams and explanations whi ch will guide the reader in the correct installation and
operation of the FX2N-64DNET DeviceNet Interface Block. It should be read and understood befre attempting
to install or use the unit.
• Further infomation can be found in the hardware manual for connecting main unit, FX Series Programming
Manual and manual of DeviceNet master units.
• If in doubt at any stage of the installation of FX2N-64DNET DeviceNet Interface Block always consult a profes-
sional electrical engineer who is qualified and trained to the local and national standards which apply to the
installati on site.
• If in doubt about the operation or use of FX2N-64DNET DeviceNet Interface Block please consult the nearest
Mitsubisi Electric distributor.
• This manual is subject to change without notice.
FX2N-64DNET DeviceNet
Interface Block
User’s Manual
FX2N-64DNET DeviceNet Interface Block
Manual number :JY992D86301
Manual revision :A
Date :April 2000
FX2N-64DNET DeviceNet Interface Block
ii
FX2N-64DNET DeviceNet Interface Block
iii
Guidelines for the Safety of th e User and Protection of the FX2N-64DNET
DeviceNet Interface Block.
This manual provides information for the use of the FX2N- 64DNET DeviceNet Interface Block.
The manual has been written to be used b
y
trained and competent personnel. The definition of
such a person or persons is as follows:
a) An
y
en
g
ineer who is responsible for the plannin
g
, desi
g
n and construction of automatic
equipment usin
g
the product associated with this manual, should be of a competent
nature, trained and qualified to the local and national standards required to fulfill that
role. These en
g
ineers should be full
y
aware of all aspects of safet
y
with re
g
ards to auto -
mated equipment.
b) An
y
commissionin
g
or service en
g
ineer must be of a competent nature, trained and qual-
ified to the local and national standards required to fulfill that job. These en
g
ineers
should also be trained in the use and maintenance of the completed product. This
includes bein
g
completel
y
familiar with all associated documentation for said product. All
maintenance should be carried out in accorda nce with established safet
y
practices.
c) All operators of the completed e quipment should be trained to use that pr oduct in a safe
and c oordinated manner in complian ce to estab lished safe t
y
practices. The operators
should also be familiar with documentation which is connected with the actual operation
of the completed equipment.
Note : The term ‘completed equipment’ refers to a third part
y
constructed device which con-
tains or uses the product associated with this manual.
FX2N-64DNET DeviceNet Interface Block
iv
Note’s on the Symbols Used in this Manual
At various times throu
g
h out this manual certain s
y
mbols will be used to hi
g
hli
g
ht points of
information which are intend ed to ensure the users personal safet
y
and pro tect the inte
g
rit
y
of
equipment. W henever an
y
of the follo win
g
s
y
mbols are encoun tered its associated n ote must
be read and understood. Each of the s
y
mbols used will now be listed with a brief description of
its meanin
g
.
Hardware Warnings
1) Indicates that the identified dan
g
er WILL cause ph
y
sical and propert
y
dama
g
e.
2) Indicates that the identified dan
g
er could POSSIBLY cause ph
y
sical and propert
y
dama
g
e.
3) Indicates a point of further interest or further explanation.
Software Warnings
4) Indicates special care must be taken when usin
g
this element of software.
5) Indicates a special point which the user of the associate software element should
be aware.
6) Indicates a point of interest or further explanation.
FX2N-64DNET DeviceNet Interface Block
v
• Under no circumstances will Mitsubishi Electric be liable responsible for an
y
consequential
dama
g
e that ma
y
arise as a result of the installation or use of this equipment.
• All examples and dia
g
rams shown in this manual are intended onl
y
as an aid to understand-
in
g
the text, not to
g
uaran tee operatio n. Mitsubi shi Electric will a ccept no res ponsibilit
y
for
actual use of the product based on these illustrative examples.
•Owin
g
to the ver
y
g
reat variet
y
in possible application of this equipment,
y
ou must satisf
y
y
ourself as to its suitabilit
y
for
y
our specific application.
FX2N-64DNET DeviceNet Interface Block
vi
vii
Table of Contents
Guideline.............................................................................................iii
1. Introduction............................................................................................1-1
1.1 Features of the 64DNET......................................................................................1-1
1.2 External Dimensions and Each Part Name .........................................................1-2
1.3 S
y
stem Confi
g
uration ..........................................................................................1-4
1.4 Applicable PLC. ...................................................................................................1-5
2. Wirin
g
and Mountin
g
.............................................................................2-1
2.1 Mountin
g
..............................................................................................................2-1
2.1.1 Arrangements............................................................................................................2-1
2.1.2 Mounting....................................................................................................................2-2
2.2 Wirin
g
..................................................................................................................2-3
2.2.1 Caution......................................................................................................................2-3
2.2.2 Wiring ........................................................................................................................2-4
2.2.3 Terminat in g Res is tor ........ .... .... .... .... .... .... ............ ............ ............ ............ ........... .... ..2- 4
3. Specifications........................................................................................3-1
3.1 General Specifications......................... ................................................................3-1
3.2 Power Suppl
y
Specification s ...............................................................................3-1
3.3 Performance Specifications.................................................... .................. ...........3-2
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block
viii
4. Allocation of Buffer Memories (BFMs)...................................................4-1
4.1 Buffer Memories (BFM) Lists................................. ..............................................4-2
4.2 DeviceNet LINK Enable <BFM #0> (Read/Write)................................................4-8
4.3 Module Status about Connection <BFM #1> (Read Onl
y
) ..................................4-9
4.4 Module Status about DeviceNet <BFM #2> (Read Onl
y
)..................................4-10
4.5 Number of DeviceNet UCMM Connections <BFM #3> (Read/Write)................4-11
4.6 DeviceNet Bus-off Counter <BFM #4> (Read/Write)................................ .........4-11
4.7 Number of DeviceNet Retries <BFM #5> (Read/Write).....................................4-12
4.8 FROM/TO WDT Settin
g
<BFM #6> (Read/Write)..............................................4-13
4.9 Mode Control Fla
g
s <BFM #7> (Read/Write)....................................................4-14
4.10 UCMM Client Connection Settin
g
<BFM #8 ~ #11> (Read/Write).....................4-15
4.11 UCMM Client Sendin
g
Tri
gg
er <BFM #12 ~ #15> (Read/Write) .......................4-16
4.12 UCMM Client Receivin
g
Status <BFM #16 ~ #19> (Read Onl
y
).......................4-17
4.13 UCMM Server Receivin
g
Status <BFM #20 ~ #23> (Read Onl
y
)......................4-18
4.14 Error Status <BFM #26 ~ #29> (Read Onl
y
).....................................................4-19
4.15 Module ID Code <BFM #30> (Read Onl
y
) ........................................................4-19
4.16 UCMM Client W DT switch <BFM #32 ~ #35> (Read/Write)..............................4-20
4.17 UCMM Client Connection Status <BFM #36 ~ #39> (Read Onl
y
).....................4-21
4.18 UCMM Client Communication Status <BFM #40 ~ #43> (Read Onl
y
)..............4-22
4.19 UCMM Server Communication Status <BFM # 44 ~ #47 > (Read Onl
y
) ............4-23
4.20 Baud Rate <BFM #48> (Read Onl
y
) .................................................................4-24
4.21 Master/Slave Communication Data Area <BFM #100 ~ #133>.........................4-24
4.21.1 Send Data/Receive Data Area <BFM #100 ~ #131> (Read/Write).........................4-25
4.21.2 Number of Link Points <BFM #132> (Read/Write)..................................................4-26
4.21.3 MAC ID <BFM #133> (Read Only)..........................................................................4-26
FX2N-64DNET DeviceNet Interface Block
ix
4.22 UCMM Client Communication Data Area <BFM #10000 ~ #1 6336> ................4-27
4.22.1 Send Data/Receive Data Area <BFM #100*1 ~ #131*1> (Read/Write).......4-27
4.22.2 Length of Assembly Data <BFM #132*1> (Read/Write)....................................4-29
4.22.3 Length of Sending Common Service Data <BFM #133*1> (Read/Write)..........4-29
4.22.4 Length of Receiving Data <BFM #134*1> (Read Only).....................................4-30
4.22.5 Group Selection <BFM #135*1> (Read/Write) ..................................................4-30
4.22.6 Class ID and Instance ID <BFM #136*1>..........................................................4-31
4.22.7 Attribu te ID and Service Code <BFM #137*1>..................................................4-32
4.23 UCMM Server Communication Data Area <BFM #20000 ~ #26336>...............4-33
4.23.1 Send/Receive Data Area <BFM #200*1 ~ #231*1> (Read/Write) ...............4-33
4.23.2 Length of Assembly Data <BFM #232*1> (Read/Write)....................................4-35
4.23.3 Length of Sending Common Service Data <BFM #233*1> (Read/Write)..........4-35
4.23.4 Length of Receiving Data <BFM #234*1> (Read Only).....................................4-36
4.23.5 Group Select <BFM #235*1> (Read Only)........................................................4-36
4.23.6 Class ID and Instance ID <BFM #236*1> (Read only)......................................4-37
4.23.7 Attribu te ID and Service Code <BFM #237*1> (Read only) ..............................4-37
5. DIP Switch Settin
g
.................................................................................5-1
5.1 Settin
g
DIP Switch...............................................................................................5-1
5.1.1 Mode Setting (DIP Switch: SW0, SW1).....................................................................5-1
5.1.2 Baud Rate Setting (DIP Switch: DR0, DR1)..............................................................5-2
5.1.3 MAC ID Setting (DIP Switches: NA0 ~ NA5).............................................................5-3
6. Client/Sever Communication by UCMM Connection.............................6-1
6.1 Information of UCMM Connection b
y
64DNET......................................... ...........6-1
6.2 How to Use Peer to Peer Communica tion...........................................................6-2
FX2N-64DNET DeviceNet Interface Block
x
7. Example Pro
g
ram..................................................................................7-1
7.1 S
y
stem Confi
g
uration ..........................................................................................7-1
7.2 Operation.............................................................................................................7-2
7.3 Exam ple Pro
g
ram................................................................................................7-3
7.3.1 Initial Setting..............................................................................................................7-4
7.3.2 Check ing Erro r St atu s ...... .... .... .... ............ ............ ............ ............ ............ .... ........... ..7-8
7.3.3 Input Data and Output Data for Master/Slave I/O Connection ..................................7-9
7.3.4 Input Data and Output Data for UCMM Connection................................................7-10
8. Dia
g
nostics............................................................................................8-1
8.1 Preliminar
y
Checks..............................................................................................8-1
8.2 LED Check ..........................................................................................................8-2
8.3 Error Code...........................................................................................................8-5
8.3.1 64DN ET Error Co de (BFM #7 Bit 1 is ON)....... .... .... .... .... .... ............ ............ ........... ..8-5
8.3.2 DeviceNet Error Code (BFM #7 Bit 1 is OFF) .........................................................8-18
Appendix A
EDS (Electric Data Sheet)......... ...............................................................A-1
FX2N-64DNET DeviceNet Interface Block
xi
Appendix B
Class ID, Instance ID, Attribute ID and Service Code..............................B-1
B-1: Identit
y
(0x01)........................................................................................... ...........B-1
B-2: Messa
g
e Router (0x02).......................................................................................B-2
B-3: DeviceNet (0x03).................................................................................................B-3
B-4: Assembl
y
(0x04)..................................................................................................B-5
B-5: Connection (0x05) ...............................................................................................B-6
B-6: Acknowled
g
e Handler Obje ct (2B Hex).............................................................B-12
Appendix C
List of Further Information Manual ...........................................................C-1
FX2N-64DNET DeviceNet Interface Block
xii
Introduction 1
1-1
1. Introduction
1.1 Features of the 64DNET
The FX2N-64DNET DeviceNet Interface Block (hereafter called “64DNET”) can be used to con-
nect FX0N and FX2N series pro
g
ramma ble controller to a DeviceNet net work (hereafter calle d
“DeviceNet”). The 64DNET is a slave (Group 2) on DeviceNet.
• The 64DNET passed the conformance test with A-14 for DeviceNet. (The 64DNET
conforms to the DeviceNet specifications Volume 1 release 2.0 and Volume 2 release 2.0.)
• The 64DNET can communicate to the master b
y
the Master/Slave communication (usin
g
the Master/Slave I/O connection), and can communicate to other node of supportin
g
the
UCMM connection b
y
Client/Server communication (usin
g
the UCMM connection).
• Communication Data Len
g
th;
- The Master/Slave communication will both send and receive 64 b
y
tes of data to/from the
master.
- The Client/Sever communication will both send and receive 64 b
y
tes of data to/from
each node.
• The communication method for I/O connection supports “pollin
g
”, “c
y
clic” and “chan
g
e of
state”.
• The MAC ID and baud rate is adjusted b
y
DIP switches. See chapter 5.
• The communication between the connected main unit and the internal buffer memor
y
of the
64DNET is handled b
y
FROM/TO instructions.
DeviceNet is a re
g
istered trademark of the Open DeviceNet Vendor Association, In c.
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Introduction 1
1-2
1.2 External Dimensions and Each Part Name
Dimensions: mm (inches) MASS (Wei
g
ht):Approx. 0.2 k
g
(0.44 lbs)
Accessor
y
: Special block No. label
Figure 1.1: External Dimensions
a) Groove for mountin
g
DIN rail (DIN46277) <DIN rail width: 35mm (1.38")>
b) Direct mountin
g
hole (2-φ4.5 (0.18"))
POWER
FX
2N
-64DNET
NS
MS
FROM/TO
FX2N-64DENT
SW1
SW0
DR1
DR0
NA5
NA4
NA3
NA2
NA1
NA0
Remove top cover
4(0.16")
4(0.16")
90(3.54")
87(3.43")
94(3.70")
9(0.35")
43(1.69")
80(3.15")
a)
b)
c) e)
d)
f )
g)
h)
i )
j )
k)
l )
c)
c)
b)
FG
FX2N-64DNET DeviceNet Interface Block Introduction 1
1-3
c) Connector for connectin
g
DeviceNet communication cable
Figure 1.2: Connector layout
d) Hook for mountin
g
DIN rail
e) Extension cable
f) POWER LED:
g
)FROM/TO LED
h) MS LED (Module Status LED)
i) NS LED (Network Status LED)
j) DIP switch for settin
g
the MAC ID, baud rate and operation mode. See chapter 5.
k) FG Terminal (screw terminal: M3 (0 .12"))
l) Connector for connectin
g
extension cable
V+ (Red)
CAN_H (White)
C AN _L (Blue)
Sh ield ( d rain wir e )
V- (Black)
FX2N-64DNET DeviceNet Interface Block Introduction 1
1-4
1.3 System Configuration
Figure 1.3: System Configuration
M aster station
FX
2N
-
64DNET
FX
0N
, F X
2N
,
FX
2NC
FX
2N
-
64DNET
FX
0N
, F X
2N
Slave
N etwork power
supply unit
(2 4 V D C)
: Dro p lin e
: Tru n k lin e
: T erminating resistor : Ta p: Powe r tap
SlaveSlave
FX2N-64DNET DeviceNet Interface Block Introduction 1
1-5
1.4 Applicable PLC
Table 1.1: Agreement PLC
Programmable
Controllers Description
FX0N ser ies All products
FX2N ser ies
FX2N-64DNET DeviceNet Interface Block Introduction 1
1-6
MEMO
Wiring and Mounting 2
2-1
2. Wiring and Mounting
2.1 Mounting
2.1.1 Arrangements
The 64DNET connects on the ri
g
ht side of connected main unit or extension unit/block (includ-
in
g
special function blocks). For further information of mountin
g
arran
g
ements, refer to the
hardware manual of the connected main unit.
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Wiring and Mounting 2
2-2
2.1.2 Mounting
The mountin
g
method of the 64DNET can be DIN rail mountin
g
or direct wall mountin
g
.
1) DIN rail mountin
g
•Ali
g
n the upper side of the DIN rail mountin
g
g
roove of the 64DNET with a DIN rail*1 (),
and push it on the DIN rail(). See Fi
g
ure 2.1.
• When removin
g
the 64DNET from the DIN rail, the hook for DIN rail is pulled (), and the
64DNET is removed (). See Fi
g
ure 2.1.
Figure 2.1: Attach to DIN Rail and Remove from DIN Rail
*1 Uses DIN 46277 <35mm (1.38")>
2) Direct mountin
g
to back wa lls
The 64DNET can be mounted with the M4 screw b
y
usin
g
the direct mountin
g
hole.
However, an interval space between each unit of 1 ~ 2 mm is necessar
y
.
FX2N-64DNET DeviceNet Interface Block Wiring and Mounting 2
2-3
2.2 Wiring
2.2.1 Caution
1) Do not la
y
si
g
nal cable near to hi
g
h volta
g
e power cable or house them in the same trunk-
in
g
duct. Effects of noise or sur
g
e induction ma
y
occur. Keep si
g
nal cables a safe distance
of more than 100 mm (3.94") from these power cable s.
2) The terminal screws of the 64DNET are M3 (0.12"), therefore the crimp st
y
le terminal (see
drawin
g
) suitable for use with these screws should be fitted to the cable for wirin
g
.
Figure 2.2: Crimp Terminals
3) The terminal ti
g
htenin
g
torque is 0.5 ~ 0.8 Nm. Ti
g
hten securel
y
to avoid malfunction.
4) Cut off all phases of power source before installation or performin
g
wirin
g
work in order to
avoid electric shock or dama
g
e of product.
5) Replace the provided terminal cover before suppl
y
in
g
power and operatin
g
the unit after
installation or wirin
g
work in order to avoid electric shock.
6.2 mm (0.24" )
or less
For M3 (0.12") 6.2 mm (0.24")
or less
For M3 (0.12")
FX2N-64DNET DeviceNet Interface Block Wiring and Mounting 2
2-4
2.2.2 Wiring
Connects Each color code of DeviceNet communication cable to same color part in DeviceNet
connector.
Figure 2.3: Wiring
2.2.3 Terminating Resistor
The units at each end of the Device Net must have a terminatin
g
resistor.
However, the 64DNET does not have a terminatin
g
resistance built-in.
V+ (Red)
CAN_H (White)
C AN _L (Blue)
Sh ield ( d rain wir e )
V- (Black)
FG
FX
2N
, FX
2NC
, FX
0N
Series PLC
D eviceN et communication cable
G rounding resistor 100
Ω
or
le ss ( Class D) DeviceNet connector
FX
2N
-
64DNET
Specifications 3
3-1
3. Specifications
3.1 General Specifications
3.2 Power Supply Specifications
Table 3.1: General Specifications
Items Description
General specifications excluding
Dielectric Wit hstand Voltag e Same as those of the main unit
Dielectric Wit hstand Voltag e 500 V AC > 1 min,
tested between DC powe r l i ne in the DeviceNet connec tor and
ground
Complies with EN50325 (conformance tested with A-14)
Table 3.2: Power Supply S pecifications
Items Description
Power Supply For Communica-
tion 50 mA at 24 V DC supplied from V+, V- terminals
Internal Power Supply 120 mA at 5 V DC supplied via extension cable
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Specifications 3
3-2
3.3 Performance Specifications
Table 3.3: Performance Specif ications
Items Specifications
Node Type G2 server
Sta tion Numbers 0 ~ 63
Transmission Cable Shielded twisted-pair cable conformed with
DeviceNet specifications
MAC ID 0 ~ 63
Supported Baud Rates 125 kbps, 250 kbps, 500 kbps
Maximum Cable Length See Note 1.
Communication Data
Explicit
Connection
Predefined
Master/Slave
Connection Set
Number of
Connection 1 (Group 2)
Transmis-
sion Time-out 2,000 ms (ACK time-out)
UCMM Client/
Server Connec-
tion
Number of
Connection 63/63 (Group 1, 3) <recommend group 3>
Communica-
tion Data
Length
Sending: Maximum 64 bytes /1 connection
Receiving: Maximum 64 bytes/1 connection
FX2N-64DNET DeviceNet Interface Block Specifications 3
3-3
Communication Data
I/O
Connection
Supported Communication
Type Polling, Cyclic, Change of State
Communication Data Length
Sending: Maximum 64 bytes
(Fragmentation is allowed.)
Receiving: Maximum 64 bytes
(Fragmentation is allowed.)
Applicable PLC FX2N Series, FX0N Series
Communic ation with PLC FROM/TO instruction
Number of Occupied I/O Points 8 points taken from the programmable controller
extension bus (can be either input or output)
Module ID Code K 7090
LED Indica tors
POWER LED Lit when 5 V DC power supplied from main unit or
extension unit.
FROM/TO LED Lit when 64DNET is accessed from main unit.
MS LED See Note 2.
NS LED See Note 3.
Table 3.3: Performance Specif ications
Items Specifications
FX2N-64DNET DeviceNet Interface Block Specifications 3
3-4
Note 1; Maximum Cable Length
Note 2; MS LED Status (Module Status LED)
Table 3.4: Maximum Cable Length
Using Baud
Rate Trunk Line Maximum Cable Length Drop Line
Maximum
Length Maximum
Total Length
125 kbps Thick cable length + 5 × thin cable length ≤ 500 m (1,640 ') 6 m (20') 156 m (512')
250 kbps Thick cable length + 2.5 × thin cable length ≤ 250 m (820') 78 m (23')
500 kbps Thick cable length + thin cable length ≤ 100 m (328') 39 m (128')
Table 3.5: MS LE D Status (Module Status LED)
MS LED Status 64DNET Status Description
Not lit Power OFF The power supply is insufficient.
Lit Green Normal Operation The 64DNET is in normally operation mode.
Flashi ng Gree n at 0.5 s inter val s Stand - by The 64DNET is in stand-by status or setting
error.
Flashing Red at 0. 5 s intervals Minor Fault A recoverable error has occurred.
Lit Red Unrecoverable
Fault An un re c ov e ra bl e er r or ha s oc c urr ed. Please
contact a service representative.
Flashing Green and Red at 0.5 s
intervals Self Test The 64DNET is in self testing mode.
FX2N-64DNET DeviceNet Interface Block Specifications 3
3-5
Note 3; NS LED Network Status
Note:
When the power suppl
y
is turned on, MS LED and NS LED quickl
y
flashes
g
reen, then red,
and are turn ed off. This operation is normal.
Table 3.6: NS LED S tatus (Network Status LE D)
MS LED Status 64DNET Status Description
Not lit Not On-line The 64DNET is not on-line.
• The power supply volt age is abnormal.
• Dup_MAC_ID test is not finished.
Lit Green Link OK The 64DNET is on-line and has established the
connection.
Flashi ng Gree n at 0.5 s
intervals On-line Status
Without Connection The 64DNET is on-line but has not the established the
connection.
Flashi ng Red at 0.5 s
intervals Com mu n i c ation
Time-out The 64DNET I/O connection is in time-out status.
Lit Red Critical link Failure Communication is not possible.
Flashing Green and Red
at 0.25 s in te rv a ls Com mu n ic at ion
Fault
The 64DNET is the Communication Faulted for
detecting the Network Accessing Error. After this
module will receive the Identify Communication
Fau lted Re qu es t.
FX2N-64DNET DeviceNet Interface Block Specifications 3
3-6
MEMO
Allocation of Buffer Memories (BFMs) 4
4-1
4. Allocation of Buffer Memories (BFMs)
Caution;
1) Do not access the buffer memor
y
of “Not used” (BFM #24, #25, #31, #50 ~ #99, #134 ~
#999, #137*1 ~ #199*1, #16337 ~ #1999, #237*1 ~ #299*1) b
y
the
FROM/TO instruction. There is a possibilit
y
to cause abnormal operation of the 64DNET
if accessin
g
these buffer memories.
*1 has a value of 0 ~ 63.
2) Do not write to (access b
y
T O instruction) the buffer memor
y
of “Read onl
y
” (BFM #1, #2,
#30, #16 ~ #23, #26, #27, #30, #36 ~ #49, #133) in the pro
g
rammable controller. It is not
possible to operate the 64DNET b
y
writin
g
to (accessin
g
b
y
TO instruction) these buffer
memories.
Note:
The sendin
g
data and receivin
g
data buffers have the same buffer memor
y
addresses
(BFM #100 ~ #1031, #100*1 ~ #131*1, #200*1 ~ #231*1) for use with FROM
and TO instructions. This means it is not possible to check the buffer memor
y
data usin
g
a
FROM instruction because this instruction onl
y
reads receive buffer data.
*1 has a value of 0 ~ 63.
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-2
4.1 Buffer Memories (BFM) Lists
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
BFM #0 DeviceNet LINK enable K0 Read /Write
BFM #1 Module status about connection Read Only
BFM #2 Module status about DeviceNet
BFM #3 Number of DeviceNet UCMM connections K0808
Read /Write
BFM #4 DeviceNet bus-off counter K0
BFM #5 Number of DeviceNet retries K2
BFM #6 FROM/TO WDT (watchdog timer) setting K20
BFM #7 Module control flag
K0
BFM #8 ~ 11 UCMM client connection status
BFM #12 ~ 15 UCMM client sending trigger
BFM #16 ~ 19 UCMM client receiving status Read Only
BFM #20 ~ 23 UCMM server receiving status
BFM #24,25 Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-3
BFM #26 Error flag
K0 Read Only
BFM #27 Error code
BFM #28 Error flag latch Read/Write
BFM #29 Error code latch
BFM #30 Module ID code K7090 Read only
BFM #31 Not used
BFM #32 ~ 35 UCMM client WDT switch
K0
Read/Write
BFM #36 ~ 39 UCMM client connection stat us
Read only
BFM #40 ~ 43 UCMM client communication status
BFM #44 ~ 47 UCMM ser ver communication status
BFM #48 Baud rate K500
BFM #49 DIP switch status H 3F0
BFM #50 ~ 99 Not used
BFM #100 ~ 131 Master/Slave receive data Master/Slave send
data K0 Read/Write
BFM #132 Number of link points for Device Net H0404
BFM #133 DeviceNet MAC ID K0 Read only
BFM #134 ~ 999 Not used
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-4
BFM #10000 ~ 10031
UCMM Client 0
Receive data Send data K0 Read/WriteBFM #10032 Length of assembly data H0404
BFM #10033 Length of sending common service data K0
BFM #10034 Length of received data (assembly or
com mo n se r v ic e da ta) Read only
BFM #10035 Group select K3 Read/WriteBFM #10036 DeviceNet class ID and instance ID K0
BFM #10037 DeviceNet attribute ID and service ID
BFM #10038 ~ 10099 Not used
BFM #10100 ~ 10131
UCMM Client 1
Receive data Send data K0 Read/WriteBFM #10132 Length of assembly data H0404
BFM #10133 Length of sending common service data K0
BFM #10134 Length of received data (assembly or
com mo n se r v ic e da ta) Read only
BFM #10135 Group selecti on K3 Read/WriteBFM #10136 Dev i ceNet class ID and instance ID K0
BFM #10137 DeviceNet attribute ID and service ID
BFM #10138 ~ 10199 Not used
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-5
…
…
…
…
…
BFM #16300 ~ 16331
UCMM Client 63
Receive data Send data K0 Read/WriteBFM #16332 Length of assembly data H0404
BFM #16333 Length of sending common service data K0
BFM #16334 Length of received data (assembly or
com mo n se r v ic e da ta) Read only
BFM #16335 Group selecti on K3 Read/WriteBFM #16336 Dev i ceNet class ID and instance ID K0
BFM #16337 DeviceNet attribute ID and service ID
BFM #16338 ~ 19999 Not used
BFM #20000 ~ 20031
UCMM Server 0
Receive data Send data K0 Read/WriteBFM #20032 Length of assembly data H0404
BFM #20033 Length of sending common service data K0
BFM #20034 Length of received data (assembly or
com mo n se r v ic e da ta)
Read only
BFM #20035 Group selecti on K3
BFM #20036 DeviceNet class ID and instance ID K0
BFM #20037 DeviceNet attribute ID and service ID
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-6
BFM #20038 ~ 20099 Not used
BFM #20100 ~ 20131
UCMM Server 1
Receive data K0 Read only
BFM #20132 Length of assembly data H0404 Read/Write
BFM #20133 Length of sending common service data K0
BFM #20134 Length of received data (assembly or
com mo n se r v ic e da ta)
Read only
BFM #20135 Group selecti on K3
BFM #20136 DeviceNet class ID and instance ID K0
BFM #20137 DeviceNet attribute ID and service ID
BFM #20138 ~ 20199 Not used
…
…
…
…
…
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-7
BFM #26300 ~ 26331
UCMM Server 63
Receive data Send data K0 Read/WriteBFM #26332 Length of assembly data H0404
BFM #26333 Length of sending common service data K0
BFM #26334 Length of received data (assembly or
com mo n se r v ic e da ta)
Read only
BFM #26335 Group selecti on K3
BFM #26336 DeviceNet class ID and instance ID K0
BFM #26337 DeviceNet attribute ID and service ID
Table 4.1: BFM Lists
BFM #No. Description Default
Value
FROM/TO
Instruction
(Read/Write)
FROM Instruction
(Read) TO Instruction
(Write)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-8
4.2 DeviceNet LINK Enable <BFM #0> (Read/Write)
This buffer memor
y
is used to enable the 64DNET on DeviceNet.
Table 4.2: DeviceNet LINK Enable <BFM #0>
Value Description
K0 The 64DNET is off-line on DeviceNet.
K1 The 64DNET is on-line on DeviceNet.
Otherwise Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-9
4.3 Module Status about Connection <BFM #1> (Read Only)
This buffer memor
y
is used for checkin
g
connection status of the 64DNE T.
The connection status is allocated as follows.
Table 4.3: Module Status about Connection <BFM #1>
Bit No. Name Description
ON (1) OFF (0)
Bit 0 Master/Slave I/O
Connection
The 64DNET connects to the
master station by I/O
connection.
The 64DNET does not
connect to the master station
by I/ O Conn ection.
Bit 1 Master/Slave Explicit
Messaging Connection
The 64DNET connects to the
mas te r s tat io n by Ex pl ic i t
Connection.
The 64DNET does not
connect to the master station
by Explicit Connection.
Bit 2 UCMM Connection The 64DNET connects to the
other node by the UCMM
Connection.
The 64DNET does not
connect to the other node by
the UCMM Connection.
Bit 3 ~ 15 Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-10
4.4 Module Status about DeviceNet <BFM #2> (Read Only)
This buffer memor
y
is used for checkin
g
the DeviceNet link status of the 64DNET.
The value of this buffer memor
y
’s mean shows bellow table.
Table 4.4: Module Status about DeviceNet <BFM #2>
Value 64DNET Status MS LED Status Description
K0 Power off Not lit The po wer supply is insufficient.
K10 Device Self test Flashing Green and
Red at 0.5 s interval The 64DNET is in self-testing status.
K30 Device oper ational
(On-line) Lit Green
The 64DNET is on- line in normally
operation.
K31 Device oper ational
(Off-line) The 64DNET is off-line in normally
operation.
K50 Unrecoverable Fault Lit Red An unrecoverable error has occurre d.
Please contact a service representative.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-11
4.5 Number of DeviceNet UCMM Connections <BFM #3> (Read/Write)
This buffer memor
y
is used fo r settin
g
or checkin
g
the number of the UCMM Connections on
the DeviceNet.
The settin
g
Ran
g
e of client is 00 ~ 40 hex, and the settin
g
ran
g
e of server is 01 ~ 40 hex.
Default value is 0808 hex (client: Max. 8 connection, server: Max. 8 connection)
Figure 4.1: Number of DeviceNet UCMM Connections <BFM #3>
4.6 DeviceNet Bus-off Counter <BFM #4> (Read/Write)
This buffer mem or
y
is used for checkin
g
the number of times the bus-off has occurred on the
DeviceNet. To r eset a bus off counter, th is buffer memor
y
writes and has perm itted onl
y
“K0”.
Default value is “K0”.
Note:
If an
y
increase in this value, 64DNET does not have stable communication on
DeviceNet. Please check wirin
g
and settin
g
s.
Client
(H ex code) Server
(H ex code)
BFM #3
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-12
4.7 Number of DeviceNet Retries <BFM #5> (Read/Write)
This buffer memor
y
is used for settin
g
number of DeviceNet retries on the UCMM connection.
Default value is K2. This settin
g
ran
g
e is 0 ~ 255.
Note:
This process is performed onl
y
if the UCMM client WDT swi tch is ON. For the UCMM client
WDT switch information, refer to section 4.16.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-13
4.8 FROM/TO WDT Setting <BFM #6> (Read/Write)
This buffer memor
y
is used for settin
g
the FROM/TO WDT. This WDT is adjusted in 10 ms
steps. Default value is 20 (20 × 10 ms = 200 ms). When this value is 0, the watchdo
g
timer is
disabled. When all BFMs (BFM #0 ~ #26337) are not accessed b
y
FROM/TO instructions, the
watchdo
g
timer be
g
ins operatin
g
.
Caution:
1) Usin
g
the Master/Slave communication (Master/Slave connection)
If the watchdo
g
timer reaches the set time (BFM #6 × 10 ms), the 64DNET is in WDT
time-out status. At this time, the 64DNET will store error codes (BFM #27, #29), set error
fla
g
s (BFM #26, #28), and all the send data from the slave to the master station is
cleared. However, 6 4DNET does not stop all da ta exchan
g
e to the master station. The
64DNET will send “K0” to the master station.
Please the PLC access the BFMs (one or more) each time as in the example pro
g
ram
(see section 6.3).
2) Usin
g
the Client/Server communication (UCMM connection)
In this case, the connection of th e UCMM connection follows the UCMM Client WDT
switch settin
g
(BFM #32 ~ #35). For UCMM Client WDT switch information, refer to sec-
tion 4.16.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-14
4.9 Mode Control Flags <BFM #7> (Read/Write)
This buffer memor
y
is used for chan
g
in
g
mode of the receivin
g
data fla
g
and contents of error
code. For error code, refer to chapte r 9.
Note:
When this bit 1 is turned ON, 64DNET does not receive new data from other nodes to which
the receivin
g
data fla
g
(the UCMM client receivin
g
status and the UCMM server receivin
g
status) is turned ON. When the reception fla
g
is turned OFF, new reception data can be
received.
When this bit 1 is turned OFF, 64DNE T will receive new data from other node to which the
receivin
g
data fla
g
is turned ON. If the PLC does not read data from BFMs of receivin
g
data
area, this data will be replaced b
y
new data.
Table 4.5: Mode Control Flags
Bit No. Name Description
OFF (0) ON (1)
Bit 0 Receiving mode See Note
Bit 1 Error code type Upper byte: general error code
Lower byte: additional error code Upper byte: service type
Lower byte: det ailed error code
Bit 2 ~ 15 Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-15
4.10 UCMM Client Connection Setting <BFM #8 ~ #11> (Read/Write)
These buffer memories are used for connectin
g
to the server b
y
the UCMM connection.
Turn On MAC ID server bit to connect the 64DNET as a client via the UCMM connection. T he
allocation of the bits is as shown in the table below.
Caution:
If the connection is cut while sendin
g
or receivin
g
data, the 64DNET will not finish sendin
g
/
receivin
g
the interrupted data. the data ma
y
not be correct or complete.
Table 4.6: UCMM Client Connection Setting <BFM #8 ~ #11>
BFM No. BIt No. MAC ID BFM No. BIt No. MAC ID
BFM #8
Bit 0 0
BFM #10
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #9
Bit 0 16
BFM #11
Bit 0 18
Bit 117 Bit 119
Bit 218 Bit 250
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-16
4.11 UCMM Client Sending Trigger <BFM #12 ~ #15> (Read/Write)
These buffer memories are used for sendin
g
data to the server to which 64DNET is connected
b
y
the UCMM connection of the client.
When sendin
g
data (BF M #100*1 ~ #131*1), the bit which correspon ds to the server
destination is turned OFF → ON. After the data (BFM #100*1 ~ #131*1) is sent, this bit
is automaticall
y
turned OFF. The allocation of the bits is as shown in the table below.
For BFM #100*1 ~ #131*1, refer to section 4.23.
*1 The is entered va lue of 0 ~ 63.
Table 4.7: UCMM Client Sending Trigger <BFM #12 ~ #15>
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #12
Bit 0 0
BFM #14
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #13
Bit 0 16
BFM #15
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-17
4.12 UCMM Client Receiving Status <BFM #16 ~ #19> (Read Only)
These buffer memories are used for readin
g
received data from the server to which 64DNET is
connected b
y
the UCMM connection of the client.
When receivin
g
data from server, the bit which correspo nds to the server o f the destination is
turned OFF → ON. After the PLC reads data from BFMs (BFM #100*1 ~ #131*1) in the
received data area for the server, this bit automaticall
y
is turned OFF. The allocation of the bits
is as shown in the table below. For BFM #100*1 ~ #131*1, refer to section 4.23.
*1 The is entered va lue of 0 ~ 63.
Table 4.8: UCMM Client Receiving Status <BFM # 16~ #19>
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #16
Bit 0 0
BFM #18
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #17
Bit 0 16
BFM #19
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-18
4.13 UCMM Server Receiving Status <BFM #20 ~ #23> (Read Only)
These buffer memories are used for readin
g
received data from the client to which 64DNE T
(server) is connected b
y
the UCMM connection.
When receivin
g
data from the client, t he bit which corresponds to the server is turned OFF →
ON. After the P LC reads d ata from BFMs (BFM # 200*1 ~ #231*1) in the received data
area for the client, this bit automaticall
y
is turned OFF. The allocation of the bits is as shown in
the table below. For BFM #100*1 ~ #131*1, refer to section 4.24.
*2 The is entered va lue of 0 ~ 63.
Table 4.9: UCMM Client Connection Setting
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #20
Bit 0 0
BFM #22
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #21
Bit 0 16
BFM #23
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-19
4.14 Error Status <BFM #26 ~ #29> (Read Only)
These buffer memories are used for checkin
g
error status and error codes.
If an error occurs, the 64DNET stores "K1" to BFM #26 and #28. At the same time, the
64DNET stores the error code to BFM # 27 and #29. However, if the error automaticall
y
recov-
ers, BFM #26 and #27 will be cleared b
y
64DNET. BFM #28 and #29 are not cleared. BFM #28
and #29 can be cleared b
y
the PLC when writin
g
"K0" to these BFMs b
y
the TO instruction.
For error codes, refer to chapter 8.
4.15 Module ID Code <BFM #30> (Read Only)
The identification code fo r a 64DNET is read b
y
usin
g
the FROM instruction. The identification
code for the 64DNET is “K7090”. B
y
readin
g
this identification code, the user ma
y
create built-
in checkin
g
routines to check whether the ph
y
sical position of 64DNET matches to that soft-
ware.
Table 4.10: Error Status <BFM #26, #28>
BFM No. Name Description
K0 K1 K2 or more
BFM #26 Present error flag Norma l op er at io n
(BFM #27 is cleared
by 64DNET)
Occurred Error (error
code is stor e d BFM
#27) Not used
BFM #28 Error flag latch Normal operation Occurred Error (error
code is stor e d BFM
#29)
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-20
4.16 UCMM Client WDT switch <BFM #32 ~ #35> (Read/Write)
These buffer memories are used for settin
g
either to cut off the connection or not cut off the
connection, when the time-out occurs in the Explicit Messa
g
e.
If the MAC ID bit is ON, an Explicit error time out does not cut off the connection to th e server.
The allocation of the bits is as shown in the table below.
Table 4.11: UCMM Client WDT Switch <BFM #32 ~ #35>
BFM
No. BIt
No. MAC
ID Description BFM
No. BIt
No. MAC
ID Description
ON (1) OFF (0) ON (1) OFF (0)
BFM
#32
Bit 0 0
Does not
cut off
connection
for a server
when time -
out occurs
in Explicit
Message
Cuts off
connection
for a server
when time-
out oc curs
in Explicit
Message
BFM
#34
Bit 0 32
Does not
cut off
connection
for a server
when time-
out occurs
in Explicit
Message
Cuts off
connection
for a server
when time-
out occurs
in Explicit
Message
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM
#33
Bit 0 16
BFM
#35
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-21
4.17 UCMM Client Connection Status <BFM #36 ~ #39> (Read Only)
These buffer memories are used for checkin
g
if the server has server been connected.
The bit which corresponds to the MAC ID of the server to which 64DNET has connected previ-
ousl
y
as a client is turned ON. The allocation of the bits is as shown in the table below.
Table 4.12: UCMM Client Connection Status <BFM #36 ~ #39>
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #36
Bit 0 0
BFM #38
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #37
Bit 0 16
BFM #39
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-22
4.18 UCMM Client Communication Status <BFM #40 ~ #43> (Read Only)
These buffer memories are used to check the status of correct server communication.
The bit which corresponds to the MAC ID of the server to which 64DNET communicates
correctl
y
as a client is turned ON. The allocation of the bit is as shown in the table below.
Table 4.13: UCMM Client Communication Status <BFM #40 ~ #43>
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #40
Bit 0 0
BFM #42
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #41
Bit 0 16
BFM #43
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-23
4.19 UCMM Server Communication Status <BFM #44 ~ #47> (Read Only)
These buffer memories are used for checkin
g
the status of client. connection
The bit which correspond s to the MAC ID of the client to which 64DNET is connected b
y
client
is turned ON. The allocation of the bits is as shown in the table below.
Table 4.14: UCMM Se rver Communication Status <BFM #44 ~ #47>
BFM No. BIt No. M AC ID BFM No. BIt No. MAC ID
BFM #44
Bit 0 0
BFM #46
Bit 0 32
Bit 1 1 Bit 1 33
Bit 2 2 Bit 2 34
:
::
::
::
:
Bit 15 15 Bit 15 47
BFM #45
Bit 0 16
BFM #47
Bit 0 18
Bit 1 17 Bit 1 19
Bit 2 18 Bit 2 50
:
::
::
::
:
Bit 15 31 Bit 15 63
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-24
4.20 Baud Rate <BFM #48> (Read Only)
This buffer memor
y
is used for checkin
g
the baud rate.
This value is the baud rate. When 64DNET starts, the value set with DIP switches is stored in
this buffer memor
y
. For settin
g
the baud rate, refer to subsection 5.1.2.
Note:
The baud rate cannot be chan
g
ed b
y
the DIP switches when the 64DNET is ON. Please
turn 64DNET off to chan
g
e the DIP switch positions.
4.21 Master/Slave Communication Data Area <BFM #100 ~ #133>
This area is used for I/O connection.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-25
4.21.1 Send Data/Receive Data Area <BFM #100 ~ #131> (Read/Write)
These buffer memories are used to send/receive data to/from the master.
Note:
• The sendin
g
data and receivin
g
data buffers have the same buffer memor
y
addresses
(BFM #100 ~ #131) for use with FROM and TO instructions. This means it is not possible
to check the buffer memor
y
data usin
g
a FROM instruction because this instruction onl
y
reads receive buffer data.
• Buffer Memories (BFM #100 ~ #131) are onl
y
refreshed for the number of b
y
tes decided
b
y
BFM #132.
Therefore, when less data is received from the master compared to the previous time,
some data remains from the prior messa
g
e.
Table 4.15: Send Data/Receive Data Area <BFM #100 ~ #131>
BFM No.
Description
Send Data (using TO Instruction) Receive Data (using FROM Instruction)
Upper Byte Lower Byte Upper Byte Lower Byte
BFM #100 2nd byte 1st byte 2nd byte 1st byte
BFM #101 4th byte 3rd byte 4t h byte 3rd byte
BFM #102 6th byte 5th byte 6th byte 5th byte
:
::
::
:
BFM #131 64th byte 63th byte 64th byte 63th byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-26
4.21.2 Number of Link Points <BFM #132> (Read/Write)
This buffer memor
y
is used for settin
g
number of link points of the I/O connection.
The 64DNET can exchan
g
e maximum 64 b
y
tes to the master. Default value is H0404 (Hex
code). The settin
g
ran
g
e of the upper and lower b
y
tes is H01 to H40.
Figure 4.2: Number of Points <BFM #132>
4.21.3 MAC ID <BFM #133> (Read Only)
This buffer memor
y
is used for checkin
g
the MAC ID of master and 64DNET I/O connection.
The upper b
y
te is the MAC ID of the master. The lower b
y
te is the MAC ID of the 64DNET. The
MAC ID of 64DNET is stored to the lower b
y
te durin
g
start up.
Figure 4.3: MAC ID <BFM #133>
Send data
(H ex code) Receive data
(H ex code)
BF M #132
U pper byte Lower byte
Master
(H ex code) 64DNET
(H ex code)
BF M #133
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-27
4.22 UCMM Client Communication Data Area <BFM #10000 ~ #16336>
This area is used for the UCMM connection when 64DNET is a client.
4.22.1 Send Data/Receive Data Area <BFM #100*1 ~ #131*1> (Read/Write)
These buffer memo ries are used to send/receive data to/from the server. The buffer memor
y
for send/receive data is allocated as in tab le 4.16.
Note:
• The send data and receive data buffers have the same buffer memor
y
addresses (BFM
#100*1 ~ #131*) for use with FROM and TO instructions. This means it is not
possible to check the buffer memor
y
data usin
g
a FROM instruction because this
instruction onl
y
reads receive buffer data.
• Buffer Memories (BFM #100*1 ~ #131*) are onl
y
refreshed for the number of
b
y
tes decided b
y
BFM #132.
Therefore, when less data is received from the master compared to the previous time,
some data remains from the prior messa
g
e.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-28
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
Table 4.16: Send Data/Receive Data Area <BFM #1
00
*1
~ #1
31
*1
>
BFM No.
Description
Send Data (using TO Instruction) Receive Data (using FROM Instruction)
Upper Byte Lower Byte Upper Byte Lower Byte
BFM #100*1 2nd byte 1st byte 2nd byte 1st byte
BFM #101*1 4th byte 3rd byte 4th byte 3rd byte
BFM #102*1 6th byte 5th byte 6th byte 5th byte
:
::
::
:
BFM #131*1 64th byte 63th byte 64th byte 63th byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-29
4.22.2 Length of Assembly Data <BFM #132*1> (Rea d/Write)
These buffer memories are used for settin
g
len
g
th of assembl
y
data about the connected to
the server. The 64DNET can exchan
g
e maximum 64 b
y
tes to the server. Default value is
H0404 (Hex code). The settin
g
ran
g
e of the upper and lower b
y
tes is H01 to H40 .
Figure 4.4: Length of Assembly Data <BFM #1
32
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
4.22.3 Length of Sending Common Service Data <BFM #133*1> (Read/Write)
These buffer memories are used for settin
g
len
g
th of sendin
g
common service data to the
server. Default value is K0.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
BFM #1
32 Send data
(H ex code) Receive data
(H ex code)
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-30
4.22.4 Length of Receiving Data <BFM #134*1> (Read Only)
These buffer memories are used for checkin
g
the len
g
th of data received from the server.
This value is
g
iven in number of b
y
tes received.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
4.22.5 Group S e lection <BFM #135*1> (Read/Write)
These buffer memories are used for settin
g
the connection
g
roup.
The default value is K3.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
Table 4.17: Group Setting <BFM #1
35
*1
>
Setting Value Reading Value Description
0 Not used
1 0 Group 1
2 Not used
3 3 Group 3
4 or more Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-31
4.22.6 Class ID and Instance ID <BFM #136*1>
These buffer memories are used for settin
g
the Class ID and the Instance ID.
For Class ID and Instance ID, refer to Appendix B.
Figure 4.5: Class ID and Instance ID <BFM #1
36
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
BFM #1
36 Class ID
(H ex code) In s ta n c e ID
(H ex code)
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-32
4.22.7 Attribute ID and Service Code <BFM #137*1>
These buffer memories are used for settin
g
the Class ID and the Instance ID.
For Class ID and Instance ID, refer to Appendix B.
Figure 4.6: Attribute ID and Service Code <B FM #1
37
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
BFM #1
37 Attribute ID
(H ex code) Service C ode
(H ex code)
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-33
4.23 UCMM Server Communication Data Area <BFM #20000 ~ #26336>
This area is used for the UCMM connection when 64DNET is a server.
4.23.1 Send/Receive Data Area <BFM #200*1 ~ #231*1> (Read/Write)
These buffer memories are used to send/receive data to/from the client. The buffer memor
y
for
send/receive data is allocated as in table 4.18.
Note:
• The send data and receive data buffers have the same buffer memor
y
addresses (BFM
#200*1 ~ #231*) for use with FROM and TO instructions. This means it is not
possible to check the buffer memor
y
data usin
g
a FROM instruction because this
instruction onl
y
reads receive buffer data.
• Buffer Memories (BFM #200*1 ~ #231*) are onl
y
refreshed for the number of
b
y
tes decided b
y
BFM #232.
Therefore, when less data is received from the master compared to the previous time,
some data remains from the prior messa
g
e.
*1 has a value of 0 ~ 63. This value is the MAC ID of the client.
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-34
*1 has a value of 0 ~ 63. This value is the MAC ID of the client.
Table 4.18: Send data/Receive Data Area <BFM #2
00
*1
~ #2
31
*1
>
BFM No.
Description
Send Data (using TO Instruction) Receive Data (using FROM Instruction)
Upper Byte Lower Byte Upper Byte Lower Byte
BFM #200*1 2nd byte 1st byte 2nd byte 1st byte
BFM #201*1 4th byte 3rd byte 4th byte 3rd byte
BFM #202*1 6th byte 5th byte 6th byte 5th byte
:
::
::
:
BFM #231*1 64th byte 63th byte 64th byte 63th byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-35
4.23.2 Length of Assembly Data <BFM #232*1> (Rea d/Write)
These buffer memories are used for settin
g
the len
g
th of assembl
y
data from the client.
The 64DNET can exchan
g
e maximum 64 b
y
tes to the client. Default value is H0404 (Hex
code). The settin
g
ran
g
e of the upper and lower b
y
tes is H01 to H40.
Figure 4.7: Length of Assembly Data <BFM #2
32
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the client.
4.23.3 Length of Sending Common Service Data <BFM #233*1> (Read/Write)
These buffer memories are used for settin
g
the len
g
th of the sendin
g
common service data to
the server. The default value is K0.
*1 has a value of 0 ~ 63. This value is the MAC ID of the client
BFM #2
32 Not Used
(M ust be 00 hex.) Receive data
(H ex code)
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-36
4.23.4 Length of Receiving Data <BFM #234*1> (Read Only)
These buffer memories are used for checkin
g
the len
g
th of the data received from the client.
This value is
g
iven in number of b
y
tes received.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
4.23.5 Group S e lect <BFM #235*1> (Read Only)
These buffer memories are used for checkin
g
the connection
g
roup.
The default value is K3.
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
Table 4.19: Group Setting <BFM #2
35
*1
>
Value Description
0 Group 1
1, 2 Not used
3 Group 3
4 or more Not used
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-37
4.23.6 Class ID and Instance ID <BFM #236*1> (Read only)
These buffer memories are used for checkin
g
the Class ID and the Instance ID.
For Class ID and Instance ID, refer to Appendix B.
Figure 4.8: Class ID and Instance ID <BFM #2
36
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
4.23.7 Attribute ID and Service Code <B FM #237*1> (Read only)
These buffer memories are used for checkin
g
the Attribute ID and the Service Code.
For the Attribute ID and the Service Code, refer to Appendix B.
Figure 4.9: Attribute ID and Service Code <B FM #2
37
*1
>
*1 has a value of 0 ~ 63. This value is the MAC ID of the server.
BFM #2
36 Class ID
(H ex code) In s ta n c e ID
(H ex code)
U pper byte Lower byte
BFM #2
37 Attribute ID
(H ex code) Service C ode
(H ex code)
U pper byte Lower byte
FX2N-64DNET DeviceNet Interface Block Allocation of Buffer Memories (BFMs) 4
4-38
MEMO
DIP Switch Setting 5
5-1
5. DIP Switch Setting
5.1 Setting DIP Switch
Figure 5.1: Allocation DIP Switch
5.1.1 Mode Setting (DIP Switch: SW0, SW1)
Operation mode is decided b
y
the DIP switches SW0 and SW1.
Default settin
g
: Normal operation mode (SW0 =OFF, SW1 = OFF)
Table 5.1: Mode Setting (DIP S witches: SW0, SW1)
SW1 SW0 Using Mod e
OFF OFF Normal operation
OFF ON Not usedON OFF
ON ON
0123450101
ON
SWDRNA
T hese D IP switches are O N. These D IP
switches are O FF.
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block DIP Switch Setting 5
5-2
5.1.2 Baud Rate Setting (DIP Switch: DR0, DR1)
Operation mode is decided b
y
the DIP switches DR0 and DR1.
Default settin
g
: 500 kbps (DR0 = OFF, DR1 = ON)
Table 5.2: Baud Rate Setting (DIP S witches: DR0, DR1)
DR1 DR0 Setting Baud Rate
OFF OFF 125 kbps
OFF ON 250 kbps
ON OFF 500 kbps
ON ON Not used
FX2N-64DNET DeviceNet Interface Block DIP Switch Setting 5
5-3
5.1.3 MAC ID Setting (DIP Switches: NA0 ~ NA5)
The MAC ID is decided b
y
the sum total value of the DIP switches NA0 ~ NA5. The MAC ID
settin
g
value ran
g
e is 0 ~ 63. Default settin
g
: 63 (NA0 ~ NA5 are all ON)
Example Setting
If the MAC ID of the 64 DNET is set to “30”, the DIP switches are as shown below.
Figure 5.2: Example Setting of MAC ID
Table 5.3: DIP Switch Value
DIP Switch Value
ON OFF
NA0 1
0
NA1 2
NA2 4
NA3 8
NA4 16
NA5 32
0
1
2
3
4
5
NA
ON
1
2
4
8
16
32
This v alu e is DIP s witch v alue .
FX2N-64DNET DeviceNet Interface Block DIP Switch Setting 5
5-4
MEMO
Client/Sever Comm unication by UCMM Connection 6
6-1
6. Client/Sever Communication by UCMM Connection
6.1 Information of UCMM Co nnection by 64DNET
The UCMM connection is client/ser ver communication. The direction o f connection is client to
server. The 64DNET can become one client of maximum of 63 nodes and the server of
maximum 63 nodes. Moreover, it is possible to connect to the same node b
y
the connection of
the client and the server.
For supported objects, refer to Appendix B.
Note: Supported UCMM Connection by 64DNET
When the 6 4DNET is a client, it can send data or request data from the server. If the
64DNET sends a data request to the server, it will receive data fr om the server. When the
64DNET is the server, it can receive and request data from client. If the 64DNET receives a
request from a client, it will send an answer data to the client.
Table 6.1: UCMM Connection Flags and Status
Flags Client Server
Connection status
Sending trigger flag
Receiving status
UCMM client WDT switch
Communication status
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Client/Sever Communication by UCMM Connection 6
6-2
6.2 How to Use Peer to Peer Communication
When usin
g
the peer to pee r communication, the connection for each node is shown below.
Figure 6.1: Peer to P eer Commun ication
Note:
• Each node must support the UCMM connection and know the object information (Class
ID, Instance ID, Attribute ID and service code) about all nodes.
For the ob ject information of 64DNET, refer to Appendix B.
• When usin
g
UCMM connection, please choose
g
roup 3.
M AC ID 00: This node is the master, the client of MAC ID 01
and 02, and the server of M AC ID 01 and 02.
MAC ID 0 1 : Th is n o d e is th e s la v e , th e
c lie n t o f MAC ID 0 0 a n d 0 2 ,
and the server of M AC ID 00
and 02.
: M aster/Slave C onnection : U C M M C onnection (C lient
→
Server)
MAC ID 0 2 : Th is n o d e is th e s la v e , th e
c lie n t o f MAC ID 0 0 a n d 0 1 ,
and the server of M AC ID 00
and 01.
Example Program 7
7-1
7. Example Program
7.1 System Configuration
Figure 7.1: System Configuration for E xample Program
FX
2N
-64DNET
(MAC ID: 0 1 )
FX
2N
-64MR
-ES/UL
N etwork power
supply unit
(2 4 V D C)
: Dro p lin e
: Tru n k lin e : T erminating resistor : T ap: Powe r tap
M aster station (M A C ID: 00)
FX
2N
-64DNET
(MAC ID: 0 2 )
FX
2N
-32MR
-ES/UL
FX
2N
-64DNET
(MAC ID: 0 3 )
FX
2N
-48MR
-ES/UL
Slave station 1
Slave station 2
Slave station 3
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-2
7.2 Operation
This operation is writte n for Slave Station 1.
1) Master/Slave I/O connection:
- Slave station 1 exchan
g
es 64/64 b
y
tes data to the master station (MAC ID 00) b
y
the
Master/Slave I/O connection.
- Received data from the master station is stored in D150 ~ D181 in slave station 1.
- D100 ~ D131 in slave station 1 are sent to the master station.
2) The UCMM connection when slave station 1 (MAC ID 01) is the client:
- S lave station 1 exchan
g
e 64/64 b
y
tes data to slave station 2 (server, MAC ID 02) b
y
the
UCMM connection.
- Received data from the server is stored in D500 ~ D531 in slave station 1.
- W hen X000 is turned ON, slave station 1 connects to slave st ation 2 b
y
the UCMM con-
nection.
3) The UCMM connection when the slave station 1 (MAC ID 01) is the server:
- The slave station 1 can receive 64 b
y
tes data from slave station 3 (client, MAC ID 03) b
y
the UCMM connection.
- Data received data from slave station 3 is stored in D600 ~ D631 in slave station 1.
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-3
7.3 Example Program
This example pro
g
ram is written about slave station 1.
Note:
When man
y
FROM/TO instructions are executed in the same scan, the PLC mi
g
ht have a
watchdo
g
timer error. In this case, add a watchdo
g
timer reset (FNC07 WDT) instruction
with each FROM/TO instruction that sends and receives data.
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-4
7.3.1 Initial Setting
Figure 7.2: Initial Setting
M8002
FNC 79
TO
K0 K3 H0102 K1
FNC 79
TO
K0 K4 K0 K1
FNC 79
TO
K0 K6 K10 K1
FNC 79
TO
K0 K7 H0003 K1
Initial pu ls e
Sets number for using
U CM M connection to a
client and 2 servers.
(u pp e r b yte : c lie n t, lowe r
b yte : se r ver)
Initializ es the b us -off
counter.
Se ts FROM/TO
instruction watchdog
time.
Sets the receiving mode
and the error code type.
Please see section 4.9.
(a) (a)
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-5
Figure 7.2: Initial Setting
Sets number of link
points for M aster/Slave
I/O c o n ne c tio n to 6 4 /6 4
bytes (upper byte:
sending data, low er
byte: receiving data).
FNC 79
TO
K0 K132 H4040 K1
FNC 79
TO
K0 K10232 H4040 K1 Sets number of link
points for U CMM
connection of server
(MAC ID: 0 2 ) to 6 4 /64
bytes (upper byte:
sending data, low er
byte: receiving data).
FNC 79
TO
K0 K10235 K3 K1 Sets selection group to
group 3 for this server
(MAC ID: 0 2 ).
(a) (a) (a)
(b)(b)(b)
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-6
Figure 7.2: Initial Setting
FNC 78
FROM
K0 K20335 D632 K3
Sets number of link
points for U CMM
connection of client
(MAC ID: 0 3 ) to 6 4 /64
bytes (upper byte:
sending data, low er
byte: receiving data).
FNC 79
TO
K0 K20332 H4040 K1
Reads Selection G roup,
Cla s s ID, In s tan c e ID,
Attribute ID , and S ervice
code for client (M AC ID :
03).
(b) (b) (b)
(c)(c)
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-7
Figure 7.2: Initial Setting
FNC 78
FROM
K0 K2 D0 K1 R eads module status
about D eviceN et.
R eads module status
about connection.
M8000
FNC 78
FROM
K0 K1 K1M0 K1
M0
M1
M2
Mas te r/Sla ve I/O
connection flag
U CM M connection flag
Mas ter/ Slav e Explicit
M essaging connection
flag
O n-line flag
Y000
Y001
Y002
Y003
FNC232
AND=
D0 K30
FNC232
AND=
D0 K31
FNC 79
TO
K0 K0 K1 K1
(0)
(0)
RUN m onitor
Set on-line flag to O N
(c) (c)
(d)
(d)
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-8
7.3.2 Checkin g Error Status
Figure 7.3: Checking Error Status
FNC 78
FROM
K0 K26 K1M20 K1 R eads present error
flag.
R eads error flag latch.
M8000
FNC 78
FROM
K0 K28 K1M24 K1
M20
M24
R eads present error
code.
R eads error code latch.
RUN m onitor
(d) (d)
(e)
(e)
FNC 78
FROM
K0 K27 D200 K1
FNC 78
FROM
K0 K29 D201 K1
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-9
7.3.3 Input Data and Output Data for Master/Slave I/O Con nection
Figure 7.4: Input Data and Output Data for Master/Slave I/O Connection
Write sending data
(H1234).
When 64D N ET is on-
line, the sending data is
written to B FM #100 ~
#131.
X002
FNC 79
TO
K0 K100 D100 K32
Y003
When 64D N ET is on-
line, the receiving data
is read from BFM #100
~ #131.
Writing data flag
(e) (e)
(f)
(f)
FNC 78
FROM
K0 K100 D150 K32
FNC 16
FMOV
H1234 D100 K32
P
On-line
flag
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-10
7.3.4 Input Data and Output Data for UCMM Connection
1) Usin
g
client
Figure 7.5: UCMM Connection (Client)
FNC 79
TO
K0 K8
K4M100
K4
T urns M A C ID 02 of
UCMM Client WDT
Switc h to ON.
When M 102 is O N ,
64D NET connects to
MAC ID 0 2 o n th e
DeviceNet.
M8002
When M 32 is set,
64D EN T sends data
(6 4 bytes ) to MA C ID 0 2
by U C M M connection.
R equest flag of connecting to M A C
ID : 02 on U C M M connection
(f) (f)
(g)
(g)
Send request flag for M A C ID : 02
X000
Initial plu s
FNC 79
TO
K0 K32 H0004 K1
M102
SET M32
M8000
RUN m onitor
Writes U C M M C lient
connection request.
C hecks U C M M C lient
connection status.
FNC 78
FROM
K0 K8
K4M200
K4
X001
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-11
Figure 7.5: UC MM Connection (Client)
M32
Send request for M AC ID 02
Writes sending data
Write sending data to
BF M #10200 ~ #10231.
Cla s s ID: H0 4
In s ta n c e ID: H6 6
UCMM
connection
status
(g) (g)
(h)
(h)
M202
M8000
T he sending trigger is
ON.
Writes the sending
trig g e r to BFM # 1 2 .
FNC 79
TO
K0 K12
K4M400
K1
FNC 16
FMOV
H5678 D400 K32
P
M32
FNC 79
TO
K0
K10200 D400
K32
FNC 79
TO
K0 K10236
H0466
K1
FNC 79
TO
K0
K10233 K0
K1 T he Common service
Da ta s ize se t to 0 b yte .
Attr ib u te ID: H0 3
Service code: H 10
FNC 79
TO
K0 K10237
H0310
K1
PLS M402
FNC 78
FROM
K0 K12
K4M600
K1 C hecks the status of
sending to the server.
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-12
Figure 7.5: UC MM Connection (Client)
C onnection flag of MA C ID 02
Sending flag to MA C ID
02
R esets the sending
request.
(h) (h)
(k)
(k)
M602 Y004
M602 RST M32
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-13
2) Usin
g
server
Figure 7.5: UCMM Connection (Client)
Initializ e the Z2 d ev ice .
(k) (k)
(m)
(m)
M akes receiving data
word length from byte
length.
If the receiving data byte
length is an odd
number, receiving data
word length is +1.
C hecks receiving flag of
MAC ID 0 3
R eads receiving data
b yte le n g th .
FNC 78
FROM
K0 K20334 D320 K1
RST Z2
M8000
RUN m onitor
M703
FNC 23
DIV
D320 K2 D322
FNC 232
AND=
K1 D323
FNC 20
ADD
K1 D322 Z2
FNC 78
FROM
K0
K20 K4M700
K1
(0)
(0)
(m)
R eceiving data flag of M AC ID 03
FX2N-64DNET DeviceNet Interface Block Example Program 7
7-14
Figure 7.6: UC MM Connection (Server)
FNC 236
AND<>
K1 D323
FNC 12
MOV
D322 Z2
FNC 78
FROM
K0 K20300
D600
K1Z2
(m) (m)
If the receiving data byte
length is an even
number, receiving data
word length is the same
as byte length.
(m)
Read s the r e ceiv in g
data from B FM #20300
~ #20331 area.
END
Diagnostics 8
8-1
8. Diagnostics
8.1 Preliminary Checks
1) Check “POWER LED”.
If “POWER LED” is OFF, check the connection of the 64DNET extension cable to PLC, and
check whether the 5V DC volta
g
e source capacit
y
is sufficient.
2) Check “MS LED” and “NS LED”.
If both LEDs are not lit
g
reen, check the wirin
g
for the DeviceNet, the module status in BFM
#2, the settin
g
of the Master and the error code in BFM #27, #29.
For module statu s, refer to section 4.4. Fo r error code, subsection 7.2.2. For wirin
g
, refer to
chapter 2 and manu al of the Master. For the settin
g
of the Master, refer to manual of the
Master.
3) Check whether 24 V DC volta
g
e source capacit
y
of DeviceNet suffices.
Suppl
y
current and volta
g
e.
4) Check baud rate.
If the baud rate set in 64DENT is not the same as other station, chan
g
e to matchin
g
values.
When chan
g
in
g
the settin
g
value in 64DNET, please turn the power suppl
y
of the PLC OFF
to ON.
For the bau d rate of 64DNET, see BFM #48 in 64DNET.
5) Check the MAC ID of 64DNE T.
Please do not use the same MAC ID for more than one node on the DeviceNet.
FX2N-64DNET DeviceNet Interface Block
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-2
8.2 LED Check
Check the status of the LED’s for the 64DNET as follows.
1) POWER LED check
2) FROM/TO LED check
Table 8.1: POWER LED Check
Status Description
Lit The extension cable is properly connected. And 5 V DC is properly supplied from
PLC.
Otherwise Check the connection of the 64DNET extension cable to the PLC, and check
whether the 5V DC volta
g
e source capacit
y
of PLC suffices.
Table 8.2: FROM/TO Check
Status Description
Lit. BFM is accessed by FROM/TO instruction.
Otherwise BFM is not accessed by FROM/TO instruction.
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-3
3) MS LED check
Table 8.3: MS LE D (Module Status LED) Check
MS LED Status 64DNET Status Description
Not lit Power OFF Check whether 24 V DC voltage source has sufficient
ampere capacity.
Provide sufficient current.
Lit Green Normal Operation The 64DNET is in normal operation mode.
Flashi ng Gree n at 0.5 s
intervals St an d- b y The 64DNET is in st an d- b y st atus.
Flashi ng Red at 0.5 s
intervals Minor Fault A recoverable error has occurred.
Lit Red Unrecoverable
Fault An unrecoverable error has occurr ed. Please contact
a service representative.
Flashing Green and Red at
0.5 s intervals Self Test The 64DNET is in self test mode.
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-4
4) NS LED
Table 8.4: NS LED (Network Status LED) Check
MS LED Status 64DNET Status Description
Not lit Not On-line
The 64DNET is not on-line.
• The power supply voltage is incorrect for DeviceNet.
• When the value in BFM #0 is K0, 64DNET is off-line. In this
case, write K1 to BFM #0. At this time, 64DNET will be
on-line.
Lit Green Link OK The 64DNET is on-line and has established the connection.
Flashing Green at
0.5 s intervals
On-line Status
Without
Connection
The 64DNET is on-line but has not the established the
connect ion . Chec k the sett ing of th e Maste r, and check sett ing
of the UCMM connection in 64DNET.
Flashing Red at
0.5 s intervals Communication
Time-out The 64DN ET I/O connection is in time-ou t status. Check the
settin g of the M aster.
Lit Red Critical link
Failure
Communication is not possible. Check wiring, and check the
MAC ID of 64DNET to be used by other node. If the same,
change the MAC ID of 64DNET or other node.
Flashing Green
and Red at 0.25 s
intervals
Communication
Fault
The 64DNET is in the Communication Faulted status for
detecting the Network Accessing Error. After this module will
receive the Identify Communication Faulted Request. Check
error code. For error code, refer to subsection 7.2.2.
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-5
8.3 Error Code
Error code of 64DNET is 64DNET error code and DeviceNet error code.
Note:
If error code is for the UCMM connection, please check the UCMM client connection status
(BFM #36 ~ #39), UCMM client communication status (BFM #40 ~ #43) and UCMM server
communication status (BFM #44 ~ #47). The source of the error must be checked in the
individual device buffer memories.
8.3.1 64DNET Error Code (BFM #7 Bit 1 is ON)
This error code is service t
y
pe (upper b
y
te) and detailed error code (lower b
y
te).
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
01
Critical fault connection time-out
01 The first occurrence of a duplicate
MAC ID was received. Change setti ng the M AC ID of the
DIP switch with other devices in
the network so as not to repeat
previously used numbers.
02 The sec ond occurrence of
duplicate MAC ID was received.
03 DR1 and DR2 of DIP switch are
set to 1 (This setting is the “Not
used” position). Set the baud rate correctly.
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-6
01
04 The receive buffer for the CAN
int errupt overflowed.
Reduce the number o f data of
sending and receiving, reduce the
communication frequency or
lower the baud rate.
05 CAN Controller is in the bus-off
state. C heck system configuration on
the Devi c eNet.
06 The Explicit message connection
time-out occurred.
Allocate the Explicit Message
Connection from the Master or
the client again.
11 Duplic a te MA C ID re s po ns e
message was received. Ch ange se tting t he MAC I D of t he
DIP switch with other devices in
the network so as not to repeat
previously used numbers.
12
Duplic a te MAC ID re qu es t was
received, the MAC ID is in
transmission time-out waiting
status.
13 The Polling connection time-out
occurred. Alloc ate the Master/Slave I/O
Connection from the Master
again.
14 The COS/Cyclic connection
time-out occurred.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-7
02
Allocate_Master/Slave_Connection_Set service error (An error with the connection the
Allocate request)
02 The Allocate request was received
from a different Master.
Check the settings of the Master
06
64DNE T cannot support
connec tions ot her than the Explici t
message, Polling, and COS/Cyclic
in the Allocate request.
07 The Allocate request bit is not
prop erly set. Check the setting of the Master to
order the Allocate re quest.
08 The specified connection has
already been allocated. Allocate only once for each
connection.
09 The Reserve Bit of allocator MAC
ID does not turn OFF. Check packet data for the
Allocate request from the Master.
10 Allocation Choice Bit is not
specified. Check the setting of Master to
order the Allocate re quest.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-8
02
11 The Ack Suppress Bit is specified
but the COS/Cyclic bit is not
specified.
Check the setting of Master to
order the Allocate re quest.
12 Tries to establish both COS and
Cyclic transmission method for
Master/Slave connection.
13
The Polling connection cannot be
established because the Instance
ID has a l ready been used by the
COS/C y cl ic co nn ec ti on .
03
Release_Master/Slave_Connection_Set service error (An error with the open
connection request)
06
64DNE T cannot support
connec tions ot her than the Explici t
message, Polling, and COS/Cyclic
in the Allocate request.
Connections other than the
Expli cit message, Polling, and
COS/Cyclic are not supported.
07 The connection for the Release
request is done is not specified. Specify the connection for the
Release request.
08 The specified connection has
already been released. Use only one Release request per
connection.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-9
04
Get_Attribute_Single service error (An error with the read request of the Master)
03 An invalid value for the Instance
ID and the Attribute ID of the Get
service command was specified.
Check the packet data of the Get
service request from the Master
and corre ctly sp eci f y the A tt ri bute
ID value.
05
Set_Attribute_Single error (An error with the write request of the Master)
02 The Set service is not supported
by the specified Attribute ID.
Do not use the Set service
request wi th the specified
Attribute ID.
03 The Attribute ID is outside the
range. Correctly specify the Attr ibute ID.
04 The attribute value written in the
Set service is outside the range.
06
Reset service error (A n error with the reset request of the Master)
01 The state of the connection is
contradicted. Do not reset except when in
time-out.
02 The parameter of the Reset
service is outside the range. Correctly specify parameter.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-10
07
I/O Polling reque s t receive error
01 Middle or final packet was
received before the first packet
data. Check the parameter settings of
the Master with regard to the
Master/Slave I/O communication,
and status of the D eviceNet.
02 Sequen ce error for receiv ing the I/
O data.
03 Receives more data than the
maximum number of I/O byte data.
08
Expli cit mess age reception error
01 The message fragment send and
receive are operating concurrently. Chec k the system conf iguration
on the DeviceNet.
02 Middle or final packet was
received before the first packet
data. Check the parameter setting of
the Master and the system
configuration on the DeviceNet.
03 The same me ssage f ra gmen t was
received twice rather than
receiving the complete message.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-11
08
04 Sequence error for rece iving a
message fragment. Check the parameter setting of
the Master and the system
configuration on the DeviceNet.
05 Receives message larger than
maximum number of message
bytes allowed.
06 A message is received be fore the
send message has fin i shed
transmission.
Chec k the system conf iguration
on the DeviceNet.
A1
DeviceNet object error
01 An invalid service request for the
DeviceNet Object Class was
received.
Check the packet data for the Get
service request from the Master
or other node.
02 An invalid request for the
DeviceNe t Object Instance wa s
received.
03 Instance ID which does not exist in
the DeviceNet Object Instance
was specified.
05 An invalid Class ID for the
DeviceNe t Object Instance wa s
specified.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-12
A2
Connection object error
01 The Connection Object Class was
accessed .
Check the packet data for the Get
service request from the Master.
02 An invalid Service request for the
Connection Object Instance was
received.
03 Instance ID which does not exist in
the Connection Object Instance
was specified.
04 An invalid Attribute ID for the
Connection Object Class was
specified.
A3
Identity (ID) object error
01 The Object Class ID was
accessed. Check the packet data for the Get
service request from the Master.
02 An invalid Service request for the
Object Instance ID was received.
03 A value which does not exist in the
Object Instance ID was specified.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-13
A5
Assembly object error
01 The Assemb ly Object Class was
accessed. Check the packet data for the Get
service request from the Master.
02 A value which does not exist in the
Assembly Object In stance ID was
specified.
A6
Grup2 Only UCMM message error
03 The value which does not support
to the Class ID or the Instance ID
for the UCMM message is used.
Check the packet data for the Get
service request from the Master.
B0
Peer-to-peer message error
01 The Service code received
through the UCMM connection is
not supported.
Check the client setting for the
UCMM connection with regard to
the Service code.
02 The specified Selection Group for
the UCMM connection from client
is not supported. Check the client setting for the
UCMM connection with regard to
the Selection Group.
03 The specified value of the
Selection Group in the clie nt is
invalid.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-14
B0
04 The 64DNET is already connected
to the number of devices sp ecified
in BFM #3.
Check the setting value in the
BFM #3. The 64DNET cannot be
connected to more devices than
the number in BFM #3.
06
The message ID received by the
Open_Explicit_Messaging
Connection Request is invalid in
the specified message group.
Check the setting of the client
with regard to the Source
Message ID.
07
The message ID received by the
Open_Explicit_Massaging_Conne
ction_Request already is used in
the group 1 or gr oup 3.
Check the setting of the client,
and configuration of the
DeviceNet.
08 The Instance ID received by the
Close_ Connecti on_Request is not
supported.
Check the setting of the client
about Instance ID.
09 There is no respo nse for the Op en
Explicit Messaging Connection. Check the power supply of the
server and the connection.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-15
B1
Acknowle dge Handler Object service error
01 The Acknow ledge Handler Object
was accessed.
Check the packet data from the
Master.
02 The received Service request
does not support on the
Acknowledge Handler Object.
03 The specified Instance ID is
invalided on the Acknowledge
Handler Object.
04 The specified Attribute ID is not
supported in the Acknowledge
Handler Object.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-16
B3
BFM error
01 The server does not have an
empty buffer for receiving data.
Put the server into the state that
data from the client can be
received.
02 The UCMM client sending trigger
turns ON while data is still being
sent to the server.
Check the PLC program with
regard to BFM #12 ~ #15. Do not
turn UCMM Client Sending
T rigger for the same server to ON
with data sent to the server.
03 The 64DNET enters the
Connection established request to
itself.
Check the PLC program with
regard to BFM #8 ~ #11.
04 The 64DNET enters the UCMM
client sending trigger to itself. Check the PLC program wi th
regard to BFM #12 ~ #15.
05 FROM/TO WDT error Check the PLC program. The
PLC should access the BFMs
(one or more) on every scan.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-17
B4
Hardware error of 64DNET
00 EEPROM error
Check the program of PLC about
that accessing BFM of “Not used”,
and please contact a service
representative.
FF
Others
01 The specified service does not
support on the UCMM message. Check the packet data from the
Master or the client.
02 The message router object was
accessed.
03 The specified Class ID is
invalided.
04 The network power supply is not
supplied.
Check the connection and the
network power supply. Supply
current and voltage.
Table 8.5: 64DNET Error Code
Serv ic e Ty p e
(Upper Byte)
Detailed error
code
(Lower Byte) Description Check Points
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-18
8.3.2 DeviceNet Error Code (BFM #7 Bit 1 is OFF)
This error code is
g
eneral error code (upper b
y
te) and additional error co de (lower b
y
te).
Table 8.6: DeviceNet Error Code
General
Error
Code
Additional
Error Code Description Check Poin ts
02
Resourc e un av ail ab le
01 The Open Request Group Select is
incorrect.
Check the setting of all Masters.
02 Invali d al lo ca ti on /r el ea s e ch oi c e
parameter.
04 A necessary resource for Predef ined
Master/Sla ve connection set cannot
be used.
08
Service not supported
FF 64DNE T does not suppor t this
service.
Check the specifi cati on of client and
server for the UCMM connection, and
setting of the Master.
09
Invali d attribute value
02 Allocation request is incorrect. Check the specifi cati on of client and
server for the UCMM connection, and
setting of the Master
FF Set_Attribute_Single service error Check the data for
Set_Attribute_Single service.
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-19
13 Not enough data
FF Not enough data Check the length of send data. The
send data is too small.
14
Attribute not supported
FF 64DNE T does not suppor t this
attribute.
Check attribute ID in program for
64DNET and the setting of connected
client and server.
15 Too much data
FF Too much data Check the length of send data. The
send data is too large.
16
Object does not exist
FF 64DNET does not have this object.
Check object (class ID, instance ID,
attribute ID and service code) in
program for 64DNET, and the setting
of connected client and server.
0B Reserved by DeviceNet
02 Allocate/Release request for Poll,
COS and Cyclic is incorrect. Check the parameter of Master.
Table 8.6: DeviceNet Error Code
General
Error
Code
Additional
Error Code Description Check Poin ts
FX2N-64DNET DeviceNet Interface Block Diagnostics 8
8-20
0C
Reserved by DeviceNet
01 The MAC ID is incorrect Check wiring.
FF Set_Attribute_Single service error or
Rest service error (This o bject does
not support Set_At tribute_Single.)
Check class ID, instance ID, attribute
ID and service code in program for
64DNET, and setting of connected
client and server
20
Invalid parameter
FF Rest service error Check wiring, and class ID, instance
ID, at tribute ID and service code of
Master
Table 8.6: DeviceNet Error Code
General
Error
Code
Additional
Error Code Description Check Poin ts
A-1
Appendix A:
EDS (Electric Data Sheet)
The EDS (Electric Data Sheet) of 64DNET shows bellow.
Figure A-1: EDS of 64DNET
$ File Description Section
[File] DescText = "FX2N 32 word Input / 32 Word Output Slave Unit";
CreateDate = 01-06-2000;
CreateTime = 16:14:50;
ModDate = 01-06-2000;
ModTime = 16:14:50;
Revision = 1.0;
FX2N-64DNET DeviceNet Interface Block Appendix A
FX2N-64DNET DeviceNet Interface Block
A-2
Appendix A
$ Device Description Section
[Device] Vend Code = 161;
VendName = "Mitsubishi Electric Corporation";
ProdT
y
pe = 12;
ProdT
y
peStr = "Communication Adapter";
ProdCode = 3;
MajRev = 1;
MinRev = 1;
ProdName = "FX2N-64DNET";
Catalo
g
= "Users' Manual (JY992D86301)";
FX2N-64DNET DeviceNet Interface Block Appendix A
A-3
$ I/O Characte rist ics Section
[IO_Info] Default = 0x0001; $ Bit mapped
$ Bit 0 = Poll
$ Bit 1 = Strob e
$ Bit 2 = Chan
g
e of State
$ Bit 3 = C
y
clic
$ Bit 4-15 = Reserved
PollInfo = 0x000D, $ Combine C
y
clic,COS I/O with Poll
1, $ Default Input = Input1
1; $ Default Output = Output1
COSInfo = 0x000D, $ Combine Poll,C
y
clic I/O with COS
1, $ Default Input = Input1
1; $ Default Output = Output1
C
y
clicInfo = 0x000D, $ Combine Poll,COS I/O with C
y
clic
1, $ Default Input = Input1
1; $ Default Output = Output1
FX2N-64DNET DeviceNet Interface Block
A-4
Appendix A
Input1 =
0x04, $ Size in B
y
tes
0, $ All bits si
g
nificant
0x000D, $ Polled , COS or C
y
clic Connection
"Input Data", $ Name Strin
g
6, $ Path size
"20 04 24 64 30 03", $ IO Ass
y
Obj Inst 64 Attr 3
""; $ help strin
g
Output1 =
0x04, $ Size in B
y
tes
0, $ All bits si
g
nificant
0x000D, $ Polled ,COS or C
y
clic Connection
"Output Data", $ Name Strin
g
6, $ Path size
"20 04 24 65 30 03", $ IO Ass
y
Obj Inst 65 Attr 3
""; $ help strin
g
FX2N-64DNET DeviceNet Interface Block Appendix A
A-5
$ Parameter Class Section
$ [ParamClass]
$ Parameter Section
$ [Params]
$ Parameter Enumeration S e ction
$ [EnumPar]
$ Parameter Groups Section
$ [Groups]
$ End
FX2N-64DNET DeviceNet Interface Block
A-6
Appendix A
MEMO
FX2N-64DNET DeviceNet Interface Block Appendix B
B-1
Appendix B:
Class ID, Instance ID, Attribute ID and Service Code
B-1: Identity (0x01)
Class
Attribute Not support
Service Not support
Instance (01 Hex)
Attribute ID Description GET SET Value
1 Vendor ID 161
2 Device type 12
3Product code 3
4Revision
Major revison 1H
Minor revision 1H
5 Status DeviceNet spesifica-
tion
FX2N-64DNET DeviceNet Interface Block Appendix B
FX2N-64DNET DeviceNet Interface Block
B-2
Appendix B
B-2: Message Router (0x02)
Service DeviceNet service Parameter option
0E Get_Attribute_Single
10 Get_Attribute_Signal
4B Reset
4C Get_Attribute_Single
Vendor - spec i fi c ad di ti on al
specifications
Class
Attribute Not support
Service Not support
Instance
Attribute Not support
Service Not support
Vendor - spec i fi c ad di ti on al
specifications
FX2N-64DNET DeviceNet Interface Block Appendix B
B-3
B-3: DeviceNet (0x03)
Class
Attribute ID Description GET SET Value
1Revision 02
Service DeviceNet service Parameter option
0E Get_Attribute_Single
Instance
Attribute ID Description GET SET Setting Length
1 MAC ID 0 ~ 6 3
2 Device type 0: 125kbps
1: 250kbps
2: 500kbps
3 Baud rate 0
4BOI 0 ~ 255
5Bus-off counter
DeviceNet specifica-
tion
Alloction information
Master’s MAC ID
FX2N-64DNET DeviceNet Interface Block
B-4
Appendix B
Service DeviceNet service Parameter option
0E Get_Attribute_Single
10 Get_Attribute_Signal
48 Allocate M/S Connection
Set
4C Release M/S Connection
Set
Vendor - spec i fi c ad di ti on al
specifications
FX2N-64DNET DeviceNet Interface Block Appendix B
B-5
B-4: Assembly (0x04)
Class
Attribute Not support
Service Not support
Instance (64 Hex: input, 65 Hex output, 66 Hex: UCMM server, 67 Hex: UCMM client)
Attribute ID Description GET SET Value
3data
Service DeviceNet service Parameter option
0E Get_Attribute_Single
10 Set_Attribute_Signal
Vendor - spec i fi c ad di ti on al
specifications
FX2N-64DNET DeviceNet Interface Block
B-6
Appendix B
B-5: Connection (0x05)
Class
Attribute Not support
Service Not support
Maximum active connec-
tion 128
Instance (01 Hex, 0A ~ 49 Hex, 64 ~ A3 Hex, 67 Hex: Exp licit Message)
Section Information Number of maximum Instance
Instance Type Explicit Message
Production Trigger Change of State/Application
Trigger
Transport Type Server
Transport Class 3
Attribute ID Description GET SET Value
1 State DeviceNet specifica-
tion
2 Instance type 00 He x (Explicit Mes-
sage)
3 Transport class trigger 23 Hex (Client)
83 Hex (server)
FX2N-64DNET DeviceNet Interface Block Appendix B
B-7
4 Produceed connection ID DeviceNet specifica-
tion
5 Consumed connection ID DeviceNe t specifica-
tion
6Init ia l co m m. Ch arac te ris -
tics 21 Hex
7Produceed connection
size FFFF Hex
8Consumed connection
size FFFF Hex
9 Expected packet rate 2500 ms
12 Watchdog time-out Action 1 (Auto delete)
13 Produceed connection
path length 0
14 Produceed connection
path NULL
15 Consumed connection
path length 0
16 Consumed connection
path NULL
17 Produce_Inhibit_Time 0
FX2N-64DNET DeviceNet Interface Block
B-8
Appendix B
Service DeviceNet service Parameter option
05 Reset
0E Get_Attribute_Single
10 Set_Attribute_Single
Instance (02 Hex: I/O POLL)
Section Information Number of maximum Instance
Instance Type Polled I/O 1
Production Trigger Cyclic
Transport Type Server
Transport Class 2
Attribute ID Description GET SET Value
1 State DeviceNet specifica-
tion
2 Instance type 01 He x (I/O Message)
3 Transport class trigger 82 Hex (server, class
2)
4 Produceed connection ID DeviceNet specifica-
tion
5 Consumed connection ID DeviceNe t specifica-
tion
FX2N-64DNET DeviceNet Interface Block Appendix B
B-9
6Init ia l co m m. Ch arac te ris -
tics 01 Hex
7Produceed connection
size BFM setting
8Consumed connection
size BFM setting
9 Expected packet rate 0 ms
12 Watchdog time-out Action 0 (time-out)
13 Produceed connection
path length 6
14 Produceed connection
path 20 04 24 65 30 03 Hex
15 Consumed connection
path length 6
16 Consumed connection
path 20 04 24 65 30 03 Hex
17 Produce_Inhibit_Time 0
Service DeviceNet service Parameter option
0E Reset
10 Get_Attribute_Single
Set_Attribute_Single
FX2N-64DNET DeviceNet Interface Block
B-10
Appendix B
Instance (04 Hex: I/O COS)
Section Information Number of maximum Instance
Instance Type Polled I/O 2
Production Trigger COS
Transport Type Server
Transport Class 2
Attribute ID Description GET SET Value
1 State DeviceNet specifica-
tion
2 Instance type 01 He x (I/O Message)
3 Transport class trigger
4 Produceed connection ID DeviceNet specifica-
tion
5 Consumed connection ID DeviceNe t specifica-
tion
6Init ia l co m m. Ch arac te ris -
tics 01 Hex
7Produceed connection
size BFM setting
8Consumed connection
size 0
9 Expected packet rate 0 ms
FX2N-64DNET DeviceNet Interface Block Appendix B
B-11
12 Watchdog time-out Action 0 (time-out
13 Produceed connection
path length 6
14 Produceed connection
path 20 04 24 65 30 03 Hex
15 Consumed connection
path length No ACK: 0
ACK: 4
16 Consumed connection
path
No ACK: NULL
ACK: 20 2B 24 01
17 Produce_Inhibit_Time 0
Service DeviceNet service Parameter option
0E Reset
10 Get_Attribute_Single
Set_Attribute_Single
Vendor - spec i fi c ad di ti on al
specifications
FX2N-64DNET DeviceNet Interface Block
B-12
Appendix B
B-6: Acknowledge Handler Object (2B Hex)
Class
Attribute Not support
Service Not support
Instance (01 Hex)
Attribute ID Description GET SET Value
1 Acknowledge Timer 16
2 Retry Limit 1
3COS Producing Connec-
tion Instanse Connection Instance
ID
Service DeviceNet service Parameter option
0E Get_Attribute_Single
10 Get_Attribute_Signal
Vendor - spec i fi c ad di ti on al
specifications
C-1
Appendix C:
List of Further Information Manual
For further information manual about FX Series, refer to followin
g
table. For DeviceNet master
unit and other slave units, refe r to each unit manual.
Table C-1: List of Further Information Manual
Manual Name Manual No. Description
FX2N Hardware Manual JY992D66301 This manual contains hardware explanations of wiring,
installation and specifications for FX2N Series
prog rammable controllers.
FX0/FX0N Hardware Manual JY992D4750 1 This manual contains hardware explanations of wiring ,
installation and specifications for FX0 and FX0N Series
prog rammable controllers.
FX Programming Manual JY992D48301 This man ua l co nt ai ns ins tru c tio n ex pl an a tions for the
FX0, FX0S, FX0N, FX, FX2C, FX 2N and FX2NC Series
prog rammable controllers.
FX Programming Manual II JY992D88101 Thi s man ua l co nt ai ns ins tru c tio n ex pl an a tions for the
FX1S, FX1N, FX2N and FX2NC Seri es pr og r am mab le
controllers.
FX2N-64DNET DeviceNet Interface Block Appendix C
FX2N-64DNET DeviceNet Interface Block
C-2
Appendix C
MEMO
HEAD OFFICE: MITSUBISHI DENKI BLDG MARUNOUCHI TOKYO 100-8310 TELEX: J24532 CABLE MELCO TOKYO
HIMEJI WORKS: 840, CHIYODA CHO, HIMEJI, JAPAN
JY992D86301A
(MEE0004)
Effective Apr. 2000
Specification are subuject
tochan
g
e without notice.
USER’S MANUAL
FX2N-64DNET Devic eNet Interface Block
