![ALTUS Hadron Xtorm Скачать руководство пользователя страница 84](http://html1.mh-extra.com/html/altus/hadron-xtorm/hadron-xtorm_user-manual_2914394084.webp)
4. Configuration
83
frames, then a switchover will occur. This will cause the inactive interface to be active. Notice that
there is a delay between the detection of the failure and the activation of the inactive interface, due to
the time required for its configuration. This delay can reach some tens of milliseconds.
When one of the NETs is active, this will take over the configured IP address. The inactive NET will
remain with its parameters blank (IP Address, Subnet Mask, and Gateway address) in the CPU
diagnostics.
ATTENTION:
When performing a Reset Origin command in a CPU configured with NIC Teaming on the NETx
frontal interfaces, only the interface that was active before the command will remain accessible.
After the command, the accessible interface can be viewed in the Informative Menu and of CPU’s
Configuration.
Switch Mode:
In this mode, the interface forms a pair with the subsequent interface working as an
Ethernet switch, thus allowing the communication through both doors. This mode allows the
connection of several Xtorm RTUs as a “cascade”, thus allowing the implementation of a network of
ring topology. However, to close this ring, you may connect the endings of this “cascade” to an
external switch, which supports STP or RSTP protocols. This architecture is advantageous as it
reduces the number of ports of the external switch if compared to the star network topology. On the
other hand, the time it takes for recovery in case of a fault (convergence time) is high (up to 50
seconds with STP or up to 6 seconds with RSTP. Thus, make sure the system can support this
network downtime without any major problems. If you are working on a critical system, which
cannot manage such long breaks preferably, use the star topology network. This is the case of control
or protection systems with very fast response times, for example.
Double Points
The representation of digital double input/output points is done by a special data type called DBP
(defined on the library LibDataTypes). This type consists basically on structure composed by 2
BOOL elements called OFF and ON (equivalent to TRIP and CLOSE respectively). Variables of this
type can be associated to input and output modules that have support for events and pulsed
commands (HX1110, HX2200, HX2300 and HX2320 for example), where each of the ON and OFF
elements must be mapped individually for each physical input/output point of that module. In the
case of input modules, the %I memory is updated normally even for points configured as DBP. On
the other side, for output modules the points configured as DBP will not consider the value of %Q
memory anymore.
Additional information about the configuration of double points on the input and output modules can
be obtained on their respective Technical Characteristics document.
Protocols Configuration
Table 4-27 shows the maximum configuration limits regarding the communication interfaces and
CPU communication protocols.
HX3040
Instances per Serial Interface (COMs)
1
Instances per Ethernet Interface (NETs)
4
Instances per CPU
12
Control Centers per CPU
5
Mappings per CPU
5.000
Mapped points
20.000
DNP3 connections
100
Requests for UCP
512
Table 4-27. Protocols Limits per Interface and per CPU