Hilscher comX 100CA-RE, 100CN-RE, 50CA-REFO, 51CA-RE, 51CN-RE Communication Modules, comX 10CA-COS, 10CN-COS, 10CA-DNS, 10CN-DNS, 10CA-DPS, 10CN-DPS Communication Module, COMXEB Evaluation Board User Manual

User Manual comX

Communication Modules for Real-Time-Ethernet and Fieldbus

Hilscher Gesellschaft für Systemautomation mbH www.hilscher.com

DOC100903UM05EN | Revision 5 | English | 2015-12 | Released | Public

Introduction 2/212

Table of Contents

1 INTRODUCTION.........................................................................................................9

1.1

About this Manual .......................................................................................................9

1.1.1

Mandatory read Manual .......................................................................................9

1.1.2

1.1.3

1.1.4

List of Revisions .................................................................................................10

Reference to Hardware, Software and Firmware...............................................11

Conventions in this Manual ................................................................................13

1.2

Contents of Product DVD .........................................................................................14

1.2.1

Device Description Files.....................................................................................14

1.2.2

1.2.3

Documentation Overview comX .........................................................................16

Important Changes.............................................................................................17

1.3

Ensuring Access Security .........................................................................................20

1.4

Legal Notes...............................................................................................................21

1.4.1

Copyright ............................................................................................................21

1.4.2

1.4.3

1.4.4

1.4.5

1.4.6

1.4.7

Important Notes ..................................................................................................21

Exclusion of Liability ...........................................................................................22

Warranty .............................................................................................................22

Export Regulations .............................................................................................23

Registered Trademarks......................................................................................23

EtherCAT Disclaimer..........................................................................................24

1.5

Licenses....................................................................................................................24

2 SAFETY ....................................................................................................................25

2.1

General Note ............................................................................................................25

2.2

Intended Use ............................................................................................................25

2.2.1

Intended Use of comX Communication Modules ...............................................25

2.3

Personnel Qualification.............................................................................................26

2.4

Commitment to read and understand the Manual ....................................................26

2.5

Safety Instructions ....................................................................................................27

2.5.1

Electrical Shock Hazard .....................................................................................27

2.6

Safety Instructions to avoid Property Damage .........................................................27

2.6.1

Device Destruction by exceeding allowed Supply Voltage ................................27

2.6.2

2.6.3

Device Destruction by exceeding allowed Signal Voltage .................................28

Electro-statically sensitive Devices ....................................................................28

2.7

Labeling of Safety Messages....................................................................................29

2.7.1

References Safety..............................................................................................29

3 DESCRIPTIONS AND REQUIREMENTS .................................................................30

3.1

Description................................................................................................................30

3.1.1

Block Diagrams ..................................................................................................31

3.1.2

System Requirements ........................................................................................32

3.2

Prerequisites for the Operation of the comX Communication Modules ....................33

comX | Communication Modules for Real-Time-Ethernet and Fieldbus

DOC100903UM05EN | Revision 5 | English | 2015-12 | Released | Public © Hilscher, 2010-2015

Introduction

3.2.1

3.2.2

3.2.3

3/212

Prerequisites for the Operation as Embedded System......................................33

Prerequisites for the Operation with Evaluation Board COMXEB......................34

Remarks on Storage Stability and Contact Reliability of Host-side Connector..34

3.3

Supply Voltage and Signaling Voltage......................................................................35

3.4

Prerequisites for the Software Installation ................................................................35

3.4.1

Prerequisites for the System Configurator SYCON.net .....................................35

3.5

Prerequisites for Certification....................................................................................36

3.5.1

PROFINET-IO Certification for IRT and SYNC0 Signal .....................................36

4 GETTING STARTED COMX COMMUNICATION MODULES ..................................37

4.1

Hardware Installation as Embedded System (Master and Slave) ............................37

4.2

Configuration of the comX Communication Module (Slave) .....................................39

4.3

Configuration of the comX Communication Module (Master) ...................................41

4.4

Notes for the Configuration of the Master Device.....................................................42

4.5

Device Names in SYCON.net...................................................................................44

4.6

Exchange of comX Communication modules (Master and Slave)............................46

4.6.1

Steps for Exchange of Hardware .......................................................................46

4.6.2

4.6.3

Load Firmware & Configuration into Replacement Module comX (Slave).........47

Load Firmware & Configuration into Replacement Module comX (Master).......48

4.7

Updating the Firmware, Driver and Software............................................................49

5 HARDWARE INSTALLATION, DEINSTALLATION AND REPLACEMENT ..............50

5.1

Warning Messages on Personal Injury .....................................................................50

5.1.1

Electrical Shock Hazard .....................................................................................50

5.2

Property Damage Messages ....................................................................................50

5.2.1

Device Destruction by exceeding allowed Supply Voltage ................................50

5.2.2

5.2.3

Device Destruction by exceeding allowed Signaling Voltage ............................51

Electro-statically sensitive Devices ....................................................................51

5.3

Installing the comX Communication Module in its Target Environment....................52

5.4

Decommissioning .....................................................................................................52

6 INSTALLING THE SOFTWARE ................................................................................53

7 DEVICE PHOTOS (POSITION OF SWITCHES, LEDS AND INTERFACES) ...........54

7.1

Real-Time Ethernet Communication Module COMX 100CA-RE ..............................54

7.1.1

7.1.2

COMX 100CA-RE...............................................................................................54

Ethernet Interface of COMX 100CA-RE.............................................................55

7.2

Real-Time Ethernet Communication Module COMX 100CN-RE..............................56

7.2.1

COMX 100CN-RE ..............................................................................................56

7.2.2

Ethernet Interface of COMX 100CN-RE.............................................................56

7.3

Real-Time Ethernet Communication Module COMX 50CA-REFO with Fiber Optic .57

7.3.1

7.3.2

COMX 50CA-REFO............................................................................................57

Optical Ethernet Interface of COMX 50CA-REFO .............................................58

7.4

Real-Time Ethernet Communication Module COMX51CA-RE ................................59



Introduction

7.4.1

7.4.2

4/212

COMX51CA-RE..................................................................................................59

Ethernet Interface of COMX51CA-RE................................................................60

7.5

Real-Time Ethernet Communication Module COMX 51CN-RE................................61

7.5.1

COMX 51CN-RE ................................................................................................61

7.5.2

Ethernet Interface of COMX 51CN-RE...............................................................61

7.6

CANopen Communication Module COMX 100CA-CO .............................................62

7.6.1

7.6.2

COMX 100CA-CO ..............................................................................................62

CANopen Interface of COMX 100CA-CO ..........................................................63

7.7

CANopen Communication Module COMX 100CN-CO .............................................64

7.7.1

7.7.2

COMX 100CN-CO..............................................................................................64

CANopen Interface of COMX 100CN-CO ..........................................................64

7.8

DeviceNet Communication Module COMX 100CA-DN ............................................65

7.8.1

COMX 100CA- DN .............................................................................................65

7.8.2

DeviceNet Interface of COMX 100CA-DN .........................................................66

7.9

DeviceNet Communication Module COMX 100CN-DN ............................................67

7.9.1

7.9.2

COMX 100CN-DN ..............................................................................................67

DeviceNet Interface of COMX 100CN-DN .........................................................67

7.10

PROFIBUS-DP Communication Module COMX 100CA-DP.....................................68

7.10.1

COMX 100CA-DP...............................................................................................68

7.10.2

PROFIBUS-DP Interface of COMX 100CA-DP..................................................69

7.11

PROFIBUS-DP Communication Module COMX 100CN-DP ....................................70

7.11.1

7.11.2

COMX 100CN-DP ..............................................................................................70

PROFIBUS-DP Interface of COMX 100CN-DP .................................................70

7.12

CC-Link Communication Module COMX 10CA-CCS................................................71

7.12.1

COMX 10CA-CCS..............................................................................................71

7.12.2

7.12.3

Description of the Address and Baudrate Switches ...........................................72

CC-Link Interface of COMX 10CA-CCS.............................................................72

7.13

CC-Link Communication Module COMX 10CN-CCS ...............................................73

7.13.1

COMX 10CN-CCS..............................................................................................73

7.13.2

Description of the Address and Baudrate Switches ...........................................73

7.13.3

CC-Link Interface of COMX 10CN-CCS.............................................................73

7.14

CANopen Communication Module COMX 10CA-COS.............................................74

7.14.1

COMX 10CA-COS..............................................................................................74

7.14.2

7.14.3

Description of the Address Switches..................................................................74

CANopen Interface of COMX 10CA-COS..........................................................75

7.15

CANopen Communication Module COMX 10CN-COS.............................................76

7.15.1

7.15.2

7.15.3

COMX 10CN-COS..............................................................................................76


CANopen Interface of COMX 10CN-COS..........................................................76

7.16

DeviceNet Communication Module COMX 10CA-DNS ............................................77

7.16.1

COMX 10CA-DNS..............................................................................................77

7.16.2

7.16.3


DeviceNet Interface of COMX 10CA-DNS .........................................................78

7.17

DeviceNet Communication Module COMX 10CN-DNS............................................79

7.17.1

COMX 10CN-DNS..............................................................................................79

7.17.2




Introduction

7.17.3

5/212

DeviceNet Interface of COMX 10CN-DNS.........................................................80

7.18

PROFIBUS-DP Communication Module COMX 10CA-DPS ....................................81

7.18.1

COMX 10CA-DPS ..............................................................................................81

7.18.2

7.18.3


PROFIBUS-DP Interface of COMX 10CA-DPS .................................................82

7.19

PROFIBUS-DP Communication Module COMX 10CN-DPS ....................................83

7.19.1

7.19.2

7.19.3

COMX 10CN-DPS ..............................................................................................83


PROFIBUS-DP Interface of COMX 10CN-DPS .................................................84

8 EVALUATION BOARD COMXEB .............................................................................85

8.1

Purpose ....................................................................................................................85

8.2

Controls ....................................................................................................................88

8.2.1

8.2.2

8.2.3

8.2.4

Position for host mode selection- Slide switch (S302) .......................................88

Selection of operation mode (DPM/SPM) - Slide switch (S701) ........................88

Width for data access at parallel DPM mode - Slide switch (S301)...................88

Selection of serial interface - Slide switch (S700) ..............................................89

8.2.5

8.2.6

8.2.7

Reset pushbutton (S600) ...................................................................................89

Boot-Jumper (X610) ...........................................................................................89

Configuration of AIFX Interface - Jumpers (X406 and X407) ............................89

8.3

Interfaces and connectors ........................................................................................92

8.3.1

Power supply connectors ...................................................................................92

8.3.2

8.3.3

8.3.4

Host Interfaces ...................................................................................................93

COMX Interfaces ................................................................................................97

Communication Interfaces................................................................................105

8.3.5

8.3.6

8.3.7

Diagnostic Interfaces........................................................................................107

Extension Interfaces.........................................................................................108

Pin Headers......................................................................................................108

8.4

LED displays...........................................................................................................110

8.4.1

Power LEDs......................................................................................................110

8.4.2

8.4.3

Communication Status LEDs ...........................................................................110

Ethernet Link/Activity–LEDs .............................................................................111

8.5

Accessories ............................................................................................................111

9 CONNECTION TO THE PC ....................................................................................112

9.1

Overview.................................................................................................................112

9.2

Diagnostic connections...........................................................................................112

9.2.1

Via USB ............................................................................................................112

9.2.2

Via UART..........................................................................................................113

9.3

Host connections ....................................................................................................114

9.3.1

Parallel dual-port memory interface (DPM)......................................................114

9.3.2

9.3.3

Serial dual-port memory interface (SPM).........................................................115

Serial dual-port memory interface over USB (SPM over USB)........................116

10 LEDS.......................................................................................................................117

10.1

SYS-LED ................................................................................................................117



Introduction 6/212

10.2

LEDs Fieldbus-Systems .........................................................................................117

10.2.1

10.2.2

10.2.3

10.2.4

10.2.5

LED Names of individual Fieldbus Systems ....................................................117

LEDs PROFIBUS-DP Master ...........................................................................118

LEDs PROFIBUS-DP Slave .............................................................................118

LEDs PROFIBUS MPI......................................................................................119

LEDs CC-Link Slave.........................................................................................119

10.2.6

10.2.7

10.2.8

10.2.9

LEDs CANopen Master ....................................................................................120

LEDs CANopen Slave ......................................................................................121

LEDs DeviceNet Master ...................................................................................122

LEDs DeviceNet Slave .....................................................................................123

10.3

LEDs Real-Time Ethernet Systems ........................................................................124

10.3.1

LED Names of individual Real-Time Ethernet Systems...................................124

10.3.2

10.3.3

LEDs EtherCAT-Master....................................................................................125

LEDs EtherCAT-Slave......................................................................................126

10.3.4

10.3.5

10.3.6

10.3.7

10.3.8

LEDs EtherNet/IP-Scanner (Master)................................................................128

LEDs EtherNet/IP-Adapter (Slave)...................................................................129

LEDs Open Modbus/TCP.................................................................................130

LEDs POWERLINK Controlled Node/Slave.....................................................131

LEDs PROFINET IO-RT-Controller..................................................................132

10.3.9

LEDs PROFINET IO-RT-IRT-Device ...............................................................133

10.3.10

LEDs Sercos-Master ........................................................................................134

10.3.11

LEDs Sercos-Slave ..........................................................................................136

10.3.12

LEDs VARAN Client .........................................................................................138

11 TROUBLESHOOTING ............................................................................................139

12 UPDATING THE FIRMWARE .................................................................................140

12.1

Possibilities of Firmware Update ............................................................................140

12.1.1

Update the comX-Firmware in built-in State(Embedded System) ...................140

12.1.2

Updating the Firmware using an Evaluation Board COMXEB and a PC .........142

12.2

Update the Firmware with SYCON.net ...................................................................147

12.2.1

Troubleshooting................................................................................................151

13 DIAGNOSTIC INTERFACES ..................................................................................156

13.1

Support of Diagnostic Interfaces by comX Firmware..............................................156

13.2

Hint concerning the Usage of the Software ............................................................157

13.3

Hardware Modification of comX Module for Recognition of comX-Reset at a connected Windows

®-

Diagnosis PC .......................................................................157

14 TECHNICAL DATA .................................................................................................158

14.1

Technical Data of COMX Modules .........................................................................158

14.1.1

COMX 100CA-RE.............................................................................................158

14.1.2

COMX 100CN-RE ............................................................................................159

14.1.3

COMX 100CA-CO ............................................................................................160

14.1.4

14.1.5

14.1.6

14.1.7

COMX 100CN-CO............................................................................................161

COMX 100CA-DN ............................................................................................162

COMX 100CN-DN ............................................................................................163

COMX 100CA-DP.............................................................................................164



Introduction 7/212

14.1.8

14.1.9

COMX 100CN-DP ............................................................................................165

COMX 50CA-REFO..........................................................................................166

14.1.10

COMX 51CA-RE...............................................................................................167

14.1.11

COMX 51CN-RE ..............................................................................................168

14.1.12

COMX 10CA-CCS............................................................................................169

14.1.13

COMX 10CN-CCS............................................................................................170

14.1.14

COMX 10CA-COS............................................................................................171

14.1.15

COMX 10CN-COS............................................................................................172

14.1.16

COMX 10CA-DNS............................................................................................173

14.1.17

COMX 10CN-DNS............................................................................................174

14.1.18

COMX 10CA-DPS ............................................................................................175

14.1.19

COMX 10CN-DPS ............................................................................................176

14.2

Electrical Immunity to Interference and Radio Frequency ......................................177

14.3

Technical Data Evaluation Board COMXEB...........................................................178

14.4

Technical Data of Communication Protocols..........................................................180

14.4.1

EtherCAT Master..............................................................................................180

14.4.2

14.4.3

14.4.4

14.4.5

14.4.6

EtherCAT Slave................................................................................................181

EtherNet/IP Scanner (Master) ..........................................................................182

EtherNet/IP Adapter (Slave).............................................................................183

Open Modbus/TCP...........................................................................................184

Powerlink Controlled Node/Slave.....................................................................184

14.4.7

14.4.8

14.4.9

PROFINET IO-RT-Controller (Master) .............................................................185

PROFINET IO Device (V3.4)............................................................................186

PROFINET IO Device (V3.5)............................................................................187

14.4.10

Sercos-Master ..................................................................................................188

14.4.11

Sercos-Slave ....................................................................................................189

14.4.12

VARAN Client ...................................................................................................190

14.4.13

CANopen Master ..............................................................................................191

14.4.14

CANopen Slave ................................................................................................192

14.4.15

CC-Link Slave...................................................................................................194

14.4.16

DeviceNet Master.............................................................................................195

14.4.17

DeviceNet Slave ...............................................................................................196

14.4.18

PROFIBUS DP Master .....................................................................................197

14.4.19

PROFIBUS DP Slave .......................................................................................198

14.4.20

PROFIBUS MPI................................................................................................199

15 DECOMMISSIONING, REPLACEMENT AND DISPOSAL .....................................200

15.1

Put the Device out of Operation..............................................................................200

15.2

Disposal of Waste Electronic Equipment................................................................201

16 GLOSSARY.............................................................................................................202

17 APPENDIX ..............................................................................................................206

17.1

Matrix Label ............................................................................................................206

17.2

Wiring Instructions for Fieldbus Systems................................................................206

17.3

EtherNet/IP Adapter/Slave – Instance ID of I/O Data .............................................206

17.4

Use of VARAN Client..............................................................................................207



Introduction 8/212

17.5

Failure in 10 MBit/s Half Duplex Mode and Workaround........................................207

17.6

List of Figures .........................................................................................................208

17.7

List of Tables ..........................................................................................................209

17.8

Contacts..................................................................................................................212



Introduction

1 Introduction

9/212

1.1 About this Manual

This manual contains a description of the communication modules of the comX product family from Hilscher based on the communication controllers netX.

The comX product family consists of the comX Real-Time Ethernet modules, with electrical (RE types) or optical Ethernet interface (REFO types) and comX Fieldbus Master-modules (into which also a slave firmware of the matching communication system may be downloaded).

This manual contains information about the installation, configuration, commissioning and use of the modules.

The comX communication modules for Real-Time Ethernet and Fieldbus have been designed as part („Embedded System“) of an electronic device or system. This electronic device is denominated as target system or host system of the comX communication system within the scope of this document.

However, the integration of the comX modules (as embedded systems) into their target system („Host“) is not topic of this manual. It is described in detail in a separate manual, namely the comX Design Guide, for details see section “Documentation Overview comX” on page 16.

Important!

Read and understand all instructions before installation of the communication module to avoid injury. First read the Safety chapter.



Introduction 10/212

1.1.2 List of Revisions

Index Date Chapter

3 2012-06-04

10.3.3

14.3

10.2.3

10.2.7

10.2.8

10.2.9

10.3.11

13.1

13.3

14.1.1

1.2.1

1.2.1

1.2.3

3.2.3

3.4.1

7.1.2

7.3.2

7.4

14.1.10

14.4.2

14.4.3

14.4.4

14.4.9

14.4.10

14.4.11

14.4.14

14.4.18

8

9

10.3.11

12

14.1.7

14.1.11

14.3

Revision

Added typical current consumption of COMX50CA-REFO and all COMX10 in

Technical Data

Update of EtherCAT Slave LED descriptions

Update of technical data of CANopen Slave, EtherNet/IP Adapter and Sercos

Slave V3.

Firmware names for COMX 51CA-RE added.

Names of device description files for COMX 51CA-RE added.

Table 5

and Table 6 added.

Section Important Changes updated.

Section on long-term contact reliability of host-side connector added.

System requirements for SYCON.net updated.

Figure 4: Pinning of Ethernet Interface of COMX 100CA-RE

updated.

Denomination of AVAGO transceiver chip corrected.

Section COMX 51CA-RE added.

Section LEDs PROFIBUS-DP Slave updated.

Section LEDs CANopen Slave updated.

Section LEDs DeviceNet Master updated.

Section LEDs DeviceNet Slave updated.

Section LEDs Sercos-Slave updated.

Table 83: Firmware Versions with Support for Diagnostic Interface

updated.

Table 84: First Hardware Version with new USB Interface

updated.

Temperature range of COMX-CA-RE Rev. 8

Technical data concerning COMX 51CA-RE added.

Section EtherCAT Slave updated.

Section EtherNet/IP Scanner (Master) updated.

Section EtherNet/IP Adapter (Slave) updated.

Section PROFINET IO Device (V3.5) added.

Section Sercos-Master updated.

Section Sercos-Slave updated.

Section CANopen Slave updated.

Section PROFIBUS DP Master updated.

New section “Real-Time Ethernet Communication Module COMX 51CN-RE“

New chapter “Evaluation Board COMXEB”

New chapter “Connection to the PC”

Section LEDs Sercos-Slave updated.

Chapter “Updating the Firmware” completely reworked for new evaluation board

COMXEB

Section “COMX 100CA-DP” in chapter “Technical Data”: Correction of ambient temperature range, value from German version which is corrected, has been adapted.

New section “COMX 51CN-RE”

New section “Technical Data Evaluation Board COMXEB” comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 11/212

1.1.3 Reference to Hardware, Software and Firmware

Remark concerning Software Update: The hardware revisions mentioned in this section and the versions of firmware, driver and configuration software belong together functionally. The firmware, the driver and the configuration software must be updated according to the specifications of this section at present hardware installation.

An overview on firmware update issues is given in section

Updating

the

Firmware

on page 140.

Hardware

Module Revision

Real-Time Ethernet Modules (Master/Slave) with netX 100 Processor

COMX 100CA-RE Revision 8

COMX 100CN-RE Revision 2

Real-Time Ethernet Modules (Slave) with netX 51 Processor

COMX 51CA-RE

COMX 51CN-RE

Revision 1

Revision 1

Real-Time Ethernet Modules (Slave) with netX 50 Processor/Fiber Optic

COMX 50CA-REFO Revision 2

Fieldbus Master/Slave Modules with netX 100 Processor

COMX 100CA-CO

COMX 100CA-DN

COMX 100CA-DP

Revision 4

Revision 4

Revision 4

COMX 100CN-CO

COMX 100CN-DN

COMX 100CN-DP

Fieldbus Slave-Modules with netX 10 Processor

COMX 10CA-CCS

COMX 10CN-CCS

COMX 10CA-COS

COMX 10CN-COS

COMX 10CA-DNS

COMX 10CN-DNS

COMX 10CA-DPS

COMX 10CN-DPS

Evaluation Board

Revision 3

Revision 3

Revision 3

Revision 2

Revision 2

Revision 2

Revision 1

Revision 2

Revision 1

Revision 2

Revision 1

Table 1: Reference to Hardware

Software

Software

SYCON.net cifX Device Driver

Toolkit

Table 2: Reference to Software

Software Version

V 1.360.x.x

V

1.2.x.x

V

1.1.x.x comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction

Firmware

Firmware

Real-Time Ethernet

comXecm.nxf

EtherCAT Master comXecs.nxf

EtherCAT Slave comXecs.nxf

EtherCAT Slave V4 comXeim.nxf

EtherNet/IP Scanner comXeis.nxf

EtherNet/IP Adapter

3.0.x.x

2.5.34.x

4.2.11.x

2.6.x.x comXomb.nxf

Open Modbus/TCP

2.5.x.x comXpls.nxf

POWERLINK Controlled Node 2.1.x.x comXpnm.nxf

PROFINET IO Controller comXpns.nxf

PROFINET IO Device V3

2.7.x.x

2.6.x.x

3.4.x.x

3.5.x.x comXpns.nxf

PROFINET IO Device V3.5 comXs3m.nxf

Sercos Master comXs3s.nxf

Sercos Slave comXvrs.nxf

VARAN Client

2.1.x.x

3.1.x.x

1.0.x.x

3.4.x.x cx50pns.nxf


Fiber Optics cx50pns.nxf

PROFINET IO Device V3.5

Fiber Optics

M060F000.nxf

EtherCAT Slave V4

3.5.x.x

4.2.11.x

M060H000.nxf

M060L000.nxf

EtherNet/IP Adapter

Open Modbus/TCP cx51pns.nxf

PROFINET IO Device V3.5

M060J000.nxf

Sercos Slave

2.7.13.x

2.5.11.x

3.5.26.x

3.1.19.x

Fieldbus

comXcom.nxf

CANopen Master comXcos.nxf

comXdnm.nxf

comXdns.nxf

comXdpm.nxf

comXdps.nxf

Protocol

CANopen Slave

DeviceNet Master

DeviceNet Slave

PROFIBUS DP Master

PROFIBUS DP Slave

M0203000.nxf

M0505000.nxf

M0509000.nxf

M0507000.nxf

M0502000.nxf

PROFIBUS MPI

CANopen Slave

CC-Link Slave

DeviceNet Slave

PROFIBUS DP Slave

Firmware

Version

For Hardware

2.11.x.x

3.6.x.x

2.3.x.x

2.3.x.x

2.6.x.x

2.7.x.x

2.4.x.x

3.6.x.x

2.9.x.x

2.3.x.x

2.7.x.x

COMX 100CA-RE,

COMX 100CN-RE

COMX 50CA-REFO

COMX 51CA-RE,

COMX 51CN-RE

COMX 100CA-CO,

COMX 100CN-CO

COMX 100CA-CO,

COMX 100CN-CO

COMX 100CA-DN

COMX 100CN-DN

COMX 100CA-DN

COMX 100CN-DN

COMX 100CA-DP,

COMX 100CN-DP

COMX 100CA-DP,

COMX 100CN-DP

COMX 100CA-DP,

COMX 100CN-DP

COMX 10CA-CO,

COMX 10CN-CO

COMX 10CA-CC

COMX 10CN-CC

COMX 10CA-DN

COMX 10CN-DN

COMX 10CA-DP,

COMX 10CN-DP

Table 3: Reference to Firmware

12/212 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 13/212

The following firmware is still available for legacy applications but development of this firmware has been discontinued. For new developments use version 3.4 instead.

Firmware Protocol For Hardware

comXpns.nxf


Firmware

Version

2.1.45.x COMX 100CA-RE,

COMX 100CN-RE

Table 4: Reference to old Firmware still available for Legacy Applications

1.1.4 Conventions in this Manual

Operation instructions, a result of an operation step or notes are marked as follows:

Operation Instructions:

!

<instruction> or

1. <instruction>

2. <instruction>

Results:

" <result>

Notes:

Important: <important note>

Note: <note>

<note, where to find further information> comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 14/212

1.2 Contents of Product DVD

The Communication Solutions DVD for the comX communication modules contains installation information, the required configuration software, drivers, documentation and further tools for your comX communication module.

1.2.1 Device Description Files

The cifX DVD EDS directory includes the device description files for the following kinds of comX Real-Time Ethernet Slave modules :

Device Description Files comX Modules Real-Time Ethernet (Slave)

Real-Time Ethernet Name / Extension

COMX 100CA-RE, COMX 100CN-RE

EtherCAT Slave (V2)

Hilscher COMX 100XX RE ECS

V2.2.X.xml

EtherCAT Slave (V4)


V4.2.X.xml

EtherNet/IP Adapter (Slave)

Powerlink Controlled Node / Slave

PROFINET IO-RT-Device (V3.4)

HILSCHER COMX 100XX-RE EIS V1.1.EDS

00000044_COMX 100XX RE PLS.xdd

GSDML-V2.3-HILSCHER-COMX 100XX-RE

PNS-20130225.xml

PROFINET IO-RT-Device (V3.5) netX 100

PROFINET IO-RT-Device (V2)

(on request, only for legacy applications)

Sercos Slave (V3)


PNS-20130301.xml

GSDML-V2.1-HILSCHER-COMX RE PNS-

20081210.xml

Hilscher COMX RE S3S FixCFG FSPIO

Default.xml

(see note below)

COMX 51CA-RE, COMX 51CN-RE

EtherCAT Slave (V4)


V4.2.X.xml

EtherNet/IP Adapter (Slave)

PROFINET IO-RT-Device (V3.5) netX 51

Sercos Slave (V3)

HILSCHER COMX 51XX-RE EIS V1.1.EDS


PNS-20131010.xml

Hilscher COMX51XX RE S3S FixCFG

FSPIO Default.xml

(see note below)

COMX 50CA-REFO

PROFINET IO-RT-Device (V3.4)

Fiber Optic

PROFINET IO-RT-Device (V3.5) netX 50 Fiber Optic

GSDML-V2.3-HILSCHER-COMX 50XX-REFO

PNS-20130225.xml

GSDML-V2.3-HILSCHER-COMX 50XX-REFO

PNS-20130301.xml

Table 5: Device Description Files comX Modules Real-Time Ethernet (Slave)

Note:

If you use a sercos Master which is using SDDML files for configuration, and one of the defaults for vendor code, device ID, input data size or output data size was changed, then you have to export a new updated SDDML file from

SYCON.net and import this SDDML file into the configuration software for the sercos Master.

The device description file is required to configure the used Real-Time

Ethernet Master:

• EtherCAT Master comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 15/212

• EtherNet/IP Scanner,

• POWERLINK Managing Node,

• PROFINET IO Controller,

• Sercos Master.

• VARAN Client

Device Description Files for comX Modules Fieldbus (Slave)

Fieldbus Name / Extension

CC-Link Slave For COMX 50: comx50xx-ccs_1.csp comx50xx-ccs_2.csp comx50xx-ccs_3.csp comx50xx-ccs_4.csp comx50xx-ccs-io_1.csp

For COMX 10:

CANopen Slave

DeviceNet Slave

PROFIBUS DP Slave comx10xx-ccs_1.csp comx10xx-ccs_2.csp comx10xx-ccs_3.csp comx10xx-ccs_4.csp comx10xx-ccs-io_1.csp

For COMX 10: COMX 10XX-COS COS.eds

For COMX 100: COMX 100XX-CO COS.eds

For COMX 10: COMX_10XX-DNS_DNS.EDS

For COMX 100: COMX_100XX-DN_DNS.EDS

For COMX 10: HIL_0D82.GSD

For COMX 100: HIL_0C0F.GSD

Table 6:Device Description Files comX Modules Fieldbus (Slave)

The device description file is required to configure the used

• CC-Link Master

• CANopen Master

• DeviceNet Master

• PROFIBUS-DP Master

Device Description Files comX Modules Real-Time Ethernet (Master)

Furthermore, for the following comX communication modules Real-Time

Ethernet (Master) there are device description files available on the COMX-

DVD within the EDS directory:


EtherNet/IP Scanner (Master)

Name / Extension

HILSCHER COMX 100XX-RE EIM V1.0.eds

Table 7: Device Description Files comX Modules Real-Time Ethernet (Master)

These device description files for EtherNet/IP-Master devices are required if an additional Ethernet/IP Master device shall communicate with a

Hilscher-Ethernet/IP Master device via Ethernet/IP.

The Real-Time Ethernet system Open Modbus/TCP does not use device description files. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 16/212

1.2.2 Documentation Overview comX

The following documentation overview gives information, for which items you can find further information in which manual.

All these documents are available on the Communication Solutions DVD delivered with the device underneath the directory Documentation, in

Adobe Acrobat

®

Reader format (PDF). You can also use the latest edition of a manual, which is available on the website www.hilscher.com

under

Support > Downloads > Manuals or under Products directly with the information about your product. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 17/212

1.2.3.1

Firmware

Header

GSDML

PROFINET IO-Device Firmware Versions 3.4 and 3.5

The PROFINET IO Device firmware was revised and completed and is available in version 3.5 since the third quarter 2013.

Use the PROFINET IO Device firmware in version 3.5 for a new installation, when you create or develop your application program for the first time.

If you want to change in an existing system from the PROFINET IO Device firmware version 3.4 to the version 3.5, note the following guidelines:

1. Customize your application program according to the Migration Guide

PROFINET IO Device, Migration from V3.4 to V3.5

.

If you want to change to V3.5, please check in the Migration Guide

PROFINET IO Device, Migration from V3.4 to V3.5 which changes are necessary in the application program in order to use version 3.5.

2. Adjust the configuration of your PROFINET IO Controller device. Use the new GSDML files in the configuration software of the PROFINET IO

Controller for this:

- GSDML-V2.3-HILSCHER-COMX 50XX-REFO PNS-20130301.xml

,

- GSDML-V2.3-HILSCHER-COMX 100XX-RE PNS-20130301.xml or

- GSDML-V2.3-HILSCHER-COMX 51XX-RE PNS-20131010.xml

3. Update the PROFINET IO Device firmware in your device to version

3.5.

Note also:

• SYCON.net V1.360.x.x can configure the PROFINET IO Device firmware V3.4 as well as V3.5

• netX Configuration Tool V1.0510.x.x can configure the PROFINET IO

Device firmware V3.4 as well as V3.5.

• The development of the PROFINET IO Device firmware V3.4 will not be continued, but this firmware version will be delivered furthermore.

On the Communication Solutions DVD, software and manuals relating to both firmware versions V3.4 and V3.5 are available:

PROFINET IO-Device V3.4

Directory on the DVD \ File:

PROFINET IO-Device V3.5


Firmware\COMX\comxpns.nxf Firmware\COMX\PNS V3.5.X\comxpns.nxf

For comX51:

Firmware\COMX\PNS V3.5.X\ cx51pns.nxf

Examples and API\0. Header\Firmware\PROFINET IO

Device V3.4.X

Examples and API\0. Header\Firmware\PROFINET IO

Device V3.5.X

EDS\PROFINET\V3.4.X\GSDML-V2.3-HILSCHER-COMX

50XX-REFO PNS-20130225.xml

EDS\PROFINET\V3.5.X\GSDML-V2.3-HILSCHER-

COMX 50XX-REFO PNS-20130301.xml

EDS\PROFINET\V3.4.X\GSDML-V2.3-HILSCHER-COMX

100XX-RE PNS-20130225.xml

EDS\PROFINET\V3.5.X\GSDML-V2.3-HILSCHER-

COMX 100XX-RE PNS-20130301.xml

- EDS\PROFINET\V3.5.X\ GSDML-V2.3-HILSCHER-

COMX 51XX-RE PNS-20131010.xml



Introduction 18/212

Protocol API

Documentation\7. Programming Manuals\EN\3. Protocol

API\PROFINET IO Device V3.4\PROFINET IO Device

Protocol API 14 EN.pdf

TCP IP - Packet Interface API 13 EN.pdf

Documentation\7. Programming Manuals\EN\3.

Protocol API\PROFINET IO Device V3.5\PROFINET IO

Device V3.5 Protocol API 07 EN.pdf

PROFINET IO Device - Migration from Version 3.4 to

3.5 MG 05 EN.pdf

Table 8: PROFINET IO-Device Firmware Version 3.4 and 3.5, Header, GSDML and Protocol

API Manual



Introduction 19/212

The EtherCAT Slave firmware was revised and completed and is available in version 4.2 since the third quarter 2013.

Use the EtherCAT Slave firmware in version 4.2 for a new installation, when you create or develop your application program for the first time.

If you want to change in an existing system from the EtherCAT Slave firmware version 2.5 to the version 4.2, note the following guidelines:

1. Customize your application program according to the Migration Guide

EtherCAT Slave, Migration from V2.5 to V4.2

.

If you want to change to V4.2, please check in the Migration Guide

EtherCAT Slave, Migration from V2.5 to V4.2 which changes are necessary in the application program in order to use version 4.2.

Firmware

Header

XML

2. Adjust the configuration of your EtherCAT Master device. Use the new

XML file in the configuration software of the EtherCAT Master for this:

Hilscher COMX 100XX RE ECS V4.2.X.xml.

3. Update the EtherCAT Slave firmware in your device to version 4.2.

Note also:

• SYCON.net V1.360.x.x can configure the EtherCAT Slave firmware V2.5 as well as V4.2.10.0 and higher.

• netX Configuration Tool V1.0510.x.x can configure the EtherCAT Slave firmware V2.5 as well as V4.2.

• The development of the EtherCAT Slave firmware V2.5 will not be continued, but this firmware version will be delivered furthermore.

On the Communication Solutions DVD, software and manuals relating to both firmware versions V2.5 and V4.2 are available:

EtherCAT-Slave V2.5


EtherCAT-Slave V4.2


Firmware\COMX\comxecs.nxf Firmware\COMX\ECS V4.X\comxecs.nxf

For comX51:

Firmware\COMX\ECS V4.X\M060F000.nxf

Examples and API\0. Header\Firmware\EtherCAT

Slave V2.5.X

EDS\EtherCAT\Slave\V2.X\Hilscher COMX 100XX

RE ECS V2.2.X.xml

Protocol API

Documentation\7. Programming Manuals\EN\3.

Protocol API\EtherCAT Slave V2\EtherCAT Slave

Protocol API 21 EN.pdf

Examples and API\0. Header\Firmware\EtherCAT Slave

V4.2.X

EDS\EtherCAT\Slave\V4.X\Hilscher COMX 100XX RE ECS

V4.2.X.xml

For comX51:

EDS\EtherCAT\Slave\V4.X\Hilscher COMX 51XX RE ECS

V4.2.X.xml

Documentation\7. Programming Manuals\EN\3. Protocol

API\EtherCAT Slave V4\EtherCAT Slave V4 Protocol API

03 EN.pdf

EtherCAT Slave - Migration from Version 2.5 to 4.2 MG 02

EN.pdf

Object Dictionary V3 03 API EN.pdf

Table 9: EtherCAT-Slave Firmware Version 2.5 and 4.2, Header, XML and Protocol API

Manual



Introduction

1.3 Ensuring Access Security

20/212

The firmware of the protocols

• EtherNet/IP Scanner

• EtherNet/IP Adapter

• Open Modbus/TCP

• PROFINET IO Device

• sercos Slave include an integrated web server. The access to the device by the integrated web server via Internet and Intranet brings with it the danger of misuse. You should therefore always protect the access to the device with passwords. Beyond this also restrict access to your network with suitable security mechanisms.

Important: In any case change the default password, otherwise you allow everyone the right to execute functions without authorization.

To protect the device from unauthorized access, you can restrict access to authorized users. How you set up an own user authentication is described in manual "Application Note, Functions of the Integrated WebServer" in chapter User Authentication. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 21/212

1.4.1 Copyright

© Hilscher, 2010-2015, Hilscher Gesellschaft für Systemautomation mbH

All rights reserved.

The images, photographs and texts in the accompanying material (user manual, accompanying texts, documentation, etc.) are protected by

German and international copyright law as well as international trade and protection provisions. You are not authorized to duplicate these in whole or in part using technical or mechanical methods (printing, photocopying or other methods), to manipulate or transfer using electronic systems without prior written consent. You are not permitted to make changes to copyright notices, markings, trademarks or ownership declarations. The included diagrams do not take the patent situation into account. The company names and product descriptions included in this document may be trademarks or brands of the respective owners and may be trademarked or patented. Any form of further use requires the explicit consent of the respective rights owner.

The user manual, accompanying texts and the documentation were created for the use of the products by qualified experts, however, errors cannot be ruled out. For this reason, no guarantee can be made and neither juristic responsibility for erroneous information nor any liability can be assumed.

Descriptions, accompanying texts and documentation included in the user manual do not present a guarantee nor any information about proper use as stipulated in the contract or a warranted feature. It cannot be ruled out that the user manual, the accompanying texts and the documentation do not correspond exactly to the described features, standards or other data of the delivered product. No warranty or guarantee regarding the correctness or accuracy of the information is assumed.

We reserve the right to change our products and their specification as well as related user manuals, accompanying texts and documentation at all times and without advance notice, without obligation to report the change.

Changes will be included in future manuals and do not constitute any obligations. There is no entitlement to revisions of delivered documents.

The manual delivered with the product applies.

Hilscher Gesellschaft für Systemautomation mbH is not liable under any circumstances for direct, indirect, incidental or follow-on damage or loss of earnings resulting from the use of the information contained in this publication. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 22/212

1.4.3 Exclusion of Liability

The software was produced and tested with utmost care by Hilscher

Gesellschaft für Systemautomation mbH and is made available as is. No warranty can be assumed for the performance and flawlessness of the software for all usage conditions and cases and for the results produced when utilized by the user. Liability for any damages that may result from the use of the hardware or software or related documents, is limited to cases of intent or grossly negligent violation of significant contractual obligations.

Indemnity claims for the violation of significant contractual obligations are limited to damages that are foreseeable and typical for this type of contract.

It is strictly prohibited to use the software in the following areas:

# for military purposes or in weapon systems;

# for the design, construction, maintenance or operation of nuclear facilities;

# in air traffic control systems, air traffic or air traffic communication systems;

# in life support systems;

# in systems in which failures in the software could lead to personal injury or injuries leading to death.

We inform you that the software was not developed for use in dangerous environments requiring fail-proof control mechanisms. Use of the software in such an environment occurs at your own risk. No liability is assumed for damages or losses due to unauthorized use.

1.4.4 Warranty

Although the hardware and software was developed with utmost care and tested intensively, Hilscher Gesellschaft für Systemautomation mbH does not guarantee its suitability for any purpose not confirmed in writing. It cannot be guaranteed that the hardware and software will meet your requirements, that the use of the software operates without interruption and that the software is free of errors. No guarantee is made regarding infringements, violations of patents, rights of ownership or the freedom from interference by third parties. No additional guarantees or assurances are made regarding marketability, freedom of defect of title, integration or usability for certain purposes unless they are required in accordance with the law and cannot be limited. Warranty claims are limited to the right to claim rectification. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 23/212

The delivered product (including the technical data) is subject to export or import laws as well as the associated regulations of different counters, in particular those of Germany and the USA. The software may not be exported to countries where this is prohibited by the United States Export

Administration Act and its additional provisions. You are obligated to comply with the regulations at your personal responsibility. We wish to inform you that you may require permission from state authorities to export, re-export or import the product.

Windows

®

XP, Windows

®

Vista, Windows trademarks of Microsoft Corporation.

®

7 und Windows

®

8 are registered

Acrobat

®

is a registered trademark of Adobe Systems, Inc. In the USA and other states.

CANopen

®

is a registered trademark of CAN in AUTOMATION -

International Users and Manufacturers Group e.V. (CiA), Nuremberg.

CC-Link

®

is a registered trademark of Mitsubishi Electric Corporation,

Tokyo, Japan.

DeviceNet

® and EtherNet/IP

Vendor Association, Inc).

®

are trademarks of ODVA (Open DeviceNet

EtherCAT

®

is a registered trademark and a patented technology of

Beckhoff Automation GmbH, Verl, Germany

, formerly Elektro Beckhoff

GmbH.

Modbus

®

is a registered trademark of Schneider Electric.

Powerlink

®

is a registered trademark of B&R, Bernecker + Rainer Industrie-

Elektronik Ges.m.b.H, Eggelsberg, Austria

PROFIBUS

®

und PROFINET

®

are registered trademarks of PROFIBUS

International, Karlsruhe.

SERCOS interface

® is a registered trademark of SERCOS International e.

V., Suessen, Germany.

All other mentioned trademarks are property of their respective legal owners. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Introduction 24/212

EtherCAT

®

is registered trademark and patented technology, licensed by

Beckhoff Automation GmbH, Germany.

To get details and restrictions regarding using the EtherCAT technology refer to the following documents:

$ “EtherCAT Marking rules”

$ “EtherCAT Conformance Test Policy”

$ “EtherCAT Vendor ID Policy”

These documents are available at the ETG homepage www.ethercat.org

or directly over [email protected]

.

1.5 Licenses

If a comX Communication Module is used as a Slave, neither for the firmware nor for the configuration software SYCON.net a license is required.

Licenses are required, if the comX Communication Module is used with a firmware with master functionality*.

* The master license includes the comX Communication Module operating as master and the license for the configuration software SYCON.net for the respective comX. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Safety

2 Safety

25/212

The user manual, the accompanying texts and the documentation are written for the use of the products by educated personnel. When using the products, all Safety Instructions, Property Damage Messages and all valid legal regulations have to be obeyed. Technical knowledge is presumed.

The user has to assure that all legal regulations are obeyed.

2.2.1 Intended Use of comX Communication Modules

The comX Communication Modules described in this user manual provide an interface from the device into which the module is integrated (“Target system”) to one of the networks mentioned below. Depending from the chosen model and the loaded firmware, the Real-Time Ethernet or Fieldbus systems listed in the following table can be realized using the respective comX Communication Modules.

• EtherCAT Master with COMX 100CA-RE/COMX 100CN-RE

•

COMX 51CA-RE/COMX 51CN-RE

• EtherNet/IP Scanner (Master) with COMX 100CA-RE/COMX 100CN-RE

• EtherNet/IP Adapter (Slave) with COMX 100CA-RE/COMX 100CN-RE/


• Open Modbus/TCP (Server) with COMX 100CA-RE/COMX 100CN-RE/


• Powerlink Controlled Node/Slave with COMX 100CA-RE/COMX 100CN-

RE

• PROFINET IO-RT-Controller (Master) with COMX 100CA-RE/COMX

100CN-RE

• PROFINET IO-RT-IRT-Device (Slave) with COMX 100CA-RE/COMX

100CN-RE/COMX 50CA-REFO/ COMX 51CA-RE/COMX 51CN-RE

• Sercos-Master with COMX 100CA-RE/COMX 100CN-RE


• VARAN Client (Slave) with COMX 100CA-RE/COMX 100CN-RE

• CANopen Master with COMX 100CA-CO/COMX 100CN-CO

• CANopen Slave with COMX 100CA-CO/COMX 100CN- CO/

COMX 10CA-CO/COMX 10CN- CO

• CC-Link Slave with COMX 10CA-CCS/COMX 10CN-CCS

• DeviceNet Master with COMX 100CA-DN/COMX 100CN-DN

• DeviceNet Slave with COMX 100CA-DN/COMX 100 CN- DN/

COMX 10CA-DN/COMX 10 CN- DN

• PROFIBUS DP Master with COMX 100CA-DP/COMX 100CN-DP comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Safety 26/212

• PROFIBUS DP Slave with COMX 100CA-DP/COMX 100CN-DP/

COMX 10CA-DP/COMX 10CN-DP

• PROFIBUS MPI with COMX 100CA-DP/COMX 100CN-DP

The comX Communication Module may only be operated as part of a communication system as described in this document and in the comX

Design Guide. It has been exclusively designed for creating connections to such networks. Typically, the comX communication module is integrated within a device.

The comX Communication Module must only be installed, configured and removed by qualified personnel. Job-specific technical skills for people professionally working with electricity must be present concerning the following topics:

• Safety and health at work

• Mounting and connecting of electrical equipment

• Measurement and Analysis of electrical functions and systems

• Evaluation of the safety of electrical systems and equipment

• Installing and Configuring IT systems

2.4 Commitment to read and understand the Manual

•

Important!

$ To avoid personal injury and to avoid property damage to your system or to your communication module, you must read and understand all instructions in the booklet and all accompanying texts to your communication module, before installing and operating your communication module.

$

First read the safety chapter. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Safety 27/212

To ensure your own personal safety and to avoid personal injury, you necessarily must read, understand and follow the following and all other safety instructions in this manual, before you install and operate your communication module.

The danger of a lethal electrical shock caused by parts with more than 50V may occur, if you open the device to install the comX communication module.

• Hazardous Voltage may be present inside the device, into which the comX communication module is integrated.

• Strictly obey to all safety rules provided by the device’s manufacturer in the documentation!

• First disconnect the power plug of the device.

• Make sure, that the power supply is off at the device.

• Open the housing and install or remove the comX Communication

Module only after disconnecting power.

An electrical shock is the result of a current flowing through the human body. The resulting effect depends on the intensity and duration of the current and on its path through the body. Currents in the range of approximately ½ mA can cause effects in persons with good health, and indirectly cause injuries resulting from startle responses. Higher currents can cause more direct effects, such as burns, muscle spasms, or ventricular fibrillation.

In dry conditions permanent voltages up to approximately 42.4 V peak or

60 V DC are not considered as dangerous, if the contact area is equivalent to a human hand.

Reference Safety [S2]

2.6 Safety Instructions to avoid Property Damage

To avoid property damage respectively device destruction to the comX communication module and to the system into which the comX is integrated, you necessarily must read, understand and follow the following and all other property damage messages in this manual, before you install and operate your communication module.

2.6.1 Device Destruction by exceeding allowed Supply Voltage

For all comX Communication Modules described in this manual adhere to the instruction hereafter: comX

Communication Module must not be operated with a supply voltage of 5V! Exclusively use the mandatory supply voltage of 3,3 V ±

5 % as specified. Operation of the comX

Communication Module at a voltage above the allowed range (i.e. more than 3,3 V + 5 %) can cause either severe damage to the comX module or even device destruction. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Safety 28/212

• The comX Communication Module must only be operated with the specified supply voltage. Take care of not exceeding the limits of the allowed voltage range for the supply voltage.

A supply voltage below the allowed range may cause malfunction of the comX module. The allowed range is given by the tolerances specified in the manual.

The specifications for the mandatory supply voltage for the comX modules described in this manual can be found in chapter Technical Data of COMX

Modules

beginning on page 130 and in Table 13: Supply Voltage and

Signaling Voltage for comX Communication Modules beginning on page

35. For each type of device the necessary and allowed supply voltage, including the tolerance.

2.6.2 Device Destruction by exceeding allowed Signal Voltage

For all comX communication modules described in this manual, take care of the following notice:

• All I/O signal pins at the comX communication module tolerate only the specified signal voltage.

• Operation of the comX communication module at signal voltages significantly exceeding the specified maximum signal voltage of 3.3 V ± 5

% may cause severe damage or device destruction.

The specifications for the maximum signal voltage of the comX modules described in this manual can be found in Table 12: Supply Voltage and

Signaling Voltage for comX Communication Modules

beginning on page

35. The signal voltage is equal to the supply voltage.

Adhere to the necessary safety precautions for components that are vulnerable with electrostatic discharge.

This equipment is sensitive to electrostatic discharge, which cause internal damage and affect normal operation. Follow guidelines when you handle this equipment:

• Touch a grounded object to discharge potential static.

• Wear an approved grounding wrist strap.

• Do not touch connectors or pins on the cifX Communication Interface.

• Do not touch circuit components inside the equipment.

• If available, use a static-safe workstation.

When not in use, store the equipment in appropriate static-safe packaging.

Reference Safety [2] comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Safety

2.7 Labeling of Safety Messages

Safety

Symbol

29/212

USA

• The Section Safety Messages at the beginning of a chapter are pinpointed particularly. They are highlighted with a specific safety symbol and a signal word according to the degree of endangerment.

Inside the safety message the danger is exactly named.

• The Integrated Safety Messages within an instruction description are highlighted with a signal word according to the degree of endangerment and possibly by a principle symbol. Inside the safety message the danger is exactly named.

Sort of Warning or Principle

Warning of Personal Injury and Property Damage Message

USA: Warning of Personal Injury

As in the scope of the ANSI Z535 Standard (for USA) instructions to a property damage message may not contain a warning triangle, this property damage messages are listed separately for the USA.

Warning of Lethal Electrical Shock

Warning of Damages by Electrostatic Discharge

Principle: Disconnect the Power Plug

Signal

Word

Note

Meaning

Table 10: Safety Symbols and Sort of Warning or Principle

Meaning (USA)

Indicates a direct hazard with high risk, which will have as consequence death or grievous bodily harm if it isn't avoided.

Indicates a possible hazard with medium risk, which will have as consequence death or

(grievous) bodily harm if it isn't avoided.

Indicates a minor hazard with medium risk, which could have as consequence simple battery if it isn't avoided.

Indicates a Property Damage Message.

Indicates an important note in the manual.

Table 11: Signal Words

Indicates a Hazardous Situation Which if not

Avoided, will Result in Death or Serious Injury.


Avoided, could Result in Death or Serious

Injury.


Avoided, may Result in Minor or Moderate

Injury.

Indicates a Property Damage Message.

Indicates an Important Note in the Manual.

In this document all Safety Instructions and Safety Messages are designed according both to the international used safety conventions as well as to the ANSI Z535 standard, refer to reference safety [S1].

[S1] ANSI Z535.6-2006 American National Standard for Product Safety Information in

Product Manuals, Instructions, and Other Collateral Materials

[S2] IEC 60950-1, Information technology equipment - Safety - Part 1: General requirements, (IEC 60950-1:2005, modified); German Edition EN 60950-1:2006

[S3] EN 61340-5-1 and EN 61340-5-2 as well as IEC 61340-5-1 and IEC 61340-5-2 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Descriptions and Requirements 30/212

3.1 Description

The products of the comX family are communication modules for Real-Time

Ethernet and Fieldbus for the integration into host systems. comX communication modules provide I/O data to the host in a dual-port memory.

Each Real-Time Ethernet protocol has special requirements to the communication technology, such as switch or hub functionality, for instance. The comX communication module covers these requirements for the respective protocols.


on page 12 explains for any comX communication module which protocols are applicable.

Highlights

• 2-Port Ethernet with switch and hub for line topology

• System-/Status-/Link- and Activity-LEDs

• Host Interface with 8- or 16-Bit data width

• USB- and UART diagnostic interface

• Direct access onto the process data within the Dual-Port Memory

• SYCON.net (based on FDT/DTM standard) available as configurator

• comX 10: Address and baudrate switches

• comX 50 CA-REFO:

Fiber optic interface according to AIDA

• If used as embedded system, SYCON.net can be used if at least one of the interfaces USB and UART is connected to outside of the system.

• For all other cases, a PC adapter card is available for firmware update, configuration and diagnosis, see chapter 8”Evaluation Board COMXEB” on page 85 and section „Updating the Firmware“ on page 140. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



In the following, the block diagram for the Real-Time Ethernet module

COMX 100CA-RE is depicted:

Figure 1: Block Diagram of Real-Time Ethernet Module

Here the corresponding block diagram for the comX Fieldbus Modules:

Figure 2: Block Diagram of a Fieldbus Module




For a sensible application of the communication modules of the comX family, the following conditions must be fulfilled:

At the target system:

1. Mechanical connection: 50 pin SMT connector (male, grid distance 1.27 mm, for instance type SAMTEC TFM - 125 - 02 - S - D – A or TFC - 125

- 02 - F - D – A, see www.samtec.com)

2. Electrical connection: Pin assignment as described in section

Connector X1 in the comX Design Guide.

3. Communication via Dual-Port Memory. Access using the cifX Device

Driver or based on a toolkit.

4. Power supply: Via pins in connector X1, see comX Design Guide. The applied supply voltage must always be in the range between 3,3 V ± 5

%.

At the communication system connected to the comX module (i.e. either

Real-Time Ethernet or. Fieldbus):

5. A Master of the communication system fitting to the respective type of comX module and the loaded firmware, if a Slave firmware has been loaded.

6. A Slave of the communication system fitting to the respective type of comX module and the loaded firmware, if a Master firmware has been loaded.

Concerning topics 2 and 4 also see the pin assignments provided by the comX Design Guide in chapter 3. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



3.2 Prerequisites for the Operation of the comX

Communication Modules

3.2.1 Prerequisites for the Operation as Embedded System

The following prerequisites must be fulfilled for the operation of the comX communication modules as Embedded System .

1. The comX communication modules must be mounted correctly in the 50 pin SMT connector of the host system (when using comX modules of the

CN series: this is additionally valid for the 30 pin SMT connector of the host system). The connector must be connected according to the specifications given in the comX Design Guide.

2. A suitable supply voltage in the voltage range 3.3 V ± 5% must be connected.

3. The module must be loaded with the correct firmware for the communication system/ protocol to be applied on the module.

4. Please find out the correct firmware for the applied system to be installed on your communication module using the reference table (Table 3:

Reference to Firmware

on page 12 within section 1.1.3 "Reference to

Hardware, Software and Firmware

“).

5. The comX communication module must have been configured correctly,, for instance with the system configurator SYCON.net which is delivered with the comX modules (for more information, see SYCON.net documentation).

6. For the communication with the comX module, either the cifX Device

Driver or the toolkit must have been installed correctly (at least V1.0.5.x).

7. In order to avoid thermal damage, the allowed temperature range needs to be obeyed. See specifications in section “Technical Data of COMX

Modules”

on page 158. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



3.2.2 Prerequisites for the Operation with Evaluation Board COMXEB

The following prerequisites must be fulfilled for the operation of the comX communication modules with evaluation board COMXEB together with a connected PC.

1. On the PC Microsoft Windows

®

must have been installed (Windows® XP

Service Pack 3, Windows® Vista (32 bit), Windows® 7 Service Pack 1 (32 bit), Windows® 7 Service Pack 1 (64 bit) or Windows® 8 (32 oder 64 bit)

).

2. The COMXEB must be provided with its power supply (Voltage +24V). This can be done using the power adaptor which is included in the scope of delivery via socket X932 or usingt another power supply connected to the

CombiCon connector X930 .

3. One of the diagnostic interfaces (USB: X611 / seriell: X601 ) of the evaluation board COMXEB musr be connected to the PC, see section

8.3.5”Diagnostic Interfaces” on page 107.

4. The comX communication module must be mounted correctly in the 50 pin

SMT connector of the evaluation board COMXEB X300 , X400 or X501

(when using comX modules of the CN series: this is additionally valid for the 30 pin SMT connector of the host system X401 / X500 ).

5. The module must be loaded with the correct firmware for the communication system/ protocol to be applied on the module (this happens on the COMXEB).

Please find out the correct firmware for the applied system to be installed on your communication module using the reference table (Table 3:

Reference to Firmware

on page 12 within section 1.1.3 "Reference to

Hardware, Software and Firmware

“).

6. The comX communication module must have been configured correctly, for instance with the system configurator SYCON.net which is delivered with the comX modules (this happens on the COMXEB ,for more information, see SYCON.net documentation).

3.2.3 Remarks on Storage Stability and Contact Reliability of Hostside Connector

For the host-side connectors used in the comX communication modules

(Samtec Types SFC-115-T2-L-D-A-K-TR and SFC-125-T2-L-D-A-K-TR), the following applies concerning storage stability and long-term immunity against contact failure:

1. Hilscher only uses highly reliable connectors in the comX modules. The supplier of the connector warrants a minimum expected storage time of

5 years without any loss of spring tension when the connectors have been mounted. According to its general terms and conditions, Hilscher assures this warranted storage time to you.

2. In order to preserve the spring tension and to improve the immunity against contact failure of the host-side connectors, the following storage conditions are recommended: o

Storage in dry package such as ESD bags which additionally can be heat-sealed. o

Alternatively: Controlled storage at a temperature of max. 25°C and

50% relative humidity. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



3.3 Supply Voltage and Signaling Voltage

The following table provides the required and permissible supply voltage for each of the devices as well as the required or tolerated signaling voltage for the I/O signal pins:

comX Supply Voltage Signaling Voltage

All types +3.3 V DC ±5 % +3.3 V DC ±5 %

Table 12: Supply Voltage and Signaling Voltage for comX Communication Modules

The typical current depends on the type of comX module, for detailed values on current consumption see section “Technical Data of COMX

Modules”

.

3.4 Prerequisites for the Software Installation

3.4.1 Prerequisites for the System Configurator SYCON.net

• PC with 1 GHz processor or higher

• Windows

®

XP SP3, Windows

®

SP1, Windows

Vista (32 bit) SP2, Windows

®

7 (64 bit) SP1, Windows

®

®

7 (32 bit)

8 (32 bit) or Windows

®

8 (64 bit)

• Administrator privilege required for installation

• Internet Explorer 5.5 or higher

• Free disk space: min. 400 MByte

• DVD ROM drive

• RAM: min. 512 MByte, recommended 1024 MByte

• Graphic resolution: min. 1024 x 768 pixel

• Keyboard and Mouse

• USB, serial or Ethernet interface

Note: If the project file is saved and opened again or if it is used on another PC, the system requirements must match. Particularly the DTM must be installed on the used PC.

Restriction

Touch screen is not supported. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Descriptions and Requirements

3.5 Prerequisites for Certification

36/212

If you intend to develop a final product to be certified with the official

PROFINET-IO certification for IRT, the host base board of your product must provide a SYNC0 signal (2pin connector including GND), for instance in order to allow to connect an oscilloscope there.

For this purpose, the communication modules COMX provide the SYNC0 signal line Request to Send, Serial line & SYNC0 which is located at pin

#15 of system connector. The SYNC0 signal has LVTTL level (3.3 V). A maximum load of 6 mA must not be exceeded.

You should keep the cable length for the sync signals below 50 mm and take into account EMC aspects. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Getting Started comX Communication Modules

4 Getting Started comX Communication Modules

37/212

4.1 Hardware Installation as Embedded System (Master and

Slave)

#

1

2

Step

Preparation

Take safety precautions

The following table describes the steps on how to install a comX

Communication Module (Master and Slave) as it is typical for many cases.

Description For detailed information see section

Page

Take all necessary safety precautions for the installation of the comX:

Carefully read the documentation of the device into which the comX is to be mounted.

Especially, obey precisely to the safety rules demanded by the device’s manufacturer

In any case, take care of the following:

Electrical Shock Hazard

27

Lethal Electrical Shock caused by parts with more than 50V!

Disconnect the power plug of the connecting device.

Make sure, that the power supply is off at the connecting device.

Installation Hardware

Open housing

Hardware Installation,

Deinstallation and

Replacement

Installing the comX

Communication Module in its Target Environment

Install comX

Close housing

Plug the connecting cable to the Master or

Slave

Now open the housing of the host system if present.

Take care of the host system being not connected to its supply voltage.

Plug in and mount the comX within the host system.

If necessary, connect diagnostic connection cable from comX to Diagnosis PC (either via

USB- or serial connection).

Close the housing of the host system if any is present.

Plug in the connecting cable from the comX to the Master or Slave.

Important!

When using Ethernet TCP/UDP-IP,

EtherNet/IP or Modbus TCP exclusively use switches or 10/100

MBit/s dual speed hubs and ensure, that the network is operated at a speed of 100 MBit/s or in full duplex mode.

Note!

Use the RJ45 Connector only for

LAN connections but not for telecommunication connections!

Failure in 10 MBit/s Half

Duplex Mode and

Workaround

Ethernet Interface of

COMX

100CA-RE

207

55




#

38/212

Step

Plug target system to supply voltage

Description

When using PROFINET IO-Controller take care of the following:

Important hint for cabling!

Only connect ports with different cross-over settings with each other.

Otherwise no connection will be established between the devices. If the port settings of the comX

PROFINET IO-Controller have not been set to AUTO, then port 0 will be set to uncrossed and port 1 to crossed.

Plug the target system to its supply voltage and switch it on.

If a PC has been connected for diagnostic purposes, do the same for the PC.

For detailed information see section

See according User

Manual at Documentation

Overview comX

Page

16

Table 13: Steps for the Hardware Installation of a comX Communication Module (Master und Slave)



Getting Started comX Communication Modules 39/212

4.2 Configuration of the comX Communication Module

(Slave)

#

1

2

(a)

2.1

(a)

2.2

(a)

2

(b)

2.1

(b)

2.2

(b)

2.3

(b)

2.4

(b)

2.5

(b)

Step

Driver Installation

The following table describes the steps on how to configure a comX

Communication Module (Slave) as it is typical for many cases. The comX

Communication Module (Slave) can be configured using the cifX Test

Application. In many cases, the corresponding DTM in the configuration software SYCON.net can be used alternatively.


Page

Install the required driver(s) (cifX Device

Driver, USB Driver…). For a serial connection no special driver is required.

See separate manual

“Software Installation and

Documentation

Overview ”

Download Firmware and Configuration

(a) with the cifX Test Application

The cifX Test Application is delivered and installed with the cifX Device Driver .

Updating the Firmware using an Evaluation

Board COMXEB and a

PC

142

cifX Test Application

Installation

Configuration steps comX (Slave)

OR

Download

Firmware and

Configuration,

Diagnosis, I/O Data

Installing SYCON.net

If not already happened in Step 1, install the

cifX Test Application.

In the cifX Test Application

- select and download the firmware

- adjust the device parameters for comX

Communication Module (Slave)

(b) using SYCON.net

Possibly use the corresponding DTM in the configuration software SYCON.net.

Run the SYCON.net-Setup and follow to the instructions of the installation wizard.



PC

142

Firmware Download



Documentation

Overview ”

Update the

Firmware with

SYCON.net

Also see corresponding user manual under

Documentation Overview comX

Configuration comX (Slave)

Download

Configuration

Diagnosis

- Start configuration software SYCON.net,

- Create new project /Open existing project,

- Insert Slave into configuration,

- Select driver and assign device.

- Select and download the firmware.

- Configure the comX Communication Module

(Slave)

- Download the configuration to the comX

(Slave) *.

(*EtherCAT-Slave,

EtherNet/IP-Adapter (Slave),

Open-Modbus/TCP (Slave),

Powerlink-Controlled-Node/Slave,

PROFINET IO-Device (Slave),

Sercos-Slave,

PROFIBUS DP-Slave,

CANopen-Slave,

DeviceNet-Slave,)

- Right click on device symbol.

- Select context menu entry Diagnosis,

- then select Diagnosis > General or

Firmware Diagnosis,

- or select Diagnosis > Extended Diagnosis.

Device Names in

SYCON.net

147

16

44




2.6

(b)

I/O Monitor - Right click on device symbol.


- then Tools > IO Monitor.

-Check the input or output data.

Table 14: Configuration Steps for the comX Communication Module (Slave)

40/212

Important: SYCON.net cannot be used for the configuration of the CC-

Link Slave communication module COMX 50CA-CC. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



4.3 Configuration of the comX Communication Module

(Master)

#

1

2

Step

Driver Installation

The following table describes the steps on how to configure a comX

Communication Module (Master) as it is typical for many cases. The comX

Communication Module (Master) can be configured using the configuration software SYCON.net.


Page

Install the required driver(s) (cifX Device

Driver, USB Driver…). For a serial connection no special driver is required.



Documentation

Overview ”

Download

Firmware and

Configuration,

Diagnosis, I/O Data

using SYCON.net

Possibly use the corresponding DTM in the configuration software SYCON.net..

(Alternatively,

for this purpose

also the usage of the cifX Test Application is possible.)

2.2 Firmware Download

2.3 Configuration comX

(Master)

2.4 Download

Configuration instructions of the installation wizard.


- Create new project /Open existing project,

- Insert Master into configuration,

- Select driver and assign device.


- Configure the comX (Master).



Documentation

Overview ”

Update the

Firmware with

SYCON.net

Also see corresponding user manual under

Documentation Overview comX

Device Names in

SYCON.net

147

16

44

2.5 Diagnostic


(Master) *

(*EtherCAT-Master,

EtherNet/IP-Scanner (Master),

PROFINET IO-Controller (Master) ,

Sercos- Master,

PROFIBUS DP-Master,

CANopen-Master,

DeviceNet-Master)



- then select Diagnosis > General,

Firmware

or Master Diagnosis,

- or select Diagnosis > Extended Diagnosis.



- then Tools > IO Monitor.

-Check the input or output data.

Table 15: Configuration Steps for the comX Communication Module (Master)




4.4 Notes for the Configuration of the Master Device

To configure the Master, a device description file is required. Please take into account the following notes during the configuration of the Master

Device:

Real-Time

Ethernet-System

Notes

EtherCAT Slave

To configure the Master, an XML file (device description file) is required.

The settings in the used Master must comply with the settings in the

Slave to establish communication. Important parameters are: Vendor ID,

Product Code, Serial Number, Revision Number, Output/Input Data Bytes

If the XML file Hilscher COMX RE ECS V2.2.X.xml is use/updated, the firmware with the version 2.2.x must be use/updated.

EtherNet/IP-

Adapter

The loadable firmware supports for the number of cyclic input data and for cyclic output data in total up to 400 bytes. If more than 200 bytes for input data or for output data should be exchanged via EtherCAT, then a customer specific XML file is necessary. Additionally the following formula applies: (number of input bytes + 3)/4 + (number of output bytes + 3)/4 must be less or equal to 100.

To configure the Scanner/Master, an EDS file (device description file) is required. The settings in the used Scanner/Master must comply with the settings in the Adapter/Slave to establish communication. Important parameters are: Input, Output Data Bytes, Vendor ID, Product Type,

Product Code, Major Rev, Minor Rev, IP Address and Netmask.

Powerlink-

Controlled-

Node/Slave

PROFINET IO-

Device sercos Slave

To configure the Managing Node/Master, an XDD file (device description file) is required. The settings in the used Managing Node/Master must comply with the settings in the Controlled Node/Slave, to establish communication. Important parameters are: Vendor ID, Product Code,

Serial Number, Revision Number, Node ID, Output and Input length.

To configure the Controller, a GSDML file (device description file) is required. The settings in the used Controller must comply with the settings in the Device to establish communication. Important parameters are: Station Name, Vendor ID, Device ID, Input and Output Data Bytes.

Under Name of Station, the name must be typed which was also used in the configuration file of the master of this device. If no name chosen freely is used in the configuration file, then the name from the GSDML file is used.

The sercos Master uses the sercos address to communicate with the slave. Some Masters verify Device ID, Vendor Code, Input Data Size and

Output Data Size and do further communication to the slave only if all these values match. Therefore the master reads these parameters from the slave and compares them with the configuration stored in the master.

The parameters Device ID, Vendor Code, Input Data Size and Output

Data Size are part of the SDDML device description file. If for the configuration of the sercos Master SDDML files are used and a default value of one of these parameters was changed, then a SDDML file must be created in the configuration software via Export SDDML and then used in the configuration of the SERCOS Master. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Fieldbus-System Notes

PROFIBUS DP

Slave

CANopen Slave

To configure the Master, a GSD file (device description file) is required.


Slave to establish communication. Important parameters are: Station

Address, Ident Number, Baudrate and Config Data (the configuration data for the output and input length).

To configure the Master, an EDS file (device description file) is required.


Slave to establish communication. Important parameters are: Node

Address and Baudrate.

DeviceNet Slave

To configure the Master, an EDS file (device description file) is required.


Slave to establish communication. Important parameters are: MAC ID,

Baudrate, Produced Size, Consumed Size, Vendor ID, Product Type,

Product Code, Major Rev, Minor Rev.

CC-Link Slave

To configure the Master, a CSP file (device description file) is required.


Slave to establish communication. Important parameters are: Slave

Station Address, Baudrate, Station Type and Vendor Code.

Table 16: Notes for the Configuration of the Master Device

Further information to the device description files can be found under section Device Description Files on page 14. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



4.5 Device Names in SYCON.net

The following table contains the device names displayed for the single communication protocols in the configuration software SYCON.net.

The table shows the card type of the comX Communication Interface and which protocol can be used. Furthermore, the table shows, for which protocol which device must be selected from the device catalog to configure the comX Communication Module with SYCON.net.

comX (Module

Type)

Protocol DTM Specific

Group

Device Name in

SYCON.net

Real-time Ethernet EtherCAT Master

COMX 100XX-RE/ECS EtherCAT Slave Gateway/Stand-

Alone Slave

EtherNet/IP Scanner

(Master)

EtherNet/IP Adapter

(Slave)

Gateway/Stand-

Alone Slave

Open-Modbus/TCP Gateway/Stand-

Alone Slave

Powerlink-

Controlled-

Node/Slave

PROFINET IO-RT-

Controller

Gateway/Stand-

Alone Slave

COMX 100XX-RE/EIS

COMX 100XX-RE/OMB

COMX 100XX-RE/PLS

COMX 100XX-RE/PNS

Real-time Ethernet

PROFINET IO-RT-

Device

Gateway/Stand-

Alone Slave

Sercos-Master Master

Sercos-Slave

EtherCAT Slave

Gateway/Stand-

Alone Slave

Gateway/Stand-

Alone Slave

EtherNet/IP Adapter

(Slave)

Gateway/Stand-

Alone Slave

Open-Modbus/TCP Gateway/Stand-

Alone Slave

PROFINET IO-RT-

Device

Gateway/Stand-

Alone Slave

CANopen

Sercos-Slave

PROFINET IO-RT-

Device

CANopen Master

Gateway/Stand-

Alone Slave

Gateway/Stand-

Alone Slave

CANopen Slave

Gateway/Stand-

Alone Slave

DeviceNet

DeviceNet Master

DeviceNet Slave

Gateway/Stand-

Alone Slave

PROFIBUS-DP PROFIBUS DP

Master

PROFIBUS DP

Slave comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Gateway/Stand-

Alone Slave

COMX 100XX-RE/S3S

COMX 51XX-RE/ECS

COMX 51XX-RE/EIS

COMX 51XX-RE/OMB

COMX 51XX-RE/PNS

COMX 51XX-RE/S3S

COMX 50XX-

REFO/PNS

COMX 100XX-CO/COS

COMX 10XX-COS/COS

COMX 100XX-DN/DNS

COMX 10XX-DNS/DNS

COMX 100XX-DP/DPS

© Hilscher, 2010-2015


CC-Link

CC-Link Slave

Gateway/Stand-

Alone Slave

XX means CA or CN

Table 17: Device Names in SYCON.net by Communication Protocol

45/212

COMX 10XX-DPS/DPS

COMX 10XX-CCS/CCS comX | Communication Modules for Real-Time-Ethernet and Fieldbus



4.6 Exchange of comX Communication modules (Master and

Slave)

4.6.1 Steps for Exchange of Hardware

#

1

2

4

6

7

9

Step

In the following table the steps for the exchange (in the replacement case) of a comX communication module (Master oder Slave) are described, as they are typical for many cases of application.


Page

Hardware Installation Deinstall comX communication module to be replaced.

Take the required safety precautions.

Take safety precautions

Take all necessary safety precautions for the installation of the comX:

Carefully read the documentation of the device into which the comX is to be mounted.

Especially, obey precisely to the safety rules demanded by the device’s manufacturer

In any case, take care of the following:

Remove screws fixing the comX


Disconnect the power plug of the connecting device.

Make sure, that the power supply is off at the connecting device.

Now open the housing of the host system if present.

Take care of the host system being not connected to its supply voltage as long as the case is open.

First remove both screws used for fixing the comX at the front panel of the device.

Then pull the comX communication module to be exchanged carefully out of the connector(s).

Plug-in replacement comX

Now carefully plug the replacement comX communication module into the connector(s).

Take care of good fitting and contact.

Fix replacement comX Fix the replacement comX at the front panel of the device using the 2 screws.

Close the housing of the host system if any is present.

Plug target system to supply voltage

Plug the target system to its supply voltage and switch it on.

Decommissioning

Electrical Shock Hazard

52

27

Decommissioning

52

Table 18: Steps how to replace the comX Communication modules (Master and Slave)




4.6.2 Load Firmware & Configuration into Replacement Module comX

(Slave)

#

1

(a)

1.1

(a)

1

(b)

1.1

(b)

1.2

(b)

Step

Download Firmware and Configuration

Configuration steps comX (Slave)

Note: For comX communication module s without Rotary Switch Slot

Number (Module ID) in terms of a device exchange service (replacement case) you must manually download the same firmware and configuration into the replacement cifX, as into the preceding cifX Communication

Interface.

The following table describes the steps on how to download the firmware and the configuration of a comX communication module (Slave) exchange service (replacement case) as it is typical for many cases. The download can be performed for the Slave using the cifX Test Application or alternatively the configuration software SYCON.net can be used.


Page

(a) With the cifX Test Application

The cifX Test Application is delivered and installed together with the cifX Device Driver.

In the cifX Test Application

- select and download the firmware

- adjust the device parameters for comX communication module (Slave)



PC

See above

142

(b) using SYCON.net

OR

Download

Firmware and

Configuration

Firmware Download

Download

Configuration


- open existing project,

- if so, select driver,

- assign device.



(Slave) *.

(*EtherCAT-Slave,

EtherNet/IP-Adapter (Slave),

Open-Modbus/TCP (Slave),

Powerlink-Controlled-Node/Slave,

PROFINET IO-Device (Slave),

Sercos-Slave,

PROFIBUS DP-Slave,

CANopen-Slave,

DeviceNet-Slave,)

Update the

Firmware with SYCON.net

See corresponding user manual under

Documentation

and

Device Names in

SYCON.net

147

16

44

Table 19: Firmware and Configuration Download Steps comX Communication modules

(Slave) at Module Exchange (Replacement Case)




4.6.3 Load Firmware & Configuration into Replacement Module comX

(Master)

# Step

1

Download

Firmware and

Configuration

1.1 Firmware Download

The following table describes the steps on how to download the firmware and the configuration of a comX Communication Module (Master) exchange service (replacement case) as it is typical for many cases. The download can be performed for the Master using the configuration software

SYCON.net


Page using

SYCON.net


- open existing project,

- if so, select driver,

- assign device.


Update the

Firmware with

SYCON.net

See corresponding user manual under

Documentation

147

16

1.2 Download

Configuration

- Download the configuration to the replacement comX (Master)*

(*EtherCAT-Master, EtherNet/IP-Scanner

(Master), PROFINET IO-Controller (Master) ,

Sercos- Master, PROFIBUS DP-Master,

CANopen-Master, DeviceNet-Master)

Table 20: Steps Firmware and Configuration Download Steps comX Communication modules (Master) at Module Exchange (Replacement Case)




4.7 Updating the Firmware, Driver and Software

Note: As a prerequisite for the software update, the project files, the configuration files and firmware files have to be saved.

At existing hardware installation the firmware, the driver and the configuration software must be updated according to the versions given in section “Reference to Hardware, Software and Firmware” on page 11.

This is illustrated by the following graphic:

For detailed information about firmware update also see chapter Updating

the Firmware



Hardware Installation, Deinstallation and Replacement 50/212

Replacement

5.1 Warning Messages on Personal Injury

Obey to the following safety advices, when installing, deinstalling or replacing the comX Communication Modules described in this manual.


$ HAZARDOUS VOLTAGE may be present inside the device, into which the comX communication module is integrated.

$ Strictly obey to all safety rules provided by the device’s manufacturer in the documentation!

$ Therefore first disconnect the power plug of the device.

$ Make sure, that the power supply is off at the device.

$ Open the housing and install or remove the comX Communication

Module only after disconnecting power.

$ Strictly obey to all safety rules given in the documentation supplied by the manufacturers of this device.!

5.2 Property Damage Messages

Obey to the following property damage messages, when installing, deinstalling or replacing the comX Communication Module.

5.2.1 Device Destruction by exceeding allowed Supply Voltage

Adhere for all comX Communication Modules described in this manual the instruction hereafter:

Device Destruction!

$ Use only the mandatory supply voltage to operate the comX

Communication Module.

$ Operating the comX with a supply voltage above of the specified range leads to device destruction.

USA:


$ Use only the mandatory supply voltage to operate the comX

Communication Module.

$ Operating the comX with a supply voltage above of the specified range comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Hardware Installation, Deinstallation and Replacement leads to device destruction.

51/212

5.2.2 Device Destruction by exceeding allowed Signaling Voltage

Adhere for all comX Communication Modules described in this manual the instruction hereafter:


$ All I/O signal pins at the comX Communication Module tolerate only a specified signaling voltage!

$ Operation the comX with a signaling voltage other than the specified signaling voltage may lead to severe damage to the comX

Communication Module!

USA:


$ All I/O signal pins at the comX Communication Module tolerate only a specified signaling voltage!

$ Operation the comX with a signaling voltage other than the specified signaling voltage may lead to severe damage to the comX

Communication Module!

For detailed information on the supply and signaling voltage of the comX

Communication Modules described in this manual, refer to section “Supply

Voltage and Signaling Voltage”

on page 34.

Adhere to the necessary safety precautions for components that are vulnerable with electrostatic discharge.

Electro-statically sensitive Devices

$

To prevent damage to the device and the comX Communication

Module, make sure, that the comX is grounded via the endplate and the

PC and make sure, that you are discharged when you install/ deinstall the comX Communication Module. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Hardware Installation, Deinstallation and Replacement 52/212

5.3 Installing the comX Communication Module in its Target

Environment

For the installation of the comX communication module into the device into which the comX module is to be integrated (also denominated as “host system” or “target environment”), proceed as follows:


• Strictly obey to all safety rules given in the documentation supplied by the manufacturers of this device!

• Plug off the device into which the comX module is to be integrated!

• Make sure, that this device is separated from the supply voltage and free of current, before you continue.

• Adhere to the necessary safety precautions for components that are vulnerable with electrostatic discharge described in section

5.2.3“Electro-statically sensitive Devices” on page 51

!

Step 1: If necessary, remove the housing of this device. In all cases, strictly adhere to the manuals of this device.

!

Step 2: Definitely avoid touching open contacts or ends of wires.

!

Step 3: Plug in the comX communication module carefully but solidly in to its connector (50 pin SMT connector, male, grid width 1.27 mm, at

COMX-CN modules additionally 30 pin SMT connector, male, grid width

1.27 mm).

!

Step 4: If you had opened the housing of the device in step 1, then close it now. Again strictly adhere to the manuals of this device anyway.

!

Step 5: Connect the device with its supply voltage and switch it on again. Check, whether the device behaves normally.

!

Step 6: If this is the case, connect the device to the corresponding communication partner (Master in case of Slave Module, Slave in case of Master-Module) via Ethernet- or Fieldbus (depending on the type of comX communication module).

5.4 Decommissioning

In order to avoid personal injury, material and environmental damage strictly obey the rules on putting the comX modules out of service and on disposal given in section “Decommissioning, Replacement and Disposal” on page 199. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Installing the Software 53/212

The installation of the software delivered with the device on the

Communication Solutions DVD (Configuration software, drivers, tools) is subject of a separate manual “comX”, which is also contained on that DVD, see there.

There you will find descriptions of the installation of the following software under Windows XP, 7 and 8:

• cifX Device Driver

• SYCON.net

• netX Configuration Tool

• USB-Driver comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Device Photos (Position of Switches, LEDs and Interfaces) 54/212

7 Device Photos (Position of Switches, LEDs and

Interfaces)

7.1 Real-Time Ethernet Communication Module COMX

100CA-RE

Figure 3: Photo of Communication Module COMX 100CA-RE with Cooler

LED Displays of COMX 100CA-RE

SYS LED

COM0 LED

COM1 LED

SMT-Connectors of the COMX 100CA-RE (Connection to Host)

System Interface

Connectors of the COMX 100CA-RE (connected to outside)

Ethernet Interface Channel 0

Ethernet Interface Channel 1 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Device Photos (Position of Switches, LEDs and Interfaces)

7.1.2 Ethernet Interface of COMX 100CA-RE

55/212

Figure 4: Pinning of Ethernet Interface of COMX 100CA-RE

Pin Signal Description

1

2

TX+

TX–

Transmit data positive

Transmit data negative

3 RX+ Receive data positive

4 TERM

5 TERM

6 RX – Receive data negative

7 TERM

8 TERM

* Bob Smith Termination

Table 21: Pinning of Ethernet Connector at Channel 0 and Channel 1

The Ethernet interfaces of the comX communication modules provide the

Auto-Crossover feature.

For a schematic diagram of the Ethernet Interface of COMX 100CA-RE refer to the comX Design Guide. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.2 Real-Time Ethernet Communication Module COMX

100CN-RE

Figure 5: Photo of Communication Module COMX 100CN-RE

Note: Please take care of the following: The figure above shows the

COMX 100CN-RE communication module without the metal blocks required for mounting!

SMT-Connectors of the COMX 100CN-RE (Connection to Host)

System Interface

Ethernet Interface

7.2.2 Ethernet Interface of COMX 100CN-RE

The pin assignment of the Ethernet interface of the COMX 100CN-RE is described in the comX Design Guide within subsection 3.2.4. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.3 Real-Time Ethernet Communication Module COMX 50CA-

REFO with Fiber Optic

The COMX 50CA-REFO communication modules conform with the AIDA specifications.

Figure 6: Photo COMX 50CA-REFO

LED Displays of COMX 100CA-RE

SYS LED

COM0 LED

COM1 LED

SMT-Connectors of the COMX 100CA-RE (Connection to Host)

System Interface

Optical Connectors of the COMX 50CA-REFO (connected to outside)

Ethernet Interface Channel 0 (Fiber Optic)

Ethernet Interface Channel 1 (Fiber Optic) comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.3.2 Optical Ethernet Interface of COMX 50CA-REFO

58/212

The COMX 50CA-REFO has 2 optical Ethernet interfaces with Transceivers of type Avago QFBR-5978. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Real-Time Ethernet Communication Module

COMX51CA-RE

7.4.1 COMX51CA-RE

Figure 7: Photo of Communication Module COMX51CA-RE with Cooler

LED Displays of COMX51CA-RE

SYS LED

COM0 LED

COM1 LED

SMT-Connectors of the COMX51CA-RE (Connection to Host)

System Interface

Connectors of the COMX51CA-RE (connected to outside)

Ethernet Interface Channel 0

Ethernet Interface Channel 1 comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.4.2 Ethernet Interface of COMX51CA-RE

See section Ethernet Interface of COMX 100CA-RE on page 55.




7.5 Real-Time Ethernet Communication Module COMX 51CN-

RE

Figure 8: Photo of Communication Module COMX 51CN-RE

SMT-Connectors of the COMX51CN-RE (Connection to Host)

System Interface

Ethernet Interface

7.5.2 Ethernet Interface of COMX 51CN-RE

The pin assignment of the Ethernet interface of the COMX 51CN-RE is described in the comX Design Guide within subsection 3.2.4. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.6 CANopen Communication Module COMX 100CA-CO

62/212

Figure 9: Photo of Communication Module COMX100 CA-CO

LED Displays of COMX 100CA-CO

SYS LED

COM LED

SMT-Connectors of the COMX 100CA-CO (Connection to Host)

System Interface

Fieldbus connector of COMX 100CA-CO (connected to outside)

CANopen Interface comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.6.2 CANopen Interface of COMX 100CA-CO

The following figure shows the CANopen interface (D-Sub plug, male, 9 pin)

Figure 10: CANopen-Interface (D-Sub-plug, 9-pin) of the COMX 100CA-CO

Connection with

D-Sub-Plug

Signal Description

3

7

CAN_GND

CAN_H

CAN reference potential

CAN-High bus line

Figure 11: Pinning of CANopen Interface of the COMX 100CA-CO




7.7 CANopen Communication Module COMX 100CN-CO

64/212

Figure 12: Photo of Communication Module COMX100 CN-CO

SMT-Connectors of the COMX 100CN-CO (Connection to Host)

System Interface

CANopen Interface

7.7.2 CANopen Interface of COMX 100CN-CO

The pin assignment of the CANopen interface of the COMX 100CN-CO is described in the comX Design Guide within subsection 3.2.1. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.8 DeviceNet Communication Module COMX 100CA-DN

7.8.1 COMX 100CA- DN

65/212

Figure 13: Photo of Communication Module COMX 100CA-DN


COMX 100CA-DN communication module without the metal blocks required for mounting!

LED Displays of COMX 100CA-DN

SYS-LED

COM-LED

SMT-Connectors of the COMX 100CA-DN (Connection to Host)

System Interface

Fieldbus connector COMX 100CA-DN (connected to outside)

DeviceNet Interface comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.8.2 DeviceNet Interface of COMX 100CA-DN

The following figure shows the DeviceNet interface of the COMX 100CA-

DN (Combicon plug, 5 pin):

Figure 14: DeviceNet Interface (CombiCon-Plug, 5 pin) of the COMX 100CA-DN

Connection with

CombiCon plug

Signal Color Description

4

5 power supply

2 CAN_L Blue

3 Drain

CAN Low signal

Shield

CAN_H

V+

White

Red

CAN High signal

+24 V DeviceNet supply voltage

Table 22: Pinning of the DeviceNet-Interface of the COMX 100CA-DN




7.9 DeviceNet Communication Module COMX 100CN-DN

67/212

Figure 15: Photo of Communication Module COMX 100CN-DN

SMT-Connectors of the COMX 100CN-DN (Connection to Host)

System Interface

DeviceNet -Interface

7.9.2 DeviceNet Interface of COMX 100CN-DN

The pin assignment of the DeviceNet interface of the COMX 100CN-DN is described in the comX Design Guide within subsection 3.2.2. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.10 PROFIBUS-DP Communication Module COMX 100CA-DP

Figure 16: Photo of Communication Module COMX 100CA-DP


COMX 100CA-DP communication module without the metal blocks required for mounting!

LED Displays of COMX 100CA-DP

SYS-LED

COM-LED

SMT-Connector of the COMX 100CA-DP (Connection to Host)

System Interface

Fieldbus connector COMX 100CA-DP (connected to outside)

PROFIBUS-DP-Interface comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.10.2 PROFIBUS-DP Interface of COMX 100CA-DP

The following figure shows the PROFIBUS-DP interface (D-Sub plug, female, 9 pin)

Figure 17: PROFIBUS-DP-Interface(D-Sub plug, female, 9 pin) of the COMX 100CA-DP

Connection with

D-Sub-Plug


Receive-/Send data-P (Line B at plug)

5

6

DGND

VP

Data reference potential

Power supply (positive)

8 RxD/TxD-N plug)

