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

L-force | PLC Designer - CANopen for Runtime Systems
CanDevice
36 DMS 2.0 EN 05/2009 TD29

[1018]
SubNumber=4
ParameterName=Vendor identification
[1018sub0]
ParameterName=Number of entries
ObjectType=0x7
DataType=0x5
AccessType=ro
DefaultValue=2
PDOMapping=0
[1018sub1]
ParameterName=VendorID
ObjectType=0x7
DataType=0x7
AccessType=ro
DefaultValue=0x0
PDOMapping=0
[1018sub2]
ParameterName=Product Code
ObjectType=0x7
DataType=0x7
AccessType=ro
DefaultValue=0x0
PDOMapping=0
For the meaning of the particular objects please see the CANopen specification DS301.
The EDS-file contains, besides the mandatory entries, the definitions for SYNC, Guarding, Emergency
and Heartbeat. If this objects are not used, as Guarding and Heartbeat in the shown example, the
default values are set to 0. But these objects are available at runtime in the object dictionary of the
CanDevice, thus they are described nevertheless in the EDS-file.
Analogue this is valid for the (not listed here) entries for the communication and mapping parameters.
Always all 8 possible (bit mapping is not supported by the library!) subindices of the mapping objects
0x16xx resp. 0x1Axx are available, but potentially not regarded in subindex 0.
Note: With entry FixedNumOfPDOs=1 in the cfg-file in the CANDEVICE section, the mapping objects,
if e.g. no default mapping is predefined, always are set up for 4 PDOs, so that at runtime 4 PDOs are
available for the mapping of variables. Subindex 0 of the mapping objects however is pre-set with 0,
because in case no default mapping is defined none of the objects is allocated.