SICK CDM425-10234094 CDM425-00034094 Connection Modules Operating instructions

Brand: SICK

Model: CDM425-10234094 CDM425-00034094 Connection Modules

Type: Operating instructions

OPERATING INSTRUCTIONS

CDM425-10234094

CDM425-00034094

Connection Modules

Gateways for connecting a SICK identification

sensor to PROFINET IO

Operating Instructions CDM425 PROFINET IO

This document describes the field bus gateway CDM425 PROFINET I/O (Version V3.34 or higher) and the

initialization with a CLV6xx (V3.32 or higher).

The needed handling on the Profinet Controller side is described here by explaining the handling of a S7

CPU with integrated Profinet.

The field bus gateway CDM425 PROFINET I/O is simply referred as CDM425 in this document.

Content

Feature CDM425........................................................................................................................................3

2 Electrical connection................................................................................................................................4

3 Connecting sensors .................................................................................................................................6

3.1 Connecting CLV6xx Bar Code Scanner.............................................................................................7

3.2 Connecting other devices ..................................................................................................................9

4 Handling on PLC Side ............................................................................................................................10

4.1 Install GSDML file ............................................................................................................................10

4.2 Mode overview of CDM425..............................................................................................................11

4.3 Insert CDM425 in HW-Config...........................................................................................................12

5 CDM425 data modes...............................................................................................................................13

5.1 CDM425 in Handshake Mode (HS)..................................................................................................13

5.1.1 Byte Layout Handshake mode (HS)..............................................................................................15

5.1.2 Receive Data.................................................................................................................................15

5.1.3 Example 1, Receive Single Block Telegram (HS-Mode):..............................................................16

5.1.4 Example 2, Receive Multiple Block Telegram (HS-Mode) ............................................................17

5.1.5 Transmit Data................................................................................................................................18

5.1.6 Example 3, Transmit single block telegram SW-Trigger 21/22 (HS-Mode)...................................19

5.1.7 Example 4, Transmit multiple block telegram (HS-Mode).............................................................20

5.1.8 Binary Inputs .................................................................................................................................21

5.1.9 Binary Outputs ..............................................................................................................................22

5.2 CDM425 in No Handshake mode (NH)............................................................................................23

5.2.1 Byte Layout in No-Handshake Mode (NH):...................................................................................23

5.2.2 Example 5, Receive Telegram (NH-Mode): ..................................................................................24

5.2.3 Example 6, Transmit Telegram (NH-Mode) ..................................................................................25

5.3 CDM425 in Device master mode (DM) ............................................................................................26

5.3.1 Byte Layout in Device Master Mode (DM-Mode) ..........................................................................27

5.3.2 Example 7, Receive Telegram (DM-Mode):..................................................................................28

5.3.3 Example 8, Transmit Telegram (DM-Mode)..................................................................................29

6 Appendix .................................................................................................................................................30

6.1 Tools for checking and setting Device name and IP-Address from PLC side..................................30

6.2 Checking Profinet device names from PLC side..............................................................................32

6.3 Checking Ethernet Line using PST (Primary Setup Tool) ................................................................32

6.4 Using PortVison Tool .......................................................................................................................33

6.5 Parameterization of CDM425 via Web-Interface..............................................................................34

6.6 Firmware-Update CMD425 using PortVison Tool............................................................................37

6.7 Software versions of CDM425 .........................................................................................................38

6.8 Function of LEDs of CMD425 ..........................................................................................................38

Operating Instructions CDM425 PROFINET IO

1 Feature CDM425

The CDM425 is a one-port Profinet gateway from RS 232 to Profinet IO with one serial RS 232 port which

can be connected to a device as:

 9600, 19200, 38400, or 57600 Baud

 8, n, 1 or 8, odd, 1

 Data must be framed with STX (Hex 02) and ETX (Hex 03)

 Data receiving and transmitting is possible

 Max. Data length is 220 byte in DM/NH-Mode and 4000 byte in HS-Mode

The Interface is connected at the Host Port of the sensor (Pins 7 + 9 of 15 pin-HD socket).

The Default settings are:

Device Name: CDM425

IP-Address: 192.168.0.2

Subnet-Mask: 255.255.255.0

