Difference between revisions of "Category:EtherCAT:ECAT GENERAL GUIDE"
| Line 28: | Line 28: | ||
* [[EtherCAT:EC SDO READ STRING|EC_SDO_READ_STRING]] | * [[EtherCAT:EC SDO READ STRING|EC_SDO_READ_STRING]] | ||
<br/> | <br/> | ||
| − | From the ControlStudio's terminal the user can learn about the state of the ECat master and what | + | From the ControlStudio's terminal the user can learn about the state of the ECat master and what slaves are found by the ECat master on the [[:File:Axystems;EC_master_slave_position_topology.PNG|physical topology]]: |
* [[EtherCAT:EC_MASTER|EC_MASTER]] | * [[EtherCAT:EC_MASTER|EC_MASTER]] | ||
* [[EtherCAT:EC_SLAVES|EC_SLAVES]] | * [[EtherCAT:EC_SLAVES|EC_SLAVES]] | ||
* [[EtherCAT:EC MASTER OPMODE|EC_MASTER_OPMODE]] | * [[EtherCAT:EC MASTER OPMODE|EC_MASTER_OPMODE]] | ||
| + | Usually an ECat slave has many SDO objects that can be read or written. | ||
| + | |||
| + | When the real-time communication is initiated the ECat master asks the slaves to changed to Ethercat mode "SAFEOP". In this mode the clocks of the slaves | ||
| + | and the master are synchronized. This process may take up to a 30 seconds and it depends on the number of slaves in the topology. Once the clocks are synchronized the ECat master asks the slaves to change mode to "OP" | ||
| + | |||
| + | |||
| + | In order to create real-time communication that allows motion only a few objects are required: | ||
| + | From ECat master to slave: | ||
| + | Control word | ||
| + | Position command | ||
| + | From slave to ECat master: | ||
| + | Status word | ||
| + | Position feedback | ||
| + | |||
| + | The ECat slave must have these four objects mapped to a PDO in order to allow motion. | ||
Revision as of 14:41, 31 December 2014
Category:EtherCAT:ECAT GENERAL GUIDE EtherCAT - General Guide
The front page is EtherCAT
Introduction
From Wikipedia:
"EtherCAT - Ethernet for Control Automation Technology - is an Ethernet-based fieldbus system, invented by Beckhoff Automation. The protocol is standardized in IEC 61158 and is suitable for both hard and soft real-time requirements in automation technology.
The goal during development of EtherCAT was to apply Ethernet for automation applications requiring short data update times (also called cycle times; ≤ 100 µs) with low communication jitter (for precise synchronization purposes; ≤ 1 µs) and reduced hardware costs."
http://en.wikipedia.org/wiki/EtherCAT
softMC's current main fieldbus is EtherCAT and this guide will help you to setup the system. A part of softMC is a software entity called "EtherCAT Master". The ECat master is a part of the Linux kernel and it works in parallel to the Real-Time Motion task of the softMC. Connecting the softMC to ECat slaves ins't enough to create motion. A few actions must be carried out in order to setup the real-time communication that allows motion.
 | IMPORTANT |
|
It is critical to maintain the demonstrated order of the EtherCAT setup. Any change in the given example may result in undefined behavior! |
EtherCAT slaves and EtherCAT modes
Communication with an ECat slave can be done via SDO or via PDO. When a slave is powered up it automatically gets into ECat mode "INIT". If the slave senses that an ECat master is connected to the physical topology it automatically gets into ECat mode "PREOP". In this mode the ECat master can communicate with the slave, query some basic data that will later be used to setup the real-time communication, and allow the user to communicate with the slave via SDO. SDO communication isn't real-time. It is useful to gather data and configure the slave before starting the real-time communication. To use SDO communication please refer to:
From the ControlStudio's terminal the user can learn about the state of the ECat master and what slaves are found by the ECat master on the physical topology:
Usually an ECat slave has many SDO objects that can be read or written.
When the real-time communication is initiated the ECat master asks the slaves to changed to Ethercat mode "SAFEOP". In this mode the clocks of the slaves and the master are synchronized. This process may take up to a 30 seconds and it depends on the number of slaves in the topology. Once the clocks are synchronized the ECat master asks the slaves to change mode to "OP"
In order to create real-time communication that allows motion only a few objects are required:
From ECat master to slave:
Control word
Position command
From slave to ECat master:
Status word
Position feedback
The ECat slave must have these four objects mapped to a PDO in order to allow motion.
Drive Address
Example
See Also
- Setup EtherCAT - How to setup EtherCAT
- EC_ETHERCAT_INIT
This category currently contains no pages or media.