PC Cards CIFX 104

User Manual

PC Cards cifX PC/104 (CIFX 104)

Installation, Operation and Hardware Description

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

DOC120206UM44EN | Revision 44 | English | 2015-07 | Released | Public

Table of Contents 2/171

Table of Contents

1 INTRODUCTION.........................................................................................................8

1.1

About the User Manual ...............................................................................................8

1.1.1

1.1.2

1.1.3

1.1.4

List of Revisions ...................................................................................................9

Notes on Hardware, Firmware, Software and Driver Versions ..........................10

Conventions in this Manual ................................................................................12

Used Terminology ..............................................................................................12

1.2

Contents of the Product DVD ...................................................................................13

1.2.1

1.2.2

Installation Guide, Documentation Overview .....................................................13

What's New.........................................................................................................13

1.2.3

1.2.4

Important Changes.............................................................................................13

Device Description Files cifX..............................................................................16

1.3

Legal Notes...............................................................................................................17

1.3.1

Copyright ............................................................................................................17

1.3.2

1.3.3

Important Notes ..................................................................................................17

Exclusion of Liability ...........................................................................................18

1.3.4

1.3.5

1.3.6

1.3.7

1.3.8

Warranty .............................................................................................................18

Export Regulations .............................................................................................19

Registered Trademarks......................................................................................19

EtherCAT Disclaimer..........................................................................................20

Obligation to read and understand the Manual ..................................................20

1.4

Licenses....................................................................................................................20

1.4.1

License Note about VARAN Client.....................................................................20

2 SAFETY ....................................................................................................................21

2.1

General Note ............................................................................................................21

2.2

Intended Use ............................................................................................................21

2.3

Personnel Qualification.............................................................................................22

2.4

Safety Instructions to avoid Personal Injury..............................................................22

2.4.1

Electrical Shock Hazard .....................................................................................22

2.5

Safety Instructions to avoid Property Damage .........................................................23

2.5.1

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

2.5.2

2.5.3

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

Electrostatically sensitive Devices......................................................................24

2.6

Labeling of Safety Messages....................................................................................25

2.6.1

References Safety..............................................................................................25

3 DESCRIPTIONS AND REQUIREMENTS .................................................................26

3.1

Description................................................................................................................26

3.2

PC Cards cifX with integrated Interfaces ..................................................................27

3.2.1

PC Cards PC/104: CIFX 104-XX, CIFX 104-XX-R ............................................27

3.3

PC Cards cifX with AIFX Assembly Interfaces .........................................................27

3.3.1

The Label „\F“ in the Device Name ....................................................................27

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

DOC120206UM44EN | Revision 44 | English | 2015-07 | Released | Public © Hilscher, 2008-2015

Table of Contents

3.3.2

3.3.3

3/171

PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F ......................................28

AIFX Assembly Interfaces ..................................................................................28

3.4

System Requirements ..............................................................................................29

3.4.1

Slot for the PC Cards cifX PC/104 .....................................................................29

3.4.2

3.4.3

3.4.4

Power Supply and Host Interface.......................................................................29

Panel Cutout for Installing AIFX .........................................................................29

System Requirements cifX PC/104 (ISA)...........................................................30

3.5

Requirements for Operation of the PC Cards cifX....................................................31

4 GETTING STARTED.................................................................................................32

4.1

Installation and Configuration PC Card cifX PC/104 ................................................32

4.2

Note on Exchange Service (Replacement Case) .....................................................36

4.3

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

4.4

Device Names in SYCON.net...................................................................................37

4.5

Update for Firmware, Driver and Software ...............................................................38

5 DEVICE DRAWINGS ................................................................................................39

5.1

PC-Karten cifX PC/104 .............................................................................................39

5.1.1

5.1.2

CIFX 104-RE ......................................................................................................39

CIFX 104-RE-R ..................................................................................................40

5.1.3

5.1.4

5.1.5

5.1.6

CIFX 104-RE\F ...................................................................................................41

CIFX 104-RE-R\F ...............................................................................................42

CIFX 104-DP ......................................................................................................43

CIFX 104-DP-R ..................................................................................................44

5.1.7

5.1.8

5.1.9

5.1.10

5.1.11

5.1.12

5.1.1

CIFX 104-CO......................................................................................................45

CIFX 104-CO-R ..................................................................................................46

CIFX 104-DN ......................................................................................................47

CIFX 104-DN-R ..................................................................................................48

CIFX 104-DP\F, CIFX 104-CO\F, CIFX 104-DN\F, CIFX 104-CC\F..................49

CIFX 104-DP-R\F, CIFX 104-CO-R\F, CIFX 104-DN-R\F .................................49

Reverse Side CIFX 104-XX (all Basic Cards and Variants)...............................50

5.2

AIFX Assembly Interfaces ........................................................................................51

5.2.1

Ethernet - AIFX-RE.............................................................................................51

5.2.2

5.2.3

PROFIBUS - AIFX-DP........................................................................................52

CANopen - AIFX-CO ..........................................................................................53

5.2.4

5.2.5

5.2.6

DeviceNet - AIFX-DN .........................................................................................54

CC-Link - AIFX-CC .............................................................................................55

Diagnostic - AIFX-DIAG .....................................................................................56

6 HARDWARE INSTALLATION AND UNINSTALLING ...............................................57

6.1

Safety Messages on Personal Injury ........................................................................57

6.1.1

Electrical Shock Hazard .....................................................................................57

6.2

Property Damage Messages ....................................................................................58

6.2.1

6.2.2

6.2.3

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

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

Electrostatically sensitive Devices......................................................................58




6.3

cifX PC/104: Set Starting Address and Interrupt ......................................................59

6.4

Installing PC Cards cifX PC/104 (PC/104 Modules) .................................................61

6.5

Uninstalling PC Cards cifX PC/104...........................................................................64

7 TROUBLESHOOTING ..............................................................................................65

7.1

Instructions for Problem Solving ...............................................................................65

8 LED DESCRIPTIONS ...............................................................................................66

8.1

Overview LEDs Real-Time Ethernet Systems ..........................................................66

8.2

Overview LEDs Fieldbus Systems............................................................................67

8.3

System LED..............................................................................................................68

8.4

Power On LED..........................................................................................................68

8.5

EtherCAT Master ......................................................................................................69

8.6

EtherCAT Slave ........................................................................................................70

8.7

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

8.8

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

8.9

Open Modbus/TCP ...................................................................................................73

8.10

POWERLINK Controlled Node/Slave .......................................................................74

8.11

PROFINET IO-Controller ..........................................................................................75

8.12

PROFINET IO-Device...............................................................................................76

8.13

sercos Master ...........................................................................................................77

8.14

sercos Slave .............................................................................................................79

8.15

VARAN Client (Slave)...............................................................................................81

8.16

PROFIBUS DP Master .............................................................................................82

8.16.1

1 Communication Status LED ............................................................................82

8.16.2

2 Communication Status LEDs ..........................................................................83

8.17

PROFIBUS DP Slave ...............................................................................................84

8.17.1

8.17.2



8.18

PROFIBUS MPI Device ............................................................................................86

8.18.1


8.18.2


8.19

CANopen Master ......................................................................................................88

8.19.1

8.19.2



8.20

CANopen Slave ........................................................................................................90

8.20.1


8.20.2


8.21

DeviceNet Master .....................................................................................................92

8.22

DeviceNet Slave .......................................................................................................93

8.23

CC-Link Slave...........................................................................................................94

8.24

Slave.........................................................................................................................94




9 DEVICE CONNECTIONS AND SWITCHES .............................................................95

9.1

Ethernet Interface .....................................................................................................95

9.1.1

Ethernet Pin Assignment at the RJ45 Socket ....................................................95

9.1.2

9.1.3

Ethernet Connection Data ..................................................................................96

Use of Hubs and Switches .................................................................................96

9.2

PROFIBUS Interface ................................................................................................97

9.3

CANopen Interface ...................................................................................................97

9.4

DeviceNet Interface ..................................................................................................98

9.5

CC-Link Interface......................................................................................................98

9.6

Mini-B USB Connector (5 Pin) ..................................................................................99

9.7

Rotary Switch Device Address .................................................................................99

9.8

Cable Connector.....................................................................................................100

9.8.1

Pin Assignment for Cable Connector Ethernet ................................................100

9.8.2

9.8.3

Pin Assignment for Cable Connector Fieldbus X3, X304, X4 ..........................101

Pin Assignment for Cable Connector DIAG .....................................................101

9.9

SYNC Connector (Pin-Assignment, Hardware/Firmware) ......................................102

9.9.1

Pin Assignment SYNC Connector, X51 (CIFX 80 90 104C)............................102

9.9.2

9.9.3

Items on Hardware ...........................................................................................102

Items on Firmware............................................................................................102

9.10

Pin Assignment at the PC/104 Bus.........................................................................103

9.10.1

9.10.2

9.10.3

Overview...........................................................................................................103

Reference PC/104 Specification ......................................................................103

Pin Assignment for PC/104 Bus .......................................................................104

10 TECHNICAL DATA .................................................................................................106

10.1

Technical Data PC Cards cifX ................................................................................106

10.1.1

CIFX 104-RE, CIFX 104-RE-R.........................................................................106

10.1.2

10.1.3

CIFX 104-RE\F, CIFX 104-RE-R\F ..................................................................108

CIFX 104-DP, CIFX 104-DP-R.........................................................................110

10.1.4

10.1.5

10.1.6

10.1.7

CIFX 104-DP\F, CIFX 104-DP-R\F ..................................................................111

CIFX 104-CO, CIFX 104-CO-R ........................................................................113

CIFX 104-CO\F, CIFX 104-CO-R\F..................................................................114

CIFX 104-DN, CIFX 104-DN-R ........................................................................116

10.1.8

10.1.9

CIFX 104-DN\F, CIFX 104-DN-R\F ..................................................................117

CIFX 104-CC\F.................................................................................................118

10.1.10

AIFX-RE ...........................................................................................................120

10.1.11

AIFX-DP ...........................................................................................................121

10.1.12

AIFX-CO ...........................................................................................................122

10.1.13

AIFX-DN ...........................................................................................................123

10.1.14

AIFX-CC ...........................................................................................................124

10.1.15

AIFX-DIAG........................................................................................................125

10.2

Technical Data of the Communication Protocols....................................................126

10.2.1

EtherCAT Master..............................................................................................126

10.2.2

10.2.3

10.2.4

EtherCAT Slave................................................................................................127

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

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




10.2.5

10.2.6

10.2.7

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

POWERLINK Controlled Node/Slave...............................................................130

PROFINET IO-Controller..................................................................................131

10.2.8

10.2.9

PROFINET IO-Device (V3.4) ...........................................................................132

PROFINET IO-Device (V3.5) ...........................................................................133

10.2.10

sercos Master ...................................................................................................134

10.2.11

sercos Slave .....................................................................................................135

10.2.12

VARAN Client (Slave).......................................................................................136

10.2.13

PROFIBUS DP Master .....................................................................................137

10.2.14

PROFIBUS DP Slave .......................................................................................138

10.2.15

PROFIBUS MPI................................................................................................139

10.2.16

CANopen Master ..............................................................................................140

10.2.17

CANopen Slave ................................................................................................141

10.2.18

DeviceNet Master.............................................................................................142

10.2.19

DeviceNet Slave ...............................................................................................143

10.2.20

CC Link Slave...................................................................................................144

11 ANNEX....................................................................................................................145

11.1

Device Label with Barcode .....................................................................................145

11.2

Tolerances of the shown Card Dimensions ............................................................146

11.3

Dimensioning PC Cards cifX PC-104 .....................................................................147

11.3.1

CIFX 104-RE ....................................................................................................147

11.3.2

11.3.3

CIFX 104-RE\F .................................................................................................148

CIFX 104-DP ....................................................................................................149

11.3.4

11.3.5

11.3.6

CIFX 104-CO....................................................................................................150

CIFX 104-DN ....................................................................................................151

CIFX 104-FB\F .................................................................................................152

11.4

Dimensioning AIFX Assembly Interfaces................................................................153

11.4.1

Ethernet - AIFX-RE...........................................................................................153

11.4.2

11.4.3

PROFIBUS - AIFX-DP......................................................................................153

CANopen - AIFX-CO ........................................................................................154

11.4.4

11.4.5

11.4.6

DeviceNet - AIFX-DN .......................................................................................154

CC-Link - AIFX-CC ...........................................................................................155

Diagnose - AIFX-DIAG .....................................................................................155

11.5

Notes on earlier Hardeware Revisions ...................................................................156

11.5.1

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

11.6

Disposal of Waste Electronic Equipment................................................................157

11.7

References .............................................................................................................157

11.8

EtherCAT Summary over Vendor ID, Conformance test, Membership and Network

Logo........................................................................................................................158

11.8.1

11.8.2

11.8.3

11.8.4

Vendor ID .........................................................................................................158

Conformance ....................................................................................................158

Certified Product vs. Certified Network Interface .............................................158

Membership and Network Logo .......................................................................158

11.9

List of Figures .........................................................................................................159

11.10

List of Tables ..........................................................................................................160

11.11

Glossary..................................................................................................................163




11.12

Contacts..................................................................................................................171



Introduction

1 Introduction

8/171

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

®

XP, Windows

®

Vista, Windows

®

7 and Windows

®

8, as listed subsequently.

PC Cards cifX PC/104 (CIFX 104) inclusively the AIFX Assembly

Interfaces

1

:

Ethernet (AIFX-RE) for the Real-Time Ethernet systems :

PROFIBUS (AIFX-DP)

CANopen (AIFX-CO)

DeviceNet (AIFX-DN)

CC-Link (AIFX-CC)

Diagnose (AIFX-DIAG) for the fieldbus systems :

EtherCAT

EtherNet/IP

Open-Modbus/TCP

POWERLINK

PROFIBUS DP

PROFIBUS MPI

CANopen

DeviceNet

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 27) and

PC Cards cifX with AIFX Assembly Interfaces

(page

27).

The devices are described in detail in the chapters

Hardware Installation and Uninstalling

(page 57),

LED Descriptions

(page 66),

Device Connections and Switches

(page 95) and

Technical Data

(page 106).

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.

1

The AIFX Assembly Interface is also named as „Detached Network Interface“.



Introduction 9/171

1.1.1 List of Revisions

Index Date

42 14-12-01

7.1, 8.1, 8.2,

8.14, 10.1,

11.11

43 15-02-10

5,

11.1,

11.2, 11.3,

11.4

Chapter

10.2.3

10.2.4

10.2.9

10.2.10

10.2.11

10.2.17

11.7

8.14

8,

11.3,

Revisions

Section Technical Data

EtherCAT Slave

updated.


EtherNet/IP Scanner (Master)

updated.


EtherNet/IP Adapter (Slave)

updated.


PROFINET IO-Device (V3.5)

added.


sercos Master

updated.


sercos Slave

updated.


CANopen Slave

updated.

Section

References

updated.

Items on Safety Messages updated.

Sections

sercos Slave

(LEDs) flashing frequency for Identification, MST

losses, Application error and Watchdog error corrected from 4 Hz to 2 Hz.

Details about the PC card CIFX 104-CC\F as well as for the assembly interface AIFX-CC added.

Sections

Instructions for Problem Solving, Overview LEDs Real-Time

Ethernet Systems

,

Overview LEDs Fieldbus Systems

,

sercos Slave

,

Technical Data PC Cards cifX

,

Glossary

updated and completed.

Note:

‘Preliminary’ status refers only to the sections 11.1 to 11.4. All other parts of this revision are in ‘released’ status.

Chapter

Device Drawings

revised and completed.

Section

Device Label with Barcode

updated.

Section

Tolerances of the shown Card Dimensions

and

Dimensioning PC

Cards cifX PC-104 added.

Section

Dimensioning AIFX Assembly Interfaces

moved to the annex (until rev. 42 in chapter ‘Device Drawings’)

Chapter

Section

LED Descriptions

Table 1: List of Revisions

revised.

Dimensioning PC Cards cifX PC-104

slight corrections added.



Introduction 10/171

1.1.2 Notes on Hardware, Firmware, Software and Driver Versions

Note on Software Update:

The hardware revisions and the versions for the firmware, the driver or the configuration software listed in this section functionally belong together. For existing hardware installation the firmware, the driver and the configuration software must be updated according to the details listed in this section.

For the software upgrade system overview refer to section

Update for

Firmware, Driver and Software

on page 38.

1.1.2.1 Hardware: PC Cards cifX, AIFX Assembly Interfaces

PC Card cifX, AIFX Part No. Hardware

Revision

USB from HW

Rev.

CIFX 104-RE 1278.100 2 1

CIFX 104-RE-R

CIFX 104-RE\F

1

1279.100 2

CIFX 104-RE-R\F

1

1279.101 2

1

2 1

6

1

6

CIFX 104-DP 1278.410 2 1

CIFX 104-DP-R 1279.410 2 1

CIFX 104-DP\F

2

1278.411 1

6

CIFX 104-DP-R\F

2

1279.411 2 1

6

CIFX 104-CO 1278.500 2 1

CIFX 104-CO-R 1279.500 2 1

CIFX 104-CO\F

3

1278.501 1

6

CIFX 104-CO-R\F

3

1279.501 2 1

6

CIFX 104-DN 1278.510 2 1

CIFX 104-DN-R 1279.510 2 1

CIFX 104-DN\F

4

1278.511 1

6

CIFX 104-DN-R\F

4

1279.511 2 1

6

CIFX 104-CC\F

5

1278.741 1

6

1

inclusively Ethernet Assembly Interface

(AIFX-RE)

2

inclusively PROFIBUS Assembly Interface

(AIFX-DP)

3

inclusively CANopen Assembly Interface

(AIFX-CO)

4

inclusively DeviceNet Assembly Interface

(AIFX-DN)

5

inclusively CC-Link Assembly Interface

(AIFX-CC)

6

only when using the Diagnostic Assembly

Interface (AIFX-DIAG)

Table 2: Reference on Hardware PC Cards cifX, AIFX Assembly Interfaces

1.1.2.2 Driver and Software

Driver and Software

SYCON.net netX Configuration Tool-Setup cifX Device Driver

Toolkit

SYCONnet netX setup.exe

netXConfigurationUtility_Setup.exe cifX Device Driver Setup.exe

cifX TCP/IP Server for SYCON.net

US Driver

cifX TCP Server.exe

USB Driver of Windows

®

Table 3: Reference on Driver and Software

Version

1.360.x.x

1.0510.x.x

1.2.x.x

1.1.x.x

V2.1.0.0

5.1.2600.x



Introduction 11/171

1.1.2.3 Firmware

Fieldbus System

CANopen Master

CANopen Slave

CC-Link Slave

DeviceNet Master

DeviceNet Slave

EtherCAT Master

EtherCAT Slave

EtherCAT Slave

EtherNet/IP Adapter

EtherNet/IP Scanner

Firmware File Firmware

Version*

CIFXCOM.NXF

CIFXCOS.NXF 3.6.x.x

CIFXCCS.NXF 2.9.x.x

CIFXDNM.NXF

Minimum Version of the Firmware for

USB Support

-

CIFXDNS.NXF cifxecm.NXF cifxECS.NXF cifxECS.NXF cifxEIS.NXF cifxEIM.NXF

2.5. x.x (V2)

4.2.x.x (V4)

2.7. x.x

2.6. x.x

Minimum Version of the Firmware for

PC Cards cifX PC/104

- from 2.5.13.0 from 2.5.10.0 from 2.3.4.1 from 2.2.4.1 from 2.2.3.0 from 2.2.2.0

POWERLINK Controlled Node cifxPLS.NXF

PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS MPI Device

CIFXDPM.NXF

CIFXDPS.NXF

CIFXMPI.NXF

PROFINET IO Controller

PROFINET IO Device

PROFINET IO Device cifxPNM.NXF cifxPNS.NXF cifxPNS.NXF sercos Master sercos Slave

VARAN Client cifxS3M.NXF cifxS3S.NXF cifxvrs.nxf

2.1. x.x

2.6. x.x

3.4.x.x (V3)

3.5.x.x (V3)

Table 4: Reference on Firmware

Note: *

Unless otherwise indicated, in this manual data to the firmware version correspond to the stack version.

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 section

Hardware: PC Cards cifX, AIFX Assembly Interfaces

on page 10.

The downloadable cifX firmware runs on PC cards cifX

PC/104

. The firmware 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

.



Introduction

1.1.3 Conventions in this Manual

12/171

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

Notes

Important:

<important note you must follow to avoid malfunction>

Note:

<general note>

<note, where to find further information>

Operation Instructions

1. <instruction>

2. <instruction> or

¾ <instruction>

Results

° <result>

Safety Messages

The labeling of safety messages is explained in the chapter

Safety

.

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



Introduction 13/171

1.2 Contents of the Product DVD

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.

1.2.1 Installation Guide, Documentation Overview

The installation guide

Software Installation and Documentation Overview

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

).

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.

The DeviceNet Master firmware from V2.3.11.0 and the DeviceNet Master

DTM from V1.360.x.x support the network scan function. If in the device a firmware version V2.3.10.0 or earlier is used then a firmware update to

V2.3.11.0 or higher must be done, in order to use the

network scan

function.



Introduction 14/171

1.2.3.2 PROFINET IO-Device Firmware Versions 3.4 and 3.5

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

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

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

1. Customize your application program according to the Migration Guide

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

.

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

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

which changes are necessary in the application program in order to use version 3.5.

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

Controller for this:

GSDML-V2.3-HILSCHER-CIFX RE PNS-20130301.xml.

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

3.5.

Note also:

•

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

•

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

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

•

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

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

PROFINET IO-Device V3.4

Directory on the DVD \ File:

PROFINET IO-Device V3.5


Firmware

Header

GSDML

Firmware\CIFX\cifxpns.nxf Firmware\CIFX\PNS V3.5.X\cifxpns.nxf

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

Device V3.4.X

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

RE PNS-20130225.xml

Protocol API

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

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

Protocol API 13 EN.pdf

TCP IP - Packet Interface API 13 EN.pdf

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

Device V3.5.X

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

CIFX RE PNS-20130301.xml

Documentation\7. Programming Manuals\EN\3.

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

Device V3.5 Protocol API 06 EN.pdf

PROFINET IO Device - Migration from Version 3.4 to

3.5 MG 03 EN.pdf

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

API Manual



Introduction 15/171

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

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

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

1. Customize your application program according to the Migration Guide

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

.

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

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

which changes are necessary in the application program in order to use version 4.2.

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

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

Hilscher CIFX RE ECS V4.2.X.xml.

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

Note also:

•

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

•

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

•

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

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

EtherCAT-Slave V2.5


EtherCAT-Slave V4.2


Firmware\CIFX\cifxecs.nxf Firmware\CIFX\ECS V4.X\cifxecs.nxf

Firmware

Header

XML

Examples and API\0. Header\Firmware\EtherCAT

Slave V2.5.X

EDS\EtherCAT\Slave\V2.X\Hilscher CIFX RE ECS

V2.2.X.xml

Protocol API

Documentation\7. Programming Manuals\EN\3.

Protocol API\EtherCAT Slave V2\EtherCAT Slave

Protocol API 21 EN.pdf

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

V4.2.X

EDS\EtherCAT\Slave\V4.X\Hilscher CIFX RE ECS

V4.2.X.xml

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

API\EtherCAT Slave V4\EtherCAT Slave V4 Protocol API

03 EN.pdf

EtherCAT Slave - Migration from Version 2.5 to 4.2 MG 02

EN.pdf

Object Dictionary V3 03 API EN.pdf

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

Manual



Introduction 16/171

1.2.4 Device Description Files cifX

PC Cards cifX

CIFX 104-RE

CIFX 104-RE-R

CIFX 104-RE\F

CIFX 104-RE-R\F

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.

System File Name of the Device Description File

EtherCAT Slave For the EtherCAT Slave Firmware V2.5:

Hilscher cifX RE ECS V2.2.x.xml

(or with extension DDF)

For the EtherCAT Slave Firmware with V4.2.1.0 the

Hilscher

CIFX RE ECS V4.2.X.xml

is provided.

Note!

If the XML file

Hilscher cifX RE ECS V2.

2

.x.xml

is used/re-installed, the firmware must be used/re-installed at the Version

2.

5

.x

.

EtherNet/IP Adapter (Slave)

HILSCHER CIFX-RE EIS V1.1.EDS

EtherNet/IP Scanner (Master)

HILSCHER CIFX-RE EIM V1.0.eds

Note!

The description files for the EtherNet/IP Master device is needed, when an additional EtherNet/IP Master device shall communicate to a Hilscher EtherNet/IP

Master device via EtherNet/IP.

POWERLINK-Controlled-

Node/Slave

00000044_CIFX RE PLS.xdd

PROFINET IO-Device For the PROFINET IO Device Firmware V3.4:

GSDML-V2.3-HILSCHER-CIFX RE PNS-20130225.xml

For the PROFINET IO Device Firmware with V3.5.13.1

the

GSDML-V2.3-HILSCHER-CIFX RE PNS-20130301.xml

is provided.

sercos Slave