Mac address: 00 06 77 xx xx xx (printed on a label on the upper side of the field bus gateway)

The following sensors can be connected:

with parameterization from Sensor side via SOPAS-ET (CLV6xx):

 CLV6xx bar code scanner

With separate parameterization via PLC-Tools or Web-Interface (CDM425):

 CLV42x-45x bar code scanner

 CLV48x/49x bar code scanner with cable 2027046 or 2030023,

 LECTOR62x, ICR84x-2/ICR85x-2 camera-based code reader,

 RFH620/630 RFID interrogator

 Any device which can send or receive RS 232 strings in the described format.

If a triggering from the PLC should be done a SW-Trigger must be used.

CDM425-00034094: for 1 sensor (based on CDM420-0001)

CDM425-10234094: for 2 sensors in CAN-Bus (based on CDM420-0004)

Operating Instructions CDM425 PROFINET IO

2 Electrical connection

CDM425-00034094 (part no 1048488) for 1 sensor :

This module is based on CDM420-0001.

The Profinet IO Gateway is fixed wired on the RS 232 host port of the sensor.

For further details please refer to CDM420 documentation:

■ CDM420-0001 Operating Instructions (part no. 8010004)

Terminal assignment CDM425:

To mechanical acce

ss the Aux-Port on the lower board of the

CDM425 you have to dismount the fieldbus gateway by opening

the above hex screw.

Operating Instructions CDM425 PROFINET IO

CDM425-10234094: (part no 1050643) for 2 sensors in CAN-Bus, (based on CDM420-0004)

This module is based on CDM420-0004.

The Profinet IO Gateway is fixed wired on the RS 232 host port of the first sensor.

For further details please refer to CDM420 documentation:

■ CDM420-0004 Operating Instructions (part no. 8011155)

Terminal assignment CDM425:

Main board (1.device) upper board (2. device)

Operating Instructions CDM425 PROFINET IO

3 Connecting sensors

At Profinet the devices are identified via the Device name (also named Profinet station name or Profinet

name). This Device name must be unique in the network. Additionally the IP-Address must be unique.

Both values can be set via PLC / Profinet programming system.

The parameterization can be also done via the CLV6xx or via the Web-Interface .

The device can be all times identified with the MAC-Address. The MAC-Address is printed on a label on the

upper side of the field bus gateway.

Operating Instructions CDM425 PROFINET IO

3.1 Connecting CLV6xx Bar Code Scanner

The CLV6xx can be connected as follows. The CLV6xx host port is than connected via the CDM425 to

Profinet. A CLV6xx (V3.32 or higher) can do also the initialization of the CDM425.

- Load factory default parameters in the CLV6xx

- E.g. set trigger to “command” if the PLC should trigger the CLV.

For serial Host of the CLV6xx use default settings:

Operating Instructions CDM425 PROFINET IO

With the CLV6xx the CDM425 can be selected as field bus gateway on the Host-Port. This forces the

scanner to initialize the CDM425 at power on. The CDM425 should be in default setting.

Using this way you can set a unique station name here “scan01” for the CDM425. It is later used as the

main reference to identify the module in Profinet. The name can be free chosen. The complete rules for

Profinet station names are rather complex. For an easy way you can chose a name with max 32 characters,

starting with a letter, containing only standard letters and digits and use “-“ for separation. The name is not

case sensitive. Note

: Since CLV6xx V5.10 a station name rule checker is included in SOPAS-ET.

Activating:

To activate the chosen parameters please save parameter permanent in the CLV6xx and power cycle

scanner and CDM425!

At power up the CLV6xx will initialize the CDM425 and set the name and the IP in the CDM425.

Monitoring:

You can monitor if the CDM425 was correct initialized by looking into the System status of SOPAS-ET.

It must show that the CDM425 was correct detected as “green”. Additional you can see the firmware version

of the CDM425.

Changing IP by the PLC/Webpage:

When the station name is later changed via the Webpage or via the PLC the new name is also transported

back into the scanner. You can see the new name after an upload from SOPAS-ET.

The IP address is at a Profinet systems typically set by the Profinet Controller (the PLC). If you have this

function activated the PLC overwrites the IP address in the scanner and forces this to 0.0.0.0 to indicate that

