Jetter JX3-BN-EC User Manual page 29

Jetter AG
7.2 EtherCAT® object directories
Use with third-party
hardware
7.2.1 Overview
Object dictionary
Object
7.2.2 Object Dictionary JX3-BN-EC
JX3-BN-EC User Manual
You can also use the JX3-BN-EC in combination with a controller that was not
developed and produced by der Jetter AG.
To establish an EtherCAT
JX3-BN-EC, you need the object directory of the JX3-BN-EC and the object di-
rectories of the connected JX3 I/O modules.
With the CoE protocol, EtherCAT
®
as in the CANopen standard EN 50325-4:
■ Object dictionary
■ PDO mapping (Process Data Objects)
■ SDO (Service Data Objects)
This makes it possible to implement EtherCAT
equipped with CANopen
®
Since the EtherCAT slave JX3-BN-EC is based on the CoE protocol, it contains
an object directory. The object directory is the interface with which the EtherCAT
master (user) can access all relevant slave parameters.
The object directory is divided into different sections. Each index section is as-
signed a specific meaning:
Index section
0x0000 - 0x0FFF Data Type Description
0x1000 - 0x1FFF Communication objects
0x2000 - 0x5FFF Manufacturer Specific
0x6000 - 0x9FFF Profiles Specific
0xA000 - 0xFFFF Reserved
Each entry in the object directory is called an object.
An object consists of:
■ an index that identifies the object as a whole;
■ one or more subindexes, each of which contains elementary information.
Each subindex within each object has several attributes such as :
■ Data type
■ Access rights (RO = Read Only, WO = Write Only, RW = Read Write)
Sub- Description/
Index
index Name
0x1000 Device type
0x1001 Error register
0x1008 Device name
0x1009 Hardware version
0x100A Software version
®
connection between the third-party controller and the
®
offers the same communication mechanisms
®
at manageable costs.
Description
Type
UDINT
USINT
STRING (9)
STRING (4)
STRING (4)
Programming | 7
®
in slaves that were previously
Type of Base
access Type
RO
RO
RO
RO
RO
®
Ele-
ment
s
- -
- -
- -
- -
- -
29 / 92