Hilscher CIFX RE S3S FixCFG FSPIO Default.xml,

Hilscher CIFX RE S3S VarCFG FSPDrive.xml

System

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.

File Name of the Device Description File

PROFIBUS

DP Slave

HIL_0B69.GSD

PC Cards cifX

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

CANopen-Slave

DeviceNet Slave

CIFX CO COS.eds

CIFX_DN_DNS.EDS

CC-Link Slave

cifx-ccs_1.csp, cifx-ccs_2.csp, cifx-ccs_3.csp, cifx-ccs_4.csp,

(for one, two, three or four Remote Device Station), cifx-ccs_io.csp (for one Remote IO Device Station)

Table 7: Device Description Files for PC Cards cifX



Introduction 17/171

1.3.1 Copyright

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

All rights reserved.

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

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

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

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

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

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

The manual delivered with the product applies.

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



Introduction 18/171

1.3.3 Exclusion of Liability

The software was produced and tested with utmost care by Hilscher

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

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

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

•

for military purposes or in weapon systems;

•

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

•

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

•

in life support systems;

•

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

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

1.3.4 Warranty

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



Introduction 19/171

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

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

Windows

®

XP, Windows

®

Vista, Windows

®

7 and Windows registered trademarks of Microsoft Corporation.

®

8 are

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 is a registered trademark of Mitsubishi Electric Corporation, Tokyo,

Japan.

DeviceNet™ and EtherNet/IP™ are trademarks of ODVA (Open DeviceNet

Vendor Association, Inc).

EtherCAT

®

is a registered trademark and a patented technology of

Beckhoff Automation GmbH, Verl, Germany

, formerly Elektro Beckhoff

GmbH.

Modbus is a registered trademark of Schneider Electric.

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

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

PROFIBUS

®

and PROFINET

®

are registered trademarks of PROFIBUS &

PROFINET International (PI), Karlsruhe. sercos and sercos interface are registered trademarks of sercos international e. V., Suessen, Germany.

PC/104™ is a trademark of the PC/104 Consortium (pc104.org).

All other mentioned trademarks are property of their respective legal owners.



Introduction 20/171

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

1.3.8 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 providing the product manuals.

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

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



Safety

2 Safety

21/171

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, Safety Messages, Property

Damage Messages and all valid legal regulations have to be obeyed.

Technical knowledge is presumed. The user has to assure that all legal regulations are obeyed.

PC Cards cifX

CIFX 104-RE

CIFX 104-RE-R

CIFX 104-RE\F

CIFX 104-RE-R\F

AIFX

AIFX-RE, AIFX-DIAG

AIFX-DP, AIFX-DIAG

AIFX-CO, AIFX-DIAG

AIFX-DN, AIFX-DIAG

AIFX-CC, AIFX-DIAG

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.

Real-Time Ethernet System PC Cards cifX Fieldbus System

PROFIBUS DP Master,

PROFIBUS DP Slave,

PROFIBUS MPI Device

EtherCAT Master,

EtherCAT Slave

EtherNet/IP Scanner (Master),

EtherNet/IP Scanner (Slave)

CIFX 104-DP

CIFX 104-DP-R

CIFX 104-DP\F

CIFX 104-DP-R\F

Open-Modbus/TCP

POWERLINK Controlled Node/Slave

CIFX 104-CO-R

CIFX 104-CO\F

CIFX 104-CO-R\F

PROFINET IO-Controller (Master),

PROFINET IO-Device (Slave) sercos Master, sercos Slave

VARAN Client (Slave)

CIFX 104-DN

CIFX 104-DN-R

CIFX 104-DN\F

CIFX 104-DN-R\F

CIFX 104-CC\F

CANopen Master,

CANopen Slave

DeviceNet Master,

DeviceNet Slave

CC-Link slave

Table 8: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby

The

AIFX Assembly 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.

PC Cards cifX with AIFX Assembly Interface

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

Table 9: PC Cards cifX with AIFX Assembly Interface



Safety 22/171

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

•

Safety and health at work

•

Mounting and connecting of electrical equipment

•

Measurement and Analysis of electrical functions and systems

•

Evaluation of the safety of electrical systems and equipment

•

Installing and Configuring IT systems

2.4 Safety Instructions to avoid Personal Injury

To ensure your own personal safety and to avoid personal injury, you necessarily must read, understand and follow the following safety instructions and safety messages in this manual about danger causing personal injury, before you install and operate your PC card cifX.

The danger of a lethal electrical shock caused by parts with more than 50V may occur if you open the PC cabinet to install the PC card cifX.

•

HAZARDOUS VOLTAGE is present inside of the PC or of the connecting device, into which the PC card cifX is integrated. Strictly obey to all safety rules provided by the device’s manufacturer in the documentation!

•

First disconnect the power plug of the PC or of the connecting device, before you open the cabinet.

•

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

•

Open the PC cabinet and install or remove the PC card cifX only after disconnecting power.

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

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

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

Reference Safety [S2]



Safety 23/171

2.5 Safety Instructions to avoid Property Damage

To avoid property damage respectively device destruction to the PC card cifX and to your system, you necessarily must read, understand and follow the following safety instructions and safety messages in this manual about danger causing property damage, before you install and operate your PC card.

2.5.1 Device Destruction by exceeding allowed Supply Voltage

To avoid device destruction 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 allowed 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 allowed 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

29. There the required and permitted supply voltage is provided by device

type inclusively the permitted tolerance range.

2.5.2 Device Destruction by exceeding allowed Signaling Voltage

To avoid device destruction 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


Interface

on page 29. There the required and permitted signaling voltage

is provided by device type.



Safety 24/171

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 25/171

2.6 Labeling of Safety Messages

•

The

Section Safety Messages

at the beginning of a chapter are pinpointed particularly and highlighted by a signal word according to the degree of endangerment. The kind of danger is specified exactly by the safety message text and

optionally

by a specific safety sign.

•

The within an instruction description are highlighted with a signal word according to the degree of endangerment.

The kind of danger is specified exactly by the safety message text.

Signal Word Meaning (international) Meaning (USA)

Indicates a Hazardous Situation Which if not

Avoided, will Result in Death or Serious Injury.

Safety Sign

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

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

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

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

USA Sort of Warning or Principle

Warning of Lethal Electrical Shock


Avoided, could Result in Death or Serious

Injury.


Avoided, may Result in Minor or Moderate

Injury.

Principle: Disconnect the Power Plug

Table 10: Signal Words and Safety Signs in Safety Messages on Personal Injury

Signal Word Meaning (international and USA)

Indicates a Property Damage Message.

Safety Sign Sort of Warning or Principle

Warning on Damages by Electrostatic Discharge

-

Example: Warning on Device Destruction due by too high supply voltage

Table 11: Signal Words and Safety Signs in Safety Messages on Property Damage

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

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

Product Manuals, Instructions, and Other Collateral Materials

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

[S3] EN 61340-5-1 and EN 61340-5-2 as well as IEC 61340-5-1 and IEC 61340-5-2



Descriptions and Requirements 26/171

3.1 Description

The PC cards cifX are communication interfaces of the cifX product family of Hilscher on the basis of the communication controller netX 100 for the

Real-Time Ethernet or fieldbus communication. Depending of the loaded firmware, the protocol specific

PC card cifX proceeds the communication of the corresponding Real-Time Ethernet or fieldbus system.

The used Real-Time Ethernet systems are: The used fieldbus

systems are:

EtherCAT Master

EtherCAT Slave


PROFIBUS DP Master

PROFIBUS DP Slave

PROFIBUS MPI Device


Open-Modbus/TCP

POWERLINK-Controlled-Node/Slave

PROFINET IO-Controller (Master)

CANopen Master

CANopen Slave

DeviceNet Master

DeviceNet Slave

CC-Link Slave PROFINET IO-Device (Slave)

sercos Master

sercos Slave


The PC card cifX handles the complete data exchange between the connected Ethernet or fieldbus devices and the PC. The data exchange is proceeded via dual-port memory.




3.2 PC Cards cifX with integrated Interfaces

The PC cards PC/104 CIFX 104-XX and CIFX 104-XX-R provide integrated

Ethernet, fieldbus or diagnostic interfaces.

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

CIFX 104-RE-R

PROFIBUS

CIFX 104-DP

Real-Time Ethernet Master or Slave

Real-Time Ethernet Master or Slave (connectors at the left side)

PROFIBUS DP Master or Slave and PROFIBUS MPI Device

PROFIBUS DP Master or Slave and PROFIBUS MPI Device (connectors at the left side) CIFX 104-DP-R

CANopen

CIFX 104-CO

CIFX 104-CO-R

CANopen Master or Slave

CANopen Master or Slave (connectors at the left side)

DeviceNet

CIFX 104-DN

CIFX 104-DN-R

DeviceNet Master or Slave

DeviceNet Master or Slave (connectors at the left side)

Table 12: PC Cards PC/104: CIFX 104-XX and CIFX 104-XX-R

3.3 PC Cards cifX with AIFX Assembly Interfaces

3.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 an assembly 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 assembly interface (AIFX-RE).

•

The basic cards CIFX 104-FB\F and CIFX 104-FB-R\F are equipped with a

Cable Connector Fieldbus

, to connect the PROFIBUS assembly interface (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 assembly interface (AIFX-

DIAG).

Important!

Operating the PC cards cifX PC/104 with AIFX assembly interface (label “

\F

” in the device name) requires proper connection of the

Ethernet (AIFX-RE), PROFIBUS (AIFX-DP), CANopen (AIFX-CO),

DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) assembly interface to the basic card!




3.3.2 PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F

PC Card cifX Description

PC Cards PC/104 with AIFX Assembly Interfaces


CIFX 104-RE\F

CIFX 104-RE-R\F

Real-Time Ethernet Master or Slave

- Basic card CIFX 104-RE\F and

- Ethernet assembly interface (AIFX-RE).

Real-Time Ethernet Master or Slave

(connectors at the left side)

- Basic card CIFX 104-RE-R\F and

- Ethernet assembly interface (AIFX-RE).

PROFIBUS

CIFX 104-DP\F

CIFX 104-DP-R\F

PROFIBUS DP Master or Slave or PROFIBUS MPI Device

- Basic card CIFX 104-FB\F and

- PROFIBUS assembly interface (AIFX-DP).

PROFIBUS DP Master or Slave or PROFIBUS MPI Device


- Basic card CIFX 104-FB-R\F and

- PROFIBUS assembly interface (AIFX-DP).

CANopen

CIFX 104-CO\F

CIFX 104-CO-R\F

CANopen Master or Slave


- CANopen assembly interface (AIFX-CO).

CANopen Master or Slave



- CANopen assembly interface (AIFX-CO).

DeviceNet

CIFX 104-DN\F

CIFX 104-DN-R\F

DeviceNet Master or Slave


- DeviceNet assembly interface (AIFX-DN).

DeviceNet Master or Slave



- DeviceNet assembly interface (AIFX-DN).

CC-Link

CIFX 104-CC\F

CC-Link Slave


- CC-Link assembly interface (AIFX-CC).

Table 13: PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F

AIFX

AIFX-RE

AIFX-CO

AIFX-DN

AIFX-CC

AIFX-DIAG

(optional)

Description

Ethernet Assembly Interface (with Ethernet interface)

CANopen Assembly Interface (with CANopen interface)

DeviceNet Assembly Interface (with DeviceNet interface)

CC-Link Assembly Interface (with CC-Link interface)

Diagnostic Assembly Interface (with diagnostic interface)

For the PC Cards cifX



CIFX 104-CO\F, CIFX 104-CO-R\F

CIFX 104-DN\F, CIFX 104-DN-R\F

CIFX 104-CC\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

Table 14: AIFX Assembly Interfaces for PC Cards cifX with Cable Connector




3.4.1 Slot for the PC Cards cifX PC/104

PC with slot (5 V) for PC cards cifX

PC/104

:

PC Cards cifX

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

Bus [Pins] Slot

104

PC/104 Slot

(5 V)

Table 15: Slot for the PC Cards cifX PC/104

3.4.2 Power Supply and Host Interface

PC Cards cifX

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

For the power supply and the host interface used for the PC cards cifX

PC/104

you must observe the following requirements:

Supply

Voltage

Signaling Voltage

Host Interface

Host Interface

(PCI slot)

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

+5 V dc ±5 %/

Typ. 500 mA

5 V Input compatible,

5 V TTL Output compatible

(Uout

≥

2,4 V

@

6 mA)

PC/104

Table 16: Requirements Power Supply and Host Interface for PC Cards cifX PC/104

The data in the

Table 16

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

3.4.3 Panel Cutout for Installing AIFX

PC Card cifX

PC/104

In order to connect the AIFX assembly 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.

Panel Cutout

at the front plate of the PC cabinet

Table 17: Panel Cutout at the at the front plate of the PC cabinet



Descriptions and Requirements

PC Cards cifX

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

30/171

AIFX

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.

Panel Cutout and Holes

AIFX-RE

AIFX-DP

AIFX-CO

Required Cutout for two RJ45 Sockets

Important!

The panel cutout layout must also cover the

LEDs COM 0 and COM1 at the AIFX-RE.

Standard cutout

Holes

D-Sub-15

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

Required Cutout

Standard cutout for Dsub female Connector, 9 pin

D-Sub-9

Holes 2, distance between the holes 25 mm

Further Information in section

PROFIBUS - AIFX-DP

on page 52.

Required Cutout for D-Sub male Connector, 9 pin

CIFX 104-DN\F

CIFX 104-DN-R\F

CIFX 104-CC\F

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

AIFX-DN

AIFX-CC

AIFX-DIAG

Standard cutout D-Sub-9

Holes 2, distance between the holes 25 mm


CANopen - AIFX-CO

on page 53.

Required Cutout for CombiCon male Connector, 5 pin

Standard cutout

Holes

D-Sub-9

2x2, distance between the holes 24,94 mm


DeviceNet - AIFX-DN

on page 54.

Required Cutout

Standard cutout

Holes for CombiCon male Connector, 5 pin

CombiCon male Connector

2x2, distance between the holes 24,96 mm


CC-Link - AIFX-CC

on page 55.

Required Cutout for the light channels, the rotary switch and the Mini B USB plug

Standard cutout -

Holes 2, distance between the holes 47,1 mm


Diagnostic - AIFX-DIAG

on page 56.

Table 18: Required Panel Cutout and Holes for AIFX

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



Descriptions and Requirements



31/171

3.5 Requirements for Operation of the PC Cards cifX

Protocols

Software

Installation

How to use the

Software

Firmware

Download

Parameter

Setting

Communication

Hardware

Installation

Environmental

Conditions

Operating the PC cards cifX properly, the following described requirements must be fulfilled.

EtherCAT Slave,

EtherCAT Master,

EtherNet/IP Adapter (Slave),


Open-Modbus/TCP,

POWERLINK-Controlled-Node/Slave,

PROFINET IO Device (Slave),

PROFINET IO Controller (Master) sercos Slave, sercos Master,


PROFIBUS DP Slave,

PROFIBUS DP Master,

PROFIBUS MPI Device,

CANopen Slave,

CANopen Master,

DeviceNet Slave,

DeviceNet Master,

CC-Link Slave

1. Driver for the Host Interface

Host Interfaces: PC/104

• The device driver

cifX Device Driver

must be installed (from V1.0.x.x).

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


necessarily on the current version indicated in section

Driver and Software

on page 10.

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.

On how to use the software for the configuration, the firmware download and for the diagnosis, note 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.

3. Using the configuration software

SYCON.net

or for the Slave alternatively the Slave configuration tool


, the user must select and download the firmware to the PC card cifX.

4. The PC card cifX must be parameterized using one of the following options:

• Configuration Software

SYCON.net

• alternatively Slave configuration tool


(only Slave)

• Application program (programming required)

5. For the communication of a PC card cifX (Slave) a Master device for the respective communication system is required. For the communication of a PC card cifX (Master) a Slave device for the respective communication system is required.

Important!

Operating the PC cards cifX with

Cable Connector Ethernet

or with the

Cable

Connector Fieldbus

(label “

\F

” in its device name) requires proper connection of the

Ethernet (AIFX-RE), PROFIBUS (AIFX-DP), CANopen (AIFX-CO), DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) assembly interface to the basic card!

Due to a plug element from ERNI the lower limit of the operating temperature for all PC cards cifX

Real-Time Ethernet is 0 °C. This applies to all hardware revisions of the PC card cifX Real-Time

Ethernet.

Table 19: Requirements to operate PC Cards cifX properly

© Hilscher, 2008-2015

Getting Started 32/171

4.1 Installation and Configuration PC Card cifX PC/104

# Step

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


. The Master device can be configured using the corresponding Master DTM in the configuration software

SYCON.net

.

Description Page For detailed information see manual / section

1

1.1

Installing Driver and

Software

Installing


1.2

Installing USB Driver

Depending by device type / features

1.3 Reserve

Memory

Range / Interrupt

at the operating system.

Enter the Communication Solutions DVD in the PC and follow to the instructions of the installation wizard, to install the driver.

Only for PC Cards cifX PC/104: equipped with an USB interface or with the diagnostic assembly interface (AIFX-DIAG).

Reserve for the PC card cifX the memory range and if necessary one interrupt at the 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:

Start the

netX Configuration Tool setup

program to install the

netX Configuration

Tool

.

2 Preparing Hardware

Installation

2.1 Take precautions on

Electrostatically sensitive Devices

Electrostatically sensitive Devices

Make sure, that the PC card cifX is grounded via the endplate and the PC and make sure, that you are discharged when you install/ uninstall the PC Card cifX.

2.2 Set

Starting Address

and

Interrupt

2.3 Set

Data Bus Width

. Depending by the target system

(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 precautions.

3.1 Take safety precautions

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

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

Make sure, that the power supply is off at the

PC or at the connecting device.

Refer to User Manual

Software Installation for the PC Cards cifX

Electrostatically sensitive

Devices

cifX PC/104: Set Starting

Address and Interrupt

Device Drawings

24

59

39

Hardware Installation and Uninstalling

57

Electrical Shock Hazard

22



Getting Started

# Step Description For detailed information see manual / section

Installing PC Cards cifX

PC/104

33/171

Page

61

3.3

3.4

3.7 Plug the connecting cable to the Master or

Slave

4

Installing cifX

If so, plug module

(only for PC Cards cifX

PC/104 with label “\F” in its device name and with Cable Connector

Ethernet X4 or

Fieldbus X3)

3.8 Connect the PC to the power / switch on.

Notice on how to use the Software

4.1 For the configuration, the firmware download and for the diagnosis, note:

Now open the cabinet of the PC or of the connecting device.

Plug in and mount the PC card cifX.

(a) Install the first PC/104 module on the mainboard.

(b) Install any other PC/104 module on the respective underlying PC/104 module.

Important!

Operating the PC cards cifX with AIFX assembly interface requires proper connection of the

AIFX-RE, AIFX-DP, AIFX-CO,

AIFX-DN or AIFX-CC assembly interface to the basic card!

If so, connect an Ethernet (AIFX-RE),

PROFIBUS (AIFX-DP), CANopen (AIFX-CO),

DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) assembly interface.

If so, additionally connect an diagnostic assembly interface (AIFX-DIAG).

To the basic card of each PC card cifX first connect the AIFX-RE, AIFX-DP, AIFX-CO,

AIFX-DN, AIFX-CC or AIFX-DIAG assembly interface to the PC card cifX and check if the connector is plugged in correctly. Only then plug another PC/104 module.

Close the cabinet of the PC or connecting device.

Note for all PC Cards cifX Real-Time

Ethernet:

Note!

The RJ45 socket is only for use in LAN, not for telecommunication circuits.

Note for PC Cards cifX PROFINET IO

Controller:

Important for Hardware Wiring!

Connect only ports with each other, which have different cross-over settings. Otherwise a connection between the devices can not be established. If the port settings of the PC card cifX PROFINET IO controller are not set to AUTO, then Port0 is switched uncrossed and Port1 crossed.

Plug in the connecting cable from the PC card cifX to the PC card Master or Slave.

Connect the PC or the connecting device to the power supply and switch it on.

Use only

one

Software.

Important!

To avoid communication problems with the device, use the

USB interface, the serial interface as well as the cifX Device Driver exclusively with

one

software, that is

SYCON.net

or

netX Configuration

Tool

.

The Label „\F“ in the

Device Name

Ethernet Interface

See corresponding user manual

Requirements for

Operation of the PC

Cards cifX

27

95

31



Getting Started

# Step Description

5

5.1

Configuring Slave using SYCON.net

Firmware Download

Firmware Slave:

Download Firmware and Configuration

Use the corresponding Slave DTM in the configuration software

SYCON.net

.

- Start configuration software

SYCON.net

,

- Create new project /Open existing project,

- Insert Slave into configuration,

- Select driver and assign device.

- Select and download the firmware.

EtherCAT Slave,

EtherNet/IP Adapter,

Open-Modbus/TCP,

POWERLINK-

Controlled-Node/Slave,

PROFINET IO Device, sercos Slave,

VARAN Client,

PROFIBUS DP Slave,

PROFIBUS MPI

Device,

CANopen Slave,

DeviceNet Slave,

CC-Link Slave

-Configure the PC card cifX (Slave). 5.2 Configuration cifX (Slave)

5.3 Download

Configuration

6

OR

Configuring

Slave using netX


6.1 Downloading Firmware and Configuration

(Slave)

- Download the configuration to the PC card cifX (Slave)


If SYCON.net was already used on the PC, stop the ODMV3 service. Therefore, select

Service > Stop

from the context menu of the

ODMV3 system tray icon.

For detailed information see manual / section


Device Names in

SYCON.net

Requirements for

Operation of the PC

Cards cifX

34/171

Page

37

31

The ODMV3 system tray icon changes to

ODMV3 Service stopped

.

7

7.1

Configuring Master using SYCON.net

Firmware Download

Firmware Master:

In the


:

- select the Firmware protocol,

- Set the PC card cifX (Slave) parameters.

- Select

Apply

.

The selected firmware and the configuration are downloaded to the replacement card cifX.

The configuration is saved to the hard disk of the PC.


Use the corresponding Master DTM in the configuration software

SYCON.net

.

- Start configuration software

SYCON.net

,

- Create new project /Open existing project,

- Insert Master into configuration,

- Select driver and assign device.

- Select and download the firmware.

EtherCAT Master,

EtherNet/IP Scanner,

PROFINET IO

Controller,

PROFIBUS DP Master,

CANopen Master,

DeviceNet Master

- Configure the PC card cifX (Master). 7.2 Configuration cifX (Master)



See Operating

Instruction Manual netX

Configuration Tool for cifX, comX and netJACK


Device Names in

SYCON.net

Notes for the

Configuration of the

37

36

© Hilscher, 2008-2015


# Step

7.3 Download

Configuration

8 Diagnosis by

SYCON.net

(Slave and Master)

8.1 Diagnosis Steps

(Master and Slave)

Description For detailed information see manual / section

Master Device

Page

- Download the configuration to the PC card cifX (Master).

Diagnosis, I/O Data

Use the corresponding Slave or Master DTM in the configuration software

SYCON.net

.

- In netDevice rightclick on device symbol.

- Select context menu entry

Diagnosis

,

- then select

Diagnosis > General

or

Firmware Diagnosis

,

- or select

Diagnosis > Extended Diagnosis

.

- 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 by netX Configuration

Tool

(only Slave)

9.1 Diagnosis Steps

(Slave)

Diagnosis

If SYCON.net was already used on the PC, stop the ODMV3 service. Therefore, select

Service > Stop

from the context menu of the

ODMV3 system tray icon.

In the


:

- In the navigation area click on

Diagnostic

,

- click in the

Diagnostic

pane to

Start

, to start the communication to the Master device and to run the diagnosis.

- click on

Extended

, to run the extended diagnosis.

See Operating

Instruction Manual netX

Configuration Tool for cifX, comX and netJACK

Table 20: Steps for the Software and Hardware Installation, the Configuration and for the

Diagnosis of a PC Card cifX PC/104 (Master and Slave)




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

4.3 Notes for the Configuration of the Master Device

System Note

To configure the Master, a device description file is required. Please note the following notes for the configuration of the Master Device:

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.

EtherNet/IP

Adapter

POWERLINK-

Controlled-

Node/Slave

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.

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

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

To configure the Managing Node/Master, an XDD file (device description file) is required. The settings in the used Managing Node/Master must comply with the settings in the Controlled

Node/Slave, to establish communication. Important parameters are: Vendor ID, Product Code,

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

PROFINET IO

Device

To configure the Controller, a GSDML file (device description file) is required. The settings in the used Controller must comply with the settings in the Device to establish communication.

Important parameters are: Station Name, Vendor ID, Device ID, Input and Output Data Bytes.

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

sercos Slave

PROFIBUS DP

Slave

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

To configure the Master, a GSD 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: Station Address, Ident Number, Baudrate and Config Data (the configuration data for the output and input length).

To configure the Master, an EDS file (device description file) is required. The settings in the used Master must comply with the settings in the Slave to establish communication. Important parameters are: Node Address and Baudrate.

DeviceNet Slave