the Profinet Controller (the PLC) has overwritten it.

You can also set the IP address via DHCP. To use this, your system needs a DHCP server. This is typically

not used in Profinet IO systems.

Avoid Double IP’s:

If a sensor with Ethernet Interface is used please take care that using a CDM425 the IP address of the

sensor has nothing to do with Profinet. But if the sensor is the same network, please take care that the IP

address of the sensor is all times different to the IP from the CDM425.

If e.g. both are at default 192.168.0.1 please use SOPAS-ET-Auto-IP-Scan to change the IP from the sensor.

Or change it at the CDM425 via the PLC-Tools or via the PortVision tool.

Operating Instructions CDM425 PROFINET IO

3.2 Connecting other devices

When connecting a device which can not initialize the CDM425 you have to do a manual parameterization of

the CDM425 by

a) using the PLC-Tools to set only IP-Address and Device name (preferred way) or

b) using the CDM425 webpage (PortVision tool) if it is needed to change all parameters.

Please make sure that the sensor uses a correct format and that the CDM425 is set to the same format.

Preferred is to use the default setting of the CDM425:

RS 232 with 57600 Baud, 8, n, 1.

Here a possible setting for CLV43x:

Than you only have to change the Device name and the IP-Address at the 425, e.g. by the

PLC HW-Config. See chapter 6.1.

If your device needs another settings please refer to chapter 6.4 and 6.5 in the Appendix.

Possible settings for CDM425: (for complete options go online to webpage of CDM425)

 RS232 with 9600 … 57600 Baud

 7/8 Data bits, no/odd/even parity, 1/2 Stop bits

 Data must be framed with STX (Hex 02) and ETX (Hex 03)

Operating Instructions CDM425 PROFINET IO

4 Handling on PLC Side

4.1 Install GSDML file

Install GSDML-File or install the complete sample project (it will install the GSDML automatically).

To install the GSD File chose “Options/Install GSD File …” at the HW-Config.

Additional you may select “Options/Update catalog”.

The CDM425 is than shown in the catalog as follows:

“Profinet / Additional Field Devices / Gateway / Sick / CDM425”:

Operating Instructions CDM425 PROFINET IO

4.2 Mode overview of CDM425

The CDM425 offers since V3.30 three Modes of operation:

The modes can be chosen by selecting the needed part of the GSD file.

Additional it can be chosen if GSD definition V1.0 or V2.1 should be used. Please select the definition which

fits to your PLC / Busmaster. Today normally both definitions can be used.

Displaying of CDM425 in GSD-file when loading into Step 7 HW-Config:

CDM425

Handshake-Mode: (recommended)

 Compatible to Byte-Handshake Mode of CMF400 / CDF 600

 Receiving and Transmitting with max. telegram length of 4000 byte (with blocking)

 The data transfer is done using a handshake with a receive buffer of up to 20 incoming telegrams.

So also a CAN scanner network with Mux / Server with up to 20 devices (1 Mux + 19 Server) can be

connected, without loosing data when all send at the same time.

CDM425 No-Handshake-Mode:

 Compatible to No-Byte-Handshake Mode of CMF400 / CDF 600

 Receiving and Transmitting with max. telegram length of 220 byte

 The max telegram length is limited by the size of the input and output area.

No fragmentation / blocking is done.

 No Handshake is needed on PLC Side.

CDM425 Device-Master-Mode: (not recommended for new installations)

 Compatible to the old CDM425 version V3.01

 Receiving and Transmitting with max. telegram length of 220 byte

 The max telegram length is limited by the size of the input and output area.

No fragmentation / blocking is done.

 No Handshake is needed on PLC Side.

Compatibility with old version V3.01:

The new firmware version (V3.30) of the CDM425 works also with the old GSDML-File.

In this case DM-Mode is active.

The new GSDML-File with a selection of DM-Mode works also with an old firmware version (V3.01) of the

CDM425.

Operating Instructions CDM425 PROFINET IO

4.3 Insert CDM425 in HW-Config

To insert the CDM425 into the system please first select the needed part, e.g. “CDM425 Handshake V2.1”

and put it with drag and drop on to the Profinet line.

By double clicking th

