
Operating Instructions
Chapter
6
Flexi Soft Gateways
8012664/XB29/2013-06-11
© SICK AG • Industrial Safety Systems • Germany • All rights reserved
149
Subject to change without notice
Fieldbus gateways
SDO 1400…1403: RxPDO communication parameters
Using SDO 1400 to 1403 the communication parameters for the RxPDOs 1 to 4 are
configured. E.g. SD0 1400 defines the parameters for RxPDO 1 etc.
Subindex Mapping
Format
Description
1
COB ID
UDINT
CAN identifier for this PDO, read-only
2
Receive mode
SINT
Fix 255 (asynchronous mode)
The receive mode (read-write) defines how the PDO shall be received. For the RxPDOs the
receive mode is set to 255 (asynchronous mode). In this mode the data of a received
RxPDO will be routed immediately to the outputs.
If the receive mode is set to another value than 255, an error code is generated (abort
code 0609 0030h, invalid parameter value).
SDO 1600…1603: RxPDO mapping parameters
This SDO can not be used since the RxPDO mapping is done using the Flexi Soft Designer.
See also Tab. 110 and Tab. 112.
SDO 1800…1803: TxPDO communication parameters
Using SDO 1800 to 1803 the communication parameters for the TxPDOs 1 to 4 are
configured. E.g. SD0 1800 defines the parameters for TxPDO 1 etc.
Subindex Mapping
Format
Description
1
COB ID
UDINT
CAN identifier for this PDO, read-only
2
Transmission type
SINT
Defines when the PDO is to be sent
5
Event timer
UINT
In ms
The transmission type is set to 255 (asynchronous mode, event triggered) as a default for
all TxPDOs.
The event timer contains the rate in ms for the cyclic transmission of the TxPDO.
TxPDO transmission types
TxPDO
Synchronous
Asynchronous
RTR
1, 2, 3, 4
0, 1…240
254, 255
253
If the transmission type is set to an invalid value, an error code is generated (abort code
0609 0030h, invalid parameter value).
Synchronous:
The synchronous transmission type 0 means that the TxPDO will be sent
after the reception of a Sync message, but only if data has changed. The synchronous
transmission types n = 1…240 define that the TxPDO will be sent after the reception of the
n
th
Sync message.
Asynchronous, event triggered on change of state:
The asynchronous transmission type
255 (without configured event timer) means that the TxPDO will be sent each time if at
least one input bit has changed that has been mapped on this PDO.
Asynchronous, event triggered on timer event:
The asynchronous transmission type
254/255 (with configured event timer) defines that the TxPDO will be sent each time the
event timer has expired. E.g. a value of 500 for the event timer means that the gateway
will send the corresponding TxPDO each 500 ms.
RTR, on request:
The transmission type 253 defines that the TxPDO can be polled via RTR
(remote transmission request). This requires a CAN message with DLC = 0, RTR = 1 and
the COB ID of the TxPDO to the gateway. The gateway will then respond with the requested
TxPDO.
Tab. 122: SDO 1400…1403
contents
Note
Tab. 123: SDO 1800…1803
contents
Tab. 124: TxPDO
transmission types
Note