Siemens IP-Module Especificaciones Pagina 37

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 85
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 36
Siemens TCP/IP Ethernet Driver Help
Optimizing Siemens TCP/IP Ethernet Communications
The Siemens TCP/IP Ethernet Driver was designed to provide the best performance with the least amount of
impact on the system's overall performance. While the Siemens TCP/IP Ethernet Driver is fast, there are a couple
of guidelines that can be used to optimize the application and gain maximum performance.
This server refers to communications protocols like Siemens TCP/IP Ethernet as a channel. Each channel defined
in the application represents a separate path of execution in the server. Once a channel has been defined, a
series of devices can then be defined under that channel. Each of these devices represents a single Siemens
TCP/IP Ethernet controller from which data will be collected. Although this approach to defining the application
provides a high level of performance, it does not take full advantage of the Siemens TCP/IP Ethernet Driver or the
network. An example of how the application may appear when configured using a single channel is shown below.
Each device appears under a single Siemens TCP/IP Ethernet channel.
In this configuration, the driver must move from one device to the
next as quickly as possible to gather information at an effective rate.
As more devices are added or more information is requested from a
single device, the overall update rate begins to suffer.
If the Siemens TCP/IP Ethernet Driver could only define one channel, then the example above would be the only
option available; however, the Siemens TCP/IP Ethernet Driver can define up to 256 channels. Using multiple
channels distributes the data collection workload by simultaneously issuing multiple requests to the network. An
example of how the same application may appear when configured using multiple channels is shown below.
Each device has now been defined under its own channel. In this new
configuration, a single path of execution is dedicated to the task of
gathering data from each device.
The performance will improve even if the application has more than
256 devices. While 256 or fewer devices may be ideal, the application
will still benefit from additional channels. Although spreading the
device load across all channels will cause the server to move from
device to device again, it can now do so with far less devices to
process on a single channel.
Important: Although the OPC server limits the number of channels to 256, the device ultimately determines the
number of allowed connections. This constraint comes from the fact that some devices cannot support 256
connections. For these devices, the maximum number of channels defined should equal the maximum number of
connections allowed. For devices that support more than 256 connections, the maximum 256 channels should be
defined, with devices spread evenly over these 256 channels. For more information on device connections, refer
to Link Settings.
www. kepware.com
37
Vista de pagina 36
1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 84 85

Comentarios a estos manuales

Sin comentarios