To configure the Master, an EDS file (device description file) is required. The settings in the used Master must comply with the settings in the Slave to establish communication. Important parameters are: MAC ID, Baudrate, Produced Size, Consumed Size, Vendor ID, Product Type,

Product Code, Major Rev, Minor Rev.



Getting Started

System

CC-Link Slave

37/171

Note

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 21: 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.

4.4 Device Names in SYCON.net

PC Cards cifX

CIFX 104-RE,

CIFX 104-RE-R

CIFX 104-RE\F

CIFX 104-RE-R\F

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. Furthermore, the table shows, for which protocol which device must be selected from the device catalog to configure the PC card cifX with SYCON.net.

Protocol DTM Specific Group Device Name in

SYCON.net

EtherCAT Master Master CIFX RE/ECM

EtherCAT Slave



Gateway/Stand-Alone Slave

Master


CIFX RE/ECS

CIFX RE/EIM

CIFX RE/EIS

Open-Modbus/TCP Gateway/Stand-Alone RE/OMB

POWERLINK-Controlled-

Node/Slave

PROFINET IO-Controller

PROFINET IO-Device


Master


CIFX RE/PLS

CIFX RE/PNM

CIFX RE/PNS sercos Master sercos Slave


Master



CIFX RE/S3M

CIFX RE/S3S

CIFX RE/VRS

CIFX 104-DP

CIFX 104-DP-R

CIFX 104-DP\F

CIFX 104-DP-R\F

PROFIBUS DP Master

PROFIBUS DP Slave

Master

Gateway/ Stand-Alone Slave

CIFX DP/DPM

CIFX DP/DPS

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

PROFIBUS MPI Device

CANopen Master


Master

CIFX DP/MPI

CIFX CO/COM

CANopen Slave

DeviceNet Master


Master

CIFX CO/COS

CIFX DN/DNM

DeviceNet Slave Gateway/ Stand-Alone Slave CIFX DN/DNS

CC-Link Slave

Gateway/

Stand-Alone Slave

CIFX CC/ CCS

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




4.5 Update for Firmware, Driver and Software

Note:

As a pre-requirement for the software update the project files, the configuration files and firmware files are to be saved.

At existing hardware installation the firmware, the driver and the configuration software must be updated according to the versions given in section

Notes on Hardware, Firmware, Software and Driver

on page 10.

The following graphic gives an overview:

Figure 1: System Overview cifX to update Firmware, Driver and Software

Note the specific details for devices with

PC/104 bus

in section

Firmware

on page 11.



Device Drawings 39/171

5.1 PC-Karten cifX PC/104

System LED

(gelb/grün) /

(yellow/green)

Kommunikationsstatus-LED 0 und 1

(rot/grün) /

Communication Status LED 0 and 1

(red/green)

SYNC-Anschluss /

SYNC Connector

(X51, 3-polig /

3 pin

)

Steckbrücke Datenbusbreite 8 Bit und 16 Bit

(J9, im Bild Einstellung Steckbrücke für 16 Bit)

Data Bus Width Jumpers 8 Bit and 16 Bit

(

J9,

Jumper Settings for 16 Bit shown)

Ethernet RJ45-Buchse /

RJ45 Socket

(X6)

Kanal 0 /

Channel 0 (CH 0)

Kanal 1 /

Channel 1 (CH 1)

LED grün /

green

LED gelb /

yellow

Mini-B-USB-Buchse /

Mini B USB Plug

(X5, 5-polig /

5 pin

)

Drehschalter Geräteadresse /

Rotary Switch Device Address

(ohne Funktion /

without function

)

(x16)

(x1)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)

Interrupt-Steckbrücke /

Interrupt Jumper

(J8, 11-polig /

11 pin

)

Adresssteckbrücke /

Address Jumpers

(J7, 7-polig /

7 pin

)

Standardeinstellungen Steckbrücken /

Default Jumper Settings

Figure 2: CIFX 104-RE*

Note:

*Device supports

Auto Crossover

Function.

With loaded

EtherCAT Master

firmware only the RJ45 channel 0 can be used, channel 1 is deactivated. Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated.

For

Open Modbus/TCP

with V2.3.4.0 and higher both Rj45channels can be used.

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 23: Starting Address and Interrupt for

16 KByte Dual-Port Memory

on page 59.

The meaning of the

LEDs

depends from the loaded firmware. See chapter

LED Descriptions

beginning from page 66.

For the pin assignment of the

PCI/104

bus X1/X2 refer to section

Pin

Assignment for PC/104 Bus

on page 104.


SYNC

Connector refer to section

Pin

Assignment SYNC Connector, X51

on page 102.

For further information on the

Mini-B USB


Mini-B USB Connector (5 Pin)

on page 99.






(X51, 3-polig /

3 pin

)




