PC Cards Cifx 104 Um 54 en

User Manual
PC Cards cifX PC/104 (CIFX 104)
Installation, Operation and Hardware Description
Hilscher Gesellschaft für Systemautomation mbH

www.hilscher.com
DOC120206UM54EN | Revision 54 | English | 2022-03 | Released | Public
Table of Contents 2/200
Table of Contents
1 INTRODUCTION ......................................................................................................... 8
1.1 About the User Manual ...............................................................................................8
1.2 List of Revisions ..........................................................................................................9
1.3 Obligation to read and understand the Manual ...........................................................9
2 DESCRIPTIONS AND REQUIREMENTS ................................................................. 10

2.1 Description ................................................................................................................10
2.2 PC Cards cifX with integrated Interfaces ..................................................................11
2.2.1 PC Cards PC/104: CIFX 104-XX, CIFX 104-XX-R ............................................ 11
2.3 PC Cards cifX with AIFX detached Network Interfaces ............................................11
2.3.1 The Label „\F“ in the Device Name .................................................................... 11
2.3.2 PC Cards PC/104: CIFX 104-XX\F und Variants ............................................... 12
2.3.3 AIFX detached Network Interfaces..................................................................... 13
2.4 Contents of the Product DVD ...................................................................................14
2.4.1 Installation Guide, Documentation Overview ..................................................... 14
2.4.2 What's New......................................................................................................... 14
2.4.3 Important Changes ............................................................................................. 15
2.4.4 Device Description Files cifX .............................................................................. 16
2.5 Revision or version status of hardware and software ...............................................16
2.5.1 Hardware: PC Cards cifX ................................................................................... 17
2.5.2 Hardware: Product Components for PC Cards cifX ........................................... 17
2.5.3 Driver and Software ............................................................................................ 17
2.5.4 Firmware ............................................................................................................. 18
2.6 Device Label with Barcode .......................................................................................19
3 DEVICE DRAWINGS ................................................................................................ 20

3.1 PC-Karten cifX PC/104 .............................................................................................20
3.1.1 CIFX 104-RE ...................................................................................................... 20
3.1.2 CIFX 104-RE-R .................................................................................................. 21
3.1.3 CIFX 104-RE\F ................................................................................................... 22
3.1.4 CIFX 104-RE-R\F ............................................................................................... 23
3.1.5 CIFX 104-DP ...................................................................................................... 24
3.1.6 CIFX 104-DP-R .................................................................................................. 25
3.1.7 CIFX 104-CO ...................................................................................................... 26
3.1.8 CIFX 104-CO-R .................................................................................................. 27
3.1.9 CIFX 104-DN ...................................................................................................... 28
3.1.10 CIFX 104-DN-R .................................................................................................. 29
3.1.11 CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F .................. 30
3.1.12 CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F ................................. 30
3.1.13 Reverse Side CIFX 104-XX (all Basic Cards and Variants) ............................... 31
3.2 AIFX detached Network Interfaces ...........................................................................32
3.2.1 Ethernet - AIFX-RE............................................................................................. 32
PC Cards cifX PC/104 | Installation, Operation and Hardware Description

DOC120206UM54EN | Revision 54 | English | 2022-03 | Released | Public © Hilscher, 2008-2022
3.2.2 Ethernet - AIFX-RE\M12 .................................................................................... 33
3.2.3 PROFIBUS - AIFX-DP ........................................................................................ 34
3.2.4 CANopen - AIFX-CO .......................................................................................... 35
3.2.5 DeviceNet - AIFX-DN ......................................................................................... 36
3.2.6 CC-Link - AIFX-CC ............................................................................................. 37
3.2.7 Diagnostic - AIFX-DIAG ..................................................................................... 38
4 SAFETY .................................................................................................................... 39
4.1 General Note ............................................................................................................39
4.2 Intended Use ............................................................................................................39
4.3 Personnel Qualification .............................................................................................40
4.4 Safety Instructions ....................................................................................................40
4.4.1 Hazardous Voltage, electric Shock .................................................................... 40
4.4.2 Communication Stop during Firmware Update or Configuration Download ...... 41
4.4.3 Mismatching System Configuration .................................................................... 41
4.5 Property Damage ......................................................................................................42
4.5.1 Exceeding permissible Supply Voltage .............................................................. 42
4.5.2 Exceeding permissible Signaling Voltage .......................................................... 42
4.5.3 Electrostatic sensitive Devices ........................................................................... 43
4.5.4 Power Disconnect while downloading Firmware or Configuration ..................... 44
4.5.5 Exceeding the maximum Number of allowed Write/Delete Accesses ............... 44
4.5.6 Invalid Firmware ................................................................................................. 45
4.5.7 Information and Data Security ............................................................................ 45
4.6 Warnings ...................................................................................................................46
5 REQUIREMENTS ..................................................................................................... 48
5.1 System Requirements ..............................................................................................48
5.1.1 Slot for the PC Cards cifX PC/104 ..................................................................... 48
5.1.2 Power Supply and Host Interface ....................................................................... 48
5.1.3 Panel Cutout for Installing AIFX ......................................................................... 49
5.1.4 System Requirements cifX PC/104 (ISA) ........................................................... 50
5.1.5 AIFX-RE\M12: Max. permissible Current per external LED ............................... 50
5.2 Requirements for Operation of the PC Cards cifX ....................................................51
5.3 Prerequisites for Certification ....................................................................................52
5.3.1 PROFINET IO Certification for IRT and SYNC0 Signal ..................................... 52
6 INSTALLATION, COMMISSIONING AND UNINSTALLING...................................... 53

6.1 Overview an Installation and Configuration ..............................................................54
6.2 cifX PC/104: Set Starting Address and Interrupt ......................................................58
6.3 Installing PC Cards cifX PC/104 (PC/104 Modules) .................................................60
6.4 Notes for the Configuration of the Master Device .....................................................64
6.5 Device Names in SYCON.net ...................................................................................65
6.6 Update for Firmware, Driver and Software ...............................................................66
6.7 Instructions for Problem Solving ...............................................................................67
6.8 Note on Exchange Service (Replacement Case) .....................................................68
6.9 Uninstalling PC Cards cifX PC/104 ...........................................................................68
6.10 Disposal of Waste Electronic Equipment ..................................................................69
7 DIAGNOSIS WITH LEDS .......................................................................................... 70

7.1 Overview LEDs Real-Time Ethernet Systems ..........................................................70
7.2 Overview LEDs Fieldbus Systems ............................................................................71
7.3 System LED ..............................................................................................................72
7.4 Power On LED ..........................................................................................................72
7.5 CC-Link IE Field Basic Slave ....................................................................................73
7.6 EtherCAT Master ......................................................................................................74
7.7 EtherCAT Slave ........................................................................................................76
7.8 EtherNet/IP Scanner (Master) ..................................................................................77
7.9 EtherNet/IP Adapter (Slave) .....................................................................................79
7.10 Open Modbus/TCP ...................................................................................................81
7.11 POWERLINK-Controlled-Node/Slave .......................................................................82
7.12 PROFINET IO Controller ..........................................................................................83
7.13 PROFINET IO-Device ...............................................................................................85
7.14 Sercos Master ...........................................................................................................86
7.15 Sercos Slave .............................................................................................................88
7.16 VARAN Client (Slave) ...............................................................................................90
7.17 PROFIBUS DP Master .............................................................................................91
7.17.1 1 Communication Status LED ............................................................................ 91
7.17.2 2 Communication Status LEDs .......................................................................... 92
7.18 PROFIBUS DP Slave ...............................................................................................93
7.19 PROFIBUS MPI Device ............................................................................................95
7.20 CANopen Master ......................................................................................................97
7.21 CANopen Slave ........................................................................................................99
7.21.2 2 Communication Status LEDs ........................................................................100
7.22 DeviceNet Master ...................................................................................................101
7.23 DeviceNet Slave .....................................................................................................102
7.24 CC-Link Slave .........................................................................................................103
8 DEVICE CONNECTIONS AND SWITCHES ........................................................... 104

8.1 Ethernet Interface ...................................................................................................104
8.1.1 Ethernet Pin Assignment at the RJ45 Socket ..................................................104

8.1.2 Ethernet Pin Assignment at the M12 Socket....................................................105
8.1.3 Ethernet Connection Data ................................................................................106
8.1.4 Use of Hubs and Switches ...............................................................................106
8.2 PROFIBUS Interface ..............................................................................................107
8.3 CANopen Interface .................................................................................................107
8.4 DeviceNet Interface ................................................................................................108
8.5 CC-Link Interface ....................................................................................................108
8.6 Mini-B USB Connector (5 Pin) ................................................................................109
8.7 Rotary Switch Device Address ...............................................................................109
8.8 Cable Connector .....................................................................................................110
8.8.1 Pin Assignment for Cable Connector Ethernet X4 or X304 .............................110
8.8.2 Pin Assignment for Cable Connector Fieldbus X3, X304, X4 ..........................111
8.8.3 Pin Assignment for Cable Connector DIAG .....................................................111
8.8.4 Pin Assignment Cable Connector Ethernet X1, AIFX-RE ................................112
8.8.5 Pin Assignment Cable Connector X2, AIFX-RE\M12.......................................113
8.8.6 Pin Assignment Cable Connector LED Signals X3, AIFX-RE\M12..................114
8.8.7 Pin Assignment Cable Connector Fieldbus X1, AIFX-DP ................................115
8.8.8 Pin Assignment Cable Connector Fieldbus X1, AIFX-CO................................115
8.8.9 Pin Assignment Cable Connector Fieldbus X1, AIFX-DN ................................116
8.8.10 Pin Assignment Cable Connector Fieldbus X1, AIFX-CC ................................116
8.9 Cable for detached Network Interfaces AIFX .........................................................117
8.9.1 Cable for AIFX-RE or AIFX-RE\M12 ................................................................117
8.9.2 Optional Cable Length 30 cm for PC-cards cifX with AIFX-DP, AIFX-CO or
AIFX-DN ...........................................................................................................117
8.10 SYNC Connector (Pin-Assignment, Hardware/Firmware) ......................................118
8.10.1 Pin Assignment SYNC Connector, X51 (CIFX 80 90 104C) ............................118
8.10.2 Items on Hardware ...........................................................................................118
8.10.3 Items on Firmware ............................................................................................118
8.11 Pin Assignment at the PC/104 Bus .........................................................................119
8.11.1 Overview...........................................................................................................119
8.11.2 Pin Assignment for PC/104 Bus .......................................................................120
9 TECHNICAL DATA ................................................................................................. 122

9.1 Technical Data PC Cards cifX ................................................................................122
9.1.1 CIFX 104-RE, CIFX 104-RE-R .........................................................................122
9.1.2 CIFX 104-RE\F, CIFX 104-RE-R\F and Variants .............................................124
9.1.3 CIFX 104-DP, CIFX 104-DP-R .........................................................................126
9.1.4 CIFX 104-DP\F, CIFX 104-DP-R\F ..................................................................127
9.1.5 CIFX 104-CO, CIFX 104-CO-R ........................................................................129
9.1.6 CIFX 104-CO\F, CIFX 104-CO-R\F..................................................................130
9.1.7 CIFX 104-DN, CIFX 104-DN-R ........................................................................132
9.1.8 CIFX 104-DN\F, CIFX 104-DN-R\F ..................................................................133
9.1.9 CIFX 104-CC\F .................................................................................................135
9.1.10 AIFX-RE ...........................................................................................................136
9.1.11 AIFX-RE\M12 ...................................................................................................138
9.1.12 AIFX-DP ...........................................................................................................139
9.1.13 AIFX-CO ...........................................................................................................140
9.1.14 AIFX-DN ...........................................................................................................141
9.1.15 AIFX-CC ...........................................................................................................142
9.1.16 AIFX-DIAG........................................................................................................143
9.2 Technical Data of the Communication Protocols ....................................................144
9.2.1 CC-Link IE Field Basic Slave ...........................................................................144
9.2.2 EtherCAT Master ..............................................................................................145
9.2.3 EtherCAT Slave ................................................................................................146
9.2.4 EtherNet/IP Scanner (Master) ..........................................................................147
9.2.5 EtherNet/IP Adapter (Slave) .............................................................................148
9.2.6 Open Modbus/TCP ...........................................................................................149
9.2.7 POWERLINK Controlled Node/Slave ...............................................................149
9.2.8 PROFINET IO-Controller ..................................................................................150
9.2.9 PROFINET IO-Device ......................................................................................151
9.2.10 Sercos Master ..................................................................................................153
9.2.11 Sercos Slave ....................................................................................................154
9.2.12 VARAN Client (Slave).......................................................................................155
9.2.13 PROFIBUS DP Master .....................................................................................156
9.2.14 PROFIBUS DP Slave .......................................................................................157
9.2.15 PROFIBUS MPI ................................................................................................158
9.2.16 CANopen Master ..............................................................................................159
9.2.17 CANopen Slave ................................................................................................160
9.2.18 DeviceNet Master .............................................................................................161
9.2.19 DeviceNet Slave ...............................................................................................162
9.2.20 CC Link Slave ...................................................................................................163
10 DIMENSIONS.......................................................................................................... 164
10.1 Tolerances of the shown Card Dimensions ............................................................164
10.2 Dimensioning PC Cards cifX PC-104 .....................................................................165
10.2.1 CIFX 104-RE ....................................................................................................165
10.2.2 CIFX 104-RE\F .................................................................................................166
10.2.3 CIFX 104-DP ....................................................................................................167
10.2.4 CIFX 104-CO ....................................................................................................168
10.2.5 CIFX 104-DN ....................................................................................................169
10.2.6 CIFX 104-FB\F .................................................................................................170
10.3 Dimensioning AIFX detached Network Interfaces ..................................................171
10.3.1 Ethernet - AIFX-RE...........................................................................................171
10.3.2 Ethernet M12 - AIFX-RE\M12 ..........................................................................172
10.3.3 PROFIBUS - AIFX-DP ......................................................................................173
10.3.4 CANopen - AIFX-CO ........................................................................................173
10.3.5 DeviceNet - AIFX-DN .......................................................................................174
10.3.6 CC-Link - AIFX-CC ...........................................................................................175
10.3.7 Diagnose - AIFX-DIAG .....................................................................................175
11 ANNEX .................................................................................................................... 176

11.1 References .............................................................................................................176
11.1.1 Reference PC/104 Specification ......................................................................176
11.1.2 References Safety ............................................................................................177
11.2 Conventions in this Manual .....................................................................................178
11.2.1 Used Terminology ............................................................................................178
11.3 Legal Notes .............................................................................................................179
11.4 Licenses..................................................................................................................182
11.4.1 License Note about VARAN Client ...................................................................182
11.5 Registered Trademarks ..........................................................................................183
11.6 EtherCAT Disclaimer ..............................................................................................183
11.6.1 EtherCAT Summary over Vendor ID, Conformance test, Membership and
Network Logo ...................................................................................................184
11.7 Notes on earlier Hardeware Revisions ...................................................................185
11.7.1 Failure in 10 MBit/s Half Duplex Mode and Workaround .................................185
11.8 List of Figures .........................................................................................................186
11.9 List of Tables ..........................................................................................................187
11.10 Glossary ..................................................................................................................191
11.11 Contacts ..................................................................................................................200

Introduction 8/200
1 Introduction
1.1 About the User Manual
This user manual provides descriptions of the installation, operation and
hardware of the PC cards cifX PC/104 under Windows® 7, Windows® 8 and
Windows® 10, as listed subsequently.
PC Cards cifX PC/104 (CIFX 104) inclusively the AIFX detached network
interfaces:
 Ethernet (AIFX-RE)  PROFIBUS (AIFX-DP)
 Ethernet M12 (AIFX-RE\M12)  CANopen (AIFX-CO)
 DeviceNet (AIFX-DN)
 CC-Link (AIFX-CC)
 Diagnose (AIFX-DIAG)
for the Real-Time Ethernet systems: for the fieldbus systems:
 CC-Link IE Field Basic  PROFIBUS DP
 EtherCAT  PROFIBUS MPI
 EtherNet/IP  CANopen
 Open-Modbus/TCP  DeviceNet
 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 cifX with integrated Interfaces (page 11) and PC Cards cifX with
AIFX detached Network Interfaces (page 11).
The devices are described in detail in the chapters Installation,
Commissioning and Uninstalling (page 53), Diagnosis with LEDs (page 70),
Device Connections and Switches (page 104) and Technical Data (page
122).
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/200
1.2 List of Revisions

Index Date Chapter Revisions
53 21-09-30 2.4.3, Section Important Changes updated, Windows® 10 added.
2.5.2, Section Hardware: Product Components for PC Cards cifX;
AIFX-RE, Rev. 2.
2.5.4, Section Firmware updated.
3.2.5, 10.3.5, Sections DeviceNet - AIFX-DN and DeviceNet - AIFX-DN: Representation
with counterpart.
7.17.2, 7.18.2, Sections 2 Communication Status LEDs,2 Communication Status LEDs,
7.20.2,7.21.2, 2 Communication Status LEDs, 2 Communication Status LEDs:
Update ERR LED description.
7.9, Section EtherNet/IP Adapter (Slave) updated.
8.1.4, Section Use of Hubs and Switches updated.
8.1.4, Section Use of Hubs and Switches updated.
8.8.4, 8.8.7, Sections Pin Assignment Cable Connector Ethernet X1, AIFX-RE, Pin
8.8.8, 8.8.9, Assignment Cable Connector Fieldbus X1, AIFX-DP, Pin Assignment
8.8.10, Cable Connector Fieldbus X1, AIFX-CO, Pin Assignment Cable Connector
Fieldbus X1, AIFX-DN, Pin Assignment Cable Connector Fieldbus X1,
AIFX-CC added.
9.1, Section Technical Data PC Cards cifX: UKCA added.
9.2, Section Technical Data of the Communication Protocols updated
(EtherCAT Master V3, POWERLINK Controlled Node/Slave V2 as well as
PROFINET IO-Controller V2 removed, PROFINET IO-Device V3.4
respectively V3.13 removed respectively updated to V4)
10.3.1, Section Ethernet - AIFX-RE revised.
10.3.5, 10.3.6 Sections DeviceNet - AIFX-DN and CC-Link - AIFX-CC updated.
54 22-03-21 All Language revision of safty instructions.
Table 1: List of Revisions
1.3 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.

Descriptions and Requirements 10/200
2 Descriptions and Requirements

2.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
 EtherCAT Master  PROFIBUS DP Slave
 EtherCAT Slave  PROFIBUS MPI Device
 EtherNet/IP Scanner (Master)  CANopen Master
 EtherNet/IP Adapter (Slave)  CANopen Slave
 Open-Modbus/TCP  DeviceNet Master
 POWERLINK-Controlled-Node/Slave  DeviceNet Slave
 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.

2.2 PC Cards cifX with integrated Interfaces

The PC cards PC/104 CIFX 104-XX and CIFX 104-XX-R provide integrated
Ethernet, fieldbus or diagnostic interfaces.
2.2.1 PC Cards PC/104: CIFX 104-XX, CIFX 104-XX-R

PC Card cifX Description
PC Cards PCI-104 with integrated Ethernet, fieldbus or diagnostic interface
Real-Time Ethernet
CIFX 104-RE Real-Time Ethernet Master or Slave
CIFX 104-RE-R Real-Time Ethernet Master or Slave (connectors at the left side)
PROFIBUS
CIFX 104-DP PROFIBUS DP Master or Slave and PROFIBUS MPI Device
CIFX 104-DP-R PROFIBUS DP Master or Slave and PROFIBUS MPI Device (connectors at the left side)
CANopen
CIFX 104-CO CANopen Master or Slave
CIFX 104-CO-R CANopen Master or Slave (connectors at the left side)
DeviceNet
CIFX 104-DN DeviceNet Master or Slave
CIFX 104-DN-R DeviceNet Master or Slave (connectors at the left side)
Table 2: PC Cards PC/104: CIFX 104-XX and CIFX 104-XX-R
2.3 PC Cards cifX with AIFX detached Network Interfaces

2.3.1 The Label „\F“ in the Device Name
The PC cards cifX including the label “\F” in its device name are composed
of a basic card and a detached network interface AIFX.
• The basic cards CIFX 104-RE\F and CIFX 104-RE-R\F are equipped
with a Cable Connector Ethernet, to connect the Ethernet detached
network interface (AIFX-RE) or the Ethernet M12 detached network
interface (AIFX-RE\M12).
• The basic cards CIFX 104-FB\F and CIFX 104-FB-R\F are equipped
with a Cable Connector Fieldbus, to connect the detached network
interface PROFIBUS (AIFX-DP), CANopen (AIFX-CO), DeviceNet
(AIFX-DN) or CC-Link (AIFX-CC*), (*only for CIFX 104-FB\F; Note: ‘FB’
stands for ‚Fieldbus’.)
• The basic cards CIFX 104-RE\F, CIFX 104-RE-R\F, CIFX 104-FB\F and
CIFX 104-FB-R\F are additionally equipped with a Cable Connector
DIAG, to optionally connect the diagnostic detached network interface
(AIFX-DIAG).
Important! Operating the PC cards cifX PC/104 with AIFX detached
network interface (label “\F” in the device name) requires proper
connection of the Ethernet (AIFX-RE), the Ethernet M12 (AIFX-RE\M12),
PROFIBUS (AIFX-DP), CANopen (AIFX-CO), DeviceNet (AIFX-DN) or
CC-Link (AIFX-CC) detached network interface to the basic card!

2.3.2 PC Cards PC/104: CIFX 104-XX\F und Variants

PC Card cifX Description
PC Cards PC/104 with AIFX detached Network Interfaces
Real-Time Ethernet
CIFX 104-RE\F Real-Time Ethernet Master or Slave
- Basic card CIFX 104-RE\F and
- Ethernet detached network interface (AIFX-RE).
CIFX 104-RE-R\F Real-Time Ethernet Master or Slave (connectors at the left side)
- Basic card CIFX 104-RE-R\F and
- Ethernet detached network interface (AIFX-RE).
CIFX 104-RE\F\M12 Real-Time Ethernet Master or Slave
- Basic card CIFX 104-RE\F and
- Ethernet M12 detached network interface (AIFX-RE\M12).
CIFX 104-RE-R\F\M12 Real-Time Ethernet Master or Slave (connectors at the left side)
- Basic card CIFX 104-RE-R\F and
- Ethernet M12 detached network interface (AIFX-RE\M12).
PROFIBUS
CIFX 104-DP\F PROFIBUS DP Master or Slave or PROFIBUS MPI Device
- Basic card CIFX 104-FB\F and
- PROFIBUS detached network interface (AIFX-DP).
CIFX 104-DP-R\F PROFIBUS DP Master or Slave or PROFIBUS MPI Device (connectors at the left side)
- Basic card CIFX 104-FB-R\F and
- PROFIBUS detached network interface (AIFX-DP).
CANopen
CIFX 104-CO\F CANopen Master or Slave
- CANopen detached network interface (AIFX-CO).
CIFX 104-CO-R\F CANopen Master or Slave (connectors at the left side)
- CANopen detached network interface (AIFX-CO).
DeviceNet
CIFX 104-DN\F DeviceNet Master or Slave
- DeviceNet detached network interface (AIFX-DN).
CIFX 104-DN-R\F DeviceNet Master or Slave (connectors at the left side)
- DeviceNet detached network interface (AIFX-DN).
CC-Link
CIFX 104-CC\F CC-Link Slave
- CC-Link detached network interface (AIFX-CC).
Table 3: PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F, CIFX 104-RE\F\M12, CIFX
104-RE-R\F\M12