Table 23: Pinning of the PROFIBUS-DP Interface of the COMX 100CA-DP




7.11 PROFIBUS-DP Communication Module COMX 100CN-DP

Figure 18: Photo of Communication Module COMX 100CN-DP

SMT-Connectors of the COMX 100CN-DP (Connection to Host)

System Interface

PROFIBUS-DP-Interface

7.11.2 PROFIBUS-DP Interface of COMX 100CN-DP

The pin assignment of the PROFIBUS-DP interface of the COMX 100CN-

DP is described in the comX Design Guide within subsection 3.2.3. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.12 CC-Link Communication Module COMX 10CA-CCS

71/212

Figure 19: Photo of Communication Module COMX 10CA-CCS

LED Displays of COMX 10CA-CCS

SYS-LED

COM-LED

Address and Baudrate Switches of the COMX 10CA-CCS

Address Switch 1 for CC-Link Slave Address (x10)

Address Switch 2 for CC-Link Slave Address (x1)

Baudrate Switch

SMT-Connectors of the COMX 10CA-CCS (Connection to Host)

System Interface

Fieldbus connector of COMX 10CA-CCS (connected to outside)

CC-Link Interface comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.12.2 Description of the Address and Baudrate Switches

72/212

The address and baudrate switches of the COMX 10CA-CCS are described in the comX Design Guide.

7.12.3 CC-Link Interface of COMX 10CA-CCS

The following drawing shows the CC-Link interface (D-Sub-male connector,

9-pole) of the COMX 10CA-CCS:

Isolated RS-485 interface:

Figure 20: CC-Link Interface (Screw terminal connector, 5 pin)

Connection with

Screw terminal

Connector

Signal

Description

Table 24: CC-Link -Interface of COMX 10CA-CCS




7.13 CC-Link Communication Module COMX 10CN-CCS

73/212

Figure 21: Photo of Communication Module COMX 10CN-CCS

SMT-Connectors of the COMX 10CN-CCS (Connection to Host)

System Interface

CC-Link Interface

Address and Baudrate Switches of the COMX 10CN-CCS

Address Switch 1 (Address x 10)

Address Switch 2 (Address x 1)

Baudrate Switch

7.13.2 Description of the Address and Baudrate Switches

The address and baudrate switches of the COMX 10CN-CCS are described in the comX Design Guide.

7.13.3 CC-Link Interface of COMX 10CN-CCS

The pin assignment of the CC-Link interface of the COMX 10CN-CCS is described in the comX Design Guide within subsection 3.2.1. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.14 CANopen Communication Module COMX 10CA-COS

74/212

Figure 22: Photo of Communication Module COMX10 CA-COS

LED Displays of COMX 10CA-COS

SYS LED

COM LED

SMT-Connectors of the COMX 10CA-COS (Connection to Host)

System Interface

Fieldbus Connector of COMX 10CA-COS (connected to outside)

CANopen Interface

Address Switches of COMX 10CA-COS

Address Switch 1

Address Switch 2

7.14.2 Description of the Address Switches

The address and baudrate switches of the COMX 10CA-COS are described in the comX Design Guide. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.14.3 CANopen Interface of COMX 10CA-COS

75/212

The following figure shows the CANopen interface (D-Sub plug, male, 9 pin)

Figure 23: CANopen-Interface (D-Sub-plug, 9-pin) of the COMX 10CA-COS

Connection with

D-Sub-Plug


3

7

CAN_GND

CAN_H

CAN reference potential

CAN-High bus line

Figure 24: Pinning of CANopen Interface of the COMX 10CA-COS




7.15 CANopen Communication Module COMX 10CN-COS

76/212

Figure 25: Photo of Communication Module COMX 10CN-COS

LED Displays of COMX 10CN-COS

SYS-LED

COM-LED

SMT-Connectors of the COMX 10CN-COS (Connection to Host)

System Interface

CANopen -Interface

Address Switches of COMX 10CN-COS

Address Switch 1

Address Switch 2


The address switches of the COMX 10CN-COS are described in the comX

Design Guide.

7.15.3 CANopen Interface of COMX 10CN-COS

The pin assignment of the CANopen interface of the COMX 10CN-COS is described in the comX Design Guide within subsection 3.2.2. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.16 DeviceNet Communication Module COMX 10CA-DNS

77/212

Figure 26: Photo of Communication Module COMX 10CA-DNS

LED Displays of COMX 10CA-DNS

SYS-LED

COM-LED

SMT-Connectors of the COMX 10CA-DNS (Connection to Host)

System Interface

Fieldbus connector COMX 10CA-DNS (connected to outside)

DeviceNet Interface

Address switches of COMX 10CA-DNS

Address Switch 1

Address Switch 2


The address switches of the COMX 10CA-DNS are described in the comX

Design Guide. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.16.3 DeviceNet Interface of COMX 10CA-DNS

78/212

The following figure shows the DeviceNet interface of the COMX 10CA-

DNS (Combicon plug, 5 pin):

Figure 27: DeviceNet Interface (CombiCon- Pug, 5 pin) of the COMX 10CA-DNS

Connection with

CombiCon plug

Signal Color Description

4

5

2 CAN_L Blue power supply

CAN Low signal

3 Drain Shield

CAN_H

V+

White

Red

CAN High signal

+24 V DeviceNet supply voltage

Table 25: Pinning of the DeviceNet-Interface of the COMX 10CA-DNS




7.17 DeviceNet Communication Module COMX 10CN-DNS

79/212

Figure 28: Photo of Communication Module COMX 10CN-DNS

LED Displays of COMX 10CN-DNS

SYS-LED

COM-LED

SMT-Connectors of the COMX 10CN-DNS (Connection to Host)

System Interface

DeviceNet Interface

Address Switches of COMX 10CN-DNS

Address switch 1

Address switch 2 comX | Communication Modules for Real-Time-Ethernet and Fieldbus




80/212

The address switches of the COMX 10 CN-DNS are described in the comX

Design Guide.

7.17.3 DeviceNet Interface of COMX 10CN-DNS

The pin assignment of the DeviceNet interface of the COMX 10CN-DNS is described in the comX Design Guide within subsection 3.2.3. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



7.18 PROFIBUS-DP Communication Module COMX 10CA-DPS

Figure 29: Photo of Communication Module COMX 10CA-DPS

LED Displays of COMX 10CA-DPS

SYS-LED

COM-LED

SMT-Connector of the COMX 10CA-DPS (Connection to Host)

System Interface

Fieldbus connector COMX 10CA-DPS (connected to outside)


Address Switches of COMX 10CA-DPS

Address switch 1

Address switch 2


The address switches of the COMX 10 CA-DPS are described in the comX

Design Guide. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



The following figure shows the PROFIBUS-DP interface (D-Sub plug, female, 9 pin)

Figure 30: PROFIBUS-DP-Interface (D-Sub plug, female, 9 pin) of the COMX 10CA-DPS

Connection with

D-Sub-Plug


Receive-/Send data-P (Line B at plug)

5

6

DGND

VP


Power supply (positive)

8 RxD/TxD-N plug)

Table 26: Pinning of the PROFIBUS-DP Interface of the COMX 10CA-DPS




7.19 PROFIBUS-DP Communication Module COMX 10CN-DPS

Figure 31: Photo of Communication Module COMX 10CN-DPS

LED Displays of COMX 10CN-DPS

SYS-LED

COM-LED

SMT-Connectors of the COMX 10CN-DPS (Connection to Host)

System Interface


Address Switches of COMX 10CN-DPS

Address switch 1

Address switch 2 comX | Communication Modules for Real-Time-Ethernet and Fieldbus




84/212

The address switches of the COMX 10 CN-DPS are described in the comX

Design Guide.

The pin assignment of the PROFIBUS-DP interface of the COMX 10CN-

DPS is described in the comX Design Guide within subsection 3.2.3. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Evaluation Board COMXEB

8 Evaluation Board COMXEB

85/212

8.1 Purpose

The evaluation board COMXEB allows commissioning and testing of comX modules. Using the evaluation board you can connect a comX module to a

PC or network via a host interface or diagnostic interface.

The COMXEB eases commissioning as you can configure the comX, load firmware into it, perform function tests and diagnosis. You can also use the evaluation board with a mounted comX module in order to develop the application program on a PC and to test it via the host interface.

The evaluation board COMXEB provides all necessary controls, displays and interfaces, see Figure 32 below. This chapter explains the basic function and describes these controls, displays and interfaces of the evaluation board COMXEB.

1 2 3 4 5

X409

36

X406

X407

X405

X402

35

34

33

32

P400

31

P401

30

X404

29

X403

P500

28

27

P501

CH0_LINK

26

25

CH0_ACT

24

CH1_LINK

23

CH1_ACT

22

X502

21

CH0

CH1

20 19 18 17 16 15 14 13 12

Figure 32: COMXEB

6

7

8

9

X350

X709

S701

S700

10

X351

11

S600 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Evaluation Board COMXEB 86/212

Figure 32

on page 85 shows a photo of the evaluation board COMXEB where all controls, displays and interfaces are marked with a number. The assignment of these numbers to the denominations and descriptions of these elements is given by the following table:

Number Denomination Meaning / Description

(1)

X300

Interface COMX CA-Module

(2)

(3)

X400

X501

/X401

/X500

Interface COMX CN Fieldbus modules

Interface COMX CN Real-Time Ethernet modules

(4)

S302 Host mode selection

(5)

(6)

(7)

S301

X350

X709

Data width (8/16 Bit) at parallel DPM mode

Host interface (Parallel Dual-Port-Memory interface, connection via CAB- NXPCA-PCI to NXPCA-PCI)

SPM interface

(8)

S701

DPM mode

(9)

(10)

S702

X351

Selection of SPM connector

Pin header SYNC/UART1

(11)

(12)

(13)

S600

X932

X930

Reset pushbutton

Female pin connector for power supply