(

J9,


System LED

(gelb/grün) /

(yellow/green)

Kommunikationsstatus-LED 0 und 1

(rot/grün) /

Communication Status LED 0 and 1

(red/green)


RJ45 Socket

(X306)

Kanal 1 /

Channel 1 (CH 1)

Kanal 0 /

Channel 0 (CH 0)

LED grün /

green

LED gelb /

yellow

(x1)

(x16)



(X305, 5-polig /

5 pin

)



(ohne Funktion /

without function

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Figure 3: CIFX 104-RE-R*

Note:

*Device supports

Auto Crossover

Function.

With loaded

EtherCAT Master

firmware only the RJ45 channel 0 can be used, channel 1 is deactivated. Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated.

For

Open Modbus/TCP

with V2.3.4.0 and higher both Rj45channels can be used.

In

Interrupt Mode


Polling Mode

.




on page 59.

The meaning of the

LEDs

depends from the loaded firmware. See chapter

LED Descriptions



PCI/104


Pin


on page 104.


SYNC


Pin


on page 102.


Mini-B USB



on page 99.



Device Drawings

System-LED

(gelb/grün) /

(yellow/green)



(X51, 3-polig /

3 pin

)

41/171




(

J9,


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

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



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.

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


SYNC


Pin


on page 102.






(X51, 3-polig /

3 pin

)




(

J9,


System LED

(gelb/grün) /

(yellow/green)



(X304, 20-polig /

20 pin

)



(X303, 12-polig /

12 pin

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 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


In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


SYNC


Pin


on page 102.



Device Drawings

System LED

(gelb/grün)

(yellow/green)

Kommunikationsstatus-LED

(rot/grün)

Communication Status LED

(red/green)

PROFIBUS-Schnittstelle

DSub-Buchse (X400B, 9-polig)

PROFIBUS Interface

DSub female Connector

(X400B, 9 pin)

43/171




(

J9,




(X5, 5-polig /

5 pin

)



(ohne Funktion /

without function

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)

(x16)

(x1)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Figure 6: CIFX 104-DP

Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.







(

J9,


System LED

(gelb/grün) /

(yellow/green)

Kommunikations-LED

(rot/grün) /

Communication LED

(red/green)


DSub-Buchse (X400, 9-polig)


DSub female Connector (X400, 9 pin)

(x1)



(X305, 5-polig /

5 pin

)

(x16)



(ohne Funktion /

without function

)

Figure 7: CIFX 104-DP-R

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.



Device Drawings

System LED

(gelb/grün)

(yellow/green)

CAN LED

(rot/grün)

(red/green)

CANopen-Schnittstelle

DSub-Stecker (X400B, 9-polig)

CANopen Interface

DSub male Connector (X400B, 9 pin)

45/171




(

J9,




(X5, 5-polig /

5 pin

)



(ohne Funktion /

without function

)

(x16)

(x1)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Figure 8: CIFX 104-CO

Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.







(

J9,


System LED

(gelb/grün) /

(yellow/green)

CAN LED

(rot/grün) /

(red/green)


DSub-Stecker, (X400, 9-polig)


DSub male Connector, (X400, 9 pin)

(x1)

(x16)



(X305, 5-polig /

5 pin

)



(ohne Funktion /

without function

)

Figure 9: CIFX 104-CO-R

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.



Device Drawings

System LED

(gelb/grün) /

(yellow/green)

Modulnetzwerkstatus-LED

(rot/grün) /

Module Network Status LED

(red/green)

DeviceNet-Schnittstelle

COMBICON-Stecker (X360, 5-polig)

DeviceNet Interface

COMBICON male Connector

(X360, 5 pin)

47/171

Steckbrücke Datenbusbreite

(J9, im Bild Brückung für 16 Bit)

Data Bus Width Jumpers

(J9, Jumper Settings for 16 Bit shown)


Mini-B USB Plug

(X5, 5-polig /

5 pin

)



(ohne Funktion /

without function

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)

(x16)

(x1)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

) je mit Standardbrückungen /

Default Jumper Settings each

Figure 10: CIFX 104-DN

Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.







(

J9,


System LED

(gelb/grün) /

(yellow/green)

Modulnetzwerkstatus-LED

(rot/grün) /

Module Network Status LED

(red/green)


COMBICON-Stecker (X360B, 5-polig)


COMBICON male Connector (X360B, 5 pin)

(x1)

(x16)



(X305, 5-polig /

5 pin

)


Rotary Switch Device Addres

s

(ohne Funktion /

without function

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 pin

)



Figure 11: CIFX 104-DN-R

Note:

In

Interrupt Mode


Polling Mode

.




on page 59.


PCI/104


Pin


on page 104.


Mini-B USB



on page 99.




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

System LED

(gelb/grün) /

(yellow/green)




(

J9,


Kabelstecker Feldbus /

Cable Connector Fieldbus

(X4, 10-polig /

10 pin

)



(X3, 12-polig /

12 pin

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 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


Polling Mode

. For further details refer to

Table 23: Starting Address and Interrupt for 16 KByte Dual-Port Memory

on page 59.




(

J9,


System-LED

(gelb/grün) /

(yellow/green)



(X304, 10-polig /

10 pin

)



(X303, 12-polig /

12 pin

)

PC/104 Bus

(X1, 64-polig /

64 pin

)

(X2, 40-polig /

40 pin

)



(J8, 11-polig /

11 pin

)



(J7, 7-polig /

7 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


Polling Mode

. For further details refer to


on page 59.



Device Drawings

5.1.1 Reverse Side CIFX 104-XX (all Basic Cards and Variants)

50/171

PC/104 Bus (Stiftleiste / Plug Connector)

Figure 14: Reverse Side CIFX 104-XX (all Basic Cards and Variants)




5.2.1 Ethernet - AIFX-RE

Only for

CIFX 104-RE\F, CIFX 104-RE-R\F.


RJ45 Socket



(X1, 20-polig /

20 pin

)

Kanal 1 /

Channel 1

(CH 1)

Matrixcode auf Rückseite von X200 /

Matrixcode on Reverse Side of X200

Kanal 0 /

Channel 0

(CH 0)

LED grün /

green

LED gelb /

yellow

Figure 15: Ethernet Assembly Interface (AIFX-RE)*

Note:

*Assembled device supports Auto Crossover Function. Note also: With loaded

EtherCAT Master firmware only the RJ45 channel 0 can be used, channel 1 is deactivated. Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated. For Open Modbus/TCP with V2.3.4.0 and higher both RJ 45 channels can be used.

COM0 COM1

COM0:

Kommunikationsstatus-LED 0

(rot/grün) /

Communication Status LED 0

(red/green)

COM1: Kommunikationsstatus-LED 1

(rot/grün) /

Communication Status LED 1

(red/green)

Figure 16: Front Side and LED Display Ethernet Assembly 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

LED Descriptions




Device Drawings

5.2.2 PROFIBUS - AIFX-DP

Only for

CIFX 104-DP\F, CIFX 104-DP-R\F.


DSub-Buchse (X400, 9-polig)


DSub female Connector (X400, 9 pin)



(X1, 10-polig /

10 pin

)

Matrixcode auf Seite von U401 /

Matrixcode is at Side of U401

Figure 17: PROFIBUS Assembly Interface (AIFX-DP)

52/171

ERR

STA

ERR:

LED Fehlerstatus

(rot) /

LED Error status

(red)

STA: LED Status

(grün) /

LED Status

(green)

Figure 18: Front Side and LED Display PROFIBUS Assembly 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

LED Descriptions




Device Drawings

5.2.3 CANopen - AIFX-CO

Only for

CIFX 104-CO\F, CIFX 104-CO-R\F.



(X1, 10-polig /

10 pin

)


DSub-Stecker (X400, 9-polig)


DSub male Connector (X400, 9 pin)



Figure 19: CANopen Assembly Interface (AIFX-CO)

53/171

ERR RUN

ERR:

LED Fehlerstatus

(rot) /

LED Error status

(red)

RUN: LED Run

(grün) /

LED Run

(green)

Figure 20: Front Side and LED Display Assembly 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

LED Descriptions




Device Drawings

5.2.4 DeviceNet - AIFX-DN

Only for

CIFX 104-DN\F, CIFX 104-DN-R\F.





(X360, 5 pin)



(X1, 10-polig /

10 pin

)



Figure 21: DeviceNet Assembly Interface (AIFX-DN)

54/171

MNS

MNS:

LED Modulnetzwerkstatus

(rot) /

LED Module Network status

(red)

Figure 22: Front Side and LED Display DeviceNet Assembly Interface (AIFX-DN)

The meaning of the

LED MNS

at the reverse side of the AIFX-DN corresponds to the description in chapter

LED Descriptions




Device Drawings

5.2.5 CC-Link - AIFX-CC

Only for

CIFX 104-CC\F.



(X1, 10-polig /

10 pin

)

Figure 23: CC-Link Assembly Interface (AIFX-CC)

CC-Link-Schnittstelle


CC-Link Interface


(X360, 5 pin)

55/171

Matrix_Code

L-RUN

L-ERR

Figure 24: Reverse Side CC-Link Assembly 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 25: Front Side and LED Display CC-Link Assembly Interface (AIFX-CC)

The meaning of the

LEDs L-RUN

and

L-ERR

aat the reverse side of the AIFX-CC corresponds to the description in chapter

LED Descriptions





5.2.6 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)



(X2, 5-polig /

5 pin

)



(ohne Funktion /

not assigned

)



(X1, 12-polig /

12 pin

)

(x16) nicht verwendet

/ not used

Versorgungsspannung-EIN-LED

(grün) /

Power ON LED

(green)

Kommunikationsstatus-LEDs

(rot/grün) /

Communication Status LEDs

(red/green)

System LED

(gelb/grün) /

(yellow/green)

Figure 26: Diagnostic Assembly Interface (AIFX-DIAG)

The meaning of the

LEDs

at the

AIFX-DAIG

corresponds to the descriptions in chapter

LED Descriptions

beginning from page 66. For further information on the

Mini-B USB



on page99.

SYS

COM0

COM1

5

6

7

8

3 2 1 0 F

9 A

B

C

3

5

6

78

9

A

B

C

1 2

F0

Mini-

USB

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

PWR

PWR:

Versorgungsspannung-EIN-LED (grün) /

Power ON LED (green)

-

-

COM0: Kommunikationsstatus-LED 0 (rot/grün) /

Communication Status LED 0 (red/green)

Reverse Side with Matrix Label

COM1: Kommunikationsstatus-LED 1 (rot/grün) /

Communication Status LED 1 (red/green)

Figure 27: Front Side, LED Display and Reverse Side Diagnostic Assembly Interface (AIFX-

DIAG)



Hardware Installation and Uninstalling 57/171

6 Hardware Installation and Uninstalling

To install / uninstall the PC cards cifX

PC/104

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 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 check any notes in the overview in chapter

Getting Started

on page 32.

6.1 Safety Messages on Personal Injury

Obey to the following safety messages on personal injury, when installing, uninstalling or replacing the PC card cifX.


HAZARDOUS VOLTAGE inside of the PC or of the connecting device.

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

First disconnect the power plug of the PC or of the connecting device, before you open the cabinet.


Open the PC cabinet and install or remove the PC card cifX only after disconnecting power.




6.2 Property Damage Messages

Obey to the following property damage messages, when installing, uninstalling or replacing the PC card cifX.

6.2.1 Device Destruction by exceeding allowed Supply Voltage

Adhere for all PC cards cifX described in this manual the instruction hereafter:

Device Destruction!

Use only the permissible supply voltage to operate the PC card cifX.

Operating the PC card cifX with a supply voltage above of the specified range leads to device destruction.

6.2.2 Device Destruction by exceeding allowed Signaling Voltage

Adhere for all PC cards cifX described in this manual the instruction hereafter:

Device Destruction!

All I/O signal pins at the PC card cifX tolerate only the specified signaling voltage!

Operation 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 detailed information on the supply and signaling voltage of the PC cards cifX described in this manual, refer to section


Interface

on page 29.

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.




6.3 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

Device Manager

.

¾ Select .

° 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:

Please 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

14

X

X

E0000 X X X 12 X

…

Default Addresse D0000

Polling

No jumper is set.


3 X

(X = Jumper closed)

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 Management Interface) depending. Please 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

Windows

®

(*) in "Standard PC" mode (ACPI disabled). Therefore the ACPI-

HAL of Windows

®

®

(*) must be replaced with the STANDARD-PC-HAL or

(*) must be installed new. Please contact Microsoft how to change the Windows

®

(*) XP-HAL, because this can make your installation unusable.

(*) Windows

®

XP

4. Reserve 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.4 Installing PC Cards cifX PC/104 (PC/104 Modules)

Note:

For PC cards cifX PC/104 with AIFX assembly interface first install the basic card.

Then connect the AIFX assembly interface to the basic card.

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


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

¾ 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 39.

3. Take safety precautions.


¾

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

¾


4. Open cabinet.

¾ Open the cabinet of the PC or of the connecting 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-DP, AIFX-CO, AIFX-DN, AIFX-

CC assembly 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 Assembly 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-DP, AIFX-CO, AIFX-DN or AIFX-CC assembly 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), PROFIBUS (AIFX-DP), CANopen (AIFX-CO),

DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) assembly interface to the basic card!

6. Connect the Ethernet assembly interface (AIFX-RE) to the basic card.

¾ Connect the on the AIFX-RE with the cable.

¾ Connect the (or X304) on the basic card

CIFX 104-RE\F or CIFX 104-RE-R\F with the cable.

Î Î

Figure 28: Connecting the Ethernet Assembly Interface (AIFX-RE) to the Basic Card CIFX

104-RE\F (Example)

AIFX-CO

Assembly

Interface with

Cable

Connector Fieldbus X1

7. Or connect the PROFIBUS (AIFX-DP), CANopen (AIFX-CO),

DeviceNet (AIFX-DN) or CC-Link (AIFX-CC) assembly interface to the basic card.

¾ Connect the on the assembly interface with the cable.

¾ Connect the (or X304) on the PC card

CIFX 104-FB\F or CIFX 104-FB-R\F Feldbus with the cable.

Example basic card

CIFX 104-CO-R\

F,

Cable Connector Fieldbus X4

Î

Î

Important!

The contacts on the connection cable must face up!

Figure 29: Connecting the CANopen Assembly Interface (AIFX-CO) to the Basic Card 104-

FB-R\F (Example)

¾ Install the AIFX-RE, AIFX-DP, AIFX-CO, AIFX-DN or AIFX-CC assembly interface at the front plate of the PC cabinet.




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:

8. If so, connect the diagnostic assembly interface (AIFX-DIAG):

¾ Connect the

cable connector DIAG X1

on the diagnostic assembly interface (AIFX-DIAG) with the cable.

¾ Connect the (or X303) on the PC card cifX with the cable.

¾ Install the assembly interface AIFX-DIAG at the front plate of the PC cabinet).

Î

Î

Important!

The contacts on the connection cable must face up!

Figure 30: Connecting the Diagnostic Assembly Interface (AIFX-DIAG) to the Basic Card

CIFX 104-FB-R\F (Example)

After this:

9. Close cabinet.

¾

Close the cabinet of the PC or connecting device.

10. Plug the connecting cable to the Master or Slave.

¾ For the PC cards CIFX 104-RE\F or CIFX 104-RE-R\F note:

Note:

The RJ45 socket is only for use in LAN, not for telecommuni-cation circuits. For further information refer to section


on page 95.

¾ Plug the connecting cable from the PC card cifX to the PC card Master or Slave.

11. Connect the PC or the connecting device to the power supply and switch it on.

¾ Connect the PC or the connecting device to the power supply.

¾

Switch on the PC or the connecting device.




6.5 Uninstalling PC Cards cifX PC/104

1. Take safety precautions.


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

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


¾ To prevent damage to the PC and the PC card cifX, make sure, that the


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

¾ Remove the connecting cable between the PC card cifX to be replaced and the PC card Master or Slave.

3. Open cabinet.

¾ Open the cabinet of the PC or of the connecting device.

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 assembly interfaces from the basic cards.

(b) Reinstall the removed PC/104 modules.

Uninstall AIFX Assembly Interfaces

Only for PC cards PC/104 with AIFX Assembly Interface CIFX 104-XX\F and CIFX 104-XX-R\F:

4. Uninstall the Ethernet assembly interface (AIFX-RE), PROFIBUS

(AIFX-DP), CANopen (AIFX-CO), DeviceNet (AIFX-DN) and diagnostic

(AIFX-DIAG):

¾ Remove the AIFX assembly 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

5. Remove PC card cifX

PC/104

.

¾ Loosen the four fastening screws of the PC card cifX.

¾ Remove the PC card cifX.

After this:

6. Close cabinet.

¾ Close the cabinet of the PC or connecting device.



Troubleshooting

7 Troubleshooting

65/171

7.1 Instructions for Problem Solving

In case of any error, follow the instructions for problem solving given here:

General

¾ Check the PC card cifX operating requirements according to the requirements given in the section

Requirements for Operation

on page

31.

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 LED shows the common system status of the device. It can be yellow or green ON or it can blink green/yellow.

•

The LEDs display the status of the Real-Time Ethernet or fieldbus communication. Depending by protocol and state, the LEDs can be ON or flash cyclic or acyclic in green or red (or orange).

If the LED SYS is solid green and the LED COM or COM0 is static green, the PC card cifX is in operational state, the Master is in data exchange with the connected Slaves and the communication is running without fault. The meaning of the LEDs is described in chapter

LED Descriptions


LINK-LED

(for PC cards cifX Real-Time Ethernet)

¾ Check using the LINK LED’s status whether a connection to the

Ethernet is established. Therefore use the description on the LINK LED in the chapter

LED Descriptions


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.



LED Descriptions 66/171

8.1 Overview LEDs Real-Time Ethernet Systems

Note:

The meaning of the communication status LEDs and of the Ethernet

LEDs at the device is defined by the loaded firmware of the protocol.

LED Naming in the Device

Drawing

SYS

(System

Status)

(yellow/green)

COM 0

(Communication

Status

)

COM 1

(Communication

Status

)

SYS SYS SYS SYS SYS SYS SYS SYS SYS

RUN RUN MS RUN BS SF STA S RUN

(green) (green) (red/ green)

(green) (green)

(red)

(green)

(red/ green / orange)

(green)

ERR ERR NS ERR BE BF ERR - ERR

(red) (red)

(red/ green)

(red) (red) (red)

(red) (red)

(green)

(yellow)

(green)

(yellow)

Table 24: Overview LEDs Real-Time Ethernet Systems

LED

System Status

Name

SYS

Meaning

System Status

Communication

Status

BS

BE

SF

BF

S

RUN

ERR

STA

MS

NS

Run

Error

Status

Module Status

Network Status

Bus Status

Bus Error

System Failure

Bus Failure

Status / Error

Table 25: LED Names

LED

Ethernt

Name

LINK, L

ACT, A

Meaning

Link

Activity

L/A Link/Activity

L/A IN Link/Activity Input

L/A OUT Link/Activity Output

RX/TX Receive/Transmit



LED Descriptions

8.2 Overview LEDs Fieldbus Systems

LED

67/171

System Status

SYS SYS SYS SYS

(gelb/green)

Communication

Status

COM CAN MNS

L RUN

(green)

(red/green) (red/green) (red/green)

L ERR

(red)

Table 26: Overview LEDs by Fieldbus System for 1 Channel Devices

LED

System Status

Name

SYS

Meaning

System Status

Communication Status

MNS

L RUN / L ERR

Table 27: LED Names

Module Network Status

Status Run / Status Error




LED

SYS

LED State

On

Off

Blinking

Color

The System Status LED

SYS

can assume the states described below.

State

Duo LED yellow/green

(green)

On

Blinking

(green/yellow)

Meaning

Operating System running

Second stage bootloader is waiting for firmware.

(yellow)

On Bootloader netX (= romloader) is waiting for second stage bootloader.

(off)

Off Power supply for the device is missing or hardware defect.

Table 28: System Status LED States

Definition

The indicator is constantly on.

The indicator is constantly off.

The indicator turns on and off cyclically.

Table 29: System Status LED State Definitions

LED

PWR

LED state

On

Off

Color

LED green

The power On LED

PWR

can assume the states described below.

State Meaning

(green)

On Power supply for the device on.

(off)

Off Power supply for the device is missing.

Table 30: Power On LED States

Definition



Table 31: Power On LED state definitions




LED

RUN

General name:

COM 0

ERR

General name:

COM 1

LINK

Ch0

ACT

Ch0

For the EtherCAT Master protocol, the communication LEDs

RUN

and

ERR

as well as the Ethernet LEDs

LINK

and

ACT

can assume the states described below. This description is valid from stack version V3.0.

State Meaning Color

Duo LED red/green

(off)

Off

(green)

Blinking

(2,5 Hz)

(green)

Flickering

(10 Hz)

INIT

: The device is in state INIT.

PRE-OPERATIONAL

: The device is in PRE-OPERATIONAL state.

BOOT

: Device is in Boot mode.

(green)

Single flash

SAFE-OPERATIONAL

: The device is in SAFE-OPERATIONAL state.

OPERATIONAL

: The device is in OPERATIONAL state.

(green)

On

Duo-LED red/green

(off)

Off

(red)

On

Master has no errors.

Master has detected a communication error. The error is indicated in the DPM.

LED green

(green)

On

(off)

LED yellow

Off

(yellow)

(off)

Flickering

(load dependant)

Off

The device is linked to the Ethernet.

The device has no link to the Ethernet.

The device sends/receives Ethernet frames.

The device does not send/receive Ethernet frames.

Table 32: LED states for the EtherCAT Master protocol

LED State

On

Off

Blinking

(2,5 Hz)

Flickering

(10 Hz)

Single flash

Flickering (load dependant)

Definition



The indicator turns on and off with a frequency of 2,5 Hz:

“on” for 200 ms, followed by “off” for 200 ms.

The indicator turns on and off with a frequency of 10 Hz: “on” for 50 ms, followed by “off” for 50 ms.

The indicator shows one short flash (200 ms) followed by a long “off“ phase (1,000 ms).

The indicator turns on and off with a frequency of approximately 10 Hz to indicate high 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 33: LED state definitions for the EtherCAT Master protocol




LED

RUN

General name:

COM 0

For the EtherCAT Slave protocol, the communication LEDs

RUN

and

ERR

as well as the Ethernet-LED

L/A IN

or

L/A OUT

can assume the states described below. This description is valid from stack version V2.5 (V2).



(off)

Off

(green)

Blinking

(2,5 Hz)

INIT

: The device is in state INIT.

PRE-OPERATIONAL

: The device is in PRE-OPERATIONAL state.

ERR

General name:

COM 1

L/A IN

or

L/A OUT

(green)

Single flash

(green)

On


SAFE-OPERATIONAL

OPERATIONAL

: The device is in SAFE-OPERATIONAL state.

: The device is in OPERATIONAL state.

(off)

Off

No error:

The EtherCAT communication of the device is in working condition.

(red)

(red)

(red)

Blinking

(2,5 Hz)

Invalid configuration:

General Configuration Error

Possible reason: State change commanded by master is impossible due to register or object settings.

Single Flash

Local error:

Slave device application has changed the EtherCAT state autonomously.

Double

Flash

Possible reason 1: A host watchdog timeout has occurred.

Possible reason 2: Synchronization Error, device enters Safe-

Operational automatically.

Application watchdog timeout:

An application watchdog timeout has occurred.

Possible reason: Sync Manager Watchdog timeout.

LED green

(green)

(green)

On

Flickering

(load dependant)

Off

Link:

The device is linked to the Ethernet, but does not send/receive

Ethernet frames.

Activity:

The device is linked to the Ethernet and sends/receives

Ethernet frames.


(off)

LED yellow

(off)

Off This LED is not used.

Table 34: LED states for the EtherCAT Slave protocol

LED State

On

Off

Blinking

(2,5 Hz)

Single flash

Double flash


Beschreibung






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




8.7 EtherNet/IP Scanner (Master)

LED

MS

(Module status)

General name:

COM 0

For the EtherNet/IP Scanner protocol, the communication LEDs

MS

and

NS


LINK

and

ACT




On

(green)

(green)

Flashing

(1 Hz)

(red/green)

(red)

(red)

Flashing

(1 Hz)

Flashing

(1 Hz)

On

Device operational

: The device is operating correctly.

Standby

: The device has not been configured.

Self-test

: The device is performing its power up testing.

Minor fault

: The device has detected a recoverable minor fault. E. g. an incorrect or inconsistent configuration can be considered as a minor fault.

Major fault

: The device has detected a non-recoverable major fault.

NS

(Networkstatus)

General name::

COM 1

LINK

Ch0 & Ch1

ACT

Ch0 & Ch1

(Off)

Off


On

(green)

(green)

Flashing

(1 Hz)

(red/green)

(red)

Flashing

(1 Hz)

Flashing

(1 Hz)

No power

Connected

: The device has at least one established connection (even to the

Message Router).

No connections

: The device has no established connections, but has obtained an IP address.

Self-test

: The power supply to the device is missing.


Connection timeout

: One or more of the connections in which this device is the target have timed out. This status will be finished only if all timed out connections are reestablished or if the device is reset.

Duplicate IP

: The device has detected that its IP address is already in use.

(red)

On

(Off)

Off

Not powered, no IP address

: The device does not have an IP address (or is powered off).

LED green

On

(green)

(Off)

LED yellow

Off

(yellow)

(Off)

Flickering

(load dependant)

Off





Table 36: LED states for the EtherNet/IP Scanner protocol

LED state

On

Definition


Off The indicator is constantly off.

Flashing (1 Hz)

The indicator turns on and off with a frequency of 1 Hz:


Flickering

(load dependant)


Table 37: LED state definitions for the EtherNet/IP Scanner protocol




8.8 EtherNet/IP Adapter (Slave)

LED

MS

(Module status)

General name:

COM 0

For the EtherNet/IP Adapter protocol, the communication LEDs

MS

and

NS


LINK

and

ACT

can assume the states described below. This description is valid from stack version V2.7 (V2) or from V3.0.



(green)

On

(green)

(red/green)

(red)

Flashing

(1 Hz)

Flashing

(1 Hz)

Flashing

(1 Hz)

(red)

On

Device operational

: The device is operating correctly.

Standby

: The device has not been configured.

Self-test


Minor fault

: The device has detected a recoverable minor fault. E. g. an incorrect or inconsistent configuration can be considered as a minor fault.

Major fault

: The device has detected a non-recoverable major fault.

NS

(Networkstatus)

General name::

COM 1

LINK

Ch0 & Ch1

ACT

Ch0 & Ch1

(Off)

Off


(green)

On

No power

: The power supply to the device is missing.

(green)

(red/green)

Flashing

(1 Hz)

Flashing

(1 Hz)

Flashing

(1 Hz)

Connected

: The device has at least one established connection (even to the Message Router).

No connections

Self-test

: The device has no established connections, but has obtained an IP address.


(red)

Connection timeout

: One or more of the connections in which this device is the target have timed out. This status will be finished only if all timed out connections are reestablished or if the device is reset.

Duplicate IP

: The device has detected that its IP address is already in use.

(red)

On

(Off)

Off

Not powered, no IP address

: The device does not have an IP address (or is powered off).

LED green

(green)

On

(Off)

LED yellow

Off

(yellow)

(Off)

Flickering

(load dependant)

Off





Table 38: LED states for the EtherNet/IP Adapter protocol

LED state

On

Definition



Flashing (1 Hz)



Flickering

(load dependant)


Table 39: LED state definitions for the EtherNet/IP Adapter protocol




LED

RUN

General name:

COM 0

ERR

General name:

COM 1

LINK

Ch0 & Ch1

ACT

Ch0 & Ch1

For the OpenModbusTCP protocol, the communication LEDs

RUN

and

ERR


LINK

and

ACT




On

(green)

(green)

Flashing

(1 Hz)

(green)

Flashing

(5 Hz)

Connected

: OMB task has communication. At least one TCP connection is established.

Ready, not yet configured:

OMB task is ready and not yet configured.

Waiting for Communication:

OMB task is configured.

(off)

Off


(off)

Off

(red)

Flashing

(2 Hz,

25% on )

System error

(red)

LED green

On Communication error active


(green)

On

(off)

LED yellow

Off The device has no link to the Ethernet.

(yellow)

(off)


Off

Not Ready

: OMB task is not ready.

No communication error



Table 40: LED states for the OpenModbusTCP protocol

LED state

On

Off

Definition



Flashing (1 Hz) The indicator turns on and off with a frequency of 1 Hz:


Flashing (2 Hz,

25% on

)







Table 41: LED state definitions for the OpenModbusTCP protocol




8.10 POWERLINK Controlled Node/Slave

LED

BS

(Bus Status)

General name:

COM 0

For the POWERLINK Controlled Node protocol, the communication LEDs

BS

(Bus Status) and

BE

(Bus Error) as well as the Ethernet LED

L/A




(green)

On

(green)

Triple Flash

(green)

Double flash

Slave is in

‘Operational’

state

Slave is in

‚ReadyToOperate’

state

Slave is in

‚Pre-Operational 2’

state

(green)

Single flash Slave is in

‚Pre-Operational 1’

state

(red/green)

(red/green)

Flickering

(10 Hz)

Blinking

(2,5 Hz)

Slave is in

‚Basic Ethernet’

state

Slave is in

‚Stopped’

state

BE

(Bus Error)

General name:

COM 1

L/A

Ch0 & Ch1

Ch0 & Ch1

(off)


(off)

Off

(red)

On

Slave has no error

Slave has detected an error

LED green

(green)

On

(green)

(off)

LED yellow


Off

(off)

Off

Link:

The device is linked to the Ethernet, but does not send/receive Ethernet frames.

Activity:


Ethernet frames.


This LED is not used.

Table 42: LED states for the POWERLINK Controlled Node protocol

LED state

On

Off

Triple Flash

Double flash

Single flash

Flickering

(10 Hz)

Blinking

(2,5 Hz)


Definition



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



The indicator turns on and off with a frequency of approximately 10 Hz: on for approximately 50 ms, followed by off for 50 ms. Red and green LEDs shall be on alternately.

The indicator turns on and off with a frequency of approximately 2.5 Hz: on for approximately 200 ms, followed by off for 200 ms. Red and green LEDs shall be on alternately.


Table 43: LED state definitions for the POWERLINK Controlled Node protocol




8.11 PROFINET IO-Controller

LED

SF

(System

Failure)

General name:

COM 0

BF

(Bus

Failure)

General name:

COM 1

LINK

Ch0 & Ch1

RX/TX

Ch0 & Ch1

For the PROFINET IO-Controller protocol, the communication LEDs

SF

(system failure) and

BF

(bus failure) as well as the Ethernet LEDs

LINK

and

RX/TX




(off)

Off

(red)

(red)

Flashing

(1 Hz, 3 s)

Flashing

(2 Hz)

(red)

On

(

together with SF „red

ON

)


(off)

Off

(red)

(red)

(red)

Flashing

(2 Hz)

On

(


ON")

On

(


OFF")

LED green

No error

DCP signal service

is initiated via the bus.

System error:

Invalid configuration, Watchdog error or internal error

System error:

Invalid configuration, Watchdog error or internal error

No error

Configuration fault:

Not all configured IO-Devices are connected.

No valid Master license

No Connection:

No Link.

(green)

On

(off)

LED yellow

Off

(gelb)

(off)

Flickering

(load dependant)

Off





Table 44: LED states for the PROFINET IO-Controller protocol

LED state

On

Off

Flashing

(1 Hz, 3 s)

Definition



The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed by “off” for 500 ms.



Flickering

(load dependant)


Table 45: LED state definitions for the PROFINET IO-Controller protocol




8.12 PROFINET IO-Device

LED

SF

(System

Failure)

General name:

COM 0

Color

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

State


Meaning

(off)

(red)

Flashing

(

1 Hz, 3 s)

On

DCP signal service is initiated via the bus.

(red)

Watchdog timeout; channel, generic or extended diagnosis present; system error

BF

(Bus

Failure)

General name:

COM 1


(off)

(red)

(red)

Flashing

(2 Hz)

On

No data exchange

No configuration; or low speed physical link; or no physical link

LINK

Ch0 & Ch1

RX/TX

Ch0 & Ch1

LED green

(green)

On

(off)

LED yellow

Off

(gelb)

(off)

Flickering

(load dependant)

Off





Table 46: LED states for the PROFINET IO-Device protocol

LED state

On

Off

Definition



Flashing

(1 Hz, 3 s)

The indicator turns on and off for 3 seconds with a frequency of 1 Hz: “on” for 500 ms, followed by “off” for 500 ms.



Flickering

(load dependant)


Table 47: LED state definitions for the PROFINET IO-Device protocol




8.13 sercos Master

LED

STA

General name:

COM 0

ERR

General name:

COM 1

For the sercos Master protocol, the communication LEDs

STA

and

ERR

as well as the Ethernet LED

L/A




(green)

On

(green)

Triple Flash

(green)

Double flash

(green)

Single flash

(green)

Blinking (2,5 Hz)

(green)

Flickering (10 Hz)

CP4: Communication phase 4





Master is not configured and is in NRT.

After a status change this isn't indicated again

NRT:

Non Real-Time Mode

(off)

Off


(red)

Single flash

(red)

Double flash

(red)

Triple Flash

(red)

Quadruple Flash

(red)

Blinking (2,5 Hz)

(red)

Single Flickering

(red)

Double Flickering

(red)

Flickering (10 Hz)

Bus Sync error threshold

Internal Stop of the bus cycle

DPM watchdog has expired.

No Master license present in the device.

Error in the configuration database.

Channel Init was executed at the Master.

Slave is missing.

Boot-up was stopped due to an error.

L/A

Ch0 & Ch1

Ch0 & Ch1

(off)

LED green

(green)

On

(green)

(off)

LED yellow

Flickering

(load dependant)

Off

(off)

Off

Link:


Activity:

The device is linked to the Ethernet and sends/receives Ethernet frames.



Table 48: LED states for the sercos Master protocol




LED state

On

Off

Single flash

Double flash

Triple Flash

Definition





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 Flash The indicator shows a sequence of four 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)

Single Flickering

The indicator turns on and off with a frequency of 2,5 Hz: “on” for 200 ms, followed by “off” for

200 ms.

The indicator is switched on and off once: 'on' for 50 ms, followed by 'off' for 500 ms.

Double

Flickering

Flickering

(10 Hz)

Flickering

(load dependant)

The indicator is switched on and off and on once: 'on' / 'off' / 'on' each for approximately 50 ms, followed by 'off' for 500 ms.

The indicator turns on and off with a frequency of 10 Hz: 'on' for 50 ms, followed by 'off' for 50 ms.

The indicator turns on and off with a frequency of approximately 10 Hz to indicate high 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 49: LED state definitions for the sercos Master protocol




8.14 sercos Slave

LED

S

General name:

COM 0

For the sercos Slave protocol, the communication LED

S

as well as the

Ethernet LED

L/A




(orange = red/green simultaneously)

(green)

On

CP4: Communication phase 4:

Normal operation, no error

(green)

Blinking (2 Hz)

Loopback:

The network state has changed from „fast-forward“ to „loopback“.


(green/orange)

(orange)

Flashing

(3 x green/3s)

(2 x green/3s)

(1 x green/3s)

On




General name:

COM 1

L/A

Ch0 & Ch1

(orange/green)

Blinking (2 Hz)

HP0:

Hot-plug mode (not yet implemented)

(1 x orange/3s)

HP1:


(2 x orange/3s)

HP2:


(orange)

(green/red)

Flashing (2 Hz)

Identification:

Corresponds to C-DEV.Bit 15 in the Slave’s

Device Control indicating remote address allocation or configuration errors between Master and Slaves (for details refer to sercos Slave V3 Protocol API Manual).

Flashing (2 Hz, min. 2s)

MST losses ≥ (S-0-1003/2):

Depends on IDN S-0-1003 (for details refer to sercos Slave Protocol API manual).

Corresponds to S-DEV.Bit 15 in the Device Status indicating a communication warning (Master SYNC telegrams have not been received).

Flashing (2 Hz)

Application error (C1D):

See GDP & FSP Status codes class error, (see sercos Slave V3 Protocol API Manual).

(red/orange)

(red)

(red)

Flashing (2 Hz)

Watchdog error:

Application is not running (not yet implemented)

On

Communication Error (C1D):

Error detected according to sercos third generation Class 1 Diagnosis, see SCP Status codes class error (see sercos Slave V3 Protocol API Manual).

(off)

Off


(off)

Off

NRT-Mode:

(Non Real-Time Mode) No sercos Communication


LED green

(green)

(green)

On

Link:


Activity:


Ethernet frames.


Ch0 & Ch1

(off)

LED yellow


Off


(off)

Table 50: LED state definitions for the sercos Slave protocol




LED state

On

Definition




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)

(2 x green/3s)

Flashing green for 250 ms, then orange on for 2 second and 750 ms.

Flashing green / orange / green, each for 250 ms, then orange on for 2 seconds and 250 ms.

(3 x green/3s)

(1 x orange/3s)

(2 x orange/3s)

Flashing green / orange / green / orange / green, each for 250 ms, then orange on for 1 second and 750 ms.

Flashing orange for 250 ms, then green on for 2 second an 750 ms.

Flashing orange / green / orange, each for 250 ms, then green on for 2 seconds and 250 ms.


The indicator turns on and off with a frequency of approximately 10 Hz to indicate high 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 51: LED state definitions for the sercos Slave protocol




8.15 VARAN Client (Slave)

LED

RUN

General name:

COM 0

For the VARAN Client protocol, the communication LEDs

RUN

and

ERR


LINK

and

ACT




On

(green)

(green)

Configured and communication is active.

Blinking (5 Hz) Configured and communication is inactive.

ERR

General name:

COM 1

LINK

Ch0 & Ch1

ACT

Ch0 & Ch1

(off)


(off)

Off Configured.

(red)

Blinking (5 Hz) Not configured.

(red)

LED green

(green)

On

(off)

(off)

Off

LED yellow

(yellow)

Flickering

(load dependant)

Off





Table 52: LED-Zustände für das VARAN-Client-Protokoll

LED state

On

Off

Blinking (5 Hz)

Flickering

(load dependant)

Definition






Table 53: Definitionen der LED-Zustände für das VARAN-Client-Protokoll




8.16 PROFIBUS DP Master

8.16.1 1 Communication Status LED

For the PROFIBUS DP Master protocol, the communication status LED

COM


State Meaning LED Color cifX with 1 Communication Status LED

(current Hardware Revision)

COM Duo LED red/green

(green)

On Communication to all Slaves is established.

(green)

(green)

Flashing (5 Hz) PROFIBUS is configured, but bus communication is not yet released from the application.

Flashing acyclic No configuration or faulty configuration

(red)

Flashing (5 Hz) Communication to at least one Slave is disconnected.

(red)

(off)

On

Off

Communication to all Slaves is disconnected or another serious error has occurred.

Redundant Mode: The active Master was not found.

Device is not switched on or network power is missing.

Table 54: LED states for the PROFIBUS DP Master protocol – 1 Communication Status LED

(current Hardware Revision)

LED State Definition

On

Off




"on" for 100 ms, followed by "off" for 100 ms.

Flashing acyclic

The indicator turns on and off in irregular intervals.

Table 55: LED state definitions for the PROFIBUS DP Master protocol




8.16.2 2 Communication Status LEDs

For the PROFIBUS DP Master protocol, the communication status LEDs

STA

and

ERR


State Meaning LED Color 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)

(green)

Flashing (5 Hz)

PROFIBUS is configured, but bus communication is not yet released from the application.

Flashing acyclic No configuration or faulty configuration

(off)

Off

LED red is off:


LED red is flashing or “on”:

Refer to description LED red.

ERR LED red

(off)

Off Refer to description for LED green.

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

Table 56: LED states for the PROFIBUS DP Master protocol – 2 Communication Status

LEDs (AIFX-DP connected or prior Hardware Revision)

LED State

On

Definition




"on" for 100 ms, followed by "off" for 100 ms.

Flashing acyclic

The indicator turns on and off in irregular intervals.

Table 57: LED state definitions for the PROFIBUS DP Master protocol



LED Descriptions

8.17 PROFIBUS DP Slave

84/171


For the PROFIBUS DP Slave protocol, the communication status LED

COM





(green)

On RUN, cyclic communication

(green)

Flashing, cyclic (2 Hz)

Master is in CLEAR state.

(red)

(red)

(red)

Flashing, acyclic (1 Hz)


On

Device is not configured.

STOP, no communication, connection error

Wrong configuration at PROFIBUS DP Slave.

(off)

Off Device is not switched on or network power is missing.

Table 58: LED states for the PROFIBUS DP Slave protocol – 1 Communication Status LED


LED State

On

Off



Definition



The indicator turns on and off in irregular intervals, with a frequency of 1 Hz:




Table 59: LED state definitions for the PROFIBUS DP Slave protocol





For the PROFIBUS DP Slave protocol, the communication status LEDs

STA

and

ERR


State Meaning LED Color cifX with 2 Communication Status LEDs

(AIFX-DP is connected or for prior Hardware Revisions)

STA

LED green

(green)

On RUN, cyclic communication

(green)

(off)


Off

Master is in CLEAR state.

LED red is off:


LED red is flashing or on:


ERR LED red

(off)

Off Refer to description for LED green.

(red)

Device is not configured.

(red)

(red)



On

STOP, no communication, connection error

Wrong configuration at PROFIBUS DP Slave.

Table 60: LED states for the PROFIBUS DP Slave protocol – 2 Communication Status LEDs

(AIFX-DP connected or prior Hardware Revision)

LED State

On

Off



Definition



The indicator turns on and off in irregular intervals, with a frequency of 1 Hz:




Table 61: LED state definitions for the PROFIBUS DP Slave protocol




8.18 PROFIBUS MPI Device


For the PROFIBUS MPI protocol, the communication status LED

COM




(green)

On

(green)

Blinking (5 Hz)

Status:

The device currently holds the PROFIBUS token and is able to transfer telegrams of data.

Status:

The device is configured to be a part of the PROFIBUS ring, but it must share the PROFIBUS token with other PROFIBUS-

Master devices present on the PROFIBUS ring.

(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 62: LED states for the PROFIBUS MPI protocol – 1 Communication Status LED

LED State

On

Off

Blinking (5 Hz)

Blinking (0.5 Hz)

Definition



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.

The indicator turns on and off with a frequency of appr. 0.5 Hz:


Table 63: LED state definitions for the PROFIBUS MPI protocol





LED Color

For the PROFIBUS MPI protocol, the communication status LEDs

STA

and

ERR


State Meaning cifX with 2 Communication Status LEDs

(AIFX-DP is connected)

STA LED green

(green)

(green)

(green)

On

Blinking (5 Hz)

Status:

The device currently holds the PROFIBUS token and is able to transfer telegrams of data.

Status:

The device is configured to be a part of the PROFIBUS ring, but it must share the PROFIBUS token with other PROFIBUS-

Master devices present on the PROFIBUS ring.

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 64: LED states for the PROFIBUS MPI protocol – 2 Communication Status LEDs

(AIFX-DP connected)

LED State

On

Off

Blinking (5 Hz)

Blinking (0.5 Hz)

Definition



The indicator turns on and off with a frequency of appr. 5 Hz:


The indicator turns on and off with a frequency of appr. 0.5 Hz:


Table 65: LED state definitions for the PROFIBUS MPI protocol




8.19 CANopen Master


LED Color

For the CANopen Master protocol, the communication status LED

CAN


State Meaning cifX with 1 Communication Status LED


CAN Duo-LED red/green

(green)

On

OPERATIONAL:

The device is in the OPERATIONAL state.

(green)

(green)

Blinking (2,5 Hz)

Single flash

PREOPERATIONAL:

The device is in the PREOPERATIONAL state.

STOPPED

: The device is in STOPPED state.

(red)

(red)

(red)

(off)

Single flash

Double flash

Warning Limit reached

: At least one of the error counters of the

CAN controller has reached or exceeded the warning level (too many error frames).

Error Control Event

: A guard event (NMT Slave or NMT Master) or a heartbeat event (Heartbeat consumer) has occurred.

On

Off

Bus Off

: The CAN controller is in bus OFF state.

RESET:

The device is executing a reset or the device has no configuration.

Table 66: LED states for the CANopen Master protocol – 1 Communication Status LED


LED state

On

Off

Blinking (2,5

Hz)

Single flash

Double flash

Definition






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





LED Color

For the CANopen Master protocol, the communication status LEDs

RUN

and

ERR



(AIFX-CO is connected or for prior Hardware Revisions)

RUN LED green

(green)

On

OPERATIONAL:


(green)

Blinking (2,5 Hz)

PREOPERATIONAL:


STOPPED

: The device is in STOPPED state.

(green)

Single flash

(off)

Off

LED red is off:

RESET:


LED red is flashing or “on”:


ERR LED red

Off Refer to description LED green.

(off)

(red)

(red)

Single flash

Double flash


: At least one of the error counters of the

CAN controller has reached or exceeded the warning level (too many error frames).



Bus Off


(red)

On

Table 68: LED states for the CANopen Master protocol – – 2 Communication Status LEDs

(AIFX-CO connected or prior Hardware Revision)

LED state

On

Off

Blinking (2,5

Hz)

Single flash

Double flash

Definition






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 Master protocol




8.20 CANopen Slave


LED Color

For the CANopen Slave protocol, the communication status LED

CAN


State Meaning cifX with 1 Communication Status LED


CAN Duo LED red/green

(green)

On

OPERATIONAL:


(green)

Blinking

(2.5 Hz)

Single flash

PREOPERATIONAL:


(green)

STOPPED:

The device is in STOPPED state.

(red/green)

(red)

(red)

(red)

Flickering

(10 Hz)

Single flash

Double flash

On

Auto Baud Rate Detection active:

The Device is in the auto baud rate detection mode.


: At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).



Bus Off


(off)

Off

RESET:


Table 70: States of the CAN LED for the CANopen Slave protocol – 1 Communication

Status LED (current Hardware Revision)

LED State

On

Off

Flickering

(10 Hz)

Blinking

(2.5 Hz)

Single Flash

Double Flash

Definition





200 ms.

The indicator shows one short flash (200 ms) followed by a long “off” phase (1,000 ms).

The indicator shows a sequence of two short flashes (each 200 ms), separated by a short off phase (200 ms). The sequence is finished by a long “off” phase (1,000 ms).

Table 71: LED state definitions for the CANopen Slave protocol





LED Color

For the CANopen Slave protocol, the communication status LEDs

RUN

and

ERR



(AIFX-CO is connected or for prior Hardware Revisions)

RUN LED green

On

OPERATIONAL:


(green)

(green)

Blinking

(2.5 Hz)

Single flash

PREOPERATIONAL:


(green)

STOPPED:

The device is in STOPPED state.

(green)

Flickering

(10 Hz, alternatively with ERR LED)

Off



(off)

LED red is off:

RESET:


LED red is flickering, flashes or “on”:


ERR LED red

Off Refer to description LED green.

(off)

(red)

(red)

Flickering

(10 Hz, alternatively with RUN LED)

Single flash



(red)

Double flash


: At least one of the error counters of the CAN controller has reached or exceeded the warning level (too many error frames).



Bus Off


(red)

On

Table 72: States of the CAN LED for the CANopen Slave protocol – 2 Communication

Status LEDs (AIFX-CO connected or prior Hardware Revision)

LED State

On

Off

Flickering

(10 Hz)

Blinking

(2.5 Hz)

Single Flash

Double Flash

Definition





200 ms.

The indicator shows one short flash (200 ms) followed by a long “off” phase (1,000 ms).

The indicator shows a sequence of two short flashes (each 200 ms), separated by a short off phase (200 ms). The sequence is finished by a long “off” phase (1,000 ms).

Table 73: LED state definitions for the CANopen Slave protocol




8.21 DeviceNet Master

LED

MNS

For the DeviceNet Master protocol, the communication status LED

MNS


Color State


Meaning

(green)

(green)

(green/red/

Off)

On

Device operational AND on-line, connected

Device is online and has established all connections with all Slaves.

Flashing (1 Hz)

Device operational AND on-line

Device is online and has established no connection in the established state.

Flashing (2Hz)

Green/Red/Off

- Configuration missing, incomplete or incorrect.

Self test after power on

(red)

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

On

No network power present.

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 Master protocol

LED state

On

Definition


Off

Flashing (2 Hz) green/red/off


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.

The indicator turns on green on for 250 ms, then red on for 250 ms, then off.

Table 75: LED state definitions for the DeviceNet Master protocol




8.22 DeviceNet Slave

LED

MNS

Color

For the DeviceNet Slave protocol, the communication status LED

MNS


State


Meaning

(green)

(green)

On

Device operational AND on-line, connected

Device is online and has established all connections with all Slaves.

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.

(green/red/

Off)

Flashing (2Hz)

Green/Red/Off

Self test after power on

(red)

(red)

(off)

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.

On

Off

Connection timeout.

No network power present.

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

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

LED state

On

Definition



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) green/red/off

The indicator turns on green on for 250 ms, then red on for 250 ms, then off.

Table 77: LED state definitions for the DeviceNet Slave protocol




8.23 CC-Link Slave

8.24 Slave

LED

L RUN

Color

LED green

For the CC-Link Slave protocol, the communication status LEDs

L-RUN

and

L-ERR


State Meaning

(green)

On

After participating in the network, the device receives both refresh and 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)

(red)

(off)

Blinking

On

Off

The switch setting has been changed from the setting at the reset cancellation (blinks for 0.4 sec.).

1. CRC error

2. Address parameter error (0,65 or greater is set including the number of occupied stations)

3. Baud rate switch setting error during cancellation of reset (5 or greater)

1. Normal communication

2. Resetting hardware

Table 78: LED states for the CC-Link Slave protocol

LED state

On

Off

Blinking

Definition



The indicator turns on and off cyclically.

Table 79: LED state definitions for the CC-Link Slave protocol



Device Connections and Switches

9 Device Connections and Switches

95/171

For the Ethernet interface use RJ45 plugs and twisted pair cable of category 5 (CAT5) or higher, which consists of 4 twisted cores and has a maximum transmission rate of 100 MBit/s (CAT5).

9.1.1 Ethernet Pin Assignment at the RJ45 Socket

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.

Ethernet

Channel 0

Ethernet

Channel 1

Figure 31: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX

Pin Signal

1 TX+

Meaning

Transmit Data +

2 TX– Transmit Data –

3 RX+ Receive +

6 RX– Receive –

2

2

* Bob Smith Termination

Table 80: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX

Further Notes:

(1) The RJ45 socket is only for use in LAN, not for telecommunication circuits.

(2) With loaded EtherCAT Master firmware only the RJ45 channel 0 can be used, channel

1 is deactivated. Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated. For the Open Modbus/TCP firmware with V2.3.4.0 and higher both RJ45 RJ45channels can be used.




9.1.2 Ethernet Connection Data

Medium

Length of cable

Transmission rate

2 x 2 Twisted-Pair cupric cable, CAT5 (100 MBit/s)

Typ. 100 m

10 MBit/s/100 MBit/s

Table 81: Ethernet Connection Data

96/171

9.1.3 Use of Hubs and Switches

For the corresponding communication systems, the use of hubs and/or switches is either forbidden or allowed. The following table shows the acceptable use of hubs and switches by each communication system:

Communication System

EtherCAT

EtherNet/IP

Open Modbus/TCP

POWELINK

PROFINET IO sercos

VARAN*

Hub

forbidden allowed

Switch

only allowed between EtherCAT Master and first EtherCAT Slave

(100 MBit/s, Full Duplex) allowed

(10 MBit/s/100 MBit/s, Full or Half Duplex, Auto-Negotiation) allowed allowed

(10 MBit/s/100 MBit/s, Full or Half Duplex, Auto-Negotiation) allowed forbidden forbidden Only allowed if the switch supports ‚Priority Tagging’ and LLDP

(100 MBit/s, Full Duplex) forbidden forbidden forbidden forbidden

Table 82: Use of Hubs and Switches

*Instead of hubs and switches VARAN uses splitter. [3]




Isolated RS-485 interface:

97/171

Figure 32: PROFIBUS Interface (DSub female connector, 9 pin), X400

Connection with

DSub female connector

Signal Meaning

connection B plug

6 VP Positive supply voltage

Receive/Send Data-N respectively connection A plug

Table 83: PROFIBUS Interface, X400

Isolated ISO 11898 interface:

Figure 33: CANopen Interface (DSub male connector, 9 pin), X400

Connection with

DSub male connector

Signal Description

2 CAN_L Line

7

1, 4, 5, 6, 8, 9

CAN_H

Table 84: CANopen Interface, X400

CAN High Bus Line

Do not connect!




Isolated ISO 11898 interface:

98/171

Figure 34: DeviceNet Interface (CombiCon male Connector, 5 pin), X360

Color Description Connection with

CombiCon male connector

Signal

1 V- Black Reference potential DeviceNet supply voltage

3 Drain Shield

+24 V DeviceNet supply voltage 5 V+ Red

Table 85: DeviceNet Interface, X360

Isolated RS-485 interface:

Figure 35: CC-Link Interface (CombiCon male Connector, 5 pin)

Connection with

Screw terminal

Connector

Signal Meaning

Table 86: CC-Link Interface



Device Connections and Switches 99/171

9.6 Mini-B USB Connector (5 Pin)

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

assembly interface is connected, the

Mini-B USB

connector on the AIFX-DIAG can be used.

Figure 36: Mini-B USB Connector (5 Pin)

Pin Name Description

1 USB_EXT USB Bus Power (+5 V dc, supplied externally)

2 D-

3 D+

4 ID

5 GND Ground

Table 87: Pin Assignment Mini-B USB Connector

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.




9.8.1 Pin Assignment for Cable Connector Ethernet

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

3

4

STA0_green

(

RE LED COM 0

)

STA0_red

(

RE LED COM 0

)

5 XM0_TX

6 STA1_green

(

RE LED COM 1

)

7 CH0_LINKn

8 CH0_ACTIVITY

9 AIFINIT

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_LINKn

20 CH1_ACTIVITY

Table 88: Pin Assignment for Cable Connector Ethernet X4 or X304

Cable Connector Ethernet:

Figure 37: 1x20 Pins for CIFX 104-RE\F, CIFX 104-RE-R\F




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

4 I2C_DATA/ PIO 5

5 XMAC2_TX

6 XMAC2_RX

7 XMAC2_IO0

8 XMAC2_IO1

9 /RSTOUT

Table 89: Pin Assignment for Cable connector Fieldbus X3, X304 or X4

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

2

GND GND

+3V3 +3V3

3

4

STA2 (

FB LED COM 0

) STA2

STA3 (

FB LED COM 1

) STA3

5

6

7

USB_POS USB_POS

USB_NEG USB_NEG

RDYn RDYn

8

9

RUNn RUNn

STA0_green (

not used

) STA0_green )

10

11

STA0_red (

not used

) STA0_red )

STA1_green (

not used

) STA1_green )

12

STA1_red (

not used

) STA1_red )

Table 90: Pin Assignment for Cable connector DIAG X3 or X303




9.9 SYNC Connector (Pin-Assignment, Hardware/Firmware)

9.9.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 91: Pin Assignment for SYNC Connector, X51

9.9.2 Items on Hardware

Item

SYNC Signal

Connector

Max. Cable

Length

Explanation

3.3 V (LVTTL), maximum load 6 mA

SYNC connector, X51 (for the PC cards cifX, as indicated under section

Pin Assignment SYNC

Connector, X51

on page 102.)

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)

