Rockwell-automation 1738 Assembly Connections for POINT I/O and ArmorP Manual de usuario Pagina 14

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 82
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 13
Publication 1734-UM016A-EN-P - October 2010
8 Configuration
Module Configuration Sent with the Connection Request
Individual module configuration must be manually constructed and appended
to the minimal configuration assembly specified in the table Minimal Adapter
Configuration Assembly on page 5. For each module that needs to be
configured, the following information must be provided:
This structure may be repeated for as many modules as necessary until the
whole assembly exceeds 509 bytes. The module order is not important as long
as all module configuration follows the minimal header information from the
table Minimal Adapter Configuration Assembly on page 5.
If any part of the configuration assembly is wrong (either the minimal
assembly or a portion directed to an I/O module), the connection request will
be rejected with the General Return Code indicating an Error in the Data
Segment (0x09). The Extended Error code will indicate the byte offset into the
configuration data segment where the error was detected. The Configuration
assembly details for all of the 1734 and 1738 I/O modules are presented in
Module Assembly Information on page 31.
Module Configuration with RSNetWorx for DeviceNet
RSNetWorx for DeviceNet provides a rich parameter-based configuration user
interface. The POINT I/O and ArmorPOINT I/O adapters have the
capability to present their backplane as a DeviceNet subnet to RSLinx. The
subnet can be used to bridge configuration data from RSNetWorx for
DeviceNet to backplane devices. With this method, all configuration for a
POINT I/O backplane can be stored to the DeviceNet network file (.DNT)
and restored via this file if necessary.
Module Configuration Information
Field Data Type Description
Slot number USINT The slot number to identify modules that require
configuration data.
Configuration size USINT The size, in bytes, of the Configuration Data for the
given module. It does not include the size of the first
three fields shown here.
Configuration
assembly instance
UINT The adapter reads this field to access the module
configuration assembly’s instance number.
Configuration data Array of
BYTE
The configuration assembly data as defined by the
module's EDS file.
Vista de pagina 13
1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 81 82

Comentarios a estos manuales

Sin comentarios