2.3.3 AIFX detached Network Interfaces

AIFX Description For the PC Cards cifX
AIFX-RE Ethernet detached network interface CIFX 104-RE\F, CIFX 104-RE-R\F
AIFX- Ethernet M12 detached network interface CIFX 104-RE\F\M12,
RE\M12 CIFX 104-RE-R\F\M12
AIFX-DP PROFIBUS detached network interface CIFX 104-DP\F, CIFX 104-DP-R\F
AIFX-CO CANopen detached network interface CIFX 104-CO\F, CIFX 104-CO-R\F
AIFX-DN DeviceNet detached network interface CIFX 104-DN\F, CIFX 104-DN-R\F
AIFX-CC CC-Link detached network interface CIFX 104-CC\F
AIFX-DIAG Diagnostic detached network interface CIFX 104-RE\F, CIFX 104-RE-R\F
(optional) CIFX 104-RE\F\M12,
CIFX 104-RE-R\F\M12,
CIFX 104-DP\F, CIFX 104-DP-R\F,
CIFX 104-CO\F, CIFX 104-CO-R\F,
CIFX 104-DN\F, CIFX 104-DN-R\F,
CIFX 104-CC\F
Table 4: AIFX detached Network Interfaces for PC Cards cifX with Cable Connector

2.4 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).
2.4.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).
2.4.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.

2.4.3 Important Changes
2.4.3.1 EtherMet/IP Adapter Firmware Version V3.6
New firmware version 3.6 for EtherNet/IP-Adapter

The EtherNet/IP-Adapter firmware has been revised and is now available
as V3.6.
Use the EtherNet/IP-Adapter firmware V3.6 for a new installation when
creating or developing your application program for the first time.
If you want to change from firmware version 3.3 to version 3.5, please refer
to the Migration Guide under https://kb.hilscher.com/x/NqhTC.
2.4.3.2 PROFINET IO-Device Firmware Version V4.5
New firmware version 4.5 for PROFINET IO-Device

The PROFINET IO-Device firmware has been revised and is now available
as V4.5.
Use the PROFINET IO-Device firmware V4.5 for a new installation when
creating or developing your application program for the first time.
If you want to change from an older firmware version to the latest version in
an existing system, please refer to the Migration Guide, which is available
under https://kb.hilscher.com/x/lRyRBg.

2.4.4 Device Description Files 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,
PROFIBUS MPI and VARAN do not use device description files.
PC Cards cifX System File Name of the Device Description File

CIFX 104-RE CC-Link IE Field Basi 0x0352_CIFX RE CCIEBS_1_en.cspp
CIFX 104-RE-R Slave
CIFX 104-RE\F
EtherCAT Slave Hilscher CIFX RE ECS V4.6.X.xml
CIFX 104-RE-R\F
CIFX 104-RE\F\M12 EtherCAT Master Hilscher Master Redundancy Port.xml
CIFX 104-RE-R\F\M12
EtherNet/IP-Adapter HILSCHER CIFX-RE EIS V1.1.EDS
(Slave)
EtherNet/IP Scanner HILSCHER CIFX-RE EIM V1.0.eds
(Master)
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 00000044_CIFX RE PLS.xdd

Controlled Node/Slave
PROFINET IO-Device GSDML-V2.35-HILSCHER-CIFX RE PNS-yyyymmdd.xml
Sercos Slave SDDML#v3.0#Hilscher#CIFX_RE-FIXCFG_FSPIO#yyyy-mm-dd.xml,
SDDML#v3.0#Hilscher#CIFX_RE-VARCFG_FSPDRIVE#yyyy-mm-dd.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.
CIFX 104-DP PROFIBUS HIL_0B69.GSD

CIFX 104-DP-R DP Slave
CIFX 104-DP\F
CIFX 104-DP-R\F
CIFX 104-CO CANopen Slave CIFX CO COS.eds
CIFX 104-CO-R
CIFX 104-CO\F
CIFX 104-CO-R\F
CIFX 104-DN DeviceNet Slave CIFX_DN_DNS.EDS
CIFX 104-DN-R
CIFX 104-DN\F
CIFX 104-DN-R\F
CIFX 104-CC\F CC-Link Slave 0x0352_CIFX-CCS_2.11_en.cspp,
0x0352_CIFX-CCS_2.11_en.cspproj
Table 5: Device Description Files for PC Cards cifX
2.5 Revision or version status of hardware and software

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 66.

2.5.1 Hardware: PC Cards cifX
PC Card cifX, AIFX Part No. Hardware USB
Revision from HW
Rev.
CIFX 104-RE 1278.100 3 1
CIFX 104-RE-R 1279.100 3 1
CIFX 104-RE\F1 1278.101 3 16 1inclusively detached network interface
Ethernet (AIFX-RE)
CIFX 104-RE\F\M127 1278.121 3 16
2inclusively detached network interface
CIFX 104-RE-R\F1 1279.101 3 16
PROFIBUS (AIFX-DP)
CIFX 104-RE-R\F\M127 1279.121 3 16 3inclusively detached network interface
CIFX 104-DP 1278.410 2 1 CANopen (AIFX-CO)
4
CIFX 104-DP-R 1279.410 2 1 inclusively detached network interface
DeviceNet (AIFX-DN)
CIFX 104-DP\F2, 8 1278.411 2 16
5inclusively detached network interface
CIFX 104-DP-R\F2, 8 1279.411 2 16
CC-Link (AIFX-CC)
CIFX 104-CO 1278.500 2 1 6 only when using the detached network
CIFX 104-CO-R 1279.500 2 1 interface diagnostic (AIFX-DIAG)
7
CIFX 104-CO\F3, 8 1278.501 2 16 inclusively detached network interface
Ethernet M12
CIFX 104-CO-R\F3, 8 1279.501 2 16
(AIFX-RE\M12)
CIFX 104-DN 1278.510 2 1 8optional mit 30 cm-Kabel verfügbar;
CIFX 104-DN-R 1279.510 2 1 Bestellbezeichnung erweitert sich um „/30“
CIFX 104-DN\F4, 8 1278.511 2 16
CIFX 104-DN-R\F4, 8 1279.511 2 16
CIFX 104-CC\F5 1278.741 2 16
Table 6: Reference on Hardware PC Cards cifX
2.5.2 Hardware: Product Components for PC Cards cifX

AIFX detached Part No. Hardware
Network Interfaces Revision
AIFX-RE 2800.100 2
AIFX-RE\M12 2800.101 2
AIFX-DP8 2800.400 2 8 optionally available with 30 cm cable;
part number is extended by „/30“

AIFX-CO8 2800.500 2
AIFX-DN8 2800.510 3
AIFX-CC 2800.730 2
AIFX-DIAG 2800.000 2
Table 7: Reference on Hardware AIFX detached Network Interfaces
2.5.3 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.5
Toolkit 1.6
cifX TCP/IP Server for SYCON.net cifX TCP Server.exe V2.3
US Driver USB Driver of Windows® 5.1.2600.x
Table 8: Reference on Driver and Software

2.5.4 Firmware
Protocol Firmware File Firmware Minimum Version Minimum Version
Version* of the Firmware for of the Firmware for
USB Support PC Cards cifX PC/104
CANopen Master CIFXCOM.NXF 2.14 from 2.5.2.0 from 2.4.5.0
CANopen Slave CIFXCOS.NXF 3.8 from 2.4.4.0 from 2.4.2.0
CC-Link Slave CIFXCCS.NXF 2.13 - -
CC-Link IE Field Basic Slave C020Y000.NXF 1.1 -
DeviceNet Master C0206000.NXF 2.4 from 2.2.7.0 from 2.2.4.0
DeviceNet Slave CIFXDNS.NXF 2.7 from 2.2.7.0 from 2.2.5.0
EtherCAT Master CIFXECM.NXF 4.5 (V4) from 2.4.4.0 from 2.4.3.0
EtherCAT Slave CIFXECS.NXF 4.8 (V4) from 2.5.13.0 from 2.5.10.0
EtherNet/IP Scanner CIFXEIM.NXF 2.11 from 2.2.4.1 from 2.2.2.0
EtherNet/IP-Adapter C010H000.NXF 3.6 (V3) from 2.3.4.1 from 2.2.3.0
Open-Modbus/TCP CIFXOMB.NXF 2.7 from 2.3.2.1 from 2.3.1.0
POWERLINK Controlled Node C010K000.NXF 3.4 (V3) from 2.1.22.0 from 2.1.19.0
PROFIBUS DP Master CIFXDPM.NXF 2.8 from 2.3.22.0 from 2.3.21.0
PROFIBUS DP Slave CIFXDPS.NXF 2.11 from 2.3.30.0 from 2.3.30.0
PROFIBUS MPI-Gerät CIFXMPI.NXF 2.4 from 2.4.1.2 from 2.4.4.1
PROFINET IO-Controller C010C000.NXF 3.4 (V3) from 2.4.10.0 from 2.4.10.0
PROFINET IO-Device C010D000.NXF 4.5 (V4) from 3.4.9.0 from 3.4.7.0
Sercos Master CIFXS3M.NXF 2.1 from 2.0.14.0 from 2.0.12.0
Sercos Slave CIFXS3S.NXF 3.5 from 3.0.13.0 from 3.0.10.0
VARAN-Client CIFXVRS.NXF 1.1 from 1.0.3.0 from 1.0.3.0
Table 9: Reference on Firmware
Note: *Unless otherwise indicated, in this manual data to the firmware

version correspond to the stack version.
The downloadable cifX firmware runs on PC cards cifX PC/104. The firm-
ware automatically detects whether it is running on a PC cards cifX PC-
104. Precedent cifX firmware is only applicable to PC cards cifX PC/104.
If a precedent cifX firmware (without PC/104 recognition) is loaded in

a PC Card cifX PC/104, the cifX will get defective and must be sent to
the service! For the PC cards cifX PC/104 only cifX firmware from the
minimum versions may be used as listed in table Reference on Firmware
on page 18.

2.6 Device Label with Barcode

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 bar code and the information contained
therein in plain text.
The bar code (EAN 39) contains the following information:
Part number: 1234.567
Hardware revision: 1
Serial number: 20002
Security code: X
Figure 1: Example Barcode Label (EAN 39)

Device Drawings 20/200
3 Device Drawings
3.1 PC-Karten cifX PC/104
3.1.1 CIFX 104-RE
Steckbrücke Datenbusbreite 8 Bit und 16 Bit
System LED (gelb/grün) / (yellow/green) (J9, im Bild Einstellung Steckbrücke für 16 Bit)
Kommunikationsstatus-LED 0 und 1 (rot/grün) / SYNC-Anschluss / SYNC Connector Data Bus Width Jumpers 8 Bit and 16 Bit
Communication Status LED 0 and 1 (red/green) (X51, 3-polig / 3 pin) (J9, Jumper Settings for 16 Bit shown)
COM 1
COM 0
SYS
Ethernet RJ45-Buchse / RJ45 Socket
(X6) Kanal 0 /
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Channel 0 (CH 0)
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Kanal 1 /
Channel 1 (CH 1)
LED LED
grün / green gelb / yellow
(x16)
Mini-B-USB-Buchse / Mini B USB Plug
(X5, 5-polig / 5 pin)
(x1)
Drehschalter Geräteadresse /
Rotary Switch Device Address
(ohne Funktion / without function)
Interrupt-Steckbrücke / Interrupt Jumper

PC/104 Bus
(J8, 11-polig / 11 pin)
(X1, 64-polig / 64 pin)
Adresssteckbrücke / Address Jumpers
(X2, 40-polig / 40 pin)
(J7, 7-polig / 7 pin)
Standardeinstellungen Steckbrücken / Default Jumper Settings
Figure 2: CIFX 104-RE*
Note:
 *Device supports Auto Crossover Function.
 In Interrupt Mode (IRQ = Interrupt Request) exactly one jumper must
be set. If no jumper is set, the PC card cifX works in Polling Mode.
For further details refer to Table 18: Starting Address and Interrupt for
16 KByte Dual-Port Memory on page 58.
 The meaning of the LEDs depends from the loaded firmware. See
chapter Diagnosis with LEDs beginning from page 70.
 For the pin assignment of the PCI/104 bus X1/X2 refer to section Pin
Assignment for PC/104 Bus on page 120.
 For the pin assignment of the SYNC Connector refer to section Pin
Assignment SYNC Connector, X51 on page 118.
 For further information on the Mini-B USB Connector refer to section
Mini-B USB Connector (5 Pin) on page 109.

3.1.2 CIFX 104-RE-R

(J9, im Bild Einstellung Steckbrücke für 16 Bit)
SYNC-Anschluss / SYNC Connector Data Bus Width Jumpers 8 Bit and 16 Bit
(X51, 3-polig / 3 pin) (J9, Jumper Settings for 16 Bit shown)
System LED (gelb/grün) / (yellow/green)
Kommunikationsstatus-LED 0 und 1 (rot/grün) /
COM 0
COM 1
SYS
Communication Status LED 0 and 1 (red/green)
Ethernet RJ45-Buchse / RJ45 Socket (X306)

Kanal 1 /
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Channel 1 (CH 1)
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Kanal 0 /
Channel 0 (CH 0) LED LED
grün / green gelb / yellow

(X305, 5-polig / 5 pin)
(x1)
(x16) (ohne Funktion / without function)
PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)

(J8, 11-polig / 11 pin)
Figure 3: CIFX 104-RE-R*
Note:
 *Device supports Auto Crossover Function.
 The meaning of the LEDs depends from the loaded firmware. See
chapter Diagnosis with LEDs beginning from page 70.

3.1.3 CIFX 104-RE\F

SYNC-Anschluss / SYNC Connector
System-LED
(gelb/grün) /
SYS
(yellow/green)

Data Bus Width Jumpers 8 Bit and 16 Bit
(J9, Jumper Settings for 16 Bit shown)
Kabelstecker Ethernet /
Cable Connector Ethernet
(X4, 20-polig / 20 pin)
Kabelstecker DIAG /
Cable Connector DIAG
(X3, 12-polig / 12 pin)
PC/104-Bus / PC/104 Bus Interrupt-Steckbrücke / Interrupt Jumper

(X1, 64-polig / 64 pin) (J8, 11-polig / 11 pin)
(X2, 40-polig / 40 pin) Adresssteckbrücke / Address Jumpers
Figure 4: Basic Card for CIFX 104-RE\F
Note:
 If the assembly inter face diagnostic AIFX-DIAG is connected to the
basic card for the PC card CIFX 104-RE\F or CIFX 104-RE-R\F, the
Mini-B USB connector on the AIFX-DIAG can be used beginning with
the hardware revision 5 of the PC card cifX.

3.1.4 CIFX 104-RE-R\F

SYNC-Anschluss / SYNC Connector Data Bus Width Jumpers 8 Bit and 16 Bit
(X51, 3-polig / 3 pin) (J9, Jumper Settings for 16 Bit shown)
System LED
(gelb/grün) / (yellow/green)
SYS
Kabelstecker Ethernet /
(X304, 20-polig / 20 pin)
Kabelstecker DIAG /
(X303, 12-polig / 12 pin)
PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)

(J8, 11-polig / 11 pin)
Figure 5: Basic Card for CIFX 104-RE-R\F
Note:
 If the assembly inter face diagnostic AIFX-DIAG is connected to the
basic card for the PC card CIFX 104-RE\F or CIFX 104-RE-R\F, the
Mini-B USB connector on the AIFX-DIAG can be used beginning with
the hardware revision 5 of the PC card cifX.

3.1.5 CIFX 104-DP

System LED (gelb/grün)
(yellow/green)
Kommunikationsstatus-LED (rot/grün)
Communication Status LED (red/green)
COM
SYS
PROFIBUS-Schnittstelle Steckbrücke Datenbusbreite 8 Bit und 16 Bit
DSub-Buchse (X400B, 9-polig) (J9, im Bild Einstellung Steckbrücke für 16 Bit)
PROFIBUS Interface (J9, Jumper Settings for 16 Bit shown)
DSub female Connector
(X400B, 9 pin)
(x16)
Drehschalter Geräteadresse / (x1)

PC/104 Bus
(X1, 64-polig / 64 pin) Interrupt-Steckbrücke / Interrupt Jumper
Figure 6: CIFX 104-DP
Note:

3.1.6 CIFX 104-DP-R

Kommunikations-LED (rot/grün) /
Communication LED (red/green)
COM
SYS
PROFIBUS-Schnittstelle
DSub-Buchse (X400, 9-polig)
PROFIBUS Interface
DSub female Connector (X400, 9 pin)

(x1)
(X305, 5-polig / 5 pin)
(x16) Drehschalter Geräteadresse /

PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)
(J8, 11-polig / 11 pin)
Figure 7: CIFX 104-DP-R
Note:

3.1.7 CIFX 104-CO

System LED (gelb/grün)
(yellow/green)
CAN LED (rot/grün)
CAN
SYS
(red/green)

CANopen-Schnittstelle Data Bus Width Jumpers 8 Bit and 16 Bit
DSub-Stecker (X400B, 9-polig) (J9, Jumper Settings for 16 Bit shown)
CANopen Interface
DSub male Connector (X400B, 9 pin)

(x16)
Rotary Switch Device Address (x1)
PC/104 Bus
Figure 8: CIFX 104-CO
Note:

3.1.8 CIFX 104-CO-R


CAN LED (rot/grün) / (red/green)
CAN
SYS
CANopen-Schnittstelle
DSub-Stecker, (X400, 9-polig)
CANopen Interface
DSub male Connector, (X400, 9 pin)

(X305, 5-polig / 5 pin)
(x1)
(x16)
PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)
(J8, 11-polig / 11 pin)
Figure 9: CIFX 104-CO-R
Note:

3.1.9 CIFX 104-DN

System LED (gelb/grün) /
(yellow/green)
Modulnetzwerkstatus-LED (rot/grün) /
MNS
SYS
Module Network Status LED (red/green)
Steckbrücke Datenbusbreite
(J9, im Bild Brückung für 16 Bit)
Data Bus Width Jumpers
DeviceNet-Schnittstelle
1
COMBICON-Stecker (X360, 5-polig)
2
DeviceNet Interface
3
COMBICON male Connector
4
(X360, 5 pin)
(x16)
Mini-B-USB-Buchse / Mini-B USB Plug
Drehschalter Geräteadresse / (x1)

PC/104 Bus
je mit Standardbrückungen / Default Jumper Settings each
Figure 10: CIFX 104-DN
Note:

3.1.10 CIFX 104-DN-R

Modulnetzwerkstatus-LED (rot/grün) /
MNS
SYS
Module Network Status LED (red/green)
1
COMBICON-Stecker (X360B, 5-polig)
5
2
4
DeviceNet Interface
3
COMBICON male Connector (X360B, 5 pin)
3
2
4
1
5
(x1)
(X305, 5-polig / 5 pin)
(x16) Drehschalter Geräteadresse /

PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)
(J8, 11-polig / 11 pin)
Figure 11: CIFX 104-DN-R
Note:

3.1.11 CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F

System LED
SYS
(gelb/grün) /
(yellow/green)

Kabelstecker Feldbus /
Cable Connector Fieldbus
(X4, 10-polig / 10 pin)
Kabelstecker DIAG /
(X3, 12-polig / 12 pin)
PC/104 Bus
(X1, 64-polig / 64 pin)
(J8, 11-polig / 11 pin)
Figure 12: Basic Card CIFX 104-FB\F for CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F,
CIFX 104-CC\F
Note: In Interrupt Mode (IRQ = Interrupt Request) exactly one jumper must be set. If
no jumper is set, the PC card cifX works in Polling Mode. For further details refer to
Table 18: Starting Address and Interrupt for 16 KByte Dual-Port Memory on page 58.
3.1.12 CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F

System-LED
(gelb/grün) / (yellow/green)
SYS
(X304, 10-polig / 10 pin)
Kabelstecker DIAG /
(X303, 12-polig / 12 pin)
PC/104 Bus
(X1, 64-polig / 64 pin)
(X2, 40-polig / 40 pin)
(J8, 11-polig / 11 pin)
Figure 13: Basic Card CIFX 104-FB-R\F for CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F
Note: In Interrupt Mode (IRQ = Interrupt Request) exactly one jumper must be set. If
no jumper is set, the PC card cifX works in Polling Mode. For further details refer to
Table 18: Starting Address and Interrupt for 16 KByte Dual-Port Memory on page 58.

3.1.13 Reverse Side CIFX 104-XX (all Basic Cards and Variants)
PC/104 Bus (Stiftleiste / Plug Connector)
Figure 14: Reverse Side CIFX 104-XX (all Basic Cards and Variants)

3.2 AIFX detached Network Interfaces
3.2.1 Ethernet - AIFX-RE

Only for CIFX 104-RE\F, CIFX 104-RE-R\F.
Ethernet RJ45-Buchse / RJ45 Socket
Pin 7: Term 2
Pin 4: Term 1
Pin 5: Term 1
Pin 8: Term 2
Kabelstecker Ethernet / Kanal 1 /
Pin 3: RX+
Pin 1: TX+
Pin 6: RX-
Pin 2: TX-
Channel 1
Cable Connector Ethernet (CH 1)
(X1, 20-polig / 20 pin)
Kanal 0 /
Channel 0
(CH 0) LED LED
Matrixcode auf Rückseite von X200 / grün / green gelb / yellow
Matrixcode on Reverse Side of X200
Figure 15: Ethernet detached Network Interface (AIFX-RE)*
Note: *Assembled device supports Auto Crossover Function.
COM0 COM1
COM0: Kommunikationsstatus-LED 0 (rot/grün) /

Communication Status LED 0 (red/green)

Figure 16: Front Side and LED Display Ethernet detached Network Interface (AIFX-RE)
The meaning of the LEDs COM0 and COM1 at the reverse side of the
AIFX-RE and the meaning of the green and yellow LEDs at RJ45Ch0
and RJ45Ch1 corresponds to the description in chapter Diagnosis with
LEDs beginning from page 70.

3.2.2 Ethernet - AIFX-RE\M12

Only for CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12.
M12-Buchse / M12 Female Connector

