This documentation describes the function blocks that are contained in the
"LenzeIo1000Drv" function library. These function blocks enable the access of Lenze PLC
products (e.g. 9400
ServoPLC) to the decentralised I/O system 1000.
Note!
The "LenzeIo1000Drv" is exclusively suitable for Lenze-PLCs the project planning
environment of which is not
Functional survey
Loading of the default setting of the L-force I/O system 1000
Parameter setting of the I/O compound modules (analog inputs and outputs,
temperature measurement, counters, encoder evaluation, pulse width modulation)
Function library "LenzeIo1000Drv"
About this documentation
provided with an *.eds import!
Setting of the communication-relevant parameters in the I/O system
Coordination of the process communication between PLC and I/O system
Validity information
The information given in this documentation is valid for the following function library:
Function libraryFrom version
LenzeIo1000DrvVxx.libV1.0
Document history
VersionDescription
1.007/2011TD05 First edition for LenzeIo1000DrvV10.lib
Tip!
The "LenzeIo1000DrvVxx.lib" library version can be queried via the following global
constants:
• C_wLenzeIo1000DrvVersionER: Enabled major version
• C_wLenzeIo1000DrvVersionEL: Enabled minor version
• C_wLenzeIo1000DrvVersionIR: Internal minor version
• C_wLenzeIo1000DrvVersionBN: Internal build number
DMS 1.0 EN - 07/2011 - TD05L3
Page 4
Function library "LenzeIo1000Drv"
About this documentation
Conventions used
1.1Conventions used
This documentation uses the following conventions to distinguish between different types
of information:
Type of informationWritingExamples/notes
Numbers
Decimal separatorPointThe decimal point is always used.
Text
Program name» «The Lenze PC software »PLC Designer«...
WindowItalicsThe Message window ... / The Options dialog box...
Variable identifierBy setting bEnable to TRUE...
Control elementBoldThe OK button... / The copy command... / The
Sequence of menu
commands
Shortcut<Bold>Press <F1> to open the online help.
Program codeCourier
KeywordCourier bold
Example: 1234.56
Properties tab... / The Name input field...
If several commands must be used in sequence to
carry out a function, then the individual commands
are separated by an arrow: Select File
If a key combination is required for a command, a "+"
is inserted between the key identifiers: Use
<Shift>+<ESC>...
IF var1 < var2 THEN
a = a + 1
END IF
Open to...
HyperlinkUnderlined
Symbols
Page reference ( 4)Optically highlighted reference to another page. It is
Step-by-step instructions
Optically highlighted reference to another topic. It is
activated with a mouse click in this online
documentation.
activated with a mouse click in this online
documentation.
Step-by-step instructions are indicated by a
pictograph.
4LDMS 1.0 EN - 07/2011 - TD05
Page 5
1.2Definition of notes used
The following signal words and symbols are used in this documentation to indicate
dangers and important information:
Safety instructions
Layout of the safety instructions:
Danger!
(characterises the type and severity of danger)
Note
(describes the danger and gives information about how to prevent dangerous
situations)
Function library "LenzeIo1000Drv"
About this documentation
Definition of notes used
PictographSignal wordMeaning
Danger!Danger of personal injury through dangerous electrical voltage
Danger!Danger of personal injury through a general source of danger
Stop!Danger of property damage
Application notes
PictographSignal wordMeaning
Note!Important note to ensure trouble-free operation
Reference to an imminent danger that may result in death or serious personal
injury if the corresponding measures are not taken.
Reference to an imminent danger that may result in death or serious personal
injury if the corresponding measures are not taken.
Reference to a possible danger that may result in property damage if the
corresponding measures are not taken.
Tip!Useful tip for simple handling
Reference to another document
DMS 1.0 EN - 07/2011 - TD05L5
Page 6
Function library "LenzeIo1000Drv"
System requirements
2System requirements
Software
The function library can be used with the following Lenze software:
ProductType designationVersion
Drive PLC Developer StudioESP-DDS2-x2.x
PLC Designer V22.2 or higher
PLC Designer V3ESPEVPDxxxxxx3.x
Supported target systems
Product rangeType designationHardware versionFrom software version
Drive PLCEPL-102001A or higher2.x
9300 Servo PLCEVS93xx-EI
EVS93xx-ET
ECSECSxA1B or higher7.x
9400 ServoPLCE94AxPExxxx2A or higher2.x
2M or higher2.x
Required libraries for use in »Drive PLC Developer Studio«
with Drive PLC/9300 Servo PLC/ECS:
Unless already available, insert the following libraries into the library management (menu
WindowLibrary management):
CANopenSdoDrvV10.lib
LenzeTICan9300V10.lib
LenzeIo1000DrvV10.lib
LenzeConversionBoxV10.lib (optional)
Note!
Before the "LenzeTICan9300V10.lib" library is inserted into the library manager,
the CAN_Management system block must be implemented into the Control configuration.
If the CAN_Management system block is missing or implemented subsequently,
a compilation error may be caused during the project compilation.
Remedy:
implement the CAN_Management system block and re-insert the library into
the library manager.
Remove "LenzeTICan9300V10.lib" library from the library manager,
6LDMS 1.0 EN - 07/2011 - TD05
Page 7
Function library "LenzeIo1000Drv"
System requirements
Required libraries for use in the »PLC Designer« with 9400 ServoPLC:
Unless already available, insert the following libraries into the library management (menu
Project planning concept
Parameterisation and process data blocks
3Project planning concept
The user is provided with suitable function blocks by the "LenzeIo1000Drvlib" library to
enable support of the decentralised I/O system through Lenze PLC products These function
blocks are implemented in an IEC 61131 program and serve both for parameterising the I/
O system and for process data processing. They provide digital and analog input and
output information of the I/O system. Configurations of the user via user codes are not
required.
3.1Parameterisation and process data blocks
The "LenzeIo1000Drvlib" library contains two types of function blocks:
1. Parameterisation blocks
2. Process data blocks
Parameterisation blocks
Parameterisation blocks allow the modification of index information in the decentralised
I/O system and the transmission of specified data. These data are transmitted only once to
the I/O system during the initialisation phase..
The parameterisation blocks for modules and monitoring functions are required for
individual parameter setting of analog modules, communication monitoring, etc.
The parameterisation blocks communication settings (L_io1000ParPDO15
L_io1000ParPDO610
) are mandatory for data exchange between PLC and I/O system.
and
Note!
In case of parameterisation blocks with the same bus node address at the
byNodeAdr input, the bExecute inputs must not be set to TRUE at the same time.
The parameter setting of the modules and the communication settings of a bus
coupler have to be started successively.
Process data blocks
Process data blocks are required for transmitting and receiving I/O data between PLC and
I/O system. The process data blocks L_io1000Data15
evaluate and process the current process data information of the inputs of the I/O system
in the PLC program. Information and data of the PLC control can be transmitted to the
process via the output modules of the I/O system.
and L_io1000Data610 serve to
8LDMS 1.0 EN - 07/2011 - TD05
Page 9
3.2Initialisation of the CAN driver
The "LenzeIo1000Drv.lib" function library for the L-force I/O system 1000 is based on a
library for transmitting and receiving CAN objects. Depending on the PLC version, the "CAN
on board" or an optional fieldbus card can be used as communication channel.
9400 ServoPLC
For using the "LenzeCanMsg.lib" library, an initialisation of the CAN driver with L_CanInit
function block call is required. This function block must only be called once. Thus, best use
the "PLC_START" system event for calling this function.
The L_CanInit function block outputs information on the communication channel used via
its dwHandle output. This information must be provided to the blocks of the
"LenzeIo1000Drv.Lib" via the dwHandle input.
Drive PLC, 9300 Servo PLC, ECS
For using the "LenzeCanDrv.lib" library, an initialisation of the CAN driver with the
L_CanInit function call is required. This function must only be called once. Thus, best use
the system POU "PLC_ColdStart" for calling this function.
Function library "LenzeIo1000Drv"
Project planning concept
Initialisation of the CAN driver
The L_CanInit function returns information on the communication channel used via the
dwHandle variable. This information must be provided to the blocks of the
"LenzeIo1000Drv.Lib" via the dwHandle input.
DMS 1.0 EN - 07/2011 - TD05L9
Page 10
Function library "LenzeIo1000Drv"
Project planning concept
Minimum configuration
3.3Minimum configuration
For implementing the I/O system, a minimum configuration must be carried out. It consists
of a parameterisation block L_io1000ParPDO15
relationships and a process data block L_io1000Data15
information.
The parameterisation block must be connected to the process data block as follows:
for parameterising the communication
for evaluation the input/output
The parameterisation block does not have to be executed in the same task as the
process data block. In this case, the outputs of the parameterisation block must be
connected to the inputs of the process data block.
10LDMS 1.0 EN - 07/2011 - TD05
Page 11
4Function blocks
Function blockFunction
L_io1000ParAiDc
L_io1000ParAiTemperature
L_io1000ParAoDc
L_io1000ParCounterEPMS600
L_io1000ParCounterEPMS601
L_io1000ParCounterEPMS602
L_io1000ParCounterEPMS603
L_io1000ParCounterEPMS604
L_io1000ParRestore
L_io1000ParPDO15
L_io1000ParPDO610
L_io1000ParComGuarding
L_io1000Data15
L_io1000Data610Process data transfer PDO6 ... PDO10
This FB serves to load the default setting into the I/O system.
A FALSE/TRUE edge at the bExecute input causes the command to be sent to the I/O
system.
The dnState output shows the transmission status.
Note!
If the PLC has the task to completely parameterise the I/O system, this FB must
be called first (before any other parameter blocks).
L_io1000ParRestore
⎯ bExecutebDone ⎯
⎯ dwHandlednState ⎯
⎯ byNodeAdr
Inputs
Identifier/data typeInformation/possible settings
bExecute
dwHandle
DWORD
byNodeAdr
FALSEÊTRUE Load default setting in I/O system
BOOL
• 9400 ServoPLC: Handle created by FB L_CanInit
• Drive PLC, 9300 Servo PLC, ECS: 10
1 ... 127 CAN node address of the I/O system
BYTE
Outputs
Identifier/data typeValue/meaning
bDone
BOOL
dnState
38LDMS 1.0 EN - 07/2011 - TD05
Status
DINT
TRUE Default setting has been loaded into the I/O system
-1000 Error while executing the internal block for writing CAN indices
-1002 Wrong value at the dwHandle input
-1003 byNodeAdr input is not in valid range
-1006 Writing of a wrong CAN index
-1007 Timeout while writing a CAN index of the I/O system
-1100 Error while writing a parameter of the I/O system
-1101 Output buffer is full
Page 39
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParRestore - Load default setting in I/O system
Sequence
For accepting the reset communication setting, the NMT command "Reset Node" is sent to
the I/O system. The I/O system re-initialises and returns a boot-up telegram as soon as it is
in the "Pre-Operational" status again. Only if the FB receives this boot-up telegram, loading
of the default setting is completed.
Note!
After sending the NMT command "Reset Node" to the I/O system, the FB has to
receive the boot-up telegram within 10 s, otherwise a timeout error will be
output at the dnState output.
DMS 1.0 EN - 07/2011 - TD05L39
Page 40
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
4.10L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
Call possible in:; Cyclic task
Interrupt task
This FB serves to set communication-relevant parameters for data exchange between PLC
and I/O system via the process data objects PDO1 ... PDO5.
Via 3 or 4 input values, a transmit/receive object is parameterised.
The DataTo_IOData15 output serves to transmit fixed-structure information to the
L_io1000Data15
A FALSE/TRUE edge at the bExecute input starts the parameter setting.
The dnState output shows the parameter setting status.
• In order to completely parameterise the I/O system 1000, the
parameterisation blocks can be linked (bDone output connected to bExecute
input of the next FB) or executed successively in a sequencer.
• If only a maximum of 5 PDOs are required for communication, the
FB L_io1000ParPDO15 should be executed last in the sequencer as this FB
serves to save the parameter set of the parameter set.
• Deactivate all PDOs that are not required for communication. This saves
runtime resources of the PLC.
40LDMS 1.0 EN - 07/2011 - TD05
Page 41
Function library "LenzeIo1000Drv"
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
L_io1000ParPDO15
⎯ bExecutebDone ⎯
⎯ dwHandlednState ⎯
⎯ byNodeAdrDataTo_IOData15 ⎯
⎯ bStoreParameter
⎯ wCobID_RxPDO1
⎯ byTransmissionType_RxPDO1
⎯ tCycleTime_RxPDO1
⎯ wCobID_RxPDO2
⎯ byTransmissionType_RxPDO2
⎯ tCycleTime_RxPDO2
⎯ wCobID_RxPDO3
⎯ byTransmissionType_RxPDO3
⎯ tCycleTime_RxPDO3
⎯ wCobID_RxPDO4
⎯ byTransmissionType_RxPDO4
⎯ tCycleTime_RxPDO4
⎯ wCobID_RxPDO5
⎯ byTransmissionType_RxPDO5
⎯ tCycleTime_RxPDO5
⎯ wCobID_TxPDO1
⎯ byTransmissionType_TxPDO1
⎯ tInhibitTime_TxPDO1
⎯ tCycleTime_TxPDO1
⎯ wCobID_TxPDO2
⎯ byTransmissionType_TxPDO2
⎯ tInhibitTime_TxPDO2
⎯ tCycleTime_TxPDO2
⎯ wCobID_TxPDO3
⎯ byTransmissionType_TxPDO3
⎯ tInhibitTime_TxPDO3
⎯ tCycleTime_TxPDO3
⎯ wCobID_TxPDO4
⎯ byTransmissionType_TxPDO4
⎯ tInhibitTime_TxPDO4
⎯ tCycleTime_TxPDO4
⎯ wCobID_TxPDO5
⎯ byTransmissionType_TxPDO5
⎯ tInhibitTime_TxPDO5
⎯ tCycleTime_TxPDO5
Function blocks
DMS 1.0 EN - 07/2011 - TD05L41
Page 42
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
TRUE Save parameter set at the end of the parameterisation process.
BOOL
Identifier
for PDO1 ... PDO5 (PLC I/O system)
for PDO1 ... PDO5 (I/O system PLC)
Transmission mode
for PDO1 ... PDO5 (PLC I/O system)
for PDO1 ... PDO5 (I/O system PLC)
BYTE
Cycle time
for PDO1 ... PDO5 (PLC I/O system)
for PDO1 ... PDO5 (I/O system PLC)
TIME
TIME
0 ... 65535 Cycle time in [ms]
Blocking time
for PDO1 ... PDO5 (I/O system PLC)
0 ... 65535 Blocking time in [ms]
Then the NMT command "Reset Node" is sent to the I/O system.
0 Automatic allocation of the identifiers
> 0 Value of the set identifier
0 Event-controlled
1 Time-controlled
2 Event-controlled with higher-level cycle time
3 PDO deactivated
( 45)
42LDMS 1.0 EN - 07/2011 - TD05
Page 43
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
Outputs
Identifier/data typeValue/meaning
bDone
dnState
BOOL
Status of parameter setting
DINT
• When the function has been executed successfully, the value "0" is output.
TRUE Parameter setting completed successfully
-1000 Error while executing the function block
-1003 byNodeAdr input is not in valid range
-1005 Wrong value at wCobID_RxPDO1 input
-1006 Wrong value at byTransmissionType_RxPDO1 input
-1007 Cycle time at tCycleTime_RxPDO1 input > 65535 ms
-1008 Wrong value at wCobID_RxPDO2 input
-1009 Wrong value at byTransmissionType_RxPDO2 input
-1010 Cycle time at tCycleTime_RxPDO2 input > 65535 ms
-1011 Wrong value at wCobID_RxPDO3 input
-1012 Wrong value at byTransmissionType_RxPDO3 input
-1013 Cycle time at tCycleTime_RxPDO3 input > 65535 ms
-1014 Wrong value at wCobID_RxPDO4 input
-1015 Wrong value at byTransmissionType_RxPDO4 input
-1016 Cycle time at tCycleTime_RxPDO4 input > 65535 ms
-1017 Wrong value at wCobID_RxPDO5 input
-1018 Wrong value at byTransmissionType_RxPDO5 input
-1019 Cycle time at tCycleTime_RxPDO5 input > 65535 ms
-1020 Wrong value at wCobID_TxPDO1 input
-1021 Wrong value at byTransmissionType_TxPDO1 input
-1022 Blocking time at tInhibitTime_TxPDO1 input > 65535 ms
-1023 Cycle time at tCycleTime_TxPDO1 input > 65535 ms
-1024 Wrong value at wCobID_TxPDO2 input
-1025 Wrong value at byTransmissionType_TxPDO2 input
-1026 Blocking time at tInhibitTime_TxPDO2 input > 65535 ms
-1027 Cycle time at tCycleTime_TxPDO2 input > 65535 ms
Function library "LenzeIo1000Drv"
Function blocks
1 Parameter setting started
0 Parameter setting completed successfully
DMS 1.0 EN - 07/2011 - TD05L43
Page 44
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
Identifier/data typeValue/meaning
dnState
DataTo_IOData15
io1000_ParPDO15
Status of parameter setting (continuation)
DINT
-1028 Wrong value at wCobID_TxPDO3 input
-1029 Wrong value at byTransmissionType_TxPDO3 input
-1030 Blocking time at tInhibitTime_TxPDO3 input > 65535 ms
-1031 Cycle time at tCycleTime_TxPDO3 input > 65535 ms
-1032 Wrong value at wCobID_TxPDO4 input
-1033 Wrong value at byTransmissionType_TxPDO4 input
-1034 Blocking time at tInhibitTime_TxPDO4 input > 65535 ms
-1035 Cycle time at tCycleTime_TxPDO4 input > 65535 ms
-1036 Wrong value at wCobID_TxPDO5 input
-1037 Wrong value at byTransmissionType_TxPDO5 input
-1038 Blocking time at tInhibitTime_TxPDO5 input > 65535 ms
-1039 Cycle time at tCycleTime_TxPDO5 input > 65535 ms
-1100 Error when sending the reset node telegram to the I/O system
-1101 Error when receiving the boot-up telegram from the I/O system
-1102 Timeout when receiving the boot-up telegram from the I/O system
-1103 Error when sending the start remote node telegram to the I/O
system
-2000 Error while executing the internal block for writing CAN indices
-2002 Wrong value at the dwHandle input
-2003 Wrong value at the byNodeAdr input
-2006 Writing of a wrong CAN index
-2007 Timeout while writing a CAN index of the I/O system
-2100 Error while writing a parameter of the I/O system
-2101 Output buffer is full
Communication-relevant parameters for the process data objects PDO1 ... PDO5
• Output for transmitting the structure data to the L_io1000Data15 process data
block.
44LDMS 1.0 EN - 07/2011 - TD05
Page 45
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO15 - Communication settings PDO1 ... PDO5
Automatic allocation of the identifiers
For the process data objects PDO1 ... PDO5, the identifiers can be automatically allocated
as a function of the node address. If an automatic allocation is required, the value "0" has
to be applied at the corresponding wCobID_... input. In this case, the identifier is calculated
as follows:
The basic identifiers are defined block-internally:
Process data objectBasic identifier
RxPDOs (PLC I/O system)TxPDOs (I/O system PLC)
PDO1835836
PDO2840841
PDO3845846
PDO4850851
PDO5855856
Example for RxPDO1 and node address 3: Identifier = 835 + 3 = 838
If a value higher than "0" is given at the wCobID_... input, the applied value is used as
identifier for the corresponding PDO instead.
Note!
If several I/O systems (stations) at the system bus are parameterised via the
FB L_io1000ParPDO15 with standard values, an identifier collision may occur
between the individual PDOs of these stations. Hence, check the identifiers used.
Saving the parameter set in the I/O system safe against mains failure
If the bStoreParameter input is set to TRUE, the parameter set of the I/O system will be
saved safe against mains failure at the end of the parameterisation process.
For accepting the communication setting, the NMT command "Reset Node" is sent to the
I/O system. The I/O system re-initialises and returns a boot-up telegram as soon is it is in
the "Pre-Operational" status again. After the boot-up telegram has been received, the
bDone output of the FB is set to TRUE.
Note!
• Only Global Drive (e.g. Drive PLC): For sending the NMT telegram, the
controller has to be in the "Operational" CAN status. Hence, the controller has
to be parameterised as CAN master.
• After sending the NMT command "Reset Node" to the I/O system, the FB has
to receive the boot-up telegram within 10 s, otherwise a timeout error will be
output at the dnState output.
DMS 1.0 EN - 07/2011 - TD05L45
Page 46
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
4.11L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
Call possible in:; Cyclic task
Interrupt task
This FB serves to set communication-relevant parameters for data exchange between PLC
and I/O system via the process data objects PDO6 ... PDO10.
Via 3 or 4 input values, a transmit/receive object is parameterised.
The DataTo_IOData610 output serves to transmit fixed-structure information to the
L_io1000Data610
A FALSE/TRUE edge at the bExecute input starts the parameter setting.
The dnState output shows the parameter setting status.
• In order to completely parameterise the I/O system 1000, the
parameterisation blocks can be linked (bDone output connected to bExecute
input of the next FB) or executed successively in a sequencer.
• If only a maximum of 5 PDOs are required for communication, the
FB L_io1000ParPDO610 should be executed last in the sequencer as this FB
serves to save the parameter set of the parameter set.
• Deactivate all PDOs that are not required for communication. This saves
runtime resources of the PLC.
46LDMS 1.0 EN - 07/2011 - TD05
Page 47
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
L_io1000ParPDO610
⎯ bExecutebDone ⎯
⎯ dwHandlednState ⎯
⎯ byNodeAdrDataTo_IOData610 ⎯
⎯ bStoreParameter
⎯ wCobID_RxPDO6
⎯ byTransmissionType_RxPDO6
⎯ tCycleTime_RxPDO6
⎯ wCobID_RxPDO7
⎯ byTransmissionType_RxPDO7
⎯ tCycleTime_RxPDO7
⎯ wCobID_RxPDO8
⎯ byTransmissionType_RxPDO8
⎯ tCycleTime_RxPDO8
⎯ wCobID_RxPDO9
⎯ byTransmissionType_RxPDO9
⎯ tCycleTime_RxPDO9
⎯ wCobID_RxPDO10
⎯ byTransmissionType_RxPDO10
⎯ tCycleTime_RxPDO10
⎯ wCobID_TxPDO6
⎯ byTransmissionType_TxPDO6
⎯ tInhibitTime_TxPDO6
⎯ tCycleTime_TxPDO6
⎯ wCobID_TxPDO7
⎯ byTransmissionType_TxPDO7
⎯ tInhibitTime_TxPDO7
⎯ tCycleTime_TxPDO7
⎯ wCobID_TxPDO8
⎯ byTransmissionType_TxPDO8
⎯ tInhibitTime_TxPDO8
⎯ tCycleTime_TxPDO8
⎯ wCobID_TxPDO9
⎯ byTransmissionType_TxPDO9
⎯ tInhibitTime_TxPDO9
⎯ tCycleTime_TxPDO9
⎯ wCobID_TxPDO10
⎯ byTransmissionType_TxPDO10
⎯ tInhibitTime_TxPDO10
⎯ tCycleTime_TxPDO10
DMS 1.0 EN - 07/2011 - TD05L47
Page 48
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
TRUE Save parameter set at the end of the parameterisation process.
BOOL
Identifier
for PDO6 ... PDO10 (PLC I/O system)
for PDO6 ... PDO10 (I/O system PLC)
Transmission mode
for PDO6 ... PDO10 (PLC I/O system)
for PDO6 ... PDO10 (I/O system PLC)
BYTE
Cycle time
for PDO6 ... PDO10 (PLC I/O system)
for PDO6 ... PDO10 (I/O system PLC)
TIME
TIME
0 ... 65535 Cycle time in [ms]
Blocking time
for PDO6 ... PDO10 (I/O system PLC)
0 ... 65535 Blocking time in [ms]
Then the NMT command "Reset Node" is sent to the I/O system.
0 Automatic allocation of the identifiers
> 0 Value of the set identifier
0 Event-controlled
1 Time-controlled
2 Event-controlled with higher-level cycle time
3 PDO deactivated
( 51)
48LDMS 1.0 EN - 07/2011 - TD05
Page 49
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
Outputs
Identifier/data typeValue/meaning
bDone
dnState
BOOL
Status of parameter setting
DINT
• When the function has been executed successfully, the value "0" is output.
TRUE Parameter setting completed successfully
-1000 Error while executing the function block
-1003 byNodeAdr input is not in valid range
-1005 Wrong value at wCobID_RxPDO6 input
-1006 Wrong value at byTransmissionType_RxPDO6 input
-1007 Cycle time at tCycleTime_RxPDO6 input > 65535 ms
-1008 Wrong value at wCobID_RxPDO7 input
-1009 Wrong value at byTransmissionType_RxPDO7 input
-1010 Cycle time at tCycleTime_RxPDO7 input > 65535 ms
-1011 Wrong value at wCobID_RxPDO8 input
-1012 Wrong value at byTransmissionType_RxPDO8 input
-1013 Cycle time at tCycleTime_RxPDO8 input > 65535 ms
-1014 Wrong value at wCobID_RxPDO9 input
-1015 Wrong value at byTransmissionType_RxPDO9 input
-1016 Cycle time at tCycleTime_RxPDO9 input > 65535 ms
-1017 Wrong value at wCobID_RxPDO10 input
-1018 Wrong value at byTransmissionType_RxPDO10 input
-1019 Cycle time at tCycleTime_RxPDO10 input > 65535 ms
-1020 Wrong value at wCobID_TxPDO6 input
-1021 Wrong value at byTransmissionType_TxPDO6 input
-1022 Blocking time at tInhibitTime_TxPDO6 input > 65535 ms
-1023 Cycle time at tCycleTime_TxPDO6 input > 65535 ms
-1024 Wrong value at wCobID_TxPDO7 input
-1025 Wrong value at byTransmissionType_TxPDO7 input
-1026 Blocking time at tInhibitTime_TxPDO7 input > 65535 ms
-1027 Cycle time at tCycleTime_TxPDO7 input > 65535 ms
Function library "LenzeIo1000Drv"
Function blocks
1 Parameter setting started
0 Parameter setting completed successfully
DMS 1.0 EN - 07/2011 - TD05L49
Page 50
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
Identifier/data typeValue/meaning
dnState
DataTo_IOData610
io1000_ParPDO610
Status of parameter setting (continuation)
DINT
-1028 Wrong value at wCobID_TxPDO8 input
-1029 Wrong value at byTransmissionType_TxPDO8 input
-1030 Blocking time at tInhibitTime_TxPDO8 input > 65535 ms
-1031 Cycle time at tCycleTime_TxPDO8 input > 65535 ms
-1032 Wrong value at wCobID_TxPDO9 input
-1033 Wrong value at byTransmissionType_TxPDO9 input
-1034 Blocking time at tInhibitTime_TxPDO9 input > 65535 ms
-1035 Cycle time at tCycleTime_TxPDO9 input > 65535 ms
-1036 Wrong value at wCobID_TxPDO10 input
-1037 Wrong value at byTransmissionType_TxPDO10 input
-1038 Blocking time at tInhibitTime_TxPDO10 input > 65535 ms
-1039 Cycle time at tCycleTime_TxPDO10 input > 65535 ms
-1100 Error when sending the reset node telegram to the I/O system
-1101 Error when receiving the boot-up telegram from the I/O system
-1102 Timeout when receiving the boot-up telegram from the I/O system
-1103 Error when sending the start remote node telegram to the I/O
system
-2000 Error while executing the internal block for writing CAN indices
-2002 Wrong value at the dwHandle input
-2003 Wrong value at the byNodeAdr input
-2006 Writing of a wrong CAN index
-2007 Timeout while writing a CAN index of the I/O system
-2100 Error while writing a parameter of the I/O system
-2101 Output buffer is full
Communication-relevant parameters for the process data objects PDO6 ... PDO10
• Output for transmitting the structure data to the L_io1000Data610 process data
block.
50LDMS 1.0 EN - 07/2011 - TD05
Page 51
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParPDO610 - Communication settings PDO6 ... PDO10
Automatic allocation of the identifiers
For the process data objects PDO6 ... PDO10, the identifiers can be automatically allocated
as a function of the node address. If an automatic allocation is required, the value "0" has
to be applied at the corresponding wCobID_... input. In this case, the identifier is calculated
as follows:
The basic identifiers are defined block-internally:
Process data objectBasic identifier
RxPDOs (PLC I/O system)TxPDOs (I/O system PLC)
PDO6865861
PDO7870866
PDO8875871
PDO9880876
PDO10885881
Example for RxPDO6 and node address 3: Identifier = 860 + 3 = 863
If a value higher than "0" is given at the wCobID_... input, the applied value is used as
identifier for the corresponding PDO instead.
Note!
If several I/O systems (stations) at the system bus are parameterised via the
FB L_io1000ParPDO610 with standard values, an identifier collision may occur
between the individual PDOs of these stations. Hence, check the identifiers used.
Saving the parameter set in the I/O system safe against mains failure
If the bStoreParameter input is set to TRUE, the parameter set of the I/O system will be
saved safe against mains failure at the end of the parameterisation process.
For accepting the communication setting, the NMT command "Reset Node" is sent to the
I/O system. The I/O system re-initialises and returns a boot-up telegram as soon is it is in
the "Pre-Operational" status again. After the boot-up telegram has been received, the
bDone output of the FB is set to TRUE.
Note!
• Only Global Drive (e.g. Drive PLC): For sending the NMT telegram, the
controller has to be in the "Operational" CAN status. Hence, the controller has
to be parameterised as CAN master.
• After sending the NMT command "Reset Node" to the I/O system, the FB has
to receive the boot-up telegram within 10 s, otherwise a timeout error will be
output at the dnState output.
DMS 1.0 EN - 07/2011 - TD05L51
Page 52
Function library "LenzeIo1000Drv"
Function blocks
L_io1000ParComGuarding - Parameterising monitoring functions
This FB serves to parameterise the monitoring functions provided by the I/O system.
This includes:
– NodeGuarding, heartbeat and Lenze-specific monitoring functions.
– Setting of the switching performance of the output channels in the event of an error
via the byErrorBehavior input.
A FALSE/TRUE edge at the bExecute input starts the parameter setting.
The dnState output shows the transmission status.
This FB coordinates the digital and analog input/output data of the process data objects
PDO1 ... PDO5. The FB is the interface between the PLC and the I/O system.
Data from the PLC are transmitted to the I/O system (digital and analog output
channels) via the abyPDO1...5_DataToIO inputs.
The statuses of the digital and analog input channels are transmitted to the PLC via the
abyPDO1...5_DataFromIO outputs.
After the FALSE-TRUE edge at bEnablePDOTransfer, the FB sends the NMT command
"Start remote node" to the I/O system to change its status to "Operational". In this
state, the current process image of the I/O system is sent.
This FB coordinates the digital and analog input/output data of the process data objects
PDO6 ... PDO10. The FB is the interface between the PLC and the I/O system.
Data from the PLC are transmitted to the I/O system (digital and analog output
channels) via the abyPDO6...10_DataToIO inputs.
The statuses of the digital and analog input channels are transmitted to the PLC via the