e module you can select the device name which is the main identification on Profinet.

This name must match to the name you have given to the CDM425 using SOPAS-ET or via the PLC tools.

When you activate “Assign IP-Address by IO-Controller” the PLC will set the IP-Address automatically if a

device with the matching Profinet device name was found.

Operating Instructions CDM425 PROFINET IO

Please take care that no double IP addresses are used. When using a Sensor with Ethernet and a CDM

take care that both devices need a different IP address. When you ever have the situation that two devices

have the same IP address, please change one address before you continue. E.g. use SOPAS-ET Auto-IP-

Scan to change the IP from the sensor, or change the IP-Address of the CDM425 via the PLC Tools.

5 CDM425 data modes

With the CDM425 you may choose different data transmission modes. These modes are SICK created and

require the matching partner on PLC side. The implementation of the PLC side is described in the following

chapters.

 HS (HandShake) Mode (recommended) for general use. Compatibility to CDF600/CMF400 (and CLV6xx

'integrated Profinet')

 NH (No-Handshake) Mode is intended for tests or when only short single telegrams must be transported.

 DM (DeviceMaster) Mode is compatible to older CDM425 firmware (not recommended for new

installations).

5.1 CDM425 in Handshake Mode (HS)

CDM425 Handshake-Mode:

 Compatible to Byte-Handshake Mode of CMF400 / CDF 600

 Receiving and Transmitting with max. telegram length of 4000 byte (with blocking)

 The data transfer is done using a handshake with a receive buffer of up to 20 incoming telegrams.

So also a CAN scanner network with Mux / Server with up to 20 devices (1 Mux + 19 Server) can be

connected, without loosing data when all send at the same time.

This mode is in general preferred and can handle a single device also as a complex system like a CAN-

network with one Mux and max 19 Server. The needed byte handshake is just an easy copying of a single

byte. See chapter 5.1.2.

You have to select at least one Input module and one output module for the CDM425 device.

In HS Mode 5 bytes in front of the data field are for administration. So a Module of e.g. 32 byte can hold up to

27 byte of data without using blocking.

Operating Instructions CDM425 PROFINET IO

Insert one Input module and one Output module into the CDM425:

Additional th

e I/O Address must be selected.

The data must be handled consistent, so either set I/O-Address that it is inside your process image or use

the SFC 14/15 for the consistent data handling. The size of the process image can be seen by double

clicking the CPU at the hardware config of S7. For further details please refer to your manufactors

documentation of your Profinet controller.

Example: Here 128 byte process-image size is used at the S7 CPU:

Operating Instructions CDM425 PROFINET IO

5.1.1 Byte Layout Handshake mode (HS)

Address Inputs (data CLV  PLC) Output (data PLC  CLV)

Binary Inputs Binary Outputs

ReceiveCount (counter)



ReceiveCountBack (counter)

TransmitCountBack (counter)



TransmitCount (counter)

ReceiveLenght Lowbyte TransmitLength Lowbyte

ReceiveLenght Highbyte TransmitLength Highbyte

ReceiveData, Byte 1 TransmitData, Byte 1

ReceiveData, Byte 2 TransmitData, Byte 2

…

… …

ReceiveData, Byte n - 5 TransmitData, Byte n – 5

The length of the data area depends of the chosen module from 3 … 220 byte

In HS Mode 5 bytes in front of the data field are for administration. So a Module of e,g, 32 byte can hold up to

27 byte of data without using blocking.

5.1.2 Receive Data

The bus module place the received data in the ReceiveData field and inserts also the ReceiveLength of

them. The data on the serial line must contain an STX at the beginning and an ETX at the end. These

framing characters are stripped and not displayed in the data field to the PLC and also not counted at the

length.

Serial Line: STX a b c ETX  PLC Input range: 3 byte with content a b c

Additional the ReceiveCount value is counted up to indicate that new data was received.

Bytehandshake:

To indicate that the PLC has received the data correctly, the PLC has to answer to the bus module by

copying the ReceiveCount value to the output side to ReceiveCountBack within 10 sec. So the second input

byte must be copied to the second output byte. (Bytehandshake ). When the bus module gets that both

values are identical again, it can send the next data. The ReceiveCount runs from 1 to 255. 0 is skipped