Kabelstecker Ethernet / Kanal 1 / Channel 1 (CH 1)
X1 Lightpipe
(X2, 20-polig / 20 pin)
LEDs Kanal 0 und 1/ Channel 0 and 1
Ethernet LEDs grün, gelb / green, yellow
Kommunikationsstatus-LEDs /
green1 yellow1 COM1
Communication Status LEDs
flexibles X2 COM0, COM1 (rot/grün / red/green)
green0 yellow0 COM0
Folienkabel /
M12-Buchse / M12 Female Connector
flexible
flat cable Kanal 0 / Channel 0 (CH 0)
2
X0
Pinbelegung M12-Buchse /
X3
3 Pin Assignment
1
M12 Female Connector
Kabelstecker LED-Singale /
Cable Connector LED Signals 4
(X3, 10-polig / 10 pin)
Figure 17: Ethernet M12 detached Network Interface (AIFX-RE\M12)
Note: *Assembled device supports Auto Crossover Function.
Figure 18: Ethernet M12 detached Network Interface (AIFX-RE\M12)
The meaning of the LEDs COM0 and COM1 and of the green and yellow
Ethernet LEDs (for channel0 and channel1) of the AIFX-RE\M12
corresponds to the description in chapter Diagnosis with LEDs beginning
from page 70.

3.2.3 PROFIBUS - AIFX-DP

Only for CIFX 104-DP\F, CIFX 104-DP-R\F.
PROFIBUS-Schnittstelle
DSub-Buchse (X400, 9-polig)
PROFIBUS Interface
DSub female Connector (X400, 9 pin)
(X1, 10-polig / 10 pin) Matrixcode auf Seite von U401 /
Matrixcode is at Side of U401
Figure 19: PROFIBUS detached Network Interface (AIFX-DP)
ERR STA
ERR: LED Fehlerstatus (rot) /

LED Error status (red)
STA: LED Status (grün) /

LED Status (green)
Figure 20: Front Side and LED Display PROFIBUS detached Network Interface (AIFX-DP)
The meaning of the LEDs ERR and STA at the reverse side of the AIFX-
DP corresponds to the description in chapter Diagnosis with LEDs
beginning from page 70.

3.2.4 CANopen - AIFX-CO

Only for CIFX 104-CO\F, CIFX 104-CO-R\F.
CANopen-Schnittstelle
DSub-Stecker (X400, 9-polig)
CANopen Interface
DSub male Connector (X400, 9 pin)
(X1, 10-polig / 10 pin) Matrixcode auf Seite von U362 /
Matrixcode is at Side of U362
Figure 21: CANopen detached Network Interface (AIFX-CO)
ERR RUN
ERR: LED Fehlerstatus (rot) /
LED Error status (red)
RUN: LED Run (grün) /

LED Run (green)
Figure 22: Front Side and LED Display detached Network Interface (AIFX-CO)
The meaning of the LEDs ERR and RUN at the reverse side of the
AIFX-CO corresponds to the description in chapter Diagnosis with LEDs

3.2.5 DeviceNet - AIFX-DN

Only for CIFX 104-DN\F, CIFX 104-DN-R\F.
DeviceNet Interface
COMBICON plug Connector
5
(X360, 5 pin)
4
3
2
1
(X1, 10-polig / 10 pin)
Matrixcode auf Seite von U362 /
Matrixcode is at side of U362
Figure 23: DeviceNet detached Network Interface (AIFX-DN, with counter part)
MNS
MNS: LED Modulnetzwerkstatus (rot) /

LED Module Network status (red)
Figure 24: Front Side and LED Display DeviceNet detached Network Interface (AIFX-DN,
with counter part)
The meaning of the LED MNS at the reverse side of the AIFX-DN
corresponds to the description in chapter Diagnosis with LEDs beginning
from page 70.

3.2.6 CC-Link - AIFX-CC

Only for CIFX 104-CC\F.
CC-Link-Schnittstelle
5
CC-Link Interface
4
COMBICON male Connector
3
(X360, 5 pin)
2
1
(X1, 10-polig / 10 pin)
Figure 25: CC-Link detached Network Interface (AIFX-CC)
L-RUN
L-ERR
Figure 26: Reverse Side CC-Link detached Network Interface (AIFX-CC) with Matrix Label
L-ERR L-RUN
L-RUN: LED L-Run (grün) /
LED L-Run (green)
L-ERR: LED L-Error (rot) /

LED L-Error (red)
Figure 27: Front Side and LED Display CC-Link detached Network Interface (AIFX-CC, with
counter part)
The meaning of the LEDs L-RUN and L-ERR aat the reverse side of the
AIFX-CC corresponds to the description in chapter Diagnosis with LEDs

3.2.7 Diagnostic - AIFX-DIAG

Only for CIFX 104-RE\F, CIFX 104-RE-R\F, CIFX 104-DP\F, CIFX 104-DP-R\F,
CIFX 104-CO\F, CIFX 104-CO-R\F, CIFX 104-DN\F, CIFX 104-DN-R\F,
CIFX 104-CC\F.

(x1) (ohne Funktion / not assigned)
Kabelstecker DIAG /
not used
not used
(X1, 12-polig / 12 pin) (x16)
PWR
nicht verwendet / not used
Versorgungsspannung-EIN-LED (grün) / Power ON LED (green)

COM 1
COM 0
SYS
Kommunikationsstatus-LEDs (rot/grün) /
Communication Status LEDs (red/green)
Figure 28: Diagnostic detached Network Interface (AIFX-DIAG)
The meaning of the LEDs at the AIFX-DAIG corresponds to the

descriptions in chapter Diagnosis with LEDs beginning from page 70. For
further information on the Mini-B USB Connector refer to section Mini-B
USB Connector (5 Pin) on page109.
Matrix_Code
78 9 78 9
34 5 6
34 5 6
A
A
B CD
B CD
Mini-
EF 2 EF 2
01 01
USB
SYS: System LED (gelb/grün) / (yellow/green)
SYS PWR PWR: Versorgungsspannung-EIN-LED (grün) /

Power ON LED (green)
COM0 -
COM1 - Reverse Side with Matrix Label
Figure 29: Front Side, LED Display and Reverse Side Diagnostic detached Network
Interface (AIFX-DIAG)

Safety 39/200
4 Safety
4.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.
4.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 104-RE CC-Link IE Field Basic Slave CIFX 104-DP PROFIBUS DP Master,
CIFX 104-RE-R CIFX 104-DP-R PROFIBUS DP Slave,
CIFX 104-RE\F EtherCAT Master, CIFX 104-DP\F PROFIBUS MPI Device
CIFX 104-RE-R\F EtherCAT Slave CIFX 104-DP-R\F
CIFX 104-RE\F\M12
CIFX 104-RE-R\F\M12 EtherNet/IP Scanner (Master),
EtherNet/IP Adapter (Slave)
Open-Modbus/TCP CIFX 104-CO CANopen Master,
CIFX 104-CO-R CANopen Slave
POWERLINK Controlled Node/Slave CIFX 104-CO\F
CIFX 104-CO-R\F
PROFINET IO-Controller (Master), CIFX 104-DN DeviceNet Master,
PROFINET IO-Device (Slave) CIFX 104-DN-R DeviceNet Slave
CIFX 104-DN\F
Sercos Master, CIFX 104-DN-R\F
Sercos Slave
VARAN Client (Slave) CIFX 104-CC\F CC-Link slave
Table 10: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby
The AIFX detached Network Interfaces are each attached to the

respective basic card for the PC card cifX via a cable connector (label „\F“).
Thereby the PC card cifX is equipped with a Real-Time Ethernet or fieldbus
interface and in addition with a diagnostic interface.
AIFX PC Cards cifX with AIFX detached Network Interface
AIFX-RE, AIFX-DIAG CIFX 104-RE\F, CIFX 104-RE-R\F
AIFX-RE\M12, AIFX-DIAG CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12
AIFX-DP, AIFX-DIAG CIFX 104-DP\F, CIFX 104-DP-R\F
AIFX-CO, AIFX-DIAG CIFX 104-CO\F, CIFX 104-CO-R\F
AIFX-DN, AIFX-DIAG CIFX 104-DN\F, CIFX 104-DN-R\F
AIFX-CC, AIFX-DIAG CIFX 104-CC\F
Table 11: PC Cards cifX with AIFX detached Network Interface

Safety 40/200
4.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.
4.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.
4.4.1 Hazardous Voltage, electric Shock

Danger to life or risk of injury by electric shock may occur if you open the
housing of your PC (or connection device) to install your PC card.
• Hazardous voltages are present in the PC (or connection device) for
mounting. Strictly obey to all safety rules provided by the PC’s
manufacturer in the documentation!
• First disconnect the power plug of the PC (or connection device), before
you open the housing.
• Make sure that the power supply is off at the PC (or connection device).
• Only then open the housing and install or remove the PC card.
Reference Safety [S2]

Safety 41/200
4.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.
4.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 42/200
4.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.
4.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.
The data on the mandatory supply voltage for the PC cards cifX described
in this manual you find in the Power Supply and Host Interface on page
48. There the required and permitted supply voltage is provided by device
type inclusively the permitted tolerance range.
4.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!
• Operation 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 48. There the required and permitted signaling voltage
is provided by device type.

Safety 43/200
4.5.3 Electrostatic 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 44/200
4.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.).
4.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 45/200
4.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.
4.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 46/200
4.6 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.
Hazardous voltage!
Danger to life, risk of injury by electric shock
Hazardous voltages are present in the PC (or connection device).
 Strictly obey to all safety rules provided by the PC’s manufacturer in the
documentation!
 First disconnect the power plug of the PC (or connection device), before
you open the housing.
 Make sure that the power supply is off at the PC (or connection device).
 Only then open the housing and install or remove the PC card.
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.

Safety 47/200
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 48.
Electrostatic 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.

Requirements 48/200
5 Requirements
5.1 System Requirements
5.1.1 Slot for the PC Cards cifX PC/104
PC with slot (5 V) for PC cards cifX PC/104:
PC Cards cifX Bus [Pins] Slot
CIFX 104-RE CIFX 104-CO 104 PC/104 Slot (5 V)
CIFX 104-RE-R CIFX 104-CO-R
CIFX 104-RE\F CIFX 104-CO\F
CIFX 104-RE-R\F CIFX 104-CO-R\F
CIFX 104-RE\F\M12 CIFX 104-DN
CIFX 104-RE-R\F\M12 CIFX 104-DN-R
CIFX 104-DP CIFX 104-DN\F
CIFX 104-DP-R CIFX 104-DN-R\F
CIFX 104-DP\F CIFX 104-CC\F
CIFX 104-DP-R\F
Table 12: Slot for the PC Cards cifX PC/104
5.1.2 Power Supply and Host Interface

For the power supply and the host interface used for the PC cards cifX
PC/104 you must observe the following requirements:
PC Cards cifX Supply Signaling Voltage Host Interface

Voltage Host Interface (PCI slot)
CIFX 104-RE CIFX 104-CO +5 V dc ±5 %/ 5 V Input compatible, PC/104
CIFX 104-RE-R CIFX 104-CO-R Typ. 500 mA
5 V TTL Output compatible
CIFX 104-RE\F CIFX 104-CO\F
CIFX 104-RE-R\F CIFX 104-CO-R\F (Uout ≥ 2,4 V @6 mA)
CIFX 104-RE\F\M12 CIFX 104-DN
CIFX 104-RE-R\F\M12 CIFX 104-DN-R
CIFX 104-DP CIFX 104-DN\F
CIFX 104-DP-R CIFX 104-DN-R\F
CIFX 104-DP\F CIFX 104-CC\F
Table 13: Requirements Power Supply and Host Interface for PC Cards cifX PC/104
The data in the Table 13 above have the following meaning:

Supply Voltage
The required and permissible supply voltage at the PC cards cifX PC/104
Signaling Voltage Host Interface
The required or tolerated signaling voltage at the I/O signal pins at the
PC/104 bus of the PC cards cifX PC/104
Host Interface (PCI slot) Type of the host interface

Requirements 49/200
5.1.3 Panel Cutout for Installing AIFX

In order to connect the AIFX detached network interface to a PC card cifX
PC/104 with cable connector Ethernet or fieldbus (labeling „\F“), make sure
that the front plate of the PC cabinet has an appropriate cutout and holes
for fastening the AIFX.
PC Card cifX Panel Cutout
PC/104 at the front plate of the PC cabinet
Table 14: Panel Cutout at the at the front plate of the PC cabinet
The panel cutout must be dimensioned sufficiently large for the interface,
display or control elements placed on the AIFX. Partial standard cutouts
can be used.
PC Cards cifX AIFX Panel Cutout and Holes
CIFX 104-RE\F AIFX-RE Required Cutout for two RJ45 Sockets
CIFX 104-RE-R\F Important! The panel cutout layout must also cover the
LEDs COM 0 and COM1 at the AIFX-RE.
Standard cutout D-Sub-15
Holes 2, distance between the holes 37,3 mm
Further Information In the data sheet MOD JACK – MJIM [2], as well as in
section Ethernet - AIFX-RE on page 32 or Ethernet - AIFX-
RE on page 171.
CIFX 104-RE\F\M12 AIFX- Required Cutout for M12 Socket
CIFX 104-RE- RE\M12 Important! The panel cutout layout must also cover the
R\F\M12 LEDs for channel 0 and channel 1 at the AIFX-RE\M12,
inlcuding the green and yellow Ethernet LEDs as well as the
communication LEDs COM 0 and COM1.
Standard cutout M12
Holes 2, distance between the holes 55 mm
Further Information In the data sheet 99_3732_203_04.pdf [4], as well as in
section Ethernet - AIFX-RE\M12 on page 33 or Ethernet
M12 - AIFX-RE\M12 on page 172.
CIFX 104-DP\F AIFX-DP Required Cutout for Dsub female Connector, 9 pin
CIFX 104-DP-R\F
Further Information in section PROFIBUS - AIFX-DP on page 34 or PROFIBUS
- AIFX-DP on page 173.
CIFX 104-CO\F AIFX-CO Required Cutout for D-Sub male Connector, 9 pin
CIFX 104-CO-R\F
Further Information in section CANopen - AIFX-CO on page 35 or CANopen -
AIFX-CO on page 173.
CIFX 104-DN\F AIFX-DN Required Cutout for CombiCon male Connector, 5 pin
CIFX 104-DN-R\F
Holes 2x2, distance between the holes 24,94 mm
Further Information in section DeviceNet - AIFX-DN on page 36 or DeviceNet -
AIFX-DN on page 174.
CIFX 104-CC\F AIFX-CC Required Cutout for CombiCon male Connector, 5 pin
Standard cutout CombiCon male Connector
Holes 2x2, distance between the holes 24,96 mm
Further Information in section CC-Link - AIFX-CC on page 37 or CC-Link - AIFX-

Requirements 50/200
CC on page 175.
CIFX 104-RE\F AIFX-DIAG Required Cutout for the light channels, the rotary switch and the Mini B USB
CIFX 104-RE-R\F plug
CIFX 104-DP\F
Standard cutout -
CIFX 104-DP-R\F
CIFX 104-CO\F Holes 2, distance between the holes 47,1 mm
CIFX 104-CO-R\F Further Information in section Diagnostic - AIFX-DIAG on page 38 or Diagnose -
CIFX 104-DN\F AIFX-DIAG on page 175.
CIFX 104-DN-R\F
Table 15: Required Panel Cutout and Holes for AIFX
5.1.4 System Requirements cifX PC/104 (ISA)

Note: To operate a PC Card cifX PC/104 (ISA) in a PC, the PC has to
provide a free ISA memory area of 16 Kbyte in the memory range C0000
to FBFFF. If the PC card cifX should be operated with interrupt, then the
PC must provide additionally a free ISA interrupt.
5.1.5 AIFX-RE\M12: Max. permissible Current per external LED

When using the Ethernet AIFX-RE\M12 detached network interface with the
requirement IP67 and the LED signals are routed via the cable connector
LED signals X3 to the mainboard or to a separate detached LED board, the
maximum current drawn per LED must not exceed 5 mA.
Note: The outputs on the cable connector LED signals X3 can drive max.
5 mA. This means that the maximum permissible current per external LED
is 5 mA. If this maximum current is not sufficient, an external driver is
required previous to the LED.

Requirements 51/200
5.2 Requirements for Operation of the PC Cards cifX

Operating the PC cards cifX properly, the following described requirements
must be fulfilled.
Protocols CC-Link IE Field Basic Slave, Sercos Slave, PROFIBUS DP Slave,
EtherCAT Slave, Sercos Master, PROFIBUS DP Master,
EtherCAT Master, VARAN Client (Slave) PROFIBUS MPI Device,
EtherNet/IP Adapter (Slave), CANopen Slave,
EtherNet/IP Scanner (Master), CANopen Master,
Open-Modbus/TCP, DeviceNet Slave,
POWERLINK-Controlled-Node/Slave, DeviceNet Master,
PROFINET IO Device (Slave), CC-Link Slave
PROFINET IO Controller (Master)
Software 1. Driver for the Host Interface
Installation Host Interfaces: PC/104
• 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 17.
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.
Parameter 4. 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)
• Application program (programming required)
Communica- 5. 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.
Hardware Important! 1.) Operating the PC cards cifX with Cable Connector Ethernet or with the
Installation Cable Connector Fieldbus (label “\F” in its device name) requires proper connection of
the Ethernet (AIFX-RE or AIFX-RE\M12), PROFIBUS (AIFX-DP), CANopen (AIFX-CO),
DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) detached network interface to the basic card!
2.) The USB cable must not be connected to the PC card cifX when booting the host PC!
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 16: Requirements to operate PC Cards cifX properly

Requirements 52/200
5.3 Prerequisites for Certification

5.3.1 PROFINET IO Certification for IRT and SYNC0 Signal
5.3.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 20.

Installation, Commissioning and Uninstalling 53/200
6 Installation, Commissioning and Uninstalling

To install / uninstall the PC cards cifX PC/104
 CIFX 104-RE  CIFX 104-CO
 CIFX 104-RE-R  CIFX 104-CO-R
 CIFX 104-RE\F  CIFX 104-CO\F
 CIFX 104-RE-R\F  CIFX 104-CO-R\F
 CIFX 104-RE\F\M12  CIFX 104-DN
 CIFX 104-RE-R\F\M12  CIFX 104-DN-R
 CIFX 104-DP  CIFX 104-DN\F
 CIFX 104-DP-R  CIFX 104-DN-R\F
 CIFX 104-DP\F  CIFX 104-CC\F
 CIFX 104-DP-R\F
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.

6.1 Overview an Installation and Configuration

