![IFM PDM360NG Series System Manual Download Page 246](http://html1.mh-extra.com/html/ifm/pdm360ng-series/pdm360ng-series_system-manual_3875026246.webp)
ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
CAN in the PDM360
CAN POUs to CANopen
246
CANopen master
Differentiation from other CANopen libraries ............................................................................ 246
Create a CANopen project ........................................................................................................ 247
Add and configure CANopen slaves ......................................................................................... 249
Master at runtime ...................................................................................................................... 253
Start the network ....................................................................................................................... 255
Network states........................................................................................................................... 256
1859
Differentiation from other CANopen libraries
8015
The 3S stack *) is not used.
The libraries are based on the specifications of CiA DS301, V402.
*) 3S = Smart Software Solutions,
CoDeSys
For users the advantages of the CoDeSys CANopen library are as follows:
The complete system contains the CANopen configurator and integration in the development
system.
The resources of the target system are used carefully. Memory is allocated depending on the used
configuration, not for a maximum configuration.
Automatic updating of the inputs and outputs without additional measures.
The following functions defined in CANopen are at present supported by the
ifm
CANopen library:
Transmitting PDOs:
master transmits to slaves (slave = node, device)
Transmitting event-controlled (i.e. in case of a change), time-controlled (RepeatTimer) or as
synchronous PDOs, i.e. always when a SYNC was transmitted by the master. An external SYNC
source can also be used to initiate transmission of synchronous PDOs.
Receiving PDOs:
master receives from slave
Depending on the slave: event-controlled, request-controlled, acyclic and cyclic.
PDO mapping
Assignment between a local object directory and PDOs from/to the CANopen slave (if supported
by the slave).
Transmitting and receiving SDOs
Automatic configuration of all slaves via SDOs at the system start.
Application-controlled transmission and reception of SDOs to/from configured slaves.
Synchronisation
Automatic transmission of SYNC messages by the CANopen master.
Nodeguarding
Automatic transmission of guarding messages and lifetime monitoring for every slave configured
accordingly.
We recommend: It is better to work with the heartbeat function for current devices since then the
bus load is lower.
Heartbeat
Automatic transmission and monitoring of heartbeat messages.