CombiCon female connector for power supply

(14)

(15)

P900

P800

Power LED (entire device)

Power LED of SPM USB interface

(16)

X829

SPM USB interface

(17)

(18)

X611

X610

USB diagnostic interface

Jumper for boot mode

(19)

(20)

(21)

X601

-

X502

UART diagnostic interface

Matrix label (see section 17.1 “ Matrix Label ” in appendix for explanation

(22)

(23)

CH1_ACT

CH1_LINK

Real-time Ethernet interface (2 Channels)

Ethernet Activity-LED Channel 1 yellow

Ethernet Link-LED Channel 1 green

(24)

(25)

(26)

(27)

(28)

(29)

(30)

(31)

(32)

CH0_ACT

CH0_LINK

P501

P500

X403

X404

P401

P400

X402

Ethernet Activity-LED Channel 0 yellow

Ethernet Link-LED Channel 0 green

Communication status STA0

Communication status STA1

CANopen interface

DeviceNet interface

Communication status STA

LED (unused)

PROFIBUS interface

(33)

(34)

(35)

(36)

X405

X407

X406

X409

CC-Link interface

Jumper for AIFX connector

Jumper for AIFX connector

AIFX connector

Table 27: Legend to Figure 32




Assignment of comX modules to the sockets on the COMXEB

The following Table 28: Assignment of comX modules to the sockets on the

COMXEB:

explains, which comX modules can be applied in which socket on the COMXEB:

Socket/ Interface Module family Module

Socket

Socket

X300

X400 /

(1)

X401

(2)

comX CA module comX CN Fieldbus module

COMX 10CA-CCS

COMX 10CA-COS

COMX 10CA-DNS

COMX 10CA-DPS

COMX 50CA-REFO

COMX 51CA-RE

COMX 100CA-RE

COMX 100CA-CO

COMX 100CA-DN

COMX 100CA-DP

COMX 10CN-CCS

COMX 10CN-COS

COMX 10CN-DNS

COMX 10CN-DPS

Socket X500 / X501

(3)

comX CN-RE module

COMX 100CN-CO

COMX 100CN-DN

COMX 100CN-DP

COMX 51CN-RE

COMX 100CN-RE

Table 28: Assignment of comX modules to the sockets on the COMXEB:

Host connection and operation modes

The host connection is usually done via a parallel dual port memory interface ( X350

(6)

). If comX modules with netX10 or netX51 are used, alternatively a serial dual port memory interface is available.

The following operation modes are available:

Operation modes with parallel DPM (for all comX module types)

• DPM 8-bit (see page 114)

• DPM 16bit (see page 114)

Operation modes with serial DPM (SPI 50 MHz, only for comX 10 and comX 51)

• SPM via pin header

X709

(7)

(see page 115)

• SPM via USB Type B interface (

X829 )

(16)

(see page 116)

Setting the operation modes

Information on setting the modes of operation can be found in section

Controls




8.2 Controls

You can find additional information on this topic in section Setting the slide

switches depending on the selection of the host interface

on page 96.

8.2.1 Position for host mode selection- Slide switch (S302)

The setting of slide switch (S302)

(4)

decides between host-controlled and

board-controlled

mode of operation of the COMXEB.

Choose position Board of switch S302

(4)

, if the switch settings on the COMXEB shall decide about the selection of DPM or

SPM mode ( Slide switch S701

(8)

) and at DPM mode about the selection of 8-Bit mode or 16-Bit mode for DPM access mode ( Slide switch S301

(5)

).

Choose position Host of switch S302, if the host shall decide about the selection of DPM or SPM mode and at DPM mode about the selection of 8-Bit mode or 16-Bit mode for DPM access. This requires the lines DPM_DIRQ# and DPM_SIRQ# of

X350 to be connected accordingly at the host.

8.2.2 Selection of operation mode (DPM/SPM) - Slide switch (S701)

This slide switch (S701)

(8)

selects either the DPM or SPM mode of operation if option „Board-controlled“ of slide switch S302

(4)

has been chosen.

If the application should use serial dual port memory for the host connection, switch to SPM.

If the application should use parallel dual port memory for the host connection, switch to DPM.

Otherwise, if the slide switch S302

(4)

has been set to option „Host-

controlled“,

the host will decide on its own whether DPM or SPM mode is used.

Note: The selection of the DPM or SPM mode will get valid if a reset of the comX module is performed.

8.2.3 Width for data access at parallel DPM mode - Slide switch

(S301)

Slide switch S301

(5)

allows switching between data access to parallel dual-port memory with a width of 8 bit or 16 bit.

DPM data access width is 16 bit

DPM data access width is 8 bit

However, this is only relevant in DPM mode of operation. The DPM mode is set with slide switch S701

(8)

and slide switch S302

(4)

. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



•

Note: A power cycle is necessary to switch from 8 bit data width to 16 bit data with and vice versa, because the data width is read and set during start-up only.

•

8.2.4 Selection of serial interface - Slide switch (S700)

Slide switch S700

(9)

alternatively activates the pin header X709 or the

USB interface X829 .

SPM signals are connected with the pin header X709

(7)

SPM signals are connected with USB interface X829

(16)

(via the FTDI chip).

However, this is only relevant in SPM operation mode. The SPM mode is set with slide switch S701

(8)

and slide switch S302

(4)

.

8.2.5 Reset pushbutton (S600)

Pressing the pushbutton S600

(11)

initiates a reset of the comX module.

The boot jumper X610

(18)

should be set if you intend to activate the serial boot mode over USB. The start-up behavior is as follows:

• When boot jumper X610

(18)

is open, the comX module starts the firmware directly.

• When boot jumper X610

(18)

is set, the comX module stays in the serial boot mode (SYS LED on comX communication module is blinking yellow). In this mode the comX is able to load a new code such as a second-stage boot loader via either USB (or UART) and to subsequently execute it.

•

Note: The boot jumper X610

(18)

does not have any effect if no device is connected to the USB diagnosis connector X611 .

•

8.2.7 Configuration of AIFX Interface - Jumpers (X406 and X407)

These jumpers are used to configure the extension interface X409

(36)

for connecting to an AIFX. The AIFX is available as accessory for PROFIBUS,

CANopen, DeviceNet and CC-Link.

Important: Only set the jumpers in case of a comX with TTL signals

(COMX-CN... \NIF) being mounted in the COMX interfaces X400

(2)

and

X401

(2)

.

Short circuit

Never set a jumper between positions 1 and 2 of jumper X406

(35)

or

X407

(34)

! comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Fieldbus

PROFIBUS

Jumper

90/212

Description

Set the jumpers X406

(35)

and

X407

(34)

according to Figure 33 if you want to use an AIFX-DP at the

AIFX interface X409

(36)

.

CANopen/

DeviceNet

Figure 33:Jumper settings for using X409 as

PROFIBUS interface


(35)

and

X407

(34)

according to Figure 34 if you want to use an AIFX-CO or an

AIFX-DN at the AIFX interface

X409

(36)

.

CC-Link

Figure 34: Jumper settings for using X409 as

CANopen/ DeviceNet interface


(35)

and

X407

(34)

according to Figure 35 if you want to use an AIFX-CC at the

AIFX interface X409

(36)

.

Figure 35: Jumper settings for using X409 as CC-

Link interface




Fieldbus

Kein AIFX

Jumper

Figure 36: Jumper settings for using X409 without

AIFX

91/212

Description

Remove all jumpers both at X406

(35)

and at X407

(34)

(see Figure

36

), if you do not connect to an

AIFX at the AIFX interface

(36)

. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



8.3.1 Power supply connectors

8.3.1.1 Socket for Barrel Connector of Power Adaptor X932

The evaluation board COMXEB must be supplied with DC in the voltage range between 18 V and 30 V. Usually, this is done by an adaptor whose barrel connector has to be put into socket X932

(12)

. The typical supply voltage of that adaptor is 24 V DC ± 6 V DC.

The consumed power depends mainly on the type of the used comX module, for more details see the comX Design Guide.

Pin

1

Description

GND

2

+24V DC

Figure 37: Pin assignment power supply socket X932

The corresponding barrel connector of the power adaptor looks like this:

Figure 38: Barrel connector of the power adaptor

Alternatively, external power supply is possible via the green CombiCon connector X930

(13)

(3-pin).

X930

2

3

Pin

1

Name

GND

+24 V DC

FE

Table 29: Pin assignment of external power supply connector X930




8.3.2.1 Parallel Dual-Port-Memory Interface – Pin header (X350)

Table 30: Pin assignment Host interface X350

shows the pin assignment of the 68 pin dual-port memory interface X350

(6)

.

X350 Pin Signal

1

2 GND

3

4

5 GND

6

7 RES_DPM_IN#

8

9

10

11 DPM_DIRQ#

12 DPM_BUSY#

13 GND

14 DPM_RD#

15

16 DPM_WR#

17 GND

18 DPM_SIRQ#

19 DPM_BHE#

20 GND

21

22

23

24 DPM_CS#

25 GND

26

27

28

29

30

31

32

33 GND

34

35

36 DPM_A13

37 DPM_A12

38 DPM_A11

39 DPM_A10

40 DPM_A09

41 DPM_A08

42 DPM_A07 comX | Communication Modules for Real-Time-Ethernet and Fieldbus



43 DPM_A06

44 DPM_A05

45 DPM_A04

46 DPM_A03

47 DPM_A02

48 DPM_A01

49 DPM_A00

50 GND

51 IN_DPM_D15

52 IN_DPM_D14

53 IN_DPM_D13

54 IN_DPM_D12

55 IN_DPM_D11

56 IN_DPM_D10

57 IN_DPM_D09

58 IN_DPM_D08

59 DPM_D07

60 DPM_D06

61 DPM_D05

62 DPM_D04

63 DPM_D03

64 DPM_D02

65 DPM_D01

66 DPM_D00

Table 30: Pin assignment Host interface X350

94/212

Using the DPM over USB interface is described in section Parallel dual-

port memory interface (DPM)

on page 114.

The USB Interface X829

(16)

of the evaluation board COMXEB for accessing the serial dual-port memory is implemented as a USB socket of type B.

This interface is currently not supported, it is reserved for future applications. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



8.3.2.3 SPM Interface - Pin Header X709

95/212

The SPI interface provides signals for connecting to a host system (i.e. SPI master).

The signals of the serial dual-port memory interface of the evaluation board

COMXEB can be routed to the pin header X709

(7)

(16-pin) if according settings are made at switches S700

(9)

(Switch SPM to pin header, FTDI chip will not be used) and S701

(8)

(SPM Mode).

The pin assignment of pin header X709

(7)

is as follows:

Pin Header X709 Pin Signal

1 L_SPM_MISO

3 L_SPM_MOSI

4 GND

5 L_SPM_CS#

6 GND

7 L_SPM_CLK

8 GND

9 L_SPM_DIRQ#

10 GND

11 L_SPM_SIRQ#

12 GND

13 L_SPM_SIO2

14 GND

15 L_SPM_SIO3

16 GND

Table 31: Pin assignment of pin header X709

Figure 39: SPI-master-slave-connection

This figure also illustrates the signal directions. At least the signals

SPI_CLK

, SPI_CSn, SPI_MOSI und SPI_MISO and GND must be connected. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



8.3.2.4

96/212

Setting the slide switches depending on the selection of the host interface

At any particular time only one of the three host interfaces X350

(6)

, X709

(7)

or X829

(16)

can be used. The decision, which one of these will actually be used, depends on the settings of the slide switches S302 , S701 , S301 and S700 .

Mode Board controlled

For the operation of the host interfaces X350

(6)

, X709

(7)

and X829

(16)

, the slide switches described in section Controls on page 88 must be set according to the following Table 32: Settings for selecting the host interface

:

Activated host interface S302 S701 S700 S301

Parallel DPM interface

X350

(6)

Serial DPM interface X709

(7)

(Pin header)

Board

Board

DPM

SPM

Setting is not relevant

X709

Selection of

8 or 16 bit mode



(16)

(SPM over USB)

Board

SPM X829 Setting is not relevant

Table 32: Settings for selecting the host interface in mode Board controlled

Mode Host controlled

In mode Host controlled the firmware of the comX module evaluates the signals DPM_DIRQn und DPM_SIRQn of the parallel DPM interface X350

(6)

.

The selection of the host interface additionally depends from signal

DPM_DIRQn

in this mode. Signal DPM_SIRQn decides, whether the 8 bit or

16 bit mode is selected for the operation of the parallel DPM interface X350

(6)

, see below.

For the operation of the host interfaces X350

(6)

, X709

(7)

and X829

(16)

in mode Host controlled the following settings and signals are required, proceed according to the following Table 33: Settings for selecting the host

interface in mode Host controlled

:

Activated host interface

S302 Signal

DPM_DIRQ

S700 Signal

DPM_SIRQ

Parallel DPM interface

X350

(6)

Host

1

(parallel mode, default)


Selection of 8 or 16 bit mode:

DPM_SIRQ=1

selects the 8bit Mode

DPM_SIRQ=0

selects the

16-bit Mode


(7)

(Pin header)

0

(serial mode)

X709 Setting is not relevant

Host


(16)

(SPM over

USB)

Host

0

(serial mode)

X829 Setting is not relevant

Table 33: Settings for selecting the host interface in mode Host controlled




8.3.3.1 COMX Interface X300

Table 34: Pin assignment comX-interface X300

shows the pin assignment of the 50 pin interface X300

(1)

for connecting to all comX-CA communication modules.

X300 Pin Signal

(Parallel mode)

1

2

Word interface, active low

Bus high enable, active low

3

4

5

6

7

8

9

10

Data line 15

Data line 14

Data line 13

Data line 12

Data line 11

Data line 10

Data line 9

Data line 8

11 Ground

12 Power Supply

13 Transmit Data,

Serial line

14 Receive Data, Serial line

15 Request to Send,

Serial line & SYNC0

16 Clear to Send,

Serial line & SYNC1

17

USB positive,

Diagnostic line

18 USB negative,

Diagnostic line

19 Receive Data,

Diagnostic line

20 Transmit Data,

Diagnostic line

21 Reset, active low

22 Busy, active low

23

During operation:

Interrupt, active low

COMX 10 at start-up:

Host mode selection

24 Read, active low

25 Write, active low

26 Chip select, active low

27 Address line 13

28 Address line 12

29 Address line 11

30 Address line 10

31 Address line 9

Symbol

(Parallel mode)

DPM_SIRQ#

DPM_BHE#

DPM_D15

DPM_D14

DPM_D13

DPM_D12

DPM_D11

DPM_D10

DPM_D9

DPM_D8

GND

+3V3

UART1_TXD

UART1_RXD

UART1_RTS#/

SYNC0

UART1_CTS#/

SYNC1

USB+

USB-

UART0_RXD

UART0_TXD

Signal

(Serial mode)

reserved reserved reserved reserved

SPM_SIRQ#

Symbol

(Serial mode)

SPM_SIRQ#

SPM_DIRQ#–

Clock

Chip select, active low

Request to Send,

Serial line & SYNC0

Clear to Send,

Serial line & SYNC1

USB positive,

Diagnostic line

USB negative,

Diagnostic line

Receive Data,

Diagnostic line

Transmit Data,

Diagnostic line

SPM_DIRQ#

SPM_CLK

SPM_CS#

Master Out Slave In SPM_MOSI

Master In Slave Out SPM_MISO

Ground

Power Supply

GND

+3V3

UART1_TXD Transmit Data,

Serial line

Receive Data, Serial line

UART1_RXD

UART1_RTSn/

SYNC0

UART1_CTSn/

SYNC1

USB+

USB-

UART0_RXD

UART0_TXD

DPM_RESET#

DPM_BUSY#

Reset, active low

-

DPM_RESETn

-

DPM_DIRQ# DPM_DIRQn COMX 10, COMX 51 at start-up:

Host mode selection

DPM_RD#

DPM_WR#

DPM_CS#

DPM_A13

DPM_A12

DPM_A11

DPM_A10

DPM_A9 comX | Communication Modules for Real-Time-Ethernet and Fieldbus



32 Address line 8

33 Address line 7

34 Address line 6

35 Address line 5

36 Address line 4

37 Address line 3

38 Address line 2

39 Address line 1

40 Address line 0

41 Data line 7

42 Data line 6

43 Data line 5

44 Data line 4

45 Data line 3

46 Data line 2

47 Data line 1

48 Data line 0

49 Ground

DPM_A8

DPM_A7

DPM_A6

DPM_A5

DPM_A4

DPM_A3

DPM_A2

DPM_A1

DPM_A0

DPM_D7

DPM_D6

DPM_D5

DPM_D4

DPM_D3

DPM_D2

DPM_D1

DPM_D0

GND

+3V3





8.3.3.2

X400

COMX Interfaces X400/X401



(2)

for connecting to comX-CN communication modules for Fieldbus systems.

Pin Signal

(Parallel mode)

Symbol

(Parallel mode)

Signal

(Serial mode)

Symbol

(Serial mode)

5

6

3

4

1

2

7

8

Word Interface, active low DPM_SIRQ# reserved

Bus high enable, active low DPM_BHE# reserved

Data line 15

Data line 14

Data line 13

Data line 12

Data line 11

Data line 10

DPM_D15

DPM_D14

DPM_D13

DPM_D12

DPM_D11

DPM_D10

SPM_CS#

DPM_D9 reserved reserved

SPM_SIRQ#

SPM_DIRQ#

Clock


SPM_SIRQ#

SPM_DIRQ#

SPM_CLK

Master Out Slave In SPM_MOSI 9 Data line 9

10 Data line 8

11 Ground

DPM_D8

GND

Master In Slave Out

+3V3

UART1_TXD

SPM_MISO

13 Transmit Data,

Serial line


15 Request to Send,

Serial line & SYNC0

16

Clear to Send,

Serial line & SYNC1

UART1_RXD

UART1_RTS#/

SYNC0

UART1_CTS#/

SYNC1

USB+ 17 USB positive,

Diagnostic line

18 USB negative,

Diagnostic line

19 Receive Data,

Diagnostic line

20 Transmit Data,

Diagnostic line


USB-

UART0_RXD

UART0_TXD

22 Busy, active low

23 During operation:



Host mode selection

DPM_RESET#

DPM_BUSY#

DPM_DIRQ#

24 Read, active low



27 Address line 13

28 Address line 12

29 Address line 11

30 Address line 10

31 Address line 9

32 Address line 8

33 Address line 7

DPM_RD#

DPM_WR#

DPM_CS#

DPM_A13

DPM_A12

DPM_A11

DPM_A10

DPM_A9

DPM_A8




34 Address line 6

35 Address line 5

36 Address line 4

37 Address line 3

38 Address line 2

39 Address line 1

40 Address line 0

41 Data line 7

42 Data line 6

43 Data line 5

44 Data line 4

45 Data line 3

46 Data line 2

47 Data line 1

48 Data line 0

49 Ground

DPM_A6

DPM_A5

DPM_A4

DPM_A3

DPM_A2

DPM_A1

DPM_A0

DPM_D7

DPM_D6

DPM_D5

DPM_D4

DPM_D3

DPM_D2

DPM_D1

DPM_D0

GND

+3V3







(2)

for connecting to comX-CN communication modules for Fieldbus systems.

X401 Signal Symbol Pi n

1

2

PROFIBUS, Receive Data

CC-Link Receive Driver Enable, active low

4

5

6

CC-Link, Transmission period signal

PROFIBUS, Enable Bus Driver

CC-Link, Transmission Data

7

8

CAN, Receive Data (CANopen/DeviceNet)

CC-Link, Received Data (channel 1)

9

CAN, Transmit Data (CANopen/DeviceNet)

10

11

CAN, Power Fail

12

13 COM-LED, STA, Cathode green LED

14 SYS-LED, RUN, Cathode green LED

15 COM-LED, ERR, Cathode red LED

16 SYS-LED, RDY, Cathode yellow LED

17 Ground

18 Power Supply (+3.3 V)

20 Do not use –required for isolation

21 Do not use –required for isolation

22 PROFIBUS Reference potential

23 PROFIBUS Control

CAN_H Bus line

24

25 PROFIBUS, Receive / Send Data-N

26 PROFIBUS, Receive / Send Data-P

CANopen, CAN Ground

DeviceNet, Reference potential

CC-Link, Data A

27

DeviceNet, CAN Low Signal

CC-Link, Data B

28 DeviceNet, Drain

CC-Link, Data Ground

29 PROFIBUS, Positive power supply

CANopen, CAN_L Bus line

DeviceNet, CAN High-Signal

CC-Link, Function Ground

30 DeviceNet +24V Power Supply

CC-Link, Shield

DP_RX

CC_RDE#

DP_TX

CC_SDGATON

DP_EN

CC_SD

CO_RX/DN_RX

CC_RD

CO_TX/DN_TX

STA2#

CAN_PF

ERR2#

STA#

RUN#

ERR#

RDY#

GND

+3V3

PIO

DP_ISOGND

DP_CNTR-P

CO_H

DP_RXD_TXD-N

DP_RXD_TXD-P

CO_DN_V-

CO_DN_V-

CC_DA

DN_CAN_L

CC_DB

CO_DRAIN

CC_DG

DP_VP

CO_L

DN_CAN_H

CC_FG

DN_V+

CC_SLD





8.3.3.3

X501

COMX Interfaces X500/X501



(3)

for connecting to comX-CN communication modules for Real-Time Ethernet.

6

7

8

2

3

4

5

Pin Signal

(Parallel mode)

1

Symbol

(Parallel mode)

Signal

(Serial mode)

Word Interface, active low DPM_SIRQ# reserved

Bus high enable, active low

Data line 15

Data line 14

Data line 13

DPM_BHE#

DPM_D15

DPM_D14

DPM_D13 reserved reserved reserved

SPM_SIRQ#–

9

Data line 12

Data line 11

Data line 10

Data line 9

10 Data line 8

11 Ground

Symbol

(Serial mode)

SPM_SIRQ#

DPM_D12

DPM_D11

DPM_D10

SPM_DIRQ#–

Clock

SPM_DIRQ#

SPM_CLK


SPM_CS#

Master Out Slave In SPM_MOSI DPM_D9

DPM_D8

GND

Master In Slave Out SPM_MISO

+3V3

UART1_TXD 13 Transmit Data,

Serial line


15

SYNC0 & Request to Send,

Serial line

16 SYNC1 & Clear to Send,

Serial line

17 USB positive,

Diagnostic line

UART1_RXD

SYNC0/

UART1_RTS#

SYNC1/

UART1_CTS#

USB+

18 USB negative,

Diagnostic line

19 Receive Data,

Diagnostic line

20 Transmit Data,

Diagnostic line


22 Busy, active low

23 During operation:



Host mode selection

USB-

UART0_RXD

UART0_TXD

DPM_RESET#

DPM_BUSY#

DPM_DIRQ#

24 Read, active low



27 Address line 13

28 Address line 12

29 Address line 11

30 Address line 10

31 Address line 9

32 Address line 8

33 Address line 7

DPM_RD#

DPM_WR#

DPM_CS#

DPM_A13

DPM_A12

DPM_A11

DPM_A10

DPM_A9

DPM_A8




34 Address line 6

35 Address line 5

36 Address line 4

37 Address line 3

38 Address line 2

39 Address line 1

40 Address line 0

41 Data line 7

42 Data line 6

43 Data line 5

44 Data line 4

45 Data line 3

46 Data line 2

47 Data line 1

48 Data line 0

49 Ground

DPM_A6

DPM_A5

DPM_A4

DPM_A3

DPM_A2

DPM_A1

DPM_A0

DPM_D7

DPM_D6

DPM_D5

DPM_D4

DPM_D3

DPM_D2

DPM_D1

DPM_D0

GND

+3V3





X500



(3)

for connecting to comX-CN communication modules for Real-Time Ethernet.

Pin Signal

1

Symbol

Link-LED Channel 0 Cathode green, active low CH0_LINK#

2 TX/RX-LED Channel 0 Cathode yellow, active low

CH0_TXRX#

3

4

5

6

7

Link-LED Channel 1 Cathode green, active low CH1_LINK#

TX/RX-LED Channel 1Cathode yellow, active low

CH1_TXRX#

Transmit Data Positive Channel 0

Transmit Data Negative Channel 0

Transmit Center Tap Channel 0

8 Ground

9 Receive Data Positive Channel 0

10 Receive Data Negative Channel 0

PHY0_TXP

PHY0_TXN

PHY0_TXCT

GND

PHY0_RXP

PHY0_RXN

11 Receive Center Tap Channel 0

12 Ground

13 Transmit Data Positive Channel 1

14 Transmit Data Negative Channel 1

15 Transmit Center Tap Channel 1

16 Ground

PHY0_RXCT

GND

PHY1_TXP

PHY1_TXN

PHY1_TXCT

GND

17 Receive Data Positive Channel 1

18 Receive Data Negative Channel 1

19 Receive Center Tap Channel 1

20 Ground

28 -

29 -

30 -

PHY1_RXP

PHY1_RXN

PHY1_RXCT

GND

21 Status-LED Channel 0 Cathode red, active low STA0_CR#

22 Status-LED Channel 0 Cathode green, active low

STA0_CG#

23 Status-LED Channel 1 Cathode red, active low STA1_CR#

24 Status-LED Channel 1 Cathode green, active low

STA1_CG#

RDY# 25 SYS-LED, RDY, Cathode yellow LED, active low

26 SYS-LED, RUN, Cathode green LED, active low

RUN#

PIO





8.3.4.1

X402

8.3.4.2

X403

PROFIBUS-DP Interface X402

The following Table 39 explains the PROFIBUS-DP interface X402

(32)

(9-pin D-Sub, female) of the evaluation board COMXEB:


Transmit /receive data-P or pin B at the male connector

5

6

DP_ISOGND

DP_VP


Supply voltage +

Transmit /receive data-N or pin A at the male connector

Table 39: Pin assignment of the PROFIBUS-DP interface of COMXEB

CANopen Interface X403

The following Table 40 explains the CANopen interface X403

(28)

(9-pin D-

Sub, male) of the evaluation board COMXEB:


2 CO_L CAN-Low-line

3 CO_DN_V- CAN reference potential

8.3.4.3

X404

Table 40: Pin assignment of the CANopen interface of COMXEB

DeviceNet Interface X404

The following Table 41 explains the DeviceNet interface X404

(29)

(5-pin

CombiCon male connector) of the evaluation board COMXEB:

Pin Signal Color Description

Data reference potential of

DeviceNet-power supply

3 CO_DRAIN Shield

5 DN_V+ Red +24 V DeviceNet power supply

Table 41: Pin assignment of the DeviceNet interface of COMXEB




8.3.4.4

X405

CC-Link Interface X405

106/212

The following Table 42 explains the CC-Link interface X405

(33)

(5-pin

CombiCon screw connector) of the evaluation board COMXEB:

Connection to

CombiCon male connector


1 CC_DA

2 CC_DB

3 CC_DG Data

4 CC_SLD Shield

5 CC_FG

Table 42: Pin assignment of the CC-Link interface X405 of the COMXEB

X502

The following Table 43 explains the Real-Time Ethernet interface X502

(21)

(RJ45) of the evaluation board COMXEB:


1 TXP0 Transmit data +

2 TXN0

3 RXP0

4 TERM

5 TERM

6 RXN0

7 TERM

8 TERM

Transmit data –

Receive data +

Bob Smith termination

Receive data –

Bob Smith termination

Table 43: Pin assignment of Ethernet connector at channel 0 (channel 1 accordingly)

The Ethernet lines of the COMXEB provide Auto-Crossover -functionality. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



8.3.5.1

8.3.5.2

RS-232 Diagnostic Interface – DSub plug (X601)

The UART diagnostic interface X601

(19)

of the evaluation board COMXEB has been implemented as a DSub male connector (9-pin).

The following table explains the pin assignment of the connector:

Pin Name Description

2 RXD Receive data of comX comX

4 DTR Return-To-Send signal

5 GND Ground via 100 Ω resistor

Figure 40: Pin assignment of diagnostic interface connector X601

USB Diagnostic Interface - USB Mini-B connector (X611)

The diagnostic interface X611

(17)

of the evaluation board COMXEB is implemented as a USB socket of type Mini-B (5-pin).

USB Socket Pin

Signal

Description

Power supply of USB Bus (+5 V, external) 1 VBUS

2 D-

3 D+

4 ID

5 GND

N.c.

Ground

Figure 41: Pin assignment of Mini-B USB socket X611 (5-pin)




8.3.6.1 AIFX Interface (X409)

The COMXEB provides an additional 10-pin interface X409

(36)

for connecting to an AIFX plug-on interface only at \NIF modules such as the

COMX 100CN-DP\NIF, for example.

Note: This interface has to be configured according to the fieldbus system supported by the mounted comX Fieldbus module via the jumpers X406

(35)

and X407

(34)

. Also see Configuration of AIFX Interface - Jumpers

(X406 and X407)

on page 89.

X409 Pin Signal Description

Supply power +3.3V

(Output)

3 -

4 -

5 TX Transmit

7

EN_PB/

DN_PF

CANopen/

DeviceNet Power fail

CC-Link RDE Signal

(active low)

10 -

Table 44: Pin assignment of interface X409

Pin header X351

(10)

provides the synchronization signals SYNC0 and

SYNC1 depending on the used firmware for Real-time Ethernet (EtherCAT

Slave, PROFINET IO Device, and Sercos Master/Slave). These are located on lines of the netX which can also be used for UART1. However, UART1 is not supported by the standard firmware. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Item

SYNC signal

Connector

Max. cable length

Pin Header X351

109/212

2

3


1 UART1_TXD Transmit

UART1_RXD

SYNC0/

UART1_RTS#

UART 1 Receive

SYNC0 or UART 1 RTS

SYNC1 or UART 1 CTS 4 SYNC1/

UART1_CTS#

5 GND

6 +3V3

7 -

8 -

9 -

10 -

Ground

Supply power +3.3V (output)

Table 45: Pin assignment of pin header X351

Items on hardware

Explanation

3,3 V (LVTTL), maximum load 6 mA

SYNC- Connector, X351:

Pin header male, 10-pins, pitch spacing 2.54mm

Recommendation: Max. 50 mm

Note: Take EMC into consideration for the cable laying

Tabelle 1: SYNC connector: SYNC sgnal, connector, max. cable length

Protocol

EtherCAT Slave

Sercos Master

Sercos Slave

Items on firmware

The firmware determines the input signal or output signal. The following table shows the meaning of the SYNC signals for each protocol.

Signal IO_SYNC0

Input/Output

Signal IO_SYNC1

Input/Output

SYNC 1

Output

From

Firmware

Version

Remarks

- Configurable SYNC 0

Output

External trigger to start bus cycle

Input

Rising edge

CON_CLK

Output

DIV_CLK

Output

3.0.10.0 Configurable

Table 46: Meaning of the SYNC sgnals for each protocol




There are three groups of LEDs at the COMXEB:

Power-LEDs

Communication status LEDs

Ethernet Link/Activity–LEDs

The following Table 47: Power LEDs of COMXEB explains the power LEDs of COMXEB:

Denomination of LED

Type Description

P800

(15)

Single-LED green chip FT2232HQ is present, i.e. 5V available at USB interface X829

(16)

.

P900

(14)

Single-LED green evaluation board is operational, i.e. whether either

X932

(12)

or X930

(13)

is supplied with 24 V

Table 47: Power LEDs of COMXEB

8.4.2 Communication Status LEDs

While COMX-CA modules have own LEDs for displaying the communication status (and other information), the COMX-CN modules use

LEDs located on the COMXEB. These are the LEDs P400

(31)

, P401

(30)

,

P500

(27)

and P501

(26)

.

The following Table 48: Communication Status LEDs of COMXEB explains the communication status LEDs of COMXEB:

Description Denomination Type

P400

(31)

P401

(30)

Duo LED

( green/

red)

P500

(27)

P501

(26)

Duo LED

( green/

red)

Duo LED

( green/

red)

Indicates the communication status signals STA (Pin

#13) and ERR (Pin #15) of the COMX-CN Fieldbus module.

STA is displayed in green, ERR in red.

Indicates the communication status signals STA1_CG

(Pin #24) and STA1_CR (Pin #23) of channel1 of the

COMX-CN- RE module.

STA1_CG is displayed in green, STA1_CR in red.

Indicates the communication status signals STA0_CG

(Pin #22) and STA0_CR (Pin #21) of channel 0 of the

COMX-CN- RE module.

STA0_CG is displayed in green, STA0_CR in red.

Table 48: Communication Status LEDs of COMXEB

The LEDs P401 is only active if a COMX-CN Fieldbus module has been plugged into X400 (2) and X401 (2) . The meaning of the blinking codes of all supported Fieldbus systems is described in section 10.2”LEDs Fieldbus-

Systems

” on page 117. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



The LEDs P500 (27) and P501 (26) are only active if a COMX-CN Real-

Time Ethernet module has been plugged into X500 (3) and X501 (3) . The meaning of the blinking codes of all supported Real-Time Ethernet systems is described in section LEDs Real-Time Ethernet Systems on page 124.

These LEDs are only active if a COMX-CN-RE module has been plugged into the comX interfaces X500

(3)

und X501

(3)

. They are directly located at the RJ45 ( X502 ) of the corresponding Ethernet communication channel.

The following Table 49: Ethernet Link/Activity–LEDs explains the communication status LEDs of COMXEB:

Denomination Type Description

CH0_LINK

(25)

green

CH0_ACT

(24)

CH1_LINK

(23)

CH1_ACT

(22)

yellow

green

yellow

This LED displays the Ethernet link status of channel

0 of the Ethernet interface.

This LED displays the Ethernet activity status of channel 0 of the Ethernet interface.

This LED displays the Ethernet link status of channel

1 of the Ethernet interface.

This LED displays the Ethernet activity status of channel 1 of the Ethernet interface.

Table 49: Ethernet Link/Activity–LEDs

Meaning of the LED signals

Information on the LED signals can be found in section LEDs Real-Time

Ethernet Systems on page 124. Refer to the appropriate subsection for the currently used real-time Ethernet system

8.5 Accessories

Accessory

For the Evaluation Board COMXEB the following accessories are available:

Article number Description Purpose

NXPCA-PCI 7902.100

Ribbon cable

Allows access to the parallel dual-port memory from an external PC

For connecting the COMXEB with the NXPCA-PCI CAB-

NXPCA-PCI

4400.000

AIFX-DP 2800.400 For connecting the COMXEB via X409

AIFX-CO 2800.500

PROFIBUS interface

CANopen interface

For connecting the COMXEB via X409

AIFX-DN 2800.510

AIFX-CC 2800.730

DeviceNet interface

CC-Link interface



Table 50: Accessories for the Evaluation Board COMXEB



Connection to the PC

9 Connection to the PC

112/212

9.1 Overview

The connection between PC and a COMX module can be accomplished in three different manners which are described in the following.

The following kinds of host connections are possible:

$ Parallel DPM

$ Serial SPM

$ SPM-USB

The following kinds of diagnostic connections between a PC and a COMX module are possible:

$

Serial connection via UART diagnostic interface X601

(19)

$ Via the USB diagnostic interface X611

(17)

In order to operate a comX module via a USB connection at a PC, proceed as follows:

1. Plug the comX module into the appropriate comX interface for that kind of module:

$ comX-CA into

(1)

$ comX-CN Fieldbus module into X400 / X401

(2)

$ comX-CN-RE module into X500 / X501

(3)

2. Connect the USB diagnostic interface X611

(17)

with a serial port of your PC via a USB cable.

3. Create other connections (such as Host, Fieldbus, Real-time

Ethernet connections) for your test, if necessary,

4. Supply the COMXEB with power. Use the power supply delivered with the device and connect it to socket X932

(12)

of the COMXEB.

5. Then switch on the PC.

Firmware update via USB connection

Section 12.1.2.2 „Set-up B2: Updating the Firmware with SYCON.net via

the USB Interface

“ on page 144 describes how to perform a firmware update via a USB connection. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Connection to the PC 113/212

The firmware must be capable of UART and be configured for the use of

UART, for instance with SYCON.net.

In order to operate a comX module via a serial connection at a PC, proceed as follows:

1. Plug the comX module into the appropriate comX interface for that kind of module:

$ comX-CA into

(1)

$ comX-CN Fieldbus module into X400 / X401

(2)

$ comX-CN-RE module into X500 / X501

(3)

2. Connect the UART diagnostic interface X601

(19)

with a serial port of your PC via a SubD cable (9 pin).

3. Create other connections (such as Host, Fieldbus, Real-time

Ethernet connections) for your test, if necessary,

4. Supply the COMXEB with power. Use the power supply delivered with the device and connect it to socket X932

(12)

of the COMXEB.

5. Then switch on the PC.

Firmware update via serial connection

Section 12.1.2.1 „Set-up B1: Updating the Firmware with SYCON.net via

the Serial Interface

“ on page 143 describes how to perform a firmware update via a serial connection. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



9.3.1 Parallel dual-port memory interface (DPM)

A host connection via the parallel dual-port memory can be established using the NXPCA-PCI. In order to do so, mount the NXPCA-PCI within a free PCI slot of a PC and connected to the evaluation board COMXEB by the ribbon cable CAB- NXPCA-PCI as shown in Figure 42 below.

NXPCA-PCI

COMXEB

Figure 42: Connection COMXEB <=> NXPCA-PCI ( <=> Host) via parallel Dual-Port Memory

A connection from the host to the COMXEB via SPM can be accomplished either via the SPM over USB interface X829

(16)

or via pin header X709

(7)

. When using the SPM over USB interface X829

(16)

, a usual USB cable can be used for the connection comX | Communication Modules for Real-Time-Ethernet and Fieldbus



9.3.2 Serial dual-port memory interface (SPM)

The connection between the COMXEB and the host is accomplished via a cable connected to X709

(7)

according to the following Figure 43: Serial

host connection via X709

.

Figure 43: Serial host connection via X709

The connection of each signal is done exactly as depicted in Figure 39:

SPI-master-slave-connection




9.3.3 Serial dual-port memory interface over USB (SPM over USB)

Only for future applications

Using the SPM over USB-interface X829

(16)

a connection to a PC can be established via a usual USB cable (Type A / Type B), see Figure 44: Serial

host connection via the USB connector X829

below.

Figure 44: Serial host connection via the USB connector X829



LEDs

10 LEDs

117/212

10.1 SYS-LED

LED

SYS

The following table describes the meaning of the system LED.

Color State

Duo LED yellow/green

Meaning

(green)

On Operating System running

(green/yellow)

Blinking green/yellow

Second Stage Boot loader is waiting for firmware

(yellow)

-

On

Off

Second Stage Boot loader missing; contact technical support

Power supply for the device is missing or hardware defect

Table 51: System LED

The SYS-LED is located at the left edge of the COMX 100CA-RE on the left hand side of the netX Processor and is denominated as „L1“ within the context of the preceding section.

At the COMX 100CN-RE there are no LEDs at the communication module itself but the LED signals are connected outside by connector X2.

10.2 LEDs Fieldbus-Systems

10.2.1 LED Names of individual Fieldbus Systems

LED

System

( (yellow)/ (green)) status SYS SYS SYS SYS

Communication status

LED

System Status

Name

SYS

COM CAN LRUN

(red / green)

(red / green)

(green)

LERR

(red)

MNS

(red / green)

Meaning

System

Communication Status

LRUN/LERR Run/Error

MNS Module Network Status comX | Communication Modules for Real-Time-Ethernet and Fieldbus


LEDs 118/212

10.2.2 LEDs PROFIBUS-DP Master

LED

COM

The subsequent table describes the meaning of the LEDs for the comX

PROFIBUS-DP Master communication modules (COMX 100CA-DP/ COMX

100CN-DP) when the firmware of the PROFIBUS DP Master protocol is loaded to the comX communication module.

Color State Meaning

Duo LED red/green

(green)

(green)

Flashing acyclic

Flashing cyclic

On

No configuration or stack error

PROFIBUS is configured, but bus communication is not yet released from the application

Communication to all Slaves is established

(green)

(red)

Flashing cyclic

On

Communication to at least one Slave is disconnected

(red)

Communication to one/all Slaves is disconnected

Table 52: LEDs PROFIBUS DP Master

LED

COM


PROFIBUS-DP Slave communication modules (COMX CA-DP/ COMX CN-

DP) when the firmware of the PROFIBUS DP Slave protocol is loaded to the comX communication module.

Color State


Meaning

(green)

On RUN, cyclic communication

(red)

On Wrong configuration at PROFIBUS DP slave.

(red)

Flashing cyclic STOP, no communication, connection error

(red)

Flashing acyclic not configured

Table 53: LEDs PROFIBUS DP Slave



LEDs 119/212

LED

COM

10.2.5 LEDs CC-Link Slave

LED

L RUN

L ERR

The subsequent table describes the meaning of the LEDs for the comX CC-

Link Slave communication modules (COMX 100CA-CCS/ COMX 100CN-

CCS) when the firmware of the CC-Link Slave protocol is loaded to the comX communication module.


LED green

(off)

(green)

Off

On

1. Before participating in the network

2. Unable to detect carrier

3. Timeout

4. Resetting hardware

Receive both refresh and polling signals or just the refresh signal normally, after participating in the network.

LED red

(off)

(red)

(red)

Off

Blinking

On

1. Normal communication

2. Resetting hardware

The switch setting has been changed from the setting at the reset cancellation (blinks for 0.4 sec.).

1. CRC error

2. Address parameter error (0, 65 or greater is set including the number of occupied stations)

3. Baud rate switch setting error during cancellation of reset

(5 or greater)

Table 55: LEDs CC-Link Slave

The subsequent table describes the meaning of the LEDs for the comX communication module when the firmware of the PROFIBUS MPI protocol is loaded to the device.



(green)

(green)

On

Blinking

(regularly)

5 Hz

Status

The device currently holds the PROFIBUS token and is able to transfer telegrams of data.

Status

The device is configured to be a part of the PROFIBUS ring, but it must share the PROFIBUS token with other

PROFIBUS-Master devices present on the PROFIBUS ring.

Status

Automatic baudrate detection is running

(green)

Blinking

(regularly)

0.5 Hz

On

(red)

(off)

Off

Error

Communication error at the PROFIBUS.

Status/Error

The device has not been integrated into the PROFIBUS ring, i.e. it has not been configured correctly or has a wrong configuration or has not received the PROFIBUS token.

Table 54: LEDs PROFIBUS MPI



LEDs 120/212

10.2.6 LEDs CANopen Master

LED

CAN


CANopen Master communication modules (COMX-CA-CO/ COMX-CN-

COM) when the firmware of the CANopen Master protocol is loaded to the comX communication module.



Off

Single flash

The device is executing a reset

STOPPED: The Device is in STOPPED state

-

(green)

(green)

(green)

Blinking

On

PREOPERATIONAL: The Device is in the

PREOPERATIONAL state

OPERATIONAL: The Device is in the OPERATIONAL state

(red)

(red)

Single flash

Double flash

Warning Limit reached: At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).

Error Control Event: A guard event (NMT Slave or NMTmaster) or a heartbeat event (Heartbeat consumer) has occurred.

Bus Off: The CAN controller is bus off

(red)

On

Table 56: LEDs CANopen Master

LED State Definition for CANopen Master for the CAN LED

Indicator state Definition

On The indicator is constantly on.

Off

Blinking

Single Flash

Double Flash

The indicator is constantly off.

The indicator turns on and off with a frequency of 2,5 Hz: on for

200 ms, followed by off for 200 ms.

The indicator shows one short flash (200 ms) followed by a long off phase (1,000 ms).

The indicator shows a sequence of two short flashes (each

200 ms), separated by a short off phase (200 ms). The sequence is finished by a long off phase (1,000 ms).

Table 57: LED State Definition for CANopen Master for the CAN LED



LEDs 121/212

10.2.7 LEDs CANopen Slave

Color


CANopen Slave communication modules (COMX-CA-CO/ COMX-CN-

COS) when the firmware of the CANopen Slave protocol is loaded to the comX communication module.

State Meaning LED

comX

CAN Duo LED red/green

(off)

Off

(green)

Single flash

(green)

Blinking

(green)

On

(red/green)

(red)

Flickering

(alternatively red / green)

Single flash

RESET: The device is executing a reset

STOPPED: The device is in STOPPED state

PREOPERATIONAL: The device is in the PREOPERATIONAL state

OPERATIONAL: The device is in the OPERATIONAL state

Auto Baud Rate Detection active: The Device is in the Auto Baud Rate

Detection mode

(red)

(red)

Double flash

On

Warning Limit reached: At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).

Error Control Event: A guard event (NMT Slave or NMT-master) or a heartbeat event (Heartbeat consumer) has occurred.

Bus Off: The CAN controller is bus off

Table 58: LEDs CANopen Slave – 1 Communication Status LED (current Hardware

Revision)

Indicator state

On

Off

Flickering

Blinking

Single Flash

Double Flash

LED State Definition for CANopen Slave for the CAN LED

Definition

The indicator is constantly on.


The indicator turns on and off with a frequency of 10 Hz: on for 50 ms, followed by off for 50 ms.

The indicator turns on and off with a frequency of 2,5 Hz: on for 200 ms, followed by off for 200 ms.


The indicator shows a sequence of two short flashes (each 200 ms), separated by a short off phase (200 ms). The sequence is finished by a long off phase (1,000 ms).

Table 59: LED State Definition for CANopen Slave for the CAN LED



LEDs 122/212

LED

MNS

Indicator state

On

Off

Flashing (1 Hz) green

Flashing (1 Hz) red

Color

The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the DeviceNet Master protocol is loaded to the device.

State


Meaning

(green)

On

Device Operational AND On-line, Connected

Device is online and has established all connections with all Slaves.

(green)

(green/red/off)

Flashing (1 Hz)

Device Operational AND On-line

Device is online and has established no connection in the established state.

- Configuration missing, incomplete or incorrect.

Flashing

Green/Red/Off

Selftest after power on:

Green on for 250 ms, then red on for 250 ms, then off.

(red)

(red)

(off)

Flashing (1 Hz) Minor Fault and/or Connection Time-Out

Device is online and has established one or more connections in the established state. It has data exchange with at least one of the configured Slaves.

Minor or recoverable fault: No data exchange with one of the configured Slaves. One or more Slaves are not connected.

Connection timeout

On

Off

Critical Fault orCritical Link Failure

Critical connection failure; device has detected a network error: duplicate MAC-ID or severe error in CAN network (CAN-bus off).

Device is not powered

- The device may not be powered.

Device is not on-line and/or No Network Power

- The device has not completed the Dup_MAC_ID test yet.

- The device is powered, but the network power is missing.

Table 60: LEDs DeviceNet Master

LED State Definition for DeviceNet Master for the MNS LED

Definition



The indicator turns on and off with a frequency of appr. 1 Hz: on for appr. 500 ms, followed by off for appr. 500 ms.


Table 61: LED State Definition for DeviceNet Master for the MNS LED



LEDs 123/212

LED

MNS

Indicator state

On

Off

Flashing (1 Hz) green

Flashing (1 Hz) red

Color

The subsequent table describes the meaning of the LEDs for the fieldbus when the firmware of the DeviceNet Slave protocol is loaded to the device.

State


Meaning

(green)

On

Device Operational AND On-line, Connected

Device is online and has established all connections with all Slaves.

(green)

(green/red/off)

Flashing (1 Hz)

Device Operational AND On-line

Device is online and has established no connection in the established state.

- Configuration missing, incomplete or incorrect.

Flashing

Green/Red/Off

Selftest after power on:

Green on for 250 ms, then red on for 250 ms, then off.

(red)

(red)

(off)

Flashing (1 Hz) Minor Fault and/or Connection Time-Out

Device is online and has established one or more connections in the established state. It has data exchange with at least one of the configured Slaves.

Minor or recoverable fault: No data exchange with one of the configured Slaves. One or more Slaves are not connected.

Connection timeout

On

Off

Critical Fault orCritical Link Failure

Critical connection failure; device has detected a network error: duplicate MAC-ID or severe error in CAN network (CAN-bus off).

Device is not powered

- The device may not be powered.

Device is not on-line and/or No Network Power

- The device has not completed the Dup_MAC_ID test yet.

- The device is powered, but the network power is missing.

Table 62: LEDs DeviceNet Slave

LED State Definition for DeviceNet Slave for the MNS LED

Definition





Table 63: LED State Definition for DeviceNet Slave for the MNS LED



LEDs 124/212

10.3 LEDs Real-Time Ethernet Systems

10.3.1 LED Names of individual Real-Time Ethernet Systems

Note: Depending on the loaded COMX 100CA-RE/COMX 100CN-RE firmware the LEDs of the COMX 100CA-RE/COMX 100CN-RE communication modules are configured as follows.

Color of LED

(red/ green Duo-

LED)

(green)

(red)

(red/ green Duo-

LED)

(green)

(red)

(Ethernet

Connectors)

(green)

(yellow)

(Ethernet

Connectors)

(green)

(yellow)

RUN RUN MS BS RUN - STA S3 RUN

ERR ERR NS BE ERR BF ERR - ERR

LINK

-

L/A

IN

L/A

OUT

LINK L/A LINK LINK L/A L/A LINK

LINK L/A LINK LINK L/A L/A LINK

LED

Communication Status

RJ45

Name

RUN

MS

NS

BS

BE

ERR

STA

SF

BF

S3

LINK, L

ACT, A

L/A

L/A IN

L/A OUT

Meaning

Run

Error

Status

System Error

Bus Error

Module Status

Network Status

Bus Status

Bus Error

Sercos Status/Error

Link

Activity

Link/Activity

Link/Activity Input

Link/Activity Output

Table 64: LED Names of individual Real-Time Ethernet Systems



LEDs 125/212

LED

RUN

Name in the device drawing:

COM 0

ERR


COM 1


Real-Time Ethernet communication modules (COMX 100CA-RE/ COMX

100CN-RE) when the firmware of the EtherCAT Master protocol is loaded to the comX communication module.



(off)

Off

INIT: The device is in state INIT

PRE-OPERATIONAL: The device is in PRE-

OPERATIONAL state

BOOT: Device is in BOOT state

(green)

Blinking

(green)

Flickering

(green)

Single Flash

(green)

On


(off)

Off

(red)

On

SAFE-OPERATIONAL: The device is in SAFE-

OPERATIONAL state

OPERATIONAL: The device is in OPERATIONAL state

Master has no errors

Master has detected a communication error. The error is indicated in the DPM

LINK/

RJ45

Ch0

ACT/

RJ45

Ch0

LED green

(green)

On A link is established

(off)

LED yellow

(yellow)

Flashing The device sends/receives Ethernet frames

Table 65: LEDs EtherCAT Master

LED State Definition for EtherCAT Master for the RUN and ERR LEDs


On

Off

Blinking

Flickering

Single Flash

Double Flash





The indicator turns on and off with a frequency of approximately

10 Hz: on for approximately 50 ms, followed by off for 50 ms.




Table 66: LED State Definition for EtherCAT Master for the RUN and ERR LEDs



LEDs 126/212

L/A IN/

RJ45

Ch0

L/A

OUT/

RJ45

Ch1

RJ45

Ch0

RJ45

Ch1

LED

RUN


COM 0

ERR


COM 1



100CN-RE) when the firmware of the EtherCAT Slave protocol is loaded to the comX communication module.



(off)

Off

INIT: The device is in state INIT

(green)

(green)

Blinking

Single Flash

PRE-OPERATIONAL: The device is in state PRE-

OPERATIONAL

SAFE-OPERATIONAL: The device is in state SAFE-

OPERATIONAL

OPERATIONAL: The device is in state OPERATIONAL

(green)

(green)

On


(off)

(red)

(red)

(red)

Off

Blinking

No error: The EtherCAT communication of the device is in working condition

Invalid Configuration: General Configuration Error

Possible reason: State change commanded by master is impossible due to register or object settings.

Single Flash

Local Error: Slave device application has changed the

EtherCAT state autonomously.

Possible reason 1: A host watchdog timeout has occurred.

Possible reason 2: Synchronization Error, device enters

Safe-Operational automatically.

Double Flash Application Watchdog Timeout: An application watchdog timeout has occurred.

Possible reason: Sync Manager Watchdog timeout.

LED green

On A link is established

(green)


(off)

LED yellow

(yellow)

- -

Table 67: LEDs EtherCAT Slave



LEDs 127/212

LED State Definition for EtherCAT Slave for the RUN and ERR LEDs


On

Off

Blinking

Single Flash

Double Flash








Table 68: LED State Definition for EtherCAT Slave for the RUN and ERR LEDs



LEDs 128/212

10.3.4 LEDs EtherNet/IP-Scanner (Master)

LED

MS


COM 0


Real-Time Ethernet communication modules (COMX-CA-RE/ COMX-CN-

RE) when the firmware of the EtherNet/IP Scanner (Master) protocol is loaded to the comX communication module.



(green)

On

Device operational: If the device is operating correctly, the module status indicator shall be steady green.

(green)

Flashing Standby: If the device has not been configured, the module status indicator shall be flashing green.

(red)

On Major fault: If the device has detected a non-recoverable major fault, the module status indicator shall be steady red.

(red)

(red/green)

Flashing Minor fault: If the device has detected a recoverable minor fault, the module status indicator shall be flashing red. NOTE:

An incorrect or inconsistent configuration would be considered a minor fault.

Flashing Self-test: While the device is performing its power up testing, the module status indicator shall be flashing green/red.

NS


COM 1

status indicator shall be steady off.


(green)

(green)

(red)

(red)

(red/green)

On

Connected: If the device has at least one established connection (even to the Message Router), the network status indicator shall be steady green.

Flashing No connections: If the device has no established connections, but has obtained an IP address, the network status indicator shall be flashing green.

On Duplicate IP: If the device has detected that its IP address is already in use, the network status indicator shall be steady red.

Flashing Connection timeout: If one or more of the connections in which this device is the target has timed out, the network status indicator shall be flashing red. This shall be left only if all timed out connections are reestablished or if the device is reset.

Flashing Self-test: While the device is performing its power up testing, the network status indicator shall be flashing green/red.

IP address (or is powered off), the network status indicator shall be steady off.

LINK/RJ45

Ch0 & Ch1

LED green

(green)

-

LED yellow

On

Off

A connection to the Ethernet exists

The device has no connection to the Ethernet

ACT/RJ45

Ch0 & Ch1

(yellow)


Table 69: LEDs EtherNet/IP Scanner (Master)



LEDs 129/212

10.3.5 LEDs EtherNet/IP-Adapter (Slave)

LED

MS


COM 0



RE) when the firmware of the EtherNet/IP Adapter (Slave) protocol is loaded to the comX communication module.



