CX1100-00xx: Hardware Documentation
CX1100-00xx: Hardware Documentation
CX1100-00xx: Hardware Documentation
CX1100-00xx
Embedded-PC
Version: 2.1
Date: 2015-08-19
Table of contents
Table of contents
1 Foreword .................................................................................................................................................... 5
1.1 Notes on the documentation............................................................................................................. 5
1.2 Safety instructions ............................................................................................................................ 6
1.3 Documentation Issue Status............................................................................................................. 6
2 Product overview....................................................................................................................................... 8
2.1 Appropriate Use................................................................................................................................ 8
2.2 System Overview.............................................................................................................................. 8
2.3 Architecture of the power supply units............................................................................................ 10
2.4 Adapter RAM Hardware address overview..................................................................................... 15
2.5 Display ............................................................................................................................................ 18
2.5.1 Display setup ...................................................................................................................... 18
2.5.2 Representing text on the display......................................................................................... 19
2.5.3 LC Display........................................................................................................................... 23
2.6 4 + 1 navigation switch ................................................................................................................... 24
2.6.1 Operating principle of the switch......................................................................................... 24
2.7 CX1100-0001.................................................................................................................................. 26
2.7.1 CX1100-0001 connections.................................................................................................. 26
2.7.2 Technical data CX1100-0001 ............................................................................................. 27
2.7.3 Architecture of power supply CX1100-0001 ....................................................................... 28
2.8 CX1100-0002 / CX1100-0012 ........................................................................................................ 29
2.8.1 CX1100-00x2 connections.................................................................................................. 29
2.8.2 Technical data CX1100-0002 ............................................................................................. 30
2.8.3 Technical data CX1100-0012 ............................................................................................. 31
2.8.4 Architecture of power supply CX1100-00x2........................................................................ 32
2.9 CX1100-0003 / CX1100-0013 ........................................................................................................ 36
2.9.1 CX1100-00x3 connections.................................................................................................. 36
2.9.2 Technical data CX1100-0003 ............................................................................................. 37
2.9.3 Technical data CX1100-0013 ............................................................................................. 38
2.9.4 Architecture of power supply CX1100-00x3........................................................................ 39
2.10 CX1100-0004 / CX1100-0014 ........................................................................................................ 43
2.10.1 CX1100-00x4 connections.................................................................................................. 43
2.10.2 Technical data CX1100-0004 ............................................................................................. 44
2.10.3 Technical data CX1100-0014 ............................................................................................. 45
2.10.4 Architecture of power supply CX1100-00x4........................................................................ 46
3 Transport.................................................................................................................................................. 47
3.1 Unpacking, installation and transport.............................................................................................. 47
6 Decommissioning.................................................................................................................................... 72
6.1 Removal and disposal .................................................................................................................... 72
7 Appendix .................................................................................................................................................. 75
7.1 ADS Return-Codes ......................................................................................................................... 75
7.2 Certifications ................................................................................................................................... 77
7.3 Support and Service ....................................................................................................................... 78
1 Foreword
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
For that reason the documentation is not in every case checked for consistency with performance data,
standards or other characteristics.
In the event that it contains technical or editorial errors, we retain the right to make alterations at any time
and without warning.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, Safety over EtherCAT®, TwinSAFE®, XFC®and XTS® are registered
trademarks of and licensed by Beckhoff Automation GmbH.
Other designations used in this publication may be trademarks whose use by third parties for their own
purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents:
EP1590927, EP1789857, DE102004044764, DE102007017835
with corresponding applications or registrations in various other countries.
The TwinCAT Technology is covered, including but not limited to the following patent applications and
patents:
EP0851348, US6167425 with corresponding applications or registrations in various other countries.
EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany
Copyright
© Beckhoff Automation GmbH & Co. KG, Germany.
The reproduction, distribution and utilization of this document as well as the communication of its contents to
others without express authorization are prohibited.
Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a
patent, utility model or design.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the
documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are
familiar with the applicable national standards.
Description of symbols
In this documentation the following symbols are used with an accompanying safety instruction or note. The
safety instructions must be read carefully and followed without fail!
Risk of injury!
Failure to follow the safety instructions associated with this symbol endangers the life and
health of persons.
WARNING
Personal injuries!
Failure to follow the safety instructions associated with this symbol can lead to injuries to
persons.
CAUTION
Tip or pointer
This symbol indicates information that contributes to better understanding.
Note
Version Changes
0.2 revised version
description of four power supplies
CX10xx architecture description
1.0 memory mapping / fieldbus connections
1.1 library for 4 + 1 navigation switch added
1.2 Blink codes for CX1100-0004 (EtherCAT) extended
1.3 Changes in GCB - Watchdog Error Counter
1.4 Display access via ADS added
1.5 Blink codes for IP-Link errors added
1.6 Notes on hardware revision added
1.7 Terminal bus diagnosis in PLC program added
1.8 Notes on terminal bus diagnosis with firmware > B7
added
1.9 Notes on wire installation added
2.0 Notes on new power supplies for CX1030 added
2.1 Revised version
2 Product overview
Local I/O signals are connected via the CX1100-0002 power supply variant, to which all Beckhoff Bus
Terminals can be connected, or via CX1100-0003, which in addition to the Bus Terminals enables the
connection of Extension Box IExxxx type Beckhoff Fieldbus Box modules. The option to connect Bus
Terminals or Fieldbus Box modules creates a control system with a very variable, expandable I/O level with
large signal variety. The I/O data are stored in a DPRAM, which is accessible by the CPU via the system
bus. The power supplies of the CX system can be changed in the field: If, for example, local I/O via Bus
Terminals is required, CX1100-0001 can be replaced with CX1100-0002 in the field. Local I/O signals are
connected via the CX1020 and the CX1100-0002 power supply variants (Bus Terminals), CX1100-0003 (Bus
Terminals
and Fieldbus Box modules via IP-Link) or CX1100-0004 for EtherCAT Terminals. With CX1100-0004 the I/O
data are stored directly in the main memory of the CPU; a DPRAM is no longer required. The CX1100-0004
power supply unit for EtherCAT Terminals can only be connected in conjunction with the basic CX1020/
CX1000/CX1010 CPU module.
For the CPU CX1030 a modified power supply unit is necessary. For this use the modules CX1100-001x .
The functions are similar to the modules CX1100-000x.
An overview about architecture with the common system components GCB, ACB, NOVRAM, display and
switch are described together in one chapter. Special interfaces are described in the power supply units
containing the interfaces.
All power supply feature, except for power supply, the following functions:
1. Display 2 x 16 characters
2. 4+1 navigation switch
3. Non Volatile RAM
These functions are managed by the control program via the PC104 bus. The structure of the CX1100-0001
is shown in the following figure:
The CPU of the main module controls the whole architecture. With memory mapped I/O regions data can be
exchanged. The data needed to run the system is combined in the "General Control Block" (GCB). Its base
address is "0xD1000". The figure shows the Data and the offset. Some registers are not needed in all units.
So only the requested registers are mapped other addresses are masked out.
Firmware Version:
These two bytes contain the hex decimally coded version number of the CX1100 firmware. E.g. the first byte
could show B3(hex): this results in firmware version B3.
Firmware Revision:
These two bytes contain the hex decimally coded revision number of the CX1100 firmware. E.g. the byte
could show 00: this results in revision 00.
Reset Node:
with this bit, a software reset of the 80C165 microcontroller can be performed. This is different from the
hardware reset which may be performed in the Auxiliary Control Block (ACB).
Remap:
with this bit, the two-byte PLC interfaces normally residing in the input/output process areas can be
remapped into the general control block for K-Bus and IP-Link. Thus the input/output process image areas
can be kept clean and for the sole purpose of storing I/O-data.
Link Images:
if set, this bit links the K-Bus logically to the IP-Link in the case of error occurrence - meaning that if one of
them stops operating, the other one is stopped as well. By default, this bit is set so stopping both I/O
systems in case of error is the standard behavior.
Watchdog Time:
With the request of an I/O cycle through "PD cycle request", a watchdog timer with this specified millisecond
time is started. If the cycle is not being restarted by a next "PD cycle request", the watchdog elapses and as
a consequence the output process image is zeroed. This resets all outputs to a safe state (OFF). It also
increments the value in "Watchdog Error Counter" by one. If another value than the default 100ms is written
to this cell, a "Reset node" is needed to activate the change.
Cycle Time:
This is the time elapsed between the initiation and termination of an I/O process image update (K-Bus + IP-
Link ). The time is recorded in units of microseconds and starts with writing a new cycle request to the field
"PD cycle request" and it stops with the termination response in the field "PD cycle ready". For CX1100-0002
this time reflects the K-Bus update time, for CX1100-0003 it is the sum of K-Bus update time and IP-Link
update time.
Processdata Error:
This byte contains the information on the error status of the I/O blocks. The possible bit codes are:
The bit is set to "TRUE", if an error occurred. If both bits are zero, there is no error on either bus system.
Error recovery may be attempted by invoking the "Reset bus" service in the corresponding CB of either K-
Bus or IP-Link.
The following schematic shows the layout of the ACB and is followed by a description of the single bits
contained in it.
DATA/#CMD: This bit controls whether the byte "Display Data Reg" holds a command or display data.
EN: This is the enable bit for executing the operation with the display controller.
BL OFF: If set, this bit turns of the backlight of the LCD Display. This feature may be used for blinking
with the backlight, thus attracting the users attention to an important message on the display. It may also be
used to save power in the case of power loss and UPS operation.
In Register:
These bits reflect the contact status of the 4+1 direction navigation switch on the front side of the CX1100
unit. These events may be used by a software for implementing a menu driven data input/output together
with the LCD display.
Bit 0 UP
Bit 1 DOWN
Bit 2 LEFT
Bit 3 RIGHT
Bit 4 SELECT
Bit 5 PWR-FAIL (reserved for future use - do not use)
An example for access the switch is given in the detailed description of the switch.
Out Register:
Bit 0 RES C165
This bit resets the microcontroller 80C165 and restarts the initialization of the K-Bus and IP-Link circuit. For
doing the reset, this bit must be set high and then set back to low. There is no need for an explicit hold time.
This bit may be used to recover from K-Bus faults such as removing a terminal during operation. It needs to
be set at least once at startup or initialization of the user software before operating the k-Bus.
CX1101 CX1100-0001 power supply unit with display, 4 + 1 navigation switch and NOVRam
CX1102 CX1100-0002 power supply unit with display, 4 + 1 navigation switch, NOVRam and K-bus
connection
CX1103 CX1100-0003 power supply unit with display, 4 + 1 navigation switch, NOVRam, K-bus-
connection and IP-Link-connection
CX1104 CX1100-0004 power supply unit with display, 4 + 1 navigation switch, NOVRam and E-bus
connection.
The I/O operation is done through the bytes named "PD cycle ready" and "PD cycle request" in the GCB.
The K-Bus cycle is triggered by a write operation to the byte "PD cycle request". Although the value being
written to this byte does not matter (it is only the write operation which is important), it is recommendable
write a counter-up value to this byte. The microcontroller for the K-Bus will react to the write operation by
performing a K-Bus cycle and gathering the I/O data. Once the cycle is completed and the electrical signal
input data are written to the DP-RAM, the microcontroller will set the content of byte "PD cycle ready" equal
to the content of "PD cycle request", thus signaling the completion of the I/O cycle. The time required to run a
K-Bus cycle depends on the number of terminals attached to CX1100: it is minimum 700 microseconds and
typically well below 5 milliseconds. The K-Bus cycle time can be viewed by using the TwinCAT System
Manager tool, by entering the exact terminal configuration.
At startup of the user program, before going into cyclic operation, it is mandatory to reset the K-Bus
controller by triggering the "RES C165" bit in the Auxiliary Control Block section of CX1100. Please refer to
the description of the ACB for how to do this.
The sequence of operating the K-Bus can be explained by assuming a cyclic automation task executed each
10 ms on the main CX1000 CPU:
- check if K-Bus operation of previous cycle has finished: is "PD cycle ready" = "PD cycle request" ? Proceed
if yes, issue error message and abort cyclic task operation if not, because a K-Bus cycle does not need 10
milliseconds to finish !
- read the input data from the DP-RAM (these are the input data gathered by the previous cycle "n-1" )
- write the output data to the DP-RAM (these are the outputs calculated by the previous cycle "n-1" ).
- increment and write the new value to "PD cycle request"
- perform task user code
- check if K-Bus operation of previous cycle has finished: is "PD cycle ready" = "PD cycle request" ? Proceed
if yes, issue error message and abort cyclic task operation if not, because a K-Bus cycle does not need 10
milliseconds to finish !
- read the input data from the DP-RAM (these are the input data gathered by the previous cycle "n" )
- write the output data to the DP-RAM (these are the outputs calculated by the previous cycle "n" ).
- increment and write the new value to "PD cycle request"
- perform task user code
Of course only the I/O bytes needed should be copied to or from the DP-RAM, since each read or write
operation over PC104 is time consuming. Please note that the terminal outputs need a K-Bus refresh no
later than 100 milliseconds, otherwise the watchdog in each terminal will shut off the outputs. This means
that the task cycle time should be below 100 milliseconds. Also, if more than one cyclic automation task
needs access to K-Bus I/O, it is important that only one task operates the K-Bus and the other tasks
implement an I/O buffering in order to have a consistent I/O image. In this scenario, the task with the highest
priority has the shortest cycle time and will trigger the K-Bus.
Please note also that it is assumed that in each cycle the integrity of the K-Bus is being checked by
examining the "Processdata error" field in the GCB. Cyclic operation should be aborted in the case of an I/O
error and user should be prompted for corrective actions. Cyclic operation can be resumed after resetting the
faulty bus over the service request fields of the control block.
For some fieldbus connections (all Slave modules) the base addresses are mapped in the memory region
upper DFFFF(hex). So this modules must be ordered with other base addresses. The same situation takes
place if more than two or more master modules of same type are used (for more see note below). The order
numbers for the modules are:
Replace xxx with the following number for the requested fieldbus system:
• 200 for Lightbus
• 310 for Profibus
• 510 for CAN-open
• 520 for DeviceNet
• 750 for Sercos (only Master connection available)
Two connection modules (master or slave) can be used simultaneously. If more than two
connections are needed call Beckhoff Automation GmbH for further information.
Note
2.5 Display
For easy reading a background illumination is integrated to the display. The illumination can be switch on
and off. This blinking can be used to attract the user in certain situations. The state can be set via the
controller. The controller reads the registers in "Auxiliary Control Block" and addresses the display in the
desired manner.
This is done by selecting the CX10x0 device in the hierarchy browser. Under the CX1100 tab it is possible to
write both lines of the display in the "Display settings" area. This requires the fields at the location for
initialisation and writing to be selected. The changes only take effect after the configuration has been written.
When TwinCAT restarts, the set text is then displayed.
The display can be controlled directly through the Display tab. The corresponding functions are carried out
immediately through the switches. It is possible to execute the following functions:
• Switch the display on/off (text is displayed/hidden)
• Background illumination on/off
• Clear the display (text is cleared, and must be re-entered)
• Cursor on/off (the cursor is displayed)
• Cursor flash on/off (the cursor flashes)
The desired text is entered into the text input field. The "Write current" switch inserts the text at the current
position of the cursor.
Using the "Write At" switch, the numerical input box and the "Second Line" check box, it is possible to write
to a specified position on the display. The useful range of values for the position extends from 0 to 15. The
user should also, however, consider the length of the text. (Each line has 16 characters!) In the example
illustrated below, the text "CX1100-000x" is written to Position 0 (the start of the line) on Line 2.
It is then called from the program with its parameters. There are five parameters for this function block:
• bExecute : BOOL
• nDevID : UDINT
• nMode : E_CX1000_DisplayModes
• stLine : STRING(20)
• nCursorPos : DWORD
The command is executed in response to a rising edge at "bExecute". "nDevID" provides the Device ID of
the CX1100 that is to be written to. The ID is displayed in the System Manager. (The General tab for the
CX1100, top right). The parameter "stLine" is used to pass a text of at most 20 characters. Only the first 16
of these characters, however, will be displayed. The writing position of the text uses quoted through
"nCursorPos". 0 to 15 is a useful range for this value. "nMode" selects the operating mode of the function
block. The modes are:
• e_CX1000_DisplayNoAction : No action.
• e_CX1000_DisplayOn : Switch on the display.
• e_CX1000_DisplayOff : Switch off the display.
• e_CX1000_CursorOn : Switch on the cursor.
• e_CX1000_CursorOff : Switch off the cursor.
• e_CX1000_CursorBlinkOn : Switch on the cursor flashing.
• e_CX1000_CursorBlinkOff : Switch off the cursor flashing.
• e_CX1000_BackLightOn : Switch on the background illumination.
• e_CX1000_BackLightOff : Switch off the background illumination.
• e_CX1000_ClearDisplay : Clear the content of the screen.
• e_CX1000_WriteLine1 : Write to the first line.
• e_CX1000_WriteLine1 : Write to the second line.
The block supplies a few status signals for evaluating the program environment. These can be used to
provide feedback to the PLC program. There are three response signals from the function:
• bBusy : BOOL
• bErr : BOOL
• nErrorID : UDINT
"bBusy" indicates that the command is at present being transferred by ADS. No new command will be
accepted as long as "bBusy" remains TRUE. "bErr" reports an error in a call to a function block. (The signal
becomes TRUE). "nErrorID" permits the error that has occurred to be analysed by means of an error
number. The error number [} 75] refers to an error in the ADS protocol.
2.5.3 LC Display
The LC Display of the power supply units has two rows of 16 characters each and is used for displaying
system and user messages.
Index Index Off- Access Data type Phys. Unit Def. Range Description Remarks
Group set
0x00005000 0xFFFF90F R&W Cursor OFF
+ DeviceID F
0x00005000 0xFFFF91F R&W Cursor ON
+ DeviceID F
0x00005000 0xFFFF92F R&W Cursor
+ DeviceID F blink OFF
0x00005000 0xFFFF93F R&W Cursor
+ DeviceID F blink ON
0x00005000 0xFFFF94F R&W Display
+ DeviceID F OFF
0x00005000 0xFFFF95F R&W Display ON
+ DeviceID F
0x00005000 0xFFFF96F R&W Backlight
+ DeviceID F OFF
0x00005000 0xFFFF97F R&W Backlight
+ DeviceID F ON
1. UP
2. DOWN
3. LEFT
4. RIGHT
5. SELECT
Combined inputs, such as UP + RIGHT or UP + RIGHT + SELECT can also be entered. The values of the
switches are stored in a register of the "Auxiliary Control Block", ACB. Details may be referred to in the
architectural description.
The register can be accessed from within a PLC program, and the value can be assessed. This requires a
variable of type USINT first to be created in the PLC program. This is then linked in the TwinCAT System
Manager to the IN-register of the CX1100.
The figure shows the linked signals (with a bright red background). The switch can be accessed from the
PLC program through the Switch variable. The PLC program takes the form described below. To begin an
external variable is declared as an input. (In this example it is at address 0)
PROGRAM MAIN
VAR
Taster AT %IB0 : USINT;
END_VAR
A simple CASE statement can then be used to evaluate the switch, and the desired function can be initiated,
e.g.:
CASE Taster OF
0: ACTION := NONE;
1: ACTION := UP;
2: ACTION := DOWN;
4: ACTION := LEFT;
8: ACTION := RIGHT;
16: ACTION := SELECT;
END_CASE;
In this case, "ACTION" is a newly defined ENUM type. It is also possible for the desired action to be
activated immediately.
The sum of the numerical values is used for the combined functions. In other words, UP (1) and RIGHT (8)
would be 8 + 1 = 9. In this way, only sensible combinations are possible. In other words, switch positions that
are opposite to one another cannot be selected without damaging the switch.
If the programmer does not want to carry out the evaluation, the TwinCAT System provides a library function
that implements conversion of the switch input into an ENUM type. For this purpose, the library for the CX
Systems, TcSystemCX.lib, must be integrated into the library manager. The function is called
"F_CXNaviSwitch(iCX1100_IN : USINT)", and returns an ENUM type. This encodes the direction of the
switch that has been pressed as names, for example e_CX1100_NaviSwitch_MIDDLE for <Middle>. The full
list of valid possibilities is:
• e_CX1100_NaviSwitch_IDLE
• e_CX1100_NaviSwitch_MIDDLE
• e_CX1100_NaviSwitch_TOP
• e_CX1100_NaviSwitch_TOPRIGHT
• e_CX1100_NaviSwitch_RIGHT
• e_CX1100_NaviSwitch_BOTTOMRIGHT
• e_CX1100_NaviSwitch_BOTTOM
• e_CX1100_NaviSwitch_BOTTOMLEFT
• e_CX1100_NaviSwitch_LEFT
• e_CX1100_NaviSwitch_TOPLEFT
• e_CX1100_NaviSwitch_MIDDLE_TOP
• e_CX1100_NaviSwitch_MIDDLE_TOPRIGHT
• e_CX1100_NaviSwitch_MIDDLE_RIGHT
• e_CX1100_NaviSwitch_MIDDLE_BOTTOMRIGHT
• e_CX1100_NaviSwitch_MIDDLE_BOTTOM
• e_CX1100_NaviSwitch_MIDDLE_BOTTOMLEFT
• e_CX1100_NaviSwitch_MIDDLE_LEFT
• e_CX1100_NaviSwitch_MIDDLE_TOPLEFT
Further details on the function can be read in the TwinCAT documentation. The function can be used in a
program as follows: (The declaration and linking are as given in the example above)
CASE F_CXNaviSwitch(Taster) OF
e_CX1100_NaviSwitch_IDLE :; (* do nothing *)
e_CX1100_NaviSwitch_MIDDLE :call_select; (* select item *)
e_CX1100_NaviSwitch_TOP :call_prev_item;(* previous menue item *)
e_CX1100_NaviSwitch_RIGHT :call_inc_value;(* increase value *)
e_CX1100_NaviSwitch_BOTTOM :call_next_item;(* next menue item *)
e_CX1100_NaviSwitch_LEFT :call_dec_value;(* decrease value *)
END_CASE;
Further evaluation of the switch inputs is then done later in the program.
2.7 CX1100-0001
Pin Assignmnet
1 +24 V DC
2 0 V DC
3 GROUND
4 reserved / don't use
5 reserved / don't use
LED:
With proper connection of the power supply unit and with power supply turned on, the power LED (PWR)
lights up green. In the case of a short-circuit, it lights up red.
1. Display 2 x 16 characters
2. 4+1 navigation switch
3. Non Volatile RAM
These functions are managed by the control program via the PC104 bus. The structure of the CX1100-0001
is shown in the following figure:
This power supply unit features only the basic functions. These functions are described in the architecture
overview.
LED:
With proper connection of the power supply unit and with power supply turned on, the power LED (PWR)
lights up green. In the case of a short-circuit, it lights up red.
The I/O LEDs display the operation status of the Bus Terminals. Error-free start-up of the configuration is
signalled by the red "I/O ERR" LED being extinguished. If the ”I/O ERR" LED blinks, an error in the area of
the terminals is indicated. The error code can be determined from the frequency and number of blinks.
PE power contacts
The ”PE" power contact must not be used for other potentials.
1. Display 2 x 16 characters
2. 4+1 navigation switch
3. Non Volatile RAM
4. K-bus connections
These functions are managed by the control program via the PC104 bus. The structure of the CX1100-00x2
is shown in the following figure:
This power supply unit features the basic functions. These functions are described in the architecture
overview. Further the k-bus is supported. The access to the bus is managed by a 4 KB dual-ported-RAM
(DPRAM). A microcontroller (80C165) manages the data transfer to the k-bus. The DPRAM is accessed by
the CPU (via PC104 bus) and the microcontroller.
The memory image of the K-bus resides in the lower memory region (D000 to D0400). This region separates
in input and output region. Since firmware version ≥ B3 it is possible to shift the I/O regions. In this way the
process image can be adapted to the needed space. To each I/O-region the is a control block. Each block
consists of 8 byte for diagnosis purpose. These regions can be shifted, too. The following table shows the
structure of the interface. The offset addresses are default values.
CB K-Bus
Offset Default
0xFD0[2] K-Bus 2 byte plc interface to
CX1100-0002/3
0xFD2[2] K-Bus 2 byte plc interface from
CX1100-0002/3
0xFD4[2] K-Bus diagnosis to CX1100-0002/3
0xFD6[2] K-Bus diagnosis from
CX1100-0002/3
0xFD8 K-Bus service request bitfield
0xFD9 K-Bus service response bitfield
0xFDA K-Bus error code
0xFDB K-Bus error argument
0xFDC[2] K-Bus base ptr Inputs 0x000
0xFDE[2] K-Bus base ptr Outputs 0x200
0xFE0-0xFE1 K-Bus cycle count
0xFE2-0xFE3 K-Bus cycle time [µs]
0xFE4 K-Bus bus status
0xFE5-0xFEE Reserved
0xFEF Retry counter
K-Bus 2 byte plc interface to CX1100-0002/3 / K-Bus 2 byte plc interface from
CX1100-0002/3
These two bytes for each direction - from the main CPU to CX1100 and back - special communication with
the register model of the I/O microcontroller. Through this interface, a communication to K-Bus terminals can
take place. The so called register model description can be found in the hardware description manuals of the
terminals and bus couplers. This communication is typically used for extended diagnosis or configuration of
terminals if they need to deviate from the delivery standard, e.g. changing the baud rate for RS232-terminals
or gain/offset values with analog terminals.
Reset Bus:
with this bit, a reset of the K-Bus may be performed. This is necessary after the occurrence of an error
(detected by examination of the "Processdata error"-byte in the GCB) e.g. after a terminal has been pulled
out. After performing the K-Bus reset, the error code and error argument may be read from the locations "K-
Bus error code" and "K-Bus error argument" in the CB K-Bus. If there is no error after reset, the K-Bus is
ready for operation again.
Free Run:
not implemented. Reserved for future use..
This information is also reflected in the "Processdata error" field (bit0) of the GCB.
Retry counter
This is a retry counter which is incremented each time the microcontroller needs to redo a cycle because of a
communication error. This counter can be used for judgment of the K-Bus signal quality.
Fieldbus connection:
Plug the IP link connector into the respective connections, i.e. one fibre-optic cable each into IN (x03) and
OUT (x04). You then connect the other end with the corresponding IP link interface of the extension box. The
connection must be made so that the output of the fieldbus connection is connected to the input of the
extension box and vice versa.
LED:
With proper connection of the power supply unit and with power supply turned on, the power LED (PWR)
lights up green. In the case of a short-circuit, it lights up red. The I/O LEDs display the operation status of the
Bus Terminals. Error-free start-up of the configuration is signaled by the red "I/O ERR" LED being
extinguished. If the ”I/O ERR" LED blinks, an error in the area of the terminals is indicated. The error code
can be determined from the frequency and number of blinks.
PE power contacts
The ”PE" power contact must not be used for other potentials.
1. Display 2 x 16 characters
2. 4+1 navigation switch
3. Non Volatile RAM
4. K-bus connections
5. IP-Link bus connection
These functions are managed by the control program via the PC104 bus. The structure of the CX1100-00x3
is shown in the following figure:
This power supply unit features the basic functions. These functions are described in the architecture
overview. Further the k-bus is supported. This interface is described in the architecture of the CX1100-0002
unit. This unit also features the access to the IP-Link bus. A fiber optics ring can be connected to the power
supply The access is realized by a 4 KB dual-ported RAM. A microcontroller (80C165) manages the data
transfer to the IP-Link-bus. The DPRAM is accessed by the CPU (via PC104 bus) and the microcontroller.
The memory image of the IP-Link bus resides in the lower memory region (D400 to D0A00). This region
separates in input and output region. Since firmware version ≥ B3 it is possible to shift the I/O regions. In this
way the process image can be adapted to the needed space. Each block jhas a size of 768 bytes. The
following table shows the structure of the interface. The offset addresses are default values.
CB IP-Link
Offset Default
0xFB0[2] IPL 2 byte plc interface to
CX1100-0002/3
0xFB2[2] IPL 2 byte plc interface from
CX1100-0002/3
0xFB4[2] IPL diagnosis to CX1100-0002/3
0xFB6[2] IPL diagnosis from CX1100-0002/3
0xFB8 IPL service request bitfield
0xFB9 IPL service response bitfield
0xFBA IPL error code
0xFBB IPL error argument
0xFBC[2] IPL base ptr Inputs 0x400
0xFBE[2] IPL base ptr Outputs 0x700
0xFC0-0xFC1 IPL cycle count
0xFC2-0xFC3 IPL cycle time [µs]
0xFC4 IPL bus status
0xFC5-0xFCE Reserved
0xFCF Retry counter
IP-Link 2 byte plc interface to CX1100-0003 / IP-Link 2 byte plc interface from
CX1100-0003
These two bytes for each direction - from the main CPU to CX1100 and back - special communication with
the register model of the I/O microcontroller. Through this interface, a communication to K-Bus terminals can
take place. The so called register model description can be found in the hardware description manuals of the
terminals and bus couplers. This communication is typically used for extended diagnosis or configuration of
terminals if they need to deviate from the delivery standard, e.g. changing the baud rate for RS232-terminals
or gain/offset values with analog terminals.
Reset Bus:
with this bit, a reset of the K-Bus may be performed. This is necessary after the occurrence of an error
(detected by examination of the "Processdata error"-byte in the GCB) e.g. after a terminal has been pulled
out. After performing the K-Bus reset, the error code and error argument may be read from the locations "K-
Bus error code" and "K-Bus error argument" in the CB K-Bus. If there is no error after reset, the K-Bus is
ready for operation again.
Free Run:
not implemented. Reserved for future use..
This information is also reflected in the "Processdata error" field (bit0) of the GCB.
Retry counter
This is a retry counter which is incremented each time the microcontroller needs to redo a cycle because of a
communication error. This counter can be used for judgment of the K-Bus signal quality.
LED:
With proper connection of the power supply unit and with power supply turned on, the power LED (PWR)
lights up green. In the case of a short-circuit, it lights up red.
PE power contacts
The ”PE" power contact must not be used for other potentials.
This power supply is designed for use with CX1020 systems only. Operation with CX1000
systems is not possible because the EtherCAT protocol is not implemented / designed in
the hardware of the CX1000 systems.
Note
The power supply CX1100-0004 can only be used instead and not simultaneously with sys-
tem interface CX1020-N060
Note
It is important to keep attention to the hardware revision of the power supply. Power sup-
plies with a hardware revision > 2.0 only work with CX1020 systems with a hardware revi-
sion > 2.1 !
Attention
With the CX1100-0004 power supply EtherCAT Terminals can be connected to the CX1020-System. With
CX1100-0004 the I/O data are stored directly in the main memory of the CPU; a DPRAM is no longer
required. The CX1100-0004 power supply unit for EtherCAT Terminals can only be connected in conjunction
with the basic CPU modules CX1010/CX1020/CX1030. The combination with CX1000/CX1001 is not
possible.
With the CX1100-0014 power supply EtherCAT Terminals can be connected to the CX10x0-System. With
CX1100-0004 the I/O data are stored directly in the main memory of the CPU; a DPRAM is no longer
required. The CX1100-0014 power supply unit for EtherCAT Terminals can not be connected in conjunction
with the basic CX1000 CPU module.
1. Display 2 x 16 characters
2. 4+1 navigation switch
3. Non Volatile RAM
4. E-bus connection
These functions are managed by the control program via the PC104 bus. The structure of the CX1100-0004
is shown in the following figure:
This power supply unit features the basic functions. These functions are described in the architecture
overview. Further the E-bus is supported. The access to the bus is transparent for the user. The unit
transfers the signals from EtherCAT-bus to E-bus. The control is managed by the CPU. The E-bus terminals
are accessed by TwinCAT similar to the K-bus terminals.
3 Transport
Unpacking
Proceed as follows to unpack the unit:
1. Remove packaging.
2. Do not discard the original packaging. Keep it for future relocation.
3. Check the delivery for completeness by comparing it with your order.
4. Please keep the associated paperwork. It contains important information for handling the unit.
5. Check the contents for visible shipping damage.
6. If you notice any shipping damage or inconsistencies between the contents and your order, you should
notify Beckhoff Service.
Attention
During transport in cold conditions, or if the unit is subjected to extreme temperature swings, condensation
on and inside the unit must be avoided.
Prior to operation, the unit must be allowed to slowly adjust to room temperature. Should condensation
occur, a delay time of approximately 12 hours must be allowed before the unit is switched on.
Installation
The devices are designed for installation in control cabinets. You will find installation instructions in the
chapter mechanical mounting.
4.1.1 Dimensions
The CX family product range is characterized by small overall installed size and high modularity. For project
planning purposes, a CPU module, a power supply unit and the associated system interfaces and fieldbus
interfaces have to be provided. The overall width of the application is made up of the individual modules.
With a height of 100 mm, the module dimensions exactly match those of the Beckhoff Bus Terminals.
Together with the lowered connector surfaces, this means that it can be used in a standard terminal box with
a height of 120 mm.
CX1100-0001:
CX1100-0002:
CX1100-0003:
CX1100-0004:
CX1100-0012:
CX1100-0013:
CX1100-0014:
Then fix the CX1020 block on the top hat-rail using the latching straps. You should hear a soft click.
Attention
Only apply pressure at insensitive points of the housing (edges). Never apply pressure on the display, the
buttons or movable parts of the CX10x0 system. After successful latching on the top-hat rail the straps
should be pushed back to their original position.
At least the power connections must be installed. The upper connections "24v" and "0V" must be connected
to power supply. If the power supply CX1100-0001 is used the power supply is connected via the 5-pin open
style connector. (see connections / wiring)
4.2 Commissioning
CX1100-0001 connections
This power supply unit has no I/O interface. Though it is connected via a 5-pin "Open Pluggable Connector".
In older versions of the unit the lower inputs are labeled with UPS+/-. These inputs are not in use and must
not be connected.
CX1100-00x2 connections
This power supply unit has a k-bus interface. The k-bus will be connected separately to the power supply. It
is possible to disable control and bus electronic separately.
CX1100-00x3 connections
This power supply unit has also a k-bus interface. Additional it has an IP-Link interface. The power supply is
equal to CX1100-0002.
CX1100-00x4 connections
This power supply unit was especially designed to connect E-bus terminal to the CX1020-system. The upper
connections supply the CX-System and the E-bus. The lower power connections can be connected to +24V.
UL requirements
Though the handling is identical for both sub busses the explaination is done generally.
k_bus_request AT %QX0.0 : BOOL;
k_bus_err_code AT %IB0 : USINT;
k_bus_err_arg AT %IB1 : USINT;
k_bus_state AT %IB2 : USINT;
ip_bus_request AT %QX0.1 : BOOL;
ip_bus_err_code AT %IB3 : USINT;
ip_bus_err_arg AT %IB4 : USINT;
ip_bus_state AT %IB5 : USINT;
END_VAR
In the PLC program the analysis can be done as follows: (this is only pseudo code)
....
IF k_bus_state = 1 THEN (* an error occured on K-Bus*)
k_bus_request := TRUE; (* request vaules for ErrCode and ErrArg *)
CASE k_bus_err_code OF
0 : return; (* should not happen, though an error occured *)
1 : CASE k_bus_arg OF
0 : report error; (* EEPROM checksum error *)
1 : report error; (* overflow in code buffer *)
2 : report error; (* unknown datatype *)
END_CASE;
2 : CASE k_bus_arg OF
0 : report error; (* programmed configuration, wrong table entry *)
ELSE report error; (* wrong table entry *)
END_CASE;
3 : report error (* K-Bus command error *)
4 : CASE k_bus_arg OF
0 : report error; (* break after power supply *)
ELSE report error; (* break after terminal 'k_bus_arg' *)
END_CASE;
5 : report error (* K-Bus-error during register-communication with termi-
nal 'k_bus_arg' *)
9 : CASE k_bus_arg OF
0 : report error; (* checksum error in program flash *)
ELSE report error; (* terminal 'k_bus_arg' does not exist in boot configuration *)
END_CASE;
14 : report error (* 'k_bus_arg'-th terminal has wrong format *)
15 : report error (* wrong number of bus terminals *)
16 : report error (* length of K-Bus data is invalid *)
END_CASE
k_bus_request := TRUE; (* reset bus, if reason for error is re-
moved, bus starts again *)
....
To make the control work, the register and the program must be linked in System Manager. If the PLC
program is attached in System Manager the following signals are available:
Analog the registers of the terminal bus are shown in System Manager :
and
If all signals are linked the programmer can load configuration and PLC program onto the system.
Firmware > B7
With a new firmware release B7 it is easier to access the diagnosis values. The solution described above
clears the error code if the reason for the error is no longer present. With the firmware > B7 its possible to
get the error codes directly in the case of the error. To access the error codes the Bit 4 in GCB must be set
to 1. So for diagnosis its a good idea to set the bit in the initialization of error routine or PLC program. The bit
must be linked to the bit 4 in GCB:
In the case of some errors, rectification does not cause the power supply to leave the blink sequence. The
power supply can only be restarted by switching its supply voltage off and on again.
Note:
The supply voltage of the power supply unit, which is necessary to supply power to the CX1000 system,
must not be interrupted in the middle of operation. Switching off the supply voltage to the power supply unit
refers here to the power supply on the power contacts.
In the case of some errors, rectification does not cause the power supply to leave the blink sequence. The
power supply can only be restarted by switching its supply voltage off and on again.
Note:
The supply voltage of the power supply unit, which is necessary to supply power to the CX1000 system,
must not be interrupted in the middle of operation. Switching off the supply voltage to the power supply unit
refers here to the power supply on the power contacts.
In the case of some errors, rectification does not cause the power supply to leave the blink sequence. The
power supply can only be restarted by switching its supply voltage off and on again.
Note:
The supply voltage of the power supply unit, which is necessary to supply power to the CX1000 system,
must not be interrupted in the middle of operation. Switching off the supply voltage to the power supply unit
refers here to the power supply on the power contacts.
If an error occurs on both terminal busses (K-Bus and IP-Link-Bus) the error on K-Bus is
reported at first. The IP-Link-Bus error is reported as second. Both error codes are intro-
duced by their typical blink signal.
Note
In the case of some errors, rectification does not cause the power supply to leave the blink sequence. The
power supply can only be restarted by switching its supply voltage off and on again.
Note:
The supply voltage of the power supply unit, which is necessary to supply power to the CX1000 system,
must not be interrupted in the middle of operation. Switching off the supply voltage to the power supply unit
refers here to the power supply on the power contacts.
If an error occurs on both terminal busses (K-Bus and IP-Link-Bus) the error on K-Bus is
reported at first. The IP-Link-Bus error is reported as second. Both error codes are intro-
duced by their typical blink signal.
Note
The functions for L/A and RUN LED are available in hardware revision > 2.0. The LEDs have no function in
older revisions.
The functions for L/A and RUN LED are available in hardware revision > 2.0. The LEDs have no function in
older revisions.
6 Decommissioning
1.1. Release and remove the first Terminal next to the power supply unit on the top-
hat rail.
First remove any wiring from power supply unit and then from the first terminal on the top-hat rail next to the
power supply unit. If the wiring is to be reused for another system, it is advisable to make a note of the
connections. Then pull the orange terminal release (see arrow) to release the terminal and pull it out.
2.1. Separating the power supply unit, the CX10x0 CPU and other components
Place the CX10x0 block onto a suitable support with the front facing down. Then insert a flat screwdriver with
dimensions 1.0 x 5.5 x 150 mm into the locking mechanism, and then operating the slider by turning it about
90 degrees.
The locking mechanism on the rear affects an approx. 2-3 mm wide clearance of the module latching
mechanism, pushing them apart. The plug connectors of the PC 104 interface can then be pulled apart
carefully.
Only modules (CPU, fieldbus connections and UPS modules) that can be separated non-destructively
feature a release device. Modules that cannot be separated only feature a marking point (with or without red
paint seal). Applying force to these elements will destroy them.
Forcibly opening the module housing (e.g. removing the cover) will destroy the housing.
Attention
Disposal
The device must be fully dismantled in order to dispose of it.
Electronic parts must be disposed of in accordance with national electronics scrap regulations.
7 Appendix
7.2 Certifications
All products of the Embedded PC family are CE, UL and GOST-R certified. Since the product family is
continuously developed further, we are unable to provide a full listing here. The current list of certified
products can be found at www.beckhoff.com.
The addresses of Beckhoff's branch offices and representatives round the world can be found on her internet
pages:
http://www.beckhoff.com
You will also find further documentation for Beckhoff components there.
Beckhoff Headquarters
Beckhoff Automation GmbH & Co. KG
Huelshorstweg 20
33415 Verl
Germany
Phone: +49(0)5246/963-0
Fax: +49(0)5246/963-198
e-mail: [email protected]
Beckhoff Support
Support offers you comprehensive technical assistance, helping you not only with the application of
individual Beckhoff products, but also with other, wide-ranging services:
• support
• design, programming and commissioning of complex automation systems
• and extensive training program for Beckhoff system components
Hotline: +49(0)5246/963-157
Fax: +49(0)5246/963-9157
e-mail: [email protected]
Beckhoff Service
The Beckhoff Service Center supports you in all matters of after-sales service:
• on-site service
• repair service
• spare parts service
• hotline service
Hotline: +49(0)5246/963-460
Fax: +49(0)5246/963-479
e-mail: [email protected]