1. Manuals
  2. Brands
  3. ALTUS Manuals
  4. Touch terminals
  5. Hadron Xtorm
  6. User manual

ALTUS Hadron Xtorm User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Hadron Xtorm
User Manual
Rev. C 02/2017
Doc. Code: MU223600

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Hadron Xtorm and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for ALTUS Hadron Xtorm

  • Page 1 Hadron Xtorm User Manual Rev. C 02/2017 Doc. Code: MU223600...
  • Page 2 General Supply Conditions No part of this document may be copied or reproduced in any form without the prior written consent of Altus Sistemas de Automação S.A. who reserves the right to carry out alterations without prior advice. According to current legislation in Brazil, the Consumer Defense Code, we are giving the following information to clients who use our products, regarding personal safety and premises.

  • Page 3: Table Of Contents

    Summary Summary 1. INTRODUCTION ............................7 Hadron Xtorm Series ...........................7 Innovative Features ..........................8 Main Features ............................9 Documents Related to this Manual ......................10 Technical Support ............................12 Warning Messages Used in this Manual ....................12 2. TECHNICAL DESCRIPTION ......................... 13 Panels and Connections ..........................13 General Features............................
  • Page 4 Summary RS-485 Communication with Internal Termination ................44 RS-485 Communication with External Termination ................45 RS-422 Communication without Termination ..................46 RS-422 Communication with Internal Termination ................47 RS-422 Communication with External Termination ................48 RS-422 Network Example ........................49 IRIG- B Connection ...........................
  • Page 5 Summary Informative Menu and of CPU’s Configuration ..................189 Function Blocks and Functions ....................... 192 Inputs and Outputs Update ......................... 192 RetainTimer ............................194 Non-Redundant Timer ........................198 User Log ............................200 ClearRtuDiagnostic ..........................203 ClearEventQueue ..........................203 User Management and Access Rights ..................... 204 User Management and Project’s Access Rights ..................
  • Page 6 Summary Identification of a HX3040 CPU ......................261 General Features ..........................262 Operation Principles ..........................264 Single Redundant Project ........................264 Redundant Project Structure ....................... 264 Multiple Mapping ..........................267 Diagnostics, Commands and User Data Structure ................268 Cyclic Synchronization Services through Redundancy Synchronism Channels ........268 Sporadic Synchronization Services through Redundancy Synchronism Channels .......
  • Page 7 Summary I/O Modules Diagnostics .......................... 331 Not Loading the Application at Startup ....................334 Power Supply Failure ..........................334 Common Problems ..........................335 Troubleshooting ............................336 Preventive Maintenance .......................... 336 8. ELECTRIC PANEL DESIGN ........................ 337 Mechanical Design ........................... 337 Dimensions ............................

  • Page 8: Introduction

    (HPPs) and power substations. Hadron Xtorm Series holds an advanced technology on its bus. Due to a high-speed Ethernet interface it enables the sharing of inputs/outputs and data information within multiple controllers in the same system.

  • Page 9: Innovative Features

    (without supervisor or programmer), reducing maintenance and commissioning times. OFD – On Board Full Documentation: Hadron Xtorm Series CPUs are capable of storing the complete project documentation in its own memory. This feature can be very convenient for backup purposes and maintenance, since the complete information is stored in a single and reliable place.

  • Page 10: Main Features

    MasterTool Xtorm configuration tool. High Speed Bus Hadron Xtorm Series architecture features a state-of-the art bus based on Ethernet 100 Mbps. The high throughput allows the updating of large amounts of inputs in a short period of time. The modules are automatically addressed and identified avoiding eventual errors during the application configuration and field maintenance.

  • Page 11: Documents Related To This Manual

    1. Introduction Capacities In Hadron Xtorm Series, the largest rack can hold up to 18 modules. The combination between the chosen modules must not exceed the current limit of the rack power supply. The current consumed by each Hadron Xtorm Series module from the bus is found in the Technical Characteristics’...
  • Page 12 Características Técnicas del UCP 6 ETH, 2 SERIALES, IRIG-B, Spanish RED. CE123701 Hadron Xtorm Series Backplane Racks Technical Characteristics English CT123701 Características Técnicas dos Bastidores da Série Hadron Xtorm Portuguese CS123701 Características Técnicas de los Bastidores de la Serie Hadron Spanish Xtorm CE123200...

  • Page 13: Technical Support

    1. Introduction Technical Support For Altus Technical Support, call +55 51 3589-9500 (São Leopoldo, RS, Brazil). For further information regarding Altus Technical Support on other places, see http://www.altus.com.br or send an email to altus@altus.com.br. If the equipment is already installed, make sure to have the following information at the moment of support requesting: ...

  • Page 14: Technical Description

    (read only) and local time (read only). The Hadron Xtorm Series features a graphic display notifying the status and useful information, such as application states (Run/Stop), miniSD card status, activity on serial interfaces (RX and TX) among others.

  • Page 15: General Features

    2. Technical Description Interfaces Models Description RJ45 communication connector in the 10/100Base-TX standard. Allows point-to-point or network communication in the open protocols, MODBUS TCP client and server, NET 1 to NET 6 HX3040 MODBUS RTU via TCP client and server, DNP3 Client and Server.
  • Page 16 2. Technical Description Electronic Tag on Display (ETD) Isolation Logic to protective earth 2500 Vac / 1 minute Logic to Ethernet interfaces 1500 Vac / 1 minute Logic to serial port (COM 2) 2000 Vac / 1 minute Logic to IRIG-B port 2500 Vac / 1 minute Ethernet interfaces to protective 1500 Vac / 1 minute...

  • Page 17: Specific Features

    1 analogic input point can be represented by two bytes. The Hadron Xtorm Series HX3040 CPU defines all the area of addressable input variables memory (%I) as redundant variables, which means that the user does not need to select this area.
  • Page 18 2. Technical Description Persistent symbolic variable memory: It is the area where the persistent symbolic variables are assigned. Persistent data keep their respective values even after a download of a new application into CPU. ATTENTION: The declaration and use of persistent variables should be performed exclusively through the Persistent Vars object, which may be included in the project through the tree view in Application ->...

  • Page 19: Serial Interfaces

    2. Technical Description Serial Interfaces COM 1 HX3040 Connector DB9 shielded female Physical interface RS-232C or RS-485 (depending on the connected cable) RS-232C: full duplex Communication direction RS-485: half duplex Maximum number of RS-485 transceivers RS-485 termination No (allows the use of external active termination) Modem signals RTS, CTS, DCD 600, 1.200, 1.800, 2.400, 4.800, 9.600, 19.200, 38.400, 57.600,...

  • Page 20: Ethernet Interfaces

    2. Technical Description Ethernet Interfaces NET 1 to NET 6 HX3040 Connector RJ45 shielded female Auto crossover Maximum cable length 100 m Cable type UTP or ScTP, category 5 Baud rate 10/100 Mbps Physical layer 10/100Base-TX Data link layer LLC (logic link control) Network layer IP (internet protocol) TCP (transmission control protocol)

  • Page 21: Graphic Display

    2. Technical Description Graphic Display The Hadron Xtorm Series CPUs have a graphic display used to show status and diagnostics of the entire system including specific diagnostics of each additional module. The display also offers an easy-to-use menu that brings the user a fast way to read or set some parameters such as: internal temperature (read only);...

  • Page 22: Performance

     Operational System Time  Module quantity (process data, input/output, among others) Application Times The execution time of a Hadron Xtorm CPUs application depends on the following variables:  Input read time (local and remote)  Tasks execution time ...

  • Page 23: Initialization Times

    AL-1752: RS-232C standard cable with two DB9 male connectors for communication between CPUs of Hadron Xtorm Series and the Altus products of the H Series and HMIs of IX Series. AL-1753: RS-232C standard cable with one DB9 male connector and one DB25 male connector for...
  • Page 24 HX8300 and HX8320 power supplies. HX9402 (10-terminals), on the other hand, can be used in any input/output modules of the Hadron Xtorm Series. HX9405 (4- terminals) refers to the exclusive use of the CPU HX3040 IRIG-B. These products support temperatures ranging from -5 ºC to 70 ºC.

  • Page 25: Installation

    Such procedure guaranties that the module static energy limits are not exceeded. It is important to register each received equipment serial number, as well as software revisions, if there are any. These information are necessary, in case you need to contact Altus Technical Support. Mechanical Installation Rack Clamping Drilling for 9 slots Rack In order to clamp a 9 slots rack, use 5 (five) M4 screws (Figure 3-1).
  • Page 26 3. Installation Figure 3-2. Drilling for 18 Slots Rack In all holes must be used M4 type DIN 7985 pan head screw. These screws can be fastened directly to the panel or with nuts when the panel thickness is insufficient to hold the thread. When using nuts, it is recommended the use of self-locking type nuts in order to avoid loosening.

  • Page 27: Module Insertion

    To remove the rack, perform the reverse sequence previously indicated (Assembly). Module Insertion The following example shows a generic Hadron Xtorm Series module so that the procedure here described applies to all modules of the Series. First, attach the bottom part of the module to the rack. Notice that the bottom part works as a guide for the correct insertion.
  • Page 28 3. Installation Figure 3-5. HX6000 and the Rack After attaching the bottom of the module as described above, make a single and continuous rotation movement through the clamping cursor (which should be at the lock position). The bottom part of the module gets into the same place and the clamping lock fits in the rack upper part.
  • Page 29 3. Installation By properly following the procedures described above, the module will be perfectly connected to the bus (Figure 3-7). Figure 3-7. Docked Module in the Rack There is no other way to connect the module to the rack. Any attempt of entering it in a different manner may cause irreparable damages.

  • Page 30: Module Removal

    3. Installation Module Removal The following example shows a generic Hadron Xtorm module so that the procedure here described applies to all modules of the Series. First, pull the retention cursor (Figure 3-9 /1) in order to unlock it from the bus and then rotate it in one single and continuous movement (Figure 3-9 /2).
  • Page 31 The input and output modules of the Hadron Xtorm Series present some specific characteristics that will be addressed below. I/O Terminal Blocks The terminals blocks of Hadron Xtorm Series I/O modules use a clamping wire system with spring terminals, which do not require a screw for this purpose. Identification All pins of I/O terminals blocks have a serial number from 1 to 10.
  • Page 32 3. Installation Figure 3-11. Rack Connector Cover Insertion Rack Connector Cover Removal In order to remove the Hadron Xtorm Series HX9102 connector cover, pull it from the upper side (Figure 3-12). Figure 3-12. Rack Connector Cover Removal...

  • Page 33: Electrical Installation

    3. Installation Electrical Installation DANGER: When executing any installation in an electric panel, certify that the main energy supply is OFF. Electrical Safety ATTENTION: The pin 5 of HX8300 and HX8320 modules terminal block is the ground protection and shall be connected to the local ground with a good connection, ensuring a maximum impedance of 0.1 Ω.

  • Page 34: Spring Terminal Blocks

    3. Installation Figure 3-13. Printed Circuit Boards Area (HX9001 and HX9003) Spring Terminal Blocks This type of terminal has a spring-based clamping system, which ensures a high reliability even in environments subject to vibration (Figure 3-14 and Figure 3-15). For its assembly, use a 3.5 mm wide screwdriver with insulated cable (Figure 3-15).
  • Page 35 3. Installation Figure 3-15. I/O Module Spring Terminal Block Figure 3-16. Spring Terminal Block In order to mount the wire into the terminal block:  Insert the screwdriver into the terminal block driver and open the terminal spring  Insert the wire into the terminal block ...
  • Page 36 3. Installation 6-Route Pin In this case, use a 2.5 mm² wire. Crimp the specified terminals to the given wire (2.5 mm²) in each route. ATTENTION: Use terminals with length A = 12 mm to ensure effective contact (see Figure 3-18). 10-Route Pin In this case, use wires from 0.5 mm²...

  • Page 37: Connections

    3. Installation Figure 3-19. Cable Assembly (10-Route Connector) Wiring Removal In order to remove the terminal blocks wires, use a 3.5 mm wide screwdriver with insulated cable. Insert the screwdriver into the drive next to the wire while pulling it out (Figure 3-14 and Figure 3-15).

  • Page 38: Cpu Electrical Installation

    Figure 3-20 shows the Hadron Xtorm Series CPU electrical diagram installed in a rack of the same Series. The same image can be seen on the left side of the CPU mechanics.

  • Page 39: Ip Address

    3. Installation IP Address The NET 1 Ethernet interface is used for Ethernet communication and CPU configuration. Default parameters: NET 1 IP Address 192.168.15.1 Subnet Mask 255.255.255.0 Gateway Address 192.168.15.253 Table 3-1. NET 1 Ethernet Interface Default Parameters The IP address and Subnet mask parameters can be visualized in the CPU graphical display, through the parameters menu, as described in Informative Menu and of CPU’s Configuration.

  • Page 40: Free Arp

    600 ms and so on until the fifth trigger at time 3 s. Network Cable Installation Hadron Xtorm Series CPUs Ethernet ports are identified on the panel from NET 1 to NET 6. These ports have standard pin outs, which are used, for example, in PCs. The connector type, cable type, physical level, among other details regarding the CPU and the Ethernet network device are defined in the Technical Description - Ethernet Interfaces.

  • Page 41: Serial Network Connection (Com 1)

    The interface can be connected in a communication network through a hub or switch, or straight to the communication equipment. In this last case, due to Hadron Xtorm CPUs Auto Crossover feature, there is no need for a crossover network cable, the one used to connect two PCs point to point via Ethernet port.

  • Page 42: Rs-232C Communication

    3. Installation RS-232C Communication In order to connect the Hadron Xtorm CPU to a RS-232C device, be sure to use the correct cable, as described in the chapter Technical Description - Related Products . RS-485 Communication without Termination In order to connect the Hadron Xtorm CPU to a RS-485 network with no termination in COM 1 interface, the identified terminals of cable AL-1763 must be connected in the respective device terminals, as shown in Table 3-9.

  • Page 43: Rs-485 Communication With External Termination

    3. Installation RS-485 Communication with External Termination In order to connect the Hadron Xtorm CPU to a RS-485 network through the COM 1 interface external termination, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-10.

  • Page 44: Serial Network Connection (Com 2)

    Serial Network Connection (COM 2) The COM 2 isolated communication interface enables the connection to an RS-485/422 network. See in the following the Hadron Xtorm CPU DB9 female connector with the proper identification and signals description. Figure 3-25 Hadron Xtorm CPU DB9 Female Connector...

  • Page 45: Rs-485 Communication With Internal Termination

    The unconnected pins must be insulated so there is no contact between them. RS-485 Communication with Internal Termination In order to connect the Hadron Xtorm CPU to a RS-485 network through the internal termination of the COM 2 interface, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-13.

  • Page 46: Rs-485 Communication With External Termination

    The unconnected pins must be insulated so there is no contact between them. RS-485 Communication with External Termination In order to connect the Hadron Xtorm CPU to a RS-485 network through the external termiantion of the COM 2 interface, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-14.

  • Page 47: Rs-422 Communication Without Termination

    The unconnected pins must be insulated so there is no contact between them. RS-422 Communication without Termination In order to connect the Hadron Xtorm CPU to a RS-422 without termination network through the COM 2 interface, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-15.

  • Page 48: Rs-422 Communication With Internal Termination

    The unconnected pins must be insulated so there is no contact between them. RS-422 Communication with Internal Termination In order to connect the Hadron Xtorm CPU to a RS-422 network through the internal termination of the COM 2 interface, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-16.

  • Page 49: Rs-422 Communication With External Termination

    The unconnected pins must be insulated so there is no contact between them. RS-422 Communication with External Termination In order to connect the Hadron Xtorm CPU to a RS-422 network through the external termination of the COM 2 interface, the identified terminals of the AL-1763 cable must be connected in the respective device terminals, as shown in Table 3-17.

  • Page 50: Rs-422 Network Example

    RS-422 Network Example Figure 3-32 shows an example of a RS-422 network where the Xtorm CPU is used as master. In the example, there are slave devices with RS-422 interface as well as Altus solution for derivators and terminators. Figure 3-32. RS-422 Network Example Diagram Note: The AL-2600 modules that are at the network endings work as terminators.

  • Page 51: Irig- B Connection

    In cases where the Hadron Xtorm Series bus expansion is used, the timing of the CPU's internal clock will synchronize the time stamps for events generationof I/O modules in the expansion bus (Figure 3-33).
  • Page 52 3. Installation For cases where the application uses CPU redundancy in the same rack, the time synchronization signal generated by the GPS must be connected to the IRIG-B input of each one of the CPUs, regardless of which CPU is in Active mode and which is in Standby mode, thus guaranteeing the system time synchronism.

  • Page 53: Irig-B Connection Pins

    3. Installation IRIG-B Connection Pins In order to connect the Hadron Xtorm CPU to an IRIG-B time synchronization signal connect the cable pins containing the IRIG-B signal on the CPU HX3040 terminals, as shown in Table 3-18. CPU’s Pin Name...

  • Page 54: Memory Card Installation

    3. Installation Memory Card Installation This section describes how to insert the memory card into the Hadron Series Xtorm CPU. For further information about its use, see Configuration – Memory Card. Initially, notice the correct insertion position of the memory card. One corner is different from the others and this should be used as a reference for correct the insertion of the card.

  • Page 55: Programmer Installation

    Programmer Installation To install MasterTool Xtorm development software, have on hands the distribution CD-ROM or download the installation file at http://www.altus.com.br. Next, close all running programs, and double-click the installation file. The installer will prompt the following screen: Figure 3-38. Installation Assistant...
  • Page 56 3. Installation First screen indicates the beginning of the installation and displays the version of MasterTool Xtorm software to be installed on your computer. Click Next to continue. The screen that refers to the license agreement will be shown, which should be read carefully. If you agree to the license terms, click Next to continue.
  • Page 57 3. Installation Figure 3-41. Components Selection You will see the screen that refers to the installation folder, which sets the paths and locations of all items to be installed. Then, click Next to continue. Figure 3-42. Folder Selection MasterTool Xtorm installation has been started. Wait while the necessary files are being installed on your computer.
  • Page 58 3. Installation Figure 3-43. Installation Process By the end of the installation, you are asked if you want to reboot the computer so the changes may be applied. Figure 3-44. Complete Installation...
  • Page 59 3. Installation MasterTool Xtorm is installed and ready for use. To run it, click the shortcut “MasterTool Xtorm” within the group “Altus” “Altus” “MasterTool Xtorm”, which was created during the installation, in the Start menu. The first time the software is started, a screen requesting the registration information will be displayed.

  • Page 60: Configuration

    4. Configuration 4. Configuration The Hadron Xtorm Series CPU is configured and programmed through the MasterTool Xtorm software. Its configuration defines the behavior and utilization modes for peripherals and CPUs special features. The programming represents the application developed by the user, also known as applicative.

  • Page 61: General Parameters

    Table 4-1. CPU General Configurations Hot Swap Hadron Xtorm Series CPUs provide the possibility of I/O modules change in the bus with no need for system turn off and without information loss. This feature is known as hot swap. CAUTION: Hadron Xtorm Series CPUs do not guarantee the persistent and retentive variables retentivity in case the power supply or even the CPU is removed from the energized backplane rack.
  • Page 62 4. Configuration  Enabled, Without Startup Consistency Therefore, the user can choose the behavior the system must assume in abnormal bus situations and when the CPU is in Run Mode. Table 4-2 presents the possible abnormal bus situations. Situation Possible causes Incompatible - Some module connected to the bus is different from the model that is configuration...
  • Page 63 Always replace one module at a time so the CPU updates the modules state. Table 4-3 presents the bus conditions and the Hadron Xtorm CPU LED DL operation state. For further information regarding the diagnostics LEDs states, see chapter Maintenance – Diagnostics via...

  • Page 64: Time Synchronization

    4. Configuration Enabled, with start Enabled, without start Disabled, for declared Condition consistency for declared consistency modules only modules only LED DL: Blinks 2x Blue LED DL: Blinks 2x Blue LED DL: Blinks 2x Blue Non declared module Application: Run Application: Run Application: Run LED DL: Blinks 2x Blue...
  • Page 65 4. Configuration Figure 4-2. Time Synchronization Configuration Configuration Description Default Options Time zone. Difference between UTC(Universal Time Zone -03:00 -12:59 to +13:59 Time Coordnated) time and the local time Enables the synchronism through the IRIG-B Disabled Enable IRIG-B Disabled protocol. Enabled Sets the priority of the IRIG-B sync source regarding the other sources.
  • Page 66 4. Configuration Configuration Description Default Options Before updating the time, the CPU compares the time received from the SNTP server with its Minimum Error current time. The CPU time is only updated if 0 to 65535 Before Clock the difference between the received time and Update (x1 ms) current time is greater than the time (milliseconds) set in this field.
  • Page 67 4. Configuration This synchronization method should be used only as a synchronism helper method, since the accuracy of the synchronization process of the RTU clock depends largely on delay and network traffic, as well as the CPU processing load, since this mechanism is handled by a low priority task. ATTENTION: In architectures with CPU redundancy, DNP3 Server driver is disabled in the non-active CPU.

  • Page 68: Internal Points

    4. Configuration ATTENTION: The SNTP service depends on the user application only for its configuration. This service will run even when the CPU is in STOP or BREAKPOINT mode, since there is an application in the CPU with the SNTP client enabled and properly configured. CAUTION: It is vital the configuration of at least one SNTP server if IRIG-B synchronism method isn’t used.
  • Page 69 The IEC 61850, DNP3 and IEC104 standards have their own formats for representing the quality information of a point. The Hadron Xtorm Series, in turn, has its own quality format, called Internal Quality (very similar to IEC 61850). This format is defined by the QUALITY type (LibRtuStandard library) and is used internally for storing the quality, allowing conversions between protocols without loss of information.
  • Page 70 3 – Questionable (Current value may be different from IED) Table 4-7. QUALITY Structure DNP3 Conversion Table 4-8 illustrates the quality conversion of DNP3 to internal points. Table 4-9 illustrates the quality conversion of internal points to DNP3 for Hadron Xtorm Series available for HD8500.
  • Page 71 4. Configuration DNP3 -> Internal Internal Quality DNP3 Quality Flags VALIDITY IF JUST ONLINE, ONLINE VALIDITY_GOOD NOT ONLINE FLAG_OLD_DATA VALIDITY_QUESTIONABLE RESTART FLAG_RESTART VALIDITY_QUESTIONABLE COMM_LOST FLAG_COMM_FAIL AND FLAG_OLD_DATA VALIDITY_QUESTIONABLE IF JUST FLAG_REMOTE_SUBSTITUTED AND REMOTE_FORCED REMOTE_FORCED AND FLAG_OPERATOR_BLOCKED ONLINE, VALIDITY_GOOD IF JUST LOCAL_FORCED FLAG_LOCAL_SUBSTITUTED AND LOCAL_FORCED AND ONLINE,...
  • Page 72 4. Configuration Internal-> IEC 60870-5-104 Digital Internal Quality IEC 60870-5-104 Quality Flags VALIDITY FLAG_RESTART NOT TOPICAL FLAG_COMM_FAIL NOT TOPICAL FLAG_REMOTE_SUBSTITUTED SUBSTITUTED FLAG_LOCAL_SUBSTITUTED SUBSTITUTED FLAG_FILTER FLAG_OVERFLOW FLAG_REFERENCE_ERROR FLAG_INCONSISTENT FLAG_OUT_OF_RANGE FLAG_INACCURATE FLAG_OLD_DATA NOT TOPICAL FLAG_FAILURE INVALID FLAG_OPERATOR_BLOCKED BLOCKED FLAG_TEST VALIDITY_INVALID INVALID Tabela 4-10. Internal Conversion to IEC 60870-5-104 to Digital Points Internal->IEC 60870-5-104 Analogic Internal Quality IEC 60870-5-104 Quality...
  • Page 73 INVALID Tabela 4-12. Internal Conversion to IEC 60870-5-104 to Counters IEC 61850 Conversion Table 4-13 relates the quality type of internal points to the IEC 61850 quality for Hadron Xtorm Series available for HD8500. Internal-> IEC 61850 Internal Quality Flags...

  • Page 74: Engineering Conversion

    Table 4-14. MODBUS Quality I/O Module Quality To assist in the use of diagnostics of each I/O point, the Hadron Xtorm Series automatically creates a quality structure for each module used in the RTU project. This is accomplished through its own internal structure accessible via QUALITY structure, which is available in the IOQualities GVL (automatically created by the HD8500 template).

  • Page 75: Alarms

    4. Configuration this purpose the user of a control system usually is faced with the demand to convert engineering units. This conversion is usually associated to the relationship between physical points and internal points. The configuration of Engineering Conversion (Figure 4-5), follows the parameters described in Table 4-16.

  • Page 76: Event Grouping

    4. Configuration Configurations Description Default Possibilities INT, DINT, LINT, UINT, UDINT, ULINT, Symbolic variable that has the WORD, DWORD, LWORD, REAL or Input information used for alarm LREAL. The variable can be simple, array generation or array element and may be in structures. Type of comparison to be held It may take two pre-set values: "Higher Type...
  • Page 77 4. Configuration Figure 4-7. Event Grouping Operation ATTENTION: If a group of points is used as input to another grouping, make sure that the “Maximum Delay” parameter of the first group is smaller than the one of the group in which it is being inserted The event-grouping configuration (Figure 4-8) allows up to 128 inputs in the Events Grouping table.

  • Page 78: Serial Interfaces Configuration

    4. Configuration Serial Interfaces Configuration COM 1 The COM 1 communication interface is composed by a DB9 female connector for RS-232C and RS- 485 (non-isolated) interfaces. It allows peer to peer or network communication in open protocols, MODBUS RTU slave or MODBUS RTU master. The network communication is performed through a converter.
  • Page 79 4. Configuration  Bit 5: UART parity error. The parity bit read is not correct according to the calculated one  Bit 6: UART overrun error. Data was lost during the FIFO UART reading. New characters were received before the later ones were removed. This error will only be indicated in the first character read after the overrun error indication.
  • Page 80 4. Configuration Configuration Description Default Options Port Advanced Parameters - RTS: Enabled at the beginning of transmission and restarted, as fast as possible after the end of it. E.g.: Control of a RS-232/RS-485 external converter. - RTS OFF: Always disabled. - RTS ON: Always enabled.

  • Page 81: Com 2

    4. Configuration COM 2 The COM 2 communication interface is composed by a DB9 female connector for RS-422C and RS- 485 interfaces. It allows peer to peer or network communication in open protocols, MODBUS RTU slave or MODBUS RTU master. Table 4-22 presents the parameters that must be configured for the proper functioning of the application.

  • Page 82: Ethernet Interfaces Configuration

    Table 4-24. COM 2 Advanced Configurations Ethernet Interfaces Configuration The Hadron Xtorm CPUs provides six local Ethernet interfaces (NET 1 to NET 6) which can function independently or as pairs. Each interface or pair must be set in a different subnet.

  • Page 83: Reserved Tcp Ports

    4. Configuration Reserved TCP Ports The following TCP ports of the Ethernet interfaces, both local and remote, are used by CPUs services, so they are reserved and cannot be used by the user: 80, 8080, 1217, 1740, 1741, 1742,1743 and 11740. Ethernet Interfaces Advanced Configurations The HX3040 CPU Ethernet channels can be configured in three different modes: individually, in NIC Teaming pairs or in Switch mode.

  • Page 84: Double Points

    4. Configuration 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.
  • Page 85 4. Configuration Notes: Instances per Serial Interface (COMs): Due to its characteristics, each serial interface supports only one communication protocol instance. Examples of instances compatible with serial interfaces: MODBUS RTU Master and MODBUS RTU Slave. Instances per Ethernet Interface (NETs): Ethernet Interfaces support more than one communication protocol instance, as described in the table.
  • Page 86 4. Configuration  MODBUS Server Protocol: The limit (²) regards the Ethernet interfaces that limit the number of connections that can be made to other devices via the same Ethernet interface. It is not necessary, nor possible, declare or configure the Clients under the instance of the MODBUS Server protocol.

  • Page 87: Cpu Event Queue

    4. Configuration Legend:  - The protocol remains active, in normal operation  - The protocol is disabled CPU Event Queue The CPU features an event queue of FIFO type (First In, First Out) which is used to buffer temporarily the events related to communication points until they are transferred to their final destination.
  • Page 88 4. Configuration Overflow Signalling The overflow signalling of the CPU queue occurs in two situations:  If the CPU queue is partially occupied and the available space isn't enough to store the new events generated in the execution cycle  If the CPU has stoped the generation of events (because were detected more events in a single execution cycle than the total size of the CPU queue) As well as in the CPU queue, the signalling of overflow for the consumer queue occurs in two...

  • Page 89: Interception Of Commands From Control Center

    4. Configuration After that, the events are inserted in the CPU queue. As for Client/Master drivers, the CPU also generates quality events in case of communication failure with the slave device. Note:  HX1110 and HX1120: The modules internally stores the events in a structure containing from one to 32 events.
  • Page 90 4. Configuration bExec: when FALSE, the command just leaves to be intercepted by the user application but it keeps been processed normally by the server. bDone: after the intercepting the command, the user is responsible for treating it. At the end of treatment, this input should be enabled so that a new command can be received.
  • Page 91 4. Configuration Parameter Type Description When true indicates the reception of selection command with bSelectWithValue BOOL value. Table 4-34. sSelectConfig Parameters Parameter Type Description Configuration of the received selection command. Table 4-36 sOperateConfig STRUCT describes the structure’s parameters. Refers to the received operation command. Table 4-37 sValue STRUCT describes the structure’s parameters.
  • Page 92 4. Configuration Parameter Type Description diValue DINT Operation point value. Table 4-40. sIntegerStatus Parameters Parameter Type Description dwValue DWORD Operation point value. Table 4-41. sEnumeratedStatus Parameters Parameter Type Description Informs the data type of the received analog value: eType ENUM INTEGER (0) FLOAT (1) diValue...
  • Page 93 4. Configuration dbpDoublePointIO: DBP; // Variable mapped to the output module Xtorm dbpDoublePointIEC104: DBP; // Variable mapped to IEC 104 Server bSetup: BOOL:= TRUE; // Enables the initial setup of the Interceptor END_VAR IF bSetup THEN // Performs the function Setup in the first cycle CRReceive.dwVariableAddr:=ADR(dbpDoublePointIEC104);...

  • Page 94: Modbus - Data Types

    MODBUS RTU Master This protocol is available for Hadron Xtorm Series CPUs in its serial channels. By selecting this option in MasterTool Xtorm, the CPU becomes the MODBUS communication master, allowing the access to other devices with the same protocol (when in Run Mode).
  • Page 95 4. Configuration Figure 4-11. MODBUS RTU Master General Parameters Configuration Screen Configuration Description Default Options Delay for the answer Send Delay (ms) 0 to 65535 transmission Minimum Interframe Minimum silence time 3.5 to 100.0 (chars) between different frames. Table 4-46. MODBUS RTU Master General Configurations Notes: Send Delay: The answer to a MODBUS request may cause problems in certain moments, as in the RS-485 interface or other half-duplex.
  • Page 96 4. Configuration Diagnostic Variable Size Description T_DIAG_MODBUS_RTU_MASTER_1.* 8: invalid UART RX Threshold parameter 9: invalid time-out parameter 10: busy serial port 11: UART hardware error 12: remote hardware error 20: invalid transmission buffer size 21: invalid signal modem method 22: CTS time-out = true 23: CTS time-out = false 24: transmission time-out error 30: invalid reception buffer size...
  • Page 97 4. Configuration Devices Configuration The slave devices configuration (Figure 4-12), follows the parameters below: Figure 4-12. Device General Parameters Settings Configuration Description Default Options Slave Address MODBUS slave address 0 to 255 Communication Defines the application level time-out 3000 10 to 65535 Time-out (ms) Maximum Number Defines the numbers of retries before...
  • Page 98 4. Configuration Figure 4-13. MODBUS Data Mappings Screen Configuration Description Default Options Name of a variable declared in a program Value Variable Symbolic variable name or GVL Write Coil (1 bit) Read Coil (1 bit) Write Holding Register (16 bits) Read Holding Register (16 bits) Data Type MODBUS data type...
  • Page 99 4. Configuration Data Types Size [bits] Description Coil Writing Writing digital output Coil Reading Reading digital output Writing Register Writing analog output Reading Holding Register Reading analog output Holding Register with AND Analog output which can be read or written mask with AND mask Holding Register with OR...
  • Page 100 4. Configuration Figure 4-14. MODBUS Master Data Requests Screen Default Configuration Description Options Value FC01 – Read Coils FC02 – Read Input Status FC03 – Read Holding Registers FC04 – Read Input Registers FC05 – Write Coil MODBUS function type Function Code FC06 –...
  • Page 101 0x17 Reading/writing of holding registers (FC 23) Table 4-52. MODBUS Functions Supported by Hadron Xtorm CPUs Polling: This parameter indicates how often the communication defined by this request should be executed. When the communication is completed, the CPU waits for the time set in the polling field, and then proceeds to a new communication.
  • Page 102 4. Configuration Write Data Range: This field shows the MODBUS writing data range set for each request. The initial writing address, plus the writing data size result in the writing data range for each one of the requests. Generate Diagnostic Variables: The diagnostics of the configured MODBUS request are stored in T_DIAG_MODBUS_RTU_MAPPING_1 variables (Table 4-53).

  • Page 103: Modbus Rtu Slave

    MainTask is not running. MODBUS RTU Slave This protocol is available for the Hadron Xtorm Series on its serial channels. By selecting this option in MasterTool Xtorm, the CPU becomes a MODBUS communication slave, allowing the connection with MODBUS RTU master devices.
  • Page 104 4. Configuration MODBUS Slave Protocol General Parameters The following pictures show the MODBUS protocol initial screen (Figure 4-15) and its general parameters: Figure 4-15. MODBUS RTU Slave Configuration Screen Configuration Description Default Options Slave Address MODBUS slave address 1 to 255 Table 4-54.
  • Page 105 4. Configuration Diagnostic Variable Size Description T_DIAG_MODBUS_RTU_SLAVE_1 *. The bit bNotRunning was enabled as the bInterruptedByCommand BOOL slave was interrupted by the user through command bits bConfigFailure BOOL Discontinued diagnosis bRXFailure BOOL Discontinued diagnosis bTXFailure BOOL Discontinued diagnosis bModuleFailure BOOL Discontinued diagnosis bDiag_7_reserved BOOL...
  • Page 106 4. Configuration Diagnostic Variable Size Description T_DIAG_MODBUS_RTU_SLAVE_1 *. of a broadcast command, this counter is incremented, but it is not transmitted (0 to 65535). Counter of normal requests received by the slave and answered with exception code. In case of a broadcast command, this counter is incremented, but it is not transmitted (0 to 65535).

  • Page 107: Modbus Ethernet

    MODBUS variables in other controllers or HMIs compatible with the MODBUS TCP protocol or MODBUS RTU via TCP. The Hadron Xtorm CPU functions simultaneously as a client and a server in the same communication network. Regardless if it concerns MODBUS TCP or MODBUS RTU via TCP, this CPU and can even have more instances associated to the Ethernet interface (Table 4-26).
  • Page 108 4. Configuration Figure 4-17 represents some of the communication possibilities using the MODBUS TCP protocol simultaneously with the MODBUS RTU via TCP protocol. Figure 4-17. MODBUS TCP Communication Network The association of MODBUS variables with CPU symbolic variables is made by the user through the definition of the relations via MasterTool Xtorm configuration tool.

  • Page 109: Modbus Ethernet Client

    4. Configuration MODBUS Ethernet Client This protocol is available for all Hadron Xtorm Series CPUs on its Ethernet channels. When selecting this option at MasterTool Xtorm, the CPU becomes a MODBUS communication client, allowing the access to other devices with the same protocol, when in Run Mode.
  • Page 110 4. Configuration Diagnostic Variable Size Description T_DIAG_MODBUS_ETH_CLIENT_1.* Diagnostic Bits: bRunning BOOL The client is in execution mode The client is not in execution mode (see bit: bNotRunning BOOL bInterruptedByCommand) The bit bNotRunning was enabled, as the client bInterruptedByCommand BOOL was interrupted by the user through command bits bConfigFailure BOOL...
  • Page 111 4. Configuration Device Configuration The client devices configuration, depicted on Table 4-61, follows the parameters: Figure 4-19. Device General Parameters Settings Configuration Description Default Options 1.0.0.1 to IP Address Server IP address 0.0.0.0 223.255.255.254 TCP Port TCP Port 2 to 65534 Slave Address MODBUS Slave address 0 to 255...
  • Page 112 4. Configuration Notes: Maximum Simultaneous Requests: It is used with a high scan cycle. This parameter is fixed in 1 (not editable) when the configured protocol is MODBUS RTU via TCP. Communication Time-out: The communication time-out is the time that the client will wait for a server response to the request.
  • Page 113 4. Configuration Default Configuration Description Options Value Variable name declared in a program or Value Variable Symbolic variable name Write Coil (1 bit) Read Coil (1 bit) Write Holding Register (16 bits) Read Holding Register (16 bits) Data Type MODBUS data type Holding Register –...
  • Page 114 4. Configuration Figure 4-21. MODBUS Data Request Screen Default Configuration Description Options Value FC01 – Read Coils FC02 – Read Input Status FC03 – Read Holding Registers FC04 – Read Input Registers FC05 – Write Coil Function Code MODBUS function type FC06 –...
  • Page 115 4. Configuration T_DIAG_MODBUS_ETH_MAPPING_1 variable type for each one of the requests, on the "ReqDiagnostics" GVL. Generate Disabling Variables: The disabling symbolic variables can be generated automatically through the "Generate Disabling Variables" button. A click on it creates a BOOL variable for each one of the requests, on the "Disables"...
  • Page 116 4. Configuration MODBUS Client Diagnostics The diagnostics of the configured MODBUS request are stored in variables of type T_DIAG_MODBUS_ETH_CLIENT_1 which are described in Table 4-67. Diagnostic Variable Size Description T_DIAG_MODBUS_ETH_MAPPING_1.* Communication Status Bits: bCommIdle BOOL Communication idle (waiting to be executed) bCommExecuting BOOL Active communication...

  • Page 117: Modbus Ethernet Server

    Table 4-67. MODBUS Client Relations Diagnostics Exception Codes: the definitions of the exception codes 128, 129 and 255 are valid only with Altus slaves. For slaves from other manufacturers these exception codes can have different meanings. Disabling Variable: Field for the variable used to disable MODBUS requests individually configured in Requests tab.
  • Page 118 4. Configuration The following items describe each one of these settings. MODBUS Server Protocol General Parameters The general parameters, found on the MODBUS protocol configuration initial screen (Figure 4-22), are defined as: Figure 4-22. MODBUS Server General Parameters Settings Configuration Description Default Options...
  • Page 119 4. Configuration Communication Times The communication times of the MODBUS server protocol, found on the “Advanced...” button of the configuration screen, are divided into: Task Cycle and Connection Inactivity Time-out. Configuration Description Default Value Options Time for the instance execution Task Cycle within the cycle, without considering 5 to 100...
  • Page 120 4. Configuration Diagnostics Variable Size Description T_DIAG_MODBUS_ETH_SERVER_1 *. Communication statistics: Number of established connections wActiveConnections WORD between client and server (0 to 64). Connections counter, between the client wTimeoutClosedConnections WORD and server, interrupted after a period of inactivity-time-out (0 to 65535). Connections counter interrupted due to wClientClosedConnections WORD...
  • Page 121 4. Configuration Configurations Description Default Possibilities Name of a variable declared in a program or Value Variable Symbolic variable name Coil Input Status DataType MODBUS data type Holding Register Input Register Data Start Starting address of the MODBUS 1 to 65536 Address data Absolute start address of the...

  • Page 122: Dnp3 - Data Types

    Table 4-73. DNP3 Variable Declaration DNP3 Ethernet Client This protocol is available for the Hadron Xtorm Series CPUs on its Ethernet channels. When selecting this option at MasterTool Xtorm, the CPU becomes a client of the DNP3 communication. HX3040 CPUs support up to 12 drivers for communication. Therefore, the top limit of instantiating for DNP3 Client drivers also depends on how many drivers of other protocols are instantiated.
  • Page 123 4. Configuration  Add the DNP3 Client protocol to one of the available Ethernet channels (NET 1 to NET 6).  To execute this procedure, see Inserting a Protocol Instance.  Set the Ethernet interface. See Ethernet Interfaces Configuration  Set the general parameters of the DNP3 Client protocol with the Link Address.
  • Page 124 4. Configuration Figure 4-25. DNP3 Client Data Mapping Configurations Descriptions Default Possibilities Name of a variable declared in a program or Value Variable Name of the symbolic variable g01 – Binary Input g03 – Double Binary Input g10 – Binary Output g20 –...
  • Page 125 4. Configuration Notes: Value Variable: Name of the symbolic variable to be mapped. When a reading command is sent, the return sent in response will be stored in this variable. In case of a writing command, the written value is also stored in this variable. The variable may be simple, array or array element and may be in structures.
  • Page 126 4. Configuration Figure 4-26. Configuration Screen of the DNP3 Client Link Layer Configurations Description Default Possibilities Address Outstation Origin DNP3 Address 0 to 65519 (Outstation) IP Address Outstation IP Address 0.0.0.0 1.0.0.1 to 223.255.255.254 Listen port address for Outstation TCP Port 20000 0 to 65535 connection...
  • Page 127 4. Configuration Maximum Retries: Number of times that the DNP3 Client device relays the message if it does not receive the client's confirmation. To enable it, select the options “Always” or “Sometimes” in the field “Sends Confirmed User Data Frames”. Confirmation Time-Out (s): Determines what is the time (in seconds) for the “DNP3 Client”...
  • Page 128 4. Configuration Configurations Description Default Possibilities Time-out to Waiting for Maximum time the outstation Complete Application waits for complete response 1 to 86400 Layer Response (s) of the application layer Maximum time for the Select Command Time- execution of selection 100 to 10000 out (ms) command...
  • Page 129 4. Configuration Custom Requests of the DNP3 Client The configuration of the DNP3 Server relations (Figure 4-28), follow the parameters shown below (Table 4-79): Figure 4-28. Message Screen of DNP3 Client Custom Requests Configurations Description Default Possibilities g04v00 - Double-bit binary input event with default variation.
  • Page 130 4. Configuration Configurations Description Default Possibilities g22v05 - Counter event 32 bits with flag and time. g22v06 - Counter event 16 bits with flag and time. g23v00 - Frozen counter event any variation. g23v01 - Frozen counter event 32 bits with flag.
  • Page 131 4. Configuration Configurations Description Default Possibilities Sets the period (ms) that Polling (ms) 1000 0 to 86400000 the request occurs. Name of the symbolic Name of a variable declared in a program or Diagnostic Variable variable that will receive the diagnosis of request. Table 4-79.
  • Page 132 4. Configuration Object Variation Allowed Qualifier g22v00 - Counter event default variation. g22v01 - Counter event 32 bits with flag. g22v02 - Counter event 16 bits with flag. Counter g22v05 - Counter event 32 bits with flag and time. g22v06 - Counter event 16 bits with flag and time. g23v00 - Frozen counter event any variation.
  • Page 133 4. Configuration Diagnostic Variable Size Description T_DIAG_DNP_CLIENT_REQUEST_1.* Transport Layer. dwReserved_0 DWORD Reserved dwReserved_1 DWORD Reserved dwReserved_0 DWORD Reserved dwReserved_1 DWORD Reserved Request Diagnostics CLOSED BYTE Closed communication with the IED eConnection Status CONNECTED BYTE Operative communication with the IED SUCCESS BYTE Indication of successful request Indicates that a response has been received,...
  • Page 134 4. Configuration Requests Diagnostics: From all the bits available in the tIIN structure, only three of them are actually related to the request (NO_FUNC_CODE_SUPPORT, OBJECT_UNKNOWN and PARAMETER_ERROR). All the others are related to the Outstation to which the request is addressed to.
  • Page 135 Hadron Xtorm Series Module, for example). The modules have to support this functionality, though. If you use a bus expansion of Hadron Xtorm Series mixed to Nexto Series, but the digital output module does not support this functionality, the CPU returns the following error code: DNP3_COMMAND_ERROR_STATUS_NOT_SUPPORTED.
  • Page 136 4. Configuration Parameter Type Description Status of execution, indicates if a new command can be sent. The values are as follows: eExecStatus ENUM (BYTE) DNP3_COMMAND_EXEC_STATUS_DONE (0) DNP3_COMMAND_EXEC_STATUS_RUNNING (1) Indicates whether the last command was successful. DNP3_COMMAND_ERROR_STATUS_NO_ERROR (0) DNP3_COMMAND_ERROR_STATUS_TIMEOUT (1) DNP3_COMMAND_ERROR_STATUS_NO_SELECT (2) DNP3_COMMAND_ERROR_STATUS_FORMAT_ERROR (3) DNP3_COMMAND_ERROR_STATUS_NOT_SUPPORTED (4) eErrorStatus...
  • Page 137 4. Configuration Parameter Type Description bRequest BOOL When TRUE, executes the command dwVariableAddr DWORD Command variable address to send UNSIGNED udiCommandTimeOut Time for timeout of this command DOUBLE INT Table 4-89. DNP3_ColdCommand Block Input Parameters Parameter Type Description Status of execution, indicates if a new command can be sent. The values are as follows: eExecStatus ENUM (BYTE)

  • Page 138: Dnp3 Ethernet Server

    Table 4-91. Status Code for DNP Commands DNP3 Ethernet Server This protocol is available for Hadron Xtorm Series CPUs in its Ethernet channels. When you select this option in MasterTool Xtorm, the CPU becomes DNP3 communication server, allowing connection with up to five DNP3 client devices. For each client, the driver has a unique event queue with the following characteristics ...
  • Page 139 4. Configuration  Set the link layer parameters, specifying the response fragmentation, confirmation messages, integrity polling, timing, commands and event queue.  Set the unrequested message parameters, specifying the control parameters and trigger conditions. The following items describe each one of these settings. Configuration of the DNP3 Server Mappings The general configuration of the DNP3 Server (Figure 4-29) follow the parameters shown below (Table 4-92):...
  • Page 140 4. Configuration Configurations Description Default Possibilities g3v1 – Double-bit binary input packed format g3v2 – Double-bit binary input with flags g40v1 –Analog output status 32 bits with flag g40v2 –Analog output status 16 bits with flag g40v3 –Analog output status single precision, floating-point with flag g22v1 –...
  • Page 141 4. Configuration Event Group and Default Variation: The field is used to set the range for the events that will be returned if the DNP3 client does not specify a variation in the request data, or in the case of unsolicited messages.
  • Page 142 4. Configuration Figure 4-31. DNP3 Server Link Layer Configuration Screen Configurations Description Default Possibilities Address DNP3 address of this server 0 to 65519 (Outstation) Address (Master) DNP3 Address of the connected client. 0 to 65519 IP Address IP of the connected client (used when the 0.0.0.0 1.0.0.1 to 223.255.255.254 (Master)
  • Page 143 4. Configuration fields. The message “Source Address” must match the “Destination Address” set for the Client. Similarly, the message “Destination Address” must match the “Source Address” set by the Client. Enable Self-address: Enables the reception of messages with the 65532 address of the DNP3 client. Sends Confirmed User Data Frames: The following confirmation modes for the link layer are available: Function Type...
  • Page 144 4. Configuration Configurations Description Default Possibilities Allow Multiple Option to Enable/Disable Response Disabled Fragmented Enabled Transmission with Multiple Fragments Enabled Responses Request Confirmation Option to Enable/Disable Response Disabled of Multiple Fragmented Confirmation Request with Multiple Enabled Enabled Responses Fragments TX Fragmented Length Maximum size of the fragments 2048 249 to 2948...
  • Page 145 4. Configuration Configuration of the DNP3 Server Unrequested Messages The configuration of the DNP3 Server relations (Figure 4-33), follow the parameters shown below (Table 4-99): Figure 4-33. DNP3 Server Unsolicited Messages Configuration Screen Configurations Description Default Possibilities Enable Option to Enable/Disable unsolicited Disabled Unsolicited Enabled...
  • Page 146 4. Configuration Enable Unsolicited Messages: This option enables the DNP3 server to allow unrequested messages. Number of Unsolicited Retries: Number of times the DNP3 server will try to retransmit the message. Confirmation Time-out(s): Specifies the time to be waits after a time-out for the unsolicited message that was transmitted.
  • Page 147 4. Configuration Diagnostic Variable T_DIAG_DNP_SERVER_1.* Size Description Mask used to indicate dwUnsolEna DWORD which classes are enabled the unsolicited messages. dwReserved_1 DWORD Reserved Number of frames wRXFrames WORD received wTXFrames WORD Number of frames sent Communication error counter including errors in tStats wCommErrors WORD...

  • Page 148: Iec 60870-5-104 - Data Types

    4. Configuration DNP3 Client Driver If the variable is associated to an IED point in a DNP3 Client driver, the command is redirected and sent to be executed by the IED itself and the value of the variable stored in the CPU memory is not updated.

  • Page 149: Iec 60870-5-104 Server

    IF bTransient THEN usiVTI := usiVTI OR 16#80; END_IF IEC 60870-5-104 Server This protocol is available for Hadron Xtorm Series CPUs in its Ethernet channels. When you select this option in MasterTool Xtorm, the CPU becomes IEC 60870-5-104 communication server,...
  • Page 150 4. Configuration allowing connection with up to five IEC 60870-5-104 client devices. For each client, the driver has a unique event queue with the following characteristics  Size: 4.500 events  Overflow policy: keeps the most recent event Follow the steps below in order to set this protocol: ...
  • Page 151 4. Configuration Parameter Description Default Possibilities Value Variable Symbolic variable name Variable name declared in a program or GVL Single Point Information Double Point Information Step Position Information Measured Value (Normalized) Measured Value (Scaled) Measured Value (Short Floating Point) Configruation of the IEC 60870- Object Type Integrated Totals 5-104 object type...
  • Page 152 4. Configuration New values of the dead band variable will be considered just when an analog input variable changes its value. Dead Band Type: The following dead band settings are available: Function Type Configurations Description In this option, any value variation in a group's Disabled point, however small, generates event to this point.
  • Page 153 4. Configuration Parameter Description Default Possibilities Listen port address for client connection (used Port Number 2404 1 a 65535 when the client connection is not IP). IP Address IP of the connected client (used when the 0.0.0.0 1.0.0.1 a 223.255.255.254 (Master) client connection is IP).
  • Page 154 4. Configuration Parameter Description Default Possibilities Enable Time Option to Enable/Disable time Disabled Disabled Synchronization synchronization request. Enabled Period in which the selection Maximum Time command remains active (starts Between Select and counting from the confirmation of 1 a 180 Operate (s) receipt of the selection command) waiting for the Operate command.
  • Page 155 4. Configuration Function Type Configurations Description It is equivalent to Mode D of counters acquisition (integrated totals) defined by IEC 60870-5-104. Freeze by conter- In this mode, counters' interrogation commands interrogation command, (freeze) from the control stations will freeze the transmit spontaneously counters.
  • Page 156 4. Configuration Diagnostic Variable T_DIAG_IEC104_SERVER_1.* Size Description wSize WORD Queue size wUsage WORD Number of events in the queue dwReserved_0 DWORD Reserved dwReserved_1 DWORD Reserved wRXFrames WORD Number of frames received wTXFrames WORD Number of frames sent Communication error counter including errors in the Physical tStats wCommErrors...
  • Page 157 4. Configuration Output Module If the variable mapped to the IEC 60870-5-104 output point is associated to an output card (e.g. HX2320) from Xtorm Series, the command will be redirected and executed by the card itself. In case of pulsed commands, this redirection will work only if the variable is the of DBP type. If a variable of type BOOL is used, the IEC 60870-5-104 server returns a negative confirmation message (failure) for pulsed commands, as well as when a persistent command is directed to a BPD variable mapped in the output card.

  • Page 158: Iec61850 Server

    CommandReceiver function block. IEC61850 Server This protocol is available for the CPU Hadron Xtorm Series in your Ethernet channels. When you select this option in MasterTool Xtorm, the CPU becomes the IEC61850 communication server, allowing connection with IEC61850 clients via MMS protocol and also enabling the sending and receiving of fast messages via GOOSE protocol.
  • Page 159 4. Configuration  Add an instance of IEC61850 Server protocol to one of the available Ethernet channels (NET 1 to NET 6). To perform this procedure, see chapter Inserting a Protocol Instance.  Configure the Ethernet interface. To perform this procedure, see chapter Ethernet Interfaces Configuration ...
  • Page 160 4. Configuration The implementation of the IEC 61850 data structure in MasterTool Xtorm IEC 61131-3 programming environment is achieved by POUs of Function Block type. The Logical Devices, Logical Nodes and Objects are represented by a Function Block, while Attributes become symbolic variables of elementary types according to IEC 61131-3.
  • Page 161 4. Configuration The enumerated data types have a set of elements whose values are named. The Table 4-114 below describes the values (in decimal base) that represent in the RTU memory each one of the elements names: Value (Common Attribute Identifier (decimal) Data Class)
  • Page 162 4. Configuration Value (Common Attribute Identifier (decimal) Data Class) pos-neg-zero dir-quad-zero angRef Vother Aother Table 4-114. Elements represented in the RTU memory Due to the flexibility of STRING type attributes size, the implementation of these elements in the IEC 61131-3 environment is performed differently from the others. Instead of directly storing the string character set, the symbolic variable that represents the attribute stores only a reference to a table where, in fact, the string is.
  • Page 163 4. Configuration In this example, the attribute "d" of the Object NamPlt is VisString255 type and its corresponding symbolic variable is: gfbIEC61850_LogicalDevice.LLN0.fbNamPlt.d_REF Thus, to assign the value "TEST" to this attribute in ST language: gaVisSTRING255[gfbIEC61850_LogicalDevice.GGIO4.fbNamPlt.d_REF]:= 'TEST'; Database Configuration The configuration of the IEC61850 Server protocol Database is performed through the Configuration tab from the inclusion of a Logical Device and their respective Logical Nodes: Figure 4-41.
  • Page 164 4. Configuration Figure 4-42. Adding and Configuring the Logical Device Name The Logical Device is an abstraction level of the data model defined in IEC61850, and aims to organize the data. The IEC61850 Server driver supports only one Logical Device, and its name can be changed through the Device Name field.
  • Page 165 4. Configuration Figure 4-43. Adding a Logical Node By clicking on a configured Logical Node, the user can modify its prefix and its index through the fields Node Prefix and Logical Node Index. In addition, it is possible to add and remove optional Data Objects.
  • Page 166 4. Configuration The Table 4-116 shows all configuration fields present on this screen, informing their default values and configuration possibilities: Configurations Description Default Possibilities Set of up to 80 characters (letters, Server Name Define the Physical Device name Server numbers and underline) Set of up to 32 characters (letters, Device Name Define the Logical Device name...
  • Page 167 Additionally, the Hadron Xtorm RTU supports the Dynamic Datasets feature, which allows a 61850 Client to create datasets during runtime. After creating a dataset, it is possible to associate it to an existing Report Control Block.
  • Page 168 4. Configuration The Table 4-117 shows all configuration fields present on this screen, informing their default values and configuration possibilities: Configurations Description Default Possibilities Sets the size (in bytes) of the events Buffersize 5000 0 to 4294967295 buffer (for Buffered Reports) Name to identify this Report Control Set of up to 32 characters (letters, Name...
  • Page 169 4. Configuration Notes: Buffersize: This parameter is not used by IEC 61850 Server driver. The buffer size is fixed at 20Kbytes for each Buffered Report Control Block. Data Update: This option is not supported, in this way, is not used by the driver. General Interrogation: This option is not supported, in this way, is not used by the driver.
  • Page 170 4. Configuration The comparison activities of the dataset and message sending performed by each control block, are associated with the RTU task. If the Fast Goose option is enabled, the Control Block performs these activities in ProtTask, which is a cyclic task of high priority with very short interval (default is 4 ms), thus allowing to set extremely fast GOOSE messages to meet performance requirements for critical parts of the system.
  • Page 171 4. Configuration Figure 4-48. Importing a SCL File Click the Import button and select the desired SCL file. The CPU opens a screen with a list of its Physical Devices and Logical Devices. Click on a Logical Device and check the GOOSE messages list (Control Blocks) on the bottom of the screen.
  • Page 172 4. Configuration The right side of the screen shows the message-related information that will be received. These fields are automatically filled in by importing the data in the GOOSE Control Block associated to the message. Thus, do not modify them. The bottom of this screen displays the data contained in the selected message, where you can configure which elements of the received dataset will be effectively stored in the RTU memory.
  • Page 173 4. Configuration If the Source Variable is associated to a source able of generating events with own time stamp (DNP3 IED or digital input module, for example), the IEC 61850 Server driver will receive these events and update the attribute “t” (Timestamp) of the object concerning the attribute that was mapped, so as to behave as a “consumer”.

  • Page 174: Communcation Performance

    Communcation Performance MODBUS Communication Performance The configurable MODBUS devices in Hadron Xtorm CPUs run in a cyclical way and in background, that is, with a priority below the user application. Thus, its performance will vary according to the remaining time, taking into account the difference between the interval and the...
  • Page 175 4. Configuration 50 ms runtime, will have a lower performance than an application of 25 ms that runs at every 100 ms interval. This is because, in the second case, the CPU will take a longer time between each MainTask cycle to perform the lowest priority tasks.

  • Page 176: Dnp3 Communication Performance

    4. Configuration ATTENTION: Notice that the communication performance presented in this chapter are examples using a CPU with only one MODBUS TCP Server device. Thus, there is not any logic in the application that could delay the communication. Therefore, take these performances as maximum ones. As to cycle times equal or larger than 20 ms, the increase of the response rate is linear.

  • Page 177: Iec 60870-5-104 Communication Performance

    4. Configuration IEC 60870-5-104 Communication Performance IEC 60870-5-104 Server The CPU runs the IEC 60870-5-104 Server driver in the same way as other communication Server drivers, i.e., in background, cyclically, and with a priority below the user application. The task of this driver specifically runs at every 50ms, and just 1 run cycle of the driver is enough to process and respond requests.

  • Page 178: Memory Card

    Further information on memory card, see Configuration - Memory Card. RTC Clock Hadron Xtorm Series CPUs have an internal clock that can be used through the LibPlcStandard.lib. This library is automatically loaded during the creation of a new project (to add libraries, see...

  • Page 179: Function Blocks And Functions For Rtc Reading And Writing

    4. Configuration Figure 4-51. RTC Writing and Reading Function Blocks Function Blocks and Functions for RTC Reading and Writing Among other function blocks, there are four which are very important for clock reading (GetDateAndTime and GetTimeZone) and for date/time settings (SetDateAndTime and SetTimeZone).
  • Page 180 4. Configuration When called, the function will read the clock current value and fill the DATEANDTIME structure. The function returns the reading result. Example in ST: PROGRAM UserPrg xStatus : RTC_CMD_STATUS; DateAndTime : EXTENDED_DATE_AND_TIME; xRead : BOOL; END_VAR -------------------------------------------------------------------------- IF (xRead = TRUE) THEN xStatus := GetDateAndTime(DateAndTime);...
  • Page 181 4. Configuration Example in ST: PROGRAM UserPrg RTCStatus : RTC_CMD_STATUS; TimeZone : TIMEZONESETTINGS; xRead : BOOL; END_VAR -------------------------------------------------------------------------- //FB GetTimeZone IF (xRead = TRUE) THEN GetTimeZone (TimeZone); xRead := FALSE; END_IF Function Blocks and Functions for RTC Writing and Configuration SetDateAndTime The SetDateAndTime function block configures the clock: Figure 4-52.
  • Page 182 4. Configuration SetDateAndTime : SetDateAndTime; xRequest : BOOL; DateAndTime : EXTENDED_DATE_AND_TIME; xDone : BOOL; xExec : BOOL; xError : BOOL; RTCStatus : RTC_CMD_STATUS; xWrite : BOOL; END_VAR -------------------------------------------------------------------------- IF (xWrite = TRUE) THEN SetDateAndTime( Request := xRequest, DateAndTime := DateAndTime, Done =>...

  • Page 183: Rtc Data Structure

    STATUS output parameter. For further details on the STATUS output parameter, see the correspondent section. RTC Data Structure The RTC Reading and Setting function blocks of Hadron Xtorm Series CPU use the following data structure. EXTENDED_DATE_AND_TIME...

  • Page 184: User Files Memory

    User Files Memory Hadron Xtorm Series CPUs have a memory area destined to general data storage, in other words, the user can store several project files of any format in the CPU memory. This memory area varies according to the CPU model.
  • Page 185 4. Configuration Figure 4-53. User Files Access After updating the CPU files column, the root directory of the CPU stored files will be shown. Then, select the folder where the files should be transfer to. Use the default “InternalMemory” folder to store the files in the CPU’s internal memory (32 Mbytes), since it is not possible to transfer them to the root directory.
  • Page 186 4. Configuration Figure 4-54. Transferring Files ATTENTION: The files contained in the folder of a project created by MasterTool Xtorm tool have special names reserved by the system in this way cannot be transferred through the Files tab. If the user wishes to transfer a project to the user memory, you must compact the folder and then download the compressed file (* .zip for example).

  • Page 187: Memory Card

    Kbytes/s. Memory Card Among other memories, the Hadron Xtorm Series CPUs allow the user the utilization of a memory card. It is defined according the features described in Technical Description, which stores, amongst other files, the project and the CPU internal memory application.
  • Page 188 4. Configuration Figure 4-56. Memory Card Settings When a password is configured for the memory card in MasterTool, it is necessary to perform the following steps so that when the project is sent, the encrypted file which is created by MasterTool has the password included in its content and it is also sent.

  • Page 189: Access In Mastertool

    4. Configuration ATTENTION: If there is any file in the memory card root named “Application” or “Backup”, it will be deleted so as to create the system folders with the same name. The CPU uses such folders to store both the application and the project archive.

  • Page 190: Informative Menu And Of Cpu's Configuration

    Application.app, Application.crc, Archive.prj, Stdlogger.csv Informative Menu and of CPU’s Configuration The access to the Informative Menu and of Hadron Xtorm CPU’s Configuration as well as the detailed access of diagnostics, are available through levels, for menu’s information access, change levels and modify some Configuration, just a long press in OTD button is necessary, to surf between items in the same level, only a short press is necessary in OTD button.
  • Page 191 4. Configuration Level 1 Level 2 Level 3 Type TEMPERATURE Informative CONTRAST CONTRAST LEVEL Configurable HARDWARE DATE AND TIME Informative BACK Back Level ENGLISH >ENGLISH Configurable PORTUGUES >PORTUGUES Configurable LANGUAGE ESPANOL >ESPANOL Configurable VOLTAR Back Level NET 1 IP ADDRESS Informative NET 1 MASK Informative...
  • Page 192 BACKUP – Does a CPU’s data backup on memory card The Figure 4-59describes an example of how to operate Hadron Xtorm CPU’s menu, through CPU’s adjust contrast procedure in Status in screen. In addition to turn easier the configuration, it’s possible to identify all levels and each type of pressing to navigate between them, to modify other parameters, as Language and insert the password (s) of Memory Card, just following the same access rules.

  • Page 193: Function Blocks And Functions

    4. Configuration Figure 4-59. Contrast Adjustment In addition to the Hadron Xtorm CPU's menu be terminated by a long press in the diagnostics button on the BACK screen at level 1, there are also another conditions of leaving, they are described below: ...
  • Page 194 4. Configuration ATTENTION: REFRESH_INTPUT function does not support the update of any inputs that have been mapped to symbolic variables. For its proper operation, map the input to a variable within the memory of direct representation input variables (%I). Figure 4-60. Function for Input Updating Input Parameters Type Description...

  • Page 195: Retaintimer

    4. Configuration ATTENTION: REFRESH_OUTPUT function does not support the update of any outputs that have been mapped to symbolic variables. For its proper operation, map the input to a variable within the memory of direct representation output variables (%Q). Figure 4-61. Function for Output Updating Input Parameters Type Description...
  • Page 196 4. Configuration TOF_RET The function block TOF_RET implements a time delay to disable an output. When the input IN has its state changed from TRUE to FALSE (falling edge), the specified time PT will be counted and the Q output will be driven to FALSE at the end of it. When input IN is in logic level 1 (TRUE), output Q remains in the same state (TRUE), even if this happened in the middle of the counting process.
  • Page 197 4. Configuration // Actions executed at the end of the counting IF (TOF_RET.Q = FALSE) THEN bStart := TRUE; END_IF TON_RET The function block TON_RET implements a time delay to enable an output. When the input IN has its state changed from FALSE to TRUE (rising edge), the specified time PT will be counted and the Q output will be driven to TRUE at the end of it.
  • Page 198 4. Configuration Example in ST: PROGRAM UserPrg VAR RETAIN bStart : BOOL; TON_RET : TON_RET; END_VAR // When bStart=TRUE starts counting TON_RET(IN := bStart, PT := T#20S); // Actions executed at the end of the counting IF (TON_RET.Q = TRUE) THEN bStart := FALSE;...

  • Page 199: Non-Redundant Timer

    4. Configuration Figure 4-67. TP_RET Function Block Graphic Behavior Example in ST: PROGRAM UserPrg VAR RETAIN bStart : BOOL; TP_RET : TP_RET; END_VAR // Sets TP_NR TP_RET(IN := bStart, PT := T#20S); bStart := FALSE; // Actions performed during the counting IF (TP_RET.Q = TRUE) THEN // It executes while the counter is activated ELSE...
  • Page 200 4. Configuration Example in ST: PROGRAM NonSkippedProg bStart : BOOL := TRUE; TOF_NR : TOF_NR; END_VAR // When bStart=FALSE starts the counting TOF_NR(IN := bStart, PT := T#20S); // Actions performed at the end of the counting IF (TOF_NR.Q = FALSE) THEN bStart := TRUE;...

  • Page 201: User Log

    4. Configuration Example in ST: PROGRAM NonSkippedProg bStart : BOOL; TP_NR : TP_NR; END_VAR // Sets TP_NR TP_NR(IN := bStart, PT := T#20S); bStart := FALSE; // Actions performed during the counting IF (TP_NR.Q = TRUE) THEN // It executes while the counter is activated ELSE // It executes when the counter is deactivated END_IF...
  • Page 202 4. Configuration ATTENTION: User Logs are available starting from version 1.1.0.12 of the Hadron Xtorm CPU. And to use this functionality, MasterTool Xtorm version 1.10 or higher is required. UserLogAdd This function is used to add a new user log message, adding a new line to the log file in the memory card.
  • Page 203 4. Configuration If a file presents an access problem (bad sector) and it is not possible to continue writing, the extension "corrupted" will be added to the name of this file and a new file will be created. The number of logs per file is not fixed, varying according to the size of the messages. The number of files created is limited to 1024 with a maximum size of 1MB each, so the memory card requires 1GB of free space.

  • Page 204: Clearrtudiagnostic

    4. Configuration IF (m_DeleteLogs = TRUE) THEN eLogError := UserLogDeleteAll(); m_DeleteLogs := FALSE; // ‘eLogError’ variable will receive possible function errors END_IF ATENTION: The return of the UserLogDeleteAll function does not indicate complete operation, only execution confirmation, which can take a long time if there are too many log files in the directory. The function to register new user logs will be unavailable during this time, returning the code USER_LOG_PROCESSING for any operation.

  • Page 205: User Management And Access Rights

    4. Configuration Example in ST, where the function call cleans the event queue and, consequently, reset all the communication drivers event queue occupancy diagnostics T_DIAG_DNP_SERVER_1.tClient_*.tQueueDiags.wUsage: PROGRAM UserPrg ClearEventQueueStatus : Type_Result; END_VAR ClearEventQueueStatus := ClearEventQueue(); User Management and Access Rights Provide functions to define user accounts and configure access rights to the project. Note that the specific user management device must be supported to control the access rights in the CP file system and objects at runtime.
  • Page 206 4. Configuration Users Figure 4-73. Project Settings, Users and Groups Registered current users are listed in a tree structure. Through the Add or Edit commands you can display beside Name (login), the full name and the user description. Each user's properties can be viewed or not (are hidden) through the plus and minus sign respectively.
  • Page 207 4. Configuration To define a new user account, use the Add button to open the Add User dialog. Figure 4-74. Adding an User Account properties owns the following fields:  Logon name: new users logon name.  Full name: new user’s full name. Just useful as additional information. ...
  • Page 208 4. Configuration To delete one or more user accounts, select their users in the appropriate list and press Remove. Note that this action does not require confirmation. You can not delete all group members (at least one must remain). If you try this, an error message will be shown. Groups Figure 4-75.
  • Page 209 4. Configuration To add a new group, use the Add button and open the corresponding dialog. Figure 4-76. Add Group The following fields must be filled:  Name: new group’s name.  Description: new group’s description. Serves only as additional information. ...
  • Page 210 4. Configuration Settings Figure 4-77. Project Settings, User and Groups Settings The following basic configurations of user accounts can be done:  Maximum number of authentication trials: if this option is enabled, the user account will become invalid after the specified number of attempts to carry out the login with the wrong password. If the option is not enabled, the user can perform as many attempts as you want.
  • Page 211 4. Configuration denied to MainPrg and to a certain group of users, the default value of this right to ACT would also be "denied" automatically. To access Permissions screen user must click on this option in Project menu, after User Management >...

  • Page 212: Ucp's User Management And Access Rights

    4. Configuration  : The right to perform one or more actions selected in the Actions window is not guaranteed explicitly, but by default, due to that right has been guaranteed to the "main" object. Basically this is the default setting for all the rights that have not been explicitly configured. ...
  • Page 213 4. Configuration Users and Groups The dialog Users and Groups is provided in a dialogue guide Device. It allows you to configure user and group accounts that, together with the management of access rights control access to objects in the PLC in online mode. Common For some functions of a controller that can be performed only by authorized users, uses the Online User Management.
  • Page 214 4. Configuration ATTENTION: By opening this dialogue the fields Password and Confirm password will be filled with fictitious characters, the user must replace these characters for a valid password. Figure 4-81. Adding User : the Import Users dialog shows all the names of users currently defined in the project user management.
  • Page 215 Table 4-148. Users and Groups Users and Groups Default The following groups and users are defined by default in the Hadron Xtorm Series CPUs. This division into a larger number of groups is to present an initial proposal for different levels of users who can access the CPU.
  • Page 216 4. Configuration Watch Group Group created to define access rights to users who can only view without making any modification in the application, if not used this group can be deleted. Administrator User The Administrator user is defined in the Everyone and Administrator groups. The default password for the Administrator user is "Administrator"...
  • Page 217 4. Configuration Access rights (add / remove children, execute, modify and view) are configured for each device and enable for each user actions according to. Relevant rights Add / Devices Action remove Execute Modify View children Device Login Logger Read Log inputs Application Login Download application to a CPU without...
  • Page 218 4. Configuration Modify (for example, send applications, etc.) View (monitoring) Objects (action “devices”) In each action node type, are the "devices" (objects) of action (e.g., Device). These objects mapped in the device tree or structure of the file system, are displayed in a structured way.
  • Page 219 4. Configuration In the new UCP Xtorm or updated CPU, run the command Load from Disk, and selecting the file generated before eventually execute command Download to Device, thus sending the settings for the CPU.

  • Page 220: Initial Programming

    5. Initial Programming 5. Initial Programming The main goal of this chapter is to help in the programming and configuration of Hadron Xtorm Series CPUs so that the user will be able to take the first steps before starting a controller programming.
  • Page 221 5. Initial Programming SIGNIFICANCE OVERLAPPING Byte Word DWord LWord Byte Word DWord %QX0.7 %QX0.6 %QX0.5 %QB00 %QX0.4 %QB00 %QX0.3 %QX0.2 %QX0.1 %QX0.0 %QW00 %QW00 %QX1.7 %QX1.6 %QX1.5 %QX1.4 %QB01 %QB01 %QX1.3 %QX1.2 %QX1.1 %QD00 %QX1.0 %QD00 %QW01 %QX2.7 %QX2.6 %QX2.5 %QX2.4 %QB02 %QB02...

  • Page 222: Project Profiles

    5. Initial Programming The Table 5-2 shows the organization and memory access, illustrating the significance of bytes and the disposition of other variable types, including overlapping. Project Profiles A project profile in MasterTool Xtorm is a group of rules, common features and patterns used in the development of an industrial automation solution.

  • Page 223: Custom Profile

    The Custom project profile allows the developer to exploit all Runtime System potentialities, implemented in the Hadron Xtorm Series processing centrals. None of the functionalities is disabled; neither any priority nor association between task and programs is imposed. It is also possible to create tasks and programs with any names, except for “MainTask”, “StartPrg”, “MainPrg”,...

  • Page 224: New Project

    5. Initial Programming Default Task Priority Type Options Event value MainTask MainPrg Cyclic 20 ms CyclicTask00 CyclicPrg00 Cyclic 200 ms CyclicTask01 CyclicPrg01 Cyclic 500 ms ExternInterruptTask00 ExternInterruptPrg00 External COM1_CTS TimeInterruptTask00 TimeInterruptPrg00 Cyclic 20 ms ExternInterruptTask01 ExternInterruptPrg01 External COM1_DCD TimeInterruptTask01 TimeInterruptPrg01 Cyclic 30 ms Freewhe...
  • Page 225 5. Initial Programming Later, a window will be presented to the user, requesting the selection of the project type and the name and path to store the project in the computer. Click on OK to proceed or Cancel. Figure 5-2. Project Classification Next, select the desired CPU, the basic hardware modules that form the bus, that is, the model of both backplane rack and power supply and the redundancy configuration.
  • Page 226 5. Initial Programming Figure 5-3. Features Selection By choosing “Redundancy”, the system automatically selects the option for power supply redundancy. Notice that projects with CPU redundancy necessarily request power supply redundancy. Figure 5-4 exhibits the screen with this option selected. Figure 5-4.
  • Page 227 5. Initial Programming On the next screen, choose the number of modules to be used in the project. Then, the wizard will automatically create the objects of these modules within the project. Figure 5-5. Options of I/O Modules...
  • Page 228 5. Initial Programming Then, select the profile and the default language for POUs (programs). The example below shows RTU profile without redundancy and ST language. Click Next to continue or Cancel to abort the creation of project. Figure 5-6. Features Selection of the Project Profile...

  • Page 229: Adding Modules

    5. Initial Programming The next screen defines the language of the POU created by the selected profile. As the created profile is non-redundant, there are only two POUs (UserPrg) / (StartPrg) and the ST language remains the same. Click on Previous to return to the last screen, Finish to end or Cancel to abort the process.
  • Page 230 5. Initial Programming Figure 5-8. Library Visualization Then, select the module to be inserted and drag it to the bus configuration area, by pressing the left button of the mouse. Figure 5-9. Adding Modules...

  • Page 231: Creating Pous

    5. Initial Programming Creating POUs A POU (Program Organization Unit) is a subdivision from the applicative program, which can be written in any language available in the software. With the project creation through a selected profile, some POUs are already created. It is possible to create more POUs, up to the maximum limit of the program memory size.
  • Page 232 5. Initial Programming Figure 5-11. POU Classification To edit a POU, select the tab with the correspondent name and start the application development in the chosen language. The same procedure is valid for the POUs created automatically by the project profile.

  • Page 233: Creating Tasks

    5. Initial Programming Creating Tasks A POU must be related to a task to be executed. This scaling mechanism, called Task, is very useful for real time systems, which are defined as periodic execution, or under request of an event (change of state of any Boolean variable).

  • Page 234: Task Configuration

    5. Initial Programming Figure 5-14. Task Name Task Configuration After the task is open, the configuration window will appear for the user to define and classify its functioning. The field “Priority (0...31)” establishes the priority in which the task will be executed in the application, where zero is the highest priority.
  • Page 235 5. Initial Programming The field “Sensitivity” refers to how many times the watchdog will be achieved to activate the bWatchdogReset diagnostics. If the task Cycle Time reaches the Sensitivity field value multiplied by the Time field, the diagnostics will also be indicated. Attention should be given to the fact that the watchdog of the CPU is not used to protect the user application from surge at cycle time, but of crashes.

  • Page 236: Pou - Task Connection

    5. Initial Programming POU – Task Connection As described previously, for a POU to be executed in the application, it must be connected to a task. In the project profiles (except Custom), the POUs are already associated to its respective tasks. In case new POUs are created, make sure they are connected to the tasks.
  • Page 237 5. Initial Programming HX3040 Task Type Custom Configuration Task Cyclic (WHSB) Cyclic Triggered by Event Triggered by External User Task Event Freewheelin Triggered by State NET (n) – Client or Cyclic Server Instances COM (n) – Master or Cyclic Slave Instances TOTAL Table 5-6.

  • Page 238: Cpu Configuration

    5. Initial Programming CPU Configuration The Hadron Xtorm is based on setting CPU parameters such as watchdog, hot swap, time synchronism, internal points, engineering conversion, alarms and events grouping. Double-click the Hadron Xtorm CPU in the device tree (Figure 5-17), and configure the required fields as described in the CPU chapter.

  • Page 239: Libraries

    5. Initial Programming In case the CPU with the configured IP is not found in the network, or the active CPU has a different IP, a message will appear on the screen during the Login. The message requests the user to change the previous IP for the configured one (Yes).

  • Page 240: Inserting A Protocol Instance

    5. Initial Programming Inserting a Protocol Instance The Hadron Xtorm, Series CPUs, as described in General Features, offers protocols as the MODBUS. The user must add and configure the desired protocol instance (see Protocols Configuration). Two cases of MODBUS protocol insertion are described below, one in the serial interface and the other in the Ethernet interface.
  • Page 241 5. Initial Programming After that, the available protocols for the user will appear on the screen. Select “MODBUS Slave”, expands the options tree, select the device and click “Add Device”, as depicted in Figure 5-22: Figure 5-22. Selecting the Protocol...

  • Page 242: Ethernet Modbus

    5. Initial Programming Ethernet MODBUS The first step to configure the MODBUS Ethernet in client mode is to include the instance in the desired NET (in this case, NET 1, as the CPU HX3040 presents six Ethernet interfaces). Click with the right button over NET and select “Add Device...”...
  • Page 243 5. Initial Programming After that, the available protocols for the user will appear on the screen. Select MODBUS > MODBUS Ethernet > MODBUS Client > MODBUS Symbol Client” and click “Add Device”, as depicted in Figure 5-24: Figure 5-24. Selecting the Protocol...

  • Page 244: Dnp3 Server

    5. Initial Programming DNP3 Server The first step to configure DNP3 in server mode is to include the instance in the desired NET (in this case, NET 1, as the CPU HX3040 presents six Ethernet interfaces). Click with the right button over NET and select “Add Device...”...
  • Page 245 5. Initial Programming After that, the available protocols for the user will appear on the screen. Select “DNP3 > DNP3Ethernet > DNP3 Server > DNP3 Server” and click “Add Device”, as depicted in Figure 5-26: Figure 5-26. Selecting the DNP3 Protocol...

  • Page 246: Servidor Iec 60870-5-104

    5. Initial Programming Servidor IEC 60870-5-104 The first step to configure IEC 60870-5-104 in server mode is to include the instance in the desired NET (in this case, NET 1, as the CPU HX3040 presents six Ethernet interfaces). Click with the right button over NET and select “Add Device...”...

  • Page 247: Finding The Network

    5. Initial Programming After that, the available protocols for the user will appear on the screen. Select “IEC 60870-5-104 > IEC 60870-5-104 Server > IEC 60870-5-104 Server” and click “Add Device”, as depicted in Figure 5-28: Figure 5-28. Selecting the IEC 60870-5-104 protocol Finding the Network As there is the possibility of more than one CPU to be connected to the network, the user must find all communication units and select the desired one.
  • Page 248 5. Initial Programming Figure 5-29. Finding the CPU Then, select the desired CPU. Click “Set active path” in order to activate the CPU and inform the configuration software to which CPU it should communicate with and send the project. Figure 5-30. Activating the CPU If necessary, change the device default name.

  • Page 249: Compiling A Project

    5. Initial Programming Compiling a Project In order to execute the verification of the created application, the user must compile the project. This is the most efficient way to find out receive error warnings regarding any mistake made during the product configuration and application edition.

  • Page 250: Login

    5. Initial Programming Figure 5-33. Including the Messages on the Screen Login After compiling the application and correcting the eventual errors, the project must be sent to the CPU. For that to be possible, you have to perform the Login operation in the MasterTool Xtorm software.
  • Page 251 5. Initial Programming After the command execution, some user interface messages may appear, due to differences between the old project and the new one that is being sent, or simply because there was a variation in some variable. Figure 5-35 shows the message that MasterTool Xtorm will present in case the new project is different from the project already existent inside the CPU.

  • Page 252: Run Mode

    5. Initial Programming Figure 5-37. First Application Sending Run Mode Right after the project has been sent to the CPU, the application will not be performed immediately (only if an online change has been made). For that to happen, select the “Start” command. This function allows the user to control the execution of the application sent to the CPU.

  • Page 253: Stop Mode

    5. Initial Programming Figure 5-39. Program in Execution In case the CPU is initialized with an application already internally stored, it automatically goes to Run Mode, without the need for a MasterTool Xtorm command. Stop Mode In order to discontinue the CPU execution, without losing the connection with the MasterTool Xtorm software, select “Stop”...

  • Page 254: Monitoring, Writing And Forcing Variables

    When a CPU presents forced variables and it is de-energized, the variables will lose the forcing in the next initialization. The limit of forcing for the Hadron Xtorm CPUs is 128 variables, regardless of the CPU model and its configuration.

  • Page 255: Variables Used In Several Sources

    5. Initial Programming Variables Used in Several Sources A source is a point of an I/O module or a communication driver that writes to a variable. When a project is compiled, MasterTool Xtorm checks all points, and informs whether the variable is being used in more than one source.

  • Page 256: Simulation Mode

    5. Initial Programming Simulation Mode MasterTool IEC XE has an important simulation feature, which allows the user to test its application without the equipment use, which provides a higher flexibility for the program development. However, some specific resources cannot be simulated, depending on the CPUs hardware. The following resources are unavailable in the simulation mode: ...

  • Page 257: Project Upload

    In this case, the same written data, for example in QD0%, will be written differently on Simulation mode and in Hadron Xtorm Series CPUs. If the written data is 16 # 1234ABDC, the data distribution in the CPU memory will be as follows: ...
  • Page 258 5. Initial Programming Figure 5-43. Project Upload Then, select the desired CPU and click OK, as shown in Figure 5-44. Figure 5-44. CPU Selection ATTENTION: The memory size area to store a project in Hadron Xtorm CPUs is defined in Specific Features.

  • Page 259: Cpu Operating States

    5. Initial Programming ATTENTION: The upload retrieves the last stored project in the controller as described in the former paragraphs. In case the download refers to the execution of only a specific application, it will not be possible to retrieve it through this procedure (Upload). CPU Operating States The Run mode indicates that all CPU’s application tasks are running.

  • Page 260: Reset Process Command (Iec 60870-5-104)

    5. Initial Programming Notes: Reset: This command disables the breakpoints that were defined in the application. Command: In order to execute a Warm, Cold or Reset Origin, it is necessary to be with MasterTool in online mode (logged in to the CPU). Reset Process Command (IEC 60870-5-104) This reset process command can be requested by the IEC 60870-5-104 clients.

  • Page 261: Hx3040 Redundancy

    If the networks are duplicated the availability is even higher. The Hadron Xtorm Series CPUs hot-standby redundancy is not applied to I/O modules. In case the user whishes the I/O module redundancy, one can handle it in the application level. As an example, the user can duplicate or even triplicate an analog input module and create a vote scheme to define which input will be regarded at a given point in the application.

  • Page 262: Configurations Of A Redundant Cpu

    6. HX3040 Redundancy Figure 6-1. Example of Redundant Architecture with HX3040 Configurations of a Redundant CPU To configure the CPU to the redundant mode, perform the following steps:  Create a project by selecting the option for redundant CPUs.  Configure the Ethernet interfaces.

  • Page 263: General Features

    6. HX3040 Redundancy General Features Redundant CPU General Features Allowed CPUs HX3040 Redundancy types Hot-standby The CPU supports, at least, simple failures in doubled equipment in the racks. In Failure tolerances specific cases, it can support multiple failures. - Not-configured: initial state, also considered when the CPU is off or is not executing the MainTask.
  • Page 264 6. HX3040 Redundancy Redundant CPU General Features At each MainTask cycle, CPUA and CPUB exchange diagnostics and commands. The user has 128 redundant data bytes available within the redundant CPU Redundant data synchronization diagnostics. The synchronism occurs through the channels between the CPUs. This way, a CPU knows the diagnostics and commands of the other.

  • Page 265: Operation Principles

    6. HX3040 Redundancy Operation Principles This section describes the redundant CPU functions, along with its behavior and states. In addition to that, it presents the concepts as well as programming and configuration constraints. Single Redundant Project Due to the identification register previously described, there is a single project for the redundant CPU, identical for both CPUA and CPUB.
  • Page 266 6. HX3040 Redundancy Oppositely to the MainPrg, which cannot and must not be modified, the user may modify other programs. When the redundant project is created from the Redundancy Template, the programs are “empty”, although it is possible to the user insert them a code. StartPrg Program This POU runs only once, at the first cycle of each one of the CPUs.
  • Page 267 6. HX3040 Redundancy Therefore, NonSkippedPrg will always run in both CPUs (CPUA and CPUB), regardless of its redundancy state. As for the UserProtPrg program, it will run only in the active CPU. This POU presents a higher priority than UserPrg. Oppositely to the ProtPrg, which cannot and must not be modified, the user may modify other programs.

  • Page 268: Multiple Mapping

    6. HX3040 Redundancy Redundant and Non-Redundant Symbolic Variables Besides the direct representation variables (%I, %Q) which are automatically allocated, the user can explicitly declare symbolic variables, inside of POUs or GVLs. The maximum size allowed for redundant symbolic variables allocation is 512kbytes. ATTENTION: Symbolic variables must not be mistaken with symbolic variables addressed through the AT directive.

  • Page 269: Diagnostics, Commands And User Data Structure

    6. HX3040 Redundancy END_IF Above there is an example of logic in ST language, where the redundancy switchover commands can be executed through two variables from different communication ports. Where: var_StandBy_command_Ethernet_relation: Bool type variable assigned to an Ethernet communication Coil that will execute the command to put the local CPU in Stand-By. var_StandBy_command_Serial_relation: Bool type variable assigned to a Serial communication Coil that will execute the command to put the local CPU in Stand-By.

  • Page 270: Sporadic Synchronization Services Through Redundancy Synchronism Channels

    6. HX3040 Redundancy  Copying RedDgnLoc from CPUA to RedDgnRem da CPUB  Copying RedCmdLoc from CPUA to RedCmdRem da CPUB  Copying RedUsrLoc from CPUA to RedUsrRem da CPUB  Copying RedDgnLoc from CPUA to RedDgnRem da CPUA  Copying RedCmdLoc from CPUB to RedCmdRem da CPUA ...

  • Page 271: Redundant Ethernet Networks With Nic Teaming

    6. HX3040 Redundancy  Trace The synchronization service will start within thirty seconds after one of the CPUs goes into Active state, and after its beginning, the project CRC will be checked at every five seconds. When a synchronization is started (if the CPU is in RUN mode), the Non-Active CPU goes into Stop mode, at the Not-Configured state.

  • Page 272: Ip Change Methods

    Ports Configuration . IP Change Methods Projects carried out with a Hadron Xtorm Series redundant CPU provide a method for IP change of the Ethernet ports NET1 to NET6. This method, named Active IP, defines the ports’ behavior, regarding its IP, according to the current CPU redundancy state (Active or Non-Active) and its identification (CPUA or CPUB).

  • Page 273: Nic Teaming And Active Ip Combined Use

    Active IP Address: IP address of the ports NET 1 + NET 2 of that CPU which is in Active state. Thus, the Hadron Xtorm Series combines the excellent availability of NIC Teaming strategy with the practicality of Active IP strategy, releasing scripts in SCADA systems or other clients connected to servers in the Active CPU.
  • Page 274 6. HX3040 Redundancy In other situations, the user must request this configuration manually, e.g. pressing a button over the CPU’s display menu. Manual configuration requests usually are not necessary in maintenance situations (before leaving the Non-Configured state). E.g. if the CPU has not reached the Non- Configured state due to some failure.

  • Page 275: Commands Of The Redundancy Menu Of The Cpu's Display

    6. HX3040 Redundancy The bus control remains in the passive state. The passive mode is used to test the transmission and reception circuits and the physical layer to avoid hidden flaws. Total failure may cause a switch to the Inactive state. Inactive State The CPU reaches this state after some failures, or due to a manual request before a programmed maintenance.
  • Page 276 6. HX3040 Redundancy Non- Configured Starting Inactive Standby Active Figure 6-4. Redundancy Machine State The following sections describe all these transitions as well as the causes that can trigger them. To correctly interpret the operation of this state machine, notice the following rules and sequences: ...
  • Page 277 6. HX3040 Redundancy Transition 3 – Starting to Non-Configured  The current CPU is turned off or rebooted (Reset Warm, Reset Cold or Reset Origin).  The current CPU is inserted in an incorrect position.  There are configuration logic errors in the project received from MasterTool Xtorm. ...

  • Page 278: First Instants In Active State

    6. HX3040 Redundancy  The current CPU cannot control the bus and it is aware that the other CPU is in Stand-by. This condition is not evaluated for the first 2 seconds of the Active state. Transition 10 - Active to Stand-by ...

  • Page 279: Common Failures Which Cause Automatic Switchovers Between Cpus

    6. HX3040 Redundancy Common Failures which Cause Automatic Switchovers between CPUs This section lists the most common faults, which automatically cause a switchover between CPUs (Active to Non-active / Stand-by to Active). These failures trigger a subset of those transitions examined on the previous section (Transition between Redundancy States).

  • Page 280: Failure Tolerance

    6. HX3040 Redundancy DG_HX3040_01.RedCmdLoc.bStandbyLocal := TRUE; END_IF END_IF ------------------------------------------------------------------ IF ((DG_HX3040.tDetailed.Serial.COM[1].byProtocol <> 0) OR (DG_HX3040.tDetailed.Serial.COM[2].byProtocol <> 0))THEN //If a communication error occurs, the CPU performs a switchover. IF MODBUS_Device_REQDG_0001.byStatus.bCommError THEN //Local CPU in StandBy. DG_HX3040_01.RedCmdLoc.bStandbyLocal := TRUE; END_IF END_IF Notes: When two interfaces form a NIC Teaming pair, the inactive interface will always have the IP address 0.0.0.0.

  • Page 281: Redundancy Overhead

    6. HX3040 Redundancy happen a second failure in the redundant component during the repair of the first failure, which would undermine the system. Therefore, the longer the time of repair, the lower system availability. 8. Schedule periodic offline tests in the components, so as to detect non-diagnosable faults. The goal is to detect hidden faults, particularly in redundant components (or even in simple ones, as long they, which are not usually requested, as a safety relay, for example.
  • Page 282 6. HX3040 Redundancy transfer time of 15ms (7ms + 6,4ms / Kbyte * 117 Kbytes = 15ms). MasterTool indicates this period by as the “maximum redundancy overhead”. ATTENTION: MasterTool calculates the overhead considering a forcing list of empty of redundant variables. The MainTask cycle time should be set taking into account the “maximum redundancy overhead”...

  • Page 283: Redundant Cpu Programming

    6. HX3040 Redundancy Redundant CPU Programming Wizard for a New Redundant Project Creation To create a new redundant project, click File / New Project, and then select MasterTool Standard Project. Initially, enter the project name and the directory where you want to store it, as shown in Figure 6-5: Figure 6-5.
  • Page 284 6. HX3040 Redundancy The first point is the hardware initial configuration of the RTU.  Select the CPU model: As the redundancy is implemented only in HX3040, it shall be selected by the user.  Select the rack model: There are two options of racks available; the choice depends on the number of used modules.
  • Page 285 6. HX3040 Redundancy Then, define the amount and types of the application I/Os:  Select the quantity of digital input points  Select the quantity of digital output points  Select the quantity of V/I analog input points  Select the quantity of RTD analog input points Figure 6-7.
  • Page 286 6. HX3040 Redundancy Next, select the project profile and the standard language for the program creation:  Select the project profile: RTU Profile only.  Select the default language for all programs: The chosen language applies to all programs, but it is possible to use any other language for a specific POU.
  • Page 287 6. HX3040 Redundancy To conclude, select the language for common programs and for the ones associated with redundancy:  Programs associated with MainTask (MainPrg)  Programs associated with cyclic tasks: ST only. MasterTool disables the other options.  Programs associated with redundancy main tasks Figure 6-9.

  • Page 288: Project Configuration With Cpu Redundancy

    6. HX3040 Redundancy  Power supply (positions 0 and 1)  HX3040 CPU (positions 2 and 3)  I/O Modules (remaining positions in the rack) Project Configuration with CPU Redundancy The Wizard is always used to generate the first version of a redundant project. This ensures that the initial version of the project will be generated quickly and correctly.

  • Page 289: I/O Drivers Configuration

    6. HX3040 Redundancy ATTENTION: The odd NETs (1, 3 and 5) have the Advanced button, while the even ones (2, 4 and 6) do not. Through this button, you can set the NETs redundancy (NIC Teaming) and select the Switch mode as well.
  • Page 290 6. HX3040 Redundancy StartPrg Program In this POU, the user can create logics and loops, and start variables as well. Such variables will run only once at the first cycle of each RTU, and thus will not be called again during the project execution.
  • Page 291 6. HX3040 Redundancy Where: Device name: Name displayed in the TreeView for the MODBUS device. Request number: Request number declared in the MODBUS device table, ordered from top to bottom, starting in 0001. Example: Disables VAR_GLOBAL MODBUS_Device_DISABLE_0001 : BOOL; MODBUS_Device_DISABLE_0002 : BOOL;...
  • Page 292 6. HX3040 Redundancy GVL Module_Diagnostics The "Module_Diagnostics" GVL declares the diagnostic variables of the modules used in the project, except for the CPU and communication drivers. This GVL is not editable, so the variables are automatically declared with the type specified by the module to which it belongs, when it is added to the project.
  • Page 293 6. HX3040 Redundancy Variable declaration of mapping quality: [Device name]_QUALITY_[Mapping number]: LibDataTypes.QUALITY; Where: Device name: Name displayed in the TreeView for the device. Mapping number: Mapping number declared in the mapping device table, ordered from top to bottom, starting in 0001. Example: Qualities VAR_GLOBAL...
  • Page 294 6. HX3040 Redundancy Figure 6-13. GVL Qualities in Online Mode ReqDiagnostics GVL The "ReqDiagnostics" GVL declares the diagnostic variables of the MODBUS Master/Client and DNP3 Client requests. It is not mandatory, but it is recommended to use the automatic generation of these variables, which is done by clicking on the button "Generate Diagnostic Variables"...
  • Page 295 6. HX3040 Redundancy Example: ReqDiagnostics VAR_GLOBAL MODBUS_Device_REQDG_0001 : T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_REQDG_0002 : T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_REQDG_0003 : T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_1_REQDG_0001 : T_DIAG_MODBUS_ETH_MAPPING_1; MODBUS_Device_1_REQDG_0002 : T_DIAG_MODBUS_ETH_MAPPING_1; Outstation_REQDG_0001 : T_DIAG_DNP_CLIENT_REQUEST_1; END_VAR The "ReqDiagnostics" GVL is editable, so the diagnostic variables of the requests can be created manually and do not need to follow the model created by the automatic declaration.

  • Page 296: Prottask Configurations

    6. HX3040 Redundancy Example: System_Diagnostics VAR_GLOBAL DG_HX3040 : T_DIAG_HX3040_1; DG_DNP3_Client : T_DIAG_DNP_CLIENT_1; DG_DNP3_Server : T_DIAG_DNP_SERVER_1; DG_MODBUS_Symbol_Client : T_DIAG_MODBUS_ETH_CLIENT_1; DG_MODBUS_Symbol_RTU_Master : T_DIAG_MODBUS_RTU_MASTER_1; END_VAR By sending an application to the HX3040 CPU and putting it in "Execution", through GVL "System_Diagnostics" you can monitor the diagnostics variable values of the CPU and MODBUS communication devices, IEC 6185 Server and DNP3 Client as well (Figure 6-15).

  • Page 297: Gvls With Redundant Symbolic Variables

    6. HX3040 Redundancy NonSkippedProtPrg Program This POU is similar to "NonSkippedPrg", except that it features a higher priority. The "NonSkippedProtPrg" is created only in projects with CPU redundancy. GVLs with Redundant Symbolic Variables You can create GVLs other than those mentioned above, so as to declare redundant symbolic variables.

  • Page 298: Getting The Redundancy State Of A Cpu

    6. HX3040 Redundancy  Do not use program POUs written in SFC (Sequential Function Chart), as they use the IEC timer for transitions timing.  Do not mix declaration of symbolic variables with ATs in GVLs. Create separate GVLs declaring AT variables in the first one and the symbolic variables in the second one. Getting the Redundancy State of a CPU You can check the redundancy status of a CPU from the Redundancy Diagnostics Structure: eRedStateLocal : REDUNDANCY_STATE;...
  • Page 299 6. HX3040 Redundancy Step 1 – Find out the IP Address for MasterTool Connection The first step is to find out the IP address of this CPU NET 1 channel, for connect it to MasterTool. This should be done through the display and CPU HX3040 button, as described in Informative Menu and of CPU’s Configuration.

  • Page 300: Mastertool Connection With A Hx3040 Cpu From A Redundant Cpu

    6. HX3040 Redundancy After sending the project to one of the CPUs, the other one will download the project automatically by means of internal sync channel. ATTENTION: Within the project developed with the MasterTool and loaded on the CPU in this step, it was defined new IP addresses for the interface NET 1 of CPUA and CPUB, as well as an IP address for the interface NET of CPU 1 active (Active IP address) –...

  • Page 301: Load Of Changes In Offline And Online Mode

    6. HX3040 Redundancy The changes should always be loaded into Active CPU, which will transfer them automatically to the non-active CPU, through the channels of synchronism. Therefore, the MasterTool typically must use the unique IP address of CPU that is in the active state (IP address of the CPUx), to connect to port NET 1 of the HX3040 Active CPU.

  • Page 302: Load Of Changes In Online Mode

    6. HX3040 Redundancy For more information, the MasterTool IEC XE User Manual TM8500 (MU299048) should be consulted. Load of Changes in Online Mode In the section Load of Changes in Offline and Online Mode, were described modifications that require offline load and those that allow online load. A charge must be made online by connecting the MasterTool to Active CPU NET 1 channel, using your unique IP address (CPUA or CPUB IP).

  • Page 303: Interaction With The Redundancy Through The Hx3040 Cpu Graphics Display

    6. HX3040 Redundancy These commands will only be triggered if the Active CPU is operating with redundancy disarmed, i.e. another CPU must be in the Inactive State (or out of the bus). Otherwise, a blocking message appears: "The Login cannot be performed, because the current project is different from the project in use on the CPU.
  • Page 304 FALSE - The configuration process, run on non-configured state, still not ended or was not run. TRUE - The configuration process, run on non-configured, finished with errors. This is a system error, not usually expected. Contact Altus support for reporting it. Notify also the bConfigError BOOL diagnostic value of ConfigErrorCode to Altus support.
  • Page 305 6. HX3040 Redundancy .RedundancyDiagnostics.* Type Description FALSE – The size of the data structure is within the expected. TRUE – The application is not compatible between the two PLCs. Was performed a new application download to one of the CPU with one of the following changes: Modification of redundant data area;...
  • Page 306 6. HX3040 Redundancy .RedundancyDiagnostics.* Type Description IEC synchronization Timer is required for bump-less operation of some function blocks as TON and TOF. Through this diagnosis Active CPU IEC Timer is received and updated in dwIECTimer dwIECTimer non-active CPU, since the Diagnostics and Commands Exchange service have been successfully executed.
  • Page 307 6. HX3040 Redundancy The Table 6-6 shows all messages to be presented to the states and changes of redundancy, accessible to the user by means of diagnosis "DG_HX3040_01. RedDgnLoc. RedundancyDiagnostics. eStateChangeReason.". Messages presented in the description are identical to the messages that will be displayed in the Log.
  • Page 308 6. HX3040 Redundancy State String do Estado Log Message Description Value The Project Archive between the Standby to Non-Configured, the Project Archive in SBY_ARCHIVE_DIFF CPUs is different the CPUs is different. SBY_ONLINE_CHANGE_AP There is an online change in the Standby to Non-Configured, an online application Application of the Active CPU load was performed on the Active CPU.
  • Page 309 6. HX3040 Redundancy State String do Estado Log Message Description Value NON_ACT_OTHER_CPU_A Application of the other CPU was Application of the other CPU was reset. PP_RESET_BY_USER reset NON_ACT_OTHER_CPU_A Application of the other CPU is Application of other CPU is at breakpoint. PP_BRKP_BY_USER stopped by breakpoint Table 6-6.

  • Page 310: Redundancy Event Logs

    RedUsrLoc, which will be received in another CPU in RedUsrRem. Redundancy Event Logs The MasterTool allows observing various logs to a Hadron Xtorm CPU, among which is the redundancy event logs. These messages, specific to the redundancy, log in System Log.
  • Page 311 6. HX3040 Redundancy  wCycleCounter  dwIECTimer  SyncLinkStatistics Each line shown in the log has the following columns:  Time Stamp: date and time of the event, with a resolution of milliseconds  Severity: information, warning, error or exception ...

  • Page 312: Maintenance

     Diagnostics via Function Blocks The first one is an innovating feature of Hadron Xtorm Series, which allows a quick access to the abnormal conditions of the application. The second is purely visual, generated through one bicolor LED (DL) (red / blue) placed on the frontal part of the module. The next feature is the graphic visualization in a WEB page of the rack and the respective configured modules.
  • Page 313 7. Maintenance Figure 7-1 shows the CPU switch on the CPU screen: Figure 7-1. Diagnostics Switch When the CPU is in active mode, through a short touch, it starts showing the bus diagnostics (in a different state it shows the message “NO DIAG”). Initially, the Tag is visualized (configured in the module proprieties of the MasterTool Xtorm software, according to IEC 61131-3 standard), in other words, the name which was attributed to the CPU.
  • Page 314 (∞) Table 7-1. Tempo de One Touch The diagnostics messages presented on Hadron Xtorm CPU graphic display are described in the chapter Diagnostics via Variables, Table 7-3 and Table 7-4. If any situation of stuck button occurs in one of the I/O modules, the diagnostic button of this module...

  • Page 315: Diagnostics Via Led

    ATTENTION: One Touch Diag (OTD): This option is available only in the operation mode. Diagnostics via LED Hadron Xtorm Series CPUs contain a LED for diagnostics indication (LED DL). Table 7-2 illustrates the meaning of each LED state. DL (Color)
  • Page 316 7. Maintenance Figure 7-3. Initial Screen The CPU also provides a “System Overview”, tab, which can be visualized through the Rack or via the module list (right side of the screen). While there is no application on the CPU, this page displays a configuration with the largest available rack plus a standard power supply, along with the connected CPU.
  • Page 317 7. Maintenance Figure 7-4. System Information By clicking in one of the modules, the CPU displays the amount of diagnostics and the amount of diagnostics for each module channel (Figure 7-5): ATTENTION: When a CPU is restarted and the application goes into exception during startup, the diagnostics will no longer be valid.
  • Page 318 7. Maintenance Figure 7-5. Diagnostics amount per module and per channel By clicking on one of the lines of Figure 7-5 table, a screen that shows the description of each diagnosis appears, as illustrated in Figure 7-6: Figure 7-6. Module/Channel Diagnostics List...
  • Page 319 Besides, the user can choose one out of three languages: Portuguese, English and Spanish. Select the desired option in upper right corner. The correspondent Firmware Updating tab is restricted to the user, that is, for Altus internal use only. In cases of remote updating (radio or satellite connection, for instance) the minimum speed of the link must be 128Kbps).

  • Page 320: Diagnostics Via Variables

    7. Maintenance Diagnostics via Variables Hadron Xtorm Series CPUs offer a set of global symbolic variables, which supplies several diagnostics information related to the hardware and software. These data structures showing the diagnostics of all modules declared on the bus are mapped within variables of direct representation %Q.
  • Page 321 Modules with Fatal Error: In case the modules with fatal error diagnostic is true, it must be verified which is the problematic module in the bus and send it to Altus Technical Assistance, as it has hardware failure. Module with Parameterization Error: In case the parameterization error diagnostic is true, the user must check if the bus modules are correctly configured and if the firmware /MasterTool Xtorm version are correct.
  • Page 322 Duplicated Slot: If there is any duplicated address position then the diagnosis of Duplicated Slot will be true. Hardware Failure: In case the Hardware Failure diagnostic is true, the CPU must be sent to Altus Technical Assistance, as it has problems in the RTC, auxiliary processor, or other hardware resources.
  • Page 323 7. Maintenance DG_HX3040.tDetailed.* Variable Type Description Counter of reset performed by the RTS - Runtime System wRTSResetCounter WORD (0 to 65535). The CPU was restarted due a failure in the power supply in bBrownOutReset BOOL the last startup. Reset.* The CPU was restarted due the active watchdog in the last bWatchdogReset BOOL startup.
  • Page 324 7. Maintenance DG_HX3040.tDetailed.* Variable Type Description abyMAC BYTE ARRAY(6) Port MAC Address bStandbyState BOOL Interface in stand-by state bActiveState BOOL Interface in active state bControllerFailure BOOL NIC Teaming failure NICTeami bLinkDown BOOL Interface without link ng.* bInterMsgTimeout BOOL Time-out waiting for NIC Teaming pair. bGeneralRxMsgTi BOOL Time-out waiting for network packages.
  • Page 325 7. Maintenance DG_HX3040.tDetailed.* Variable Type Description Informs the abnormal situation in the bus, which caused the application stop for each mode of hot swapping: INITIALIZING (0): This state is presented while the other states are not ready. RESET_WATCHDOG (1): Application in Stop Mode due the reset by hardware watchdog or by a Runtime restart, when the configuration “Start User Application after Reset by Watchdog”...
  • Page 326 7. Maintenance DG_HX3040.tDetailed.* Variable Type Description Identification of I/O modules errors, individually: Array [0..31] represents 32 backplane racks, being each position made up by 32 bits. Each bit of these DWORDs represents the bus position, being the Bit-0 equivalent to position 0.
  • Page 327 7. Maintenance DG_HX3040.tDetailed.* Variable Type Description EXTENDED_DATE_AND _TIME sLastUpdateTime sLastUpdateTime.byDayOfMonth BYTE sLastUpdateTime.byMonth BYTE Date and time of the last sync time via SNTP. sLastUpdateTime.wYear WORD sLastUpdateTime.byHours BYTE sLastUpdateTime.byMinutes BYTE sLastUpdateTime.bySeconds BYTE sLastUpdateTime.byMilliseconds WORD bServiceEnabled BOOL IRIGB service enabled. Counter of times the time was updated by IRIGB service (0 dwTimeUpdatedCount DWORD to 4294967295).

  • Page 328: Diagnostics Via Function Blocks

    7. Maintenance Code Description Code Description 0x0014 Fieldbus error. 0x0056 Invalid maneuver. 0x0015 I/O updating error. 0x0057 Protected page. 0x0016 Cycle time (execution) exceeded. 0x0058 Double failure. 0x0017 Program online updating too long 0x0059 Invalid OpCode. 0x0018 Unsolved external references. 0x0100 Data type misalignment.

  • Page 329: Graphic Display

    //Variable ‘Info’ gets possible function errors. Graphic Display The graphic display available in the Hadron Xtorm Series CPUs is an important tool for process control, as through it is possible to recognize eventual error conditions, active components or diagnostics presence. Furthermore, all diagnostics including the I/O modules are presented to the user...
  • Page 330 Further information regarding the diagnostic key and its visualization see One Touch Diag. Figure 7-9 shows the available characters in the Hadron Xtorm CPU graphic display and their respective meanings. Figure 7-9. CPU HX3040 Status Screen Legend: 1.
  • Page 331 11. Indication of network link failure (x) on the Ethernet port (N) (NET 1 to NET 6). For more information about Ethernet interfaces, see chapter Ethernet Interfaces Configuration Besides the characters described above, Hadron Xtorm CPUs can present some messages on the graphic display, correspondent to a process, which is being executed at the moment.

  • Page 332: System Log

    Note: CPU System Log: Hadron Xtorm CPUs system logs are not reloaded in case of a CPU reboot or Runtime restart, that is, it will not be possible to view the oldest logs when one of these conditions occur.
  • Page 333 7. Maintenance Figure 7-10. Visualization of the CPU diagnostics As illustrated in Figure 7-10, both the tag and the list of all active diagnostic related to the module will be shown twice on the CPU display. After that the respective module will exit the diagnostic mode and the CPU display will indicate information regarding the CPU.
  • Page 334 7. Maintenance Identifying points of I / O with individual diagnostic After entering the diagnostic mode, the I/O modules indicate which points have individual diagnoses, flashing the respective I/O segment. For example, if the segment shown in Figure 7-12 is flashing, it indicates that the second I/O point of the module has an active individual diagnosis.

  • Page 335: Not Loading The Application At Startup

    Stop Mode. In case of a login, MasterTool Xtorm software indicates that there is no application on the CPU. For reloading the application, reboot the CPU or download a new application. Power Supply Failure Hadron Xtorm Series Power Supply presents a failure detection system according to the levels defined in its technical features (see Main Features).

  • Page 336: Common Problems

    Xtorm CPU and to the network device?  Is the Hadron Xtorm Series CPU on, in execution mode (Run) and with no diagnostics related to hardware? If the Hadron Xtorm CPU indicates execution mode (Run) but it does not respond to the requested communications, whether through MasterTool Xtorm or protocols, check the following items: ...

  • Page 337: Troubleshooting

    Check if the supply voltage gets to the Hadron Xtorm power supply contacts and if is correctly polarized. Check all the connections of the communication cables. Does not...

  • Page 338: Electric Panel Design

    Depth of Rack-mounted Module The depth of Hadron Xtorm Series module and rack set can be obtained by adding 28 mm to the depth of the module. In the example of Figure 8-1, a standard module with 184.2 mm depth was used.

  • Page 339: Spacing Between Modules And Other Equipment In The Panel

    Wiring area = (3.14 * radius ^ 2) It is considered as “wiring area” the total area, including the insulation. Horizontal/Vertical Mounting Hadron Xtorm Series allows the use of RTU in horizontal orientation. Vertical mounting is not allowed in the rack.

  • Page 340: Thermal Design

    8. Electric Panel Design Thermal Design Altus equipment is designed to work at an ambient temperature of up to 60 °C (except where specified). Therefore, this should be the maximum internal temperature of the cabinet. The following precautions should be observed in panel design:...
  • Page 341 8. Electric Panel Design The power dissipated by a panel can then be calculated through equation Qs = k * A * (internal temperature – external temperature), or obtained from Figure 8-3. Figure 8-3. Dissipated Power x Surface x Temperature Diff. This value can, however, be tripled in case of air circulation outside of the panel.
  • Page 342 8. Electric Panel Design In this case, the temperature has exceeded the limit of the equipment operation (60 °C), and must be provided another way to remove excess heat. The limit of installed power for the internal temperature of 60 degrees is: Qs = k * A * (Ti –...

  • Page 343: Electrical Design

    The electrical design of the Altus RTUs must comply with the IEEE 518/1977, "Guide for Installation of Electrical Equipment to Minimize Electrical Noise Inputs to Controllers External Sources".

  • Page 344: Cabinet Lighting

    8. Electric Panel Design For the best performance of your equipment, it is necessary to separate the circuits as to its type, in order to reduce electromagnetic interference, as follows: 1. AC power circuits and AC and DC loads drives 2.
  • Page 345 8. Electric Panel Design RC Circuit The RC protection circuit (Resistor in series with a Capacitor) can be mounted in parallel with the contact or in parallel with the load. The assembly in parallel with contacts is recommended for loads supplied into DC voltage.
  • Page 346 8. Electric Panel Design Circuit with Diode and Zener The circuit with diode and zener is suitable when the time to disconnect the circuit with diode is excessive. As well as the protection circuit with diode, it should only be used in DC voltages. The zener voltage should be slightly higher than the peak voltage of load Figure 8-9.

  • Page 347: Distribution Of Power Supply Out Of The Cabinet

    8. Electric Panel Design Figure 8-11. CKT with capacitor in parallel with contacts Figure 8-12. CKT with capacitor in parallel with the load Distribution of power supply out of the cabinet In applications where the Cabinet is distant from the machine or the system to be controlled, although it is in the same building, the following procedures are recommended: 1.
  • Page 348 The Figure 8-13 shows the correct way of installing lightning protection to a generic system. Each system has its own details of installation, so it is recommended to consider each case individually to define the best protection way. In cases regarded as critical, consult the Altus support service.

  • Page 349: Glossary

    Is the smallest part of a function that change data and represents a function in a physical device. MasterTool Xtorm Identifies the Altus software for PC, executable only in Windows®, which allows the development of the Hadron Xtorm Series RTU´s. Throughout this manual, this software is referenced by its acronym or as MasterTool Xtorm.
  • Page 350 9. Glossary Mapping Variable addressing to an action, protocol, etc. Menu Set of options available and displayed by a program on video and that can be selected by the user to activate or perform a certain task. Master Equipment connected to a communication network where the commands requests to the other network devices originate.
  • Page 351 9. Glossary RS-232C It is a standard for data serial exchange between two points (peer to peer) RS-422 It is a standard for data serial exchange between two or more points (full duplex peer to peer) RS-485 It is a standard for data serial exchange between two or more points (half duplex peer to peer). 10Base-T Physical layer type for Ethernet defined in the IEEE 1990 standard 802.3i.

Table of Contents