Overview Of Fx 3U -Can Communication Block; Characteristics - Mitsubishi Electric MELSEC-F FX3U-CAN User Manual

FX -CAN User's Manual
3U
1.1.2 Overview of FX
®
CANopen ready I/O stations and device stations can be connected to the CAN bus and information can be
transmitted to the FX
1. The maximum send / receive message number
80 TPDO /80 RPDO (8 bytes / PDO) can be sent and received to/from a CANopen
®
2. CANopen device/application Profiles according to CiA
• Interface and Device Profile CiA
• Application Profile CiA
3. Communication with other CANopen
All nodes on the CANopen
has a unique identifying number that is read by the receiving nodes to determine whether that data should be
kept in the receiving nodes' Buffer Memory.
The FX -CAN communication block uses buffer memories to communicate on the CAN bus. Each buffer
3U
memory is separated into memory dedicated to write TO and memory dedicated to read FROM the CAN bus.
These Buffer Memories are accessed by FROM/TO commands of the PLC. However, only FX
FX5U/FX5UC PLC supports direct specification of the buffer memory.
For further information on applied instructions, bit specification of word devices and direct specification of
buffer memory, refer to the following manual.
Note
Buffer memory that is assigned in 32 bits must use 32-bit instructions to read/write.
32-bit data cannot be correctly read/written from/to buffer memory if 16-bit read/write instructions are used.
1.1.3

Characteristics

This section describes the characteristics of the CAN bus, communication with other CANopen
some of the special features available in the CANopen
1. The object dictionary
The Object Dictionary is a type of indexed storage system that contains data, device parameters, CANopen
feature setup data, instruction triggers, and other information necessary to configure and operate the
®
CANopen protocol.
2. SDO command
The Service Data Object Command can be used to read/write data to the Object Dictionary.
This command can be used to set network parameters and also to initiate CANopen
3. SYNC service
The SYNC service provides the basic network synchronization mechanism.
4. TIME service
The TIME service provides a simple network clock. CANopen
TIME object to adjust their own time base to that of the time stamp object producer.
5. EMCY object service
Emergency objects are triggered by the occurrence of a CANopen
transmitted from an emergency producer on the CANopen
16
-CAN communication block
3U
-CAN communication block and FX
3U
®
405 V2.0 for IEC 61131-3 Programmable Devices.
®
417 V2.1 for lift control systems.
®
®
network can write data to all the other nodes on the network. Each piece of data
/FX /FX
3G 3GC
®
Standards
nodes
→ Refer to PROGRAMMING MANUAL
®
protocol.
®
devices that operate a local clock may use the
®
device internal error situation and are
®
device.
1 Introduction
/FX /FX5U/FX5UC PLC.
3U 3UC
®
network.
®
®
functionality.
1.1 Outline
/FX /
3U 3UC
nodes, and
®