1. Manuals
  2. Brands
  3. ALTUS Manuals
  4. Processor
  5. Nexto NX3004
  6. User manual

ALTUS Nexto NX3004 User Manual

Nexto series
Hide thumbs Also See for Nexto NX3004:
Table of Contents

Advertisement

Quick Links

User Manual
Nexto Series CPUs
NX3004, NX3005, NX3010,
NX3020, NX3030
Rev. K 11/2017
Doc. Code.: MU214605

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Nexto NX3004 and is the answer not in the manual?

Questions and answers

Related Manuals for ALTUS Nexto NX3004

Summary of Contents for ALTUS Nexto NX3004

  • Page 1 User Manual Nexto Series CPUs NX3004, NX3005, NX3010, NX3020, NX3030 Rev. K 11/2017 Doc. Code.: MU214605...
  • Page 3 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 4: Table Of Contents

    Summary Table of Contents 1. INTRODUCTION ............................1 Nexto Series ..............................2 Innovative Features ..........................3 Documents Related to this Manual ......................4 Visual Inspection............................5 Technical Support ............................5 Warning Messages Used in this Manual .....................5 2. TECHNICAL DESCRIPTION ........................6 Panels and Connections ..........................6 General Features............................8 Common General Features ........................8 Specific Features............................9 Serial Interfaces ...........................
  • Page 5 Summary RS-422 Communication with Internal Termination ................30 RS-422 Communication with External Termination ................31 RS-422 Network Example ........................31 Memory Card Installation ......................... 32 Architecture Installation ........................... 33 Module Installation on the Main Backplane Rack ................. 33 Programmer Installation ........................... 33 4.
  • Page 6 Summary User Log ............................218 ClearRtuDiagnostic ..........................221 ClearEventQueue ..........................221 SNMP ............................... 222 Introduction ............................222 SNMP in Nexto CPUs ........................222 Private MIB ............................223 Configuration............................. 226 User and SNMP Communities ......................227 User Management and Access Rights ..................... 228 5.
  • Page 7 Summary 6. REDUNDANCY WITH NX3030 CPU ....................263 Introduction ............................. 263 Technical Description and Configuration ....................265 Minimum Configuration of a Redundant CPU (Not Using PX2612 Panel) ......... 265 Typical Configurations of a Redundant CPU ..................265 NX4010 Module ..........................266 Redundancy Control Panel PX2612 ....................
  • Page 8 Summary Off-Line and On-Line Modifications Download ................. 319 On-Line Download of Modifications ....................320 Off-Line Download of Modifications with Process Control Interruption ..........321 Previous Planning for Off-Line Modifications without Process Control Interruption ......322 Exploring the Redundancy for Off-Line downloading of Modifications without Interruption of the Process control...........................

  • Page 9: Introduction

    1. Introduction 1. Introduction Nexto Series CPUs were designed to fulfill several customers’ demands in a variety of applications present on industrial automation and process control. Due to its compact and rugged body, excellent performance and fast I/Os update time provided by a unique high-speed communication bus, Nexto Series CPUs are the best choice for the most demanding control applications.

  • Page 10: Nexto Series

    1. Introduction Nexto Series Nexto Series is a powerful and complete series of Programmable Controllers (PLC) with exclusive and innovative characteristics. Due to its flexibility, functional design, advanced diagnostic resources and modular architecture, the Nexto PLC can be used to control systems in small, medium and large scale applications.

  • Page 11: Innovative Features

    1. Introduction Innovative Features Nexto Series brings to the user several innovations in utilization, supervision and system maintenance. These features were developed focusing a new experience in industrial automation. The list below shows some new features that users will find in the Nexto Series. Battery Free Operation: Nexto Series does not require any kind of battery for memory maintenance and real time clock operation.

  • Page 12: Documents Related To This Manual

    In order to obtain additional information regarding the Nexto Series, other documents (manuals and technical features) besides this one, may be accessed. These documents are available in its last version on the site http://www.altus.com.br/site_en/. Each product has a document designed by Technical Features (CE), where the product features are described.

  • Page 13: Visual Inspection

    It’s important to register each received equipment serial number, as well as software revisions, in case they exist. This information is necessary, in case the Altus Technical Support is contacted. Technical Support For Altus Technical Support contact in São Leopoldo, RS, call +55 51 3589-9500. For further information regarding the Altus Technical Support existent on other places, see http://www.altus.com.br/site_en/...

  • Page 14: Technical Description

    2. Technical Description 2. Technical Description This chapter presents all technical features from Nexto Series CPUs NX3004, NX3005, NX3010, NX3020 and NX3030. Panels and Connections The following figure shows the CPU NX3030 front panel. Figure 2-1. CPU NX3030 As it can be seen on the figure, on the front panel upper part is placed the graphic display used to show the whole system status and diagnostics, including the specific diagnostics of each module.
  • Page 15 2. Technical Description CPU’s Informative and Configuration Menu. For further information regarding the MS switch, see Configuration - Memory Card. Keys Description Switch placed on the module upper part. Used for diagnostics visualization on Diagnostics the graphic display or for navigation through the informative menu and CPU Switch configuration.

  • Page 16: General Features

    2. Technical Description General Features Common General Features NX3004, NX3005, NX3010, NX3020, NX3030 Backplane rack occupation 2 sequential slots Instruction List (IL) Structured Text (ST) Ladder Diagram (LD) Programming languages Sequential Function Chart (SFC) Function Block Diagram (FBD) Continuous Function Chart (CFC) Cyclic (periodic) Event (software event) Tasks...

  • Page 17: Specific Features

    2. Technical Description Conformal coating IP Level IP 20 IEC 61131-2 IEC 61131-3 CE, Electromagnetic Compatibility (EMC) and Low-Voltage Directive (LVD). Standards Module dimensions (W x H x D) 36.00 x 114.63 x 115.30 mm Package dimensions (W x H x D) 44.00 x 122.00 x 147.00 mm Weight 350 g...
  • Page 18 2. Technical Description Maximum number of PROFIBUS-DP network (using master modules PROFIBUS-DP) PROFIBUS-DP network redundancy support Redundancy support (half-clusters) Event oriented data reporting (SOE) Protocol DNP3 DNP3 Maximum event queue size 1000 1000 Clock synchronization (SNTP) Web pages development (available trough the HTTP protocol) Integrated power supply Current consumption from backplane rack power...
  • Page 19 2. Technical Description The full list of when the symbolic persistent variables keep their values and when the value is lost can be found in the Table 2-6. Besides the persistent area size declared in the Table 2-5, are reserved these 44 bytes to store information about the persistent variables (not available for use).

  • Page 20: Serial Interfaces

    2. Technical Description information. This area is shared with source code memory, being the total area the sum of “program memory” and “source code memory”. User files memory: This memory area offers another way for the user to store files such as doc, pdf, images, and other files.

  • Page 21: Ethernet Interfaces

    2. Technical Description RS-485 Maximum Transceivers: It is the maximum number of transceivers that can be used on a same bus. Ethernet Interfaces NET 1 NX3004, NX3005, NX3010, NX3020, NX3030 Connector Shielded female RJ45 Auto crossover Maximum cable length 100 m Cable type UTP or ScTP, category 5 Baud rate...

  • Page 22: Power Supply

    2. Technical Description Table 2-11. Ethernet NET 2 Interface Features Power Supply NX3004, NX3005 Nominal input voltage 24 Vdc Maximum output power 15 W Maximum output current Input voltage 19.2 to 30 Vdc Maximum input current (inrush) 30 A Maximum input current 1.4 A Maximum input voltage interrupt 10 ms @ 24 Vdc...

  • Page 23: Compatibility With Other Products

    2. Technical Description Compatibility with Other Products There are some incompatibilities between the Nexto Series CPUs and the MasterTool IEC XE. See the following table to find out which version of MasterTool IEC XE should be used. Nexto Series CPU Software Version MasterTool IEC XE compatible version NX3004 NX3005...

  • Page 24: Time For Instructions Execution

    2. Technical Description Time for Instructions Execution Table 2-15 presents the necessary execution time for different instructions in Nexto Series CPUs: Instruction Language Variables Instruction Times (us) 1000 Contacts BOOL REAL 1000 Divisions REAL REAL REAL 1000 Multiplications REAL REAL REAL 1000 Sums REAL...

  • Page 25: Physical Dimensions

    2. Technical Description Physical Dimensions NX3004/NX3005 Dimensions in mm. Figure 2-2. NX3004 and NX3005 CPU Physical Dimensions...

  • Page 26: Nx3010/Nx3020/Nx3030

    2. Technical Description NX3010/NX3020/NX3030 Dimensions in mm. Figure 2-3. NX3010, NX3020 and NX3030 CPU Physical Dimensions...

  • Page 27: Purchase Data

    2. Technical Description Purchase Data Integrant Items The product package has the following items:  NX3004, NX3005, NX3010, NX3020 or NX3030 module  6-terminal connector with fixing (only NX3004 and NX3005)  Installation guide Product Code The following code should be used to purchase the product: Code Description CPU, 1 Ethernet port, 1 serial channel, remote rack expansion support and power...
  • Page 28 CPUs of the Nexto Series and Altus products of the H Series. AL-1754: RS-232C standard cable with one DB9 male connector and one DB9 female connector for o communication between CPUs of the Nexto Series and Altus products of the Exter Series or Serial port, RS-232C standard, of a microcomputer.

  • Page 29: Installation

    3. Installation 3. Installation This chapter presents the necessary proceedings for the Nexto Series CPUs physical installation, as well as the care that should be taken with other installation within the panel where the CPU is been installed. Mechanical Installation NX3004 and NX3005 The CPUs NX3004 and NX3005 must be inserted in the backplane rack position 0.

  • Page 30: Nx3010, Nx3020 And Nx3030

    3. Installation Diagram Notes: 1. Ethernet interface pattern 10/100Base-TX for programming, debugging and MODBUS TCP network connection or other protocols. 2. Serial interface pattern RS-485/RS-422 for MODBUS RTU network connection or other protocols. The physical interface choice depends on the cable used. 3.

  • Page 31: Ethernet Network Connection

    3. Installation 11. Serial interface pattern RS-485/RS-422 for MODBUS RTU network connection or other protocols. The physical interface choice depends on the cable used. 12. The module is grounded through Nexto Series backplane rack. 13. The power supply comes from the backplane rack connection. There is no need for external connections.

  • Page 32: Network Cable Installation

    3. Installation Five ARP commands are triggered within a 200 ms initial interval, doubling the interval every new triggered command, totalizing 3 s. Example: first trigger occurs at time 0, the second one at 200 ms and the third one at 600 ms and so on until the fifth trigger at time 3 s. Network Cable Installation Nexto Series CPUs Ethernet ports, identified on the panel by NET 1 and NET 2 (NX3020 and NX3030), have pattern pin outs which are the same used in PCs.

  • Page 33: Serial Network Connection Rs-232

    3. Installation Serial Network Connection RS-232 The NX3010, NX3020 and NX3030 COM 1 non isolated communication interface allows the connection to a RS-232C network. As follows it’s presented the DB9 female connector to Nexto CPU, with identification and sign description. Figure 3-4.

  • Page 34: Rs-485 Communication Without Termination

    3. Installation Figure 3-5. DB9 Female Connector, NX3004/NX3005 CPU (COM 1) and NX3010/NX3020/NX3030 CPU (COM 2) Sign Description Not used Term+ Internal Termination, positive TXD+ Data Transmission, positive RXD+ Data Reception, positive Negative Reference for External Termination Positive Reference for External Termination Term- Internal Termination, negative TXD-...

  • Page 35: Rs-485 Communication With Internal Termination

    3. Installation Figure 3-6. RS-485 Connections with no Termination Diagram Diagram Note: The not connected terminal must be insulated so they do not make contact with each other. RS-485 Communication with Internal Termination In order to connect in a RS-485 network using the internal termination in COM 1 (NX3004 or NX3005) or COM 2 (NX3010, NX3020 or NX3030) interface, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on Table 3-7.

  • Page 36: Rs-485 Communication With External Termination

    3. Installation Diagram Note: The not connected terminals must be insulated so they do not make contact with each other. RS-485 Communication with External Termination In order to connect to a RS-485 network using a COM 1 (NX3004 or NX3005) or COM 2 (NX3010, NX3020 or NX3030) interface external termination, the AL-1763 cable identified terminals must be connected in the respective device terminals according to the Table 3-8.

  • Page 37: Rs-422 Communication Without Termination

    3. Installation Figure 3-9. Connection Diagram of a RS-485 Network with External Termination and Master Redundancy RS-422 Communication without Termination In order to connect in a RS-422 network with no termination in COM 1 (NX3004 and NX3005) or COM 2 (NX3010, NX3020 and NX3030) interface, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on Table 3-9.

  • Page 38: Rs-422 Communication With Internal Termination

    3. Installation Figure 3-10. RS-422 Connections with no Termination Diagram Diagram Note: The not connected terminal must be insulated so they don’t make contact with each other. RS-422 Communication with Internal Termination In order to connect in a RS-422 network using the internal termination in COM 1 (NX3004 and NX3005) or COM 2 (NX3010, NX3020 and NX3030) interface, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on Table 3-10.

  • Page 39: Rs-422 Communication With External Termination

    The not connected terminals must be insulated so they do not make contact with each other. RS-422 Network Example Figure 3-13 below shows an example of RS-422 network utilization, using the Nexto CPU as master, slave devices with RS-422 Interface, and Altus solutions for terminators and connections.

  • Page 40: Memory Card Installation

    3. Installation Figure 3-13. RS-422 Network Example Diagram Note: The AL-2600 modules which are in the network endings perform the terminators function. In this case the AL-2600 keys must be configured in PROFIBUS Termination. Memory Card Installation This section presents how to insert the memory card into the models NX3010, NX3020 and NX3030 Nexto Series CPUs .

  • Page 41: Architecture Installation

    To execute the MasterTool IEC XE development software installation, it is necessary to have the distribution CD-ROM or download the installation file from the site http://www.altus.com.br/site_en/. For further information about the step by step to installation, consult MasterTool IEC XE User Manual MT8500 – MU299609.

  • Page 42: Configuration

    4. Configuration 4. Configuration The Nexto Series CPUs are configured and programmed through the MasterTool IEC XE software. The configuration made defines the behavior and utilization modes for peripherals use and the CPUs special features. The programming represents the application developed by the user, also known as applicative.
  • Page 43 4. Configuration NX3010: 32768 NX3010: 0 to 32768 NX3020: 65536 NX3020: 0 to 65536 NX3030: 98304 NX3030: 0 to 98304 CPU Parameters When enabled starts the user application Start User after the hardware Application After watchdog reset or Enable a Watchdog through the Runtime Disable Disable...
  • Page 44 4. Configuration ATTENTION: When the initial address or the retentive or persistent data memory size are changed in the user application, the memory is totally reallocated, what makes the retentive and persistent variable area be clean. So the user has to be careful so as not to lose the saved data in the memory. ATTENTION: In situations where the symbolic persistent memory area is modified, a message will be displayed by MasterTool IEC XE programmer, to choose the behavior for this area after charging the modified...
  • Page 45 4. Configuration For further information regarding the diagnostics correspondent to the above described situations, see Diagnostics via Variables. If a module is present in a specific position in which should not exist according to the configuration modules, this module is considered as non-declared. The options of hot swap Disabled for Declared Modules Only and Enabled with Consistency in the Start Only for Declared Modules do not take into consideration the modules that are in this condition.
  • Page 46 4. Configuration Stop mode and the LED DG starts to blink 4x (as shown in Table 4-3). For these cases, to turn the CPU back to normal Run, in addition to undo what caused the abnormal situation it is necessary to perform a Reset Warm or Reset Cold.
  • Page 47 4. Configuration Enabled, with Enabled with Enabled without Disabled for Consistency in Condition Startup Consistency in the Disabled declared modules the Start Only for Consistency Start only Declared Modules Non declared LED DG: 2x LED DG: 2x LED DG: Blinks 2x LED DG: Blinks 4x LED DG: Blinks 2x module...
  • Page 48 4. Configuration VAR RETAIN wLocalSymbolicRetentiveVariable_01 : WORD; END_VAR Or, for global variables, declared within a list of global variables: VAR_GLOBAL RETAIN wGlobalSymbolicRetentiveVariable_01 : WORD; END_VAR On the other hand, the persistent symbolic variables shall be declared in a Persistent Variables object, being added to the application.
  • Page 49 4. Configuration application layer. As the TCP configuration is a reference for every instances configured, the time will be valid if it is smaller than the configured inside a protocol:  Initial Time-out: indicates how long, after the first message transmission, the message must be retransmitted, assuming it has not been received by the destiny device.
  • Page 50 4. Configuration The following pictures depict the difference between the sending of an immediate and a calibrated ACK: ATTENTION; The NX3004 and NX3005 CPUs have a slightly different behavior. They don’t consider the value configured on the parameter Initial Time out, they consider only the communication Time out. Even so, the value configured for communication Time out is used when it’s inferior to 3 seconds and it’s never going to be doubled on retries.

  • Page 51: External Event Configuration

    4. Configuration ATTENTION: The delay parameter in case of ACK sending only applies to communication between the CPU and the MasterTool IEC XE software. To communicate with other devices and/or other protocols (MODBUS, for example) the standard used shall be “no delay”. Project Parameters The CPU project parameters are related to the configuration for input/output refreshing at the task that they are used of the project tasks and consistency of the retentive and persistent area in %Q, and...
  • Page 52 4. Configuration Figure 4-4. Configuration Screen for External Event in CPU In the configuration external event tab, within the CPU settings, it is necessary to select which module will be the interruption source, in the field Module Address: Name. Then it must be selected which input of this module will be responsible for the event generation (IO_EVT_0).

  • Page 53: Soe Configuration

    4. Configuration corresponding field. In this case, IO_EVT_0 should be selected since the other origin sources (IO_EVT_1 to IO_EVT_7) are not available. In the sequence, the field POUS should be checked if the right POU is selected, because it will be used by the user to define the actions to be performed when an external event occurs.
  • Page 54 4. Configuration The SOE will run in the MainTask context, starting already at the first cycle. The SOE will run at the end of each MainTask cycle, comparing the mapped bits in order to detect transitions occurred in the cycle. In this way, every cycle in which the events are generated, an increase of time in this cycle of the MainTask will occur.

  • Page 55: Time Synchronization

    4. Configuration the first client. Selects the TCP Port for communication port for 20001 1 to 65535 Client 2 the second client. Table 4-5. SOE Configuration Notes: Data Memory Size: The data memory size reserved to be used by the static data will always be twice the value set as the second half of the memory area is used to store the previous variables values of the first half.
  • Page 56 4. Configuration Figure 4-8. SNTP Configuration Configuration Description Standard Default Options Time zone of the user Time zone (hh:mm) location. Hours and minutes -3:00 -12:59 to +13:59 can be inserted. Disabled SNTP Service Enables the SNTP service Disabled Enabled Period for SNTP Time interval of the Synchronization (x1 synchronization requests...
  • Page 57 4. Configuration ATTENTION If the PLC receives a time sync command from the control center, and this option is disabled, an error answer will be returned to that command. But if this option is enabled then a success message will be returned to the control center, even that the sync command be discarded for there be another synchronism method active with higher priority.

  • Page 58: Internal Points

    4. Configuration one responds, the synchronization time will be 10 s minimum (waiting for the two servers response and the new connection with first server attempt). When NX3020 and NX3030 CPUs are used, depending on the SNTP server subnet, the client will use an Ethernet interface which is in the corresponding subnet in order to do the synchronism requests.
  • Page 59 4. Configuration ATTENTION If a value variable doesn’t own a related quality variable, it will be reported as default a constant good quality (no significant indication) when the value variable is reported to a client or control center. In this way, this tab purpose isn’t to create or declare internal points. To do that, just declare value and/or quality variables in a GVL and map it on the communication driver.
  • Page 60 4. Configuration Figure 4-10. Internal Points Configuration Example Quality Conversions The internal point's quality is a trust level information about the value stored on that point. The quality may inform, for example, that the value stored is out of range, or yet that it is valid, but low trusted.
  • Page 61 4. Configuration Name Type Description The RESTART flag indicates that the data haven’t been FLAG_RESTART BOOL updated by the field since the device’s reset. Indicates there is a communication failure on te way between FLAG_COMM_FAIL BOOL the data origin device and the reports device. If TRUE the data values are overwritten in the remote FLAG_REMOTE_SUBSTITUTED BOOL...
  • Page 62 4. Configuration FLAG_INACCURATE FLAG_OLD_DATA NOT TOPICAL FLAG_FAILURE INVALID FLAG_OPERATOR_BLOCKED BLOCKED FLAG_TEST VALIDITY_INVALID INVALID Table 4-10. Digital Points Conversion Internal to IEC 60870-5-104 Internal -> IEC 60870-5-104 Analog 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...
  • Page 63 4. Configuration MODBUS Internal Quality As the MODBUS standard don’t specify quality types to each point, but for help on use of each point's communication diagnostic, MasterTool allows the quality variables mapping, through an internal own structure, to each MODBUS point. The Table 4-13 describes the quality types that each MODBUS point can assume.
  • Page 64 4. Configuration To help on the development of such applications, there are following pratical examples, in ST language, for the main POFIBUS modules (DI, DO, AI. AO), based on Nexto Serie's PROFIBUS slaves (NX5110). The user should feel encouraged to make any needed adaptation and change to fit to its application.
  • Page 65 4. Configuration // Waits the PROFIBUS slave become apt to exchange data and diagnostics // (It is necessary to wait, avoiding invalid quality generation) IF DG_NX5110.tPbusHeadA.tStatus1.bStation_Non_Existent = FALSE AND DG_NX5110.tPbusHeadA.tStatus1.bStation_Not_Ready = FALSE AND DG_NX5110.tPbusHeadA.wIdentNumber > 0 THEN QUALITY_PB_NX1005_O.FLAGS.FLAG_COMM_FAIL:= FALSE; // If there is a module presente on the bus (slot = 2) and // if there isn’t no modules config problem (general) and // if there is no config problem in that module (specific) and // if there isn’t fatal error identification by the module and...
  • Page 66 4. Configuration // (check first, because invalid validity must prevail) DG_NX6000_8_AI_Voltage_Current.tGeneral.bCalibrationError = TRUE THEN QUALITY_PB_NX6000.VALIDITY:= VALIDITY_QUESTIONABLE; QUALITY_PB_NX6000.FLAGS.FLAG_INACCURATE:= TRUE; ELSE QUALITY_PB_NX6000.FLAGS.FLAG_INACCURATE:= FALSE; END_IF // Condition to turns on out of range indication // (check first, because invalid validity must prevail) IF DG_NX6000_8_AI_Voltage_Current.tDetailed.tAnalogInput_00.bOverRange = TRUE OR DG_NX6000_8_AI_Voltage_Current.tDetailed.tAnalogInput_00.bUnderRange = TRUE THEN QUALITY_PB_NX6000.VALIDITY:= VALIDITY_QUESTIONABLE;...

  • Page 67: Serial Interfaces Configuration

    4. Configuration QUALITY_PB_NX6100.FLAGS.FLAG_RESTART:= FALSE; QUALITY_PB_NX6100.FLAGS.FLAG_FAILURE:= FALSE; QUALITY_PB_NX6100.FLAGS.FLAG_INACCURATE:= FALSE; QUALITY_PB_NX6100.FLAGS.FLAG_OLD_DATA:= FALSE; ELSE // Condition to turns on imprecision indication // (check first, because invalid validity must prevail) IF DG_NX6100_4_AO_Voltage_Current.tGeneral.bCalibrationError = TRUE THEN QUALITY_PB_NX6100.VALIDITY:= VALIDITY_QUESTIONABLE; QUALITY_PB_NX6100.FLAGS.FLAG_INACCURATE:= TRUE; ELSE QUALITY_PB_NX6100.FLAGS.FLAG_INACCURATE:= FALSE; END_IF // Condition to turns on general failure indication (priority) IF (DG_NX5110.tPbusHeadA.dwModuleNotPresent AND SHL(1, 4)) >...
  • Page 68 4. Configuration Even Serial port parity Parity Always One Parity None configuration Parity Always Zero No Parity Sets the serial Data Bits communication character 5, 6, 7 and 8 bits quantity Sets the serial port stop Stop Bits 1, 1.5 and 2 bits Extended Mode: Extended operation mode which delivers information...
  • Page 69 4. Configuration bits number. Table 4-16 shows the allowed configurations for COM 1 interfaces of the NX3010, NX3020 and NX3030 CPUs: Data Bits Stop Bits Parity NO PARITY, ODD, EVEN, PARITY ALWAYS ONE, 1,1.5 PARITY ALWAYS ZERO NO PARITY, ODD, EVEN, PARITY ALWAYS ONE, 1, 2 PARITY ALWAYS ZERO NO PARITY, ODD, EVEN, PARITY ALWAYS ONE,...

  • Page 70: Com1 (Nx3004/Nx3005) And Com 2 (Nx3010/Nx3020/Nx3030)

    4. Configuration - Enabled: Configuration When true, generates an enabled RX CTS Event external event due to Enabled - Disabled: Configuration CTS signal change. disabled Table 4-17. RS-232 Standard Serial Advanced Configurations Notes: RX in TX: This advanced parameter is valid for RS-232C settings and RS-422. Event RX DCD: External events such as the DCD signal COM 1 of the CPUs NX3010, NX3020, NX3030, may be associated only to tasks of custom project profile, for further information, please see the MasterTool IEC XE User Manual –...

  • Page 71: Ethernet Interfaces Configuration

    4. Configuration Data Bits Stop Bits Parity NO PARITY, ODD, EVEN, PARITY ALWAYS AONE, 1, 1.5 PARITY ALWAYS ZERO NO PARITY, ODD, EVEN, PARITY ALWAYS AONE, 1, 2 PARITY ALWAYS ZERO NO PARITY, ODD, EVEN, PARITY ALWAYS AONE, 1, 2 PARITY ALWAYS ZERO NO PARITY, ODD, EVEN, PARITY ALWAYS AONE, 1, 2...

  • Page 72: Remote Ethernet Interfaces

    4. Configuration NET 2 The NET 2 interface is composed by a RJ45 communication connector pattern 10/100Base-TX. It allows the point to point or network communication in the following open protocols: MODBUS TCP Client, MODBUS RTU via TCP Client, MODBUS TCP Server and MODBUS RTU via TCP Server. The parameters which must be configured for the proper functioning of the application are described below: Configuration...
  • Page 73 4. Configuration An example of typical application for NX5000 module is the setting of a redundant HSDN (High Speed Deterministic Network) for communication between different PLCs. Through this network, several PLCs can exchange messages in an entirely segregated network to ensure determinism and fast communication.

  • Page 74: Protocols Configuration

    4. Configuration Using the NX3020 CPU it is possible to insert up to two NX5000 modules in the project. By using the NX3030 CPU it is possible to insert up to six. If it is used a CPU NX3020 or NX3030, it is possible to configure a NIC Teaming pair, using up to the maximum number of modules allowed for each CPU, such as the architecture shown in the Figure 4-11, where we have a NIC Teaming pair and one independent Ethernet interface, using three modules.
  • Page 75 4. Configuration Table 4-24. Limits of the protocols by CPU Notes: Mapped Points: Each variable or item of a given data type is assumed to be a mapping. The same is considered for each position of the ARRAY type. This means that if a simple variable is declared, it will be considered a mapping and if an ARRAY type is declared, the count will be equal to the size of the declared ARRAY.
  • Page 76 4. Configuration MODBUS RTU MODBUS RTU MODBUS Ethernet MODBUS Ethernet Limitations Master Slave Client Server Maximum number of mappings per instance Maximum number of devices Maximum number of mappings per device Maximum number of simultaneous requests per instance Maximum number of simultaneous requests per device...
  • Page 77 4. Configuration MODBUS RTU MODBUS RTU MODBUS MODBUS Limitations Master Slave Ethernet Client Ethernet Server Devices per instance Requests per device Simultaneous requests per instance Simultaneous requests per device Table 4-26. MODBUS Protocol Limitations for Symbolic Mappings Notes: Devices per instance: ...

  • Page 78: Protocol Behavior X Cpu State

    4. Configuration IEC 60870-5-104 Limitations Servidor Devices per instance Simultaneous requests per instance Simultaneous requests per device Table 4-27. Protocol Server IEC 60870-5-104 Limits Notes: Devices per instance: Quantity of client devices, of type control center, supported for each protocol Server IEC 60870-5-104 instance.

  • Page 79: Double Points

    4. Configuration Notes: Symbol : Protocol remains active and operating normally. Symbol :Protocol is disabled. SOE: Sequence of Events protocol (SOE) is not available for NX3004, NX3005 and NX3010 CPU models. IEC 60870-5-104: The IEC 60870-5-104 Server protocol is not allowed to NX3005 and NX3010 CPU models.
  • Page 80 4. Configuration Figure 4-13. CPU’s Event Queue Cosumers The consumers are typically communication drivers that that will communicate with SCADA or HMI. After been stored in CPU’s queue, the cosumers receive the events related to communication points mapped in its configuration. These events are then stored in a consumer’s own events queue, which the size and working is described on the communication driver specific section .

  • Page 81: Interception Of Commands Coming From The Control Center

    4. Configuration  If the CPU aborted the event generation (because occurred to more events in a single execution cycle than the events queue total size) Producers The producers are tipically communication drivers or PLC internal elements that are capable to generate events.
  • Page 82 4. Configuration Input action defined by user from the following list: SUCCESS(0), NOT_SUPPORTED(1) BLOCKED_BY_SWITCHING_HIERARCHY(2) SELECT_FAILED(3) INVALID_POSITION(4) POSITION_REACHED(5) PARAMETER_CHANGE_IN_EXECUTION(6) STEP_LIMIT(7) BLOCKED_BY_MODE(8) BLOCKED_BY_PROCESS(9) BLOCKED_BY_INTERLOCKING(10) BLOCKED_BY_SYNNCHROCHECK(11) COMMAND_ALREADY_IN_EXECUTION(12) BLOCKED_BY_HEALTH (13) eCommandResult ENUM ONE_OF_N_CONTROL(14) ABORTION_BY_CANCEL(15) TIME_LIMIT_OVER(16) ABORTION_BY_TRIP(17) OBJECT_NOT_SELECTED(18) OBJECT_ALREADY_SELECTED(19) NO_ACCESS_AUTHORITY(20) ENDED_WITH_OVERSHOOT(21) ABORTION_DUE_TO_DEVIATION(22) ABORTION_BY_COMMUNICATION_LOSS(23) BLOCKED_BY_COMAND(24) NONE(25) INCONSISTENT_PARAMETERS(26) LOCKED_BY_OTHER_CLIENT(27) HARDWARE_ERROR(28)
  • Page 83 4. Configuration Parameter Type Description Indicates that a command was intercepted and the data are bCommandAvailable BOOL available to be processed. This structure store received command data, which is composed by the following fields: - eCommand - sSelectParameters sCommand STRUCT - sOperateParameters - sCancelParameters The description of each field is in this section.
  • Page 84 4. Configuration Parameter Type Description When true indicates that an operation command without bDirectOperate BOOL select was received. When true indicates that a command, which doesn’t require bNoAcknowledgement BOOL the receiving acknowledge, was received. When true indicates that an operation command activated bTimedOperate BOOL by time was received.

  • Page 85: Modbus Rtu Master

    4. Configuration Table 4-40. Parameters sEnumeratedStatus Parameter Type Description Informs the data type of the received analog value. eType ENUM INTEGER (0) FLOAT (1) diValue DINT Point operation value, integer format. fValue REAL Point operation value, float format. Table 4-41. Parameters sAnalogueValue Parameter Type Description...
  • Page 86 4. Configuration  Configure the serial interface, choosing the transmission speed, the RTS/CTS signals behavior, the parity, the channel stop bits, among others configurations by a double click on the COM 1 or COM 2 serial channel.  See Configuration - Serial Interfaces Configuration chapter. MODBUS Master Protocol Configuration by Symbolic Mapping To configure this protocol using symbolic mapping, you must perform the following steps: ...
  • Page 87 4. Configuration Direct Diagnostic Variable Representation Size Description T_DIAG_MODBUS_RTU_MASTER_1.* Variable Diagnostics Bits: %QX(n).0 bRunning The master is running. The master is not running (see bit: %QX(n).1 bNotRunning bInterruptedByCommand). The bit bNotRunning was enabled as %QX(n).2 bInterruptedByCommand the master was interrupted by the user through command bits.
  • Page 88 4. Configuration Direct Diagnostic Variable Representation Size Description T_DIAG_MODBUS_RTU_MASTER_1.* Variable %QX(n+2).6 bDiag_22_reserved Reserved %QX(n+2).7 bDiag_23_reserved Reserved %QB(n+3) byDiag_03_reserved BYTE Reserved Communication Statistics: Counter of request transmitted by the %QW(n+4) wTXRequests WORD master (0 to 65535) Counter of normal responses received %QW(n+6) wRXNormalResponses WORD...
  • Page 89 4. Configuration Configuration Description Default Options Slave Address MODBUS slave address 0 to 255 Communication Defines the application 3000 10 to 65535 Time-out (ms) level time-out Defines the numbers of Maximum Number retries before reporting a 0 to 9 of Retries communication error Table 4-46.
  • Page 90 4. Configuration Configuration Description Default Options Name of a variable 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 91 4. Configuration Figure 4-17. Data Requests Screen MODBUS Master Default Configuration Description Options Value 01 – Read Coils 02 – Read Input Status 03 – Read Holding Registers 04 – Read Input Registers 05 – Write Coil Function Code MODBUS function type 06 –...
  • Page 92 4. Configuration Notes: Setting: the number of factory default settings, and the values for the column Options, may vary according to the data type and MODBUS function (FC). Function Code: MODBUS (FC) functions available are the following: Code Function Type Description 0x01 Read coils (FC 01)
  • Page 93 4. Configuration Direct Diagnostic variable of type Representation Size Description T_DIAG_MODBUS_RTU_MAPPING_1.* Variable Communication status bits: Communication idle %QX(n).0 bCommIdle (waiting to be executed) %QX(n).1 bCommExecuting Active communication Communication delayed, because the maximum number of concurrent requests was reached. Deferred communications will be carried out in the same sequence in which they were ordered to %QX(n).2...
  • Page 94 128, 129 and 255 presented in the table are valid only when using Altus slaves. Slaves from other manufacturers might use other definitions for each code. Disabling Variable: variable of Boolean type used to disable, individually, MODBUS requests configured on request tab via button at the bottom of the window.
  • Page 95 4. Configuration Figure 4-18 MODBUS RTU Master Setup Screen Direct representation variables (%Q) for the protocol diagnostic: Configuration Description Default Value Options Initial Address of Initial address of the 0 to 2147483628 Diagnostics in %Q diagnostic variables Size Size of diagnostics area Disabled for editing Table 4-53.
  • Page 96 4. Configuration Devices Configuration – Configuration for Direct Representation (%Q) The configuration of the slave devices, viewed in Figure 4-19, comprises the following parameters: Figure 4-19. Device Configuration Configuration Description Default Value Option Identifier, according to Name Name of the instance MODBUS_Device IEC 61131-3 The MODBUS slave...
  • Page 97 4. Configuration Mappings Configuration – Configuration for Direct Representation (%Q) The MODBUS relations settings, viewed in Figure 4-20 and Figure 4-21, follow the parameters described in Table 4-55: Figure 4-20. MODBUS Data Type Figure 4-21. MODBUS Function In Table 4-55, the number of factory default settings, and the values for the column options, may vary according to the data type and MODBUS function (FC).

  • Page 98: Modbus Rtu Slave

    4. Configuration Write Mask of IEC Initial address of the variables for the 0 to 2147483644 Variables write mask (%Q) Table 4-55. Device Mapping Notes: Function: the available data types are detailed in the Table 4-48 and MODBUS functions (CF) are available in the Table 4-50.
  • Page 99 4. Configuration Independent of the configuration mode, the steps to insert an instance of the protocol and configure the serial interface are equal. The procedure to insert an instance of the protocol is found in detail in the MasterTool IEC XE User Manual -MU299605. The remaining configuration steps are described below for each mode: ...
  • Page 100 4. Configuration Figure 4-23. Modbus Slave Advanced Configurations Configuration Description Default Possibilities Time for the instance execution within the Task Cycle (ms) cycle, without 20 to 100 considering its own execution time Delay for the Send Delay (ms) 0 to 65535 transmission response Minimum silence time Minimum...
  • Page 101 4. Configuration Direct Diagnostic Variable Representation Size Description T_DIAG_MODBUS_RTU_SLAVE_1 *. Variable The slave is not in execution (see bit: %QX(n).1 bNotRunning bInterruptedByCommand) The bit bNotRunning was enabled as %QX(n).2 bInterruptedByCommand the slave was interrupted by the user through command bits %QX(n).3 bConfigFailure Discontinued diagnosis...
  • Page 102 4. Configuration Direct Diagnostic Variable Representation Size Description T_DIAG_MODBUS_RTU_SLAVE_1 *. Variable Communication Statistics: Counter of normal requests received by the slave and answered normally. In %QW(n+4) wRXRequests WORD case 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...
  • Page 103 4. Configuration Configuration Description Default Options Name of a variable declared in a program or Value Variable Symbolic variable name Coil (1-bit) Input Status (1-bit) Data Type MODBUS data type Holding Register (16-bit) Input Register (16-bit) Data Start MODBUS data initial address 1 to 65536 Address Data Size...
  • Page 104 4. Configuration Figure 4-25. MODBUS RTU Slave Configuration Screen Address and direct representation variables (%Q) to control relations and diagnostics: Configuration Description Default Value Options %Q Start Address Initial address of the diagnostic 0 to 2147483628 variables DiagnosticsArea Disabled for Size Size of diagnostics area editing...
  • Page 105 4. Configuration Mappings Configuration – Configuration via Direct Representation (%Q) The settings of the MODBUS relations, viewed in Figure 4-26 and Figure 4-27, follow the parameters described in Table 4-62: Figure 4-26. Adding MODBUS Relations Figure 4-27. Configuring the MODBUS Relation Configuration Description Default Value...

  • Page 106: Modbus Ethernet

    4. Configuration Data Size: the value of data size defines the maximum amount of data that a MODBUS relation can access, from the initial address. Thus, to read a continuous address range, it is necessary that all addresses are declared in a single interface. This field varies with the MODBUS data type configured, i.e.
  • Page 107 4. Configuration Figure 4-28. MODBUS TCP Communication Network The association of MODBUS variables with CPU symbolic variables is made by the user through relations definition via MasterTool IEC XE configuration tool. It’s possible to configure up to 32 relations for the server mode and up to 128 relations for the client mode. The relations in client mode, on the other hand, must respect the data maximum size of a MODBUS function: 125 registers (input registers or holding registers) or 2000 bits (coils or input status).
  • Page 108 4. Configuration Table 4-63 and Table 4-64 bring, respectively, the complete list of data and MODBUS functions supported by the Nexto CPUs. Data type Size [bits] Description Coil Digital output which can be read or written Input Status Digital input which can be only read Holding Register Analog output which can be read or written Input Register...
  • Page 109 4. Configuration  Add and configure the MODBUS mappings, specifying the variable name, data type, data initial address, data size and variable that will receive the quality data.  Add and configure the MODBUS request, specifying the desired function, the scan time of the request, the initial address (read/write), the size of the data (read/write), the variable that will receive the data quality, and the variable responsible for disabling the request.
  • Page 110 4. Configuration (counters) %QX(n+2).3 bDiag_19_reserved Reserved %QX(n+2).4 bDiag_20_reserved Reserved %QX(n+2).5 bDiag_21_reserved Reserved %QX(n+2).6 bDiag_22_reserved Reserved %QX(n+2).7 bDiag_23_reserved Reserved %QB(n+3) byDiag_03_reserved BYTE Reserved Communication Statistics: Counter of number of requests %QW(n+4) wTXRequests WORD transmitted by the client (0 to 65535) Counter of normal answers %QW(n+6) wRXNormalResponses WORD...
  • Page 111 4. Configuration Notes: IP Address: IP address of Modbus Server Device. TCP Port: if there are multiple instances of the protocol added in a single Ethernet interface, different TCP ports must be selected for each instance. Some TCP ports, among the possibilities mentioned above, are reserved and therefore cannot be used.
  • Page 112 4. Configuration Figure 4-31. MODBUS Data Type Default Configuration Description Options Value Name of a variable declared in a program or Value Variable Symbolic variable name Coil Write (1-bit) Coil Read (1-bit) Holding Register Write (16-bit) Holding Register Read (16 bit) Data Type MODBUS data type Holding Register –...
  • Page 113 4. Configuration Data Start Address: initial address of the MODBUS mapping data. Data Size: the size value specifies the maximum amount of data that a MODBUS relation can access, from the initial address. Thus, to read a continuous address range, it is necessary that all addresses are declared in a single interface.
  • Page 114 4. Configuration Variable or GVL Field for symbolic variable used to disable MODBUS requests individually configured. Variable used to disable Disabling Variable This variable must be of BOOL type. The MODBUS variable can be simple or array element and can be in structures. Table 4-71.
  • Page 115 4. Configuration Write Data Range: this field shows the MODBUS write data range configured for each request. The initial address of writing plus the size of the write data will result in the range of write data for each request. Diagnostic Variable: the configured MODBUS request diagnostics, either by symbolic mapping or by direct representation, are stored in variables of type T_DIAG_MODBUS_ETH_CLIENT_1 and the mapping by direct representation are in 4-byte and 2-word, which is described in Table 4-73 (n is...
  • Page 116 Exception Codes: the exception codes show in this filed is the server returned values. 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.
  • Page 117 4. Configuration  Add and configure devices by setting address, direct representation variables (%Q) to disable the relations and communication port.  Add and configure MODBUS relations, specifying the data type and MODBUS function, time- outs, direct representation variables (%Q) to receive diagnoses of the relation and other to receive/write the data, amount of data to be reported and polling of the relation.
  • Page 118 4. Configuration Device Configuration – Configuration via Direct Representation (%Q) The configuration of client devices, displayed in Figure 4-34, includes the following parameters: Figure 4-34. Configuring MODBUS Client Configuration Description Factory default Options Identifier, according to Name Name of the instance MODBUS_Device IEC 61131-3 1.0.0.1 to...
  • Page 119 4. Configuration Mapping Configuration – Configuration via Direct Representation (%Q) The setting of the MODBUS relations, displayed in Figure 4-35 and Figure 4-36, follows the parameters described in Table 4-77. Figure 4-35. MODBUS Data Type Figure 4-36. MODBUS Function Configuration Description Default Value Option...
  • Page 120 4. Configuration Write Mask of Starting address of variables 0 to 2147483644 IEC Variables for write mask (%Q) Table 4-77. Device Mapping Notes: Device Mappings Table: the number of settings and values described in the column Options may vary according to the data type and MODBUS function. Slave Address: typically, the address 0 is used when the server is a MODBUS RTU or MODBUS TCP Gateway via TCP, and the same broadcasts the request to all network devices.
  • Page 121 4. Configuration MODBUS Client Relation Start in Acyclic Form To start a MODBUS Client relation in acyclic form, it is suggested the following method which can be implemented in a simple way in the user applicative program:  Define the maximum polling time for the relations ...
  • Page 122 4. Configuration TCP Port: if there are multiple instances of the protocol added in a single Ethernet interface, different TCP ports must be selected for each instance. Some TCP ports, among the possibilities mentioned above, are reserved and therefore cannot be used. They are: 80, 8080, 1217, 1740, 1741, 1742,1743 and 11740.
  • Page 123 4. Configuration Configuration Description Default Value Options Time for the instance execution within the cycle, without Task Cycle (ms) 5 to 100 considering its own execution time. Maximum idle time between Connection Inactivity client and server before the 10 to 3600 Time-out (s) connection is closed by the server.
  • Page 124 4. Configuration %QX(n+2).3 bDiag_19_reserved Reserved %QX(n+2).4 bDiag_20_reserved Reserved %QX(n+2).5 bDiag_21_reserved Reserved %QX(n+2).6 bDiag_22_reserved Reserved %QX(n+2).7 bDiag_23_reserved Reserved %QB(n+3) byDiag_03_reserved BYTE Reserved Communication statistics: Number of established connections %QW(n+4) wActiveConnections WORD between client and server (0 to 64). Connections counter, between the client and server, interrupted after %QW(n+6) wTimeoutClosedConnections...
  • Page 125 4. Configuration Note: Counters: all counters of the MODBUS Ethernet Server Diagnostics return to zero when the limit value 65535 is exceeded Mapping Configuration – Configuration via Symbolic Mapping The setting of the MODBUS Server mappings, visualized in Figure 4-39, follows the parameters described in Table 4-82.
  • Page 126 4. Configuration Data Range: is a read-only field and reports on the range of addresses that is being used by this mapping. It is formed by the sum of the fields "Initial Address" and "Size". There can be no range overlays with others mappings of the same "data type".
  • Page 127 4. Configuration RTU via TCP Protocol Protocol selection Table 4-83. Settings to control relations and diagnostics Notes: %Q Start Address of Diagnostics Area: this field is limited by the size of output variables addressable memory (%Q) at CPU, which can be found in chapter Technical Description - Specific Features.
  • Page 128 4. Configuration Figure 4-42. MODBUS Function Configuration Description Default Options Coil (1 bit) Holding Register (16 bits) Data Type MODBUS data type Coil Input Status (1 bit) Input Register (16 bits) Data Start MODBUS data initial 1 to 65536 Address address 1 to 65536 (Holding Register and Input Register)
  • Page 129 4. Configuration still not used. The default cannot be defined for the Data Size field as it will vary according to selected MODBUS data type. The configurations in the “Filters...” button, described on Table 4-85, are related to the TCP communication filters: Configuration Description...

  • Page 130: Opc Da Server

    4. Configuration OPC DA Server It’s possible to communicate with the Nexto Series CPUs using the OPC DA (Open Platform Communication Data Access) technology. This open communication platform was developed to be the standard in industrial communications. Based on client/server architecture, it offers several advantages in project development and communication with automation systems.
  • Page 131 4. Configuration stored. The SCADA system access the information on these devices and store on the SCADA server, so that the SCADA clients can consult it during the plant operation. Acquisition Network The acquisition network is where the requests for data collected by field devices travel.
  • Page 132 4. Configuration ATTENTION: The variables shown in the objects IoConfig_Globals, IoConfig_Application_Mappings e IoConfig_Global_Mappings are used internally for I/O control e shouldn’t be used by the user. ATTENTION: In addition to the variables declared at SFC language POUs, some implicitly created variables are also shown.
  • Page 133 4. Configuration {attribute 'symbol' := 'write'} the column shows {attribute 'symbol' := 'readwrite'} the column shows Type Data type of the declared variable. Members When the data type is a Struct, a button is enabled in this column. Clicking on the button will allow the selection of which elements of that struct will be provided to the OPC Server.
  • Page 134 4. Configuration  {attribute 'symbol' := 'read'} – when the attribute value is ‘read’, the variables will be available to the OPC Server with read only access right.  {attribute 'symbol' := 'write'} – when the attribute value is ‘write’, the variables will be available to the OPC Server with write only access right.
  • Page 135 4. Configuration Figure 4-46. OPC Server Settings The Gateway Configuration is the same set in the Gateway used for the communication between the MasterTool IEC XE and the PLC and described in Communication Configuration, present in the MasterTool IEC XE User Manual – MU299609. If the configuration used is localhost, the Gateway Address must be filled with 127.0.0.1.
  • Page 136 4. Configuration recommended to use STRING with numbers or with “_”. It the project name that is loaded in the PLC. allows up to 49 characters. Gateway Address IP Address of the 127.0.0.1 0.0.0.0 to computer that the 255.255.255.255 OPC Server is installed, for the cases in which all PLCs are in the same...
  • Page 137 4. Configuration When a new PLC needs to be configured on the OPC Server, simply press the New PLC button and the configuration will be created. When the setup screen is accessed, a list of all PLCs already configured on the OPC Server will be displayed. Existing configurations can be edited by selecting the PLC in the Devices list and editing the parameters.
  • Page 138 4. Configuration object with the right read only by the SCADA. When the value of the variable is TRUE, data is read by connecting with this PLC. This way, every time there is a status change among PLCs, the variable state will also change, remaining in the state TRUE in the PLC which is in the redundancy active state.
  • Page 139 4. Configuration STATE_NO_SYMBOLS There are no symbols (variables) available in the PLC configured in the OPC Server. It can happen when there are no symbols or there isn’t a project loaded on the PLC. STATE_SYMBOLS_LOADED Finished the process of reading the symbols (variables) from the PLC configured in the OPC Server.
  • Page 140 4. Configuration Maximum number of variables communicating with a single 20.000 Maximum number of variables 5.000 declared in a single POU or GVL Maximum number of PLCs in a OPC Server Maximum number of simultaneous connections of an OPC Server in a single PLC Table 4-91.
  • Page 141 4. Configuration Figure 4-47. Selecting the OPC Server in the Client Configuration In cases where the server is remotely located, it may be necessary to add the network path or IP address of the computer in which the server is installed. In these cases, there are two configuration options.

  • Page 142: Master Ethercat

    4. Configuration ATTENTION: The simulation mode of MasterTool IEC XE software can be used for OPC communication tests. The information on how to configure it are presented in the Testing an OPC Communication using the Simulator section of the Master Tool IEC XE User Manual – MU299609. Master EtherCAT EtherCAT (Ethernet Control Automation Technology) is a master-slave architecture protocol with high performance, for deterministic Ethernet, that allows real time performance as it updates 1000...
  • Page 143 4. Configuration ports. A EherCAT junction is marked with the icon. The Device Tree example in Figure 4-49 shows different possibilities. Figure 4-49. EtherCAT configuration example ATTENTION: - Only one EtherCAT Master instance per project is allowed. - Only supported by the NX3020 and NX3030 CPU models. - Only available on the NET connectors of the PLC.
  • Page 144 4. Configuration than one device with the same description. With a double click on the entrance a list will open, and so the desired device can be selected. After completing the changes in the EtherCAT network configuration, it’s necessary to do a new project download, for the changes to take effect.
  • Page 145 4. Configuration InSync the first EtherCAT slave whose DC setting is active. This variable is TRUE shortly after this synchronization is successfully completed. This signal, for example, can be used to initialize SoftMotion function blocks in case of compatibility with the device after the CLP is in synchronized mode, otherwise jumps in position may occur.
  • Page 146 4. Configuration Variable Type Possible Values Description DG_Slave* ETC_SLAVE_BOOT=3 ETC_SLAVE_INIT=1 ETC_SLAVE_PREOPERATIO ETC_SLAVE_STA NAL=2 tDiag.wState Current Slave State. ETC_SLAVE_SAVEOPERATI ONAL=4 ETC_SLAVE_OPERATIONAL tDiag. After the EtherCAT stack initialization, this dwVendorID BOOL Any DWORD variable return the VendorID read from the slave. Any DWORD After the EtherCAT stack initialization, this tDiag.
  • Page 147 4. Configuration 90XX External Error. A000 Unsuccessful PRE- OPERATIONAL to SAFE- OPERATION transition. A001 Unsuccessful SAFE- OPERATIONAL to OPERATION transition. F0XX Additional Functions. FFXX Device Specific. byErrorRegister BYTE Faixa BYTE Register error. 0000-9FFF Manufacturer Specific Error Field. tDiag.tLastEmergen ARRAY[0..5] OF BYTE A000-EFFF Diagnostic Data.
  • Page 148 4. Configuration If enabled, this option Marked Sync Window allows monitoring the Unmarked Monitoring Unmarked Slave synchronization. Time for the Sync Synch Window [µs] 1 to 32768 Window Monitoring. Enabling of the combined Marked Use LRW instead of read and write Unmarked LWR/LRD Unmarked...
  • Page 149 4. Configuration also change the value of the wDCInSyncWindow variable, configuring the maximum jitter allowed on the synchronization between master and slaves. Use LRW instead of LWR/LRD: Activating this option enables the Slave-to-Slave communication because, instead of using separated reading (LRD) and write (LWR) commands, combined reading/writing (LRW) commands will be used.
  • Page 150 4. Configuration The Information tab, present on the EtherCAT Master configuration editor, shows, if available, the following general information about the module: Name, Vendor, Type, Version Number, Category, Order Number, Description, Image. EtherCAT Slave Configuration Below are listed the main EtherCAT Slave configuration options, as defined in the Device Description File.
  • Page 151 4. Configuration Device Configuration Description Default Value Possibilities network. Slave final address, assign by the Master during startup. This EtherCAT Address 1 to 65535 address is independent from the position in the network. Enable the Slave Marked Enable Expert Settings advanced Settings Unmarked Unmarked...
  • Page 152 4. Configuration Device Configuration Description Default Value Possibilities Set a time reference (in microseconds) for the SDO Access 0 to 100000 timeout check of a SDO Access. Set a time reference (in microseconds) for the I -> P timeout check of the 0 to 100000 (Timeouts) switch from Init to Pre-...
  • Page 153 4. Configuration Check VendorID and ProductID: By default, at startup of the system the Vendor ID and/or the Product ID will be checked against the current configured settings. If a mismatch is detected, the bus will be stopped and no further actions will be executed. This serves to avoid the download of an erroneous configuration.
  • Page 154 4. Configuration Figure 4-54. FMMU/Sync Dialog FMMU This table shows the Fieldbus Memory Management Units (FMMUs) of the slave which are used for handling the process data. Each mapping of the logical address GlobStartAddr on a physical address Ph. StartBit is defined. Bitwise mapping is possible. New units can be added and existing ones can be edited by the Edit FMMU dialog, to be opened via the Add…...
  • Page 155 4. Configuration Figure 4-55. Process Data Dialog The Expert Process Data dialog will only be available in the EtherCAT Slave configuration editor if the Enable Expert Settings option is activated. It provides another, more detailed, vision of the process data, adding to what is presented in the Process Data tab. Furthermore, the download of the PDO Assignment and the PDO Configuration can be activated in this dialog.
  • Page 156 4. Configuration Figure 4-56. Expert Process Data Dialog This dialog id divided in four sections and two options:  Sync Manager: List of Sync Manager with data size and type of PDOs  PDO Assignment: List of PDOs assigned to the selected Sync Manager. The checkbox activates the PDO and IO channels are created.
  • Page 157 4. Configuration Editing the PDO List Figure 4-57. Edit PDO List Dialog This dialog is opened through the context menu from the PDO List area, presented in Figure 4-56. Below are some explanations on the configuration options presented in this dialog. ...
  • Page 158 4. Configuration Figure 4-58. ‘Select item from object directory’ dialog Startup Parameters In the Startup Parameters tab, parameters for the device can be defined, which will be transferred by SDOs (Service Data Objects) or IDN at the system’s startup. The options available in this tab, as well as the access possibilities, vary according to the EtherCAT Slave used and they are present in the Device Description File.
  • Page 159 4. Configuration Figure 4-59. Online Dialog This tab is divided in the following functionality group.  State Machine: The buttons Init, Pre-Op (Pre-Operational), Op (Operational) and Safe-Op (Safe-Operational) can be used for debugging purposes. They make the slave transition to the respective state.

  • Page 160: Ethernet/Ip

    4. Configuration Figure 4-60. I/O Mapping Dialog Status and Information tabs The Status tab of the EtherCAT Slave provides status information (e.g. ‘Running’, ‘Stopped’) and device-specific diagnostic messages, also on the used card and the internal bus system. The Information dialog, presented in the EtherCAT Slave configuration editor, show, if available, the following general information about the module: Name, Vendor, Type, Version Number, Categories, Order Number, Description, Image.
  • Page 161 4. Configuration An EtherNet/IP Adapter supports up to 64 modules of input or output. These modules can be of type BYTE, WORD, DWORD or REAL. And the MainTask’s interval of a device running an Adapter must be lesser or equal the RPI. ATTENTION EtherNet/IP can’t be used together with ethernet NIC-Teaming nor with Half-Cluster's redundancy.
  • Page 162 4. Configuration Figure 4-62. Adding an EtherNet/IP Adapter or Scanner EtherNet/IP Scanner Configuration The Scanner requires at least one Adapter with which it will exchange data. New Adapters can be installed on MasterTool with the EDS and DCF Files. The configuration options may difer depending on the device description file of the added Adapter.
  • Page 163 4. Configuration Figure 4-63. Adding an EtherNet/IP Adapter Under the Scanner General After open the Adapter declared under the Scanner it’s possible to configure it as needed. The first Tab is General, on it is possible to configure the IP address and the Electronic Keying parameters. These parameters must be checked or unchecked if the adapter being used is installed on MasterTool.
  • Page 164 4. Configuration Figure 4-64. EtherNet/IP General Tab Connections The upper area of the Connections tab displays a list of all configured connections. When there is an "Exclusive Owner" connection in the EDS file, it is inserted automatically when the Adapter is added.
  • Page 165 4. Configuration The configuration data is defined in the EDS file. The data is transmitted to the remote adapter when the connection is opened. Configuration Description Default Value Options Request Packet Interval: Multiple of RPI (ms) exchange interval of the 10 ms MainTask input and output data.
  • Page 166 4. Configuration Assemblies The upper area of the Assemblies tab displays a list of all configured connections. When a connection is selected, the associated inputs and outputs are displayed in the lower area of the tab. Figure 4-67. EtherNet/IP Assemblies Output Assembly and Input Assembly: Configuration Description...
  • Page 167 4. Configuration Figure 4-68. Adding an EtherNet/IP Module under the Adapter Module Types There are 8 diferent modules which can be added under the adapter. Four outputs and four inputs. They are of type BYTE, WORD, DWORD and REAL. These types can be chosen in the general tab of the module Figure 4-69.

  • Page 168: Iec 60870-5-104 Server

    4. Configuration EtherNet/IP Module I/O Mapping It shows the name of the automatically generated instance of the module under IEC Objects in the Variable column. In this way, the instance can be accessed by the application The “Always update variables” option must be keeped as default in Enable 1. IEC 60870-5-104 Server This protocol is available to Nexto Serie CPUs NX3030 NX3020 and NX3005, on its Ethernet channels.
  • Page 169 4. Configuration Double Command (C_DC_NA) Regulating Step Command (C_RC_NA) Setting Point Command, normalized Value (C_SE_NA ) Setting Point Command, scaled Value (C_SE_NB ) Setting Point Command, short floating point Value (C_SE_NC ) REAL Table 4-101. Variables Declaration to IEC 60870-5-104 Notes: Regulating Step Command: The C_RC_NA’s object states Lower and Higher are associated respectively to ON and OFF internal DBP type states.
  • Page 170 4. Configuration pulses , also known by trip/close commands, with determined duration (enough to the switching of the device under control). Consult the Double Points section of Utilization Manual for informations about double digital points through DBP data type. Once the Nexto Series digital input and output modules don’t support DBP points mapping, some application trickery are needed to make it possible.
  • Page 171 4. Configuration Figure 4-72. Double Point Variables Mapping on the Client IEC 60870-5-104 Figure 4-73. Variables Mapping at the Module Inputs At last, the user must insert two code lines in its application, to be cyclically executed, to simple variables value attribution to double point: ...
  • Page 172 4. Configuration The example code below, POU CmdRcv, treats pulsed commands received from clients for a digital double point, mapped in a NX2020 module. Besides the following ST code it is need to map a DBP point in Nexto’s IEC 60870-5-104 server. Figure 4-75.
  • Page 173 4. Configuration byCmdType:= 102, byPulseTime:= DWORD_TO_BYTE(CmdReceive.sCommand.sOperateParameters.sValue.sDoublePoint.sPulseConfig.dwOffDu ration/10), ptDbpVarAdr:= ADR(dbpIEC104), stQuality:= IOQualities.QUALITY_NX2020[5], byStatus=> byResult); END_IF ELSE // Returns “command not supported” byResult:= 1; END_IF COMMAND_TYPE.CANCEL: // Returns “command finished with success” // (controlled by IEC104 protocol) byResult:= 7; END_CASE // Treats the pulsed command function result // and generates the answer to the intercepted command CASE byResult OF 1: // Invalid type of command...
  • Page 174 4. Configuration // 4 = module didn’t answer to the command (absent) // 5 = command started or running // 6 = There is already an active command on this point // 7 = pulse command finished with success END_VAR byState: BYTE;...
  • Page 175 4. Configuration ptDbpVarAdr^.ON:= FALSE; ptDbpVarAdr^.OFF:= FALSE; // Returns finished command, only if the command hasn’t changed IF byCmdType = 100 OR byCmdType = byState THEN byStatus:= 7; END_IF // Next state: initial byState:= 0; END_IF END_CASE // Checks digital module (DBP point) quality IF stQuality.VALIDITY <>...
  • Page 176 4. Configuration Figure 4-77. Server IEC 60870-5-104 General Parameters Screen Parameter Description Factory Default Possibilities Name of a variable declared in a POU Value Variable Symbolic variable name or GVL Single Point Information Double Point Information Step Position Information Measured Value (Normalized) Measured Value (Scaled) Measured Value (Short Floating Point)
  • Page 177 4. Configuration declared on Value Variable column, which value is going to be read, or reported to , the client in case of events. ATTENTION When the Counter Variable has a quality variable associated, to the quality to be transferred to the frozen variable at freeze command, it must be associated a quality variable to the frozen one.
  • Page 178 4. Configuration Parameter Description Factory Default Possibilities Listened port address to client Port Number connection. Used when the client 2404 1 to 65535 connection isn’t through IP. IP Address Connected client IP, used when the 0.0.0.0 1.0.0.1 to 223.255.255.254 (Master) client connection is through IP.
  • Page 179 4. Configuration Operate (s) starts from the received selection command acknowledge) waiting the Operate command All Events (SOE) All Events (SOE) Transmission Mode of Analog input events transmission mode Analog Inputs Events Most Recent Events Freeze by counter- interrogation command, Freeze by counter- transmit spontaneously Frozen couters transmission mode...
  • Page 180 4. Configuration The Standard IEC 60870-5-104, section “Transmission control using Start/Stop”, foresee the commands STARTDT and STOPDT utilization to data traffic control between client and server, using simple or multiple connections. Despite Nexto supports such commands, its utilization isn’t recommended to control data transmission, mainly with redundant CPUs, because such commands aren’t synchronized between both CPUs.

  • Page 181: Communication Performance

    4. Configuration Protocol IEC 60870-5-104 object type Qualifier Double Command Regulation Step Single Command Command No additional definition Same behavior of Same behavior of short Same behavior of short persistent qualifier pulse qualifier pulse qualifier (default) Short pulse duration Requires command interception to application treatment.
  • Page 182 4. Configuration For the master and client devices the operating principle is exactly the same, but taking into account the polling time of the MODBUS relation and not the cycle time of the MODBUS task. For these cases, the worst performance of a relationship will be performed after the polling time, along with the user application Execution Time.

  • Page 183: Opc Server

    4. Configuration N = 19.6 That is, in this configuration the MODBUS Server answers, on average, 19 requisitions per second. In case the obtained value is multiplied by the number of bytes in each requisition, we will obtain a transfer rate of n bytes per second. Remote Interfaces The performance of a device MODBUS Server in one remote Ethernet interface is similar to the performance in the CPU’s local interfaces.

  • Page 184: System Performance

    4. Configuration answer the requests. However, for it be a low priority task , it’s not guaranteed that it will run with that periodicity, because it depends on the CPU load and also on other protocol tasks rivalry. To help in the compreention of the driver Server IEC 60870-5-104 performance are presented the result of some test done with a Client 60870-5-104 simulator, connected to a NX3030 running a Server IEC 60870-5-104.The configured data base was compose of 900 digital points and 100 analog points ( all with quality and time stamp), and the maintask was using 70ms (of the 100ms interval).

  • Page 185: Memory Card

    4. Configuration Memory Card Data transfers involving the memory card is performed by the CPU in the background, as this gives priority to the execution of user application and communication processing. Thus, the transfer of files to the card may suffer an additional significant time, depending on the Cycle Time of the user application.
  • Page 186 4. Configuration ATTENTION: The function blocks for RTC (RTC (NextoGetDateAndTime, NextoGetDateAndTimeMs, NextoSetDateAndTime e NextoSetDateAndTimeMs) reading and writing cannot be used in the area of redundant data in redundant projects. The function blocks can be used only in non-redundant POUs, as the POU NonSkippedPrg. For more details on the functioning of POU NonSkippedPrg see NonSkippedPrg.
  • Page 187 4. Configuration Input and Output Type Description Parameters This variable present the reading of Time Zone TimeZone TIMEZONESETTINGS configuration. Table 4-116. Input and Output Parameters of GetTimeZone Output Parameters Type Description Returns the function error state, see Table GetTimeZone RTC_STATUS 4-125.
  • Page 188 4. Configuration Figure 4-84. SetDateAndTime Input parameters Type Description This variable, when receives a rising edge, REQUEST BOOL enables the clock writing. Receives the values of date and hour with EXTENDED_DATE_A DATEANDTIME milliseconds. See section ND_TIME EXTENDED_DATE_AND_TIME Table 4-119. Input Parameters of SetDateAndTime Output parameters Type Description...

  • Page 189: Rtc Data Structures

    4. Configuration ATTENTION: If you try to write time values outside the range of the RTC, the values are converted to valid values, provided they do not exceed the valid range of 01/01/2000 to 12/31/2035. For example, if the user attempts to write the value 2000 ms, it will be converted to 2 seconds, write the value 100 seconds, it will be converted to 1 min and 40 seconds.
  • Page 190 4. Configuration EXTENDED_DATE_AND_TIME This structure is used to store the RTC date when used the function blocks for date reading/setting within milliseconds of accuracy. It is described in the Table 4-123: Structure Type Variable Description BYTE byDayOfMonth Stores the day of the set date. BYTE ByMonth Stores the month of the set date.

  • Page 191: User Files Memory

    4. Configuration time zone. Table 4-125. RTC_STATUS TIMEZONESETTINGS This structure is used to store the time zone value in the reading/setting requests of the RTC’s function blocks and it is described in Table 4-126: Structure Type Variable Description iHour Set time zone hour TIMEZONE SETTINGS iMinutes...
  • Page 192 4. Configuration After updating the CPU column of files, the root directory of files stored in the CPU will be shown. Then it will be possible to select the folder where the files will be transferred to. The "InternalMemory" folder is a default folder to be used to store files in the CPU’s internal memory, since it is not possible to transfer files to the root directory.

  • Page 193: Memory Card

    4. Configuration Furthermore, the user has some operation options in the storing files area, which are the following:  New directory : allows the creation of a new folder in the user memory area  Delete item : allows the files excluding in the folders in the user memory area ...
  • Page 194 4. Configuration screen the user can configure the passwords, which control the information use. For further information regarding the table, see Project Parameters chapter. Figure 4-89. Memory Card Configuration 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 195: Mastertool Access

    4. Configuration ATTENTION: If the memory card is removed without have been unmounted through CPU’s menu, during a file transference, this process can cause the lose of card data as well as corrupt the files in it. This process may cause the need of another card formatting when it'll be inserted on the CPU again. ATTENTION: If there is any file at memory card root named “NextoMemCard”...

  • Page 196: Cpu's Informative And Configuration Menu

    4. Configuration Figure 4-91. Files Stored in the Memory Card Inside the memory card directory, additionally to the files which are stored into the card, it will be also the “NextoMemCard” and “Backup” folders. In these folders both the application and the current project are saved in case the user chooses to transfer them or to make a backup of them through the CPU menu.
  • Page 197 4. Configuration END. IP NET 2 Informative MASK NET 2 Informative RETURN Return level IDENT. CP Informative ESTADO REM. Informative REDUNDANCY SINCR. PROJ. Informative RETURN Return level FIRMWARE Informative BOOTLOADER Informative SOFTWARE PROC. AUX. Informative RETURN Return level CARD > CPU CPU PASSWORD Configurable CPU >...
  • Page 198 4. Configuration o PLC ID – Informs the PLC identification in the redundancy. Possible information:   o REMOTE STATE – Informs the state of the remote redundant PLC. Possible states:  ACTIVE  STANDBY  INACTIVE  NOT CONFIG. ...

  • Page 199: Function Blocks And Functions

    4. Configuration Figure 4-92. Contrast Adjust Besides the possibility of the Nexto CPUs menu to be closed through a long touch on the screen diagnostic button RETURN from level 1, there are also other output conditions that are described below: ...
  • Page 200 4. Configuration Therefore, when an external event is waited, the serial function blocks are finished and the control is returned to the main program. The task treatment continues in the next cycle, in other words, on the next time the block is called. Before describing the special function blocks for serial interfaces, it is important to know the Data types, it means, the data type used by the blocks: Data type...
  • Page 201 4. Configuration Data type Options Description Lower values make the TIMESTAMP more precise when the EXTENDED MODE is used and minimizes the overrun errors. However, values too low may cause too many interruptions and delay the CPU. When true, select the RX line and the block extended mode.
  • Page 202 4. Configuration Data type Options Description data are being overwritten. Returns to zero when it reaches the maximum value (65535). Sum the last 5 error counters (frame, RX_ANY_ERRORS parity, interruption, RX FIFO overrun, RX queue overrun). RX_REMAINING Number of characters in the RX queue. List of critic error codes that can be returned by the serial function block.
  • Page 203 4. Configuration Data type Options Description STOPBITS_1_5 Table 4-128. Serial Function Blocks Data types SERIAL_CFG This function block is used to configure and initialize the desired serial port. After the block is called, every RX and TX queue associated to the serial ports and the RX and TX FIFO are restarted. Figure 4-93.
  • Page 204 4. Configuration Utilization example in ST language, after the library Nexto Serial is inserted in the project: PROGRAM MainPrg Config: SERIAL_CFG; Port: SERIAL_PORT := COM1; Parameters: SERIAL_PARAMETERS := (BAUDRATE := BAUD9600, DATABITS := DATABITS_8, STOPBITS := STOPBITS_1, PARITY := PARITY_NONE, HANDSHAKE := RS232_RTS, UART_RX_THRESHOLD := 8, MODE :=NORMAL_MODE,...
  • Page 205 4. Configuration Output parameters Type Description This variable is true when the block is completely executed. It is false DONE BOOL otherwise. EXEC BOOL This variable is true while the block is being executed. It is false otherwise. This variable is true when the block concludes the execution with an error. It ERROR BOOL is false otherwise.
  • Page 206 4. Configuration Input parameters Type Description This variable, when true, enables the function REQUEST BOOL block use. Select the serial port, as described in the PORT SERIAL_PORT SERIAL_PORT data type. Table 4-133. SERIAL_GET_CTRL Input Parameters Output parameters Type Description This variable is true when the block is DONE BOOL completely executed.
  • Page 207 4. Configuration SERIAL_GET_RX_QUEUE_STATUS This block is used to read some status information regarding the RX queue, specially developed for the normal mode, but it can also be used in the extended mode. Figure 4-96. Block Used to Visualize the RX Queue Status Input parameters Type Description...
  • Page 208 4. Configuration Get_Status.EXEC; Get_Status.ERROR; Status := Get_Status.STATUS; //If it’s necessary to treat the error Status_RX := Get_Status.RXQ_STATUS; // If it’s necessary to treat the error of the RX queue SERIAL_PURGE_RX_QUEUE This function block is used to clean the serial port RX queue, local and remote. The UART RX FIFO is restarted too.
  • Page 209 4. Configuration PROGRAM MainPrg Purge_Queue: SERIAL_PURGE_RX_QUEUE; Port: SERIAL_PORT := COM1; Status: SERIAL_STATUS; END_VAR //INPUTS: Purge_Queue.REQUEST := TRUE; Purge_Queue.PORT := Port; //FUNCTION: Purge_Queue(); //OUTPUTS: Purge_Queue.DONE; Purge_Queue.EXEC; Purge_Queue.ERROR; Status := Purge_Queue.STATUS; // If it’s necessary to treat the error. SERIAL_RX This function block is used to receive a serial port buffer, using the RX queue normal mode. In this mode, each character in the RX queue occupy a single byte which has the received data, storing 5, 6, 7 or 8 bits, according to the serial interface configuration.
  • Page 210 4. Configuration Output parameters Type Description This variable is true when the block is DONE BOOL completely executed. It is false otherwise. This variable is true while the block is being EXEC BOOL executed. It is false otherwise. This variable is true when the block concludes the execution with an error.
  • Page 211 4. Configuration Figure 4-99. Block Used for Reception Buffer Reading Input parameters Type Description This variable, when true, enables the function REQUEST BOOL block use. Select the serial port, as described in the PORT SERIAL_PORT SERIAL_PORT data type. POINTER TO Pointer of a SERIAL_RX_CHAR_EXTENDED RX_BUFFER_POINTER SERIAL_RX_CHAR_E...
  • Page 212 4. Configuration finished. The time unit is 10µs. This output parameter type is important to detect the silence time in protocols as MODBUS RTU. It might not be the silence time after the last received character by this function block, as it is only true if RX_REMANING = 0.
  • Page 213 4. Configuration Input parameters Type Description This variable, when true, enables the function REQUEST BOOL block use. Select the serial port, as described in the PORT SERIAL_PORT SERIAL_PORT data type. RTS_VALUE BOOL Value to be written on RTS signal. RTS_EN BOOL Enables the RTS_VALUE parameter writing.
  • Page 214 4. Configuration SERIAL_TX This function block is used to transmit a data buffer through serial port and it is only finalized after all bytes were transmitted or after time-out (generating errors). Figure 4-101. Block for Values Transmission by the Serial Input parameters Type Description...

  • Page 215: Inputs And Outputs Update

    4. Configuration case some error has occurred during transmission. Table 4-146. SERIAL_RX Output Parameters Utilization example in ST language, after the library is inserted in the project and the serial port configured: PROGRAM MainPrg Transmit: SERIAL_TX; Port: SERIAL_PORT := COM1; Buffer_Pointer: ARRAY [0..9] OF BYTE := [0,1,2,3,4,5,6,7,8,9];...
  • Page 216 4. Configuration REFRESH_INPUT This function block is used to update the specified module inputs without the necessity to wait for the cycle to be completed. It is important to notice that the filters configured in the MasterTool IEC XE and the update time of the module inputs will have to be considered in effective time of the inputs update in the application developed by the user.
  • Page 217 4. Configuration REFRESH_OUTPUT This function block is used to update the specified module outputs. It is not necessary to wait until the cycle is finished. It is important to notice that the update time of the module outputs will have to be considered in the effective time of the outputs update in the application developed by the user.

  • Page 218: Pid Function Block

    4. Configuration PID Function Block The PID function block is used to control a real process. The block is always available in the NextoPID library which must be added to the project (for the library insertion proceeding, see MasterTool IEC XE Programming Manual – MP399608, chapter Library). Figure 4-104.
  • Page 219 4. Configuration Input parameters Type Description Dead band. Minimum error value able to generate a MV DeadBand REAL correction in automatic mode, in other words, little errors (smaller than the DeadBand) won’t cause any variation in the defined variable. Process variable maximum value. In case the PV value is higher than the configured, MaxPV REAL...
  • Page 220 4. Configuration Output parameters Type Description REAL Manipulated Variable. Real sample time, in seconds, used for the EffST REAL derivative action and MV limit rate calculus. Real sample time from the last three cycles, in Eff3ST REAL seconds, used for the derivative action calculus. Real sample time maximum value, in seconds, MaxEffST REAL...

  • Page 221: Timer Retain

    4. Configuration Timer Retain The time retain is a function block developed for applications as production line clocks, that need to store its value and restart the counting from the same point in case of power supply failure. The values stored by the function block, are only zero in case of a Cold Reset, Original Reset or a new application download (see the MasterTool IEC XE User Manual - MU299609), when the counters keep working, even when the application is stopped (Stop Mode).
  • Page 222 4. Configuration Figure 4-107. TOF_RET Block Graphic Behavior Utilization example in ST language: PROGRAM MainPrg VAR RETAIN bStart : BOOL := TRUE; TOF_RET : TOF_RET; END_VAR // When bStart=FALSE starts counting TOF_RET( IN := bStart, PT := T#20S); // Actions executed at the end of the counting IF (TOF_RET.Q = FALSE) THEN bStart := TRUE;...
  • Page 223 4. Configuration Figure 4-109. TON_RET Block Graphic Behavior Utilization example in ST language: PROGRAM MainPrg 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 224: Non-Redundant Timer

    4. Configuration Figure 4-111. TP_RET Block Graphic Behavior Utilization example in ST language: PROGRAM MainPrg VAR RETAIN bStart : BOOL; TP_RET : TP_RET; END_VAR // Configure TP_NR TP_RET( IN := bStart, PT := T#20S); bStart := FALSE; // Actions executed during the counting IF (TP_RET.Q = TRUE) THEN // Executes while the counter is activated ELSE...
  • Page 225 4. Configuration END_VAR // When bStart=FALSE starts the counting TOF_NR( IN := bStart, PT := T#20S); // Actions executed at the end of the counting IF (TOF_NR.Q = FALSE) THEN bStart := TRUE; END_IF TON_NR The TON_NR function block implements a delay time to enable an output and has its functioning and configuration similar to the TON_RET function block, differentiating only for not being redundant nor retentive.

  • Page 226: User Log

    4. Configuration bStart := FALSE; // Actions executed during the counting IF (TP_NR.Q = TRUE) THEN // Executes while the counter is activated ELSE // Executes when the counter is deactivated END_IF User Log Feature that allows the user to create own records and write to log files on the memory card present in the CPU.
  • Page 227 4. Configuration message with a resolution of milliseconds where the event was registered. The date and time information is also used in the formation of the names of the log files. The UserLogAdd function can be used to enter multiple messages within a single task and also in different application tasks.
  • Page 228 4. Configuration Input Parameters Type Description This variable specifies the event type of the log being byEventType BYTE added as options for the USER_LOG_EVENT_TYPES data type. This variable should contain the set of characters that pszMessage USER_LOG_MESSAGE compose the message to be added to the log file. The message must contain a maximum of 150 characters.

  • Page 229: Clearrtudiagnostic

    4. Configuration the generated by the UserLogAdd function. Logs of other CPUs and files added manually by the user during execution are not deleted. The Figure 4-116 represents the function UserLogDeleteAll: Figure 4-116. UserLogDeleteAll Function Utilization example in ST language: PROGRAM MainPrg eLogError : USER_LOG_ERROR_CODES;...

  • Page 230: Snmp

    4. Configuration Using example in ST language, where the function call is going to clear the events queue, and consequently , reset the communication drivers events queue usage diagnostics T_DIAG_DNP_SERVER_1.tClient_*.tQueueDiags.wUsage: PROGRAM UserPrg ClearEventQueueStatus : TYPE_RESULT; END_VAR ClearEventQueueStatus := ClearEventQueue(); SNMP Introduction SNMP (Simple Network Management Protocol) is a protocol widely used by network administrators to provide important information and diagnostic equipment present in a given Ethernet network.

  • Page 231: Private Mib

    1.4.0.25. For it has been reserved for PEN (Private Enterprise Number) with the unique number 43427 for products Altus. Thus, all private objects of Nexto Series can be accessed through the OID .1.3.6.1.4.1.43427.1 (iso.org.dod. internet.private.enterprise.Altus SA.Nexto). In this OID three relevant subdivisions Nexto CPUs, as seen in Figure 4-118.
  • Page 232 4. Configuration Figure 4-118. OID Tree View The objects available via SNMP in the Nexto Series CPUs are existing diagnostics, which are important for managing networks. These objects can be seen in Table 4-161. To access them through an SNMP manager the user must make requests from OID .1.3.6.1.4.1.43427.1.4.1 to NX3004, .1.3.6.1.4.1.43427.1.5.1 to NX3005, .1.3.6.1.4.1.43427.1.1.1 to NX3010, 1.3.6.1.4.1.43427.1.2.1 to NX3020 and.1.3.6.1.4.1 .43427.1.3.1 to NX3030.
  • Page 233 4. Configuration Groups Diagnostic Description Warm Start Counter: It will only be incremented during energization CPUWarmStartCounter sequence of the system and not due to the Reset Warm command of MasterTool IEC XE (0 to 65535) Counter of disorders smaller than the time of power CPUHotStartCounter failure to support the CPU (0 to 65535) Reset counter made by the RTS (Runtime System)

  • Page 234: Configuration

    4. Configuration Groups Diagnostic Description ConnectionStatus2 Connection status of client 02 Client 02 event queue status: FALSE – OK SOE2 OverflowStatus2 TRUE – Queue limit exceeded EventsCounter2 Client 02 event counter on queue Table 4-161. Diagnostics via SNMP These diagnostics was not available at the CPUs NX3004 and NX3005. ATTENTION: Items Ethernet NET2, SNTP and SOE are available only for CPUs NX3020 and NX3030 Configuration...

  • Page 235: User And Snmp Communities

    4. Configuration If the user wants to return to the default settings, it must be manually reconfigure the same according to the User and SNMP Communities section. Therefore, all current SNMP configurations will be kept in the firmware update process. These options can be visualized in Figure 4-120. Figure 4-120.

  • Page 236: User Management And Access Rights

    4. Configuration Communities Default String Type rocommunity Public Only read rwcommunity Private Read and Write Table 4-162. SNMP v1/v2c Default Communities info It’s possible to access SNMP v3 using default user, see table below: Authentication Authentication Private Private User Type Protocol Password Protocol...

  • Page 237: Initial Programming

    5. Initial Programming 5. Initial Programming The main goal of this chapter is to help in the programming and configuration of Nexto Series CPUs so that the user will be able to take the first steps before starting a controller programming. Nexto Series CPU uses the standard IEC 61131-3 for language programming, which are: IL, ST, LD, SFC and FBD, and besides these, an extra language, CFC.
  • Page 238 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 %QB01 %QX1.4 %QB01 %QX1.3 %QX1.2 %QX1.1 %QD00 %QX1.0 %QD00 %QW01 %QX2.7 %QX2.6 %QX2.5 %QX2.4 %QB02 %QB02...

  • Page 239: 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 the MasterTool IEC XE is a group of rules, common features and patterns used in an industrial automation solution development, a profile which implies in the application implementation form.

  • Page 240: Single

    5. Initial Programming Single In the Single Project Profile, the application has only one user task, MainTask. This task is responsible for the execution of a single Program type programming unit called MainPrg. This single program can call other programming unit, of the Program, Function or Function Block types, but the whole code will be executed exclusively by the MaisTask.

  • Page 241: Expert

    5. Initial Programming Furthermore, this profile can include event tasks with higher priority than the basic tasks, which can interrupt (preempt) these tasks execution at any time. The task called ExternInterruptTask00 is an event task of the External type which execution is triggered by some external event, such as the variation of a control signal on a serial port or the variation of a digital input on the NEXTO bus.

  • Page 242: Custom

    5. Initial Programming Custom The Custom project profile allows the developer to explore all the potential of the Runtime System implemented in the Nexto Series central processing units. No functionality is disabled; no priority, task and programs association or nomenclature are imposed. The only exception is for MainTask, which must always exist with this name in this Profile.

  • Page 243: General Table

    5. Initial Programming General Table Project Profiles Verifications Single Machine Basic Normal Expert Custom Total tasks Quantity [01..03] [01..32] [01..32] [01..32] Programs Quantity <n> <n> per Tasks Main Task Name Type Cyclic Cyclic Continuous Cyclic Cyclic <n> Priority <n> Quantity Time Name <n>...
  • Page 244 5. Initial Programming NX3004/NX3005 NX3010 NX3020 NX3030 Task Type Configuration Task (Task WHSB) Cyclic Cyclic Triggered by Event Triggered by External User Tasks Event Freewheeling Triggered by State NETs – Client or Server Instances Cyclic COM (n) – Master or Slave Instances Cyclic TOTAL Table 5-10.

  • Page 245: Cpu Configuration

    5. Initial Programming CPU Configuration The Nexto CPU configuration is based on the action of structuring the diagnostics area, the retentive and persistent memory area and hot swap mode, among other parameters. The user must double-click on the Nexto CPU, in the device tree, as shown on Figure 5-1, and configure the field as described in the CPU Configuration.

  • Page 246: 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, requesting to the user the possibility of changing the previous IP by the configured (Yes option) or No and quit sending the project.

  • Page 247: Modbus Rtu

    5. Initial Programming MODBUS RTU The first step for the MODBUS RTU configuring, in slave mode, is to include the instance in the desired COM (COM 1 in this case) by clicking with the right button on the COM and select “Add Device...”, as shown on Figure 5-4: Figure 5-4.

  • Page 248: Modbus Ethernet

    5. Initial Programming Figure 5-5. Selecting the Protocol MODBUS Ethernet 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 NX3010 has only one Ethernet interface). Click on the NET with the mouse right button and select “Add Device...”, as shown on Figure 5-6:...
  • Page 249 5. Initial Programming Figure 5-6. Adding the Instance After that, the available protocols for the user will appear on the screen. Define the protocol configuration mode selecting “MODBUS Symbol Client”, for symbolic mapping setting or “MODBUS Client”, for direct addressing (%Q) and click on Add Device, as depicted on Figure 5-7:...

  • Page 250: Server Iec 60870-5-104

    5. Initial Programming Figure 5-7. Selecting the Protocol Server IEC 60870-5-104 The first step to configure the IEC 60870-5-104 communication driver, in server mode, is to include the instance under the desired NET (CPU NX3030 owns two Ethernet interfaces, NET1 and NET 2). Click with the right button over the NET and select “Add Device…”, according the Figure 5-8:...
  • Page 251 5. Initial Programming Figure 5-8. Adding a Server IEC 60870-5-104 Instance After that, will show up the available protocols screen. In this case, select “IEC 60870-5-104 > IEC 60870-5-104 Server > IEC 60870-5-104 Server” and click on Add Device, according to Figure 5-9:...
  • Page 252 5. Initial Programming Figure 5-9. Selecting the Server IEC 60870-5-104 Protocol At last the user must click with the riht button over the inserted protocol Server IEC 60870-5-104 and insert one or more Clients, according to Figure 5-10:...

  • Page 253: Finding The Network

    5. Initial Programming Figure 5-10. Inserting a Client of Server IEC 60870-5-104 Protocol Finding the Network As there is the possibility of more CPUs being connected to the network, the user must find all communication units and select the desired one. Initially, the option Device must be accessed, in the device tree, double-clicking on it.
  • Page 254 5. Initial Programming Figure 5-11. Finding the CPU Following, the desired CPU must be selected and the option “Set active path” clicked, to activate the CPU and to inform the configuration software the CPU should communicate and send the project. Figure 5-12.

  • Page 255: Login

    5. Initial Programming If necessary, the user can change the default name of the device that is displayed. For that, you must click the right mouse button on the desired device and select "Change Node Name". After a name change, the device will not return to the default name under any circumstances. Login After the application has been compiled and the errors found corrected, the project must be sent to the CPU.

  • Page 256: Run Mode

    5. Initial Programming Figure 5-14. CPU Project Updating ATTENTION: In the online changes is not permitted to associate symbolic variables mapping from a global variable list (GVL) and use these variables in another global variable list (GVL). Figure 5-15 shows a message the MasterTool IEC XE shows when only changes in the application variables were done;...
  • Page 257 5. Initial Programming CPU. Besides, it allows initial values to be pre-configured, in order to turn possible the CPU updating on the first cycle. To select such functionality, the option “Start”, from the Debug menu, must be clicked, as shown on Figure 5-17.

  • Page 258: Stop Mode

    5. Initial Programming In case the CPU is initialized with an application already internally stored, it automatically goes to Run Mode, without the need for a MasterTool IEC XE command. Stop Mode For CPU execution interruption, without losing the connection with the MasterTool IEC XE software, the user must select the “Stop”...

  • Page 259: Logout

    5. Initial Programming The Table 5-11 exemplifies the medium execution time added to the MainTask with a number of forced variables: Active PLC Stand-by PLC Execution Time 50 ms 100 ms 200 ms 50 ms 100 ms 200 ms Increase with 10 forcings 2.4 % 2.2 % 1.7 %...
  • Page 260 5. Initial Programming Figure 5-21. Project Upload Option After, the desired CPU has to be selected and the OK button clicked as shown on Figure 5-22. To ensure that the project loaded in the CPU is identical and can be accessed in other workstations, consult the chapter Projects Download/Login Method without Project Differences at the MasterTool IEC XE User Manual MT8500 - MU299609.

  • Page 261: Cpu Operating States

    5. Initial Programming ATTENTION: The upload recovers the last project stored in the controller as described in the previous paragraphs. In case only the download for execution of a specific applicative occurs, it will not be possible to be recovered through upload. CPU Operating States When a CPU is in Run mode it indicates that all application tasks are in execution.

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

    5. Initial Programming Reset Process Command (IEC 60870-5-104) This process reset command can be solicited by IEC 60870-5-104 clients. After answer the client, the CPU start a rebooting process, as if being done an energizing cycle. In case of redundant PLCs , the process reset command is synchronized with the non active PLC, resulting the reboot of both PLCs.

  • Page 263: Gvl Ioqualities

    5. Initial Programming Requisition disabling variables declaration [Device Name]_DISABLE_[Requisition Number] : BOOL; Where: Device name: Name that shows on TreeView to the MODBUS device. Requisition Number: Requisition number tha was declared on the MODBUS device requisition table following the sequence from up to down, starting on 0001. Example: Device.Application.Disables VAR_GLOBAL...

  • Page 264: Gvl Module_Diagnostics

    5. Initial Programming arrays, and dimensions according to I/Os quantities of the module to which it belongs when that is added to the project. Example: Device.Application.IOQualities VAR_BLOBAL QUALITY_NX1001: ARRAY[0..15] OF LibDataTypes.QUALITY; QUALITY_NX2020: ARRAY[0..15] OF LibDataTypes.QUALITY; QUALITY_NX6000: ARRAY[0..7] OF LibDataTypes.QUALITY; QUALITY_NX6100: ARRAY[0..3] OF LibDataTypes.QUALITY;...

  • Page 265: Gvl Qualities

    5. Initial Programming Figure 5-24. Modules_Diagnostics GVL in Online Mode GVL Qualities In “Qualities” GVL, are declared the quality variable of the internal variables MODBUS Master/Client of symbolic mapping . It is not mandatory but is recommended to use these variables' automattic generation, what is done clicking on button “Generate Quality Variables”...
  • Page 266 5. Initial Programming [Device Name]_QUALITY_[Mapping Number]: LibDataTypes.QUALITY; Where: Device Name: Name that appear at the TreeView to the device. Mapping Number: Number of the mapping that was declared on the device mapping table, following the up to down sequence, starting with 0001. ATTENTION: It is not possible to associate quality variables to the direct representation MODBUS Master/Client drivers mappings.

  • Page 267: Gvl Reqdiagnostics

    5. Initial Programming Figure 5-25. Qualities GVL in Online Mode GVL ReqDiagnostics In “ReqDiagnostics” GVL, are declared the requisition diagnostics variables of symbolic mapping MODBUS Master/Client. It is nor mandatory, but recommended the use of these variables’ automatic generation, what is done by clicking in the button “Generate Diagnostic Variables” in device requisitions tab.
  • Page 268 5. Initial Programming [Device Name]_REQDG_[Requisition Number]: [Variable Type]; Where: Device Name: Name that appear at the TreeView to the device. Mapping Number: Number of the mapping that was declared on the device mapping table, following the up to down sequence, starting with 0001. Variable Type: Number “NXMODBUS_DIAGNOSTIC_STRUCTS.T_DIAG_MODBUS_RTU_MAPPING_1”...

  • Page 269: Gvl System_Diagnostics

    5. Initial Programming Figure 5-26. ReqDiagnostics GVL in Online Mode GVL System_Diagnostics In “System_Diagnostics” GVL, are declared the diagnostic variables of the CPU, of the communication interface (Ethernet and PROFIBUS) and of all communication drivers. This GVL isn’t editable and the variables are declared automatically with type specified by the device to which it belongs whne it is added to the project.
  • Page 270 5. Initial Programming Figure 5-27. System_Diagnostics GVL in Online Mode...

  • Page 271: Redundancy With Nx3030 Cpu

    6. Redundancy with NX3030 CPU 6. Redundancy with NX3030 CPU Introduction This chapter describes the Nexto Series CPUs redundancy which can only be used with the NX3030 CPU. Nexto’ s redundancy is of the hot-standby type, thus, the controllers are doubled. One controller is normally in active state and controlling a process, while the other is normally in stand-by state, keeping the synchronism with the active controller.
  • Page 272 6. Redundancy with NX3030 CPU SCADAs MasterTool Ethernet A Ethernet B Synchonism channel NETA Other CPUs (redundants Synchonism channel NETB or not) PX2612 cluster de CPs PLCA PLCB (half-cluster) (half-cluster) PROFIBUS 1 A PROFIBUS 1 B Non-redundant Ethernet Ethernet HSDN A Ethernet HSDN B Other HSDN CPUs...

  • Page 273: Technical Description And Configuration

    6. Redundancy with NX3030 CPU Technical Description and Configuration Minimum Configuration of a Redundant CPU (Not Using PX2612 Panel) A redundant CPU is composed, at least, by:  Two identical half-clusters Each half-cluster consists of at least the following modules: ...

  • Page 274: Nx4010 Module

    6. Redundancy with NX3030 CPU  Ethernet Interfaces NX5000 In case is necessary, bigger racks can be used, as the NX9002 (16 positions) and NX9003 (24 positions). It must be observed that all the listed modules, so far in this chapter, have double width (occupy two positions).

  • Page 275: Redundancy Control Panel Px2612

    6. Redundancy with NX3030 CPU Figure 6-3. NX4010 Module NX4010 Features Its main features are:  Data and application synchronization between two half-clusters;  Redundant communication interface between two half-clusters;  Automatic switchover (active half-cluster change) in case of NX4010 and CPU communication time out;...
  • Page 276 6. Redundancy with NX3030 CPU  RL A: 2 terminals connected to a relay NO (normally open) contacts, which can be commanded by PLCB to switch off PLCA. This relay must be closed by PLCB in order to switch off PLCA; ...

  • Page 277: Interconnections Between Half-Clusters And The Redundancy Control Panel Px2612

    6. Redundancy with NX3030 CPU Interconnections between Half-Clusters and the Redundancy Control Panel PX2612 Figure 6-6 shows how the connections between PLCA, PLCB and PX2612 have to be made, including the possibility to allow a CPU to switch off the other, which is necessary in exceptional situations.

  • Page 278: General Features

    6. Redundancy with NX3030 CPU General Features Redundant CPU General Features Allowed CPUs NX3030 Redundancy types Hot-standby Tolerates, at least, simple failures in doubled equipment in the Failure tolerances half-clusters. In specific cases, it can tolerate multiple failures. - Not-configured: initial state, also considered when the CPU is off or isn’t executing the MainTask;...
  • Page 279 6. Redundancy with NX3030 CPU - Through buttons, allows commands of switchover or redundancy states transition for maintenance; - LEDs signalize the redundancy state in each half-cluster; Redundancy Control Panel PX2612 - NO relay allows a half-cluster to switch off the other in extreme situations.

  • Page 280: Purchase Data

    6. Redundancy with NX3030 CPU This way, redundant Ethernet network can be built easily, without the need for the clients, connected to a NIC Teaming, to implement complex scripts to switch IP addresses. The CPU supports 2 PROFIBUS networks, each one may be redundant or not.

  • Page 281: Principles Of Operation

    6. Redundancy with NX3030 CPU Principles of Operation In this section, the redundant CPU functions using a NX3030 CPU is described, along with its behavior and states. It’s also presented concepts and programming and configuration restrictions that will be used in the next chapters. NX3030 CPU Identification A NX3030 CPU has a nonvolatile identification register where it’s possible for it to be identified as: ...
  • Page 282 6. Redundancy with NX3030 CPU fbRedundancyManagement(); NonSkippedPrg(); IF fbRedundancyManagement.m_fbDiagnosticsLocal.eRedState = REDUNDANCY_STATE.ACTIVE THEN ActivePrg(); END_IF MainPrg call two POUs from the program type, called NonSkippedPrg and ActivePrg. NonSkippedPrg is always called, as it’s executed in both CPUs. On the other hand, ActivePrg is only called when the “RedDgnLoc.RedState = Active”...
  • Page 283 6. Redundancy with NX3030 CPU cycle, through the synchronism channels NETA and NETB. On the other hand, non-redundant variables aren’t copied between half-clusters, thus can have different values in PLCA and PLCB. The non-redundant variables are used to store private information of each half-cluster (PLCA or PLCB), such as module diagnostics inside the half-cluster, including the redundancy diagnostics (half-cluster diagnostics state, etc.).
  • Page 284 6. Redundancy with NX3030 CPU Redundant and Non-redundant %Q Variables The NX3030 CPU allocates 96kbytes of %Q variables (%QB0 ... %QB98303). The first 80 Kbytes can be redundant (%QB0 ... %QB81919). The last 16kbytes are always non- redundant (%QB81920 ... %QB98303). The 80 Kbytes area which can be redundant is divided in two sections: ...
  • Page 285 6. Redundancy with NX3030 CPU RQS kbytes %Q redundant RQS = 0 ... 65535 outputs RQS default = 16384 65 kbytes Reservado for redundant %Q output 65536 - RQS expansion 96 kbytes RQD kbytes Redundant RQD = RQS ... 81919 RQD default = 16384 diagnostics 80 kbytes...

  • Page 286: Multiple Mapping

    6. Redundancy with NX3030 CPU  When declared in the NonSkippedPrg program. This program has been described previously in the NonSkippedPrg section.  When declared in POUs from the “function” type. It can be observed this POUs normally must allocate variables only on the pile (non static), which consequently don’t need to be redundant. If the user declares static variables (VAR STATIC) inside the POUs from the “function”...

  • Page 287: Diagnostics, Commands And User Data Structure

    6. Redundancy with NX3030 CPU Above there’s an example in ST language, where the redundancy command can be executed through two variables from different communication ports. On the same example, three different commands were executed (StandBy, Inactive and Turn-on). Where: var_StandBy_ command_Ethernet_relation: Bool type variable attributed to an Ethernet communication Coil which will execute the command to put the local Half-Cluster in Stand-By.

  • Page 288: Cyclic Synchronization Services Through Neta And Netb

    6. Redundancy with NX3030 CPU  User Information Exchanged between PLCA and PLCB Cyclic Synchronization Services through NETA and NETB This section describes the three synchronization services which occur cyclically in a redundant CPU between PLCA and PLCB, through NETA and NETB synchronism channels. These services are executed at the beginning of each MainTask cycle, and in the sequence which they appear below: ...

  • Page 289: Sporadic Synchronization Services Through Neta And Netb

    6. Redundancy with NX3030 CPU Redundant Forcing List Synchronization This service is responsible for the redundant forcing list transferring, from the Active CPU to the Inactive CPU. For this service to be executed, several conditions must be satisfied:  Both synchronization services previous to this cycle (Diagnostics and Commands Exchange) must be completed with success;...

  • Page 290: Project Synchronization Disabling

    6. Redundancy with NX3030 CPU Besides keeping the projects synchronized, the Project Synchronization will also avoid the Non- Active CPU to assume superior states in relation to Starting in case the CRC is different or some Online Change is to be executed in the Active CPU. ATTENTION: A project synchronization will have the same effect as a download in the Non-Active CPU.

  • Page 291: Profibus Network Configuration

    6. Redundancy with NX3030 CPU To disable the Project synchronization, the user must, firstly, connect into desired PLC with the software MasterTool (see chapter MasterTool Connection with a NX3030 CPU from a Redundant PLC). Next, in the Online / Cluster Basic Configuration menu, the combo-box “Project Synchronization” must be opened, allowing the selection of the two following options: ...

  • Page 292: Redundant Ethernet Networks With Nic Teaming

    6. Redundancy with NX3030 CPU  PO5065: PROFIBUS slave DP-V1 with Hart, for Ponto Series remotes;  AL-3416: PROFIBUS slave DP-V0 for AL-2004 CPU.  NX5210: PROFIBUS slave DP-V0 for Nexto Series remotes. Figure 6-1 also shows the possibility to connect non-redundant remotes to this type of redundant PROFIBUS network, through the AL-2433 module (ProfiSwitch).
  • Page 293 6. Redundancy with NX3030 CPU Overall, it can be listed up to four IPs, according to the IP change method. Fixed IP It’s the simplest method for IP addressing and can be configured in the Ethernet interfaces in the NX5000 Ethernet modules. In this method, it’s only listed the IP addresses from the PLCA and from PLCB.
  • Page 294 6. Redundancy with NX3030 CPU Parameters that must be configured in the Exchange IP method:  IP Address Active: PLCA communication address  IP Address Non Active: PLCB communication address  Subnetwork Mask  Gateway Address Active IP This method is used in the redundant NX3030 CPU NETs and is also possible to be configured in the NX5000 modules.
  • Page 295 6. Redundancy with NX3030 CPU Figure 6-12. Active IP method – NX5000 Parameters that must be configured in the Active IP method for the NX5000 Ethernet modules:  IP Address Active: Active PLC communication address. Replaces the IP address from the Non- Active PLCX;...

  • Page 296: Nic Teaming And Active Ip Combined Use

    6. Redundancy with NX3030 CPU Parameters that must be configured in the Multiple IP method:  IP Address PLC A Active: PLCA communication address, when in Active state.  IP Address PLC A Non Active: PLCA communication address, when in Non-Active state. ...

  • Page 297: Opc Communication Use With Redundant Projects

    6. Redundancy with NX3030 CPU Failure in Connected MODBUS Server The time to detect the fault in a remote MODBUS Server depends on the time-out settings configured on each MODBUS Client. When a fault is detected in all Servers, the bAllDevicesCommFailure diagnostic (see Modbus Diagnostics used at Redundancy section used in) changes its state to TRUE.
  • Page 298 6. Redundancy with NX3030 CPU Sometimes, the CPU goes to Not-Configured state when has already received an automatic configuration request, when the new request for Starting state changing is not necessary. This happens at the CPU energizing, for instance. In other situations, the user must request manually this configuration, e.g. pressing a button on the PX2612 redundancy command panel.

  • Page 299: Px2612 Redundancy Command Panel Functions

    6. Redundancy with NX3030 CPU Stand-By State In this state the CPU is ready to be switched to the Active state, in case there’s a request for that, as a failure in the Active CPU. The Stand-by CPU also verifies its own diagnostics and can be switched to the Not-Configured or Inactive state, in case some failures occur.
  • Page 300 6. Redundancy with NX3030 CPU PX2612 Buttons This section describes the functions of the PX2612 buttons. The STAND-BY button has the following functions:  To request a switching from the Active state to the Stand-by state, useful when maintenance in the Active CPU is needed.

  • Page 301: Transition Between Redundancy States

    6. Redundancy with NX3030 CPU Each LED can be off, on or blinking. In case it’s blinking, it remains on for 0.5 seconds and off for the same time. Note that there are four different animations for the Active state, due to the following features: ...
  • Page 302 6. Redundancy with NX3030 CPU  Transitions can only be triggered if the CPU is on and the MainTask is executing. Otherwise the CPU is assumed to be in the Not-Configured state  In several cases, transitions caused by the PX2612 panel buttons are mentioned. It must be recalled there are alternatives for these buttons, which are internal commands from one CPU or the other (via NETA / NETB).
  • Page 303 6. Redundancy with NX3030 CPU Transition 4 – Starting to Active  The other CPU is in Non-Active state. Before the transition is possible, this condition must remain true for some time, higher to PLCB than PLCA. This way, at the moment PLCA and PLCB are simultaneously turned on;...

  • Page 304: First Instants In Active State

    6. Redundancy with NX3030 CPU Starting state. This condition isn’t analyzed if the project automatic synchronization is disabled ( Project Synchronization Disabling section)  The other PLC is in Active state and firmware version of this PLC is incompatible with the firmware version of the Active PLC Transition 11 –...

  • Page 305: Failures Associated To Switchovers Between Half-Clusters Managed By The User

    6. Redundancy with NX3030 CPU  NX8000 power supply fault in the Active CPU  Rack bus failure (NX9001, NX9002 or NX9003) in the Active CPU  Failures in the NX3030 CPU from the Active CPU, such as: o Watchdog o Restart (reset warm, cold or origin) o Stop o Failure in the bus interfaces in one or both synchronization channels NETA and NETB...

  • Page 306: Fault Tolerance

    6. Redundancy with NX3030 CPU IF (DG_NX3030.tDetailed.Ethernet.NET1.bLinkDown AND DG_NX3030.tDetailed.Ethernet.NET2.bLinkDown) THEN //Change the local PLC to StandBy. DG_NX4010.tRedundancy.RedCmdLoc.bStandbyLocal := TRUE; END_IF ELSE //NIC Teaming disabled: error in one of NETs to execute a switchover. IF (DG_NX3030.tDetailed.Ethernet.NET1.bLinkDown OR DG_NX3030.tDetailed.Ethernet.NET2.bLinkDown) THEN //Change the local PLC to StandBy. DG_NX4010.tRedundancy.RedCmdLoc.bStandbyLocal := TRUE;...
  • Page 307 6. Redundancy with NX3030 CPU situations, such as process programmed maintenance, are used for that purpose. The higher the period between off-line testes, the higher the time which the failure may remain hidden, and the higher the probability of a failure to damage the system, in other words, the smaller the availability These principles were considered in the redundant CPU project using NX3030.

  • Page 308: Redundancy Overhead

    6. Redundancy with NX3030 CPU  NX5001 modules (PROFIBUS masters) in redundant configuration, configured in vital failure mode.  NX5000 modules (Ethernet) in configurations with NIC Teaming (redundancy managed by the user). Redundancy Overhead A redundant application implies on an application processing time increase, when compared to the necessary time for a non-redundant equivalent application.
  • Page 309 6. Redundancy with NX3030 CPU Figure 6-15. New Project Next, the Wizard which generates the redundancy project run some questions for the user, regarding the desired configuration that must be answered successively. The first point to be defined is the initial configuration for the half-cluster hardware: ...
  • Page 310 6. Redundancy with NX3030 CPU Figure 6-16. Hardware initial configuration After, the user must define the communication networks used in the redundant application:  Select the number of PROFIBUS networks: By the Wizard, can be created up to four PROFIBUS networks, and they can be single or redundant.
  • Page 311 6. Redundancy with NX3030 CPU Figure 6-17. Communication networks configuration Then the project profile and the standard language must be selected for the program creation:  Select the project profile: It’s only possible to use the simple project profile for the redundancy; hence the selection option is disabled ...
  • Page 312 6. Redundancy with NX3030 CPU Figure 6-19. Specific programs language ATTENTION: The ActivePrg and NonSkippedPrg POUs are created automatically, empty, in language selected on the previous questions. Other POUs which are created manually by the user can be used in any available language, except in redundant POUs which can’t be written in SFC language as it uses the IEC timer as background.

  • Page 313: Half-Clusters Configuration

    6. Redundancy with NX3030 CPU Half-Clusters Configuration The Wizard is always used to generate the first version of a redundant project. This guarantees the initial version is generated quick and correctly. However, it’s possible that some modifications are necessary in a half-cluster, such as the insertion of new NX5001 and NX5000 modules that can be executed changing the half-cluster configuration screen.
  • Page 314 6. Redundancy with NX3030 CPU ATTENTION: The NET 2 configuration screen has the same structure as the NET 1 configuration screen, but it doesn’t have the checkbox “Redundancy”, neither the NIC Teaming configuration parameters. NIC Teaming between NET 1 and NET 2 The advanced option on the NET 1 configuration screen opens a new configuration screen, which defines if NET 1 will be redundant.

  • Page 315: Nx5001 Modules Configuration

    6. Redundancy with NX3030 CPU When configured in conjunction with the NIC Teaming redundancy, failure is considered vital failure, when a fault occurs in NET1 and NET2 interfaces. NX5001 Modules Configuration Insertion or Removal of NX5001 modules NX5001 modules can be inserted or removed from the half-cluster rack. To execute this operation correctly, one must be aware of the following rules: ...
  • Page 316 6. Redundancy with NX3030 CPU Figure 6-22. NX5001 redundancy parameters For grouping two NX5001 modules in a redundant PROFIBUS network, a double click must be executed on an ungrouped NX5001 module which has another ungrouped NX5001 module at its right in the rack. Next the parameter “Network Redundancy”, available at the tab “Module Parameters”, must be marked as TRUE, as shown on the Figure 6-22.

  • Page 317: Nx5000 Modules Configuration

    6. Redundancy with NX3030 CPU Thus, a command run by the user to disable an interface will not run the way it’s expected. For example, if an interface has the status of this bit changed from TRUE to FALSE on an active CPU, this will not be interpreted as a failure that would take the CPU Active for the Inactive state.

  • Page 318: Nx4010 Redundancy Configuration

    6. Redundancy with NX3030 CPU NX5000 Modules Configuration For each NX5000 module in a redundant PLC, the address parameters must be adjusted as described in the IP Change Methods section, which can be accessed through a double click on the NET 1 interface, below each NX5000 module placed on the devices tree.

  • Page 319: I/O Drivers Configuration

    6. Redundancy with NX3030 CPU Redundancy %Q %Q redundant memory memory offset offset reserved for 65536 0 to 81919 reserved for diagnostics initial diagnostics address Redundancy %Q %Q redundant memory memory length offset reserved for 16384 0 to 81920 reserved for diagnostics size diagnostics Table 6-3.
  • Page 320 6. Redundancy with NX3030 CPU After each compilation, MasterTool sums the redundancy overhead calculated with the parameter which informs the POU times (NonSkippedPrg and ActivePrg), and verifies is the minimum looseness parameterized is being obeyed. E.g.:  Parameters configured in the MainTask screen: o MainTask cycle time: 100 ms o POUs NonSkippedPrg + ActivePrg estimated time: 10 ms o Minimum tolerance: 30%...

  • Page 321: Redundancy Configuration Object

    6. Redundancy with NX3030 CPU ATTENTION: It must be avoided to call additional POUs from the program type inside the NonSkippedPrg, as symbolic variables declared in this type of POU are redundant, and inside the NonSkippedPrg it’s normally desirable non-redundant variables. Usually the NonSkippedPrg code is small and doesn’t need to call additional POUs from the program type for its structure.

  • Page 322: Pous From The Program Type With Redundant Symbolic Variables

    6. Redundancy with NX3030 CPU POUs from the Program Type with Redundant Symbolic Variables The user can declare redundant symbolic variables in POUs from the program type, with exception of the NonSkippedPrg POU where the symbolic variables declared are considered redundant. In order to define a new POU as redundant, it must be marked in the Redundancy Configuration object after its creation, in the project devices tree.

  • Page 323: Getting The Redundancy State Of A Half-Cluster

    6. Redundancy with NX3030 CPU  Do not mix symbolic variables declaration with ATs in the GVLs. Separate GVLs must be created where in one the AT variables will be declared and in another, the symbolic variables  Do not store a variable address in a redundant variable (use a redundant variable as a pointer), as the variable addresses may be different in the PLCA and PLCB ...

  • Page 324: Redundant Cpu Program Downloading

    6. Redundancy with NX3030 CPU //Actions executed when the diagnostics are active END_IF END_IF Redundant CPU Program Downloading The Redundant CPU Programming section described issues related to the development of a project for a redundant CPU with NX3030 CPU. In this section, many methods and steps to download this project in a redundant CPU are described, considering situations such as: ...
  • Page 325 6. Redundancy with NX3030 CPU details the possible identifications which can be observed on this list. Anyhow, all possible identification has a field showing the IP address or part of it. For instance, the bytes between square brackets form the CPU address. The right byte inside the brackets, indicate the IP address end in hexadecimal.

  • Page 326: Mastertool Connection With A Nx3030 Cpu From A Redundant Plc

    6. Redundancy with NX3030 CPU The CPU identification isn’t part of the redundant project developed with MasterTool. Such identification is only in a CPU non-volatile memory area, which can be modified using MasterTool. CAUTION: The redundancy doesn’t work properly in case one of the CPUs isn’t identified as PLCA and the other PLCB, when a process control interruption may occur.

  • Page 327: Modification Download In A Redundant Project

    6. Redundancy with NX3030 CPU On this list it’s possible to find the following standard identifications, in case the PLC name on the network hasn’t been changed previously by the user:  NX3030_<IP address>_PLCA: identification related to the PLCA. In this case, the field <IP address>...

  • Page 328: On-Line Download Of Modifications

    6. Redundancy with NX3030 CPU Modifications which Demand Off-Line Download and the Interruption of the Process Control The following modifications in a project will make it impossible to be downloaded in a redundant system with no interruption of the process control: ...

  • Page 329: Off-Line Download Of Modifications With Process Control Interruption

    6. Redundancy with NX3030 CPU could be synchronized. From version 2.01 this operation is no longer needed. After sending the application the send operation for nonvolatile memory is performed automatically. ATTENTION: It’s important to remember that online modifications, without the option mentioned previously selected, will be lost in case of a hot reset or a CPU switch off.

  • Page 330: Previous Planning For Off-Line Modifications Without Process Control Interruption

    6. Redundancy with NX3030 CPU ATTENTION: When the Active PLC goes out from the Run mode and goes to Not-Configured, if the other PLC was forgotten in Stand-by state, it takes over as Active and switches off the PLC which has just gone from Active to Not-Configured.
  • Page 331 6. Redundancy with NX3030 CPU ATTENTION: At the physical construction of these remotes (electric panels), it’s strongly recommended to insert compatible bases with the future I/O modules in the respective positions. This way, when the I/O module insertion is necessary in this remote, there’s no need for switching off the remote to insert the base.
  • Page 332 6. Redundancy with NX3030 CPU Step 3 – Allocate %I and %Q Variables Areas for the PROFIBUS Network considering Future Remote Expansion As the NX5001, remotes and I/O modules were being inserted in the device tree in the previous step, %I and %Q variables were being allocated in three different areas: ...
  • Page 333 6. Redundancy with NX3030 CPU At first, the parameter “ %Q Initial Address of Module Diagnostics Area” must be modified in the first NX5001 module, as shown on the table on the next figure. The planned initial address must be used for the diagnostic %Q variables area.
  • Page 334 6. Redundancy with NX3030 CPU into the group of Modifications which Allow On-Line Download, is possible to do an On-Line Download of Modifications with no generation of incompatibility of applications between the PLCs. Project Update due to MasterTool IEC XE Update The MasterTool IEC XE programming tool is under a constant enhancement process, improving its features and adding new ones.

  • Page 335: Exploring The Redundancy For Off-Line Downloading Of Modifications Without Interruption Of The Process Control

    6. Redundancy with NX3030 CPU  After this, the Half-Cluster that was in Stand-by will pass to Non-Configured and will receive the Project from the Half-Cluster in Active state. By the end of this process the Half-Cluster state will change to Starting and then back to Stand-by. Exploring the Redundancy for Off-Line downloading of Modifications without Interruption of the Process control In the Off-Line and On-Line Modifications Download section, it was informed that some...
  • Page 336 6. Redundancy with NX3030 CPU The modifications that must be loaded off-line, and supported by this procedure do not affect the structure of redundant variables. However, some modifications which can be loaded on-line can change the structure of redundant variables, e.g.: ...
  • Page 337 6. Redundancy with NX3030 CPU  Install a new NX5000 module. This can be done through a module hot-insertion in each half- cluster rack, then connecting it to the Ethernet network  Install a new redundant PROFIBUS network. The NX5001 can be hot-inserted in each half- cluster rack.
  • Page 338 6. Redundancy with NX3030 CPU Step 10 – Projects Synchronism Enabling in the Active PLC In the step 5, the project synchronism was disabled in the Non-Active PLC. It can be observed this PLC is now in Active state. In this step, the project synchronism must be enabled again in this PLC. The screen and methodology used for it were described in the section Project Synchronization Disabling.

  • Page 339: Maintenance

    6. Redundancy with NX3030 CPU Maintenance Modules Hot Swapping in a Redundant PLC In case of failure in a module from one of the PLCs (PLCA and PLCB), the module hot swapping may be necessary, without interrupt the process control. For that, the following steps must be followed: ...

  • Page 340: Redundancy Diagnostics On The Nx3030 Cpu Graphic Display

    6. Redundancy with NX3030 CPU  For downloading off-line a different project in the Non-Active PLC, as described in the Exploring the Redundancy for Off-Line downloading of Modifications without Interruption of the Process control section  For monitoring or forcing the non-redundant variables in the Non-Active PLC Redundancy Diagnostics on the NX3030 CPU Graphic Display Many diagnostics related to redundancy can be observed on the NX3030 CPU display.
  • Page 341 TRUE – the configuration process, executed in the Not-Configured state, has finished with errors. It’s a system error, normally not expected. Get in contact with ALTUS support to report it. bConfigError Also inform the ConfigErrorCode diagnostic value for the ALTUS support.
  • Page 342 6. Redundancy with NX3030 CPU Direct Representation AT variable Variable DG_NX4010.tRedundancy.R Description edDgnLoc.sGeneral_Diag.* Variable successfully in this MainTask cycle. FALSE – The RedDgnRem structure has obsolete or invalid values, as it wasn’t read from the other PLC (remote) in this cycle. TRUE –...
  • Page 343 6. Redundancy with NX3030 CPU Direct Representation AT variable Variable DG_NX4010.tRedundancy.R Description edDgnLoc.sGeneral_Diag.* Variable application or these have been synchronized already with the stand-by PLC. TRUE – Failure in the NX4010 module. The NX3030 CPU can’t communicate with this module through bus, or there’s a failure in the bFailedRED NX4010 microprocessor.
  • Page 344 6. Redundancy with NX3030 CPU Direct Representation AT variable Variable DG_NX4010.tRedundancy.R Description edDgnLoc.sGeneral_Diag.* Variable TRUE – this PLC can’t communicate in the master state (active or passive) in the PROFIBUS 2 network. In case the PROFIBUS 2 network is redundant, FailurePROFIBUS_2 results from a AND logic between FailedPBUS2A and FailedPBUS2B.
  • Page 345 6. Redundancy with NX3030 CPU Direct Representation AT variable Variable DG_NX4010.tRedundancy.R Description edDgnLoc.sGeneral_Diag.* Variable MasterTool command used to write on this non- volatile variable is described. informs the redundancy state of this PLC: - Not-Configured = 0 - Starting = 2 %QB(n+9) eRedState - Stand-by = 3...
  • Page 346 6. Redundancy with NX3030 CPU the correct value because they depend on the correct functioning of the communication between the two CPUs, so that information can be correctly generated. The “sNETA_Diag” substructure has the following fields for NETA synchronism channels diagnostics: Direct Representation AT Variable...
  • Page 347 6. Redundancy with NX3030 CPU Table 6-8. NETB Interface Specific Diagnostics The “sNET_Stat” substructure has service success and failure statistics. The local and remote PLCs statistics can be restarted through commands: //Local PLC DG_NX4010.tRedundancy.RedCmdLoc.bResetNETStatisticsLocal := TRUE; //Remote PLC DG_NX4010.tRedundancy.RedCmdLoc.bResetNETStatisticsRemote := TRUE; The substructure has the following counters: Direct AT Variable...
  • Page 348 6. Redundancy with NX3030 CPU TRUE – This PLC can’t communicate in the master state (active or passive) in the PROFIBUS 3 network. In case the PROFIBUS 3 network is redundant, FailurePROFIBUS_3 results from a AND logic between FailedPBUS1A and bFailureProfibus_3 FailedPBUS3B.
  • Page 349 6. Redundancy with NX3030 CPU FALSE – Keep Alive packets aren’t being received. TRUE – THE NX3030 CPU is receiving Keep Alive packets from the other half- cluster’s CPU, through NET 2. bRemCpuKeepAliveNet2 FALSE – Keep Alive packets aren’t being received.
  • Page 350 6. Redundancy with NX3030 CPU ATTENTION: There are two command bits which normally must be turned off by the user: DG_NX4010.tRedundancy.RedCmdLoc.bTestModeLocal and _NX4010.tRedundancy. RedCmdLoc.bTestRelayLocal. Further details regarding these commands are described ahead in this section. In case the user forgets to turn them off, there are automatic mechanisms which are supposed to do it instead.
  • Page 351 6. Redundancy with NX3030 CPU Direct Representation AT variable Variable DG_NX4010.tRedundancy.Re Description dCmdLoc.* Variable activated. TRUE – This command puts the PX2612 panel in test mode, allowing its components to be tested (LEDs, relays and buttons), as explained in PX2612 Panel Test section. The PX2612 test mode is only accepted when this bit is on both PLCs.
  • Page 352 6. Redundancy with NX3030 CPU  Redundancy Diagnostics (RedDgnLoc and RedDgnRem), already described in the Redundancy Diagnostics Structure section  Redundancy Commands (RedCmdLoc and RedCmdRem), already described in the Redundancy Commands section  User Information Exchanged between PLCA and PLCB (RedUsrLoc and RedUsrRem), which are described in this section The RedUsrLoc and RedUsrRem structures are simply a 128 bytes array, which utilization can be freely defined by the user.

  • Page 353: Px2612 Panel Test

    6. Redundancy with NX3030 CPU ATTENTION: Some diagnostics may point to possible failures during the redundant system initialization and in the tasks first cycles. But in a correct system function these diagnostics no longer indicate errors right after the system initialization. PX2612 Panel Test The PX2612 panel is composed by buttons, LEDs and relays.
  • Page 354 6. Redundancy with NX3030 CPU It can be observed that normally the LED is on the pressed button side, except for the TURN ON PLCx. Before the LED remains on, it’s necessary to hold the button for, at least, 1 second. The LED returns to blinking after it’s released.

  • Page 355: Maintenance

    7. Maintenance 7. Maintenance Module Diagnostics One feature of the Nexto Series is the abnormality diagnostic generation, whether they are failures, errors or operation modes, allowing the operator to identify and solve problems which occurs in the system easily. The Nexto CPUs permit many ways to visualize the diagnostics generated by the system, which are: ...
  • Page 356 7. Maintenance Figure 7-1. Diagnostic Switch With only a short touch, the CPU starts to show the bus diagnostics (when active, otherwise shows the “NO DIAG” message). Initially, the Tag is visualized (configured in the module properties in the MasterTool IEC XE software, following the IEC 61131-3 standard), in other words, the name attributed to the CPU, and after that all diagnostics are shown, through CPU display messages.
  • Page 357 7. Maintenance Figure 7-2. CPU Diagnostics Visualization Before all visualization process be concluded, it is just to give a short touch on the diagnostic switch, at any moment, or press the diagnostic switch from any I/O module connected to the bus. In case a long touch is executed, the CPU goes to navigation menu, which is described in the CPU’s Informative and Configuration Menu chapter.

  • Page 358: Diagnostics Via Led

    7. Maintenance will indicate that there is a module with active diagnostics. To remove this diagnostic from the CPU, a hot swap must be done in the module where the diagnostic is active.. For further details on the procedure for viewing the diagnostics of the CPU or other bus modules, see description in the User Manual Nexto Series - MU214000.

  • Page 359: Diagnostics Via Web

    7. Maintenance RJ45 Connector LEDs Both LEDs placed in the RJ45 connectors (in case of NX3010, only one connector), identified by NET 1 and NET 2, help the user in the installed physical network problem detection, indicating the network LINK speed and the existence of interface communication traffic. The LEDs meaning is presented on Table 7-4.
  • Page 360 7. Maintenance There is also the “System Information” tab, which can be visualized through the Rack or the present module list (option on the screen right side). While there is no application on the CPU, this page will display a configuration with the largest available rack and a standard power supply, connected with the CPU.

  • Page 361: Diagnostic Explorer

    Updating tab is restricted to the user, in other words, it is for Altus internal use only. Firmware Update tab is restricted to the user, that is, only for internal use of Altus. In cases where the update is performed remotely (via a radio or satellite connection for example, the minimum speed of the link must be 128Kbps).

  • Page 362: Diagnostics Via Variables

    7. Maintenance  Right - clicking on the module and selecting “Diagnostic”, the Diagnostic Explorer is opened, directing for the module status page Diagnostics via Variables The Nexto Series CPUs have many variables for diagnostic indication. There are data structures with the diagnostics of all modules declared on the bus, mapped on the variables of direct representation %Q, and defined symbolically through the AT directive, in the GVL Diagnostics created automatically by the MasterTool IEC XE.
  • Page 363 7. Maintenance Direct Representation Diagnostics DG_Modulo.tSummarized. Variable Description Message * AT Variable Variable FALSE – The hardware is working properly. TRUE – One or more exceptions SOFTWARE bSoftwareException EXCEPTION generated by the software. FALSE – No exceptions generated in the software. bReserved_10 Reserved TRUE –...
  • Page 364 Otherwise, the problem is treated as “Incompatible Configuration”. 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.
  • Page 365 7. Maintenance Ethernet Interfaces: The diagnostics regarding to the NET 2 interface are only available for the NX3020 and NX3030 CPUs. Detailed Diagnostics The tables below contain Nexto Series’ CPUs detailed diagnostics. It is important to have in mind the observations below before consulting them: ...
  • Page 366 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 Exception. Exception code generated by the %QW(n+21) WORD wExceptionCode RTS. See Table 7-29. Exception. Level, in percentage (%), of %QB(n+23) BYTE byProcessorLoad charge in the processor. Table 7-9.
  • Page 367 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 CPU Startup status: 01: Hot start RetainInfo. 02: Warm Start %QB(n+25) BYTE byCPUInitStatus 03: Cold Start PS.: These variables are restarted in all startup. Counter of cold startups: It will be added only due hot RetainInfo.
  • Page 368 7. Maintenance Note: Temperature: In order to see the temperature directly in the memory address, a conversion must be made, since the data size is DINT and monitoring is done in 4 bytes. Therefore, it’s recommended to use the associated symbolic variable, because it already provides the final temperature value. CPU Direct Representation Variable DG_Modulo.tDetailed.* Size...
  • Page 369 7. Maintenance 65535) Number of characters left in the Serial.COM2. %QW(n+78) WORD transmission buffer in COM 2. (0 wTXPendingBytes to 65535) Serial.COM2. These counters are restarted in %QW(n+80) WORD wBreakErrorCounter the following conditions: - Startup Serial.COM2. %QW(n+82) WORD wParityErrorCounter - Configuration of COM 2 serial port Serial.COM2.
  • Page 370 7. Maintenance Ethernet.NET1. Counter of sent packages through %QD(n+179) DWORD dwPacketsSent NET 1 port. (0 to 4294967295) Counter of received packages Ethernet.NET1. %QD(n+183) DWORD through NET 1 port. (0 to dwPacketsReceived 4294967295) Ethernet.NET1. Counter of sent bytes through %QD(n+187) DWORD dwBytesSent NET 1 port.
  • Page 371 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 (15) szMask STRING Ethernet.NET2. %QB(n+254) NET 2 Gateway Address (15) szGateway STRING Ethernet.NET2. %QB(n+270) NET 2 MAC Address (17) szMAC BYTE Ethernet.NET2. %QB(n+288) IP NET 2 Address ARRAY(4) abyIP BYTE...
  • Page 372 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 Indicates if the memory used for UserFiles. %QB(n+219) %QB(n+346) BYTE recording user files is able to byMounted receive data. UserFiles. Free memory space for user files %QD(n+220) %QD(n+347) DWORD...
  • Page 373 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 Identification of errors in I/O modules, individually: The 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 374 7. Maintenance Situations in which the Application Stops: The codes for the possible situations in which the application stop can be consulted below: Code Enumerable Description INITIALIZING This state is presented while other states are not ready. Application in Stop Mode due to hardware watchdog reset or runtime reset, when the option “Start User Application After a Watchdog Reset”...
  • Page 375 7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 SNTP. %QX(n+532).0 %QX(n+633).0 SNTP Service enabled. bServiceEnabled Indicates which server is active: 00: None active server. SNTP. %QB(n+533) %QB(n+634) BYTE byActiveTimeServer 01: Active Primary Server. 02: Active Secondary Server.

  • Page 376: Diagnostics Via Function Blocks

    7. Maintenance CPU Direct Representation Variable DG_Modulo.tDetailed.* Size Description AT Variable NX3004 NX3005 NX3010 NX3020 NX3030 Queue status of client events 02 SOE[2]. FALSE – There was no overflow %QX(n+663).1 bOverflowStatus TRUE – Exceeded queue limit SOE[2]. %QB(n+664) BYTE Reserved byReserved_0 SOE[2].
  • Page 377 7. Maintenance GetTaskInfo This function returns the task information of a specific application. Figure 7-8. GetTaskInfo Function Below, the parameters that must be sent to the function for it to return the application information are described. Input parameter Type Description psAppName POINTER TO STRING Application name...

  • Page 378: Graphic Display

    7. Maintenance Graphic Display The graphic display available in the Nexto Series CPUs is an important tool for the process control, as through it is possible to recognize possible error conditions, active components or diagnostics presence. Besides, all diagnostics including the I/O modules are presented to the user through the graphic display.
  • Page 379 MSG. ERROR the requested module (s) Indicates the product presented an unexpected problem. Get in SIGNATURE MISSING contact with Altus Technical Support sector Indicates that occurred an error in the application and the APP. ERROR RESTARTING Runtime is restarting the application.

  • Page 380: System Log

    7. Maintenance System Log The System Log is an available feature in the MasterTool IEC XE programmer. It is an important tool for process control, as it makes it possible to find events on CPU that may indicate error conditions, presence of active components or active diagnostics. Such events can be viewed in chronological order with a resolution of milliseconds, with a storage capacity of up to one thousand log entries stored in the CPU internal memory, that can’t be removed.

  • Page 381: Common Problems

    Is the respective communication protocol correctly configured in the CPU?  Are the variables which enable the MODBUS relations properly enabled? If no problem has been identified, consult the Altus Technical Support. Troubleshooting Table 7-32 shows the symptoms of some problems with their possible causes and solutions. If the problem persists, consult the Altus Technical Support.

  • Page 382: Preventive Maintenance

    7. Maintenance For models NX3010, NX3020 and NX3030, the CPU Screen CPU must be placed in slots 2 and 3 of rack 0. Put shows the it in the correct slots. CPU in a wrong position message CPUs NX3004 and NX3005 must be placed in slots WRONG SLOT 0 and 1 of rack 0.

  • Page 383: Glossary

    8. Glossary 8. Glossary Active CPU In a redundant system, the Active CPU performs the system control, reading the input points values, executing the applicative program and driving the output values. ActivePrg POU from the program type, created automatically, which should be completed by the user. It runs only on the Active PLC, and used to control the automated process.
  • Page 384 The only task allowed by a redundant PLC. Calls the MainPrg program. MasterTool IEC XE Identifies the Altus program for microcomputers, executable in Windows environment, which allows the development of applications for the Nexto CPUs series. Throughout the manual, this program is referred to by the acronym or as MasterTool IEC XE programmer..
  • Page 385 Set consisting on a cluster (PLCA and PLCB), PX2612 control panel, and remote I/O systems. Relays language and Group of instructions and variables that allow an applicative program edition to be used in a PLC. Altus blocks Ripple Ripple present in DC supply voltage.
  • Page 386 8. Glossary Sweeping cycle A complete execution of the applicative program in a programmable controller. Symbolic Variables IEC Variables created in POUs and GVLs during the applicative development, which are not addressed directly in the memory. Name associated with a variable or a logic that allows a brief identification of its contents. Time-out Predetermined maximum time that a communication is completed.

  • Page 387: Annex A. Dnp3 Interoperability

    Annex A. DNP3 Interoperability 9. Annex A. DNP3 Interoperability DNP3 Device Profile DNP3 DEVICE PROFILE DOCUMENT Device Identification Vendor Name Altus S/A Device Name NX3030 Device Function Slave DNP Levels Supported for Requests: None Responses: None Connections Supported IP Networking...

  • Page 388: Dnp V3.0 Implementation Table

    Annex A. DNP3 Interoperability DNP V3.0 Implementation Table DNP OBJECT GROUP & VARIATION REQUEST RESPONSE Master may issue Master must parse Outstation must parse Outstation may issue Group Description Function Qualifier Function Qualifier Codes Codes Codes Codes (dec) (hex) (dec) (hex) Binary Input –...

This manual is also suitable for:

Nexto nx3020Nexto nx3005Nexto nx3010Nexto nx3030

Table of Contents