Programming manual for Meca500 (for firmware 9.2.x)
83
ETHERCAT COMMUNICATION
4.2.16 Communication mode (SdO)
When EtherCAT is enabled, subindex 1 of this SDO is equal to 2 (see table below). Currently, you cannot
change the communication mode for port ECAT OUT and therefore subindex 2 of this SDO is ignored
(will always be the same as that of port ECAT IN). To switch both ports to TCP/IP, change the value of
subindex 1 to 1.
COMMUNICATION MODE SDO
Index SI O. code Type
Name
Default Min.
Max.
Access PDO
8000h
Record
Commun. mode
RO
n/a
1 Variable USINT Port In
1
1
2
RW
n/a
2 Variable USINT
Port Out (ignored)
1
1
2
RW
n/a
Table 38:
Communication mode SDO
4.3. PdO Mapping
The process data objects (PDOs) provide the interface to the application objects. The PDOs are used
to transfer data via cyclic communications in real time. PDOs can be reception PDOs (RxPDOs), which
receive data from the EtherCAT master (the PLC or the industrial PC), or transmission PDOs (TxPDOs),
which send the current value from the slave (the Meca500) to the EtherCAT master.
In the previous section, we listed the PDOs object dictionary. PDO assignment is summarized in the next
two tables.
RECEIVING PDO
PDO
Object(s)
Name
Note
1600h
7200h
RobotControl
Mandatory. See
.
1601h
7310h
MotionControl
Mandatory. See
1602h
7305h, 7306h
Movement
Mandatory. See
.
1610h
7400h
HostTime
Mandatory. See
1611h
7410h
BrakesControl
Mandatory. See
.
1620h
7420h
DynamicDataConfiguration 1
Mandatory. See
.
1621h
7421h
DynamicDataConfiguration 2
Mandatory. See
.
1622h
7422h
DynamicDataConfiguration 3
Mandatory. See
.
1623h
7423h
DynamicDataConfiguration 4
Mandatory. See
.
Table 39:
RxPDOs