Recommendation: Max. 50 mm

Note

: Take EMC into consideration for the cable laying

Table 92: SYNC Connector: SYNC Signal, Connector, Max. Cable Length

9.9.3 Items on Firmware

Protocol

EtherCAT Slave sercos Master sercos Slave

The firmware determines the input signal or output signal. The following table shows the meaning of the SYNC signals for each protocol.

Signal IO_SYNC0

Input/Output

Signal IO_SYNC1

Input/Output

SYNC 0

Output

External trigger to start bus cycle

Input

Rising edge

CON_CLK

Output

SYNC 1

Output

DIV_CLK

Output

Table 93: Meaning of the SYNC Signals for each Protocol

From

Firmware

Version

Remarks

- Configurable

3.0.10.0 Configurable




9.10 Pin Assignment at the PC/104 Bus

9.10.1 Overview cifX

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

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

2

For the PC cards cifX

PC/104

the table below gives an overview about the pin assignment at the PC/104 bus.

Hardware

Revision

PC/104 Pin Assignment at the PC/104 Bus

Bus [Pins] according

Compare Section, page to the standard

104

yes Pin Assignment for PC/104 Bus

, 104

PC/104

Specification

[bus spec 8]

Table 94: Pin Assignment at the PC/104 Bus

9.10.2 Reference PC/104 Specification

No. Specification

[bus spec 8] PC/104 Specification

Revision Version De

2.6 October 13, 2008

Table 95: Reference PC/104 Specification

www

pcisig.com, pc104.org




9.10.3 Pin Assignment for PC/104 Bus

Only for:

CIFX 104-RE, CIFX 104-RE-R ,


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

3

4

1

2 SD7

SD6

SD5

GND

RESET

+5V

IRQ9

5 SD4

6 SD3

7 SD2

8 SD1

9 SD0

11 AEN

12 SA19

13 SA18

14 SA17

15 SA16

16 SA15

17 SA14

18 SA13

19 SA12

20 SA11

21 SA10

22 SA9

23

24

SA8

SA7

25 SA6

26 SA5

27 SA4

28 SA3

29 SA2

30 SA1

31

32

SA0

GND

SMEMW

SMEMR

IRQ7

IRQ6

IRQ5

IRQ4

IRQ3

+5V

GND

GND

Table 96: 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

105/171

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

4

5

6

7

8

9

10

11 SD8

12 SD9

13 SD10

14 SD11

15 SD12

16 SD13

17 SD14

18 SD15

19

IRQ10

IRQ11

IRQ12

IRQ15

IRQ14

+5V

GND

GND

Table 97: Pin Assignment for PC/104-Bus, X2 (Used Control Signals on the Expansion

Connector)

The pin assignment described in

Table 96

and

Table 97

originates from the standard [bus spec 8, page B-2] (refer to section

Reference PC/104

Specification

on page 103).



Technical Data

10 Technical Data

106/171

10.1 Technical Data PC Cards cifX

Note:

All technical data are temporarily and can be altered without notice.

10.1.1 CIFX 104-RE, CIFX 104-RE-R

CIFX 104-RE,

CIFX 104-RE-R

Part

Parameter Value

Name

Part No.

Description

Function

CIFX 104-RE CIFX 104-RE-R

1278.100 1279.100

PC Card cifX PC/104 for Real-Time Ethernet Master or

Slave; (for CIFX 104-RE-R connectors at the right side)

Communication Interface with PC/104 and Ethernet interface

Communication

Controller

Integrated Memory

System Interface

Ethernet

Communication

RAM

FLASH

Size of the Dual-Port Memory

Bus Type

Transmission Rate

Data Access

Width for the data access to the

Dual-Port Memory (DPM)

Supported Real-Time Ethernet communication systems

(determined by the loaded firmware)

8 MB SDRAM

4 MB serial Flash EPROM

16 KByte

PC/104, according to [bus spec 8], refer to section

Overview

, page 103.

33 MHz

DPM

8 Bit or 16 Bit

Ethernet interface

Ethernet Frame Types

Transmission Rate

Interface Type

Galvanic Isolation

Isolation Voltage

Half duplex/Full duplex

Auto-Negotiation

Auto-Crossover

Connector

Channel 0 and 1

EtherCAT Master, EtherCAT Slave



Open Modbus/TCP





Ethernet II

100 MBit/s,

10 MBit/s (depending on loaded firmware)

100 BASE-TX,

10 BASE-T (depending on loaded firmware), refer to section


, page 95. isolated

1000 VDC (tested for 1 minute) depending on loaded firmware, supported (at 100 MBit/s) depending on loaded firmware depending on loaded firmware

2* RJ45 Socket

With loaded EtherCAT Master firmware only the RJ45 channel 0 can be used, channel 1 is deactivated.



Technical Data

CIFX 104-RE,

CIFX 104-RE-R

Diagnosis Interface

Power supply

Operation

Environmental

Conditions

Device

CE Sign

Configuration

107/171

Parameter Value

USB Interface

Supply Voltage

Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated.

For Open Modbus/TCP with V2.3.4.0 and higher both

RJ45 channels can be used.

Mini B USB Plug (5 pin), refer to section

Mini-B USB

Connector (5 Pin)

, page 99.

SYS

System Status LED

The meaning of the following LEDs depends on the loaded firmware:

COM 0

COM 1

LED Communication Status 0 (duo LED)

LED yellow

LED green

LED Communication Status 1 (duo LED) at RJ45Ch0 and RJ45Ch1, for Ethernet Link status, Ethernet Activity status and additional status

Refer to chapter

LED Descriptions

, page 66.

+5 V dc ±5 %, refer to section


Interface

, page 29.

Maximum Current at at 5 V (typically) 500 mA

Connector Via PC/104 Bus

Rotary Switch Device Address

Is currently unassigned. Refer to section

Rotary Switch

Device Address

on page 99.

Operating temperature range* 0 °C ... +70 °C

*Air flow during measurment

Storage temperature range

0,5m/s

0 °C ... +70 °C

Humidity 10 … 95% relative humidity, no condensation permitted

Dimensions (L x W x H)

Mounting/Installation

97 x 91 x 24.3 mm

PC/104 Slot (5 V), refer to section

Slot for the PC Cards cifX PC/104

, page 29.

RoHS Yes

CE Sign Yes

Emission

Immunity

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A

(Radio disturbance characteristics - Limits and methods of measurement)

EN 61000-4-2:2009 (Electrostatic discharge test)

EN 61000-4-3:2006 + A1:2008 + A2:2010 (Radiated, radio-frequency, electromagnetic field test)

EN 61000-4-4:2004 + A1:2010 (Burst Electrical fast transients/burst test)

EN 61000-4-5:2006 (Surge test)

EN 61000-4-6:2009 (to conducted disturbances, induced by radio- frequency fields)

EN 61000-4-8:2010 (power frequency magnetic field test)

EN 61000-6-2:2005 + B1:2011 (for industrial environments)

SYCON.net Configuration Software

Master and Slave

Configuration Software Slave netX Configuration Tool

Table 98: Technical Data CIFX 104-RE, CIFX 104-RE-R



Technical Data 108/171

10.1.2 CIFX 104-RE\F, CIFX 104-RE-R\F

Parameter Value CIFX 104-RE\F,

CIFX 104-RE-R\F

Part Name

Part No.

Description

Function

CIFX 104-RE\F CIFX 104-RE-R\F

1278.101 1279.101

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 assembly interface (AIFX-RE) and

- diagnostic assembly interface (AIFX-DIAG).

Communication Interface with PC/104 and Ethernet interface

Communication

Controller

Integrated Memory

System Interface

Ethernet

Communication

RAM

FLASH


Bus Type

Transmission Rate

Data Access



Supported Real-Time Ethernet communication systems

(determined by the loaded firmware)

8 MB SDRAM


16 KByte


Overview

, page 103.

33 MHz

DPM

8 Bit or 16 Bit

Ethernet interface

Ethernet Frame Types

Transmission Rate

Interface Type

Half duplex/Full duplex

Auto-Negotiation

Auto-Crossover

Ethernet Assembly Interface

Connector AIFX-RE

Channel 0 and 1

EtherCAT Master, EtherCAT Slave



Open Modbus/TCP





Ethernet II

100 MBit/s,

10 MBit/s (depending on loaded firmware)

100 BASE-TX,

10 BASE-T (depending on loaded firmware), refer to section


, page 95. depending on loaded firmware, supported (at 100 MBit/s) depending on loaded firmware depending on loaded firmware

AIFX-RE, refer to section

AIFX-RE

, page 120.

Important!

Operating the PC cards CIFX 104-RE\F or CIFX 104-

RE-R\F requires proper connection of the Ethernet assembly interface (AIFX-RE) to the basic card!

Cable Connector Ethernet X4 (X304)

(JST SM20B-SRSS-TB(LF)(SN), Pitch 1,0 mm)

With loaded EtherCAT Master firmware only the RJ45 channel 0 can be used, channel 1 is deactivated.

Beginning with the EtherCAT Master firmware version 3 channel 1 can be reactivated if redundancy is activated.



Technical Data

CIFX 104-RE\F,

CIFX 104-RE-R\F

Diagnosis Interface

Power supply

Environmental

Conditions

Device

CE Sign

Configuration

109/171

Parameter Value

Diagnostic Assembly Interface

Connector AIFX-DIAG

Supply Voltage

Maximum Current at at 5 V (typically)

Connector

Operating temperature range*



For Open Modbus/TCP with V2.3.4.0 and higher both

RJ45 channels can be used.

AIFX-DIAG, refer to section

AIFX-DIAG

, page 125.

Note:

If the diagnostic

AIFX-DIAG

assembly interface is connected to the PC card CIFX 104-RE\F or CIFX 104-

RE-R\F, the

Mini-B USB


Cable Connector DIAG X3 (X303)

(JST 12FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm)

SYS

System Status LED

For LEDs at AIFX-RE, refer to section

AIFX-RE

, page 120.



Interface

, page 29.

500 mA

Via PC/104 Bus

0 °C ... +70 °C

0,5m/s

0 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign Yes

Emission

Immunity

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A





EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 99: Technical Data CIFX 104-RE\F, CIFX 104-RE-R\F




10.1.3 CIFX 104-DP, CIFX 104-DP-R

Parameter Value CIFX 104-DP,

CIFX 104-DP-R

Part Name

Part No.

Description

Function

CIFX 104-DP

1278.410

CIFX 104-DP-R

1279.410

PC Card cifX PC/104 PROFIBUS DP Master or Slave and

PROFIBUS MPI Device;

(for CIFX 104-DP-R connectors at the right side)

Communication Interface with PC/104 and fieldbus interface PROFIBUS

Communication

Controller

Integrated Memory

System Interface

PROFIBUS

Communication

PROFIBUS Interface

Diagnosis Interface

Power supply

Operation

Environmental

Conditions

Device

RAM

FLASH

8 MB SDRAM



Bus Type

16 KByte


Overview

, page 103.

33 MHz Transmission Rate

Data Access



DPM

8 Bit or 16 Bit

Supported communication standard/ protocol (determined by the loaded firmware)

PROFIBUS DP Master,

PROFIBUS DP Slave,

PROFIBUS MPI Device

Transmission Rate

Interface Type

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

RS 485, refer to section

PROFIBUS Interface

, page 97.

Galvanic Isolation

Isolation Voltage

Connector

USB Interface isolated

1000 VDC (tested for 1 minute)

DSub female Connector, 9 pin

Supply Voltage


Mini-B USB

Connector (5 Pin)

, page 99.

SYS

System Status LED

COM 0


The meaning of the COM LED depends on the loaded firmware. Refer to chapter

LED Descriptions

, page 66.



Interface

, page 29.

Maximum Current at at 5 V (typically) 500 mA

Connector Via PC/104 Bus

Rotary Switch Device Address Is currently unassigned. Refer to section

Rotary Switch

Device Address

on page 99.

Operating temperature range* -20 °C ... +70 °C



0,5m/s

-10 °C ... +70 °C

Humidity



10 … 95% relative humidity, no condensation permitted

97 x 91 x 24.3 mm



, page 29.



Technical Data

CIFX 104-DP,

CIFX 104-DP-R

CE Sign

Configuration

111/171

Parameter Value

RoHS Yes

CE Sign

Emission

Yes

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A


Immunity EN 61000-4-2:2009 (Electrostatic discharge test)



EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 100: Technical Data CIFX 104-DP, CIFX 104-DP-R

10.1.4 CIFX 104-DP\F, CIFX 104-DP-R\F

CIFX 104-DP\F,

CIFX 104-DP-R\F

Part

Parameter Wert

Name

Part No.

Description

Function

CIFX 104-DP\F

1278.411

CIFX 104-DP-R\F

1279.411

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 assembly interface (AIFX-DP) and


Communication Interface with PC/104 and fieldbus interface PROFIBUS

Communication

Controller

Integrated Memory

System Interface

RAM

FLASH


Bus Type

8 MB SDRAM


16 KByte


Overview

, page 103.

PROFIBUS

Communication

Transmission Rate

Data Access

33 MHz

DPM




8 Bit or 16 Bit

PROFIBUS DP Master,

PROFIBUS DP Slave,

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



Technical Data

CIFX 104-DP\F,

CIFX 104-DP-R\F

Diagnosis Interface

Power supply

Environmental

Conditions

Device

CE Sign

Configuration

112/171

Parameter Wert

Interface Type RS 485, refer to section

PROFIBUS Interface

page 97.

PROFIBUS Assembly Interface AIFX-DP, refer to section

AIFX-DP

page 121.

Important!

Operating the PC cards CIFX 104-DP\F or CIFX 104-

DP-R\F requires proper connection of the PROFIBUS assembly interface (AIFX-DP) to the basic card!

Connector AIFX-DP


Cable Connector Fieldbus X4 (X304)



AIFX-DIAG

, page 125.

Connector AIFX-DIAG

Supply Voltage


Connector






SYS

System Status LED

For LEDs at AIFX-DP, refer to section

AIFX-DP

page 121.



Interface

, page 29.

500 mA

Via PC/104 Bus

-20 °C ... +70 °C

0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign

Emission

Immunity

Yes

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A





EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 101: Technical Data CIFX 104-DP\F, CIFX 104-DP-R\F




10.1.5 CIFX 104-CO, CIFX 104-CO-R

Parameter Value CIFX 104-CO,

CIFX 104-CO-R

Part Name

Part No.

Description

Function

CIFX 104-CO CIFX 104-CO-R

1278.500 1279.500

PC Card cifX PC/104 CANopen Master or Slave;

(for CIFX 104-CO-R connectors at the right side)

Communication Interface with PC/104 and fieldbus interface CANopen

Communication

Controller

Integrated Memory

System Interface

CANopen

Communication

CANopen Interface

Diagnosis Interface

Power supply