The following table describes the steps for the software and hardware
installation and for the configuration of a PC card cifX PC/104 (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 USB Driver Only for PC Cards cifX PC/104: equipped with
Depending by device an USB interface or with the diagnostic
type / features detached network interface (AIFX-DIAG).
1.3 Reserve Memory Reserve for the PC card cifX the memory
Range / Interrupt at range and if necessary one interrupt at the
the operating system. operating system.
1.4 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.5 Installing netX For PC Cards cifX Slave:
Configuration Tool
Start the netX Configuration Tool setup
program to install the netX Configuration
Tool.
2 Preparing Hardware
Installation
2.1 Take precautions on Electrostatic sensitive 43
Devices Electrostatic 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 Set Starting Address cifX PC/104: Set Starting 58
and Interrupt Address and Interrupt
2.3 Set Data Bus Width. Depending by the target system Device Drawings 20
(motherboard) if so, set a Data Bus Width of
8 bit or 16 bit. (Default jumper setting 16 Bit)
3 Hardware Installation Installing cifX. Take required safety Installation, 53
precautions. Commissioning and
Uninstalling

information see
manual / section
3.1 Take safety Hazardous Voltage, 40
precautions electric Shock
Hazardous Voltage! Danger to Life,
Risk of Injury by Electric Shock
Disconnect the power plug of the PC
(or connection device).
Make sure that the power supply is off at the
PC (or connection device).
3.2 Open cabinet Now open the cabinet of the PC or of the Installing PC Cards cifX 60
connection device. PC/104
3.3 Installing cifX Plug in and mount the PC card cifX.
3.4 If so, plug module (a) Install the first PC/104 module on the
mainboard.
(b) Install any other PC/104 module on the
respective underlying PC/104 module.
3.5 Connect AIFX The Label „\F“ in the 11
Important! Operating the PC
(only for PC Cards cifX Device Name
cards cifX with AIFX detached
PC/104 with label “\F” network interface requires proper
in its device name and connection of the AIFX-RE, AIFX-
with Cable Connector RE\M12, AIFX-DP, AIFX-CO,
Ethernet X4 or AIFX-DN or AIFX-CC detached
Fieldbus X3) network interface to the basic card!
If so, connect an Ethernet (AIFX-RE or AIFX-

RE\M12), PROFIBUS (AIFX-DP), CANopen
(AIFX-CO), DeviceNet (AIFX-DN) or CC-Link
(AIFX-CC) detached network interface.
Note! If IP 67 is requried:
On the Ethernet AIFX-RE\M12
detached network interface,
remove the front LED lightpipe and
route the LED signals via the cable
connector LED signals X3 to the
mainboard or a separate detached
LED board.
If so, additionally connect an diagnostic
detached network interface (AIFX-DIAG).
To the basic card of each PC card cifX first
connect the AIFX-RE, AIFX-RE\M12, AIFX-
DP, AIFX-CO, AIFX-DN, AIFX-CC or AIFX-
DIAG detached network interface to the PC
card cifX and check if the connector is
plugged in correctly. Only then plug another
PC/104 module.
3.6 Close cabinet Close the cabinet of the PC or connection
device.
3.7 Plug the connecting Note for all PC Cards cifX Real-Time Ethernet Interface 104
cable to the Master or Ethernet:
Slave
Note! The RJ45 socket is only for
use in LAN, not for telecommuni-
cation circuits.

information see
manual / section
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-
ween the devices can not be estab- See corresponding user
lished. If the port settings of the PC manual
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.8 Connect the PC to the Connect the PC or the connection device to
power / switch on. the power supply and switch it on.
4 Notice on how to use Use only one Software.
the Software
4.1 For the configuration, Important! To avoid communication Requirements for 51
the firmware download problems with the device, use the Operation of the PC
and for the diagnosis, USB interface, the serial interface Cards cifX
note: as well as the cifX Device Driver
exclusively with one software, that
is SYCON.net or netX
Configuration Tool.
5 Configuring Slave Download Firmware and Configuration
using SYCON.net Use the corresponding Slave DTM in the
5.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 65
- Select and download the firmware. SYCON.net
Firmware Slave: CC-Link IE Field Basic PROFIBUS DP Slave,
Slave, PROFIBUS MPI
EtherCAT Slave, Device,
EtherNet/IP Adapter, CANopen Slave,
Open-Modbus/TCP, DeviceNet Slave,
POWERLINK- CC-Link Slave
Controlled-Node/Slave,
PROFINET IO Device,
Sercos Slave,
VARAN Client,
5.2 Configuration -Configure the PC card cifX (Slave).
cifX (Slave)
5.3 Download - Download the configuration to the PC card
Configuration cifX (Slave)
6 OR Configuring Download Firmware and Configuration
Slave using netX
Configuration Tool
6.1 Downloading Firmware If SYCON.net was already used on the PC, Requirements for 51
and Configuration stop the ODMV3 service. Therefore, select Operation of the PC
(Slave) Service > Stop from the context menu of the Cards cifX
ODMV3 system tray icon.

information see
manual / section
The ODMV3 system tray icon changes to
ODMV3 Service stopped.
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.
7 Configuring Master Download Firmware and Configuration
using SYCON.net Use the corresponding Master DTM in the
7.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 65
- 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,
7.2 Configuration - Configure the PC card cifX (Master). Notes for the
Configuration of the 64
cifX (Master)
Master Device
7.3 Download - Download the configuration to the PC card
Configuration cifX (Master).
8 Diagnosis by Diagnosis, I/O Data
SYCON.net Use the corresponding Slave or Master DTM
(Slave and Master) in the configuration software SYCON.net.
8.1 Diagnosis Steps - In netDevice rightclick on device symbol. See corresponding user
(Master and Slave) - Select context menu entry Diagnosis, manual
- then select Diagnosis > General or
Firmware Diagnosis,
- or select Diagnosis > Extended Diagnosis.
8.2 I/O Monitor - In netDevice rightclick on device symbol.
- Select context menu entry Diagnosis,
- then Tools > IO Monitor.
-Check the input or output data.
9 OR Slave Diagnosis Diagnosis

by netX Configuration
Tool (only Slave)
9.1 Diagnosis Steps If SYCON.net was already used on the PC,
(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 start Configuration Tool for
the communication to the Master device and cifX, comX and netJACK
to run the diagnosis.
- click on Extended, to run the extended
diagnosis.
Table 17: Steps for the Software and Hardware Installation, the Configuration and for the
Diagnosis of a PC Card cifX PC/104 (Master and Slave)

6.2 cifX PC/104: Set Starting Address and Interrupt

To set the starting address and or an interrupt (or polling) for PC Cards
cifX PC/104, proceed as follows:
1. Check the memory area of the PC.
Important! Make sure that the configured memory areas and interrupts of
the PC are not used by another PC component.
In order to identify and prevent such errors:

 Start the Device Manager.
 Select menu View > Resources by type.
 The used Memory respectively the interrupt (IRQ) resources are
shown.
 Search for a free memory area:
The possible memory areas of 16 KByte are:
• C0000 … C3FFF (hex),
• D0000 … D3FFF (hex),
• E0000 … E3FFF (hex) or
• F0000 … F3FFF (hex).
The PC card cifX PC/104 can be used in poll mode or in interrupt mode.
 If the PC card cifX shall be used in interrupt mode, then search for a
free interrupt:
Possible interrupts are 3, 4, 5, 6, 7, 9, 10, 11, 12, 14, 15
2. Configure the start address of the PC card cifX PC/104 (Hardware).
Note: Note that the PC card cifX PC/104 requires a free memory area of
16 KByte. Possible are the following areas:
- C0000 … C3FFF (hex),
- D0000 … D3FFF (hex),
- E0000 … E3FFF (hex) or
- F0000 … F3FFF (hex).
Address A19 A18 A17 A16 A15 A14 Interrupt 3 … 12 14 15

C0000 X X X X 15 X
D0000 X X X 14 X
E0000 X X X 12 X
F0000 X X …
Default Addresse D0000 3 X
(X = Jumper closed)
Polling No jumper is set.

Table 18: Starting Address and Interrupt for 16 KByte Dual-Port Memory
For more see next page.

3. If you are using the interrupt mode, set up a free interrupt on the PC
card cifX PC/104 (Hardware).
For polling operation mode interrupt jumpers are not required.
Note: The default setting is address D0000 and no interrupt (Basis

Configuration 0). To change the address select Basis Configuration 1.
The interrupt and the address can be changed under Basis
Configuration 2.
Note: On some PCs it is not possible to find a free ISA memory area
between C0000–FBFFF or a free ISA interrupt in the Device Manager.
This is Windows®(*) ACPI (Advanced Configuration and Power Manage-
ment Interface) depending. Check at first if your PC is ACPI compatible
and you are using the latest BIOS version for your mainboard. Are there
still problems to find available ISA resources, you can try to run
Windows®(*) in "Standard PC" mode (ACPI disabled). Therefore the ACPI-
HAL of Windows®(*) must be replaced with the STANDARD-PC-HAL or
Windows®(*) must be installed new. Contact Microsoft how to change the
Windows®(*) XP-HAL, because this can make your installation unusable.
(*) Windows® XP
4. Reserve Memory Range / Interrupt at the operating system.

 Reserve for the PC cards cifX PC/104 the memory range and if
necessary one interrupt at the operating system.
For further information refer to User Manual Software Installation for the
PC Cards cifX on the Communication Solutions DVD.

6.3 Installing PC Cards cifX PC/104 (PC/104 Modules)

Note: For PC cards cifX PC/104 with AIFX detached network interface
first install the basic card. Then connect the AIFX detached network
interface to the basic card.
1. Adhere to the necessary safety precautions for components that are
vulnerable with electrostatic discharge.

2. Configure starting address, interrupt and data bus width of the PC card
cifX PC/104
 Configure the start address of the PC card cifX PC/104.
 If you are using the interrupt mode, set up a free interrupt on the PC
card cifX PC/104.
For polling operation mode interrupt jumpers are not required.
Note: Several PC/104 modules can be plugged one upon the other. For
each PC card CIFX 104-RE\F you must define a free memory area of 16
KByte.
For further information on the starting address and or an interrupt (or
polling) refer to section cifX PC/104: Set Starting Address and Interrupt
on page 58.
 Depending by the target system (motherboard) if so, set at the PC card
cifX PC/104 a Data Bus Width of 8 bit or 16 bit.
By default the jumper is set for a data bus width of 16 Bit (refer to chapter
Device Drawings on page 20.
3. Take safety precautions.
Hazardous voltage!
 Disconnect the power plug of the PC (or connection device).
4. Open cabinet.
 Open the cabinet of the PC or of the connection device.
Note: If several PC/104 modules shall be put together in a stack:
(a) Install the first PC/104 module on the mainboard.
(b) Only for the basic cards CIFX 104-RE\F and CIFX 104-RE-R\F or the
basic cards CIFX 104-FB\F and CIFX 104-FB-R\F: Connect the AIFX-RE,
AIFX-RE\M12, AIFX-DP, AIFX-CO, AIFX-DN, AIFX-CC detached network
interface or AIFX-DIAG to the basic card for the first PC/104 module.
(c) Connect any other PC/104 module on the respective underlying
PC/104 module.
5. Install PC card cifX PC/104.

 Plug the PC card cifX into a free PC/104 slot (or if so, to the underlying
PC/104 module).
 Fix the PC card cifX using 4 spacing bolts and screws intended to the
mainboard (or if so, to the underlying PC/104 module). The scope of
delivery does not include spacing bolts and screws.
Connect AIFX detached Network Interface

Only for the basic cards CIFX 104-RE\F and CIFX 104-RE-R\F or the basic
cards CIFX 104-FB\F and CIFX 104-FB-R\F:
Note: First connect the AIFX-RE, AIFX-RE\M12, AIFX-DP, AIFX-CO,
AIFX-DN or AIFX-CC detached network interface to each basic card
PC/104, before plugging another PC/104 module. Just so you can check
exactly whether the AIFX is properly connected to the basic card.
Important! Operating the PC cards CIFX 104-XX\F or CIFX 104-XX-R\F
requires proper connection of the Ethernet (AIFX-RE or AIFX-RE\M12),
PROFIBUS (AIFX-DP), CANopen (AIFX-CO), DeviceNet (AIFX-DN) or
CC-Link (AIFX-CC) detached network interface to the basic card!
Note: If IP 67 is requried: On the Ethernet AIFX-RE\M12 detached

network interface, remove the front LED lightpipe and route the LED
signals via the cable connector LED signals X3 to the mainboard or a
separate detached LED board.
6. Mount the detached network interfaces at the housing panel of the PC.
 Install the AIFX-RE, AIFX-RE\M12, AIFX-DP, AIFX-CO, AIFX-DN or
AIFX-CC detached network interface at the front plate of the PC
cabinet.
7. Connect the Ethernet detached network interface (AIFX-RE) or the
Ethernet M12 detached network interface (AIFX-RE\M12) to the basic
card.
 Connect the cable connector Ethernet X1 on the AIFX-RE (or the
cable connector Ethernet X2 on the AIFX-RE\M12) with the cable.
 Connect the cable connector Ethernet X4 (or X304) on the basic card
CIFX 104-RE\F or CIFX 104-RE-R\F with the cable.
 
Figure 30: Connecting the Ethernet detached Network Interface (AIFX-RE) to the Basic Card
CIFX 104-RE\F (Example)
8. Or connect the PROFIBUS (AIFX-DP), CANopen (AIFX-CO),

DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) detached network interface
to the basic card.
 Connect the cable connector fieldbus X1 on the detached network
interface with the cable.
 Connect the cable connector fieldbus X4 (or X304) on the PC card
CIFX 104-FB\F or CIFX 104-FB-R\F Feldbus with the cable.
AIFX-CO with Cable Example basic card CIFX 104-CO-R\F, Cable Connector Fieldbus X4
Connector Fieldbus X1


Important! The contacts on the connection

cable must face up!
Figure 31: Connecting the CANopen detached Network Interface (AIFX-CO) to the Basic
Card 104-FB-R\F (Example)
Connect AIFX-DIAG
Only for the basic cards CIFX 104-RE\F and CIFX 104-RE-R\F or the basic
cards CIFX 104-FB\F and CIFX 104-FB-R\F:
9. If so, connect the diagnostic detached network interface (AIFX-DIAG):
 Connect the cable connector DIAG X1 on the diagnostic detached
network interface (AIFX-DIAG) with the cable.
 Connect the cable connector DIAG X3 (or X303) on the PC card cifX
with the cable.
 Install the detached network interface AIFX-DIAG at the front plate of
the PC cabinet).


Important! The contacts on the connection

cable must face up!
Figure 32: Connecting the Diagnostic detached Network Interface (AIFX-DIAG) to the Basic
Card CIFX 104-FB-R\F (Example)
After this:
10. Close cabinet.
 Close the cabinet of the PC or connection device.
11. Plug the connecting cable to the Master or Slave.

 For the PC cards cifX Real-Time Ethernet note:

Note: The RJ45 socket is only for use in LAN, not for telecommuni-cation
circuits. For further information refer to section Ethernet Interface on
page 104.
 Plug the connecting cable from the PC card cifX to the PC card Master
or Slave.
12. Connect the PC or the connection device to the power supply and
switch it on.
 Connect the PC or the connection device to the power supply.
 Switch on the PC or the connection device.

6.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.
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.
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.
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 19: Notes for the Configuration of the Master Device

Further information to the device description files you find under section
on Device Description Files cifX page 16.
6.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 104-RE, CC-Link IE Field Basic Slave Gateway/Stand-Alone Slave CiFX RE/CCIBS
CIFX 104-RE-R
CIFX 104-RE\F EtherCAT Master Master CIFX RE/ECM
CIFX 104-RE-R\F
CIFX 104-RE\F\M12 EtherCAT Slave Gateway/Stand-Alone Slave CIFX RE/ECS
CIFX 104-RE-R\F\M12
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 104-DP PROFIBUS DP Master Master CIFX DP/DPM

CIFX 104-DP-R
CIFX 104-DP\F PROFIBUS DP Slave Gateway/ Stand-Alone Slave CIFX DP/DPS
CIFX 104-DP-R\F
PROFIBUS MPI Device Gateway/ Stand-Alone Slave CIFX DP/MPI
CIFX 104-CO CANopen Master Master CIFX CO/COM
CIFX 104-CO-R
CIFX 104-CO\F CANopen Slave Gateway/ Stand-Alone Slave CIFX CO/COS
CIFX 104-CO-R\F
CIFX 104-DN DeviceNet Master Master CIFX DN/DNM
CIFX 104-DN-R
CIFX 104-DN\F
CIFX 104-DN-R\F DeviceNet Slave Gateway/ Stand-Alone Slave CIFX DN/DNS
CIFX 104-CC\F CC-Link Slave Gateway/Stand-Alone Slave CIFX CC/CCS
Table 20: Device Names in SYCON.net by Communication Protocol

6.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 Revision or version status of hardware and software
on page 16. The following graphic gives an overview:
Figure 33: System Overview cifX to update Firmware, Driver and Software
Note the specific details for devices with PC/104 bus in section Firmware
on page 18.

6.7 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 the section Requirements for Operation on page
51.
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 lights statically green and the LED COM (or COM0) lights
statically green (or possibly is “off”), 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 Diagnosis with LEDs beginning from page 70.
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 Diagnosis with LEDs beginning from page 70.
Cable
 Check that the pin assignment of the cable is correct. This means, the
cable by which you connect the PC card cifX to the PC card Master or
Slave.
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.

6.8 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 PC cards cifX 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.
6.9 Uninstalling PC Cards cifX PC/104

1. Take safety precautions.
Hazardous voltage!
 Disconnect the power plug of the PC (or connection device).

 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.
2. Open cabinet.
 Open the cabinet of the PC or of the connection device.
Note: If a PC card CIFX 104-XX\F or CIFX 104-XX-R\F shall be
uninstalled from a stack of PC/104 modules:
(a) Remove all PC/104 modules above from the PC card cifX and the PC
card cifX. For each PC card cifX first remove the AIFX detached network
interfaces from the basic cards.
(b) Reinstall the removed PC/104 modules.
Uninstall AIFX detached Network Interfaces

Only for PC cards PC/104 with AIFX detached network interface CIFX 104-
XX\F and CIFX 104-XX-R\F:
3. Uninstall the Ethernet detached network interface (AIFX-RE or AIFX-
RE\M12), PROFIBUS (AIFX-DP), CANopen (AIFX-CO), DeviceNet
(AIFX-DN) and diagnostic (AIFX-DIAG):
 Remove the AIFX detached network interfaces from the front plate of
the PC cabinet.
 Disconnect the cables from the PC card cifX PC/104; cable connector
Ethernet X4 (or X304) or cable connector fieldbus X4 (or X304) and
cable connector DIAG X3 (or X303).

Remove PC Card cifX

4. Remove PC card cifX PC/104.
 Loosen the four fastening screws of the PC card cifX.
 Remove the PC card cifX.
After this:
5. Close cabinet.
 Close the cabinet of the PC or connection device.
6.10 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.

Diagnosis with LEDs 70/200
7 Diagnosis with LEDs

7.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
POWERLINK
Modbus/TCP
in the Device
EtherNet/IP
Field Basic
CC-Link IE
EtherCAT
Drawing EtherCAT
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)
(red/
n)
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
(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 -

Ethernet
(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 21: 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 22: LED Names

7.2 Overview LEDs Fieldbus Systems

LED
CC-Link (Slave)
PROFIBUS MPI
PROFIBUS DP
(1 Duo LED)
(1 Duo LED)
(1 Duo LED)
(1 Duo LED)
DeviceNet
CANopen
(2 LEDs)
System Status SYS SYS SYS SYS SYS
(gelb/green)
Communication COM COM CAN MNS L RUN
Status
(green)
(red/green) (green) (red/green) (red/green)
L ERR
(red)
Table 23: Overview LEDs by Fieldbus System for 1 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 24: LED Names

7.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 25: System Status LED States
7.4 Power On LED

The power On LED PWR can assume the states described below.
PWR LED green
(green)
On Power supply for the device on.
(off)
Off Power supply for the device is missing.
Table 26: Power On LED States

7.5 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)
(green)
On Station in operation and cyclic transmission in progress.
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 On Link: The station is linked to the Ethernet, but does not
(green)
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 27: 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 28: LED state definitions for theCC-Link IE Field Basic Slave protocol

7.6 EtherCAT Master

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 V4.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 The device is not configured.
(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)
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)
Off The device has no link to the Ethernet.
ACT LED yellow

Ch0 Off This LED is not used.
(off)
Table 29: LED states for the EtherCAT Master protocol

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
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).
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.
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.
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.
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
irregular intervals to indicate low Ethernet activity.
Table 30: LED state definitions for the EtherCAT Master protocol

7.7 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).
General Off INIT: The device is in state INIT.
(off)
name:
COM 0 (green)
Blinking PRE-OPERATIONAL: The device is in PRE-OPERATIONAL state.
(2,5 Hz)
(green)
Single flash SAFE-OPERATIONAL: The device is in SAFE-OPERATIONAL state.
(green)
On OPERATIONAL: The device is in OPERATIONAL state.

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 Link: The device is linked to the Ethernet, but does not send/receive
(green)
On
Ethernet frames.
(green)
Flickering Activity: The device is linked to the Ethernet and sends/receives
(load Ethernet frames.
dependant)
(off)
LED yellow
(off)
Table 31: LED states for the EtherCAT Slave protocol
LED State Beschreibung

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 (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
Table 32: LED state definitions for the EtherCAT Slave protocol

7.8 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
(green)
On Device operational: The device is operating correctly.
status)
General Flashing Standby: The device has not been configured.
name: (green) (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 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) transport class) is established, and an Exclusive Owner connection has not
(green)
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 On The device is linked to the Ethernet.
(green)
(Off)
ACT LED yellow

Ch0 & Ch1 Flickering The device sends/receives Ethernet frames.
(yellow) (load de-
pendant)
(Off)
Off The device does not send/receive Ethernet frames.
Table 33: 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 34: LED state definitions for the EtherNet/IP Scanner protocol

7.9 EtherNet/IP Adapter (Slave)

For the EtherNet/IP Adapter protocol, the communication LEDs MS and NS
as well as the Ethernet LEDs LINK and ACT can assume the states
described below. This description is valid from stack version V3.4 (V3).
MS Duo-LED red/green
(Module
(green)
On Device operational: The device is operating correctly.
status)
General (green)
Flashing (1 Hz) Standby: The device has not been configured.
name:
COM 0 Flashing fast Self-test: The device performs a self-test after power-on. The
(green/red/ green/red/gree following sequence is displayed during the self-test:
green) n
• NS-LED off.
• MS-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).
• NS-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).
Flashing Flashing sequence: The flashing sequence is used to visually
sequence identify the device. The scanner can start the flashing sequence in
(red/green/
red/green/off Identity object 1 of the device. The MS LED and NS LED perform
off)
the flashing sequence simultaneously.
(red)
Flashing (1 Hz) Major recoverable fault: The device has detected a major
recoverable 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
(green)
On
status) connection (any transport class) is established, and an Exclusive
General Owner connection has not timed out.
name::
(green)
Flashing (1 Hz) No connections: An IP address is configured, but no CIP
COM 1
connections are established, and an Exclusive Owner connection
has not timed out.
Flashing fast Self-test: The device performs a self-test after power-on. Refer to
(green/red/ green/red/green the description of the MS LED in the self-test status.
green)
Flashing Flashing sequence: The flashing sequence is used to visually
(red/green/ sequence identify the device. The scanner can start the flashing sequence in
off) red/green/off Identity object 1 of the device. The MS LED and NS LED perform
the flashing sequence simultaneously.
(red)
Flashing (1 Hz) Connection timeout: An IP address is configured, and an
Exclusive Owner connection for which this device is the target has
timed out.
The NS LED 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 grün
(green)
(off)
ACT LED gelb

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

Flashing (1 Hz) The LED turns on and off with a frequency of 1 Hz: “On” for 500 ms, followed by “Off” for 500 ms.
Flashing fast The MS LED or NS LED turns on green "On" for 250 ms, then red "On" for 250 ms, then green
green/red/green "On" (until the test is completed).
Flashing The MS LED and NS LED each turn red "On" for 500 ms, then green "On" for 500 ms, then "Off"
sequence for 500 ms. This flashing sequence is repeated at least 6 times.
red/green/off
Table 36: LED state definitions for the EtherNet/IP Adapter protocol

7.10 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

(green)
(off)
ACT LED yellow

Ch0 & Ch1 Flicker- The device sends/receives Ethernet frames.
(yellow) ing (load
depen-
dant)
(off)
Table 37: 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 38: LED state definitions for the OpenModbusTCP protocol

7.11 POWERLINK-Controlled-Node/Slave
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) On Slave is in ‘Operational’ state
(green)
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 39: 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 40: LED state definitions for the POWERLINK Controlled Node protocol

7.12 PROFINET IO Controller

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 41: PROFINET IO Controller, SYS, COM0 and COM1 LEDs states


LINK LED green
(green)
(off) Off The device has no link to the Ethernet.
RX/TX LED yellow

Ch0 & Ch1 Flickering The device sends/receives Ethernet frames.
(gelb) (load
dependent)
(off) Off The device does not send/receive Ethernet frames.
Table 42: 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:
(1 Hz) “on” for 500 ms, followed by “off” for 500 ms.
Table 43: PROFINET IO Controller, LEDs states definitions

7.13 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 No error
(off)
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
(green)
(off)
RX/TX LED yellow

Ch0 & Ch1 Flickering
(gelb)
The device sends/receives Ethernet frames.
(load de-
pendant)
(off)
Table 44: 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 45: LED state definitions for the PROFINET IO-Device protocol

7.14 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 46: 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 47: LED state definitions for the Sercos Master protocol

7.15 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 48: 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 49: LED state definitions for the Sercos Slave protocol

7.16 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 &
On The device is linked to the Ethernet.
LINK OUT
(green)
Ch1
(off)
ACT IN LED yellow

Ch0 &
Flickering The device sends/receives Ethernet frames.
ACT OUT
(yellow) (load
Ch1
dependant)
(off)
Table 50: 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 51: Definitionen der LED-Zustände für das VARAN-Client-Protokoll

7.17 PROFIBUS DP Master

7.17.1 1 Communication Status LED
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.
cifX with 1 Communication Status LED (current Hardware Revision)
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 52: LED states for the PROFIBUS DP Master protocol – 1 Communication Status LED
(current Hardware Revision)

"on" for 100 ms, followed by "off" for 100 ms.
Flashing The indicator turns on and off in irregular intervals.
acyclic
Table 53: LED state definitions for the PROFIBUS DP Master protocol

7.17.2 2 Communication Status LEDs

