Lenze Function library LenzeIO1000Drv Manual de usuario Pagina 51

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 64
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 50
DMS 1.0 EN - 07/2011 - TD05 L 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:
Identifier (COB-ID) = basic identifier + node address (node ID)
The basic identifiers are defined block-internally:
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.
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.
Process data object Basic identifier
RxPDOs (PLC I/O system) TxPDOs (I/O system PLC)
PDO6 865 861
PDO7 870 866
PDO8 875 871
PDO9 880 876
PDO10 885 881
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.
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.
Vista de pagina 50
1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 63 64

Comentarios a estos manuales

Sin comentarios