Lenze · I/O system 1000 · Reference Manual · DMS 5.0 EN · 09/2016 · TD17 408
8 DeviceNet communication
8.2 Access to the I/O system 1000
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
8.2.2 Access to parameter data
Your configuration tool also enables you to parameterise your I/O compound modules. For this
purpose, the DeviceNet bus coupler must be located actively at the bus.
Your configuration tool serves to parameterise your modules in string form via the corresponding
DeviceNet slot. you can also transfer the current parameters from the modules to the configuration
tool, adapt and rewrite them.
Rules for the parameters
• Each DeviceNet must be parameterised with a string.
• Within the string, each parameter consists of a type with attached value.
• The parameters must be separated by a space.
• Only parameters written in small letters are supported.
Depending on the type, you can indicate hexadecimal, decimal or binary values as parameters:
Example: The I/O compound module EPM-S405 has 18 bytes of parameter data. For
parameterisation with the default values, the following string occurs:
x00 x00 x00 x00 x00 x02 xC1 x02 2x7FFF 2x8000 xC1 x02 2x7FFF 2x8000
Type Meaning Value as Example string
x 1 byte Hexadecimal xhh
2x 2 bytes Hexadecimal 2xhhhh
4x 4 bytes Hexadecimal 4xhhhhhhhh
+ 1 byte decimal positive +ddd
2+ 2 bytes decimal positive 2+ddddd
4+ 4 bytes decimal positive 4+dddddddddd
- 1 byte decimal negative -ddd
2- 2 bytes decimal negative 2-ddddd
4- 4 bytes decimal negative 4-dddddddddd
b 1 byte Binary xbbbbbbbb
Note!
If the parameter data does not match the hardware structure, the DeviceNet bus coupler
changes to an error status and signalises it via its status LEDs.
Modules that have not yet been parameterised will be automatically supplied with their
default values as soon as a read access from the configuration tool is executed.