during normal operation.

When the CDM set the value to 0 during operation it indicates that an error has occurred and the counting

has to start new. In this case the PLC must answer with a 0, otherwise the counting did not start again. So

the PLC should copy all times without any condition the ReceiveCount value to ReceiveCountBack.

Longer data telegrams are splitted into blocks (Fragmentation):

When the received data is too long and does not fit into the input area complete, it is automatically splitted

into blocks. The ReceiveLength shows all times the length of the remaining data. At the first block the length

is equal to the complete telegram length. When this block is answered with the byte handshake the next

block is send and the length is counting down.

Example:

Receiving 100 byte with a block size of 32 Byte input (can hold up to 27 byte in one block)

ReceiveCount ReceiveLength ReceiveData

1 100 first 27 data bytes

1 73 next 27 data bytes

1 46 next 27 data bytes

1 19 last 19 data bytes, the rest is filled up with 00

The indication, if a single block was received or a start of a longer fragmentized data, must be done by

checking the ReceiveLength. When the ReceiveLength is longer than the data input size a fragmentation is

done. If it is shorter it is a single telegram.

Operating Instructions CDM425 PROFINET IO

5.1.3 Example 1, Receive Single Block Telegram (HS-Mode):

Input: 16 Byte, Output: 16 Byte, Data telegram with up to 11 Bytes  single block

This can be done by triggering the scanner e.g. via Hardware, so the PLC needs only data receiving.

Time: 1 2 3 4

Comments:

Time 1: First data “CLV6xx-Data” (11 Byte) was received and displayed to PLC with ReceiveCount = 1

Time 2: The PLC has recognized the data and confirms this by copying ReceiveCount to

ReceiveCountBack. Now the CDM is ready for next data.

Time 3: Second data “123456789” (9 Byte) was received by the CDM and displayed to PLC with

ReceiveCount = 2

Time 4: The PLC has recognized the data and confirms this by copying ReceiveCount to

ReceiveCountBack. Now the CDM is ready for next data.

Operating Instructions CDM425 PROFINET IO

5.1.4 Example 2, Receive Multiple Block Telegram (HS-Mode)

Input: 16 Byte, Output: 16 Byte, Data telegram “CLV6xx-12345” with 12 Bytes  splitted into 2 blocks

This can be done by triggering the scanner e.g. via Hardware, so the PLC needs only data receiving.

Time: 1 2/3 4

Comments:

Time 1: First data block “CLV6xx-1234” (first 11 Byte) was received and displayed to PLC with

ReceiveCount = 1. The ReceiveLenth is 12 byte.

Time 2: The PLC has recognized the data and by seeing that 12 byte do not fit into the input range,

it knows that more blocks will follow. It confirms it by copying ReceiveCount to ReceiveCountBack.

Time 3: The CDM sends immediately the next block “5” (only 1 byte left) to the PLC with ReceiveCount = 2

and ReceiveLenth = 1.

Time 4: The PLC has recognized the next block and confirms this by copying ReceiveCount to

ReceiveCountBack. Now the transmission of the complete telegram is finished.

The data length which can be transported depends on the selected input range. Input size – 5  Input block size

The max length of a data telegram is 4000 bytes splitted into multiple blocks.

Operating Instructions CDM425 PROFINET IO

5.1.5 Transmit Data

The PLC can send also data e.g. commands to the CDM/Sensor. This is optional and only needed if any

action like serial triggering should be done to the sensor or connected device.

Data sending and data receiving can be done independent. It is recommended to handle at first the data

receiving and start than to create the sending routine.

To send out some data the data must be set the data at output side of the CDM425. The data must be

inserted without the STX / ETX framing, also the length is counted without the framing characters.

The CDM will add the framing characters on serial line. Example:

PLC Input range: 4 byte with content: s R I 0  Serial Line: STX s R I 0 ETX

The sending is started by counting up the TransmitCount value. The value has to run from 1 … 255 and

must start again than with 1. The 0 must be skipped.

The CDM will answer by copying the TransmitCount to TransmitCountBack to confirm that the data is send

out. Before the next data can be send out the PLC has to wait until these values are equal again.

When TransmitCountBack was set to from the CDM to 0 it indicates that there was an error and the counting

