2
0
1
6
-0
9
42
Operation and communication
Shielding
Ensure continuous shielding when cabling the reader. For details of the suitable fieldbus
cables, see chapter 2.3.
Startup Behavior
After switch-on, the reader in a CANopen network passes through several operating states.
1.
Initialization
Startup process of the reader.
2.
Preoperational
Reader state on completion of the startup process. The reader reports this state to the
NMT master.
3.
Operational
Operative state of the reader. The NMT master sets this state via an NMT start node tele-
gram once it has received the preoperational message from the reader.
Exchange of Process Data
Within the CANopen network, process data is exchanged via Process Data Objects (PDO).
See chapter 5.1.1. Process data objects are divided into:
■
Transmit PDOs (TxPDO)
Process data objects that transmit input data and diagnostic data.
■
Receive PDOs (RxPDO)
Process data objects that transmit output data.
The first 4 PDOs per transmit or receive data packet transmit the default CAN identifier. All
other PDOs of a data packet can be configured by the user.
Communication Types
In the CANopen network, various communication types are specified for process data objects.
The communication type of each PDO is controlled via the "Transmission Type" parameter. The
"Transmission Type" parameter is defined in subindex 2 of the communication parameter
object (from 0x1400) and is transmitted during the startup process via an SDO. See chapter
5.1.1.
The reader supports the following communication types:
"Transmission Type"
parameter
Transmission
Description
0
Event-controlled
Synchronous
TxPDO
: Data is detected upon receipt of a
SYNC (=
sync
hronization object). Data is
transmitted only in the event of a change.
RxPDO
: Data is sent in an event-controlled
manner and adopted in a SYNC.
1
Cyclic
Synchronous
Data is adopted and transmitted cyclically at
each nth SYNC.
n = 1 ... 240.
n can be individually assigned for each PDO to
control transmission cycles.
241 ... 251
Reserved
252 (TxPDO only)
Synchronous
RTR (=
r
emote
t
ransmission
r
equest)
Data is detected upon receipt of a SYNC. Data
is sent via RTR only on request.
253 (TxPDO only)
Asynchronous
RTR
Data is detected and sent via RTR only on
request.