For the PROFIBUS DP Master protocol, the communication status LEDs
STA and ERR can assume the states described below. This description is
valid from stack version V2.6.
cifX with 2 Communication Status LEDs (AIFX-DP is connected or for prior Hardware Revisions)
STA LED 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
(off)
Off The ERR LED is off: Device is not switched on or network power is
missing.
The ERR LED is flashing or “on”: Refer to description LED red.
ERR LED red
(red)
Flashing (5 Hz) Communication to at least one Slave is disconnected.
(off)
On Communication to all Slaves is disconnected or another serious error
has occurred.
Redundant Mode: The active Master was not found.
(off)
Off No error: There is no error, respectiveley see description for STA
LED.
Table 54: LED states for the PROFIBUS DP Master protocol – 2 Communication Status
LEDs (AIFX-DP connected or prior Hardware Revision)

Flashing (5 Hz) The LED turns on and off with a frequency of 5 Hz:
"On" for 100 ms, followed by "Ooff" for 100 ms.
Flashing TheLED turns on and off in irregular intervals.
acyclic
Table 55: LED state definitions for the PROFIBUS DP Master protocol

7.18 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 56: LED states for the PROFIBUS DP Slave protocol – 1 Communication Status LED

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 57: LED state definitions for the PROFIBUS DP Slave protocol


For the PROFIBUS DP Slave protocol, the communication status LEDs
STA and ERR can assume the states described below. This description is
cifX with 2 Communication Status LEDs (AIFX-DP is connected or for prior Hardware Revisions)
STA LED green
(green)
On RUN, cyclic communication
(green)
Flashing, Master is in CLEAR state.
cyclic (2 Hz)
(off)
Off LED red is off: Device is not switched on or network power is missing.
LED red is flashing or on: Refer to description LED red.
ERR LED red
(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 No error: There is no error, respectiveley see description for STA
LED.
Table 58: LED states for the PROFIBUS DP Slave protocol – 2 Communication Status LEDs
(AIFX-DP connected or prior Hardware Revision)

Flashing, The indicator turns on and off in irregular intervals, with a frequency
acyclic (1 Hz) of 1 Hz:
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 59: LED state definitions for the PROFIBUS DP Slave protocol

7.19 PROFIBUS MPI Device

For the PROFIBUS MPI protocol, the communication status LED COM can
version V2.4.
cifX with 1 Communication Status LED
(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 60: LED states for the PROFIBUS MPI protocol – 1 Communication Status LED

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:
Table 61: LED state definitions for the PROFIBUS MPI protocol


For the PROFIBUS MPI protocol, the communication status LEDs STA and
ERR can assume the states described below. This description is valid from
stack version V2.4.
cifX with 2 Communication Status LEDs (AIFX-DP is connected)
STA LED green
(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.
ERR LED red
(off)
Table 62: LED states for the PROFIBUS MPI protocol – 2 Communication Status LEDs
(AIFX-DP connected)

Blinking (5 Hz) The indicator turns on and off with a frequency of appr. 5 Hz:
Blinking (0.5 The indicator turns on and off with a frequency of appr. 0.5 Hz:
Hz) “on” for appr. 1000 ms, followed by “off” for appr. 1000 ms.
Table 63: LED state definitions for the PROFIBUS MPI protocol

7.20 CANopen Master

For the CANopen Master protocol, the communication status LED CAN can
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.
(off)
Off RESET: The device is executing a reset or the device has no
configuration.
Table 64: LED states for the CANopen Master protocol – 1 Communication Status LED

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 65: LED state definitions for the CANopen Master protocol


For the CANopen Master protocol, the communication status LEDs RUN
and ERR can assume the states described below. This description is valid
from stack version V2.11.
cifX with 2 Communication Status LEDs (AIFX-CO is connected or for prior Hardware Revisions)
RUN LED green
(green)
(green)
Blinking (2,5 Hz) PREOPERATIONAL: The device is in the PREOPERATIONAL
state.
(green)
(off)
Off LED red is off: RESET: The device is executing a reset or the
device has no configuration.
LED red is flashing or “on”: Refer to description LED red.
ERR LED red
(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)
(off)
Off No error: There is no error, respectiveley see description for
RUN LED.
Table 66: LED states for the CANopen Master protocol – 2 Communication Status LEDs
(AIFX-CO connected or prior Hardware Revision)

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 67: LED state definitions for the CANopen Master protocol

7.21 CANopen Slave

For the CANopen Slave protocol, the communication status LED CAN can
version V3.4.
CAN Duo LED red/green
(green)
(green)
Blinking PREOPERATIONAL: The device is in the PREOPERATIONAL state.
(2.5 Hz)
(green)
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)
(off)
Off RESET: The device is executing a reset or the device has no
configuration.
Table 68: 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 69: LED state definitions for the CANopen Slave protocol


For the CANopen Slave protocol, the communication status LEDs RUN and
ERR can assume the states described below. This description is valid from
stack version V3.4.
cifX with 2 Communication Status LEDs (AIFX-CO is connected or for prior Hardware Revisions)
RUN LED green
(green)
(green)
Blinking PREOPERATIONAL: The device is in the PREOPERATIONAL state.
(2.5 Hz)
(green)
(green)
(10 Hz, detection mode.
alternatively
with ERR LED)
(off)
Off LED red is off: RESET: The device is executing a reset or the device
has no configuration.
LED red is flickering, flashes or “on”: Refer to description LED red.
ERR LED red
(red)
(10 Hz, detection mode.
alternatively
with RUN LED)
(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)
(off)
Off No error: There is no error, respectiveley see description for RUN
LED.
Table 70: States of the CAN LED for the CANopen Slave protocol – 2 Communication
Status LEDs (AIFX-CO connected or prior 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 71: LED state definitions for the CANopen Slave protocol

7.22 DeviceNet Master

For the DeviceNet Master protocol, the communication status LED MNS
can assume the states described below. This description is valid from stack
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 72: 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 73: LED state definitions for the DeviceNet Master protocol

7.23 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 74: 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 75: LED state definitions for the DeviceNet Slave protocol

7.24 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
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 76: LED states for the CC-Link Slave protocol

Device Connections and Switches 104/200
8 Device Connections and Switches

8.1 Ethernet Interface
RJ45 plugs or M12 plugs are used for the Ethernet interface.
• For RJ45 connector, use twisted pair cable of category 5 (CAT5) or
higher, which consists of 4 wires twisted in pairs and has a maximum
transmission rate of 100 MBit/s (CAT5).
• For M12 connector, use Category 5 (CAT5) or higher cable with a
maximum transfer rate of 100 MBit/s (CAT5).
8.1.1 Ethernet Pin Assignment at the RJ45 Socket

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 34: 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 77: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX
Note: The RJ45 socket is only for use in LAN, not for telecommunication
circuits.

8.1.2 Ethernet Pin Assignment at the M12 Socket

Real-Time Ethernet 2 x M12 plug connections (to DIN EN 61076 2 101/ IEC
61076 2 101), D-coded socket.
Note: The device supports the Auto Crossover function. Due to this fact
RX and TX can be switched. The following figure shows the M12 standard
pin assignment.
Figure 35: Ethernet Pin Assignment at the M12 Socket for AIFX-RE\M12 (D coded)
Pin Signal Meaning

1 TX+ Transmit Data +
2 RX+ Receive Data +
3 TX– Transmit Data –
4 RX– Receive Data –
PE Metal screw connection
Table 78: Ethernet Pin Assignment M12 Socket for AIFX-RE\M12

8.1.3 Ethernet Connection Data

Medium RJ45 2 x 2 Twisted-Pair copper cable, CAT5 (100 MBit/s)
M12 2 x cable, CAT5 (100 MBit/s)
Length of cable max. 100 m
Transmission 10 MBit/s/100 MBit/s
rate
Table 79: Ethernet Connection Data
8.1.4 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
CC-Link IE Field-Basic- forbidden star topology, with Layer 2 switch
Slave (must support 100 MBit/s, 1 GBit/s support is optional)
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 80: Use of Hubs and Switches
*Instead of hubs and switches VARAN uses splitter. [3]

8.2 PROFIBUS Interface

Isolated RS-485 interface:
Figure 36: 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 81: PROFIBUS Interface, X400
8.3 CANopen Interface

Isolated ISO 11898 interface:
Figure 37: 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 82: CANopen Interface, X400

8.4 DeviceNet Interface

Isolated ISO 11898 interface:
Figure 38: 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 83: DeviceNet Interface, X360
8.5 CC-Link Interface

Isolated RS-485 interface:
Figure 39: 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 84: CC-Link Interface

8.6 Mini-B USB Connector (5 Pin)

Important! When booting the host PC the USB cable must be connected
to the PC card cifX!
The host PC does not boot when a USB cable is connected to the PC card
cifX installed in the PC.
The Mini-B USB connector is provided for the following PC cards cifX:
CIFX 104-RE, CIFX 104-DP, CIFX 104-CO, CIFX 104-DN,
CIFX 104-RE-R, CIFX 104-DP-R, CIFX 104-CO-R, CIFX 104-DN-R
In addition a Mini-B USB connector will be available for the following PC
cards cifX if the AIFX-DIAG is connected to the PC card cifX:
CIFX 104-RE\F*, CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F,
CIFX 104-CC\F,
CIFX 104-RE-R\F*, CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F
Note! *From the hardware revision 5 of the PC cards CIFX 104-RE\F and
CIFX 104-RE-R\F if the diagnostic AIFX-DIAG detached network interface
is connected, the Mini-B USB connector on the AIFX-DIAG can be used.
Figure 40: Mini-B USB Connector (5 Pin)
Pin Name Description

1 USB_EXT USB Bus Power (+5 V dc, supplied externally)
2 D- Data -
3 D+ Data +
4 ID Not connected
5 GND Ground
Table 85: Pin Assignment Mini-B USB Connector
8.7 Rotary Switch Device Address

The Rotary Switch Device Address at the PC cards
CIFX 104-RE, CIFX 104-RE-R, CIFX 104-RE\F, CIFX 104-RE-R\F,
CIFX 104-DP, CIFX 104-DP-R, CIFX 104-DP\F, CIFX 104-DP-R\F,
CIFX 104-CO, CIFX 104-CO-R, CIFX 104-CO\F, CIFX 104-CO-R\F,
CIFX 104-DN, CIFX 104-DN-R, CIFX 104-DN\F, CIFX 104-DN-R\F,
CIFX 104-CC\F
currently is unassigned. The Slave address setting is done via the
configuration software.

8.8 Cable Connector

8.8.1 Pin Assignment for Cable Connector Ethernet X4 or X304
Only for CIFX 104-RE\F (X304), CIFX 104-RE-R\F (X4).
Pin Assignment for Cable Connector Ethernet X4 or X304 – Cable 20 pin
Ethernet and Status LEDs:
Pin Signal
1 GND
2 +3V3 Analog
3 STA0_green (RE LED COM 0)
4 STA0_red (RE LED COM 0)
5 XM0_TX (for M12 variants not assigned)
6 STA1_green (RE LED COM 1)
7 CH0_LINK
8 CH0_ACTIVITY
9 /RSTOUT
10 STA1_red (RE LED COM 1)
11 CH0_TXP
12 CH0_TXN
13 CH0_RXP
14 CH0_RXN
15 CH1_TXP
16 CH1_TXN
17 CH1_RXP
18 CH1_RXN
19 CH1_LINK
20 CH1_ACTIVITY
Table 86: Pin Assignment for Cable Connector Ethernet X4 or X304
Cable Connector Ethernet X4 or X304:
Figure 41: Cable Connector Ethernet X4 or X304; 1x20 Pins for CIFX 104-RE\F, CIFX 104-
RE-R\F

8.8.2 Pin Assignment for Cable Connector Fieldbus X3, X304, X4

Only for
CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F: (X304);
CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F: (X4).
Pin Assignment for Cable connector Fieldbus X3, X304 or X4,
Cable 10 pin Fieldbus:
Pin Signal
1 GND
2 +3V3 Analog
3 I2C_CLK/PIO 4
4 I2C_DATA/ PIO 5
5 XMAC2_TX
6 XMAC2_RX
7 XMAC2_IO0
8 XMAC2_IO1
9 /RSTOUT
10 (not used)
Table 87: Pin Assignment for Cable connector Fieldbus X3, X304 or X4
8.8.3 Pin Assignment for Cable Connector DIAG

Only for CIFX 104-RE\F (X303), CIFX 104-RE-R\F (X3),
CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F: (X303)
Pin Assignment for Cable connector DIAG X3 or X303 -
Cable 12 pin USB + Status LEDs
Pin Signal (Feldbus) Signal (Ethernet)
1 GND GND
2 +3V3 +3V3
3 STA2 (FB LED COM 0) STA2 (not used)
4 STA3 (FB LED COM 1) STA3 (not used)
5 USB_POS USB_POS
6 USB_NEG USB_NEG
7 RDYn RDYn
8 RUNn RUNn
9 STA0_green (not used) STA0_green (RE LED COM 0)
10 STA0_red (not used) STA0_red (RE LED COM 0)
11 STA1_green (not used) STA1_green (RE LED COM 1)
12 STA1_red (not used) STA1_red (RE LED COM 1)
Table 88: Pin Assignment for Cable connector DIAG X3 or X303

8.8.4 Pin Assignment Cable Connector Ethernet X1, AIFX-RE

Only for AIFX-RE; Pin Assignment for Cable Connector Ethernet X1 -
Cable 20 pin Ethernet and Status LEDs
Pin Name Description Type
1 GND Ground Power
2 3V3 3.3V Power Power
3 LED COM0- LED COM0 (green) Input
GREEN
4 LED COM0- LED COM0 (red) Input
RED
5 - (not used) NC
6 LED COM1- LED COM1 (green) Input
GREEN
7 LED LINK0 LED LINK0 (yellow) Input
8 LED ACT0 LED ACT0 (green) Input
9 RSTOUT# Reset out Input
10 LED COM1- LED COM01 (red) Input
RED
11 CH0_TXP Channel 0 TX+ Input
12 CH0_TXN Channel 0 TX- Input
13 CH0_RXP Channel 0 RX+ Output
14 CH0_RXN Channel 0 RX- Output
15 CH1_TXP Channel 1 TX+ Input
16 CH1_TXN Channel 1 TX- Input
17 CH1_RXP Channel 1 RX+ Output
18 CH1_RXN Channel 1 RX- Output
19 LED LINK1 LED LINK1 (yellow) Input
20 LED ACT1 LED ACT1 (green) Input
Table 89: Pin Assignment for Cable Connector Ethernet X1, AIFX-RE (Hardware-Rev. 2)
Cable Connector Ethernet X1:
Figure 42: Cable Connector Ethernet X1; 1x20 Pins, AIFX-RE

8.8.5 Pin Assignment Cable Connector X2, AIFX-RE\M12

Only for AIFX-RE\M12; Pin Assignment for Cable Connector Ethernet X2 -
Cable 20 pin Ethernet and Status LEDs
Pin Signal Pin Signal
1 CH1_ACTIVITY (EN LED YEL1) 11 STA1_red (RE LED COM1)
2 CH1_LINK (EN LED GRN1) 12 /RSTOUT
3 CH1_RXN 13 CH0_ACTIVITY (EN LED YEL0)
4 CH1_RXP 14 CH0_LINK (EN LED GRN0)
5 CH1_TXN 15 STA1_green (RE LED COM1)
6 CH1_TXP 16 (unbelegt)
7 CH0_RXN 17 STA0_red (RE LED COM0)
8 CH0_RXP 18 STA0_green (RE LED COM0)
9 CH0_TXN 19 +3V3 Analog
10 CH0_TXP 20 GND
Table 90: Pin Assignment for Cable Connector Ethernet X2, AIFX-RE\M12
Cable Connector Ethernet X2:
Figure 43: Cable Connector Ethernet X2; 1x20 Pins, AIFX-RE\M12

8.8.6 Pin Assignment Cable Connector LED Signals X3, AIFX-RE\M12

Only for AIFX-RE\M12; Pin Assignment for Cable Connector LED Signals
X3 - Cable 10 pin Ethernet and Status LEDs
Pin Signal
1 CH0_LINK_E (EN LED GRN0)
2 CH0_ACTIVITY_E (EN LED YEL0)
3 CH1_LINK_E (EN LED GRN1)
4 CH1_ACTIVITY_E (EN LED YEL1)
5 STA0_green (RE LED COM0)
6 STA0_red (RE LED COM0)
7 STA1_green (RE LED COM1)
8 STA1_red (RE LED COM1)
9
GND
10
Table 91: Pin Assignment for Cable Connector LED Signals X3, AIFX-RE\M12
Cable Connector LED Signals X3:
Figure 44: Cable Connector LED Signals X3; 1x10 Pins, AIFX-RE\M12
Note: The outputs on the cable connector LED signals X3 can drive max.
5 mA. This means that the maximum permissible current per external LED
is 5 mA. If this maximum current is not sufficient, an external driver is
required previous to the LED.

8.8.7 Pin Assignment Cable Connector Fieldbus X1, AIFX-DP

Pin assignment for cable connector fieldbus X1, AIFX-DP, 10-pin cable
1 GND Ground Power
2 3V3 3,3V Power Power
3 I2C_SCL I2C clock signal Input
4 I2C_SDA I2C data signal Input / Output
5 TX Fieldbus transmit Input
6 RX Fieldbus receive Output
7 EN_PB Enable PROFIBUS Input / Output
8 - (not used) NC
10 - (not used) NC
Table 92: Pin Assignment for Cable Connector fieldbus X1, AIFX-DP (Hardware Rev. 2)
8.8.8 Pin Assignment Cable Connector Fieldbus X1, AIFX-CO

Pin assignment for cable connector fieldbus X1, AIFX-CO, 10-pin cable
1 GND Ground Power
7 - (not used) NC
8 - (not used) NC
10 - (not used) NC
Table 93: Pin Assignment for Cable Connector fieldbus X1, AIFX-CO (Hardware Rev. 2)

8.8.9 Pin Assignment Cable Connector Fieldbus X1, AIFX-DN

Pin assignment for cable connector fieldbus X1, AIFX-DN, 10-pin cable
1 GND Ground Power
7 PF_DN Power fail DeviceNet Input / Output
8 - (not used) NC
10 - (not used) NC
Table 94: Pin Assignment for Cable Connector fieldbus X1, AIFX-DN (Hardware Rev. 3)
8.8.10 Pin Assignment Cable Connector Fieldbus X1, AIFX-CC
Pin assignment for cable connector fieldbus X1, AIFX-CC, 10-pin cable
1 GND Ground Power
7 EN_CC Enable CC-Link Input / Output
8 - (not used) NC
10 - (not used) NC
Table 95: Pin Assignment for Cable Connector fieldbus X1, AIFX-CC (Hardware Rev. 2)

8.9 Cable for detached Network Interfaces AIFX
8.9.1 Cable for AIFX-RE or AIFX-RE\M12

Note: If the detached network interfaces Ethernet (AIFX-RE) or Ethernet
M12 (AIFX-RE\M12) are ordered without a basic card, the connecting
cable must be ordered separately.
Cable 1 for AIFX Part No Note
CAB-AIFX-RE 4.100.102 Connection to cable connector Ethernet with 1 x 20 pins,
cable length = 15 cm
Table 96: Cable for connecting the detached Network Interfaces AIFX-RE or AIFX-RE\M12
8.9.2 Optional Cable Length 30 cm for PC-cards cifX with AIFX-DP,

AIFX-CO or AIFX-DN
For the connection of the detached network interfaces fieldbus (AIFX-DP,
AIFX-CO or AIFX-DN) for the PC cards cifX with the label "\F" in the device
name, cables with a length of 15 cm are supplied as standard.
The PC cards cifX fieldbus with AIFX-DP, AIFX-CO or AIFX-DN can be
ordered with an optional 30 cm cable to connect the detached network
interfaces fieldbus (AIFX-DP, AIFX-CO or AIFX-DN). See also note 8 in
Table 6: Reference on Hardware PC Cards cifX on page 17 or Table 7:
Reference on Hardware AIFX detached Network Interfaces on page 17. In
this case the part number is extended by "/30".
1
UL Certification: The cable CAB-AIFX-RE is certified according to UL 508. UL-
File-Nr. E221530
The cable CAB-AIFX-RE with 1 x20 pins for CIFX 104-RE\F and their variants is
currently only available as 15cm version.
8.10 SYNC Connector (Pin-Assignment, Hardware/Firmware)

8.10.1 Pin Assignment SYNC Connector, X51 (CIFX 80 90 104C)
Only for CIFX 104-RE, CIFX 104-RE-R, CIFX 104-RE\F, CIFX 104-RE-R\F.
Pin Signal
1 GND
2 IO_SYNC0
3 IO_SYNC1
Table 97: Pin Assignment for SYNC Connector, X51
8.10.2 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 on page 118.)
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)
Max. Cable Recommendation: Max. 50 mm
Length Note: Take EMC into consideration for the cable laying
Table 98: SYNC Connector: SYNC Signal, Connector, Max. Cable Length
8.10.3 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 99: Meaning of the SYNC Signals for each Protocol

8.11 Pin Assignment at the PC/104 Bus

8.11.1 Overview
For the PC cards cifX PC/104 the table below gives an overview about the pin
assignment at the PC/104 bus.
cifX Hardware PC/104 Pin Assignment at the PC/104 Bus PC/104
Revision Bus [Pins] Specification
according Compare Section, page
to the
standard
CIFX 104-RE 2 104 yes Pin Assignment for PC/104 Bus, 120 [bus spec 8]
CIFX 104-RE-R 2
CIFX 104-RE\F 2
CIFX 104-RE-R\F 2
CIFX 104-RE\F\M12 3
CIFX 104-RE-R\F\M12 3
CIFX 104-DP 2
CIFX 104-DP-R 2
CIFX 104-DP\F 2
CIFX 104-DP-R\F 2
CIFX 104-CO 2
CIFX 104-CO-R 2
CIFX 104-CO\F 2
CIFX 104-CO-R\F 2
CIFX 104-DN 2
CIFX 104-DN-R 2
CIFX 104-DN\F 2
CIFX 104-DN-R\F 2
CIFX 104-CC\F 2
Table 100: Pin Assignment at the PC/104 Bus

8.11.2 Pin Assignment for PC/104 Bus

Only for:
CIFX 104-RE, CIFX 104-RE-R ,
CIFX 104-RE\F, CIFX 104-RE-R\F ;
CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12
The used control signals of the PC/104 bus are given in the tables below.
Pin Assignment for PC/104-Bus, X1

Pin (X1) A B
1 GND
2 SD7 RESET
3 SD6 +5V
4 SD5 IRQ9
5 SD4
6 SD3
7 SD2
8 SD1
9 SD0
2
10 IOCHRDY GND
11 AEN SMEMW
12 SA19 SMEMR
13 SA18
14 SA17
15 SA16
16 SA15
17 SA14
18 SA13
19 SA12
20 SA11
21 SA10 IRQ7
22 SA9 IRQ6
23 SA8 IRQ5
24 SA7 IRQ4
25 SA6 IRQ3
26 SA5
27 SA4
28 SA3
29 SA2 +5V
30 SA1
31 SA0 GND
32 GND GND
Table 101: Pin Assignment for PC/104-Bus, X1 (Control Signals used on the 8 Bit
Connector)
2
Differs from the standard [bus spec 9, page B-2].
Important: Avoid dual-port memory access errors

It is mandatory that the host CPU always uses the IOCHNRDY (pin A10)
signal, otherwise these results in wrong data read from the dual-port
memory or dual-port memory write accesses are being ignored.
- The maximum value for accesses can not be specified.
- For maximum performance, the IOCHNRDY signal must always be
evaluated by the host CPU.
- If you use a host CPU that can not use the IOCHNRDY (A10) signal,
then contact our technical support.
Pin Assignment for PC/104-Bus, X2

Pin (X2) C D
0 GND GND
1 SBHE MEMCS16
2
3 IRQ10
4 IRQ11
5 IRQ12
6 IRQ15
7 IRQ14
8
9
10
11 SD8
12 SD9
13 SD10
14 SD11
15 SD12
16 SD13 +5V
17 SD14
18 SD15 GND
19 GND
Table 102: Pin Assignment for PC/104-Bus, X2 (Used Control Signals on the Expansion
Connector)
The pin assignment described in Table 101 and Table 102 originates from the
standard [bus spec 8, page B-2] (refer to section Reference PC/104
Specification on page 176).

Technical Data 122/200
9 Technical Data
9.1 Technical Data PC Cards cifX
Note: All technical data are temporarily and can be altered without notice.
9.1.1 CIFX 104-RE, CIFX 104-RE-R

CIFX 104-RE, Parameter Value
CIFX 104-RE-R
Part Name CIFX 104-RE CIFX 104-RE-R
Part No. 1278.100 1279.100
Description PC Card cifX PC/104 for Real-Time Ethernet Master or
Slave; (for CIFX 104-RE-R connectors at the right side)
Function Communication Interface with PC/104 and Ethernet
interface
Communication Type netX 100 processor
Controller
Integrated Memory RAM 8 MB SDRAM
FLASH 4 MB serial Flash EPROM
Size of the Dual-Port Memory 16 KByte
System Interface Bus Type PC/104, according to [bus spec 8], refer to section
Overview, page 119.
Transmission Rate 33 MHz
Data Access DPM
Width for the data access to the 8 Bit or 16 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),
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 104.
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

