UG IC EtherNetIP 2port EN
UG IC EtherNetIP 2port EN
Universal Fieldbus-Gateway
UNIGATE® IC-EtherNet/IP 2Port
1 General introduction . . . . . . . . . . . . . . . . . . . . . . . . 9
2 The UNIGATE® IC . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 Technical introduction . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4 The serial standard interface . . . . . . . . . . . . . . . . . . . . . . 10
2.5 The synchronous interface . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 The Debug-interface . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.7 UNIGATE® IC hardware survey . . . . . . . . . . . . . . . . . . . . 11
3 Hardware design. . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2.1 -Boot enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.2 Load out (SPI-Master: SS0-). . . . . . . . . . . . . . . . . . . . . . 13
3.2.3 Data out (SPI-Master: SS1-) . . . . . . . . . . . . . . . . . . . . . . 13
3.2.4 Data In (SPI: MISO) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.5 Load In (SPI: MOSI) . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.6 Clock (SPI: SCK) . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.7 -Reset In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.2.8 LED-LINKACT 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.9 LED-LINKACT 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.10 State-LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.11 -Config Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.12 DbgTX, DbgRx. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.13 TE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2.14 TX, RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 Basic line of proceeding . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.6 Layout examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.7 Handling (mounting the UNIGATE® IC on the carrier board) . . . . . . 22
3.8 Requirement for Ethernet-Interface . . . . . . . . . . . . . . . . . . . 23
4 The serial interface . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2 Initialization of the serial interface . . . . . . . . . . . . . . . . . . . 24
4.3 Use of the serial interface . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Further operation modes . . . . . . . . . . . . . . . . . . . . . . . . 24
5 Synchronous serial interface . . . . . . . . . . . . . . . . . . . 25
5.1 Shift register operation . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1.1 Example-Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Disclaimer of liability
We have checked the contents of the document for conformity with the hardware and software
described. Nevertheless, we are unable to preclude the possibility of deviations so that we are
unable to assume warranty for full compliance. The information given in the publication is,
however, reviewed regularly. Necessary amendments are incorporated in the following editions.
We would be pleased to receive any improvement proposals which you may have.
Copyright
Copyright (C) Deutschmann Automation GmbH & Co. KG 1997 – 2022. All rights reserved.
This document may not be passed on nor duplicated, nor may its contents be used or disclosed
unless expressly permitted. Violations of this clause will necessarily lead to compensation in
damages. All rights reserved, in particular rights of granting of patents or registration of
utility-model patents.
1 General introduction
In the past the integration of a fieldbus connection required an enormous effort from the progress
engineers. On account of the large variety of communication systems it is not enough to compile
the right combination of communication hardware; due to their standards and fundamentals dif-
ferent busses also require the corresponding skills of the engineers.
This does not apply in case of the UNIGATE® IC by Deutschmann Automation any more. All dig-
ital functions, software, stack and driver as well as optocoupler are integrated on a UNIGATE® IC
in correspondence with the standard. In addition to the reduction of the required size, also differ-
ent fieldbusses can easily be integrated.
Since 1997 Deutschmann Automation has experience in the field of fieldbus gateways; this
enormous experience results in the UNIGATE® IC as a consistent sequel of this successful
product line.
Terminology
In the entire document and in all parts of the software that is to be used, the terms Input and Out-
put are used. Input and Output are ambiguous, always depending on the viewpoint. We see the
fieldbus as central interface and as integral component of your device; therefore in all places it is
always referred to data from the viewpoint of the Slave, that is Input data, as data from the Mas-
ter to the Slave - regardless of the used bus.
Representation of numbers
Numbers in decimal format are always represented without prefix and without suffix as well.
Hexadecimal numbers are always marked with the prefix 0x.
2 The UNIGATE® IC
2.1 Technical introduction
The UNIGATE® IC by Deutschmann Automation contains all components that are required for
the communication in a fieldbus in one single module. Therefore a developer does not have to
take care for that detail any more, only a hardware redesign is necessary in order to integrate the
UNIGATE® IC and the required plug connectors.
2.2 Availability
The module is available as EtherNet/IP. Further fieldbusses are either planned or being worked
on. They will only differ in the connections of the busses. The meaning of the general pins 1 - 9
as well as 24 and 26 - 32 will remain unchanged also for further fieldbus implementations.
You can find an up-to-date list for all UNIGATE® ICs under:
http://www.deutschmann.de.
2.3 Firmware
UNIGATE® IC is programmed via scripts. On principle any script, that has been developed for a
UNIGATE® SC, can also be operated on the UNIGATE® IC.
3 Hardware design
This chapter gives basic advise, that is required in order to load UNIGATE® IC into your own
hardware designs. In the following all ports of UNIGATE® IC are described in detail.
3.1 Ports
UNIGATE® IC features 32 pins in its layout as a DIL 32 component. The exact mechanical
dimensions can be taken from chapter 16.
3.2 Pinout
Pin Technical Name Description
specifications Remark
1* 3.3V ± 5% < 460mA Vcc +3.3V voltage supply
2 INLogic -BE boot enable
3 OUTDriver Load out strobe signal for synchronous, serial
(SS0-) interface
4 OUTDriver Data out output data for synchronous, serial inter-
(SS1-) face
5 INLogic Data in input data of the synchronous, serial
(MISO) interface internally pulled up with 10 k
6 OUTLogic Load in strobe signal input data of the synchro-
(MOSI) nous, serial interface
7 OUTDriver Clock clock pulse signal for synchronous,
(SCK) serial interface
8 INReset -Reset in reset-input of the IC internally pulled up with 100 k
9* connected to pin 1 Vcc +3.3V voltage supply
10 according to norm Error-LED Anode of the red LED
11 according to norm LED-LINK- Ethernet-link pulse found / Networkdata
ACT1 traffic Port 1
12 nc nc not connected
13 according to norm RD1- Ethernet-signal RD- Port1 galvanically isolated
insulation voltage 1000 Vrms
14 according to norm RD1+ Ethernet-signal RD+ Port1
15 according to norm TD1- Ethernet-signal TD- Port1
16 according to norm TD1+ Ethernet-signal TD+ Port1
17 according to norm TD2+ Ethernet-signal TD+ Port2
18 according to norm TD2- Ethernet-signal TD- Port2
19 according to norm RD2+ Ethernet-signal RD+ Port2
20 according to norm RD2- Ethernet-signal RD- Port2
21 nc nc not connected
22 according to norm LED-LIN- Ethernet-link pulse found / Network data
KACT2 traffic Port2
23 nc nc not connected
24* connected to pin 32 GND Ground supply voltage of the IC
25 State-LED Bus status LED (Anode of the green
LED)
26 INLogic -Config Mode Signal to start in configuration mode internally pulled up with 100 k
27 OUTLogic DbgTX serial Debug TX
28 INLogic DbgRX serial Debug RX internally pulled up with 100 k
29 INLogic RX serial data RX internally pulled up with 100 k
30 OUTLogic TX serial data TX
3.2.7 -Reset In
• A reset generator (Max 809) is on board; with it in the normal case the reset input is not requi-
red. In this case the reset input has to be connected with VCC, in order to avoid interferences
(see chapter 3.6).
• If the the customer’s application has to initiate a reset of the UNIGATE® IC, then the reset input
can also be connected with a reset output of the customer’s application instead of connecting it
with VCC. Here all specifications of the reset signal, mentioned in chapter 3.2 have to be kept.
The reset-impulse is supposed to last at least 10 ms.
3.2.8 LED-LINKACT 1
A green LED can be connected to this line (see chapter 3.6). This is directly accessed by the
Processor and is glowing when the Gateway on Port 1 is an operational network (it will receive
link pulses) and flickers if there is network traffic.
3.2.9 LED-LINKACT 2
A green LED can be connected to this line (see chapter 3.6). This is directly accessed by the
Processor and is glowing when the Gateway on Port 2 is an operational network (it will receive
link pulses) and flickers if there is network traffic.
3.2.10 State-LED
A green LED can be connected to this line (see chapter 3.6). It shows the Bus Status and is glow-
ing in the state of “Ethernet ok, data exchange active“. It is flashing in the state “Waiting for link
connection“.
3.2.13 TE
The transmit enable signal allows the connection of RS485 drivers to the IC’s serial interface.
The signal is set to High whenever the IC sends via the line TX.
3.2.14 TX, RX
Transmission and receive line of the serial interface. This interface is programmable in accor-
dance with the description in chapter 4.
3.3 Software
The software executes script-commands, which in turn control the IC’s hardware and they pro-
cess their complete protocol by software. The script itself can be generated by the company
Deutschmann Automation or with the software Protocol Developer by yourself. For a detailed
description of the script.commands of the Protocol Developer see the instruction manual Proto-
col Developer and the online documentation concerning script-commands.
Your device, which on the whole is supposed to be assembled as shown above, will now be mod-
ified in a way that the EtherNet/IP is available at the 9-pol. socket. However, a hardware redesign
is necessary in order to keep the assignment in standard form.
After the RS232-driver has been replaced by the UNIGATE® IC, EtherNet/IP is available at an
RJ45-socket.
The UNIGATE® IC independently processes the communication with the customer’s device via
the TTL-interface.
Here only the synchronous serial interface is used, the asynchronous serial interface is basically
of no account. If you want to program the script in your completed application, then the use of a
connector for the asynchronous interface is recommended. With it you can carry out the ISP-pro-
gramming.
For this operating mode no additional controller is required on your application!
The following circuit diagram is an example for how shift register components can be connected
to the IC.
Valid for all versions: A planed plug connection of the serial interface in the application offers the
possibility of an update of the firmware or the software via an external connection.
Note:
The following recommendations result from the reference design of the Micrel Switch used in the
UNIGATE® IC-EI 2Port:
• Pulse H1102
• Transpower HB726
• Bel Fuse S558-5999-U7
• YCL PT163020
• DELTA LF8505
• Mounting on a socket in the carrier board. If necessary solder the UNIGATE® IC to 2 or 4 pins
in the socket. Normally the IC can easily be pulled out after the soldering points have been re-
moved.
• Make arrangements for two holes next to the socket in the layout. After the UNIGATE® IC was
plugged in the socket pull an isolated wire over the IC and solder it on the carrier board at the
specified holes.
• Fasten the UNIGATE® IC With a wire or a tie wrap on the socket.
• Manual soldering directly on the carrier board.
• Automatic soldering directly on the carrier board, whereas „selective“ soldering is essential (no
wave soldering)
The advantage of the socketed variant is the easy download of Script- and Firmware-updates, if
the carrier board is not designed for it. Besides, that way the Fieldbus can be changed easily by
changing the UNIGATE® IC if the corresponding plug connectors are provided on the carrier
board. Another advantage is, that - normally - only a reflow soldering of the carrier board is ne-
cessary.
The advantage of the soldered variant is, that the installation height is lower and a higher shock-
and vibration-safety is provided.
To enable a quick start in the selection of appropriate components, we have compiled a list of
order numbers of Würth Elektronik below, where we source our components. Of course, other
manufacturers are possible, so the following list is to be considered exemplary.
Further information:
We had bad experiences with SMT connectors in the past, because in the field they got demol-
ished every now and then due to mechanical loads.
It allows
• the expansion of the IC for digital inputs and outputs (for example for driving LEDS or for rea-
ding switch positions)
• communicate with microcontrollers or
• the control of DA and AD converters.
Connection examples are give in chapter 3.
By using the synchronous serial interface can realize products that can work without another
microcontroller (stand-alone mode). Examples are sensor products or digital IO modules
The data exchange with the connected shift registers ensues with the commands „WriteShif-
tRegister“, „ReadShiftRegister“ or bidirectional with the command „ShiftRegisterDa-
taExchange“. The clock rate is approx. 45 kHz.
Further information on the commands and parameter values can be found in the Help section of
the Protocol Developer Software. On request, the Deutschmann Script language can be comple-
mented by additional parameter values in order to support other types of shift registers.
5.1.1 Example-Script
Note: The script example refers to the circuit example in chapter 3.5.
Set( ShiftRegisterInputBitLength, 16 );
Set( ShiftRegisterOutputBitLength, 16 );
WriteShiftRegister( OutBuffer[0] );
ReadShiftRegister( InBuffer[0] );
5.2.1 Example-Script
var L_Freq : long;
var b_Channel : byte;
var w_Len : word;
var a_BufOut : buffer[100];
var a_BufIn : buffer[100];
moveconst( b_Chanel, 0 );
moveconst( w_Len, 11 );
moveconst( a_BufOut[0], "Hello World" );
ExchangeSPI( b_Channel , w_Len , a_BufOut[0] , a_BufIn[0] );
6 The Debug-interface
6.1 Overview of the Debug-interface
The UNIGATE® IC features a Debug-interface, that allows a step-by-step processing of a script.
Normally this interface is only required for the development of a script.
Script Download
Start
Yes
No Yes
received "."?
Yes
Send <LF> (0x0A)
Send rst 96 bytes of DCS le
as 192 byte HEX-string
(e. g. 0x2E => "2E")
Calculate checksum (16-Bit)
as sum of all bytes
No
received "."?
Wait for reception of "Download ok"
(Timeout 500 ms) Yes Error
No
Bytes left > 127?
No
received "Download ok"? Yes
End
The Gateway responds with a clear text reply to that download and carries out a warm start.
Example:
The following 4-bytes script is supposed to be downloaded: 0x01 0x12 0x5A 0x23
The sum of the bytes is 0x0090 as checksum.
Then the following sequence is to be sent:
1. 0x10 Ctrl-P
2. 0x30 '0'
3. 0x31 '1'
4. 0x31 '1'
5. 0x32 '2'
6. 0x35 '5'
7. 0x41 'A'
8. 0x32 '2'
9. 0x33 '3'
10. 0x0A LF
11. 0x30 '0'
12. 0x30 '0'
13. 0x39 '9'
14. 0x30 '0'
7.4.1 Ethernet
• Baud rate: 10/100 MBit/s autodetect
• IP-address (Gateway)
• Ethernet (MAC-address)
• IP-destination host
7.4.2 RS232/RS485/RS422
• RS-ype: RS232
• Start bit: 1
• Data bits: 8
• Stop bit: 1
• Parity: None
• Baud rate: 9600 Baud
Default setting. This configuration can be changed via the Script.
8 Generating a script
8.1 What is a script?
A script is a sequence of commands, that are executed in that exact order. Because of the fact
that also mechanisms are given that control the program flow in the script it is also possible to
assemble more complex processes from these simple commands.
The script is memory-oriented. It means that all variables always refer to one memory area.
While developing a script you do not have to take care of the memory management though. The
Protocol Developer takes on this responsibility for you.
9 FTP-Server
This UNIGATE® features an integrated FTP-Server, which allows access to the file system of the
device. The FTP-Server is password protected. With the predefined user name "deutschmann“
and the password “deutschmann“ a connection can be established. The login data can be
defined by setting the Script parameters „FTP_Password“ and „FTP_UserName“.
Note: On write access to the file system the actual write process to the non-volatile memory is
taking place delayed (5 seconds after the last write access to the file system or when disconnect-
ing the FTP connection). Before restarting the device one must wait for the write process to the
non-volatile memory to complete to prevent data loss.
10 WEB-Server
This UNIGATE® has an integrated web server. The delivery condition has a HTML-Page in the
file system, which shows the system parameters of the device.
The Web Page can be changed by the customer as desired, or replaced with a self-created web
page. It can be written into the file system via FTP (see chapter 9).
<!--#exec=“Command“-->
To issue any process data, additional Script variables can be given to the Web-Server with the
Script-Commands „SetHTMLOutputString“. The command assigns the variable a name,
which then can be used in the following command:
10.2 HTML-Forms
The supporting of HTML Forms allows the Web Server to design interactive web pages. So, for
example, input forms for process values can be realized.
The script command „SetHTMLInputString“ assigns a name to a script variable, which then
can be used in the HTML form.
10.3 Examples
The interaction between Gateway-Script and HTML page can be taken from the example HTML
page „ssi.shtml“ and the example Script „example_Set_HTML_String.dss“. Both files are
accessable in the download area of our website www.deutschmann.com.
11 File System
The UNIGATE® has a file system which is being used by the integrated FTP-Server and the inte-
grated Web-Server (view chapter 10). Furthermore it‘s also used by some devices for storing of
device parameters.
If necessary the device parameter files can be created and initialized by the UNIGATE® automat-
ically. The following table shows an example of the contents of the file system in delivery condi-
tion (contents may vary depending on the device, subject to change without prior notice).
File Remark
devname.txt device name
nvdata non-volatile device parameter
bg.jpg device web site
bg_container.jpg
bg_footer.jpg
bg_topnavi.gif
bottom.gif
da-logo.gif
deutschmann.css
down.gif
favicon.ico
h4_pre.gif
header_schatten.jpg
headline.jpg
index.html
line.gif
profinet.gif
rnavmain_bg.gif
ssi.html
teaser_header.jp
It is possible to reformat the file system via FTP. It will lose all data stored in the file system. To
perform the formatting of your command-line please use the FTP client on Microsoft® Windows®
(Command Prompt -> ftp.exe). Make a connection to the FTP server of the UNIGATE® and then
run the command "del*.*". The string "*.*" is understood as a request by UNIGATE® to for-
mat the file system.
12 EtherNet/IP
If you are speaking of EtherNet/IP, then the CIP about Ethernet is meant. The end device’s proto-
col is being converted in the UNIGATE® via a Script.
12.5 Literature
We recommend the book "The Common Industrial Protocol and the Family of CIP Networks"
(PUB 00123RO), to help you quickly get to grips with the subject of Ethernet/IP. The book can be
ordered from the ODVA User Organisation (web: www.odva.org).
Issue: MAC1-MAC2-MAC3-MAC4-MAC5-MAC6
Calculation:
MAC1 = 00
MAC2 = 14
MAC3 = 11
MAC4 = (SN - 28950000) / 65536
MAC5 = ((SN - 28950000) / 256) mod 256
MAC6 = (SN - 28950000) mod 256
Consequently the device with the SN 32180349 has the MAC 00-14-11-31-4A-8D
In the configuration mode these displays are not valid and only meant for internal use.
Error no. Error description
0 Reserved
1 Hardware fault
2 EEROM error
3 Internal memory error
4 Fieldbus hardware error
5 Script error
6 Reserved
7 RS-transmit buffer overflow
8 RS-receive buffer overflow
9 RS timeout
10 General fieldbus error
11 Parity-or frame-check-error
12 Reserved
13 Fieldbus configuration error
14 Fieldbus data buffer overflow
15 Reserved
Table 1: Error handling at UNIGATE® IC
15 Firmware-update
15.1 Overview
UNIGATE® IC has a memory for the firmware. It can be replaced via the UNIGATE® IC’s Ether-
Net/IP-interface.
16 Technical data
In this chapter you will find all necessary technical data on UNIGATE® IC.
All measurements in mm.
2,70
3,20
3,95 0,47
2,54
UNIGATE® IC
Ethernet TCP/IP (wt*) + Modbus TCP (wt*)
Ethernet TCP/IP + Modbus TCP
PROFIBUS DP (PBL/PBX/PBY)
PROFIBUS DP-DPV1
EtherNet/IP 1Port
PROFINET 1Port
EtherCAT (wt*)
LONWorks
DeviceNet
CANopen
EtherCAT
MPI
RS
Note: The total height of all UNIGATE® ICs can be found in the "Pinout list for UNIGATE® IC and
UNIGATE® IC2". (Download PDF)
The pins of the UNIGATE® ICs are arranged in a grid dimension of 2.54 mm
25,00
front
4,88 15,24
DIP-Spacing Code 6
In case you intend to use other fieldbus ICs, the maximum overall height of 20 mm (including
pins) has to be taken into consideration.
* When implementing a UNIGATE® IC in your electronics, not only the mechanical dimensions but also the
thermal management must be taken into account. The ambient temperature specified in the manual does
not take into account the specific installation situation (e.g. closed housing). External factors have a major
influence on how well the heat is dissipated from the heat sources. When using the UNIGATE® IC in your
electronics, adequate heat dissipation must therefore be ensured.
With the UNIGATE® IC EtherNet/IP 2Port, the greatest heat development comes from the two components
"fido 1100" and "MICREL KSZ8873MLLI", both on the top of the module.
17 Accessory
The following tools are available from Deutschmann Automation.
The required UNIGATE® IC / ICs are ordered separately. The required voltage (5V or 3.3V,
depending on the version) can be adjusted. An RS232-interface or a USB-connection is avail-
able for the connection to the PC (Debug-interface).
The application can be connected either through the USB, RS232, RS485 or the RS422.
The bus-connections according to standard or market standard are available to test the respec-
tive bus-side. Optionally Deutschmann Add-on packages (bus-master simulation) are available.
The board contains 32 bit input and 16 bit output, provided with one LED each. Different connec-
tors allow an easy coupling to your processor. A hole matrix field with the most important signals
(voltage, IOs) allows a customized hardware extension (e. g. to connect a D/A converter).
For a transparent data exchange you will find example scripts for the respective Fieldus under
"File->New" in the Protocol Developer.
18 Servicing
Should questions arise that are not covered in this manual you can find further information in our
Your request will be recorded in the Support center and will be processed by our Support Team
as quickly as possible (Usually in 1 working day, rarely more than 3 working days.).
The more precise information a fault/error description you provide, the more exactly we will be
able to pinpoint the possible causes.
19 Annex
19.1 Explanations of the abbreviations
General
CL = Product group CL (Compact Line)
CM = Product group CM (CANopen Line)
CX = Product group CX
EL = Product group EL (Ethernet Line)
FC = Product group FC (Fast Connect)
GT = Galvanic separation RS-side
GY = Housing color gray
MB = Product group MB
RS = Product group RS
SC = Product group SC (Script)
232/485 = Interface RS232 and RS485 switchable
232/422 = Interface RS232 and RS422 switchable
DB = Additional RS232 DEBUG-interface
D9 = Connection of the RS through 9-pin D-SUB instead of 5-pin screw-plug connector
PL = Board only without DIN-rail module and without housing cover
PD = Board only without DIN-rail module and with housing cover
AG = Gateway installed in a die-cast aluminum housing
EG = Gateway installed in a stainless steel housing
IC = Product group IC (IC-design DIL32)
IC2 = Product group IC2 (IC-design DIL32)
IO8 = Option I/O8
16 = Script memory expanded to 16KB
5V = Operating voltage 5V
3,.3V = Operating voltage 3.3V
Fieldbus
CO = CANopen
C4 = CANopen V4
C4X = CANopen V4-version X (see comparison table UNIGATE® IC for the respective
product)
DN = DeviceNet
EC = EtherCAT
EI = EtherNet/IP
FE = Ethernet 10/100 MBit/s
FEX = Ethernet 10/100 MBit/s-version X (see comparison table UNIGATE® IC for the
respective product)
IB = Interbus
IBL = Interbus
LN62 = LONWorks62
LN512 = LONWorks512
ModTCP = ModbusTCP
MPI = Siemens MPI®
PL = Powerlink
PN = PROFINET-IO
PBDP = PROFIBUS DP
PBDPL = PROFIBUS DP-version L (see comparison table UNIGATE® IC for the respective
product)
PBDPX = PROFIBUS DP-version X (see comparison table UNIGATE® IC for the respective
product)
PBDPV0 = PROFIBUS DPV0
PBDPV1 = PROFIBUS DPV1
RS = Serial RS232/485/422
20 Annex
20.1 Explanations of the abbreviations
General
CL = Product group CL (Compact Line)
CM = Product group CM (CANopen Line)
CX = Product group CX
EL = Product group EL (Ethernet Line)
FC = Product group FC (Fast Connect)
GT = Galvanic separation RS-side
GY = Housing color gray
MB = Product group MB
RS = Product group RS
SC = Product group SC (Script)
232/485 = Interface RS232 and RS485 switchable
232/422 = Interface RS232 and RS422 switchable
DB = Additional RS232 DEBUG-interface
D9 = Connection of the RS through 9-pin D-SUB instead of 5-pin screw-plug connector
PL = Board only without DIN-rail module and without housing cover
PD = Board only without DIN-rail module and with housing cover
AG = Gateway installed in a die-cast aluminum housing
EG = Gateway installed in a stainless steel housing
IC = Product group IC (IC-design DIL32)
IO8 = Option I/O8
16 = Script memory expanded to 16KB
5V = Operating voltage 5V
3,.3V = Operating voltage 3.3V
Fieldbus
CO = CANopen
C4 = CANopen V4
C4X = CANopen V4-version X (see comparison table UNIGATE® IC for the respective
product)
DN = DeviceNet
EC = EtherCAT
EI = Ethernet/IP
FE = Ethernet 10/100 MBit/s
FEX = Ethernet 10/100 MBit/s-version X (see comparison table UNIGATE® IC for the
respective product)
IB = Interbus
IBL = Interbus
LN62 = LONWorks62
LN512 = LONWorks512
ModTCP = ModbusTCP
MPI = Siemens MPI®
PL = Powerlink
PN = Profinet-IO
PBDP = ProfibusDP
PBDPL = ProfibusDP-version L (see comparison table UNIGATE® IC for the respective
product)
PBDPX = ProfibusDP-version X (see comparison table UNIGATE® IC for the respective
product)
PBDPV0 = ProfibusDPV0
PBDPV1 = ProfibusDPV1
RS = Serial RS232/485/422