Operation

Environmental

Conditions

Device

RAM

FLASH


Bus Type

8 MB SDRAM


16 KByte


Overview

, page 103.

Transmission Rate

Data Access




8 Bit or 16 Bit

CANopen Master,

CANopen Slave

Transmission Rate

33 MHz

DPM

Interface Type

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

ISO-11898, refer to section

CANopen Interface

, page 97.

Galvanic Isolation

Isolation Voltage

Connector

USB Interface isolated (optically isolated)


Supply Voltage


Connector







Mini-B USB

Connector (5 Pin)

, page 99.

SYS

System Status LED

CAN

CANopen Status (duo LED)

The meaning of the CAN LED is depending on loaded firmware. Refer to chapter

LED Descriptions

, page 66.



Interface

, page 29.

500 mA

Via PC/104 Bus


Rotary Switch

Device Address

on page 99.

-20 °C ... +70 °C

0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes



Technical Data

CIFX 104-CO,

CIFX 104-CO-R

CE Sign

Configuration

114/171

Parameter Value

CE Sign

Emission

Immunity

Yes

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A





EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 102: Technical Data CIFX 104-CO, CIFX 104-CO-R

10.1.6 CIFX 104-CO\F, CIFX 104-CO-R\F

Parameter Value CIFX 104-CO\F,

CIFX 104-CO-R\F

Part Name

Part No.

Description

Function

CIFX 104-CO\F CIFX 104-CO-R\F

1278.501 1279.501

PC Card cifX PC/104 CANopen Master or Slave composed of:



- CANopen assembly interface (AIFX-CO) and


Communication Interface with PC/104 and fieldbus interface CANopen

Communication

Controller

Integrated Memory

System Interface

CANopen

Communication

CANopen Interface

RAM

FLASH


Bus Type

8 MB SDRAM


16 KByte


Overview

, page 103.

Transmission Rate

Data Access




8 Bit or 16 Bit

CANopen Master,

CANopen Slave

Transmission Rate

33 MHz

DPM

Interface Type

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

ISO-11898, refer to section

CANopen Interface

, page 97.

CANopen Assembly Interface AIFX-CO, refer to section

AIFX-CO

, page 122.



Technical Data

CIFX 104-CO\F,

CIFX 104-CO-R\F

Diagnosis Interface

Power supply

Environmental

Conditions

Device

CE Sign

Configuration

115/171

Parameter Value

Connector AIFX-CO


Connector AIFX-DIAG

Supply Voltage


Connector




Important!

Operating the PC cards CIFX 104-CO\F or CIFX 104-

CO-R\F requires proper connection of the CANopen assembly interface (AIFX-CO) to the basic card!




AIFX-DIAG

, page 125.



SYS

System Status LED

For LEDs at AIFX-CO, refer to section

AIFX-CO

, p. 122.



Interface

, page 29.

500 mA

Via PC/104 Bus

-20 °C ... +70 °C

0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign

Emission

Yes

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A


Immunity EN 61000-4-2:2009 (Electrostatic discharge test)



EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 103: Technical Data CIFX 104-CO\F, CIFX 104-CO-R\F




10.1.7 CIFX 104-DN, CIFX 104-DN-R

CIFX 104-DN,

CIFX 104-DN-R

Part

Parameter

Name

Part No.

Description

Function

Value

CIFX 104-DN CIFX 104-DN-R

1278.510 1279.510

PC Card cifX PC/104 DeviceNet Master or Slave;

(for CIFX 104-DN-R connectors at the right side)

Communication Interface with PC/104 and fieldbus interface DeviceNet

Communication

Controller

Integrated Memory

System Interface

DeviceNet

Communication

DeviceNet Interface

Diagnosis Interface

Power supply

Operation

Environmental

Conditions

Device

RAM

FLASH


Bus Type

8 MB SDRAM


16 KByte


Overview

, page 103.

Transmission Rate

Data Access

33 MHz

DPM




8 Bit or 16 Bit

DeviceNet Master,

DeviceNet Slave

Transmission Rate

Interface Type

Galvanic Isolation

Isolation Voltage

Connector

USB Interface

125 kBit/s, 250 kBit/s, 500 kBit/s

ISO-11898 according to DeviceNet specification, refer to section

DeviceNet Interface

, page 98. isolated (optically isolated)


Supply Voltage

CombiCon male Connector, 5-polig


Mini-B USB

Connector (5 Pin)

, page 99.

SYS

System Status LED

MNS

Module network status (duo LED)

The meaning of the MNS LED is depending on loaded firmware. Refer to chapter

LED Descriptions

, page 66.



Interface

, page 29.


Connector


500 mA

Via PC/104 Bus


Rotary Switch

Device Address

on page 99.




0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign Yes CE Sign



Technical Data

CIFX 104-DN,

CIFX 104-DN-R

Parameter Value

117/171

Configuration

Emission

Immunity

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A





EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 104: Technical Data CIFX 104-DN, CIFX 104-DN-R

10.1.8 CIFX 104-DN\F, CIFX 104-DN-R\F

CIFX 104-DN\F,

CIFX 104-DN-R\F

Part

Parameter Value

Name

Part No.

Description

Function

CIFX 104-DN\F

1278.511

CIFX 104-DN-R\F

1279.511

PC Card cifX PC/104 DeviceNet Master or Slave composed of:



- DeviceNet assembly interface (AIFX-DN)and


Communication Interface with PC/104 and fieldbus interface DeviceNet

Communication

Controller

Integrated Memory

System Interface

DeviceNet

Communication

DeviceNet Interface

RAM

FLASH


Bus Type

8 MB SDRAM


16 KByte


Overview

, page 103.


Data Access



DPM

8 Bit or 16 Bit


Transmission Rate

DeviceNet Master,

DeviceNet Slave

125 kBit/s, 250 kBit/s, 500 kBit/s

Interface Type ISO-11898 according to DeviceNet specification, refer to section

DeviceNet Interface

, page 98.

DeviceNet Assembly Interface AIFX-DN,

AIFX-DN,

page 123.

Important!

Operating the PC cards CIFX 104-DN\F or CIFX 104-



Technical Data

CIFX 104-DN\F,

CIFX 104-DN-R\F

Diagnosis Interface

Power supply

Environmental

Conditions

Device

CE Sign

Configuration

118/171

Parameter Value

Connector AIFX-DN


Connector AIFX-DIAG

Supply Voltage


Connector




DN-R\F requires proper connection of the DeviceNet assembly interface (AIFX-DN) to the basic card!




AIFX-DIAG

, page 125.



SYS

System Status LED

For LED at AIFX-DN, refer to section

AIFX-DN,

p. 123.



Interface

, page 29.

500 mA

Via PC/104 Bus

-20 °C ... +70 °C

0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign Yes

Emission

Immunity

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A





EN 61000-4-5:2006 (Surge test)





Master and Slave


Table 105: Technical Data CIFX104C-DN\F, CIFX 104-DN-R\F

CIFX 104-CC\F

Part

Parameter Value

Part No.

Description

1278.741

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 assembly interface (AIFX-CC) and



Technical Data

CIFX 104-CC\F Parameter

Function

119/171

Value


Communication Interface with PC/104 and fieldbus interface CC-Link

Communication

Controller

Integrated Memory

System Interface

CC-Link

Communication

CC-Link Interface

Diagnosis Interface

Power supply

Environmental

Conditions

Device

CE Sign

RAM

FLASH

8 MB SDRAM



Bus Type

16 KByte


Overview

, page 103.


Data Access



DPM

8 Bit or 16 Bit


Transmission Rate

CC-Link Slave

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

CC-Link Assembly Interface

Connector AIFX-CC


Connector AIFX-DIAG

Supply Voltage


Connector




AIFX-CC, refer to section

AIFX-CC

page 124.

Important!

Operating the PC cards CIFX 104-CC\F requires proper connection of the CC-Link assembly interface (AIFX-CC) to the basic card!

Cable Connector Fieldbus X4



AIFX-DIAG

, page 125.

Cable Connector DIAG X3


SYS

System Status LED

For LEDs at AIFX-CC, refer to section

AIFX-CC

page 124.



Interface

, page 29.

500 mA

Via PC/104 Bus

0 °C ... +60 °C

0,5m/s

-10 °C ... +70 °C




97 x 91 x 24.3 mm



, page 29.

RoHS Yes

CE Sign

Emission

Immunity

Yes

EN 55011:2009 + A1:2010, CISPR 11:2009, Class A




EN 61000-4-4:2004 + A1:2010 (Burst Electrical fast



Technical Data

CIFX 104-CC\F Parameter

120/171

Value

transients/burst test)

EN 61000-4-5:2006 (Surge test)




Table 106: Technical Data CIFX104C-CC\F

10.1.10 AIFX-RE

AIFX-RE

Part

Interface

PC Card cifX

Ethernet Interface

Parameter Value

Name AIFX-RE

Part No.

Description

2800.100

Ethernet assembly interface (with Ethernet interface) for the PC cards CIFX 104-RE\F, CIFX 104-RE-R\F

Connector

Galvanic Isolation

Isolation Voltage

Connector

Cable Connector Ethernet X1

(JST SM20B-SRSS-TB(LF)(SN), Pitch 1.0 mm) isolated


2* RJ45 Socket

Display

Power supply

Environmental

Conditions

Device

CE Sign

UL Certification

LED Display (on the reverse side of the device)

Connector




The meaning of the following LEDs depends on the loaded firmware::

COM 0


COM 1


LED yellow

LED green

at RJ45Ch0 and RJ45Ch1, for Ethernet Link status, Ethernet Activity status and additional status

Refer to chapter

LED Descriptions

, page 66.

Cable Connector Ethernet X1

0 °C ... +70 °C

0,5m/s

0 °C ... +70 °C


Environment



For UL compliant usage:

The device must be used in a pollution degree 2 environment.

30,7 x 42,3 x 18,5 mm (H = width of the front panel)

At the basic cards CIFX 104-RE\F, CIFX 104-RE-R\F:

Cable Connector Ethernet X4 (X304)

RoHS Yes

CE Sign Yes

Emission, Immunity

The device is certified according to UL 508

Tested together with the corresponding basic card cifX.

UL-File-Nr. E221530

Table 107: Technical Data AIFX-RE



Technical Data

10.1.11 AIFX-DP

AIFX-DP

Part

Interface

PC Card cifX

PROFIBUS Interface

Display

Power supply

Environmental

Conditions

Device

CE Sign

UL Certification

121/171

Parameter Value

Name AIFX-DP

Part No.

Description

Connector

Galvanic Isolation

Isolation Voltage

2800.400

PROFIBUS assembly interface (with PROFIBUS interface) for the PC cards



(JST 10FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm) isolated

Connector




The meaning of the following LEDs depends on the loaded firmware:

Connector


ERR

STA

LED Error status (red)

LED Status (green)

For PROFIBUS MPI the STA LED is not used.

Refer to chapter

LED Descriptions

, page 66.


-20 °C ... +70 °C



0,5m/s

-10 °C ... +70 °C


Environment





17 x 31 x 18,5 mm (H = width of the front panel)

At the basic cards CIFX 104-FB\F, CIFX 104-FB-R\F:


RoHS Yes

CE Sign Yes

Emission, Immunity


Tested together with the corresponding basic card cifX.

UL-File-Nr. E221530

Table 108: Technical Data AIFX-DP



Technical Data

10.1.12 AIFX-CO

AIFX-CO

Part

Interface

PC Card cifX

CANopen Interface

Display

Power supply

Environmental

Conditions

Device

CE Sign

UL Certification

122/171

Parameter Value

Name AIFX-CO

Part No.

Description

2800.500

CANopen assembly interface (with CANopen interface) for the PC cards CIFX 104-CO\F, CIFX 104-CO-R\F

Connector

Galvanic Isolation

Isolation Voltage

Connector



(JST 10FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm) isolated (optically isolated)




ERR

LED Error status (red)

RUN

LED Run (green)

Refer to chapter

LED Descriptions

, page 66.

Connector



-20 °C ... +70 °C



0,5m/s

-10 °C ... +70 °C


Environment





17 x 31 x 18,5 mm (H = width of the front panel)



RoHS Yes

CE Sign Yes

Emission, Immunity


Tested together with the corresponding basic card cifX..

UL-File-Nr. E221530

Table 109: Technical Data AIFX-CO



Technical Data

10.1.13 AIFX-DN

AIFX-DN

Part

Interface

PC Card cifX

DeviceNet Interface

Display

Power supply

Environmental

Conditions

Device

CE Sign

UL Certification

123/171

Parameter Value

Name AIFX-DN

Part No.

Description

2800.510

DeviceNet assembly interface (with DeviceNet interface) for the PC cards CIFX 104-DN\F, CIFX 104-DN-R\F

Connector

Galvanic Isolation

Isolation Voltage

Connector



(JST 10FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm) isolated (optically isolated)



MNS

Module network status (duo LED)

Connector


The meaning of the MNS LED is depending on loaded firmware. Refer to chapter

LED Descriptions

, page 66.


-20 °C ... +70 °C



0,5m/s

-10 °C ... +70 °C


Environment





23,7 x 31 x 18,5 mm (L = 23,7, without CombiCon male

Connector; H = width of the front panel)



RoHS Yes

CE Sign Yes

Emission, Immunity



UL-File-Nr. E221530

Table 110: Technical Data AIFX-DN



Technical Data

10.1.14 AIFX-CC

AIFX-CC

Part

Interface

PC Card cifX

CC-Link Interface

Display

Power supply

Environmental

Conditions

Device

CE Sign

124/171

Parameter Value

Name AIFX-CC

Part No.

Description

2800.730

CC-Link assembly interface (with CC-Link interface) for the PC card CIFX 104-CC\F

Connector Cable Connector Fieldbus X1

(JST 10FMN-SMT-A-TF(LF)(SN), Pitch 1,0 mm) isolated (optically isolated) Galvanic Isolation

Isolation Voltage

Connector




L RUN

L ERR

LED L Run (Duo-LED)

LED L Error (Duo-LED)

Refer to chapter

LED Descriptions

, page 66.

Connector





0 °C ... +60 °C

0,5m/s

-10 °C ... +70 °C




43,2 x 31 x 18,5 mm (L = 43,2, without CombiCon male

Connector; H = width of the front panel)

At the basic card CIFX 104-FB\F:


RoHS Yes

CE Sign Yes

Emission, Immunity Tested together with the corresponding basic card cifX.

Table 111: Technical Data AIFX-CC




10.1.15 AIFX-DIAG

AIFX-DIAG

Part

Schnittstelle

PC-Karte cifX

Diagnosis Interface

Power supply

Operation

Environmental

Conditions

Device

CE Sign

UL Certification

Parameter Value

Name AIFX-DIAG

Part No.

Description

2800.000

Connector

Diagnostic assembly interface (with diagnostic interface) for the PC cards


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

Cable Connector DIAG X1


USB Interface Mini B USB Plug (5 pin), refer to section

Mini-B USB

Connector (5 Pin)

, page 99.

PWR

SYS

Supply Voltage ON LED

System Status LED


COM 0


COM 1


Connector

Refer to chapter

LED Descriptions

, page 66.

Kabelstecker DIAG X1

Rotary Switch Device Address Is currently unassigned. Refer to section

Rotary Switch

Device Address

on page 99.




0,5m/s

-10 °C ... +70 °C


Environment



20,5 x 52,7 x 18,5 mm (H = width of the front panel) Dimensions (L x W x H)

Mounting/Installation For the basic cards:

CIFX 104-RE\F, CIFX 104-RE-R\F,

CIFX 104-FB\F, CIFX 104-FB-R\F


RoHS Yes

CE Sign Yes

Emission, Immunity



UL-File-Nr. E221530

Table 112: Technical Data AIFX-DIAG



Technical Data

10.2 Technical Data of the Communication Protocols

126/171

Parameter

Maximum number of EtherCAT slaves

Maximum number of cyclic input data

Maximum number of cyclic output data

Minimum bus cycle time

Acyclic communication

Functions

Bus Scan

Description

Maximum 200 Slaves. The number of usable slaves depends on the available memory for the configuration file. See ‘configuration file’ below.

5760 bytes

5760 bytes

205 µs, depending on the used number of slaves and the used number of cyclic input data and output data. Recommended is a cycle time of 1 ms and higher.

CoE (CANopen over EtherCAT)

CoE-Upload, CoE-Download

Maximum 1500 bytes

Get OD List

Get object description

Get entry description

Emergency

Slave diagnostics

Supported

Distributed Clocks

Topology

Baud rate

Data transport layer

Configuration File (ethercat.xml or config.nxd)

Limitations

Reference to firmware/stack version

Supported, but not at the same time with Redundancy

Line or ring

100 MBit/s

Ethernet II, IEEE 802.3

PC cards PCI, PCI Express, PCI Express Low Profile, Mini PCI,

Compact PCI, Mini PCI Express, PCI-104 Real-Time Ethernet:

Maximum 1 MByte

PC cards PC/104 Real-Time Ethernet: Maximum 2 MByte

The size of the bus configuration file is limited by the size of the

RAM Disk (1 Mbyte) or FLASH disk (2 Mbyte).

All CoE Uploads, Downloads and information services must fit in one TLR-Packet. Fragmentation is not supported

Distubuted Clock and Redundancy can not be used at the same time.

V3.0.x.x

Table 113: Technical Data EtherCAT Master Protocol




Parameter




Description

256* bytes

256* bytes

SDO

SDO Master-Slave

SDO Slave-Slave (depending on Master capability)

Functions Emergency

FMMUs 3

SYNC Manager 4

Baud rate


Limitation


100 MBit/s


LRW is not supported

V2.5.x.x and V4.2.x.x

Table 114: Technical Data EtherCAT Slave Protocol

Note:

* The loadable firmware supports for the number of cyclic input data and for cyclic output data in total up to 512 bytes. If more than 256 bytes for input data or for output data shall be exchanged via EtherCAT, then a customer specific XML file is necessary. Additionally the following formula applies: The sum of the input data length and the ouput data length may not exceed 512 bytes, where each length has to be rounded up to the next multiple of 4 for this calculation.




10.2.3 EtherNet/IP Scanner (Master)

Parameter

Maximum number of EtherNet/IP connections

Maximum number of total cyclic input data

Maximum number of total cyclic output data



IO Connection type

Description

64 connections for implicit and explicit

5712 bytes

5760 bytes

504 bytes per slave per telegram

504 bytes per slave per telegram

Cyclic, minimum 1 ms (depending on used number of connections and used number of input and output data)

Maximum number of unscheduled data

UCMM, Class 3

Explicit Messages, Client and Server Services

Quick connect

Predefined standard objects

Maximal number of user specific objects

Topology

1400 bytes per telegram

Supported

Get_Attribute_Single/All

Set_Attribute_Single/All

Supported

Identity Object

Message Route Object

Assembly Object

Connection Manager

Ethernet Link Object

TCP/IP Object

DLR Object

QoS Object

20

Tree, Line, Ring

DLR (Device Level Ring)

ACD (Address Conflict Detection)

Beacon based ’Ring Node’

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

V2.6.x.x

Table 115: Technical Data EtherNet/IP Scanner (Master) Protocol




10.2.4 EtherNet/IP Adapter (Slave)

Parameter

Maximum number of input data

Maximum number of output data

IO connection types (implicit)

IO Connection trigger types

Description

504 bytes

504 bytes

1 exclusive owner, 1 listen only, 1 input only

Cyclic, minimum 1 ms*

Application Triggered, minimum 1 ms*

Change Of State, minimum 1 ms*

* depending on number of connections and number of input and output data

Connected and unconnected

8, explicit and implicit connections

Supported

Supported

Explicit Messages

Maximum number of connections

Unconnected Message Manager (UCMM)

Quick connect

Predefined standard objects Identity Object

Message Route Object

Assembly Object

Connection Manager

DLR Object

QoS Object

TCP/IP Object

Ethernet Link Object

Reset services

Maximum number of user specific objects

DLR V2 (ring topology)

ACD (Address Conflict Detection)

Identity Object Reset Service of Type 0 and 1

20

Supported

Supported

DHCP Supported

BOOTP Supported

Baud rates 10 and 100 MBit/s

Duplex modes

MDI modes


Switch function

Limitations


Half duplex, Full duplex, Auto negotiation

MDI, MDI-X, Auto-MDIX


Integrated

CIP Sync Services are not implemented

TAGs are not supported

V2.7.x.x

Table 116: Technical Data EtherNet/IP Adapter (Slave) Protocol




Parameter

Maximum number of input data

Maximum number of output data


Modbus Function Codes

Protocol Mode

Baud rates



Description

2880 Registers

2880 Registers

Read/Write Register:

- Maximum 125 Registers per Read Telegram (FC 3, 4, 23),

- Maximum 121 Registers per Write Telegram (FC 23),

- Maximum 123 Registers per Write Telegram (FC 16)

Read/Write Coil:

- Maximum 2000 Coils per Read Telegram (FC 1, 2),

- Maximum 1968 Coils per Write Telegram (FC 15)

1,

2,

3,

4,

5,

6,

7,

15,

16,

23*

* Function Code 23 can be used via the packet API, but not with the Command Table.

Message Mode (Client Mode):

- Client (using the Command Table: The data is stored in the I/O process data image)

- Client (using the packet API: The I/O process data image is not used)

- Server (using the packet API: The I/O process data image is not used)

I/O Mode (Server Mode):

- Server (only) (The data is stored in the I/O process data image)

10 and 100 MBit/s


V2.5.x.x

Table 117: Technical Data Open Modbus/TCP Protocol

Parameter



Acyclic data transfer

Functions

Baud rate


Ethernet POWERLINK version

Limitation


Description

1490 bytes

1490 bytes

SDO Upload/Download

SDO over ASND and UDP

100 MBit/s, half-duplex


V 2

No slave to slave communication

V2.1.x.x

Table 118: Technical Data POWERLINK Controlled Node (Slave) Protocol




Parameter Description

Maximum number of PROFINET IO Devices 128

Maximum number of total cyclic input data 5712 bytes (including IOxS status bytes)

Maximum number of total cyclic output data 5760 bytes (including IOxS status bytes)



1440 bytes per device (= IOCR data length including IOxS status bytes)

1440 bytes per device (= IOCR data length including IOxS status bytes)


Alarm processing

Diagnostic data

Read/Write Record

Limited to 1392 bytes per telegram

Limited to 4096 bytes per request yes, but requires handling in host application program

One 200 byte buffer per IO device

DCP functions via API

Supported Protocols

Context management by CL-RPC

Minimum cycle time

Functions

Baud rate


Configuration file

Limitations

Name Assignment IO-Devices (DCP SET NameOfStation)

Set IO-Devices IP (DCP SET IP)

Signal IO-Device (DCP SET SIGNAL)

Reset IO-Device to factory settings (DCP Reset FactorySettings)

Bus scan (DCP IDENTIFY ALL)

RTC – Real Time Cyclic Protocol, Class 1

RTA – Real Time Acyclic Protocol

DCP – Discovery and configuration Protocol

CL-RPC – Connectionless Remote Procedure Call

Supported

1 ms

Different IO-Devices can be configured with different cycle times

Fast Startup of PROFINET IO Devices supported

100 MBit/s

Full-Duplex mode


Maximum 1 MByte

RT over UDP not supported

Multicast communication not supported

DHCP is not supported (neither for PROFINET IO-Controller nor for the IO-Devices)

Only one IOCR per IO Device

NameOfStation of IO Controller CANNOT be set using the DCP SET

NameOfStation service but only at start-up while configuring the IO

Controller

The buffer for IO-Device diagnosis data will be overwritten in case of multiple diagnostic events. Only one (the last) event is stored at the same time. If a single event produces more than 200 bytes of diagnosis data, only the first 200 bytes will be taken care of.

The usable (minimum) cycle time depends on the number of used IO

Devices, the number of used input and output data. The cycle-time, the number of configured IO Devices and the amount of IO data depend on each other. For example it is not possible due to performance reasons to have 128 IO Devices communication with cycle-time 1ms.

The size of the bus configuration file is limited by the size of the RAM

Disk (1 MByte)

WriteMultiple-Record service is not supported



Technical Data

Parameter


Description

V2.6.x.x

Table 119: Technical Data PROFINET IO RT Controller

132/171

10.2.8 PROFINET IO-Device (V3.4)

Parameter




Alarm Types

Used Protocols (subset)

Topology recognition

VLAN- and priority tagging

Context Management by CL-RPC

Identification & Maintenance

Minimum cycle time

Supported protocols

Baud rate


Limitations


Description

1024 bytes

1024 bytes

Read/Write Record, max. 1024 bytes per telegram

Process Alarm, Diagnostic Alarm, Return of SubModule Alarm

Plug Alarm (implicit), Pull Alarm (implicit)

RTC – Real Time Cyclic Protocol, Class 1 and 2 (unsynchronized), Class

3 (synchronized)




LLDP – Link Layer Discovery Protocol

SNMP – Simple Network Management Protocol

MRP – MRP Client

UDP, IP, ARP, ICMP (Ping)

LLDP, SNMP V1, MIB2, physical device yes