CIFX 104-RE, Parameter Value
CIFX 104-RE-R
Diagnosis Interface USB Interface Mini B USB Plug (5 pin), refer to section Mini-B USB
Connector (5 Pin), page 109.
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 Diagnosis with LEDs, page 70.
Power supply Supply Voltage +5 V dc ±5 %, refer to section Power Supply and Host
Interface, page 48.
Current consumption at 5 V 500 mA (maximum)
Connector Via PC/104 Bus
Operation Rotary Switch Device Address Is currently unassigned. Refer to section Rotary Switch
Device Address on page 109.
Environmental Operating temperature range* 0 °C ... +70 °C
Conditions
*Air flow during measurment 0,5m/s
Storage temperature range -40 °C ... +85 °C
Humidity 10 … 95% relative humidity, no condensation permitted
Device Dimensions (L x W x H) 97 x 91 x 24.3 mm
Mounting/Installation PC/104 Slot (5 V), refer to section Slot for the PC Cards
cifX PC/104, page 48.
RoHS Yes
Compliance with EMC CE Sign Yes
UKCA Sign Yes
Emission EN 55011+ A1, CISPR 11, Class A /
BS EN 55011+ A1, CISPR 11, Class A (Radio disturbance
characteristics - Limits and methods of measurement)
Immunity EN 61000-4-2 / BS EN 61000-4-2
(Electrostatic discharge test)
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
(Radiated, radio-frequency, electromagnetic field test)
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
(Burst Electrical fast transients/burst test)
EN 61000-4-5 / BS EN 61000-4-5 (Surge test)
EN 61000-4-6 / BS EN 61000-4-6 (to conducted
disturbances, induced by radio- frequency fields)
EN 61000-4-8 / BS EN 61000-4-8
(power frequency magnetic field test)
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
(for industrial environments)
Configuration Configuration Software SYCON.net
Master and Slave
Configuration Software Slave netX Configuration Tool
Table 103: Technical Data CIFX 104-RE, CIFX 104-RE-R

9.1.2 CIFX 104-RE\F, CIFX 104-RE-R\F and Variants

CIFX 104-RE\F Parameter Value
and Variants
Part Name, Part No. CIFX 104-RE\F 1278.101
CIFX 104-RE-R\F 1279.101
CIFX 104-RE\F\M12 1278.121
CIFX 104-RE-R\F\M12 1279.121
Description PC Card cifX PC/104 for Real-Time Ethernet Master or
Slave composed of:
- Basic card CIFX 104-RE\F or CIFX 104-RE-R\F* with
cable connector Ethernet X4 (X304) and cable connector
DIAG X3 (X303) (*connectors at the right side)
- Ethernet detached network interface (AIFX-RE) or
- Ethernet M12 detached network interface (AIFX-RE\M12)
and
- diagnostic detached network interface (AIFX-DIAG).
Function Communication Interface with PC/104 and Ethernet
interface
Controller
Overview, page 119.
Data Access 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),
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 104.
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
Ethernet detached network AIFX-RE, refer to section AIFX-RE, page 136 or AIFX-
interface RE\M12, refer to section AIFX-RE\M12, page 138.
Important! Operating the PC cards CIFX 104-RE\F or CIFX 104-
RE-R\F requires proper connection of the Ethernet detached
network interface (AIFX-RE) or the Ethernet M12 detached

CIFX 104-RE\F Parameter Value
and Variants
network interface (AIFX-RE\M12) to the basic card!
Connector AIFX-RE or Cable Connector Ethernet X4 (X304)
AIFX-RE\M12 (JST SM20B-SRSS-TB(LF)(SN), Pitch 1,0 mm)
Diagnosis Interface Diagnostic detached network AIFX-DIAG, refer to section AIFX-DIAG, page 143.
interface Note: If the diagnostic AIFX-DIAG detached network
interface is connected to the PC card CIFX 104-RE\F or
CIFX 104-RE-R\F, the Mini-B USB connector on the
AIFX-DIAG can be used beginning with the hardware
revision 5 of the PC card cifX.
Connector AIFX-DIAG Cable Connector DIAG X3 (X303)
(JST 12FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm)
For LEDs at AIFX-RE, refer to section AIFX-RE, page 136
or AIFX-RE\M12, refer to section AIFX-RE\M12, page 138.
Interface, page 48.
Current at 5 V 500 mA (maximum)
Conditions
RoHS Yes
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 104: Technical Data CIFX 104-RE\F, CIFX 104-RE-R\F, CIFX 104-RE\F\M12, CIFX
104-RE-R\F\M12

9.1.3 CIFX 104-DP, CIFX 104-DP-R

CIFX 104-DP, Parameter Value
CIFX 104-DP-R
Part Name CIFX 104-DP CIFX 104-DP-R
Part No. 1278.410 1279.410
Description PC Card cifX PC/104 PROFIBUS DP Master or Slave and
PROFIBUS MPI Device;
(for CIFX 104-DP-R connectors at the right side)
Function Communication Interface with PC/104 and fieldbus
interface PROFIBUS
Controller
Overview, page 119.
Data Access DPM
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, refer to section PROFIBUS Interface, page 107.
Galvanic Isolation isolated
Connector DSub female Connector, 9 pin
The meaning of the COM LED depends on the loaded
firmware. Refer to chapter Diagnosis with LEDs, page 70.
Interface, page 48.
Current at 5 V 500 mA (maximum)
Environmental Operating temperature range* -20 °C ... +70 °C
Conditions
RoHS Yes

CIFX 104-DP, Parameter Value
CIFX 104-DP-R
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 105: Technical Data CIFX 104-DP, CIFX 104-DP-R
9.1.4 CIFX 104-DP\F, CIFX 104-DP-R\F

CIFX 104-DP\F, Parameter Wert
CIFX 104-DP-R\F
Part Name CIFX 104-DP\F CIFX 104-DP-R\F
Part No. 1278.411 1279.411
Description PC Card cifX PC/104 PROFIBUS DP Master or Slave and
PROFIBUS MPI Device composed of:
- Basic card CIFX 104-FB\F or CIFX 104-FB-R\F* with
cable connector Fieldbus X4 (X304) and cable connector
- PROFIBUS detached network interface (AIFX-DP) and
interface PROFIBUS
Controller
Overview, page 119.
Data Access DPM
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,
CIFX 104-DP\F, Parameter Wert
CIFX 104-DP-R\F
3 MBit/s, 6 MBit/s, 12 MBit/s
Interface Type RS 485, refer to section PROFIBUS Interface page 107.
PROFIBUS detached network AIFX-DP, refer to section AIFX-DP page 139.
interface Important! Operating the PC cards CIFX 104-DP\F or CIFX 104-
DP-R\F requires proper connection of the PROFIBUS detached
network interface (AIFX-DP) to the basic card!
Connector AIFX-DP Cable Connector Fieldbus X4 (X304)

interface
For LEDs at AIFX-DP, refer to section AIFX-DP page 139.
Interface, page 48.
Conditions
RoHS Yes
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 106: Technical Data CIFX 104-DP\F, CIFX 104-DP-R\F

9.1.5 CIFX 104-CO, CIFX 104-CO-R

CIFX 104-CO, Parameter Value
CIFX 104-CO-R
Part Name CIFX 104-CO CIFX 104-CO-R
Part No. 1278.500 1279.500
Description PC Card cifX PC/104 CANopen Master or Slave;
(for CIFX 104-CO-R connectors at the right side)
interface CANopen
Controller
Overview, page 119.
Data Access DPM
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 107.
Galvanic Isolation isolated (optically isolated)
Connector DSub male Connector, 9 pin
CAN CANopen Status (duo LED)
The meaning of the CAN LED is depending on loaded
Interface, page 48.
Conditions
RoHS Yes

CIFX 104-CO, Parameter Value
CIFX 104-CO-R
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 107: Technical Data CIFX 104-CO, CIFX 104-CO-R
9.1.6 CIFX 104-CO\F, CIFX 104-CO-R\F

CIFX 104-CO\F, Parameter Value
CIFX 104-CO-R\F
Part Name CIFX 104-CO\F CIFX 104-CO-R\F
Part No. 1278.501 1279.501
Description PC Card cifX PC/104 CANopen Master or Slave
composed of:
- CANopen detached network interface (AIFX-CO) and
interface CANopen
Controller
Overview, page 119.
Data Access DPM
CANopen Supported communication CANopen Master,
Communication standard/ protocol (determined by CANopen Slave
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 104-CO\F, Parameter Value
CIFX 104-CO-R\F
Interface Type ISO-11898, refer to section CANopen Interface, page 107.
CANopen detached network AIFX-CO, refer to section AIFX-CO, page 140.
interface Important! Operating the PC cards CIFX 104-CO\F or CIFX 104-
CO-R\F requires proper connection of the CANopen detached
network interface (AIFX-CO) to the basic card!
Connector AIFX-CO Cable Connector Fieldbus X4 (X304)
interface
For LEDs at AIFX-CO, refer to section AIFX-CO, p. 140.
Interface, page 48.
Conditions
RoHS Yes
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 108: Technical Data CIFX 104-CO\F, CIFX 104-CO-R\F

9.1.7 CIFX 104-DN, CIFX 104-DN-R

CIFX 104-DN, Parameter Value
CIFX 104-DN-R
Part Name CIFX 104-DN CIFX 104-DN-R
Part No. 1278.510 1279.510
Description PC Card cifX PC/104 DeviceNet Master or Slave;
(for CIFX 104-DN-R connectors at the right side)
interface DeviceNet
Controller
Overview, page 119.
Data Access DPM
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 108.
Galvanic Isolation isolated (optically isolated)
Connector CombiCon male Connector, 5-polig
MNS Module network status (duo LED)
The meaning of the MNS LED is depending on loaded
Interface, page 48.
Conditions
RoHS Yes

CIFX 104-DN, Parameter Value
CIFX 104-DN-R
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 109: Technical Data CIFX 104-DN, CIFX 104-DN-R
9.1.8 CIFX 104-DN\F, CIFX 104-DN-R\F

CIFX 104-DN\F, Parameter Value
CIFX 104-DN-R\F
Part Name CIFX 104-DN\F CIFX 104-DN-R\F
Part No. 1278.511 1279.511
Description PC Card cifX PC/104 DeviceNet Master or Slave
composed of:
- DeviceNet detached network interface (AIFX-DN)and
interface DeviceNet
Controller
Overview, page 119.
Data Access DPM
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,

CIFX 104-DN\F, Parameter Value
CIFX 104-DN-R\F
refer to section DeviceNet Interface, page 108.
DeviceNet detached network AIFX-DN, refer to section AIFX-DN, page 141.

interface Important! Operating the PC cards CIFX 104-DN\F or CIFX 104-
DN-R\F requires proper connection of the DeviceNet detached
network interface (AIFX-DN) to the basic card!
Connector AIFX-DN Cable Connector Fieldbus X4 (X304)
interface
For LED at AIFX-DN, refer to section AIFX-DN, p. 141.
Interface, page 48.
Conditions
RoHS Yes
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Master and Slave
Table 110: Technical Data CIFX104C-DN\F, CIFX 104-DN-R\F

9.1.9 CIFX 104-CC\F
CIFX 104-CC\F Parameter Value
Part Name CIFX 104-CC\F
Part No. 1278.741
Description PC Card cifX PC/104 CC-Link Slave composed of:
- Basic card CIFX 104-FB\F with cable connector Fieldbus
X4 and cable connector DIAG X3,
- CC-Link detached network interface (AIFX-CC) and
interface CC-Link
Controller
Overview, page 119.
Data Access DPM
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
Interface Type RS-485, refer to section CC-Link Interface, page 108.
CC-Link detached network AIFX-CC, refer to section AIFX-CC page 142.

interface Important! Operating the PC cards CIFX 104-CC\F requires
proper connection of the CC-Link detached network interface
(AIFX-CC) to the basic card!
Connector AIFX-CC Cable Connector Fieldbus X4
interface
Connector AIFX-DIAG Cable Connector DIAG X3
For LEDs at AIFX-CC, refer to section AIFX-CC page 142.
Interface, page 48.
Conditions
RoHS Yes

CIFX 104-CC\F Parameter Value
UKCA Sign Yes
Immunity EN 61000-4-2 / BS EN 61000-4-2
EN 61000-4-3 + A1 + A2 / BS EN 61000-4-3 + A1 + A2
EN 61000-4-4 + A1 / BS EN 61000-4-4 + A1
EN 61000-4-8 / BS EN 61000-4-8
EN 61000-6-2 + B1 / BS EN 61000-6-2 + B1
Configuration Configuration Software SYCON.net or netX Configuration Tool
Table 111: Technical Data CIFX104C-CC\F
9.1.10 AIFX-RE
AIFX-RE Parameter Value
Part Name AIFX-RE
Part No. 2800.100
Description Ethernet detached network interface
for the PC cards CIFX 104-RE\F, CIFX 104-RE-R\F
Interface Connector Cable Connector Ethernet X1
PC Card cifX (JST SM20B-SRSS-TB(LF)(SN), Pitch 1.0 mm)
Ethernet Interface Galvanic Isolation isolated
Connector 2* RJ45 Socket
Display LED Display (on the reverse side The meaning of the following LEDs depends on the loaded
of the device) firmware::
LED yellow at RJ45Ch0 and RJ45Ch1,
for Ethernet Link status, Ethernet Activity
LED green
status and additional status
Power supply Connector Cable Connector Ethernet X1
Conditions
Storage temperature range From hardware revision 3: -40 °C ... +85 °C
Hardware revision 1 and 2: 0 °C ... +70 °C
Environment For UL compliant usage:
The device must be used in a pollution degree 2
environment.
Device Dimensions (L x W x H) 30,7 x 42,3 x 18,5 mm (H = width of the front panel)

AIFX-RE Parameter Value
Mounting/Installation At the basic cards CIFX 104-RE\F, CIFX 104-RE-R\F:
Cable Connector Ethernet X4 (X304)
RoHS Yes
UKCA Sign Yes
Emission, Immunity Tested together with the corresponding basic card cifX.
UL Certification The device is certified according UL-File-Nr. E221530
to UL 508
Table 112: Technical Data AIFX-RE

9.1.11 AIFX-RE\M12
AIFX-RE\M12 Parameter Value
Part Name, Part No. AIFX-RE\M12 2800.101
Description Ethernet detached network interface for the PC cards
CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12
Interface Connector Cable Connector Ethernet X2
PC Card cifX (JST SM20B-SRSS-TB(LF)(SN), Pitch 1.0 mm)
Ethernet Interface Galvanic Isolation isolated
Connector 2* M12 Socket
Display LED Display (via lightpipe) The meaning of the following LEDs depends on the loaded
Alternative use: firmware:
1. LED displays via the COM 0 LED Communication Status 0 (duo LED)
lightpipe COM 1 LED Communication Status 1 (duo LED)
or LED yellow Ch0 and Ch1 Ethernet Link status,
2. LED signals via Ethernet Activity status and additional
LED green
cable connector status
LED Signals X3 Refer to chapter Diagnosis with LEDs, page 70.
Cable connector LED Signals X3 Signals for the communication LEDs COM0 and COM1
(each green/red), or the Ethernet LEDs Ch0 and Ch1
Ethernet link status (green), Ethernet activity status
(yellow) and other statuses green or yellow. The meaning
of the LEDs connected via the signals depends on the
loaded firmware.
For pin assignment of the LED signals see section Pin
Assignment Cable Connector LED Signals X3, AIFX-
RE\M12 on page 114.
Maximum current consumption for the individual LEDs:
5 mA
Power supply Connector Cable Connector Ethernet X2
Conditions
*Air flow during measurment 0,5 m/s
Device Dimensions (L x W x H) 60 x 36 x 15,5 mm
Mounting/Installation At the basic cards CIFX 104-RE\F, CIFX 104-RE-R\F:
Cable Connector Ethernet X304 (X4)
RoHS Yes
UKCA Sign Yes
Emission, Immunity Tested together with the corresponding basic cards cifX.
Table 113: Technical Data AIFX-RE\M12

9.1.12 AIFX-DP
AIFX-DP Parameter Value
Part Name AIFX-DP
Part No. 2800.400
Description PROFIBUS detached network interface for the PC cards
CIFX 104-DP\F, CIFX 104-DP-R\F
Interface Connector Cable Connector Fieldbus X1
PC Card cifX (JST 10FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm)
PROFIBUS Interface Galvanic Isolation isolated
Connector DSub female Connector, 9 pin
of the device) firmware:
ERR LED Error status (red)
STA LED Status (green)
For PROFIBUS MPI the STA LED is not used.
Power supply Connector Cable Connector Fieldbus X1
Conditions
environment.
Device Dimensions (L x W x H) 17 x 31 x 18,5 mm (H = width of the front panel)
Mounting/Installation At the basic cards CIFX 104-FB\F, CIFX 104-FB-R\F:
Cable Connector Fieldbus X4 (X304)
RoHS Yes
UKCA Sign Yes
to UL 508
Table 114: Technical Data AIFX-DP

9.1.13 AIFX-CO
AIFX-CO Parameter Value
Part Name AIFX-CO
Part No. 2800.500
Description CANopen detached network interface for the PC cards
CIFX 104-CO\F, CIFX 104-CO-R\F
CANopen Interface Galvanic Isolation isolated (optically isolated)
Connector DSub male Connector, 9 pin
of the device) firmware::
ERR LED Error status (red)
RUN LED Run (green)
Conditions
environment.
Device Dimensions (L x W x H) 17 x 31 x 18,5 mm (H = width of the front panel)
RoHS Yes
UKCA Sign Yes
Emission, Immunity Tested together with the corresponding basic card cifX..
to UL 508
Table 115: Technical Data AIFX-CO

9.1.14 AIFX-DN
AIFX-DN Parameter Value
Part Name AIFX-DN
Part No. 2800.510
Description DeviceNet detached network interface for the PC cards
CIFX 104-DN\F, CIFX 104-DN-R\F
DeviceNet Interface Galvanic Isolation isolated (optically isolated)
Display LED Display (on the reverse side MNS Module network status (duo LED)
of the device)
The meaning of the MNS LED is depending on loaded
Conditions
environment.
Device Dimensions (L x W x H) 23,7 x 31 x 18,5 mm (L = 23,7, without CombiCon male
Connector; H = width of the front panel)
RoHS Yes
UKCA Sign Yes
to UL 508
Table 116: Technical Data AIFX-DN

9.1.15 AIFX-CC
AIFX-CC Parameter Value
Part Name AIFX-CC
Part No. 2800.730
Description CC-Link detached network interface for the PC card CIFX
104-CC\F
CC-Link Interface Galvanic Isolation isolated (optically isolated)
Display LED Display (on the reverse side L RUN LED L Run (Duo-LED)
of the device)
L ERR LED L Error (Duo-LED)
Conditions
Device Dimensions (L x W x H) 43,2 x 31 x 18,5 mm (L = 43,2, without CombiCon male
Connector; H = width of the front panel)
Mounting/Installation At the basic card CIFX 104-FB\F:
RoHS Yes
UKCA Sign Yes
Table 117: Technical Data AIFX-CC

9.1.16 AIFX-DIAG
AIFX-DIAG Parameter Value
Part Name AIFX-DIAG
Part No. 2800.000
Description Diagnostic detached network interface for the PC cards
CIFX 104-RE\F, CIFX 104-RE-R\F
CIFX 104-DP\F, CIFX 104-DP-R\F,
CIFX 104-CO\F, CIFX 104-CO-R\F,
CIFX 104-DN\F, CIFX 104-DN-R\F,
CIFX 104-CC\F
Schnittstelle Connector Cable Connector DIAG X1
PC-Karte cifX (JST 12FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm)
Display LED Display PWR Supply Voltage ON LED
SYS System Status LED
The meaning of the following LEDs depends on the loaded
firmware::
Power supply Connector Kabelstecker DIAG X1
Conditions
environment.
Device Dimensions (L x W x H) 20,5 x 52,7 x 18,5 mm (H = width of the front panel)
Mounting/Installation For the basic cards:
CIFX 104-RE\F, CIFX 104-RE-R\F,
CIFX 104-FB\F, CIFX 104-FB-R\F
Cable Connector DIAG X3 (X303)
RoHS Yes
UKCA Sign Yes
to UL 508
Table 118: Technical Data AIFX-DIAG

9.2 Technical Data of the Communication Protocols
9.2.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 119: Technical data CC-Link IE Field Basic Slave protocol

