User guide

MDX-ETHERNET User Guide 29
Issue : a www.leroy-somer.com
7.3 Mapping conflicts
The Drive indicates if there is a mapping conflict like other MDX-ETHERNET cyclic OUT
channels, analog inputs or other.
7.4 Cyclic data mapping errors
The MDX-ETHERNET module will scan and check the Modbus mapping parameter
configuration for errors during initialisation (ex. Pr 15.32 = ENABLED). If an error is
detected, then the MDX-ETHERNET configuration error detected will be indicated in
mapping status parameter, Pr 15.49. See section 12.8 Cyclic parameter number
(Mapping status) for full details.
7.5 Mapping data sizes
The data size depends on the size of the mapped parameter and if data compression is
turned on or not (see Table 7.6).
Table 7.6 Actual data sizes
Consider the following example:
• Mapping Pr 15.10 to a 32-bit value and Pr 15.11 to a 16-bit value.
• Mapping Pr 15.20 to a 32-bit value and Pr 15.21 to a 1-bit value.
• Data compression turned on (Pr 15.34 set to ENABLED).
• The mapping length is at 2 (Pr 15.39 and Pr 15.40).
The following settings is show:
•Pr 15.38 = 6 (4 + 2),
•Pr 15.41 = 6 (4 + 2).
Pr 15.38 and Pr 15.41 allow to know number of data bytes for de input and output
mapping.
Input cyclical data bytes
output cyclical data bytes
7.6 Disabling mappings
Any unused mapping parameters (Pr 15.10 to Pr 15.19 and Pr 15.20 to Pr 15.29) are
disable by the number of parameter in the mapping (Pr 15.39 and Pr 15.40).
Parameter size (bits)
Actual data size (bits)
compression enabled (Pr 15.34)
Actual data size (bits)
compression disabled (Pr 15.34)
116 32
816 32
16 16 32
32 32 32
Pr 15.38
Default 8
Range 0 to 127
Access RO
Pr 15.41
Default 8
Range 0 to 127
Access RO
- Having unmapped channels between valid mapped channels is not permitted.
- Having unmapped channels (mapping to 0) is not permitted if the number of
parameter (Pr 15.39 and Pr 15.40) include this unmapped channel.
NOTE