(green)

(green)

(red)

(red)

(red/green)

On

Device operational: If the device is operating correctly, the module status indicator shall be steady green.

Flashing

Standby: If the device has not been configured, the module status indicator shall be flashing green.

On Major fault: If the device has detected a non-recoverable major fault, the module status indicator shall be steady red.

Flashing Minor fault: If the device has detected a recoverable minor fault, the module status indicator shall be flashing red. NOTE:

An incorrect or inconsistent configuration would be considered a minor fault.

Flashing Self-test: While the device is performing its power up testing, the module status indicator shall be flashing green/red.

NS


COM 1

LINK/RJ45

Ch0 & Ch1

ACT/RJ45

Ch0 & Ch1

(red) status indicator shall be steady off.


(green)

(green)

(red)

On Connected: If the device has at least one established connection (even to the Message Router), the network status indicator shall be steady green.

Flashing

No connections: If the device has no established connections, but has obtained an IP address, the network status indicator shall be flashing green.

On Duplicate IP: If the device has detected that its IP address is already in use, the network status indicator shall be steady red.

Flashing Connection timeout: If one or more of the connections in which this device is the target has timed out, the network status indicator shall be flashing red. This shall be left only if all timed out connections are reestablished or if the device is reset.

(red/green)

Flashing

Self-test: While the device is performing its power up testing, the network status indicator shall be flashing green/red.

Not powered, no IP address: If the device does not have an

IP address (or is powered off), the network status indicator shall be steady off.

LED green

On A connection to the Ethernet exists

(green)

-

LED yellow

Off The device has no connection to the Ethernet


(yellow)

Table 70: LEDs EtherNet/IP Adapter (Slave)



LEDs 130/212

10.3.6 LEDs Open Modbus/TCP

LED

RUN


COM 0

ERR


COM 1

LINK/RJ

45 Ch0

& Ch1

ACT/RJ

45 Ch0

& Ch1



100CN-RE) when the firmware of the Open Modbus/TCP protocol is loaded to the comX communication module.



(off)

(green)

(green)

(green)

Off

Flashing cyclic with 1Hz


On

Not Ready

OMB task is not ready

Ready, not configured yet

OMB task is ready and not configured yet

Waiting for Communication:

OMB task is configured

Connected:

OMB task has communication – at least one TCP connection is established


(off)

Off No communication error

(red)

(red)


(On/Off Ratio =

25 %)

System error

On Communication error active

LED green

(green)

(yellow)

On

(off)

LED yellow

Off

Flashing



The device sends/receives Ethernet frames

Table 71: LEDs Open Modbus/TCP



LEDs 131/212

10.3.7 LEDs POWERLINK Controlled Node/Slave

LED

BS


COM



100CN-RE) when the firmware of the Powerlink Controlled Node/Slave protocol is loaded to the comX communication module.



0

BE


COM 1

L/A/

RJ45

Ch0 & Ch1

(off)

(green)

Flickering

Single

Flash

Slave is in Basic Ethernet state

Slave is in Pre-Operational 1

Double

Flash

Slave is in Pre-Operational 2

Triple Flash Slave is in ReadyToOperate

On Slave is Operational

Slave is Stopped Blinking


(off)

Off

(red)

On

Slave has no error

Slave has detected an error

Link: A connection to the Ethernet exists

RJ45

Ch0 & Ch1

LED green

(green)

On

(green)

Flashing

(off)

Off

LED yellow

-

Activity: The device sends/receives Ethernet frames


This LED is not used.

Table 72: LEDs Powerlink Controlled Node/Slave

LED State Definition for Powerlink Controlled Node/Slave for the

BS/BE LEDs

Indicator state

Definition

On

Off



Blinking

Flickering

Single Flash

Double Flash

Triple Flash


2,5 Hz: on for approximately 200 ms, followed by off for 200 ms. Red and green LEDs shall be on alternately.


10 Hz: on for approximately 50 ms, followed by off for 50 ms. Red and green LEDs shall be on alternately.

The indicator shows one short flash (approximately 200 ms) followed by a long off phase (approximately 1,000 ms).

The indicator shows a sequence of two short flashes (each approximately 200 ms), separated by a short off phase (approximately

200 ms). The sequence is finished by a long off phase (approximately

1,000 ms).

The indicator shows a sequence of three short flashes (each comX | Communication Modules for Real-Time-Ethernet and Fieldbus


LEDs 132/212 approximately 200 ms), separated by a short off phase (approximately

200 ms). The sequence is finished by a long off phase (approximately

1,000 ms).

Table 73: LED State Definition for Powerlink Controlled Node/Slave for the BS/BE LEDs

10.3.8 LEDs PROFINET IO-RT-Controller

LED

SF


COM 0



100CN-RE) when the firmware of the PROFINET IO-RT Controller protocol is loaded to the comX communication module.



(red)

On

(red)

Flashing cyclic at 2 Hz

(

together with BF „red ON“)

No valid Master license

System error: Invalid configuration, Watchdog error or internal error

BF


COM 1

(off)


(red)

(red)

On


No Connection: No Link.

or (

together with SF „red ON“)

No valid Master license

Configuration fault: not all configured IO-Devices are connected.

LINK/RJ45

Ch0 & Ch1

(off)

LED green

(green)

On

(off)

LED yellow

Off



RX/TX/RJ45

Ch0 & Ch1

(yellow)


Table 74: LEDs PROFINET IO-RT Controller



LEDs 133/212

10.3.9 LEDs PROFINET IO-RT-IRT-Device

LED

SF


COM 0



RE) when the firmware of the PROFINET IO-RT-Device protocol is loaded to the comX communication module.



(red)

(red)

On


(for 3 sec.)

Watchdog timeout; channel, generic or extended diagnosis present; system error

DCP signal service is initiated via the bus

BF


COM 1

(off)


(red)

(red)

On


No configuration; or low speed physical link; or no physical link

No data exchange

LINK/RJ45

Ch0 & Ch1

(off)

LED green

(green)

On

(off)

Off

LED yellow



RX/TX/RJ45

Ch0 & Ch1

(yellow)


Table 75: LEDs PROFINET IO-RT-Device



LEDs 134/212

10.3.10 LEDs Sercos-Master

LED

STA


COM 0

ERR


COM 1



RE) when the firmware of the Sercos Master protocol is loaded to the comX communication module.



(green)

Blinking

CP0: Communication phase 0

Master isn't configured and is in NRT. After a status change this isn't indicated again


(green)

Flickering

(green)

Single Flash

(green)

Double Flash

(green)

(red)

Triple Flash

(green)

(red)

On

(off)

Off


Blinking

Flickering

(red)

(red)

Single

Flickering

Quadruple

Flash




NRT: Non Real-time Mode

Error in the configuration database.

Boot-up was stopped due to an error.

Channel Init was executed at the Master.

No Master license present in the device

(red)

Triple Flash DPM Watchdog has expired.

Internal Stop of the bus cycle

(red)

Double Flash

(red)

Single Flash Bus Sync Error Threshold

L/A/RJ45

Ch0 & Ch1

RJ45

Ch0 & Ch1

(off)

LED green

(green)

On

(green)

Flashing

(off)

Off

LED yellow

-

Table 76: LEDs Sercos Master

Link: A connection to the Ethernet exists

Activity: The device sends/receives Ethernet frames


This LED is not used. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


LEDs 135/212

LED State Definition for Sercos Master for the STA and ERR LEDs


Off

Blinking

Single Flickering

Flickering

Single Flash

Double Flash

Triple Flash

Quadruple Flash




The indicator turns on and off with a frequency of approximately 10 Hz: on for approximately 50 ms, followed by off for 50 ms.

The indicator turns on and off once: on for approximately 50 ms, followed by off for 50 ms.