9.2.2 EtherCAT Master

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 (CONFIG.NXD),
(ETHERCAT.XML or CONFIG.NXD) maximum 3 MByte (ETHERCAT.XML)
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 120: Technical Data EtherCAT Master Protocol

9.2.3 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 121: 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.

9.2.4 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
Reference to firmware/stack version V2.10
Table 122: Technical Data EtherNet/IP Scanner Protocol

9.2.5 EtherNet/IP Adapter (Slave)

Maximum number of input data 504 bytes per assembly instance
Maximum number of output data 504 bytes per assembly instance
Maximum number of assembly instances 10
IO connection types (implicit) Exclusive Owner
Listen Only
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
Unconnected Message Manager (UCMM) Supported
Maximum number of connections Implicit connections (Class 1): 5
Explicit connections (Class 3): 10
UCMM: 10
Predefined standard objects Identity object (1, 0x01)
Message Router object (2, 0x02)
Assembly object (4, 0x04)
Connection Manager (6, 0x06)
DLR object (71, 0x47)
QoS object (72, 0x48)
TCP/IP object (245, 0xF5)
Ethernet Link object (246, 0xF6)
Maximum number of user specific objects 20
Supported functions, protocols and, services TCP/IP, UDP/IP
DHCP, BOOTP
Quick Connect
Device Level Ring (DLR) - Media Redundancy
Address Conflict Detection (ACD)
Quality of Service
CIP Reset services - Identity Object Reset Service (Type 0 and 1)
Ethernet interface 10 and 100 MBit/s
Integrated switch
Duplex modes Half duplex, Full duplex, Auto negotiation
MDI modes MDI, MDI-X, Auto-MDIX
Limitations Tags are not supported.
Connection type "Null forward Open" is not supported.
CIP Motion is not supported.
CIP Safety is not supported.
Table 123: Technical Data EtherNet/IP Adapter protocol

9.2.6 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
Baud rates 10 and 100 MBit/s
Table 124: Technical Data Open Modbus/TCP Protocol
9.2.7 POWERLINK Controlled Node/Slave

Maximum number of cyclic input data 1490 bytes
Maximum number of cyclic output data 1490 bytes
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 125: Technical Data POWERLINK Controlled Node Protocol

9.2.8 PROFINET IO-Controller

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
Multicast communication 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 126: Technical Data PROFINET IO Controller Protocol
9.2.9 PROFINET IO-Device

Maximum number of cyclic input data 1440 bytes (including IOPS and IOCS)12 bytes
Maximum number of cyclic output data 1440 bytes (including IOPS and IOCS)
Maximum number of submodules Depends on the firmware, can be configured via “Number of configurable
submodules” in tag list. Up to 256 in general and may be smaller number
for specific firmware.
Note: If the application uses max. 2 APIs, the “Number of configurable
submodules” can be used. Each further API reduces the total number of
usable submodules by 1.
Multiple Application Relations (AR) Depends on the firmware, can be configured via “Number of additional IO
Connections (ARs)” in tag list.
Up to 4 IO-ARs and one Supervisor-DA AR in general and may be
smaller for numbers specific firmware.
Acyclic communication (Record objects) Read/Write Record, max supported size can be configured via taglist.
Alarm types Process Alarm, Diagnostic Alarm, Return Of Submodule Alarm, Plug
Alarm (implicit), Pull Alarm (implicit), Update Alarm, Status Alarm, Upload
and Retrieval Notification Alarm
Diagnosis entries Depends on the firmware, can be configured via “Number of available
Diagnosis buffers” in tag list.
Up to 256 application diagnosis records of type Channel or Extended
Channel Diagnosis in general and may be smaller number for specific
firmware.
Identification & Maintenance (I&M) I&M0 Read: Either integrated for slot 0 / subslot 1 or forwarded to the
application for each submodule.
I&M1-5 Read/Write: Either built in for Slot 0 / Subslot 1 or pass through
to application for any submodule. I&M4 and I&M5 are inactive by default.
Topology recognition LLDP, SNMP V1, Physical Device Record Objects
Minimum cycle time (MinDeviceInterval) RT_CLASS_1: 1 ms (min. SendClockFactor 32)
RT_CLASS_3: 250 µs (min. SendClockFactor 8)
IRT support RT_CLASS_3

Media redundancy MRP Client
Additional supported features "Shared Device"
Asset Management
PROFIenergy ASE
Data transport layer Ethernet II, IEEE 802.3, MAUType 16
PROFINET IO specifiation V2.3, PNIO_version 2.35
V2.2 ("legacy startup") is supported
Conformance Class C
Application IP stack API The lwIP IP stack can be used by the application via Socket API Packets.
Up to 8 sockets are available to the Application.
Application Raw Ethernet API Sending and Receiving Raw Ethernet Frames as Application is
supported
Restrictions RT over UDP not supported.
Multicast communication not supported.
DHCP is not supported.
The amount of configured I/O-data influences the minimum cycle time
that can be reached.
Only 1 Input-CR and 1 Output-CR per AR are supported.
Little endian byte order not supported.
System Redundancy (SR-AR) and Dynamic Reconfiguration are not
supported.
The usage of PROFINET CombinedObjectContainer is not supported.
SharedInput is not supported.
MRPD is not supported.
DFP and other HighPerformance-profile related features are not
supported.
Submodules cannot be configured or used by an AR in subslot 0.
The stack does not support usage of PDEV submodules
(InterfaceSubmodule or PortSubmodule) outside of slot 0. In addition the
InterfaceSubmodule is only supported in subslot 0x8000 and the
PortSubmodules are only supported in subslots 0x8001 and 0x8002.
Reference to stack version V4.5
Table 127: Technical Data PROFINET IO-Device protocol
The maximum values for number of submodules, Multiple Application

Relations, Acyclic communication, and Diagnosis entries are configuration
parameters in the tag list of a firmware. Each of these features require
resources and have to be set in order to not exceed the available resource
(e.g. RAM) of a device.

9.2.10 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 128: Technical Data Sercos Master Protocol

9.2.11 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 129: Technical Data Sercos Slave Protocol

9.2.12 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 130: Technical Data VARAN Client Protocol

9.2.13 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 131: Technical Data PROFIBUS DP Master Protocol

9.2.14 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 132: Technical Data PROFIBUS DP Slave Protocol

9.2.15 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.x.x
Table 133: Technical Data PROFIBUS-MPI Protocol

9.2.16 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.11.x.x
Table 134: Technical Data CANopen Master Protocol

9.2.17 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
Reference to firmware/stack version V3.6.x.x
Table 135: Technical Data CANopen Slave Protocol

9.2.18 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 136: Technical Data DeviceNet Master Protocol

9.2.19 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 137: Technical Data DeviceNet Slave Protocol

9.2.20 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 138: Technical Data CC-Link-Slave-Protocol

Dimensions 164/200
10 Dimensions
10.1 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 section Dimensioning PC Cards cifX PC-
104 from page 165) 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 H) specified in section Technical Data PC

Cards cifX on page 122 (and also the identical values in the data sheet
cifX and on the ‘Hilscher Site’) are rounded and unified for the type of
card.

Dimensions 165/200
10.2 Dimensioning PC Cards cifX PC-104

10.2.1 CIFX 104-RE
81.26
30.71
7.63
5.08
L0915012 CIFX104-RE
12.24
3 1
16.40
Hilscher X51
GND
IO1
IO0
LP1 V4 V3 V1
R28
R27
R13
R14
R15
R16
R1
R2
made in Germany
R3
ø3.
50
2.46
16Bit
8Bit
R25
R26
CH 0
CH_A
C110 C100 CH 1
R102 J9
R112 N110 P12 N100
C60
31.12 (+0.16/-0.0)
R62 R111 R101 J9

R63 L100
C61 R110 L110 R100
P11 P13 C101
P4 C111 D4
C62 R19
45DB321 D3 C9
R64 N1
R65 C4
C63 R67
C135 C131
P3 C3 G1 C8 C6
C11 CH 0
25
C132
CH_B
R8 C153 C2 D2
95.88
CH 1
90.80
X6
R17 C1
SDRAM2Mx32
C150
C154
R200
C205
X5
L200
2.62
C152
C204
D5 R206
C207
R201
9.67
0.8
L201 x1
x16
R20 R21
S3 C206 C134 AOI
R18 C10 C133 C5
C151 C7
R92 R9 R6 R93 D0 C130
R7 R4 R5
40.67
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
x1
9.67
x16
C114
N5 J7 J8
S2
B1 B32
X1 A1 A32
13.97
C0 C19
X2 D0 D19
5.08
5.08
5.08 5.08
90.17
Figure 45: Dimensions CIFX 104-RE

Dimensions 166/200
10.2.2 CIFX 104-RE\F

81.26
30.71
7.63
5.08
L0915012 CIFX104-RE
12.24
3 1
Hilscher X51
GND
IO1
IO0
V1
R28
R27
R1
R2
R3 made in Germany
ø3.
50
16Bit
8Bit
R25
R26
C110 C100
R102 J9
R112 N110 P12 N100
R111 R101 J9
L100
R110 L110 R100
22.38
P11 P13 C101

P4 C111 D4
R19 D3 C9
45DB321
C4 N1
C135 C131
P3 C3 G1 C8 C6
C11 C132
25
R8 C153 C2 D2
95.88
90.80
SDRAM2Mx32
R17 C1
C150
C154
R200
C205
L200
C152
C204
X3
D5 R206
C207
R201
14.45
L201
R20 R21
52.73
AOI
C206 C134
R18 C10 C133 C5
C151 C7
R92 R9 R6 R93 D0 C130
R7 R4 R5
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
C114
N5 J7 J8
22.53
B1 B32
X1 A1 A32
C0 C19
X2 D0 D19 5.08
5.07
5.08 5.08
90.17
Figure 46: Dimensions CIFX 104-RE\F

Dimensions 167/200
10.2.3 CIFX 104-DP

81.28
5.08
5.08 7.63
R403 CIFX104-CO
R400
CIFX104-DN
12.24
R405
C401
CIFX104-DP
16.52
R404
U400
LP1 V3 V1
Hilscher
ø3.
R14
R13
R3
R2
50
16Bit
8Bit
2.65
R413
C400
L400 L401
C403
U401
8.82 C405 J9
C110 C100 R5
U410 P3 R112
Buchse
30.81
N110 R102 N100
P10 P12 R114

R111 R101
C404
P11
P4 L110 R100 L100
R110
C101
C111
P13 C131 G1
25
C8 C6
C370 R26 C153 C132 C2
95.88
C11 C135 D2
C4 C1
R370 GND N1
X400B
90.80
X5 D4
45DB321
C150
C154
2.60 C3
D3 C152
R1 R25
R367
0.8
9.67
x16
D5 C134
R20
R21
R18
AOI
S3 C9
C10 C151 C133 C7 C5
R8 D0 C130
R17 R9 R6 R7 R4 R15
40.67
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
x1
9.67
C44 N5
S2 X7 J8 L0913012
B1 B32
A1 A32
5.09
X1
13.94
C0 C19
D0 D19
5.08
X2
5.08 5.08
90.17
Figure 47: Dimensions CIFX 104-DP

Dimensions 168/200
10.2.4 CIFX 104-CO

81.28
5.08
7.64
5.08
R406 R363
N360
CIFX104-CO
82C
CIFX104-DN
12.23
R364
CIFX104-DP
16.52
C367
C362
LP1 V3 V1
Hilscher
ø3.
R14
R13
HCPL
U360
060L
U361
R3
R2
HCPL 0601
50
16Bit
8Bit
2.65 C360 R361 R360
R413
L400 L401
C403
U401
8.82 C405 J9
C110 C100 R5
U410 P3 R112
V361
Stecker
30.81
N110 R102 N100
P10 P12 R114

R111 R101
C404
P11
P4 L110 R100 L100
R110
C101
C111
P13 C131 G1
C6
25
C8
R26 C153 C132 C2
95.88
C11 C135 D2
C4 C1
90.80
GND N1
X400B
X5 D4
45DB321
C150
C154
2.60 C3
D3 C152
R1 R25
R367
0.8
9.67
D5 C134
x16
R20
R21
R18
AOI
S3 C9
C10 C151 C133 C7 C5
R8 D0 C130
R17 R9 R6 R7 R4 R15
40.67
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
9.67
C44 N5
x1
S2 X7 J8 L0913012
B1 B32
A1 A32
X1
13.94
C0 C19
D0 D19
5.09
5.09
X2
5.08 5.08
90.17
Figure 48: Dimensions CIFX 104-CO

Dimensions 169/200
10.2.5 CIFX 104-DN

81.25
5.08
7.62
5.08
R363
N360
CIFX104-CO
82C
CIFX104-DN
12.24
R364
C367 C361 CIFX104-DP
18.19
C362 R365
LP1 V3 V1
Hilscher
ø3
R366
R14
R13
HCPL
U360
060L
U361
R3
R2
.50
HCPL 0601
U362
16Bit
8Bit
C363
R413 C360 R361 R360 R362 N362
C400
1
L400 L401
C403
U401
C405 J9
2
C110 C100 R5
U410 P3 R112
V361 R102
27.40
N110 N100
3
P10 P12 R114

R111 R101
C404
P11
4
P4 L110 R100 L100

R369
R110
C101
C111
5
P13 C131 G1
C6
25
C8
C370 R26 C153 C132 C2
95.88
C11 C135 D2
C1
2.52 R371 C371 R370
C4
GND N1
90.80
X5 D4
45DB321
C150
C154
2.60 C3
D3 C152
R1 R25
R367
0.8
9.67
x1
D5 C134
x16
R20
R21
R18
AOI
S3 C9
C10 C151 C133 C7 C5
R8 D0 C130
R17 R9 R6 R7 R4 R15
40.67
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
x16
9.67
C44 N5
x1
S2 X7 J8 L0913012
B1 B32
A1 A32
5.08
X1
13.94
C0 C19
D0 D19
5.08
X2
5.08 5.08
90.17
Figure 49: Dimensions CIFX 104-DN

Dimensions 170/200
10.2.6 CIFX 104-FB\F

81.28
5.08
7.63
5.08
CIFX104-CO
CIFX104-DN
12.24
CIFX104-DP
V1
Hilscher
ø3
R3
R2
0.5
16Bit
8Bit
X4
12.47
J9
C110 C100 R5
P3 R112
N110 R102 N100
P10 P12 R114

R111 R101
P11
P4 L110 R100 L100
R110
C101
C111
P13 C131 G1
25
C8 C6
R26 C153 C132 C2
95.88
C11 C135 D2
C4 C1
GND N1
90.80
D4
45DB321
C150
C154
X3 C3 C152
D3
66.12
R1 R25
14.45
R367
D5 C134
R20
R21
R18
AOI
C9
C10 C151 C133 C7 C5
R8 D0 C130
R17 R9 R6 R7 R4 R15
C44 N5
ADR 14 15 16 17 18 19 3 4 5 6 7 9 10 11 12 14 15 IRQ
x1
X7 J8 L0913012
22.53
B1 B32
A1 A32
5.09
X1
C0 C19
D0 D19
5.08
X2
5.08 5.08
90.17
Figure 50: Dimensions CIFX 104-FB\F

Dimensions 171/200
10.3 Dimensioning AIFX detached Network Interfaces

10.3.1 Ethernet - AIFX-RE
31.2
13.7
10.0
component height
M2.5
5.6
Leiterkarte/ PCB
9.0
COM0 COM1
1.6
2.5
2.6
17.5 7.4
39.8 X200
X1
Kanal 1 /
Channel 1
flexibles (CH 1)
Folienkabel /
22.4
42.3
flexible flat
cable Kanal 0 /
Channel 0
(CH 0)
21.2
L0621112
30.7
Figure 51: Dimensioning Ethernet detached Network Interface (AIFX-RE)

Dimensions 172/200
10.3.2 Ethernet M12 - AIFX-RE\M12
Kanal 1 /
X1
Channel 1
(CH 1)
flexibles Folienkabel / green1 yellow1 COM1
30.00
flexible flat cable
X2
60.00
green0 yellow0 COM0
Kanal 0 /
X0
Channel 0
flexibles Folienkabel / (CH 0)
flexible flat cable X3
36.00
Figure 52: Dimensioning Detached Network Interface Ethernet (AIFX-RE\M12)
Figure 53: Drawing Panel Cutout Detached Network Interface Ethernet (AIFX-RE\M12)
Front panel thickness: 2-3 mm

Dimensions 173/200
10.3.3 PROFIBUS - AIFX-DP

25
10.70
component height
8.1 Leiterkarte/ PCB
13 13
2.00
ERR STA
31
X1
flexibles
Folienkabel /
X400
L0621312
flexible flat
cable
17
17.4
23.4
Figure 54: Dimensioning PROFIBUS detached Network Interface (AIFX-DP)
10.3.4 CANopen - AIFX-CO

25
10.70
component height
8.08
Leiterkarte/ PCB
13 13
2.00
ERR RUN
31
flexibles
L0621212
Folienkabel /
flexible flat
cable
17
17.4
23.4
Figure 55: Dimensioning CANopen detached Network Interface (AIFX-CO)

Dimensions 174/200
10.3.5 DeviceNet - AIFX-DN
17.5
M2,5
10
component height
6.8
7.50
OJ E T C B OJ E T C B
Leiterkarte/ PCB
3.3
3.00 3.00
2.00
13
MNS
15.5
1 2 3 4 5
OJ E T
B
C
L0621412
31
OJ E T C B
flexibles
Folienkabel /
flexible flat
X360
cable
X1
23.7
26.7
37.3
Figure 56: Dimensioning DeviceNet detached Network Interface (AIFX-DN, with counter
part)

Dimensions 175/200
10.3.6 CC-Link - AIFX-CC

18,9
10,0
M2,5
6.8
7,5
component height
BJ ECT O BJ ECT O
Leiterkarte/ PCB
3.5
3,0 3,0
2,0
12.99 13,0
L-ERR L-RUN
L1404042 AIFX-CC
XXXXX
15,5
1 2 3 4 5
XXXX.XXX
31,0
flexibles
Folienkabel /
flexible flat X360
cable
X1
43,2
45,4
56.3
Figure 57: Dimensioning CC-Link detached Network Interface (AIFX-CC, with counter part)
10.3.7 Diagnose - AIFX-DIAG

78 9 78 9
10.70
34 5 6
34 5 6
A
10.00
component height
B CD
B CD
M2.5
Mini-
EF 2 EF 2
5.6
01 01
USB
Leiterkarte
PCB 10.00
2.80
2.00
7.94
11.4
12.97
22.7
20.70 10.20
32
42,2
49.90 flexibles
Folienkabel /
L0621511
53.6
flexible flat
cable
X1
AIFX-DIAG
20.5
23.2
Figure 58: Dimensioning Diagnostic detached Network Interface (AIFX-DIAG)

Annex 176/200
11 Annex
11.1 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
[4] Data sheet 99_3732_203_04.pdf (product data sheet of the manufacturer binder):
https://catalog.weidmueller.com
References Protocol API Manuals

• 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-Basic Slave Protocol API, Revision 1, Hilscher GmbH 2018
• CC-Link Slave Protocol API Manual, Revision 12, Hilscher GmbH 2020
• DeviceNet Master Protocol API Manual, Revision 11, Hilscher GmbH 2016
• DeviceNet Slave Protocol API Manual, Revision 18, Hilscher GmbH 2020
• EtherCAT Master Protocol API Manual (V4), Revision 5, Hilscher GmbH 2017
• EtherCAT Slave Protocol API Manual (V4), Revision 12, Hilscher GmbH 2020
• EtherNetIP Scanner Protocol API Manual, Revision 15, Hilscher GmbH 2020
• EtherNetIP Adapter Protocol API Manual, Revision 20, Hilscher GmbH 2017
• Open Modbus/TCP Protocol API Manual, Revision 11, Hilscher GmbH 2018
• POWERLINK-Controlled-Node/Slave Protocol API Manual (V3), Revision 8, Hilscher GmbH 2018
• PROFIBUS DP-Master Protocol API Manual, Revision 22, Hilscher GmbH 2017
• PROFIBUS DP-Slave Protocol API Manual, Revision 20, Hilscher GmbH 2020
• PROFIBUS MPI Protocol API Manual, Revision 4, Hilscher GmbH 2011
• PROFINET IO-Controller Protocol API Manual (V3), Revision 8, Hilscher GmbH 2021
• PROFINET IO-Device Protocol API Manual (V4), Revision 4, Hilscher GmbH 2019
• 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 4, Hilscher GmbH 2021
Table 139: References Protocol API Manuals
11.1.1 Reference PC/104 Specification

No. Specification Revision Version De www
[bus spec 8] PC/104 Specification 2.6 October 13, 2008 pcisig.com,
pc104.org
Table 140: Reference PC/104 Specification

Annex 177/200
11.1.2 References Safety

[S1] American National Standards Institute, Inc.: American National Standard, Product
Safety Information in Product Manuals, Instructions, and Other Collateral Materials,
ANSI Z535.6-2016, English, 2016.
[S2] DIN Deutsches Institut für Normung e. v. and VDE Verband der Elektrotechnik
Elektronik Informationstechnik e. V.: German standard, Equipment for audio/video,
information and communication technology - Part 1: Safety requirements, (IEC
62368-1:2014, modified + Cor.:2015); English version EN 62368-1:2014 + AC:2015,
English, 2016-05.
[S3] DIN Deutsches Institut für Normung e. v. and VDE Verband der Elektrotechnik
Elektronik Informationstechnik e. V.: German standard, Electrostatics - Part 5-1:
Protection of electronic components against electrostatic phenomena, General
requirements, (IEC 61340-5-1:2016); English version EN 61340-5-1:2016, English,
2017-07.
DIN Deutsches Institut für Normung e. v. und VDE Verband der Elektrotechnik
Elektronik Informationstechnik e. V.: German standard, Electrostatics - Part 5-2:
Protection of electronic components against electrostatic phenomena, User manual,
(IEC TR 61340-5-2:2018), DIN IEC/TR 61340-5-2 (VDE V 0300-5-2), English,
2019-04.

Annex 178/200
11.2 Conventions in this Manual
Instructions
1. Operational purpose
2. Operational purpose
 Instruction
Results
 Result
Sign
Sign Note Safety sign Warning, principle
General note Warning of hazardous
voltage! Danger to life, risk
of injury by electric shock
(USA)
Important note that must be Warning of damage due to
followed to prevent malfunctions electrostatic discharge
Reference to further information Principle: Disconnect the

power plug
Table 141: Sign
Signal Words
Signal word Description
Indicates a hazardous situation which if not avoided, will result in
death or serious injury.
Indicates a hazardous situation which if not avoided, could result in
death or serious injury.
Indicates a hazardous situation which if not avoided, may result in
minor or moderate Injury.
Indicates a property damage message.
Table 142: Signal Words
11.2.1 Used Terminology

