Lenze PLC Designer PLC Designer (R2-x) CANopen for Runti User Manual Page 30

  • Download
  • Add to my manuals
  • Print
  • Page
    / 56
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 29
L-force | PLC Designer - CANopen for Runtime Systems
CanDevice
DMS 2.0 EN 05/2009 TD29 29
3 CanDevice
A »PLC Designer« programmable PLC can appear in a CAN network also as a CANopen-slave (also
named CANopen-node, in the following named „CanDevice”).
3.1 Functionality
The CanDevice library together with the CANopen-configurator provide the following functionality for
the user:
- Configuration of the following properties in »PLC Designer«: NodeGuarding/Heartbeat,
Emergency, NodeID and baudrate, on which the device should work.
- Together with the Parameter Manager in »PLC Designer« a default PDO mapping can be created,
which can be modified by the master during run time. The change of the PDO mapping is done
during the configuration phase by the master. By the mapping IEC variables of the application can
be mapped to PDOs.
- The CanDevice library provides an object dictionary, the size of which is determined by »PLC
Designer« during compilation. This dictionary contains all objects describing the CAN device and
additionally those which are defined by the Parameter Manager. In the Parameter Manager
together with the CanDevice only the list types „Parameters” and “Variables” can be used.
- The library manages accesses on the object dictionary, thus acting as SDO server at the bus.
- The library watches the nodeguarding resp. the heartbeat consumer time (only of one producer
each) and sets the corresponding error flags for the application.
- Creation of an EDS-file, describing the configured properties of the CanDevice in a way that the
device can be configured as slave below a CAN master.
The CanDevice library explicitly not
provides the following functionalities which are described in
CANopen. (All possibilities of the CANopen protocol, mentioned here and in the upper paragraph, also
are not implemented) :
- Dynamic SDO, PDO identifier.
- Blocking SDO transfer.
- Implicit generation of emergency messages. Emergency messages always must be created by
the application. For this purpose the library provides a function block, which can be used by the
application.
- Dynamic changes of the PDO properties resp. runtime properties always are updated at the
arrival of a StartNode NMT-message and at each access on an object in the communication
properties of the CanDevice.
Page view 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 55 56

Comments to this Manuals

No comments