PC Cards CIFX 50 50E 70E 100EH UM 53 EN

User Manual
PC Cards cifX
PCI (CIFX 50)
PCI Express (CIFX 50E)
Low Profile PCI Express (CIFX 70E, CIFX 100EH)
Installation, Operation and Hardware Description
Hilscher Gesellschaft für Systemautomation mbH

www.hilscher.com
DOC120204UM53EN | Revision 53 | English | 2019-08 | Released | Public
Table of Contents 2/284
Table of Contents
1 INTRODUCTION ......................................................................................................... 8
1.1 About the User Manual............................................................................................. 8
1.1.1 List of Revisions ................................................................................................... 9
1.1.2 Notes on Hardware, Firmware, Software and Driver Versions ..........................10
1.1.3 Conventions in this Manual ................................................................................ 13
1.1.4 Used Terminology .............................................................................................. 13
1.2 Contents of the Product DVD ................................................................................. 14
1.2.1 Installation Guide, Documentation Overview .....................................................14
1.2.2 What's New......................................................................................................... 14
1.2.3 Important Changes ............................................................................................. 14
1.2.4 Device Description Files PC Cards cifX ............................................................. 21
1.3 Legal Notes ............................................................................................................ 23
1.4 Registered Trademarks .......................................................................................... 26
1.4.1 EtherCAT Disclaimer .......................................................................................... 27
1.5 Obligation to read and understand the Manual ....................................................... 27
1.6 Licenses ................................................................................................................. 27
1.6.1 License Note about VARAN Client ..................................................................... 27
2 SAFETY .................................................................................................................... 28
2.1 General Note .......................................................................................................... 28
2.2 Intended Use .......................................................................................................... 28
2.3 Personnel Qualification .......................................................................................... 29
2.4 Safety Instructions.................................................................................................. 29
2.4.1 Electrical Shock Hazard ..................................................................................... 29
2.4.2 Communication Stop during Firmware Update or Configuration Download ......30
2.4.3 Mismatching System Configuration .................................................................... 30
2.5 Property Damage ................................................................................................... 31
2.5.1 Exceeding permissible Supply Voltage .............................................................. 31
2.5.2 Exceeding permissible Signaling Voltage ..........................................................32
2.5.3 Electrostatically sensitive Devices ...................................................................... 32
2.5.4 Power Disconnect while downloading Firmware or Configuration .....................33
2.5.5 Exceeding the maximum Number of allowed Write/Delete Accesses ...............33
2.5.6 Invalid Firmware ................................................................................................. 34
2.5.7 Information and Data Security ............................................................................ 34
2.6 Labeling of Safety Messages ................................................................................. 35
2.7 References Safety.................................................................................................. 35
3 DESCRIPTIONS AND REQUIREMENTS ................................................................. 36

3.1 Description ............................................................................................................. 36
3.2 PC Cards PCI CIFX 50-XX ..................................................................................... 36
3.3 PC Cards PCI (2 Channels) CIFX 50-2XX, CIFX 50-2XX\XX ................................. 37
PC Cards cifX PCI, PCIe, Low Profile PCIe | Installation, Operation and Hardware Description
DOC120204UM53EN | Revision 53 | English | 2019-08 | Released | Public © Hilscher, 2008-2019
3.4 PC Cards PCI Express CIFX 50E-XX, CIFX 70E-XX, CIFX 100EH-RE\CUBE ....... 37
3.5 PC Cards PCI Express (2 Channels) CIFX 50E-2XX, CIFX 50E-2XX\XX ............... 38
3.6 The Function „Slot Number (Card ID)“ .................................................................... 39
3.6.1 Requirements „Slot Number (Card ID)“ .............................................................. 39
3.7 The Function „DMA Mode“ ..................................................................................... 41
3.7.1 Requirements „DMA Mode“ ................................................................................ 41
3.8 PC Cards cifX with additional MRAM ..................................................................... 42
3.9 System Requirements ............................................................................................ 43
3.9.1 Slot for the PC Cards cifX PCI, PCIe and Low Profile PCIe ..............................43
3.9.2 Power Supply and Host Interface ....................................................................... 44
3.9.3 Operating Temperature Range for UL Certificate ..............................................44
3.10 Requirements for Operation of the PC Card cifX .................................................... 45
3.11 Prerequisites for Certification ................................................................................. 46
3.11.1 PROFINET IO Certification for IRT and SYNC0 Signal .....................................46
4 GETTING STARTED ................................................................................................. 47

4.1 Warnings ................................................................................................................ 47
4.2 Installation and Configuration PC Card cifX............................................................ 49
4.3 Note on Exchange Service (Replacement Case).................................................... 53
4.4 Notes for the Configuration of the Master Device ................................................... 53
4.5 Device Names in SYCON.net................................................................................. 55
4.6 Update for Firmware, Driver and Software ............................................................. 57
5 DEVICE DRAWINGS ................................................................................................ 58

5.1 PC Cards cifX PCI and PCI Express ...................................................................... 58
5.1.1 CIFX 50-RE, CIFX 50E-RE, CIFX 50E-RE\ET ...................................................58
5.1.2 CIFX 50E-CCIES ................................................................................................ 60
5.1.3 CIFX 50-DP, CIFX 50E-DP ................................................................................ 62
5.1.4 CIFX 50-2DP, CIFX 50E-2DP ............................................................................ 64
5.1.5 CIFX 50-2DP\CO, CIFX 50E-2DP\CO ............................................................... 66
5.1.6 CIFX 50-2DP\DN, CIFX 50E-2DP\DN ................................................................ 68
5.1.7 CIFX 50-CO, CIFX 50E-CO ............................................................................... 70
5.1.8 CIFX 50-2CO, CIFX 50E-2CO ........................................................................... 72
5.1.9 CIFX 50-2CO\DN, CIFX 50E-2 CO\DN .............................................................. 74
5.1.10 CIFX 50-DN, CIFX 50E-DN ................................................................................ 76
5.1.11 CIFX 50-2DN, CIFX 50E-2DN ............................................................................ 78
5.1.12 CIFX 50-2ASM, CIFX 50E-2ASM ....................................................................... 80
5.1.13 CIFX 50-CC, CIFX 50E-CC ................................................................................ 82
5.1.14 Meaning of the Front Panel Inscriptions for 2 Channel Devices ........................83
5.2 PC Cards cifX Low Profile PCI Express ................................................................. 84
5.2.1 CIFX 70E-RE, CIFX 70E-RE\MR ....................................................................... 84
5.2.2 CIFX 70E-CCIES ................................................................................................ 86
5.2.3 CIFX 100EH-RE\CUBE ...................................................................................... 88
5.2.4 CIFX 70E-DP, CIFX 70E-DP\MR ....................................................................... 89
5.2.5 CIFX 70E-CO, CIFX 70E-CO\MR ...................................................................... 91
5.2.6 CIFX 70E-DN, CIFX 70E-DN\MR ....................................................................... 93
6 HARDWARE INSTALLATION AND UNINSTALLING ............................................... 95

6.1 Fix Front Plate Sticker ............................................................................................ 96
6.1.1 Front Plate Sticker CIFX 50-RE, CIFX 50E-RE, CIFX 50E-RE\ET ....................96
6.1.2 Front Plate Sticker CIFX 70E-RE, CIFX 70E-RE\MR, CIFX 100EH-RE\CUBE .97
6.2 Installing PC Card cifX PCI, PCIe, Low Profile PCIe .............................................. 99
6.3 Uninstalling the PC Card cifX PCI, PCIe, Low Profile PCIe .................................. 100
7 TROUBLESHOOTING ............................................................................................ 101

7.1 Instructions for Problem Solving ........................................................................... 101
8 LED DESCRIPTIONS.............................................................................................. 102

8.1 Overview LEDs Real-Time Ethernet Systems ...................................................... 102
8.2 Overview LEDs Fieldbus Systems........................................................................ 103
8.3 System LED ......................................................................................................... 104
8.4 CC-Link IE Field Basic Slave................................................................................ 105
8.5 CC-Link IE Field Slave ......................................................................................... 106
8.6 EtherCAT Master V3 ............................................................................................ 107
8.7 EtherCAT Master V4 ............................................................................................ 108
8.8 EtherCAT Slave ................................................................................................... 110
8.9 EtherNet/IP Scanner (Master) .............................................................................. 111
8.10 EtherNet/IP Adapter (Slave) ................................................................................. 113
8.11 Open Modbus/TCP .............................................................................................. 115
8.12 POWERLINK Controlled Node/Slave V2, V3 ........................................................ 116
8.13 PROFINET IO-Controller V2 ................................................................................ 117
8.14 PROFINET IO Controller V3................................................................................. 118
8.15 PROFINET IO-Device .......................................................................................... 120
8.16 Sercos Master ...................................................................................................... 121
8.17 Sercos Slave ........................................................................................................ 123
8.18 VARAN Client (Slave) .......................................................................................... 125
8.19 PROFIBUS DP Master ......................................................................................... 126
8.20 PROFIBUS DP Slave ........................................................................................... 127
8.21 PROFIBUS MPI Device ........................................................................................ 128
8.22 CANopen Master.................................................................................................. 129
8.23 CANopen Slave.................................................................................................... 130
8.24 DeviceNet Master................................................................................................. 131
8.25 DeviceNet Slave................................................................................................... 132
8.26 AS Interface Master ............................................................................................. 133
8.27 CC-Link Slave ...................................................................................................... 134
9 DEVICE CONNECTIONS AND SWITCHES ........................................................... 135
9.1 Ethernet Interface................................................................................................. 135
9.1.1 Ethernet Pin Assignment at the RJ45 Socket ..................................................135
9.1.2 Ethernet Connection Data ................................................................................ 137
9.1.3 Use of Hubs and Switches ............................................................................... 137
9.2 PROFIBUS Interface ............................................................................................ 138
9.3 CANopen Interface............................................................................................... 138
9.4 DeviceNet Interface .............................................................................................. 139
9.5 AS-Interface Interface .......................................................................................... 139
9.6 CC-Link Interface ................................................................................................. 140
9.7 Rotary Switch for Slot Number (Card ID) .............................................................. 141
9.7.1 Set Slot Number (Card ID) ............................................................................... 141
9.7.2 Note for Device Exchange Service (Replacement Case): ...............................141
9.7.3 Rotary Switch Slot Number PC Cards cifX Low Profile ....................................142
9.8 SYNC Connector (Pin-Assignment, Hardware/Firmware) ..................................... 143
9.8.1 Pin Assignment SYNC Connector, X51 (CIFX 50 50E 70E) ............................143
9.8.2 Pin Assignment SYNC Connector, J1 (CIFX 100EH) ......................................143
9.8.3 Items on Hardware ........................................................................................... 144
9.8.4 Items on Firmware ............................................................................................ 144
9.9 Pin Assignment at the PCI Bus ............................................................................ 145
9.9.1 Overview ........................................................................................................... 145
9.9.2 References PCI Specifications ......................................................................... 145
9.9.3 Pin Assignment for PCI Express Bus CIFX 100EH-RE\CUBE ........................146
10 TECHNICAL DATA ................................................................................................. 147

10.1 Technical Data PC Cards cifX .............................................................................. 147
10.1.1 CIFX 50-RE ...................................................................................................... 147
10.1.2 CIFX 50E-RE, CIFX 50E-RE\ET ...................................................................... 149
10.1.3 CIFX 50E-CCIES, CIFX 70E-CCIES ................................................................ 151
10.1.4 CIFX 50-DP ...................................................................................................... 153
10.1.5 CIFX 50E-DP .................................................................................................... 154
10.1.6 CIFX 50-CO ...................................................................................................... 156
10.1.7 CIFX 50E-CO ................................................................................................... 157
10.1.8 CIFX 50-DN ...................................................................................................... 158
10.1.9 CIFX 50E-DN .................................................................................................... 160
10.1.10 CIFX 50-CC ...................................................................................................... 161
10.1.11 CIFX 50E-CC .................................................................................................... 162
10.1.12 CIFX 50-2DP .................................................................................................... 164
10.1.13 CIFX 50E-2DP .................................................................................................. 165
10.1.14 CIFX 50-2DP\CO .............................................................................................. 168
10.1.15 CIFX 50E-2DP\CO ........................................................................................... 169
10.1.16 CIFX 50-2DP\DN .............................................................................................. 171
10.1.17 CIFX 50E-2DP\DN............................................................................................ 172
10.1.18 CIFX 50-2CO .................................................................................................... 174
10.1.19 CIFX 50E-2CO ................................................................................................. 175
10.1.20 CIFX 50-2CO\DN .............................................................................................. 177
10.1.21 CIFX 50E-2CO\DN ........................................................................................... 178
10.1.22 CIFX 50-2DN .................................................................................................... 180
10.1.23 CIFX 50E-2DN .................................................................................................. 181
10.1.24 CIFX 50-2ASM ................................................................................................. 183
10.1.25 CIFX 50E-2ASM ............................................................................................... 184
10.1.26 CIFX 70E-RE, CIFX 70E-RE\MR ..................................................................... 185
10.1.27 CIFX 100EH-RE\CUBE .................................................................................... 188
10.1.28 CIFX 70E-DP, CIFX 70E-DP\MR ..................................................................... 190
10.1.29 CIFX 70E-CO, CIFX 70E-CO\MR .................................................................... 191
10.1.30 CIFX 70E-DN, CIFX 70E-DN\MR ..................................................................... 193
10.2 PCI IDs PC Cards cifX on the PCI Bus ................................................................. 195
10.3 Supported PCI-Bus Commands ........................................................................... 195
10.4 Technical Data of the Communication Protocols .................................................. 196
10.4.1 CC-Link IE Field Basic Slave ........................................................................... 196
10.4.2 CC-Link IE Field Slave ..................................................................................... 196
10.4.3 EtherCAT Master (V3) ...................................................................................... 197
10.4.4 EtherCAT Master (V4) ...................................................................................... 198
10.4.5 EtherCAT Slave ................................................................................................ 199
10.4.6 EtherNet/IP Scanner (Master) .......................................................................... 200
10.4.7 EtherNet/IP Adapter (Slave) ............................................................................. 201
10.4.8 Open Modbus/TCP ........................................................................................... 202
10.4.9 POWERLINK Controlled Node/Slave (V2) .......................................................203
10.4.10 POWERLINK Controlled Node/Slave (V3) .......................................................203
10.4.11 PROFINET IO-Controller (V2) .......................................................................... 204
10.4.12 PROFINET IO-Controller (V3) .......................................................................... 205
10.4.13 PROFINET IO-Device (V3.4) ........................................................................... 206
10.4.14 PROFINET IO Device (V3.13) .......................................................................... 207
10.4.15 Sercos Master .................................................................................................. 208
10.4.16 Sercos Slave .................................................................................................... 209
10.4.17 VARAN Client (Slave)....................................................................................... 210
10.4.18 PROFIBUS DP Master ..................................................................................... 211
10.4.19 PROFIBUS DP Slave ....................................................................................... 212
10.4.20 PROFIBUS MPI ................................................................................................ 213
10.4.21 CANopen Master .............................................................................................. 214
10.4.22 CANopen Slave ................................................................................................ 215
10.4.23 DeviceNet Master ............................................................................................. 216
10.4.24 DeviceNet Slave ............................................................................................... 217
10.4.25 AS-Interface Master.......................................................................................... 218
10.4.26 CC Link Slave ................................................................................................... 219
11 ANNEX .................................................................................................................... 220

11.1 Device Label with Matrix Code ............................................................................. 220
11.2 Tolerances of the shown Card Dimensions .......................................................... 220
11.3 Dimensions PC Cards cifX PCI and PCI Express ................................................. 221
11.3.1 CIFX 50-RE ...................................................................................................... 221
11.3.2 CIFX 50E-RE, CIFX 50E-RE\ET ...................................................................... 222
11.3.3 Front Panel CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET ..........................223
11.3.4 CIFX 50E-CCIES .............................................................................................. 224
11.3.5 Front Panel CIFX 50-CCIES ............................................................................ 225
11.3.6 CIFX 50-DP, CIFX 50E-DP .............................................................................. 226
11.3.7 Front Panel CIFX 50-DP or CIFX 50E-DP .......................................................228
11.3.8 CIFX 50-CO, CIFX 50E-CO ............................................................................. 229
11.3.9 Front Panel CIFX 50-CO or CIFX 50E-CO.......................................................231
11.3.10 CIFX 50-DN, CIFX 50E-DN .............................................................................. 232
11.3.11 Front Panel CIFX 50-DN or CIFX 50E-DN .......................................................234
11.3.12 CIFX 50-CC, CIFX 50E-CC .............................................................................. 235
11.3.13 Front Panel CIFX 50-CC or CIFX 50E-CC .......................................................237
11.3.14 CIFX 50-2DP .................................................................................................... 238
11.3.15 CIFX 50E-2DP .................................................................................................. 239
11.3.16 CIFX 50-2DP\CO .............................................................................................. 240
11.3.17 CIFX 50E-2DP\CO ........................................................................................... 241
11.3.18 CIFX 50-2DP\DN .............................................................................................. 242
11.3.19 CIFX 50E-2DP\DN............................................................................................ 243
11.3.20 CIFX 50-2CO .................................................................................................... 244
11.3.21 CIFX 50E-2CO ................................................................................................. 245
11.3.22 CIFX 50-2CO\DN .............................................................................................. 246
11.3.23 CIFX 50E-2CO\DN ........................................................................................... 247
11.3.24 CIFX 50-2DN .................................................................................................... 248
11.3.25 CIFX 50E-2DN .................................................................................................. 249
11.3.26 Front Panel CIFX 50-2FB ................................................................................. 250
11.3.27 CIFX 50-2ASM, CIFX 50E-2ASM ..................................................................... 251
11.3.28 Front Panel CIFX 50-2ASM, CIFX 50E-2ASM .................................................253
11.4 Dimensions PC Cards cifX Low Profile PCI Express ............................................ 254
11.4.1 CIFX 70E-RE, CIFX 70E-RE\MR ..................................................................... 254
11.4.2 Front Panel CIFX 70E-RE, CIFX 70E-RE\MR .................................................255
11.4.3 CIFX 70E-CCIES .............................................................................................. 256
11.4.4 Front Panel CIFX 70-CCIES ............................................................................ 257
11.4.5 CIFX 70E-DP, CIFX 70E-DP\MR ..................................................................... 258
11.4.6 CIFX 70E-CO, CIFX 70E-CO\MR .................................................................... 260
11.4.7 Front Panel CIFX 70E-CO, CIFX 70E-CO\MR .................................................261
11.4.8 CIFX 70E-DN, CIFX 70E-DN\MR ..................................................................... 262
11.4.9 Front Panel CIFX 70E-DN, CIFX 70E-DN\MR .................................................263
11.5 Notes on earlier Hardeware Revisions ................................................................. 264
11.5.1 Failure in 10 MBit/s Half Duplex Mode and Workaround .................................264
11.6 Disposal of Waste Electronic Equipment .............................................................. 265
11.7 References........................................................................................................... 265
11.8 EtherCAT Summary over Vendor ID, Conformance test, Membership and Network
Logo ..................................................................................................................... 266
11.8.1 Vendor ID ......................................................................................................... 266
11.8.2 Conformance .................................................................................................... 266
11.8.3 Certified Product vs. Certified Network Interface .............................................266
11.8.4 Membership and Network Logo ....................................................................... 267
11.9 List of Figures ...................................................................................................... 268
11.10 List of Tables ........................................................................................................ 270
11.11 Glossary ............................................................................................................... 274
11.12 Contacts ............................................................................................................... 284
Introduction 8/284
1 Introduction
1.1 About the User Manual
This user manual provides descriptions of the installation, operation and
hardware of the PC Cards cifX PCI, PCI Express and Low Profile PCI
Express under Windows® XP, Windows® Vista, Windows® 7 and
Windows® 8, as listed subsequently.
PC Cards cifX:
 PCI (CIFX 50),
 PCI Express (CIFX 50E),
 Low Profile PCI Express (CIFX 70E, CIFX 100EH-RE\CUBE*)
*only Real-Time Ethernet
for the Real-Time Ethernet systems: for the fieldbus systems:

 CC-Link IE Field  PROFIBUS DP
 CC-Link IE Field Basic  PROFIBUS MPI
 EtherCAT  CANopen
 EtherNet/IP  DeviceNet
 Open-Modbus/TCP  AS-Interface
 POWERLINK  CC-Link
 PROFINET IO
 Sercos
 VARAN
For information about the Installation of the Software refer to the User
Manual „Software Installation for PC Cards cifX“ [DOC120207UMXXEN].
For information about the Wiring of the Protocol Interface refer to the
„Wiring Instructions“ [DOC120208UMXXEN].
The devices described in this manual are listed in the sections
- PC Cards PCI CIFX 50-XX (page 36),
- PC Cards PCI (2 Channels) CIFX 50-2XX, CIFX 50-2XX\XX (page 37)
and
- PC Cards PCI Express CIFX 50E-XX, CIFX 70E-XX, CIFX 100EH-
RE\CUBE (page 37). The devices are described in detail in the chapters
Hardware Installation and Uninstalling (page 95), LED Descriptions (page
102), Device Connections and Switches (page 135) and Technical Data
(page 147).
You can download the latest edition of a manual from the website
www.hilscher.com under Support > Downloads > Manuals or under
Products directly with the information about your product.
Introduction 9/284
1.1.1 List of Revisions

Index Date Chapter Revisions
49 17-11-28 All CC-Link IE Field Slave devices added:
- CIFX 50E-CCIES,
- CIFX 70E-CCIES
9.1.1 Section Ethernet Pin Assignment at the RJ45 Socket:
Ethernet RJ45 pin assignment (1000 MBit/s) added.
18-03-21 All, Storage temperature range updated: -40 °C ... +85 °C
2, Safety communication in the document revised. Chapter Safety completed.
4.1, Section Warnings moved and changed.
10.1, Section Technical Data PC Cards cifX: Description "Maximum current at
3.3 V (typical) [value]" changed to "Current at 3.3 V [value] (maximum)".
10.1.3 Section CIFX 50E-CCIES, CIFX 70E-CCIES updated (current at 3.3V
typically, ranges for operating and storage temperature).
50 18-08-15 All CC-Link IE Field Basic Slave added, CIFX 50-RE\ET removed,
CIFX 50-RE (Revision 6, operating temperature up to + 70°C) added.
Newly added: CIFX 50E-2DP, CIFX 50E-2CO, CIFX 50E-2DN, CIFX 50E-
2DPCO, CIFX 50E-2DPDN, CIFX 50E-2CODN
8.1, Section Overview LEDs Real-Time Ethernet Systems note added.
8.9, 8.10 Sections EtherNet/IP Scanner (Master) and EtherNet/IP Adapter (Slave)
updated.
51 18-12-06 1.2.3 Section: Important Changes
PROFINET IO Controller Firmware Versions V2 and V3
Update to: PROFINET IO Controller V3 Protocol API 07 EN.pdf
PROFINET IO-Device Firmware Versions 3.4 and 3.13
V3.10 --> V3.13
Migration Guide PROFINET IO Device, Migration from V3.x to V3.13
GSDML-V2.32 --> GSDML-V2.33
DVD path 3.10 --> 3.13
Update to: PROFINET IO-Device V3.13 Protocol API 18 EN.pdf
EtherCAT Slave Firmware Versions 2.5 and 4.7
Update to: EtherCAT Slave V4 Protocol API 10 EN.pdf
EtherCAT Slave Firmware Version 4.7
POWERLINK Controlled Node V2 and V3
Update to: POWERLINK Controlled Node Protocol V3 API 08 EN.pdf
1.2.4, Section Device Description Files PC Cards cifX: Name of the device
description file for CC-Link IE Field Basic Slave added (0x0352_CIFX RE
CCIEBS_1_en.cspp).
4.4, Section Notes for the Configuration of the Master Device: Note for CC-Link
IE Field-Basic-Slave completed.
8.4 Section CC-Link IE Field Basic Slave updated.
10.1, Section Technical Data PC Cards cifX: Information on UL certification
reviewed and revised according to UL Report File E221530 (Vol. 2, Issued:
2009-12-22).
10.4 Section Technical Data of the Communication Protocols updated
(EtherCAT Slave\V4.7, EtherNetIP Scanner\V2.10, EtherNetIP Adapter\V2.13,
POWERLINK Controlled Node V3.4, PROFINET IO Controller V3.3, PROFINET IO RT
IRT Device V3.13, PROFIBUS-DP Master\V2.8, \PROFIBUS-DP Slave\V2.10, Sercos
Slave V3.5, VARAN Client\V1.1, CC-Link Slave\V2.12)
52 19-03-06 4.5 Section Device Names in SYCON.net device name updated: CC-Link IE
Field Basic Slave: CiFX RE/CCIBS
Terminology: “current” changed to “current consumption” where this meaning
is meant.
53 19-08-29 1.1.2.1, 9.9.1 Sections Hardware: PC Cards cifX and Overview: Hardware revisions
updated for CIFX 50-DP (Revsion 6), CIFX 50-CO (Revsion 6), CIFX 50-DN
(Revsion 6), CIFX 50E-RE (Revsion 6) , CIFX 50E-RE\ET (Revsion 2).
1.1.2.3 Section Firmware: Firmware name updated:
POWERLINK Controlled Node V3.4: C010K000.NXF,
PROFINET IO-Device V3.13: C010D000.NXF
Table 1: List of Revisions
Introduction 10/284
1.1.2 Notes on Hardware, Firmware, Software and Driver Versions
Note on Software Update: The hardware revisions and the versions for
the firmware, the driver or the configuration software listed in this section
functionally belong together. For existing hardware installation the
firmware, the driver and the configuration software must be updated
according to the details listed in this section.
For the software upgrade system overview refer to section Update for
Firmware, Driver and Software on page 57.
1.1.2.1 Hardware: PC Cards cifX

PC Card cifX Part No. Hardware USB „Rotary Switch Slot „DMA Mode“
Revision from HW Rev. Number (Card ID)“ from HW Rev.
from HW Rev.
CIFX 50-RE 1250.100 6 - 3 1
CIFX 50-DP 1250.410 6 - 5 1
CIFX 50-CO 1250.500 6 - 5 1
CIFX 50-DN 1250.510 6 - 5 1
CIFX 50-CC 1250.740 2 - 2 1
CIFX 50E-RE 1251.100 6 - 4 4
CIFX 50E-RE\ET 1251.105 2 - 1 1
CIFX 50E-CCIES 1251.700 1 - 1 1
CIFX 50E-DP 1251.410 6 - 5 5
CIFX 50E-CO 1251.500 5 - 4 4
CIFX 50E-DN 1251.510 5 - 4 4
CIFX 50E-CC 1251.740 4 - 3 3
CIFX 50-2DP 1252.410 3 - 3 1
CIFX 50-2DP\CO 1252.470 2 - 2 1
CIFX 50-2DP\DN 1252.480 1 - 1 1
CIFX 50-2CO 1252.500 2 - 2 1
CIFX 50-2CO\DN 1252.570 1 - 1 1
CIFX 50-2DN 1252.510 2 - 2 1
CIFX 50-2ASM 1252.630 2 - 2 1
CIFX 50E-2DP 1.253.410 1 - 1 1
CIFX 50E-2DP\CO 1.253.470 1 - 1 1
CIFX 50E-2DP\DN 1.253.480 1 - 1 1
CIFX 50E-2CO 1.253.500 1 - 1 1
CIFX 50E-2CO\DN 1.253.570 1 - 1 1
CIFX 50E-2DN 1.253.510 1 - 1 1
CIFX 50E-2ASM 1253.630 5 - 2 4
CIFX 70E-RE 1.259.100 1 - 1 1
CIFX 70E-RE\MR 1.259.103 1 - 1 1
CIFX 70E-CCIES 1259.700 1 - 1 1
CIFX 100EH-RE\CUBE 9016.090 4 - 1 1
CIFX 70E-DP 1.259.410 1 - 1 1
CIFX 70E-DP\MR 1.259.413 1 - 1 1
CIFX 70E-CO 1.259.500 1 - 1 1
CIFX 70E-CO\MR 1.259.503 1 - 1 1
CIFX 70E-DN 1.259.510 1 - 1 1
Introduction 11/284
PC Card cifX Part No. Hardware USB „Rotary Switch Slot „DMA Mode“
Revision from HW Rev. Number (Card ID)“ from HW Rev.
from HW Rev.
CIFX 70E-DN\MR 1.259.513 1 - 1 1
Table 2: Reference on Hardware PC Cards cifX
1.1.2.2 Driver and Software

Driver and Software Version
SYCON.net SYCONnet netX setup.exe 1.0500
netX Configuration Tool-Setup netXConfigurationUtility_Setup.exe 1.0900
cifX Device Driver cifX Device Driver Setup.exe 1.6
Toolkit 1.5
cifX TCP/IP Server for SYCON.net cifX TCP Server.exe V2.3
US Driver USB Driver of Windows® 5.1.2600.x
Table 3: Reference on Driver and Software
1.1.2.3 Firmware
The downloadable cifX firmware runs on PC Cards cifX PCI, PCI Express
and Low Profile PCI Express (unless otherwise stated). The firmware
automatically detects whether it is running on a PC Cards cifX PCI, PCI
Express or Low Profile PCI Express.
PC Cards and PCI Express with one Channel:

Protocol Firmware File Firmware Version* Minimum Version of the Firmware
for USB Support
CANopen Master CIFXCOM.NXF 2.14 from 2.5.2.0
CANopen Slave CIFXCOS.NXF 3.7 from 2.4.4.0
CC-Link Slave CIFXCCS.NXF 2.12 -
CC-Link IE Field Basic Slave C020Y000.NXF 1.1 -
CC-Link IE Field Slave*** C020X000.NXF 1.1 -
DeviceNet Master CIFXDNM.NXF 2.4 from 2.2.7.0
DeviceNet Slave CIFXDNS.NXF 2.5 from 2.2.7.0
EtherCAT Master CIFXECM.NXF 4.4 (V4) from 2.4.4.0
EtherCAT Master CIFXECM.NXF 3.0 (V3)** from 2.4.4.0
EtherCAT Slave CIFXECS.NXF 4.7 (V4) from 2.5.13.0
EtherCAT Slave CIFXECS.NXF 2.5 (V2)** from 2.5.13.0
EtherNet/IP Scanner CIFXEIM.NXF 2.10 from 2.2.4.1
EtherNet/IP Adapter CIFXEIS.NXF 2.13 from 2.3.4.1
Open-Modbus/TCP CIFXOMB.NXF 2.6 from 2.3.2.1
POWERLINK Controlled Node C010K000.NXF 3.4 (V3) from 2.1.22.0
POWERLINK Controlled Node CIFXPLS.NXF 2.1 (V2)** from 2.1.22.0
PROFIBUS DP Master CIFXDPM.NXF 2.8 from 2.3.22.0
PROFIBUS DP Slave CIFXDPS.NXF 2.10 from 2.3.30.0
PROFIBUS MPI-Gerät CIFXMPI.NXF 2.4 from 2.4.1.2
PROFINET IO-Controller C010C000.NXF 3.3 (V3) from 2.4.10.0
PROFINET IO-Controller CIFXPNM.NXF 2.7 (V2)** from 2.4.10.0
PROFINET IO-Device C010D000.NXF 3.13 (V3) from 3.4.9.0
Introduction 12/284
Protocol Firmware File Firmware Version* Minimum Version of the Firmware
for USB Support
PROFINET IO-Device CIFXPNS.NXF 3.4 (V3)** from 3.4.9.0
Sercos Master CIFXS3M.NXF 2.1 from 2.0.14.0
Sercos Slave CIFXS3S.NXF 3.5 from 3.0.13.0
VARAN-Client CIFXVRS.NXF 1.1 from 1.0.3.0
Table 4: Reference on Firmware (for 1 Channel Systems), **Outdated versions
Note: *Unless otherwise indicated, in this manual data to the firmware version
correspond to the stack version.
***Important! Use the PC cards CIFX 50E-CCIES or CIFX 70E-CCIES

only together with the CC-Link IE Field Slave firmware and do not use this
firmware for any other cards.
PC Cards PCI and PCI Express with two Channels:

Protocol Channel X1 Stack- Protocol Channel X2 Stack- Firmware File Firmware Version
Version Version
AS-Interface Master 2.4 AS-Interface Master 2.4 CIFX2ASM.NXF 2.4
CANopen Master 2.14 CANopen Master 2.14 C0204040.NXF 1.2
CANopen Master 2.14 CANopen Slave 3.7 C0204050.NXF 1.2
CANopen Master 2.14 DeviceNet Master 2.4 C0204060.NXF 1.2
CANopen Slave 3.7 CANopen Slave 3.7 C0205050.NXF 1.2
CANopen Slave 3.7 DeviceNet Slave 2.5 C0205070.NXF 1.2
DeviceNet Master 2.4 DeviceNet Master 2.4 C0206060.NXF 1.2
DeviceNet Master 2.4 DeviceNet Slave 2.5 C0206070.NXF 1.2
DeviceNet Slave 2.5 DeviceNet Slave 2.5 C0207070.NXF 1.2
PROFIBUS DP Master 2.7 PROFIBUS DP-Master 2.7 CIFX2DPM.NXF 1.2 (new version counting)
PROFIBUS DP Master 2.7 PROFIBUS DP-Slave 2.9 C0201020.NXF 1.2
PROFIBUS DP Master 2.7 CANopen Master 2.14 C0201040.NXF 1.2
PROFIBUS DP Master 2.7 DeviceNet Master 2.4 C0201060.NXF 1.2
PROFIBUS DP Slave 2.9 PROFIBUS DP-Slave 2.9 CIFX2DPS.NXF 1.1 (new version counting)
PROFIBUS DP Slave 2.9 CANopen Slave 3.7 C0202050.NXF 1.2
PROFIBUS DP Slave 2.9 DeviceNet Slave 2.5 C0202070.NXF 1.2
Table 5: Reference on Firmware (for 2 Channel Systems)
Introduction 13/284
1.1.3 Conventions in this Manual
Notes, operation instructions and results of operation steps are marked as

follows:
Notes
Important: <important note you must follow to avoid malfunction>
Note: <general note>
<note, where to find further information>
Operation Instructions
1. <instruction>
2. <instruction>
or
 <instruction>
Results
 <result>
Safety Messages
The labeling of safety messages is explained in the chapter Safety.
1.1.4 Used Terminology

PC Card cifX Communication Interfaces of the cifX family of Hilscher
based on the netX technology.
CIFX 50-RE Example for the product name for a PC card cifX Real-Time
Ethernet.
CIFX 50-XX Example (‘XX’ replaces ‘RE’, ‘DP’, ‘CO’, ‘DN’ or ‘CC’)
For further terminology to the PC cards cifX, its installation, configuration

and operation refer to glossary in the annex.
Introduction 14/284
1.2 Contents of the Product DVD

Note! In order to download the product DVD, you need Internet access.
On the Communication Solutions DVD you will find these installation

instructions about the software installation and the necessary configuration
software, the documentation, the drivers and software for your PC Card
cifX, and additional auxiliary tools. You can download this product DVD as
a ZIP file from the website http://www.hilscher.com (under Products, directly
with the information on your product).
1.2.1 Installation Guide, Documentation Overview

The installation guide Software Installation and Documentation Over-
view on the Communication Solutions DVD are in the directory
Documentation\0. Installation and Overview. The installation guide
includes:
 An overview on the Content of the Communication Solutions DVD (in
the section What is on the Communication Solutions DVD?)
 Overviews listing the available Documentations for PC cards cifX (in
chapter PC Cards cifX, Software and Documentation).
1.2.2 What's New

All current version information for hardware and software described in this
manual are provided in the folder \Documentation\What's New -
Communication Solutions DVD RL XX EN.pdf on the Communication
Solutions DVD.
1.2.3 Important Changes
1.2.3.1 DeviceNet Master - SYCON.net and Firmware

The DeviceNet Master firmware from V2.3.11.0 and the DeviceNet Master
DTM from V1.360.x.x support the network scan function. If in the device a
firmware version V2.3.10.0 or earlier is used then a firmware update to
V2.3.11.0 or higher must be done, in order to use the network scan
function.
Introduction 15/284
1.2.3.2 PROFINET IO-Controller Firmware Versions V2 and V3

The PROFINET IO-Controller firmware has been revised and completed
and is available in version V3 since the first quarter of 2017.
Upgrading the PROFINET IO-Controller firmware from V2 to V3 is
recommended. Use the PROFINET IO-Controller firmware V3 for a new
installation when creating or developing your application program for the
first time.
The development of the PROFINET IO-Controller firmware V2 will not be
continued. But this firmware version is still maintained and will be delivered
furthermore.
The PROFINET IO-Controller V3 implements several new features, which
are not available in the PROFNET IO-Controller V2:
• IRT operating mode
• Optimized process data performance
• Automatic name assignment
• Automatic alarm acknowledgement
• MRP Client and Manager for media redundancy
• Requirements PROFINET Specification 2.3: e. g. Advanced Startup,
MultipleInterfaceMode, network load requirements.
The process data handling in PROFINET IO-Controller V3 (process data
image structure and process data timing) was reworked to achieve the
required performance improvement and to support synchronized
applications.
Removed features and incompatibilites:
• PROFINET IO-Controller V3 does neither support swapping of IO data
nor automatic IOPS handling.
• The configuration parameters have been extended to meet the IRT
configuration requirements. The structure of the configuration database
has been changed. Therefore, the PROFINET IO-Controller V3 can not
be configured with a configuration database of the PROFINET IO-
Controller V2 and vice versa.
• The configuration API of PROFINET IO-Controller V2 are not supported
by PROFINET IO-Controller V3. The new configuration API of
PROFINET IO-Controller V3 is to be used.
• The PROFINET IO-Controller V3 does not support process data in little
endian format. This feature was rarely used and has been removed for
better performance.
Introduction 16/284
If you want to change in an existing system from the PROFINET IO-
Controller firmware V2 to V3, note the following guidelines:
1. Customize your application program according to the Migration Guide

PROFINET IO Controller Migrating from version 2 to 3.
If you want to change to V4.2, please check in the Migration Guide

PROFINET IO Controller Migrating from version 2 to 3 which changes
are necessary in the application program in order to use version 4.2.
2. If you upgrade to the PROFINET IO-Controller firmware V3, you can not
reuse the existing SYCON.net project of the PROFINET IO-Controller
firmware V2. Create a new configuration. For the PROFINET IO-
Controller firmware V3 for configuration, you need SYCON.net from
version 1.400, which contains new configuration dialogs (PROFINET IO
IRT-Controller DTM).
3. Update the PROFINET IO controller firmware in your device to
Version 3.
On the Communication Solutions DVD, files and manuals referring to

firmware V2 and V3, are available as follows:
PROFINET IO-Controller V2 PROFINET IO-Controller V3
Directory on the DVD \ File: Directory on the DVD \ File:
Firmware Firmware\CIFX\Outdated versions\PNM V2\ Firmware\CIFX\C010C000.nxf
cifxpnm.nxf
Header Examples and API\0. Examples and API\0. Header\Firmware\PROFINET
Header\Firmware\PROFINET IO Controller V2 Controller V3
Protocol API Documentation\7. Programming Manuals\EN\3. Documentation\7. Programming Manuals\EN\3.
Protocol API\PROFINET IO Controller\ Protocol API\PROFINET IO Controller V3\
PROFINET IO Controller Protocol API 19 PROFINET IO Controller V3 Protocol API 07 EN.pdf
EN.pdf, PROFINET IO Controller - Migrating from version 2
Ethernet Protocol API.pdf, to 3 MG 01 EN.pdf
TCP IP - Packet Interface API 12 EN.pdf
Table 6: PROFINET IO-Controller Firmware V2 and V3 on the Product DVD
Introduction 17/284
1.2.3.3 PROFINET IO-Device Firmware Versions V3.4 and V3.13

The PROFINET IO Device firmware was revised and completed and is
available in version 3.13 since the fourth quarter 2018.
Use the PROFINET IO Device firmware in version 3.13 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.13, note the following guidelines:

PROFINET IO Device, Migration from V3.x to V3.13.

PROFINET IO Device, Migration from V3.x to V3.13 which changes are
necessary in the application program in order to use version 3.13.
2. Adjust the configuration of your PROFINET IO Controller device. Use

the new GSDML file in the configuration software of the PROFINET IO
Controller for this:
GSDML-V2.33-HILSCHER-CIFX RE PNS-xxxxxxxx.xml.
3. Update the PROFINET IO Device firmware in your device to version
3.13.
Note also:
• SYCON.net V1.500.x.x can configure the PROFINET IO Device
firmware V3.4 as well as V3.13
• 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.13 are available:
PROFINET IO-Device V3.4 PROFINET IO-Device V3.13
Firmware Firmware\CIFX\cifxpns.nxf Firmware\CIFX\C010D000.nxf
Header Examples and API\0. Header\Firmware\PROFINET IO Examples and API\0. Header\Firmware\PROFINET IO
Device V3.4.X Device V3.13
GSDML EDS\PROFINET\V3.4.X\GSDML-V2.3-HILSCHER-CIFX EDS\PROFINET\Device\V3.13\GSDML-V2.33-
RE PNS-20130225.xml HILSCHER-CIFX RE PNS-xxxxxxxx.xml
Protocol API Documentation\7. Programming Manuals\EN\3. Protocol Documentation\7. Programming Manuals\EN\3.
API\PROFINET IO Device V3.4\PROFINET IO Device Protocol API\PROFINET IO Device V3.13\PROFINET
Protocol API 13 EN.pdf IO Device V3.13 Protocol API 18 EN.pdf
TCP IP - Packet Interface API 13 EN.pdf PROFINET IO Device - Migration from Version 3.x to
3.13 MG 09 EN.pdf
Table 7: PROFINET IO-Device Firmware Version 3.4 and 3.13, Header, GSDML and
Protocol API Manual
Introduction 18/284
1.2.3.4 EtherCAT Master Firmware Versions V3 and V4

The EtherCAT Master firmware has been revised and completed and is
available in version V4 since the first quarter of 2017.
Upgrading the EtherCAT Master firmware from V3 to V4 is recommended.
Use the EtherCAT Master firmware V4 for a new installation when creating
or developing your application program for the first time, as well as in
existing systems.
The reasons for upgrading are as follows:
• The development of the EtherCAT Master firmware V3 will not be
continued. But this firmware version will be delivered furthermore.
• Due to the software design, the EtherCAT Master firmware V3 has
considerable performance limitations on Hilscher products.
• Compared to the EtherCAT Master firmware V3, the EtherCAT Master
firmware V4 has major improvements, while keeping the backward
compatibility to the firmware V3 as much as possible. Due to the
improvements, there are advantages in device certification.
Performance improvement and new functions with EtherCAT Master
firmware V4:
• General performance improvement up to five times
• Improvements in network and individual Slave control, Slave diagnostics
• Support of CoE, SoE, EoE, FoE, ExtSync
• Support of redundancy in different, even complex topologies, including
DC and DC resynchronization and hot-connect.
• Troubleshooting improvement.
If you want to change in an existing system from the EtherCAT Master
firmware V3 to V4, you need to upgrade the EtherCAT Master firmware in
your device to V4.
With SYCON.net, you can configure both the EtherCAT Master firmware V3
as well as the EtherCAT Master firmware V4. When you upgrade to the
EtherCAT Master firmware V4, you can continue to use the existing
SYCON.net project.
EtherCAT Master V3 EtherCAT Master V4
Firmware Firmware\CIFX\Outdated versions\ECM V3\ Firmware\CIFX\cifxecm.nxf
cifxecm.nxf
Header Examples and API\0. Header\Firmware\EtherCAT Examples and API\0. Header\Firmware\EtherCAT Master
Master V3 V4
Protocol API Documentation\7. Programming Manuals\EN\ Documentation\7. Programming Manuals\EN\3. Protocol
3. Protocol API\EtherCAT Master V3\EtherCAT API\EtherCAT Master V4\EtherCAT Master V4 Protocol
Master V3 Protocol API 05 EN.pdf API 05 EN.pdf
Table 8: EtherCAT Master Firmware V3 and V4 on the Product DVD
Introduction 19/284
1.2.3.5 EtherCAT Slave Firmware Versions V2.5 and V4.7

The EtherCAT Slave firmware was revised and completed and is available
in version 4.7.
Use the EtherCAT Slave firmware in version 4.7 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.7, note the following guidelines:

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

EtherCAT Slave, Migration from V2.5 to V4.2 which changes are
necessary in the application program in order to use version 4.7.
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 CIFX RE ECS V4.6.X.xml.
3. Update the EtherCAT Slave firmware in your device to version 4.7.
Note also:
• SYCON.net V1.500 can configure the EtherCAT Slave firmware V2.5 as
well as V4.7 and higher.
• 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.7 are available:
EtherCAT-Slave V2.5 EtherCAT-Slave V4.7
Firmware Firmware\CIFX\cifxecs.nxf Firmware\CIFX\ECS V4.X\cifxecs.nxf
Header Examples and API\0. Header\Firmware\EtherCAT Examples and API\0. Header\Firmware\EtherCAT Slave V4
Slave V2.5.X
XML EDS\EtherCAT\Slave\V2.X\Hilscher CIFX RE ECS EDS\EtherCAT\Slave\V4\Hilscher CIFX RE ECS
V2.2.X.xml V4.6.X.xml
Protocol API Documentation\7. Programming Manuals\EN\3. Documentation\7. Programming Manuals\EN\3. Protocol
Protocol API\EtherCAT Slave V2\EtherCAT Slave API\EtherCAT Slave V4\EtherCAT Slave V4 Protocol API
Protocol API 21 EN.pdf 10 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.7, Header, XML and Protocol API
Manual
Introduction 20/284
1.2.3.6 EtherCAT Slave Firmware Version V4.7

In the past, the application had to use several packets in order to set
Station Alias Address. Now the EtherCAT Slave firmware executes the
Station Alias Address handling. Starting with version 4.6, the firmware
savest he Station Alias Address (Second Station Address) non volatile and
afterwards the firmware sets it to the ESC register. As a result, the
application does not have to handle the Station Alias Address anymore
compared to earlier EtherCAT Slave firmware versions.
1.2.3.7 POWERLINK Controlled Node Firmware Versions V2 and V3

The POWERLINK Controlled Node firmware has been revised and
completed and is available in version V3 since the third quarter of 2017.
Do not use the POWERLINK Controlled Node V2.x for new applications.
For a new installation when creating or developing your application
program for the first time, use the POWERLINK Controlled Node firmware
V3. Already existing applications based on V2.x do not need to be
upgraded.
The reasons for upgrading are as follows:
• The development of the POWERLINK Controlled Node firmware V2 will
not be continued.
• Performance improvements
• IPV4 support according to EPSG specification
• Multiple ASnd
POWERLINK Controlled Node V3 is developed to fulfill the following
requirements:
• Support of netX 100-based products.
• Optimization of the internal stack structure to improve performance and
less memory space requirement.
• POWERLINK Controlled Node V3 uses the object dictionary V3
component, to achieve a common base with other Hilscher stacks.
• Applications, which used configuration database (inibatch.nxd) or
configuration API of POWERLINK Controlled Node V2, can be easily
migrated to V3 because these configuration mechanisms are supported
also for V3.
If you want to change in an existing system from the POWERLINK
Controlled Node firmware V2 to V3, note the following guidelines:
1. Using the same configuration project, SYCON.net V1.500 can configure
the POWERLINK Controlled Node firmware V2 as well as V3.
2. If the application program uses the API for object dictionary V2, the
application program must be adapted and the API for object dictionary
V3 must be used. The API of the object dictionary was changed
incompatible from V2 to V3 and may require additional effort if these
services are used.
3. Adjust the configuration of your POWERLINK Managing Node device.
Use the new updated XDD file in the configuration software of the
POWERLINK Managing Node for this: 00000044_CIFX RE PLS.xdd.
Introduction 21/284
4. Update the POWERLINK Controlled Node firmware in your device to
V3.
POWERLINK Controlled Node V2 POWERLINK Controlled Node V3
Firmware Firmware\CIFX\Outdated versions\PLS V2\ Firmware\CIFX\
cifxpls.nxf C010K000.nxf
Header Examples and API\0. Header\Firmware\ Examples and API\0. Header\Firmware\
POWERLINK Controlled Node V2\netX 100 based POWERLINK Controlled Node V3
XDD EDS\POWERLINK\Slave\V2\ EDS\POWERLINK\Slave\V3\
00000044_CIFX RE PLS.xdd 00000044_CIFX RE PLS.xdd
Protocol API Documentation\7. Programming Manuals\EN\ Documentation\7. Programming Manuals\EN\
3. Protocol API\POWERLINK Controlled Node V2\ 3. Protocol API\POWERLINK Controlled Node V3\
Powerlink Controlled Node Protocol API 12 EN.pdf POWERLINK Controlled Node V3 Protocol API 08 EN.pdf
Table 10: POWERLINK Controlled Node Firmware V2 and V3 on the Product DVD
1.2.4 Device Description Files PC Cards cifX

The Communication Solutions DVD EDS directory includes the device
description files for the PC Cards cifX. The device description file is
required to configure the used Master device. The systems Open
Modbus/TCP, AS-Interface, PROFIBUS MPI and VARAN do not use device
description files.
PC Cards cifX System File Name of the Device Description File
CIFX 50-RE, CC-Link IE Field Basic Slave 0x0352_CIFX RE CCIEBS_1_en.cspp
CIFX 50E-RE,
CIFX 50E-RE\ET, EtherCAT Slave For the EtherCAT Slave Firmware V2.5:
CIFX 70E-RE, Hilscher CIFX RE ECS V2.2.X.xml (or with extension DDF)
CIFX 70E-RE\MR, For the EtherCAT Slave Firmware with V4.6
CIFX 100EH- the Hilscher CIFX RE ECS V4.6.X.xml is provided.
RE\CUBE
Note! If the XML file Hilscher cifX RE ECS V2.2.x.xml is used/re-installed, the firmware
must be used/re-installed at the Version 2.5.x.
EtherNet/IP Adapter (Slave) HILSCHER CIFX-RE EIS V1.1.EDS

EtherNet/IP Scanner (Master) HILSCHER CIFX-RE EIM V1.0.eds
Note! The description files for the EtherNet/IP Master device is needed, when an
additional EtherNet/IP Master device shall communicate to a Hilscher EtherNet/IP
Master device via EtherNet/IP.
POWERLINK Controlled 00000044_CIFX RE PLS.xdd
Node/Slave
PROFINET IO-Device For the PROFINET IO Device Firmware V3.4:
GSDML-V2.3-HILSCHER-CIFX RE PNS-20130806.xml
For the PROFINET IO Device Firmware with V3.10
the GSDML-V2.32-HILSCHER-CIFX RE PNS-20160502.xml is
provided.
Sercos Slave SDDML#v3.0#Hilscher#CIFX_RE-FIXCFG_FSPIO#2014-01-08.xml,
SDDML#v3.0#Hilscher#CIFX_RE-VARCFG_FSPDRIVE#2014-01-08.xml
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.
Introduction 22/284
PC Cards cifX System File Name of the Device Description File
CIFX 50E-CCIES, CC-Link IE Field Slave 0x0352_CIFX.cspp
CIFX 70E-CCIES
CIFX 50-DP, PROFIBUS DP Slave HIL_0B69.GSD
CIFX 50-2DP,
CIFX 50E-DP,
CIFX 50E-2DP,
CIFX 70E-DP,
CIFX 70E-DP\MR
CIFX 50-2DP\CO, PROFIBUS DP-Slave HIL_0B69.GSD
CIFX 50E-2DP\CO CANopen-Slave CIFX CO COS.eds
CIFX 50-2DP\DN, PROFIBUS DP-Slave HIL_0B69.GSD
CIFX 50E-2DP\DN DeviceNet-Slave CIFX_DN_DNS.EDS
CIFX 50-CO, CANopen Slave CIFX CO COS.eds
CIFX 50-2CO,
CIFX 50E-CO,
CIFX 50E-2CO,
CIFX 70E-CO,
CIFX 70E-CO\MR
CIFX 50-2CO\DN, CANopen-Slave CIFX CO COS.eds
CIFX 50E- DeviceNet-Slave CIFX_DN_DNS.EDS
2CO\DN
CIFX 50-DN, DeviceNet Slave CIFX_DN_DNS.EDS
CIFX 50-2DN,
CIFX 50E-DN,
CIFX 50E-2DN,
CIFX 70E-DN,
CIFX 70E-DN\MR
CIFX 50-CC, CC-Link Slave 0x0352_CIFX-CCS_2.11_en.cspp,
CIFX 50E-CC CIFX\0x0352_CIFX-CCS_2.11_en.cspproj
Table 11: Device Description Files for PC Cards cifX
Introduction 23/284
1.3 Legal Notes

Copyright
© Hilscher Gesellschaft für Systemautomation mbH
All rights reserved.
The images, photographs and texts in the accompanying materials (in the
form of a user's manual, operator's manual, Statement of Work document
and all other document types, support texts, documentation, etc.) are
protected by German and international copyright and by international trade
and protective provisions. Without the prior written consent, you do not
have permission to duplicate them either in full or in part using technical or
mechanical methods (print, photocopy or any other method), to edit them
using electronic systems or to transfer them. You are not permitted to make
changes to copyright notices, markings, trademarks or ownership
declarations. Illustrations are provided without taking the patent situation
into account. Any company names and product designations provided in
this document may be brands or trademarks by the corresponding owner
and may be protected under trademark, brand or patent law. Any form of
further use shall require the express consent from the relevant owner of the
rights.
Important notes
Utmost care was/is given in the preparation of the documentation at hand
consisting of a user's manual, operating manual and any other document
type and accompanying texts. However, errors cannot be ruled out.
Therefore, we cannot assume any guarantee or legal responsibility for
erroneous information or liability of any kind. You are hereby made aware
that descriptions found in the user's manual, the accompanying texts and
the documentation neither represent a guarantee nor any indication on
proper use as stipulated in the agreement or a promised attribute. It cannot
be ruled out that the user's manual, the accompanying texts and the
documentation do not completely match the described attributes, standards
or any other data for the delivered product. A warranty or guarantee with
respect to the correctness or accuracy of the information is not assumed.
We reserve the right to modify our products and the specifications for such
as well as the corresponding documentation in the form of a user's manual,
operating manual and/or any other document types and accompanying
texts at any time and without notice without being required to notify of said
modification. Changes shall be taken into account in future manuals and do
not represent an obligation of any kind, in particular there shall be no right
to have delivered documents revised. The manual delivered with the
product shall apply.
Under no circumstances shall Hilscher Gesellschaft für Systemautomation
mbH be liable for direct, indirect, ancillary or subsequent damage, or for
any loss of income, which may arise after use of the information contained
herein.
Liability disclaimer
The hardware and/or software was created and tested by Hilscher
Gesellschaft für Systemautomation mbH with utmost care and is made
available as is. No warranty can be assumed for the performance or
flawlessness of the hardware and/or software under all application
Introduction 24/284
conditions and scenarios and the work results achieved by the user when
using the hardware and/or software. Liability for any damage that may have
occurred as a result of using the hardware and/or software or the
corresponding documents shall be limited to an event involving willful intent
or a grossly negligent violation of a fundamental contractual obligation.
However, the right to assert damages due to a violation of a fundamental
contractual obligation shall be limited to contract-typical foreseeable
damage.
It is hereby expressly agreed upon in particular that any use or utilization of
the hardware and/or software in connection with
• Flight control systems in aviation and aerospace;
• Nuclear fusion processes in nuclear power plants;
• Medical devices used for life support and
• Vehicle control systems used in passenger transport
shall be excluded. Use of the hardware and/or software in any of the
following areas is strictly prohibited:
• For military purposes or in weaponry;
• For designing, engineering, maintaining or operating nuclear systems;
• In flight safety systems, aviation and flight telecommunications systems;
• In life-support systems;
• In systems in which any malfunction in the hardware and/or software
may result in physical injuries or fatalities.
You are hereby made aware that the hardware and/or software was not
created for use in hazardous environments, which require fail-safe control
mechanisms. Use of the hardware and/or software in this kind of
environment shall be at your own risk; any liability for damage or loss due
to impermissible use shall be excluded.
Warranty
Hilscher Gesellschaft für Systemautomation mbH hereby guarantees that
the software shall run without errors in accordance with the requirements
listed in the specifications and that there were no defects on the date of
acceptance. The warranty period shall be 12 months commencing as of the
date of acceptance or purchase (with express declaration or implied, by
customer's conclusive behavior, e.g. putting into operation permanently).
The warranty obligation for equipment (hardware) we produce is 36
months, calculated as of the date of delivery ex works. The aforementioned
provisions shall not apply if longer warranty periods are mandatory by law
pursuant to Section 438 (1.2) BGB, Section 479 (1) BGB and Section 634a
(1) BGB [Bürgerliches Gesetzbuch; German Civil Code] If, despite of all
due care taken, the delivered product should have a defect, which already
existed at the time of the transfer of risk, it shall be at our discretion to
either repair the product or to deliver a replacement product, subject to
timely notification of defect.
The warranty obligation shall not apply if the notification of defect is not
asserted promptly, if the purchaser or third party has tampered with the
products, if the defect is the result of natural wear, was caused by
unfavorable operating conditions or is due to violations against our
operating regulations or against rules of good electrical engineering
Introduction 25/284
practice, or if our request to return the defective object is not promptly
complied with.
Costs of support, maintenance, customization and product care

Please be advised that any subsequent improvement shall only be free of
charge if a defect is found. Any form of technical support, maintenance and
customization is not a warranty service, but instead shall be charged extra.
Additional guarantees
Although the hardware and software was developed and tested in-depth
with greatest care, Hilscher Gesellschaft für Systemautomation mbH shall
not assume any guarantee for the suitability thereof for any purpose that
was not confirmed in writing. No guarantee can be granted whereby the
hardware and software satisfies your requirements, or the use of the
hardware and/or software is uninterruptable or the hardware and/or
software is fault-free.
It cannot be guaranteed that patents and/or ownership privileges have not
been infringed upon or violated or that the products are free from third-party
influence. No additional guarantees or promises shall be made as to
whether the product is market current, free from deficiency in title, or can be
integrated or is usable for specific purposes, unless such guarantees or
promises are required under existing law and cannot be restricted.
Confidentiality
The customer hereby expressly acknowledges that this document contains
trade secrets, information protected by copyright and other patent and
ownership privileges as well as any related rights of Hilscher Gesellschaft
für Systemautomation mbH. The customer agrees to treat as confidential all
of the information made available to customer by Hilscher Gesellschaft für
Systemautomation mbH and rights, which were disclosed by Hilscher
Gesellschaft für Systemautomation mbH and that were made accessible as
well as the terms and conditions of this agreement itself.
The parties hereby agree to one another that the information that each
party receives from the other party respectively is and shall remain the
intellectual property of said other party, unless provided for otherwise in a
contractual agreement.
The customer must not allow any third party to become knowledgeable of
this expertise and shall only provide knowledge thereof to authorized users
as appropriate and necessary. Companies associated with the customer
shall not be deemed third parties. The customer must obligate authorized
users to confidentiality. The customer should only use the confidential
information in connection with the performances specified in this
agreement.
The customer must not use this confidential information to his own
advantage or for his own purposes or rather to the advantage or for the
purpose of a third party, nor must it be used for commercial purposes and
this confidential information must only be used to the extent provided for in
this agreement or otherwise to the extent as expressly authorized by the
disclosing party in written form. The customer has the right, subject to the
obligation to confidentiality, to disclose the terms and conditions of this
agreement directly to his legal and financial consultants as would be
required for the customer's normal business operation.
Introduction 26/284
Export provisions
The delivered product (including technical data) is subject to the legal
export and/or import laws as well as any associated regulations of various
countries, especially such laws applicable in Germany and in the United
States. The products / hardware / software must not be exported into such
countries for which export is prohibited under US American export control
laws and its supplementary provisions. You hereby agree to strictly follow
the regulations and to yourself be responsible for observing them. You are
hereby made aware that you may be required to obtain governmental
approval to export, reexport or import the product.
1.4 Registered Trademarks

Windows® XP, Windows® Vista, Windows® 7, Windows® 8, Windows®
8.1 and Windows® 10 are registered trademarks of Microsoft Corporation.
Linux is a registered trademark of Linus Torvalds.
QNX is a registered trademark of QNX Software Systems, Ltd.
VxWorks is a registered trademark of Wind River Systems, Inc.
IntervalZero RTX™ is a trademark of IntervalZero.
Adobe-Acrobat® is a registered trademark of the Adobe Systems
Incorporated.
CANopen® is a registered trademark of CAN in AUTOMATION -
International Users and Manufacturers Group e.V (CiA), Nürnberg.
CC-Link and CC-Link IE Field are registered trademarks of Mitsubishi
Electric Corporation, Tokyo, Japan.
is a registered trademark of Mitsubishi Electric Corporation, Tokyo, Japan.
DeviceNet™ and EtherNet/IP™ are trademarks of ODVA (Open DeviceNet
Vendor Association, Inc).
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® and PROFINET® are registered trademarks of PROFIBUS &
PROFINET International (PI), Karlsruhe.
Sercos and Sercos interface are registered trademarks of Sercos
international e. V., Suessen, Germany.
PCI™, PCI EXPRESS® and PCIe® are trademarks or registered trademarks
of the Peripheral Component Interconnect Special Interest Group (PCI-
SIG).
All other mentioned trademarks are property of their respective legal
owners.
Introduction 27/284
1.4.1 EtherCAT Disclaimer

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 info@ethercat.org.
A summary over Vendor ID, Conformance test, Membership and Network
Logo can be found within the appendix section of this document under
section EtherCAT Summary over Vendor ID, Conformance test,
Membership and Network Logo on page 266.
1.5 Obligation to read and understand the Manual

Important!
 To avoid personal injury and to avoid property damage to your system
or to your PC card, you must read and understand all instructions in the
manual and all accompanying texts to your PC card, before installing
and operating your PC card.
 First read the Safety Instructions in the safety chapter.
 Obey to all Safety Messages in the manual.
 Keep the product DVD as ZIP file providing the product manuals.
1.6 Licenses
If a PC Card cifX is used as a Slave, neither for the firmware nor for the
configuration software SYCON.net a license is required.
Licenses will be required if the PC Card cifX is used with
• a firmware with master functionality*.
* The master license includes the PC Card cifX operating as master and
the license for the configuration software SYCON.net for the respective
cifX.
1.6.1 License Note about VARAN Client

In order to use the PC Card cifX with VARAN, you need a license which
you can acquire at the VNO (VARAN Bus-Nutzerorganisation, Bürmooser
Straße 10, A-5112 Lamprechtshausen, info@varan-bus.net) 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.
Safety 28/284
2 Safety
2.1 General Note
The documentation in the form of a user manual, an operating instruction
manual or other manual types, as well as the accompanying texts have
been created for the use of the products by educated personnel. When
using the products, all Safety Messages, Integrated Safety Messages,
Property Damage Messages and all valid legal regulations must be obeyed.
Technical knowledge is presumed. The user has to assure that all legal
regulations are obeyed.
2.2 Intended Use

The PC Cards cifX described in this user manual are PC cards for the Real-
Time Ethernet or fieldbus communication. Depending from the loaded
firmware, the Real-Time Ethernet or fieldbus systems listed in the following
table can be realized using the respective PC Card cifX.
PC Cards cifX Real-Time Ethernet System PC Cards cifX Fieldbus System
CIFX 50-RE, CC-Link IE Field Basic Slave CIFX 50-DP PROFIBUS DP Master,
CIFX 50E-RE, EtherCAT Master, CIFX 50E-DP, PROFIBUS DP Slave,
CIFX 50E-RE\ET, EtherCAT Slave CIFX 70E-DP, PROFIBUS MPI Device
CIFX 70E-RE, CIFX 70E-DP\MR
CIFX 70E-RE\MR, EtherNet/IP Scanner (Master),
EtherNet/IP Adapter (Slave) CIFX 50-2DP, PROFIBUS DP Master,
CIFX 100EH- CIFX 50E-2DP PROFIBUS DP Slave
RE\CUBE Open-Modbus/TCP
CIFX 50-2DP\CO, PROFIBUS DP Master,
POWERLINK-Controlled-Node/Slave CIFX 50E-2DP\CO PROFIBUS DP Slave,
PROFINET IO-Controller (Master), CANopen Master,
PROFINET IO-Device (Slave) CANopen Slave
Sercos Master, CIFX-50-2DP\DN, PROFIBUS DP Master,
Sercos Slave CIFX 50E-2DP\DN PROFIBUS DP Slave,
VARAN-Client (Slave) DeviceNet Master,
DeviceNet Slave
CIFX 50E-CCIES, CC-Link IE Field Slave CIFX 50-CO CANopen Master,
CIFX 70E-CCIES CIFX 50-2CO CANopen Slave
CIFX 50E-CO,
CIFX 50E-2CO,
CIFX 70E-CO,
CIFX 70E-CO\MR
CIFX 50-2CO\DN, CANopen Master,
CIFX 50E-2CO\DN CANopen Slave
DeviceNet Master,
DeviceNet Slave
CIFX 50-DN DeviceNet Master,
CIFX 50-2DN DeviceNet Slave
CIFX 50E-DN,
CIFX 50E-2DN,
CIFX 70E-DN,
CIFX 70E-DN\MR
CIFX 50-2ASM, AS-Interface Master
CIFX 50E-2ASM
CIFX 50-CC CC-Link Slave
CIFX 50E-CC
Table 12: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby
Safety 29/284
2.3 Personnel Qualification

The PC Card cifX 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 Safety Instructions

To ensure your own personal safety and to avoid personal injury, you
necessarily must read, understand, and comply with the safety instructions
and safety messages in this manual before you install and operate your PC
card cifX.
For cases if both, personal injury as well as property damage (damage of
equipment or device) may occur together, you find the safety instructions in
this section.
2.4.1 Electrical Shock Hazard

The danger of a lethal electrical shock caused by parts with more than 50V
may occur if you open the PC cabinet to install the PC Card cifX.
• HAZARDOUS VOLTAGE is present inside of the PC or of the connec-
ting device, into which the PC Card cifX is integrated. Strictly obey to all
safety rules provided by the device’s manufacturer in the documentation!
• First disconnect the power plug of the PC or of the connecting device,
before you open the cabinet.
• Make sure, that the power supply is off at the PC or at the connecting
device.
• Open the PC cabinet and install or remove the PC Card cifX only after
disconnecting power.
Reference Safety [S2]
Safety 30/284
2.4.2 Communication Stop during Firmware Update or Configuration

Download
If you want to perform either a firmware update (as a download) or a
configuration download, both via the corresponding Master DTM in
SYCON.net, be aware of the following:
• Together with the firmware download, an automated reset to the device
is performed that will interrupt all network communication and all
established connections will drop.
• If you download the configuration during bus operation, the
communication between master and slaves is stopped.
Possible faulty System Operation

• An unpredictable and unexpected behavior of machines and plant
components may cause personal injury and property damage.
 Stop the application program, before starting the firmware update or
before downloading the configuration.
 Make sure that your equipment operates under conditions that prevent
personal injury or property damage. All network devices should be
placed in a fail-safe mode, before starting the firmware update or before
downloading a configuration.
Loss of Device Parameters, Overwriting of Firmware

• Both the firmware download and the configuration download erase the
configuration data base. The firmware download overwrites the existing
firmware in the network device.
 To complete the firmware update and to make the device operable
again, re-load the configuration after the firmware update has been
finished.
For devices with Ethernet technology
• Device parameters that have been saved volatile, e. g. as the
temporarily set IP address parameters, are getting lost during the reset.
 In order to prevent loss of configuration data, make sure that your
project configuration data are saved non-volatile, before you initiate a
firmware update or download the configuration.
2.4.3 Mismatching System Configuration

Mismatching system configuration loaded into the device could result in
faulty data mapping in the application program and thus unexpected
equipment operation may cause personal injury or damage of equipment.
 In the device use only a configuration suitable for the system.
Safety 31/284
2.5 Property Damage

To avoid system damage and device damage to the PC card cifX, you
necessarily must read, understand, and comply with the safety instructions
and safety messages in this manual before you install and operate the PC
card cifX.
2.5.1 Exceeding permissible Supply Voltage

To avoid device damage due to high supply voltage to your PC Card cifX,
you must observe the following instructions. These instructions apply to all
PC Cards cifX described in this manual.
The PC Card cifX may only be operated with the specified supply voltage.
Make sure that the limits of the permissible range for the supply voltage are
not exceeded. A supply voltage above the upper limit can cause severe
damage to the PC Card cifX! A supply voltage below the lower limit can
cause malfunction in the PC Card cifX. The permissible range for the
supply voltage is defined by the tolerances specified in this manual.
For the PC cards listed hereafter adhere specifically: The PC Card cifX
• CIFX 50-RE
• CIFX 50-DP, CIFX 50-2DP, CIFX 50-2DP\CO, CIFX 50-2DP\DN,
CIFX 50-CO, CIFX 50-2CO, CIFX 50-2CO\DN,
CIFX 50-DN, CIFX 50-2DN,
CIFX 50-2ASM, CIFX 50-CC
• CIFX 50E-RE, CIFX 50E-RE\ET
• CIFX 50E-CCIES,
• CIFX 50E-DP, CIFX 50E-2DP, CIFX 50E-2DP\CO, CIFX 50E-2DP\DN,
CIFX 50E-CO, CIFX 50E-2CO, CIFX 50E-2CO\DN,
CIFX 50E-DN, CIFX 50E-2DN, CIFX 50E-2ASM,
CIFX 50E-CC
• CIFX 70E-RE, CIFX 70E-RE\MR, CIFX 100EH-RE\CUBE
• CIFX 70E-CCIES
• CIFX 70E-DP, CIFX 70E-DP\MR
• CIFX 70E-CO, CIFX 70E-CO\MR
• CIFX 70E-DN, CIFX 70E-DN\MR
may not be powered by a 5V supply voltage! The PC Card cifX may only be
powered by a 3.3 V dc ±5 % supply voltage.
The data on the mandatory supply voltage for the PC Cards cifX described
in this manual you find in section Power Supply and Host Interface on
page 44. There the required and permitted supply voltage is provided by
device type inclusively the permitted tolerance range.
Safety 32/284
2.5.2 Exceeding permissible Signaling Voltage

To avoid device damage due to high signal voltage to your PC Card cifX,
you must observe the following instructions. These instructions apply to all
PC Cards cifX described in this manual.
• All I/O signal pins at the PC Card cifX tolerate only the specified
signaling voltage!
• Operating of your PC Card cifX with a signaling voltage other than the
specified signaling voltage may lead to severe damage to the PC Card
cifX!
The data on the mandatory signaling voltage for the PC Cards cifX
described in this manual you find in the section Power Supply and Host
Interface on page 44. There the required and permitted signaling voltage
is provided by device type.
2.5.3 Electrostatically sensitive Devices

This equipment is sensitive to electrostatic discharge, which cause internal
damage and affect normal operation. Therefore adhere to the necessary
safety precautions for components that are vulnerable with electrostatic
discharge if you install or replace your device. Follow the guidelines listed
hereafter when you handle this equipment:
• Touch a grounded object to discharge potential static.
• Wear an approved grounding wriststrap.
• Do not touch connectors or pins on the PC Card cifX.
• 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 [S3]
Safety 33/284
2.5.4 Power Disconnect while downloading Firmware or

Configuration
If during the process of downloading a firmware or configuration
• the power supply to a PC with the software application is interrupted,
• or the power supply to the PC card cifX is interrupted,
• or a reset to the PC card cifX is performed,
this may lead to the following consequences:
Loss of Device Parameters, Firmware Corruption

• The firmware download or the configuration download will be interrupted
and remains incomplete.
• The firmware or the configuration database will be corrupted and device
parameters will be lost.
• Device damage may occur as the PC card cifX cannot be rebooted.
Whether these consequences occur depends on when the power
disconnect occurs during the download.
 During configuration download process, do not interrupt the power
supply to the PC, or to the PC card cifX and do not perform a reset!
Otherwise you might be forced to return your PC card cifX for repair.
Power Drop during Write and Delete Accesses in the File System
The FAT file system in the netX firmware is subject to certain limitations in
its operation. Write and delete accesses in the file system (firmware
update, configuration download etc.) can destroy the FAT (File Allocation
Table) if the accesses cannot be completed if the power drops. Without a
proper FAT, a firmware may not be found and cannot be started.
Make sure that the power supply to the device is not interrupted during
write and delete accesses in the file system (firmware update, configuration
download, etc.).
2.5.5 Exceeding the maximum Number of allowed Write/Delete

Accesses
This device uses a serial Flash chip for storing remanent data, such as
firmware, configuration, etc. This chip allows a maximum of 100 000
write/delete accesses which is sufficient for a standard device operation.
Writing/deleting the chip excessively (e.g. in order to change configuration
or name of station) will exceed the maximum number of allowed
write/delete accesses and, thus, result in damage to the device. If, e.g., the
configuration is changed every hour, the maximum number will be reached
after 11.5 years. If, e.g., it is changed every minute, the maximum number
will already be reached after approx. 69 days.
Avoid exceeding the maximum number of allowed write/delete accesses by
excessive writing.
Safety 34/284
2.5.6 Invalid Firmware

Loading invalid firmware files could render your device unusable.
 Only download firmware files to your PC Card cifX that are valid for this
device.
Otherwise you may be forced to return your device for repair.
2.5.7 Information and Data Security

Take all usual measures for information and data security, in particular for
PC Cards cifX with Ethernet technology. Hilscher explicitly points out that a
device with access to a public network (Internet) must be installed behind a
firewall or only be accessible via a secure connection such as an encrypted
VPN connection. Otherwise the integrity of the device, its data, the
application or system section is not safeguarded.
Hilscher can assume no warranty and no liability for damages due to
neglected security measures or incorrect installation.
Safety 35/284
2.6 Labeling of Safety Messages

• The Section Safety Messages at the beginning of a chapter are
pinpointed particularly and highlighted by a signal word according to the
degree of endangerment. The type of danger is specified by the safety
message text and optionally by a specific safety sign.
• The Integrated Safety Messages within an instruction description are
highlighted with a signal word according to the degree of endangerment.
The type of danger is specified by the safety message text.
Signal Word Meaning (International) Meaning (USA)
Indicates a direct hazard with high risk, which Indicates a hazardous situation which if not
will have a consequence of death or grievous avoided, will result in death or serious injury.
bodily harm if it is not avoided.
Indicates a possible hazard with medium Indicates a hazardous situation which if not
risk, which will have a consequence of death avoided, could result in death or serious injury.
or (grievous) bodily harm if it is not avoided.
Indicates a minor hazard with medium risk, Indicates a hazardous situation which if not
which could have a consequence of minor or avoided, may result in minor or moderate
moderate bodily harm if it is not avoided. Injury.
Indicates a property damage message. Indicates a property damage message.
Table 13: Signal Words
Safety Sign USA Warning or Principle

Warning of lethal electrical shock
Principle: Disconnect the power plug
Warning on damages by electrostatic discharge
Warning of device damage, for example due to exceedingly high supply voltage or
exceedingly high signaling voltage.
Warning of device damage, for example due to power disconnect during firmware
update or configuration download, exceeding the maximum number of allowed
write/delete accesses or due to invalid or non-authorized firmware.
Table 14: Safety Signs
Note: The ANSI Z535.6 standard specifies in section 4.8: "Messages about
hazards that could result in both, physical injury and property damage are
considered safety messages, not property damage messages." Thus
depending of the type of danger and its consequences, warning messages
marked by a signal word DANGER, WARNING or CAUTION may include
both, messages on physical injury and property damage.
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.6 standard, refer to safety reference [S1].
2.7 References Safety
[S1] ANSI Z535.6-2011 American National Standard for Product Safety Information in
Product Manuals, Instructions, and Other Collateral Materials
[S2] DIN EN 62368-1: 2016-05, Audio/video, information and communication technology
equipment - Part 1: Safety requirements (IEC 62368-1: 2014, modified +
Cor.:2015); German version EN 62368-1: 2014 + AC: 2015
[S3] EN 61340-5-1 and EN 61340-5-2 as well as IEC 61340-5-1 and IEC 61340-5-2
Descriptions and Requirements 36/284
3 Descriptions and Requirements

3.1 Description
The PC Cards cifX are communication interfaces of the cifX product family
of Hilscher on the basis of the communication controller netX 100 for the
Real-Time Ethernet or fieldbus communication. Depending of the loaded
firmware, the protocol specific PC Card cifX proceeds the communication of
the corresponding Real-Time Ethernet or fieldbus system.
The used Real-Time Ethernet systems are: The used fieldbus systems
are:
 CC-Link IE Field Basic Slave  PROFIBUS DP Master
 CC-Link IE Field Slave  PROFIBUS DP Slave
 EtherCAT Master  PROFIBUS MPI Device
 EtherCAT Slave  CANopen Master
 EtherNet/IP Scanner (Master)  CANopen Slave
 EtherNet/IP Adapter (Slave)  DeviceNet Master
 Open-Modbus/TCP  DeviceNet Slave
 POWERLINK-Controlled-Node/Slave  AS-Interface Master
 PROFINET IO-Controller (Master)  CC-Link Slave
 PROFINET IO-Device (Slave)
 Sercos Master
 Sercos Slave
 VARAN Client (Slave)
The PC Card cifX handles the complete data exchange between the
connected Ethernet or fieldbus devices and the PC. The data exchange is
proceeded via dual-port memory.
3.2 PC Cards PCI CIFX 50-XX

PC Card cifX Description
PC Cards PCI with integrated Ethernet or fieldbus interface
Real-Time Ethernet
CIFX 50-RE Real-Time Ethernet Master or Slave.
PROFIBUS
CIFX 50-DP PROFIBUS DP Master or Slave and PROFIBUS MPI Device
CANopen
CIFX 50-CO CANopen Master or Slave
DeviceNet
CIFX 50-DN DeviceNet Master or Slave
CC-Link
CIFX 50-CC CC-Link Slave
Table 15: PC Cards PCI CIFX 50-XX
3.3 PC Cards PCI (2 Channels) CIFX 50-2XX, CIFX 50-2XX\XX

PC Cards PCI with two integrated fieldbus interfaces (2 Channels)
PROFIBUS
CIFX 50-2DP 2 x PROFIBUS DP Master or Slave
CIFX 50-2DP\CO Channel X1: PROFIBUS DP Master or Slave, channel X2: CANopen Master or Slave
CIFX 50-2DP\DN Channel X1: PROFIBUS DP Master or Slave, channel X2: DeviceNet Master or Slave
CANopen
CIFX 50-2CO 2 x CANopen Master or Slave
CIFX 50-2CO\DN Channel X1: CANopen Master or Slave, channel X2: DeviceNet Master or Slave
DeviceNet
CIFX 50-2DN 2 x DeviceNet Master or Slave
AS-Interface
CIFX 50-2ASM 2 x AS-Interface Master
CIFX 50E-2ASM 2 x AS-Interface Master
Table 16: PC Cards PCI (2 Channels) CIFX 50-2XX, CIFX 50-2XX\XX
3.4 PC Cards PCI Express CIFX 50E-XX, CIFX 70E-XX, CIFX

100EH-RE\CUBE
PC Cards PCI Express with integrated Ethernet or fieldbus interface
Real-Time Ethernet
CIFX 50E-RE or Real-Time Ethernet Master or Slave
CIFX 50E-RE\ET Note: The PC card CIFX 50E-RE\ET can be used in an enlarged temperature rage
from -20°C to +70 °C.
CIFX 70E-RE, Low Profile PCI Express Real-Time-Ethernet Master or Slave
CIFX 70E-RE\MR (Low Profile PCIe with RTE)
CIFX 100EH- Real-Time Ethernet Master or Slave, (low-profile card) exclusively for the installing in KEBA
RE\CUBE KeControl industry PCs series CP 3XX (Cube).
CC-Link IE Field Slave
CIFX 50E-CCIES CC-Link IE Field Slave
CIFX 70E-CCIES Low Profile PCI Express CC-Link IE Field Slave (Low Profile PCIe)
PROFIBUS
CIFX 50E-DP PROFIBUS DP Master or Slave and PROFIBUS MPI Device
CIFX 70E-DP, Low Profile PCI Express PROFIBUS DP Master or Slave
CIFX 70E-DP\MR and PROFIBUS MPI Device (Low Profile PCIe with PROFIBUS)
CANopen
CIFX 50E-CO CANopen Master or Slave
CIFX 70E-CO, Low Profile PCI Express CANopen Master or Slave
CIFX 70E-CO\MR (Low Profile PCIe with CANopen)
DeviceNet
CIFX 50E-DN DeviceNet Master or Slave
CIFX 70E-DN, Low Profile PCI Express DeviceNet Master or Slave
CIFX 70E-DN\MR (Low Profile PCIe with DeviceNet)
CC-Link
CIFX 50E-CC CC-Link Slave
Table 17: PC Cards PCI Express CIFX 50E-XX, CIFX 70E-XX
Note: The PC cards CIFX 70E-RE\MR, CIFX 70E-DP\MR, CIFX 70E-
CO\MR and CIFX 70E-DN\MR additionally are equipped with an MRAM
(128Kbyte = 64K Words). For further information refer to section PC Cards
cifX with additional MRAM on page 42.
3.5 PC Cards PCI Express (2 Channels) CIFX 50E-2XX, CIFX

50E-2XX\XX
PC Cards PCI Express with two integrated fieldbus interfaces (2 Channels)
PROFIBUS
CIFX 50E-2DP 2 x PROFIBUS DP Master or Slave
CIFX 50E-2DP\CO Channel X1: PROFIBUS DP Master or Slave, channel X2: CANopen Master or Slave
CIFX 50E-2DP\DN Channel X1: PROFIBUS DP-Master or Slave, channel X2: DeviceNet Master or Slave
CANopen
CIFX 50E-2CO 2 x CANopen-Master or Slave
CIFX 50E-2CO\DN Channel X1: CANopen Master or Slave, channel X2: DeviceNet Master or Slave
DeviceNet
CIFX 50E-2DN 2 x DeviceNet Master or Slave
Table 18: PC Cards PCI Express (2 Channels) CIFX 50E-2XX, CIFX 50E-2XX\XX
3.6 The Function „Slot Number (Card ID)“

Device revisions equipped with a Rotary Switch Slot Number (Card ID)
are listed separately in section Hardware: PC Cards cifX on page 10 in
Table 2.
The Slot Number (Card ID) must be set at the PC card cifX using the
Rotary Switch Slot Number (Card ID). The Slot Number (Card ID) will
serve to distinguish PC cards cifX from each other clearly, especially if
several PC cards cifX are installed into the very same PC. The application
program requests the Slot Number (Card ID) from the PC card cifX via the
cifX Device Driver.
For further information refer to section Rotary Switch for Slot Number
(Card ID) on page 141.
3.6.1 Requirements „Slot Number (Card ID)“

For the application program is able to identify a PC card cifX via its Slot
Number (Card ID) explicitly and to distinguish it from other PC cards cifX in
the PC, for device revisions equipped with a Rotary Switch for Slot
Number (Card ID) the required versions of the firmware, the driver, the
bootloader and the SYCON.net setup must be used:
PC Cards with one Channel:
PC Card cifX From Hardware Firmware File Protocol From Firmware
Revision Version
CIFX 50-RE, 3 C020Y000.NXF CC-Link IE Field-Basic-Slave 1.1
CIFX 50E-RE, 1 CIFXECM.NXF EtherCAT-Master 4.3 (V4)
CIFX 50E-RE\ET, 4
CIFX 70E-RE, 1 CIFXECM.NXF EtherCAT Master 2.4.3.x
CIFX 70E-RE\MR, 1 CIFXECS.NXF EtherCAT-Slave 4.5 (V4)
CIFX 100EH- 1 CIFXECS.NXF EtherCAT Slave 2.5.5
RE\CUBE 1 CIFXEIM.NXF EtherNet/IP Scanner 2.2.1
CIFXEIS.NXF EtherNet/IP Adapter 2.3.29
CIFXOMB.NXF Open-Modbus/TCP 2.3.3
CIFXPLS.NXF POWERLINK Controlled Node 2.1.19
C010C000.NXF PROFINET IO-Controller 3.2 (V3)
CIFXPNM.NXF PROFINET IO Controller 2.3
CIFXPNS.NXF PROFINET IO Device 3.3.6 (V3)
CIFXS3M.NXF Sercos Master 2.0.9
CIFXS3S.NXF Sercos Slave 3.0.8
CIFXVRS.NXF VARAN Client 1.0
CIFX 50E-CCIES, 1 C020X000.NXF CC-Link IE Field Slave 1.1
CIFX 70E-CCIES
CIFX 50-DP, 5 CIFXDPM.NXF PROFIBUS DP Master 2.3
CIFX 50E-DP, 5 CIFXDPS.NXF PROFIBUS DP Slave 2.3
CIFX 70E-DP, 1
CIFX 70E-DP\MR 1 CIFXMPI.NXF PROFIBUS MPI Device 2.2.5
CIFX 50-CO, 5 CIFXCOM.NXF CANopen Master 2.3
CIFX 50E-CO, 4
CIFX 70E-CO, 1 CIFXCOS.NXF CANopen Slave 2.3
CIFX 70E-CO\MR 1
CIFX 50-DN, 5 CIFXDNM.NXF DeviceNet Master 2.2
CIFX 50E-DN, 4 CIFXDNS.NXF DeviceNet Slave 2.2
CIFX 70E-DN, 1
CIFX 70E-DN\MR 1
CIFX 50-CC, 2 CIFXCPS.NXF CC-Link Slave 2.4
CIFX 50E-CC 2
Table 19: Firmware Versions for the Function Slot Number (Card ID), (for 1 Channel
Systems)

Revision Version
CIFX 50-2DP, 1 CIFX2DPM.NXF PROFIBUS DP Master, 2 Channels 1.0 (new version
CIFX 50E-2DP counting)
CIFX2DPS.NXF PROFIBUS DP Slave, 2 Channels 1.0 (new version
counting)
C0201020.NXF PROFIBUS DP-Master, 1 Channel 1.1
+ PROFIBUS DP Slave, 1 Channel
CIFX 50-2DP\CO, 1 C0201040.NXF PROFIBUS DP Master, 1 Channel 1.0
CIFX 50E-2DP\CO + CANopen Master, 1 Channel
C0202050.NXF PROFIBUS DP Slave, 1 Channel 1.0
+ CANopen Slave, 1 Channel
CIFX 50-2DP\DN, 1 C0201060.NXF PROFIBUS DP Master, 1 Channel 1.0
CIFX 50E-2DP\DN + DeviceNet Master, 1 Channel
+ DeviceNetSlave, 1 Channel
CIFX 50-2CO, 1 C0204040.NXF CANopen Master, 2 Channels 1.0
CIFX 50E-2CO
C0205050.NXF CANopen Slave, 2 Channels 1.0
C0204050.NXF CANopen Master, 1 Channel 1.1
CIFX 50-2CO\DN, 1 C0204060.NXF CANopen Master, 1 Channel 1.0
CIFX 50E-2CO\DN + DeviceNet Master, 1 Channel
C0205070.NXF CANopen Slave, 1 Channel 1.0
+ DeviceNet Slave, 1 Channel
CIFX 50-2DN, 1 C0206060.NXF DeviceNet Master, 2 Channels 1.0
CIFX 50E-2DN C0207070.NXF DeviceNet Slave, 2 Channels 1.0
C0206070.NXF DeviceNet-Master, 1 Channel 1.2
+ DeviceNet-Slave, 1 Channel
CIFX 50-2ASM, 2 CIFX2ASM.NXF AS-Interface Master, 2 Channels 2.1
CIFX 50E-2ASM 2
Table 20: Firmware Versions for the Function Slot Number (Card ID) (for 2 Channel
Systems)
Driver and Software Version or higher

cifX Device Driver cifX Device Driver Setup.exe 0.95x
SYCON.net SYCONnet netX setup.exe V1.201
Table 21: Versions Driver, Bootloader and SYCON.net for Function Slot Number (Card ID)
• The cifX Device Driver versions 0.950 and higher identify PC cards cifX
alternatively via its Slot Number (Card ID) if this is supported by the
hardware.
• The cifX Device Driver up to version 0.94x identifies PC cards cifX via
its device and serial number. For the device exchange service
respectively a manual intervention is required.
3.7 The Function „DMA Mode“

Device revisions which provide DMA Mode are listed separately in section
Hardware: PC Cards cifX on page 10 in Table 2.
Note: The functions Slot Number (Card ID) and DMA Mode are in
technical view independently from each other.
The DMA Mode is activated via the device driver cifX Device Driver.
For further information refer to the user manual Software Installation for
the PC Cards cifX in section Activating DMA Mode in the cifX Device Driver
Setup.
3.7.1 Requirements „DMA Mode“

For device revisions providing the DMA Mode the required versions of the
firmware, the driver and the SYCON.net setup must be used:
PC Cards with one Channel:

Revision Version
CIFX 50-RE, 1 C020Y000.NXF CC-Link IE Field-Basic-Slave 1.1
CIFX 50E-RE, 1 CIFXECM.NXF EtherCAT-Master 4.3 (V4)
CIFX 50E-RE\ET, 4
CIFX 70E-RE, 1 CIFXECM.NXF EtherCAT-Master 2.4.6 (V2)
CIFX 70E-RE\MR, 1 CIFXECS.NXF EtherCAT-Slave 4.5 (V4)
CIFX 100EH- 1 CIFXECS.NXF EtherCAT-Slave 2.5.5 (V2)
RE\CUBE 1 CIFXEIM.NXF EtherNet/IP Scanner 2.2
CIFXEIS.NXF EtherNet/IP Adapter 2.3
CIFXOMB.NXF Open-Modbus/TCP 2.4
CIFXPLS.NXF POWERLINK Controlled Node 2.1.24
C010C000.NXF PROFINET IO-Controller 3.2 (V3)
CIFXPNM.NXF PROFINET IO-Controller 2.3 (V2)
CIFXPNS.NXF PROFINET IO Device 3.4 (V3)
CIFXS3M.NXF Sercos Master 2.0.15
CIFXS3S.NXF Sercos Slave 3.0.15
CIFXVRS.NXF VARAN Client 1.0
CIFX 50E-CCIES, 1 C020X000.NXF CC-Link IE Field Slave 1.1
CIFX 70E-CCIES
CIFX 50-DP, 1 CIFXDPM.NXF PROFIBUS DP Master 2.3
CIFX 50E-DP, 4 CIFXDPS.NXF PROFIBUS DP Slave 2.3
CIFX 70E-DP, 1
CIFX 70E-DP\MR 1 CIFXMPI.NXF PROFIBUS MPI Device not supported
CIFX 50-CO, 1 CIFXCOM.NXF CANopen Master 2.3
CIFX 50E-CO, 4 CIFXCOS.NXF CANopen Slave 2.3
CIFX 70E-CO, 1
CIFX 70E-CO\MR 1
CIFX 50-DN, 1 CIFXDNM.NXF DeviceNet Master 2.2
CIFX 50E-DN, 4 CIFXDNS.NXF DeviceNet Slave 2.2
CIFX 70E-DN, 1
CIFX 70E-DN\MR 1
CIFX 50-CC, 1 CIFXCCS.NXF CC-Link Slave 2.4
CIFX 50E-CC 3
Table 22: Firmware Versions for the DMA Mode (for 1 Channel Systems)

Revision Version
CIFX 50-2DP, 1 CIFX2DPM.NXF PROFIBUS DP Master, 2 Channels 1.0 (new version
CIFX 50E-2DP counting)
CIFX2DPS.NXF PROFIBUS DP Slave, 2 Channels 1.0 (new version
counting)
C0201020.NXF PROFIBUS DP-Master, 1 Channel 1.1

+ PROFIBUS DP Slave, 1 Channel
CIFX 50-2DP\CO, 1 C0201040.NXF PROFIBUS DP Master, 1 Channel 1.0
CIFX 50E-2DP\CO + CANopen Master, 1 Channel
CIFX 50-2DP\DN, 1 C0201060.NXF PROFIBUS DP Master, 1 Channel 1.0
CIFX 50E-2DP\DN + DeviceNet Master, 1 Channel
+ DeviceNetSlave, 1 Channel
CIFX 50-2CO, 1 C0204040.NXF CANopen Master, 2 Channels 1.0
CIFX 50E-2CO
C0205050.NXF CANopen Slave, 2 Channels 1.0
C0204050.NXF CANopen Master, 1 Channel 1.1
CIFX 50-2CO\DN, 1 C0204060.NXF CANopen Master, 1 Channel 1.0

CIFX 50E-2CO\DN + DeviceNet Master, 1 Channel
C0205070.NXF CANopen Slave, 1 Channel 1.0
+ DeviceNet Slave, 1 Channel
CIFX 50-2DN, 1 C0206060.NXF DeviceNet Master, 2 Channels 1.0
CIFX 50E-2DN C0207070.NXF DeviceNet Slave, 2 Channels 1.0
C0206070.NXF DeviceNet-Master, 1 Channel 1.2
+ DeviceNet-Slave, 1 Channel
CIFX 50-2ASM, 2 CIFX2ASM.NXF AS-Interface Master, 2 Channels 2.1
CIFX 50E-2ASM 4
Table 23: Firmware Versions for the DMA Mode (for 2 Channel Systems)
Driver and Software Version or higher

cifX Device Driver cifX Device Driver Setup.exe 0.95x
SYCON.net SYCONnet netX setup.exe V1.201
Table 24: Versions Driver and SYCON.net for the DMA Mode
3.8 PC Cards cifX with additional MRAM

The PC cards CIFX 70E-XX\MR (CIFX 70E-RE\MR, CIFX 70E-DP\MR,
CIFX 70E-CO\MR and CIFX 70E-DN\MR) are identical to the PC cards
CIFX 70E-XX and work with the same firmware. However, the PC cards
CIFX 70E-XX\MR have an additional memory module for storing remanent
data, MRAM with 128Kbyte (= 64K words). Using the cifX Device Driver
(from Version 1.1.1.0) access from the application program to this memory
is possible and it can be used as a remanent memory for the host system.
3.9 System Requirements

3.9.1 Slot for the PC Cards cifX PCI, PCIe and Low Profile PCIe
PC with slot (3.3 V) for PC cards cifX PCI, PCI Express and Low Profile PCI
Express:
PC Cards cifX PCI Bus Slot
[Pins]
CIFX 50-RE CIFX 50-DN 124 PCI slot (3.3 V)
CIFX 50-DP CIFX 50-2DN
CIFX 50-2DP CIFX 50-2ASM
CIFX 50-2DP\CO CIFX 50-CC
CIFX 50-2DP\DN
CIFX 50-CO
CIFX 50-2CO
CIFX 50-2CO\DN
CIFX 50E-RE CIFX 70E-RE 36 PCI Express x1 slot (3.3 V),
CIFX 50E-RE\ET CIFX 70E-RE\MR
x1 1 = One Lane [bus spec 3]
CIFX 50E-CCIES CIFX 70E-CCIES
CIFX 50E-DP CIFX 70E-DP
CIFX 50E-2DP CIFX 70E-DP\MR
CIFX 50E-2DP\CO CIFX 70E-CO
CIFX 50E-2DP\DN CIFX 70E-CO\MR
CIFX 50E-CO CIFX 70E-DN
CIFX 50E-2CO CIFX 70E-DN\MR
CIFX 50E-2CO\DN
CIFX 50E-DN
CIFX 50E-2DN
CIFX 50E-2ASM
CIFX 50E-CC
Device Damage!
The PC card CIFX 100EH-RE\CUBE may not be installed in standard PCs.
The pin assignment of the PCI Express bus does not meet the standard [bus spec 3]. By consequence malfunction
can occur at the PCI express bus.
Install the PC card CIFX 100EH-RE\CUBE exclusively in KEBA KeControl industry PCs series CP 3XX (Cube).
CIFX 100EH-RE\CUBE 64 PCI Express x4 slot (3.3 V) ,
x41 = Four Lane
In the PCI Express x4 slot only lane 0 is used. For further details
refer to section Pin Assignment for PCI Express Bus CIFX
100EH-RE\CUBE on page 146.
Table 25: Slot for the PC Cards cifX PCI, PCIe and Low Profile PCIe
1 The terms "x1" or "x4“ refer to the convention of the PCI Express specifications
[bus spec 3] to the number of lanes in the slot.
3.9.2 Power Supply and Host Interface

For the power supply and the host interface used for the PC cards cifX PCI,
PCIe and Low Profile PCIe you must observe the following requirements:
PC Cards cifX Supply Voltage Signaling Voltage Host Interface
Host Interface (PCI slot)
CIFX 50-RE CIFX 50-DN +3.3 V dc ±5 %/ Max. 1 A 5 V or 3.3 V PCI
CIFX 50-DP CIFX 50-2DN
CIFX 50-2DP, CIFX 50-CC
CIFX 50-2DP CIFX 50-2ASM
CIFX 50-2DP\CO
CIFX 50-2DP\DN
CIFX 50-CO
CIFX 50-2CO
CIFX 50-2CO\DN
CIFX 50E-RE CIFX 70E-RE +3.3 V dc ±5 %/ Max. 1 A PCIe-compatible PCI Express
CIFX 50E-RE\ET CIFX 70E-RE\MR
CIFX 50E-CCIES CIFX 70E-CCIES
CIFX 50E-DP CIFX 70E-DP
CIFX 50E-2DP CIFX 70E-DP\MR
CIFX 50E-2DP\CO CIFX 70E-CO
CIFX 50E-2DP\DN CIFX 70E-CO\MR
CIFX 50E-CO CIFX 70E-DN
CIFX 50E-2CO CIFX 70E-DN\MR
CIFX 50E-2CO\DN
CIFX 50E-DN
CIFX 50E-2DN
CIFX 50E-2ASM
CIFX 50E-CC
CIFX 100EH-RE\CUBE
Table 26: Requirements Power Supply and Host Interface for PC Cards cifX PCI, PCIe Low
Profile PCIe
The data in the Table 26 above have the following meaning:

Supply Voltage
The required and permissible supply voltage at the PC card cifX PCI, PCIe
and Low Profile PCIe.
Note: To ensure that the compatibility between different systems is guaran-

teed, providing a maximum of 1 A (for +3.3 VDC ±5 %) is recommended.
The typical current consumption depends on the type of the PC card cifX.
For detailed values on the typical current consumption see section
Technical Data PC Cards cifX on page 147.
Signaling Voltage Host Interface
The required or tolerated signaling voltage at the I/O signal pins at the PCI
bus of the PC cards cifX PCI or at the PCI express bus of the PC cards cifX
PCIe and Low Profile PCIe.
Host Interface (PCI slot) Type of the host interface
3.9.3 Operating Temperature Range for UL Certificate

The UL certificate for the PC cards cifX is valid for the range 0°C to +55°C
(for CIFX 100EH-RE 0°C to +65°C).
Regardless of this the PC cards cifX are designed for the operating
temperatures (-20°C to +55°C or -20°C to +70°C) as specified in section
Technical Data PC Cards cifX on page 147.
3.10 Requirements for Operation of the PC Card cifX

Operating the PC cards cifX properly, the following described requirements
must be fulfilled.
Protocols CC-Link IE Field Slave, PROFINET IO Device (Slave), PROFIBUS MPI Device
EtherCAT Slave, PROFINET IO Controller CANopen Slave,
EtherCAT Master, (Master), Sercos Slave, CANopen Master,
EtherNet/IP Adapter (Slave), Sercos Master, DeviceNet Slave,
EtherNet/IP Scanner (Master), VARAN Client (Slave), DeviceNet Master,
Open-Modbus/TCP, PROFIBUS DP Slave, AS-Interface Master;
POWERLINK-Controlled-Node/Slave, PROFIBUS DP Master, CC-Link Slave
Software 1. Driver for the Host Interface

Installation Host Interfaces: PCI and PCI Express
• The device driver cifX Device Driver must be installed (from V1.0).
If you install the device into a PC, in general Windows® will be available as operating system. In this
case the cifX Device Driver must be installed to communicate to the device and to exchange data via
the dual-port memory.
Important! Upgrade older versions of the cifX Device Driver necessarily on the current version
indicated in section Driver and Software on page 11.
OR
• If Windows® is not available as operating system, an own driver must be developed using the cifX
Driver Toolkit and this driver must be installed.
• For the operating systems Linux, Windows® CE, VxWorks, QNX and IntervalZero RTX ™ you can
buy Device Driver at the company Hilscher Gesellschaft für Systemautomation mbH
http://www.hilscher.com/.
2. The configuration software SYCON.net or alternatively the simple Slave configuration tool netX
Configuration Tool must be installed or another application program by which the PC card cifX
(Slave) can be parameterized.
How to use the On how to use the software for the configuration, the firmware download and for the diagnosis, note
Software the following notice:
Important! 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 ODMV3) or
- the netX Configuration Tool or
- the cifX Test Application or
- the cifX Driver Setup Utility or
- the application program.
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.
Firmware 3. Using the configuration software SYCON.net or for the Slave alternatively the Slave configuration
Download tool netX Configuration Tool, the user must select and download the firmware to the PC card cifX.
4. Important! Use the PC cards CIFX 50E-CCIES or CIFX 70E-CCIES only together with the CC-
Link IE Field Slave firmware and do not use this firmware for any other cards.
Parameter 5. The PC card cifX must be parameterized using one of the following options:
Setting • Configuration Software SYCON.net
• alternatively Slave configuration tool netX Configuration Tool (only Slave, not for newer systems)
• Application program (programming required)
Communica- 6. For the communication of a PC card cifX (Slave) a Master device for the respective communication
tion system is required. For the communication of a PC card cifX (Master) a Slave device for the
respective communication system is required.
PC Settings for Important! If you install a PC card cifX PCI Express, you always must disable the Microsoft Windows
PC Cards cifX "Link State Power Management". Otherwise, it cannot be excluded that your PC freezes during the
PCI Express PC card cifX PCI Express is in operation.
Environmental Due to a plug element from ERNI the lower limit of the operating temperature for all PC cards cifX
Conditions Real-Time Ethernet is 0 °C. This applies to all hardware revisions of the PC card cifX Real-Time
Ethernet, unless otherwise stated.
Table 27: Requirements to operate PC Cards cifX properly
3.11 Prerequisites for Certification

3.11.1 PROFINET IO Certification for IRT and SYNC0 Signal
3.11.1.1 Providing SYNC0 Signal at SYNC Connector of the PC Card cifX
Note: A PROFINET IO certification for PROFINET IRT requires
(mandatory) that your PC card cifX offers the synchronization signal
(SYNC0), in order to allow e. g. connecting an oscilloscope. Therefore the
SYNC connector of your PC card cifX must be accessible.
Information about where the SYNC connector is placed on your PC card

cifX, you can find in the chapter Device Drawings on page 58.
3.11.1.2 Using the SYNC0 Signal at the Host System

Only valid for PC Card CIFX 100EH-RE\CUBE:
If you forward the SYNC0 signal of your PC card cifX 100 EH-RE\CUBE to
the PCI Express bus X2, you must adhere to the following design
specification:
Note: A PROFINET IO certification for PROFINET IRT requires

(mandatory) that the host system offers a connector for the
synchronization signal (SYNC0), in order to allow e. g. connecting an
oscilloscope.
For this purpose you must use the SYNC0 signal and mass of the PCI
Express bus X2 of the PC card cifX 100EH-RE\CUBE at the host system
and provide it at the host system via a well accessible 2-pin connector.
The PC card CIFX 100 EH-RE\CUBE provides the SYNC0 signal SYNC0. If
at the SYNC connector (J1) the jumper is set on Pin1-Pin2, the SYNC0
signal is provided at pin B24 of the PCI Express bus X2. For further details
on the pin assignment of the SYNC connector and on how to set the
jumpers, refer to section Pin Assignment SYNC Connector, J1 (CIFX
100EH) on page 143. For the pin assignment of the PCI Express bus X2,
refer to section Pin Assignment for PCI Express Bus CIFX 100EH-
RE\CUBE on page 146.
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.
Getting Started 47/284
4 Getting Started
4.1 Warnings
When installing, uninstalling or replacing the PC card cifX, obey to the
following safety messages on personal injury respectively on personal
injury that may occur together with property damage.
Lethal Electrical Shock caused by parts with more than 50V!

HAZARDOUS VOLTAGE inside of the PC or of the connecting device.
 Strictly obey to all safety rules provided by the device’s manufacturer in
the documentation!
 First disconnect the power plug of the PC or of the connecting device,
before you open the cabinet.
 Make sure, that the power supply is off at the PC or at the connecting
device.
 Open the PC cabinet and install or remove the PC card cifX only after
disconnecting power.
Communication Stop caused by Firmware or Configuration Download

Initiating a firmware or configuration dowload process during bus operation
will stop the communication and a subsequent plant stop may cause
unpredictable and unexpected behavior of machines and plant
components, possibly resulting in personal injury and damage to your
equipment.
The firmware download overwrites the existing firmware. The
communication stop may cause loss of device parameters and possible
device damage may occur.
 Stop the application program, before you start the firmware or
configuration dowload.
 Make sure that all network devices are placed in a fail-safe condition.
Mismatching System Configuration

Mismatching system configuration loaded into the device could result in
faulty data mapping in the application program and thus unexpected
equipment operation may cause personal injury or damage of equipment.
 In the device use only a configuration suitable for the system.
Obey to the following property damage messages, when installing,
uninstalling or replacing the PC card cifX.
Exceeding permissible Supply Voltage

Operating the PC card cifX with a supply voltage above of the specified
range leads to device damage.
 Use only the permissible supply voltage to operate the PC card cifX.
Exceeding permissible Signaling Voltage!

All I/O signal pins at the PC card cifX tolerate only the specified signaling
voltage! Operating the PC card cifX with a signaling voltage other than the
specified signaling voltage may lead to severe damage to the PC card cifX!
 For the operation of the PC card cifX use only the specified signaling
voltage.
For further information on the permissible supply and signaling voltage refer
to section Power Supply and Host Interface on page 44.
Electrostatically sensitive Devices

 Adhere to the necessary safety precautions for components that are
vulnerable with electrostatic discharge.
 To prevent damage to the PC and the PC card cifX, make sure, that the
PC card cifX is grounded via the endplate and the PC and make sure,
that you are discharged when you install/uninstall the PC card cifX.
Power Disconnect while dowloading Firmware or Configuration

If the power supply to the PC or device is interrupted while the firmware or
configuration is being downloaded, the download will be aborted, the
firmware may be corrupted, the device parameters may be lost, and the
device may be damaged.
 During firmware or configuration download process do not interrupt the
power supply to the PC, or to the device and do not perform a reset to
the device!
Invalid Firmware
Loading invalid firmware files could render your device unusable.
 Only proceed with a firmware version valid for your device.
4.2 Installation and Configuration PC Card cifX

The following table describes the steps for the software and hardware
installation and for the configuration of a PC card cifX (Master and Slave)
Real-Time Ethernet and fieldbus as it is typical for many cases. The Slave
device can be configured using the corresponding Slave DTM in the
configuration software SYCON.net. Alternatively, you can also use the
simple Slave configuration tool netX Configuration Tool. The Master
device can be configured using the corresponding Master DTM in the
configuration software SYCON.net.
# Step Description For detailed Page
information see
manual / section
1 Installing Driver and
Software
1.1 Installing - Download the Communication Solutions Refer to User Manual
cifX Device Driver DVD as ZIP file to the local hard disk of your Software Installation for
PC. the PC cards cifX
- Unzip the ZIP file.
- Double-click the *.exe file in the root
directory of the DVD to open the autostart
menu.
- Follow to the instructions of the installation
wizard, to install the driver.
1.2 Installing SYCON.net For PC Cards cifX Master or Slave:
Run the SYCON.net-Setup and follow to the
instructions of the installation wizard.
1.3 Installing netX For PC Cards cifX Slave:
Configuration Tool
Start the netX Configuration Tool setup
Not usable for CC-Link program to install the netX Configuration
IE Field cards Tool.
2 Preparing Hardware
Installation
2.1 Take precautions on Electrostatically sensitive 32
Electrostatically Devices
sensitive Devices Electrostatically sensitive Devices
Make sure, that the PC card cifX is grounded
via the endplate and the PC and make sure,
that you are discharged when you install/
uninstall the PC card cifX.
2.2 Glue sticker on the For CIFX 50-RE, CIFX 50E-RE, CIFX 70E- Fix Front Plate Sticker 96
front plate. RE, CIFX 70E-RE\MR and CIFX 100EH-
RE\CUBE
2.2 Set the Slot Number Value 0 or a value from 1 to 9 Rotary Switch for Slot 141
(Card ID) Number (Card ID)
3 Hardware Installation Installing cifX. Take required safety Hardware Installation 95
precautions. and Uninstalling
3.1 Take safety Electrical Shock Hazard 29
precautions
Lethal Electrical Shock caused by parts
with more than 50V!
Disconnect the power plug of the PC or of
the connecting device.
Make sure, that the power supply is off at the
PC or at the connecting device.
3.2 Open cabinet Now open the cabinet of the PC or of the Installing PC Card cifX PCI, 99
connecting device. PCIe, Low Profile PCIe
information see
manual / section
3.3 Installing cifX Plug in and mount the PC card cifX.
Notice for CIFX 100EH-RE\CUBE:
Device Damage!
Install the PC card CIFX 100EH-RE\CUBE
exclusively in KEBA KeControl industry PCs
series CP 3XX (Cube). Otherwise yy
consequence malfunction can occur at the
PCI express bus.
3.4 Close cabinet Close the cabinet of the PC or connecting
device.
3.5 Plug the connecting Note for all PC Cards cifX Real-Time Ethernet Interface 135
cable to the Master or Ethernet:
Slave
Note! The RJ45 socket is only for
use in LAN, not for telecommuni-
cation circuits.
Note for PC Cards cifX PROFINET IO
Controller:
Important for Hardware Wiring!
Connect only ports with each other,
which have different cross-over set-
tings. Otherwise a connection bet-
See corresponding user
ween the devices can not be estab-
manual
lished. If the port settings of the PC
card cifX PROFINET IO controller
are not set to AUTO, then Port0 is
switched uncrossed and Port1
crossed.
Plug in the connecting cable from the PC card
cifX to the PC card Master or Slave.
3.6 Connect the PC to the Connect the PC or the connecting device to
power / switch on. the power supply and switch it on.
4 Hardware Settings Hardware Settings in the Driver Setup
4.1 Set Slot Number Set in the cifX Device Driver Setup the Slot Refer to User Manual
(Card ID) Number (Card ID) which has been set at the Software Installation for
PC card cifX (hardware). the PC Cards cifX
4.2 DMA Mode in the Activate the DMA Mode in the cifX Device
cifX Device Driver Driver Setup.
Setup
5 PC Settings
5.1 for PC Cards cifX PCI Important! If you install a PC card Refer to User Manual
Express cifX PCI Express, you always must Software Installation for
disable the Microsoft Windows "Link the PC Cards cifX
State Power Management".
Otherwise, it cannot be excluded that
your PC freezes during the PC card
cifX PCI Express is in operation.
6 Notice on how to use Use only one Software.
the Software
6.1 For the configuration, Important! To avoid communication Requirements for 45
the firmware download problems with the device, use the Operation of the PC
and for the diagnosis, USB interface, the serial interface as Card cifX
note: well as the cifX Device Driver
exclusively with one software that is
SYCON.net or netX Configuration
Tool.
information see
manual / section
Note for PC Cards CIFX 50E-CCIES and
CIFX 70E-CCIES:
Important!
For PC cards CIFX 50E-CCIES or
CIFX 70E-CCIES only use CC-Link
IE Field Slave firmware.
Use CC-Link IE Field Slave
firmware only with PC cards CIFX
50E-CCIES or CIFX 70E-CCIES.
7 Configuring Slave Download Firmware and Configuration
using SYCON.net Use the corresponding Slave DTM in the
7.1 Firmware Download - Start configuration software SYCON.net, See corresponding user
- Create new project /Open existing project, manual
- Insert Slave into configuration,
- Select driver and assign device. Device Names in 55
- Select and download the firmware. SYCON.net
Firmware Slave: CC-Link IE Field Basic PROFIBUS DP Slave,
Slave, PROFIBUS MPI
CC-Link IE Field Slave*, Device,
EtherCAT Slave, CANopen Slave,
EtherNet/IP Adapter, DeviceNet Slave,
Open-Modbus/TCP, CC-Link Slave
POWERLINK-
Controlled-Node/Slave,
PROFINET IO Device,
Sercos Slave,
VARAN Client,
Important! *Use the CC-Link IE
Field Slave firmware only together
with the PC cards CIFX 50E-CCIES
or CIFX 70E-CCIES and do not use
anny other firmware for these cards.
7.2 Configuration -Configure the PC card cifX (Slave).
cifX (Slave)
7.3 Download - Download the configuration to the PC card
Configuration cifX (Slave)
8 OR Configuring Download Firmware and Configuration
Slave using netX (not valid for CC-Link IE Field Slave)
Configuration Tool
8.1 Downloading Firmware If SYCON.net was already used on the PC, Requirements for 45
and Configuration stop the ODMV3 service. Therefore, select Operation of the PC
(Slave) Service > Stop from the context menu of the Card cifX
ODMV3 system tray icon.
The ODMV3 system tray icon changes to

ODMV3 Service stopped.
information see
manual / section
In the netX Configuration Tool: See Operating
- select the Firmware protocol, Instruction Manual netX
- Set the PC card cifX (Slave) parameters. Configuration Tool for
- Select Apply. cifX, comX and netJACK
The selected firmware and the configuration
are downloaded to the replacement card cifX.
The configuration is saved to the hard disk of
the PC.
9 Configuring Master Download Firmware and Configuration
using SYCON.net Use the corresponding Master DTM in the
9.1 Firmware Download - Start configuration software SYCON.net, See corresponding user
- Create new project /Open existing project, manual
- Insert Master into configuration, Device Names in 55
- Select driver and assign device. SYCON.net
- Select and download the firmware.
Firmware Master: EtherCAT Master, PROFIBUS DP Master,
EtherNet/IP Scanner, CANopen Master,
PROFINET IO DeviceNet Master,
Controller, AS-Interface Master
Notes for the 53
9.2 Configuration - Configure the PC card cifX (Master).
Configuration of the
cifX (Master)
Master Device
9.3 Download - Download the configuration to the PC card
Configuration cifX (Master).
10 Slave Diagnosis by Diagnosis, I/O Data
SYCON.net Use the corresponding Slave or Master DTM
(Slave and Master) in the configuration software SYCON.net.
10.1 Diagnostic - Rightclick on the device symbol. See corresponding user
- Select context menu entry Diagnosis, manual
- then select Diagnosis > General or
Firmware Diagnosis,
- or select Diagnosis > Extended Diagnosis.
10.2 I/O Monitor - Rightclick on device symbol.
- Select context menu entry Diagnosis,
- then Tools > IO Monitor.
-Check the input or output data.
11 OR Slave Diagnosis Diagnosis
by netX Configuration
Tool (only Slave)
11.1 Configuration Steps If SYCON.net was already used on the PC,
cifX (Slave) stop the ODMV3 service. Therefore, select
Service > Stop from the context menu of the
ODMV3 system tray icon.
In the netX Configuration Tool: See Operating
- In the navigation area click on Diagnostic, Instruction Manual netX
- click in the Diagnostic pane to Start, to Configuration Tool for
start the communication to the Master device cifX, comX and netJACK
and to run the diagnosis.
- click on Extended, to run the extended
diagnosis.
Table 28: Steps for the Software and Hardware Installation, the Configuration and for the
Diagnosis of a PC Card cifX (Master and Slave)
4.3 Note on Exchange Service (Replacement Case)

For the exchange service (replacement case) of a PC card cifX (Master and
Slave) obey to the following note.
Important! For the replacement card cifX with Rotary Switch Slot
Number (Card ID) set the same Slot Number (Card ID) as at the
previous PC card cifX (see section Rotary Switch for Slot Number (Card
ID) on page 141).
For PC cards cifX without Rotary Switch Slot Number (Card ID) in terms
of a device exchange service (replacement case) you must manually
download the same firmware and configuration into the replacement card
cifX, as into the preceding cifX.
4.4 Notes for the Configuration of the Master Device

To configure the Master, a device description file is required. Note the
following notes for the configuration of the Master Device:
System Note
CC-Link IE Field To configure the Master, a CSPP file (device description file) is required. The settings in the
Basic Slave used Master must comply with the settings in the Slave to establish communication. Important
parameters are: Slave Station Address, Input and output data, , vendor code, model type,
occupied stations.
CC-Link IE Field To configure the Master, a CSPP file (device description file) is required. The settings in the
Slave used Master must comply with the settings in the Slave to establish communication. Important
parameters are: Slave Station Address, Input and output data, vendor code, model code.
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 and Input
Data Bytes.
EtherCAT Slave If the XML file Hilscher CIFX RE ECS V2.2.X.xml is use/updated, the firmware with the version
2.2.x must be use/updated.
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 EtharCAT, then a customer specific XML file is necessary. Additionally the
following formular applies: (number of input bytes + 3)/4 + (number of output bytes + 3)/4 must
be less or equal to 100.
EtherNet/IP To configure the Scanner/Master, an EDS file (device description file) is required. The settings
Adapter 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- To configure the Managing Node/Master, an XDD file (device description file) is required. The
Controlled- settings in the used Managing Node/Master must comply with the settings in the Controlled
Node/Slave Node/Slave, to establish communication. Important parameters are: Vendor ID, Product Code,
Serial Number, Revision Number, Node ID, Output and Input length.
PROFINET IO To configure the Controller, a GSDML file (device description file) is required. The settings in the
Device 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.
System Note
Sercos Slave The Sercos Master uses the Sercos address to communicate with the slave. Some Masters will
verify Device ID, Vendor Code, Input Data Size and Output Data Size and will do further
communication to the Slave only if all these values match. Therefor 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.
PROFIBUS DP To configure the Master, a GSD file (device description file) is required. The settings in the used
Slave Master must comply with the settings in the Slave to establish communication. Important
parameters are: Station Address, Ident Number, Baudrate and Config Data (the configuration
data for the output and input length).
CANopen Slave To configure the Master, an EDS file (device description file) is required. The settings in the
parameters are: Node Address and Baudrate.
DeviceNet Slave To configure the Master, an EDS file (device description file) is required. The settings in the
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. The settings in the used
Master must comply with the settings in the Slave to establish communication. Important
parameters are: Slave Station Address, Baudrate, Station Type and Vendor Code.
Table 29: Notes for the Configuration of the Master Device
Further information to the device description files you find under section
on Device Description Files PC Cards cifX page 21.
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 PC card cifX and which protocol can be used. Further-
more, the table shows, for which protocol which device must be selected
from the device catalog to configure the PC card cifX with SYCON.net.
PC Cards cifX Protocol DTM Specific Group Device Name in
SYCON.net
CIFX 50-RE, CC-Link IE Field Basic Slave Gateway/Stand-Alone Slave CiFX RE/CCIBS
CIFX 50E-RE,
CIFX 50E-RE\ET EtherCAT Master Master CIFX RE/ECM
CIFX 70E-RE,
CIFX 70E-RE\MR, EtherCAT Slave Gateway/Stand-Alone Slave CIFX RE/ECS
CIFX 100EH-RE\CUBE EtherNet/IP Scanner (Master) Master CIFX RE/EIM
EtherNet/IP Adapter (Slave) Gateway/Stand-Alone Slave CIFX RE/EIS
Open-Modbus/TCP Gateway/Stand-Alone Slave CIFX RE/OMB
POWERLINK-Controlled- Gateway/Stand-Alone Slave CIFX RE/PLS

Node/Slave
PROFINET IO-Controller Master CIFX RE/PNM
PROFINET IO-Device Gateway/Stand-Alone Slave CIFX RE/PNS
Sercos Master Master CIFX RE/S3M
Sercos Slave Gateway/Stand-Alone Slave CIFX RE/S3S
VARAN Client (Slave) Gateway/Stand-Alone Slave CIFX RE/VRS
CIFX 50E-CCIES, CC-Link IE Field Slave Gateway/Stand-Alone Slave CiFX RE/CCIES

CIFX 70E-CCIES
CIFX 50-DP, PROFIBUS DP Master Master CIFX DP/DPM
CIFX 50E-DP,
CIFX 70E-DP, PROFIBUS DP Slave Gateway/Stand-Alone Slave CIFX DP/DPS
CIFX 70E-DP\MR
PROFIBUS MPI Device Gateway/Stand-Alone Slave CIFX DP/MPI
CIFX 50-2DP, 2*CIFX DP/DPM

CIFX 50E-2DP PROFIBUS DP Master Master for each PROFIBUS DP
channel one CIFX DP/DPM
2*CIFX DP/DPS
PROFIBUS DP Slave Gateway/Stand-Alone Slave for each PROFIBUS DP
channel one CIFX DP/DPS
CIFX 50-2DP\CO, 1*CIFX DP/DPM,
CIFX 50E-2DP\CO for PROFIBUS DP channel
PROFIBUS DP Master, one CIFX DP/DPM
Master
CANopen Master 1*CIFX CO/COM,
for CANopen channel
one CIFX CO/COM
1*CIFX DP/DPS,
for PROFIBUS DP channel
PROFIBUS DP Slave, one CIFX DP/DPS
Gateway/Stand-Alone Slave
CANopen Slave 1*CIFX CO/COS,
for CANopen channel
one CIFX CO/COS
CIFX 50-2DP\DN, 1*CIFX DP/DPM,
CIFX 50E-2DP\DN for PROFIBUS DP channel
PROFIBUS DP Master, one CIFX DP/DPM
Master
DeviceNet Master 1*CIFX DN/DNM,
for DeviceNet channel
one CIFX DN/DNM
PC Cards cifX Protocol DTM Specific Group Device Name in
SYCON.net
1*CIFX DP/DPS,
for PROFIBUS DP channel
PROFIBUS DP Slave, one CIFX DP/DPS
DeviceNet Slave 1*CIFX DN/DNS,
for DeviceNet channel one
CIFX DN/DNS
CIFX 50-CO
CIFX 50E-CO, CANopen Master Master CIFX CO/COM
CIFX 70E-CO,
CIFX 70E-CO\MR CANopen Slave Gateway/Stand-Alone Slave CIFX CO/COS
CIFX 50-2CO, 2* CIFX CO/COM

CIFX 50E-2CO CANopen Master Master for each CANopen channel
one CIFX CO/COM
1* CIFX CO/COM,
for 1 CANopen channel
CANopen Master, Master, one CIFX CO/COM
CANopen Slave Gateway/ Stand-Alone Slave 1* CIFX CO/COS,
for 1 CANopen channel
one CIFX CO/COS
2*CIFX CO/COS
CANopen Slave Gateway/Stand-Alone Slave for each CANopen channel
one CIFX CO/COS
CIFX 50-CO\DN, 1* CIFX CO/COM,
CIFX 50E-2CO/DN for CANopen channel
CANopen Master, one CIFX CO/COM
Master
DeviceNet Master 1*CIFX DN/DNM,
one CIFX DN/DNM
1* CIFX CO/COS,
for CANopen channel
CANopen Slave, one CIFX CO/COS
DeviceNet Slave 1* CIFX DN/DNS,
one CIFX DN/DNS
CIFX 50-DN DeviceNet Master Master CIFX DN/DNM
CIFX 50E-DN,
CIFX 70E-DN, DeviceNet Slave Gateway/Stand-Alone Slave CIFX DN/DNS
CIFX 70E-DN\MR
CIFX 50-2DN, 2* CIFX DN/DNM
CIFX 50E-2DN DeviceNet Master Master for each DeviceNet channel
one CIFX DN/DNM
2* CIFX DN/DNS
DeviceNet Slave Gateway/Stand-Alone Slave for each DeviceNet channel
one CIFX DN/DNS
CIFX AS/ASM
CIFX 50-2ASM,
AS-Interface Master Master for each AS-Interface
CIFX 50E-2ASM
channel one CIFX AS/ASM
CIFX 50-CC
CC-Link Slave Gateway/Stand-Alone Slave CIFX CC/CCS
CIFX 50E-CC
Table 30: Device Names in SYCON.net by Communication Protocol
4.6 Update for Firmware, Driver and Software

Note: As a pre-requirement for the software update the project files, the
configuration files and firmware files are 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 Notes on Hardware, Firmware, Software and Driver Versions on
page 10. The following graphic gives an overview:
Figure 1: System Overview cifX to update Firmware, Driver and Software
Note the specific details for devices with Rotary Switch Slot Number
(Card ID) in the section The Function „Slot Number (Card ID)“ on page 39
or DMA Mode in section The Function „DMA Mode“ on page 41.
Device Drawings 58/284
5 Device Drawings
5.1 PC Cards cifX PCI and PCI Express
5.1.1 CIFX 50-RE, CIFX 50E-RE, CIFX 50E-RE\ET
Drehschalter Slot-Nummer (Karten-ID) /

Rotary Switch Slot Number (Card ID) S1
System LED (gelb/grün) / (yellow/green)

SYS Kommunikationsstatus-LED 0 und 1 (rot/grün) /
Communication Status LED 0 and 1 (red/green)
COM0
COM1
Ethernet RJ45-Buchse /
Ethernet RJ45 Socket
Kanal 0 /
CIFX 50-RE
Channel 0 (CH 0)
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Hilscher
Pin 2: TX-
Kanal 1 /
Channel 1 (CH 1)
3
L ED L ED
g rün / green gelb / yellow
1
X51
X2
B1 B62
PCI Bus SYNC-Anschluss /

(X2/(X1), 124-polig / 124 pin) SYNC Connector
(X51, 3-polig / 3 pin)
Figure 2: CIFX 50-RE* (from hardware rev. 3)

S1
Rotary Switch Slot Number (Card ID)
Matrix_Code
SYS Kommunikationsstatus-LED 0 und 1 (rot/grün) /
COM0
COM1
Kanal 0 /
Channel 0 (CH 0)
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
CIFX50E-RE
Pin 2: TX-
L0608012
AOI
Kanal 1 /
Channel 1 (CH 1)
1
LED LED
grün / green gelb / yellow
3
X51
B1 B18
SYNC-Anschluss /
SYNC Connector
PCI Express Bus
(36-polig / 36 pin)
Figure 3: CIFX 50E-RE* (from hardware rev. 4), CIFX 50E-RE\ET* (from hardware rev. 1)
Note: *Device supports Auto Crossover Function. Note also: With loaded
EtherCAT Master firmware only the RJ45 channel 0 can be used,
channel 1 is deactivated. Beginning with EtherCAT Master firmware V3
channel 1 can be reactivated if redundancy is activeted. For Open
Modbus/TCP with V2.3.4.0 and higher both RJ45 channels can be used.
For the SYNC pin assignment of the SYNC Connector refer to section
Pin Assignment SYNC Connector, X51 (CIFX 50 50E 70E) on page 143.
Device drawings of earlier device revisions without rotary switch slot
number (card ID) are included in the user manual for PC cards cifX Real-
Time Ethernet up to manual rev. 32.
The figure below shows the front plate of the PC cards CIFX 50-RE, CIFX
50E-RE or CIFX 50E-RE\ET:
7 8
1  Rotary Switch Slot Number (Card ID)*

5 6
9
0
The figure shows the rotary switch in position 1. Refer also to

1
4
2 3
section Rotary Switch for Slot Number (Card ID), page 141.
SYS 2  System LED (yellow/green)
COM0 3  Communication Status LED 0* (red/green)
COM1 4  Communication Status LED 1* (red/green),

(*Designation and meaning depends by protocol)
Refer also to chapter LED Descriptions, page 102.
5  Ethernet Interface Channel 0
6  Ethernet Interface Channel 1

Refer also to section Ethernet Interface, page 135.
Figure 4: Front Plate for CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET
*From hardware revision 3 (for CIFX 50-RE), 4 (for CIFX 50E-RE) or 1 (for
CIFX 50E-RE\ET) on, the Rotary Switch Slot Number (Card ID) is
provided.
5.1.2 CIFX 50E-CCIES
System LED
SYS (gelb/grün) / (yellow/green)
Kommunikationsstatus-LEDs /
Communication Status LEDs
RUN, RD, SD (grün/green)
D-LINK, USER1, USER2 (gelb/yellow)
ERR (rot/red)
DL U2 U1 SYS
ERR RD SD RUN
Kanal 0 /
Channel 0
(CH 0)
LED LED Kanal 1 /

grün / green gelb / yellow Channel 1
(CH 1)
Pin 4: D3+
Pin 3: D2+
Pin 7: D4+
Pin 1: D1+
Pin 5: D3-
Pin 2: D1-
Pin 8: D4-
Pin 6: D2-
SYNC-Anschluss /
SYNC Connector
PCI Express Bus
(36-polig / 36 pin)
Figure 5: CIFX 50E-CCIES* (Hardware revision 1)
Note: *Device supports Auto Crossover Function.
For details about the Rotary Switch Slot Number (Card ID) refer to
The figure below shows the front plate of the PC card CIFX 50E-CCIES:
DL U2 U1 SYS
ERR RD SD RUN 1
System LED SYS (yellow/green),
 LEDs Communication Status LEDs
DL U2 U1 SYS RUN, RD, SD (green)
ERR RD SD RUN D-LINK, USER1, USER2 (yellow)
2 ERR (red)
Ethernet Interface Channel 0
CH0
 Ethernet Interface Channel 1

CH1 Refer also to section Ethernet Interface, page 135.
LINK
L.ER
Figure 6: Front Plate for CIFX 50E-CCIES
5.1.3 CIFX 50-DP, CIFX 50E-DP

S1
Hilscher
AOI
System LED (gelb/grün) / (yellow/green) SYS
Kommunikationsstatus-LED (rot/grün) / COM

Communication Status LED (red/green)
PROFIBUS-Schnittstelle
DSub-Buchse (9-polig)
XXXXX
PROFIBUS Interface
DSub female Connector (9 pin) XXXX.XXX X
Matrix Code
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
L0618015
B1 B62
X2
PCI Bus
(X2, 124-polig / 124 pin)
Figure 7: CIFX 50-DP (hardware revision 5)*

S1
Matrix_Code
Kommunikationsstatus-LED (rot/grün) / COM

Communication Status LED (red/green)
PROFIBUS Interface
L0731013
AOI
DSub female Connector (9 pin)

CIFX50E-CO-DN-DP
B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 8: CIFX 50E-DP (hardware revision 5)*
*Device drawings of earlier device revisions without rotary switch slot

number (card ID) or with two COM LEDs are included in the user manual
for PC cards cifX fieldbus up to manual rev. 23.
The figure below shows the front plate of the PC cards
CIFX 50-DP or CIFX 50E-DP:
 Rotary Switch Slot Number (Card ID)*

7 8
5 6
9
0
1
4
2 3
chapter Rotary Switch for Slot Number (Card ID), page 141.
SYS 2
 System LED (yellow/green)
COM 3  Communication Status LED COM (red/green)
Refer also to chapter, LED Descriptions, page 102.
4  PROFIBUS Interface;
Refer also to chapter, PROFIBUS Interface page 138.
Figure 9: Front Plate CIFX 50-DP or CIFX 50E-DP
*From hardware revision 5 (for CIFX 50-DP or CIFX 50E-DP) on, the
Rotary Switch Slot Number (Card ID) is provided.
5.1.4 CIFX 50-2DP, CIFX 50E-2DP

COM 0 LED (rot/grün) für Kanal X1 / (red/green) for Channel X1
A Device drawing of the earlier device revision without rotary switch slot
Hilscher
COM 0
COM 1
made in Germany
SYS
S1 Rotary Switch Slot Number (Card ID)
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
PROFIBUS-Schnittstelle, Kanal X2
number (card ID) is included in the user manual rev. 37.

L0834002
PROFIBUS Interface, Channel X2

CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
XXXXX
PROFIBUS Interface, Channel X1 XXXX.XXX X
Matrix Code

-
X2
B1 B62
PCI Bus (124-polig / 124 pin)
Figure 10: CIFX 50-2DP (Hardware Revision 3)

Hilscher
COM 0
COM 1
made in Germany
SYS

CIFX 50E-CO
CIFX 50E-DP
CIFX 50E-DN
L1510011

XXXXX

XXXX.XXX
CIFX 50E-CO
CIFX 50E-DP
CIFX 50E-DN

B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 11: CIFX 50E-2DP (Hardware Revision 1)
CIFX 50-2DP, CIFX 50E-2DP:
1
 System LED (yellow/green)
2
 (not used)
3
 Communication Status LED COM0 (red/green)
4
X2  Communication Status LED COM1 (red/green)
5
 PROFIBUS Interface Channel X2
6  PROFIBUS Interface Channel X1

X1
Figure 12: Front Plate CIFX 50-2DP, CIFX 50E-2DP
5.1.5 CIFX 50-2DP\CO, CIFX 50E-2DP\CO

CAN 1 LED (rot/grün) für Kanal X2 / (red/green) for Channel X2
Hilscher
COM 0
CAN 1
made in Germany
SYS
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
CANopen-Schnittstelle, Kanal X2
L0834002
DSub-Stecker (9-polig)
CANopen Interface, Channel X2

DSub male Connector (9 pin)
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
XXXXX
Matrix Code
X2
B1 B62
Figure 13: CIFX 50-2DP\CO (Hardware Revision 2)

Hilscher
COM 0
CAN 1
made in Germany
SYS

CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
L1510011

XXXXX
DSub male Connector (9 pin) XXXX.XXX

CIFX 50E-DN
CIFX 50E-CO
CIFX 50E-DP

B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 14: CIFX 50E-2DP\CO (Hardware Revision 1)
CIFX 50-2DP\CO, CIFX 50E-2DP\CO:
1
2
 (not used)
3
4
X2
 Communication Status LED CAN1 (red/green)
5
 CANopen Interface Channel X2
Refer also to chapter CANopen Interface, page 138.
6
 PROFIBUS Interface Channel X1
X1
Figure 15: Front Plate CIFX 50-2DP\CO, CIFX 50E-2DP\CO
5.1.6 CIFX 50-2DP\DN, CIFX 50E-2DP\DN

MNS 1 LED (rot/grün) für Kanal X2 / (red/green) for Channel X2
Hilscher
COM 0
MNS 1
made in Germany
SYS
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
DeviceNet-Schnittstelle, Kanal X2
L0834002
COMBICON-Stecker (5-polig)
2
3
DeviceNet Interface, Channel X2
4
COMBICON male Connector
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
(5 pin)
XXXXX
Matrix Code
X2
B1 B62
Figure 16: CIFX 50-2DP\DN (Hardware Revision 1)

Hilscher
COM 0
MNS 1
made in Germany
SYS

CIFX 50E-DN
CIFX 50E-DP
CIFX 50E-CO
L1510011

XXXXX
COMBICON male Connector XXXX.XXX

CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
(5 pin)

B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 17: CIFX 50E-2DP\DN (Hardware Revision 1)
CIFX 50-2DP\DN, CIFX 50E-2DP\DN:
1
2
 (not used)
3
4
X2  Communication Status LED MNS1 (red/green)
1 2 3 4 5
5
 DeviceNet Interface Channel X2;
Refer also to chapter DeviceNet Interface, page 139.
6  PROFIBUS Interface Channel X1

X1
Figure 18: Front Plate CIFX 50-2DP\DN, CIFX 50E-2DP\DN
5.1.7 CIFX 50-CO, CIFX 50E-CO

Rotary Switch Slot Number (Card ID) S1 Hilscher
AOI
CAN LED (rot/grün) / (red/green) CAN
CANopen-Schnittstelle
XXXXX
CANopen Interface
DSub male Connector (9 pin) XXXX.XXX X
Matrix Code
CIFX 50-DP
CIFX 50-DN
CIFX 50-CO
L0618015
X400
B1 B62
X2
PCI Bus
(X2, 124-polig / 124 pin)
Figure 19: CIFX 50-CO (hardware revision 5)

Matrix_Code
CAN LED (rot/grün) / (red/green) CAN
CANopen Interface
L0731013
AOI
CIFX50E-CO-DN-DP
B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 20: CIFX 50E-CO (from hardware revision 4)

number (card ID) or with two COM LEDs are included in the user manual
for PC cards cifX fieldbus up to manual rev. 23.
CIFX 50-CO or CIFX 50E-CO:
7 8  Rotary Switch Slot Number (Card ID)*

1
5 6
9
0
1
4
2 3
CAN 3  Communication Status LED CAN (red/green)
4  CANopen Interface
Figure 21: Front Plate for CIFX 50-CO or CIFX 50E-CO
*From hardware revision 5 (for CIFX 50-CO or CIFX 50E-CO) on, the Rotary
Switch Slot Number (Card ID) is provided.
5.1.8 CIFX 50-2CO, CIFX 50E-2CO

Hilscher
CAN 0
CAN 1
made in Germany
SYS
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
L0834002

CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
XXXXX
CANopen Interface, Channel X1 XXXX.XXX X
Matrix Code
X2
B1 B62
Figure 22: CIFX 50-2CO (Hardware Revision 2)

Hilscher
CAN 0
CAN 1
made in Germany
SYS

CIFX 50E-DN
CIFX 50E-CO
CIFX 50E-DP
L1510011

XXXXX
DSub male Connector (9 pin) XXXX.XXX

CIFX 50E-DN
CIFX 50E-CO
CIFX 50E-DP

B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 23: CIFX 50E-2CO (Hardware Revision 1)
CIFX 50-2CO, CIFX 50E-2CO:
1
2
 (not used)
3
 Communication Status LED CAN0 (red/green)
4
 Communication Status LED CAN1 (red/green)
X2
5
 CANopen Interface Channel X2
6  CANopen Interface Channel X1

X1
Figure 24: Front Plate CIFX 50-2CO, CIFX 50E-2CO
5.1.9 CIFX 50-2CO\DN, CIFX 50E-2 CO\DN

Hilscher
MNS 1
CAN 0
made in Germany
SYS
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
L0834002
2
3
4
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
(5 pin)
CANopen-Schnittstelle, Kanal X1 5
XXXXX
CANopen Interface, Channel X1 XXXX.XXX X
Matrix Code
X2
B1 B62
Figure 25: CIFX 50-2 CO\DN (Hardware Revision 1)

Hilscher
MNS 1
CAN 0
made in Germany
SYS

CIFX 50E-DN
CIFX 50E-CO
CIFX 50E-DP
L1510011

XXXXX

CIFX 50E-CO
CIFX 50E-DP
CIFX 50E-DN
(5 pin)

B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 26: CIFX 50E-2 CO\DN (Hardware Revision 1)
CIFX 50-2CO\DN, CIFX 50E-2 CO\DN:
1
2
 (not used)
3
 Communication Status LED CAN0 (red/green)
4
 Communication Status LED MNS1 (red/green)
X2
1 2 3 4 5
5
 DeviceNet Interface Channel X2;
6
 CANopen Interface Channel X1
X1
Figure 27: Front Plate CIFX 50-2CO\DN, CIFX 50E-2 CO\DN
5.1.10 CIFX 50-DN, CIFX 50E-DN

S1
Hilscher
AOI
Modulnetzwerkstatus-LED (rot/grün) / MNS

Module Network Status LED (red/green)
DeviceNet-Schnittstelle
1
XXXXX
2
DeviceNet Interface
COMBICON male Connector (5 pin) XXXX.XXX X
3
Matrix Code
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
L0618015
4
5
B1 B62
X2
PCI Bus
(X2, 124-polig / 124 pin)
Figure 28: CIFX 50-DN (hardware revision 5)

4
1
C
C
8
Matrix_Code
Modulnetzwerkstatus-LED (rot/grün) / MNS

Module Network Status LED (red/green)
1
DeviceNet Interface
2
COMBICON male Connector (5 pin)

L0731013
AOI
CIFX50E-CO-DN-DP
3
4
5
B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 29: CIFX 50E-DN (from hardware revision 4)

number (card ID) are included in the user manual for PC cards cifX
fieldbus up to manual rev. 23.
The figure below shows the front plate of the PC cards CIFX 50-DN or
CIFX 50E-DN:

7 8
5 6
9
0
1
4
2 3
SYS 2
 System LED (yellow/green)
MNS 3  Communication Status LED MNS (red/green)
1 2 3 4 5 Refer also to chapter LED Descriptions, page 102.
4  DeviceNet Interface; refer also to chapter DeviceNet Interface,

page 139.
Note: The front plate cutout for the CombiCon male

Connector is at the PCB side 0.5 mm outside of the
standard front plate cutout.
Figure 30: Front Plate CIFX 50-DN or CIFX 50E-DN
*From hardware revision 5 (for CIFX 50-DN or CIFX 50E-DN on, the Rotary
Switch Slot Number (Card ID) is provided.
5.1.11 CIFX 50-2DN, CIFX 50E-2DN

Hilscher
MNS 0
MNS 1
made in Germany
SYS
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
L0834002
2
3
4
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
(5 pin)
5
DeviceNet-Schnittstelle, Kanal X1 1
XXXXX
2
DeviceNet Interface, Channel X1 XXXX.XXX X

Matrix Code
3

4
(5 pin)
5
X2
B1 B62
Figure 31: CIFX 50-2DN (Hardware Revision 2)

Hilscher
MNS 0
MNS 1
made in Germany
SYS

CIFX 50E-DP
CIFX 50E-DN
CIFX 50E-CO
L1510011

XXXXX

CIFX 50E-DP
CIFX 50E-CO
CIFX 50E-DN
(5 pin)

(5 pin)
B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 32: CIFX 50E-2DN (Hardware Revision 1)
CIFX 50-2DN, CIFX 50E-2DN:
1
2
 (not used)
3
 Communication Status LED MNS0 (red/green)
4
 Communication Status LED MNS1 (red/green)
X2
1 2 3 4 5
5  DeviceNet Interface Channel X2
1 2 3 4 5
6  DeviceNet Interface Channel X1

X1
Figure 33: Front Plate CIFX 50-2DN, CIFX 50E-2DN
5.1.12 CIFX 50-2ASM, CIFX 50E-2ASM

COM1 LED (rot/grün) / (red/green) COM1
AS-Interface-Schnittstelle, Kanal X1
COMBICON-Stecker (2-polig) 1
AS-Interface, Channel X1
COMBICON male Connector (2 pin) CIFX50-2ASM Matrix
2
Hilscher Label
made in Germany
L0916002
UL
1
2
AOI
AS-Interface, Channel X2 B1
X2
B62
PCI Bus
(124-polig / 124 pin)
Figure 34: CIFX 50-2ASM (hardware revision 2)

PCI Express Bus

(36-polig / 36 pin)
Figure 35: CIFX 50E-2ASM (from hardware revision 2)

The figure below shows the front plate of the PC card CIFX 50-2ASM:
7 8
1
5 6
9
0
The figure shows the rotary switch in position 1; refer also to chapter
1
4
2 3
Rotary Switch for Slot Number (Card ID), page 141.

COM1 3  COM1 LED (red/green)
COM2 4  COM2 LED (red/green)
X1
5  AS-Interface Interface Channel X1
6  AS-Interface Interface Channel X2

Refer also to chapter AS-Interface Interface, page 139.
X2
Figure 36: Front Plate CIFX 50-2ASM
*From hardware revision 2 on, the Rotary Switch Slot Number (Card ID)
is provided.
5.1.13 CIFX 50-CC, CIFX 50E-CC

XXXXX
XXXX.XXX X
Matrix Code
L Run LED (grün) / (green) L RUN
L Error LED (rot) / (red) L ERR
CC-Link-Schnittstelle
Schraubstecker (5-polig)
1
2
CC-Link Interface AOI

Screw Terminal Connector
3
(5 pin)
CIFX50-CC
CIFX50-CP
Hilscher GmbH
L0912012
4
5
X2
B1 B62
PCI Bus
(X2, 124-polig / 124 pin)
Figure 37: CIFX 50-CC (hardware revision 2)*

S1
XXXXX
XXXX.XXX X
Matrix Code
L Run LED (grün) / (green) L RUN

Hilscher
L Error LED (rot) / (red) L ERR

GmbH
CC-Link-Schnittstelle
Schraubstecker (5-polig)
1
2
L0910012
CC-Link Interface
CIFX50E-CC
CIFX50E-CP
Screw terminal connector (5 pin)

3
4
5
B1 B18
PCI Express Bus

(36-polig / 36 pin)
Figure 38: CIFX 50E-CC (hardware revision 4)*

Note: *The front plate cutout for the screw terminal connector is at the
PCB side 0.5 mm outside of the standard front plate cutout.
The figure below shows the front plate of the PC cards CIFX 50-CC or
CIFX 50E-CC:
7 8
1
5 6
9
0
The figure shows the rotary switch in position 1; refer also to chapter
1
4
2 3
Rotary Switch for Slot Number (Card ID), page 141.

L RUN 3  Communication Status LED L RUN (red/green)
L ERR 4  Communication Status LED L ERR (red/green)

1 2 3 4 5
5  CC-Link Interface
Refer also to chapter CC-Link Interface, page 140.
Figure 39: Front Plate CIFX 50-CC or CIFX 50E-CC
*From hardware revision 2 (for CIFX 50-CC) on or 3 (for CIFX 50E-CC), the
Rotary Switch Slot Number (Card ID) is provided.
5.1.14 Meaning of the Front Panel Inscriptions for 2 Channel Devices

PC card cifX Channel X1 Channel X2
CIFX 50-2DP, CIFX 50E-2DP COM0 COM1
CIFX 50-2DP\CO, CIFX 50E-2DP\CO COM0 CAN1
CIFX 50-2DP\DN, CIFX 50E-2DP\DN COM0 MNS1
CIFX 50-2CO, CIFX 50E-2CO CAN0 CAN1
CIFX 50-2CO\DN, CIFX 50E-2CO\DN CAN0 MNS1
CIFX 50-2DN, CIFX 50E-2DN MNS0 MNS1
CIFX 50-2ASM, CIFX 50E-2ASM COM1 COM2
Table 31: Assignment of the LEDs to the Channels
X1 and X2 indicate the bus interfaces: X1 stands for fieldbus 1 (channel

X1), X2 stands for fieldbus 2 (channel X2).
Note: Within the configuration software SYCON.net the communication

channels are named with ‘Ch0’, ’Ch1’ … .
5.2 PC Cards cifX Low Profile PCI Express

5.2.1 CIFX 70E-RE, CIFX 70E-RE\MR
Kommunikationsstatus-LED 1 und 0 (rot/grün) /
System-LED (gelb/grün) / System LED (yellow/green)
COM 1
COM 0
SYS
S1
Kanal 0 /
Channel 0 (CH 0)
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Kanal 1 /
Channel 1 (CH 1)
LED LED
SYNC-Anschluss /
SYNC Connector
PCI-Express-Bus / PCI Express Bus

(X2/(X1), 64-polig / 64 pin)
Figure 40: CIFX 70E-RE* (Hardware revision 1)

COM 1
COM 0
SYS
S1
Kanal 0 /
Channel 0 (CH 0)
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Kanal 1 /
Channel 1 (CH 1)
LED LED
SYNC-Anschluss /
SYNC Connector

(X2/(X1), 64-polig / 64 pin)
Figure 41: CIFX 70E-RE\MR* (Hardware revision 1)
Note: *Device supports Auto Crossover Function. Note also: With loaded
EtherCAT Master firmware only the RJ45 channel 0 can be used,
channel 1 is deactivated. Beginning with the EtherCAT Master firmware
version 3 channel 1 can be reactivated if redundancy is activated.
For Open Modbus/TCP with V2.3.4.0 and higher both RJ45 channels can
be used.
About Rotary Switch for Slot Number (Card ID) refer to section Rotary
Switch for Slot Number (Card ID), on page 141.
The figure below shows the front plate of the PC card CIFX 70E-RE or ,
CIFX 70E-RE\MR:
1
 (not used)
2
 Communication Status LEDs COM1*
COM1
3
COM0  Communication Status LEDs COM0*
SYS 4
 System LED (yellow/green)
(*red/green, Designation and meaning depends by protocol).
5  Ethernet Interface Channel 0
6  Ethernet Interface Channel 1

Figure 42: Front Plate for CIFX 70E-RE, CIFX 70E-RE\MR

System LED
SYS (gelb/grün) / (yellow/green) Drehschalter Slot-Nummer (Karten-ID) /
Kommunikationsstatus-LEDs / Rotary Switch Slot Number (Card ID)
Communication Status LEDs
RUN, RD, SD (grün/green)
D-LINK, USER1, USER2 (gelb/yellow)
ERR (rot/red)
DL U2 U1 SYS
ERR RD SD RUN
Kanal 0 /
Channel 0
(CH 0)
LED LED
Kanal 1 /
Channel 1
(CH 1)
Pin 4: D3+
Pin 3: D2+
Pin 7: D4+
Pin 1: D1+
Pin 5: D3-
Pin 2: D1-
Pin 8: D4-
Pin 6: D2-
SYNC-Anschluss /
SYNC Connector
PCI Express Bus
(36-polig / 36 pin)
Figure 43: CIFX 70E-CCIES* (Hardware revision 1)
Note: *Device supports Auto Crossover Function.
For details about the Rotary Switch Slot Number (Card ID) refer to
The figure below shows the front plate of the PC card CIFX 70E-CCIES:
DL U2 U1 SYS
 LEDs System LED SYS (yellow/green),
ERR RD SD RUN 1 DL U2 U1 SYS Communication Status LEDs
ERR RD SD RUN RUN, RD, SD (green)
D-LINK, USER1, USER2 (yellow)
ERR (red)
2 Ethernet Interface Channel 0
CH0
3  Ethernet Interface Channel 1

CH1
LINK
L.ER
Figure 44: Front Plate for CIFX 70E-CCIES
5.2.3 CIFX 100EH-RE\CUBE

COM 1
COM 0
SYS
S1
Kanal 0 /
Channel 0 (CH 0)
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Kanal 1 /
Channel 1 (CH 1)
LED LED
SYNC-Anschluss /
SYNC Connector
(J1, 3-polig / 3 pin)

(X2/(X1), 64-polig / 64 pin)
Figure 45: CIFX 100EH-RE\CUBE*
The figure below shows the front plate of the PC card CIFX 100EH-
RE\CUBE:
Note: *Device supports Auto

 (not used) Crossover Function. Note
also: With loaded EtherCAT
 Communication Status LEDs COM1* Master firmware only the
1 RJ45 channel 0 can be used,
 Communication Status LEDs COM0*
2 channel 1 is deactivated.
COM1
COM0
 System LED (yellow/green) Beginning with the EtherCAT

SYS
3 Master firmware version 3

(*red/green, Designation and meaning
channel 1 can be reactivated
4 depends by protocol). Refer also to chapter
if redundancy is activated.
LED Descriptions, page 102.
For Open Modbus/TCP with
 Ethernet Interface Channel 0 V2.3.4.0 and higher both
5 RJ45 channels can be used.
About Rotary Switch for Slot

 Ethernet Interface Channel 1 Number (Card ID) refer to
6 Refer also to section Ethernet Interface, section Rotary Switch for Slot
page 135. Number (Card ID), on page
141.
For the pin assignment of the
PCI Express bus X2(X1) see
section Pin Assignment for PCI
Express Bus CIFX 100EH-
For the SYNC pin assignment
of the SYNC Connector refer to
section Pin Assignment SYNC
Connector, J1 (CIFX 100EH)
on page 143.
Figure 46: Front Plate CIFX 100EH-RE\CUBE
5.2.4 CIFX 70E-DP, CIFX 70E-DP\MR

Kommunikationsstatus-LED (rot/grün) / Drehschalter
Communication Status LED (red/green) Slot-Nummer (Karten-ID) /
System-LED (gelb/grün) / Rotary Switch
System LED (yellow/green) Slot Number (Card ID)
COM
SYS
S1
PROFIBUS Interface
DSub female Connector
(9 pin)

(X2/(X1), 64-polig / 64 pin)
Figure 47: CIFX 70E-DP (Hardware revision 1)
Kommunikationsstatus-LED (rot/grün) / Drehschalter

Communication Status LED (red/green) Slot-Nummer (Karten-ID) /
COM
SYS
S1
PROFIBUS Interface
DSub female Connector
(9 pin)

(X2/(X1), 64-polig / 64 pin)
Figure 48: CIFX 70E-DP\MR (Hardware revision 1)
About Rotary Switch for Slot Number (Card ID) refer to section Rotary Switch for Slot
Number (Card ID), on page 141.
The figure below shows the front plate of the PC card CIFX 70E-DP or
CIFX 70E-DP\MR:
1  (not used)
2  (not used)
3  Communication Status LED COM (red/green)
COM
SYS
4  System LED (yellow/green)
5  PROFIBUS Interface
Refer also to chapter PROFIBUS Interface page 138.
Figure 49: Front Plate CIFX 70E-DP, CIFX 70E-DP\MR
5.2.5 CIFX 70E-CO, CIFX 70E-CO\MR

Drehschalter
CAN LED (rot/grün) / (red/green) Slot-Nummer (Karten-ID) /
CAN
SYS
S1
CANopen Interface

(X2/(X1), 64-polig / 64 pin)
Figure 50: CIFX 70E-CO (Hardware revision 1)
Drehschalter
CAN LED (rot/grün) / (red/green) Slot-Nummer (Karten-ID) /
CAN
SYS
S1
CANopen Interface

(X2/(X1), 64-polig / 64 pin)
Figure 51: CIFX 70E-CO\MR (Hardware revision 1)
About Rotary Switch for Slot Number (Card ID) refer to section Rotary Switch for Slot
Number (Card ID), on page 141.
The figure below shows the front plate of the PC card CIFX 70E-CO or
CIFX 70E-CO\MR:
1  (not used)
2  (not used)
3  Communication Status LED CAN (red/green)
CAN
SYS
5  CANopen Interface
Figure 52: Front Plate CIFX 70E-CO, CIFX 70E-CO\MR
5.2.6 CIFX 70E-DN, CIFX 70E-DN\MR

Modulnetzwerkstatus-LED (rot/grün) / Drehschalter
Module Network Status LED (red/green) Slot-Nummer (Karten-ID) /
MNS
SYS
S1
COMBICON-Stecker
(5-polig)
1
2
DeviceNet Interface
3
(5 pin)
4
5

(X2/(X1), 64-polig / 64 pin)
Figure 53: CIFX 70E-DN (Hardware revision 1)
Modulnetzwerkstatus-LED (rot/grün) / Drehschalter

Module Network Status LED (red/green) Slot-Nummer (Karten-ID) /
MNS
SYS
S1
COMBICON-Stecker
(5-polig)
1
2
DeviceNet Interface
3
(5 pin)
4
5

(X2/(X1), 64-polig / 64 pin)
Figure 54: CIFX 70E-DN\MR (Hardware revision 1)
About Rotary Switch for Slot Number (Card ID) refer to section Rotary
Switch for Slot Number (Card ID), on page 141.
The figure below shows the front plate of the PC card CIFX 70E-DN or
CIFX 70E-DN\MR:
1  (not used)
2  (not used)
3  Communication Status LED MNS (red/green)
MNS
SYS
1 2 3 4 5
5  DeviceNet Interface
Figure 55: Front Plate CIFX 70E-DN, CIFX 70E-DN\MR
Hardware Installation and Uninstalling 95/284
6 Hardware Installation and Uninstalling

To install / uninstall the PC Cards the PC Cards cifX PCI Express
cifX PCI
 CIFX 50-RE,  CIFX 50-2DP,
 CIFX 50-DP, CIFX 50-CO,  CIFX 50-2DP\CO, CIFX 50-2DP\DN,
 CIFX 50-DN, CIFX 50-CC,  CIFX 50-2CO, CIFX 50-2CO\DN,
 CIFX 50E-RE, CIFX 50E-RE\ET,  CIFX 50-2DN,
 CIFX 50E-CCIE,  CIFX 50-2ASM,
 CIFX 50E-DP, CIFX 50E-CO,  CIFX 50E-2ASM
 CIFX 50E-DN, CIFX 50E-CC
and Low Profile PCI Express
 CIFX 70E-RE, CIFX 70E-RE\MR,  CIFX 70E-DP, CIFX 70E-DP\MR,
 CIFX 70E-CCIE,  CIFX 70E-CO, CIFX 70E-CO\MR,
 CIFX 100EH-RE\CUBE  CIFX 70E-DN, CIFX 70E-DN\MR
handle as described in the sections hereafter. The device drawing of your
PC card cifX gives information on the manual control elements of your
device.
For the installation, uninstalling and replacement of the PC card cifX

adhere to the necessary safety precautions given in the safety chapter
and in section Warnings on page 47 and check any notes in the overview
given Getting Started on page 47.
6.1 Fix Front Plate Sticker

6.1.1 Front Plate Sticker CIFX 50-RE, CIFX 50E-RE, CIFX 50E-RE\ET
Note: Your PC card cifX set contains a set of front plate stickers (9
different stickers). Depending from the loaded firmware the label on each
sticker indicates for the respective system the following LED names:
- of the system and communication status LEDs (above)
- of the RJ45 Ethernet female connector LEDs (below).
Further information to this question you find also in chapter LED
Descriptions beginning from page 102.


 To prevent damage to the PC and the PC card cifX, make sure, that
the PC card cifX is grounded via the endplate and the PC and make
sure, that you are discharged when you install/uninstall the PC card
cifX.
 Use the sticker according to the device and firmware and glue it on the
front of the PC card CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET.
Figure 56: Front Plate Stickers for CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET
Sercos Master
PROFINET IO
Sercos Slave
Modbus/TCP
POWERLINK
LED
EtherNet/IP
Field Basic
CC-Link IE
EtherCAT
EtherCAT
VARAN
Master
Slave
Open
SYS
SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS
(yellow/green)
COM 0
RUN RUN MS RUN BS SF STA S RUN RUN
(red/ green)
COM 1
ERR ERR NS ERR BE BF ERR - ERR ERR
(red/ green)
green LINK L/A IN LINK LINK L/A LINK L/A L/A LINK IN L/A
RJ45
Ch0
yellow ACT - ACT ACT - RX/TX - - ACT IN -

green LINK L/A OUT LINK LINK L/A LINK L/A L/A L/A
RJ45
LINK OUT
Ch1
yellow ACT - ACT ACT - RX/TX - - ACT OUT -
Table 32: LED Labeling depending of the loaded Firmware
6.1.2 Front Plate Sticker CIFX 70E-RE, CIFX 70E-RE\MR, CIFX 100EH-
RE\CUBE
Note: Your PC card CIFX 70E-RE, CIFX 70E-RE\MR or CIFX 100EH-
RE\CUBE set contains a set of front plate stickers (9 different stickers,
each 2 parts). Depending from the loaded firmware the label on each
sticker indicates for the respective system the following LED names:
(1) of the system and communication status LEDs (partial sticker
above)
(2) of the RJ45 Ethernet female connector LEDs (partial sticker below).
Further information to this question you find also in chapter LED
Descriptions beginning from page 102.

 Use the two part sticker according to the device and firmware and glue
it on the front of the PC card CIFX 70E-RE, CIFX 70E-RE\MR or CIFX
100EH-RE\CUBE.
Front CIFX 100EH-RE\CUBE Front CIFX 70E-RE, How to
CIFX 70E-RE\MR
1. Glue the "partial sticker above" with the

1 system specific names of the system
1 and communication status LEDs
above  of the LEDs COM1, COM0
and SYS on the front plate.
2
2. Glue the "partial sticker below " with
2
the system specific names of the
RJ45 Ethernet female connector
LEDs below  of the RJ45 on the front
plate.
Table 33: Fix Front Plate Sticker at the CIFX 70E-RE, CIFX 70E-RE\MR or CIFX 100EH-
RE\CUBE
Figure 57: Front Plate Stickers for CIFX 70E-RE, CIFX 70E-RE\MR
Sercos Master
PROFINET IO
Sercos Slave
Modbus/TCP
LED POWERLINK
EtherNet/IP
Field Basic
CC-Link IE
EtherCAT
EtherCAT
VARAN
Master
Slave
Open
SYS
SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS
(yellow/green)
COM 0
RUN RUN MS RUN BS SF STA S RUN RUN
(red/ green)
COM 1
ERR ERR NS ERR BE BF ERR - ERR ERR
(red/ green)
green LINK L/A IN LINK LINK L/A LINK L/A L/A LINK IN L/A
RJ45
Ch0
yellow ACT - ACT ACT - RX/TX - - ACT IN -

green LINK L/A OUT LINK LINK L/A LINK L/A L/A L/A
RJ45
LINK OUT
Ch1
yellow ACT - ACT ACT - RX/TX - - ACT OUT -
Table 34: LED Labeling depending of the loaded Firmware, CIFX 70E-RE, CIFX 70E-
RE\MR
Figure 58: Front Plate Stickers for CIFX 100EH-RE\CUBE
6.2 Installing PC Card cifX PCI, PCIe, Low Profile PCIe

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

2. Fix front plate sticker (only for CIFX 50-RE, CIFX 50E-RE, CIFX 50E-
RE\ET, CIFX 70E-RE, CIFX 70E-RE\MR or CIFX 100EH-RE\CUBE).
 Use the sticker according to the device and firmware and glue it on the
front of the PC card cifX (see section Fix Front Plate Sticker on page
96).
3. Set Slot Number (Card ID).
 For devices with Rotary Switch Slot Number (Card ID) set the Slot
Number (Card ID): (Value 0 or a value from 1 to 9), (see section Rotary
Switch for Slot Number (Card ID) on page 141).
4. Take safety precautions.

 Disconnect the power plug of the PC or of the connecting device.
device.
Device Damage!
 The PC card CIFX 100EH-RE\CUBE may not be installed in standard
PCs. The pin assignment of the PCI Express bus does not meet the
standard [bus spec 3]. By consequence malfunction can occur at the
PCI express bus.
 Install the PC card CIFX 100EH-RE\CUBE exclusively in KEBA
KeControl industry PCs series CP 3XX (Cube).
5. Open cabinet.
 Open the cabinet of the PC or of the connecting device.
6. Install PC card cifX.

 Plug the PC card cifX PCI into a free PCI slot.
 Plug the PC card cifX PCI Express or Low Profile PCI Express into a
free PCI express slot.
 Fix the PC card cifX using the hole intended.
After this:
7. Close cabinet.
 Close the cabinet of the PC or connecting device.
8. Plug the connecting cable to the Master or Slave.
 Note for the PC cards cifX Real-Time Ethernet::
Note: The RJ45 socket is only for use in LAN, not for telecommunication
circuits. For further information refer to section Ethernet Interface on
page 135.
 Plug the connecting cable from the PC card cifX to the PC card Master
or Slave.
9. Connect the PC or the connecting device to the power supply and
switch it on.
 Connect the PC or the connecting device to the power supply.
 Switch on the PC or the connecting device.
6.3 Uninstalling the PC Card cifX PCI, PCIe, Low Profile PCIe
1. Take safety precautions.

 Disconnect the power plug of the PC or of the connecting device.
device.

2. Remove the connecting cable to the Master or Slave.

 Remove the connecting cable between the PC card cifX to be replaced
and the PC card Master or Slave.
3. Open cabinet.
 Open the cabinet of the PC or of the connecting device.
4. Uninstall PC card cifX.
 Loosen the PC card cifX.
 Remove the PC card cifX from the PCI slot or from the PCI express
slot.
After this:
5. Close cabinet.
 Close the cabinet of the PC or connecting device.
.
Troubleshooting 101/284
7 Troubleshooting
7.1 Instructions for Problem Solving
In case of any error, follow the instructions for problem solving given here:
General
 Check the PC card cifX operating requirements according to the
requirements given in section Requirements for Operation on page 45.
SYS and COM Status LEDs Troubleshooting of the system is done by
examining the LEDs behaviour. The PC cards cifX have depending by card
type two or three bicolor status LEDs, which inform the user about the
communication state of the device.
• The SYS LED shows the common system status of the device. It can be
yellow or green ON or it can blink green/yellow.
• The COM LEDs display the status of the Real-Time Ethernet or fieldbus
communication. Depending by protocol and state, the LEDs can be ON
or flash cyclic or acyclic in green or red (or orange).
If the LED SYS is solid green and the LED COM or COM0 is static green,
the PC card cifX is in operational state, the Master is in data exchange with
the connected Slaves and the communication is running without fault. The
meaning of the LEDs is described in chapter LED Descriptions beginning
from page 102.
LINK-LED (for PC cards cifX Real-Time Ethernet)
 Check using the LINK LED’s status whether a connection to the
Ethernet is established. Therefore use the description on the LINK LED
in the chapter LED Descriptions beginning from page 102.
Cable
 Check that the pin assignment of the cable is correct. I. e., the cable by
which you connect the PC card cifX to the PC card Master or Slave.
Firmware CC-Link IE Field Slave
 Use the PC cards CIFX 50E-CCIES or CIFX 70E-CCIES only together
with the CC-Link IE Field Slave firmware and do not use this firmware
for any other cards.
Configuration
 Check the configuration in the Master device and the Slave device. The
configuration has to match.
Diagnosis
Via Online > Diagnosis (for SYCON.net) or netX Configuration Tool >
Diagnostics (for netX Configuration Tool) the diagnostic information of the
device is shown. The shown diagnostic information depends on the used
protocol.
Further information about the device diagnosis and its functions you find
in the operating instruction manual of the corresponding Real-Time
Ethernet or fieldbus system.
LED Descriptions 102/284
8 LED Descriptions
The LEDs will be used to indicate status information of the PC card cifX.
Each LED has a specific function during Run, configuration download and
error indications. The descriptions hereafter show the reaction of each LED
for the PC card cifX during these states.
8.1 Overview LEDs Real-Time Ethernet Systems

Note: The meaning of the communication status LEDs and of the Ethernet
LEDs at the device is defined by the loaded firmware of the predocol.
Sercos Master
LED Naming
PROFINET IO
Sercos Slave
Modbus/TCP
POWERLINK
in the Device
EtherNet/IP
Field Basic
CC-Link IE
EtherCAT
EtherCAT
Drawing
VARAN
Master
Open-
Slave
SYS (System SYS SYS SYS SYS SYS SYS SYS SYS SYS SYS
Status)
(yellow/green)
COM 0 RUN RUN MS RUN BS SF STA S RUN RUN
(Communication
Status)
(green) (green) (red/gree (green) (green) (red) (green) (green) (green)
n) (red/
green/
orange)
COM 1 ERR ERR NS ERR BE BF ERR - ERR ERR

(Communication
Status)
(red) (red) (red/ (red) (red) (red) (red) (red) (red)
green)
Ethernet Ethernet
(green) LINK L/A IN LINK LINK L/A LINK L/A L/A LINK IN L/A
Ch0
(yellow) ACT - ACT ACT - RX/TX - - ACT IN -
(green) - L/A OUT LINK LINK L/A LINK L/A L/A LINK OUT L/A
Ch1
(yellow) - - ACT ACT - RX/TX - - ACT OUT -

Table 35: Overview LEDs Real-Time Ethernet Systems
LED Name Meaning LED Name Meaning

System Status SYS System Status LINK, L Link
COM Communication Status ACT, A Activity
RUN Run L/A Link/Activity
ERR Error L/A IN Link/Activity Input
STA Status L/A OUT Link/Activity Output
MS Module Status Ethernet LINK IN Link Input
Kommunikations-
status
NS Network Status LINK OUT Link Output
BS Bus Status ACT IN Activity Input
BE Bus Error ACT OUT Activity Output
SF System Failure
RX/TX Receive/Transmit
BF Bus Failure
S Status / Error
Table 36: LED Names
Note: The PC cards CIFX 50E-CCIES and CIFX 70E-CCIES are based
on their own hardware and are equipped with several LEDs that are
different from those of the PC cards cifX RE variants. The descriptions of
the CC-Link IE Field slave LEDs are given in the CC-Link IE Field Slave
section on page 106.
8.2 Overview LEDs Fieldbus Systems

LED
PROFIBUS MPI
PROFIBUS DP
(1 Duo LED)
(1 Duo LED)
(1 Duo LED)
(1 Duo LED)
DeviceNet
CANopen
(2 LEDs)
CC-Link
(Slave)
System Status SYS SYS SYS SYS SYS
(yellow/green)
Communication Status COM COM CAN MNS L RUN
(green)
(red/green) (green) (red/green) (red/green)
L ERR
(red)
Table 37: Overview LEDs by Fieldbus System for 1 Channel Devices
LED
PROFIBUS D
AS-Interface
(1 Duo LED/
(1 Duo LED/
(1 Duo LED/
(1 Duo LED/
DeviceNet
CANopen
(Master)
channel)
channel)
channel)
channel)
System Status (yellow/green)
SYS SYS SYS SYS
Communication Status (red/green)

Channel X1 (SYCONnet: Ch0) COM0 CAN0 MNS0 COM1
Channel X2 (SYCONnet: Ch1) COM1 CAN1 MNS1 COM2
Table 38: Overview LEDs by Fieldbus System for 2 Channel Devices
LED Name Meaning

System Status SYS System Status
COM Communication Status
CAN CANopen Status
Communication Status
MNS Module Network Status
L RUN / L ERR Status Run / Status Error
Table 39: LED Names
* Descriptions for 2-Communication Status LEDs of PROFIBUS DP

Master and Slave devices as well as of CANopen Master and Slave
devices of earlier device revisions are included in the user manual for PC
cards cifX fieldbus up to manual revision 23.
8.3 System LED

The System Status LED SYS can assume the states described below.
LED Color State Meaning
SYS Duo LED yellow/green
(green) On Operating System running
Blinking, Second stage bootloader is waiting for firmware.

(green/yellow) cyclic
(yellow) On Bootloader netX (= romloader) is waiting for second stage bootloader.
(off) Off Power supply for the device is missing or hardware defect.
Table 40: System Status LED States
8.4 CC-Link IE Field Basic Slave

For the CC-Link IE Field Basic Slave protocol, the communication LEDs
RUN and ERR as well as the Ethernet LED L/A can assume the states
described below.
RUN Duo LED red/green
(Run) On Station in operation and cyclic transmission in progress.
(green)
General
name: (green)
Blinking (2.5 Hz) Station in operation and cyclic transmission stopped.
COM0
(green)
Flickering (10 Hz) Station not configured.
(off)
Off Station is disconnected.
ERR (red)
On Communication error.
(Error)
(red)
Triple Flash DPM watchdog has expired.
General
name: Off Station is disconnected.
COM1 (off)
L/A LED green

Ch0 & Ch1 Link: The station is linked to the Ethernet, but does not
(green)
On
send/receive Ethernet frames.
(green)
Flickering (load Activity: The station is linked to the Ethernet and sends/receives
dependent) Ethernet frames.
(off)
Off The station has no link to the Ethernet.
Ch0 & Ch1 LED yellow
(off)
Off This LED is not used.
Table 41: LED states for the CC-Link IE Field Basic Slave
LED State Definition

Triple Flash The indicator shows a sequence of three 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).
Blinking (2.5 Hz) The indicator turns on and off with a frequency of 2.5 Hz:
“on” for 200 ms, followed by “off” for 200 ms.
Flickering (10 Hz) The indicator turns on and off with a frequency of 10 Hz:
Flickering The indicator turns on and off with a frequency of approximately 10 Hz to indicate high
(load dependent) Ethernet activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on
and off in irregular intervals to indicate low Ethernet activity.
Table 42: LED state definitions for theCC-Link IE Field Basic Slave protocol
8.5 CC-Link IE Field Slave

For the CC-Link IE Field Slave protocol, the communication LEDs RUN,
RD, SD, D-LINK, ERR, USER1 and USER2 as well as the Ethernet-LEDs
LINK0 or L-ERR0 and LINK1 or L-ERR1 can assume the states described
below. This description is valid from CC-Link IE Field Slave stack version
V1.1.
RUN LED green: Indicates the operation status.
(green)
On Operating normally (depending from the netX firmware “BusOn” status)
(off)
Off A watchdog timer error or a hardware failure has occurred.
RD LED green: Displays the reception status of the data.
(green)
On Receiving data.
(off)
Off Data not received.
SD LED green: Displays the sending status of the data.
(green)
On Sending data.
(off)
Off Data not sent.
D-LINK LED yellow: Indicates the status of the data link.
(yellow)
On Data link in operation (cyclic transmission in progress)
(yellow)
Blinking Data link in operation (cyclic transmission stopped)
(off)
Off Data link not performed (disconnected)
ERR LED red: Indicates the CP520 error status.
(red)
On Error in own station
(off)
Off Normal operation
USER1 LED yellow: Indicates an user-defined status 1.
(yellow)
On Currently not used
(off)
Off Currently not used
USER2 LED yellow: Indicates an user-defined status 2.
(yellow)
On Currently not used
(off)
Off Currently not used
LINK0, LED green

LINK1
(green)
On Link up
Ch0 & Ch1
(Off)
Off Link down
L-ERR0, LED yellow

L-ERR1
(yellow)
On Abnormal data received or loopback in progress
Ch0 & Ch1
(Off)
Off Normal data received or loopback not performed
Table 43: LED states for the CC-Link IE Field Slave protocol
Name Meaning Name Meaning

RUN Run ERR Error
RD Reception status of the data USER User-defined status
SD Sending status of the data LINK Link status
D-LINK Data link L-ERR Error status of the received data, the line and the loopback
Table 44: LED Names CC-Link IE Field Slave protocol
8.6 EtherCAT Master V3

For the EtherCAT Master protocol, the communication LEDs RUN and ERR
as well as the Ethernet LEDs LINK and ACT can assume the states
described below. This description is valid from stack version V3.0.
General Off INIT: The device is in state INIT.
(off)
name:
COM 0 Blinking PRE-OPERATIONAL: The device is in PRE-OPERATIONAL state.
(green) (2,5 Hz)
Flickering BOOT: Device is in Boot mode.
(green) (10 Hz)
Single flash SAFE-OPERATIONAL: The device is in SAFE-OPERATIONAL state.
(green)
On OPERATIONAL: The device is in OPERATIONAL state.
(green)
ERR Duo-LED red/green
General Off Master has no errors.
(off)
name:
COM 1 (red)
On Master has detected a communication error. The error is indicated in
the DPM.
LINK LED green
Ch0
On The device is linked to the Ethernet.
(green)
(off)
Off The device has no link to the Ethernet.
ACT LED yellow

Ch0
Flickering The device sends/receives Ethernet frames.
(yellow) (load
dependant)
(off)
Off The device does not send/receive Ethernet frames.
Table 45: LED states for the EtherCAT Master protocol

Blinking The indicator turns on and off with a frequency of 2,5 Hz:
(2,5 Hz) “on” for 200 ms, followed by “off” for 200 ms.
Flickering The indicator turns on and off with a frequency of 10 Hz: “on” for 50 ms, followed by “off” for 50
(10 Hz) ms.
Single flash The indicator shows one short flash (200 ms) followed by a long “off“ phase (1,000 ms).
Flickering (load The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet
dependant) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in
irregular intervals to indicate low Ethernet activity.
Table 46: LED state definitions for the EtherCAT Master protocol
8.7 EtherCAT Master V4

For the EtherCAT Master protocol, the communication LEDs RUN and ERR
(off)
name:
COM 0 Blinking PRE-OPERATIONAL: The device is in PRE-OPERATIONAL state.
(green) (2,5 Hz)
Flickering The device is not configured.
(green) (10 Hz)
(green)
(green)
General Off Master has no errors.
(off)
name:
COM 1 (red)
Single flash Bus Sync error threshold
(red)
Double flash Internal Stop of the bus cycle
(red)
(red)
Quadruple No Master license present in the device.
Flash
(red)
Blinking Error in the configuration database.
(2,5 Hz)
(red)
Single Channel Init was executed at the Master.
Flickering Remarks: Transient error so can happen to be not visible at all.
(red)
Double Slave is missing.
Flickering Unconfigured Slave
No matching mandatory slave list
No bus connected
(red)
Flickering Boot-up was stopped due to an error.
(10 Hz)
LINK LED green
Ch0 On Link: The device is linked to the Ethernet, but does not
(green) send/receive Ethernet frames.
Flickering Activity: The device is linked to the Ethernet and sends/receives
(green) (load Ethernet frames.
dependent)
(off)
ACT LED yellow

Ch0
(off)
Table 47: LED states for the EtherCAT Master protocol

Double flash The indicator shows a sequence of two short flashes (each 200 ms), separated by a short off
Triple Flash The indicator shows a sequence of three 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).
Quadruple The indicator shows a sequence of four short flashes (each 200 ms), separated by a short off
Flash phase (200 ms). The sequence is finished by a long off phase (1,000 ms).
Single The indicator is switched on and off once: 'on' for 50 ms, followed by 'off' for 500 ms.
Flickering
Double The indicator is switched on and off and on once: 'on' / 'off' / 'on' each for approximately 50
Flickering ms, followed by 'off' for 500 ms.
(10 Hz) ms.
Flickering The indicator turns on and off with a frequency of approximately 10 Hz to indicate high Ethernet
(load dependant) activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in
Table 48: LED state definitions for the EtherCAT Master protocol
8.8 EtherCAT Slave

For the EtherCAT Slave protocol, the communication LEDs RUN and ERR
as well as the Ethernet-LED L/A IN or L/A OUT can assume the states
described below. This description is valid from stack version V2.5 (V2).
(off)
name:
COM 0 (green)
Blinking PRE-OPERATIONAL: The device is in PRE-OPERATIONAL state.
(2,5 Hz)
(green)
(green)

General Off No error: The EtherCAT communication of the device is in working
(off)
name: condition.
COM 1
(red)
Blinking Invalid configuration: General Configuration Error
(2,5 Hz) Possible reason: State change commanded by master is impossible
due to register or object settings.
(red)
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.
(red)
Double Application watchdog timeout: An application watchdog timeout has
Flash occurred.
Possible reason: Sync Manager Watchdog timeout.
L/A IN or LED green
L/A OUT
(green)
On Link: The device is linked to the Ethernet, but does not send/receive
Ethernet frames.
(green)
Flickering Activity: The device is linked to the Ethernet and sends/receives
(load Ethernet frames.
dependant)
(off)
LED yellow
(off)
Table 49: LED states for the EtherCAT Slave protocol
LED State Beschreibung

Table 50: LED state definitions for the EtherCAT Slave protocol
8.9 EtherNet/IP Scanner (Master)

For the EtherNet/IP Scanner protocol, the communication LEDs MS and
NS as well as the Ethernet LEDs LINK and ACT can assume the states
MS Duo-LED red/green
(Module On Device operational: The device is operating correctly.
status) (green)
General Flashing Standby: The device has not been configured.

name: (green) (1 Hz)
COM 0 Self-test: The device is performing its power-up testing.
Flashing
(green/red/
green) The module status indicator test sequence occurs before the network status
indicator test sequence, according to the following sequence:
• Network status LED off.
• Module status LED turns green for approximately 250 ms, turns red
for approximately 250 ms, and again turns green (and holds that
state until the power-up test has completed).
• Network status LED turns green for approximately 250 ms, turns red
for approximately 250 ms, and then turns off (and holds that state
until the power-up test has completed).
(red)
Blinking Major recoverable fault: The device has detected a major recoverable fault.
(1 Hz) E.g., an incorrect or inconsistent configuration can be considered a major
recoverable fault.
(red)
On Major unrecoverable fault: The device has detected a major unrecoverable
fault.
(Off)
Off No power: The device is powered off.
NS Duo-LED red/green
(Network- Connected: An IP address is configured, at least one CIP connection (any
On
status)
(green) transport class) is established, and an Exclusive Owner connection has not
General timed out.
name::
Flashing No connections: An IP address is configured, but no CIP connections are
COM 1
(green) (1 Hz) established, and an Exclusive Owner connection has not timed out.
Flashing Self-test: The device is performing its power-up testing. Refer to description
(green/red/ for module status LED self-test.
off)
(red)
Blinking Connection timeout: An IP address is configured, and an Exclusive Owner
(1 Hz) connection for which this device is the target has timed out.
The network status indicator returns to steady green only when all timed out
Exclusive Owner connections are reestablished.
(red)
On Duplicate IP: The device has detected that its IP address is already in use.
(Off)
Off Not powered, no IP address: The device does not have an IP address (or is
powered off).
LINK LED green
Ch0 & Ch1
(green)
(Off)
ACT LED yellow

Ch0 & Ch1 Flickering The device sends/receives Ethernet frames.
(yellow) (load de-
pendant)
(Off)
Table 51: LED states for the EtherNet/IP Scanner protocol
LED state Definition

Blinking The indicator turns on and off with a frequency of 1 Hz:
(1 Hz) “on” for 500 ms, followed by “off” for 500 ms.
(load activity: on for approximately 50 ms, followed by off for 50 ms. The indicator turns on and off in
dependant) irregular intervals to indicate low Ethernet activity.
Table 52: LED state definitions for the EtherNet/IP Scanner protocol
8.10 EtherNet/IP Adapter (Slave)

For the EtherNet/IP Adapter protocol, the communication LEDs MS and NS
described below. This description is valid from stack version V2.7 (V2) or
from V3.0.
MS Duo-LED red/green
(Module Device operational: The device is operating correctly.
(green)
On
status)
General (green)
Flashing Standby: The device has not been configured.
name: (1 Hz)
COM 0 Flashing Self-test: The device is performing its power-up testing.
(green/red/
green) The module status indicator test sequence occurs before the network
status indicator test sequence, according to the following sequence:
• Network status LED off.
• Module status LED turns green for approximately 250 ms, turns
red for approximately 250 ms, and again turns green (and holds
that state until the power-up test has completed).
• Network status LED turns green for approximately 250 ms, turns
red for approximately 250 ms, and then turns off (and holds that
state until the power-up test has completed).
(red)
Blinking Major recoverable fault: The device has detected a major recoverable
(1 Hz) fault. E.g., an incorrect or inconsistent configuration can be considered a
major recoverable fault.
(red)
On Major unrecoverable fault: The device has detected a major
unrecoverable fault.
(Off)
Off No power: The device is powered off.
NS Duo-LED red/green
(Network- Connected: An IP address is configured, at least one CIP connection (any
(green)
On
status)
transport class) is established, and an Exclusive Owner connection has not
General timed out.
name::
(green)
Flashing No connections: An IP address is configured, but no CIP connections are
COM 1
(1 Hz) established, and an Exclusive Owner connection has not timed out.
Flashing Self-test: The device is performing its power-up testing. Refer to
(green/red/ description for module status LED self-test.
off)
(red)
Blinking Connection timeout: An IP address is configured, and an Exclusive
(1 Hz) Owner connection for which this device is the target has timed out.
The network status indicator returns to steady green only when all timed
out Exclusive Owner connections are reestablished.
(red)
On Duplicate IP: The device has detected that its IP address is already in use.
(Off)
Off Not powered, no IP address: The device does not have an IP address (or
is powered off).
LINK LED green
Ch0 & Ch1
(green)
(Off)
ACT LED yellow

Ch0 & Ch1 Flickering
(yellow)
The device sends/receives Ethernet frames.
(load de-
pendant)
(Off)
Table 53: LED states for the EtherNet/IP Adapter protocol

Blinking The indicator turns on and off with a frequency of 1 Hz:
Table 54: LED state definitions for the EtherNet/IP Adapter protocol
8.11 Open Modbus/TCP

For the OpenModbusTCP protocol, the communication LEDs RUN and
ERR as well as the Ethernet LEDs LINK and ACT can assume the states
RUN Duo-LED red/green
General On Connected: OMB task has communication. At least one TCP connection is
name: (green) established.
COM 0
Flashing Ready, not yet configured: OMB task is ready and not yet configured.
(green) (1 Hz)
Flashing Waiting for Communication: OMB task is configured.
(green) (5 Hz)
(off)
Off Not Ready: OMB task is not ready.

General Off No communication error
(off)
name:
COM 1 (red)
Flashing System error
(2 Hz,
25% on)
(red)
On Communication error active
LINK LED green

Ch0 & Ch1 On The device is linked to the Ethernet.
(green)
(off)
ACT LED yellow

Ch0 & Ch1
Flicker- The device sends/receives Ethernet frames.
(yellow) ing (load
depen-
dant)
(off)
Table 55: LED states for the OpenModbusTCP protocol

Flashing (1 Hz) The indicator turns on and off with a frequency of 1 Hz:
Flashing (2 Hz, The indicator turns on and off with a frequency of 2 Hz:
25% on) “on” for 125 ms, followed by “off” for 375 ms.
Table 56: LED state definitions for the OpenModbusTCP protocol
8.12 POWERLINK Controlled Node/Slave V2, V3

For the POWERLINK Controlled Node protocol, the communication LEDs
BS (Bus Status) and BE (Bus Error) as well as the Ethernet LED L/A can
assume the states described below. This description is valid from stack
version V2.1 respectively from stack version V3.0.
BS Duo LED red/green
(Bus Status) Slave is in ‘Operational’ state
(green)
On
General
name: (green)
Triple Flash Slave is in ‚ReadyToOperate’ state
COM 0
(green)
Double flash Slave is in ‚Pre-Operational 2’ state
(green)
Single flash Slave is in ‚Pre-Operational 1’ state
(green)
Flickering Slave is in ‚Basic Ethernet’ state
(10 Hz)
(green)
Blinking Slave is in ‚Stopped’ state
(2,5 Hz)
(off)
Off Slave initializing
BE Duo LED red/green

(Bus Error)
(off)
Off Slave has no error
General
name: (red)
On Slave has detected an error
COM 1
L/A LED green
Ch0 & Ch1 Link: The device is linked to the Ethernet, but does not
(green)
On
(green)
Flickering (load Activity: The device is linked to the Ethernet and sends/receives
dependant) Ethernet frames.
(off)
(off)
Table 57: LED states for the POWERLINK Controlled Node protocol

Flickering The indicator turns on and off with a frequency of 10 Hz: “on” for 50 ms, followed by off for 50 ms.
(10 Hz) The red LED and the green LED are switched on alternately.
Blinking The indicator turns on and off phase with a frequency of 2.5 Hz:
(2,5 Hz) on for 200 ms, followed by off for 200 ms. The red LED and the green LED are switched on
alternately.
Table 58: LED state definitions for the POWERLINK Controlled Node protocol
8.13 PROFINET IO-Controller V2

For the PROFINET IO-Controller protocol, the communication LEDs SF
(system failure) and BF (bus failure) as well as the Ethernet LEDs LINK
and RX/TX can assume the states described below. This description is
valid from stack version V2.6.
SF (System Duo LED red/green
Failure) No error
(off)
Off
General
name: (red)
Flashing DCP signal service is initiated via the bus.
COM 0 (1 Hz, 3 s)
(red)
Flashing System error: Invalid configuration, Watchdog error or internal error
(2 Hz)
(red)
On No valid Master license
(together
with SF „red
ON)
BF Duo LED red/green
(Bus No error
(off)
Off
Failure)
General (red)
Flashing Configuration fault: Not all configured IO-Devices are connected.
name: (2 Hz)
COM 1 On No valid Master license
(red)
(together
with SF „red
ON")
(red)
On No Connection: No Link.
(together
with SF „red
OFF")
LINK LED green
Ch0 & Ch1
(green)
(off)
RX/TX LED yellow

Ch0 & Ch1 Flickering The device sends/receives Ethernet frames.
(gelb)
(load de-
pendant)
(off)
Table 59: LED states for the PROFINET IO-Controller protocol

Flashing The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed
(1 Hz, 3 s) by “off” for 500 ms.
Table 60: LED state definitions for the PROFINET IO-Controller protocol
8.14 PROFINET IO Controller V3
For the PROFINET IO Controller protocol, the system status LED SYS, the
communication LEDs SF (system failure) and BF (bus failure), as well as
the Ethernet LEDs LINK and RX/TX can assume the states described
below. This description is valid from stack version V3.0.
SYS SF BF Meaning
Systen Status System Bus Failure LED name
Failure
COM 0 COM 1 General LED name
yellow/green red/green red/green Colours of the Duo LEDs SYS, SF or BF
Firmware and Configuration
Off Off Off Power supply for the device is missing or hardware defect.
On, yellow Off Off No second stage bootloader found in Flash memory.
Off Off No firmware file found in Flash file system.

Flashing,
green/yellow,
cyclic
On, green On, red Off PROFINET IO Controller is not configured.
On, green Off On, red No Ethernet port has a link. E.g., no cable connected to any of
the Ethernet ports.
On, green Off Flashing, PROFINET IO Controller is not online (Bus is switched to Off).
red, 2 Hz
PROFINET communication
On, green Off Flashing, Not all configured devices are in data exchange.
or red, 1 Hz
On, red
On, green On, red - One IO Device connected to the PROFINET IO Controller
reports a problem.
On, green Off Off All devices are in data exchange and no problem has been
reported by any device.
PROFINET IO Controller operation
On, green Flashing, Off A PROFINET DCP Set Signal has been received.
red, 1 Hz, 3 s
On, green Flashing, Flashing, The PROFINET IO Controller has detected an address conflict.
red, 2 Hz red, 2 Hz Another device in the network is using the same Name of
Station or IP address as the PROFINET IO Controller.
Or
Watchdog error
On, green On, red On, red No valid Master license
Table 61: PROFINET IO Controller, SYS, COM0 and COM1 LEDs states

LINK LED green
Ch0 & Ch1 On The device is linked to the Ethernet.
(green)
(off) Off The device has no link to the Ethernet.
RX/TX LED yellow

Ch0 & Ch1
(gelb) (load
dependent)
(off) Off The device does not send/receive Ethernet frames.
Table 62: PROFINET IO Controller, Ethernet LEDs states

Flashing The indicator turns on and off for 3 seconds with a frequency of 1 Hz:
(1 Hz, 3 s) “on” for 500 ms, followed by “off” for 500 ms.
Flashing The indicator turns on and off with a frequency of 1 Hz:
Table 63: PROFINET IO Controller, LEDs states definitions
8.15 PROFINET IO-Device

For the PROFINET IO-Device protocol, the communication LEDs SF
(System Failure) and BF (Bus Failure) as well as the Ethernet LEDs LINK
and RX/TX can assume the states described below. This description is
valid from stack version V3.x (V3).
SF (System Duo LED red/green
Failure)
(off)
Off No error
General
name: (red)
Flashing DCP signal service is initiated via the bus.
COM 0 (1 Hz, 3 s)
(red)
On Watchdog timeout; channel, generic or extended diagnosis present;
system error
BF Duo LED red/green
(Bus
(off)
Off No error
Failure)
General (red)
Flashing No data exchange
name: (2 Hz)
COM 1 On No configuration; or low speed physical link;
(red)
or no physical link
LINK LED green
Ch0 & Ch1
(green)
(off)
RX/TX LED yellow

Ch0 & Ch1 Flickering
(gelb)
The device sends/receives Ethernet frames.
(load de-
pendant)
(off)
Table 64: LED states for the PROFINET IO-Device protocol

Flashing The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed
(1 Hz, 3 s) by “off” for 500 ms.
Table 65: LED state definitions for the PROFINET IO-Device protocol
8.16 Sercos Master

For the Sercos Master protocol, the communication LEDs STA and ERR as
well as the Ethernet LED L/A can assume the states described below. This
description is valid from stack version V2.1.
STA Duo LED red/green
General On CP4: Communication phase 4
(green)
name:
COM 0 (green)
Triple Flash CP3: Communication phase 3
(green)
Double flash CP2: Communication phase 2
(green)
Single flash CP1: Communication phase 1
(green)
Blinking (2,5 Hz) CP0: Communication phase 0
(green)
Flickering (10 Hz) Master is not configured and is in NRT. After a status change
this isn't indicated again
(off)
Off NRT: Non Real-Time Mode
ERR Duo LED red/green
General Single flash Bus Sync error threshold
(red)
name:
COM 1 (red)
Double flash Internal Stop of the bus cycle
(red)
(red)
Quadruple Flash No Master license present in the device.
(red)
Blinking (2,5 Hz) Error in the configuration database.
(red)
Single Flickering Channel Init was executed at the Master.
(red)
Double Flickering Slave is missing.
(red)
Flickering (10 Hz) Boot-up was stopped due to an error.
(off)
Off No error
L/A LED green
Ch0 & Ch1 Link: The device is linked to the Ethernet, but does not
(green)
On
(green)
Flickering Activity: The device is linked to the Ethernet and
(load dependant) sends/receives Ethernet frames.
(off)
(off)
Table 66: LED states for the Sercos Master protocol

Quadruple Flash The indicator shows a sequence of four short flashes (each 200 ms), separated by a short off
Blinking (2,5 Hz) The indicator turns on and off with a frequency of 2,5 Hz: “on” for 200 ms, followed by “off” for
200 ms.
Single Flickering The indicator is switched on and off once: 'on' for 50 ms, followed by 'off' for 500 ms.
Double The indicator is switched on and off and on once: 'on' / 'off' / 'on' each for approximately 50 ms,
Flickering followed by 'off' for 500 ms.
Flickering The indicator turns on and off with a frequency of 10 Hz: 'on' for 50 ms, followed by 'off' for 50
(10 Hz) ms.
(load dependant) activity: 'on' for approximately 50 ms, followed by 'off' for 50 ms. The indicator turns on and off
in irregular intervals to indicate low Ethernet activity.
Table 67: LED state definitions for the Sercos Master protocol
8.17 Sercos Slave

For the Sercos Slave protocol, the communication LED S as well as the
Ethernet LED L/A can assume the states described below. This description
is valid from stack version V3.2.
S Duo LED red/green (orange = red/green simultaneously)
General On CP4: Communication phase 4:Normal operation, no error
(green)
name:
COM 0 (green)
Blinking (2 Hz) Loopback: The network state has changed from „fast-forward“
to „loopback“.
Flashing CP3: Communication phase 3
(green/orange) (3 x green/3s)
(2 x green/3s) CP2: Communication phase 2
(1 x green/3s) CP1: Communication phase 1
(orange)
On CP0: Communication phase 0
Blinking (2 Hz) HP0: Hot-plug mode

(orange/green)
(1 x orange/3s) HP1: Hot-plug mode
(2 x orange/3s) HP2: Hot-plug mode
Flashing (2 Hz) Identification:
(orange) Invoked by (C-DEV.Bit15 in the Device Control)
Or
SIP Identification Request
Flashing (2 Hz, MST losses ≥ (S-0-1003/2): The communication warning (S-
(green/red) min. 2s) DEV.Bit 15) is present in the Device Status.
Flashing (2 Hz) Application error (C1D): See GDP & FSP Status codes class
(red/orange) error.
(red)
Flashing (2 Hz) Watchdog error: Application is not running
(red)
On Communication Error (C1D): Error detected according to
Sercos third generation Class 1 Diagnosis, see SCP Status
codes class error.
(off)
Off NRT-Mode: (Non Real-Time Mode) No Sercos Communication
General Duo LED red/green
name: Off This LED is not used.
COM 1 (off)
L/A LED green

Ch0 & Ch1 On Link: The device is linked to the Ethernet, but does not
(green) send/receive Ethernet frames.
Flickering (load Activity: The device is linked to the Ethernet and sends/receives
(green) dependant) Ethernet frames.
(off)
(off)
Table 68: LED state definitions for the Sercos Slave protocol

one color: On for appr. 250 ms, followed by off for appr. 250 ms.
two colors: First color for appr. 250 ms, followed by the second color for appr. 250 ms.
Flashing
(1 x green/3s) Flashing green for 250 ms, then orange on for 2 second and 750 ms.
(2 x green/3s) Flashing green / orange / green, each for 250 ms, then orange on for 2 seconds and 250 ms.
(3 x green/3s) Flashing green / orange / green / orange / green, each for 250 ms, then orange on for 1 second
and 750 ms.
(1 x orange/3s) Flashing orange for 250 ms, then green on for 2 second an 750 ms.
(2 x orange/3s) Flashing orange / green / orange, each for 250 ms, then green on for 2 seconds and 250 ms.
dependant) activity: "on" for approximately 50 ms, followed by "off" for 50 ms. The indicator turns on and off
in irregular intervals to indicate low Ethernet activity.
Table 69: LED state definitions for the Sercos Slave protocol
8.18 VARAN Client (Slave)

For the VARAN Client protocol, the communication LEDs RUN and ERR as
well as the Ethernet LEDs LINK IN and LINK OUT or ACT IN and ACT
OUT can assume the states described below. This description is valid from
stack version V1.0.
RUN Duo-LED red/green
General On Configured and communication is active.
name: (green)
COM 0
Blinking (5 Hz) Configured and communication is inactive.
(green)
(off)
Off Not configured.

General Off Configured.
(off)
name:
COM 1 (red)
Blinking (5 Hz) Not configured.
(red)
On Communication error occurred.
LINK IN LED green

Ch0 &
LINK OUT
(green)
Ch1
(off)
ACT IN LED yellow

Ch0 &
ACT OUT
(yellow) (load
Ch1 dependant)
(off)
Table 70: LED-Zustände für das VARAN-Client-Protokoll

Blinking (5 Hz) The indicator turns on and off with a frequency of 5 Hz:
Table 71: Definitionen der LED-Zustände für das VARAN-Client-Protokoll
8.19 PROFIBUS DP Master

For the PROFIBUS DP Master protocol, the communication status LED
COM can assume the states described below. This description is valid from
stack version V2.6.
COM Duo LED red/green
(green)
On Communication to all Slaves is established.
(green)
Flashing (5 Hz) PROFIBUS is configured, but bus communication is not yet released
from the application.
(green)
Flashing acyclic No configuration or faulty configuration
(red)
Flashing (5 Hz) Communication to at least one Slave is disconnected.
(red)
On Communication to all Slaves is disconnected or another serious error
has occurred.
Redundant Mode: The active Master was not found.
(off)
Off Device is not switched on or network power is missing.
Table 72: LED states for the PROFIBUS DP Master protocol

"on" for 100 ms, followed by "off" for 100 ms.
Flashing The indicator turns on and off in irregular intervals.
acyclic
Table 73: LED state definitions for the PROFIBUS DP Master protocol
Note: For 2-Channel Devices per channel works 1 communication LED.
* Descriptions for 2-Communication Status LEDs of earlier device

revisions are included in the user manual for PC cards cifX fieldbus up to
manual rev. 23.
8.20 PROFIBUS DP Slave

For the PROFIBUS DP Slave protocol, the communication status LED
COM can assume the states described below. This description is valid from
stack version V2.7.
(green)
On RUN, cyclic communication
(green)
Flashing, Master is in CLEAR state.
cyclic (2 Hz)
(red)
Flashing, Device is not configured.
acyclic (1 Hz)
(red)
Flashing, STOP, no communication, connection error
cyclic (2 Hz)
(red)
On Wrong configuration at PROFIBUS DP Slave.
(off)
Off Device is not switched on or power is missing.
During firmware download process.
Table 74: LED states for the PROFIBUS DP Slave protocol

Flashing, The indicator turns on and off in irregular intervals, with a frequency
acyclic (1 Hz) of 1 Hz: “on” for 750 ms, followed by “off” for 250 ms.
Flashing, The indicator turns on and off with a frequency of 2 Hz:
cyclic (2 Hz) “on” for 250 ms, followed by “off” for 250 ms.
Table 75: LED state definitions for the PROFIBUS DP Slave protocol
Note: For 2-Channel Devices per channel works 1 communication LED.

manual rev. 23.
8.21 PROFIBUS MPI Device

For the PROFIBUS MPI protocol, the communication status LED COM can
version V2.4.
(green)
On Status: The device currently holds the PROFIBUS token and is
able to transfer telegrams of data.
(green)
Blinking (5 Hz) 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.
(green)
Blinking (0.5 Hz) Status: Automatic baudrate detection is running
(off)
Off Status: 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 76: LED states for the PROFIBUS MPI protocol

Blinking (5 Hz) The indicator turns on and off with a frequency of appr. 5 Hz:
“on” for appr. 100 ms, followed by “off” for appr. 100 ms.
Blinking (0.5 Hz) The indicator turns on and off with a frequency of appr. 0.5 Hz:
“on” for appr. 1000 ms, followed by “off” for appr. 1000 ms.
Table 77: LED state definitions for the PROFIBUS MPI protocol
8.22 CANopen Master
For the CANopen Master protocol, the communication status LED CAN
can assume the states described below. This description is valid from stack
version V2.11.
CAN Duo-LED red/green
(green)
On OPERATIONAL: The device is in the OPERATIONAL state.
(green)
Blinking (2,5 Hz) PREOPERATIONAL: The device is in the PREOPERATIONAL
state.
(green)
Single flash STOPPED: The device is in STOPPED state.
(red)
Single 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).
(red)
Double flash Error Control Event: A guard event (NMT Slave or NMT Master)
or a heartbeat event (Heartbeat consumer) has occurred.
(red)
On Bus Off: The CAN controller is in bus OFF state.
(aus)
Off RESET: The device is executing a reset or the device has no
configuration.
Table 78: LED states for the CANopen Master protocol

Blinking (2,5 The indicator turns on and off with a frequency of 2,5 Hz:
Hz) “on” for 200 ms, followed by “off” for 200 ms.
Double flash 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 79: LED state definitions for the CANopen Master protocol

manual rev. 23.
8.23 CANopen Slave
For the CANopen Slave protocol, the communication status LED CAN
version V3.4.
cifX with 1 Communication Status LED (current Hardware Revision)
CAN Duo LED red/green
(green)
On OPERATIONAL: The device is in the OPERATIONAL state.
(green)
Blinking PREOPERATIONAL: The device is in the PREOPERATIONAL state.
(2.5 Hz)
(green)
Single flash STOPPED: The device is in STOPPED state.
Flickering Auto Baud Rate Detection active: The Device is in the auto baud rate
(red/green) (10 Hz) detection mode.
(red)
Single 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).
(red)
Double flash Error Control Event: A guard event (NMT Slave or NMT Master) or a
heartbeat event (Heartbeat consumer) has occurred.
(red)
On Bus Off: The CAN controller is in bus OFF state.
(off)
Off RESET: The device is executing a reset or the device has no
configuration.
Table 80: States of the CAN LED for the CANopen Slave protocol – 1 Communication
Status LED (current Hardware Revision)

(10 Hz) ms.
Blinking The indicator turns on and off with a frequency of 2,5 Hz: “on” for 200 ms, followed by “off” for
(2.5 Hz) 200 ms.
Single Flash The indicator shows one short flash (200 ms) followed by a long “off” phase (1,000 ms).
Double Flash 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 81: LED state definitions for the CANopen Slave protocol

manual rev. 23.
8.24 DeviceNet Master

For the DeviceNet Master protocol, the communication status LED MNS
version V2.3.
MNS Duo LED red/green
(green)
On Device operational AND on-line, connected
Device is online and has established all connections with all Slaves.
(green)
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 (2Hz) Self test after power on
(green/red/ Green/Red/Off
Off)
(red)
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
Minor or recoverable fault: No data exchange with one of the
configured Slaves. One or more Slaves are not connected.
Connection timeout.
No network power present.
(red)
On Critical fault or critical link failure
Critical connection failure; device has detected a network error:
duplicate MAC-ID or severe error in CAN network (CAN-bus off).
(off)
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 yet completed the Dup_MAC_ID test.
- The device is powered, but the network power is missing.
Table 82: LED states for the DeviceNet Master protocol

Flashing (1 Hz) 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.
Flashing (2 Hz) The indicator turns on green on for 250 ms, then red on for 250 ms, then off.
green/red/off
Table 83: LED state definitions for the DeviceNet Master protocol
8.25 DeviceNet Slave

For the DeviceNet Slave protocol, the communication status LED MNS can
version V2.3.
MNS Duo LED red/green
(green)
On Device operational AND on-line, connected
Device is online and has established all connections with all Slaves.
(green)
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 (2Hz) Self test after power on
(green/red/ Green/Red/Off
Off)
(red)
Flashing (1 Hz) Minor fault and/or connection time-out
Device has no connectin to the Master.
Minor or recoverable fault: No data exchange with the Master.
Connection timeout.
No network power present.
(red)
On Critical fault or critical link failure
Critical connection failure; device has detected a network error:
duplicate MAC-ID or severe error in CAN network (CAN-bus off).
(off)
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 yet completed the Dup_MAC_ID test.
- The device is powered, but the network power is missing.
Table 84: LED states for the DeviceNet Slave protocol

Flashing (1 The indicator turns on and off with a frequency of appr. 1 Hz:
Hz) on for appr. 500 ms, followed by off for appr. 500 ms.
Flashing (2 The indicator turns on green on for 250 ms, then red on for 250 ms,
Hz) then off.
green/red/off
Table 85: LED state definitions for the DeviceNet Slave protocol
8.26 AS Interface Master

For the AS-Interface Master protocol, the communication status LED COM
version V2.3.
(green)
On No configuration error, data exchange
active
(green)
Flashing Configuration error, data exchange
active
(green)
Flickering The communication is stopped.
Flashing „Configuration mode“ active
(red/green)
(red)
Flashing AS-Interface power fail
(red)
On Heavy system error or hardware failure
(off)
Off No configuration found for this channel
Table 86: LEDs states for the AS-Interface Master protocol

On The indicator is constantly on.
Off The indicator is constantly off.
Flashing The indicator turns on and off cyclically in slowly changing phases.
Flickering The indicator turns on and off cyclically in rapidly changing phases.
Table 87: LED state definitions for the AS-Interface Master protocol
8.27 CC-Link Slave

For the CC-Link Slave protocol, the communication status LEDs L-RUN
and L-ERR can assume the states described below. This description is
valid from stack version V2.9.
L RUN LED green
On After participating in the network, the device receives both refresh and
(green) polling signals or just the refresh signal normally.
(off) Off 1. Before participating in the network

2. Unable to detect carrier
3. Timeout
4. Resetting hardware
L ERR LED red
(red) Blinking The switch setting has been changed from the setting at the reset
cancellation (blinks for 0.4 sec.).
(red) On 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)
(off) Off 1. Normal communication

2. Resetting hardware
Table 88: LED states for the CC-Link Slave protocol
Device Connections and Switches 135/284
9 Device Connections and Switches

9.1 Ethernet Interface
For the Ethernet interface use RJ45 plugs and twisted pair cable of
category 5 (CAT5) or higher, which consists of 4 twisted cores and has a
maximum transmission rate of 100 MBit/s (CAT5).
9.1.1 Ethernet Pin Assignment at the RJ45 Socket
100 BASE-TX and 10 BASE-T

For the PC cards CIFX 50-RE, CIFX 50E-RE, CIFX 50E-RE\ET, CIFX 70E-
RE, CIFX 70E-RE\MR, CIFX 100EH-RE\CUBE:
Note: The device supports the Auto Crossover function. Due to this fact
RX and TX can be switched. The following figure shows the RJ45
standard pin assignment.
Figure 59: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX
Pin Signal Meaning

1 TX+ Transmit Data +
2 TX– Transmit Data –
3 RX+ Receive Data +
4 Term 1 Connected to each other and
terminated to PE through RC circuit*
5 Term 1
6 RX– Receive Data –
7 Term 2 Connected to each other and
terminated to PE through RC circuit*
8 Term 2
* Bob Smith Termination
Table 89: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX
Further Notes:
(1) The RJ45 socket is only for use in LAN, not for telecommunication
circuits.
(2) With loaded EtherCAT Master firmware only the RJ45 channel 0 can
be used, channel 1 is deactivated. Beginning with the EtherCAT Master
firmware version 3 channel 1 can be reactivated if redundancy is
activated. For the Open Modbus/TCP firmware with V2.3.4.0 and higher
both RJ45channels can be used.
1000BASE-T
For the PC cards CIFX 50E-CCIES, CIFX 70E-CCIES:
Figure 60: Ethernet Pin Assignment at the RJ45 Socket (1000 MBit/s)
Pin Signal Meaning

1 D1+ Transmit/receive data positive channel 1
2 D1– Transmit/receive data negative channel 1
Use of Bob Smith Termination
Table 90: Ethernet Pin Assignment at the RJ45 Socket (1000 MBit/s)
9.1.2 Ethernet Connection Data

100 BASE-TX and 10 BASE-T 1000 BASE-T
Medium 2 x 2 Twisted-Pair copper cable, Copper cable*, Cat6, Cat6A, Cat7, Cat7A,
Cat5 (100 MBit/s) (1 Gbit/s)
*Fully occupied cable (all 8 cable cores)
Length of cable Max. 100 m Max. 100 m
Transmission rate 10 MBit/s/100 MBit/s 1 Gbit/s
Table 91: Ethernet Connection Data
9.1.3 Use of Hubs and Switches

For the corresponding communication systems, the use of hubs and/or
switches is either forbidden or allowed. The following table shows the
acceptable use of hubs and switches by each communication system:
Communication System Hub Switch
EtherCAT forbidden only allowed between EtherCAT Master and first EtherCAT Slave
(100 MBit/s, Full Duplex)
EtherNet/IP allowed allowed
(10 MBit/s/100 MBit/s, Full or Half Duplex, Auto-Negotiation)
Open Modbus/TCP allowed allowed
(10 MBit/s/100 MBit/s, Full or Half Duplex, Auto-Negotiation)
POWELINK allowed forbidden
PROFINET IO forbidden Only allowed if the switch supports ‚Priority Tagging’ and LLDP
(100 MBit/s, Full Duplex)
Sercos forbidden forbidden
VARAN* forbidden forbidden
Table 92: Use of Hubs and Switches
*Instead of hubs and switches VARAN uses splitter. [3]
9.2 PROFIBUS Interface

Isolated RS-485 interface:
Figure 61: PROFIBUS Interface (DSub female connector, 9 pin), X400
Connection with Signal Meaning

DSub female
connector
3 RxD/TxD-P Receive/Send Data-P respectively
connection B plug
5 DGND Reference potential
6 VP Positive supply voltage
8 RxD/TxD-N Receive/Send Data-N respectively
connection A plug
Table 93: PROFIBUS Interface, X400
9.3 CANopen Interface

Isolated ISO 11898 interface:
Figure 62: CANopen Interface (DSub male connector, 9 pin), X400
Connection with Signal Description

DSub male
connector
2 CAN_L CAN_Low Bus Line
3 CAN_GND CAN Ground
7 CAN_H CAN High Bus Line
1, 4, 5, 6, 8, 9 Do not connect!
Table 94: CANopen Interface, X400
9.4 DeviceNet Interface

Isolated ISO 11898 interface:
Figure 63: DeviceNet Interface (CombiCon male Connector, 5 pin), X360
Connection with Signal Color Description

CombiCon male
connector
1 V- Black Reference potential DeviceNet supply voltage
2 CAN_L Blue CAN Low-Signal
3 Drain Shield
4 CAN_H White CAN High-Signal
5 V+ Red +24 V DeviceNet supply voltage
Table 95: DeviceNet Interface, X360
9.5 AS-Interface Interface

The AS-Interface Master conforms to Complete Specification 2.11 (Annex
B, Version 2.0) the profile M3 (Full Extended Master).
AS-Interface interface according to IEC 364-4-41.
Figure 64: AS-Interface Interface (CombiCon male Connector, 2 pin)
Connection Signal Description

with
CombiCon
male
connector
1 AS-i + AS-Interface positive voltage
2 AS-i - AS-Interface negative voltage
Table 96: AS-Interface Interface
9.6 CC-Link Interface

Isolated RS-485 interface:
Figure 65: CC-Link Interface (CombiCon male Connector, 5 pin)
Connection with Signal Meaning

Screw terminal
Connector
1 DA Data A
2 DB Data B
3 DG Data Ground
4 SLD Shield
5 FG Field Ground
Table 97: CC-Link Interface
9.7 Rotary Switch for Slot Number (Card ID)

Device revisions equipped with a Rotary Switch Slot Number (Card ID)
are listed separately in section Hardware: PC Cards cifX in Table 2 on page
10.
The Rotary Switch Slot Number (Card ID) serves to set the Slot Number
(Card ID) of the PC cards cifX.
The figure below describes possible switch positions of the Rotary Switch
Slot Number (Card ID).
Switch Position Meaning
0 The value 0 means:
 no Slot Number (Card ID), i. e. the Slot Number (Card ID) is not used,
 for downwards compatibility purposes,
 characterizes PC cards cifX not equipped with a Rotary Switch Slot Number (Card ID);
i. e. these PC cards cifX are identified via its device number and serial number.
Example
Rotary Switch Slot Number (Card ID) Switch Position 0
1…9 corresponds to the Slot Number (Card ID) 1 … 9

Example
Table 98: Rotary Switch for Slot Number (Card ID), S1
9.7.1 Set Slot Number (Card ID)

If the Slot Number (Card ID) shall not be used:
 set the value 0.
Or
If the Slot Number (Card ID) shall be used:
 Set a value from 1 to 9.
For further information about the Slot Number (Card ID) refer to section
The Function „Slot Number (Card ID)“ (page 39) or to the user manual
Software Installation for the PC Cards cifX, sections Slot Number (Card ID)
in the cifX Device Driver Setup and Slot Number (Card ID) in the Configu-
ration Software.
9.7.2 Note for Device Exchange Service (Replacement Case):

Important: For PC cards cifX with Rotary Switch Slot Number (Card ID)
in terms of a device exchange service (replacement case) you must set at
the replacement card cifX the same Slot Number (Card ID) as at the
preceding cifX. Then the same firmware and configuration is loaded into
the replacement card cifX, as into the preceding cifX.
9.7.3 Rotary Switch Slot Number PC Cards cifX Low Profile

The Table 99 below shows the Rotary Switch Slot Number (Card ID) of
the PC cards cifX Low Profile PCI Express in switch position 0 and 1.
Description
Table 99: Rotary Switch Slot Number (Card ID) PC Cards cifX Low Profile PCI Express
9.8 SYNC Connector (Pin-Assignment, Hardware/Firmware)

9.8.1 Pin Assignment SYNC Connector, X51 (CIFX 50 50E 70E)
Only for:
CIFX 50-RE (from hardware Rev. 3 on), CIFX 50E-RE, CIFX 50E-RE\ET,
CIFX 70E-RE
Pin Signal
1 GND
2 IO_SYNC0
3 IO_SYNC1
Table 100: Pin Assignment for SYNC Connector, X51
9.8.2 Pin Assignment SYNC Connector, J1 (CIFX 100EH)

Only for: CIFX 100EH-RE\CUBE.
Pin Signal
1 IO_SYNC0
2 Jumper set: SYNC signal is transferred to the PCI Express Bus Pin B24*
Jumper not set: static high 3.3 V (with pull-up)
3 IO_SYNC1
Table 101: Pin Assignment for SYNC Connector, J1
Note! *
• If the jumper is set on Pin1-Pin2, then the IO_SYNC0 signal will be
transferred to the PCI Express Bus X2 (pin B24).
Or
• If the jumper is set on Pin2-Pin3, then the IO_SYNC1 signal will be
transferred to the PCI Express Bus X2 (pin B24).
Or
• If the no jumper is set, then the signal at the PCI Express Bus X2 pin
B24 will be static High 3.3 V (with pull-up).
Compare section Pin Assignment for PCI Express Bus CIFX 100EH-
9.8.3 Items on Hardware

Item Explanation
SYNC Signal 3.3 V (LVTTL), maximum load 6 mA
Connector SYNC connector, X51 (for the PC cards cifX, as indicated under section Pin Assignment SYNC
Connector, X51 (CIFX 50 50E 70E) on page 143.)
Female connector, 3 pin, pitch spacing 1.25 mm (for example, the type Molex series 51021)
and female crimp contacts in design (e. g. type Molex series 50079/50058)
SYNC connector, J1 (for CIFX 100EH-RE\CUBE)
Male Connector with jumper, 3 pin, pitch spacing 2,54 mm
Max. Cable Recommendation: Max. 50 mm
Length Note: Take EMC into consideration for the cable laying
Table 102: SYNC Connector: SYNC Signal, Connector, Max. Cable Length
9.8.4 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.
Protocol Signal IO_SYNC0 Signal IO_SYNC1 From Remarks
Input/Output Input/Output Firmware
Version
EtherCAT Slave SYNC 0 SYNC 1 - Configurable
Output Output
Sercos Master External trigger to start bus - 2.0.8.0 -
cycle
Input
Rising edge
Sercos Slave CON_CLK DIV_CLK 3.0.10.0 Configurable
Output Output
Table 103: Meaning of the SYNC Signals for each Protocol
9.9 Pin Assignment at the PCI Bus
9.9.1 Overview
For the PC cards cifX PCI, PCI Express and Low Profile PCI Express the table
below gives an overview about the pin assignment at the PCI bus.
PC Card cifX Hardware PCI Bus PCI Pin Assignment at the PCI Bus PCI
Revision Type Bus Specification
acc. to compare section, page
[Pins]
standard
CIFX 50-RE 6 PCI 124 yes - [bus spec 1]

CIFX 50-DP 6
CIFX 50-CO 6
CIFX 50-DN 6
CIFX 50-CC 2
CIFX 50-2DP 3
CIFX 50-2DP\CO 2
CIFX 50-2DP\DN 1
CIFX 50-2CO 2
CIFX 50-2CO\DN 1
CIFX 50-2DN 2
CIFX 50-2ASM 2
CIFX 50E-RE 6 PCI 36 yes - [bus spec 2,
CIFX 50E-RE\ET 2 Express Rev. 2.0],
CIFX 50E-CCIE 1 [bus spec 3]
CIFX 50E-DP 6
CIFX 50E-CO 5
CIFX 50E-DN 5
CIFX 50E-CC 4
CIFX 50E-2DP 1
CIFX 50E-2DP\CO 1
CIFX 50E-2DP\DN 1
CIFX 50E-2CO 1
CIFX 50E-2CO\DN 1
CIFX 50E-2DN 1
CIFX 50E-2ASM 5
CIFX 70E-RE 1
CIFX 70E-RE\MR 1
CIFX 50E-CCIE 1
CIFX 70E-DP 1
CIFX 70E-DP\MR 1
CIFX 70E-CO 1
CIFX 70E-CO\MR 1
CIFX 70E-DN 1
CIFX 70E-DN\MR 1
CIFX 100EH-RE\ 4 PCI 64 no Pin Assignment for PCI Express Bus [bus spec 2,
CUBE Express CIFX 100EH-RE\CUBE, 146 Rev. 2.0],
[bus spec 3]
Table 104: Pin Assignment at the PCI Bus
9.9.2 References PCI Specifications

No. Specification Revision Version Date www
[bus spec 1] PCI Local Bus Specification 2.3 - February 21, 2003 pcisig.com
[bus spec 2] PCI Express® Base Specification 2.0 - January 15, 2007
[bus spec 3] PCI Express® Card Electromechanical 2.0 - April 11, 2007
Specification
Table 105: References PCI Specifications
9.9.3 Pin Assignment for PCI Express Bus CIFX 100EH-RE\CUBE

Only for: CIFX 100EH-RE\CUBE (x1 = One Lane) 2
PCI Express Bus X2 (Side B) PCI Express Bus X1 (Side A)
Pin Name Description Pin Name Description
B1 n. u. (not used) A1 PRSNT1# Hot-Plug presence detect
B2 n. u. (not used) A2 n. u. (not used)
B4 GND Ground A4 GND Ground
B5 n. u. (not used) A5 JTAG-TCK JTAG Test Clock
B6 n. u. (not used) A6 JTAG-TDI JTAG Test Data Input
B7 GND Ground A7 JTAG-TDO JTAG Test Data Output
B8 3V3 3.3V Power A8 JTAG-TMS JTAG Test Mode Select Input
B9 JTAG-TRST# JTAG Test Reset A9 3V3 3.3V Power
B10 n. v. (not used) A10 3V3 3.3V Power
B11 n. u. (not used) A11 PERST# PCIe Reset
Key
B12 n. u. (not used) A12 GND Ground
B13 GND Ground A13 PCIe_CLK+ PCIe Clock
B14 PCIe_TP Transmitter Lane, A14 PCIe_CLK- differential pair
B15 PCIe_TN differential pair A15 GND Ground
B16 GND Ground A16 PCIe_RP Receiver Lane,
B17 PRSNT2# Hot-Plug presence detect A17 PCIe_RN differential pair
B18 GND Ground A18 GND Ground
B23 GND Ground A23 n. u. (not used)
B24 IO_SYNC0 / Real-Time Ethernet SYNC 4 A24 n. u. (not used)
IO_SYNC1 / 3.3V 3
B26 SPI_CS# ID Chip Select A26 n. u. (not used)
B27 SPI_MOSI ID Slave In A27 n. u. (not used)
B28 SPI_MISO ID Slave Out A28 n. u. (not used)
B29 SPI_CLK ID Clock A29 n. u. (not used)
Table 106: Pin Assignment for PCI Express-Bus CIFX 100EH-RE\CUBE
2Pinning A19 to A32 / B19 to B32 not standard conform [bus spec 3, page 73-74].
3Ifat the SYNC connector J1 the jumper is set, the IO_SYNC signal is transferred
to the PCI Express Bus X2 pin B24 (jumper on pin1-pin2(J1): IO_SYNC0, pin2-
pin3(J1): IO_SYNC1). If no jumper is set, the signal is 3,3V static High (with Pull-up).
Refer to section Pin Assignment SYNC Connector, J1 (CIFX 100EH), on page 111.
4in 3V3 logic.
Technical Data 147/284
10 Technical Data
10.1 Technical Data PC Cards cifX
Note: All technical data are temporarily and can be altered without notice.
10.1.1 CIFX 50-RE

CIFX 50-RE Parameter Value
Part Name CIFX 50-RE
Part No. 1250.100
Description PC Card cifX PCI Real-Time Ethernet Master or Slave
Function Communication interface with PCI and Ethernet interface
Communication Type netX 500 processor
Controller
Integrated Memory RAM 8 MB SDRAM
FLASH 4 MB serial Flash EPROM
Size of the Dual-Port Memory 64 KByte
System Interface Bus Type PCI, according to [bus spec 1], refer to section Overview,
page 145.
Transmission Rate 33 MHz
Data Access DPM or DMA (Direct Memory Access)
Width for the data access to the 32-Bit
Dual-Port Memory (DPM)
Ethernet Supported Real-Time Ethernet CC-Link IE Field Basic Slave
Communication communication systems
EtherCAT Master, EtherCAT Slave
(determined by the loaded
firmware) EtherNet/IP Scanner (Master),
EtherNet/IP Adapter (Slave),
Open Modbus/TCP
POWERLINK Controlled Node/Slave
PROFINET IO-Controller (Master),
PROFINET IO-Device (Slave)
Sercos Master, Sercos Slave
VARAN Client (Slave)
Ethernet Frame Types Ethernet II
Ethernet Interface Transmission rate 100 MBit/s, 10 MBit/s (depending on loaded firmware)
Interface Type 100 BASE-TX,
10 BASE-T (depending on loaded firmware),
refer to section Ethernet Interface, page 135.
Galvanic Isolation isolated
Isolation Voltage 1000 VDC (tested for 1 minute)
Half duplex/Full duplex depending on loaded firmware,
supported (at 100 MBit/s)
Auto-Negotiation depending on loaded firmware
Auto-Crossover depending on loaded firmware
Connector 2* RJ45 Socket
Channel 0 and 1 With loaded EtherCAT Master firmware only the RJ45
channel 0 can be used, channel 1 is deactivated.
Beginning with the EtherCAT Master firmware version 3
channel 1 can be reactivated if redundancy is activated.
For Open Modbus/TCP with V2.3.4.0 and higher both
CIFX 50-RE Parameter Value
RJ45 channels can be used.
Display LED Display SYS System Status LED
The meaning of the following LEDs depends on the loaded
firmware:
COM 0 LED Communication Status 0 (duo LED)
LED yellow at RJ45Ch0 and RJ45Ch1,
for Ethernet Link status, Ethernet Activity
LED green
status and additional status
Refer to chapter LED Descriptions, page 102.
Power supply Supply Voltage +3.3 V dc ±5 %, refer to section Power Supply and Host
Interface, page 44.
Current consumption at 3.3 V 650 mA (maximum)
Connector Via PCI Bus
Operation Rotary Switch Slot Number To set the Slot Number (Card ID)
(Card ID)
Environmental CIFX 50-RE (to Rev. 5) CIFX 50-RE (Rev. 6)
Conditions
Operating temperature range* 0 °C ... +55 °C 0 °C ... +70 °C
*Air flow during measurment 0,5m/s
Storage temperature range -40 °C ... +85 °C
Humidity 10 … 95% relative humidity, no condensation permitted
Environment For UL compliant usage:
The device must be used in a pollution degree 2
environment.
Device Dimensions (L x W x H) 120,0 x 86 x 18,5 mm (from hardware revision 3)
Mounting/Installation PCI slot (3.3 V), refer to section Slot for the PC Cards cifX
PCI, PCIe and Low Profile PCIe, page 43.
RoHS Yes
CE Sign CE Sign Yes
Emission EN 55011:2009 + A1:2010, CISPR 11:2009, Class A
(Radio disturbance characteristics - Limits and methods of
measurement)
Immunity EN 61000-4-2:2009 (Electrostatic discharge test)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
radio-frequency, electromagnetic field test)
EN 61000-4-4:2004 + A1:2010 (Burst Electrical fast
transients/burst test)
EN 61000-4-5:2006 (Surge test)
EN 61000-4-6:2009 (to conducted disturbances, induced
by radio- frequency fields)
EN 61000-4-8:2010 (power frequency magnetic field test)
EN 61000-6-2:2005 + B1:2011 (for industrial
environments)
UL Certification The device CIFX 50-RE is UL-File-Nr. E221530
certified according to UL 508.
Configuration Configuration Software SYCON.net
Master and Slave
Configuration Software Slave netX Configuration Tool
Table 107: Technical Data CIFX 50-RE
10.1.2 CIFX 50E-RE, CIFX 50E-RE\ET
CIFX 50E-RE, Parameter Value
CIFX 50E-RE\ET
Part Name CIFX 50E-RE CIFX 50E-RE\ET
Part No. 1251.100 1251.105
Description PC Card cifX PCI Express Real-Time Ethernet Master or
Slave
Function Communication interface with PCI Express and Ethernet
interface
Controller
System Interface Bus Type PCI Express, One Lane Port, according to [bus spec 2,
Rev. 2.0] and [bus spec 3], refer to section Overview,
page 145.
Transmission Rate 2 GBit/s
Data Access DPM or DMA* (Direct Memory Access);
*beginning from Hardware Revision 4
Open Modbus/TCP
Ethernet Interface Transmission rate 100 MBit/s,
10 MBit/s (depending on loaded firmware)
CIFX 50E-RE\ET
firmware:
LED green
Interface, page 44.
Connector Via PCI Express Bus
(Card ID)
Environmental CIFX 50E-RE CIFX 50E-RE\ET
Conditions
Operating temperature range* 0 °C ... +55 °C 0 °C ... +70 °C
environment.
Mounting/Installation PCI Express x1 slot (3.3 V), refer to section Slot for the PC
Cards cifX PCI, PCIe and Low Profile PCIe, page 43.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-RE is UL-File-Nr. E221530
Master and Slave
Table 108: Technical Data CIFX 50E-RE, CIFX 50E-RE\ET
10.1.3 CIFX 50E-CCIES, CIFX 70E-CCIES
CIFX 50E-CCIES, Parameter Value
CIFX 70E-CCIES
Part Name CIFX 50E-CCIES CIFX 70E-CCIES
Part No. 1251.700 1259.700
Description PC Card cifX PCI Express CC-Link IE Field Slave
Function Communication interface with PCI Express and Ethernet
interface
Controllers CP520 (CC-Link IE Communication Controller)
Integrated Memory RAM SDRAM 64MBIT
FLASH 4 MB or 32 MBIT serial Flash EPROM
page 145.
Ethernet Supported Real-Time Ethernet CC-Link IE Field Slave
Communication communication system
Ethernet Interface Transmission rate 1 Gbit/s
Interface Type 1000 BASE-T, refer to section Ethernet Interface, p. 135.
Isolation Voltage 1000 VDC (getestet für 1 Minute)
Auto-Negotiation Constantly on
Auto-Crossover Constantly on
Channel 0 and 1 Always 2 channels can be used.
For Details refer to section CC- RUN Run
Link IE Field Slave, page 106.
RD Reception status o the data
SD Sending status o the data
D-LINK Data link
ERR Error
USER User-defined status
At RJ45Ch0 and RJ45Ch1:
LINK Link status (for Ethernet)
(LED yellow)
L-ERR Error status of the received data, the line
(LED green) and the loopback (for Ethernet)
Interface, page 44.
Current consumption at 3.3 V 880 mA (typical)
1200 mA (maximum)
(Card ID)
CIFX 50E-CCIES, Parameter Value
CIFX 70E-CCIES
Environmental Operating temperature range* CIFX 50E-CCIES CIFX 70E-CCIES
Conditions
-25 °C ... +70 °C -25 °C ... +70 °C
Device Dimensions (L x W x H) 120,0 x 69,0 x 18,5 mm (length incl. front plate)
RoHS Yes
CE Sign CE Sign Yes
Emission Refer to CE declaration of conformity
Immunity Refer to CE declaration of conformity
Table 109: Technical Data CIFX 50E-CCIES, CIFX 70E-CCIES
10.1.4 CIFX 50-DP

CIFX 50-DP Parameter Value
Part Name CIFX 50-DP
Part No. 1250.410
Description PC Card cifX PCI PROFIBUS DP Master or Slave and
PROFIBUS MPI Device
Function Communication interface with PCI and PROFIBUS
interface
Controller
page 145.
PROFIBUS Supported communication PROFIBUS DP Master,
Communication standard/ protocol (determined by PROFIBUS DP Slave,
the loaded firmware) PROFIBUS MPI Device
PROFIBUS Interface Transmission rate 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
Interface Type RS 485, according EN 50170, refer to section PROFIBUS
Interface page 138.
Connector DSub female Connector, 9 pin
COM LED Communication Status (duo LED)
The meaning of the COM LED depends on the loaded
firmware. Refer to chapter LED Descriptions, page 102.
Interface, page 44.
(Card ID)
Environmental Operating temperature range* -20 °C ... +70 °C (acc. to UL: 0 °C ... +55 °C)
Conditions
environment.
RoHS Yes
CIFX 50-DP Parameter Value
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-DP is UL-File-Nr. E221530
Master and Slave
Table 110: Technical Data CIFX 50-DP
10.1.5 CIFX 50E-DP

CIFX 50E-DP Parameter Value
Part Name CIFX 50E-DP
Part No. 1251.410
Description PC Card cifX PCI Express PROFIBUS DP Master or Slave
and PROFIBUS MPI Device
Function Communication interface with PCI Express and
PROFIBUS interface
Controller
page 145.
Interface Type RS 485, refer to section PROFIBUS Interface page 138.
CIFX 50E-DP Parameter Value
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes

measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-DP is UL-File-Nr. E221530
Master and Slave
Table 111: Technical Data CIFX 50E-DP
10.1.6 CIFX 50-CO

CIFX 50-CO Parameter Value
Part Name CIFX 50-CO
Part No. 1250.500
Description PC Card cifX PCI CANopen Master or Slave
Function Communication interface with PCI and CANopen interface
Controller
page 145.
CANopen Supported communication CANopen Master,
Communication standard/ protocol (determined by CANopen Slave
the loaded firmware)
CANopen Interface Transmission rate 10 kBit/s, 20 kBit/s, 50 kBit/s, 100 kBit/s, 125 kBit/s,
250 kBit/s, 500 kBit/s, 800 kBit/s, 1 MBit/s
Interface Type ISO-11898, refer to section CANopen Interface, page 138.
Galvanic Isolation optically isolated
Connector DSub male Connector, 9 pin
CAN CANopen Status (duo LED)
The meaning of the CAN LED depends on the loaded
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
CIFX 50-CO Parameter Value
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-CO is UL-File-Nr. E221530
Master and Slave
Table 112: Technical Data CIFX 50-CO
10.1.7 CIFX 50E-CO

CIFX 50E-CO Parameter Value
Part Name CIFX 50E-CO
Part No. 1251.500
Description PC Card cifX PCI ExpressCANopen Master or Slave
CANopen interface
Controller
page 145.
CANopen Interface Transmission rate 10 kBit/s, 20 kBit/s, 50 kBit/s, 100 kBit/s,

125 kBit/s, 250 kBit/s, 500 kBit/s, 800 kBit/s, 1 MBit/s

CIFX 50E-CO Parameter Value
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-CO is UL-File-Nr. E221530
Master and Slave
Table 113: Technical Data CIFX 50E-CO
10.1.8 CIFX 50-DN

CIFX 50-DN Parameter Value
Part Name CIFX 50-DN
Part No. 1250.510
Description PC Card cifX PCI DeviceNet Master or Slave
Function Communication interface with PCI and DeviceNet interface
Controller
page 145.
DeviceNet Supported communication DeviceNet Master,
Communication standard/ protocol (determined by DeviceNet Slave
DeviceNet Interface Transmission rate 125 kBit/s, 250 kBit/s, 500 kBit/s
Interface Type ISO-11898 according to DeviceNet specification,
refer to section DeviceNet Interface, page 139.
Connector CombiCon male Connector, 5 pin
MNS Module Network Status (duo LED)
The meaning of the MNS LED depends on the loaded
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-DN is UL-File-Nr. E221530
Master and Slave
Table 114: Technical Data CIFX 50-DN
10.1.9 CIFX 50E-DN

CIFX 50E-DN Parameter Value
Part Name CIFX 50E-DN
Part No. 1251.510
Description PC Card cifX PCI ExpressDeviceNet Master or Slave
DeviceNet interface
Controller
page 145.
firmware. Refer to chapter LED Descriptions, page 102..
Interface, page 44.
(Card ID)
Conditions
CIFX 50E-DN Parameter Value
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-DN is UL-File-Nr. E221530
Master and Slave
Table 115: Technical Data CIFX 50E-DN
10.1.10 CIFX 50-CC

CIFX 50-CC Parameter Value
Part Name CIFX 50-CC
Part No. 1250.740
Description PC Card cifX PCI CC-Link Slave
Function Communication interface with PCI and CC-Link interface
Controller
page 145.
CC-Link Supported communication CC-Link Slave
Communication standard/ protocol (determined by
CC-Link Interface Transmission rate 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s
CIFX 50-CC Parameter Value
Interface Type RS-485, refer to section CC-Link Interface, page 140.
L RUN LED L Run (Duo LED)
L ERR LED L Error (Duo LED)
Interface, page 44.
(Card ID)
Environmental Operating temperature range* -20 °C ... +55 °C
Conditions
environment.
Device Dimensions (L x W x H) 120 x 85,4 x 18,5 mm (from hardware revision 2)
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-CC is UL-File-Nr. E221530
Configuration Configuration Software SYCON.net or netX Configuration Tool
Table 116: Technical Data CIFX 50-CC
10.1.11 CIFX 50E-CC

CIFX 50E-CC Parameter Value
Part Name CIFX 50E-CC
Part No. 1251.740
Description PC Card cifX PCI ExpressCC-Link Slave
CC-Link interface
Controller
page 145.
CC-Link Supported communication CC-Link Slave
CC-Link Interface Transmission rate 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s
Interface Type RS-485, refer to section CC-Link Interface, page 140.
L RUN LED L Run (Duo LED)
L ERR LED L Error (Duo LED)
Interface, page 44.
(Card ID)
Environmental Operating temperature range* 0 °C ... +60 °C (acc. to UL: 0 °C ... +55 °C)
Conditions
environment.
Device Dimensions (L x W x H) 120 x 89,9 x 18,5 mm (from hardware revision 3)
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-CC is UL-File-Nr. E221530
Configuration Configuration Software SYCON.net or netX Configuration Tool
Table 117: Technical Data CIFX 50E-CC
10.1.12 CIFX 50-2DP

CIFX 50-2DP Parameter Value
Part Name CIFX 50-2DP
Part No. 1252.410
Description PC Card cifX PCI 2 channel PROFIBUS DP Master or
Slave
Function Communication interface with PCI and 2 x PROFIBUS
interface
Controller
page 145.
Communication standard/ protocol (determined by PROFIBUS DP Slave
PROFIBUS Interface Transmission rate 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
Interface Type 2 * RS 485, refer to section PROFIBUS Interface p. 138.
CIFX 50-2DP Parameter Value
COM 0 LED Communication Status 0 (duo LED) for
channel X1
channel X2
The meaning of the LEDs COM0 and COM1 depends on
the loaded firmware. Refer to ch. LED Descriptions, p.
102.
Interface, page 44.
(Card ID)
Conditions
environment.
Device Dimensions (L x W x H) 120 x 94,5 x 18,5 mm
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-2DP is UL-File-Nr. E221530
Configuration Configuration Software Master SYCON.net
Table 118: Technical Data CIFX 50-2DP
10.1.13 CIFX 50E-2DP

CIFX 50E-2DP Parameter Value
Part Name CIFX 50E-2DP
Part No. 1253.410
Description PC Card cifX PCI Express 2 channel PROFIBUS DP
Master or Slave
2 x PROFIBUS interface
Controller
page 145.
Interface Type RS 485, refer to section PROFIBUS Interface page 138.
for channel X1
for channel X2
The meaning of the LEDs COM0 and COM1 depends on
the loaded firmware. Refer to ch. LED Descriptions, p.
102.
Interface, page 44.
(Card ID)
Conditions
environment.
Device Dimensions (L x W x H) 120,0 x 95 x 21,5 mm
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 119: Technical Data CIFX 50E-DP
10.1.14 CIFX 50-2DP\CO

CIFX 50-2DP\CO Parameter Value
Part Name CIFX 50-2DP\CO
Part No. 1252.470
Description PC Card cifX PCI 2 channel -
Channel X0: PROFIBUS DP Master or Slave,
Channel X1: CANopen Master or Slave
Function Communication interface with PCI, 1 x PROFIBUS and
1 x CANopen interface
Controller
page 145.
6 MBit/s, 12 MBit/s
channel X1
CAN 1 CANopen Status 1 (duo LED) for channel X2
The meaning of the LEDs COM0 and CAN1 depends on
the loaded firmware. Refer to chapter LED Descriptions,
page 102.
Interface, page 44.
(Card ID)
CIFX 50-2DP\CO Parameter Value
Environmental Operating temperature range* -20 °C ... +70°C
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 120: Technical Data CIFX 50-2DP\CO
10.1.15 CIFX 50E-2DP\CO

CIFX 50E-2DP\CO Parameter Value
Part Name CIFX 50E-2DP\CO
Part No. 1253.470
Channel X1: CANopen Master or Slave
Function Communication interface with PCI Express,
1 x PROFIBUS and 1 x CANopen interface
Controller
page 145.
6 MBit/s, 12 MBit/s
channel X1
The meaning of the LEDs COM0 and CAN1 depends on
page 102.
Interface, page 44.
(Card ID)
Environmental Operating temperature range* -20 °C ... +70°C
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 121: Technical Data CIFX 50E-2DP\CO
10.1.16 CIFX 50-2DP\DN

CIFX 50-2DP\DN Parameter Value
Part Name CIFX 50-2DP\DN
Part No. 1252.480
Channel X1: DeviceNet Master or Slave
Function Communication interface with PCI, 1 x PROFIBUS and
1 x DeviceNet interface
Controller
page 145.
6 MBit/s, 12 MBit/s
channel X1
CIFX 50-2DP\DN Parameter Value
MNS 1 DeviceNet-Status 1 (duo LED) for channel X2
The meaning of the LEDs COM0 and MNS1 depends on
page 102.
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 122: Technical Data CIFX 50-2DP\DN
10.1.17 CIFX 50E-2DP\DN

CIFX 50E-2DP\DN Parameter Value
Part Name CIFX 50E-2DP\DN
Part No. 1253.480
1 x PROFIBUS and 1 x DeviceNet interface
Controller
page 145.
6 MBit/s, 12 MBit/s
channel X1
MNS 1 DeviceNet-Status 1 (duo LED) for channel X2
The meaning of the LEDs COM0 and MNS1 depends on
page 102.
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 123: Technical Data CIFX 50-2DP\DN
10.1.18 CIFX 50-2CO

CIFX 50-2CO Parameter Value
Part Name CIFX 50-2CO
Part No. 1252.500
Description PC Card cifX PCI 2 channel CANopen Master or Slave
Function Communication interface with PCI and 2 x CANopen
interface
Controller
page 145.
The meaning of the LEDs CAN0 and CAN1 depends on
page 102.
CIFX 50-2CO Parameter Value
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 124: Technical Data CIFX 50-2CO
10.1.19 CIFX 50E-2CO

CIFX 50E-2CO Parameter Value
Part Name CIFX 50E-2CO
Part No. 1253.500
Description PC Card cifX PCI Express 2 channel CANopen Master or
Slave
2 x CANopen interface
Controller
page 145.
CAN 0 CANopen Status 0 (duo LED) for channel
X1
CAN 1 CANopen Status 1 (duo LED) for channel
X2
The meaning of the LEDs CAN0 and CAN1 depends on
page 102.
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 125: Technical Data CIFX 50E-2CO
10.1.20 CIFX 50-2CO\DN

CIFX 50-2CO\DN Parameter Value
Part Name CIFX 50-2CO\DN
Part No. 1252.570
Channel X0: CANopen Master or Slave,
Function Communication interface with PCI, 1 x CANopen and
1 x DeviceNet interface
Controller
page 145.
MNS 1 CANopen Status 1 (duo LED) for channel X2
The meaning of the LEDs CAN0 and MNS1 depends on
page 102.
CIFX 50-2CO\DN Parameter Value
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 126: Technical Data CIFX 50-2CO\DN
10.1.21 CIFX 50E-2CO\DN

CIFX 50E-2CO\DN Parameter Value
Part Name CIFX 50E-2CO\DN
Part No. 1253.570
Channel X0: CANopen Master or Slave,
1 x CANopen and 1 x DeviceNet interface
Controller
page 145.
MNS 1 CANopen Status 1 (duo LED) for channel X2
The meaning of the LEDs CAN0 and MNS1 depends on
page 102.
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 127: Technical Data CIFX 50E-2CO\DN
10.1.22 CIFX 50-2DN

CIFX 50-2DN Parameter Value
Part Name CIFX 50-2DN
Part No. 1252.510
Description PC Card cifX PCI 2 channel DeviceNet Master or Slave
Function Communication interface with PCI and 2 x DeviceNet
interface
Controller
page 145.
MNS 0 Module Network Status 0 (duo LED) for channel
X1
MNS 1 Module Network Status 1 (duo LED) for channel
X2
The meaning of the LEDs MNS 0 and MNS 1 depends on
page 102.
Interface, page 44.
CIFX 50-2DN Parameter Value
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Table 128: Technical Data CIFX 50-2DN
10.1.23 CIFX 50E-2DN

CIFX 50E-2DN Parameter Value
Part Name CIFX 50E-2DN
Part No. 1253.510
Description PC Card cifX PCI 2 channel ExpressDeviceNet Master or
Slave
2x DeviceNet interface
Controller
page 145.
MNS 0 Module Network Status 0 (duo LED) for
channel X1
MNS 1 Module Network Status 1 (duo LED) for
channel X2
The meaning of the LEDs MNS 0 and MNS 1 depends on
page 102.
Interface, page 44.
(Card ID)
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 129: Technical Data CIFX 50E-2DN
10.1.24 CIFX 50-2ASM

CIFX 50-2ASM Parameter Value
Part Name CIFX 50-2ASM
Part No. 1252.630
Description PC Card cifX PCI 2 channel AS-Interface Master
Function Communication interface with PCI and 2 x AS-Interface
interface
Controller
page 145.
AS-Interface Supported communication AS-Interface Master
AS-Interface Interface Transmission rate 166,67 kBit/s
Interface Type 2 *, acc. to IEC 364-4-41, refer to section AS-Interface
Interface, page 139.
COM1 LED channel X1 (duo LED)
Interface, page 44.
(Card ID)
Conditions
environment.
CIFX 50-2ASM Parameter Value
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50-2ASM is UL-File-Nr. E221530
Table 130: Technical Data CIFX 50-2ASM
10.1.25 CIFX 50E-2ASM

CIFX 50E-2ASM Parameter Value
Part Name CIFX 50E-2ASM
Part No. 1253.630
Description PC Card cifX PCI Express2 channel AS-Interface Master
2 x AS-Interface interface
Controller (since hardware revision 04 netX 500; before netX 100)
page 145.
AS-Interface Supported communication AS-Interface Master
AS-Interface Interface Transmission rate 166,67 kBit/s
Interface Type 2 *, acc. to IEC 364-4-41, refer to section AS-Interface
Interface, page 139.
CIFX 50E-2ASM Parameter Value
Refer to ch. LED Descriptions, p. 102.
Interface, page 44.
(Card ID)
Environmental Operating temperature range* 0 °C ... +55 °C
Conditions
environment.
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 50E-2ASM is UL-File-Nr. E221530
Table 131: Technical Data CIFX 50E-2ASM

CIFX 70E-RE\MR
Part Name CIFX 70E-RE CIFX 70E-RE\MR
Part No. 1.259.100 1.259.103
Description PC Card cifX Low Profile PCI Express Real-Time-Ethernet
Master or Slave (Low Profile PCIe with RTE), (and
CIFX 70E-RE\MR
variants with additional MRAM ‚MR’)
Ethernet interface
Controller
MRAM (only CIFX 70E-RE\MR) 128Kbyte (= 64K Words);
Note: Using the cifX Device Driver (from Version 1.1.1.0)
access to this memory is possible and it can be used as a
remanent memory.
page 145.
Open Modbus/TCP
firmware:
CIFX 70E-RE\MR
LED green for Ethernet Link status, Ethernet Activity
Interface, page 44.
(Card ID)
Conditions
Device Dimensions (L x W x H) 119,0 x 69,0 x 18,5 mm
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 132: Technical Data CIFX 70E-RE, CIFX 70E-RE\MR
10.1.27 CIFX 100EH-RE\CUBE

CIFX 100EH-RE Parameter Value
Part Name CIFX 100EH-RE
Part No. 9016.090
Description PC Card cifX PCI Express for Real-Time Ethernet Master
or Slave, (low-profile card) exclusively for the installing in
KEBA KeControl industry PCs series CP 3XX (Cube).
Ethernet interface
Controller
System Interface Bus Type PCI Express, One Lane Port*, (refer to section Overview,
page 145 and Pin Assignment for PCI Express Bus CIFX
100EH-RE\CUBE, page 146.
*The PC card CIFX 100EH-RE\CUBE can be used for x4
connectors, but not a real x4 connection (mechanical deviation
from the standard, it is used only 1 lane).
Ethernet Supported Real-Time Ethernet EtherCAT Master, EtherCAT Slave
EtherNet/IP Scanner (Master),
firmware)
Open Modbus/TCP
firmware:
LED green
Interface, page 44.
(Card ID)
Conditions
environment.
x4 5 = Four Lane; In the PCI Express x4 slot only lane 0 is used.
For further details refer to section Pin Assignment for PCI Express
Bus CIFX 100EH-RE\CUBE on page 146.
Master License NXLIC Master (Part No 8211.000)
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
UL Certification The device CIFX 100EH- UL-File-Nr. E221530
RE\CUBE is certified according to
UL 508.
5 The term "x4“ refers to the convention of the PCI Express specifications [bus
spec 3] to the number of lanes in the slot.
Master and Slave
Table 133: Technical Data CIFX 100EH-RE\CUBE

CIFX 70E-DP, Parameter Value
CIFX 70E-DP\MR
Part Name CIFX 70E-DP CIFX 70E-DP\MR
Part No. 1259.410 1259.413
Description PC Card cifX Low Profile PCI Express PROFIBUS DP
Master or Slave and PROFIBUS MPI Device (Low Profile
PCIe with PROFIBUS), (and variants with additional
MRAM ‚MR’)
PROFIBUS interface
Controller
MRAM (only CIFX 70E-DP\MR) 128Kbyte (= 64K Words);
remanent memory.
page 145.
Interface Type RS 485, refer to section PROFIBUS Interface, page 138.
Interface, page 44.
(Card ID)
CIFX 70E-DP, Parameter Value
CIFX 70E-DP\MR
Conditions
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 134: Technical Data CIFX 70E-DP, CIFX 70E-DP\MR

CIFX 70E-CO, Parameter Value
CIFX 70E-CO\MR
Part Name CIFX 70E-CO CIFX 70E-CO\MR
Part No. 1259.500 1259.503
Description PC-Karte cifX Low Profile PCI Express CANopen Master
or Slave (Low Profile PCIe mit CANopen), (and variants
with additional MRAM ‚MR’)
CANopen interface
Controller
MRAM (only CIFX 70E-CO\MR) 128Kbyte (= 64K Words);
remanent memory.
page 145.
CIFX 70E-CO, Parameter Value
CIFX 70E-CO\MR
Interface, page 44.
(Card ID)
Conditions
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 135: Technical Data CIFX 70E-CO, CIFX 70E-CO\MR
CIFX 70E-DN, Parameter Value
CIFX 70E-DN\MR
Part Name CIFX 70E-DN CIFX 70E-DN\MR
Part No. 1259.510 1259.513
Description PC Card cifX Low Profile PCI Express DeviceNet Master
or Slave (Low Profile PCIe with DeviceNet), (and variants
with additional MRAM ‚MR’)
DeviceNet interface
Controller
MRAM (only CIFX 70E-DN\MR) 128Kbyte (= 64K Words);
remanent memory.
page 145.
Interface, page 44.
(Card ID)
Conditions
CIFX 70E-DN, Parameter Value
CIFX 70E-DN\MR
RoHS Yes
CE Sign CE Sign Yes
measurement)
EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated,
EN 61000-4-5:2006 (Surge test)
environments)
Master and Slave
Table 136: Technical Data CIFX 70E-DN, CIFX 70E-DN\MR
10.2 PCI IDs PC Cards cifX on the PCI Bus

On the PCI bus the PC Cards cifX have the following PCI IDs:
PCI IDs Value
VendorID 0x15CF
DeviceID 0x0000
Subsystem Vendor ID 0x0000
Subsystem Device ID 0x0000
Table 137: PCI IDs PC Cards cifX on the PCI Bus
10.3 Supported PCI-Bus Commands

From the following table you can see which PCI bus commands are
supported by the Hilscher PC Cards cifX PCI, PCI Express and Low Profile
PCI Express.
C/BE3# C/BE2# C/BE1# C/BE0# Command Type supported
0 0 0 0 Interrupt Acknowledge no
0 0 0 1 Special Cycle no
0 0 1 0 I/O Read 
0 0 1 1 I/O Write 
0 1 0 0 Reserved no
0 1 0 1 Reserved no
0 1 1 0 Memory Read 
0 1 1 1 Memory Write 
1 0 0 0 Reserved no
1 0 0 1 Reserved no
1 0 1 0 Configuration Read 
1 0 1 1 Configuration Write 
1 1 0 0 Memory Read Multiple no
1 1 0 1 Dual Address Cycle no
1 1 1 0 Memory Read Line no
1 1 1 1 Memory Write and Invalidate no
Table 138: Supported / not supported PCI Bus Commands
C/BE = Bus Command and Byte Enable Signal of PCI
10.4 Technical Data of the Communication Protocols
10.4.1 CC-Link IE Field Basic Slave
Parameter Description
Maximum number of cyclic input data RY data: 128 bytes (1024 bits)
RWw data: 512 words (16 bit)
Maximum number of cyclic output data RX data: 128 bytes (1024 bits)
RWr data: 512 words (16 bit)
Occupied stations 1 … 16
(1 station has 64 bits RY data, 32 words RWw data, 64 bits RX
data, and 32 words RWr data.)
Acyclic communication SLMP Server and Client
Data transport layer Ethernet II, IEEE 802.3
Baud rate 100 MBit/s
Reference to firmware / stack version V1.1
Ports
Cyclic data 61450 (UDP)
Discovery and SLMP Server 61451 (UDP)
SLMP Parameter 45237 (UDP)
SLMP Communication 20000 (UDP)
Table 139: Technical data CC-Link IE Field Basic Slave protocol
10.4.2 CC-Link IE Field Slave

Station types Remote Device Station, Intelligent Device Station
Remote Device Station
RWw data: 64 words (each 16 bit)
RWr data: 64 words (each 16 bit)
Intelligent Device Station
RWw data: 1024 words (each 16 bit)
RWr data: 1024 words (each 16 bit)
Remote Device Station, Intelligent Device Station
Acyclic communication SLMP
Baud rate 1 GBit/s, full-duplex
Reference to firmware/stack version V1.1
Table 140: Technical data CC-Link IE Field Slave protocol
10.4.3 EtherCAT Master (V3)

Maximum number of EtherCAT slaves Maximum 200 Slaves. The number of usable slaves depends on
the available memory for the configuration file. See ‘configuration
file’ below.
Maximum number of cyclic input data 5760 bytes
Maximum number of cyclic output data 5760 bytes
Minimum bus cycle time 250 µ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.
Acyclic communication CoE (CANopen over EtherCAT)
CoE-Upload, CoE-Download
Maximum 1500 bytes
Functions Get OD List
Get object description
Get entry description
Emergency
Slave diagnostics
Bus Scan Supported
Redundancy Supported, but not at the same time with Distributed Clocks
Distributed Clocks Supported, but not at the same time with Redundancy
Topology Line or ring
Configuration File (ethercat.xml or config.nxd) PC cards PCI, PCI Express, PCI Express Low Profile, Mini PCI,
Compact PCI, Mini PCI Express, PCI-104 Real-Time Ethernet:
Maximum 1 MByte
PC cards PC/104 Real-Time Ethernet: Maximum 2 MByte
Limitations 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
Distubuted Clock and Redundancy can not be used at the same
time.
Table 141: Technical Data EtherCAT Master Protocol
10.4.4 EtherCAT Master (V4)

Maximum number of EtherCAT slaves Maximum of 388 slaves, if RCX_GET_SLAVE_HANDLES_REQ
service is used for determining number of slaves.
The number of usable slaves depends on several parameters: the
available memory for the configuration file (see ‘configuration file’
below), used cycle time, frame propagation time.
Maximum number of cyclic input data Appr. 4600 bytes, if no LRW command (Logical Read Write) is
used for process data
Maximum number of cyclic output data Appr. 4600 bytes, if no LRW command (Logical Read Write) is
used for process data
Acyclic communication CoE (CANopen over EtherCAT): SDO, SDOINFO, Emergency
FoE (File Access over EtherCAT)
SoE (Servo Drive Profile over EtherCAT)
EoE (Ethernet over EtherCAT)
Configurable with SYCON.net: CoE
If the file ETHERCAT.XML contains the appropriate configuration
information (e.g. created with "EtherCAT Configurator"), following
functions can be used: CoE, SoE, EoE
Mailbox protocols CoE, EoE, FoE, SoE
Functions Distributed Clocks
Redundancy
Slave diagnostics
Bus scan
Minimum bus cycle time 250 µs, depending on the used number of slaves and the used
number of cyclic input data and output data.
Topology Line or ring
Slave station address range 1 – 14335
Data transport layer Ethernet II, IEEE 802.3, 100 MBit/s, full-duplex
Configuration file Maximum 1 MByte
(ETHERCAT.XML or CONFIG.NXD)
Synchronization via ExtSync Supported (not configurable with SYCON.net)
ENI Slave-to-Slave copy infos Supported (not configurable with SYCON.net)
Hot Connect Supported (not configurable with SYCON.net)
EoE (Ethernet over EtherCAT) Via NDIS
Limitations The size of the bus configuration file is limited by the size of the
RAM disk (1 MByte) or Flash disk (3 MByte).
Store-and-forward switches cannot be used within network
topology due to hard receive timing model
RCX_GET_SLAVE_HANDLES_REQ can only communicate up to
388 slaves.
Process data is restricted by the dual-port memory to 5760 bytes.
Table 142: Technical Data EtherCAT Master Protocol
10.4.5 EtherCAT Slave

Maximum number of cyclic input data 256* bytes
Maximum number of cyclic output data 256* bytes
Acyclic communication SDO
SDO Master-Slave
SDO Slave-Slave (depending on Master capability)
Type Complex Slave
Functions Emergency
FMMUs 3
SYNC Manager 4
Distributed Clocks (DC) Supported, 32 Bit
Limitation LRW is not supported
Reference to firmware/stack version V2.5 and V4.7
Table 143: Technical Data EtherCAT Slave Protocol
Note: * 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.
10.4.6 EtherNet/IP Scanner (Master)

Maximum number of EtherNet/IP connections 64 connections for implicit and explicit
Maximum number of total cyclic input data 5712 bytes
Maximum number of total cyclic output data 5760 bytes
Maximum number of cyclic input data 504 bytes per slave per telegram
Maximum number of cyclic output data 504 bytes per slave per telegram
IO Connection type Cyclic, minimum 1 ms (depending on used number of connections
and used number of input and output data)
Maximum number of unscheduled data 1400 bytes per telegram
UCMM, Class 3 Supported
Explicit Messages, Client and Server Services Get_Attribute_Single/All
Set_Attribute_Single/All
Quick connect Supported
Predefined standard objects Identity Object
Message Route Object
Assembly Object
Connection Manager
Ethernet Link Object
TCP/IP Object
DLR Object
QoS Object
Maximal number of user specific objects 20
Network scan Supported
Topology Tree, Line, Ring
DLR (Device Level Ring) Beacon based ’Ring Node’
ACD (Address Conflict Detection) Supported
DHCP Supported
BOOTP Supported
Baud rates 10 and 100 MBit/s
Switch function Integrated
Limitations CIP Sync Services are not implemented
TAGs are not supported
Table 144: Technical Data EtherNet/IP Scanner Protocol
10.4.7 EtherNet/IP Adapter (Slave)

Maximum number of input data 504 bytes
Maximum number of output data 504 bytes
IO connection types (implicit) 1 exclusive owner, 1 listen only, 1 input only
IO Connection trigger types 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
Explicit Messages Connected and unconnected
Maximum number of connections 8, explicit and implicit connections
Unconnected Message Manager (UCMM) Supported
Quick connect Supported
Predefined standard objects Identity Object
Message Route Object
Assembly Object
Connection Manager
DLR Object
QoS Object
TCP/IP Object
Ethernet Link Object
Time Sync Object
Reset services Identity Object Reset Service of Type 0 and 1
Maximum number of user specific objects 20
DLR V2 (ring topology) Supported
ACD (Address Conflict Detection) Supported
DHCP Supported
BOOTP Supported
Duplex modes Half duplex, Full duplex, Auto negotiation
MDI modes MDI, MDI-X, Auto-MDIX
Switch function Integrated
Limitations CIP Sync Services are not implemented
TAGs are not supported
Table 145: Technical Data EtherNet/IP Adapter Protocol
10.4.8 Open Modbus/TCP

Maximum number of input data 2880 Registers
Maximum number of output data 2880 Registers
Acyclic communication 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)
Modbus Function Codes 1,
2,
3,
4,
5,
6,
7,
15,
16,
23*,
43
* Function Code 23 can be used via the packet API, but not with
the Command Table.
Protocol Mode 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)
Command table (Configuration API only) Max. 16 servers configurable
Max. 256 commands
Table 146: Technical Data Open Modbus/TCP Protocol
10.4.9 POWERLINK Controlled Node/Slave (V2)

Acyclic data transfer SDO Upload/Download
Functions SDO over ASND and UDP
Baud rate 100 MBit/s, half-duplex
Ethernet POWERLINK version V2
Limitation No slave to slave communication
Table 147: Technical Data POWERLINK Controlled Node Protocol
10.4.10 POWERLINK Controlled Node/Slave (V3)

Acyclic data transfer SDO Upload/Download
Functions SDO over ASND and UDP
Baud rate 100 MBit/s, half-duplex
Ethernet POWERLINK version V2
Limitation No slave to slave communication
Table 148: Technical Data POWERLINK Controlled Node Protocol
10.4.11 PROFINET IO-Controller (V2)

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)
Maximum number of cyclic input data 1440 bytes per device (= IOCR data length including IOxS status
bytes)
Maximum number of cyclic output data 1440 bytes per device (= IOCR data length including IOxS status
bytes)
Acyclic communication Read/Write Record
Limited to 1392 bytes per telegram
Limited to 4096 bytes per request
Alarm processing yes, but requires handling in host application program
Diagnostic data One 200 byte buffer per IO device
DCP functions via API 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)
Supported Protocols RTC – Real Time Cyclic Protocol, Class 1
RTA – Real Time Acyclic Protocol
DCP – Discovery and configuration Protocol
CL-RPC – Connectionless Remote Procedure Call
Context management by CL-RPC Supported
Minimum cycle time 1 ms
Different IO-Devices can be configured with different cycle times
Functions Fast Startup of PROFINET IO Devices supported
Full-Duplex mode
Configuration file Maximum 1 MByte
Limitations 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
Table 149: Technical Data PROFINET IO RT Controller Protocol
10.4.12 PROFINET IO-Controller (V3)

Maximum number of ARs (Application 128 for RT communication
Relation) 64 for IRT communication
Maximum number of cyclic input data 5652 bytes, including provider and consumer status
Maximum number of cyclic output data 5700 bytes, including provider and consumer status
Send clock 1 ms, 2 ms, 4 ms for RT mode
250 µs, 500 µs, 1 ms, 2 ms, 4 ms for IRT mode
Performance limits of ARs Max. 8 ARs, if a send clock < 500 µs
Max. 16 ARs, if a send clock < 1 ms
Max. 64 ARs, if a send clock < 2 ms
Maximum number of submodules 2048
Maximum amount of data per IOCR 1440 bytes
Number of IOCRs per AR 1 Input IOCR
1 Output IOCR
Maximum amount of data for acyclic 65536 bytes
read/write record access
Maximum amount of record data per AR 16384 bytes
Alarm processing (configurable) Stack processes alarms automatically
Applikation processes alarms
Maximum number of ARVendorBlock 256
Maximum size of ARVendorBlockData 512 bytes
Device Access AR CMI Timeout 20 s
Functions Automatic Name Assignment
Media Redundancy Client
Media Redundancy Manager (requires license)
DCP function API 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)
DCP GET
PROFINET specification Implemented according to V2.3 ED2 MU3
Legacy Startup supported according to PROFINET specification V2.2
Limitations The size of the bus configuration file is limited by the size of the RAM
Disk (1 Mbyte)
The usable (minimum) cycle time depends on the number of used IO
Devices, the number of used input and output data.
RT over UDP not supported
DHCP is not supported (neither for PROFINET IO Controller nor for
IO-Devices)
Only one IOCR per IO-Device per direction
One instance of DeviceAccess AR can be used at the same time only
MRPD is not supported
Planning of IRT is not done by the PROFINET IO Controller protocol
stack
Sync Slave is not supported
One fragmented acyclic services can be used at the same time only
Multiple MRP Managers are not supported
One DCP Service can be used in parallel only
Multiple Sync Masters are not supported
Table 150: Technical Data PROFINET IO Controller Protocol
10.4.13 PROFINET IO-Device (V3.4)

Acyclic communication Read/Write Record, max. 1024 bytes per telegram
Alarm Types Process Alarm, Diagnostic Alarm, Return of SubModule Alarm
Plug Alarm (implicit), Pull Alarm (implicit)
Supported protocols 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
Used Protocols (subset) UDP, IP, ARP, ICMP (Ping)
Topology recognition LLDP, SNMP V1, MIB2, physical device
VLAN- and priority tagging yes
Context Management by CL-RPC Supported
Identification & Maintenance Read and write of I&M1-4
Minimum cycle time 1 ms for RTC1 and RTC2
250 µs for RTC3
Limitations RT over UDP not supported
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
Reference to firmware/stack version V3.4.x.x
Table 151: Technical Data PROFINET IO RT IRT Device Protocol
10.4.14 PROFINET IO Device (V3.13)

Maximum number of submodules 255 submodules per Application Relation at the same time,
1000 submodules can be configured
Multiple Application Relations (AR) The Stack can handle up to 8 IO-ARs, one Supervisor AR and one
Supervisor-DA AR at the same time
Acyclic communication Read/Write Record, max. 8 KB (fragmented)
Alarm Types Process Alarm, Diagnostic Alarm, Return of SubModule Alarm,
Plug Alarm (implicit), Pull Alarm (implicit), Update Alarm, Status Alarm,
Isochronous Problem Alarm, Upload and Retrieval Notification Alarm
Supported protocols RTC – Real Time Cyclic Protocol,
class 1 (unsynchronized), class 3 (synchronized)
LLDP – Link Layer Discovery Protocol
SNMP – Simple Network Management Protocol
MRP – MRP Client
Topology recognition LLDP, SNMP V1, MIB2, physical device
Identification & Maintenance Read and write of I&M0-5, Read of I&M5
Minimum cycle time 1 ms for RT_CLASS_1
250 µs for RT_CLASS_3
IRT Support RT_CLASS_3
Media Redundancy MRP client is supported
Asset Management Max. 199 assets
PROFIenergy PROFIenergy ASE implementation with one PE entity per submodule
Additional features DCP, VLAN- and priority tagging, Shared Device (max. 1 RTC3 AR)
PROFINET IO specification V2.2 (legacy startup) and V2.3
Limitations RT over UDP not supported.
Multicast communication not 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 per AR 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.
SharedInput is not supported.
MRPD is not supported.
DFP and other HighPerformance-profile related features are not
supported.
PDEV functionality is only supported for submodules located in slot 0.
Submodules can not be configured or used by an AR in subslot 0.
DAP and PDEV submodules only supported in slot 0.
Only one IO Supervisor AR is supported in parallel.
Table 152: Technical Data PROFINET IO RT IRT Device Protocol
10.4.15 Sercos Master

Maximum number of cyclic input data 5760 bytes (including Connection Control per Connection)
Maximum number of cyclic output data 5760 bytes (including Connection Control per Connection)
Maximum number of configured slave devices 511
Minimum cycle time 250 µs
Acyclic communication Service channel: Read/Write/Commands
Functions Bus Scan
Communication phases NRT, CP0, CP1, CP2, CP3, CP4
Topology Line and double ring
Redundancy supported
NRT channel 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
Supported Sercos version Communication Specification Version 1.3
TCP/IP stack integrated
Table 153: Technical Data Sercos Master Protocol
10.4.16 Sercos Slave

Maximum number of cyclic produced data 132 bytes (including Connection Control and IO Status)
Maximum number of cyclic consumed data 124 bytes (including Connection Control and IO Status)
Maximum number of slave devices 8
Sercos addresses 1 … 511
Minimum cycle time 250 µs
Topology Line and ring
Communication phases NRT, CP0, CP1, CP2, CP3, CP4, HP0, HP1, HP2
Descriptors for connections (including Connection Max. 64
Control and IO Status/Control)
Acyclic Communication (Service Channel) Read/Write/Standard Commands
Cross Communication (CC) Supported
Supported Sercos version Communication Specification Version 1.1.2 and 1.3.1
Supported Sercos Communication Profiles SCP_FixCFG Version 1.1.1
SCP_VarCFG Version 1.1.1
SCP_VarCFG Version 1.1.3
SCP_HP Version 1.1.1
SCP_SysTime Version1.3
Supported User SCP Profiles 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 1.1.1
SCP_ExtMuX 1.1.2
SCP_RTBListProd 1.3
SCP_RTBListCons 1.3
SCP_RTBWordProd 1.3
SCP_RTBWordCons 1.3
SCP_OvSBasic 1.3
SCP_WDCon 1.3
Supported FSP profiles FSP_IO
FSP_Drive
FSP_Encoder
SCP Sync Supported
SCP_NRT Supported
S/IP Supported
Identification LED Supported
Storage location of object dictionary Mixed mode
Limitations 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)
Table 154: Technical Data Sercos Slave Protocol
10.4.17 VARAN Client (Slave)

Memory Area Read Memory Area 1,
Write Memory Area 1,
Read Memory Area 2,
Write Memory Area 2
Functions Memory Read
Memory Write
Integrated 2 port splitter for daisy chain topology Supported
VARAN protocol version 1.1.1.0
Limitations Integrated EMAC for IP data exchange with client application not
supported
SPI single commands (optional feature) not supported
Table 155: Technical Data VARAN Client Protocol
10.4.18 PROFIBUS DP Master

Maximum number of PROFIBUS DP slaves 125 (DPV0/DPV1)
Maximum number of cyclic input data 244 bytes per slave
Maximum number of cyclic output data 244 bytes per slave
Configuration data Max. 244 bytes per slave
Parameterization data per slave 7 bytes standard parameter per slave
Max. 237 bytes application specific parameters per slave
Acyclic communication DPV1 class 1 read, write
DPV1 class 1 alarm
DPV1 class 2 initiate, read, write, data transport, abort
Maximum number of acyclic read/write 240 bytes per slave and telegram
Functions Configuration in Run (CiR), requires host application program
support
Timestamp (Master functionality)
Redundancy Supported, requires host application program support
Baud rate 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
Data transport layer PROFIBUS FDL
Limitations 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.
Table 156: Technical Data PROFIBUS DP Master Protocol
10.4.19 PROFIBUS DP Slave

Maximum number of acyclic data (read/write) 240 bytes/telegram
Maximum number of modules 24
Configuration data Max. 244 bytes
Parameter data 237 bytes application specific parameters
Acyclic communication DP V1 Class 1 Read/Write
DP V1 Class 1 Alarm
DP V1 Class 2 Read/Write/Data Transport
Baud rate 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 baudrate detection is supported
Limitations 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
Table 157: Technical Data PROFIBUS DP Slave Protocol
10.4.20 PROFIBUS MPI

Maximum number of MPI connections 126
Maximum number of write data 216 bytes
Maximum number of read data 222 bytes
Functions 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)
Baud rate Fixed values ranging from 9,6 kBits/s to 12 MBit/s
Auto-detection mode is supported
Reference to firmware/stack version 2.4
Table 158: Technical Data PROFIBUS-MPI Protocol
10.4.21 CANopen Master

Maximum number of CANopen nodes 126
Maximum number of receive PDOs 512
Maximum number of transmit PDOs 512
Exchange of process data Via PDO transfer:
- synchronized,
- remotely requested and
- event driven (change of date)
Acyclic communication SDO Upload/Download, max. 512 bytes per request
Functions 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
Baud rates 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 layer 2 access Send/receive via API supported (11 bit/29 bit)
Data transport layer CAN Frames
CAN Frame type for CANopen 11 Bit
Reference to version V2.14
Table 159: Technical Data CANopen Master Protocol
10.4.22 CANopen Slave

Maximum number of receive PDOs 64
Maximum number of transmit PDOs 64
Exchange of process data Via PDO transfer
- synchronized,
- remotely requested and
- event driven (change of date, event timer)
On request of the host application program by packet
Acyclic communication SDO upload/download (server only)
Emergency message (producer)
Timestamp (producer/consumer)
Functions 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
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 layer 2 access Send/receive via API supported (11 bit/29 bit)
Data transport layer CAN Frames
CAN Frame type for CANopen 11 Bit
Table 160: Technical Data CANopen Slave Protocol
10.4.23 DeviceNet Master

Maximum number of DeviceNet slaves 63
Maximum number of cyclic input data 255 bytes/connection
Maximum number of cyclic output data 255 bytes/connection
Maximum Configuration data 1000 bytes/slave
Acyclic communication Explicit connection
All service codes are supported
Connections Bit Strobe
Change of State
Cyclic
Poll
Explicit Peer-to-Peer Messaging
Function Quick Connect
Fragmentation Explicit and I/O
UCMM Supported
Objects Identity Object (Class Code 0x01)
Message Router Object (Class Code 0x02)
DeviceNet Object (Class Code 0x03)
Connection Object (Class Code 0x05)
Acknowledge Handler Object (Class Code 0x06)
250 kBit/s,
500 kBit/s
Auto baudrate detection is not supported
Data transport layer CAN frames
Table 161: Technical Data DeviceNet Master Protocol
10.4.24 DeviceNet Slave

Acyclic communication 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 Supported
Fragmentation Explicit and I/O
UCMM Not supported
250 kBit/s,
500 kBit/s
Auto baudrate detection is not supported
Data transport layer CAN frames
Table 162: Technical Data DeviceNet Slave Protocol
10.4.25 AS-Interface Master

Maximum number of supported slaves Max. 62 slaves
Maximum number of total cyclic input data Max. 248 bits using digital slaves
Max. 248 bytes using analog (transparent) slaves
The maximum number depends on the used slave profiles
Maximum number of total cyclic output data Max. 248 bits using digital slaves
Max. 248 bytes using analog (transparent) slaves
Maximum number of cyclic input data Max. 4 Bit digital data
Max. 4 channel with up to 16 bit analog data
Maximum number of cyclic output data Max. 4 Bit digital data
Max. 4 channel with up to 16 bit analog data
Parameterization data 4 bit per standard slave
3 bit per extended slave
Maximum number of acyclic read/write Max. 220 bytes for string transfer
Functions Support of data exchange via combined transaction types 1, 2, 3,
4 and 5 (CTT 1-5)
Automatic address assignment
Modification of address and Extended ID1-Code of Slave
supported
Profile for extended Master: M4
Baud rate 166,67 kBaud
AS-Interface specification 3.0 Revision 2
Limitations 'Synchronous Data I/O Mode' not supported
Table 163: Technical Data AS-Interface Master Protocol
10.4.26 CC Link Slave

Firmware works according to CC-Link Version 2.0:
Station Types Remote Device Station (up to 4 occupied stations)
Maximum input data 368 bytes
Maximum output data 368 bytes
Input data remote device station 112 bytes (RY) and 256 bytes (RWw)
Output data remote device station 112 bytes (RX) and 256 bytes (RWr)
Extension cycles 1, 2, 4, 8
Baud rates 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 48 bytes
Maximum output data 48 bytes
Input data remote I/O station 4 bytes (RY)
Output data remote I/O station 4 bytes (RX)
Input data remote device station 4 bytes (RY) and 8 bytes (RWw) per occupied station
Output data remote device station 4 bytes (RX) and 8 bytes (RWr) per occupied station
Baud rates 156 kBit/s, 625 kBit/s, 2500 kBit/s, 5 MBit/s, 10 MBit/s
Firmware
Table 164: Technical Data CC-Link-Slave-Protocol
Annex 220/284
11 Annex
11.1 Device Label with Matrix Code
You can identify your device by means of the device label.
Note: The position of the device label on your device can be seen from the
device drawing.
The device label consists of a matrix code and the information contained
therein in plain text.
The 2 D code (Data Matrix Code) contains the following information:
Part number: 1234.567
Hardware revision: 1
Serial number: 20000 (for mini matrix 20001)
The device label with matrix code can be designed as mini-sticker.
Figure 66: Example 2D Label (mini sticker on the right)
11.2 Tolerances of the shown Card Dimensions

The manufacturing tolerance of the printed circuit boards of the PC card
cifX is ± 0.1 mm per milled PCB edge. For all dimensions of the PCB
indicated on the drawings (in the sections Dimensions PC Cards cifX PCI
and PCI Express from page 221 and Dimensions PC Cards cifX Low Profile
PCI Express from page 254) thus results for the length L and the width W,
a tolerance of ± 0.1 mm (per milled edge) x 2 = ± 0.2 mm.
W = [width of the board in mm] ± 0.2 mm
L = [length of the board in mm] ± 0.2 mm
The depth T of the PCB depends on the highest part used or the circuit
board plus the descenders. The thickness of the PCB is = 1.6 mm ± 10%.
Note: The dimensions (L x W x D) specified in section Technical Data PC

Cards cifX on page 147 (and also the identical values in the data sheet
cifX and on the ‘Hilscher Site’) are rounded and unified for the respective
types of card. Here the depth of the PC cards PCI (CIFX 50), PCI Express
(CIFX 50E) or Low Profile PCI Express (CIFX 70E) has been equated to
the rounded width of the front panel.
Annex 221/284
11.3 Dimensions PC Cards cifX PCI and PCI Express
11.3.1 CIFX 50-RE
25.40
S1
4
1
C
C
R90
8
Matrix_Code
L0602014
R3 R2 R1
YG
V1
V200
YG
R209
R212
R208
V201
YG
R211
R210
85.34
X200
79.25
CH_A
70.71
C9 C135 C131 C153 R91
CIFX 50-RE
C110 N110 L110 C132 G1 D2
64.11
31.12 (+0.16/-0.0)
C200 C2 C6
R202 C8
C201
57.51
45DBxx D1 25
C111
Hilscher
R203
R111 R110
SDRAM2Mx32
D4 C4 D3 C3 N1 C1
R207
C152
D10 R200 C154 R33
C100
C205 C150
C204
LCX08
36.07
C202 C7
R204
3
C203
L200 C130
C206
R205
L201 C207
CH_B
R100
1
R201 X51
C133 C5
AOI C151
R206
C134
1.83 X2
B1 B62
11.16
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 67: Dimensions CIFX 50-RE (from Hardware Rev.3
Annex 222/284
11.3.2 CIFX 50E-RE, CIFX 50E-RE\ET
25.40
S1
1
R90
C
8
2
Matrix_Code
BOOT
YG
R1
R2
R3
V1 R212
R209
YG
V200
R208
YG
R211
R210
V201
85.34
79.25
CH_A
70.71
R207 D4 C110 L110 C135 C131

R200 D3 C4
64.11
C9 C153 C132 C8 C6
31.12 (+0.16/-0.0)
45DBxx
C2
57.51
25
C111
R110
R202 C200
N110 C20H
CIFX50E-RE
R203 C201
L0608012
C17E C17F C18B C18E R111
R34
C17D
SDRAM2Mx32
C18C
D5 C17C N1
R5 C17 C1 G1
C3
C17I AOI
27.81
C152
C150
C17J
C204 C154
C18A R11
C18D R19
C205
R201
C17G
R33
C17H
R7 R12
L201 L200
C7
R204 C202
R205 C203
1
R10A
C130
R15
C133
R126
R10D
C207
R6 R13 C5
C16A
C206
CH_B
R16 R18B R19A R10C
3
R10B C16 D1
C16B R18A D2
C19D
X200
C17B R17 R206 C134 X51
C1
C16C C17A C151

1
R20A
C1
C15C
C14C
1.83
0
C20E
11.16
C20G C19C
C15A C20B C19A
C15B C20A C19B
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 68: Dimensions CIFX 50E-RE (from Hardware Rev.4), CIFX 50E-RE\ET (from
Hardware Rev.1)
Annex 223/284
11.3.3 Front Panel CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET
Figure 69: Dimensions Front Panel CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET
Annex 224/284
55.95
64.20
52.97
50.43
47.92
31.18
28.37
11.63
15.00
33.35
41.35
45.00
56.20
58.10
65.30
118.00
Figure 70: Dimensions CIFX 50E-CCIES (from Hardware Rev.1)
Annex 225/284
11.3.5 Front Panel CIFX 50-CCIES
Figure 71: Dimensions Front Panel CIFX 50E-CCIES
Annex 226/284
11.3.6 CIFX 50-DP, CIFX 50E-DP
25.40
Hilscher
1
R90
C
8 S1
2
AOI
R3 R2 R1
YG
V1
V200 BOOT
YG
R209
R208
R370 C370
R8
85.34
79.25
70.71
U401 C403 C110 L110 C135 C131 R34 C153 C132 C8 D2 C6

L401 N110 G1
64.11
R405
PSD-3R305S
C2
L400
XXXXX
R413
C111 25
Buchse
30.89
R111 R110 C11
SDRAM2Mx32
N1 C1 XXXX.XXX X
C3 R33 Matrix Code
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
U410 C152
C154
D3
C4
C404
L0618015
C411 C150
R5 R7
36.07
RM=2.54mm U400
C7
R400
R403
6.83 R404 C130

45DBxx
EU US
C401
C133 C5
C134
X400 R35 D4 C151
C400 C9 C10
B1 B62
11.28
X2
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 72: Dimensions CIFX 50-DP (Hardware Rev.5)
Annex 227/284
25.40
S1
1
R90
C
8
2
Matrix_Code
YG
R1
R2 L400 L401
R3 R413
BOOT
V1
R212
C403
C404
YG
R209
U401
U410
V200
R208 PSD-3R305S
C411
C370
R370
85.34
79.25
70.71
D4 D3 C4 L110 C135 C131
C110
64.11
C153 C132 C8 C6
R400
45DBxx
R405 C9
C111
C2
N110
R404 R110 25
Buchse
L0731013
30.89
C17E C17F C18B R111 AOI
SDRAM2Mx32
C18C
CIFX50E-CO-DN-DP
D5 R34 C1
R5 G1
C17I
27.81
C17J C17 N1 C3
C152
C18A
C150
C18D R19
R33
C17G C20H C154
C400
C17H C18E
RM=2.54mm R7 C17D R11
C401 U400 C17C
C7
R10A
T6 R12
6.83
R403
C133
C130
R15 R10D R17 C5
R126 R18B R18A C18
R6 R10C R13
R16 R10B
EU US R19A C16 C134
D2
C19D D1
X400 C1
C15C
C14C
C151
1
C16A R20A
C16B C16C
C1
0
C20E C19C
11.28
C17B C20G C19A

C17A C15A C20B C19B
C15B C20A
C14A
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 73: Dimensions CIFX 50E-DP (Hardware Rev.6)
Annex 228/284
11.3.7 Front Panel CIFX 50-DP or CIFX 50E-DP
Figure 74: Dimensions Front Panel CIFX 50-DP or CIFX 50E-DP
Annex 229/284
11.3.8 CIFX 50-CO, CIFX 50E-CO
25.40
Hilscher
1
R90
C
S1
8
2
AOI
R3 R2 R1
YG
V1
V200 BOOT
YG
R209
R208
R370 C370
R8
85.34
79.25
70.71
U401 C403 C110 L110 C135 R34

L401 N110 C153 C132 G1 C8 D2 C6
64.11
PSD-3R305S
L400 C131
XXXXX
C2
R406
25
R413
C111
Stecker
30.89
R111 R110 C11
SDRAM2Mx32
N1 C1 XXXX.XXX X
C3 R33 Matrix Code
CIFX 50-DP
CIFX 50-DN
CIFX 50-CO
C154
D3 C152
C4
U410 C404
L0618015
C411
36.07
RM=2.54mm C360 C150
R5 C7
HCPL
060L
R364 R361
V365
6.83 U361
45DBxx
R360
R363
R6 C130
82C
HCPL
X400
0601
EU US C133
N360 C134 C5
C362 R35 D4 C151
C367 U360 C9 C10
B1 B62
11.28
X2
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 75: Dimensions CIFX 50-CO (Hardware Rev.5)
Annex 230/284
25.40
S1
1
R90
C
8
2
Matrix_Code
YG
R1
R2 L400 L401
R3 R413
V1
BOOT
R212
C403
C404
YG
R209
U401
U410
V200
R208 PSD-3R305S
C411
C370
R370
85.34
79.25
70.71
D4 D3 C4 L110 C135 C131
C110
64.11
C153 C132 C8 C6
45DBxx
C9
C111
C2
R406 N110
U361 R110 25
Stecker
L0731013
AOI
30.89
HCPL
R111
060L
C17E C17F C18B
SDRAM2Mx32
C18C
CIFX50E-CO-DN-DP
D5 R34 C1
C360
R361
R5 G1
C17I
27.81
U360 C17J C17 N1 C3
C152
C18A
C150
HCPL
C18D
0601
R19
R33
C17G C20H C154
C17H
R360
C18E
RM=2.54mm R7 C17D R11
C367
C17C
C7
R10A
6.83 R12
R364
R363
C133
C130
R15 R10D
R18B R18A R17 C5
R126
R6 C18 R10C R13
N360 R16 R10B
82C
EU US V361 D2
C362
R19A C16 C134

C19DC11 D1
X400
C15C
C14C
C16A R20A C1 C151

C16B C16C 0
C20E C19C
11.28
C17B C20G C19A

C17A C15A C20B C19B
C15B C20A
C14A
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 76: Dimensions CIFX 50E-CO (from Hardware Rev.4)
Annex 231/284
11.3.9 Front Panel CIFX 50-CO or CIFX 50E-CO
Figure 77: Dimensions Front Panel für CIFX 50-CO or CIFX 50E-CO
Annex 232/284
11.3.10 CIFX 50-DN, CIFX 50E-DN
25.40
Hilscher
1
R90
C
C
S1
8
2
AOI
R3 R2 R1
YG
V1
V200 BOOT
YG
R209
R208
R370 C370
R8
R371
C371
85.34
79.25
70.71
U401 C403 C110 L110 C135 C131 R34 C8 D2 C6

L401 N110 C153 C132 G1
64.11
PSD-3R305S
C2
L400
XXXXX
2
R413
C361 C111 25
27.40
R111 R110 C11

R365
SDRAM2Mx32
C363 N1 XXXX.XXX X
3
C3 R33 C1 Matrix Code
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
U410 N361 C152
D3
C154
R366
C4
C404 U362
L0618015
R362
4
R369 C411 C150

R7
36.07
C360 C7
HCPL
060L
R364 R361
V365
5
U361 C130
45DBxx
R360
R363
R4
82C
HCPL
0601
C133 C5
4.70 N360 C134 C151
C362 U360 R35 D4
C367 C9 C10
13.02
B1 B62
X2
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 78: Dimensions CIFX 50-DN (Hardware Rev.5)
Annex 233/284
25.40
S1
1
R90
C
8
2
Matrix_Code
YG
R1
R2 L400 L401
R3 R413
V1
BOOT
R212
C403
R209 C404
YG
U401
U410
V200
R208 PSD-3R305S
C411
C370
R370 R371
C371
85.34
79.25
R366
70.71
C361
D4 D3 C4 L110 C135 C131
R365
C110
U362 C8 C6
64.11
C363 C153 C132

45DBxx C9
C111
2
C2
N110
U361 R110 25
L0731013
N361
27.40
HCPL
R111
060L
C17E C17F C18B AOI

C18C
SDRAM2Mx32
CIFX50E-CO-DN-DP
D5 R34 C1
3
C360
R362
R5 G1
C17I
C17J C17 N1
27.81
U360 C3
C152
C18A
C150
HCPL
C18D
0601
R19
R33
4
R369 C17G C20H C154

C17H
R360
C18E
C367 R7 C17D R11
C17C
C7
R10A
5
R12
R364
R363
C130
R15
C133
R10D R17
R126 R18B R18A C5
R6 C18 R10C R13
N360 R16 R10B
82C
V361 D2
C362
R19A C16 C134

C19DC11
4.70 D1
C15C
C14C
C16A R20A C1 C151

C16B C16C 0
13.02
C20E C19C
C17B C20G C19A
C17A C15A C20B C19B
C15B C20A
C14A
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 79: Dimensions CIFX 50E-DN (from Hardware Rev.4)
Annex 234/284
11.3.11 Front Panel CIFX 50-DN or CIFX 50E-DN
Figure 80: Dimensions Front Panel CIFX 50-DN or CIFX 50E-DN
Annex 235/284
11.3.12 CIFX 50-CC, CIFX 50E-CC
25.40
S1
XXXXX
4
1
R90
C
XXXX.XXX X
2
Matrix Code
R1 L72 C71 L71
YG
R3
R2
C68
V1 R99
R208A C69
U72
YG
R208D
PSD-3R305S
R212
V200
YG
V201
U71
C73
C74
85.34
79.25
70.71
C131
L110 C111 C135 R34
C110 N110 C153 C132 G1 C8 D2 C6
64.11
C2
2
57.51
25 AOI
27.40
R111 R110 C11
SDRAM2Mx32
R33
N1
3
U70
C3 C1
C75
HCPL
061N
C70
CIFX50-CC
CIFX50-CP
C152
Hilscher GmbH
L70
D3
C154
N70 R71 R70
C4
R78
L0912012
4
R5 R7 C150
36.07
U73
C7
75ALS181
HCPL
R80
0720
D70 C76
5
C77 D4 C130
45DBxx
R4 R6
R79 R72 R35
HCPL
0720
C79 C133
C78 C134 C5
4.70 V70 R81 C72
U74 C151
C9 C10
13.02
X2
B1 B62
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 81: Dimensions CIFX 50-CC (Hardware Rev.2)
Annex 236/284
25.40
XXXXX
4
1
R90
C
XXXX.XXX X
2
S1
Matrix Code
YG
R1
R2
R3
V1
R208A
YG
R208D
Hilscher
V200 R99
YG
GmbH
R212
V201
85.34
79.25
70.71
D4 L110 C135 C131

R1S-3.305
D3 C4 D2
C110
C8 C6
64.11
C69 C9 C153 C132

L71
45DBxx
C2
C111
2
L0910012
CIFX50E-CC
CIFX50E-CP
57.51
N110
R110
25
27.40
C17E C17F C18B

R111
SDRAM2Mx32
C71 L72 R70 C18A C18C
D5
3
U72 C18D R34 C1 AOI

C17G R5 G1
D70 R71 U70 C17H
C73 R7 C17I
HCPL
27.81
C152
C150
061N
C17J
C75 C17 N1 C3
R19 C154
R72
4
C74 C20H
R33
L70 C70 C18E
U71 C15 R11
C17D
R15 T4 T3
C7
HCPL
C17C
0720
C76
R78 C77 R10A

75ALS181
T2 R12
C130
5
T6
C133
R80 R126
U73 R6 R17 C5
R81 C78 T1 R18B R18A
HCPL
R79
0720
C79
C72
4.70 R13
C1
N70 T5 C16 C134 C151 D1
U74 R16 C16A
1
V70
C16B C16C R20A R10D
C15C
C14C
C1
13.02
C20E 0 R8
C17B C20G C19C R10C
C20B C19A R10B
C17A C15A C19B C19D
C15B C20A
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 82: Dimensions CIFX 50E-CC (from Hardware Rev.4)
Annex 237/284
11.3.13 Front Panel CIFX 50-CC or CIFX 50E-CC
Figure 83: Dimensions Front Panel CIFX 50-CC or CIFX 50E-CC
Annex 238/284
11.3.14 CIFX 50-2DP

59.94
R1 Hilscher L600
made in Germany 8 C 4
BOOT C603 L601
LP 2 C 1
R2 C604
R3 R1S3.305
U610 U601
S1
V1 V200 V201 C570 R90
C605
T600
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
R601
R616
L0834002
R602 R614
R606 R603 R613
R604 R611 R615 R612
R600 C601 C600
ALS176
Buchse
30.89
R605
U600
C606 N620
CIFX 50-DP
CIFX 50-DN
CIFX 50-CO
4.67
L400
94.49
C403 L401
R570
X600 C370
C404
82.02
R1S3.305
U401
U410
R401
T400
C405 C135 C131 R34
C100 R110 C153 C132 G1 C8 D2 C6
R406 N110
XXXXX
R402 R414 D10 C110 C2
R413
C111
R403
R416 R412 R100
25
R404
R400 R411
Buchse
LCX08
30.89
ALS176
R415 XXXX.XXX X
SDRAM2Mx32
C11 Matrix Code
N1 C1
C400
C401 R33
R405
U400 C3 C152
N420 D3
C154
C406
C4
R7 C150 -
36.07
C7
C130
D4
C133
C12
45DBxx
R4
X400
R370
C134 C151
C5 AOI
C9 C10
B1 X2 B62
11.28
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 84: Dimensions CIFX 50-2DP (Hardware Rev.3)
Annex 239/284
11.3.15 CIFX 50E-2DP
62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3 U610
S1
V1 V200 V201 C570
AOI R90
C605
CIFX 50E-DN
CIFX 50E-DP
CIFX 50E-CO
T600
L1510011
R601
R616
R602 R614
R606 R603 R613
R604 R611 R615 R612
R600 C601 C600
ALS176
Buchse
30.89
R605
U600
C606 N620
XXXXX
XXXX.XXX
CIFX 50E-DP
CIFX 50E-CO
CIFX 50E-DN
94.49
4.67
L400
C403 L401
R570
X600 U401
C370 C9
C404
82.02
U410
R110
N110 C135 C131
R401
45DBxx D3 C4
T400 C110 C153 C132 C8 C6
C111
C405 C2
U400
R406 R402 R414 D4
R403
R416
R413
R412
25
R411
R404
R400 C17E C17F C18B
SDRAM2Mx32
C18A C18C
Buchse
D5
30.89
C18D R34 C1
ALS176
R415 C17G R5 G1
C17H C17I
R7
C400
C152
C150
C401 C17J N1
30.35
C17 C3
R19
R33
R405
N420 R11 C154

C406 C20H
C18E
C15 C17D
T4
R100
C7
C17C R211
R10A
R15
R12
C130
T2 T3 T6
C133
R17 C5
R126 T1 R18B R18A R19A
R6
R16
D2
R370 T5
R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C15C
C14C
X400 C17B
C20E
C20G C19C R8
R10C
C20B C19A R10B
C17A C15A C19B C19D
11.28
C15B C20A
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 85: Dimensions CIFX 50E-2DP (Hardware Rev.1)
Annex 240/284
11.3.16 CIFX 50-2DP\CO

59.94
R1 Hilscher L600
BOOT C603 L601
LP 2 C 1
R2 C604
R3 U610
R1S3.305
U601
S1
V1 V200 V201 C570 R90
C605
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
L0834002
R607
Stecker
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
U561
82C
C567
U560
HCPL
0601
R560
N560 R563
CIFX 50-DP
CIFX 50-DN
CIFX 50-CO
4.67
L400
94.49
C403 L401
R570
X600 C370
C404
82.02
R1S3.305
U401
U410
R401
T400
C405 C135 C131 R34
C153 C132 C8 D2
C100 R110 G1 C6
R406 N110
XXXXX
R402 R414 D10 C110 C2
R413
C111
R403
R416 R412 R100
25
R404
R400 R411
Buchse
LCX08
30.89
ALS176
R415 XXXX.XXX X
SDRAM2Mx32
C11 Matrix Code
N1 C1
C400
C401 R33
R405
U400 C3 C152
N420 D3
C154
C406
C4
R7 C150
36.07
C7
C130
D4
C133
C12
45DBxx
R4
X400
R370
C134 C151
C5 AOI
C9 C10
B1 X2 B62
11.28
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 86: Dimensions CIFX 50-2DP\CO (Hardware Rev.2)
Annex 241/284
11.3.17 CIFX 50E-2DP\CO

62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3
U610
S1
V1 V200 V201 C570
AOI R90
C605
CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
L1510011
R607
Stecker
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
XXXXX
U561
82C
C567
U560
HCPL
0601
R560 XXXX.XXX
N560 R563
CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
94.49
4.67
L400
C403 L401
R570
X600 U401
C370 C9
C404
82.02
U410
R110
N110 C135 C131
R401
45DBxx D3 C4
T400 C110 C153 C132 C8 C6
C111
C405 C2
U400
R406 R402 R414 D4
R403 R413 25
R411 R416 R412
R404
R400 C17E C17F C18B
SDRAM2Mx32
C18A C18C
Buchse
D5
30.89
C18D R34 C1
ALS176
R415 C17G R5 G1
C17H C17I
R7
C400
C152
C150
C17J
C401 C17 N1 C3
30.35
R19
R33
R405
N420 R11 C154

C406 C20H
C18E
C15 C17D
T4
R100
C7
C17C R211
R10A
R15
R12
C130
T2 T3 T6
C133
R17 C5
R126 T1 R18B R18A R19A
R6
R16
D2
R370 T5 R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C15C
C14C
X400 C17B
C20E C19C
C20G C19A
R8
R10C
C17A C15A C20B R10B
C20A C19B C19D
11.28
C15B
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 87: Dimensions CIFX 50E-2DP\CO (Hardware Rev. 1)
Annex 242/284
11.3.18 CIFX 50-2DP\DN
59.94
R1 Hilscher L600
BOOT C603 L601
LP 2 C 1
R2 C604
R3 R1S3.305
U610 U601
S1
V1 V200 V201 C570 R90
R571
C571 C605
CIFX 50-DN
CIFX 50-CO
CIFX 50-DP
1
L0834002
2
R607
27.40
R608 V565
3
HCPL
R561
060L
R564
C560
C562
U561
82C
C567
4
U560
HCPL
0601
R560
N560 R563 R562
R569
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
C563
5
V564 N561
L400
94.49
R566 R565 U562 C403 L401

C561
6.65
R570
C370
C404
82.02
R1S3.305
U401
U410
R401
T400
C405 C135 C131 R34
C100 R110 C153 C132 G1 C8 D2 C6
R406 N110
XXXXX
R402 R414 D10 C110 C2
C111
R403 R413 R100
R416 R412
25
R404
R400 R411
Buchse
LCX08
30.89
ALS176
R415 XXXX.XXX X
SDRAM2Mx32
C11 Matrix Code
N1 C1
C400
C401 R33
R405
U400 C3 C152
N420 D3
C154
C406
C4
R7 C150
36.07
C7
C130
C133
D4
C12
45DBxx
R4
X400
R370
C134 C151
C5 AOI
C9 C10
B1 X2 B62
11.28
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 88: Dimensions CIFX 50-2DP\DN (Hardware Rev.1)
Annex 243/284
11.3.19 CIFX 50E-2DP\DN
62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3
U610
S1
V1 V200 V201 C570
R571 AOI R90
C571 C605
CIFX 50E-CO
CIFX 50E-DP
CIFX 50E-DN
L1510011
R607
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
XXXXX
U561
82C
C567
HCPL U560
0601
R560 XXXX.XXX
N560 R563 R562
CIFX 50E-DN
CIFX 50E-DP
CIFX 50E-CO
R569
94.49
C563
4.67
V564 N561
L400
R566 R565 U562
C403 L401
C561
R570
X600 U401
C370 C9
C404
82.02
U410
R110
N110 C135 C131
R401
45DBxx D3 C4
T400 C110 C153 C132 C8 C6
C111
C405 C2
R406 U400
R402 R414 D4
R403
R416
R413
R412
25
R404
R400 R411 C17E C17F C18B
SDRAM2Mx32
C18A C18C
Buchse
D5
30.89
C18D R34 C1
ALS176
R415 C17G R5 G1
C17H C17I
C400
R7
C152
C150
C17J
C401 C17 N1 C3
30.35
R19
R33
R405
N420 R11 C154

C406 C20H
C18E
C15 C17D
T4
R100
C7
C17C R211
R10A
R15
R12
C130
T2 T3 T6
C133
R17 C5
R126 T1 R18B R18A R19A
R6
R16
D2
R370 T5 R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C14C
C15C
X400 C17B
C20E
C20G C19C R8
R10C
C20B C19A R10B
C17A C15A C19B C19D
C20A
11.28
C15B
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 89: Dimensions CIFX 50E-2DP\DN (Hardware Rev. 1)
Annex 244/284
11.3.20 CIFX 50-2CO

59.94
R1 Hilscher L600
BOOT C603 L601
LP 2 C 1
R2 C604
R3 R1S3.305
U610 U601
S1
V1 V200 V201 C570 R90
C605
CIFX 50-DN
CIFX 50-DP
CIFX 50-CO
L0834002
R607
Stecker
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
U561
82C
C567
U560
HCPL
0601
R560
N560 R563
CIFX 50-DP
CIFX 50-CO
CIFX 50-DN
4.67
L400
94.49
C403 L401
R570
X600
C370
C404
82.02
R1S3.305
U401
U410
C405 C135 C131 R34 C8

C100 R110 C153 C132 G1 D2 C6
N110
XXXXX
D10 C110 C2
C111
R100
R407
25
Stecker
LCX08
30.89
XXXX.XXX X
SDRAM2Mx32
R408 V365 C11 Matrix Code
N1 R33 C1
R364
C3 C152
D3
C154
C4
C360
HCPL
060L
R361
82C
R7 C150
36.07
U361 C7
C362
C130
C133
U360 D4
N360
HCPL
0601
C12
45DBxx
R363 R360
C367 R4
X400
R370
C134 C151
C5 AOI
C9 C10
B1 X2 B62
11.28
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 90: Dimensions CIFX 50-2CO (Hardware Rev.2)
Annex 245/284
11.3.21 CIFX 50E-2CO

62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3 U610
S1
V1 V200 V201 C570
AOI R90
C605
CIFX 50E-CO
CIFX 50E-DP
CIFX 50E-DN
L1510011
R607
Stecker
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
XXXXX
U561
82C
C567
HCPL U560
0601
R560 XXXX.XXX
N560 R563
CIFX 50E-DN
CIFX 50E-DP
CIFX 50E-CO
94.49
4.67
L400
C403 L401
R570
X600 U401
C370 C9
C404
82.02
U410
R110
45DBxx D3 C4 N110 C135
C110 C153 C132 C8 C6
C111
C405 C2
D4
25
R407
C17E C17F C18B
SDRAM2Mx32
C18C
Stecker
C18A D5
30.89
C18D R34 C1
C17G R5 G1
R408 V365 C17H C17I
R361
R7
C152
C150
C17J N1 C3
30.35
C17
R19
R33
R364 R11 C154
U361 C20H
C360 C18E
HCPL
060L
C15 C17D
82C
T4
R100
C7
C17C R211
R10A
R15
R12
C130
C362 U360 T2 T3 T6
C133
R360 R17 C5
N360
HCPL
R126
0601
T1 R18B R18A R19A

R363 R6
C367 R16
D2
R370 T5 R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C14C
C15C
X400 C17B
C20E
C20G C19C R8
R10C
C19A R10B
C17A C15A C20B C19B C19D
11.28
C15B C20A
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 91: Dimensions CIFX 50E-2CO (Hardware-Rev. 1)
Annex 246/284
11.3.22 CIFX 50-2CO\DN

59.94
R1 Hilscher L600
BOOT C603 L601
LP 2 C 1
R2 C604
R3 U610
R1S3.305
U601
S1
V1 V200 V201 C570 R90
R571
C571 C605
CIFX 50-DP
CIFX 50-CO
CIFX 50-DN
1
L0834002
R607
2
26.90
R608 V565
3
R561
HCPL
060L
R564
C560
C562
U561
82C
C567
4
U560
HCPL
0601
R560
R569 N560 R563 R562
CIFX 50-DP
CIFX 50-DN
CIFX 50-CO
C563
5
V564 N561
L400
94.49
R566 R565 U562 C403 L401

C561
6.65
R570
C370
C404
82.02
R1S3.305
U401
U410
C405 C135 C131 R34 C8 D2

C100 R110 C153 C132 G1 C6
N110
XXXXX
D10 C110 C2
C111
R100
R407
25
Stecker
LCX08
30.89
XXXX.XXX X
SDRAM2Mx32
R408 V365 C11 Matrix Code
N1 R33 C1
R364
C3 C152
D3
C154
C4
C360
HCPL
060L
R361
C150
82C
R7
36.07
U361 C7
C362
C130
D4
C133
N360 U360
HCPL
0601
C12
45DBxx
R363 R360
C367 R4
X400
R370
C134 C151
C5 AOI
C9 C10
B1 X2 B62
11.28
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 92: Dimensions CIFX 50-2CO\DN (Hardware Rev.1)
Annex 247/284
11.3.23 CIFX 50E-2CO\DN

62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3 U610
S1
V1 V200 V201 C570
R571 AOI R90
C571 C605
CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
L1510011
R607
30.89
R608 V565 R561
HCPL
060L
R564
C560
C562
XXXXX
U561
82C
C567
U560
HCPL
0601 R560 XXXX.XXX
N560 R563 R562
CIFX 50E-DN
CIFX 50E-DP
CIFX 50E-CO
R569
94.49
C563
4.67
V564 N561
L400
R566 R565 U562
C403 L401
C561
R570
X600 U401
C370 C9
C404
82.02
U410
R110
45DBxx D3 C4 N110 C135 C131
C110 C153 C132 C8 C6
C111
C405 C2
D4
25
R407
C17E C17F C18B
SDRAM2Mx32
C18A C18C
Stecker
D5
30.89
C18D R34 C1
C17G R5 G1
R408 V365 C17H C17I
R361
R7
C152
C150
C17J N1
30.35
C17 C3
R19
R33
R364 R11 C154
U361 C20H
C360 C18E
HCPL
060L
C15 C17D
82C
T4
R100
C7
C17C R211
R10A
R15
R12
C130
U360 T2 T3 T6
C133
C362
R360 R17 C5
N360
HCPL
R126
0601
T1 R18B R18A R19A

R363 R6
C367 R16
D2
R370 T5 R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C15C
C14C
X400 C17B
C20E
C20G C19C R8
R10C
C19A R10B
C17A C15A C20B C19B C19D
11.28
C15B C20A
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 93: Dimensions CIFX 50E-2CO\DN (Hardware Rev. 1)
Annex 248/284
11.3.24 CIFX 50-2DN

59.94
R1 Hilscher L600
made in Germany
BOOT C603 L601
LP
R2 C604
R3 U610
R1S3.305
U601 S1
V1 V200 V201 C570 R90
R571
C571 C605
CIFX 50-CO
CIFX 50-DP
CIFX 50-DN
1
L0834002
2
R607
27.40
R608 V565
3
HCPL
R561
060L
R564
C560
C562
U561
82C
C567
4
U560
HCPL
0601
R560
R569 N560 R563 R562
CIFX 50-DP
CIFX 50-CO
CIFX 50-DN
C563
5
V564 N561
L400
94.49
R566 R565 U562 C403 L401

R570 C561
8.29
X600 C370
C404
82.02
R371 R1S3.305
U401
U410
C371
1
C405 C135 C131 R34 C8 D2

C100 R110 C153 C132 G1 C6
N110
XXXXX
D10 C110 C2
2
C111
R100
R407
25
LCX08
27.40
XXXX.XXX X
SDRAM2Mx32
R408 V365 C11
3
N1 C1 Matrix Code
R33
R364
C3 C152
D3
C154
C360
C4
HCPL
060L
4
R361
C150
82C
R7
36.07
U361 C7
R369 C362
C130
D4
C133
U360
5
N360
HCPL
0601
C12
45DBxx
R363 R360
C367 R4
R362
V364
X400
R370
R366 R365
C363
C134 C151
C5 AOI
C361 U362 N361
C9 C10
13.04
B1 X2 B62
15.01
40.77
55.28
57.14
103.56
105.38
119.91
Figure 94: Dimensions CIFX 50-2DN (Hardware Rev.2)
Annex 249/284
11.3.25 CIFX 50E-2DN

62.48
R1 Hilscher L600
BOOT C603 L601
R208
R210
U601
LP 2 C 1
R2 C604
R3
U610
S1
V1 V200 V201 C570
R571 AOI R90
C571 C605
CIFX 50E-CO
CIFX 50E-DN
CIFX 50E-DP
L1510011
R607
30.89
R608 V565
HCPL
R561
060L
R564
C560
C562
XXXXX
U561
82C
C567
HCPL U560
0601 R560 XXXX.XXX
N560 R563 R562
CIFX 50E-DP
CIFX 50E-CO
CIFX 50E-DN
R569
94.49
C563
4.67
V564 N561
L400
R566 R565 U562
C403 L401
C561
R570
X600 U401
C370 C9
C404
82.02
R371
U410
C371 R110
45DBxx D3 C4
C110 N110 C135 C131
C153 C132 C8 C6
C111
C405 C2
D4
25
R407
C17E C17F C18B
SDRAM2Mx32
C18A C18C
D5
30.89
C18D R34 C1
C17G R5 G1
R408 V365 C17H C17I
R361
R7
C152
C150
C17J N1
30.35
C17 C3
R19
R33
R364 R11 C154
U361 C20H
C360 C18E
HCPL
060L
C15 C17D
82C
T4
R100
C7
C17C R211
R10A
R15
R12
C130
U360 T2 T3 T6
C133
R369 C362
R360 R17 C5
N360
HCPL
R126
0601
T1 R18B R18A R19A

R363 R6
C367 R16
D2
R370 V364 R362 T5
R13
C16 C134 D1 C151
C11
C10
C16A
C16B C16C R20A R10D
C14C
C15C
X400 R366 R365 N361 C20E C19C R8

R10C
C361 U362
C363 C17B
C15A
C20G
C20B C19A
C19B R10B
C17A C19D
11.28
C15B C20A
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.89
Figure 95: Dimensions CIFX 50E-2DN (Hardware Rev. 1)
Annex 250/284
11.3.26 Front Panel CIFX 50-2FB
Figure 96: Dimensions Front Panel CIFX 50-2FB
Annex 251/284
11.3.27 CIFX 50-2ASM, CIFX 50E-2ASM

62.48
C303
V300 C302
D300
R90
S1
C301
L300 C300
ASI4UC-E-M
U300 C305
ADuM1301
R303
E300
V1 BOOT
YG R1
R3 V301
R2 R305
V200 V302B
R302
R301
R308
R309
C308
YG
R307
R208B
V302 C353
R208A V350 C352 D350
V201 R212
YG
R208D
R353
R208C L350
C351
C350
ASI4UC-E-M
U350 C355
ADuM1301
E350
94.49
V351
X300
79.25
R355
R351
R352
R358
R357
R359
C358
V352B V352
70.71
1
12.19
C111 C135 C131 R34

3.05
C110 N110 L110 C153 C132 C8 D2 C6

G1
64.11
CIFX50-2ASM C2 Matrix
2
57.51
L301 Hilscher 25
made in Germany R111 R110 C11 Label
SDRAM2Mx32
N1 C1
X350 C3 R33
L0916002
C154
L351 D3 C152
UL
C4
1
38.61
12.19
C150
C7
D4
2
R4 R6 C130
45DBxx
R35
C133 C5
C134 AOI
C9 C10 C151
X2
13.00
B1 B62
15.01
40.77
55.28
57.14
103.56
105.38
119.89
Figure 97: Dimensions CIFX 50-2ASM (Hardware Rev.2)
Annex 252/284
62.48
C303
V300 C302
R90
XXXXX
D300
S1 XXXX.XXX X
C301
L300 C300 Matrix Code
ASI4UC-E-M
U300 C305
R303
ADuM1402
ADuM1301
E300
YG
R1
R2 BOOT V301 R305
R3
V1 R314
V302B
R302
R301
YG
R307
R308
R309
C308
R208B
R208A V302
C353
V200 V350 C352 D350
R212 AOI
YG
R208D
R353
R208C L350
ASI4UC-E-M
C351
V201
C350
U350 C355
ADuM1402
ADuM1301
E350
94.49
V351
R355
R364
79.25
R351
R352
R357
R358
R359
C358
V352B V352
70.71
1
12.19
3.05
D4 C110 L110 C135 C131

D3 C4
64.11
C9 C153 C132 C8 C6
45DBxx
C2
2
57.51
R34 C111
L301
N110 C20H R110 25
L0917013
CIFX50E-2ASM
C17E C17F C18B C18E R111
C18C C17D
SDRAM2Mx32
C18A
C18D D5 C17C C17 N1
C17G R5 C1 G1
30.35
C3
C17H C17I
R7
C152
C150
C17J R11
L351
C154
R19
1
12.19
R33
C15
T4 R12
C7
R10A
2
C130
T2 T3 T6
C133
R15 C5
R126 T1 R18B R18A R19A R13
R6
R16 D1
R17 D2
T5
C1
C134 C16 C151
1
C16A
C16B C16C R20A R10D
C1
C15C
C14C
13.00
R8
0
C20E C19C R10C
C17B C20G C19A R10B
C17A C15A C20B C19B
C15B C20A C19D
C14A C18
C14B R18D
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.91
Figure 98: Dimensions CIFX 50E-2ASM (from Hardware Rev.2)
Annex 253/284
11.3.28 Front Panel CIFX 50-2ASM, CIFX 50E-2ASM
Figure 99: Dimensions Front Panel CIFX 50-2ASM, CIFX 50E-2ASM
Annex 254/284
11.4 Dimensions PC Cards cifX Low Profile PCI Express

GND CIFX70E-RE
XXXXX
R90 8 C 4 S1 L1113011
AOI XXXX.XXX X 2 C 1
Hilscher GmbH
V201
V200
R209
R208
R211
R210
R21
R20
C12B
V2
V1
R2
R3
C12
R1
C113F
BOOT
C114C
C114D
C115C
C115D
C114B
C114E
C115B
C115E
R33
C110D
C110C
C110E
C110B
D4
C113D
C113C
C113B
C113E
C113
C9
C14D
45DBxx
C14
R214 D3 C116C C116D
C110 G1 C116B C116E
CH_A
L110 C135 C131

C111 C153 C132 D2
C4 C8
C6B
R207 C2
56.13
C6
C123E
C123D
C123C N110 C112
25
C18C
C17E
C18B
C17F
C123B R110
64.39
31.12 (+0.16/-0.0)
R111
R34
D5
SDRAM2Mx32
N1
R200 R5 C17 C1
C17I
C3
C152
C150
C17J
R11 R12
C204 C154
C18A
C201 C200
C205
C18D R19
C122E C17G C20H

47.84
R203 R202 C122D C15

C17H C18E
L201 L200
R7 C17D
C122C T4
C7
C17C
C122B R10A
R15
C130
T3
T6
C133
T2
R126
R201 C16A R10D
C207
R6 C16B
C206
C20E C19C
R16 T1 R18B R18A C15A

C15B
C14A
C14B
C18
R18D
C20G
C20B
C20A
C19A
C19B R19A
R10C
R10B R13
C203 C202 C121E C19D
D1
C5B
C121D T5 R17
C151
C5
C134 C16
C121C
R100
C17A C17B
C16C C15C C14C R20A C10 C11 R206
C121B
CH_B
R205 R204
C119C
C119D
C118C
C118D
C117C
C119B
C119E
C118B
C118E
C117B
C117E
C117D
C109
3 1
C120C
C120D
X51
C120B
C120E
X200
1.04
11.16
T11 T12
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.00
Figure 100: Dimensions CIFX 70E-RE and CIFX 70E-RE\MR (Hardware Rev.1)
Annex 255/284
11.4.2 Front Panel CIFX 70E-RE, CIFX 70E-RE\MR
Figure 101: Dimensions Front Panel für CIFX 70E-RE, CIFX 70E-RE\MR
Annex 256/284
55.95
64.20
52.97
50.43
47.92
31.18
28.37
11.63
15.00
33.35
41.35
45.00
56.20
58.10
65.30
118.00
Figure 102: Dimensions CIFX 70E-CCIES (from Hardware Rev. 1)
Annex 257/284
11.4.4 Front Panel CIFX 70-CCIES
Figure 103: Dimensions Front Panel CIFX 70E-CCIES
Annex 258/284

GND CIFX70E-CO-DN-DP
XXXXX
R90 8 C 4 S1
AOI L1112011
XXXX.XXX X
R212 R211
2 C 1 Hilscher GmbH
V200
R33 C12
V1
V2
D4 C113F
C14D C12B
L400
C403C
C403D
C403B
BOOT
C403
C9
45DBxx
C114C
C114D
C115C
C115D
C114B
C114E
C115B
C115E
C113D
C113E
C110D
C110C
C110E
C110B
R209
R208
R1
C113C
C113B
R413
R21
R20
R2
R3
U401 L401
C14
LWL-4 X400 C370
C404E
C113
C116C C116D
C404D C110 C116B C116E
D3 L110 C8
C404C R1S-3.305 C111 C131 C153 C132 D2
C135
R370 C404B C2
56.13
C6B
N110
C6
C404 C4
R405
C15
R110
C112
R34 25
U410 C123E
64.39
C17E C17F C18B

R111N1
SDRAM2Mx32
C411C C123D C18C
D5 C3 C1
R15 C123C R5 G1
C123B C17I
C411
C152
C150
C18A C17J C17
C411B
30.89
C18D R19 C3C

C411E C3B
C17G C20H
C411D C17H C18E
47.84
R11
R7
C154
R400 C17D
T4
C7
C17C
R402 T2 R10A
T3
C130
R403 R126 T6 R12
C133
R6 C16B C19C
R10D
R17
C20E
R404 R16 C16A R18B R 18A C15A

C15B
C14A
C14B
C18
R18D
C20G
C20B
C20A
C19A
C19B R19A
R10C
T1
R10B
C400B
T5 C19D
D1
C5B
C14C R13
C5
C16C C16 C134 C151
R100
C401B C401 C17A C17B
C15C R20A
C400
U400
R18E C10 C11
C120C
C120D
C119C
C119D
C118C
C118D
C117C
C117D
C120E
C120B
C119B
C119E
C118B
C118E
C117B
C117E
C109
11.28
T11 T12
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.00
Figure 104: Dimensions CIFX 70E-DP and CIFX 70E-DP\MR (Hardware Rev.1)
Annex 259/284
Figure 105: Blende für CIFX 70E-DP, CIFX 70E-DP\MR
Annex 260/284

XXXXX
R90 8 C 4 S1
AOI L1112011
XXXX.XXX X
R212 R211
2 C 1 Hilscher GmbH
V200
R33 C12
V1
V2
D4 C113F
C14D C12B
L400
C403C
C403D
C403B
BOOT
C403
C9
45DBxx
C114C
C114D
C115C
C115D
C114B
C114E
C115B
C115E
C113D
C110D
C110C
C113E
C110E
C110B
R209
R208
R1
C113C
C113B
R413
R21
R20
R2
R3
U401 L401
C14
LWL-4 X400 C404E
C113
C116C C116D
C370 C404D C110 C116B C116E
D3 L110 C8
C404C
C111 C131 C153 C132 D2
R1S-3.305 C135
R370 C404B C2
56.13
C6B
N110
C6
C404 C4
V361 C15
R110
C112
R34 25
U410 C123E
64.39
C17E C17F C18B

R111N1
SDRAM2Mx32
C411C C123D C18C
D5 C3 C1
R15 C123C R5 G1
C362 C123B C17I
C411
C152
C150
C17J C17
82C
C411B R360 C18A

30.89
C18D R19 C3C

C411E U360 C17G
C3B
C20H
C411D C17H C18E
47.84
N360
HCPL
R11
R7
0601
C154
T4 C17D
R406 R363
C7
C17C
T2 R10A
T3
C130
R126 T6 R12
C133
C367
C360
U361 R6 C16B C20E C19C
R10D
R17
R16 C16A R18B R18A C15A C14A C18 C20G C19A
R19A
R361
C15B C14B R18D C20B C19B
C20A
R10C
R364 T1
HCPL
R10B
060L
C400B
T5 C19D
D1
C5B
C14C R13
C5
C16C C16 C134 C151
R100
C401B C17A C17B
C15C R20A
C400
C401 U400
R18E C10 C11
C120C
C120D
C119C
C119D
C118C
C118D
C117C
C117D
C120E
C120B
C119B
C119E
C118B
C118E
C117B
C117E
C109
11.28
T11 T12
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.00
Figure 106: Dimensions CIFX 70E-CO and CIFX 70E-CO\MR (Hardware Rev.1)
Annex 261/284
11.4.7 Front Panel CIFX 70E-CO, CIFX 70E-CO\MR
Figure 107: Dimensions Front Panel für CIFX 70E-CO, CIFX 70E-CO\MR
Annex 262/284

XXXXX
R90 8 C 4 S1
C99
AOI L1112011
XXXX.XXX X
R212 R211
2 C 1 Hilscher GmbH
V200
R33 C12
V1
V2
D4 C113F
C14D C12B
L400
C403C
C403D
C403B
C403
BOOT C9
45DBxx
C114C
C114D
C115C
C115D
C114B
C114E
C115B
C115E
C113D
C110D
C110C
C113E
C110E
C110B
R209
R208
R1
C113C
C113B
R413
R21
R20
R2
R3
U401 L401
C14
LWL-4 C404E
C113
C116C C116D
C370 C404D C110 C116B C116E
D3 L110 C8
C404C
C111 C131 C153 C132 D2
R1S-3.305 C135
R370 C404B C2
56.13
C6B
N110
C6
C404 C4
V361 C15 R34 25
1
C112
U410 R110
64.39
C123E C17E C17F C18B R111N1
SDRAM2Mx32
C411C C123D C18C
D5 C3 C1
R15 C123C R5 G1
C362 C123B C17I
2
C411
C152
C150
82C
C18A C17J C17

C411B R360 R19 C3C
C18D
C411E U360 C17G
C3B
27.40
C363 C20H
C411D C17H C18E
47.84
N360
HCPL
R11
R7
0601
C154
3
C17D
R363 T4
C7
N361
C17C
T2 R10A
T3
C130
R126 T6 R12
C133
C367
C360
U361 R6 C16B C19C
R10D
R17
4
C20E
R16 C16A R18B R18A C15A C14A C18
R18D C20G C19A
R19A
R361
C15B C14B C20B C19B
C20A
R10C
R369 R364 T1
HCPL
060L R10B
C400B
T5 C19D
D1
C5B
C14C R13
C5
C16C C16 C134 C151
R100
C401B
5
C17A C17B
C15C R20A
C400
C401 U400
R18E C10 C11
C361
C371
C120C
C120D
C119C
C119D
C118C
C118D
C117C
C117D
C120E
C120B
C119B
C119E
C118B
C118E
C117B
C117E
R371 R365
R366 U362
R362
C109
11.41
T11 T12
B1 B18
15.01
33.35
41.35
45.01
56.18
58.12
65.30
119.00
Figure 108: Dimensions CIFX 70E-DN and CIFX 70E-DN\MR (Hardware Rev.1)
Annex 263/284
11.4.9 Front Panel CIFX 70E-DN, CIFX 70E-DN\MR
Figure 109: Dimensions Front Panel CIFX 70E-DN, CIFX 70E-DN\MR
Annex 264/284
11.5 Notes on earlier Hardeware Revisions

11.5.1 Failure in 10 MBit/s Half Duplex Mode and Workaround
The note is only valid for the PC cards cifX up to serial numbers indicated:
PC Cars cifX Part No up to Serial Number
CIFX 50-RE 1250.100 22414
CIFX 50E-RE 1251.100 20167
Failure of the Network Communication

 Do not operate hardware with the communication controllers netX 50,
netX100 or netX 500 with the protocols Ethernet TCP/UDP/IP,
EtherNet/IP or Modbus TCP at 10 MBit/s in half-duplex mode, otherwise
failure of the network communication can occur.
 Use only switches or 10/100 MBit/s dual-speed hubs and ensure that
the network operates at 100 MBit/s and in full-duplex mode.
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
Annex 265/284
11.6 Disposal of Waste Electronic Equipment

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.
11.7 References
[1] THE CIP NETWORKS LIBRARY, Volume 6, CompoNet Adaptation of CIP,
Edition 1.4 November 2008
[2] Data sheet MOD JACK – MJIM:
https://www.erni-x-press.com/de/downloads/zeichnungen/203313.pdf
[3] Design - Specification for VARAN Rev. 0.76, section 5.1.4 VARAN Splitter
References Protocol API Manuals
• AS-Interface Master Protocol API Manual, Revision 5, Hilscher GmbH 2016
• CANopen Master Protocol API Manual, Revision 16, Hilscher GmbH 2016
• CANopen Slave Protocol API Manual (V3), Revision 7, Hilscher GmbH 2016
• CC-Link IE Field Slave Protocol API, Revision 1, Hilscher GmbH 2018
• CC-Link IE Field-Basic Slave Protocol API, Revision 1, Hilscher GmbH 2018
• CC-Link Slave Protocol API Manual, Revision 11, Hilscher GmbH 2017
• DeviceNet Master Protocol API Manual, Revision 11, Hilscher GmbH 2016
• DeviceNet Slave Protocol API Manual, Revision 15, Hilscher GmbH 2016
• EtherCAT Master Protocol API Manual (V4), Revision 5, Hilscher GmbH 2017
• EtherCAT Master Protocol API Manual (V3), Revision 5, Hilscher GmbH 2013
• EtherCAT Slave Protocol API Manual (V4), Revision 10, Hilscher GmbH 2017
• EtherCAT Slave Protocol API Manual (V2), Revision 21, Hilscher GmbH 2013
• EtherNetIP Scanner Protocol API Manual, Revision 14, Hilscher GmbH 2017
• EtherNetIP Adapter Protocol API Manual, Revision 20, Hilscher GmbH 2017
• Open Modbus/TCP Protocol API Manual, Revision 10, Hilscher GmbH 2016
• POWERLINK-Controlled-Node/Slave Protocol API Manual (V3), Revision 8, Hilscher GmbH 2018
• POWERLINK-Controlled-Node/Slave Protocol API Manual (V2), Revision 13, Hilscher GmbH 2015
• PROFIBUS DP-Master Protocol API Manual, Revision 22, Hilscher GmbH 2017
• PROFIBUS DP-Slave Protocol API Manual, Revision 19, Hilscher GmbH 2017
• PROFIBUS MPI Protocol API Manual, Revision 4, Hilscher GmbH 2011
• PROFINET IO-Controller Protocol API Manual (V3), Revision 7, Hilscher GmbH 2017
• PROFINET IO-Controller Protocol API Manual (V2), Revision 19, Hilscher GmbH 2015
• PROFINET IO-Device Protocol API Manual (V4), Revision 2, Hilscher GmbH 2018
• PROFINET IO-Device Protocol API Manual (V3), Revision18, Hilscher GmbH 2018
• Sercos Master Protocol API Manual, Revision 11, Hilscher GmbH 2013
• Sercos Slave Protocol API Manual (V3), Revision 17, Hilscher GmbH 2017
• VARAN Client Protocol API Manual, Revision 3, Hilscher GmbH 2013
Table 165: References Protocol API Manuals
Annex 266/284
References referring to the safety issues are listed separately in section
References Safety on page 35. References referring to the Standard Bus
Specifications for PCI and PCI Express are listed separately References
PCI Specifications on page 145.
11.8 EtherCAT Summary over Vendor ID, Conformance test,

Membership and Network Logo
11.8.1 Vendor ID
The communication interface product is shipped with Hilscher’s secondary vendor ID, which
has to be replaced by the Vendor ID of the company shipping end products with the
integrated communication interface. End Users or Integrators may use the communication
interface product without further modification if they re-distribute the interface product (e.g.
PCI Interface card products) only as part of a machine or machine line or as spare part for
such a machine. In case of questions, contact Hilscher and/or your nearest ETG
representative. The ETG Vendor-ID policies apply.
11.8.2 Conformance
EtherCAT Devices have to conform to the EtherCAT specifications. The EtherCAT
Conformance Test Policies apply, which can be obtained from the EtherCAT Technology
Group (ETG, www.ethercat.org).
Hilscher range of embedded network interface products are conformance tested for network
compliance. This simplifies conformance testing of the end product and can be used as a
reference for the end product as a statement of network conformance (when used with
standard operational settings). It must however be clearly stated in the product
documentation that this applies to the network interface and not to the complete product.
Conformance Certificates can be obtained by passing the conformance test in an official

EtherCAT Conformance Test lab. Conformance Certificates are not mandatory, but may be
required by the end user.
11.8.3 Certified Product vs. Certified Network Interface

The EtherCAT implementation may in certain cases allow one to modify the behavior of the
EtherCAT network interface device in ways which are not in line with EtherCAT
conformance requirements. For example, certain communication parameters are set by a
software stack, in which case the actual software implementation in the device application
determines whether or not the network interface can pass the EtherCAT conformance test.
In such cases, conformance test of the end product must be passed to ensure that the
implementation does not affect network compliance.
Generally, implementations of this kind require in-depth knowledge in the operating

fundamentals of EtherCAT. To find out whether or not a certain type of implementation can
pass conformance testing and requires such testing, contact EtherCAT Technology Group
(“ETG”, www.ethercat.org) and/or your nearest EtherCAT conformance test centre.
EtherCAT may allow the combination of an untested end product with a conformant network
interface. Although this may in some cases make it possible to sell the end product without
having to perform network conformance tests, this approach is generally not endorsed by
Hilscher. In case of questions, contact Hilscher and/or your nearest ETG representative.
Annex 267/284
11.8.4 Membership and Network Logo
Generally, membership in the network organization and a valid Vendor-ID are prerequisites
in order to be able to test the end product for conformance. This also applies to the use of
the EtherCAT name and logo, which is covered by the ETG marking rules.
Vendor ID Policy accepted by ETG Board of Directors, November 5, 2008
Annex 268/284
11.9 List of Figures

Figure 1: System Overview cifX to update Firmware, Driver and Software 57
Figure 2: CIFX 50-RE* (from hardware rev. 3) 58
Figure 3: CIFX 50E-RE* (from hardware rev. 4), CIFX 50E-RE\ET* (from hardware rev. 1) 58
Figure 4: Front Plate for CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET 59
Figure 5: CIFX 50E-CCIES* (Hardware revision 1) 60
Figure 6: Front Plate for CIFX 50E-CCIES 61
Figure 7: CIFX 50-DP (hardware revision 5)* 62
Figure 8: CIFX 50E-DP (hardware revision 5)* 62
Figure 9: Front Plate CIFX 50-DP or CIFX 50E-DP 63
Figure 10: CIFX 50-2DP (Hardware Revision 3) 64
Figure 11: CIFX 50E-2DP (Hardware Revision 1) 64
Figure 12: Front Plate CIFX 50-2DP, CIFX 50E-2DP 65
Figure 13: CIFX 50-2DP\CO (Hardware Revision 2) 66
Figure 14: CIFX 50E-2DP\CO (Hardware Revision 1) 66
Figure 15: Front Plate CIFX 50-2DP\CO, CIFX 50E-2DP\CO 67
Figure 16: CIFX 50-2DP\DN (Hardware Revision 1) 68
Figure 17: CIFX 50E-2DP\DN (Hardware Revision 1) 68
Figure 18: Front Plate CIFX 50-2DP\DN, CIFX 50E-2DP\DN 69
Figure 19: CIFX 50-CO (hardware revision 5) 70
Figure 20: CIFX 50E-CO (from hardware revision 4) 70
Figure 21: Front Plate for CIFX 50-CO or CIFX 50E-CO 71
Figure 22: CIFX 50-2CO (Hardware Revision 2) 72
Figure 23: CIFX 50E-2CO (Hardware Revision 1) 72
Figure 24: Front Plate CIFX 50-2CO, CIFX 50E-2CO 73
Figure 25: CIFX 50-2 CO\DN (Hardware Revision 1) 74
Figure 26: CIFX 50E-2 CO\DN (Hardware Revision 1) 74
Figure 27: Front Plate CIFX 50-2CO\DN, CIFX 50E-2 CO\DN 75
Figure 28: CIFX 50-DN (hardware revision 5) 76
Figure 29: CIFX 50E-DN (from hardware revision 4) 76
Figure 30: Front Plate CIFX 50-DN or CIFX 50E-DN 77
Figure 31: CIFX 50-2DN (Hardware Revision 2) 78
Figure 32: CIFX 50E-2DN (Hardware Revision 1) 78
Figure 33: Front Plate CIFX 50-2DN, CIFX 50E-2DN 79
Figure 34: CIFX 50-2ASM (hardware revision 2) 80
Figure 35: CIFX 50E-2ASM (from hardware revision 2) 80
Figure 36: Front Plate CIFX 50-2ASM 81
Figure 37: CIFX 50-CC (hardware revision 2)* 82
Figure 38: CIFX 50E-CC (hardware revision 4)* 82
Figure 39: Front Plate CIFX 50-CC or CIFX 50E-CC 83
Figure 40: CIFX 70E-RE* (Hardware revision 1) 84
Figure 41: CIFX 70E-RE\MR* (Hardware revision 1) 84
Figure 42: Front Plate for CIFX 70E-RE, CIFX 70E-RE\MR 85
Figure 43: CIFX 70E-CCIES* (Hardware revision 1) 86
Figure 44: Front Plate for CIFX 70E-CCIES 87
Figure 45: CIFX 100EH-RE\CUBE* 88
Figure 46: Front Plate CIFX 100EH-RE\CUBE 88
Figure 47: CIFX 70E-DP (Hardware revision 1) 89
Figure 48: CIFX 70E-DP\MR (Hardware revision 1) 89
Figure 49: Front Plate CIFX 70E-DP, CIFX 70E-DP\MR 90
Figure 50: CIFX 70E-CO (Hardware revision 1) 91
Figure 51: CIFX 70E-CO\MR (Hardware revision 1) 91
Annex 269/284
Figure 52: Front Plate CIFX 70E-CO, CIFX 70E-CO\MR 92
Figure 53: CIFX 70E-DN (Hardware revision 1) 93
Figure 54: CIFX 70E-DN\MR (Hardware revision 1) 93
Figure 55: Front Plate CIFX 70E-DN, CIFX 70E-DN\MR 94
Figure 56: Front Plate Stickers for CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET 96
Figure 57: Front Plate Stickers for CIFX 70E-RE, CIFX 70E-RE\MR 98
Figure 58: Front Plate Stickers for CIFX 100EH-RE\CUBE 98
Figure 59: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX 135
Figure 60: Ethernet Pin Assignment at the RJ45 Socket (1000 MBit/s) 136
Figure 61: PROFIBUS Interface (DSub female connector, 9 pin), X400 138
Figure 62: CANopen Interface (DSub male connector, 9 pin), X400 138
Figure 63: DeviceNet Interface (CombiCon male Connector, 5 pin), X360 139
Figure 64: AS-Interface Interface (CombiCon male Connector, 2 pin) 139
Figure 65: CC-Link Interface (CombiCon male Connector, 5 pin) 140
Figure 66: Example 2D Label (mini sticker on the right) 220
Figure 67: Dimensions CIFX 50-RE (from Hardware Rev.3 221
Figure 68: Dimensions CIFX 50E-RE (from Hardware Rev.4), CIFX 50E-RE\ET (from Hardware Rev.1) 222
Figure 69: Dimensions Front Panel CIFX 50-RE, CIFX 50E-RE or CIFX 50E-RE\ET 223
Figure 70: Dimensions CIFX 50E-CCIES (from Hardware Rev.1) 224
Figure 71: Dimensions Front Panel CIFX 50E-CCIES 225
Figure 72: Dimensions CIFX 50-DP (Hardware Rev.5) 226
Figure 73: Dimensions CIFX 50E-DP (Hardware Rev.6) 227
Figure 74: Dimensions Front Panel CIFX 50-DP or CIFX 50E-DP 228
Figure 75: Dimensions CIFX 50-CO (Hardware Rev.5) 229
Figure 76: Dimensions CIFX 50E-CO (from Hardware Rev.4) 230
Figure 77: Dimensions Front Panel für CIFX 50-CO or CIFX 50E-CO 231
Figure 78: Dimensions CIFX 50-DN (Hardware Rev.5) 232
Figure 79: Dimensions CIFX 50E-DN (from Hardware Rev.4) 233
Figure 80: Dimensions Front Panel CIFX 50-DN or CIFX 50E-DN 234
Figure 81: Dimensions CIFX 50-CC (Hardware Rev.2) 235
Figure 82: Dimensions CIFX 50E-CC (from Hardware Rev.4) 236
Figure 83: Dimensions Front Panel CIFX 50-CC or CIFX 50E-CC 237
Figure 84: Dimensions CIFX 50-2DP (Hardware Rev.3) 238
Figure 85: Dimensions CIFX 50E-2DP (Hardware Rev.1) 239
Figure 86: Dimensions CIFX 50-2DP\CO (Hardware Rev.2) 240
Figure 87: Dimensions CIFX 50E-2DP\CO (Hardware Rev. 1) 241
Figure 88: Dimensions CIFX 50-2DP\DN (Hardware Rev.1) 242
Figure 89: Dimensions CIFX 50E-2DP\DN (Hardware Rev. 1) 243
Figure 90: Dimensions CIFX 50-2CO (Hardware Rev.2) 244
Figure 91: Dimensions CIFX 50E-2CO (Hardware-Rev. 1) 245
Figure 92: Dimensions CIFX 50-2CO\DN (Hardware Rev.1) 246
Figure 93: Dimensions CIFX 50E-2CO\DN (Hardware Rev. 1) 247
Figure 94: Dimensions CIFX 50-2DN (Hardware Rev.2) 248
Figure 95: Dimensions CIFX 50E-2DN (Hardware Rev. 1) 249
Figure 96: Dimensions Front Panel CIFX 50-2FB 250
Figure 97: Dimensions CIFX 50-2ASM (Hardware Rev.2) 251
Figure 98: Dimensions CIFX 50E-2ASM (from Hardware Rev.2) 252
Figure 99: Dimensions Front Panel CIFX 50-2ASM, CIFX 50E-2ASM 253
Figure 100: Dimensions CIFX 70E-RE and CIFX 70E-RE\MR (Hardware Rev.1) 254
Figure 101: Dimensions Front Panel für CIFX 70E-RE, CIFX 70E-RE\MR 255
Figure 102: Dimensions CIFX 70E-CCIES (from Hardware Rev. 1) 256
Figure 103: Dimensions Front Panel CIFX 70E-CCIES 257
Figure 104: Dimensions CIFX 70E-DP and CIFX 70E-DP\MR (Hardware Rev.1) 258
Annex 270/284
Figure 105: Blende für CIFX 70E-DP, CIFX 70E-DP\MR 259
Figure 106: Dimensions CIFX 70E-CO and CIFX 70E-CO\MR (Hardware Rev.1) 260
Figure 107: Dimensions Front Panel für CIFX 70E-CO, CIFX 70E-CO\MR 261
Figure 108: Dimensions CIFX 70E-DN and CIFX 70E-DN\MR (Hardware Rev.1) 262
Figure 109: Dimensions Front Panel CIFX 70E-DN, CIFX 70E-DN\MR 263
11.10 List of Tables

Table 1: List of Revisions 9
Table 2: Reference on Hardware PC Cards cifX 11
Table 3: Reference on Driver and Software 11
Table 4: Reference on Firmware (for 1 Channel Systems), **Outdated versions 12
Table 5: Reference on Firmware (for 2 Channel Systems) 12
Table 6: PROFINET IO-Controller Firmware V2 and V3 on the Product DVD 16
Table 7: PROFINET IO-Device Firmware Version 3.4 and 3.13, Header, GSDML and Protocol API Manual 17
Table 8: EtherCAT Master Firmware V3 and V4 on the Product DVD 18
Table 9: EtherCAT-Slave Firmware Version 2.5 and 4.7, Header, XML and Protocol API Manual 19
Table 10: POWERLINK Controlled Node Firmware V2 and V3 on the Product DVD 21
Table 11: Device Description Files for PC Cards cifX 22
Table 12: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby 28
Table 13: Signal Words 35
Table 14: Safety Signs 35
Table 15: PC Cards PCI CIFX 50-XX 36
Table 16: PC Cards PCI (2 Channels) CIFX 50-2XX, CIFX 50-2XX\XX 37
Table 17: PC Cards PCI Express CIFX 50E-XX, CIFX 70E-XX 37
Table 18: PC Cards PCI Express (2 Channels) CIFX 50E-2XX, CIFX 50E-2XX\XX 38
Table 19: Firmware Versions for the Function Slot Number (Card ID), (for 1 Channel Systems) 39
Table 20: Firmware Versions for the Function Slot Number (Card ID) (for 2 Channel Systems) 40
Table 21: Versions Driver, Bootloader and SYCON.net for Function Slot Number (Card ID) 40
Table 22: Firmware Versions for the DMA Mode (for 1 Channel Systems) 41
Table 23: Firmware Versions for the DMA Mode (for 2 Channel Systems) 42
Table 24: Versions Driver and SYCON.net for the DMA Mode 42
Table 25: Slot for the PC Cards cifX PCI, PCIe and Low Profile PCIe 43
Table 26: Requirements Power Supply and Host Interface for PC Cards cifX PCI, PCIe Low Profile PCIe 44
Table 27: Requirements to operate PC Cards cifX properly 45
Table 28: Steps for the Software and Hardware Installation, the Configuration and for the Diagnosis of a PC
Card cifX (Master and Slave) 52
Table 29: Notes for the Configuration of the Master Device 54
Table 30: Device Names in SYCON.net by Communication Protocol 56
Table 31: Assignment of the LEDs to the Channels 83
Table 32: LED Labeling depending of the loaded Firmware 96
Table 33: Fix Front Plate Sticker at the CIFX 70E-RE, CIFX 70E-RE\MR or CIFX 100EH-RE\CUBE 97
Table 34: LED Labeling depending of the loaded Firmware, CIFX 70E-RE, CIFX 70E-RE\MR 98
Table 35: Overview LEDs Real-Time Ethernet Systems 102
Table 36: LED Names 102
Table 37: Overview LEDs by Fieldbus System for 1 Channel Devices 103
Table 38: Overview LEDs by Fieldbus System for 2 Channel Devices 103
Table 39: LED Names 103
Table 40: System Status LED States 104
Table 41: LED states for the CC-Link IE Field Basic Slave 105
Table 42: LED state definitions for theCC-Link IE Field Basic Slave protocol 105
Annex 271/284
Table 43: LED states for the CC-Link IE Field Slave protocol 106
Table 44: LED Names CC-Link IE Field Slave protocol 106
Table 45: LED states for the EtherCAT Master protocol 107
Table 46: LED state definitions for the EtherCAT Master protocol 107
Table 47: LED states for the EtherCAT Master protocol 108
Table 48: LED state definitions for the EtherCAT Master protocol 109
Table 49: LED states for the EtherCAT Slave protocol 110
Table 50: LED state definitions for the EtherCAT Slave protocol 110
Table 51: LED states for the EtherNet/IP Scanner protocol 112
Table 52: LED state definitions for the EtherNet/IP Scanner protocol 112
Table 53: LED states for the EtherNet/IP Adapter protocol 114
Table 54: LED state definitions for the EtherNet/IP Adapter protocol 114
Table 55: LED states for the OpenModbusTCP protocol 115
Table 56: LED state definitions for the OpenModbusTCP protocol 115
Table 57: LED states for the POWERLINK Controlled Node protocol 116
Table 58: LED state definitions for the POWERLINK Controlled Node protocol 116
Table 59: LED states for the PROFINET IO-Controller protocol 117
Table 60: LED state definitions for the PROFINET IO-Controller protocol 117
Table 61: PROFINET IO Controller, SYS, COM0 and COM1 LEDs states 118
Table 62: PROFINET IO Controller, Ethernet LEDs states 119
Table 63: PROFINET IO Controller, LEDs states definitions 119
Table 64: LED states for the PROFINET IO-Device protocol 120
Table 65: LED state definitions for the PROFINET IO-Device protocol 120
Table 66: LED states for the Sercos Master protocol 121
Table 67: LED state definitions for the Sercos Master protocol 122
Table 68: LED state definitions for the Sercos Slave protocol 123
Table 69: LED state definitions for the Sercos Slave protocol 124
Table 70: LED-Zustände für das VARAN-Client-Protokoll 125
Table 71: Definitionen der LED-Zustände für das VARAN-Client-Protokoll 125
Table 72: LED states for the PROFIBUS DP Master protocol 126
Table 73: LED state definitions for the PROFIBUS DP Master protocol 126
Table 74: LED states for the PROFIBUS DP Slave protocol 127
Table 75: LED state definitions for the PROFIBUS DP Slave protocol 127
Table 76: LED states for the PROFIBUS MPI protocol 128
Table 77: LED state definitions for the PROFIBUS MPI protocol 128
Table 78: LED states for the CANopen Master protocol 129
Table 79: LED state definitions for the CANopen Master protocol 129
Table 80: States of the CAN LED for the CANopen Slave protocol – 1 Communication Status LED (current
Hardware Revision) 130
Table 81: LED state definitions for the CANopen Slave protocol 130
Table 82: LED states for the DeviceNet Master protocol 131
Table 83: LED state definitions for the DeviceNet Master protocol 131
Table 84: LED states for the DeviceNet Slave protocol 132
Table 85: LED state definitions for the DeviceNet Slave protocol 132
Table 86: LEDs states for the AS-Interface Master protocol 133
Table 87: LED state definitions for the AS-Interface Master protocol 133
Table 88: LED states for the CC-Link Slave protocol 134
Table 89: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX 135
Table 90: Ethernet Pin Assignment at the RJ45 Socket (1000 MBit/s) 136
Table 91: Ethernet Connection Data 137
Table 92: Use of Hubs and Switches 137
Table 93: PROFIBUS Interface, X400 138
Table 94: CANopen Interface, X400 138
Annex 272/284
Table 95: DeviceNet Interface, X360 139
Table 96: AS-Interface Interface 139
Table 97: CC-Link Interface 140
Table 98: Rotary Switch for Slot Number (Card ID), S1 141
Table 99: Rotary Switch Slot Number (Card ID) PC Cards cifX Low Profile PCI Express 142
Table 100: Pin Assignment for SYNC Connector, X51 143
Table 101: Pin Assignment for SYNC Connector, J1 143
Table 102: SYNC Connector: SYNC Signal, Connector, Max. Cable Length 144
Table 103: Meaning of the SYNC Signals for each Protocol 144
Table 104: Pin Assignment at the PCI Bus 145
Table 105: References PCI Specifications 145
Table 106: Pin Assignment for PCI Express-Bus CIFX 100EH-RE\CUBE 146
Table 107: Technical Data CIFX 50-RE 148
Table 108: Technical Data CIFX 50E-RE, CIFX 50E-RE\ET 150
Table 109: Technical Data CIFX 50E-CCIES, CIFX 70E-CCIES 152
Table 110: Technical Data CIFX 50-DP 154
Table 111: Technical Data CIFX 50E-DP 155
Table 112: Technical Data CIFX 50-CO 157
Table 113: Technical Data CIFX 50E-CO 158
Table 114: Technical Data CIFX 50-DN 160
Table 115: Technical Data CIFX 50E-DN 161
Table 116: Technical Data CIFX 50-CC 162
Table 117: Technical Data CIFX 50E-CC 164
Table 118: Technical Data CIFX 50-2DP 165
Table 119: Technical Data CIFX 50E-DP 167
Table 120: Technical Data CIFX 50-2DP\CO 169
Table 121: Technical Data CIFX 50E-2DP\CO 171
Table 122: Technical Data CIFX 50-2DP\DN 172
Table 123: Technical Data CIFX 50-2DP\DN 174
Table 124: Technical Data CIFX 50-2CO 175
Table 125: Technical Data CIFX 50E-2CO 177
Table 126: Technical Data CIFX 50-2CO\DN 178
Table 127: Technical Data CIFX 50E-2CO\DN 180
Table 128: Technical Data CIFX 50-2DN 181
Table 129: Technical Data CIFX 50E-2DN 183
Table 130: Technical Data CIFX 50-2ASM 184
Table 131: Technical Data CIFX 50E-2ASM 185
Table 132: Technical Data CIFX 70E-RE, CIFX 70E-RE\MR 187
Table 133: Technical Data CIFX 100EH-RE\CUBE 190
Table 134: Technical Data CIFX 70E-DP, CIFX 70E-DP\MR 191
Table 135: Technical Data CIFX 70E-CO, CIFX 70E-CO\MR 192
Table 136: Technical Data CIFX 70E-DN, CIFX 70E-DN\MR 194
Table 137: PCI IDs PC Cards cifX on the PCI Bus 195
Table 138: Supported / not supported PCI Bus Commands 195
Table 139: Technical data CC-Link IE Field Basic Slave protocol 196
Table 140: Technical data CC-Link IE Field Slave protocol 196
Table 141: Technical Data EtherCAT Master Protocol 197
Table 142: Technical Data EtherCAT Master Protocol 198
Table 143: Technical Data EtherCAT Slave Protocol 199
Table 144: Technical Data EtherNet/IP Scanner Protocol 200
Table 145: Technical Data EtherNet/IP Adapter Protocol 201
Table 146: Technical Data Open Modbus/TCP Protocol 202
Table 147: Technical Data POWERLINK Controlled Node Protocol 203
Annex 273/284
Table 148: Technical Data POWERLINK Controlled Node Protocol 203
Table 149: Technical Data PROFINET IO RT Controller Protocol 205
Table 150: Technical Data PROFINET IO Controller Protocol 206
Table 151: Technical Data PROFINET IO RT IRT Device Protocol 207
Table 152: Technical Data PROFINET IO RT IRT Device Protocol 208
Table 153: Technical Data Sercos Master Protocol 208
Table 154: Technical Data Sercos Slave Protocol 209
Table 155: Technical Data VARAN Client Protocol 210
Table 156: Technical Data PROFIBUS DP Master Protocol 211
Table 157: Technical Data PROFIBUS DP Slave Protocol 212
Table 158: Technical Data PROFIBUS-MPI Protocol 213
Table 159: Technical Data CANopen Master Protocol 214
Table 160: Technical Data CANopen Slave Protocol 215
Table 161: Technical Data DeviceNet Master Protocol 216
Table 162: Technical Data DeviceNet Slave Protocol 217
Table 163: Technical Data AS-Interface Master Protocol 218
Table 164: Technical Data CC-Link-Slave-Protocol 219
Table 165: References Protocol API Manuals 265
Annex 274/284
11.11 Glossary
10-Base T
Standard for communication on Ethernet over twisted pair lines with RJ45
connectors and a Baud_rate of 10 MBit/s (according to the IEEE 802.3
specification).
100-Base TX
Standard for communication on Ethernet over unshielded twisted pair lines
with RJ45 connectors and a Baud_rate of 100 MBit/s according to the IEEE
802. Specification
1000BASE-T
Standard for communication on Ethernet over unshielded twisted pair lines
with RJ45 connectors and a Baud_rate of 1 GBit/s according to the IEEE
802.3ab Specification.
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.
Boot loader
Program loading the firmware into the memory of a device in order to be
executed.
CC-Link IE Field
Communication system for industrial Ethernet designed and developed by
Mitsubishi Electric Corporation, Tokyo, Japan, for high data throughput
based on Gigabit
CC-Link IE Field Master
Station in the CC-Link IE Field network controlling parameters and
managing cyclic communication
CC-Link IE Field Slave
Station in the CC-Link IE Field network communicating with a master
station
CC-Link IE Field Basic
Communication system for Industrial Ethernet designed and developed by
Mitsubishi Electric Corporation, Tokyo, Japan, providing CC-Link IE Field
with a speed of 100 Mbit/s based on TCP/IP
Annex 275/284
CC-Link IE Field Basic Master
Station in the CC-Link IE Field Basic network controlling parameters and
managing cyclic communication
CC-Link IE Field Basic Slave
Station in the CC-Link IE Field Basic network communicating with a master
station
Ch0, Ch1 …
Within the configuration software SYCON.net the communication channels
are named ‚Ch0’, Ch1’ ….
For the Real-Time-Ethernet devices cifX, comX and netJACK and the Real-
Time Ethernet protocols used with it, the following shall apply:
‘Ch0’ in SYCON.net: Both ports of the Ethernet RJ45 connector CH0 and
CH1 are assigned always to channel 0 in SYCON.net.
‘Ch1’ in SYCON.net: Depending on the firmware channel 1 in SYCON.net
can be used as an additional communication channel.
CH0, CH1 (Ch0, Ch1)
Names for the ports of an Ethernet RJ45 socket with two Ethernet
channels.
CH0 stands for Ethernet channel 0.
CH1 stands for Ethernet channel 1.
cifX
Communication InterFace based on netX
cifX TCP/IP Server
cifX TCP Server.exe
Program for the remote diagnostics via Ethernet.
Name: cifX TCP/IP Server for SYCON.net
User Interface: TCP/IP Server for cifX
Coil
A coil is a single bit in the memory that can be accessed using Modbus:
read or write access with FC 1, 5, 15. Depending on the used Modbus
function code a single coil or several coils lying in succession can be
accessed.
CSP
electronic device data sheet, required for each CC-Link device
CSPP
(CSP+) Control and communication system profile, respectively
specification and device description file that contains and provides the
necessary data on CC-Link compatible devices for commissioning,
operation and maintenance.
Annex 276/284
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.
DHCP
Dynamic Host Configuration Protocol
This is a protocol simplifying the configuration of IP networks by
automatically assigning IP addresses.
Discrete Input
A “Discrete Input” (as defined in the Modbus terminology) is a single bit in
the memory which can be accessed using Modbus (read with FC 2).
DP
Decentral Periphery
DPM
Dual-Port Memory
EDS
Electronic Data Sheet
EDS file
A special kind of Device Description File used for example by EtherNet/IP.
ET
Extended Temperature Range (Operating Temperature)
PC cards cifX with the addition of "ET" at the end of the part name can be
used in an extended operating temperature range. Details to the operating
temperature range are given in the technical data to the respective card.
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
for real-time application, various real-time extensions have been
developed.
EtherNet/IP
Rockwell. It partly uses the CIP (Common Industrial Protocol).
Annex 277/284
EtherNet/IP Scanner
A Scanner exchanges real-time I/O data with Adapters and Scanners. This
type of node can respond to connection requests and can also initiate
connections on its own.
EtherNet/IP Adapter
An Adapter emulates functions provided by traditional rack-adapter
products. This type of node exchanges real-time I/O data with a Scanner
Class product. It does not initiate connections on its own.
Ethernet POWERLINK
B&R. It partly uses CANopen technologies.
FDL
Fieldbus Data Link defines the PROFIBUS communication on layer 2,
identical for DP and FMS
Firmware
Software running inside a device providing the basic functionality of this
device. It can be updated by a firmware download.
Full duplex
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 will be possible to transmit data even if currently data are
received. Full-duplex is the opposite of Half_duplex.
Function code
A function code (FC) is a standardized method to access, i. e. read or write
on coils (Bits) or registers via Modbus.
Modbus function codes are elements of Modbus request/reply telegrams.
GSD
Generic Station Description, Device description file
GSD file
A special kind of Device Description File used by PROFIBUS (GSD =
Generic Station Description).
GSDML
Generic Station Description Markup Language
XML based device description file.
GSDML file
A special kind of XML-based Device Description File used by PROFINET.
Annex 278/284
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
analyze the data traffic and sends received data to all connected
communication partners. A hub can be used for setting up a star topology.
Industrial Ethernet
See Real-Time Ethernet
IP
Internet Protocol.
IP belongs to the TCP/IP family of protocols and is defined in RFC791. It is
based on layer 3 of the ISO/OSI 7 layer model of networking.
It is a connectionless protocol, i.e. you do not need to open a connection to
a computer before sending an IP data packet to it. Therefore IP is not able
to guarantee that the IP data packets really arrive at the recipient. On IP
level neither the correctness of data nor the consistence and completeness
are checked.
IP defines special addressing mechanisms, see IP Address.
IP Address
Address within IP (the Internet Protocol, part of TCP/IP).
An IP address is an address identifying a device or a computer within a
network using the IP protocol. IP addresses are defined as a 32 bit number.
Usually, for ease of notation the IP address is divided into four 8 bit
numbers which are represented in decimal notation and separated by
points:
a.b.c.d
where a.b.c.d are each integer values between 0 and 255.
Example: 192.168.30.15
However, not all combinations are allowed, some are reserved for special
purposes.
The IP address 0.0.0.0 is defined as invalid.
MAC-ID
MAC = Media Access Control
Definition for Ethernet:
A MAC-ID is on delivery a unique (physical) Ethernet address of the device.
MAC-IDs are defined as a 48 bit number. Usually, for ease of notation the
MAC-ID address is divided into six 8 bit numbers which are represented in
hexadecimal notation and separated by “minus”-signs (-):
Annex 279/284
A-B-C-D-E-F
where A-B-C-D-E-F are each integer values between 0 and 255.
Example: 00-02-A2-20-91-18
Definition for DeviceNet: The MAC-ID is the network address of the device.
The network address of a device serves to distinguish itself on a DeviceNet
fieldbus system from any other device or Slave on this network. This should
be a unique number for each device. A valid MAC-ID address is within a
range of 0 to 63 and can be re-entered and changed in the MAC-ID box in
the Device Configuration Dialog.
Master
Type of device that initiates and controls the communication on the bus
Modbus Data Model
The data model distinguishes four basic types of data areas:
• Discrete Inputs (inputs) = FC 2 (Read)
• coils (outputs) = FC 1, 5, 15 (Write and Read back)
• Input register (input data) = FC 4 (Read)
• Holding register (output data) = FC 3, 6, 16, 23 (Write and Read back).
It should be noted, however, that depending on the device manufacturer
and device type:
• the data area in the device may be present or not,
• and two data areas can be combined into one data region. For example,
discrete inputs and input registers can be a common data area, which can
be accessed with read-FC 2 and FC 4.
• Further FC 1 and FC 3 are used instead of reading back the inputs to read
the outputs.
MPI
Multi Point Interface
The MPI is a proprietary interface of the SIMATIC® S7® series of PLCs. It is
compatible to PROFIBUS and based on RS-485. It usually works with a
transmission rate of 187.5 kBaud.
netX
networX on chip, Hilscher network communication controllers
netX Configuration Tool
The netX Configuration Tool allows users to operate cifX or netX based
devices in different networks. Its graphical user interface serves as a
configuration tool for the installation, configuration and diagnosis of the
devices.
Object Dictionary
An object dictionary is a storage area for device parameter data structures.
It is accessed in standardized manner.
Annex 280/284
Open Modbus/TCP
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.
PCB
Printed Circuit Board, (printed = machine-made) circuit board
PCIe
Abbreviation for PCI Express

PC Card cifX
Communication Interfaces of the cifX product family of Hilscher on the
basis of the communication controller netX 100:
for the Real-Time Ethernet systems and for the fieldbus systems
 CC-Link IE Field  PROFIBUS DP
 CC-Link IE Field Basic  PROFIBUS MPI
 EtherCAT  CANopen
 EtherNet/IP  DeviceNet
 Open-Modbus/TCP  AS-Interface
 POWERLINK  CompoNet
 PROFINET IO  CC-Link
 Sercos
 VARAN
as Communication Interface netX with PCI Bus
 PCI (CIFX 50),
 PCI Express (CIFX 50E),
 Low Profile PCI Express (CIFX 70E, CIFX 100EH-RE\CUBE*),
 Compact PCI (CIFX80),
 Mini PCI (CIFX90),
 Mini PCI Express (CIFX 90E),
 PCI-104 (CIFX 104C)
and as Communication Interface netX with ISA Bus
 PC/104 (CIFX 104).
*only Real-Time Ethernet
PROFINET
A communication system for Industrial Ethernet designed and developed by
PROFIBUS & PROFINET International (PI). It uses some mechanisms
similar to those of the PROFIBUS field bus.
PROFINET IO Controller
A PROFINET control unit responsible for the defined run-up of an I/O
subsystem and the cyclic or acyclic data exchange.
Annex 281/284
PROFINET IO Device
A PROFINET field device that cyclically receives output data from its IO-
Controller and responds with its input data.
RE
RE stands for Real-Time Ethernet
Real-Time Ethernet
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
• CC-Link IE Field
• CC-Link IE Field Basic
• EtherCAT
• EtherNet/IP
• Ethernet POWERLINK
• Open Modbus/TCP
• PROFINET
• Sercos
• VARAN
Register
A register 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.
Depending on the used Modbus function code a single register or multiple
registers sequentially located can be accessed.
Modbus differs Input Registers (FC 4) and Holding Registers (FC 3, 6, 16,
23).
Remanent
Remanent memory holds its data even after power-off, for instance flash
memory is remanent. It is also called non-volatile memory.
RJ45
A connector type often used for Ethernet connection. It has been
standardized by the Federal Communications Commission of the USA
(FCC).
Sercos
Bosch-Rexroth and supported by Sercos International.
Slave
Type of device that is configured by the Master and which then performs
the communication
Annex 282/284
Switch
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.
SYCON.net
FDT/DTM based configuration and diagnosis software by Hilscher
SYNC
Synchronization cycle of the master
TCP/IP
Transport Control Protocol/Internet Protocol connection-orientated, secure
transfer protocol as basis for the Internet-protocols
UCMM
Unconnected Message Manager
VARAN
Versatile Automation Random Access Network
A communication system for industrial Ethernet based on the DIAS-BUS
developed by Sigmatek. The system is supported by the VARAN-BUS-
NUTZERORGANISATION (VNO).
Watchdog Timer
A watchdog timer provides an internal supervision mechanism of a
communication system. It supervises that an important event happens
within a given timeframe (the watchdog time which can be adjusted
accordingly, for instance by a parameter in the warmstart message) and
causes an alarm otherwise (usually this is accomplished by changing the
operational state of the communication system to a more safe state).
X1, X2, X3, X4 …
serve as position names on the circuit board but can also have other or
extended meanings
X1, X2
(names on the front panel) ... serve for PC cards cifX PCI and PCI Express
with 2 channels to identify the respective communication channel:
X1 stands for fieldbus 1 (channel X1; in SYCON.net assigned to Ch0).
X2 stands for fieldbus 2 (channel X2; in SYCON.net assigned to Ch1).
XDD file
A special kind of Device Description file used by Ethernet POWERLINK.
XML
XML means Extended Markup Language. It is a symbolic language for
structuring data systematically. XML is standard maintained by the W3C
Annex 283/284
(World-wide web consortium). Device Description Files often use XML-
based formats for storing the device-related data appropriately.
Annex 284/284
11.12 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: info@hilscher.com
Support
Phone: +49 (0) 6190 9907-99
E-Mail: de.support@hilscher.com
Subsidiaries
China Japan
Hilscher Systemautomation (Shanghai) Co. Ltd. Hilscher Japan KK
200010 Shanghai Tokyo, 160-0022
Phone: +86 (0) 21-6355-5161 Phone: +81 (0) 3-5362-0521
E-Mail: info@hilscher.cn E-Mail: info@hilscher.jp
Support Support
Phone: +86 (0) 21-6355-5161 Phone: +81 (0) 3-5362-0521
E-Mail: cn.support@hilscher.com E-Mail: jp.support@hilscher.com
France Korea
Hilscher France S.a.r.l. Hilscher Korea Inc.
69500 Bron Seongnam, Gyeonggi, 463-400
Phone: +33 (0) 4 72 37 98 40 Phone: +82 (0) 31-789-3715
E-Mail: info@hilscher.fr E-Mail: info@hilscher.kr
Support
Phone: +33 (0) 4 72 37 98 40 Switzerland
E-Mail: fr.support@hilscher.com Hilscher Swiss GmbH
4500 Solothurn
India Phone: +41 (0) 32 623 6633
Hilscher India Pvt. Ltd. E-Mail: info@hilscher.ch
Pune, Delhi, Mumbai Support
Phone: +91 8888 750 777 Phone: +49 (0) 6190 9907-99
E-Mail: info@hilscher.in E-Mail: ch.support@hilscher.com
Italy USA
Hilscher Italia S.r.l. Hilscher North America, Inc.
20090 Vimodrone (MI) Lisle, IL 60532
Phone: +39 02 25007068 Phone: +1 630-505-5301
E-Mail: info@hilscher.it E-Mail: info@hilscher.us
Support Support
Phone: +39 02 25007068 Phone: +1 630-505-5301
E-Mail: it.support@hilscher.com E-Mail: us.support@hilscher.com

PC Cards CIFX 50 50E 70E 100EH UM 53 EN

Uploaded by

Copyright:

Available Formats

PC Cards CIFX 50 50E 70E 100EH UM 53 EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PC Cards CIFX 50 50E 70E 100EH UM 53 EN

Uploaded by

Copyright:

Available Formats

User Manual

Installation, Operation and Hardware Description

Hilscher Gesellschaft für Systemautomation mbH

3 DESCRIPTIONS AND REQUIREMENTS ................................................................. 36

4 GETTING STARTED ................................................................................................. 47

5 DEVICE DRAWINGS ................................................................................................ 58

6 HARDWARE INSTALLATION AND UNINSTALLING ............................................... 95

7 TROUBLESHOOTING ............................................................................................ 101

8 LED DESCRIPTIONS.............................................................................................. 102

10 TECHNICAL DATA ................................................................................................. 147

11 ANNEX .................................................................................................................... 220

for the Real-Time Ethernet systems: for the fieldbus systems:

1.1.1 List of Revisions

1.1.2.1 Hardware: PC Cards cifX

1.1.2.2 Driver and Software

PC Cards and PCI Express with one Channel:

***Important! Use the PC cards CIFX 50E-CCIES or CIFX 70E-CCIES

PC Cards PCI and PCI Express with two Channels:

1.1.3 Conventions in this Manual

Notes, operation instructions and results of operation steps are marked as

Important: <important note you must follow to avoid malfunction>

Note: <general note>

<note, where to find further information>

1.1.4 Used Terminology

For further terminology to the PC cards cifX, its installation, configuration

1.2 Contents of the Product DVD

On the Communication Solutions DVD you will find these installation

1.2.1 Installation Guide, Documentation Overview

1.2.2 What's New

1.2.3 Important Changes

1.2.3.1 DeviceNet Master - SYCON.net and Firmware

1.2.3.2 PROFINET IO-Controller Firmware Versions V2 and V3

1. Customize your application program according to the Migration Guide

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

On the Communication Solutions DVD, files and manuals referring to

1.2.3.3 PROFINET IO-Device Firmware Versions V3.4 and V3.13

1. Customize your application program according to the Migration Guide

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

2. Adjust the configuration of your PROFINET IO Controller device. Use

1.2.3.4 EtherCAT Master Firmware Versions V3 and V4

1.2.3.5 EtherCAT Slave Firmware Versions V2.5 and V4.7

1. Customize your application program according to the Migration Guide

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

1.2.3.6 EtherCAT Slave Firmware Version V4.7

1.2.3.7 POWERLINK Controlled Node Firmware Versions V2 and V3

1.2.4 Device Description Files PC Cards cifX

EtherNet/IP Adapter (Slave) HILSCHER CIFX-RE EIS V1.1.EDS

1.3 Legal Notes

Costs of support, maintenance, customization and product care

1.4 Registered Trademarks

1.4.1 EtherCAT Disclaimer

To get details and restrictions regarding using the EtherCAT technology

1.5 Obligation to read and understand the Manual

1.6.1 License Note about VARAN Client

2.2 Intended Use

2.3 Personnel Qualification

2.4 Safety Instructions

2.4.1 Electrical Shock Hazard

Reference Safety [S2]