Lenze PLC Designer PLC Designer (R2-x) CANopen for Runtime Systems - Manual (Page 5)

L-force | PLC Designer - CANopen for Runtime Systems
About this documentation
4 DMS 2.0 EN 05/2009 TD29

1.3 Trademarks
Microsoft, Windows and Windows NT are either registered trademarks or trademarks of Microsoft
Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in
the U.S.A. and/or other countries.
All other product names contained in this online documentation are trademarks of the corresponding
owners.
1.4 CANopen terms and Lenze implementation
According to CANopen in a CAN network there are no masters and slaves.
According to CANopen there is a NMT-Master, a configuration master etc., always keeping in mind,
that all participants in a CAN network have equal rights.
The Lenze implementation proceeds on the assumption that a CAN network serves as periphery of a
»PLC Designer«-programmable controller. As a consequence »PLC Designer« in the CAN
configurator names a PLC “CAN-Master”. This master is NMT-master and configuration master.
Normally the PLC will mind that the network can be taken into operation. The master starts the
particular nodes which are known to it via the configuration. These nodes are named “slaves”.
In order also to approach the master to the status of a CANopen-node, an object dictionary for the
master was introduced. The master also can act as a SDO server, not anymore only as a SDO-Client
in the configuration phase of the slave. (Further details in a later chapter.)