must start new. Than the PLC has to set also the TransmitCount to 0 for about 1 sec to confirm that it was

detected. Than it can start again to send out data.

The reason for an error might be:

 Invalid length of 0 or > 4000 byte

 A transmitting was started with first block but not continued, or incorrect continued.

 When TransmitCount was not counted in correct sequence. It must be 1, 2, 3, … 255, 1, 2, 3, …

Transmitting longer data needs to be splitted into blocks (Fragmentation):

When a longer data telegram must be send out it can be transported into blocks to the CDM.

Therefore start with the first block and set the length all times to the remaining data which needs to be send.

When the block is answered from the CDM with TransmitCountBack as a byte handshake the next block can

be send and the length is counting down. The next blocks have to follow with 10 sec, otherwise a timeout

occurs.

Example:

Sending 100 byte with a block size of 32 Byte output (can hold up to 27 byte in one block)

TransmitCount TransmitLength TransmitData

1 100 first 27 data bytes

2 73 next 27 data bytes

3 46 next 27 data bytes

4 19 last 19 data bytes

Operating Instructions CDM425 PROFINET IO

5.1.6 Example 3, Transmit single block telegram SW-Trigger 21/22 (HS-Mode)

Input: 16 Byte, Output: 16 Byte, Data telegram with 2 bytes “21” / “22” is send (each 2 bytes)

This can be used to trigger a CLV 6xx/4xx from the PLC when the scanner is parameterized to be triggered via

Command / Serial Interface. Here no trigger echo is parameterized, and data output at trigger end.

Time: 1 2/3 4 5 6/7 8

Comments:

Time 1: First data telegram “21” (Trigger start) was send by setting TransmitCount = 1 on output side.

When the CDM has send out the data it confirms this by copying TransmitCount to

TransmitCountBack on input side.

Time 2/3: Second data telegram “22” (Trigger stop) was send by setting TransmitCount = 2 on output side.

When the CDM has send out the data it confirms this to TransmitCountBack.

After trigger stop the result data of the scanner here “1234567890” (10 Byte) was received and

displayed to PLC with ReceiveCount = 1.

Time 4: The PLC has recognized the data and confirms this by copying ReceiveCount to

ReceiveCountBack. Now the CDM is ready for next data.

Time 5: Next data telegram “21” (Trigger start) send with TransmitCount = 3, CDM confirms

Time 6/7: Next data telegram “22” (Trigger stop) send with TransmitCount = 4, CDM confirms

After trigger stop the result data of the scanner here “NoRead” (6 Byte) was received and displayed to

PLC with ReceiveCount = 2.

Time 8: The PLC has recognized the data and confirms this by copying ReceiveCount to

ReceiveCountBack. Now the CDM is ready for next data.

The TransmitCount has to start again with 1 when 255 was reached, so 0 must be skipped.

Operating Instructions CDM425 PROFINET IO

5.1.7 Example 4, Transmit multiple block telegram (HS-Mode)

Input: 16 Byte, Output: 16 Byte, Data telegram “2MC10j1234567890” with 16 Bytes  splitted into 2 blocks

This command is used at CLV6xx to set the condition “Match 1” to Code 128 with content “1234567890”.

The command did not send an answer back.

Time: 1/2 3/4

Comments:

Time 1: First data block of 11 byte was send by setting TransmitCount = 1

with the TransmitLength = 16.

Time 2: When the CDM gots the first data block it confirms this by copying TransmitCount to

TransmitCountBack on input side.

Time 3: Second data block of the last 5 byte was send by counting up TransmitCount = 2

with the TransmitLength = 5.

Time 4: When the CDM gots the second data block it confirms this by copying TransmitCount to

TransmitCountBack on input side.

The TransmitCount has to start again with 1 when 255 was reached, so 0 must be skipped.

The data length which can be transported depends on the selected output range.

Output size – 5  Output block size

Page is loading ...

SICK CDM425-10234094 CDM425-00034094 Connection Modules Operating instructions

SICK CDM425-10234094 CDM425-00034094 Connection Modules Operating instructions

SICK CDM425-10234094 CDM425-00034094 Connection Modules Operating instructions

Related papers

Other documents