The indicator shows a sequence of three short flashes (each


The indicator shows a sequence of four short flashes (each


Table 77: LED State Definition for Sercos Master for the STA and ERR LEDs



LEDs 136/212

10.3.11 LEDs Sercos-Slave

LED

S3


COM 0


COM 1

L/A/RJ45

Ch0 & Ch1



RE) when the firmware of the sercos Slave protocol is loaded to the comX communication module.


Duo LED red/green/orange (orange = red/green simultaneously)

(off)

Off

NRT-Mode: No sercos Communication

(green)

(green)

(green/ orange)

(orange/ green)

(orange)

On CP4: Communication phase 4, Normal operation, no error

Flashing (4 Hz) Loopback: The network state has changed from „fastforward“ to „loopback“.

Flashing

(1 x green / 3 s)

Flashing

(2 x green / 3 s)

CP1: Communication phase 1: Flashing green for 250 ms, then orange on for 2 second and 750 ms

CP2: Communication phase 2: Flashing green / orange / green, each for 250 ms, then orange on for 2 seconds and 250 ms

Flashing

(3 x green / 3 s)

Flashing (4 Hz) HP0: Hot-plug mode (not yet implemented): Flashing orange permanently

Flashing (1 x orange / 3 s)

HP2: Hot-plug mode (not yet implemented): Flashing orange for 250 ms, then green on for 2 seconds an 750 ms

Flashing (2 x orange / 3 s)

CP3: Communication phase 3: Flashing green / orange / green / orange / green, each for 250 ms, then orange on for 1 second and 750 ms

HP3: Hot-plug mode (not yet implemented): Flashing orange / green / orange, each for 250 ms, then green on for 2 seconds and 250 ms

On CP0: Communication phase 0

(orange)

(green/ red)

(red

/orange)

Flashing (2 Hz) Identification: Corresponds to C-DEV.Bit 15 in the

Slave’s Device Control indicating remote address allocation or configuration errors between Master and

Slaves (for details refer to sercos Slave V3 Protocol API

Manual).

Flashing (2 Hz),

The LED flashes at least for

2 seconds from green to red.

MST losses ≥

(S-0-1003/2): Depends on IDN S-0-1003

(for details refer to sercos Slave Protocol API manual).

Corresponds to S-DEV.Bit 15 in the Device Status indicating a communication warning (Master SYNC telegrams have not been received)

Flashing (2 Hz) Application error (C1D): See GDP & FSP Status codes class error. See sercos Slave V3 Protocol API Manual.

(red)

(red)

Flashing (2 Hz)

On

Watchdog error: Application is not running (not yet implemented)

Communication Error (C1D): Error detected according to sercos Class 1 Diagnosis, see SCP Status codes class error. See sercos Slave V3 Protocol API Manual.


- - This LED is not used.

LED green

(green)

On Link: A connection to the Ethernet exists comX | Communication Modules for Real-Time-Ethernet and Fieldbus


LEDs

RJ45

Ch0 & Ch1

(green)

Flickering

(off)

Off

LED yellow

- -

Table 78: LEDs sercos Slave

137/212

Activity: The device sends/receives Ethernet frames


This LED is not used.

LED State Definition for sercos Slave for the S3 LED


On

Off

Flashing (2 Hz)

Flashing (4 Hz)

Flickering



The indicator turns on and off with a frequency of 2 Hz: first color for appr. 250 ms, followed by the second color for appr. 250 ms.

The indicator turns on and off with a frequency of 4 Hz: first color for appr. 125 ms, followed by the second color for appr. 125 ms.


10 Hz: on for approximately 50 ms, followed by off for 50 ms.

Table 79: LED State Definition for sercos Slave for the S3 LED



LEDs 138/212

10.3.12 LEDs VARAN Client

LED

RUN


COM 0

ERR


COM 1

Color

The subsequent table describes the meaning of the LEDs for the comX communication module when the firmware of the VARAN Client protocol is loaded into the device.

State


Meaning

(off)

(green)

Blinking Configured and communication is inactive.

(green)

On Configured and communication is active.


(off)

Off Configured.

(red)

(red)

LINK

RJ45

Ch0 & Ch1

ACT

RJ45

Ch0 & Ch1

Indicator state

On

Off

Blinking

LED green

(green)

(yellow)

On

(off)

LED yellow

Off

Flashing



The device sends/receives Ethernet frames

Table 80: LEDs VARAN Client

LED State Definition for VARAN Client for the RUN and ERR LEDs

Definition



The indicator turns on and off with a frequency of 5 Hz: on for 100 ms, followed by off for

100 ms.

Table 81: LED State Definition for VARAN Client for the RUN and ERR LEDs



Troubleshooting 139/212

11 Troubleshooting

In case of any error, please follow the hints given here in order to solve the problem:

General

!

Check, whether the requirements for comX communication module operation are fulfilled:

Important: In any case, update older versions of the cifX Device Driver to the current version, see

Table 2: Reference to Software

.

.

Further information on this topic you can find in section “Prerequisites

for the Operation of the comX Communication

Modules” on page 33.

SYS-LED

!

Check the status of the SYS LED. A solid green SYS LED indicates that the firmware of the comX communication module is operational.

LINK-LED

!

Check using the LINK LED status, whether a connection to the Ethernet has been established successfully. Depending on the environment of the comX communication module proceed as follows:

• If the comX communication module is mounted in its target environment:

Check signals LINK0 at pin 1 for channel 0 and LINK1 at pin 3 for channel 1, respectively.

Mounting

!

Check that the comX communication module is mounted correctly in the socket.

Configuration

!

Check the configuration in the master and the slave device. The configuration has to match. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Updating the Firmware

12 Updating the Firmware

140/212

12.1 Possibilities of Firmware Update

This section introduces the various possibilities of firmware update for the

COMX-C communication modules and explains, when which possibility should be considered.

During the construction of the device it must be taken into account, that at least one of the two diagnostic interfaces which are suited for firmware update must be accessible, i.e. connected to the outside.

This not only enables an easy way for the firmware update, but also provides extensive diagnosis possibilities via the configuration software

SYCON.net (see sections „Diagnosis“ and „Extended Diagnosis“ of the

SYCON.net DTM manuals) being a sophisticated and powerful diagnostic tool or alternatively via the cifX test application as a lean and compact diagnostic tool which is easy to use.

If neither the serial nor the USB interface is connected to the outside of the device, a firmware update can only be performed by removing the comX communication module from the device and connecting it to a PC using an evaluation board (COMXEB, Hilscher part number 1530.000)

12.1.1 Update the comX-Firmware in built-in State(Embedded System)

For firmware update in built-in state (i.e. as embedded system, the following two solutions are available: comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Updating the Firmware 141/212

12.1.1.1 Set-up A1: Updating the Firmware with SYCON.net via the USB-

Interface

This set-up is used for updating the firmware of an embedded system via the USB interface from an external PC.

Necessary preconditions:

1. The USB interface of the comX communication module must be leaded through and connected to the outside of the device into which the comX communication module has been built in.

2. SYCON.net has been installed at the PC.

Figure 45: Set-up A1: Updating the Firmware with SYCON.net via the USB-Interface

Note: Read in section

Update the Firmware with SYCON.net

on page 147 how you can update the f

SYCON.net.

irmware of a comX communication module with comX | Communication Modules for Real-Time-Ethernet and Fieldbus



12.1.1.2 Set-up A2: Updating the Firmware with SYCON.net via the Serial

Interface

This set-up is used for updating the firmware of an embedded system via the serial interface from an external PC.


1. The serial interface of the comX communication module must be leaded through and connected to the outside of the device into which the comX communication module has been built in.

2. SYCON.net has been installed at the PC.

Figure 46: Set-up A2: Updating the Firmware with SYCON.net via the Serial Interface

Note: Read in section


on page 147 how you can update the f

SYCON.net.

irmware of a comX communication module with

12.1.2 Updating the Firmware using an Evaluation Board COMXEB and a PC

For firmware update of comX communication modules connected to a PC via the evaluation board COMXEB, the following solutions are available: comX | Communication Modules for Real-Time-Ethernet and Fieldbus



12.1.2.1 Set-up B1: Updating the Firmware with SYCON.net via the Serial

Interface

This set-up is used for updating the firmware of a comX communication modules connected to a PC via the evaluation board COMXEB (see above) using SYCON.net via the serial interface.


1. The comX communication

module is plugged into the appropriate module socket of the evaluation board COMXEB.

2. A serial connection has been established between evaluation board

(diagnostic interface X601) and (external) PC.

3. SYCON.net has been installed at the (external) PC.

Figure 47: Set-up B1: Firmware update with SYCON.net via the serial interface using evaluation board COMXEB

Note: Read in section “


”

on page 147 how you can update the f irmware of a comX communication module with

SYCON.net.




12.1.2.2 Set-up B2: Updating the Firmware with SYCON.net via the USB

Interface

This set-up is used for updating the firmware of a comX communication module connected to a PC via the evaluation board COMXEB (see above) using SYCON.net via a USB interface.



module is plugged into the appropriate module socket of the evaluation board COMXEB. connection has been established between the evaluation board

(Mini-USB interface X611) and the (external) PC.


Figure 48: Set-up B2: Firmware update with SYCON.net via the USB interface using evaluation board COMXEB

Note: Read in section 12.2 “


”

on page 147 how you can update the f irmware of a comX communication module with SYCON.net.




12.1.2.3 Set-up B3: Updating the Firmware with SYCON.net via NXPCA-PCI and

DPM

This set-up is used for updating the firmware of a comX communication module connected to a PC via the evaluation board COMXEB (see above) using SYCON.net via NXPCA-PCI and a DPM interface.



module is plugged into the appropriate module socket of the evaluation board COMXEB.

2. A ribbon cable connection has been established between the evaluation board (Host interface X350 ) and the (external) PC.


Figure 49: Set-up B3: Firmware update with SYCON.net via the NXPCA-PCI and DPM interface using evaluation board COMXEB




12.1.2.4

146/212

Set-up B4: Updating the Firmware with SYCON.net via SPM over USB

This set-up is used for updating the firmware of a comX communication module connected to a PC via the evaluation board COMXEB (see above) using SYCON.net via SPM over USB.



module is plugged into the appropriate module socket of the evaluation board COMXEB. connection

has been established between the evaluation board

(Host interface X829

(16)

) and the (external) PC.


Figure 50: Set-up B4: Updating the Firmware with SYCON.net via SPM over USB




12.2 Update the Firmware with SYCON.net

For comX communication modules which are used as embedded systems and already mounted into their target environment , this is the only possibility to perform a firmware update. In order to access the comX module, SYCON.net has to be used in conjunction with the netX driver.

This can be accomplished both via a USB connection and via a serial connection. This complies with the update possibilities described in sections Set-up A1: Updating the Firmware with SYCON.net via the USB-

Interface

and Set-up A2: Updating the Firmware with SYCON.net via the

Serial Interface

.

A firmware update can also be performed via a serial or USB interface at a comX communication module connected to a PC via an evaluation board.

This complies with the update possibilities described in sections “Set-up

B1: Updating the Firmware with SYCON.net via the Serial Interface

” and

“Set-up B2: Updating the Firmware with SYCON.net via the USB Interface”.

In this case SYCON.net has to be applied in conjunction with the netX

Driver.

!

In order to start the System Configurator SYCON.net selects the following entry in the Windows starting menu.

Programs > SYCON.net System Configurator > SYCON.net

" The System Configurator SYCON.net is opened.

You can find a detailed description of the update process in the manual of the DTM of the Fieldbus or Real-Time Ethernet communication system of your choice, see topic User Manual SYCON.net.

In order to update the firmware of the comX communication module with

SYCON.net, the following three steps are necessary, which have to be performed exactly in the given order:

1. Creation project

2. Device assignment (Create connection to the comX communication module). This includes the:

• Selection of the correct driver

• and the selection of the comX communication module to be used.

3. Performing the main part of the firmware update

The selection of the driver must be done taking into account the update method to be applied, as described above.

Access from SYCON.net to the comX communication module is done via the netX driver.

!

Select the “netX Driver” by checking the according checkbox for “netX

Driver

”.

Note: This is described in section corresponding

3.2.1 “Selecting the Driver“

of the

SYCON.net DTM Manual.

More valuable information concerning this topic can be found in section

3.2.4 “netX Driver” of the SYCON.net DTM-Manual. The necessary adjustment of interfacing parameters is explained in section 3.2.4.2

“Driver parameters for netX Driver - USB/RS232 Connection“

..




Figure 51: Selection of netX Driver

Note:

The selection of the device can be done as explained in section „Device

Assignment

“ of the according SYCON.net DTM manual.

!

We recommend only to display the suitable devices when performing the following steps. Select „Suitable only“ in the combo box „Device

selection“

.

!

In order to start the search process for suitable devices, click at the button „Search“(see Figure 52: Starting the Search Process for Devices

and Selection of Device

on page 149, at the red arrow right on top).

!

For the selection of the device check the checkbox of the comX communication module whose firmware is to be updated (also see

Figure 52: Starting the Search Process for Devices and Selection of

Device

on page 149, at the red arrow in the center part of the figure). comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Figure 52: Starting the Search Process for Devices and Selection of Device

The main part of the firmware update is described in section 3.4 „Firmware

Download

“ of the respective SYCON.net DTM Manual. Proceed as follows:

!

In the navigation area, select Settings>Firmware Download.

!

Open a file selection dialog by clicking at the button „Select“ (Figure 53:

Firmware Download with SYCON.net (after Selection of the Firmware)

, see right at the top).

!

In this dialog select the firmware file to be loaded.

"

Then, the screen should look like this: comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Figure 53: Firmware Download with SYCON.net (after Selection of the Firmware)

!

In order to start the firmware update process, click at „Load“ (Figure 53:

Firmware Download with SYCON.net (after Selection of the Firmware)

see ).

Important: Take care of the warning message issued within the window. A reconstruction of the state prior to starting the firmware update might be impossible.




12.2.1 Troubleshooting

Problem

The following table lists some known error situations, explains their causes and shows possible ways to solve the respective problem.

The error message appears.

Explanation 1 The loaded file does not contain firmware for any Hilscher device (neither for comX nor for any other Hilscher device).

Action 1 Load a correct firmware file, see Table 3: Reference to Firmware on page 12!

Explanation 2 At update possibility B1: the adapter card has either only bad contact to the PCI carrier board or no contact at all.

Action 2 Check whether the adapter card is mounted correctly.

Explanation 3 At update possibility B1: the comX communication module has either bad contact to the adapter card or no contact at all.

Action 3 Check whether the comX communication module is mounted correctly.

Problem The error message appears.

Explanation 1 The connection to the comX communication module has been lost due to contact problems.

Action 1 Check whether the comX communication module and in case of update possibility B1 the adapter card is mounted correctly.

Explanation 2 At update possibility A1, A2 and B2:

The connection to the comX communication module has been lost due to contact problems at the serial or USB connection.

Action 2 At update possibility A1, A2 and B2: Check whether the serial cable or the USB cable has correct contact. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



Problem The error message

152/212

Explanation

1

Action 1

Explanation

2

Action 2

Problem appears.

The connection to the comX communication module has been lost due to contact problems.

Check whether the comX communication module and in case of update possibility

B1 the adapter card is mounted correctly.

At update possibility A1, A2 and B2:

The connection to the comX communication module has been lost due to contact problems at the serial or USB connection.

At update possibility A1, A2 and B2: Check whether the serial cable or the USB cable has correct contact.


Explanation The device classes do not match. The selected firmware file contains a Hilscher firmware which is not suited for the comX communication module but for another

Hilscher product (in this case for instance a cifX card).

Action Select a firmware suitable for the comX communication module by clicking at

Select

and selecting the firmware within the subsequent file selection dialog. See


on page 12. Finally, load this firmware into the comX communication module by clicking at Download. comX | Communication Modules for Real-Time-Ethernet and Fieldbus




153/212

Problem appears.

Explanation The communication classes do not match. Either the firmware file to be loaded is suited for a Master/Scanner/Controller and the installed comX communication module requires a Slave/ Adapter/ Device firmware or firmware file to be loaded is suited for a Slave/ Adapter/ Device and the installed comX communication module requires a Master/Scanner/Controller firmware.

If a change from Master to Slave or vice versa is intended and a Master license is present, then click at Yes to perform the intended change. In all other cases click at No.

Action Use a firmware of the correct type for your comX communication module, i.e. a

Master firmware for a Master module and a Slave firmware for a Slave module.


Explanation The protocol classes do not match. The selected firmware does not support any protocol suited for the selected comX communication module. This error situation mostly occurs in conjunction with the two error situations discussed directly above, see the illustration.

Action Use a suitable firmware for a protocol that is supported by your comX communication module.

If a change of the Real-Time Ethernet System is intended and you use a comX

Real-Time Ethernet Module (such as COMX 100CA-RE, COMX 100CN-RE), click at Yes in order to perform the intended change. In all other cases click at No. comX | Communication Modules for Real-Time-Ethernet and Fieldbus




154/212 appears.

Explanation The protocol classes do not match. The selected firmware does not support any protocol suited for the selected comX communication module. This error situation mostly occurs in conjunction with the two error situations discussed directly above, see the illustration.

Action Use a suitable firmware for a protocol that is supported by your comX communication module.

If a change of the Real-Time Ethernet System is intended and you use a comX

Real-Time Ethernet Module (such as COMX 100CA-RE, COMX 100CN-RE), click at Yes in order to perform the intended change. In all other cases click at No.

options do not match…”

appears.

Explanation The hardware options do not match, i.e. either you use a Real-Time Ethernetfirmware in conjunction with a Fieldbus communication module, or vice versa, a

Fieldbus firmware in conjunction with a Real-Time Ethernet communication module. comX communication module.

If the option Yes is clicked at, a non-conforming firmware is loaded and the module will not operate correctly. button in screen Firmware Download is grayed out and thus deactivated.

Explanation There is a (not necessarily permanent) contact problem.

Action Check whether the comX communication module and the adapter card are mounted correctly and have good electrical contact. Then, click the button Select and again select the firmware file to be loaded using the subsequent file selection dialog. Afterwards, the button Download should not be grayed out anymore. comX | Communication Modules for Real-Time-Ethernet and Fieldbus




155/212 appears.

Explanation A message timeout has occurred. The connection to the comX communication module has been lost due to contact problems, while the button Select has been clicked..

Action Check whether the comX communication module and in case of update possibility

B1 the adapter card has been mounted correctly.

Problem The error message appears.

Explanation At update possibility A1, A2 and B2: The firmware download has been finished with an error due to the serial or USB connection to the comX communication module having been lost during the firmware download.

Action At update possibility A1, A2 and B2: Check whether the serial cable or the USB cable has correct contact.

Table 82: Possible Causes of Errors, their Consequences and necessary Actions for their

Removal at Firmware Update with SYCON.net

If problems should occur at the firmware download, you should also check the following additional topics:

• If you intend to load a Master firmware: is a Master license present and loaded. If not, a Master license has to be purchased at Hilscher and must be loaded.

• Is the switch Byte/Word of the PCI carrier board CIF 50-CB-COM-ABC in position „Word“? If necessary, switch to „Word“!

• Especially for update possibility B1: Check the revision number of the

PCI carrier board CIF 50-CB-COM-ABC. This revision number must be greater or equal to 5. Revisions 1 to 4 of the PCI carrier board are not capable for connecting comX modules.

• Has the System Configurator SYCON.net been installed correctly

• Is the correct device selected within SYCON.net? comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Diagnostic Interfaces 156/212

13 Diagnostic Interfaces

In general, as Diagnostic Interfaces USB and serial interface are available.

13.1 Support of Diagnostic Interfaces by comX Firmware

The following table indicates from which firmware version on the firmware supports the diagnostic interface.

Firmware file name

COMXCOM.NXF

COMXCOS.NXF

M0505000.NXF

M0509000.NXF

Fieldbus system

CANopen Master

CANopen Slave

CANopen Slave comX10

CC-Link Slave comX10

Minimum allowed version number of firmware for use of

USB or serial interface

From V2.2.5.0

From V2.4.4.0

From V3.0.3.0

From V2.6.1.0

M0507000.NXF

COMXECM.NXF

DeviceNet Slave comX10

EtherCAT Master

From V2.3.5.0

From V2.4.4.0

COMXEIM.NXF

COMXEIS.NXF

EtherNet/IP Scanner

EtherNet/IP Adapter

From V 4.2.11.x

From V2.2.4.1

From V2.3.4.1

From V 2.7.13.x

COMXOMB.NXF Open Modbus/TCP From V2.3.2.1

From V 2.5.11.x

COMXPLS.NXF POWERLINK From V2.1.22.0

COMXDPM.NXF PROFIBUS-DP Master From V2.3.22.0

COMXDPS.NXF

M0502000.nxf

M0203000.nxf

PROFIBUS-DP Slave From V2.3.31.0

PROFIBUS DP Slave comX10 From V2.4.1.0

PROFIBUS MPI From V2.4.2.0 cx51pns.nxf

COMXS3M.NXF

COMXS3S.NXF

M060J000.nxf

PROFINET IO Device comX51

Sercos Master

Sercos Slave

Sercos Slave

From V3.5.26.x

From V2.0.14.0

From V3.0.13.0

From V3.1.19.x

Table 83: Firmware Versions with Support for Diagnostic Interface

The following firmwares do not provide any support of diagnostic interfaces

(USB or serial interface):

• CC-Link Slave

• PROFINET IO Device V2 (however, PROFINET IO Device from V3.4.9.0 contains the required support) comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Diagnostic Interfaces 157/212

13.2 Hint concerning the Usage of the Software

The USB interface, the serial interface as well as the cifX Device Driver may only be used exclusively by one software, that is

• the SYCON.net configuration software (with integrated ODM V3) or

• the netX Configuration Tool or

• the cifX Test Application or

• the cifX Driver Setup Utility or

• the application program

Important: Never use the listed software simultaneously, otherwise this will result in communication problems with the device.

If the SYCON.net configuration software was used on the PC, then stop the

ODMV3 service before you use one of the other software listed above.

!

Therefore, select Service > Stop from the context menu of the ODMV3 system tray icon.

13.3 Hardware Modification of comX Module for Recognition of comX-Reset at a connected Windows

®-

Diagnosis PC

The following table indicates at which hardware revision of the comX module the electronic circuit of the USB interface has been changed:

Communication module

COMX 100CA-CO

COMX 100CN-CO

COMX 100CA-DN

COMX 100CN-DN

COMX 100CA-DP

COMX 100CN-DP

COMX 50CA-CCS

(firmware does not support USB)

COMX 100CA-RE

COMX 100CN-RE

7

2

3

3

3

4

3

4

Hardware Revision

4

Table 84: First Hardware Version with new USB Interface

This modification was necessary in order to enable recognition of a comX reset by a Diagnosis PC running Microsoft Windows

®.

. Windows

®. closes the USB driver and automatically restarts it, when the comX executes a reset and is then again ready to communicate over USB. comX 10 modules and comX 51 modules always allow recognition of a comX reset by a Diagnosis PC under Windows

®

.

Note: If you use a comX communication module of a former hardware revision, it is necessary to pull away the USB cable from the USB connector and then plug it again after a reset of the comX communication module

(which, for instance occurs after a firmware download) comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Technical Data 158/212

14 Technical Data

Note: All technical data in this section are subject to change without any further notice.

14.1 Technical Data of COMX Modules

COMX 100CA-RE

Part number 1531.100

Communication Controller

Processor

Integrated Memory

System interface

RAM/ FLASH

Size of Dual-Port-Memory

Width for DPM data access

Type

8 MB SDRAM, 4 MB SPI-Flash-EPROM

16 KB

8/16 Bit

50 Pin SMT Connector, female

Ethernet Communication

Ethernet interface

Diagnosis

Display

Pin distance (Grid) 1.27 mm

Corresponding male connector SAMTEC TFM - 125 - 02 - S - D – A or TFC - 125 -

02 - F - D – A

Ethernet-Standard/ Frame type IEEE 802.3/ Ethernet II

Supported Real-Time Ethernet communication standard/ firmware

Determined by loaded firmware.: EtherCAT

Master/Slave, EtherNet/IP Scanner (Master)/

Adapter(Slave), Open Modbus/TCP, Powerlink

Controlled Node (Slave), PROFINET_IO-Controller

(Master)/ Device (Slave), Sercos Master/ Slave,

TCP/IP, VARAN Client (Slave)

2 * RJ45 socket, potential free Hardware

Transmission rate

Interface Type

100 MBit/s, 10 MBit/s (depending on the firmware)

100 BASE-TX, isolated, 10 BASE-T (depending on the loaded firmware) supported (at 100 MBit/s) Half duplex / full duplex

Auto-Negotiation / Auto-Crossover (depending on the loaded firmware)

Diagnostic interfaces/ signals UART (RXD, TXD), USB (RX0, TX0, USB+, USB-)

LED Display SYS System Status (green: RUN, yellow: RDY)

COM0, COM1 Communication Status (both green or red, depending on loaded firmware)

TX/RX0, TX/RX1 Ethernet activity status (yellow)

LINK0, LINK1 Ethernet link status (green)

Power supply /Current consumption

Environment

Device

Supply voltage +3.3 V ± 5 % DC

Typical current/ power at 3,3 V Approx. 700…750 mA / 2.5 W

Ambient temperature range

(Rev. 8)

Operation: 0°C...+65°C,

Storage (device only): -40°C…+85 °C

Storage (device in package): -10°C…+85 °C

Humidity range

Dimensions (L x W x H)

Weight

10 … 95 % relative humidity (non-condensing)

70 x 30 x 21.5 mm approx. 35-40 g

CE Sign

Configuration software

Mounting/Installation According to comX Design-Guide

RoHS yes

CE Sign yes

Emission

Immunity

System configurator

EN55011:2009 Class A; CISPR 11. Class A

According to IEC/EN 61000-4:1995, see below

SYCON.net

Table 85: Technical Data COMX 100CA-RE




Important: All data specified here apply for the COMX 100CN-RE,

Revision 2.

COMX 100CN-RE



Processor


RAM/ FLASH 8 MB SDRAM, 4 MB SPI-Flash-EPROM




Type

16 KB

8/16 Bit




Diagnosis

Display


Environment

Device

CE Sign



Corresponding male connector

SAMTEC TFM - 125 - 02 - S - D – A or TFC - 125 -

02 - F - D – A



Determined by loaded firmware.: EtherCAT

Master/Slave, EtherNet/IP Scanner (Master)/

Adapter(Slave), Open Modbus/TCP, Powerlink

Controlled Node (Slave),PROFINET_IO-Controller

(Master)/ Device (Slave), Sercos Master/ Slave,

TCP/IP, VARAN Client (Slave)

Hardware 30 Pin SMT connector, female, Grid 1.27 mm, see

COMX Design Guide. Fitting to a RJ45-Module with

Transformer, LED and termination, such as ERNI

203313 or Pulse J0864D628ANL

Transmission rate

Interface Type

100 MBit/s, 10 MBit/s (depending on the loaded firmware)

100 BASE-TX, isolated, 10 BASE-T (depending on the loaded firmware)

Half duplex / full duplex supported (at 100 MBit/s)


Diagnostic interfaces/ signals

LED Display

UART (RXD, TXD), USB (RX0, TX0, USB+, USB-)

SYS System Status

COM0, COM1 Communication Status

TX/RX0, TX/RX1 Ethernet activity status

LINK0, LINK1 Ethernet link status


Typical current/ power at 3,3 V Approx. 700…750 mA / 2.5 W

Ambient temperature range Operation: -20°C...+60°C,



Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 86: Technical Data COMX 100CN-RE




COMX 100CA-CO



Processor



RAM/ FLASH



Type


16 KB

8/16 Bit


CANopen communication

CANopen

Diagnosis

Display

interface

Pin distance (Grid)

Supported communication standard

1.27 mm


02 - F - D – A

CANopen

Interface type

Connector

Potential-free ISO-11898-interface. According to

CANopen specification EN 50325/4.

DSub plug, male, 9-pin

Transmission rates


10 kBit/s, 20 kBit/s, 50 kBit/s, 100 kBit/s,


1 MBit/s



Environment


CAN Communication status ( green: STA, red: ERR)

+3.3 V ± 5 % DC Supply voltage

Typical current/ power at 3,3 V Approx. 450…480 mA / 1.5..1.6 W


Humidity range

Operation: -20°C...+65°C,




Device

CE Sign



Weight

Mounting/Installation

70 x 30 x 21.5 mm approx. 35-40 g

According to comX Design-Guide

RoHS yes

CE Sign yes

Emission EN55011:2009 Class A; CISPR 11. Class A

Immunity

System configurator


SYCON.net

Table 87: Technical Data COMX 100CA-CO

Important: The data mentioned under „Electrical Immunity to Interference

and Radio Frequency“

apply for the communication module COMX

100CA-CO, Revision 2. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



COMX 100CN-CO



Processor



RAM/ FLASH



Type


16 KB

8/16 Bit


CANopen communication

CANopen

interface

Pin distance (Grid)


1.27 mm


02 - F - D – A

CANopen

Interface type



Connector

Transmission rates

30 Pin SMT connector, female, pin grid 1.27 mm, see COMX Design Guide.



1 MBit/s

Diagnosis

Display


Environment

Device


LED Display


SYS System Status (green: RUN, yellow: RDY)

Supply voltage

CAN Communication status

+3.3 V ± 5 % DC

( green: STA, red: ERR)





Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g

CE Sign



RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 88: Technical Data COMX 100CN-CO

Important: The data mentioned under „Electrical Immunity to Interference

and Radio Frequency“

apply for the communication module COMX

100CN-CO, Revision 1. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



COMX 100CA-DN



Processor



RAM/ FLASH



Type


16 KB

8/16 Bit


Pin distance (Grid)

DeviceNet -Communication


1.27 mm


02 - F - D – A

DeviceNet

DeviceNet interface

Interface type Potential-free ISO-11898-interface according to

DeviceNet specification

CombiCon connector

, 5-pin

Diagnosis

Display

Connector

Transmission rate


LED Display

125 kBit/s, 250 kBit/s, 500 kBit/s,




Environment

Device

CE Sign


Supply voltage

MNS Module Network Status ( green: MS, red: NS)

+3.3 V ± 5 % DC



Humidity range






70 x 30 x 21.5 mm

Weight

Mounting/Installation approx. 35-40 g


RoHS yes

CE Sign

Emission

Immunity

System configurator yes



SYCON.net

Table 89: Technical Data COMX 100CA-DN

The data mentioned under „Electrical Immunity to Interference and Radio

Frequency“

apply for the communication module COMX 100CA-DN,

Revision 2. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



COMX 100CA-DN



Processor



RAM/ FLASH

Type

Pin distance (Grid)



1.27 mm



02 - F - D – A

Size of Dual-Port-Memory 16 KB


DeviceNet -Communication


Interface type

8/16 Bit

DeviceNet

Potential-free ISO-11898-interface according to


Diagnosis

Display


Environment

Device

CE Sign


Connector 30 Pin SMT connector, female, pin grid 1.27 mm, see COMX Design Guide.

125 kBit/s, 250 kBit/s, 500 kBit/s, Transmission rate


LED Display


SYS System Status

MNS Module Network Status

+3.3 V ± 5 % DC Supply voltage





Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 90: Technical Data COMX 100CN-DN


Frequency“

apply for the communication module COMX 100CN-DN,




COMX 100CA-DP



Processor



RAM/ FLASH



Type


16 KB

8/16 Bit


Pin distance (Grid)

PROFIBUS Communication

Supported Communication

Standard/Firmware

1.27 mm


02 - F - D – A

PROFIBUS DP

PROFIBUS Interface

Interface type

Connector

Potential free RS-485 Interface

DSub connector, female, 9-pin

Diagnosis

Display

Transmission rate

Auto-Detection yes

Diagnostic interfaces/ signals UART (RXD, TXD), USB (RX0, TX0, USB+, USB-)

LED Display

9,6 kBit/s, 19,2 kBit/s, 31,25 kBit/s, 45,45 kBit/s,

93,75 kBit/s, 187,5 kBit/s, 500 kBit/s,

1,5 MBit/s, 3 MBit/s, 6 MBit/s,12 MBit/s


COM Communication status

( green: STA, red:

ERR)


Environment

Device



Ambient temperature range Operation: -20C°... +70°C,



Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g

CE Sign



RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 91: Technical Data COMX 100CA-DP




COMX 100CN-DP



Processor



RAM/ FLASH



Type


16 KB

8/16 Bit


Pin distance (Grid)


Supported Communication

Standard/Firmware

1.27 mm


02 - F - D – A

PROFIBUS DP


Interface type

Connector


Transmission rate

30-pin SMT connector, female, grid distance 1.27 mm, see COMX Design Guide.




Diagnosis

Display

Auto-Detection yes


LED Display


SYS System Status

COM Communication Status


Environment

Device






Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g

CE Sign



RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 92: Technical Data COMX 100CN-DP


Frequency“

apply for the communication module COMX 100CN-DP,




COMX 50CA-REFO

Part number


Type




Optical Ethernet interface

RAM/ FLASH



1551.110 netX 50 Processor


16 KB

8/16 Bit

50 Pin SMT Connector, female Type



02 - F - D – A


PROFINET IO- Device (Slave)) Supported Real-Time Ethernet communication standard/ firmware

Hardware 2 x fiber optical transceivers Avago AFBR-5978Z with SC-RJ connector.

100 MBit/s

Diagnosis

Display

Transmission rate

Half duplex / full duplex

Conforms to AIDA standard


LED Display supported (at 100 MBit/s) yes



COM0, COM1 Communication Status (both green or red,)



Environment

Device



Typical current/ power at 3,3 V Approx 950. mA / 3,14 W (at 3,3 V)




Humidity range


Weight


70 x 30 x 21.5 mm approx. g

CE Sign



RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 93: Technical Data COMX 50CA-REFO




14.1.10 COMX 51CA-RE

COMX 51CA-RE

Part number


Type



SPI interface

RAM/ FLASH





16 KB

8/16 Bit

50 Pin SMT Connector, female Type



02 - F - D – A

SPI Mode SPI Slave, Mode 3



Diagnosis

Display

CPOL 1

CPHA 1



Hardware

Transmission rate

Determined by loaded firmware.: EtherCAT Slave,

EtherNet/ Adapter(Slave), Open Modbus/TCP,

PROFINET IO Device (Slave), Sercos Slave,

TCP/IP

2 * RJ45 socket, potential free

Interface Type

100 MBit/s, 10 MBit/s (depending on the firmware)

100 BASE-TX, isolated, 10 BASE-T (depending on the loaded firmware)

Half duplex / full duplex supported (at 100 MBit/s)



LED Display






Environment

Device

CE Sign




Maximum current/ power at 3,3 V 530…580 mA / max. 1.9 W


(Rev. 1)

Operation: 0°C...+65°C,



Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 94: Technical Data COMX 51CA-RE




14.1.11 COMX 51CN-RE

COMX 51CN-RE

Part number


Type


RAM/ FLASH

System interfaces

Parallel system interface

Type



Type

Pin distance (Grid)


1.27 mm


02 - F - D – A

SPI Mode SPI Slave, Mode 3

Serial system interface

(SPI interface)




Parallel or serial (SPI), via Dual Port Memory

16 KB

8/16 Bit, switchable


Diagnosis

Display



Determined by loaded firmware.: Determined by loaded firmware.: EtherCAT Slave, EtherNet/

Adapter(Slave), Open Modbus/TCP, PROFINET IO

Device (Slave), Sercos Slave

Hardware 30 Pin SMT connector, female, Grid 1.27 mm, see

COMX Design Guide.

100 MBit/s, 10 MBit/s (depending on the firmware) Transmission rate

Interface Type 100 BASE-TX, isolated, 10 BASE-T (depending on the loaded firmware)

(depending on the loaded firmware) Half duplex / full duplex


Type USB or serial

Serial diagnostic interface UART (RXD, TXD)

USB diagnostic interface

LED Display

USB (USB+, USB-)



ACT0, ACT1 Ethernet activity status (yellow)

Power supply /

Current consumption

Environment

Device

CE Sign


Supply voltage


+3.3 V ± 5 % DC

Maximum current/ power at 3,3 V 550…570 mA / max. 1.9 W


Humidity range






70 x 30 x 21.5 mm

Weight

Mounting/Installation approx. 22 g according to comX Design-Guide

RoHS yes

CE Sign

Emission

Immunity




SYCON.net

Table 95: Technical Data COMX 51CN-RE




14.1.12 COMX 10CA-CCS

Important: All data specified here apply for the COMX 10CA-CCS,

Revision 1.

COMX 10CA-CCS


Part number


Type


RAM/ FLASH



- /, 4 MB SPI-Flash-EPROM


16 KB (14 address lines), where 8 KB used by firmware (13 address lines, lowest 8 KB)

8/16 Bit (switchable)

CC-Link Communication

CC-Link Interface

Diagnosis

Display

Rotary Switch


Environment

Device

CE Sign


Type

Pin distance (Grid)


1.27 mm


02 - F - D – A


Interface type

CC-Link Version 2.0 and 1.1 according to CC-Link

Standard V.2.00 BAP-05025-J

Potential-free RS-485 interface

Connector 5-pole screw connector (RIACON Type 166)

Transmission rates 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10

MBit/s

UART (RXD, TXD), USB (RX0, TX0, USB+, USB-) Diagnostic interfaces/ signals

LED Display

Adjustment of Address and

Baudrate


L RUN/L ERR Communication Status

(green: L RUN, red: L ERR)

2 Rotary Switches for Address and 1 Rotary Switch for Baudrate


Typical current/ power at 3,3 V Approx. 225 mA / 0,75 W (at 3,3 V)

Ambient temperature range Operation: 0°C... +55°C,



Humidity range


Weight



70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign

Emission

Immunity




SYCON.net

Table 96: Technical Data COMX 10CA-CCS



Technical Data

14.1.13 COMX 10CN-CCS

170/212

Important: All data specified here apply for the COMX 10CN-CCS,

Revision 1.

COMX 10CN-CCS

Part number


Type



RAM/ FLASH - /, 4 MB SPI-Flash-EPROM


CC-Link Communication

CC-Link Interface

Diagnosis

Display

Rotary Switch

Size of Dual-Port-Memory 16 KB (14 address lines), where 8 KB used by firmware (13 address lines, lowest 8 KB)

8/16 Bit (switchable) Width for DPM data access

Type

Pin distance (Grid)


1.27 mm


02 - F - D – A


Interface type

Connector

CC-Link Version 2.0 and 1.1 according to CC-Link

Standard V.2.00 BAP-05025-J

Potential-free RS-485 interface

Transmission rates


LED Display


156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10

MBit/s



Baudrate


L RUN/L ERR Communication Status

(green: L RUN, red: L ERR)

2 Rotary Switches for Address and 1 Rotary Switch for Baudrate


Environment

Device

CE Sign




Ambient temperature range Operation: 0°C... +55°C,



Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 97: Technical Data COMX 10CN-CCS




14.1.14 COMX 10CA-COS

COMX 10CA-COS




CANopen

Communication

CANopen Interface

Diagnosis

Display

Rotary Switch


Environment

Device

CE Sign


Important: All data specified here apply for the COMX 10CA-COS,

Revision 2.

Part number

Type

RAM/ FLASH





8/16 Bit (switchable) Width for DPM data access

Type

Pin distance (Grid)


1.27 mm


02 - F - D – A


CANopen

Interface type

Connector



DSub plug, male, 9-pin

Transmission rates




1 MBit/s




Baudrate

Supply voltage

CAN Communication status ( green: STA, red: ERR)

2 Rotary Switches for Address

+3.3 V ± 5 % DC

Typical current/ power at 3,3 V Approx.. 250 mA / 0.825 W (at 3,3 V)


Humidity range






70 x 30 x 21.5 mm

Weight

Mounting/Installation approx. 35-40 g


RoHS yes

CE Sign

Emission

Immunity




SYCON.net

Table 98: Technical Data COMX 10CA-COS


Frequency“

apply for the communication module COMX 10CA-COS,




14.1.15 COMX 10CN-COS

Important: All data specified here apply for the COMX 10CN-COS,

Revision 1.

COMX 10CN-COS


Part number


Type


RAM/ FLASH







CANopen Communication

CANopen Interface

Diagnosis

Display

Rotary Switch


Environment

Device

CE Sign


Type

Pin distance (Grid)


02 - F - D – A


CANopen

Interface type Potential-free ISO-11898-interface. According to


Connector


1.27 mm

Transmission rates




1 MBit/s


LED Display


SYS System Status

(green: RUN, yellow: RDY)

CAN Communication status

(green: STA, red: ERR)


Baudrate

Supply voltage


+3.3 V ± 5 % DC





Humidity range 10 … 95 % relative humidity (non-condensing)


Weight

70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 99: Technical Data COMX 10CN-COS



Technical Data

14.1.16 COMX 10CA-DNS

173/212

Important: All data specified here apply for the COMX 10CA-DNS,

Revision 2.

COMX 10CA-DNS

Part number


Type



RAM/ FLASH - /, 4 MB SPI-Flash-EPROM


Rotary Switch


Environment

Size of Dual-Port-Memory 16 KB (14 address lines), where 8 KB used by firmware (13 address lines, lowest 8 KB)



1.27 mm


02 - F - D – A

DeviceNet

DeviceNet Communication


DeviceNet Interface



Connector

Transmission rates

CombiCon connector , 5-pin


Diagnosis

Display


Type

Pin distance (Grid)


LED Display




( green: MS, red: NS)

2 Rotary Switches for Address Adjustment of Address and

Baudrate






Humidity range 10 … 95 % relative humidity (non-condensing)

Device

CE Sign



Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes


Immunity

System configurator


SYCON.net

Table 100: Technical Data COMX 10CA-DNS


Frequency“

apply for the communication module COMX 10CA-DNS,




14.1.17 COMX 10CN-DNS

Important: All data specified here apply for the COMX 10CN-DNS,

Revision 1.

COMX 10CN-DNS


Part number


Type


RAM/ FLASH







Type

Pin distance (Grid)


02 - F - D – A

DeviceNet

DeviceNet Communication


DeviceNet Interface



Connector


1.27 mm



Diagnosis

Display

Transmission rates


LED Display



Rotary Switch


Environment

Device


Baudrate


( green: MS, red: NS)







Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g

CE Sign



RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 101: Technical Data COMX 10CN-DNS


Frequency“

apply for the communication module COMX 10CN-DNS,




14.1.18 COMX 10CA-DPS

Important: All data specified here apply for the COMX 10CA-DPS,

Revision 2.

COMX 10CA-DPS


Part number


Type


RAM/ FLASH







Type

Pin distance (Grid)


1.27 mm


02 - F - D – A

PROFIBUS DP




Interface type

Connector


DSub connector, female, 9-pin

Transmission rates 9,6 kBit/s, 19,2 kBit/s, 31,25 kBit/s, 45,45 kBit/s,



Auto-Detection yes

Diagnosis

Display

Rotary Switch


Environment

Device

CE Sign



LED Display



COM Communication status

( green: STA, red:

ERR)



Baudrate




Humidity range max- 1005 mA at bus short circuit






Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes


Immunity

System configurator


SYCON.net

Table 102: Technical Data COMX 10CA-DPS


Frequency“

apply for the communication module COMX 10CA-DPS,




14.1.19 COMX 10CN-DPS

Important: All data specified here apply for the COMX 10CN-DPS,

Revision 1.

COMX 10CN-DPS


Part number


Type


RAM/ FLASH







Type

Pin distance (Grid)


02 - F - D – A

PROFIBUS DP




Interface type Potential free RS-485 Interface

Connector


1.27 mm

Transmission rates





Diagnosis

Display

Rotary Switch


Environment

Auto-Detection yes


LED Display



COM Communication status ( green: STA, red:

ERR)

2 Rotary Switches for Address Adjustment of Address and

Baudrate


Typical current/ power at 3,3 V Approx. 200 mA / 0,66 W (at 3,3 V) max- 1005 mA at bus short circuit




Device

CE Sign


Humidity range


Weight


70 x 30 x 21.5 mm approx. 35-40 g


RoHS yes

CE Sign yes

Emission

Immunity

System configurator



SYCON.net

Table 103: Technical Data COMX 10CN-DPS




14.2 Electrical Immunity to Interference and Radio Frequency

Test Electrostatic discharge (ESD) according

to IEC/EN 61000-4-2:1995

Contact discharge method

Fast transient interferences

(Burst), according to IEC/EN 61000-4-

4:1995

Communication and data lines

Method

Module/Revision

Air discharge method

COMX 100CA-RE Rev. 3 8 kV Criterion B

COMX 100CN-RE Rev. 1 8 kV Criterion A

COMX 100CA-CO Rev.2 10 kV Criterion A

COMX 100CN-CO Rev.1 10 kV Criterion B

COMX 100CA-DN Rev.2 8 kV Criterion B

COMX 100CN-DN Rev.1 10 kV Criterion B

COMX 100CA-DP Rev.2 10 kV Criterion A

COMX 100CN-DP Rev.1 10 kV Criterion B

COMX 50CA-REFO Rev.1 10 kV Criterion B

COMX 51CA-RE Rev.1 8 kV Criterion A

COMX 51CN-RE Rev.1 8 kV Criterion A

COMX 10CA-CCS Rev.1 8 kV Criterion B

COMX 10CN-CCS Rev.1 8 kV Criterion B

COMX 10CA-COS Rev.1 10 kV Criterion B

COMX 10CN-COS Rev.1 10 kV Criterion B

COMX 10CA-DNS Rev.1 8 kV Criterion B

COMX 10CN-DNS Rev.1 10 kV Criterion B

COMX 10CA-DPS Rev.1 8 kV Criterion B

COMX 10CN- DPS Rev.1 10 kV Criterion B

4 kV Criterion B

4 kV Criterion B

6 kV Criterion A

6 kV Criterion B

4 kV Criterion B

6 kV Criterion B

6 kV Criterion A

6 kV Criterion B

6 kV Criterion B

6 kV Criterion B

6 kV Criterion A

6 kV Criterion B

6 kV Criterion B

6 kV Criterion B

6 kV Criterion B

4 kV Criterion B

6 kV Criterion B

6 kV Criterion B

6 kV Criterion B

2 kV Criterion B

2 kV Criterion B

2 kV Criterion A

2 kV Criterion A

2 kV Criterion B

2 kV Criterion B

2 kV Criterion A

2 kV Criterion A

2 kV Criterion B

2.2 kV Criterion B

2.2 kV Criterion B

2.5 kV Criterion B

2.5 kV Criterion B

2 kV Criterion B

2 kV Criterion B

2 kV Criterion B

2 kV Criterion B

2.2 kV Criterion B

2.5 kV Criterion A

Surge voltage, according to

IEC/EN 61000-4-

5:1995

Communication and data lines

1 kV Criterion A

1 kV Criterion B

1 kV Criterion A

1 kV Criterion A

0.6 kV Criterion B

0.5 kV Criterion B

1 kV Criterion A

1 kV Criterion A

-

1 kV Criterion A

1 kV Criterion A

1 kV Criterion A

1 kV Criterion A

1 kV Criterion A

1 kV Criterion A

0.5 kV Criterion B

1 kV Criterion A

1 kV Criterion B

1 kV Criterion A

Table 104: Electrical Immunity to Interference and Radio Frequency COMX Modules

The criteria are specified according to the definition given in

EN 61131-2:2007. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



14.3 Technical Data Evaluation Board COMXEB

COMXEB

Product

Power supply

Host interface

Operating elements

Parameter

Part number

Supply voltage (range)

Value

1530.000

24V DC ± 6V DC

Typical current/ power consumption at 24 V

Power adaptor

Depends mainly on used comX module

Type TPS54360

Connection via socket

Socket for power adaptor 2-pin

CombiCon, 3-pin Alternative power connector

Dual-port memory

SPM

SPM over USB

Connector 68-pin

Pin distance 0.635 mm

Pin header, 16-pin

Switches

USB, Type B, 5-pin

(currently not supported)

4 slide switches

Switching host-controlled/ boardcontrolled access

Switching DPM/SPM

Switching 8 bit/16 bit

Switching SPM over pin header or USB

Buttons Reset

Jumper fields for AIFX interface

2x, each 16-pin

For configuration

Jumper for boot mode 2-pin

LED display comX interface

Power supply

Communication status

Ethernet Link/Activity

Suited for

COMX-CA

Suited for

COMX-CN-Fieldbus

Suited for

COMX-CN-Real-time

Ethernet

PROFIBUS-DP interface

CANopen interface

Type

Connector

Type

+3.3 V: 1 LED green

5 V USB/FTDI Chip: 1 LED green

STA/ERR Duo-LED green / red

STA2/ERR2 Duo-LED green/ red

(not used)

STA_CG/ STA1_CR

Duo-LED green / red

STA0_CG/ STA0_CR

Duo-LED green / red

CH0_LINK (green)/CH0_ACT

(yellow )

CH1_LINK (green)/CH1_ACT

(yellow)

Connector 50-pin

Pin distance 1.27 mm (male)

Connector 50-pin


Connector 30-pin


Connector 50-pin


Connector 30-pin


RS-485, potential-free

Sub-D, 9-pin, female

ISO 11898 interface, potentialfree comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Technical Data


Connector

Type

179/212

Sub-D, 9-pin, male

ISO 11898 interface, potentialfree

RS-485, potential-free

CC-Link interface

Type


Diagnostic interface (for firmware download and configuration)

Extension interface

Type

Connector

UART

USB

100 BASE-TX, isolated

10 BASE-T (depending on loaded

Firmware)

2 x RJ45

9 pin D-Sub Plug RS232

Mini-USB-Socket Type B, 5-pin

Interfaces for power supply

Additional pin headers

Device

For AIFX Interface 10-pin

Connection for AIFX-DP, AIFX-

CO, AIFX-DN and AIFX-CC

Socket for power adaptor in scope of delivery

Socket for external power supply

2-pin

3-pin, green

SYNC/UART1 10-pin

16-pin Jumper fields(2x) for AIFX interface

Dimensions (L x B x H) 138 x 135 x 19 mm

(Height measured without comX, with plastic feet)

Weight

Operating temperature range

Approx. 153 g

Operation: -20C°... +70°C

Storage temperature range

Storage (device only):

-40°C…+85 °C

Storage (device in package):

-10°C…+85 °C

RoHS yes

Emission and immunity CE Sign no (see below)

Table 105: Technical Data Evaluation Board COMXEB

Important: The device is only designed for testing purposes and not intended for use in industrial production facilities. Therefore it does not have any CE sign. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



14.4 Technical Data of Communication Protocols

14.4.1 EtherCAT Master

Parameter

Maximum number of EtherCAT slaves

Maximum number of cyclic input data

Maximum number of cyclic output data

Minimum bus cycle time

Acyclic communication

Functions

Bus Scan

Description

Maximum 200 Slaves. The number of usable slaves depends on the available memory for the configuration file. See ‘configuration file’ below.

5760 bytes

5760 bytes

205 µs, depending on the used number of slaves and the used number of cyclic input data and output data. Recommended is a cycle time of 1 ms and higher.

CoE (CANopen over EtherCAT)

CoE-Upload, CoE-Download

Maximum 1500 bytes

Get OD List

Get object description

Get entry description

Emergency

Slave diagnostics

Supported

Distributed Clocks

Topology

Baud rate

Data transport layer

Configuration File (ethercat.xml or config.nxd)

Limitations

Reference to firmware/stack version

Supported, but not at the same time with Redundancy

Line or ring

100 MBit/s

Ethernet II, IEEE 802.3

COMX 10CA-RE, COMX 100CN-RE: Maximum 2 MByte

The size of the bus configuration file is limited by the size of the

RAM Disk (1 MByte) or FLASH disk (2 MByte).

All CoE Uploads, Downloads and information services must fit in one TLR-Packet. Fragmentation is not supported

Distributed Clock and Redundancy cannot be used at the same time.

V3.0.x.x

Table 106: Technical Data EtherCAT Master Protocol




14.4.2 EtherCAT Slave

Parameter Description

COMX 51XX-RE

Maximum number of cyclic input data 1024 bytes

Maximum number of cyclic output data 1024 bytes


Type

SDO

SDO Master-Slave

SDO Slave-Slave (depending on

Master capability)

Complex Slave

Description

COMX 100XX-RE

256* bytes

256* bytes

SDO

SDO Master-Slave

SDO Slave-Slave (depending on

Master capability)

Complex Slave

Functions Emergency Emergency

FMMUs 8 3

SYNC Manager

Distributed Clocks (DC)

4

Supported, 32 Bit

4

Supported, 32 Bit

Baud rate


Limitation


100 MBit/s


LRW is not supported

V4.2.x.x

100 MBit/s


LRW is not supported

V2.5.x.x and V4.2.x.x

Table 107: Technical Data EtherCAT Slave Protocol

Note for COMX 100XX-RE: * The loadable firmware supports for the number of cyclic input data and for cyclic output data in total up to 512 bytes. If more than 256 bytes for input data or for output data shall be exchanged via EtherCAT, then a customer specific XML file is necessary.

Additionally the following formula applies: The sum of the input data length and the ouput data length may not exceed 512 bytes, where each length has to be rounded up to the next multiple of 4 for this calculation. comX | Communication Modules for Real-Time-Ethernet and Fieldbus



14.4.3 EtherNet/IP Scanner (Master)

Parameter

Maximum number of EtherNet/IP connections

Maximum number of total cyclic input data

Maximum number of total cyclic output data



IO Connection type

Description

64 connections for implicit and explicit

5712 bytes

5760 bytes

504 bytes per slave per telegram

504 bytes per slave per telegram

Cyclic, minimum 1 ms (depending on used number of connections and used number of input and output data)

Maximum number of unscheduled data

UCMM, Class 3

Explicit Messages, Client and Server Services

Quick connect

Predefined standard objects

1400 bytes per telegram

Supported

Get_Attribute_Single/All

Set_Attribute_Single/All

Supported

Identity Object

Message Route Object

Assembly Object

Connection Manager

Ethernet Link Object

TCP/IP Object

DLR Object

QoS Object

20

Tree, Line, Ring

Maximal number of user specific objects

Topology

DLR (Device Level Ring)

ACD (Address Conflict Detection)

Beacon based ’Ring Node’

Supported

DHCP Supported

BOOTP Supported

Baud rates


Switch function

Limitations


10 and 100 MBit/s


Integrated

CIP Sync Services are not implemented

TAGs are not supported

V2.6.x.x

Table 108: Technical Data EtherNet/IP Scanner (Master) Protocol




14.4.4 EtherNet/IP Adapter (Slave)

Parameter

Maximum number of input data

Maximum number of output data

IO connection types (implicit)

IO Connection trigger types

Description

504 bytes

504 bytes

1 exclusive owner, 1 listen only, 1 input only

Cyclic, minimum 1 ms*

Application Triggered, minimum 1 ms*

Change Of State, minimum 1 ms*

* depending on number of connections and number of input and output data

Connected and unconnected

8, explicit and implicit connections

Supported

Supported

Explicit Messages

Maximum number of connections

Unconnected Message Manager (UCMM)

Quick connect

Predefined standard objects Identity Object

Message Route Object

Assembly Object

Connection Manager

DLR Object

QoS Object

TCP/IP Object

Ethernet Link Object

Reset services

Maximum number of user specific objects

DLR V2 (ring topology)

ACD (Address Conflict Detection)

Identity Object Reset Service of Type 0 and 1

20

Supported

Supported

DHCP Supported

BOOTP Supported

Baud rates 10 and 100 MBit/s

Duplex modes

MDI modes


Switch function

Limitations


Half duplex, Full duplex, Auto negotiation

MDI, MDI-X, Auto-MDIX


Integrated

CIP Sync Services are not implemented

TAGs are not supported

V2.7.x.x

Table 109: Technical Data EtherNet/IP Adapter (Slave) Protocol




Parameter

Maximum number of input data

Maximum number of output data


Modbus Function Codes

Protocol Mode

Baud rates



Description

2880 Registers

2880 Registers

Read/Write Register:

- Maximum 125 Registers per Read Telegram (FC 3, 4, 23),

- Maximum 121 Registers per Write Telegram (FC 23),

- Maximum 123 Registers per Write Telegram (FC 16)

Read/Write Coil:

- Maximum 2000 Coils per Read Telegram (FC 1, 2),

- Maximum 1968 Coils per Write Telegram (FC 15)

1,

2,

3,

4,

5,

6,

7,

15,

16,

23*

* Function Code 23 can be used via the packet API, but not with the Command Table.

Message Mode (Client Mode):

- Client (using the Command Table: The data is stored in the I/O process data image)

- Client (using the packet API: The I/O process data image is not used)

- Server (using the packet API: The I/O process data image is not used)

I/O Mode (Server Mode):

- Server (only) (The data is stored in the I/O process data image)

10 and 100 MBit/s


V2.5.x.x

Table 110: Technical Data Open Modbus/TCP Protocol

14.4.6 Powerlink Controlled Node/Slave

Parameter



Acyclic data transfer

Functions

Baud rate


Ethernet POWERLINK version

Limitation


Description

1490 bytes

1490 bytes

SDO Upload/Download

SDO over ASND and UDP

100 MBit/s, half-duplex


V 2

No slave to slave communication

V2.1.x.x

Table 111: Technical Data POWERLINK Controlled Node (Slave) Protocol




14.4.7 PROFINET IO-RT-Controller (Master)


Maximum number of PROFINET IO Devices 128

Maximum number of total cyclic input data 5712 bytes (including IOxS status bytes)

Maximum number of total cyclic output data 5760 bytes (including IOxS status bytes)



1440 bytes per device (= IOCR data length including IOxS status bytes)

1440 bytes per device (= IOCR data length including IOxS status bytes)


Alarm processing

Diagnostic data

Read/Write Record

Limited to 1392 bytes per telegram

Limited to 4096 bytes per request yes, but requires handling in host application program

One 200 byte buffer per IO device

DCP functions via API

Supported Protocols

Context management by CL-RPC

Minimum cycle time

Functions

Baud rate


Configuration file

Limitations

Name Assignment IO-Devices (DCP SET NameOfStation)

Set IO-Devices IP (DCP SET IP)

Signal IO-Device (DCP SET SIGNAL)

Reset IO-Device to factory settings (DCP Reset FactorySettings)

Bus scan (DCP IDENTIFY ALL)

RTC – Real Time Cyclic Protocol, Class 1

RTA – Real Time Acyclic Protocol

DCP – Discovery and configuration Protocol

CL-RPC – Connectionless Remote Procedure Call

Supported

1 ms

Different IO-Devices can be configured with different cycle times

Fast Startup of PROFINET IO Devices supported

100 MBit/s

Full-Duplex mode


Maximum 1 MByte

RT over UDP not supported

Multicast communication not supported

DHCP is not supported (neither for PROFINET IO-Controller nor for the IO-Devices)

Only one IOCR per IO Device

NameOfStation of IO Controller CANNOT be set using the DCP SET

NameOfStation service but only at start-up while configuring the IO

Controller

The buffer for IO-Device diagnosis data will be overwritten in case of multiple diagnostic events. Only one (the last) event is stored at the same time. If a single event produces more than 200 bytes of diagnosis data, only the first 200 bytes will be taken care of.

The usable (minimum) cycle time depends on the number of used IO

Devices, the number of used input and output data. The cycle-time, the number of configured IO Devices and the amount of IO data depend on each other. For example it is not possible due to performance reasons to have 128 IO Devices communication with cycle-time 1ms.

The size of the bus configuration file is limited by the size of the RAM

Disk (1 MByte)

WriteMultiple-Record service is not supported comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Technical Data

Parameter


Description

V2.6.x.x

Table 112: Technical Data PROFINET IO RT Controller

186/212

14.4.8 PROFINET IO Device (V3.4)

Parameter




Alarm Types

Supported protocols

Used Protocols (subset)

Topology recognition

VLAN- and priority tagging

Context Management by CL-RPC

Identification & Maintenance

Minimum cycle time

Baud rate


Limitations


Description

1024 bytes

1024 bytes

Read/Write Record, max. 1024 bytes per telegram

Process Alarm, Diagnostic Alarm, Return of SubModule Alarm

Plug Alarm (implicit), Pull Alarm (implicit)

RTC – Real Time Cyclic Protocol, Class 1 and 2 (unsynchronized), Class

3 (synchronized)




LLDP – Link Layer Discovery Protocol

SNMP – Simple Network Management Protocol

MRP – MRP Client

UDP, IP, ARP, ICMP (Ping)

LLDP, SNMP V1, MIB2, physical device yes

Supported

Read and write of I&M1-4

1 ms for RTC1 and RTC2

250 µs for RTC3

100 MBit/s




Only one device instance is supported

DHCP is not supported

IRT “flex” (synchronized RT Class 2) is not supported

FastStartUp is not supported.

Media Redundancy (except MRP client) is not supported

Access to the submodule granular status bytes (IOCS) is not supported.

The amount of configured IO-data influences the minimum cycle time that can be reached.

Supervisor-AR is not supported, Supervisor-DA-AR is supported

Only 1 Input-CR and 1 Output-CR are supported

Multiple WriteRequests are not supported

Using little endian (LSB-MSB) byte order for cyclic process data instead of default big endian (MSB-LSB) byte order may have an negative impact on minimum reachable cycle time

V3.4.x.x

Table 113: Technical Data PROFINET IO RT IRT Device Protocol




14.4.9 PROFINET IO Device (V3.5)

Parameter



Maximum number of submodules

Multiple Application Relations (AR)


Alarm types

Supported protocols

Topology recognition

Identification & Maintenance

Minimum cycle time

IRT Support

Media Redundancy

Additional features

Baud rate


PROFINET IO specification

Limitations

Description

1440 bytes

1440 bytes

255 submodules per Application Relation at the same time,

1000 submodules can be configured

The Stack can handle up to 2 IO-ARs, one Supervisor AR and one

Supervisor-DA AR at the same time

Read/Write Record, max. 1024 bytes per telegram

Process Alarm, Diagnostic Alarm, Return of SubModule Alarm,

Plug Alarm (implicit), Pull Alarm (implicit)

RTC – Real Time Cyclic Protocol class 1 (unsynchronized), class 3 (synchronized)




LLDP – Link Layer Discovery Protocol

SNMP – Simple Network Management Protocol

MRP – MRP Client

LLDP, SNMP V1, MIB2, physical device

Read and write of I&M1-4

1 ms for RT_CLASS_1

1 ms for RT_CLASS_3 (COMX 50XX-RE)

500 µs for RT_CLASS_3 (COMX 51XX-RE)

250 µs for RT_CLASS_3 (COMX 100XX-RE)

RT_CLASS_3

MRP client is supported

DCP, VLAN- and priority tagging, Shared Device

100 MBit/s


V2.2 (legacy startup) and

V2.3 (but advanced startup only for RT) are supported



Only one device instance is supported

DHCP is not supported

FastStartUp is not supported

The amount of configured IO-data influences the minimum cycle time that can be reached.

Only 1 Input-CR and 1 Output-CR are supported

Using little endian (LSB-MSB) byte order for cyclic process data instead of default big endian (MSB-LSB) byte order may have an negative impact on minimum reachable cycle time

System Redundancy (SR-AR) and Configuration-in-Run (CiR) are not supported

Max. 255 submodules can be used simultaneously within one specific

Application Relation

Advanced Startup according Profinet specification V2.3 is NOT yet supported for IRT

As there is no official certification available for Profinet IO specification

V2.3 at the time of release of the stack there is no guarantee that this implementation will pass such a certification once it is available comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Technical Data

Parameter


Description

V3.5.26.x

Table 114: Technical Data PROFINET IO RT IRT Device Protocol

14.4.10 Sercos-Master

Parameter



Maximum number of configured slave devices

Minimum cycle time


Description

5760 bytes (including Connection Control per Connection)

5760 bytes (including Connection Control per Connection)

511

250 µs

Service channel: Read/Write/Commands

188/212

Communication phases NRT, CP0, CP1, CP2, CP3, CP4

Topology Line and double ring

Redundancy supported

Hot-Plug supported

Cross Communication supported, but only if the master is configured by the host application program by packets.

Baud rate


100 MBit/s, full duplex


Auto crossover

Supported sercos version

TCP/IP stack

Limitation

Reference to firmware/stack version supported

Communication Specification Version 1.3 integrated

NRT channel not usable via the API.

V2.1.x.x

Table 115: Technical Data sercos Master Protocol




14.4.11 Sercos-Slave

Parameter

COMX 51XX-RE: Maximum number of cyclic input data

(Tx) of all slaves

COMX 51XX-RE: Maximum number of cyclic output data

(Rx) of all slaves

COMX 100XX-RE: Maximum number of cyclic input data

(Tx) of all slaves

COMX 100XX-RE: Maximum number of cyclic output data (Rx) of all slaves

Maximum number of slave devices

Maximum number of applicable sercos addresses

Minimum cycle time

Topology

Communication phases

Acyclic Communication (Service Channel)

Baud rate


Supported sercos version

Supported sercos Communication Profiles

Supported User SCP Profiles

Supported FSP profiles

Description

254 bytes (including Connection Control and IO Status)




8

1 … 511

250 µs

Line and ring

NRT, CP0, CP1, CP2, CP3, CP4

Read/Write/Standard Commands

100 MBit/s

Ethernet II, IEEE 802.3 sercos in the third generation

Communication Specification Version 1.1.2

SCP_FixCFG Version 1.1.1

SCP_VarCFG Version 1.1.1

SCP_VarCFG Version 1.1.3

SCP_WD Version 1.1.1

SCP_Diag Version 1.1.1

SCP_RTB Version 1.1.1

SCP_Mux Version 1.1.1

SCP_Sig Version 1.1.1

SCP_ExtMuX Version 1.1.2

SCP_RTBListProd Version 1.3

SCP_RTBListCons Version 1.3

SCP_RTBWordProd Version 1.3

SCP_RTBWordCons Version 1.3

SCP_OvSBasic Version 1.3

SCP_WDCon Version 1.3

FSP_IO

FSP_Drive

SCP Sync Supported

S/IP Supported

Identification LED Supported

Storage location of object dictionary

Limitations

Reference to firmware/stack version mixed mode

Max. 2 connections: 1 for consumer and 1 for producer

Modifications of the Service-Channel Object Dictionary will be volatile after reset (if it resides on device)

Hot plug is not supported yet

Cross communication not supported yet

NRT Channel only forwarding

V3.1.x.x

Table 116: Technical Data sercos Slave Protocol



Technical Data

14.4.12 VARAN Client

Parameter



Memory Area

Description

128 bytes

128 bytes

Read Memory Area 1,

Write Memory Area 1

190/212

Memory Write

Integrated 2 port splitter for daisy chain topology Supported

Baud rate 100 MBit/s


VARAN protocol version

Limitations



1.1.1.0

Integrated EMAC for IP data exchange with client application not supported

SPI single commands (optional feature) not supported

Memory area 2 is not supported.

V1.0.x.x

Table 117: Technical Data VARAN Client Protocol




14.4.13 CANopen Master

Parameter

Maximum number of CANopen nodes



Maximum number of receive PDOs

Maximum number of transmit PDOs

Exchange of process data


Functions

Baud rates

CAN layer 2 access


CAN Frame type for CANopen

Reference to version

Description

126

3584 bytes

3584 bytes

512

512

Via PDO transfer:

- synchronized,

- remotely requested and

- event driven (change of date)

SDO Upload/Download, max. 512 bytes per request

Emergency message (consumer and producer)

Node guarding / life guarding, heartbeat

PDO mapping

NMT Master

SYNC protocol (producer)

Simple boot-up process, reading object 1000H for identification

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s

Send/receive via API supported (11 bit/29 bit)

CAN Frames

11 Bit

V2.11.x.x

Table 118: Technical Data CANopen Master Protocol



Technical Data

14.4.14 CANopen Slave

192/212

14.4.14.1 CANopen Slave COMX 100

Parameter







Functions

Baud rates

CAN layer 2 access




Description

512 bytes

512 bytes

64

64

Via PDO transfer

- synchronized,


- event driven (change of date, event timer)

On request of the host application program by packet

SDO upload/download (server only)

Emergency message (producer)

Timestamp (producer/consumer)

Node guarding / life guarding

Heartbeat: 1 producer, max. 64 consumer

PDO mapping

NMT Slave

SYNC protocol (consumer)

Error behaviour (configurable):

- in state operational: change to state pre-operational

- in any state: no state change

- in state operational or pre-operational: change to state stopped

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s

Auto baudrate detection is supported


CAN Frames

11 Bit

V3.6.x.x

Table 119: Technical Data CANopen Slave Protocol




14.4.14.2 CANopen Slave COMX 10

Parameter







Functions

Baud rates

CAN layer 2 access




Description

64 bytes

64 bytes

8

8

Via PDO transfer

- synchronized,


- event driven (change of date, event timer)

On request of the host application program by packet

SDO upload/download (server only)

Emergency message (producer)

Timestamp (producer/consumer)

Node guarding / life guarding

Heartbeat: 1 producer, max. 4 consumer

PDO mapping

NMT Slave

SYNC protocol (consumer)

Error behaviour (configurable):

- in state operational: change to state pre-operational

- in any state: no state change

- in state operational or pre-operational: change to state stopped

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s



CAN Frames

11 Bit

V3.6.x.x

Table 120: Technical Data CANopen Slave Protocol



Technical Data

14.4.15 CC-Link Slave


Firmware works according to CC-Link Version 2.0:

Station Types

Maximum input data

Maximum output data

Remote Device Station (up to 4 occupied stations)

368 bytes

368 bytes

Input data remote device station

Output data remote device station

Extension cycles

Baud rates

112 bytes (RY) and 256 bytes (RWw)

112 bytes (RX) and 256 bytes (RWr)

1, 2, 4, 8

156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s

Limitation Intelligent Device Station not supported

Firmware works according to CC-Link Version 1.11:

Station Types Remote I/O station,

Remote device station’ (up to 4 occupied stations)

Maximum input data

Maximum output data

48 bytes

48 bytes

Input data remote I/O station

Output data remote I/O station

Input data remote device station

Output data remote device station

Baud rates

Firmware


4 bytes (RY)

4 bytes (RX)

4 bytes (RY) and 8 bytes (RWw) per occupied station

4 bytes (RX) and 8 bytes (RWr) per occupied station

156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s

V2.9.x.x

Table 121: Technical Data CC-Link-Slave Protocol



Technical Data

14.4.16 DeviceNet Master

Parameter

Maximum number of DeviceNet slaves





Maximum Configuration data


Description

63

3584 bytes

3584 bytes

255 bytes/connection

255 bytes/connection

1000 bytes/slave

Explicit connection

All service codes are supported

Change of State

Cyclic

Poll

Explicit Peer-to-Peer Messaging

Fragmentation Explicit and I/O

UCMM Supported

Objects Identity Object (Class Code 0x01)

Message Router Object (Class Code 0x02)

DeviceNet Object (Class Code 0x03)

Baud rates


Connection Object (Class Code 0x05)

Acknowledge Handler Object (Class Code 0x06)

125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

Reference to firmware/stack version V2.3.x.x

Table 122: Technical Data DeviceNet Master Protocol



Technical Data

14.4.17 DeviceNet Slave

Parameter


Description

255 bytes



255 bytes

Get_Attribute_Single/All

Max. 240 bytes per request

Set_Attribute_Single/All

Max. 240 bytes per request

Connections Poll

Change-of-state

Cyclic

Bit-strobe

Explicit messaging

Fragmentation

Supported

Explicit and I/O

Baud rates



125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

V2.3.x.x

Table 123: Technical Data DeviceNet Slave Protocol




14.4.18 PROFIBUS DP Master

Parameter

Maximum number of PROFIBUS DP slaves





Configuration data

Parameterization data per slave


Maximum number of acyclic read/write

Functions

Description

125 (DPV0/DPV1)

5712 bytes

5760 bytes

244 bytes per slave

244 bytes per slave

Max. 244 bytes per slave

7 bytes standard parameter per slave

Max. 237 bytes application specific parameters per slave

DPV1 class 1 read, write

DPV1 class 1 alarm

DPV1 class 2 initiate, read, write, data transport, abort

240 bytes per slave and telegram

Configuration in Run (CiR), requires host application program support

Timestamp (Master functionality)

Baud rate


Limitations


9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s

Auto baud rate detection is not supported

PROFIBUS FDL

DPV2 isochronous mode and slave slave communication are not supported.

The redundancy function can not be used, if the master is configured by the host application program by packets.

V2.6.x.x

Table 124: Technical Data PROFIBUS DP Master Protocol




14.4.19 PROFIBUS DP Slave

Parameter



Maximum number of acyclic data (read/write)

Maximum number of modules

Configuration data

Parameter data


Baud rate


Limitations


Description

244 bytes

244 bytes

240 bytes/telegram

24

Max. 244 bytes

237 bytes application specific parameters

DP V1 Class 1 Read/Write

DP V1 Class 1 Alarm

DP V1 Class 2 Read/Write/Data Transport

9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s


PROFIBUS FDL

SSCY1S – Slave to slave communication state machine not implemented

Data exchange broadcast not implemented

I&M LR services other than Call-REQ/RES are not supported yet

V2.7.x.x

Table 125: Technical Data PROFIBUS DP Slave Protocol




14.4.20 PROFIBUS MPI

Parameter

Maximum number of MPI connections

Maximum number of write data

Maximum number of read data

Functions

Baud rate



Description

126

216 bytes

222 bytes

MPI Read/Write DB (data block), M (marker), Q (output), C

(Counter), T (Timer)

MPI Read I (Input)

Data type bit to access to DB (data block), M (marker), Q

(output) and I (Input, read only)

MPI Connect (automatically when first read/write function is used)

MPI Disconnect, MPI Disconnect All

MPI Get OP Status

MPI transparent (expert use only)

Fixed values ranging from 9,6 kBits/s to 12 MBit/s

Auto-detection mode is supported

PROFIBUS FDL

2.4.x.x

Table 126: Technical Data PROFIBUS-MPI Protocol



Decommissioning , Replacement and Disposal

15 Decommissioning, Replacement and Disposal

200/212

15.1 Put the Device out of Operation

For the deinstallation of the comX communication module from the device into which the comX module had been integrated (also called “host system” or “target environment”), proceed as follows:



• Strictly obey to all safety rules given in the documentation supplied by the manufacturers of this device.!

• Therefore first disconnect the power plug of the device into which the comX module had been integrated.

• Make sure, that this device is separated from the supply voltage and free of current, before you continue.

Consequences of Removal of Device

In order to avoid personal and material damage do not remove this device from a production line without having ensured a secure operation of the production line during and after the removal of the device.

Now you are ready to either remove or replace the comX communication module.

!

Step 1: If necessary, remove the housing of this device. In all cases, strictly adhere to all rules given in the manuals of this device.

!

Step 2: Definitely avoid touching open contacts or ends of wires.

!

Step 3: Disconnect the communication cables from the device.

!

Step 4: Remove the comX communication module carefully from its connector (50 pin SMT connector, male, grid width 1.27 mm, at COMX-

CN additionally 30 pin SMT connector, male, grid width 1.27 mm) onto which it had been plugged during mounting.

!

Step 5: If the comX communication module needs be replaced by another one, then replace it and reconnect the communication cables to the device.

!

Step 6: If you had opened the housing of the device in step 1, then close it now. Again strictly adhere to all rules given in the manuals of this device anyway.

!

Step 7: Connect the device with its supply voltage and switch it on again. Adhere of the commissioning rules of the supplier of the device.

Check, whether the device behaves normally.

Obey to the subsequent disposal rules. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Decommissioning , Replacement and Disposal

15.2 Disposal of Waste Electronic Equipment

201/212

According to the European Directive 2002/96/EG “Waste Electrical and

Electronic Equipment (WEEE)”, waste electronic equipment may not be disposed of as household waste. As a consumer, you are legally obliged to dispose of all waste electronic equipment according to national and local regulations.

Waste Electronic Equipment

$ This product must not be treated as household waste.

$

This product must be disposed of at a designated waste electronic equipment collecting point. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Glossary

16 Glossary

202/212

AIDA

Automatisierungs-Initiative deutscher Automobilhersteller

AIDA is a joined initiative of the German automotive industry founded by

Audi, BMW, Daimler-Chrysler and Volkswagen. AIDA conforming products are based on PROFINET.

Auto-Crossover

Auto-Crossover is a feature of an interface: An interface with Auto-

Crossover capability will automatically detect and correct if the data lines have been exchanged vice versa.

Auto-Negotiation

Auto-Negotiation is a feature of an interface: An interface with Auto-

Negotiation will automatically determine a set of correct communication parameters.

Baud rate

Data transmission speed of a communication channel or interface.

CRC

Cyclic Redundancy Check

A mathematic procedure for calculating checksums based on polynomial division in order to detect data transmission errors. For a more detailed description see the Wikipedia article

( http://en.wikipedia.org/wiki/Cyclic_redundancy_check ).

DDF

Device_Description_File .

Device Description File

A file containing configuration information about a device being a part of a network that can be read out by masters for system configuration. Device

Description Files use various formats which depend on the communication system. Often these formats are based on XML such as EDS_file s or

GSDML_file s. Contains configuration information

EDS file

A special kind of Device Description File used by Ethernet.

EtherCAT

A communication system for industrial Ethernet designed and developed by

Beckhoff Automation GmbH.

Ethernet

A networking technology used both for office and industrial communication via electrical or optical connections. It has been developed and specified by the Intel, DEC and XEROX. It provides data transmission with collision control and allows various protocols. As Ethernet is not necessarily capable comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Glossary

EtherNet/IP

Ethernet Powerlink


B&R. It partly uses CANopen technologies.

Full duplex


Rockwell. It partly uses the CIP (Common Industrial Protocol).

Full duplex denominates a telecommunication system between two communication partners which allows simultaneous communication in both directions is called a full-duplex telecommunication system. At such a system, it is possible to transmit data even if currently data are received.

Full-duplex is the opposite of Half_duplex .

Function code

203/212 for real-time application, various real-time extensions have been developed, see Real-Time Ethernet .

A function code (in the meaning defined by Modbus terminology) is a standardized method to access (i.e. read or write) coils or registers via

Modbus.

GSD file

A special kind of Device Description File used by PROFIBUS (GSD =

General Station Description).

GSDML file

A special kind of XML-based Device Description File used by PROFINET .

(GSDML = General Station Description Markup Language).

Half duplex

Half duplex denominates a telecommunication system between two communication partners which does not allow simultaneous, but alternating, communication in both directions is called a half-duplex telecommunication system. At such a system, receiving data inhibits the transmission of data. Half-duplex is the opposite of _Full_duplex .

Hub

A network component connecting multiple communication partners with each other. A hub does not provide own intelligence, thus it does not

Industrial Ethernet

See Real-Time Ethernet

netX

networX on chip, next generation of communication controllers.

Object Dictionary

An object dictionary is a storage area for device parameter data structures.

It is accessed in standardized manner. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Glossary

Open Modbus/TCP

204/212

A communication system for Industrial Ethernet designed and developed by

Schneider Automation and maintained by the Modbus-IDA organization based on the Modbus protocols for serial communication.

PROFINET


PROFIBUS International. It uses some mechanisms similar to those of the

PROFIBUS field bus.


Real-Time Ethernet (Industrial Ethernet) is an extension of the Ethernet networking technology for industrial purposes with very good Real-Time features and performance. There is a variety of different Real-Time

Ethernet systems on the market which are incompatible with each other.

The most important systems of these are

• EtherCAT

• EtherNet/IP

• Ethernet Powerlink

• Open Modbus/TCP

• PROFINET

• Sercos

• VARAN

Register

A register (in the meaning defined by Modbus terminology) is a 16-bit wide storage area for data which can be accessed and addressed as a unit by some of the Modbus Function Codes.

RJ45

A connector type often used for Ethernet connection. It has been standardized by the Federal Communications Commission of the USA

(FCC).

RoHS

Restriction of Hazardous Substances

This abbreviation denominates the directive of the European Union on the use of 6 hazardous substances in electronic products. It is titled “Directive

on the restriction of the use of certain hazardous substances in electrical and electronic equipment 2002/95/EC”,

adopted in 2003 and was getting effective on 1 July 2006.

RS232

An interfacing standard for serial communication on data lines defined by

EIA (Electronic Industries Alliance) in ANSI/EIA/TIA-232-F-1997.

RS485

An interfacing standard for differential serial communication on data lines defined by EIA (Electronic Industries Alliance) in ANSI/TIA/EIA-485-A-1998 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Glossary

Sercos

Switch

UART

VARAN

XDD file

XML

205/212


Bosch-Rexroth GmbH and supported by Sercos International.

A network component connecting multiple communication partners (or even entire branches of a network) with each other. A switch is an intelligent network component which analyzes network traffic in order to decide on its own. For the connected communication partners a switch behaves transparently.

UART means Universal Asynchronous Receiver Transmitter. It is a special kind of electronic circuit which is used for transmitting data serially with a fixed frame consisting of one start bit, five to nine data bits, an optional parity bit for the detection of transmission errors and one stop bit. Working asynchronously, it does not use an explicit clock signal.

Versatile Automation Random Access Network

A communication system for industrial Ethernet designed and developed by the Austrian automation company SIGMATEK.

A special kind of Device Description file used by Ethernet Powerlink

XML means Extended Markup Language. It is a symbolic language for structuring data systematically. XML is standard maintained by the W3C

(World-wide web consortium). Device Description Files often use XMLbased formats for storing the device-related data appropriately. comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Appendix

17 Appendix

206/212

17.1 Matrix Label

A matrix label is glued on the device. It contains 3 items:

1. Part number

2. Hardware Revision

3. Serial number

The figure shows part number 1250.100, hardware revision 3 and serial number 23456.

Part number

Hardware Revision

Serial number

Figure 54: Matrix Label

17.2 Wiring Instructions for Fieldbus Systems

You can find detailed instructions for wiring of Fieldbus Systems such as

CANopen. CC-Link, DeviceNet and PROFIBUS-DP, for instance concerning termination and requirements on the cables, within a separate manual „Wiring Instructions“ (Hilscher-document DOC120208UM01EN).

17.3 EtherNet/IP Adapter/Slave – Instance ID of I/O Data

I/O Data

Consumed I/O Data

Produced I/O Data

Instance ID Remark

100 I/O Data: EtherNet/IP Scanner/Master %

EtherNet/IP Adapter/Slave.

101 I/O Data: EtherNet/IP Adapter/Slave %

EtherNet/IP Scanner/Master.

Table 127: EtherNet/IP Adapter/Slave – Instance ID of I/O Data



Appendix 207/212

17.4 Use of VARAN Client

In order to use the comX communication module with VARAN, you need a license which you can acquire at the VNO (VARAN Bus-

Nutzerorganisation,

Bürmooser Straße 10, A-5112 Lamprechtshausen, [email protected]

) after getting a member of VON.

The license as well as the Vendor ID and the Device ID can be adjusted with the SYCON.net configuration software or with the netX Configuration

Tool.

17.5 Failure in 10 MBit/s Half Duplex Mode and Workaround

Important: The failure described here only affects older COMX 100CA-

RE modules with serial numbers up to 21557 and COMX 100CN-RE with serial numbers up to

20529

.

Affected Hardware

Hardware with the communication controller netX 50, netX 100 or netX 500; netX/Internal PHYs.

When can this Failure occur?

When using standard Ethernet communication with 10 MBit/s half duplex mode, the

PHY gets stuck in case of network collisions. Then no further network communication is possible. Only device power cycling allows Ethernet communication again.

This problem can only occur with Ethernet TCP/UDP IP, EtherNet/IP or Modbus

TCP protocols when using hubs at 10 MBit/s. The issue described above is not applicable for protocols which use 100 MBit/s or full duplex mode.

Solution / Workaround:

Do not use 10 MBit/s-only hubs. Use either switches or 10/100 MBit/s Dual Speed hubs, to make sure the netX Ethernet ports are connected with 100 MBit/s or in full duplex mode.

This erratum is fixed with all components of the ‘Y’ charge (9 digit charge number shows ‘Y’ at position 5 (nnnnYnnnn).

Reference

“Summary of 10BT problem on EthernetPHY”,

RenesasElectronics Europe, April 27,

2010 comX | Communication Modules for Real-Time-Ethernet and Fieldbus


Appendix 208/212

17.6 List of Figures

Figure 1: Block Diagram of Real-Time Ethernet Module

Figure 2: Block Diagram of a Fieldbus Module

Figure 3: Photo of Communication Module COMX 100CA-RE with Cooler

Figure 4: Pinning of Ethernet Interface of COMX 100CA-RE

Figure 5: Photo of Communication Module COMX 100CN-RE

Figure 6: Photo COMX 50CA-REFO

Figure 7: Photo of Communication Module COMX51CA-RE with Cooler

Figure 8: Photo of Communication Module COMX 51CN-RE

Figure 9: Photo of Communication Module COMX100 CA-CO

Figure 10: CANopen-Interface (D-Sub-plug, 9-pin) of the COMX 100CA-CO

Figure 11: Pinning of CANopen Interface of the COMX 100CA-CO

Figure 12: Photo of Communication Module COMX100 CN-CO

Figure 13: Photo of Communication Module COMX 100CA-DN

Figure 14: DeviceNet Interface (CombiCon-Plug, 5 pin) of the COMX 100CA-DN

Figure 15: Photo of Communication Module COMX 100CN-DN

Figure 16: Photo of Communication Module COMX 100CA-DP

Figure 17: PROFIBUS-DP-Interface(D-Sub plug, female, 9 pin) of the COMX 100CA-DP

Figure 18: Photo of Communication Module COMX 100CN-DP

Figure 19: Photo of Communication Module COMX 10CA-CCS

Figure 20: CC-Link Interface (Screw terminal connector, 5 pin)

Figure 21: Photo of Communication Module COMX 10CN-CCS

Figure 22: Photo of Communication Module COMX10 CA-COS

Figure 23: CANopen-Interface (D-Sub-plug, 9-pin) of the COMX 10CA-COS

Figure 24: Pinning of CANopen Interface of the COMX 10CA-COS

Figure 25: Photo of Communication Module COMX 10CN-COS

Figure 26: Photo of Communication Module COMX 10CA-DNS

Figure 27: DeviceNet Interface (CombiCon- Pug, 5 pin) of the COMX 10CA-DNS

Figure 28: Photo of Communication Module COMX 10CN-DNS

Figure 29: Photo of Communication Module COMX 10CA-DPS

Figure 30: PROFIBUS-DP-Interface (D-Sub plug, female, 9 pin) of the COMX 10CA-DPS

Figure 31: Photo of Communication Module COMX 10CN-DPS

Figure 32: COMXEB

Figure 33:Jumper settings for using X409 as PROFIBUS interface

Figure 34: Jumper settings for using X409 as CANopen/ DeviceNet interface

Figure 35: Jumper settings for using X409 as CC-Link interface

Figure 36: Jumper settings for using X409 without AIFX

Figure 37: Pin assignment power supply socket X932

Figure 38: Barrel connector of the power adaptor

Figure 39: SPI-master-slave-connection

Figure 40: Pin assignment of diagnostic interface connector X601

Figure 41: Pin assignment of Mini-B USB socket X611 (5-pin)

Figure 42: Connection COMXEB <=> NXPCA-PCI ( <=> Host) via parallel Dual-Port Memory

Figure 43: Serial host connection via X709

Figure 44: Serial host connection via the USB connector X829

Figure 45: Set-up A1: Updating the Firmware with SYCON.net via the USB-Interface

Figure 46: Set-up A2: Updating the Firmware with SYCON.net via the Serial Interface

Figure 47: Set-up B1: Firmware update with SYCON.net via the serial interface using evaluation board

COMXEB

Figure 48: Set-up B2: Firmware update with SYCON.net via the USB interface using evaluation board

COMXEB

81

82

83

85

76

77

78

79

73

74

75

75

69

70

71

72

65

66

67

68

62

63

63

64

56

57

59

61

31

31

54

55

107

114

115

116

141

142

92

92

95

107

90

90

90

91

143



Appendix 209/212

Figure 49: Set-up B3: Firmware update with SYCON.net via the NXPCA-PCI and DPM interface using evaluation board COMXEB

Figure 50: Set-up B4: Updating the Firmware with SYCON.net via SPM over USB

Figure 51: Selection of netX Driver

Figure 52: Starting the Search Process for Devices and Selection of Device

Figure 53: Firmware Download with SYCON.net (after Selection of the Firmware)

Figure 54: Matrix Label

145

146

148

149

150

206

17.7 List of Tables

Table 1: Reference to Hardware

Table 2: Reference to Software

Table 3: Reference to Firmware

Table 4: Reference to old Firmware still available for Legacy Applications

Table 5: Device Description Files comX Modules Real-Time Ethernet (Slave)

Table 6:Device Description Files comX Modules Fieldbus (Slave)

Table 7: Device Description Files comX Modules Real-Time Ethernet (Master)

14

15

15

Table 8: PROFINET IO-Device Firmware Version 3.4 and 3.5, Header, GSDML and Protocol API Manual 18

Table 9: EtherCAT-Slave Firmware Version 2.5 and 4.2, Header, XML and Protocol API Manual

Table 10: Safety Symbols and Sort of Warning or Principle

Table 11: Signal Words

Table 12: Supply Voltage and Signaling Voltage for comX Communication Modules

19

29

29

35

Table 13: Steps for the Hardware Installation of a comX Communication Module (Master und Slave)

Table 14: Configuration Steps for the comX Communication Module (Slave)

Table 15: Configuration Steps for the comX Communication Module (Master)

Table 16: Notes for the Configuration of the Master Device

11

11

12

13

38

40

41

43

Table 17: Device Names in SYCON.net by Communication Protocol

Table 18: Steps how to replace the comX Communication modules (Master and Slave)

Table 19: Firmware and Configuration Download Steps comX Communication modules (Slave) at Module

Exchange (Replacement Case)

45

46

47

Table 20: Steps Firmware and Configuration Download Steps comX Communication modules (Master) at

Module Exchange (Replacement Case)

Table 21: Pinning of Ethernet Connector at Channel 0 and Channel 1

Table 22: Pinning of the DeviceNet-Interface of the COMX 100CA-DN

48

55

66

69 Table 23: Pinning of the PROFIBUS-DP Interface of the COMX 100CA-DP

Table 24: CC-Link -Interface of COMX 10CA-CCS

Table 25: Pinning of the DeviceNet-Interface of the COMX 10CA-DNS

Table 26: Pinning of the PROFIBUS-DP Interface of the COMX 10CA-DPS

72

78

82

86 Table 27: Legend to Figure 32

Table 28: Assignment of comX modules to the sockets on the COMXEB:

Table 29: Pin assignment of external power supply connector X930

Table 30: Pin assignment Host interface X350

87

92

94

95 Table 31: Pin assignment of pin header X709

Table 32: Settings for selecting the host interface in mode Board controlled

Table 33: Settings for selecting the host interface in mode Host controlled

Table 34: Pin assignment comX-interface X300

96

96

98

100 Table 35: Pin assignment comX-interface X400




101

103

104

105 Table 39: Pin assignment of the PROFIBUS-DP interface of COMXEB

Table 40: Pin assignment of the CANopen interface of COMXEB

Table 41: Pin assignment of the DeviceNet interface of COMXEB

Table 42: Pin assignment of the CC-Link interface X405 of the COMXEB

105

105



Appendix 210/212

Table 43: Pin assignment of Ethernet connector at channel 0 (channel 1 accordingly)

Table 44: Pin assignment of interface X409

Table 45: Pin assignment of pin header X351

Table 46: Meaning of the SYNC sgnals for each protocol

Table 47: Power LEDs of COMXEB

Table 48: Communication Status LEDs of COMXEB

Table 49: Ethernet Link/Activity–LEDs

Table 50: Accessories for the Evaluation Board COMXEB

Table 51: System LED

Table 52: LEDs PROFIBUS DP Master

Table 53: LEDs PROFIBUS DP Slave

Table 54: LEDs PROFIBUS MPI

Table 55: LEDs CC-Link Slave

Table 56: LEDs CANopen Master

Table 57: LED State Definition for CANopen Master for the CAN LED

Table 58: LEDs CANopen Slave – 1 Communication Status LED (current Hardware Revision)

Table 59: LED State Definition for CANopen Slave for the CAN LED

Table 60: LEDs DeviceNet Master

Table 61: LED State Definition for DeviceNet Master for the MNS LED

Table 62: LEDs DeviceNet Slave

Table 63: LED State Definition for DeviceNet Slave for the MNS LED

Table 64: LED Names of individual Real-Time Ethernet Systems

Table 65: LEDs EtherCAT Master

Table 66: LED State Definition for EtherCAT Master for the RUN and ERR LEDs

Table 67: LEDs EtherCAT Slave

Table 68: LED State Definition for EtherCAT Slave for the RUN and ERR LEDs

Table 69: LEDs EtherNet/IP Scanner (Master)

Table 70: LEDs EtherNet/IP Adapter (Slave)

Table 71: LEDs Open Modbus/TCP

Table 72: LEDs Powerlink Controlled Node/Slave

Table 73: LED State Definition for Powerlink Controlled Node/Slave for the BS/BE LEDs

Table 74: LEDs PROFINET IO-RT Controller

Table 75: LEDs PROFINET IO-RT-Device

Table 76: LEDs Sercos Master

Table 77: LED State Definition for Sercos Master for the STA and ERR LEDs

Table 78: LEDs sercos Slave

Table 79: LED State Definition for sercos Slave for the S3 LED

Table 80: LEDs VARAN Client

Table 81: LED State Definition for VARAN Client for the RUN and ERR LEDs

Table 82: Possible Causes of Errors, their Consequences and necessary Actions for their Removal at

Firmware Update with SYCON.net

Table 83: Firmware Versions with Support for Diagnostic Interface

Table 84: First Hardware Version with new USB Interface

Table 85: Technical Data COMX 100CA-RE

Table 86: Technical Data COMX 100CN-RE

Table 87: Technical Data COMX 100CA-CO

Table 88: Technical Data COMX 100CN-CO

Table 89: Technical Data COMX 100CA-DN

Table 90: Technical Data COMX 100CN-DN

Table 91: Technical Data COMX 100CA-DP

Table 92: Technical Data COMX 100CN-DP

Table 93: Technical Data COMX 50CA-REFO

Table 94: Technical Data COMX 51CA-RE

155

156

157

158

159

160

161

162

163

164

165

166

167

128

129

130

131

132

132

133

134

122

123

123

124

125

125

126

127

135

137

137

138

138

118

119

119

120

120

121

121

122

106

108

109

109

110

110

111

111

117



Appendix

Table 95: Technical Data COMX 51CN-RE

Table 96: Technical Data COMX 10CA-CCS

Table 97: Technical Data COMX 10CN-CCS

Table 98: Technical Data COMX 10CA-COS

Table 99: Technical Data COMX 10CN-COS

Table 100: Technical Data COMX 10CA-DNS

Table 101: Technical Data COMX 10CN-DNS

Table 102: Technical Data COMX 10CA-DPS

Table 103: Technical Data COMX 10CN-DPS

Table 104: Electrical Immunity to Interference and Radio Frequency COMX Modules

Table 105: Technical Data Evaluation Board COMXEB

Table 106: Technical Data EtherCAT Master Protocol

Table 107: Technical Data EtherCAT Slave Protocol

Table 108: Technical Data EtherNet/IP Scanner (Master) Protocol

Table 109: Technical Data EtherNet/IP Adapter (Slave) Protocol

Table 110: Technical Data Open Modbus/TCP Protocol

Table 111: Technical Data POWERLINK Controlled Node (Slave) Protocol

Table 112: Technical Data PROFINET IO RT Controller

Table 113: Technical Data PROFINET IO RT IRT Device Protocol

Table 114: Technical Data PROFINET IO RT IRT Device Protocol

Table 115: Technical Data sercos Master Protocol

Table 116: Technical Data sercos Slave Protocol

Table 117: Technical Data VARAN Client Protocol

Table 118: Technical Data CANopen Master Protocol

Table 119: Technical Data CANopen Slave Protocol

Table 120: Technical Data CANopen Slave Protocol

Table 121: Technical Data CC-Link-Slave Protocol

Table 122: Technical Data DeviceNet Master Protocol

Table 123: Technical Data DeviceNet Slave Protocol

Table 124: Technical Data PROFIBUS DP Master Protocol

Table 125: Technical Data PROFIBUS DP Slave Protocol

Table 126: Technical Data PROFIBUS-MPI Protocol

Table 127: EtherNet/IP Adapter/Slave – Instance ID of I/O Data

211/212

194

195

196

197

198

199

206

186

188

188

189

190

191

192

193

179

180

181

182

183

184

184

186

168

169

170

171

172

173

174

175

176



Appendix

17.8 Contacts

Headquarters

Germany

Hilscher Gesellschaft für

Systemautomation mbH

Rheinstrasse 15

65795 Hattersheim

Phone: +49 (0) 6190 9907-0

Fax: +49 (0) 6190 9907-50

E-Mail: [email protected]

Support

Phone: +49 (0) 6190 9907-99


Subsidiaries

China

Hilscher Systemautomation (Shanghai) Co. Ltd.

200010 Shanghai

Phone: +86 (0) 21-6355-5161


Support

Phone: +86 (0) 21-6355-5161


France

Hilscher France S.a.r.l.

69500 Bron

Phone: +33 (0) 4 72 37 98 40


Support

Phone: +33 (0) 4 72 37 98 40


India

Hilscher India Pvt. Ltd.

New Delhi - 110 065

Phone: +91 11 43055431


Italy

Hilscher Italia S.r.l.

20090 Vimodrone (MI)

Phone: +39 02 25007068


Support

Phone: +39 02 25007068


Japan

Hilscher Japan KK

Tokyo, 160-0022

Phone: +81 (0) 3-5362-0521


Support

Phone: +81 (0) 3-5362-0521


Korea

Hilscher Korea Inc.

Suwon, Gyeonggi, 443-734

Phone: +82 (0) 31-695-5515


Switzerland

Hilscher Swiss GmbH

4500 Solothurn

Phone: +41 (0) 32 623 6633


Support

Phone: +49 (0) 6190 9907-99


USA

Hilscher North America, Inc.

Lisle, IL 60532

Phone: +1 630-505-5301


Support

Phone: +1 630-505-5301

E-Mail: [email protected] comX | Communication Modules for Real-Time-Ethernet and Fieldbus


212/212

© Hilscher, 2010-2015

Hilscher comX 100CA-RE, 100CN-RE, 50CA-REFO, 51CA-RE, 51CN-RE Communication Modules, comX 10CA-COS, 10CN-COS, 10CA-DNS, 10CN-DNS, 10CA-DPS, 10CN-DPS Communication Module, COMXEB Evaluation Board User Manual

Assistant Bot

User Manual comX

Communication Modules for Real-Time-Ethernet and Fieldbus

Hilscher Gesellschaft für Systemautomation mbH www.hilscher.com

Table of Contents

1 Introduction

1.1 About this Manual

1.1.2 List of Revisions

1.1.3 Reference to Hardware, Software and Firmware

1.1.4 Conventions in this Manual

1.2 Contents of Product DVD

1.2.1 Device Description Files

1.2.2 Documentation Overview comX

1.2.3.1

PROFINET IO-Device Firmware Versions 3.4 and 3.5

1.3 Ensuring Access Security

1.4.1 Copyright

1.4.3 Exclusion of Liability

1.4.4 Warranty

1.5 Licenses

2 Safety

2.2.1 Intended Use of comX Communication Modules

2.4 Commitment to read and understand the Manual

2.6 Safety Instructions to avoid Property Damage

2.6.1 Device Destruction by exceeding allowed Supply Voltage

2.6.2 Device Destruction by exceeding allowed Signal Voltage

2.7 Labeling of Safety Messages

3.1 Description

3.2 Prerequisites for the Operation of the comX

Communication Modules

3.2.1 Prerequisites for the Operation as Embedded System

3.2.2 Prerequisites for the Operation with Evaluation Board COMXEB

3.2.3 Remarks on Storage Stability and Contact Reliability of Hostside Connector

3.3 Supply Voltage and Signaling Voltage

3.4 Prerequisites for the Software Installation

3.4.1 Prerequisites for the System Configurator SYCON.net

3.5 Prerequisites for Certification

4 Getting Started comX Communication Modules

4.1 Hardware Installation as Embedded System (Master and

Slave)

4.2 Configuration of the comX Communication Module

(Slave)

4.3 Configuration of the comX Communication Module

(Master)

4.4 Notes for the Configuration of the Master Device

4.5 Device Names in SYCON.net

4.6 Exchange of comX Communication modules (Master and

Slave)

4.6.1 Steps for Exchange of Hardware

4.6.2 Load Firmware & Configuration into Replacement Module comX

(Slave)

4.6.3 Load Firmware & Configuration into Replacement Module comX

(Master)

4.7 Updating the Firmware, Driver and Software

Replacement

5.1 Warning Messages on Personal Injury

5.2 Property Damage Messages

5.2.1 Device Destruction by exceeding allowed Supply Voltage

5.2.2 Device Destruction by exceeding allowed Signaling Voltage

5.3 Installing the comX Communication Module in its Target

Environment

5.4 Decommissioning

7 Device Photos (Position of Switches, LEDs and

Interfaces)

7.1 Real-Time Ethernet Communication Module COMX

100CA-RE

7.1.2 Ethernet Interface of COMX 100CA-RE

7.2 Real-Time Ethernet Communication Module COMX

100CN-RE

7.2.2 Ethernet Interface of COMX 100CN-RE

7.3 Real-Time Ethernet Communication Module COMX 50CA-

REFO with Fiber Optic

7.3.2 Optical Ethernet Interface of COMX 50CA-REFO

Real-Time Ethernet Communication Module

COMX51CA-RE

7.4.1 COMX51CA-RE

7.4.2 Ethernet Interface of COMX51CA-RE

7.5 Real-Time Ethernet Communication Module COMX 51CN-

RE