Supported

Read and write of I&M1-4

1 ms for RTC1 and RTC2

250 µs for RTC3

100 MBit/s




Only one device instance is supported

DHCP is not supported

IRT “flex” (synchronized RT Class 2) is not supported

FastStartUp is not supported.

Media Redundancy (except MRP client) is not supported

Access to the submodule granular status bytes (IOCS) is not supported.

The amount of configured IO-data influences the minimum cycle time that can be reached.

Supervisor-AR is not supported, Supervisor-DA-AR is supported

Only 1 Input-CR and 1 Output-CR are supported

Multiple WriteRequests are not supported

Using little endian (LSB-MSB) byte order for cyclic process data instead of default big endian (MSB-LSB) byte order may have an negative impact on minimum reachable cycle time

V3.4.x.x

Table 120: Technical Data PROFINET IO RT IRT Device Protocol




10.2.9 PROFINET IO-Device (V3.5)

Parameter



Maximum number of submodules

Multiple Application Relations (AR)


Alarm Types

Supported protocols

Topology recognition

Identification & Maintenance

Minimum cycle time

IRT Support

Media Redundancy

Additional features

Baud rate


PROFINET IO specification

Limitations


Description

1440 bytes

1440 bytes

255 submodules per Application Relation at the same time,

1000 submodules can be configured

The Stack can handle up to 2 IO-ARs, one Supervisor AR and one

Supervisor-DA AR at the same time

Read/Write Record, max. 1024 bytes per telegram

Process Alarm, Diagnostic Alarm, Return of SubModule Alarm,

Plug Alarm (implicit), Pull Alarm (implicit)

RTC – Real Time Cyclic Protocol, class 1 (unsynchronized), class 3 (synchronized)




LLDP – Link Layer Discovery Protocol

SNMP – Simple Network Management Protocol

MRP – MRP Client

LLDP, SNMP V1, MIB2, physical device

Read and write of I&M1-4

1 ms for RT_CLASS_1

250 µs for RT_CLASS_3

RT_CLASS_3

MRP client is supported

DCP, VLAN- and priority tagging, Shared Device

100 MBit/s


V2.2 (legacy startup) and

V2.3 (but advanced startup only for RT) are supported



Only one device instance is supported

DHCP is not supported

FastStartUp is not supported

The amount of configured IO-data influences the minimum cycle time that can be reached.

Only 1 Input-CR and 1 Output-CR are supported

Using little endian (LSB-MSB) byte order for cyclic process data instead of default big endian (MSB-LSB) byte order may have an negative impact on minimum reachable cycle time

System Redundancy (SR-AR) and Configuration-in-Run (CiR) are not supported

Max. 255 submodules can be used simultaneously within one specific

Application Relation

Advanced Startup according Profinet specification V2.3 is NOT yet supported for IRT

As there is no official certification available for Profinet IO specification

V2.3 at the time of release of the stack there is no guarantee that this implementation will pass such a certification once it is available

V3.5.26.x

Table 121: Technical Data PROFINET IO RT IRT Device Protocol



Technical Data

10.2.10 sercos Master

Parameter



Maximum number of configured slave devices

Minimum cycle time


Description

5760 bytes (including Connection Control per Connection)

5760 bytes (including Connection Control per Connection)

511

250 µs

Service channel: Read/Write/Commands

134/171

Communication phases

Topology

NRT, CP0, CP1, CP2, CP3, CP4

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 sercos version

TCP/IP stack supported

Communication Specification Version 1.3 integrated

Reference to firmware/stack version V2.1.x.x

Table 122: Technical Data sercos Master Protocol




10.2.11 sercos Slave

Parameter

Maximum number of cyclic input data (Tx) of all slaves

Description

128 bytes (including Connection Control and IO Status)

Maximum number of cyclic output data (Rx) of all slaves 128 bytes (including Connection Control and IO Status)

Maximum number of slave devices 8

Maximum number of applicable sercos addresses 1 … 511

Minimum cycle time

Topology

Communication phases

Acyclic Communication (Service Channel)

250 µs

Line and ring

NRT, CP0, CP1, CP2, CP3, CP4

Read/Write/Standard Commands

Baud rate


Supported sercos version

Supported sercos Communication Profiles

Supported User SCP Profiles

100 MBit/s

Ethernet II, IEEE 802.3 sercos in the third generation

Communication Specification Version 1.1.2

SCP_FixCFG Version 1.1.1

SCP_VarCFG Version 1.1.1

SCP_VarCFG Version 1.1.3

SCP_WD Version 1.1.1

SCP_Diag Version 1.1.1

SCP_RTB Version 1.1.1

SCP_Mux Version 1.1.1

SCP_Sig Version 1.1.1

SCP_ExtMuX Version 1.1.2

SCP_RTBListProd Version 1.3

SCP_RTBListCons Version 1.3

SCP_RTBWordProd Version 1.3

SCP_RTBWordCons Version 1.3

SCP_OvSBasic Version 1.3

SCP_WDCon Version 1.3

FSP_IO Supported FSP profiles

SCP Sync

FSP_Drive

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)


Hot plug is not supported yet

Cross communication not supported yet

NRT Channel only forwarding

V3.1.x.x

Table 123: Technical Data sercos Slave Protocol



Technical Data

10.2.12 VARAN Client (Slave)

Parameter



Memory Area

Description

128 bytes

128 bytes

Read Memory Area 1,

Write Memory Area 1

136/171

Memory Write

Integrated 2 port splitter for daisy chain topology Supported

Baud rate 100 MBit/s


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

Memory area 2 is not supported.


Table 124: Technical Data VARAN Client Protocol




10.2.13 PROFIBUS DP Master

Parameter

Maximum number of PROFIBUS DP slaves





Configuration data

Parameterization data per slave


Maximum number of acyclic read/write

Functions

Description

125 (DPV0/DPV1)

5712 bytes

5760 bytes

244 bytes per slave

244 bytes per slave

Max. 244 bytes per slave

7 bytes standard parameter per slave

Max. 237 bytes application specific parameters per slave

DPV1 class 1 read, write

DPV1 class 1 alarm

DPV1 class 2 initiate, read, write, data transport, abort

240 bytes per slave and telegram

Configuration in Run (CiR), requires host application program support

Timestamp (Master functionality)

Baud rate


Limitations


9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s

Auto baud rate detection is not supported

PROFIBUS FDL

DPV2 isochronous mode and slave slave communication are not supported.

The redundancy function can not be used, if the master is configured by the host application program by packets.

V2.6.x.x

Table 125: Technical Data PROFIBUS DP Master Protocol




10.2.14 PROFIBUS DP Slave

Parameter



Maximum number of acyclic data (read/write)

Maximum number of modules

Configuration data

Parameter data


Baud rate


Limitations

Description

244 bytes

244 bytes

240 bytes/telegram

24

Max. 244 bytes

237 bytes application specific parameters

DP V1 Class 1 Read/Write

DP V1 Class 1 Alarm

DP V1 Class 2 Read/Write/Data Transport

9,6 kBits/s,

19,2 kBits/s,

31,25 kBits/s,

45,45 kBits/s

93,75 kBits/s,

187,5 kBits/s,

500 kBits/s,

1, 5 MBits/s,

3 MBits/s,

6 MBits/s,

12 MBit/s

Auto baudrate detection is supported

PROFIBUS FDL

SSCY1S – Slave to slave communication state machine not implemented

Data exchange broadcast not implemented

I&M LR services other than Call-REQ/RES are not supported yet


Table 126: Technical Data PROFIBUS DP Slave Protocol




10.2.15 PROFIBUS MPI

Parameter

Maximum number of MPI connections

Maximum number of write data

Maximum number of read data

Functions

Baud rate



Description

126

216 bytes

222 bytes

MPI Read/Write DB (data block), M (marker), Q (output), C

(Counter), T (Timer)

MPI Read I (Input)

Data type bit to access to DB (data block), M (marker), Q

(output) and I (Input, read only)

MPI Connect (automatically when first read/write function is used)

MPI Disconnect, MPI Disconnect All

MPI Get OP Status

MPI transparent (expert use only)

Fixed values ranging from 9,6 kBits/s to 12 MBit/s

Auto-detection mode is supported

PROFIBUS FDL

2.4.x.x

Table 127: Technical Data PROFIBUS-MPI Protocol




10.2.16 CANopen Master

Parameter

Maximum number of CANopen nodes



Maximum number of receive PDOs

Maximum number of transmit PDOs

Exchange of process data


Functions

Baud rates

CAN layer 2 access


CAN Frame type for CANopen

Reference to version

Description

126

3584 bytes

3584 bytes

512

512

Via PDO transfer:

- synchronized,

- remotely requested and

- event driven (change of date)

SDO Upload/Download, max. 512 bytes per request

Emergency message (consumer and producer)

Node guarding / life guarding, heartbeat

PDO mapping

NMT Master

SYNC protocol (producer)

Simple boot-up process, reading object 1000H for identification

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s

Send/receive via API supported (11 bit/29 bit)

CAN Frames

11 Bit

V2.11.x.x

Table 128: Technical Data CANopen Master Protocol




10.2.17 CANopen Slave

Parameter



Maximum number of receive PDOs

Maximum number of transmit PDOs

Exchange of process data


Functions

Description

512 bytes

512 bytes

64

64

Via PDO transfer

- synchronized,

- remotely requested and

- event driven (change of date, event timer)

On request of the host application program by packet

SDO upload/download (server only)

Emergency message (producer)

Timestamp (producer/consumer)

Node guarding / life guarding

Heartbeat: 1 producer, max. 64 consumer

PDO mapping

NMT Slave

SYNC protocol (consumer)

Error behaviour (configurable):

- in state operational: change to state pre-operational

- in any state: no state change

- in state operational or pre-operational: change to state stopped

Baud rates

CAN layer 2 access


CAN Frame type for CANopen

10 kBits/s,

20 kBits/s,

50 kBits/s,

100 kBits/s,

125 kBits/s,

250 kBits/s,

500 kBits/s,

800 kBits/s,

1 MBits/s

Auto baudrate detection is supported

Send/receive via API supported (11 bit/29 bit)

CAN Frames

11 Bit


Table 129: Technical Data CANopen Slave Protocol



Technical Data

10.2.18 DeviceNet Master

Parameter

Maximum number of DeviceNet slaves





Maximum Configuration data


Description

63

3584 bytes

3584 bytes

255 bytes/connection

255 bytes/connection

1000 bytes/slave

Explicit connection

All service codes are supported

Change of State

Cyclic

Poll

Explicit Peer-to-Peer Messaging

Fragmentation Explicit and I/O

UCMM Supported

Objects Identity Object (Class Code 0x01)

Message Router Object (Class Code 0x02)

DeviceNet Object (Class Code 0x03)

Baud rates


Connection Object (Class Code 0x05)

Acknowledge Handler Object (Class Code 0x06)

125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames


Table 130: Technical Data DeviceNet Master Protocol

142/171



Technical Data

10.2.19 DeviceNet Slave

Parameter

Description




255 bytes

255 bytes

Get_Attribute_Single/All

Max. 240 bytes per request

Set_Attribute_Single/All

Max. 240 bytes per request

Connections Poll

Explicit messaging

Change-of-state

Cyclic

Bit-strobe

Supported

Fragmentation Explicit and I/O

Baud rates



125 kBits/s,

250 kBit/s,

500 kBit/s

Auto baudrate detection is not supported

CAN frames

V2.3.x.x

Table 131: Technical Data DeviceNet Slave Protocol

143/171



Technical Data

10.2.20 CC Link Slave

Parameter Description

Firmware works according to CC-Link Version 2.0:

Station Types

Maximum input data

Maximum output data

Remote Device Station (up to 4 occupied stations)

368 bytes

368 bytes

Input data remote device station

Output data remote device station

Extension cycles

Baud rates

112 bytes (RY) and 256 bytes (RWw)

112 bytes (RX) and 256 bytes (RWr)

1, 2, 4, 8


Limitation Intelligent Device Station not supported

Firmware works according to CC-Link Version 1.11:

Station Types Remote I/O station,

Remote device station’ (up to 4 occupied stations)

Maximum input data

Maximum output data

48 bytes

48 bytes

Input data remote I/O station

Output data remote I/O station

Input data remote device station

Output data remote device station

Baud rates

Firmware


4 bytes (RY)

4 bytes (RX)

4 bytes (RY) and 8 bytes (RWw) per occupied station

4 bytes (RX) and 8 bytes (RWr) per occupied station


V2.9.x.x

Table 132: Technical Data CC-Link-Slave Protocol

144/171



Annex 145/171

11 Annex

11.1 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 38: Example Barcode Label (EAN 39)



Annex 146/171

11.2 Tolerances of the shown Card Dimensions

The manufacturing tolerance of the printed circuit boards of the PC card cifX is ± 0.1 mm per milled PCB edge. For all dimensions of the PCB indicated on the drawings (in the section

Dimensioning PC Cards cifX PC-

104

from page 147) thus results for the length L and the width W, a tolerance of ± 0.1 mm (per milled edge) x 2 = ± 0.2 mm.

W

= [

width of the board in mm

] ± 0.2 mm

L

= [

length of the board in mm

] ± 0.2 mm

The depth T of the PCB depends on the highest part used or the circuit board plus the descenders. The thickness of the PCB is = 1.6 mm ± 10%.

Note:

The dimensions (L x W x D) specified in section

Technical Data PC

Cards cifX

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



Annex

11.3 Dimensioning PC Cards cifX PC-104

81.26

30.71

7.63

2.46

LP1 V4 V3 V1

L0915012 CIFX104-RE

Hilscher made in Germany

3 1

X51

CH 0

X6

CH 1

C62

R64

R65

C63

C60

R62

C61

C110

R112

R111

N110

P4

R110

P11

R19

C4

C111

N1

L110

D4

R102

P12

R101

R100

P13

R67

R8

C11

C153

P3

C132

C2

C3

R17

D3

C100

N100

J9

C1

L100

C101

C9

J9

G1

C8 C6

CH 1

CH 0

D2

2.62

S3

X5

S2

X1

B1

A1

N5

D5

R20

R18

C205

L200

C204

R206

C207

L201

R21

C206

C134

R92

C114

ADR

R9

R6

R93

14 15 16 17 18

J7

R7

19

D0

J8

R4

3

C10

C151

4

R5

5 6

AOI

C133

C130

7 9

C7

C5

10 11 12 14 15

IRQ

X2

C0

D0

5.08

90.17

Figure 39: Dimensions CIFX 104-RE

C19

D19

ø

3.5

0

B32

A32

5.08

147/171



Annex 148/171

81.26

30.71

7.63

V1

L0915012 CIFX104-RE

Hilscher made in Germany

3 1

X51

R17

C110

R112

R111

P4

R110

P11

R19

C111

N110

L110

D4

C4

N1

R102

P12

R101

R100

P13

D3

C100

N100

J9

L100

C101

C9

J9

R8

C11

C153

P3

C132

C2

C3

G1

C8 C6

C1

D2

N5

X3

D5

R20

R18

C205

L200

C204

R206

C207

L201

R21

C206

C134

R92

ADR

R9 R6

R93

14 15 16 17 18

C114

J7

R7

19

D0

J8

R4

3

C10

C151

4

R5

5 6

AOI

7

C133

C130

9

C7

C5

10 11 12 14 15

IRQ

X1

B1

A1

X2

C0

D0

5.08

90.17

Figure 40: Dimensions CIFX 104-RE\F

C19

D19

ø3

.5

0

B32

A32

5.08



Annex

81.28

7.63

LP1

V3 V1

R400

R405

R404

R403

C401

CIFX104-DN

Hilscher

ø3

.5

0

8.82

2.65

2.60

S3

S2

X400B

X5

U410

C405

C404

R370

C370

C4

GND

R413

P13

P4

L400

C400

C403

U401

L401

P3

R112

C110

N110

C11

C131

C135

P10

R111

P11

R110

R26

C111

C153 C132

L110

N1

R102

P12

R101

R100

C2

G1

C100

C1

N100

L100

C101

C8

R114

C6

J9

R5

D2

D4

C150

C154

C3

D3

C152

R1 R25

R367

D5

C134

C9

C44

N5

R17

ADR

R8

R9

R6

14 15 16 17 18

R7

19

D0

R4

3

C10

4

R15

5

C151

6 7 9

AOI

C133

C130

C7 C5

10 11 12 14 15

IRQ

X7 J8

L0913012

B1

A1

X1

C0

D0

X2

C19

D19

5.08

90.17

Figure 41: Dimensions CIFX 104-DP

B32

A32

5.08

149/171



Annex

81.28

7.64

LP1

V3

V1

C362

R406

R364

R363

C367

060L

HCPL

N360

CIFX104-DN

Hilscher

8.82

2.65

2.60

S3

S2

X400B

X5

V361

U410

C405

C404

C4

GND

R413

P13

P4

L400

C360 R361

C403

U401

L401

R360

C110

P3

R112

N110

C11

C131

C135

P10

R111

P11

R110

R26 C153

C111

C132

L110

N1

R102

P12

R101

R100

C2

G1

C100

C1

N100

L100

C101

C8

R114

C6

J9

R5

D2

D4

C150

C154

C3

D3

R1 R25

R367

D5

C134

C9

C44

N5

R17

ADR

R8

R9

R6

14 15 16 17 18

R7

19

D0

C152

R4

3

C10

4

R15

5

C151

6 7 9

AOI

C133

C130

C7 C5

10 11 12 14 15

IRQ

X7 J8

L0913012

B1

A1

X1

C0

D0

X2

C19

D19

5.08

90.17

Figure 42: Dimensions CIFX 104-CO

ø

3.5

0

B32

A32

5.08

150/171



Annex 151/171

81.25

7.62

2.52

2.60

S3

S2

LP1

B1

A1

X1

X5

R363

N360

R364

V3 V1

C362

C367

C361

R365

R366

060L

HCPL

U362

C363

R371

V361

R369

C405

U410

C404

C371

R370

C370

C4

GND

R413

P13

P4

L400

C360

C403

R361

R360

C400

L401

U401

R362

N362

C110

P3 R112

N110

P10

R111

P11

R110

L110

C111

C11

C131

C135

R26 C153 C132

N1

R102

P12

R101

R100

C2

G1

C100

C1

N100

L100

C101

CIFX104-DN

CIFX104-DP

Hilscher

C8

R114

C6

J9

R5

D2

D4

C150

C154

C3

D3

C152

R1 R25

R367

D5

C134

C9

C44

N5

R17

ADR

R8

R9

R6

14 15 16 17 18

R7

19

D0

R4

3

C10

4

R15

5

C151

6 7 9

AOI

C133

C130

C7 C5

10 11 12 14 15

IRQ

X7 J8

L0913012

C0

D0

X2

C19

D19

5.08

90.17

Figure 43: Dimensions CIFX 104-DN

ø3

.5

0

B32

A32

5.08



Annex 152/171

81.28

7.63

CIFX104-DN

Hilscher

V1

ø3

.5

0

X4

D4

C4

GND N1

P13

P4

C110

P3 R112

N110

C11

C131

C135

R26

P10

R111

P11

R110

C153

C111

C132

L110

R102

P12

R101

R100

C2

G1

C100

C1

N100

L100

C101

C8

R114

C6

J9

R5

D2

C150

C154

X3

C3

D3

C152

R1 R25

R367

D5

C134

C9

C44

N5

R17

ADR

R8

R9

R6

14 15 16 17 18

R7

19

D0

R4

3

C10

4

R15

5

C151

6 7 9

AOI

C133

C130

C7 C5

10 11 12 14 15

IRQ

X7 J8

L0913012

B1

A1

X1

C0

D0

X2

5.08

90.17

Figure 44: Dimensions CIFX 104-FB\F

C19

D19

B32

A32

5.08



Annex

11.4 Dimensioning AIFX Assembly Interfaces

11.4.1 Ethernet - AIFX-RE

31.12 (+0.06/-0.0)

M2.5

Leiterkarte/ PCB

10.0

2.5

17.5

COM0

7.4

COM1

39.8

flexibles

Folienkabel /

flexible flat cable

X1

X200

Kanal 1 /

Channel 1

(CH 1)

Kanal 0 /

Channel 0

(CH 0)

L0621111

30.7

Figure 45: Dimensioning Ethernet Assembly Interface (AIFX-RE)

11.4.2 PROFIBUS - AIFX-DP

25

Leiterkarte/ PCB

13

ERR STA

13

153/171

X1 flexibles

Folienkabel /


17

17.4

23.4

Figure 46: Dimensioning PROFIBUS Assembly Interface (AIFX-DP)



Annex

11.4.3 CANopen - AIFX-CO

25

Leiterkarte/ PCB

13

ERR RUN

13 flexibles

Folienkabel /


17

17.4

23.4

Figure 47: Dimensioning CANopen Assembly Interface (AIFX-CO)

11.4.4 DeviceNet - AIFX-DN

18.90

M2,5

Leiterkarte/ PCB

3.00

3.00

13

MNS

154/171 flexibles

Folienkabel /


X360

X1

23.7

26.7

Figure 48: Dimensioning DeviceNet Assembly Interface (AIFX-DN)



Annex

11.4.5 CC-Link - AIFX-CC

18.90

155/171

M2,5

Leiterkarte/ PCB

3.00

3.00

13

L-ERR L-RUN

13

X360 flexibles

Folienkabel /


X1

AIFX-CC L1404001

43.2

45.4

Figure 49: Dimensioning CC-Link Assembly Interface (AIFX-CC)

11.4.6 Diagnose - AIFX-DIAG

5

6

7

8

3 2 1 0 F

9 A

B

E

CD

5

3

6

78

9

A

B

C

1 2

F0

Mini-

USB

Leiterkarte

PCB

M2.5

10.00

2.80

7.94

12.97

20.70

10.20

42,2

49.90

flexibles

Folienkabel /


X1

AIFX-DIAG

20.5

23.2

Figure 50: Dimensioning Diagnostic Assembly Interface (AIFX-DIAG)



Annex 156/171

11.5 Notes on earlier Hardeware Revisions

11.5.1 Failure in 10 MBit/s Half Duplex Mode and Workaround

The note is only valid for the PC cards cifX up to serial numbers indicated:

PC Cars cifX

CIFX 104-RE\F

Part No up to Serial Number

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 157/171

11.6 Disposal of Waste Electronic Equipment

According to the European Directive 2002/96/EG “Waste Electrical and

Electronic Equipment (WEEE)”, waste electronic equipment may not be disposed of as household waste. As a consumer, you are legally obliged to dispose of all waste electronic equipment according to national and local regulations.

Waste Electronic Equipment

This product must not be treated as household waste.

This product must be disposed of at a designated waste electronic equipment collecting point.

11.7 References

[1] THE CIP NETWORKS LIBRARY, Volume 6, CompoNet Adaptation of CIP,

Edition 1.4 November 2008

[2] Data sheet MOD JACK – MJIM: https://www.erni-x-press.com/de/downloads/zeichnungen/203313.pdf

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

[3] Design - Specification for VARAN Rev. 0.76, section 5.1.4 VARAN Splitter

References Protocol API Manuals

CANopen Master Protocol API Manual, Revision 14, Hilscher GmbH 2013

CANopen Slave Protocol API Manual (V3), Revision 5, Hilscher GmbH 2013

DeviceNet Master Protocol API Manual, Revision 10, Hilscher GmbH 2013

DeviceNet Slave Protocol API Manual, Revision 13, Hilscher GmbH 2013

EtherCAT Master Protocol API Manual (V3), Revision 5, Hilscher GmbH 2013

EtherCAT Slave Protocol API Manual, Revision 3 (V4), Hilscher GmbH 2013

EtherCAT Slave Protocol API Manual, Revision 21 (V2), Hilscher GmbH 2013

EtherNetIP Scanner Protocol API Manual, Revision 13, Hilscher GmbH 2013

EtherNetIP Adapter Protocol API Manual, Revision 12, Hilscher GmbH 2013

Open Modbus/TCP Protocol API Manual, Revision 8, Hilscher GmbH 2013

POWERLINK Controlled Node/Slave Protocol API Manual, Revision 12, Hilscher GmbH 2013

PROFIBUS DP Master Protocol API Manual, Revision 18, Hilscher GmbH 2013

PROFIBUS DP Slave Protocol API Manual, Revision 15, Hilscher GmbH 2013

PROFIBUS MPI Protocol API Manual, Revision 4, Hilscher GmbH 2011

PROFINET IO-Controller Protocol API Manual, Revision 18, Hilscher GmbH 2013

PROFINET IO-Device Protocol API Manual (V3.4), Revision 13, Hilscher GmbH 2013

PROFINET IO-Device Protocol API Manual (V3.5), Revision 6, Hilscher GmbH 2013 sercos Master Protocol API Manual, Revision 11, Hilscher GmbH 2013 sercos Slave Protocol API Manual (V3), Revision 12, Hilscher GmbH 2013

VARAN Client Protocol API Manual, Revision 3, Hilscher GmbH 2013

Table 133: References Protocol API Manuals

References referring to the safety issues are listed separately in section

References Safety