PC Card cifX Communication Interfaces of the cifX family of Hilscher
based on the netX technology.
CIFX 104-RE Example for the product name for a PC card cifX Real-
Time Ethernet.
CIFX 104-XX Example (‘XX’ replaces ‘RE’, ‘DP’, ‘CO’, ‘DN’ or ‘CC’)
CIFX 104-FB\F Example (‘FB’ replaces ‘DP’, ‘CO’, ‘DN’ or ‘CC’)
For further terminology to the PC cards cifX, its installation, configuration
and operation refer to section Glossary on page 191.

Annex 179/200
11.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
Annex 180/200
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
Annex 181/200
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.

Annex 182/200
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.
11.4 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.
11.4.1 License Note about VARAN Client

In order to use the PC card cifX with VARAN, you need a licence which you
can acquire at the VNO (VARAN Bus-Nutzerorganisation, Bürmooser
Straße 10, A-5112 Lamprechtshausen, [email protected]) after getting a
member of VON.
The licence 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.

Annex 183/200
11.5 Registered Trademarks

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.
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.
PC/104™ is a trademark of the PC/104 Consortium (pc104.org).
All other mentioned trademarks are property of their respective legal
owners.
11.6 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 [email protected].
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 184.
Annex 184/200
11.6.1 EtherCAT Summary over Vendor ID, Conformance test,

Membership and Network Logo
11.6.1.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.6.1.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.6.1.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.
11.6.1.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 185/200
11.7 Notes on earlier Hardeware Revisions

11.7.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 104-RE\F 1278.101 20003
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 186/200
11.8 List of Figures

Figure 1: Example Barcode Label (EAN 39) 19
Figure 2: CIFX 104-RE* 20
Figure 3: CIFX 104-RE-R* 21
Figure 4: Basic Card for CIFX 104-RE\F 22
Figure 5: Basic Card for CIFX 104-RE-R\F 23
Figure 6: CIFX 104-DP 24
Figure 7: CIFX 104-DP-R 25
Figure 8: CIFX 104-CO 26
Figure 9: CIFX 104-CO-R 27
Figure 10: CIFX 104-DN 28
Figure 11: CIFX 104-DN-R 29
Figure 12: Basic Card CIFX 104-FB\F for CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F
30
Figure 13: Basic Card CIFX 104-FB-R\F for CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F 30
Figure 14: Reverse Side CIFX 104-XX (all Basic Cards and Variants) 31
Figure 15: Ethernet detached Network Interface (AIFX-RE)* 32
Figure 16: Front Side and LED Display Ethernet detached Network Interface (AIFX-RE) 32
Figure 17: Ethernet M12 detached Network Interface (AIFX-RE\M12) 33
Figure 18: Ethernet M12 detached Network Interface (AIFX-RE\M12) 33
Figure 19: PROFIBUS detached Network Interface (AIFX-DP) 34
Figure 20: Front Side and LED Display PROFIBUS detached Network Interface (AIFX-DP) 34
Figure 21: CANopen detached Network Interface (AIFX-CO) 35
Figure 22: Front Side and LED Display detached Network Interface (AIFX-CO) 35
Figure 23: DeviceNet detached Network Interface (AIFX-DN, with counter part) 36
Figure 24: Front Side and LED Display DeviceNet detached Network Interface (AIFX-DN, with counter part)
36
Figure 25: CC-Link detached Network Interface (AIFX-CC) 37
Figure 26: Reverse Side CC-Link detached Network Interface (AIFX-CC) with Matrix Label 37
Figure 27: Front Side and LED Display CC-Link detached Network Interface (AIFX-CC, with counter part) 37
Figure 28: Diagnostic detached Network Interface (AIFX-DIAG) 38
Figure 29: Front Side, LED Display and Reverse Side Diagnostic detached Network Interface (AIFX-DIAG)38
Figure 30: Connecting the Ethernet detached Network Interface (AIFX-RE) to the Basic Card CIFX 104-RE\F
(Example) 61
Figure 31: Connecting the CANopen detached Network Interface (AIFX-CO) to the Basic Card 104-FB-R\F
(Example) 62
Figure 32: Connecting the Diagnostic detached Network Interface (AIFX-DIAG) to the Basic Card CIFX 104-
FB-R\F (Example) 62
Figure 33: System Overview cifX to update Firmware, Driver and Software 66
Figure 34: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX 104
Figure 35: Ethernet Pin Assignment at the M12 Socket for AIFX-RE\M12 (D coded) 105
Figure 36: PROFIBUS Interface (DSub female connector, 9 pin), X400 107
Figure 37: CANopen Interface (DSub male connector, 9 pin), X400 107
Figure 38: DeviceNet Interface (CombiCon male Connector, 5 pin), X360 108
Figure 39: CC-Link Interface (CombiCon male Connector, 5 pin) 108
Figure 40: Mini-B USB Connector (5 Pin) 109
Figure 41: Cable Connector Ethernet X4 or X304; 1x20 Pins for CIFX 104-RE\F, CIFX 104-RE-R\F 110
Figure 42: Cable Connector Ethernet X1; 1x20 Pins, AIFX-RE 112
Figure 43: Cable Connector Ethernet X2; 1x20 Pins, AIFX-RE\M12 113
Figure 44: Cable Connector LED Signals X3; 1x10 Pins, AIFX-RE\M12 114
Figure 45: Dimensions CIFX 104-RE 165
Figure 46: Dimensions CIFX 104-RE\F 166
Figure 47: Dimensions CIFX 104-DP 167
Annex 187/200
Figure 48: Dimensions CIFX 104-CO 168
Figure 49: Dimensions CIFX 104-DN 169
Figure 50: Dimensions CIFX 104-FB\F 170
Figure 51: Dimensioning Ethernet detached Network Interface (AIFX-RE) 171
Figure 52: Dimensioning Detached Network Interface Ethernet (AIFX-RE\M12) 172
Figure 53: Drawing Panel Cutout Detached Network Interface Ethernet (AIFX-RE\M12) 172
Figure 54: Dimensioning PROFIBUS detached Network Interface (AIFX-DP) 173
Figure 55: Dimensioning CANopen detached Network Interface (AIFX-CO) 173
Figure 56: Dimensioning DeviceNet detached Network Interface (AIFX-DN, with counter part) 174
Figure 57: Dimensioning CC-Link detached Network Interface (AIFX-CC, with counter part) 175
Figure 58: Dimensioning Diagnostic detached Network Interface (AIFX-DIAG) 175
11.9 List of Tables

Table 1: List of Revisions 9
Table 2: PC Cards PC/104: CIFX 104-XX and CIFX 104-XX-R 11
Table 3: PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F, CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12
12
Table 4: AIFX detached Network Interfaces for PC Cards cifX with Cable Connector 13
Table 5: Device Description Files for PC Cards cifX 16
Table 6: Reference on Hardware PC Cards cifX 17
Table 7: Reference on Hardware AIFX detached Network Interfaces 17
Table 8: Reference on Driver and Software 17
Table 9: Reference on Firmware 18
Table 10: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby 39
Table 11: PC Cards cifX with AIFX detached Network Interface 39
Table 12: Slot for the PC Cards cifX PC/104 48
Table 13: Requirements Power Supply and Host Interface for PC Cards cifX PC/104 48
Table 14: Panel Cutout at the at the front plate of the PC cabinet 49
Table 15: Required Panel Cutout and Holes for AIFX 50
Table 16: Requirements to operate PC Cards cifX properly 51
Table 17: Steps for the Software and Hardware Installation, the Configuration and for the Diagnosis of a PC
Card cifX PC/104 (Master and Slave) 57
Table 18: Starting Address and Interrupt for 16 KByte Dual-Port Memory 58
Table 19: Notes for the Configuration of the Master Device 64
Table 20: Device Names in SYCON.net by Communication Protocol 65
Table 21: Overview LEDs Real-Time Ethernet Systems 70
Table 22: LED Names 70
Table 23: Overview LEDs by Fieldbus System for 1 Channel Devices 71
Table 24: LED Names 71
Table 25: System Status LED States 72
Table 26: Power On LED States 72
Table 27: LED states for the CC-Link IE Field Basic Slave 73
Table 28: LED state definitions for theCC-Link IE Field Basic Slave protocol 73
Table 29: LED states for the EtherCAT Master protocol 74
Table 30: LED state definitions for the EtherCAT Master protocol 75
Table 31: LED states for the EtherCAT Slave protocol 76
Table 32: LED state definitions for the EtherCAT Slave protocol 76
Table 33: LED states for the EtherNet/IP Scanner protocol 78
Table 34: LED state definitions for the EtherNet/IP Scanner protocol 78
Table 35: LED states for the EtherNet/IP Adapter protocol 80
Table 36: LED state definitions for the EtherNet/IP Adapter protocol 80

Annex 188/200
Table 37: LED states for the OpenModbusTCP protocol 81
Table 38: LED state definitions for the OpenModbusTCP protocol 81
Table 39: LED states for the POWERLINK Controlled Node protocol 82
Table 40: LED state definitions for the POWERLINK Controlled Node protocol 82
Table 41: PROFINET IO Controller, SYS, COM0 and COM1 LEDs states 83
Table 42: PROFINET IO Controller, Ethernet LEDs states 84
Table 43: PROFINET IO Controller, LEDs states definitions 84
Table 44: LED states for the PROFINET IO-Device protocol 85
Table 45: LED state definitions for the PROFINET IO-Device protocol 85
Table 46: LED states for the Sercos Master protocol 86
Table 47: LED state definitions for the Sercos Master protocol 87
Table 48: LED state definitions for the Sercos Slave protocol 88
Table 49: LED state definitions for the Sercos Slave protocol 89
Table 50: LED-Zustände für das VARAN-Client-Protokoll 90
Table 51: Definitionen der LED-Zustände für das VARAN-Client-Protokoll 90
Table 52: LED states for the PROFIBUS DP Master protocol – 1 Communication Status LED (current
Hardware Revision) 91
Table 53: LED state definitions for the PROFIBUS DP Master protocol 91
Table 54: LED states for the PROFIBUS DP Master protocol – 2 Communication Status LEDs (AIFX-DP
connected or prior Hardware Revision) 92
Table 55: LED state definitions for the PROFIBUS DP Master protocol 92
Table 56: LED states for the PROFIBUS DP Slave protocol – 1 Communication Status LED (current
Table 57: LED state definitions for the PROFIBUS DP Slave protocol 93
Table 58: LED states for the PROFIBUS DP Slave protocol – 2 Communication Status LEDs (AIFX-DP
Table 59: LED state definitions for the PROFIBUS DP Slave protocol 94
Table 60: LED states for the PROFIBUS MPI protocol – 1 Communication Status LED 95
Table 61: LED state definitions for the PROFIBUS MPI protocol 95
Table 62: LED states for the PROFIBUS MPI protocol – 2 Communication Status LEDs (AIFX-DP
connected) 96
Table 63: LED state definitions for the PROFIBUS MPI protocol 96
Table 64: LED states for the CANopen Master protocol – 1 Communication Status LED (current Hardware
Revision) 97
Table 65: LED state definitions for the CANopen Master protocol 97
Table 66: LED states for the CANopen Master protocol – 2 Communication Status LEDs (AIFX-CO
Table 67: LED state definitions for the CANopen Master protocol 98
Table 68: States of the CAN LED for the CANopen Slave protocol – 1 Communication Status LED (current
Table 69: LED state definitions for the CANopen Slave protocol 99
Table 70: States of the CAN LED for the CANopen Slave protocol – 2 Communication Status LEDs (AIFX-
CO connected or prior Hardware Revision) 100
Table 71: LED state definitions for the CANopen Slave protocol 100
Table 72: LED states for the DeviceNet Master protocol 101
Table 73: LED state definitions for the DeviceNet Master protocol 101
Table 74: LED states for the DeviceNet Slave protocol 102
Table 75: LED state definitions for the DeviceNet Slave protocol 102
Table 76: LED states for the CC-Link Slave protocol 103
Table 77: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX 104
Table 78: Ethernet Pin Assignment M12 Socket for AIFX-RE\M12 105
Table 79: Ethernet Connection Data 106
Table 80: Use of Hubs and Switches 106
Table 81: PROFIBUS Interface, X400 107
Table 82: CANopen Interface, X400 107
Annex 189/200
Table 83: DeviceNet Interface, X360 108
Table 84: CC-Link Interface 108
Table 85: Pin Assignment Mini-B USB Connector 109
Table 86: Pin Assignment for Cable Connector Ethernet X4 or X304 110
Table 87: Pin Assignment for Cable connector Fieldbus X3, X304 or X4 111
Table 88: Pin Assignment for Cable connector DIAG X3 or X303 111
Table 89: Pin Assignment for Cable Connector Ethernet X1, AIFX-RE (Hardware-Rev. 2) 112
Table 90: Pin Assignment for Cable Connector Ethernet X2, AIFX-RE\M12 113
Table 91: Pin Assignment for Cable Connector LED Signals X3, AIFX-RE\M12 114
Table 92: Pin Assignment for Cable Connector fieldbus X1, AIFX-DP (Hardware Rev. 2) 115
Table 93: Pin Assignment for Cable Connector fieldbus X1, AIFX-CO (Hardware Rev. 2) 115
Table 94: Pin Assignment for Cable Connector fieldbus X1, AIFX-DN (Hardware Rev. 3) 116
Table 95: Pin Assignment for Cable Connector fieldbus X1, AIFX-CC (Hardware Rev. 2) 116
Table 96: Cable for connecting the detached Network Interfaces AIFX-RE or AIFX-RE\M12 117
Table 97: Pin Assignment for SYNC Connector, X51 118
Table 98: SYNC Connector: SYNC Signal, Connector, Max. Cable Length 118
Table 99: Meaning of the SYNC Signals for each Protocol 118
Table 100: Pin Assignment at the PC/104 Bus 119
Table 101: Pin Assignment for PC/104-Bus, X1 (Control Signals used on the 8 Bit Connector) 120
Table 102: Pin Assignment for PC/104-Bus, X2 (Used Control Signals on the Expansion Connector) 121
Table 103: Technical Data CIFX 104-RE, CIFX 104-RE-R 123
Table 104: Technical Data CIFX 104-RE\F, CIFX 104-RE-R\F, CIFX 104-RE\F\M12, CIFX 104-RE-R\F\M12
125
Table 105: Technical Data CIFX 104-DP, CIFX 104-DP-R 127
Table 106: Technical Data CIFX 104-DP\F, CIFX 104-DP-R\F 128
Table 107: Technical Data CIFX 104-CO, CIFX 104-CO-R 130
Table 108: Technical Data CIFX 104-CO\F, CIFX 104-CO-R\F 131
Table 109: Technical Data CIFX 104-DN, CIFX 104-DN-R 133
Table 110: Technical Data CIFX104C-DN\F, CIFX 104-DN-R\F 134
Table 111: Technical Data CIFX104C-CC\F 136
Table 112: Technical Data AIFX-RE 137
Table 113: Technical Data AIFX-RE\M12 138
Table 114: Technical Data AIFX-DP 139
Table 115: Technical Data AIFX-CO 140
Table 116: Technical Data AIFX-DN 141
Table 117: Technical Data AIFX-CC 142
Table 118: Technical Data AIFX-DIAG 143
Table 119: Technical data CC-Link IE Field Basic Slave protocol 144
Table 120: Technical Data EtherCAT Master Protocol 145
Table 121: Technical Data EtherCAT Slave Protocol 146
Table 122: Technical Data EtherNet/IP Scanner Protocol 147
Table 123: Technical Data EtherNet/IP Adapter protocol 148
Table 124: Technical Data Open Modbus/TCP Protocol 149
Table 125: Technical Data POWERLINK Controlled Node Protocol 149
Table 126: Technical Data PROFINET IO Controller Protocol 151
Table 127: Technical Data PROFINET IO-Device protocol 152
Table 128: Technical Data Sercos Master Protocol 153
Table 129: Technical Data Sercos Slave Protocol 154
Table 130: Technical Data VARAN Client Protocol 155
Table 131: Technical Data PROFIBUS DP Master Protocol 156
Table 132: Technical Data PROFIBUS DP Slave Protocol 157
Table 133: Technical Data PROFIBUS-MPI Protocol 158
Table 134: Technical Data CANopen Master Protocol 159

Annex 190/200
Table 135: Technical Data CANopen Slave Protocol 160
Table 136: Technical Data DeviceNet Master Protocol 161
Table 137: Technical Data DeviceNet Slave Protocol 162
Table 138: Technical Data CC-Link-Slave-Protocol 163
Table 139: References Protocol API Manuals 176
Table 140: Reference PC/104 Specification 176
Table 141: Sign 178
Table 142: Signal Words 178

Annex 191/200
11.10 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
AIFX
Assembly InterFace (detached network interface) based on netX
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
Extremely fast Industrial Ethernet communication system developed by
Mitsubishi Electric Corporation, Tokyo, Japan, for high data throughput
based on Gigabit
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
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

Annex 192/200
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
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).

Annex 193/200
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.
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).
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.
Annex 194/200
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.
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

Annex 195/200
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 (-):
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.
Annex 196/200
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.
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
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
 EtherCAT  PROFIBUS DP
 EtherNet/IP  PROFIBUS MPI
 Open-Modbus/TCP  CANopen
 POWERLINK  DeviceNet
 PROFINET IO  CC-Link
 Sercos
 VARAN
as Communication Interface netX with PCI Bus
 PCI (CIFX50),
 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),
 PC/104 (CIFX 104)
and as Communication Interface netX with PC/104 (ISA Bus)
 PC/104 (CIFX 104).
*only Real-Time Ethernet

Annex 197/200
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.
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
• 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).

Annex 198/200
Slave
Type of device that is configured by the Master and which then performs
the communication
Sercos
Bosch-Rexroth and supported by Sercos International.
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
XDD file
A special kind of Device Description file used by Ethernet POWERLINK.

Annex 199/200
XML
XML means Extended Markup Language. It is a symbolic language for
structuring data systematically. XML is standard maintained by the W3C
(World-wide web consortium). Device Description Files often use XML-
based formats for storing the device-related data appropriately.

Annex 200/200
11.11 Contacts
Headquarters Japan
Hilscher Japan KK
Germany Tokyo, 160-0022
Hilscher Gesellschaft für Systemautomation mbH Phone: +81 (0) 3-5362-0521
Rheinstraße 15 E-mail: [email protected]
D-65795 Hattersheim Support
Phone: +49 (0) 6190 9907-0 Phone: +81 (0) 3-5362-0521
Fax: +49 (0) 6190 9907-50 E-mail: [email protected]
E-mail: [email protected]
Support Republic of Korea
Phone: +49 (0) 6190 9907-990 Hilscher Korea Inc.
E-mail: [email protected] 13494, Seongnam, Gyeonggi
Phone: +82 (0) 31-739-8361
Subsidiaries E-mail: [email protected]
Support
China Phone: +82 (0) 31-739-8363
Hilscher Systemautomation (Shanghai) Co. Ltd. E-mail: [email protected]
200010 Shanghai
Phone: +86 (0) 21-6355-5161 Austria
E-mail: [email protected] Hilscher Austria GmbH
Support 4020 Linz
Phone: +86 (0) 21-6355-5161 Phone: +43 732 931 675-0
E-mail: [email protected] E-mail: [email protected]
Support
France Phone: +43 732 931 675-0
Hilscher France S.a.r.l. E-mail: [email protected]
69800 Saint Priest
Phone: +33 (0) 4 72 37 98 40 Switzerland
E-mail: [email protected] Hilscher Swiss GmbH
Support 4500 Solothurn
Phone: +33 (0) 4 72 37 98 40 Phone: +41 (0) 32 623 6633
Support
India Phone: +41 (0) 32 623 6633
Hilscher India Pvt. Ltd. E-mail: [email protected]
Pune, Delhi, Mumbai, Bangalore
Phone: +91 8888 750 777 USA
E-mail: [email protected] Hilscher North America, Inc.
Support Lisle, IL 60532
Phone: +91 8108884011 Phone: +1 630-505-5301
Support
Italy Phone: +1 630-505-5301
Hilscher Italia S.r.l. E-mail: [email protected]
20090 Vimodrone (MI)
Phone: +39 02 25007068
Support
Phone: +39 02 25007068


PC Cards Cifx 104 Um 54 en

Uploaded by

Copyright:

Available Formats

PC Cards Cifx 104 Um 54 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 104 Um 54 en

Uploaded by

Copyright:

Available Formats

User Manual

PC Cards cifX PC/104 (CIFX 104)

Installation, Operation and Hardware Description

Hilscher Gesellschaft für Systemautomation mbH

2 DESCRIPTIONS AND REQUIREMENTS ................................................................. 10

3 DEVICE DRAWINGS ................................................................................................ 20

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

6 INSTALLATION, COMMISSIONING AND UNINSTALLING...................................... 53

7 DIAGNOSIS WITH LEDS .......................................................................................... 70

8 DEVICE CONNECTIONS AND SWITCHES ........................................................... 104

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

9 TECHNICAL DATA ................................................................................................. 122

11 ANNEX .................................................................................................................... 176

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

1.2 List of Revisions

1.3 Obligation to read and understand the Manual

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2 Descriptions and Requirements

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.2 PC Cards cifX with integrated Interfaces

2.2.1 PC Cards PC/104: CIFX 104-XX, CIFX 104-XX-R

2.3 PC Cards cifX with AIFX detached Network Interfaces

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.3.2 PC Cards PC/104: CIFX 104-XX\F und Variants

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.3.3 AIFX detached Network Interfaces

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.4 Contents of the Product DVD

On the Communication Solutions DVD you will find these installation

2.4.1 Installation Guide, Documentation Overview

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.4.3 Important Changes

2.4.3.1 EtherMet/IP Adapter Firmware Version V3.6

New firmware version 3.6 for EtherNet/IP-Adapter

2.4.3.2 PROFINET IO-Device Firmware Version V4.5

New firmware version 4.5 for PROFINET IO-Device

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.4.4 Device Description Files cifX

PC Cards cifX System File Name of the Device Description File

POWERLINK 00000044_CIFX RE PLS.xdd

CIFX 104-DP PROFIBUS HIL_0B69.GSD

Table 5: Device Description Files for PC Cards cifX

2.5 Revision or version status of hardware and software

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.5.2 Hardware: Product Components for PC Cards cifX

part number is extended by „/30“

2.5.3 Driver and Software

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

Note: *Unless otherwise indicated, in this manual data to the firmware

If a precedent cifX firmware (without PC/104 recognition) is loaded in

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

2.6 Device Label with Barcode

Figure 1: Example Barcode Label (EAN 39)

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

Interrupt-Steckbrücke / Interrupt Jumper

Figure 2: CIFX 104-RE*

PC Cards cifX PC/104 | Installation, Operation and Hardware Description

3.1.2 CIFX 104-RE-R