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

L-force | PLC Designer - CANopen for Runtime Systems
Appendix
50 DMS 2.0 EN 05/2009 TD29

F7: My customer specific object dictionary starts at 2000 and ranges to the default I/O-range
(6400). Will this size be a problem?
A: No, as long as the used controller has enough memory for those variables. If you are using a
target system with a C16x-controller (65K segment limit) then a variable only can have a size of
64K. ODEntries is an array of structures, each needs 12 Bytes. Thus theoretically maximum
65536 / 12 = 5461 entries can be created. But due to the fact that on a C16x system the
module, which initializes all variables at once, also cannot be bigger than 64K, the number of
entries is considerably lower, about 500 to 1000, strongly depending on the rest of the
application.
F8: As from index 4000,0 I need 130 entries of strings of each 32 characters. Will this be a
problem? How do I get the strings into the object dictionary?
A: This is to be done like for all other variables. The strings must be IEC variables, then you can
enter them like numeric variables via the Parameter-Manager and can access them via SDO
transfers.
F9: Can you write from „outside“ (i.e. from the master) to „my“ mapping table (i.e. in my
object dictionary)?
A: see chap. 3.5 Modifying the default mapping by the master configuration
The given PDO-Mapping (in the CanDevice configuration) can be modified by the master within
certain confines. The rule ist hat the CanDevice is not able to create new object dictionary
entries, which are not yet available in the standard mapping (Default PDO-Mapping in ther
CanDevice configuration). Thus e.g. for a PDO, which contains a mapped object in the default
PDO mapping, no second object can be mapped in the master configuration..
So the mapping modified in the master configuration at maximum can contain those PDOs
which are available in the standard mapping. Within those PDOs there are 8 mapping entries
(subindices).
Possible errors which might occur in this context, will not be indicated, but the redundant PDO
definitions / redundant mapping entries will be treated as if they were not existing.
In the master the PDOs always must be arranged starting at 16#1400 (Receiving-PDO
communication parameter) resp. 16#1800 (Sending-PDO communication parameter) and must
gaplessly follow each other.
The standard mapping of the CanDevice always is available after having loaded the program. It
depends on the master configuration, whether non-available mappings (available in the master
configuration, but not available in the standard configuration) will explicitly be overwritten by the
master.
F10; How many PDOs are allowed?
A: There is only a limit given by the memory space, but no systematic limit.