on page 25.

References referring to the Standard Bus Specifications for PC/104 are listed separately

Reference PC/104 Specification

on page 103.



Annex 158/171

11.8 EtherCAT Summary over Vendor ID, Conformance test,

Membership and Network Logo

The communication interface product is shipped with Hilscher’s secondary vendor ID, which has to be replaced by the Vendor ID of the company shipping end products with the integrated communication interface. End Users or Integrators may use the communication interface product without further modification if they re-distribute the interface product (e.g.

PCI Interface card products) only as part of a machine or machine line or as spare part for such a machine. In case of questions, contact Hilscher and/or your nearest ETG representative. The ETG Vendor-ID policies apply.

11.8.2 Conformance

EtherCAT Devices have to conform to the EtherCAT specifications. The EtherCAT

Conformance Test Policies apply, which can be obtained from the EtherCAT Technology

Group (ETG, www.ethercat.org

).

Hilscher range of embedded network interface products are conformance tested for network compliance. This simplifies conformance testing of the end product and can be used as a reference for the end product as a statement of network conformance (when used with standard operational settings). It must however be clearly stated in the product documentation that this applies to the network interface and not to the complete product.

Conformance Certificates can be obtained by passing the conformance test in an official

EtherCAT Conformance Test lab. Conformance Certificates are not mandatory, but may be required by the end user.

11.8.3 Certified Product vs. Certified Network Interface

The EtherCAT implementation may in certain cases allow one to modify the behavior of the

EtherCAT network interface device in ways which are not in line with EtherCAT conformance requirements. For example, certain communication parameters are set by a software stack, in which case the actual software implementation in the device application determines whether or not the network interface can pass the EtherCAT conformance test.

In such cases, conformance test of the end product must be passed to ensure that the implementation does not affect network compliance.

Generally, implementations of this kind require in-depth knowledge in the operating fundamentals of EtherCAT. To find out whether or not a certain type of implementation can pass conformance testing and requires such testing, contact EtherCAT Technology Group

(“ETG”, www.ethercat.org

) and/or your nearest EtherCAT conformance test centre.

EtherCAT may allow the combination of an untested end product with a conformant network interface. Although this may in some cases make it possible to sell the end product without having to perform network conformance tests, this approach is generally not endorsed by

Hilscher. In case of questions, contact Hilscher and/or your nearest ETG representative.

11.8.4 Membership and Network Logo

Generally, membership in the network organization and a valid Vendor-ID are prerequisites in order to be able to test the end product for conformance. This also applies to the use of the EtherCAT name and logo, which is covered by the ETG marking rules.

Vendor ID Policy accepted by ETG Board of Directors, November 5, 2008



Annex 159/171

11.9 List of Figures

Figure 1: System Overview cifX to update Firmware, Driver and Software

Figure 2: CIFX 104-RE*

Figure 3: CIFX 104-RE-R*

Figure 4: Basic Card for CIFX 104-RE\F

Figure 5: Basic Card for CIFX 104-RE-R\F

Figure 6: CIFX 104-DP

Figure 7: CIFX 104-DP-R

Figure 8: CIFX 104-CO

Figure 9: CIFX 104-CO-R

Figure 10: CIFX 104-DN

Figure 11: CIFX 104-DN-R

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

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

Figure 14: Reverse Side CIFX 104-XX (all Basic Cards and Variants)

49

49

50

Figure 15: Ethernet Assembly Interface (AIFX-RE)*

Figure 16: Front Side and LED Display Ethernet Assembly Interface (AIFX-RE)

Figure 17: PROFIBUS Assembly Interface (AIFX-DP)

Figure 18: Front Side and LED Display PROFIBUS Assembly Interface (AIFX-DP)

Figure 19: CANopen Assembly Interface (AIFX-CO)

Figure 20: Front Side and LED Display Assembly Interface (AIFX-CO)

Figure 21: DeviceNet Assembly Interface (AIFX-DN)

Figure 22: Front Side and LED Display DeviceNet Assembly Interface (AIFX-DN)

53

53

54

54

51

51

52

52

Figure 23: CC-Link Assembly Interface (AIFX-CC)

Figure 24: Reverse Side CC-Link Assembly Interface (AIFX-CC) with Matrix Label

Figure 25: Front Side and LED Display CC-Link Assembly Interface (AIFX-CC)

Figure 26: Diagnostic Assembly Interface (AIFX-DIAG)

Figure 27: Front Side, LED Display and Reverse Side Diagnostic Assembly Interface (AIFX-DIAG)

55

55

55

56

56

Figure 28: Connecting the Ethernet Assembly Interface (AIFX-RE) to the Basic Card CIFX 104-RE\F

(Example) 62

38

39

40

41

42

43

44

45

46

47

48

Figure 29: Connecting the CANopen Assembly Interface (AIFX-CO) to the Basic Card 104-FB-R\F (Example)

62

Figure 30: Connecting the Diagnostic Assembly Interface (AIFX-DIAG) to the Basic Card CIFX 104-FB-R\F

(Example) 63

Figure 31: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX 95

Figure 32: PROFIBUS Interface (DSub female connector, 9 pin), X400

Figure 33: CANopen Interface (DSub male connector, 9 pin), X400

Figure 34: DeviceNet Interface (CombiCon male Connector, 5 pin), X360

Figure 35: CC-Link Interface (CombiCon male Connector, 5 pin)

Figure 36: Mini-B USB Connector (5 Pin)

Figure 37: 1x20 Pins for CIFX 104-RE\F, CIFX 104-RE-R\F

Figure 38: Example Barcode Label (EAN 39)

Figure 39: Dimensions CIFX 104-RE

99

100

145

147

97

97

98

98

Figure 40: Dimensions CIFX 104-RE\F

Figure 41: Dimensions CIFX 104-DP

Figure 42: Dimensions CIFX 104-CO

Figure 43: Dimensions CIFX 104-DN

Figure 44: Dimensions CIFX 104-FB\F

Figure 45: Dimensioning Ethernet Assembly Interface (AIFX-RE)

Figure 46: Dimensioning PROFIBUS Assembly Interface (AIFX-DP)

Figure 47: Dimensioning CANopen Assembly Interface (AIFX-CO)

148

149

150

151

152

153

153

154



Annex

Figure 48: Dimensioning DeviceNet Assembly Interface (AIFX-DN)

Figure 49: Dimensioning CC-Link Assembly Interface (AIFX-CC)

Figure 50: Dimensioning Diagnostic Assembly Interface (AIFX-DIAG)

160/171

154

155

155

11.10 List of Tables

Table 1: List of Revisions

Table 2: Reference on Hardware PC Cards cifX, AIFX Assembly Interfaces

9

10

Table 3: Reference on Driver and Software

Table 4: Reference on Firmware

10

11

Table 5: PROFINET IO-Device Firmware Version 3.4 and 3.5, Header, GSDML and Protocol API Manual 14

Table 6: EtherCAT-Slave Firmware Version 2.5 and 4.2, Header, XML and Protocol API Manual 15

Table 7: Device Description Files for PC Cards cifX

Table 8: PC Cards cifX and the Real-Time Ethernet or Fieldbus Systems realized thereby

Table 9: PC Cards cifX with AIFX Assembly Interface

Table 10: Signal Words and Safety Signs in Safety Messages on Personal Injury

Table 11: Signal Words and Safety Signs in Safety Messages on Property Damage

Table 12: PC Cards PC/104: CIFX 104-XX and CIFX 104-XX-R

Table 13: PC Cards PC/104: CIFX 104-XX\F, CIFX 104-XX-R\F

Table 14: AIFX Assembly Interfaces for PC Cards cifX with Cable Connector

Table 15: Slot for the PC Cards cifX PC/104

Table 16: Requirements Power Supply and Host Interface for PC Cards cifX PC/104

Table 17: Panel Cutout at the at the front plate of the PC cabinet

Table 18: Required Panel Cutout and Holes for AIFX

Table 19: Requirements to operate PC Cards cifX properly

29

29

29

30

31

25

27

28

28

16

21

21

25

Table 20: Steps for the Software and Hardware Installation, the Configuration and for the Diagnosis of a PC

Card cifX PC/104 (Master and Slave) 35

Table 21: Notes for the Configuration of the Master Device 37

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

Table 23: Starting Address and Interrupt for 16 KByte Dual-Port Memory

Table 24: Overview LEDs Real-Time Ethernet Systems

Table 25: LED Names

Table 26: Overview LEDs by Fieldbus System for 1 Channel Devices

Table 27: LED Names

Table 28: System Status LED States

Table 29: System Status LED State Definitions

67

67

68

68

37

59

66

66

Table 30: Power On LED States

Table 31: Power On LED state definitions

Table 32: LED states for the EtherCAT Master protocol

Table 33: LED state definitions for the EtherCAT Master protocol

Table 34: LED states for the EtherCAT Slave protocol

Table 35: LED state definitions for the EtherCAT Slave protocol

Table 36: LED states for the EtherNet/IP Scanner protocol

Table 37: LED state definitions for the EtherNet/IP Scanner protocol

Table 38: LED states for the EtherNet/IP Adapter protocol

Table 39: LED state definitions for the EtherNet/IP Adapter protocol

Table 40: LED states for the OpenModbusTCP protocol

Table 41: LED state definitions for the OpenModbusTCP protocol

Table 42: LED states for the POWERLINK Controlled Node protocol

Table 43: LED state definitions for the POWERLINK Controlled Node protocol

Table 44: LED states for the PROFINET IO-Controller protocol

Table 45: LED state definitions for the PROFINET IO-Controller protocol

74

74

75

75

72

72

73

73

70

70

71

71

68

68

69

69



Annex 161/171

Table 46: LED states for the PROFINET IO-Device protocol

Table 47: LED state definitions for the PROFINET IO-Device protocol

Table 48: LED states for the sercos Master protocol

Table 49: LED state definitions for the sercos Master protocol

Table 50: LED state definitions for the sercos Slave protocol

Table 51: LED state definitions for the sercos Slave protocol

Table 52: LED-Zustände für das VARAN-Client-Protokoll

Table 53: Definitionen der LED-Zustände für das VARAN-Client-Protokoll

Table 54: LED states for the PROFIBUS DP Master protocol – 1 Communication Status LED (current

Hardware Revision)

Table 55: LED state definitions for the PROFIBUS DP Master protocol

Table 56: LED states for the PROFIBUS DP Master protocol – 2 Communication Status LEDs (AIFX-DP connected or prior Hardware Revision)

Table 57: LED state definitions for the PROFIBUS DP Master protocol

82

82

83

83

Table 58: LED states for the PROFIBUS DP Slave protocol – 1 Communication Status LED (current

Hardware Revision)

Table 59: LED state definitions for the PROFIBUS DP Slave protocol

84

84

Table 60: LED states for the PROFIBUS DP Slave protocol – 2 Communication Status LEDs (AIFX-DP connected or prior Hardware Revision)

Table 61: LED state definitions for the PROFIBUS DP Slave protocol

Table 62: LED states for the PROFIBUS MPI protocol – 1 Communication Status LED

Table 63: LED state definitions for the PROFIBUS MPI protocol

Table 64: LED states for the PROFIBUS MPI protocol – 2 Communication Status LEDs (AIFX-DP connected)

Table 65: LED state definitions for the PROFIBUS MPI protocol

87

87

Table 66: LED states for the CANopen Master protocol – 1 Communication Status LED (current Hardware

Revision) 88

Table 67: LED state definitions for the CANopen Master protocol 88

Table 68: LED states for the CANopen Master protocol – – 2 Communication Status LEDs (AIFX-CO connected or prior Hardware Revision)

Table 69: LED state definitions for the CANopen Master protocol

89

89

Table 70: States of the CAN LED for the CANopen Slave protocol – 1 Communication Status LED (current

Hardware Revision)

Table 71: LED state definitions for the CANopen Slave protocol

90

90

Table 72: States of the CAN LED for the CANopen Slave protocol – 2 Communication Status LEDs (AIFX-

CO connected or prior Hardware Revision)

Table 73: LED state definitions for the CANopen Slave protocol

Table 74: LED states for the DeviceNet Master protocol

Table 75: LED state definitions for the DeviceNet Master protocol

Table 76: LED states for the DeviceNet Slave protocol

Table 77: LED state definitions for the DeviceNet Slave protocol

Table 78: LED states for the CC-Link Slave protocol

Table 79: LED state definitions for the CC-Link Slave protocol

Table 80: Ethernet Pin Assignment at the RJ45 Socket for cifX or AIFX

Table 81: Ethernet Connection Data

Table 82: Use of Hubs and Switches

Table 83: PROFIBUS Interface, X400

Table 84: CANopen Interface, X400

Table 85: DeviceNet Interface, X360

Table 86: CC-Link Interface

Table 87: Pin Assignment Mini-B USB Connector

Table 88: Pin Assignment for Cable Connector Ethernet X4 or X304

Table 89: Pin Assignment for Cable connector Fieldbus X3, X304 or X4

Table 90: Pin Assignment for Cable connector DIAG X3 or X303

Table 91: Pin Assignment for SYNC Connector, X51

100

101

101

102

97

98

98

99

95

96

96

97

93

93

94

94

91

91

92

92

85

85

86

86

76

76

77

78

79

80

81

81



Annex

Table 92: SYNC Connector: SYNC Signal, Connector, Max. Cable Length

Table 93: Meaning of the SYNC Signals for each Protocol

Table 94: Pin Assignment at the PC/104 Bus

Table 95: Reference PC/104 Specification

Table 96: Pin Assignment for PC/104-Bus, X1 (Control Signals used on the 8 Bit Connector)

Table 97: Pin Assignment for PC/104-Bus, X2 (Used Control Signals on the Expansion Connector)

Table 98: Technical Data CIFX 104-RE, CIFX 104-RE-R

Table 99: Technical Data CIFX 104-RE\F, CIFX 104-RE-R\F

Table 100: Technical Data CIFX 104-DP, CIFX 104-DP-R

Table 101: Technical Data CIFX 104-DP\F, CIFX 104-DP-R\F

Table 102: Technical Data CIFX 104-CO, CIFX 104-CO-R

Table 103: Technical Data CIFX 104-CO\F, CIFX 104-CO-R\F

Table 104: Technical Data CIFX 104-DN, CIFX 104-DN-R

Table 105: Technical Data CIFX104C-DN\F, CIFX 104-DN-R\F

Table 106: Technical Data CIFX104C-CC\F

Table 107: Technical Data AIFX-RE

Table 108: Technical Data AIFX-DP

Table 109: Technical Data AIFX-CO

Table 110: Technical Data AIFX-DN

Table 111: Technical Data AIFX-CC

Table 112: Technical Data AIFX-DIAG

Table 113: Technical Data EtherCAT Master Protocol

Table 114: Technical Data EtherCAT Slave Protocol

Table 115: Technical Data EtherNet/IP Scanner (Master) Protocol

Table 116: Technical Data EtherNet/IP Adapter (Slave) Protocol

Table 117: Technical Data Open Modbus/TCP Protocol

Table 118: Technical Data POWERLINK Controlled Node (Slave) Protocol

Table 119: Technical Data PROFINET IO RT Controller

Table 120: Technical Data PROFINET IO RT IRT Device Protocol

Table 121: Technical Data PROFINET IO RT IRT Device Protocol

Table 122: Technical Data sercos Master Protocol

Table 123: Technical Data sercos Slave Protocol

Table 124: Technical Data VARAN Client Protocol

Table 125: Technical Data PROFIBUS DP Master Protocol

Table 126: Technical Data PROFIBUS DP Slave Protocol

Table 127: Technical Data PROFIBUS-MPI Protocol

Table 128: Technical Data CANopen Master Protocol

Table 129: Technical Data CANopen Slave Protocol

Table 130: Technical Data DeviceNet Master Protocol

Table 131: Technical Data DeviceNet Slave Protocol

Table 132: Technical Data CC-Link-Slave Protocol

Table 133: References Protocol API Manuals

162/171

128

129

130

130

132

132

133

134

120

121

122

123

124

125

126

127

109

111

112

114

115

117

118

120

102

102

103

103

104

105

107

135

136

137

138

139

140

141

142

143

144

157



Annex 163/171

11.11 Glossary

10-Base T

Standard for communication on Ethernet over twisted pair lines with RJ45 connectors and a Baud_rate of 10 MBit/s (according to the IEEE 802.3 specification).

100-Base TX

Standard for communication on Ethernet over unshielded twisted pair lines with RJ45 connectors and a baud rate of 100 MBit/s according to the IEEE

802. specification

AIFX

A

ssembly

I

nter

F

ace based on net

X

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.

Ch0, Ch1 …

CH0, CH1 (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.

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.



Annex

cifX

164/171

C

ommunication

I

nter

F

ace based on net

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

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.



Annex

Ethernet

165/171

EtherNet/IP


Rockwell. It partly uses the CIP (Common Industrial Protocol).

Ethernet POWERLINK


B&R. It partly uses CANopen technologies.

FDL

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.

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. The firmware is stored remanently in the flash memory circuit of the device. It can be updated by a firmware download.

Full duplex

Full duplex denominates a telecommunication system between two communication partners which allows simultaneous communication in both directions is called a full-duplex telecommunication system. At such a system, it will be possible to transmit data even if currently data are received. Full-duplex is the opposite of Half_duplex.

Function code

A function code (FC) is a standardized method to access, i. e. read or write on coils (Bits) or registers via Modbus.

Modbus function codes are elements of Modbus request/reply telegrams.

GSD

Generic Station Description, Device description file

GSD file

A special kind of Device Description File used by PROFIBUS (GSD =

Generic Station Description).

GSDML

Generic Station Description Markup Language

XML based device description file.

GSDML file

A special kind of XML-based Device Description File used by PROFINET.



Annex

Half duplex

166/171

Half duplex denominates a telecommunication system between two communication partners which does not allow simultaneous, but alternating, communication in both directions is called a half-duplex telecommunication system. At such a system, receiving data inhibits the transmission of data. Half-duplex is the opposite of _Full_duplex.

Hub

A network component connecting multiple communication partners with each other. A hub does not provide own intelligence, thus it does not analyze the data traffic and sends received data to all connected communication partners. A hub can be used for setting up a star topology.

Industrial Ethernet

See Real-Time Ethernet

IP

Internet Protocol.

IP belongs to the TCP/IP family of protocols and is defined in RFC791. It is based on layer 3 of the ISO/OSI 7 layer model of networking.

It is a connectionless protocol, i.e. you do not need to open a connection to a computer before sending an IP data packet to it. Therefore IP is not able to guarantee that the IP data packets really arrive at the recipient. On IP level neither the correctness of data nor the consistence and completeness are checked.

IP defines special addressing mechanisms, see IP Address.

IP Address

Address within IP (the Internet Protocol, part of TCP/IP).

An IP address is an address identifying a device or a computer within a network using the IP protocol. IP addresses are defined as a 32 bit number.

Usually, for ease of notation the IP address is divided into four 8 bit numbers which are represented in decimal notation and separated by points: a.b.c.d where a.b.c.d are each integer values between 0 and 255.

Example: 192.168.30.15

However, not all combinations are allowed, some are reserved for special purposes.

The IP address 0.0.0.0 is defined as invalid.

MAC-ID

MAC = Media Access Control

Definition for Ethernet:

A MAC-ID is on delivery a unique (physical) Ethernet address of the device.

MAC-IDs are defined as a 48 bit number. Usually, for ease of notation the

MAC-ID address is divided into six 8 bit numbers which are represented in hexadecimal notation and separated by “minus”-signs (-):



Annex 167/171

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.

Modbus Data Model

MPI netX

networX on chip, Hilscher network communication controllers


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

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.

An object dictionary is a storage area for device parameter data structures.

It is accessed in standardized manner.

Open Modbus/TCP

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.

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.



Annex

PCB

168/171

Printed Circuit Board, (printed = machine-made) circuit board

PC Card cifX

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

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

EtherNet/IP

Open-Modbus/TCP

POWERLINK

PROFIBUS DP

PROFIBUS MPI

CANopen

DeviceNet

PROFINET IO

sercos

CC-Link

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

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



Annex


169/171

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

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



Annex

TCP/IP

170/171

Transport Control Protocol/Internet Protocol connection-orientated, secure transfer protocol as basis for the Internet-protocols

UCMM

Unconnected Message Manager

VARAN

V

ersatile

A

utomation

R

andom

A

ccess

N

etwork

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

X1, X2, X3, X4 …

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

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 XMLbased formats for storing the device-related data appropriately.



Annex

11.12 Contacts

Headquarters

Germany

Hilscher Gesellschaft für

Systemautomation mbH

Rheinstrasse 15

65795 Hattersheim

Phone: +49 (0) 6190 9907-0

Fax: +49 (0) 6190 9907-50

E-Mail: [email protected]

Support

Phone: +49 (0) 6190 9907-99


Subsidiaries

China

Hilscher Systemautomation (Shanghai) Co. Ltd.

200010 Shanghai

Phone: +86 (0) 21-6355-5161


Support

Phone: +86 (0) 21-6355-5161


France

Hilscher France S.a.r.l.

69500 Bron

Phone: +33 (0) 4 72 37 98 40


Support

Phone: +33 (0) 4 72 37 98 40


India

Hilscher India Pvt. Ltd.

New Delhi - 110 065

Phone: +91 11 26915430


Italy

Hilscher Italia S.r.l.

20090 Vimodrone (MI)

Phone: +39 02 25007068


Support

Phone: +39 02 25007068


Japan

Hilscher Japan KK

Tokyo, 160-0022

Phone: +81 (0) 3-5362-0521


Support

Phone: +81 (0) 3-5362-0521


Korea

Hilscher Korea Inc.

Seongnam, Gyeonggi, 463-400

Phone: +82 (0) 31-789-3715


Switzerland

Hilscher Swiss GmbH

4500 Solothurn

Phone: +41 (0) 32 623 6633


Support

Phone: +49 (0) 6190 9907-99


USA

Hilscher North America, Inc.

Lisle, IL 60532

Phone: +1 630-505-5301


Support

Phone: +1 630-505-5301


171/171



PC Cards CIFX 104

PC Cards cifX PC/104 (CIFX 104)

Table of Contents

1 Introduction

1.1 About the User Manual

1.2 Contents of the Product DVD

1.4 Licenses

2 Safety

2.4 Safety Instructions to avoid Personal Injury

2.5 Safety Instructions to avoid Property Damage

2.6 Labeling of Safety Messages

3.1 Description

3.2 PC Cards cifX with integrated Interfaces

3.3 PC Cards cifX with AIFX Assembly Interfaces

3.5 Requirements for Operation of the PC Cards cifX

4.1 Installation and Configuration PC Card cifX PC/104

4.2 Note on Exchange Service (Replacement Case)

4.3 Notes for the Configuration of the Master Device

4.4 Device Names in SYCON.net

4.5 Update for Firmware, Driver and Software

5.1 PC-Karten cifX PC/104

6 Hardware Installation and Uninstalling

6.1 Safety Messages on Personal Injury

6.2 Property Damage Messages

6.3 cifX PC/104: Set Starting Address and Interrupt

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

6.5 Uninstalling PC Cards cifX PC/104

7 Troubleshooting

7.1 Instructions for Problem Solving

8.1 Overview LEDs Real-Time Ethernet Systems

8.2 Overview LEDs Fieldbus Systems

8.7 EtherNet/IP Scanner (Master)

8.8 EtherNet/IP Adapter (Slave)

8.10 POWERLINK Controlled Node/Slave

8.11 PROFINET IO-Controller

8.12 PROFINET IO-Device

8.13 sercos Master

8.14 sercos Slave

8.15 VARAN Client (Slave)

8.16 PROFIBUS DP Master

8.17 PROFIBUS DP Slave

8.18 PROFIBUS MPI Device

8.19 CANopen Master

8.20 CANopen Slave

8.21 DeviceNet Master

8.22 DeviceNet Slave

8.23 CC-Link Slave

8.24 Slave

9 Device Connections and Switches

9.6 Mini-B USB Connector (5 Pin)

9.9 SYNC Connector (Pin-Assignment, Hardware/Firmware)

9.10 Pin Assignment at the PC/104 Bus

10 Technical Data

10.1 Technical Data PC Cards cifX

10.2 Technical Data of the Communication Protocols

11 Annex

11.1 Device Label with Barcode

11.2 Tolerances of the shown Card Dimensions

11.3 Dimensioning PC Cards cifX PC-104

11.4 Dimensioning AIFX Assembly Interfaces

11.5 Notes on earlier Hardeware Revisions

11.6 Disposal of Waste Electronic Equipment

11.7 References

11.8 EtherCAT Summary over Vendor ID, Conformance test,

Membership and Network Logo

11.9 List of Figures

11.10 List of Tables

11.11 Glossary

11.12 Contacts

Related manuals

hilscher

CIFX 104

CIFX 104-CO-R\F

hilscher

CIFX 104C

CIFX M223090AE-CO\F

CIFX 90E-2CO\DN\ET\F

CIFX M223090AE-RE\F

CIFX M223090AE-DP\F

CIFX 90E-2CO\DN\ET\F