Home

1. Introduction - Beijer Electronics

1. Figure 5 32 ee gt we NX30xxproject MasterTool IEC XE File Edit View Project Build Online Debug Tools Window Help Gr A EFE p Start Fs b g Devices Stop Shift F8 F E z Sal Gow i New Breakpoint J S og BNE F 4 i Toggle Breakpoint F9 PLcLogic fa Bill of Materials Step Into F8 Configuration and Step Out Shift F 10 a Diagnostic Explores EEE ee a Diagnostics Run to Cursor rill Library Manager Set next Statement Bj MainPrg PRG Show next Statement 7 a Task Configuration Write values Ctrl F7 Configuration i By e MainTaik orce values og Configuration Bus Unforce values Alt F7 A f NX3010 NX3010 Add All Forces To Watchlist G com1 Display Mode G com2 i oy G NETI E Figure 5 32 Starting the Application Figure 5 33 shows the application in execution In case the POU tab is selected the created variables are listed on a monitoring window in which the values can be forced and visualized by the user In case the variables are forced through the F7 command on the keyboard the CPU will indicate this condition on the graphic display For further details see Graphic Display chapter It is important to highlight that when used the MODBUS RTU Slave and the MODBUS Ethernet Server and the Read only option from the configured relations is not selected the forced writing command F7 must be done over the available variables in the monitoring window as the wri
2. SERIAL_GET_CTRL This function block is used to read the CTS DSR and DCD control signals in case they are available in the serial port A false value will be returned when there are not control signals SERIAL_GET_CTRL CTS_ ALUE DSR_VALUE DCD_VALUE Figure 4 54 Block Used to Visualize the Control Signals input parameters This variable when true enables the function Select the serial port as described in the PORT SERIAL FORT SERIAL_PORT data type Table 4 82 SERIAL_GET_CTRL Input Parameters 135 4 Configuration Output parameters This variable is true when the block is BOOL completely executed It is false 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 is false otherwise ERROR BOOL It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR STATUS SERIAL_STATUS ILLEGAL_SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE FB_GET_CTRL_NOT_ALLOWED NOT_CONFIGURED CTS_VALUE BOOL Value read in the CTS control signal DSR_VALUE BOOL Value read in the DSR control signal DCD_VALUE BOOL Value read in the DCD
3. Execution Time 50 ms 100 ms 200 ms 50 ms 100 ms 200 ms Table 5 11 The Influence of the Variables Forcing in a Redundant PLC ATTENTION When a CPU is with forced variables and it is de energized the variables will lose the forcing in the next initialization The limit of forcing for the Nexto CPUs is 128 variables regardless of model or configuration of CPU used Logout In case the user option is to finalize the communication with the CPU the command Logout must be used placed in the Online menu as shown on Figure 5 35 211 5 Initial Programming File Edit View Project Build Online Debug Tools Window Help z ms E Login Alt F8 GA IE fe B re X aa Eicon a Create boot application lon Bus 4 MU Stuff Logoff current online user 1 H PLC Logic z mi G Online Change B Bill of Materials Source download to connected device F Configuration S Redundancy Configuration Di tic aao Exp OPC Configuration Nagnostcs A i Library Manag CPU Informations MainPrg PRG Reset warm u Pp Configure Reset cold MainT amp Main ask Reset origin MainPt J Configuration Bus J nx3030 Nx3030 6 coi G com2 3 GS NETI s G NET2 Figure 5 35 Interrupting the Communication with the CPU Simulation Mode MasterTool IEC XE has an important simulation feature which allows the user to test his application without the equipmen
4. PX2612 Panel Test The PX2612 panel is composed by buttons LEDs and relays Many of these resources are not used very often thus are rarely tested and the defects may not be detected It s important to run tests from time to time in order to verify if these resources are working properly to avoid obscure failures to prevent the PX2612 use when it s necessary Test Mode Entry The first step to test the PX2612 is to set it to test mode This is done turning on the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal command bit on both PLCs The PLC perceives that is in test mode when the following two bits are on 296 6 Redundancy with NX3030 CPU e DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal RedCmdLoc TestModeLocal on in this PLC e DG_NX4010 tRedundancy RedCmdRem bTestModeLocal RedCmdLoc TestModeLocal on in the other PLC When both bits are on the PLC turns on the DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bRedPanelTestMode diagnostic to inform that the PX2612 is in test mode Test Mode Manual and Automatic Outputs The user can finish the test mode manually turning off the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal bit in both PLCs Actually turning it off in just one PLC is enough as the test mode demands this bit to be on in both PLCs However this practice is recommended In case the user forgets to turn off the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal bit it s automatically turned off 15 min
5. User Manual Nexto Series CPUs NX3010 NX3020 NX3030 Rev F 03 2015 Doc Code MU214605 www altus com br 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 advice According to current legislation in force in Brazil the Consumer Defense Code we provide the following information regarding personal safety and installation by the client The industrial automation equipment built by Altus is strong and reliable due to the stringent quality control it is subjected to However the electronic industrial control equipment programmable controllers numerical commands etc can cause damage to the machines or processes through their controllers when there are defective components and programming or installation errors This can even put human lives at risk The user should consider the possible consequences of these defects and should provide additional external installations for security so that if necessary the security of the system can be maintained especially during the initial installation and testing It is essential to completely read the manuals and or about the technical characteristics of the product before its installation or use The equipments manufactured by Altus don t cause direct environmental hazards and don t produce any kind of pollution
6. QX n 3 Communication disabled The bCommDisabled bCommidle bit is restarted in this condition QX n 4 Communication terminated bCommOk previously was held successfully QX n 5 Communication terminated bCommError BIT previously had an error Check error code QX n 6 bCommAborted BIT Not used in MODBUS RTU Master Last error code enabled when bCommError true ERR_EXCEPTION 1 response reported on an exception code see eLastExceptionCode Exception Code ERR_CRC 2 response with invalid CRC ERR_ADDRESS 3 MODBUS address not found The address that answered the request was different than expected ERR_FUNCTION 4 invalid function code The function received in response was different from that expected by request ERR_FRAME_DATA_COUNT 5 the amount of response data was different than expected ERR_NOT_ECHO 7 response is not echo of the question FC 5 and 6 ERR_REFERENCE_NUMBER 8 invalid reference number FC 15 and 16 ERR_INVALID_FRAME_SIZE 9 response less than expected ERR_SEND 21 an error occurred during the transmission phase ERR_RECEIVE 22 an error occurred during the reception phase k QX n 2 bCommPostponed MASTER_ERROR_CODE QB n 1 eLastErrorCode BYTE 73 4 Configuration ERR_SEND_TIMEOUT 41 time out on the application level during transmission ERR_RECEIVE_TIMEOUT 42 time out on the application level while waiting for reply E
7. Address or configuration selecting switch composed by pins present in the circuit board and a small removable connector used for selecting The variable can be accessed directly in the memory using the desired address E g QB0 MW 100 Part of the project corresponding to the executable code It s the program loaded into a PLC which determines the operation of a machine or process Reserved words in the programming software used to indicate diagnostics Electric signals cluster logically grouped with the function to transmit information and control between different elements of a sub system Basic information unit which can assume state 0 or 1 Time the network node type CSMA CD waits before re transmit data after the occurrence of collisions in the physical environment Rate at which information bits are transmitted via a serial interface or communications network measured in bits second Equipment for connecting two communication networks within the same protocol Dissemination of information simultaneously to all nodes connected to a communication network Information unit composed by 8 bits One of the UTP cable categories Unshielded twisted pair 100 ohm impedance and electrical characteristics supporting up to 100 MHz transmission frequency defined by the TIA EIA 568 A can be used in 10Base T and 100Base networks TX among others Set formed by the controllers half clusters PLCA and PLCB Product code formed by th
8. Figure 4 80 Project Settings Users Dialog Logged current users are listed in a tree structure Through the Add or Edit commands you can display beside Name login the full name and the user description Each user s properties can be viewed or not are hidden through the plus and minus sign respectively Each user by default is member of the Everyone To define a new user account use the Add button to open the Add User dialog 168 4 Configuration EEEKEE xxxxxx T Owner This user is also member of the Everyone group Lo _corecet_ Figure 4 81 Add User Account properties contains the following fields Logon Name Login name of the new user Full Name full name of the new user Serves only as additional information Description description of the new user Serves only as additional information Old Password This field is editable only when the dialog is used to modify an existing user account Before changing the password however you must enter a valid current password Password password for the new user Typing is represented by asterisks Confirm Password the password you entered above should be repeated and if the two passwords do not match an error message will be displayed This typing is also represented by asterisks Active This option enables the user account making it valid When the account is not valid the user can not perform the log
9. MIB is a collection of information organized hierarchically with each object of this tree is called OID Object Identifier For all equipment with SNMP it is mandatory to support MIB II In this MIB are described key informations for managing Ethernet networks SNMP in Nexto CPUs The CPUs of Nexto Series NX3010 NX3020 and NX3030 from firmware version 1 4 0 33 supports the protocols SNMPv1 SNMPv2c and SNMPv3 and support the MIB II where required objects are described in RFC 1213 The CPUs of the Nexto Series behave as agents in SNMP communication The information made available through SNMP cannot be manipulated or accessed through the user application requiring an external SNMP manager to perform access Table 4 108 contains the objects available in the Nexto CPUs ow Nome tescription O Contains name description location and other 1 3 6 1 2 1 1 ee ire ae equipment identification information Contains information of the machine s network interfaces The ifTable table OID 1 3 6 1 2 1 2 2 has the indexes 6 and 7 available which can be viewed by the network interfaces statistics NET 1 and NET 2 respectively of the Nexto series CPUs 1 3 6 1 2 1 2 Interfaces 1 3 6 1 2 1 3 At Contains information of the last required connections to the agent 1361214 P Contains statistical connections using IP protocol 13 6 1 2 15 1 3 6 1 2 1 11 Table 4 108 MID II Objects Nexto Series SNMP Agent By
10. Segment of a communication network that interconnects a group of devices nodes in order to isolate the local traffic or use different protocols or physical layer 326 8 Glossary Supervision station Sweeping cycle Symbolic Variables Tag Time out Toggle Token TX Upload UTP Varistor WD Word Watchdog circuit 10Base T Equipment connected to a PLC or instrumentation network in order to monitor or control the process variables A complete execution of the applicative program in a programmable controller 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 Predetermined maximum time that a communication is completed If exceeded retentive or diagnostic procedures will be activated Element that has two stable states alternately exchanged each activation It is a mark that indicates who is the master of the bus at the time Acronym used to indicate serial transmission PLC configuration or program reading Stands for unshielded twisted pair Cable type formed by pairs of unshielded twisted wires For network applications UTP term generally refers to the cable 100 ohms Category 3 4 or 5 specified by the TIA EIA 568 A Normally the UTP cable has four pairs of wires twisted within the same sheath outer package Protection device against
11. 1 Attempt of synchronization through the first server In case the synchronization occurs successfully the CPU waits the time for a new synchronization Synchronization Period and will synchronize again with this server using it as a primary server In case of failure the server does not respond in less than 5 s step 2 is performed 2 Attempt of synchronization through the second server In case the synchronization occurs successfully the CPU waits the time for a new synchronization Synchronization Period and will try to synchronize with this server using the primary server In case of failure the server does not respond in less than 5 s the time relative to the Synchronization Period is waited and step lis performed again As the waiting time for the response of the SNTP server is 5 s the user must pay attention to lower than 10 s values for the Synchronization Period In case the primary server does not respond the time for the synchronization will be the minimum of 5 s waiting for the primary server response and the synchronization attempt with secondary server In case neither the primary server nor the secondary one responds the synchronization time will be 10 s minimum waiting for the two servers response and the new connection with first server attempt 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 In case the serve
12. 4 Configuration File Edit View Project Build Online Debug Tools Window Help fale 1 Devices ax IZ Configuration Bus Device x G SG MS E f Communication Settings Fies Log J users and Groups Access Rights Information p J Device Nx3030 m m a n Host Location J C Temp z AR e Runtime Location gj MemoryCard i amp 5 E PLC Logic Wz Application Name Size Modified Name Size Modified hi 2 Bil of Materials t Es ed Configuration and Consumpti J Others Application EH Diagnostic Explorer E device devdescxml 233 17 KB 238 768 9 29 2014 4 39 PM i Backup Diagnostics CO File_o1tes 428 bytes 9 1 2014 6 19 PM Userlog fD Library Manager aot 226 bytes 10 2 2014 12 52 PM a NextoMemcard E MainPra PRG File_OL bt 428 bytes 10 9 2014 12 28 PM Task Configuration B maintask B MainPrg J Configuration Bus Nx3030 Nx3030 comi com2 a NETI d NET2 Last build 0 0 Precompie y Current user nobody Figure 4 46 Files Transference ATTENTION The files contained in the folder of a project created by MasterTool IEC XE have special names reserved by the system in this way cannot be transferred through the Files tab If the user wishes to transfer a project to the user memory you must compact the folder and then download the compressed file zip for example In case it is necessary to transfer documents from the C
13. Bil PLC Logic Q Start Address of Diagnostics Area protocol E Application 66922 s 2 Bil of Materials aie gt Size Configuration and Consumpti lt TCP EH Diagnostic Explorer Used range QB66922 QB66941 Diagnostics f Library Manager ee E MainPrg PRG Name Destination IP TCP Port Task Configuration B MainTask 8 MainPrg J Configuration Bus J Nx3030 Nx3030 com com2 S a NET I J mopsus_client MODBU a Ner2 Data Type Slave Address Bend Onin Siart Read Data Size Read IEC Variable ker sant Write Data Size Write IEC Variable r E Mess T Omessage s Last build 0 0 Precompie y7 Current user nobody Figure 4 30 MODBUS Client Setup Screen 98 4 Configuration Protocol selection and direct representation variables Q for diagnostics Setting Description _ Default Value Options Initial Address of Initial address of the Diagnostics in Q diagnostic variables ae pla 14740369 Size of diagnostics Disabled for editing RTU via TCP Protocol Protocol selection TCP TCP Table 4 49 Protocol selection and direct representation variables for diagnostics Notes Initial Address of Diagnostics in Q this field is limited by the size of output variables addressable memory Q at CPU which can be found in chapter Technical Description Default Value the default value cannot be defined for the In
14. Configuration and Consumption 3 Diagnostic Explorer Diagnostic IP Address PLC A Non Active 192 168 15 69 f Library Manager E ActivePra PRG MainPrg PRG NonSkippedPrg PRG Gateway Address 192 168 15 253 Redundancy Configuration 1 symbol configuration BH Task Configuration mainTask T Persistentvars J Configuration Gus J N3030 Nx3030 J Nx4010 wx4010 Nxso00 Nx5000 Period of Redundancy Test ms 500 IP Address Active 192 168 15 68 IP Address PLC B Non Active 192 168 15 70 Subnetwork Mask 255 255 255 0 ow m n Ww Advanced Ethernet Settings nese Redundancy of Communication Redundancy of Communication a NETI Retries of Redundancy Test 4 Nxs000_01 Nxs000 amp NETI comi com2 a NETI amp NET2 Switching Period s 10 Figure 4 10 NX5000 Redundancy Parameter Protocols Configuration Independent of the protocols used in each application the Nexto Series CPUs possess some maximum limits for each CPU model There are basically two different types of communication protocols symbolic and direct representation mappings The maximum limit of mappings as well as the maximum protocol quantity instances is defined on Table 4 17 NXx3010 Nx3020 _ NXx3030 Maximum number of symbolic mappings 20480 20480 20480 Maximum number of mappings for direct 512 512 512 representation COM n Master or Slave instan
15. Figure 4 72 TON_NR Function Block Utilization example in ST language PROGRAM NonSkippedProg VAR bStart BOOL m ND_VAR TON NR TON NR When bStart TRUE starts the counting TON_NR IN bStart PT T 20S Actions executed at the end of the counting IF TON_NR Q TRUE THEN bStart FALSE END IF Foe Oy 155 4 Configuration TP_NR The TP_NR function block works as a trigger and has its functioning and configuration similar to the TP_RET function block differentiating only for not being redundant nor retentive Figure 4 73 TP_NR Function Block Utilization example in ST language PROGRAM NonSkippedProg VAR bStart TP NR END_ VAR BOOL TP_NR Configure TP_NR TP_NR IN bStart PT T 20S 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 156 4 Configuration User Log Feature that allows the user to create own records and write to log files on the memory card present in the CPU The files are generated in a specific directory of the memory card in the CSV format allowing viewing in text editors and spreadsheets The separator was the semicolon character For more information about the use of the memory card see chapter C
16. IB16383 The proper configuration of redundant I from IBO is important to decrease the necessary time for redundant variables synchronization decrease the redundancy overhead E g if the real application allocates only IBO 1B1499 for redundant inputs the redundant I area size can be defined as 1500 bytes The figure below illustrates the redundant and non redundant I direct representation variables allocation where RI is the I quantity really configured as redundant I really RI kbytes redundant RI 0 80 RI default 16 Reserved for 80 kbytes redundant l expansion 80 RI kbytes 16 kbyte i redundant Figure 6 7 Redundant and Non redundant I Allocation 228 6 Redundancy with NX3030 CPU Redundant and Non redundant Q Variables The NX3030 CPU allocates 96kbytes of Q variables QBO QB98303 The first 80 Kbytes can be redundant QBO QB81919 The last 16kbytes are always non redundant QB81920 QB98303 The 80 Kbytes area which can be redundant is divided in two sections e The first Kbytes are reserved for outputs that can be redundant and are typically allocated for an TO remote system PROFIBUS MODBUS etc The size value is configurable and its default value is 16384 By default this section includes QBO QB65535 e The next bytes are reserved for diagnostics which can be redundant from the I O system I O modules diagnostics communication interfaces diagnostics
17. IP address of the Controller in 0 0 0 1 to He eS the Ethernet bus NE 1683 08 255 255 255 254 Sub network Sub net mask of the Controller 0 0 0 1 to in the Ethernet bus sues 255 255 255 254 Gateway address of the 0 0 0 1 to SENN Controller in the Ethernet bus qe TOE ees 255 255 255 254 Table 4 16 Remote NET 1 Configurations Reserved TCP Ports The following TCP ports of the Ethernet interfaces both local and remote are used by CPUs services so they are reserved and cannot be used by the user 80 161 8080 1217 1740 1741 1742 1743 and 11740 NX5000 Module Configuration The NX5000 modules can be inserted in the project to increase the number of Ethernet interfaces if the local CPU interfaces are not enough Only the NX3020 and NX3030 CPUs support the NX5000 module The Ethernet channels of the NX5000 modules can be used individually or arranged in NIC Teaming pairs NIC Teaming pairs are used to provide redundant Ethernet channels 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 Moreover setting up this network as redundant with NIC Teaming pairs provides an excellent availability To build a redundant HSDN two NX5000 modules must be inserted Figure 4 9 shows an example of
18. If the PROFIBUS 1 network is redundant it will be divided in PROFIBUS 1 A and PROFIBUS 1 B In case it s non redundant there will be only one PROFIBUS 1 A network The same is valid for PROFIBUS 2 Figure 6 1 shows an example with a single PROFIBUS network PROFIBUS 1 which is redundant PROFIBUS 1 A and PROFIBUS 1 B Only a few remote types can be connected straight to this redundant PROFIBUS network e POQ5063V5 PROFIBUS slave DP VO for Ponto Series remotes e PO5065 PROFIBUS slave DP V1 with Hart for Ponto Series remotes e AL 3416 PROFIBUS slave DP VO for AL 2004 CPU 236 6 Redundancy with NX3030 CPU e NX5210 PROFIBUS slave DP VO 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 Such non redundant PROFIBUS remotes can be from any brand or model PROFIBUS Failure Modes Vital and Not Vital Each one of the PROFIBUS networks can be configured in two different modes e Vital failure in case this network fails completely this failure can determine a redundancy state transition in the redundant CPU switchover In case a redundant PROFIBUS network a complete failure implies in the failure of both composing networks e Not Vital failure even if this network fails completely this failure won t determine a redundancy state transition in the redundant CPU switchover Redundant Etherne
19. Number of characters left in the transmission buffer in COM 1 0 to 65535 These counters are restarted in the following conditions Energizing Configuration of the COM 1 serial port Removal of RX and TX queues PS When the CPU is set with parity Without Parity the counter of errors of parity is not incremented in case it receives a different parity In this case it will be indicated an error of frame The maximum value of each counter is 65535 Reserved Protocol selected in COM 2 00 Without protocol 01 MODBUS RTU Master 02 MODBUS RTU Slave 03 Other protocol Counter of characters received from COM 2 0 to 4294967295 Counter of characters transmitted through COM 2 0 to 4294967295 Number of characters left in the reading buffer in COM 2 0 to 65535 Number of characters left in the transmission buffer in COM 2 0 to 65535 These counters are restarted in the following conditions Startup Configuration of COM 2 serial port Removal of RX and TX queues PS When the CPU is set with parity Without Parity the counter of errors of parity is not increased in case it receives a different parity In this case it will be indicated a frame error The maximum value of each counter is 65535 Reserved Reserved Bit 0 Indicates the state of the link 7 Maintenance NET n Selected protocol in NET 1 9 QB QB Eth NET1 wP QB n 93 QB nN 93 QB n 93 thernet wPr
20. Returns the number of characters which are still the RX queue after the function block execution Returns the silence time in the RX queue measured since the last received character is finished The time unit is 10us 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 Table 4 91 SERIAL_RX_EXTENDED Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Receive Ex SERIAL RX EXTENDED Port SE RIAL _ PORT COM1 Buffer Pointer ARRAY 0 1023 OF SERIAL RX _CHAR_ EXTENDED Status SERIAL STATUS END _ VAR INPUTS Receive Ex REQUEST TRUE Receive Ex PORT Port Receive Ex RX BUFFER POINTER ADR Buffer Pointer Receive Ex RX BUFFER LENGTH 1024 Max size Receive Ex RX TIMEOUT 10000 FUNCTION Receive Ex OUTPUTS Receive Ex DONE Receive Ex EXEC Receive Ex ERROR Status Receive Ex STATUS If it s necessary to treat the error Receive Ex RX RECEIVED Receive Ex RX REMAINING Receive Ex RX SILENCE SERIAL_SET_CTRL This block is used to write on the control signa
21. Target Vendor Altus Sorting order Target Version Name x 1 2 0 3 E Don t save network path in project 7 Secure online mode Figure 5 24 Activating the CPU 205 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 Compiling a Project In order to execute the verification of the created application the user must compile the project This is the most efficient way for finding or receiving error warnings regarding any mistake made during the product configuration and application edition To execute such procedure access the Build menu and click on Build or press F11 on the keyboard as shown on Figure 5 25 File Edit View Project Build Online Debug Too SEN A E IET Generate code ae Q kale e Clean Devices Clean all i Ta o a Aa Figure 5 25 Compiling the Project After the processing time which varies according the user application size the errors and alarm messages in case they are needed will be shown below as depicted on Figure 5 26 Ble Edt View Project Buld Onine Debug Tools Window Help SEIA I T a Aago Devices ya x StartPage if Configuration Bus zx 5 Noto isi J Ti 700 fj Device
22. wRedStateDuration wCycleCounter dwlIECTimer SyncLinkStatistics NET_Stat Each line presented in the log has the following columns Timestamp event time and date with resolution in milliseconds Severity information warning error or exception Description text that describes the event Component component that has generated the event and in the Redundancy Event Log case is Redundancy Management The Description column text has the following information e The diagnostic or command name which has been modified e The new value assumed by this diagnostic or command e The RedDgnLoclsGeneral_Diag wCycleCounter value which can be used as sequence auxiliary information e The RedDgnRem sGeneral_Diag CycleCounter which can be used as sequence auxiliary information An example of the Description column can be the following RedDgnLoc sGeneral Diag eRedStat Active Local cycle 1234 Remote cycle 1233 To access this screen a double click must be done on the device NX3030 in the device tree and then the tab Log must be selected There s a filter that allows selecting only the Redundancy Management component to show only the redundancy events 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
23. 8192 0 s Polling ms Used range 1X8192 0 1X8192 0 100 Mapping Diagnostics Area 66942 Used range QB66942 QB66949 Figure 4 33 MODBUS Function 100 4 Configuration Configuration Default Value Option Read Write MODBUS function t Read unction type ea Read Write Write Mask Slave Address The MODBUS slave address oe 0 to 255 Polling ms Period of communication ms 0 to 3600000 1 Mapping 3 gt z Starting address of MODBUS reese interface diagnostics 0 to 2147483640 rea Read Initial Starting address of the read Address data MODBUS 1 to 65536 y Number of read data Depends on the nead DataiSize MODBUS OoOo function used IEC Read Starting address of the read Variable variables l C S aa ee Write Initial Starting address of MODBUS Address writing data 1 10 99936 Write Data Size Number of MODBUS writing Depends on the data function used IEC Write Starting address of the write Variable variables Q ae 010219489034 Write Mask of Starting address of variables IEC Variables for write mask Q Cie Ien seen Table 4 51 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 When the address O is
24. COM 2 In order to connect to a RS 485 network using a COM 2 interface external termination the AL 1763 cable identified terminals must be connected in the respective device terminals according to the Table 3 8 Ooo o o o on _ k pa Nooo O OO ee O ST a E Table 3 8 COM 2 with RS 485 Connections with External Termination The Figure 3 7 diagram indicates how the AL 1763 connection terminals should be connected in the device terminals 26 3 Installation DEVICE NX3010 RS 485 NX3020 NX3030 AL 1763 11083002A Figure 3 7 COM 2 with RS 485 Connections Diagram with External Termination Diagram Note The not connected terminals must be insulated so they do not make contact with each other RS 422 Communication without Termination In order to connect in a RS 422 network with no termination in COM 2 interface the cable AL 1763 identified terminals must be connected in the respective device terminals as shown on Table 3 9 ws sw E a T OOOO HCSC T S a T T a a T D S a T E I 2 2 0CLClU CS Table 3 9 COM 2 with RS 422 Connections with no Termination The Figure 3 8 diagram indicates how the AL 1763 connection terminals should be connected in the device terminals DEVICE NX3010 RS 422 NX3020 NX3030 AL 1763 11032104C Figure 3 8 COM 2 with RS 422 Connections with no Termination Diagram 27 3 Installation Diagram Note The not connected termina
25. F Add remove children Dev2 Device dp Everyone Logger se Owner PlcLogic Application Settings UserManagement F Execute Modify H F View Howto Select one or more actions and target objects from the left list Then select the groups in the upper view for which you want to adjust permissions Click Grant to grant permissions for the selected groups Click Deny to deny permissions for the selected groups Click Clear to reset permissions to default for the selected groups Figure 4 90 Device Access Rights Access rights add remove child execute modify and view are configured for each device and enable for each user actions according to Table 4 115 179 4 Configuration Device Setting Access Permissions Actions Relevant Rights Add remove child Modify Se eee teaser er 2 Read ReadLogEnties Entries Application download Online Changes create Bootapoicaion S A Sid O vws O o T x wate values invarabies OOOO o a xd Force vavesinvarables V Tefo roarmemove Breakpoint o T o C sewoe OOO a o Ss O amose o S x dT Cid CCS C sanasen o O ooo C Recas OOOO O O C aons Apocan o o o poReset wam coa roin Txo C view usersetings O T Sid xd View User Settings Usearagement ement i Modify User Settings es en o o O Table 4 115 Actions and Rights Application Login E E eo eed Application download to a CPU without application Pl
26. FALSE The AL 2319A cable is connected to the NX4010 module TRUE This failure is reported in case a synchronization service hasn t been finished successfully within a specific time out and failures from the type binternalFailure or bLinkDownFailure haven t been found to justify that FALSE The NX4010 module is working properly bTimeoutFailure bReserved 4 7 Reserved QB n 33 The sNETB_Diag substructure has the following fields for NETB synchronism channels diagnostics Direct Representation AT Variable Variable DG_NX4010 tRedundancy Description RedDgnLoc sNETB_Diag Table 6 7 NETA Interface Specific Diagnostics TRUE The synchronism channel has some type of failure The 3 next diagnostics will indicate the bGeneralFailure specific failure FALSE The synchronism channel is working properly TRUE The detected failure has its cause within this PLC Such failures are treated in a special way FALSE The NX4010 module is working properly blnternalFailure TRUE The AL 2319A cable is disconnected from the NX4010 module or broken in one of the PLCs 2 bLinkDownFailure FALSE The AL 2319A cable is connected to the NX4010 module TRUE This failure is reported in case a synchronization service hasn t been finished successfully within a specific time out and failures 3 bTimeoutFailure from the type bInternalFailure or bLinkDownFailure haven t been fo
27. File Edit View Project Build New Project Ctl4N f OpenProject Ctl o A Project Archive Source upload Page Setup Recent projects b Exit Alt F4 Figure 5 1 New Project Later a window will be presented to the user requesting the project type selection and following the name and path to store the project in the computer Click on OK to proceed or Cancel to cancel New Project x Categories Templates E General l Empty Library MasterTool Standard Project Creates a new project automatically induding the corresponding CPU and selected POUs and Tasks Name Nexto Location C gt im Figure 5 2 Project Classification 188 5 Initial Programming Next the user must select the desired CPU the basic hardware modules that form the bus that is the model of both backplane rack and power supply and the redundancy configuration In this case it will be used a NX3010 CPU without redundancy a NX9001 backplane rack and a NX8000 power supply SSS SSS S999 EESS MasterTool Standard Project Al You are about to create a new MasterTool Standard Project Choose the following options and the wizard will create project as you decide Choose the CPU model 1nx30 10 Altus S A CPU 1 Eth 2 Serial Memory Card and Rack Expansion Choose the rack model Nx9001 Altus S A 12 Slot Backp
28. Some error occurred during FOMT CONE bCOM1ConfigError or after the COM 1 serial interface ERROR configuration FALSE The COM 1 serial interface configuration is correct TRUE Some error occurred during GOMZ CONE bCOM2ConfigError or after the COM 2 serial interface ERROR configuration FALSE The COM 2 serial interface configuration is correct TRUE Some error occurred during NEON bNET1ConfigError or after the NET 1 Ethernet interface ERROR f configuration FALSE The NET 1 Ethernet interface configuration is correct NET2 CONF TRUE Some error occurred during or ERROR A after the NET 2 Ethernet interface bNET2ConfigError FALSE The NET 2 Ethernet interface configuration is not correct INVALID TRUE The date or hour are invalid DATE TIME bInvalidDateTime a FALSE The date or hour are correct TRUE The RTS Runtime System RUNTIME has been restarted at least once This RESET diagnostics is only cleared in the bRTSReset system restart FALSE The RTS Runtime System is operating normally TRUE True in case the OTD key has been locked for more than 20 s at least CFD Sve once while the CPU was energized This diagnostic is only cleared in the bOTDSwitchError system restart QB n 2 FALSE The key is not currently locked or was locked while the CPU was energized bReserved_xx ABSENT RACK TRUE One or more declared racks bAbsentRacks are
29. T END_VAR INPUTS sAppName Application Variable receives the application name psAppName ADR sAppName Pointer with application name sTaskName MainTask Variable receives task name psTaskName ADR sTaskName Pointer with task name pstTaskInfo ADR TaskInfo Pointer that receives task info FUNCTION Function call Info GetTaskInfo psAppName psTaskName pstTaskInfo Variable Info receives possible function errors 318 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 For further information regarding the diagnostic key utilization and its visualization see One Touch Diag section Below on Figure 7 9 it is possible to observe the available characters in the Nexto CPU graphic display and next its respective meanings RUN S1 S2 ACT F DGO Figure 7 9 CPU Status Screen 11052006C Legend 1 Indication of the CPU status operation In case the CPU application is running the state is Run In case the CPU application is stopped the state is Stop For further details see Run Mode and Stop Mode section 2 Memor
30. 02 Secondary Server Day of the last update of the RTC Month of the last update of the RTC SNTP sLastUpdateTime i Year of the last update of the RTC wYear SNTE sLastUpdateTime Hour of the last update of the RTC byHours SNTP sLastUpdateTime byDayOfMonth SNTP sLastUpdateTime byMonth SNTP sLastUpdateTime Minute of the last update of the RTC byMinutes Second of the last update of RTC SNTP sLastUpdateTime Millisecond of the last update of RTC bySeconds SNTP sLastUpdateTime wMiliseconds SNTP wReserved_0 7 Maintenance QB n 656 QB n 656 SNTP wReserved_1 QX N 658 0 QX n 658 0 aie te aac Connection status of client 01 Queue status of client events 01 QX N 658 1 QX n 658 1 SOE 1 bOverflowStatus FALSE There was no overflow QB n 659 QB n 659 SOE 1 byReserved_0 TRUE Exceeded queue limit QX N 662 0 QX n 662 0 epee Connection status of client 02 QX n 662 1 QX n 662 1 SOE 2 bOverflowStatus QB n 663 SOE 2 byReserved_0 QW n 664 QW n 664 SOE 2 wEventsCounter oe Sevens inthe client gueue Each bit presents a rack identification QD n 506 QD n 666 QD n 666 Rack dwAbsentRacks number if the bit is TRUE it means QW n 660 QW n 660 SOE t wEventsCounter punter of events in the client queue the rack is absent Each bit presents a rack identification o o number if the bit is TRUE it means QD n 510 QD n 670 QD n 670 Rack dwDupl
31. 1 4 8 and 14 Enabled Configuration enabled Disabled Configuration disabled Enabled Configuration enabled Disabled Configuration disabled Enabled Configuration enabled Disabled Configuration disabled Table 4 10 COM 1 Advanced Configurations 57 4 Configuration COM 2 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 may be associated only to tasks of custom project profile described in the Custom section of Initial Programming chapter Event RX CTS External events such as the CTS signal COM 1 may be associated only to tasks of custom project profile described in the Custom section of Initial Programming chapter The COM 2 communication interface is composed by a DB9 female connector for the RS 422C and RS 485 patterns It allows the point to point or network communication in the open protocols MODBUS RTU slave or MODBUS RTU master When using the MODBUS master slave protocol some of these parameters such as Serial Mode Data Bits RX Threshold and Events Serial are automatically adjusted by MasterTool tool for the correct operation of this protocol The parameters which must be configured for the proper functioning of the application are described below Serial Type Serial channel RS 485 RS 422 and RS 485 configuration a 200 300 600 1200 1800 Baud Rate EEr e port 115200 2400 4800 9600
32. 1 Read Write Holding Registers FC 23 121 Write Data Range this field shows the MODBUS write data range configured for each request The initial address along with the read data size will result in the range of write data for each request Diagnostic Variable The MODBUS request diagnostics configured by symbolic mapping or by direct representation are stored in variables of type T_DIAG_MODBUS_RTU_MAPPING_1 and the mapping by direct representation are in 4 byte and 2 word which are described in Table 4 27 n is the value configured in the Diagnostic Initial Address field in Q The definitions of the exception codes 128 129 and 255 presented in this table are valid only when using Altus slaves For slaves from other manufacturers these exception codes may have different meanings 72 4 Configuration Direct Representation Variable Diagnostic variable of type T_DIAG_MODBUS_RTU_MAPPING_1 pescripion Communication status bits QX n 0 bCommlid IT Communication idle BGM 9 waiting to be executed QX n 1 bCommExecuting BIT 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 avoid indeterminacy The time spent in this State is not counted for the purposes of time out The bCommldle and bCommExecuting bits are false byStatus when the bCommPostponed bit is true
33. 19200 P 9 38400 57600 115200 bps Odd i i Even area S None Parity Always One Parity Always Zero No parity Sets the data bits quantity Data Bits in each serial 5 6 7 and 8 communication character Stop Bits se the serial port stop 1 1 1 5 and 2 Extended Mode Extended operation mode which delivers information regarding A Sets the serial port the received data frame see Serial Mode operation mode Normal Mode note on COM 1 section Normal Mode Serial communication normal operation mode Table 4 11 COM 2 Configurations The serial interfaces Data Bits configuration limits the Stop Bits and Communication Parity fields Therefore the number of stop bits and the parity method will vary according to the data bits number Table 4 12 shows the allowed configurations for COM 2 interfaces 58 4 Configuration Data Bits Stop Bits 1 15 NO PARITY ODD EVEN PARITY ALWAYS AONE pee PARITY ALWAYS ZERO 1 2 NO PARITY ODD EVEN PARITY ALWAYS AONE PARITY ALWAYS ZERO 7 1 2 NO PARITY ODD EVEN PARITY ALWAYS AONE PARITY ALWAYS ZERO 1 2 NO PARITY ODD EVEN PARITY ALWAYS AONE PARITY ALWAYS ZERO Table 4 12 Specific Configurations Advanced Configurations The advanced configurations are related to the serial communication control in other words when it is necessary the utilization of a more accurate data transmission and reception control Bytes quantity which must be received for a new UART
34. 256 6 Redundancy with NX3030 CPU al Choose the network configuration and the wizard will create and or configure the following objects within the project PROFIBUS Choose the number of networks 1 Choose the type of network 1 Single Network Single Network Single Network Single Network CPU Ethernet Interfaces Choose the type of network 1 Redundant Network with Failure Mode Disabled Single Network with Failure Mode Disabled Expansion Ethernet Interfaces Choose the number of networks 0 Single Network with Failure Mode Disabled Single Network with Failure Mode Disabled Single Network with Failure Mode Disabled Single Network with Failure Mode Disabled 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 Select the standard language for all programs The language selected by the user is the standard for all programs but any other can be used for a specific POU Choose the project profile configuration and the wizard will create the following objects within the project Choose the project profile Single Choose the default language for all programs Structured Text ST About the project profile This project template indudes only one task and its POU is a
35. 9 2 1 ConnectionStatus2 9 2 2 OverflowStatus2 Indicates status of last update 00 Not updated 01 Last update failed 02 Last update had success Indicates which server was used in the last update 00 Any update 01 Primary Server 02 Secondary Server Client 01 event queue status FALSE OK TRUE Queue limit exceeded Client 01 event counter on queue Connection status of client 02 Client 02 event queue status FALSE OK TRUE Queue limit exceeded 9 2 3 EventsCounter2 Client 02 event counter on queue Table 4 109 Diagnostics via SNMP ATTENTION Items Ethernet NET2 SNTP and SOE are available only for CPUs NX3020 and NX3030 Configuration SNMP settings can be changed through the web page in the CPU Management tab in the SNMP menu To access the settings you must first log in as shown in Figure 4 78 My altus CPU Overview System Overview CPU Management Firmware Update SNMP English Espafiol Portugu s Change password Figure 4 78 SNMP Login screen 164 4 Configuration After successful login the current state of the service enabled or disabled as well as the user information SNMPv3 and communities for SNMPv1 v2c can be viewed The user can enable or disable the service via a checkbox at the top of the screen It s also possible to change the SNMPv3 information by clicking the Change button just below the user information Will open a form where you must co
36. Cluster IP Addressing IP Address PLC A 192 168 15 68 IP Address PLCB 192 168 15 70 Subnetwork Mask 255 255 255 0 Gateway Address 192 168 15 253 Advanced Figure 6 9 Fixed IP method Parameters that must be configured in the Fixed IP method e IP Address PLC A PLCA communication address e IP Address PLC B PLCB communication address e Subnetwork Mask e Gateway Address Exchange IP The Exchange IP can be configured in the Ethernet interfaces in the NX5000 Ethernet module In this method the half cluster IP depends on the PLC state Active or Non Active On every switchover the IP change occurs between the half clusters allowing them to assume the IP address from the new redundancy state PS for this addressing method the Ethernet ports from both PLCs PLCA and PLCB assume the same IP address while they both are in the Non Active state generating a network address conflict Considering this situation uncommon where no PLC is controlling the system this turns out to be a big problem and has to be considered 238 6 Redundancy with NX3030 CPU Active IP Ethernet Port Parameters Cluster IP Addressing Method Exchange IP D Cluster IP Addressing IP Address Active 192 168 15 68 IP Address Non Active 192 168 15 69 Subnetwork Mask 255 255 255 0 Gateway Address 192 168 15 253 Advanced Figure 6 10 IP Automatic Change Parameters that must be co
37. Cycle Time is up to 80 ms This is due to the fact that the CPU needs time to perform other tasks such as communication processing processing of the display and memory card and these tasks take place within the range the remaining 20 of Cycle Time The MasterTool IEC XE has also an option to limit the Cycle Time of the MainTask by setting the watchdog of the task so Cycle Time mentioned before is respected This is done by consisting the watchdog time of the task in 80 of the interval If the user is aware of the information above and wants to use the consistency of watchdog time this would be possible by checking the checkbox Generate error on tasks watchdog consistency in the CPU configuration tab However it is recommended to keep the watchdog time configured as default with 1000 ms and the checkbox to generate error in consistency unchecked 113 4 Configuration ATTENTION For very high cycle times typically higher than 300 ms even that the value of 80 is respected it may occur a reduction in the display response time and of the diagnostics key In case the 80 percentage is not respected and the running time of the user task is closer or exceeds the interval set for the MainTask the screen and the diagnosis button cannot respond once its priority in the system running is lower than the user tasks In case an application with errors is loaded in the CPU it may be necessary to restart it without loading this applicati
38. If the user forgets the s password s s account s with access to the CPU the only way to recover this access will be updating the firmware of the same Users and Groups The Users and Groups dialog is provided in a Device dialog tab It allows you to configure user and group accounts that together with the management of access rights control access to objects in the CPU in online mode 174 4 Configuration Common For some functions of a controller can be performed only by authorized users uses the Online User Management This option provides the ability to define user accounts assign access rights for groups and force the user authentication at login The specific user management device can be pre defined by the description of this Also depends on the device description which settings can be edited in the configuration dialogs in programmer Just as the project user management users must be members of groups and user groups can only get certain access rights Using the Configuration Dialog Basically the treatment of online user management dialog is similar to the design of user management There is the possibility of importing user accounts settings from the project user management E Configuration Bus J Device x Communication Settings Files Log Users and Groups Access Rights Information Upload from device Download to device G Load from disk ge Save to disk Currently logged on user
39. MU214605 Electrical Installation DANGER When executing any installation in an electric panel certify that the main energy supply is OFF Nexto Series CPUs energy supply come from the Power Supply Module which supplies the CPUs power through the backplane rack connection It does not need any external connection The module grounding is given through the contact between the module grounding spring and the backplane rack The Figure 3 1 shows the Nexto Series CPUs electric diagram installed in a Nexto Series backplane rack The same picture can be visualized on the left side from any CPU The connectors placement depicted are merely illustrative NX3010 NX3020 NX3030 MEMORY SLOT A B A A C 10 100Base TX K L P o sus A a A 10 100Base TX c A i A RS 232C c K A RS 485 RS 422 10092251D Figure 3 1 Nexto Series CPUs Electric Diagram 20 3 Installation Diagram Notes 1 Memory card interface 2 Ethernet interface pattern 10 100Base TX for programming debugging and MODBUS TCP network connection or other protocols 3 Ethernet interface pattern 10 100Base TX for MODBUS TCP network connection or other protocols only for NX3020 and NX3030 4 Serial interface pattern RS 232C for MODBUS RTU network connection or other protocols 5 Serial interface pattern RS 485 RS 422 for MODBUS RTU network connection or other protocols The physical interface choice depends on the cable use
40. NETA or NETB is in failure and this CPU knows this failure was caused by hardware components or internal software internal failures of NETA or NETB e The Other CPU is in Active state However it s not possible to synchronize the redundant data or the redundant forcing list e The other CPU state cannot be discovered through NETA NETB but this CPU can monitor the traffic in some configured PROFIBUS networks in vital fail mode This way it looks like the other CPU is controlling the process even though NETA NETB aren t working to confirm it e Link loss occurred to an Ethernet Interface configured as Vital Failure Transition 4 Starting to Active e 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 PLCA has priority to take over in Active state e The other CPU state can t be discovered through NETA NETB and besides that this CPU can t monitor traffic in any PROFIBUS network configured as vital fail mode or those networks weren t created Therefore it really looks the other CPU if off or out of execution For safety reasons besides switching to Active this CPU turns the other off using its PX2612 relay This condition must be kept for a while before the transition is executed Transition 5 Starting to Stand by e The other PLC is in Active state The re
41. Nexto Series CPUs Models Related Products The following products must be purchased separately when necessary RS 485 network cable up to 1000 meters RS 485 network cable up to 500 meters Table 2 15 Related Products Notes MT8500 MasterTool IEC XE is available in three different versions LITE PROFESSIONAL and ADVANCED For more details please check MasterTool IEC XE User Manual MU299609 AL 2600 This module is used for branch and termination of RS 422 485 networks For each network node an AL 2600 is required The AL 2600 that is at the ends of network must be configured with termination except when there is a device with active internal termination the rest must be configured without termination AL 2301 Two shielded twisted pairs cable without connectors used for networks based on RS 485 interface with 1000 meters of maximum length AL 2306 Two shielded twisted pairs cable without connectors used for networks based on RS 485 interface with 500 meters of maximum length AL 1729 RS 232C standard cable with one RJ45 connector and one DB9 male connector for communication between CPUs of the Nexto Series and other Altus products of the DUO Series Piccolo Series and Ponto Series AL 1748 RS 232C standard cable with one DB9 male connector and 1 DB9 female connector for communication between CPUs of the Nexto Series and Altus products of the Cimrex Series AL 1752 RS 232C standard cable with two DB9 male
42. PLCs POUs After receiving the answers for the previous questions the Wizard generates the main project defining a half cluster with the following initial hardware configuration Selected rack Power supply NX8000 positions 0 and 1 NX3030 CPU positions 2 and 3 NX4010 modules positions 4 and 5 and Panel PX2612 if selected After the NX4010 module NX5001 are inserted to implement PROFIBUS network with the features previously inserted by the user e After the NX5001 modules NX5000 are inserted to implement Ethernet network with the features previously inserted by the user 258 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 The following chapters present how to insert and configure the modules NX5000 NX5001 and NX4010 Some rules and precautions must be followed for a redundant project as described in the following sub sections Fixed Configuration in the 0 to 5 Rack Positions In the 0 to 5 positions of the selected rack the following modules must be always installed e Power supply NX8000 positions 0 and 1 e NX3030 CPU positions 2 and 3 e NX4010
43. Some bus position is malfunctioning Table 4 2 Bus Abnormal Situations 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 Hot Swap Disabled for Declared Modules Only In this configuration the CPU is immediately in Stop Mode when an abnormal bus situation as described on Table 4 2 happens The LED DG starts to blink 4x according to Table 4 3 In this case in order to make the CPU to return to the normal state Run in addition to undo what caused the abnormal situation it is necessary to execute a Warm Reset or a Cold Reset it can be done through the Communication menu of the MasterTool IEC XE If a Reset Origin is carried out it will be necessary to perform the download so that the CPU can return to the normal state Run The Reset commands Warm Cold and Origin can be done by MasterTool IEC XE in the Communication menu The CPU will remain in normal Run even if find a module not declared on the bus Hot Swap Disabled This setting does not allow any abnormal situation in the bus as shown in Table 4 2 mo
44. This field varies with the MODBUS data type configured i e when selected Coil or Input Status type the data field size must be a multiple of eight Also the maximum amount must not exceed the size of output addressable memory and not assign the same values used in the application IEC Variable in case the MODBUS data type is Coil or Input Status 1 bit the IEC variables initial address will be in the format QX10 1 However if the MODBUS data type is Holding Register or Input Register 16 bit the IEC variables initial address will be in the format QW This field is limited by the memory size of the addressable output variables Q from each CPU which can be seen on Technical Description chapter Read only when enabled it only allows the communication master to read the variable data It does not allow the writing This option is valid for the writing functions only Default Value the default value cannot be defined for the IEC Variable field since the creation of a relation can be performed at any time on application development The MasterTool IEC XE software itself allocate a value from the range of direct representation output variables Q still unused The default cannot be defined for the Data Size field as it will vary according to selected MODBUS data type In the previously defined relations the maximum MODBUS data size can be 65535 maximum value configured in the Data Size field However the request which arrives in t
45. an extra language CFC These languages can be separated in text and graphic IL and ST are text languages and are similar to Assembly and C respectively LD SFC FBD and CFC are graphic languages LD uses the relay block representation and it is similar to relay diagrams SFC uses the sequence diagram representation allowing an easy way to see the event sequence FBD and CFC use a group of function blocks allowing a clear vision of the functions executed by each action The programming is made through the MasterTool IEC XE IDE development interface The MasterTool IEC XE allows the use of the six languages in the same project so the user can apply the best features offered by each language resulting in more efficient applications development for easy documentation and future maintenance For further information regarding programming see User Manual MasterTool IEC XE MU299609 Programming Manual MasterTool IEC XE MU399609 or IEC 61131 3 standard Memory Organization and Access Nexto Series uses an innovative memory organization and access feature called big endian where the most significant byte is stored first and will always be the smallest address e g 7QBO will always be more significant than QB1 as in Table 5 1 where for CPUNEXTO string the letter U is byte 0 and the letter O is the byte 7 Besides this the memory access must be done carefully as the variables with higher number of bits WORD DWORD LONG use as ind
46. application tasks It is also important to note that to avoid the generation of several events in a very short space of time that was limited the treatment of this type of event in every 10 ms i e if two or more events occurs during 10 ms after the first event the second and subsequent events are discarded This limitation is imposed to prevent an external event that is generated in an uncontrolled way do not block the CPU since the task has a higher priority over the others To configure an external event is necessary to insert a digital input module NX1001 or NX1005 and perform the configurations described below in the CPU through the software programming tool MT8500 General Parameters Bus Event Configuration Select Bus Event Module Address Name ROOSO4 NX1001 X Bus Event Mapping IO_EVT_0 I0 Rising Edge X IO_EVT_1 No Event Source I0_EVT_2 No Event Source mi IO_EVT_3 No Event Source IO_EVT_4 No Event Source v IO_EVT_5 No Event Source IO_EVT_6 No Event Source v IO_EVT_7 No Event Source z 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 In
47. e Gateway Address Ethernet Port Parameters Cluster IP Addressing Method Active IP ov Cluster IP Addressing IP Address Active 192 168 15 68 IP Address PLC A Non Active 192 168 15 69 IP Address PLC B Non Active 192 168 15 71 Subnetwork Mask 255 22595 255 Gateway Address 192 168 15 253 Advanced Figure 6 12 Active IP method NX5000 Parameters that must be configured in the Active IP method for the NX5000 Ethernet modules e IP Address Active Active PLC communication address Replaces the IP address from the Non Active PLCX e IP Address PLC A Non Active PLCA communication address when in Non Active state e IP Address PLC B Non Active PLCA communication address when in Non Active state e Subnetwork Mask e Gateway Address Multiple IP The Multiple IP method can be configured in the Ethernet interfaces from the NX5000 Ethernet modules In this method there s an IP for each half cluster and for each state of the PLC The PLCA assumes an IP address when it s Active and another when it s Non Active The same happens for the PLCB regarding its state Active or Non Active Ethernet Port Parameters Cluster IP Addressing Method Multiple IP X Cluster IP Addressing IP Address PLC A Active 192 168 15 68 IP Address PLC A Non Active 192 168 15 69 IP Address PLC B Active 192 168 15 7 IP Address PLC B Non Active 192 168 15 71 Subnetwo
48. n wicsccccccccccsscesecosesccesesssesessvevccecesecssevesevecevesecshevesenedecesessdevesesececesessiecesesesectess 55 ONY E E E E AEE TEE TETTERE RERET EE AA 55 COME EE EE EO 58 Ethernet Interfaces Configuration sesssososocssecssoooccoccecessooosocesecssoosscecsescsosossocceessoososecesssesosssseeeessssssssoe 60 Cocal Ethernet Interi Cee 5 cc 22h oct a0 AEA AEA AEA AEA AEA AEAEE AAAA 60 Remote Ethernet Interfaces aa aa A EAA AAA AEAEE AAA AAAA AAAA AEAEE 61 Reservede TCP Ports o6 oe TD DD ID IN E A OSs By 61 NX5000 Moduile Configtration scccucciesscssstesconnscnsecssbessenssenndecsdtensonsdenndecsdeensenssenedessdeessenssenesecsdeesseessteates 61 Protocols COmM ULATION sseccicceccscvsscscocescctcsevavavcccescctssevavatcececcetssevasadcecsscessseeaveccececcetcseteveccecessessseseceueecesess 63 IMO DB SRM AS Reo rts cs re ere eE A E E EEE E EE oT Te AE ELE 65 MODBUS RTU SLAVE a e e arer En EEEE EEEE E EE EEO EEEE E E EEE EEEE 79 1 BJ 51 Ohm DE E EEEE 87 Communication Performance ssc s s e3sd0n8 Ia I aa I ISISI ISISI ISISI ISASI 111 MODBUS Client Relation Start in Acyclic Form eeeeseseeseseressssrersssreesssrrerssriesssrresserieesssreerssrresseres 113 System Performante seciscrcsiesdsciscesscnsennscesdsecssensecedcssdsdessunsecesesedsesssnedecesescdscsdededeecsesesscedesedencdesessesessentedetsse 113 RRS E ET SESS AA AAAA AA mess 114 Memory Catd aienea apena aeneae a eae e ea Oe e EER E Oee aeS REEE 115 RTE CICK re sicsesctscc
49. non condensing Conformal coating Yes IP Level IP 20 IEC 61131 2 IEC 61131 3 CE Electromagnetic Compatibility EMC and Low Voltage Standards C LVD 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 CET Weight with package 400g 2 Technical Description Table 2 4 Common Features Notes Tasks Task is an object used to call POUs A Task can be triggered by period events or can run in freewheeling mode Each task can call one or more POUs Real Time Clock RTC The retention time time that the real time clock will continue to update the date and time after a CPU power down is 15 days for operation at 25 C At the maximum product temperature the retention time is reduced to 10 days Isolation Logic is the name of internal circuits such as processor memory and bus interfaces Conformal coating The covering of electronic circuits protects internal parts of the product against moisture dust and other harsh elements to electronic circuits Specific Features Addressable input variables memory l 32 Kbytes 64 Kbytes 96 Kbytes Total addressable output variables memory 32 Kbytes 64 Kbytes 96 Kbytes Q Retain Addressable output variables 8 Kbytes 16 Kbytes 16 Kbytes memory Q Persistent Addressable output variables 8 Kbytes 16 Kbytes 48 Kbytes memory Q 736 Kbytes Total redundant data memory Addressable input variables memory
50. respond to a request To process and transmit a response a MODBUS RTU Slave will takes cycles cycle time of the MODBUS task whereas a MODBUS Ethernet Server task takes only one cycle But this is the minimum time between receipt of a request and the reply If the request is sent immediately after the execution of a task MODBUS cycle time may be equal to 2 or 3 times the cycle time for the MODBUS slave and from 1 to 2 times the cycle time for the MODBUS server In this case Maximum Response Time 3 cycle time time of execution of the tasks time interframe chars send delay For example fora MODBUS Ethernet Server task with a cycle of 50 ms an application that runs for 60 ms every 100 ms the server is able to run only one cycle between each cycle of the application On the other hand using the same application running for 60 ms but with an interval of 500 ms the MODBUS performs better because while the application is not running it will be running every 50 ms and only each cycle of MainTask it will take longer to run For these cases the worst performance will be the sum of the Execution Time of the user application with the cycle time of the MODBUS task 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 pol
51. riable declared ina program or GVL Coil Input Status Holding Register Input Register Data Initial Starting address of the Data Type MODBUS data type Absolut Data Start address of absolut data Start Address of Modbus as its type Size of the MODBUS data 1 to 65536 Data Range The data range address configured Table 4 56 MODBUS Ethernet Mappings Configuration Notes Variable Value this field is used to specify a symbolic variable in MODBUS relation Data Type this field is used to specify the data type used in the MODBUS relation Data Initial Address data initial address of the MODBUS relation Absolut Data Start Address Absolute start address of the MODBUS data according to their type For example the Holding Register with address 5 has absolute address 400005 This field is read only and is available to assist in Client Master MODBUS configuration that will communicate with this device The values depend on the base address offset of each data type and allowed MODBUS address for each data type Data Size the Data Size value sets the maximum amount of data that a MODBUS relation can access from the initial address Thus in order to read a continuous range of addresses it is necessary that all addresses are declared in a single relation This field varies according to the configured type of MODBUS data Data Range is a read only field and reports on the range of addresses that is being used by this mapping It
52. s executed in both CPUs On the other hand ActivePrg is only called when the RedDgnLoc RedState Active condition is true in other words when the CPU is in active state However the NonSkippedPrg program is executed in both CPUs PLCA and PLCB independent on the redundancy state of this CPU On the other hand the ActivePrg is executed only in the active CPU Opposite to the MainPrg which must not be modified the user may modify the NonSkippedPrg and ActivePrg programs Initially when the redundant project is created from the Redundancy Template these two programs are created empty but after that the user may insert his code ATTENTION When the OPC option is enabled when creating the project the NonSkippedPrg program is not created empty For more information refer to the OPC Usage section in Redundant Projects ActivePrg Program The main goal of this program which is executed only in the active CPU is to control the final user process This program normally acts on the redundant variables among which the direct representation variables are found I and Q associated to the remote I O system For further information see the chapter Redundant CPU Programming MainTask Configuration ActivePrg Program ATTENTION The compilation being successful or not Mastertool informs the calculed looseness and the redundancy overhead predicted on the message window ATTENTION The compilation bei
53. 16 Write Multiple Registers 22 Register Write Mask 23 Read Write Multiple Registers Communication period ms 0 to 3600000 Initial Address of Initial address of the the Read Data MODBUS read data 1710 65536 Read Data Size Size of MODBUS Read data Depends on the function used Read Data Range ke Read dataaddress 0 to 2147483646 1 to 65536 Initial Address of Initial address of the the Write Data MODBUS write data Write Data Size Size of MODBUS Write data ooo Depends on the function used 0 to 2147483647 Name of a variable declared in a program or GVL Field for symbolic variable used to disable individually MODBUS requests configured This variable must be of type BOOL The variable can be simple or array element and can be in structures a MODBUS Write data address Write Data Range range Diagnostic Variable Diagnostic variable name Variable used to disable Disabling Variable MODBUS relation Table 4 25 MODBUS Master Relations Configuration 71 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 Function Type Description 1 owm Read coils FC 01 2 0x02 Read input status FC 02 3 oo Read holding registers FC 03 4 o Read input registers FC 04 abes 5 005 Write coil F
54. 28 QW n 28 QW n 28 QW n 30 QW n 30 QW n 30 QW n 32 QW n 32 QW n 32 QX n 34 QX n 34 QX n 34 QX N 36 0 QX n 36 0 QX n 36 0 QX n 36 1 QX n 36 1 QX n 36 1 QX n 35 0 QX n 37 0 QX n 35 0 QX n 35 1 QX n 37 1 QX n 35 1 DWORD BYTE ARRAY 4 BYTE ARRAY 4 BYTE ARRAY 4 BIT BIT WORD BYTE BYTE 309 DG_Modulo tDetailed AT Variable Target dwCPUModel Target abyCPUVersion Target abyBootloaderVers ion Target abyAuxprocVersion Hardware bAuxprocFailur e Hardware bRTCFailure Hardware bThermometerFailure Hardware bLCDFailure Exception wExceptionCod e Exception byProcessorLo ad byReserved_0 RetainInfo byC PUInitStatu s RetainInfo wC PUColdStar tCounter RetainInfo wCPUWarmStartCounter RetainInfo wCPUHotStartCounter RetainInfo wRTSResetCounter RetainInfo wReserved_0O Reset bBrownOutReset Reset bW atchdogReset Thermometer bOverT emperatureAlarm Thermometer bUnderT emperatureAlarm NX3010 0x3010 NX3020 0x3020 NX3030 0x3030 Firmware version Bootloader version Auxiliary processor version Failure in the communication between the auxiliary processor and the principal processor The main processor is not enabled to communicate with the RTC CPU s clock Failure in the communication between the thermometer and the main processor Failure in the communi
55. 80 Kbytes l Addressable output variables memory 80 Kbytes Q Addressable variables memory M 64 Kbytes Symbolic variables memory 512 Kbytes evo members ft Maximum number of expansion bus number of expansion bus Co el Ethernet TCP IP local interface TCP IP local interface Maximum number of additional Ethernet 2 TCP IP interface modules Ethernet TCP IP interface redundancy Maximum number of PROFIBUS DP network using master modules 1 4 4 PROFIBUS DP PROFIBUS DP network redundancy E OE E Redundancy support half clusters support half clusters Event oriented data reporting SOE gt 5 Protocol DNP3 DNP3 Maximum event queue size 1000 1000 Data base size 1 to 1000 bytes 1 to 1000 bytes Clock synchronization SNTP 10 2 Technical Description Current consumption from backplane rack power supply 800 mA 1000 mA 1000 mA Power dissipation Table 2 5 Specific Features Notes Addressable input variables memory I Area where the addressable input variables are stored Addressable variables means that the variables can be accessed directly using the desired address For instance IBO IW100 Addressable input variables can be used for mapping digital or analog input points As reference 8 digital inputs can be represented per byte and one analog input point can be represented per two bytes Total addressable output variables memory Q Area where the addressable output va
56. Ae eee eee 299 Diagnostics Via LE DD oo aoia ncaa ane EE Canes EE EE E ans eas auc EE herrea ane 302 Diagnostics va WEB serere peere cess ssencesvsiencpsssienspeosuesspeociescpevcbosepevebeyedevobinebevebusepavebascpavsbescpaeavevspebes 303 Diagnostic EXpl reiieereiiteeeneri tenein eeann EEEE E a e eE E ea a e aE AEE 305 Summary Diagnostics via V ariables sient activa ssiaviresiaeii eisai aerated 306 Diagnostics via Function Blocks eeescccessseeeceessececeessaeeecessseeecesseeecsesaeeesesaeeeeessaaeesessaeeseesaaeees 317 Graphic Dis play 3 235202 2 0sscededestsesccsssvecosccesescsccesescsccetesssccstesesacecesdvaceceseeesecessseseccsssoscessocescessoceccsestsusctesseese 319 SV SLEMI OG 255 2555 ses sesssaaescassostssvouas vucesnoss ye sbuauuneasnesevess seen sonsnesevesssoasseaneessvospsoas senses sosssssonscaeee T E 321 Not Loading the Application at Startup ssccsscssssssssssscsssssscccsscssesssscsscssesssscesssscsescsscssessssssseseess 321 Power SUPPLY Hamre sisscsssccssecscsshsst tennnsaccssscsousssaccnasssesseursenennanssssseecsecevenessessversvuntenessecsvecssensencsseesorssessues 321 Common Problems iisi ccciccesectsccscccesssvcccacesesccuceseavcacesveccasessencacesvencecesssntesesesssocesessduscssceseeasscsdccassevsecaseevexve 322 EPOUDICSHOOUIE seee ereas eE seee etere cecueveveesesss csuceveceesesss ctucevcocuentocs ceucescsevsntocecevceseseventicecesseseuenentcets scorers 323 Preventive Maintenance 50
57. Blinks 4x LED DG Blinks 2x module Application Run Application Run Application Run Application Stop Application Run Non declare LED DG Blinks 4x LED DG Blinks 2x LED DG Blinks 2x LED DG Blinks 4x LED DG Blinks 2x a ad Application Stop Application Run Application Run Application Stop Application Run Absent tiedula LED DG Blinks 2x LED DG Blinks 2x LED DG Blinks 2x LED DG Blinks 4x LED DG Blinks 4x Application Run Application Run Application Run Application Stop Application Stop Absent module LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 2x LED DG Blinks 4x LED DG Blinks 4x start condition Application Stop Application Stop Application Run Application Stop Application Stop Incompatible LED DG Blinks 2x LED DG Blinks 2x LED DG Blinks 2x LED DG Blinks 4x LED DG Blinks 4x configuration Application Run Application Run Application Run Application Stop Application Stop Incompatible configuration start condition Duplicated slot LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x address Application Stop Application Stop Application Stop Application Stop Application Stop Non operational LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x LED DG Blinks 4x module Application Stop Application Stop Application Stop Application Stop Application Stop Table 4 3 Hot Swap and Conditions Relations LED DG Blinks 4x LED DG Blinks 4x LED
58. CPU 3 3 to Memon Card Copy the project from the CPU internal Disabled Enabled Configuration enabled memory to the memory card Disabled Configuration disabled Password to Copy i Project from CPU to a wora E coping the project a 6 digits password 0 to 999999 Memory Card internal memory to memory car Copy Project from Copy the project from the memory card to Disabled Enabled Configuration enabled Memory Card to CPU the CPU internal memory Disabled Configuration disabled Password to Copy pi Password for coping the project from the As ce pest Memory memory card to the CPU internal memory Sdigits password 0 to 999999 Table 4 4 CPU Project Parameters 47 4 Configuration After setting the project copy possibilities and having created the startup application it must be found the Application crc file in order the configurations concerning the memory card have effect The search can be done at Select Application cre through the Locate File key as can be seen on Figure 4 48 External Event Configuration The external event is a feature available in the CPU which enables a digital input configured by the user when activated triggers the execution of a specific task with user defined code Thus it is possible that through this input when triggered interrupt the execution of the main application and run the set application in the task ExternInterruptTask00 which has higher priority than other
59. Configuration Ethernet Interfaces Configuration chapter The NET 2 Ethernet interface available only in NX3020 and NX3030 CPUs is used only for Ethernet communication and comes with the following default parameters configuration Subnetmask assas OO Table 3 2 Default Parameters Configuration for Ethernet NET 2 Interface The IP Address and Subnet Mask parameters can be seen on the CPU graphic display via parameters menu as described in Configuration CPU s Informative and Configuration Menu chapter 21 3 Installation The NET 2 interface parameters can be modified via MasterTool IEC XE For further information regarding configuration and parameters modifications see Configuration Ethernet Interfaces Configuration chapter Gratuitous ARP The NETx Ethernet interface promptly sends ARP packets type in broadcast informing its IP and MAC address for all devices connected to the network These packets are sent during a new application download by the MasterTool IEC XE software and in the CPU startup when the application goes into Run mode 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
60. DWORD DWORD BYTE BYTE DWORD ARRAY 32 DWORD 313 Ethernet NET2 wRXFrameErrors Ethernet NET2 wMulticast Ethernet NET2 wReserve do Ethernet NET2 wReserve d1 UserFiles byMounted UserFiles dwFreeSpacek B UserFiles dwTotalSizekB UserFiles byReserved_0 UserLogs byMounted UserLogs wFreeSpacekB UserLogs wT otalSizekB UserLogs byReserved_0 MemoryCard byMounted MemoryCard bMemcardtoC PUEnabled MemoryCard bCPUtoMemcardEnabled MemoryCard dwFreeSpacekB MemoryCard dwT otalSize kB WHSB byHotSwapAndStartupSta tus WHSB byReserved_0 WHSB adwRacklOErrorStatus Counter of errors of frame in the reception through NET 2 port 0 to 65535 Counter of multicast packages through NET 2 port 0 to 65535 Reserved Reserved Indicates if the memory used for recording user files is able to receive data Free memory space for user files in Kbytes Storage capacity of the memory of user files in Kbytes Reserved Status of memory in which are inserted the user logs Free space in the memory of user logs in Kbytes Storage capacity of the memory of user logs in Kbytes Reserved Status of the Memory Card 00 Memory card not mounted 01 Memory card inserted and mounted Protection level of the Memory Card Data reading of the memory card by the authorized CPU Data writing in the memory card by the authorized CPU Free space in the Memory Card in Kbyte
61. END VAR INPUTS Purge Queue REQUEST TRUE Purge Queue PORT Port FUNCTION Purge Queue OUTPUTS Purge Queue DONE Purge Queue EXEC Purge Queue BRROR Status Purge Queue STATUS Tf 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 SERIAL_RX RX_REMAINING Figure 4 57 Block Used to Read the Reception Buffer Values Input parameters Type This variable when true enables the function Select the serial port as described in the PORI SERIAL PORT SERIAL_PORT data type RX_BUFFER_POINTER POINTER TO BYTE Apy of a byte array to receive the buffer Specify the expected character number in the byte array In case more than the expected bytes are available only the expected quantity HX BUFFER LENGTH SINT will be read from the byte array the rest will be leaved in the RX queue maximum size equal to 1024 characters Specify the time out to receive the expected character quantity In case it is smaller than the necessary to receive the characters the RX_TIME OUT UINT RX_TIME OUT_ERROR output from the STATUS parameter will be indicated When the specified value in ms is equal to zero the function will return the data within the buffer Tab
62. Expert Custom and Machine profiles respectively Values The number defined for each task type represents the maximum values allowed WHSSB Task The WHSB is a system task that must be considered so the total value is not surpassed NETs Client or Server Instances The maximum value defined considers all system Ethernet interfaces including the expansion modules when these are applied E g MODBUS protocol instances COM n Master or Slave Instances The n represents the number of the serial interface Even with expansion modules the table value will be the maximum per interface E g MODBUS protocol instances Total The total value does not represent the sum of all profile tasks but the maximum value allowed per CPU Therefore the user can create several task types while the established numbers for each one and the total value are not surpassed 198 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 15 and configure the field as described in the CPU Configuration chapter Nexto project MasterTool IEC XE File Edit View Project Build Online Debug Tools Window Help Aa eB T 1S Devies ax Start Page i Configuration Gus jij NX3010 Neto x Devic
63. J Name MODBUS Symbol RTU Slave Vendor Altus S A Groups MODBUS Slave Version 1 0 0 0 Model Number Description MODBUS RTU Slave Append selected device as last child of cOM1 You can select another target node in the navigator while this window is open __AddDevice __Close Figure 5 20 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 21 202 5 Initial Programming File Edit View Project Build Online Debug Ic dh 8 ia ME AE J Device NX3010 PLCLogic Application 3 Bill of Materials Diagnostics i il Library Manager E MainPra PRG Task Configuration MainTask Configuration Bus J nx3010 Nx3010 B Configuration and Consumption a Diagnostic Explorer com1 com2 Figure 5 21 Adding the Instance Neta Cut Copy 3 Paste Delete Properties Add Object l Add Folder i Edit Object Edit Object With Simulation T 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 o
64. NETWORK 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 PROC AUX Informative RETURN Return level CARD gt CPU Configurable CPU gt CARD Configurable FORMAT Configurable RETURN hr ae Return level RETURN 2 ee Sad Return level Table 4 76 CPU Menu Levels SOFTWARE MEM CARD 127 4 Configuration Notes Memory Card the memory card is only available in the menu if it is connected in the Nexto CPU Password the memory card data access password is only necessary in case it is configured in the MasterTool IEC XE software You cannot edit the password via menu Network the NET 2 interface items are only available in the NX3020 and NX3030 CPUs Redundancy the Redundancy menu will only be available in case the NX3030 CPU is identified as Redundant As shown on Table 4 76 between the available options to visualize and modify are the main data necessary to user as e Information about the hardware resources o TEMPERATURE CPU Internal temperature Ex 36 C 97 F o CONTRAST Contrast setting of the CPU frontal display o DATE AND TIME Date and time set in the CPU Ex 2001 01 31 00 00 e Changing the menu language on the CPU o PORTUGUESE Changes the language to Portuguese o ENGLISH Changes the language to Englis
65. NX3020 and NX3030 have pattern pin outs which are the same used in PCs The connector type cable type physical level among other details regarding the CPU and the Ethernet network device are defined in the Technical Description Ethernet Interfaces Configuration Figure 3 2 and Table 3 3 present the RJ 45 Nexto CPU female connector with the identification and description of the valid pin out for 10Base T and 100Base TX physical levels lal Figure 3 2 RJ45 Nexto CPU Female Connector PIN 8 PIN 1 SRR sigrar eseription CSCS C a mo bata transmission postive 2 mo ata transmission negate e xos Daarecepion postive La onal 6 mo Data reception negate Oe w os S Table 3 3 RJ45 Nexto CPU Female Connector Pin out The interface can be connected in a communication network through a hub or switch or straight from the communication equipment In this last case due to Nexto CPUs Auto Crossover feature there is no need for a cross over network cable the one used to connect two PCs point to point via Ethernet port 22 3 Installation It is important to stress that it is understood by network cable a pair of RJ45 male connectors connected by a UTP or ScTP cable category 5 whether straight connecting or cross over It is used to communicate two devices through the Ethernet port These cables normally have a connection lock which guarantees a perfect connection between the
66. Nexto project MasterTool IEC XE Lele z Eie Edit View project Libraries Buld Onine Debug Tools Window Help BLAM Awalo Devices ax StartPage i Configuration Bus f Library Manager x Gl Neto X a Name Namespace Add ibrary J Device Nx3010 e J SN PLcLagie NextoStandard WAA NextoStandard F D 2G NX3010 Diagnostic Structs WAA NX3010_Diagnostic_Structs Application BilofMaterias Standard System Standard B Configuration and Consumption EB Diagnostic Explorer Diagaastics D Library Manager Add Librar eae E Manera RG a za Task Configuration a Aee maintask i i J Configuration Bus a Application J Nx3010 N3010 a Common com1 Control com2 Diagnostics NETI 9 Network P NextoSerial w Group by category be ds a Ges Current user nobody Figure 5 18 Inclusion of a Library in the Project After the desired library must be selected for project inclusion when the button OK must be pressed Inserting a Protocol Instance The Nexto Series CPUs as described in the General Features chapter offer protocols as the MODBUS The desired protocol instance must be added and configured in the communication interface as shown in the Protocols Configuration chapter Two cases of MODBUS protocol insertion are described below one in the serial interface and the other in the Ethernet interface 200 5 Init
67. Os fieldbus interfaces and many other modules on the application In addition it has user register system services and ease at debbuging and tasks management reducing the application cost and installation time Finally Nexto Series CPUs feature several communication interfaces such as serial and Ethernet ports a memory card interface and full IEC 61131 3 programming languages Oc MEM Figure 1 1 CPU NX3030 1 Introduction Nexto Series Nexto Series is a powerful and complete series of Programmable Controllers PLC directed to satisfy the necessities of small and middle sized applications as well as high level applications The series has many features and brings the best cost benefit both for great process automations and machinery automations Nexto Series is based in a modular system which allows flexibility between performance and cost Nexto Series architecture has a great variety of input and output modules These modules combined with a powerful 32 bits processor and a high speed bus based on Ethernet fit to several application kinds as high speed control for small machines complex distributed processes redundant applications and systems with a great number of I O as building automation Furthermore Nexto Series has modules for motion control communication modules encompassing the most popular field networks among other features Nexto Series uses an advanced technology in its bus which is based on a high speed
68. PROFIBUS PO5064 e Portuguese Cabe a Redundante PROFIBUS PO5065 MU209020 Manual de Utiliza o Rede HART sobre PROFIBUS Table 1 1 Related Documents 1 Introduction Visual Inspection Before resuming the installation process it is advised to carefully visually inspect the equipments verifying the existence of transport damage Verify if all parts requested are in perfect shape In case of damages inform the transport company or Altus distributor closest to you CAUTION Before taking the modules off the case it is important to discharge any possible static energy accumulated in the body For that touch with bare hands on any metallic grounded surface before handling the modules Such procedure guaranties that the module static energy limits are not exceeded 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 or send an email to altus altus com br If the equipment is already installed you must have the following information at the moment of support requesting e The model of the used equipments and the installed system configuration e The
69. Redundancy Parameters To understand these parameters the sections Redundant and Non redundant I Variables Redundant and Non redundant I Variables and Redundant and Non redundant I Variables must be read The following parameters must be configured Configuration Redundancy M memory offset Redundancy M memory length Redundancy l memory offset Redundancy l memory length Redundancy Q memory offset reserved for I O drivers Redundancy Q memory length reserved for I O drivers Redundancy Q memory offset Description Redundant M memory initial address Redundant M memory size Redundant l memory initial address Redundant l memory size Q redundant memory offset reserved for I O drivers initial address Q redundant memory offset reserved for I O drivers size Q redundant memory offset reserved for Memory M 0 disabled Memory l 0 disabled Memory Q 0 disabled 16384 65536 0 to 81919 264 0 to 81920 6 Redundancy with NX3030 CPU reserved for diagnostics initial diagnostics address Redundancy Q Q redundant memory offset reserved for 0 to 81920 diagnostics size memory length reserved for diagnostics Table 6 3 NX4010 parameters VO Drivers Configuration The configuration of I O drivers at first isn t different in relation to a non redundant CPU What can be observed is that some I O drivers have commands whic
70. SERIAL RX Port SERIAL PORT COM1 Buffer Pointer ARRAY 0 1023 OF BYTE Max size Status SERIAL STATUS END_ VAR INPUTS Receive REQUEST TRUE Receive PORT Port Receive RX_BUFFER_ POINTER ADR Buffer Pointer i Receive RX BUFFER LENGTH 1024 Max size Receive RX_ TIMEOUT 10000 FUNCTION Receive OUTPUTS Receive DONE Receive EXEC Receive ERROR Status Receive STATUS Tf it s necessary to treat the error Receive RX RECEIVED Receive RX REMAINING 140 4 Configuration SERIAL_RX_EXTENDED This function block is used to receive a serial port buffer using the RX queue extended mode as shown in the Serial Interfaces Configuration section SERIAL_RX_EXTENDED REQUEST DONE PORT EXEC RX_BUFFER_POINTER ERROR RX_BUFFER_LENGTH STATUS RX_TIMEOUT Rx_RECEIVED Figure 4 58 Block Used for Reception Buffer Reading Input parameters Type This variable when true enables the function Select the serial port as described in the FORT SERIAL FORT SERIAL_PORT data type POINTER TO RX_BUFFER_POINTER SERIAL RX CHAR_E Pointer of a SERIAL_RX_CHAR_EXTENDED array to receive the buffer values XTENDED Specify the expected character number in the SERIAL_RX_CHAR_EXTENDED array In case more than the expected bytes are RX_BUFFER_LENGTH UINT available only the expected quantity will be read from the byte array the rest will be leaved in the RX queue ma
71. Series CPUs Similarly to use this feature is required MasterTool IEC XE version 1 40 or later MODBUS RTU MASTER This protocol is available for the Nexto Series CPUs in its serial channels By selecting this option at MasterTool IEC XE the CPU becomes MODBUS communication master allowing the access to other devices with the same protocol when it is in the execution mode Run Mode There are two configuration modes for this protocol One makes use of Direct Representation Q in which the variables are defined by its address The other called Symbolic Mapping has the variables defined by its name Regardless of the configuration mode the steps to insert a protocol instance and configure the serial interface are the same The procedure to insert a protocol instance is found in detail in the MasterTool IEC XE User Manual MU299048 or in the chapter Inserting a Protocol Instance The remaining configuration steps are described below for each mode e Add the MODBUS RTU Master Protocol instance to the serial channel COM 1 or COM 2 or both in case of two communication networks e To execute this procedure see Inserting a Protocol Instance chapter e 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 e See Configuration Serial Interfaces Configuration chapter 65 4
72. Statistics transmitted by the client 0 to QW n 4 wT XRequests 65535 Counter of normal answers QW n 6 wRXNormalResponses WORD received by the client 0 to 65535 Counter of answers with QW n 8 wRXExceptionResponses WORD exception code 0 to 65535 tStat Counter of illegal answers received by the client invalid QW n 10 wRxillegalResponses WORD syntax invalid CRC or not enough bytes received 0 to 65535 WORD WORD WORD WORD Table 4 41 MODBUS Client Protocol Diagnostics Reserved BI BI I I I I T T BIT BIT BIT BIT BIT Counter of number of requests 90 4 Configuration Note Counters all MODBUS TCP Client diagnostics counters return to zero when the limit value 65535 is exceeded Device Configuration Configuration via Symbolic Mapping The client devices configuration depicted on Table 4 42 follow the parameters reee eaer Settings IP Address 0 0 0 0 TCP Port 502 Slave Address 1 5 Advanced Figure 4 27 Device General Parameters Settings IP Address Server IP address 0 0 0 0 0 0 0 1 to 255 255 255 254 TCP Port TCP port 502 2 to 65534 Slave Address MODBUS Slave address a 0 to 2147483644 Table 4 42 MODBUS Client General Configurations 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 in
73. The method used to ignore the diagnostics possibly invalid is described in section Reading Non Redundant Diagnostics Failures which Cause Automatic Switchovers between Half Clusters In this section the more common failures which automatically cause a switchover from the Active CPU to Non Active and from Stand by CPU to Active CPU are listed These failures trigger a sub group of those transitions examined in the Transition between Redundancy States section e Power supply fault in the Active CPU It s important that both CPUs have redundant power supplies in order to avoid that a power supply failure doesn t affect the Stand by CPU e NX8000 power supply fault in the Active CPU e Rack bus failure NX9001 NX9002 or NX9003 in the Active CPU e 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 e Failures in the NX4010 from the Active PLC such as o Not recognized module in the NX3030 CPU bus o Failure in the NX4010 microprocessor which prevents the NETA NETB and the PX2612 control panel buttons LEDs and relay internal diagnostics updating o Internal failures that affect one or both synchronization channels NETA and NETB 250 6 Redundancy with NX3030 CPU e Active PLC PROFIBUS network total failure in case this network is configured in vital mode In case the PROFIBUS n
74. This procedure is done only when the card is inserted or in case of the CPU reset ATTENTION It is recommended to format the memory card directly in the Nexto CPU in order to avoid possible use problems mounting time increase or even the incorrect functioning It is not recommended to remove the memory card or de energize the CPU during the formatting or during the files transfer as it can cause the loss of data as well as irreversible damages During the project configuration in the MasterTool IEC XE software the user enables the CPU project copy option for the memory card or the project copy from the card to the CPU On this same screen the user can configure the passwords which control the information use For further information regarding the table see Project Parameters chapter 124 4 Configuration a Eceo Memory Card Copy Project from CPU to Memory Card Di bled Password to Copy Project from CPU to Memory Card Copy Project from Memory Card to CPU Disabled Password to Copy Project from Memory Card to CPU Lox _cancal_ Create Boot Nexto mcf Use this option after create boot application Select the Application cre Find File Figure 4 48 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 incl
75. a Protocol Instance section MODBUS Server Ethernet Protocol Configuration for Symbolic Mapping To configure this protocol using Symbolic Mappings it is necessary to execute the following steps e Configure the MODBUS server protocol general parameters as TCP port protocol selection IP filters for Reading and Writing available at the Filters Configuration button and communication times available at the Server Advanced Configurations button e Add and configure MODBUS mappings specifying the variable name data type data initial address and data size The description of each configuration is related ahead in this chapter MODBUS Server Protocol General Parameters Configuration via Symbolic Mapping The general parameters found on the MODBUS protocol configuration initial screen Figure 4 34 are defined as 102 4 Configuration General Parameters Settings TCP Port 502 Filters Advanced Connection Mode TCP Figure 4 34 MODBUS Server General Parameters Configuration Screen RTU via TCP Connection Mode Protocol selection TC Table 4 52 Configurations Notes 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 The setti
76. a number between 1 and 4 be redundant the two networks that belongs to this are named PROFIBUS n A and PROFIBUS n B In case the PROFIBUS n be single the network that belongs to it will be named PROFIBUS n A To create a redundant PROFIBUS network must be inserted two NX5001 modules in each half cluster To create a simple PROFIBUS network simply insert a NX5001 module in each half cluster Thus it can be configured up to four simple networks or two redundant networks or a redundant and two simple In other cases fewer than four NX5001 modules will be needed in each half cluster More information about PROFIBUS networks is provided in the PROFIBUS Network Configuration section In Figure 6 1 there is only one PROFIBUS network PROFIBUS 1 and the same is redundant PROFIBUS 1 A and 1 B PROFIBUS In this example therefore were inserted two NX5001 modules in each half cluster NX5000 Modules Addition for Ethernet Networks It s possible to insert up to 6 NX5000 modules in each half cluster delivering 6 additional Ethernet channels besides the 2 Ethernet channels already existent in the NX3030 CPU The Ethernet channels can be used in an individual way or organized in NIC Teaming pairs which are used to deliver redundant Ethernet channels and are described with more details in the Redundant Ethernet Networks with NIC Teaming section A typical application for the NX5000 module can be the construction
77. absent fF FALSE There are no absent racks DUPLICATED TRUE There are racks with a RACK duplicated identification number bDuplicatedRacks FALSE There are no racks with a duplicated identification number TRUE There are racks with an INVALID BACK invalid identification number blInvalidRacks FALSE There are no racks with an invalid identification number ea TRUE There are racks with a non RACK bNonDeclaredRacks declared identification number o FALSE There are no racks with a 307 QB n 3 3 0 3 1 3 2 3 3 7 Maintenance Fro doctarec ideritication number DUPLICATED TRUE There are some duplicated SLOT slot address 3 4 bDuplicatedSlots 3 TRUE There are no duplicated slot address asaa7 bResevegxx Reserved Table 7 6 CPU Summarized Diagnostics Table Notes Direct Representation Variable n represents the value set in the CPU through the MasterTool IEC XE software such as initial address diagnostics AT Directive In the description of the symbolic variables which use the AT directive to make the mapping in direct addressing variables the syntax that must be put before the desired summarized diagnostic is DG_Module tSummarized when the Module word is replaced by the used CPU E g for the incompatible configuration diagnostic it must be used the variable DG_NX3010 tSummarized bConfigMismatch The AT directive is a word reserved in the programming soft
78. an MODBUS Server at Local Interface ATTENTION The communication performances mentioned in this chapter are just examples using a CPU with only one device MODBUS TCP Server with no logic to be executed inside the application that could delay the communication Therefore these performances must be taken as the maximum rates For cycle times equal or greater than 20 ms the increase of the answer rate is linear and may be calculated using an equation N Cx Z Z T x 1000 Z 1 T Where N is the medium number of answers per second C is the number of active connections and T is equal to the cycle time of the MODBUS task in seconds As an example a MODBUS Server with only one active connection and a cycle time of 50 ms we get C 1 T 0 05 s Z 1 0 05 20 N 1 x 20 20 0 05 x 1000 1 x 20 20 50 1 x 20 0 4 1 x 19 6 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 However due to time of the communication between the CPU and the modules the maximum performance is limited For only one active connection the number of answers is limited i
79. be connected to the PLCA and PLCB half clusters The PX2612 is divided in two sections one controlled by PLCA and another by PLCB These controllers are possible through cables AL 2317 A for PLCA and AL 2317 B for PLCB and allow each CPU to read three buttons write on three LEDs and a NO relay contact Observing the frontal view on Figure 6 5 e PLCA executes the STAND BY and INACTIVE buttons reading in PLC A sector e PLCA executes the TURN ON PLC B button reading PLCA executes the writing on the three LEDs ACTIVE STAND BY and INACTIVE from the PLC A sector PLCA executes the writing on the RL B relay used to switch off PLCB PLCB executes the STAND BY and INACTIVE buttons reading in the PLC B sector PLCB executes the TURN ON PLC A button reading PLCB executes the writing on the three LEDs ACTIVE STAND BY and INACTIVE from the PLC B sector e PLCB executes the writing on the RL A relay used to switch off PLCA PX2612 Buttons This section describes the functions of the PX2612 buttons The STAND BY button has the following functions e To request a switching from the Active state to the Stand by state useful when maintenance in the Active CPU is needed After the Active CPU is switched to Stand by and consequently the Stand by CPU is switched to Active it s possible to switched from Stand by to Inactive using the INACTIVE button and then execute the programmed maintenance in the inactive state e To request a confi
80. be replaced when it is restricted to system status verification To access the desired CPU WEB page it is just to use a standard navigator Internet Explorer 7 or superior Mozilla Firefox 3 0 or superior and Google Chrome 8 or superior and type on the address bar the CPU IP address e g Ex http 192 168 1 1 First the CPU information is presented according to Figure 7 3 Firefox X Nexto 19216811 Google Pit we English Espa ol Portugu s CPU Overview System Overview Fimware Update CPU Overview Updated on Sth August 2012 19 00 04 To refresh this page click on the icon NX3030 NX3030 Description my Configured Racks nN o Firmware Version Bootloader Version Auxiliar Processor Version Application State o Active Diagnostics z Forced Values Figure 7 3 Initial Screen 303 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 When the Rack visualization is used the modules that have diagnostics blink and assume the red color as shown on Figure 7 4 Otherwise a list with the system connected modules Tags and active diagnostics number is presented 7 altus Sys
81. be switched off there s the need of a base compatible with the new I O module in the position reserved for it o Parameters modifications in remotes or existent I O modules e Both PLCs projects must be equalized and the Redundant Data Synchronization and Redundant Forcing List services must be working properly with no failure diagnostics It can be stated these conditions are satisfied when there s a PLC in Active state and another in Stand by state In case the Non Active PLC isn t in Stand by state the following diagnostics can be observed o DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bRedDataSync TRUE indicates the success of the Redundant Data Synchronization service o DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bRedForceSync TRUE indicates the success of the Redundant Forcing List service o DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag dwApplicationCRC DG_NX4010 tRedundancy RedDgnRem dwApplicationCRC indicates both PLCs projects are equal Step 2 Don t Download in Group Modifications which can be downloaded On Line Modifications which can be downloaded on line must not be downloaded together with modifications which must be downloaded off line without the process control interruption When these two kinds of modifications are needed they must always be loaded separately For the current procedure to be successful it s absolutely necessary the modifications executed to don t cause any changes in the structu
82. 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 In this case the CPU will remain in active and the other CPU that will go to the inoperative state For these reasons this command bit should not be manipulated by the user in a redundant application For further information regarding PROFIBUS networks configuration see PROFIBUS DP NX5001 Utilization Manual PROFIBUS Remotes Configuration To configure PROFIBUS remotes under a NX5001 master the PROFIBUS DP NX5001 Master Utilization Manual must be consulted together with the following manuals Ponto Series Utilization Manual PROFIBUS PO5063V1 Head Utilization Manual and Redundant PROFIBUS PO5063V5 Head PROFIBUS PO5064 Head Utilization Manual and Redundant PROFIBUS PO5065 Head HART over PROFIBUS Network Utilization Manual For a redundant system we must pay attention to the configuration of the watchdog parameter from the PROFIBUS remote In case that in the remote configuration screen the Watchdog control checkbox is checked the Time field needs to be correctly configured There are two options to configure the Time and we must use the bigger time between e WT gt 1x2 500ms and e WT21x3 Where WT is the watchdog time and Z is the MainTask configured interval Watchdog v Watchdog control a Time ms 1000 Figure 6 23 Watchdog Configuration of a PROFIBUS Remote NX5000 Mo
83. control signal Table 4 83 SERIAL_GET_CTRL Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Get_Control SERIAL GET_CTRL Port SERIAL PORT COM1 Status SERIAL STATUS END_ VAR INPUTS Get_Control REQUEST TRUE Get_Control PORT Port FUNCTION Get_Control OUTPUTS Get_Control DONE Get_Control EXEC Get_Control ERROR Status Get _Control STATUS If it s necessary to treat the error Get_Control CTS_ VALUE Get_Control DSR_VALUE Get_Control DCD_VALUE 136 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 SERIAL_GET_RX_QUEUE_STATUS RXQ_STATUS Figure 4 55 Block Used to Visualize the RX Queue Status Input parameters Type This variable when true enables the function Select the serial port as described in the PORT Seen SERIAL_PORT data type Table 4 84 SERIAL_GET_RX_QUEUE_STATUS Input Parameters Output parameters Type This variable is true when the block is BOOL x completely executed It is false otherwise EXEC BOOL This variable is true while the block is being executed It is false otherwise This variable is true when the block c
84. currently settings applied on the device are loaded in the configuration dialog Gar Load from disk gq Save to disk The current configuration can be stored in an XML file drm and reloaded from this file which is useful to define the same user configuration on multiple systems Thus the standard dialog to search the file system will be provided The file filter is automatically set to drm file device access rights The current settings can also be documented in printed versions via Print command File menu or Document Project menu Access Rights of Old Projects To keep the old project access rights on new projects after the firmware update or in new Nexto CPUs is needed that in the old project with the original firmware execute a Load Device command so seeking the CPU settings and after Save Disk command thus saving the current configuration to a file In the new Nexto CPU or updated CPU run Disk Load command and select the previously generated file finally run the Download command to the device thus sending the settings for the CPU 181 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
85. declared modules only Disabled Enable with consistency in the start only for declared modules Enable with consistency in the start Enabled without consistency in the start TCP IP Parameters Indicates how long after the first transmission of a message it has to be retransmitted assuming it was not received by the destination device Every retransmission the time out is doubled Delay time for a confirmation command sending 0 to 100 Project Parameters Configuration to generate error in the consistency of the watchdog value in case it is higher than 80 of the task interval Table 4 1 CPU Configuration Configuration to consist the addressable persistent and retentive memories Marked It generates an error in case the watchdog value exceed 80 of the task interval value Unmarked It doesn t generate an error case the watchdog exceed 80 of the task interval value Marked It consists the addressable persistent and retentive memories Unmarked It doesn t consist the addressable persistent and retentive memories 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 mo
86. default the SNMP agent is activated i e the service is initialized at the time the CPU is started The access to the information agent is via the Ethernet interfaces NET 1 and NET 2 of the Nexto Series CPUs on TCP port 161 So when the service is active the agent information can be accessed through any one of the two Ethernet interfaces if available It is not possible to provide agent information through Ethernet interfaces NX5000 modules In Figure 4 76 an example is shown SNMP manager in which some values are read 160 4 Configuration File Discover Watch Tools Help PowerSNMP Free Manager om pi pee Agent Address Variable Oid Value oe Sie hacia Variable Watches a SNMPv1 v3_192 168 19 226 sysDesor 1 3 6 1 2 1 1 1 CPU NX3030 6 0 SNMPv2 v3_192 168 19 226 sysName 1 3 6 1 2 1 1 5 nexto default S SNMPv3 v3_192 168 19 226 sysContact 1 3 6 1 2 1 1 4 who where v3_192 168 19 2 v3_192 168 19 226 snmplnPkts 1 3 6 1 2 1 11 1 2972 v3_192 168 19 226 snmpOutPkts 1 3 6 1 2 1 11 2 2952 v3_192 168 19 226 ipinReceives 1 3 6 1 2 1 4 3 1128746 v3_192 168 19 226 iplnDelivers 1 3 6 1 2 1 4 9 1015910 v3_192 168 19 226 iplnReceives 1 3 6 1 2 1 4 3 1128679 v3_192 168 19 226 ipOutRequests 1 3 6 1 2 1 4 10 53509 v3_192 168 19 226 topOutSegs 1 3 6 1 2 1 6 11 v3_192 168 19 226 udpinDatagrams 1 3 6 1 2 1 7 1 S 6 snmpV2 Enterprise OID Generic Trap Specific Trap Figure 4 76 SNMP Manager Example
87. disabled see Project Synchronization Disabling In case this situation doesn t occur a transition from the Not Configured state for the Starting state happens as soon as a configuration request arrives 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 Manually configuration requests typically aren t necessary when a user maintenance is needed before going out from the Not Configured state e g if the CPU hasn t reached the Not Configured state due to some failure After getting out from the Not Configured state the PLC can go back to this state due to events such as e Restarting reset warm cold or origin e PLC switch off e Different projects between this PLC and the Active PLC 243 6 Redundancy with NX3030 CPU Starting State Different from all other 4 states which can last indefinitely the Starting state is temporary taking only a few seconds This state is always reached from the Not Configured state through a configuration request At the beginning of the Starting state several actions tests and verifications are executed in order to decide which will be the next state e PROFIBUS masters are e
88. 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 Furthermore the product may have Utilization Manuals the manuals codes are listed in the CE For instance the NX1001 module has the information for utilization features and purchasing on its CE On another hand the NX5001 has besides the CE a User Manual MU It is advised the following documents as additional information source CE114000 Nexto Series Technical Characteristics English CT114000 S rie Nexto Caracter sticas T cnicas Portuguese CS114000 Serie Nexto Especificaciones y Configuraciones Spanish CE114700 Nexto Series Backplane Racks Technical Characteristics English CT114700 Caracteristicas T cnicas dos Bastidores da S rie Nexto Portuguese CS114700 Caracteristicas T cnicas de los Bastidores de la Serie Spanish Nexto CE114900 NX4010 Redundancy Link Module Technical English Characteristics CT114900 Caracter sticas T cnicas do M dulo de Redund ncia Portuguese NX4010 CS114900 Caracter sticas T cnicas del M dulo de Redundancia Spanish NX4010 CE114902 NX5001 PROFIBUS DP Master Technical Characteristics English CT114902 Caracteristicas T cnicas do Mestre PROFIBUS DP Portuguese NX5001 CS114902 Especificaciones y Configuraciones Maestro PROFIBUS Spanish DP NX5001 CE114903 Ethernet Module NX5000 T
89. during its utilization However regarding the equipments discarded it is important to stress that any electronic components inside these products may cause environmental impacts if discharged incorrectly Therefore it s strongly recommended that the product is sent to recycle plants to be discarded with the proper waste treatment Altus guarantees that its equipment against genuine production defects for a period of twelve months starting at the shipping date This guarantee is given in terms of factory maintenance that is to say the transportation costs of returning to factory will be borne by the client The guarantee will be automatically suspended if there are modifications introduced to the equipment by personnel not authorized by Altus Altus are exempt from any responsibility with regard to repairs or replacement parts owing to faults created by outside influences through inappropriate use as well as the result of accidents or force maneuver Altus guarantees that its equipment works in accordance with the clear instructions contained in their manuals and or the technical features not guaranteeing the success of any particular type of application of the equipment Altus does not acknowledge any other guarantee directly or implied mainly when end customers are dealing with third party suppliers The requests for additional information about the supply equipment features and or any other Altus services must be made in written form Altu
90. eessccececeessVevesencnceveevevevesereecececsevssesueteccvcevsvesdusteccecsessverdvecse 188 OC DaT OTa DII CE A A E A A A E AA 190 OEIT r O I GERR TTT T 191 LERET T TASKS E E E E E E EE 193 Task Confis ratio ox ax a a ee ek ae ick ae os DR amp 195 POU Task Connection sT i n rian nari am ns ena aan 196 Maximum Number of TaskS ccccccccccessssenececeeeeeeeennneeeeceeeeeeessaeeeeceeeeeeeeanaeeeeeeeeeeseenaaeeeeeeeeeeeeeaaaes 197 CPU GCOmMomratiOm viscesch ci cctssccccvcsckccchcccvcncvencucccecccucnasencuencecechcnanencuccesccceceosesenccescccecuescsenccescecsecensueseusnees 199 MSM AVIES wi csi sesdescsassciascuasceuvcsivceiscesadsosdssuisasbesiboscsacsassetuskascsasesssaessssuaivetavedaecsubastbevcbedubsedtasdbancsasacibasisebiesss 200 Inserting Protocol INStance sicscicisccconccscccscsc cssonscteccscssdecssnscbeccscssdescscncbeccscssduecenscbecessssdsssssecbesessscseveussesce 200 MODBUS RTU nh ama etieniionndanaciendenes innominate mando 201 MODBUS Eth rietasnarnnniniieaii iiaii iai ae inter A EEO E E E AT 202 Finding the NOC WORK cis sssess seis cs sesec ae cee esteret erete SEE ETENA dues encncnccceesdvesssencuceseesdueeeseucuensees oeseucben 204 Compiling a PRO JOC iA 22 ics cccsccssccsssessecsescesesenssessvecssesssecseeseceasssvecsessessecesssesscossessssessessecessesseceecsestsucasecesees 206 IT En T EESO OOOO T 207 iid Oa A A a e E r A s unsbausstusivenssebbaunstonsensuaestnees 209 SCOP MOG sii cscccccccccedcscccuctcvesccsst
91. ema 4 bDiag_20_reserved oe 5 bDiag_21_reserved emas 6 bDiag_22_reserved emar 7 bDiag_23_reserved QB n 3 byDiag_03_reserved Reserved Reserved Reserved Counter of normal requests received by the slave and answered normally In case of a broadcast command this counter is incremented but it is not transmitted 0 to 65535 Communication Statistics QW n 4 wR XRequests WORD tStat QW n 6 wT XExceptionResponses WORD 81 Counter of normal requests received by the slave and answered with exception code In case of a broadcast command this counter is incremented 4 Configuration but it isn t transmitted 0 to 65535 Exception codes 1 the function code FC is legal but not supported 2 relation not found in these MODBUS data 3 illegal value for this field 128 the master client hasn t right for writing or reading 129 the MODBUS relation is disabled Counter of frames received by the slave It s considered a frame something which is processed and it is QW n 8 wRXFrames followed by a Minimum Interframe Silence in other words an illegal message is also computed 0 to 65535 Illegal request counter These are frames which start with address 0 broadcast or with the MODBUS slave QW n 10 wRXIIlegalRequests address but aren t legal requests invalid syntax smaller frames invalid CRC 0 to 65535 Counter of frames with overrun errors QW n 12 wRXOverrunErrors
92. examples of this type of modifications supported by the procedure which allow executing modifications off line download without interrupting the process control NX5000 modules insertion Ethernet Ethernet or Serial communication I O driver insertion Ethernet or Serial communication I O driver new mapping insertion MainTask period modification Some simple modifications such as the MainTask period don t demand any previous planning On the other hand the previous examples of modifications imply the direct representation I and Q variables allocation for diagnostics inputs and outputs similar to discussed in step 3 from the previous planning for hot modifications which affect the PROFIBUS network see Step 3 Allocate I and Q Variables Areas for the PROFIBUS Network considering Future Remote Expansion This way at inserting the NX5000 module or an I O Ethernet or Serial driver the allocation of the 3 following areas must be planned for the inserted device e 4 variables area for inputs e 9 Q variables area for outputs e Q variables area for diagnostics The Step 3 Allocate I and Q Variables Areas for the PROFIBUS Network considering Future Remote Expansion section shows an example of group allocation of these areas including PROFIBUS networks and an I O driver Modbus TCP server Incompatibility of Applications If the areas to be used in the future not be planned properly the redundant memory areas may have
93. executed in both CPUs PLCA and PLCB independent on the redundancy state This POU is also called by the main POU MainPrg It must be remembered that all symbolic variables defined in the NonSkippedPrg POU as well as the function blocks instances are non redundant variables The user must create additional POUs program function or function block and call or instance them inside the NonSkippedPrg POU in order to structure his program It s possible to call functions and instance function blocks defined in libraries too 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 If the NonSkippedPrg structure is needed function blocks or functions must be used Typical examples of controls executed in the NonSkippedPrg are the following 266 6 Redundancy with NX3030 CPU e To create a compact diagnostics structure Q to be reported to a SCADA system from a complete diagnostics structure where many diagnostics are not interesting for the SCADA system These diagnostics can be extracted from data structures as RedDgnLoc RedDgnRem RedUsrLoc RedUsrRem etc e To copy commands received from a SCADA system for t
94. in Active state e Both projects 2 CPUs must be identical except when the project automatic synchronization is disabled see Project Synchronization Disabling section e At least one synchronism channel NETA and or NETB must be operational If both synchronism channels NETA and NETB are operational the communication is distributed between both load balances in order to reduce the synchronization time In case only one channel is operational the synchronism will continue to be executed only by this channel keeping the redundant data synchronization ATTENTION The redundant forcing list has only forcing over redundant variables On each CPU PLCA and PLCB there can be a different forcing list related to non redundant variables Sporadic Synchronization Services through NETA and NETB The following synchronization services are executed sporadically in other words they are not executed in each MainTask cycle Another system task executes these sporadic services in background Project Synchronization This service is responsible for synchronizing the Active CPU and Non Active CPU projects This happens when the projects are different in both CPUs and the automatic projects synchronization is enabled on both CPUs The synchronization is always from the Active CPU to the Non Active CPU and it s enough that a one out of two synchronism channel NETA or NETB is operational for this service to be executed When the synchroni
95. in the device terminals DEVICE NX3010 RS 422 NX3020 NX3030 AL 1763 11083001B Figure 3 10 COM 2 with RS 422 Connections with External Termination Diagram Diagram Note The not connected terminals must be insulated so they do not make contact with each other RS 422 Network Example Figure 3 11 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 29 3 Installation Master Slave Slave NX3010 NX3020 NX3030 y AL 2600 Termination Device RS 422 Device RS 422 AL 2600 Termination AL 2600 Splitter AL 2600 Splitter AL 2600 Termination AL 2600 Termination 11052001C Cable AL 2306 Cable AL 2306 Figure 3 11 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 30 3 Installation Memory Card Installation This section presents how to insert the memory card into the Nexto Series CPUs For further information see Configuration Memory Card chapter Initially care must be taken with the correct position the memory card must be inserted One corner of it is different from the other three and this one must be used as reference for the card correct insertio
96. including the possibility to allow a CPU to switch off the other which is necessary in exceptional situations Two AL 2319 cables must be used for the synchronism and redundancy channels NETA and NETB One of these two cables interconnects the NX4010 NET 1 connector from each CPU NETA channel The other cable interconnects the NX4010 NET 2 connector from each CPU NETB channel An AL 2317 A cable interconnects the NX4010 CONTROL connector from the PLCA to the PX2612 CONTROL PLC A An AL 2317 B cable interconnects the NX4010 CONTROL connector from the PLCB to the PX2612 CONTROL PLC B Besides this it s necessary to build a special power supply circuit in order to allow a CPU to switch off the other in extreme cases For higher reliability two separate 24V power supplies must be used one for PLCA supply and other for PLCB supply It can be observed that is necessary to use two external relays from the normally closed type NC with current capacity to feed the NX8000 These relays must be dimensioned for a nominal current around 2A however a current inrush of around 10A must be taken into account Shunt diodes connected to the NC relays solenoids must be used to protect the PX2612 NO relay contacts AL 2319 NETA half cluster PLCB half cluster PLCA NETI NET2 NX4010 CONTROL 24V ov PLCA POWER SUPPLY PLCB POWER SUPPLY Figure 6 6 Interconnections between PLCA PLCB and PX2612 222 6 Redundancy
97. inserted in the first remote rack positions and the future I O modules in the last remote rack positions ATTENTION It must be considered the limitations of the Ponto Series redundant remotes at constructing this list as the PO5063V1 PROFIBUS Head Utilization Manual and PO5063V5 PROFIBUS Redundant Head and PO5064 PROFIBUS Head Utilization Manual and PO5065 PROFIBUS Redundant Head There are limits regarding the number of modules per remote number of bytes per remote current consuming per power supply etc These limits are verified automatically by the ProPonto For further information see the MT6000 MasterTool ProPonto Utilization Manual MU299040 Step 2 Insert the Redundant PROFIBUS Network Initial Version in the Project To insert the redundant PROFIBUS network initial version in the project initially the two redundant NX5001 modules must be inserted in the rack or use those already inserted by the redundancy wizard Next each remote must be inserted in the device tree below these two NX5001 as well as the I O modules under each remote Regarding the inserted I O modules there are two categories that must be treated differently e Those that are part of the PROFIBUS network initial version and will be installed immediately e Those that will be used for future expansion In the case of those that are part of the PROFIBUS network initial version the module itself must be inserted in the device tree in the planned remote
98. interface female connector and the cable male connector At the installation moment the male connector must be inserted in the module female connector until a click is heard assuring the lock action To disconnect the cable from the module the lock lever must be used to unlock one from the other Serial Network Connection COM1 The 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 3 DB9 Female Connector Nexto CPU COM 1 Table 3 4 DB9 Female Connector Pinage Nexto CPU COM 1 Tan sin a 00 2 o s eo sen _ ears o RS 232C Communication For connection to an RS 232C device use the appropriate cable as the chapter Related Products 23 3 Installation Serial Network Connection COM2 The COM 2 isolated communication interface allows the connection to a RS 485 422 network As follows it s presented the DB9 female connector to Nexto CPU with identification and sign description Figure 3 4 DB9 Female Connector Nexto CPU COM 2 sign Description Notused o 7 Table 3 5 DB9 Female Connector Pinage Nexto CPU COM 2 RS 485 Communication without termination COM 2 In order to connect in a RS 485 network with no termination in COM 2 interface the cable AL 1763 identified terminals must be connected in the respectiv
99. interruption to be generated Low UART RX values make the TIMESTAMP more precise when the EXTENDED MODE is used and 1 4 8 and 14 Threshold PESA minimizes the overrun errors However values too low may cause several interruptions delaying the CPU Table 4 13 COM 2 Advanced Configurations 59 4 Configuration Ethernet Interfaces Configuration The Nexto CPUs can provide up to two Ethernet interfaces locations NET 1 and NET 2 The NX3010 CPU has only the NET 1 interface and the CPUs NX3020 and NX3030 have NET 1 and NET 2 In addition to the local Ethernet interfaces the Nexto Series also provides remote Ethernet interfaces by including the NX5000 module The NX5000 modules have only the NET 1 interface Local Ethernet Interfaces NET 1 NET 2 The NET 1 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 IP address of the controller in 1 0 0 1 to Rena eS the Ethernet bus TAOS 255 255 255 254 Sub network Subnet mask of the controller 0 0 0 1 to in the Ethernet bus ea icone dd 255 255 255 254 Controller Gateway address 0 0 0 1 to SEU ETC in the Ethernet bus 192169 13 293 255 255 255 254 Table 4 14 N
100. 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 ATTENTION Unlike other tasks of an application when a mark is reached at MainTask debugging the MODBUS Ethernet Server instance task or any other MODBUS task will stop being executed at the moment it tries to write in the memory area This occurs in order to maintain data consistency of memory areas while MainTask is not running 106 4 Configuration MODBUS Server Ethernet Protocol Configuration via Direct Representation Q To configure this protocol using Direct Representation Q the user must perform the following steps e Configure the general parameters of MODBUS Server Protocol such as communication times address and direct representation variables Q to receive the diagnostics and control relation e Add and configure MODBUS relations specifying the MODBUS data type direct representation variables Q to receive write the data and amount of data to be reported The descriptions of each configuration are listed below in this chapter General Parameters of MODBUS Server Protocol Configuration via Direct Representation Q The general parameters found on the home screen of MODBUS protocol configuration Figure 4 36 are defined below ut Ma rrr File Edit View Project Build Online Debug Tools Window Help acu ca Aiar Devices ax i Configuration Bus J
101. local PLC to StandBy DG_NX4010 tRedundancy RedCmdLoc bStandbyLocal TRUE END_IF END_IF 251 6 Redundancy with NX3030 CPU Note When two Ethernet interfaces form a NIC Teaming pair the inactive interface will always have the IP address 0 0 0 0 This isn t a valid IP and is no possible to configure manually an interface with this address Fault Tolerance The main objective of a redundant CPU is the system availability increase The availability is the ratio between the time while the system is working properly and the total time since the system has been implemented For instance if a system was implemented 10 years ago and during this time wasn t working due to failures for a year then its availability was only 90 This kind of availability is usually unacceptable for critic systems where 99 99 availability is required or even more In order to reach this availability level several strategies are necessary e Utilization of more reliable components with high MTBF or Mean Time between Failures contributing for the MTBF increase of the system as a whole e Utilization of redundancy for at least the most critical components or components with smaller MTBF in such a way that a component failure can be tolerated without stopping the system If the redundancy is implemented through components duplication it will be
102. lt Nobody gt Users Add le Import Groups Oo add Import Figure 4 87 Device Dialog User and Groups Users The following buttons are available to configured user accounts Add the Add User dialog defines a user name and password The password must be repeated in the Confirm Password field ATTENTION When opening this dialogue the Password and Confirm Password fields are filled with fictitious characters the user must replace these characters for a valid password 175 4 Configuration User1 Figure 4 88 Adding User mote The Import Users dialog shows all the names of users currently defined in the project user management Select one or more items and confirm with OK In the Enter Password dialog type the password as defined in management so that the user account is imported into the specific user management device N g The name and the currently selected user account password can be changed The Edit User dialog lt user name gt is the Add User dialog The currently selected user account will be deleted Groups Delete The Add Group dialog sets a new name for this and selects from the currently defined users those who should be part of the group E User usera Figure 4 89 Add Group The Import Groups dialog displays a list of the groups currently defined in the project user management Select one or more items
103. necessary to inform only the size of the events queue This queue is persistent and redundant so the events will not be lost in the switchover moment neither in case of a power supply failure In case an overflow occurs in the events queue the oldest events will be overwritten In case in one single cycle are generated more events than what is supported by the queue its generation is interrupted and the overflow diagnostic is turned on SOE x bOverflowStatus For example if 100 n bits vary in a 100 events configuration causing a dispose of n events 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 In the worst case 1000 events being generated only 1000 and discarded the remaining ones this influence will be approximately of 5 ms Therefore for an application with the SOE enabled the user will have to take into account this time when setting the parameters of watchdog time and interval of the MainTask For the use of it the user must set the following parameters in the SOE Configuration tab 50 4 Configuration El Start Page E Configuration Bus a NX3030 General Parameters SNIP Configuration SOE Configuration General Configuration SOE Servic
104. need for de energizing the same Usually used in exchanges of I O modules Stands for International Electrotechnical Commission or International Electrotechnical Commission is an international standardization body that prepares and publishes international standards for electrical scope electronic and related technologies Generic standard for operation and utilization of PLCs Old IEC 1131 Third part of the generic standard for operation and use of PLCs IEC61131 Device which adapts electrically and or logically the signal transference between two pieces of equipment High priority attending event which temporarily stops the program execution and detour for a specific attending routine Defines how often a task is performed See Input output Module belonging to the inputs and outputs subsystem Set of analog or digital I O modules and interfaces of a programmable controller Also called I O Data I O devices of a system In case of PLCs typically correspond to digital or analog inputs or outputs modules which monitor or activate the controlled device Stands for isolated or isolating Memory quantity unit Means 1024 bytes if 1kbyte Acronym for Liquid Crystal Display Light emitting diode It s a type of diode that emits light when electrically stimulated Used for light indication Graphic matrix where are inserted the language instructions of a relay diagram which compose a applicative program A group of logics organiz
105. or 1 bit Coil Write 1 bit Coil Read 1 bit Data Type MODBUS data type Holding Register Write 16 bit Holding Register Read 16 bit Holding Register AND Mask 16 bit 92 4 Configuration Holding Register OR Mask 16 bit Input Register 16 bit Input Status 1 bit Data Initial Initial address of the MODBUS Size of the MODBUS data a 1 to 65536 Data Range The data range address configured Table 4 44 MODBUS Client Mappings Configuration Notes Variable Value this field is used to specify a symbolic variable in MODBUS relation Data Type this field is used to specify the data type used in the MODBUS relation Dataiye Size fits Description ee FEGE AND AND mask used in write analog output Holding Register OR Mask OR mask used in write analog output Input Register Analog input that can only be read Table 4 45 Data types supported in MODBUS Client Data Initial 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 This field varies with the MODBUS data type configured Data range this field shows to the user the memory address range used by the MODBUS relation Requests Configuration Configuration via Symbolic Mapping The setting
106. problem persists consult the Altus Technical Support Possible Cause Solution Verify if the CPU is connected properly in the rack Power off and take off all modules from the bus but the power supply and the CPU Power on the bus and verify the power supply functioning the external and the one in the rack Verify if the supply voltage gets to the Nexto power supply contacts and if is correctly polarized Does not Lack of power supply or power on incorrectly powered Verify every communication cable connection Verify the serial and Ethernet interfaces configuration in the MasterTool IEC XE software Does not Bad contact or bad communicate configuration Verify if the memory card is properly connected in the compartment Does not Verify if the memory card was put in the right side recognize the Bad connection or not as indicated on the CPU frontal panel memory card mounted Verify if the memory card wasn t unmounted through MS button placed on the frontal panel visualizing the indication on the CPU graphic display Table 7 13 Troubleshooting Table Preventive Maintenance It must be verified each year if the interconnection cables are connected firmly without dust accumulation mainly the protection devices In environments subjected to excessive contamination the equipment must be periodically cleaned from dust debris etc The TVS diodes used for transient protection caused by atmospheric
107. redundant HSDN using two NX5000 modules The Figure 4 9 also shows an example with one NX5000 module used isolated without NIC Teaming redundancy inserted to the right of the other modules 61 4 Configuration a m MasterTool SCADAS Non redundant Ethernet Ethernet HSDN B Other HSDN CPUs Normally Redundants Figure 4 9 Simple and Redundant Ethernet Networks Using NX5000 The two first NX5000 modules from the backplane rack make up a redundant NIC Teaming pair interconnected in two different switches Ethernet HSDN A and Ethernet HSDN B At some point these two switches must be interconnected so that there is connection between the two NIC Teaming ports and greater availability against double failures Such Ethernet architectures enable excellent availability against failures on Ethernet ports cables and switches A set of two Ethernet ports forming a NIC Teaming pair presents a unique IP address connected to the pair of ports Thus a client such as a SCADA or MasterTool connected to a server on a PLC does not need to concern about changing the IP address in case there is a failure in some of the NIC Teaming ports Diagnostics indicate eventual failures that may arise in any of the NIC Teaming pair ports ATTENTION Both NX3020 and NX3030 CPUs support the NX5000 module and can put two NX5000 together as an NIC Teaming pair Using the NX3020 CPU it is possible to insert up to two NX5000 modules in the proj
108. response 2 ACK request3 time Figure 4 3 Example of a Calibrated ACK Sending ATTENTION All operational systems with support to TCP IP protocol network interface have equivalent parameters to the discussed in this chapter for the Nexto Series CPUs Ethernet interface In the Windows operational system these parameters are defined in the system registers under several different identifications and must be modified only by network administrators thus affect all ams and applicative installed under the operational system 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 memory card reading and writing configuration for errors generation during the code generation due watchdog consistency of the project tasks and consistency of the retentive and persistent area in Q Generates error during the code Generate error on Tasks generation in case any project task has set Unmarked Marked watchdog consistency the watchdog time higher than 80 of the Unmarked time set in the task Interval Consist retain and Performs the consistency of retentive and Marked Marked persistent area in Q persistent areas in Q Unmarked Memory Card Copy Project from
109. ss0s50ssseoe0sss0s0e0sososee0sesosbo0sesos0seseoev0s0s0eevosnsee sosoe0sorosesnspsosesssososodesooesesosoorse 323 Bz GLOSSARY E E E E sosnoachesstoashescnoaceessuosbeaeusoshed sosesheasesschesceeacncocneueese 324 ANNEX A DNBP3 INTEROPERABILITY csssssssssssssscsssesssssccsssasssssessssssssssasesesasssessssssasesesaseseseess 328 DNPS Device Prone 2 322c2 iccssecssasecesstesssocscesssteecesectseassaccseassscosencsecosenstesvaessSesvsessieeveassisetsaseiseveestsesssesseeee 328 DNP V3 0 Implementation Table ccscscccccccccsesssnsesecssessvevssonesecssessvevesenesecssessdesesesesecssesedecesenesecesesesetevssence 329 vi 1 Introduction 1 Introduction Nexto Series CPUs were designed to fulfill several customers demands 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 In complex applications where reliability availability and remote I O operation is required Nexto Series CPUs are also a great choice due to its different redundant topologies and bus expansion possibilities Nexto Series CPUs provide innovative and unique enhanced diagnostics services They take the user to a whole new diagnostics experience By using a switch located on top of the module and a built in compact graphical LCD display the user has direct access to extensive information regarding I
110. than the configured watchdog time The diagnostics can be checked in the Exception wExceptionCode operand see on Table 7 7 Hardware Watchdog In order to reset any watchdog indication as in the WD LED or in the Reset bWatchdogReset operand the module must be disconnected from the power supply In order to verify the application conditions in the module restart see configurations on Table 4 1 302 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 OC oren meng Po o Nawowtnkaeen OSS e o omyessnewoi SSCS e 00 ness newok INK OO SSS Ethernet network transmission or reception occurrence for or to this IP address Blinks on Nexto CPU demand and not every transmission or reception in other words it may blink on a lower frequency than the real transmission or reception frequency Table 7 4 Ethernet LEDs Meaning Diagnostics via WEB Besides the previously presented features the Nexto Series brings to the user a innovating access tool to the system diagnostics and operation states through a WEB page The utilization and dynamics is very intuitive and facilitates the user operations The use of a supervisory system can
111. the PX2612 or equivalent command Starting with version 2 0 1 the CPU that is in Stand by will change your state to Not Configured during the synchronization process but will return automatically when the sources are the same between the two Half Clusters Project Synchronization Disabling On Sporadic Synchronization Services through NETA and NETB section applicative project and archive project synchronization services were described These services normally must be enabled and are useful when the project modifications can be downloaded on line in the Active CPU and the Stand by CPU afterwards automatically through the synchronism channels NETA NETB However there are project modifications which can t be downloaded on line in any CPU e g the inclusion of modules in a PROFIBUS remote or the inclusion of a new PROFIBUS remote In these cases using the CPU and PROFIBUS network redundancy such modifications can be made without interrupting the process control A procedure to accomplish this objective is described in the Exploring the Redundancy for Off Line downloading of Modifications without Interruption of the Process control section In this procedure it s necessary to disable temporarily the project synchronizations allowing for a while one CPU to operate with a project new version while the other CPU still operates with the old project version A NX3030 CPU has a register for Project Synchronization Disabling nonvolatile w
112. the network discovered in the first step This can be discovered for instance disconnecting the CPU from the network and executing a ping in its IP address As the CPU is disconnected from the network the ping function must fail If not there s equipment with the same IP address In case the IP address is already being used by equipment in the network the third step must be executed and some of the following steps too using a crossover cable to connect MasterTool to the CPU avoiding IP addresses conflict In one of the following cases at downloading the project in the CPU the definitive IP addresses are updated in it see Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 section Third Step Preparing MasterTool Connection Set Active Path The third step consists in double clicking on the Device NX3030 PLC in the Device Tree getting in the tab Communication Settings clicking on the Gateway and pressing the Scan Network button to list all CPUs detected by MasterTool in the network At this moment a CPU whose identification has the IP address found in the first step is supposed to appear In case the user has changed the network CPU name previously this name will be visualized MasterTool Connection with a NX3030 CPU from a Redundant PLC section describes with more details the possible identifications which can be observed on this list Anyhow all possible identification has a field showi
113. the three initial characters on the main screen second line as shown in the chapter Graphic Display The display screen is presented on initialization and again a few seconds after the navigation is finished without pressing the NX3030 CPU button Screens below the REDUNDANCY Menu There s a menu called REDUNDANCY where below it there are several screens The description and access of theses screens are available in the Configuration CPU s Informative and Configuration Menu chapter Redundancy Diagnostics Structure The NX4010 module diagnostics area is mapped over direct representation Q variables and defined symbolic through the AT directive in the GVL Diagnostics This section is divided in two parts e DG_NX4010 tGeneral General diagnostics for NX4010 operation They are described in the Redundancy Link Module Technical Features CE114900 e DG_NX4010 tRedundancy Redundancy specific diagnostics which are described within the chapter This item is divided in other 6 data structures o RedDgnLoc Has redundancy diagnostics of the local PLC connected e g the PLC redundancy state This section is described in Redundancy Diagnostics o RedDgnRem It s a copy from the other PLC RedDgnLoc received through Synchronism channels NETA NETB This way the local PLC has access to the remote PLC diagnostics This section is described in Redundancy Diagnostics o RedCmdLoc Has redundancy commands generated in this PLC
114. 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 e Non redundant it can t be used in a redundant CPU default configuration e PLCA used in the redundant CPU PLCA e PLCB used in the redundant CPU PLCB The identification register can be adjusted using the MasterTool programmer The first thing to be done in a NX3030 CPU before downloading the redundant project in it is to identify it as PLCA or PLCB In case the identification isn t executed several redundancy features won t work correctly as for instance the synchronization of the application between the PLCs ATTENTION The CPU identification register is not part of the redundant CPU project thus it isn t saved as part of this project in the computer where MasterTool is being executed The register is saved only in the nonvolatile CPU memory Single Redundant Project Due to the identification register previously described there s a single project for the redundant CPU identical for both PLCA and PLCB Configuration parameters that must be different for PLCA and PLCB e g Ethernet interface IP address appear doubled in the redundant CPU project one for
115. this selection the options described in the Figure 4 5 can be chosen 48 4 Configuration Bus Event Mapping IO_EVT_0 liorisng edge No Event Source I0 Rising Edge 10 Falling Edge 11 Rising Edge 11 Falling Edge 12 Falling Edge 15 Rising Edge 15 Falling Edge I6 Rising Edge I6 Falling Edge 112 Rising Edge 112 Falling Edge Figure 4 5 NX1001 Module External Event Source Options In addition to configuring the CPU it is required to configure the task responsible for executing user defined actions In this case the user must use a project profile that supports external events For further information see the chapter Project Profiles In the configuration screen of the ExternInterruptTask00 task Figure 4 6 it is necessary to select the event source in the corresponding field In this case IO_EVT_0 should be selected since the other origin sources IO_EVT_1 to IO_LEVT_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 StartPage ExternInterruptTask00 TimelnterruptTask00 Configuration Bus J NXx3010 Xx Configuration f 4 ExternInterruptTask00 Device PLC Logic Application Task Configuration E Priority 0 31 2 Type External event 10 6 0 z Watchdog Enable Time e g t 200ms 1000 Sensitivity 1 POUs Add POU PO
116. time that the client will wait for a server response to the request Fora MODBUS Client device two variables of the system must be considered the time the server takes to process a request and the response sending delay in case it is set in the server It is recommended that the time out is equal or higher than twice the sum of these parameters For further information check Protocols Configuration Communication Performance chapter Mode defines when the connection with the server is finished by the client Below follows the available options e Connection is closed after an time out or Conection is never closed in normal situations Those options presents the same behavior of Client close the connection due non response of the a request by the Server before reaching the Communication Time out e Connection is closed at the end of each communication The connection is closed by the Client after finish each request e Connection is closed after Inactive Time The connection will be closed by the Client if it reach the Inactive Time without performing a request to the Server Downtime inactivity connection time Mappings Configuration Configuration via Symbolic Mapping The MODBUS Client mappings configuration showed on Figure 4 28 follow the parameters described on Table 4 44 Figure 4 28 MODBUS Data Type s Fee Default Variable Value Symbolic variable name Name oh aivanable a red in ajprogrami
117. to be altered thus generating a incompatibility between the applications This will result in only on PLC to remain in the Active state with the other PLC remaining Inactive without the possibility of synchronizing redundant data or application between the two PLCs This incompatibility is informed by the redundancy diagnostics at DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bApplicationIncompatible This diagnostic is active when the download of a new application is done to one of the PLCs usually the Non Active with one of the following changes e Changes in the redundant memory areas configured in the parameters of the NX4010 module e Changes create or remove in the symbolic redundant variables declared in redundant POUs or redundant GVLs It is important to stress that to make changes in symbolic redundant variables the incompatibility problem will occur only if a new application download is done to one of the PLCs In case that the modifications in symbolic redundant variables and all the other modifications made in the project fit 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 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 modificati
118. used the client waits for a response and its use serves only to written commands Moreover in accordance with MODBUS standard the valid address range for slaves is 0 to 247 and addresses 248 to 255 are reserved Polling this parameter indicates how often the communication set for this relation must be executed At the end of communication will be awaited a time equal to the configured polling and after will be performed a new communication as soon as possible Mapping Diagnostic Area this field is limited by the size of output variables addressable memory Q at CPU which can be found in the chapter Technical Description Specific Features The configured MODBUS relations diagnostics are described in Table 4 48 Size of the Read and Write Data details of the size of the data supported by each function are described in the notes of Requests Configuration Symbolic Mapping Settings section IEC Read Variable in case the MODBUS data type is Coil or Input Status 1 bit the IEC variables initial address will be in the format IX10 1 However if the MODBUS data type is Holding Register or Input Register 16 bit the IEC variables initial address will be in the format IW This field is limited by the memory size of the addressable input variables I from each CPU which can be seen on Technical Description chapter IEC Write Variable in case the MODBUS data type is Coil or Input Status 1 bit the IEC variables initial address will be
119. value already written and the two words that are configured in this field using QW 0 for the AND mask and QW 2 for the OR mask allowing the user to handle the word This field is limited by the size of output variables addressable memory Q of each CPU which can be found in the chapter Technical Description Default Value the factory default value cannot be set for the Mapping Diagnostic Area IEC Reading Variable IEC Writing Variable and Writing Mask fields since the creation of a relation can be performed at any time on application development The MasterTool IEC XE software itself allocate a value from the range of direct representation output variables Q still unused Factory default cannot be set to the Reading Writing Data Size fields as they will vary according to the MODBUS data type selected ATTENTION Unlike other tasks of an application when a mark is reached at MainTask debugging the MODBUS RTU Master instance task or any other MODBUS task will stop being executed at the moment it tries to write in the memory area This occurs in order to maintain data consistency of memory areas while MainTask is not running 78 4 Configuration MODBUS RTU SLAVE This protocol is available for the Nexto Series on its serial channels At selecting this option in MasterTool IEC XE the CPU becomes a MODBUS communication slave allowing the connection with MODBUS RTU master devices This protocol is available only in execut
120. variable Process variable maximum value MaxPV In case the PV value is higher than the configured the PID block will stop the calculus and an error code will be generated in the output Process variable minimum value MinPV In case the PV value is smaller than the configured the PID block will stop the calculus and an error code will be generated in the output Sample time SampleTime Defines the PID block call period in seconds l varying from 0 001s to 1000s This parameter is not considered if the MeasureST is true When true enables the PID block proportional EnableP action In case is false the proportional action is zero When true enables the PID block derivative action EnableD Pak K In case is false the derivative action is zero When true enables the PID block integral action In Enablel AA case is false the integral action is zero When true the derivative action is calculated in the process variable Its different than zero only when DerivPV PV is changed In case if false the derivative action is calculated in the error when depends on the SP and PV variables When true enables the manual mode In case is Manual false enables the automatic mode The PID block control mode affects the way the MV and the integral action are calculated When true select the direct control when the MV is Direct included in the answer to be included in PV In case is false select the reverse control when MV is su
121. variables addressable memory Q at CPU which can be found in chapter Technical Description Specific Features 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 Disabling of Mappings composed of 32 bits used to disable individually the 32 MODBUS relations configured in Server mappings space The relation is disabled when the corresponding bit is equal to 1 otherwise the mapping is enabled Default Value the factory default value cannot be set to the Initial Address of Diagnostics in Q field because the creation of a Protocol instance may be held at any time on application development The MasterTool IEC XE software itself allocate a value from the range of output variables of direct representation Q not used yet The communication times of the MODBUS Server protocol found on the Advanced button of the configuration screen are divided into Task Cycle ms and Connection Downtime Time out s Further details are described in MODBUS Server Protocol General Parameters Configuration via Symbolic Mapping section The diagnostics and MODBUS commands are described in Table 4 55 Mapping Configuration Configuration via Direct Representation Q The MODBUS re
122. way it is just to use it as global variable The variable name is described in the detailed diagnostic list in the Diagnostics via Variables chapter Common Problems If at power on the CPU it does not work the following items must be verified e Is the room temperature within the device supported range e Is the rack power supply being fed with correct the voltage e Is the power supply the module inserted on the far left in the rack observing the rack by the front view followed by the Nexto Series CPU e Are there network devices as hubs switches or routers are powered interconnected configured and working properly e Is the Ethernet network cable properly connected to the Nexto CPU NET 1 or NET 2 port and to the network device e Is the Nexto Series CPU on in execution mode Run and with no diagnostics related to hardware If the Nexto CPU indicates the execution mode Run but it does not respond to the requested communications whether through MasterTool IEC XE or protocols the following items must be verified e Is the CPU Ethernet parameters configuration correct e Is the respective communication protocol correctly configured in the CPU e Arethe variables which enable the MODBUS relations properly enabled If no problem has been identified consult the Altus Technical Support 322 7 Maintenance Troubleshooting Table 7 13 shows the symptoms of some problems with their possible causes and solutions If the
123. when using the communication modules as the Ethernet NX5000 module for instance the time addition to the Main Task may be up to 25 of the execution average time Time for Instructions Execution Table 2 13 presents the necessary execution time for different instructions in Nexto Series CPUs iBook 2 aon oa 1000 Divisions 1000 Multiplications Table 2 13 Instruction Times Initialization Times Nexto Series CPUs have initialization times of 50 s and the initial screen with the NEXTO logo Splash is presented after 20 s from the power switched on Interval Time The CPU interval time of every task depends on the application software which can be set from 5 to 750ms 16 2 Technical Description Physical Dimensions Dimensions in mm oO D m Ki D Figure 2 2 CPU Physical Dimensions Purchase Data Integrant Items The product package has the following items e NX3010 or NX3020 or NX3030 modules e Installation guide Product Code The following code should be used to purchase the product 17 2 Technical Description High speed CPU 1 Ethernet port 2 serial channels memory card interface and remote rack expansion support High speed CPU 2 Ethernet ports 2 serial channels memory card interface and remote rack expansion support High speed CPU 2 Ethernet ports 2 serial channels memory card interface remote rack expansion and redundancy support Table 2 14
124. 00 0 Table 4 20 MODBUS RTU Master General Configurations Notes Send Delay The answer to a MODBUS protocol may cause problems in certain moments as in the RS 485 interface or other half duplex Sometimes there is a delay between the slave answer time and the physical line silence slave delay to put RTS in zero and put the RS 485 in high impedance state To solve this problem the master can wait the determined time in this field before sending the new request Otherwise the first bytes transmitted by the master could be lost Minimum Interframe The MODBUS standard defines this time as 3 5 characters but this parameter is configurable in order to attend the devices which do not follow the standard The MODBUS protocol diagnostics and commands configured either by symbolic mapping or direct representation are stored in T_DIAG_MODBUS_RTU_MASTER_1 variables For the direct representation mapping they are also in 4 bytes and 8 words which are described in Table 4 21 6699 where n is the configured value in the Q Initial Address of Diagnostic Area field 66 4 Configuration Direct Representation Variable Diagnostic Variable T_DIAG_MODBUS RTU_MASTER_1 Paste TEST Diagnostics Bits QX n 0 bRunning The master is running QX n 1 bNotRunning The master is not running see bit bInterruptedByCommanda The bit bNotRunning was enabled as binterruptedByCommand the master was
125. 00 Ethernet interfaces etc o Remotes in PROFIBUS networks o TO modules in remotes in PROFIBUS networks o MODBUS instances e To modify parameters inside devices from the device tree such as o IP addresses and other Ethernet interfaces parameters o PROFIBUS master parameters o PROFIBUS remotes parameters o TO modules parameters inside PROFIBUS remotes e To modify the MainTask period Modifications which Allow On Line Download A priori the modifications not mentioned in the sections Modifications which Demand Off Line Download and the Interruption of the Process Control and Modifications which Demand Off Line Download allows on line download Even this way the modifications which allow on line download in the PLC where MasterTool is connected are listed below These modifications are valid for variables POUs and GVLs redundant or not To add POUs from the program type if these POUs don t need to be associated to any task To remove POUs from the program type if these POUs aren t associated to any task To add or remove POUs from the function or function block type To modify the code of any type of POU program function or function block To add or remove symbolic variables in any POU type program function or function block To add or remove instances of function blocks in POUs from the program or function block type To add or remove GVLs To add or remove symbolic variables or instances of function blocks in GVLs On
126. 000 Disabling Variable Notes MODBUS Relation Settings 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 functions FC available are as follows Description 2 oo _ Readinput status F002 a o __ Readholding registers F003 a 0x04 Readinputregisters FOO ables ___2 _ __9 05_ Write a coil 05 FC Access to Variables z 6e o Write a holding register FC 06 Write multiple coils FC 15 Write holding registers FC 16 Register write mask FC 22 Read Write holding registers FC 23 Table 4 47 MODBUS Client Functions 95 4 Configuration Scan this parameter indicates how often the communication set for this request must be performed By the end of a communication will be awaited a time equal to the value configured in the field scan and after that a new communication will be executed Initial Address of the Read Data field for the initial address of the MODBUS read data Read Data Size the minimum value for the read data size is 1 and the maximum value depends on the MODBUS function FC used as below Read Coils HR 1 2000 Read Input Status FC 2 2000 Read Holding Registers HR 3 125 Read Input Registers HR 4 125 Read Write Holding Registers FC 23 121 Read Data Range this field shows the MODBUS read data range configured for each request The initial
127. 1 ms client milliseconds Notes SNTP Server It is possible to define a preferential address and another secondary one in order to access a SNTP server and therefore to obtain a synchronism of time If both fields are empty the SNTP service will remain disabled Minimum Error Before Clock Update In case this parameter is zero the clock will be updated in all synchronization requests Factory default from MasterTool IEC XE version 1 40 and later the factory default value for the IP addresses of SNTP Servers have been changed ATTENTION The SNTP Service depends on the user application only for its configuration Therefore this service will be performed even when the CPU is in STOP or BREAKPOINT modes since there is an application in the CPU with the SNTP client enabled and properly set 54 4 Configuration CAUTION It is vital a configuration of at least one SNTP server It is recommended to set two SNTP servers primary and secondary The SNTP synchronism is necessary to generate events with timestamp coherent between CPA and CPB and with world time Another purpose is to avoid discontinuity during a switchover in applications which reference date and hour considering that there is no synchronism of date and hour between the CPs through NETA and NETB synchronism channels Daylight Saving Time DST The DST configuration must be done indirectly through the function SetTimeZone which changes the time zone
128. 12 STAND BY button This would be a totally automatic solution with no operator intervention that would be typically made in the ActivePrg POU Through data structures described in the Diagnostics Commands and User Data Structure section it s possible to exchange diagnostics and commands between the half clusters through NETA and NETB This way the user can execute special redundancy managing for failures that normally wouldn t cause any switchover Further details regarding these data structures are offered in the following sections e Redundancy Diagnostics Structure e Redundancy Commands e User Information Exchanged between PLCA and PLCB Below is exemplified how the user can manage failures and execute a switchover due to an error in the Ethernet interfaces from the Active PLC this code should be used in the ActivePrg POU Verify if NIC Teaming is enabled IF DG_NX3030 tDetailed Ethernet NET1 szIP 0 0 0 0 OR DG_NX3030 tD tailed Ethernet NET2 szIP 0 0 0 0 THEN NIC Teaming enabled error in two NETs to execute a switchover 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
129. 293 6 Redundancy with NX3030 CPU FALSE Automatic configuration request disabled TRUE This command produces an equivalent action to the TURN ON PLCX bTurnOnLocal button on the PX2612 in the local PLC FALSE The TURN ON PLCx button on the local PLC isn t pressed TRUE This command produces an equivalent action to the STAND BY button on bStandbyLocal the PX2612 in the local PLC FALSE The STAND BY button on the local PLC isn t pressed TRUE This command produces an equivalent action to the INACTIVE button on bInactiveLocal the PX2612 in the local PLC FALSE The INACTIVE button on the local PLC isn t pressed TRUE This command resets the NETA NETB statistics see substructure SNET_Stat in RedDgnLoc and RedDgnRem Such statistics are failure and success counters in synchronization services FALSE The reset commands for the NETA NETB statistics in the local PLC wasn t activated bResetNET StatisticsLocal 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 Therefore for the PX2612 to be in test mode the PLC verifies if RedCmdLoc TestModeLocal and RedCmdRem TestModeLocal are both on bTestModeLocal The RedDgnLoc RedPanelT estMode diagnostic is turned on to inform that the PX2612 is reall
130. 5 Connections counter interrupted QW n 8 wClientClosedConnections WORD due to customer request 0 to 65535 Ethernet frames counter received by the server An Ethernet frame QW n 10 wRXFrames WORD can contain more than one request 0 to 65535 Requests received by the server QW n 12 wRXRequests WORD counter and answered normally 0 to 65535 Requests received by the server counter and answered with exception codes 0 to 65535 The exception codes are listed below 1 the function code FC is legal but not supported 2 relation not found in these data MODBUS 3 illegal value for the address 128 the master client has no right to read or write 129 MODBUS relation is disabled QW n 16 wRXIllegalRequests WORD sees equests counter 0 to WAW n 18 wDiag_18_reserved WORD Table 4 55 MODBUS Server Diagnostics QW n 14 wT XExceptionResponses 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 35 follows the parameters described in Table 4 56 Mappings Data Start Absolute Data Address Start Address Value Variable Data Type Data Size Data Range Figure 4 35 MODBUS Server Data Mappings Screen 105 4 Configuration oer Default Variable Value Symbolic variable name Name ot a v
131. 55 6 Redundancy with NX3030 CPU You are about to create a new MasterTool IEC XE Standard Project Choose the following options and the wizard will create a project as you decide Choose the CPU model NX3030 Altus S A CPU 2 Eth 2 Serial Memory Card Rack Expansion and Redundancy Choose the rack model Nx9000 Altus S A 8 Slot Backplane Rack Choose the power supply model INx8000 Altus S A 30 W 24 Vdc Power Supply Module Choose the redundancy configuration of Half Cluster With Redundancy Choose the operation mode of redundancy Half Cluster With redundancy panel Choose the configuration of OPC communication Disabled Choose the bus expansion redundancy configuration Without Redundancy 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 It is important stress that this architecture proposed by the Wizard is typical After that can be created more PROFIBUS networks respecting the maximum limit of four PROFIBUS Master modules NX5001 in each half cluster Choose the type of PROFIBUS networks o There s none no NX5001 module allocated o Single allocates one NX5001 module o Redundant allocates two NX5001 modules Choo
132. A NXModbus_Diagnostic_Struds Multitasking Real Time Clock Functions Z GetDateAndTime E GetDayofweek GetTimeZone SetDateAndTime 2 SetTimeZone Data Types obsolete oo Startup Counters 2 System Calls E m Figure 4 39 Clock Reading and Writing Blocks 115 4 Configuration ATTENTION Function blocks of RTC Reading and Writing previously available in 2 00 MasterTool IEC XE or older become obsolete from 2 00 or newer the following blocks are no longer used NextoGetDateAndTime NextoGetDateAndTimeMs e NextoGetTimeZone NextoSetDateAndTime NextoSetDateAndTimeMs e NextoSetTimeZone Function Blocks for RTC Reading and Writing Among other function blocks there are some very important used for clock reading GetDateAndTime GetDayOfWeek and GetTimeZone and for date and time new data configuring GetDateAndTime and SetTimeZone The proceedings to configure these two blocks are described below ATTENTION The function blocks for RTC 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 Function Blocks for RTC Reading The clock reading can be made through the following functions GetDateAndTime GetDateAndTime GetDateAndTime Figure 4 40 Date and Hour Reading Input and Outp
133. AL 2319 Synchronism channel NETB AL 2319 7 89 1011 45 67 89 1011 cluster rack NX9001 rack N 9001 half cluster PLCA half cluster PLCB Figure 6 2 Minimum configuration of a redundant CPU in rack NX9001 Typical Configurations of a Redundant CPU A minimum configuration as the one shown on Figure 6 2 may already work as redundant processing unit It would be possible to use the serial and Ethernet communication channels from NX3030 CPU for instance for MODBUS TCP communication with a SCADA system and MODBUS RTU and or MODBUS TCP communication with smart field devices or MODBUS remote I O systems In typical configurations however additional modules are inserted in the PLCA and PLCB half clusters for instance to deliver a remote PROFIBUS I O and Ethernet additional channels Among the additional modules which optionally may be inserted in the half clusters are the following e PROFIBUS Masters NX5001 e 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 218 6 Redundancy with NX3030 CPU NX5001 Modules Addition for PROFIBUS Networks A redundant PLC is up to until four NX5001 modules for PROFIBUS networks usage Each network can be single or redundant In case the PROFIBUS n being n
134. Active and the Non Active PLC This can be made comparing the diagnostics DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag dwApplicationCRC and DG_NX4010 tRedundancy RedDgnRem dwApplicationCRC in the Non Active PLC the CRCs must be different In case both projects are equal in the PLCs it s possible that the project synchronism disabling step 5 has not being properly executed This can be verified through the diagnostic DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectS yncDisable which must be true in the Non Active PLC If it isn t true the procedure must be returned to step 5 Step 9 Execute Switchover between Active and Stand by PLCs A switchover between the PLCs must be executed e g pressing the STAND BY button on the Active PLC The Stand by PLC which has a new project with the modifications takes over as Active The Active PLC which has the old project takes over as Stand by Step 10 Projects Synchronism Enabling in the Active PLC e Inthe 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 But this time we need to select the Enable option from the combo box MasterTool must be connected to the Active PLC see MasterTool Connection with a NX3030 CPU from a Redunda
135. All counters return to zero when its limit value is exceeded Redundancy Commands The structure command fields RedCmdLoc and RedCmdRem have a suffix which can be Local or Remote E g there are the command fields StandbyLocal that StandbyRemote that have equivalent effect to the PX2612 panel STAND BY button A command with Local suffix generated in RedCmdLoc must be executed in the local PLC local On the other hand a command with Remote suffix generated in RedCmdLoc will be executed in another PLC remote This works as the following e The remote PLC each MainTask cycle receives the RecCmdLoc copy from the local PLC through NETA NETB and this copy is called RedCmdRem in it e The remote PLC only executes the RedCmdRem commands with the Remote suffix Example 1 if the local PLC is in Active state and it s desired to switch it to the Stand by state the DG_NX4010 tRedundancy RedCmdLoc bStandbyLocal bit can be turned on in it Example 2 if the remote PLC is in Active state and it s desired to switch it to the Stand by state the DG_NX4010 tRedundancy RedCmdLoc bStandbyRemote bit can be turned on in the local PLC This may be useful for instance if the communication of a SCADA system is temporarily unavailable with the remote PLC In this case the command is written by the SCADA in the local PLC that retransmits to the remote PLC through NETA NETB 292 6 Redundancy with NX3030 CPU ATTENTION If the DG_NX4010 tR
136. Always Update Variable option is not set or in case the REFRESH_INPUT function is called for a module that has only outputs e InputReadFail Module internal critical failure the function transmitted frame was not returned within the defined time out e FrameTransmitError Module internal critical failure error during the frame transmission in the function e BusBusy Module internal critical failure the bus is not enabled for frame transmission in the function Utilization example in ST language PROGRAM MainPrg VAR Info ERRORCODE byRackNumber BYTE bySlotNumber BYTE END_ VAR INPUTS byRackNumber 0 bySlotNumber FUNCTION Info REFRESH INPUT byRackNumber bySlotNumber Function call Variable Info receives possible function errors ll m jo 146 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 ATTENTION REFRESH OUTPUT must only be used in MainTask task ATTENTION REFRESH_OUTPUT function does not support inputs that have been mapped to symbolic variables For proper operation it is necessary that the input is mapped to a variable within the memory direct representation o
137. BUS network or each redundant pair of NX5001 used in a redundant PROFIBUS network has the following parameters to be adjusted 261 6 Redundancy with NX3030 CPU BB StertPage i Configuration Bus J Nx5001 x DP Parameters if Process Data Module Parameters Bus 1 O Mapping Name Value Comment Q Start Address of Module Diagnostics Area 65536 Define starting address of Module Diagnostics Area Q Start Address of Slaves Diagnostics Area 0 Define starting address of Slaves Diagnostics Area Network Redundancy True Enable or disable PROFIBUS Network Redundancy Failure Mode True Enable or disable switchover in case of PROFIBUS module failure 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 22Erro Fonte de refer ncia nao encontrada In order to ungroup it the same procedure must be followed but marking the parameter as FALSE If this parameter is marked as TRUE the DP parameters and the NX5001 parameters at its right are blocked for edition ATTENTION In case of redundant networks only the parameters of the NX5001 to the far left on the bus must be adjusted while the NX5001 at the right remai
138. Bit edDgnLoc sGeneral_Diag TRUE The configuration process executed in the Not Configured state has finished bConfigDone FALSE The configuration process executed in the Not Configured state hasn t finished yet or wasn t executed 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 FALSE The configuration process has finished successfully or wasn t executed TRUE Intermediate data structure with insufficient size It s a system error normally not expected Get in contact with ALTUS support to bTemporaryBufferTooSmall report it FALSE Intermediate data structure is within the expected TRUE The Diagnostic and Commands Exchange synchronization service was executed 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 bExchangeSync TRUE The number of redundant areas exceeded the maximum allowed It s a system QB n 4 error normally not expected Get in contact with 2 bTooManyRedAreas ALTUS support to report it FALSE The number of redundant areas is within the expected 286 6 Redundancy with NX3030 CPU 287 bRedDataSync o
139. C 05 Access to Variables A 6e o Write holding register FC 06 Write multiple coils FC 15 Write holding registers FC 16 Register write mask FC 22 Read Write holding registers FC 23 Table 4 26 MODBUS Functions Supported by Nexto CPUs Scan this parameter indicates how often the communication set for this request must be performed By the end of a communication will be awaited a time equal to the value configured in the field scan and after that a new communication will be executed Initial Address of the Read Data field for the initial address of the MODBUS read data Read Data Size the minimum value for the read data size is 1 and the maximum value depends on the MODBUS function FC used as below Read Coils FC 1 2000 Read Input Status FC 2 2000 Read Holding Registers FC 3 125 Read Input Registers FC 4 125 Read Data Range this field shows the MODBUS read data range configured for each request The initial address along with the read data size will result in the range of read data for each request Initial Address of the Write Data field for the initial address of the MODBUS write data Write Data Size the minimum value for the write data size is 1 and the maximum value depends on the MODBUS function FC used as below Write Single Coil FC 5 1 Write Single Holding Registers FC 6 1 Write Multiple Coils FC 15 1968 Write Holding Registers FC 16 123 Register Write Mask FC 22
140. CPU serial number e The equipment revision and the executive software version written on the tag fixed on the product side e CPU operation mode information acquired through MasterTool IEC XE e The application software content acquired through MasterTool IEC XE e Used program version Warning Messages Used in this Manual In this manual the warning messages will be presented in the following formats and meanings DANGER Reports potential hazard that if not detected may be harmful to people materials environment and production CAUTION Reports configuration application or installation details that must be taken into consideration to avoid any instance that may cause system failure and consequent impact ATTENTION Identifies configuration application and installation details aimed at achieving maximum operational performance of the system 2 Technical Description 2 Technical Description This chapter presents all technical features from Nexto Series CPUs 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 The graphic display also offers an easy to use menu which brings to the user a quick mode for parameters reading or defining such
141. CPU switches for the Stop mode from the submitting of an application the variables in the application tasks will be lost with the exception of the persistent type variables The output variables will assume the defined value by the user and then the outputs value will switch for the safe state As the new application is loaded the output variables will assume again the defined value by the user Breakpoint When a debugging mark is reached in a task it is interrupted All the active tasks in the application will not be interrupted they will continue their execution In this mode it is possible to go through a program in the Online mode A step by step can be executed and the debugging interruptions positions depend on the editor For further information about the use breakpoints please consult the MasterTool IEC XE Utilization Manual MU299609 Exception When a CPU is in Exception it indicates that some improper operation occurred in one of the application active tasks The task which caused the Exception will be suspended and the other tasks will pass for the Stop mode It is only possible to take off the tasks from this state and set them in execution again after a new CPU start condition Therefore only with a Reset Warm Reset Cold Reset Origin or a CPU restart puts the application again in Run mode Reset Warm This command puts the CPU in Stop mode and starts all the application tasks variables except the persistent and retentive typ
142. Configuration MODBUS Master Protocol Configuration by Symbolic Mapping To configure this protocol using symbolic mapping you must perform the following steps e Configure the general parameters of the MODBUS Master protocol like transmission delay times and minimum interframe as in Figure 4 11 e Add and configure devices via the General Parameters tab defining the slave address communication time out and number of communication retries as can be seen in Figure 4 12 e Add and configure the MODBUS mappings on Mappings tab as Figure 4 13 specifying the variable name data type and the data initial address the data size and range are filled automatically e Add and configure the MODBUS requests as presented in Figure 4 14 specifying the function the scan time of the request the starting address read write the data size read write and generate diagnostic variables and disabling the request via the buttons at the bottom of the window MODBUS Master Protocol General Parameters Symbolic Mapping Configuration The general parameters found on the MODBUS protocol initial screen Figure 4 11 are defined as General Parameters Settings Send Delay ms 0 Minimum Interframe chars 3 5 gt Figure 4 11 MODBUS RTU Master Configuration Screen Configuration Description Send Delay ms rsa lea a Fo 0 to 65535 nee Minimum silence tim Minimum Gin Si encetime Interframe chars between different frames 3 5 a 1
143. D n 72 QD n 72 QW n 76 QW n 76 QW n 78 QW n 78 QW n 80 QW n 80 QW n 82 QW n 82 QW n 84 QW n 84 QW n 86 QW n 86 QW n 88 QW n 88 QW n 90 QW n 90 QX n 92 0 QX n 92 0 n 43 QD n 43 QD n 47 n 88 QW n 88 QW n 90 QX n 92 0 BYTE DWORD DWORD WORD WORD WORD WORD WORD WORD WORD BIT 310 Thermometer diT emperat ure Serial COM1 byProtocol Serial COM1 dwRXBytes Serial COM1 dwTXBytes Serial COM1 wRxXPendingBytes Serial COM1 wT XPendingBytes Serial COM1 wBreakErrorCounter Serial COM1 wParityErrorCounter Serial COM1 wFrameErrorCounter Serial COM1 wRXOverrunCounter Serial COM1 wReserved_ 0 Serial COM1 wReserved_ 1 Serial COM2 byProtocol Serial COM2 dwRXBytes Serial COM2 dwT XBytes Serial COM2 wRxXPendingBytes Serial COM2 wT XPendingBytes Serial COM2 wBreakErrorCounter Serial COM2 wParityErrorCounter Serial COM2 wFrameErrorCounter Serial COM2 wRXOverrunCounter Serial COM2 wReserved_ 0 Serial COM2 wReserved_ 1 Ethernet NET1 bLinkDow sensor of the CPU Protocol selected in the COM 1 02 MODBUS RTU Slave 03 Other protocol Counter of characters received from COM 1 0 to 4294967295 Counter of characters transmitted from COM 1 0 to 4294967295 Number of characters left in the reading buffer in COM 1 0 to 65535
144. DG Blinks 2x LED DG Blinks 4x LED DG Blinks 4x Application Stop Application Stop Application Run Application Stop Application Stop Retain and Persistent Memory Areas The Nexto CPU allows the use of symbolic variables and output variables of direct representation as retentive or persistent variables The output variables of direct representation which will be retentive or persistent must be declared in the CPU General Parameters as described at Configuration CPU Configuration General Parameters Symbolic names also can be attributed to these output variables of direct representation using the AT directive plus using the key word RETAIN or PERSISTENT on its declaration For example being QB4096 and QB20480 within the retentive and persistent memory respectively PROGRAM MainPrg VAR RETAIN byRetentiveVariable 01 AT QB4096 BYTE ND VAR AR PERSISTENT byPersistentVariable 01 AT QB20480 BYT ND VAR lt m Fl m In case the symbolic variables declared with the AT directive are not inside the respective retentive and or persistent memory errors during the code generation in MasterTool are presented informing that there are non retentive or non persistent variables defined in the retentive or persistent memory spaces Regarding the symbolic variables which will be retentive or persistent only the retentive variables may be local or global as the persistent symbolic variabl
145. Device J MopBuS_Server x e s5 MU Stuff tx MODBUS Server Configuration S J Device Nx3030 REES E PLC Logic Q Start Address of Diagnostics Area TCP Port AA We Application 66922 502 ai IE 3 Bil of Materials RTU via TCP Size Mapping Disabling B Configuration and Consumpt 3192 T Advanced EH Diagnostic Explorer paa Diiia Used range Q866922 QB66941 Used range QX8192 0 QX8195 7 f Library Manager C aiakianaaieaa E MainPrg PRG Data Type Data Start Address Data Size IEC Variable E Task Configuration ManTask B MainPrg f Configuration Bus J Nx3030 Nx3030 comi 3 com2 NET I J Mopsus_server moos 7 a NeT2 o 1 2 3 4 5 Last build 0 0 Precompile y Current user nobody Figure 4 36 MODBUS Server Setup Screen TCP port protocol and direct representation variables Q to control relations and diagnostics Configuration Default Value Options Initial Address of Starting address of the Diagnostics on Q diagnostic variables O e Die core Size of diagnostics 20 Disabled for editing TCP Port TCP Port 502 2 to 65534 Disabling of Starting address used to Mappings disable MODBUS relations Le eee RTU via TCP Protocol selection TCP pe G Table 4 57 Settings to control relations and diagnostics 107 4 Configuration Notes Initial Address of Diagnostics in Q this field is limited by the size of output
146. Ds signalize the redundancy state in each half cluster NO relay allows a half cluster to switch off the other in extreme situations A button allows the other half cluster reactivating Embedded resources for buttons LEDs and relays tests Indicate failures in the PLCA and in the PLCB independent of their states Active or Inactive Prevent obscure failures Allow quick maintenance essential for high availability Allow the execution of the same PX2612 control panel actions among other commands e g switchover command Can be executed in the local CPU or transmitted to the other CPU remote via synchronism channels NETA NETB Can be received through MasterTool or a SCADA system Can be executed through user application Register diagnostics and redundancy commands changes with timestamp allowing an investigation of the switchover causes Allow the events to have a precise timestamp adjusted to the world hour It also synchronizes the CPU real time clock for other applications Each MainTask cycle PLCA and PLCB exchange diagnostics and commands through synchronism channels NETA or NETB This way a CPU knows the other diagnostics and commands Each MainTask cycle the Active CPU copies redundant data to the Inactive CPU through the synchronism channels NETA and NETB Non redundant data are not synchronized Each MainTask cycle the Active CPU copies the redundant forcing list to the Inacti
147. EGAL_SERIAL_PORT PORT_ BUSY RROR_UART HW_ERROR_REMOTE AL_TX_BUFF_LENGTH CTS_TIME OUT_ON CTS_TIME OUT_OFF 4 Configuration TX_TIME OUT_ERROR NOT_CONFIGURED Returns the transmitted byte number which must be TX_TRANSMITTED equal to TX_BUFFER_LENGTH but can be smaller in case some error has occurred during transmission Table 4 95 SERIAL_RX Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Transmi SERIAL TX Port SERIA PORT COM1 Buffer Pointer ARRAY 0 9 OF BYT Status SERIAL STATUS Fl 0 1 2 3 4 5 6 7 8 9 END_ VAR INPUTS Transmit REQUEST TRUE Transmit PORT Port Transmit TX BUFFER POINTER ADR Buffer Pointer Transmit TX BUFFER LENGTH 10 Transmit TX TIMEOUT 10000 Transmit DELAY BEFORE TX 1000 Transmit CLEAR RX BEFORE TX TRUE FUNCTION Transmit OUTPUTS Transmit DONE Transmit EXEC Transmit ERROR Status Transmit STATUS If it s necessary to treat the error Transmit TX_ TRANSMITTED Inputs and Outputs Update Functionality used to update inputs and outputs in the applicative It is not necessary to wait until the cycle is finished When the function blocks to update the inputs and out
148. ET 1 4 Neto Bip f Device NX3010 Ethernet Port Parameters _ A PLCLogic Ethernet Port Parameters Application B Bill of Materials F Configuration and Consumption Diagnostic Explorer Diagnostic i il Library Manager E MainPrg PRG Ee Task Configuration RZ MainTask Configuration Bus J Nx3010 Nx3010 a comi a gt IP Address Subnetwork Mask Gateway Address 192 168 15 1 255 255 255 0 192 168 15 253 Figure 5 16 Configuring the CPU Communication Port 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 OK option or canceling and quit sending the project 199 5 Initial Programming MasterTool IEC XE Ex gt The Ethernet configuration is different from PLC The communication can be interrupted after downloading application Do you wish continue Figure 5 17 IP Configuration Warning Libraries There are several programming tool resources which are available through libraries Therefore these libraries must be inserted in the project so its utilization becomes possible The insertion procedure is rather simple the user must select the item Library Manager available in the left menu and select Add library as shown on Figure 5 18 T
149. ET 1 Configuration 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 IP address of the controller in 1 0 0 1 to I Aekhess the Ethernet bus ete IO 255 255 255 254 Sub network Sub net mask of the 0 0 0 1 to controller in the Ethernet bus 299 293 699 9 255 255 255 254 Gateway address of the 0 0 0 1 to SEIN GINS controller in the Ethernet bus 192 169 16 293 255 255 255 254 Table 4 15 NET 2 Configuration ATTENTION It is not possible to configure the two local Ethernet interfaces in the same sub net This kind of configuration is blocked in MasterTool This way each Ethernet interface must be configured in a different Subnetwork 60 4 Configuration Remote Ethernet Interfaces NET 1 NET 1 is an interface composed by an RJ45 communication connector pattern 10 100Base TX It allows 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 Default Value Options
150. Ethernet interface allowing input and output information and data to be shared between several controllers inside the same system The system can be easily divided and distributed throughout the whole field allowing the use of bus expansion with the same performance of a local module turning possible the use of every module in the local frame or in the expansion frames with no restrictions For interconnection between frames expansions a simple standard Ethernet cable is used Figure 1 2 Nexto Series Overview 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 CPUs Battery Free Operation Nexto Series does not require any kind of battery for R FO memory maintenance and real time clock operation This feature is extremely important because it reduces the system maintenance needs and allows the use in remote locations where maintenance can be difficult to be performed Besides this feature is environmentally friendly Multiple Block Storage Several kinds of memories are available to the user in Nexto Series CPUs offering the best option for any user needs These memories are divided in volatile memories and non volatile memories For volatile memories Nexto Series CPUs offer addre
151. For SNMPv3 in which there is user authentication and password to requests via SNMP protocol is provided a standard user described in the User and SNMP Communities section If you want to disable the service change the SNMPv3 user or communities for SNMPv1 v2c predefined you must access the web page of the CPU For details see the Configuration section Private MIB In addition to support MIB II the Nexto Series CPUs support Private MIB from firmware version 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 77 All private objects are described in MIBs ALTUS NEXTO NX3010 MIB ALTUS NEXTO NX3020 MIB and ALTUS NEXTO NX3030 MIB and can be found in www altus com br site_en 161 4 Configuration B di iso org dod internet E mgmt OverTemperatureAlarm UnderTemperatureAlarm Tiara Ethernet Application SNTP SOE GS EKL aam Figure 4 77 OID Tree View The objects available via SNMP in the Nexto Series CPUs are existing diagnostics shown in Table 7 7 which are important for managing networks These objects can be seen in Table 4 109 To access them through an SNMP manager the user must make requests from O
152. ID 1 3 6 1 4 1 43427 1 1 1 for 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 For example if the user wants to monitor the internal temperature of a CPU NX3030 the corresponding OID in this case will be 1 3 6 1 4 1 43427 1 3 1 5 3 iso org dod internet private enterprise AltusSA Nexto NX3030 NextoDiags Thermometer Temperature 162 4 Configuration Grous Diagnostic Description 1 1 CPUModel NX30XX 1 2 CPUVersion 1 Target F 1 3 BootloadVersion Bootloader Version 1 4 AuxProcVersion 2 1 AuxProcFailure Failure between Aux Proc and Main Proc The main Proc is not able to communicate with the 2 2 RTCFailure RTC CPU clock 2 Hardware 2 3ThermometerFailure Communication failure between Thermometer and Main Proc 2 4 LCDFailure A failure between the LCD and Main Initialization State of CPU 01 Hot Start 3 1 CPUInitStatus 02 Warm Start 03 Cold Start Obs These variables are reset in all energization Cold Start Counter It will only be increased due to hot removal of the CPU of the bus and not due to the Reset Cold command the of MasterTool IEC XE 0 to 65535 Warm Start Counter It will only be incremented during energization 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 pe RUMI aieuntor failure to support the CPU 0 to 65535 Reset counter made by the RTS Runtime S
153. L_BAUDRATE Lists all baud rate possibilities bits per pene SERIAL_DATABITS Lists all data bits possibilities Controls the Nexto CPU RS 232C port The transmitter is enabled to start the transmission and disabled as soon as R9292 RTS possible after the transmission is finished For example can be used to control a RS 232 RS 485 external converter Controls the RS 232C port of the Nexto SERIAL HANDSHAKE R9292 _RTS_OFF CPU The RTS signal is always off Controls the RS 232C port of the Nexto Rosse ATSLON CPU The RTS signal is always on Controls the RS 232C port of the CPU Nexto In case the CTS is disabled the RTS RS232 RT T is enabled Then waits for the CTS to be P ERIS EIS enabled to get the transmission and RTS restarts as soon as possible at the end of transmission Ex Controlling radio modems 130 4 Configuration i tre sare odor signa Controls the RS 232C port of the CPU RS232_MANUAL Nexto The user is responsible to control all the signals RTS DTR CTS DSR DCD Byte quantity which must be received to generate a new UART interruption Lower values make the TIMESTAMP more precise UART_RX_THRESHOLD when the EXTENDED MODE is used and minimizes the overrun errors However values too low may cause too many interruptions and delay the CPU SERIAL_PARAMETERS When true select the RX line and the block extended mode SERIAL_RX_EXTENDED must be used to RX QUEUE EXTENDED receive data On the other hand f
154. Line Download of Modifications In the Off Line and On Line Modifications Download section modifications which demand off line download were described along with the ones that allow online download An online change must be made by connecting the MasterTool to the NET 1 channel of the active CPU using its unique IP address Before version 2 01 of the MasterTool IEC XE it was necessary that the user selected the Create Boot Application option in the Communication menu after sending the application for the changes to be sent to the non volatile memory area of the CPU and 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 274 6 Redundancy with NX3030 CPU 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 ATTENTION An online change in the declaration of retain variables of the application adding or removing variables followed by a drop in the power CP before Create Boot Application will corrupt retentive memory because the value of the retain variables that were saved does not match the retrieved application variables in the restored memory When the Non Active PLC realizes that have a different project from the Active PLC it executes the following actions e Negotiates automa
155. MIB Toon I tel sec sles secede pcbod eh ohcbodchodcaodchohcaedchohcaodehohcaodehohcaodehohchodehohcaodehoncaodehoheaotenshenshel eb 161 COTE SUT AION Fs OE OE GeO EG SOE SOs SO Sa oOo ota Ma STE Sa Mets Se I 164 User and SNMP Communities s 0 casescsssesasasaiassaaaasasaaaaadessaaanaassaaaadesssaaadesssaaadessaaaadesssaaadaaaaaaanaaandaaae 166 User Management and Access Rights ccssssssssssssssssssssssssccssssssssssssscsssssssssssssssssssssssssssssccssssssssssessees 167 User Management and Access Rights of the Project 0 0 eeesececessnececeesseeeeeesnaeeesessaaeeseesaeeseesaeees 167 User Management and Access Rights of the CPU eeccessnceeceeeeeeeeesnnneeeeeeeeeeeesnaaeeeeeeeeeeeeenaaees 174 INITIAL PROG RAMMING wrsecccssccccactscevesssssevcsssssevcassssensessessesessssssocesssvoeesessoesessdsoaeassesascasseseesesorsoeseses 182 Memory Organization and ACCESS csssssssssossssssssssssssscssecsssssssssssssscssssssssssssssssssssssssssesssssssssssssssessees 182 Project PrOTICS sccieceishsivsseicestennsosseceeseceaccesstessdessenasceustesstsseesecceesssssdsteseessevesessevseasessevevesscssscsensensesesssuscsvanee 184 Summary SiTe EE E E AA aria E A E E heaviest E ES 184 BASIO iss E EE E EE E AE EE EE Pete toee 185 OS E nare T ETO EEE 185 l S o E E E E EE 186 Custo a E E AATE tg SOTE E A T E E tee dag ited 186 MACHINE san a EE E EEEE OE AOE O OEO OORO EOE EEEE 187 New Project isccccsensicccccssvccsucecheccdcssvessunececececss
156. MODBUS data type direct representation variables Q to receive write the data and amount of data to communicate The descriptions of each setting are listed below in this chapter 83 4 Configuration General Parameters of MODBUS Slave Protocol Configuration via Direct Representation Q The general parameters found on the home screen of MODBUS protocol configuration Figure 4 22 are defined as task Mare CE AsEISio asago Stuff Lef moneus Slave Configuration Device Nx3030 E 2 PLC Logic Q Start Address of Diagnostics Area SlaveAddress Q Application 66922 H Led Bil of Materials Size Mapping Disabling B Configuration and Consumpt 55 3192 2 eed E Diagnostic Explorer L J D ario Used range QB66922 QB66941 Used range QX8192 0 QX8195 7 fi Library Manager eae E MainPrg PRG Data Type Data Start Address Data Size IEC Variable Task Configuration MainTask Devices lt x ii Configuration Bus J MODBUS_RTU_Slave x x Slave Settings 0 1 B MainPrg m J Configuration Bus ff nx3030 Nx3030 s amp COM 1 Es movsus_RTu_slave md 5 amp com2 6 a Neri 7 a net2 pe 9 4 Add edit p Last build 0 0 Precompile 7 Current user nobody Figure 4 22 MODBUS RTU Slave Configuration Screen Address and direct representation variables Q to control relations and diagnostics Configur
157. MainTask By MainPrg J Configuration Bus J Nx3030 Nx3030 a com1 amp com2 D NETI lt lt D NET2 Last build 0 0 recompile 7 Current user nobody Figure 4 47 Utilization Options ATTENTION For a CPU in Stop Mode or with no application the transfer rate to the internal memory is approximately 150 Kbytes s For further information regarding this product feature see the MasterTool IEC XE User Manual MU299609 Memory Card Among other memories the Nexto Series CPUs allow the user the utilization of a memory card It is defined according the features described in the Technical Description Memory Card Interface chapter which stores among other files the project and application in the CPU internal memory When the card is inserted in the CPU and it presents a file type different from FAT32 it automatically identifies those files and questions the user if he wants to format the files In negative case the user cannot use the card as it is not mounted A message informing the format is not recognized is presented and the card presence is not displayed either If the user decides to format the files the CPU takes a few minutes to execute the operation depending on the cycle time execution of the application which is running in the CPU Once the memory card is mounted the CPU will read its general information leaving access to the slower memory card in the first few minutes
158. NOT_ALLOWED DSR_INTERRUPT_NOT_ALLOWED Table 4 79 Output Parameters Serial_CFG Utilization example in ST language after the library Nexto Serial is inserted in the project PROGRAM MainPrg VAR 133 4 Configuration 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 ENABLE RX ON TX FALSE ENABLE DCD EVENT FALSE ENABLE CTS EVENT FALSE Status SERIAL STATUS END_ VAR INPUTS Config REQUEST TRUE Config PORT Port Config PARAMETERS Parameters EUNCTION Config OUTPUTS Config DONE Config EXEC Config ERROR Status Config STATUS If it s necessary to treat the error SERIAL_GET_CFG The function block is used to capture the desired serial port configuration SERIAL_GET_CFG PARAMETERS Figure 4 53 Block to Capture the Serial Configuration Input parameters REQUEST BOOL This variable when true enables the function block use PORT SERIAL_PORT Select the serial port as described in the SERIAL_PORT data type Table 4 80 SERIAL_GET_CFG Input Parameters This variable is true when the block is completely executed It is fa
159. Non Active PLC can put this information in these data structures Among such information for instance might be some not mapped diagnostics in RedDgnLoc and RedDgnRem Modbus Diagnostics used at Redundancy To check for failure in all MODBUS Server configured ina MODBUS Client instance there is a specific diagnosis in each MODBUS Client instance configured Table 6 11 displays the diagnostics for this type of failure ina MODBUS Client instance called MODBUS_Symbol_Client Variable DG_MODBUS Symbol Client t Description Diag TRUE All servers configured at this Client shows error bAlIDevicesCommFailure FALSE There is at least um Server configured in this Client that doesn t shows error Table 6 11 Modbus Client Diagnostic When configured vital failure mode this diagnostic is consulted and 3 seconds after it s state change from FALSE to TRUE a switchover occurs if the other conditions for this event are satisfied 295 6 Redundancy with NX3030 CPU Redundancy Event Log MasterTool allows the observation of several logs for the Nexto PLC among them the Redundancy Event Log These messages specific for redundancy registers in the System Log modifications in practically every field of the diagnostics and redundancy commands structure data which are the following e RedDgnLoc e RedDgnRem e RedCmdLoc e RedCmdRem In case of diagnostic structures only the following fields don t generate diagnostics
160. Nx3010 a PLCLogic Application _ B Bill of Materials B Configuration and Consumption EB Diagnostic Explorer Diagnostics f Library Manager E MainPrg pre Task Configuration MainTask f Configuration Bus S J nxs010 N8010 comi oot elm com2 ba Q NETI 5 a x gc Lis i Build o error s o warning s 10 message s Description Project Object Position Memory area 3 contains Input highest used address 32768 largest contiguous me Memory area 4contains Output highest used address 32768 largest contiguous Memory area 5 contains Memory highest used address 16384 largest contiguous Memory area 6 contains Code highest used address 4194304 largest contiguous E Build complete 0 errors 0 warnings ready for download f 4 J p Precompile OK Current user nobody Figure 5 26 Compilation Messages PS In case the errors and messages are not visible on the screen the option Messages from the menu View must be selected as shown on Figure 5 27 206 5 Initial Programming Login File Edit view Project Build Online Debug Bg ED Pos Alt O S Devices Alt 1 FDevices Messages Alt 2 l 2 4 Neto E Element properties r aael o Product Library E 3 ToolBox Watch gt Eh Breakpoints fie Call Stack GJ Cross Reference List pri E Start Page E FullScee
161. Overview Lrcetes on Ser August 2612 199857 Te retenh this page dick on the low Current user nobody Figure 7 7 Diagnostic Explorer Screen 305 7 Maintenance e 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 Table 7 5 summarizes the diagnostic byte words division CPU summarized diagnostics CPU detailed diagnostics NX3010 CPU detailed diagnostics NX3020 and NX3030 Table 7 5 CPU Diagnostics Division Summarized Diagnostics Table 7 6 shows the meaning of each CPU summarized diagnostic bit Direct Representation 4 Variable Diagnostics DG_Modulo tSummarized Description 7 Message AT Variable Variable Bit kol NO DIAG 2R There is no active diagnostic 0 0 0 0 0 0 CONFIG TRUE There is a configuration P bConfigMismatch problem in the bus as the module MISMATCH 7 r inserted in the wrong position FALSE The bus is configured correctly ABSENT TRUE One or more declared MODULES DADS eniModules modules are absent FALSE All decl
162. PROFIBUS slaves diagnostics etc for instance Different from the quick diagnostics allocated in I such diagnostics allocated in Q can take more than one MainTask cycle to be updated By default this section includes 16 Kbytes QB65536 QB81919 The non redundant area QB94208 QB98303 is typically allocated for diagnostics and private commands of a half cluster and also for the redundancy command panel PX2612 LEDs and relay The user can reduce the redundant Q variable quantity in each one of the sections which can be redundant e On the first section the really redundant area size can be configured between Okbytes and 65535 bytes in 1kbyte multiples the default value is 16384 bytes The proper configuration of redundant Q is important to decrease the necessary time for redundant variables synchronization decrease the redundancy overhead E g if the real application allocates only PQO Q1499 for redundant outputs the redundant Q area size can be defined as 1500 bytes e On the second section the really redundant area size can be configured between Okbytes and 81919 bytes in 1kbyte multiples the default value is 16384 bytes The proper configuration of redundant Q is important to decrease the necessary time for redundant variables synchronization decrease the redundancy overhead E g if the real application allocates only QB65536 QB66999 for redundant diagnostics the redundant Q area size can be de
163. PU to the PC in which the MasterTool IEC XE software is installed the user must follow a very similar procedure to the previously described as the file must be selected from the right column and the button lt lt pressed placed on the center of the screen Furthermore the user has some operation options in the storing files area which are the following e New directory 4 allows the creation of a new folder in the user memory area e Delete item allows the files excluding in the folders in the user memory area e Refresh allows the file updating on the MasterTool IEC XE screen of the files in the user memory area and in the computer 123 4 Configuration Mu Stuff project ON X File Edit View Project Build Online Debug Tools Window Help SAIE A IBF 1S Devices 4x E _ Configuration Bus J Device x e mel MAT communication Settings Fies Log users and Groups Access Rights informa 7 e eve peis0 Host Locati Acie Runti Locatior 2 Temy 5 Bi Pc Loge ocation p ntime Location Application Name Size Modified Name Size Modified S B Bil of Materials C MemoryCard B Configuration and Consumpti J Others E InternalMemory ER Diagnostic Explorer device devdescxml 233 17 KB 238 768 9 29 2014 4 39 PM Diagnostics File_01 b t 428 bytes 9 1 2014 6 19 PM BD Library Manager B Nesto be 226 bytes 10 2 2014 12 52 PM MainPrg PRG Task Configuration B
164. P_RET function block works as a trigger The timer which starts when the IN input has its state changed from FALSE to TRUE that is a rising edge it is increased until the PT time limit is reached During the counting the Q output is TRUE otherwise it is FALSE The PT time can be changed during the counting as the block assumes the new value if the counting has not finished Figure 4 69 depicts the TP_RET and Figure 4 70 shows its graphic behavior Figure 4 69 TP_RET Function Block Input parameters Description BOOL This variable when receives a rising edge enables the function block counting PT TIME This variable specifies the function block counting limit time delay Table 4 104 TP_RET Input Parameters 153 4 Configuration Output parameters BOOL This variable is true during the counting otherwise is false TIME This variable shows the current time delay Table 4 105 TP_RET Output Parameters E d t0 u 23 t 1b Q ap LH ey 10 t0 PT t2t2 PT td 144PT Figure 4 70 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 Executes when the co
165. RR_CTS_OFF_TIMEOUT 43 time out while waiting for CTS false in the transmission ERR_CTS_ON_TIMEOUT 44 time out while waiting for CTS true in the transmission NO_ERROR 128 without error since startup Last exception code received by master NO_EXCEPTION 0 FUNCTION_NOT_SUPPORTED 1 QB n 2 eLastExceptionCode pesmi i S EXCERTION EE ND 18 ACCESS_DENIED 128 MAPPING_DISABLED 129 IGNORE_FRAME 255 Communication statistics QB n 3 byDiag_3_reserved Finished communications counter with or without errors The user can test when communication has finished PEN sD wCommGouhter WORD testing the variation of this counter When the value 65535 is reached the counter returns to zero Finished communications counter with errors When the QW n 6 wCommErrorCounter WORD value 65535 is reached the counter returns to zero Table 4 27 MODBUS Relations Diagnostics Disabling Variable variable of Boolean type used to disable individually MODBUS requests configured on request tab via button at the bottom of the window The request is disabled when the variable corresponding to the request is equal to 1 otherwise the request is enabled ATTENTION Differently from other application tasks when a depuration mark in the MainTask is reached the task of a Master MODBUS RTU instance and any other MODBUS task will stop running at the moment that it tries to perform a writing in a memory area It oc
166. RS 485 half duplex RS 422 maximum transceivers 11 1 transmitter and 10 receivers RS 485 maximum transceivers 32 Yes optional via cable selection Baud rate 200 300 600 1200 1800 2400 4800 9600 19200 38400 57600 115200 Protocols Master Slave MODBUS RTU Open protocol Table 2 8 COM 2 Serial Interface Features Notes Physical Interface Depending on configuration of the used cable it is possible to choose the kind of physical interface RS 422C or RS 485 The list of cables can be found at Related Products section RS 422 Maximum Transceivers It is the maximum number of transceivers that can be used on a same bus RS 485 Maximum Transceivers It is the maximum number of transceivers that can be used on a same bus 13 2 Technical Description Ethernet Interfaces NET 1 NX3010 NX3020 NX3030 Shielded female RU45 Maximum cable length Cable type UTP or ScTP category 5 10 100 Mbps Physical layer 10 100BASE TX Data link layer LLC logical link control Network layer IP internet protocol Transport layer TCP Transmission Control Protocol and UDP User Datagram Protocol Client Server MODBUS TCP Client Server MODBUS RTU via TCP HTTP Web server Application layer MasterTool IEC XE programming protocol DNP3 event oriented data reporting SNTP Clock synchronism SNMP Ethernet Network Management LEDs green speed yellow link activity Table 2 9 Ethernet NET 1 Interface F
167. SPa Eaa Taaa vp ivaa Saba inh oR ERa SEES 216 Technical Description and Configuration cccssccccssssssccsssssccssssscscsscscsssssccscssssssscsessssscsessssseseees 218 Minimum Configuration of a Redundant CPU Not Using PX2612 Panel oeenn 218 Typical Configurations of a Redundant CPU eee eesececcessseeeceeseeeeeessaeeceesnaeeecessaaeecessaeeseesaeees 218 NX4010 Mod l rs tioriori aai i E E A E EN E EEE RETRE nema 219 Redundancy Control Panel PX2612 ooo eeeceeessececcesseeccesseeecesseeecsesaeeesessaeeesessaeeesessaeeseesaeees 220 Interconnections between Half Clusters and the Redundancy Control Panel PX2612 0 eee 222 General FeatUressnn iim iir an seeps toe cdet conse des oo gum oe Ms hoe oie cota e sca e ice cas Sues aE ay 223 IPULrChase Datars sa iS ce ste EN fence ee tees Scat ace bac Socata ec Pete festa Seca dees do s facie Seca dese dees Pee 0 225 Principles OF Operation vescscccecesccscceccteencacscesssecscecccaceccsssetecccccaceccssseceeccceedacesscetssucaccacessescdecenecacasscssstessenes 226 NX3030 CPU Identification x2 cco oe nana do soso E EEE EEE E EE EEA 226 Sin le Redundant Projecticsc 2 c s e sc senssespeenosssseodeseupteteseastsdpseheesasnebateapnesatstoneopestoneusastsspaseedparusestsapne 226 Redundant ProjectsStucture iannand dd ove cel ele vdivede eia EEEE tuev n ie thevivietheriedatharte uence 226 IMT Erp le app inn see ee I EE I EO AS LS 231 Diagnostics Commands and User Data Structure eee eeees
168. Shift F8 Fo F10 F8 Shift F 10 Ctrl4 F7 F7 Unforce values Alt F7 Display Mode Figure 5 34 Stopping the Application 210 5 Initial Programming In case the CPU is initialized without the stored application it automatically goes to Stop Mode as it happens when a software exception occurs Writing and Forcing Variables After Logging into a PLC the user can write or force values to a variable of the project The writing command Ctrl F7 writes a value into a variable and this value could be overwritten by instructions executed in the application Moreover the forced writing command F7 writes a value into a variable without allowing this value to be changed until the forced variables be released ATTENTION The variables forcing can be done in the CPU only in the Online mode Diagnostic variables cannot be forced only written because diagnostics are provided by the CPU and must be overwritten by it When a forced writing is done into a redundant variable of the Active PLC the MainTask execution time will be impacted in both Active and StandBy PLC This occurs because the two half clusters will exchange in each cycle information about the forced variables Therefore when forcing variables in a redundant system the user should consider the time added to the task execution time The Table 5 11 exemplifies the medium execution time added to the MainTask with a number of forced variables
169. T 2 port 0 to 4294967295 Counter of errors of transmission through NET 2 port 0 to 65535 Counter of errors in the buffer of transmission through NET 2 port 0 to 65535 Counter of connection losses in the transmission through NET 2 port 0 to 65535 Counter of errors of collision in the transmission through NET 2 port 0 to 65535 Counter of errors of the carrier in the transmission through NET 2 port 0 to 65535 Counter of errors of reception through NET 2 port 0 to 65535 Counter of errors in the buffer of reception through NET 2 port 0 to 65535 Counter of connection losses in the reception through NET 2 port 0 to 65535 7 Maintenance NA QW n 338 QB n 219 QB n 346 QD n 220 QD n 347 QD n 224 QD n 351 QB n 228 QB n 355 QB n 229 QB n 356 QW n 230 QW n 357 QW n 232 QW n 359 QB n 234 QB n 361 QB n 235 QB n 362 QX n 236 0 QX n 363 0 QX n 236 1 QX n 363 1 QD n 237 QD n 364 QD n 241 QD n 368 QB n 245 QB n 372 QB n 246 QB n 373 QD n 247 QD n 374 QD n 375 QD n 502 QW n 338 QW n 340 QW n 342 QW n 344 QB n 346 QD n 347 QD n 351 QB n 355 QB n 356 QW n 357 QW n 359 QB n 361 QB n 362 QX n 363 0 QX n 363 1 QD n 364 QD n 368 QB n 372 QB n 373 QD n 374 QD n 502 BYTE
170. TTENTION Assign a right of access to a master node in the object tree usually means the secondary node will inherit this setting until you get a very specific definition However depending on the device it may be treated differently An the inheritances are not displayed in the dialogues Permissions This field shows user groups defined Each group is preceded by icons indicating the permission given at the time for the device currently selected in the Actions window P Actions currently selected in the Actions window are granted to the group Actions currently selected in the Actions window are denied for the group There is no explicit definition of the right of access to the actions selected at the time in the Actions window If several actions without unique settings for the group are selected no icon is displayed Button bar after selecting the objects and the desired group Actions and permissions window one of the following buttons can be used P Grant Explicitly granted access permission Deny Explicitly denied access permission Clear The right of access granted to the shares currently selected in the Actions window will be deleted i e it returns to the default Applying and Storing the Current Configuration See the respective buttons on the top bar of the dialog misled Fem dots be d in daie The definitions of the configured access rights should be sent to the device to take effect The
171. Time Acronym used to indicate serial reception Supervisory Control and Data Acquisition Supervisory system used for the plant control and operation Stands for screened twisted pair Even UTP cable but all pairs of wires are surrounded by a metal foil or a metal braid screen in order to minimize radiation and susceptibility to external noise It is also known for SUTP Screened Unshielded Twisted Pair or FTP Foil Twisted Pair A device interface that transfers data in serial mode Equipment connected to a communication network that transmits data only if requested by another device called the master Simple Network Time Protocol Protocol for network time synchronization Sequence Of Events Service to monitor the variation of pre configured digital inputs saving the date time of the change and its new state Computer programs procedures and rules related to the operation of a data processing system Device on which integrated circuits or other components fit making it easier to replace them and simplifying the maintenance In a redundant system it s the CPU that oversees the Active CPU not executing the system control but being ready to take control in case of failure on the Active CPU Half cluster PLCA or PLCB which is momentarily in Stand by state Procedure for final clearance of the control system when the programs of all stations and remote CPUs are run together having been developed and verified individually
172. TimeZone xEnable FALSE END_IF GetDayOfWeek GetDayOfWeek function is used to read the day of the week GetDayOfWeek Figure 4 42 Day of Week Reading Returns the day of the week See Section GetDay OfWeek DAYS_OF_WEEK EXTENDED DATE AND TIME Table 4 67 Output Parameters of GetDayOfWeek 117 4 Configuration When called the function will read the day of the week and fill the structure DAYS_OF_WEEK Utilization example in ST language PROGRAM MainPrg VAR DayOfWeek DAYS OF WEEK END_ VAR DayOfWeek GetDayOfWeek Function Blocks of RTC Writing The clock settings are made through function and function blocks as follows SetDateAndTime SetDateAndTime function is used to write the settings on the clock SetDateAndTime Figure 4 43 SetDateAndTime Input parameters REQUEST BOOL This variable when receives a rising edge enables the clock writing Receives the values of date and hour with DATEANDTIME ee S milliseconds See section EXTENDED_DATE_AND_TIME Table 4 68 Input Parameters of SetDateAndTime Output parameters BOOL This variable when true indicates that the action was successfully completed EXEC BOOL This variable when true indicates that the function is processing the values This variable when true indicates an error ERROR BOOL during the Reading Writing Returns the error occurred during the STATUS RTC_STATUS reading configuration See s
173. U Comment Remove POU ExternInterruptPrg00 Open POU Change POU Move Up Move Down Figure 4 6 ExternInterruptTask00 Configuration Screen 49 4 Configuration SOE Configuration The SOE Sequence of Events is responsible for the generation of a sequence of digital events Through the SOE it is possible to analyze the historic behavior of the system variables mapped in its monitoring area The SOE is an exclusive service available for the NX3020 and NX3030 models Once the SOE service has been enabled the CPU starts to behave as a DNP3 server thus it is necessary the support to the DNP3 protocol by the client for the use of this resource The supported object types as well as the function codes and the qualifiers can be found at Annex A The SOE service uses the Q addresses in order to form its base of static data For it it has to be set a continuous area of Q memory where the user will inform its beginning and size divided by two For redundant projects the Q area also has to be redundant so that in the switchover moment the DNP3 server data base is kept The DNP 3 initial address will always be 0 corresponding to QBxxxx 0 and the last address will be Area Size of Q 8 2 1 Thus once defined the static data base the user must copy each digital point which should generate events within the Q continuous area The maximum number of points which can be copied is 8000 For the events configuration it is
174. US remote I O system putting its PROFIBUS masters in active state The active state is used to establish communication with the PROFIBUS remotes slaves The Active CPU also verifies its internal diagnostic and user switchover requests to determine if a switchover is necessary The CPU goes out from the Active state only if it knows the other CPU is in Stand by mode and able to assume as Active However there are some situations where the Active CPU could go out from the Active state even with no certainty that the other CPU is in Stand by state e g if the CPU is switched off 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 PROFIBUS masters are enabled in the passive state The passive mode is used to test the transmission and reception PROFIBUS circuits and the physical layer to avoid an occult failure to happen Total failure in PROFIBUS networks configured as vitals cause a switching to the Inactive state A total failure ina PROFIBUS network damages both composing networks redundant PROFIBUS network and the single composing network non redundant PROFIBUS network If the Ethernet interfaces are enabled with vital failure option clients are enabled in passive state Total failures in Ethe
175. Writing analog output 5 Analog output which can be read or written Holding Register with AND mask with AND mask Holding Register with OR mask Analog output which can be read or written II with OR mask Input Register a Analog input which can be only read Table 4 24 Data Types Supported in MODBUS RTU Master Data Initial Address data initial address of a MODBUS mapping Data Size the size value specifies the maximum amount of data that a MODBUS interface 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 Data Range this field shows the user the memory address range used by the MODBUS interface 70 4 Configuration Requests Configuration Symbolic Mapping Settings The configuration of the MODBUS requests viewed in Figure 4 14 follow the parameters described in Table 4 25 Mappings Requests General Parameters Diagnostics Variable Type NXMODBUS_DIAGNOSTIC_STRUCTS T_DIAG_MODBUS_RTU_MAPPING_1 Generate Diagnostics Variables Generate Disabling Variables Figure 4 14 Data Requests Screen MODBUS Master Default 01 Read Coils 02 Read Input Status 03 Read Holding Registers 04 Read Input Registers 05 Write Coil Function Code MODBUS function type 06 Write Register 15 Write Multiple Coils
176. _RTU Master tCommand bRestart TRUE Diagnostics DG MODBUS Server tCommand bRestart TRUE ELSE The local PLC has entered the Not Active state Diagnostics DG MODBUS RTU_Slave tCommand bStop TRUE Diagnostics DG MODBUS RTU Master tCommand bStop TRUE Diagnostics DG MODBUS Server tCommand bStop TRUE END IF Saves the last state of the local PLC eRedStateLocal old eRedStateLocal END IF Limitations on a Redundant PLC Programming On a redundant PLC there are some limitations regarding its half cluster programming These limitations are treated in the subsections below Limitations in Redundant GVLs and POUs In a redundant GVL or a POU from the program type the following limitations must be respected for a correct functioning of the half clusters e Do not use variables from the type VAR_TEMP e Do not mix variable types VAR VAR_RETAIN VAR_PERSISTENT etc Only one type must be used in each GVL or POU e 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 e 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 268 6 Redundancy with NX3030 CPU e Do not use the function blocks for RTC reading and writing in redundant POUs More details can be found on the ch
177. _SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE FB_SET_CTRL_NOT_ALLOWED NOT_CONFIGURED Table 4 93 SERIAL_SET_CTRL Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Set Control SERIAL SET CTRL Port SERIAL PORT COM1 Status SERIAL STATUS END_ VAR INPUTS Set _Control REQUEST TRUE Set _Control PORT Port Set _Control RTS VALUE FALSE Set_Control RTS_ EN FALSE Set _Control DTR VALUE FALSE Set _Control DTR_EN FALSE Set _Control BREAK FALSE FUNCTION Set_Control OUTPUTS Set Control DONE Set_Control EXEC 143 4 Configuration Set_Control ERROR Status Set _Control STATUS error SERIAL_TX If it s necessary to treat the 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 SERIAL_TX CLEAR_R amp _BEFORE_TX TX_TRANSMITTED Figure 4 60 Block for Values Transmission by the Serial Input parameters Type REQUEST BOOL PORT SERIAL_PORT TX_BUFFER_POINTER POINTER TO BYTE UINT TX_BUFFER_LENGTH TX_TIME OUT UINT UINT BOOL Table 4 94 SERIAL_RX DELAY_BEFORE_TX CLEAR_RX_BEFORE_TX Outp
178. a Itsy and the parameter Write 0 0 0 0 0 0 0 0 to 255 255 255 255 Mask Filter IP Write Filter IP 0 0 0 0 to 255 255 255 255 Specifies a IP interval with reading access to the declared variables in the MODBUS relation 5 Specifies a subnet mask sea UES and the parameter Read 0 0 0 0 0 0 0 0 to 255 255 255 255 Mak Filter IP Table 4 59 IP Filters of Modbus Server Read Filter IP 0 0 0 0 to 255 255 255 255 Note Filters the filters are used to establish an IP addresses interval which have writing or reading access in the MODBUS relations individually configured The permission criteria is made through an AND logic operation between the Write Filter Mask and the client IP address In case the result is the same as the Write Filter IP the client has writing right E g if the Write Filter IP 192 168 15 0 and the Write Filter Mask 255 255 255 0 then only clients with IP 192 168 15 x will have writing right The same proceeding is applied to the Read Filter parameters to define the reading rights In the previously defined relations the maximum MODBUS data size can be 65536 maximum value configured in the Data Size field However the request which arrives in the MODBUS Ethernet Server must address a subgroup of this mapping and this group must have at most the data size depending on the function code which is defined below e Read coils FC 1 2000 e Read input status FC 2 2000 e Read holding registers FC 3 125 e Re
179. a client to a server need to be confirmed by the server through an ACK message transmitted to the client o All response messages sent by a client to a server need to be confirmed by the server through an ACK message transmitted to the client o If one of the parts does not receive the ACK message within the time defined by the TCP time out the message will be retransmitted by the origin address see TCP number of tries parameter o The ACK message does not need to be exclusive The ACK needed to be sent by the server to the client at the moment it receives a request can be included in the same answer message and the ACK needed to be sent by the client to the server at the request moment can be included in the same message including the next request The following pictures depict the difference between the sending of an immediate and a calibrated ACK a Client Server Message request 1 Message request 1 ACK Processing time of request 1 Message response 1 Message response 1 ACK Message request2 Message request2 ACK Processing time of request 2 Message response 2 Message response 1ACK Message request3 be time Figure 4 2 Example of an Immediate ACK Sending 0 46 4 Configuration Client Server Message request 1 Processing time of request 1 Message request 1 ACK response 1 Processing time of request 2 Message request2 ACK response 2 Message response 1 ACK request2 Message
180. a or all 60 2 Class Objects Class 1 1 read 06 no range data or all 07 08 limited qty 80 1 Internal Indications 1 read 00 01 start 129 00 start Packed format stop response stop 2 write 00 start stop index 7 329
181. a transition several conditions can trigger it These conditions must be analyzed in the sequence they appear in the sub section Any condition that goes true can cause a transition If a condition causes a transition the next conditions don t need to be analyzed 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 Such commands were mentioned preliminary in the Diagnostics Commands and User Data Structure section and are better described in the Redundancy Commands section In the following sub sections to simplify these commands are not mentioned but one must remember they can cause the same transitions as the PX2612 button 247 6 Redundancy with NX3030 CPU Transition 1 Not Configured to Starting ATTENTION The conditions of this sub section must not be analyzed in case the other CPU is in Active state and the projects are different This CPU must remain in the Not Configured state while its project is different from the other CPU project if the other is in Active state This note isn t valid if the project automatic synchronization is disabled see Project Synchronization Disabling section as in this case differences b
182. ables in other words allocate redundant memory In the same way symbolic variables when function block instances are declared in the NonSkippedPrg program or when the GVL isn t marked as redundant such instances are non redundant Multiple Mapping If the user desires to map the redundant command variables in more than one communication port COMx or NETx it s necessary the implementation of a control by the user within his own application The control logic to be implemented must write in the redundant command variables based on the variables commands values from each communication port COMx or NETx Besides that the control logic must restart the communication ports command variables as the redundancy control just restarts its own command variables The following is an example of this implementation VAR var StandBy command Ethernet_relation BOOL var StandBy command Serial relation BOOL var Inactive command Ethernet_relation BOOL var Inactive_command Serial relation BOOL var TurnOn command Ethernet_relation BOOL var Turn command Serial relation BOOL END_ VAR Logic to put the local PLC in StandBy IF var StandBy command Ethernet relation TRUE THEN DG_NX4010 tRedundancy RedCmdLoc bStandbyLocal TRUE var StandBy command Ethernet _relation FALSE END_IF IF var StandBy command Serial relation TRUE THEN DG_NX4010 tRedundancy R
183. ad IEC Variable 100 8192 0 Mapping Diagnostics Area 66962 Used range QB66962 QB66969 Figure 4 18 MODBUS Function In Table 4 30 the number of factory default settings and the values for the column options may vary according to the data type and MODBUS function FC Configuration Default Value Options Read Write MODBUS function type Read Read Write Write Mask Polling ms Communication period ms 0 to 3600000 Mapping Diagnostic Initial address of the MODBUS relation 0 to 2147483640 Area diagnostics Q Reading Initial Initial address of the MODBUS read 1 to 65536 Address data R 5 Depends on the Reading Data Size Number of MODBUS read data Writing Initial Initial address of the MODBUS write Address data Writing Data Size Number of MODBUS write data IEC Writing Variable Initial address of the write variables Q Writing Mask of IEC Initial address of the variables for the Variables write mask Q Table 4 30 Device Mapping 1 to 65536 Depends on the function used 0 to 2147483647 0 to 2147483644 i IEC Reading Variable a address of the read variables o 0 to 2147483646 fo i 77 4 Configuration Notes Function the available data types are detailed in the Table 4 24 and MODBUS functions CF are available in the Table 4 26 Polling this parameter indicates how often the communication set for this relation must be executed At the end of communication will be awaited a t
184. ad input registers FC 4 125 e Write single coil FC 5 1 e Write single holding register FC 6 1 e Force multiple coils FC 15 1968 e Write holding registers FC 16 123 e Mask Write FC 22 1 e Read Write holding registers FC 23 o Read 121 o Write 121 ATTENTION Differently from other application tasks when a depuration mark in the MainTask is reached the task of an Ethernet Server MODBUS instance and any other MODBUS task will stop running at the moment that it tries to perform a writing in a memory area It occurs in order to keep the consistency of the memory areas data while a MainTask is not running 110 4 Configuration Communication Performance Communication Rate of a MODBUS Server Device The MODBUS devices configurable in the Nexto CPU run in the background with a priority below the user application and cyclically Thus their performance varies depending on the remaining time taking into account the difference between the interval and time that the application takes to run For example a MODBUS device in an application that runs every 100 ms with a running time of 50 ms will have a lower performance than an application running every 50 ms to 200 ms of interval It happens because in the latter case the CPU will have a longer time between each MainTask cycle to perform the tasks with lower priority It also has to be taken into account the number of cycles that the device slave or server takes to
185. address plus the read data size will result in the range of read data for each request Initial Address of the Write Data field for the initial address of MODBUS write data Write Data Size the minimum value for the size of the write data is 1 and the maximum value depends on the MODBUS function FC used as below Write Coil HR 5 1 Write Holding Registers FC 6 1 Write Multiple Coils FC 15 1968 Write Holding Registers FC 16 123 Register write mask FC 22 Read Write Holding Registers FC 23 121 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 Diagnostics 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 48 n is the value configured in the field Diagnostics Initial Address in Q Direct Diagnostics of Representation T_ DIAG_MODBUS_ETH_MAPPING_1 Description Variable Type Variable Communication Status Bits Nore idle waiting to QX n 1 bCommExecuting Active communication communication Communication disabled The bCommidle bit is restarted in this condition Communication deferred because the maximum number of concurrent r
186. aded Modifications The off line downloaded modifications through this procedure usually are the following e Insertion of new devices in the devices tree e Property or parameter change in devices existing in the devices tree Such devices are normally the following Modules such as PROFIBUS master NX5001 or Ethernet modules NX5000 Ponto Series PROFIBUS remotes I O modules inside Ponto Series PROFIBUS remotes Modbus communication I O drivers Mapping of Modbus communication drivers The following cares must be taken at editing these project modifications e Ifa device existed in the previous project version and continues existing in the modified version the I and Q variables allocated for it must remain the same command diagnostic inputs and outputs Care must be taken for the inserted modifications don t change such allocations e Ifa device was inserted in the modified project version the I and Q variables allocated for it must not be allocated in the previous project version command diagnostic inputs and outputs Step 5 Inactive PLC Project Synchronism Disabling In the procedures described in the On Line Download of Modifications and Off Line Download of Modifications with Process Control Interruption sections the project is automatically synchronized from the Active PLC to the Non Active PLC However during the procedure of off line downloading without process control interruption the project synchronism m
187. ak Pou Priorty Type interval Event _ MainTask MainPrg 13 cyce 100ms Table 5 3 Task of the Single Profile In the Basic project profile the application has a user task from the Freewheeling type called MainTask which executes the program in a continuous loop with no definition of cycle time with priority fixed in 13 This task is responsible for the execution of a single programming unit POU called MainPrg It is important to stress that the cycle time can vary according with communication task quantity used as in this mode the main task is interrupted by communication tasks This profile allows the inclusion of two event tasks with higher priority which can preempt the MainTask at any moment the task called ExternInterruptTask00 is an event task from the Extern type with priority fixed in 02 the task called TimeInterruptTask00 is an event task from the cyclic type with priority fixed in 1 The basic project model includes these three task already completely defined as shown in the The developer needs only to create the associated programs Priority Type Interval_ Event _ MainPrg Freewheeling ExterninterruptTask00O ExterninterruptPrg00 o2 Exen IO_INT_O TimeinterruptTask00 TimeinteruptPrgoo oi Oye zoms Table 5 4 Basic Profile Tasks In the Normal profile the application has a user task from the cyclic type called MainTask This task is responsible for the execut
188. and Connection Downtime Time out 103 4 Configuration Configuration Default Value Options Time for the instance execution ae gyae within the cycle without considering 50 5to 100 its own execution time Connection Maximum idle time between client Downtime and server before the connection is 10 10 to 3600 Time out s closed by the server Table 4 54 Advanced Configurations Notes Task Cycle the user has to be careful when changing this parameter as it interferes directly in the answer time data volume for scanning and mainly in the CPU resources balance between communications and other tasks Connection Inactivity Time out this parameter was created in order to avoid that the maximum quantity of TCP connections is reached imagining that inactive connections remain open on account of the most different problems It indicates how long a connection client or server can remain open without being used without exchanging communication messages If the specified time is not reached the connection is closed releasing an input in the connection table MODBUS Server Diagnostics Configuration via Symbolic Mapping The diagnostics and commands of the MODBUS server protocol configured either by symbolic mapping or by direct representation are stored in variables of type T_DIAG_MODBUS_ETH_SERVER_1 and the mapping by direct representation are in 4 byte and 8 word which are described in Table 4 55 n is the value config
189. and by state allowing it to take the process control e To put the half cluster having its module changed in Inactive state through the Redundancy Control Panel PX2612 or the Redundancy Commands e Execute the necessary exchanges in the Inactive half cluster as indicated in the CPU Configuration General Parameters How to do the Hot Swap chapter e To put the half cluster back to Stand by or Active state according to necessity MasterTool Warning Messages When MasterTool is with a redundant project open or when it s connected to a NX3030 CPU identified as PLCA or PLCB some special warning messages may occur as described in the following sub sections Blocking of Redundant or Non Redundant Project Download MasterTool doesn t allow the download of a redundant project unless the CPU is NX3030 and is identified as PLCA or PLCB see NX3030 CPU Identification section On the other hand MasterTool doesn t allow the download of a non redundant project in a NX3030 CPU identified as PLCA or PLCB In case any of these illegal actions is tried MasterTool warns with a correspondent message Warnings before Commands which may stop the Active PLC Some commands as the following may stop a PLC Offline load after Online Login Debug Stop Debug New Breakpoint Online Reset warm cold origin In case MasterTool is logged to the Active PLC and one of these commands is tried before sending it to the Active PLC Mast
190. and confirm with OK to integrate them to the list of specific device user management groups 176 4 Configuration LA Edit The currently selected group can be modified with regard to its name an 2 Edit Th ly selected group can be modified with regard d associated users For this we use the Edit Group dialog lt group name gt which corresponds to the Add Group dialog Delete The currently selected group will be deleted Applying and Storing the Current Configuration See the respective buttons on the top bar of the dialog ice amp i 5 Unload fom daia S Dower io dnin The current configuration of user management should be sent to the device to make it effective The setting currently applied to the device can be charged in the configuration dialog ar Load from disk g Save to disk The current configuration can be stored in an XML file dum and reloaded from this file which is useful for configuring the same user configuration on multiple systems The standard dialog to browse files on the system will be provided for this purpose The file filter is automatically set to dum specific file user management The current settings can be printed or documented through the Print command File menu and Document Project menu respectively Default User and Groups Considerations Default user and groups existing in the device and loaded in the project from button Upload from Device was chang
191. andard MasterTool Project selected Initially the user must inform the desired name for the project and the directory where he desire to save it as shown on Figure 6 15 New Project Categories Templates General g Empty Library MasterTool Standard Project Creates a new project automatically induding the corresponding CPU and selected POUs and Tasks Name NextoRedundant Location C gt ive C 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 e Select the CPU model As the redundancy is implemented only in NX3030 it must be selected by the user e Select the rack model There are three rack available models and the choice depends on the module quantity used in the redundancy For MasterTool is important the rack size according to the configured networks quantity next wizard item e Select the power supply model e Select the redundancy configuration For a redundant project is needed to choose With Redundancy option e Select the operation mode of redundancy In this case the option in operation are with panel of redundancy or without PX2612 e Select if the OPC communication option will work or don t e Select if will be used redundancy with bus expansion 2
192. ands e 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 e First the Diagnostics Exchange and Commands service is executed e Second the Redundant Data Synchronization service is executed e Third the Redundant Forcing List Synchronization service is executed Diagnostics and Commands Exchange This service is responsible by the interchange of the following data structures in each MainTask cycle To copy RedDgnLoc from PLCA to PLCB RedDgnRem To copy RedCmdLoc from PLCA to PLCB RedCmdRem To copy RedUsrLoc from PLCA to PLCB RedUsrRem To copy RedDgnLoc from PLCB to PLCA RedDgnRem To copy RedCmdLoc from PLCB to PLCA RedCmdRem To copy RedUsrLoc from PLCB to PLCA RedUsrRem The service will be executed using only one synchronism channel NETA or NETB This way the service can be completed even if one channel has problems Redundant Data Synchronization This service is responsible for the redundant variables transferring from the Active CPU to the Inactive CPU As previously described there are symbolic redundant variables and also redundant direct representation variables I M and Q F
193. applied to the RTC In the beginning of the DST it has to be used a function to increase the time zone in one hour At the end of the DST it is used to decrease it in one hour For further information see the section RTC Clock of this manual Serial Interfaces Configuration COM 1 The COM 1 communication interface is composed by a DB9 female connector for RS 232C pattern It allows the point to point communication or in network by using a converter in MODBUS RTU slave or MODBUS RTU master the open protocols The parameters which must be configured for the proper functioning of the application are described below z Serial channel type j s Serial Type RS 232C RS 232C Serial communication port 200 300 600 1200 1800 2400 4800 Baud Rate need configuration 119200 9600 19200 38400 57600 115200 bps Odd Even sa arid None Parity Always One 9 Parity Always Zero No Parity Sets the serial Data Bits communication character 5 6 7 and 8 Stop Bits 7 the serial port stop 1 1 5 and 2 Extended Mode Extended operation Sets the serial port mode which delivers information Serial Mode operation mode Normal Mode regarding the received data frame configuration Normal Mode Serial communication normal operation mode bits quantity Table 4 8 COM 1 Configuration Notes Extended Mode This serial communication operation mode provides information regarding the data frame received The information available is the foll
194. apter RTC Clock Non redundant Program Limitations NonSkippedPrg In a POU from the program type which aren t redundant the case of a NonSkippedPrg POU the following limitations must be respected for a correct functioning of the half clusters e The traditional function blocks TON and TOF can t be used as they use the IEC timer When the Stand by PLC goes to Active state with the other half cluster coming out of Active state the IEC timer is synchronized causing a discontinuity in the timer value The function blocks TON_NR and TOF_NR must be used instead available in the NextoStandard library See Configuration Non Redundant Timer e POUs from the program type written in the SFC language Sequence Function Chart must not be used as they use the IEC timer for transition timing e 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 Getting the Redundancy State of a Half Cluster It is possible to verify the redundancy state of a half cluster in the Redundancy Diagnostics Structure VAR eRedStateLocal REDUNDANCY STATE END _ VAR eRedStateLocal DG _NX4010 tRedundancy RedDgnLoc sGeneral Diag eRedState This way the user can control a program logic that depends on redundancy state of the PLC Reading Non Redundant Diagnostics A redundant project besides present redundant d
195. arameters which cannot be accessed otherwise The three functions regarding advanced diagnostics are in the Nexto Standard library and are described below GetTaskInfo This function returns the task information of a specific application 317 7 Maintenance GetTaskInfo GetTaskInfo 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 psAppName POINTER TO STRING Application name psTaskName POINTER TO STRING pstTaskinfo POINTER TO stTasklnfo Pointer to receive the application information Table 7 10 GetTaskInfo Input Parameters The data returned by the function through the pointer informed in the input parameters are described on Table 7 11 Returned Parameters Size Description _ O Task cycle time execution with 1us resolution dwAvgScanTime DWORD Task cycle average time with 1us resolution dwLimitMaxScan DWORD Task cycle maximum time before watchdog occurrence dwlECCycleCount DWORD IEC cycle counter Table 7 11 GetTaskInfo Returned Parameters Possible ERRORCODE e NoError success execution e TaskNotPresent the desired task does not exist Example of utilization in ST language PROGRAM MainPrg VAR sAppName STRING psAppName POINTER TO STRING sTaskName STRING psTaskName POINTER TO STRING pstTaskInfo POINTER TO stTaskInfo TaskInfo stTaskInfo Info ERRORCODE
196. ared modules were detected in the bus SWAPPED TRUE TRUE There are changed MODULES bSwappedModule modules in the bus FALSE There are no changed modules in the bus NON TRUE One or more modules in the DECLARED bNonDeclaredModules bus were not declared in the MODULES configuration MODULES W PREY TRUE One or more modules in the DIAGNOSTICS bModulesWithDiagnostic bus are with active diagnostic FALSE There is no active diagnostic in the modules in the bus MODULES W TRUE One or more modules in the FATAL ERROR DOANE Fatale ine bus are in fatal error FALSE all modules are working properly MODULES W bhiod leP rameterErto TRUE One or more modules in the PARAM ERROR bus have parameterization error FALSE All modules are parameterized TRUE Master indication there is BUS ERROR failure in the WHSB bus bWHSBBusError FALSE The WHSB bus is working properly HARDWARE QB n 1 ss FAILURE bHardwareFailure TRUE CPU hardware failure 306 4 2 3 4 5 7 1 0 7 Maintenance FALSE The hardware is working properly SOFTWARE p TRUE One or more exceptions j EXCEPTION pSoftwareExcepticn generated by the software i FALSE No exceptions generated in the software i daa ERROR IN TRUE The memory card is inserted fa MEMORY CARD bMemorycardErtor in the CPU but is not working properly i FALSE The memory card is working properly TRUE
197. ariable and Write Mask of IEC Variables fields since the creation of a relation can be performed at any time on application development The MasterTool IEC XE software itself allocate a value from the range of direct representation output variables Q still unused Factory default cannot be set to the Reading Writing Data Size fields as they will vary according to the MODBUS data type selected ATTENTION Unlike other tasks of an application when a mark is reached at MainTask debugging the MODBUS Ethernet Client instance task or any other MODBUS task will stop being executed at the moment it tries to write in the memory area This occurs in order to maintain data consistency of memory areas while MainTask is not running MODBUS Ethernet SERVER This protocol is available for all Nexto Series CPUs on its Ethernet channels When selecting this option at MasterTool IEC XE the CPU becomes a MODBUS communication server allowing the connection with MODBUS client devices This protocol is only available when the CPU is in execution mode Run Mode There are two ways to configure this protocol The first one makes use of direct representation Q in which the variables are defined by your address The second one through symbolic mapping where the variables are defined by your name The procedure to insert an instance of the protocol is found in detail in the MasterTool IEC XE User Manual MU299048 or on Initial Programming Inserting
198. arts the user application after the hardware watchdog reset or through the Runtime restart but keeps the diagnostics indication via LED WD and via Diagnostics Area Q 39 Automatically allocated in the project creation NX3010 520 NX3020 681 NX3030 681 Retain Area Q NX3010 4096 NX3020 4096 NX3030 4096 NX3010 8192 NX3020 16384 NX3030 16384 NX3010 0 to 32248 NX3020 0 to 64855 NX3030 0 to 97623 It is not possible to change the size of the CPU diagnostics area NX3010 0 to 32766 Memory size of retentive data NX3020 0 to 65534 Memory size of retentive data NX3030 0 to 98302 Memory size of retentive data NX3010 0 to 8192 NX3020 0 to 16384 NX3030 0 to 16384 Persistent Area Q NX3010 12288 NX3020 20480 NX3030 20480 NX3010 8192 NX3020 16384 NX3010 8192 NX3020 16384 NX3030 16384 CPU Parameters Disable NX3010 0 to 32766 Memory size of retentive data NX3020 0 to 65534 Memory size of retentive data NX3030 0 to 98302 Memory size of retentive data NX3010 0 to 8192 NX3020 0 to 16384 NX3030 0 to 49152 Enable Disable 4 Configuration Hot Swap Hot Swap Mode Initial Time out x100 ms ACK Delay x10 ms Generate error on tasks watchdog consistency Consist retain and persistent area in Q ATTENTION variables Enable without consistency in the Hot module change start Disable for
199. as inner temperature reading only and local time reading only Just below the graphic display there are 2 LEDs used to indicate alarm diagnostics and watchdog circuit The Table 2 1 shows the LEDs description For further information regarding the LEDs status and meaning see Maintenance Diagnoses via LED chapter LED DG Diagnostics LED Table 2 1 LEDs Description Nexto Series CPUs has two switches available to the user Table 2 2 shows the description of these switches For further information regarding the diagnostics switch see chapters One Touch Diag and CPU s Informative and Configuration Menu For further information regarding the MS switch see Configuration Memory Card Interface 2 Technical Description Switch placed on the module upper part Used for diagnostics visualization on Switch the graphic display or for navigation through the informative menu and CPU configuration ms Switch placed on the frontal panel Used to securely remove the memory card Table 2 2 Keys Description Diagnostics On the frontal panel the connection interfaces of Nexto Series CPUs are available These interfaces are Ethernet communication serial communication and memory card interface Table 2 3 presents a brief description of these interfaces Available on me imertaces Avaiabieon eserption RJ45 communication connector standard 10 100Base T X NX3010 Allows the point to point or network communication thro
200. ase the differences between the Simulation Mode and the behavior with the Nexto Series CPUs are not checked Therefore the best practice is to avoid the use of variables of direct representation whenever it is possible so as to avoid reworking when developing a logic that will be tested in simulation and then loaded into a CPU The Simulation mode can also be used to simulate a redundant project However it will have the same limitations described previously being able only to test the application logic that does not depends on the hardware In this case the POUs NonSkippedPrg and ActivePrg will always be executed as if the simulated PLC was the Active PLC 213 5 Initial Programming Project Upload Nexto Series CPUs allow the project storing in the product memory which can be uploaded and reused through the MasterTool IEC XE software To store a project in the product memory the CPU must be connected Login and the option to send the source download implicitly at program download must be selected To upload the project previously stored the options shown on Figure 5 37 must be selected File Edit View Project Build 1E New Project Ctl4 n gt OpenProject Ctrl 0 Close Project A pe iE Save Project Ctrl S Save Project As Project Archive gt Source download in a 2 kpl amp Print P O Page Setup m Recent projects b b Exit altara F rrom Figure 5 37 Project Upload O
201. asterTool IEC XE Installing Please wait while Setup installs MasterTool IEC XE on your computer Extracting files C Managed Libraries System VisuElemsSpecialControls 3 4 4 0 browsercache Figure 3 23 MasterTool IEC XE Installation Screen After the installation is finished the next screen will be shown In this window it is strongly recommended to choose the restart option Click FINISH to conclude the installation proceeding 15 Setup MasterTool IEC XE E Completing the MasterTool IEC XE Setup Wizard To complete the installation of MasterTool IEC XE Setup must restart your computer Would you like to restart now Yes restart the computer now No I will restart the computer later _ wv MacterTonol Ef YE Figure 3 24 Installation Complete 37 3 Installation The MasterTool IEC XE is installed and ready to use To execute click on the MasterTool IEC XE shortcut in Altus gt MasterTool IEC XE created during the installation in Start Menu The first time the software is initialized a screen requesting registry information will appear After filling the fields correctly click on CONFIRM to use the MasterTool IEC XE Ww MasterTool IEC XE axa he Enter the product license Company Serial number Software key Figure 3 25 Registry Information Screen If there is already versions of MasterTool IEC XE installed in the computer the installer will
202. ation Default Value Options Initial Address of is Diagnostics in oo of the diagnostic 0 to 2147483628 Q variables editing Slave Address MODBUS slave address 1 to 255 Disabling of Initial address used to disable Mappings MODBUS relations Los 0102141483044 Table 4 36 Address and Direct Representation Variables Settings Notes Initial Address of Diagnostics in Q this field is limited by the size of output variables addressable memory Q of each CPU which can be found in chapter Technical Description Slave Address it is important to note that the Slave accepts requests broadcast when the master sends a command with the address set to zero Moreover in accordance with standard MODBUS the valid address range for slaves is 1 to 247 The addresses 248 to 255 are reserved Disabling of Mappings composed of 32 bits used to disable individually the 32 MODBUS relations configured in Slave mappings space The relation is disabled when the corresponding bit is equal to 1 otherwise the mapping is enabled This field is limited by the size of output variables addressable memory Q of each CPU which can be found on Technical Description chapter Default Value the factory default value cannot be set for the Initial Address of Diagnostics in Q and Disabling of Mappings fields since the creation of a relation can be performed at any time on application development The MasterTool IEC XE software itself allocate a value fr
203. ation to prevent variable mapping in non redundant areas Breakpoints Utilization in Redundant Systems For redundant systems it s recommended to use breakpoints only in the Active half cluster with the other half cluster deactivated If not when the application execution reaches a breakpoint the Stand by breakpoint will take over the Active state switching off the Active PLC MODBUS Instances Managing in Redundant System The MODBUS instances are independent from the redundancy thus they must be managed in the application when it s up to the user to choose which instances must be enabled disabled when a PLC goes to Non Active state The example below inserted in a NonSkippedPrg program executes the verification of the PLC current state and in case it s in Non Active state disables the MODBUS RTU instances master and slave and the MODBUS Ethernet Server instance VAR eRedStateLocal REDUNDANCY STATE eRedStateLocal old REDUNDANCY STATE END_ VAR Local PLC current state reading eRedStateLocal DG _NX4010 tRedundancy RedDgnLoc sGeneral Diag eRedState Has the local PLC state changed IF eRedStateLocal lt gt eRedStateLocal old THEN IF eRedStateLocal REDUNDANCY STATE ACTIVE THEN The local PLC has entered the Active state T Diagnostics DG MODBUS_RTU Slave tCommand bRestart TRUE Diagnostics DG MODBUS
204. bRedForceSync bApplicationIncompatible bProjectSyncDisable bIncompatibleFirmware QB n 5 bApplicationProjectDiff bProjectArchiveDiff bOnlineChangeApply bFailedRED NX4010 microprocessor TRUE The Redundant Data Synchronization service was executed successfully in this MainTask cycle FALSE The Redundant Data Synchronization service wasn t executed successfully in this MainT ask cycle TRUE the Redundant Forcing List Synchronization service was executed successfully in this MainT ask cycle FALSE the Redundant Forcing List Synchronization service wasn t executed successfully in this MainT ask cycle TRUE The application isn t compatible between the PLCs Was done a new application download with one of the following changes e Changes in redundant memory area e Changes in symbolic redundant variables Whereas this diagnostic be TRUE one of the PLCs will stay in Inactive state until the same application be present in the two PLCs This implies in reload the old application or download the new application to both PLCs More information about how to proceed can be found in section Redundant CPU Program Downloading FALSE The application is compatible between the PLCs TRUE The project application and project archive will not be synchronized between the PLCs It s a copy from the non volatile variable used to enabling or disabling the project synchronization as described in t
205. btracted from the answer to be included in PV When true the sample time is measured When MeasureST false the sample time is informed by the user in the SampleTime variable When true the PID block is restarted initializing all variables It can also be used to erase the integral and derivative actions and the error codes in the block output IntegralAction Stores the integral action which is eliminated in error state Table 4 98 PID Block Input Parameters Restart 149 4 Configuration Sues parameters po REAL Manipulated Variable Real sample time in seconds used for the lel ae derivative action and MV limit rate calculus Eff3ST REAL Real sample time from the last three cycles in seconds used for the derivative action calculus Real sample time maximum value in seconds Maren REAL since the PID block initialization Real sample time minimum value in seconds MinENST REAL since the PID block initialization ONoahWN Error code showed by the PID block To remove it the problem must be solved and the block restarted through the Restart variable The error codes are described below 0 no error MaxMV lt MinMV MaxPV lt MinPV PV gt MaxPV ErrorCode UINT lt PV lt MinPV Ti lt 0 001 s with the integral action enabled Td lt 0 s with the derivative action enabled Gp so MaxVarMV lt 0 9 DeadBand lt 0 10 SampleTime lt 0 001 s or SampleTime gt 1000 s with MeasureST
206. cLogic Application See below how to set access permissions and how to make them to be uploaded to the device or stored in a rechargeable file To set the permission to perform an action on one or more objects select them below the desired type of action in the Actions window Then select the desired group in the Permissions window and click the Grant or Deny button also the Permissions window See the following description of specific dialogs This part of the dialog lists the actions that can be performed during the run in files on the CPU file system and execution objects such as applications The tree is structured as follows Lj Categories of objects At the top level for structuring purposes are the folders relating to the objects of the file system and tax collection Types of action In this folder there are nodes to the four types of actions that may be running on specific objects These nodes are used only for structural purposes F Add Remove side addition or removal of secondary objects to an existing object F Execute for example start stop applications setting breakpoints etc Modify for example sending applications etc F View monitoring Objects action devices In each action node type are the devices objects of action e g Device 180 4 Configuration These objects mapped in the device tree or structure of the file system are displayed in a structured way A
207. careful in formatting cells with floating point values Utilization example in ST language 158 4 Configuration PROGRAM MainPrg VAR eLogError USER LOG ERROR CODES sMessage USER_ LOG MESSAGE END _ VAR IF m_rTemperature gt MAX TEMPERATURE ACCEPT THEN sMessage Temperature higher than expected sMessage concat sMessage REAL TO STRING m_rTemperature sMessage concat sMessage eLogError UserLogAdd USER_LOG EVENT WARN sMessage eLogError variable gets possibles function errors END IF Log file content example UserLog 201308271506245738 csv Model NX3030 Serial number 445627 Firmware version 1 4 0 4 27 08 2013 15 06 24 5738 WARN Overt 27 08 2013 16 37 45 3476 WARN Over 28 08 2013 09 10 55 4201 WARN Overt mperature 25 mperature 25 mperature 26 ct ct ct UserLogDeleteAll The UserLogDeleteAll function performs the deletion of log files present in the directory created specifically for the CPU in which is inserted the memory card i e are only deleted the logs contained in the directory named with the CPU firmware version that exists within the directory with the CPU serial version The log files deleted are only files that exist at the time of memory card mounting and the generated by the UserLogAdd function Logs of other CPUs and files added manually by th
208. cation between the LCD screen and the main processor Exception code generated by the RTS Level in percentage of charge in the processor Reserved CPU Startup status 01 Hot start 02 Warm Start 03 Cold Start PS These variables are restarted in all startup Counter of cold startups It will be added only due hot removal of the CPU in the bus and not due to the command of Cold Reset from MasterTool IEC XE 0 to 65535 Counter of hot startups It will be added only during a sequence of startup of the system and not due the command of Hot Reset from MasterTool IEC XE 0 to 65535 Counter of disorders lower than the time of support to failures in the CPU power supply 0 to 65535 Counter of reset performed by the RTS Runtime System 0 to 65535 Reserved The CPU was restarted due a failure in the power supply in the last startup The CPU was restarted due the active watchdog in the last startup Alarm generated due internal temperature at 85 C or above it Alarm generated due internal temperature at 0 or under it 7 Maintenance QD n 38 QD n 38 QD n 38 DINT QB n 42 QB n 42 QD n 43 QD n 43 AQD n 47 QD n 47 QW n 51 QW n 51 QW n 53 QW n 53 QW n 55 QW n 55 QW n 57 QW n 57 QW n 59 QW n 59 QW n 61 QW n 61 QW n 63 QW n 63 QW n 65 QW n 65 QB n 67 QB n 67 QD n 68 QD n 68 Q
209. cation error For example if the slave does not respond to a request and the master is set to send three retries the error counter number is incremented by one unit when the execution of these three retries After the increase of the communication error trying to process restarts and if the number of retries is reached again new error will increment the counter Mappings Configuration Symbolic Mapping Settings The MODBUS relations configuration showed on Figure 4 13 follows the parameters described on Table 4 23 Mappings Requests General Parameters Figure 4 13 MODBUS Data Mappings Screen 69 4 Configuration Configuration Value Variable Symbolic variable name aes ae cal of a variable declared in a program or aes ae cal 1 to Fiwessss Data Initial Initial address of the MODBUS Address data Data Size Size of the MODBUS data 1 to 65536 Table 4 23 MODBUS Mappings Settings Defaut Options Write Coil 1 bit Read Coil 1 bit Write Holding Register 16 bits Read Holding Register 16 bits Darai ype MODBUS gata type Holding Register AND Mask 16 bits Holding Register OR Mask 16 bits Input Register 16 bits fee Status 1 bit toe5538 Notes Value Variable this field is used to specify a symbolic variable in MODBUS relation Data type this field is used to specify the data type used in the MODBUS relation DataTye Size fits Description
210. cccccessecceceeseccceucsecscuescsseueseceseueeeceeuens 28 RS 422 NetWork EXAMP e iiite aina E E E E EEEE EE REEERE eesti 29 Memory Card Tinstallatio in ccccccc cece ies tececcsenchctcvccactausscencccsccsstacsccencccsecsssausccensccsecssteusscescccsecsvencvcceneiee 31 Summary Architecture Installation ssccscsccssssssssecssseessceesssesssseesscseesscsssssceesscsessscsssnssessscssesscsssscssssscsessseseones 32 Module Installation on the Main Backplane Rack sseeseeesseessesrerssrrersssrersssreerssrrerssrieessereesserresssree 32 Programmer Installation sescsccessvashseseces cucvevcsessscsesesesessonsssacesesctesdsesssnsesecesecssoassnscdesssecssosssnsctosssesesesdseseeesses 32 CONFIGURATION orecsiesteistyestatsteestetits outuestsovguostnessuossessoupseeessuvsaves venvecessvstenssesseasseesdersessdvensesssvensteovsceses 39 CPU COmPio uration scicccsccccccccocccccesonscasecoscsssescsccagecesssstuscsccegecesssereccsstegecesscesecesstegedecscesssesstegsdecsterseusssegedesses 39 General Parameters ssvexcvsvevexsvessveaiassavaataesaxaataevaveavasvavaataesaxaadaevaxaataevavaasaevanaataevaxaaiasvavaaiasvansasaetananaasiaaay 39 External Event Configuration siros a s ena e a EE ani anni niin ini 48 SOE CON SurathOni sie i seek cadena ska eked che Soke T EE Cobo tub nGeho Sea edad advo Gab i ETET E E eaS 50 amesS yNCHroOmiZatiOn siriene ee eeen eea Ee Ee EEE AEE A EE Oe EER bananas CEE E E Ea EA ENERE ERS 53 Serial Interfaces Configurati
211. ce time depends on the interval time difference minus the average execution time of the task s in execution available time until the next task cycle it means the bigger this difference for each task in an application the faster will be the transference of a data from the memory card to a CPU MasterTool IEC XE or vice versa Transferring files to the memory card will be slower than the transfer to the internal memory of the CPU For a CPU in Stop Mode or with no application the transfer rate is close to 100 Kbytes s CPU s Informative and Configuration Menu The access to the Informative Menu the Nexto CPU configuration and the detailed diagnostics are available through levels and to access the menu information change level and modify any configuration a long touch is required on the diagnostic button and to navigate through the items on the same level a short touch on the diagnostic button is required See One Touch Diag chapter to verify the functioning and the difference between the diagnostics button touch types Table 4 76 shows the menu levels and each screen type available in the CPU if they are informative configurable or to return a level Level 1 Level 2 TEMPERATURE informative CONTRAST HARDWARE DATEANDHOUR Informative RETURN Lee Return level ENGLISH Configurable PORTUGUESE Configurable SPANISH Configurable RETURN aa ee Return level LANGUAGES END IP NET 1 Informative MASK NET 1 Informative
212. ces Table 4 17 Limits of the protocols by CPU Notes Maximum number of symbolic mappings 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 The amount of mappings increments by one when there is a simple type of variable being declared independent of the size of the given type Then mapping a variable of INT type 16 bit in a Holding Register of symbolic Modbus drivers or a variable of type LINT 64 bit in four Holding Register of symbolic Modbus drivers is accounted for as just a mapping Maximum number of mappings for direct representation Each row in the settings is considered a mapping independent of the size of the amount of data in each of these rows 63 4 Configuration NETs Clients or Servers instances The maximum value defined above is distributed between all Ethernet interfaces of the system in other words it includes the expansion modules when they are applied Examples for this type of task are the MODBUS protocol instances COM n Master or Slave instances The n represents the serial interfaces number in other words even with the expansion modules the value in the table will be the maximum limit per interface Examples for this task type are th
213. ch 157 4 Configuration message addition at the end of the interval for the task also prevents the return of buffer overload So that the logs are added correctly it is important to respect time limits when the card is inserted and at startup of the CPU mentioned in chapter Configuration Memory Card After the operation the function returns the options for the given type USER_LOG_ERROR_CODES as Table 4 106 When the function return is not USER_LOG_OK the message was not registered and the function UserLogAdd should be re executed with the desired message In case of return of consecutive writing failures the memory card can be damaged The replacement by a healthy memory card ensures that the latest logged messages will be recorded on the card that is not damaged since the CPU is not restarted The Figure 4 74 represents the function UserLogAdd and Table 4 107 the input parameters UserLogAdd Figure 4 74 UserLogAdd Function input Parameters 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 Table 4 107 UserLogAdd Input Parameters The log files are generated and organized on the memory card in a specific directory path depending on the CPU serial numbe
214. ch 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 Disabling of Mappings composed of 32 bits it is used to disable individually the 32 MODBUS relations configured in device mappings space The relation is disabled when the corresponding bit is equal to 1 otherwise the mapping is enabled 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 Default Value factory default cannot be set for the Disabling of Mappings field since the creation of a protocol instance can be made at any moment within the application development The MasterTool IEC XE software itself allocate a value from the range of direct representation output variables Q still unused Communication Time out the settings present on the button Advanced on the TCP connection are described in the notes of the section Device Configuration MODBUS Master Protocol Configuration by Symbolic Mapping Mapping Configuration Configuration via Direct Representation Q The setting of the MODBUS relations displayed in Figure 4 32 and Figure 4 33 follows the parameters described in Table 4 51 Read Settings z Read Data Stat Address Read Data Size Read Coils FC 1 1 all j1 Used range 1 1 Slave Address Read IEC Variable 1
215. cial variables Q or I The SystemAT_GVL has many sentences with the AT keyword to define symbolic names for these diagnostics and commands This way when the user needs to reference these variables he can use a symbolic name instead a numeric reference GVLs with Redundant Symbolic Variables The user can create other GVLs different from the previously listed in order to declare redundant symbolic variables For that after the GVL creation it s necessary to mark it in the object configuration Redundancy Configuration in the project devices tree By default all GVLs created by the user are initially redundant ATTENTION For good practice it s recommended to avoid the AT directive use in GVLs which have redundant symbolic variables declaration to prevent variable mapping in non redundant areas 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 By default all POUs created by the user are initially redundant 267 6 Redundancy with NX3030 CPU ATTENTION For good practice it s recommended to avoid the AT directive use in POUs which have redundant symbolic variables declar
216. ck occupation 2 sequential slots Instruction List IL Structured Text ST Ladder Diagram LD Sequential Function Chart SFC Function Block Diagram FBD Continuous Function Chart CFC Programming languages Cyclic periodic Event software event Tasks External hardware event Freewheeling continuous Status software event Online changes Yi Hot swap support Yi Bus coupler redundancy support Yi 1 x RS 232C COM 1 1 x RS 485 RS 422 COM 2 RTU COM 1 and COM 2 master and slave MODBUS Protocol TCP NET 1 and NET 2 client and server RTU via TCP NET1 and NET2 client and server SNMP Protocol Yes v1 v2c and v3 versions ETE STS I Resolution of 1 ms and maximum variance of 2 s per day Watchdog Yes Status and diagnostic indication a LEDs web pages and CPU s internal es es es Serial interfaces oO n One Touch Diag OTD Electronic Tag on Display ETD Yes Isolation g Logic to protective earth 1250 Vac 1 minute Logic to Ethernet interfaces 1500 Vac 1 minute Logic to serial port COM 2 1000 Vac 1 minute Ethernet interfaces to protective 1250 Vac 1 minute earth Ethernet interfaces to serial port 1500 Vac 1 minute COM 2 Ethernet interface to Ethernet 1500 Vac 1 minute interface Serial port COM 2 to protective 1250 Vac 1 minute earth Operating temperature 0 to 60 C Storage temperature 25 to 75 C Relative humidity 5 to 96
217. conditions are shown in Table 4 61 Total Number of Variable Total Number of POUs in Variable Number per POU Variables Update Time in in CPUs i CPUs a OPC Client to00 1000 2000 a 2000 Table 4 61 Baud Rate of Communication of a OPC Server 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 Keep the relation normally disabled Enable the relation at the moment the execution is desired Wait for the confirmation of the relation execution finishing and at this moment disable it again System Performance In cases where the application has only one MainTask user task responsible for the execution of a single Program type programming unit called MainPrg as in Simple Profile the PLC consumes a certain amount of time for the task to be processed At that time we call it as Execution Time In an application the average application Execution Time using can be known using the MasterTool IEC XE in the Device item of its Devices Tree as follows PLC Logic gt Application gt Task Configuration in the Monitor tab Average Cycle Time column The user must pay attention to the Cycle Time so that it does not exceed 80 of the interval set in the MainTask user task For example in an application where the interval is 100 ms an appropriate
218. connected to a relay NO normally open contacts which can be commanded by PLCA to switch off PLCB This relay must be closed by PLCA in order to switch off PLCB A CPU PLCA or PLCB can turn off the other CPU PLCB or PLCA in some exceptional situations using the NO relays in the RLA and RLB connectors Such situations are described in the Transition between Redundancy States section The PX2612 has also 6 buttons for redundancy command and 6 LEDs used for redundancy state indication Each CPU reads 3 from these 6 buttons and controls 3 LEDs For further information regarding these buttons and LEDs functions see PX2612 Redundancy Command Panel Functions section Figure 6 4 Redundancy Control Panel PX2612 PLCE Figure 6 5 Redundancy Control Panel PX2612 Frontal View PX2612 Features The redundancy control panel PX2612 has the following features CONTROL PLC A connection to the module NX4010 from PLCA CONTROL PLC B connection to the module NX4010 from PLCB RL A relay NA terminals used to switch off PLCA RL B relay NA terminals used to switch off PLCB GND grounding Other features generals electrical mechanic and environment are presented in the Redundancy Control Panel PX2612 Technical Features CT112500 221 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
219. connectors for communication between CPUs of the Nexto Series and Altus products of the H Series AL 1753 RS 232C standard cable with one DB9 male connector and one DB25 male connector for communication between CPUs of the Nexto Series and Altus products of the H Series 18 2 Technical Description 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 AL 1761 RS 232C standard cable with two DB9 male connectors for communication between Nexto Serie CPUs and Altus products of the AL Series AL 1762 RS 232C standard cable with two DB9 male connections for communication between Nexto Series CPUs AL 1763 Cable with one DB9 male connector and terminal block for communication between CPUs of the Nexto Series and products with RS 485 RS 422 standard terminal block 19 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 Nexto Series CPUs must be inserted in the backplane rack position 2 just beside the Power Supply Module All information regarding mechanical installation and module insertion can be found at Nexto Series User Manual
220. correspondent position In the case of those that will be used for future expansion a virtual module must be inserted in the planned correspondent position A virtual module correspondent to a real module needs to allocate the same amount of I O bytes than this real module The virtual module insertion in the place of a real module avoids the real module absence diagnostics to be produced The following Table 6 4 shows real modules and its correspondent virtual modules Real Module Correspondent Virtual Module PO1000 PO9999 2 bytes input PO1001 PO9999 2 bytes input Table 6 4 Virtual Modules correspondent to the real modules Step 3 Allocate l 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 e 4 variables area for inputs e Q variables area for outputs e Q variables area for diagnostics MasterTool executes the allocation of each one of these three variable areas in a continuous way with no holes between them 277 6 Redundancy with NX3030 CPU The initial and final address of each one of these three areas must be planned considering the initially installed remotes in the network see steps 1 and two but also remotes which might be inserted in the future in this same PROFIBUS network At defining the initia
221. cribed in the Cyclic Synchronization Services through NETA and NETB section and a smaller time for the redundancy management state machines etc The total additional time due to redundancy redundancy overhead is estimated by MasterTool after the redundant CPU project compiling ATTENTION MasterTool calculated overhead consider an empty redundant variables forcing It s up to the user to define a cycle time for the MainTask which includes e The additional redundancy time estimated by MasterTool e The necessary time to execute the main POUs NonSkippedPrg and ActivePrg This time usually is measured after the project development with the redundancy additional time off e Some MainTask cycle looseness for other CPU tasks execution operational system I O PROFIBUS drivers MODBUS etc This looseness percentage can vary according to the requested performance from these other tasks E g if the MODBUS communication with the SCADA system needs to allocate too much processing to reach a satisfying performance this looseness must be increased Note Depending on the memory alignment the number of bytes used in the redundancy overhead calculus might be higher than the total amount of bytes declared in the variables 254 6 Redundancy with NX3030 CPU Redundant CPU Programming Wizard for a New Redundant Project Creation In order to create a new redundant project the File New Project command must be used and the St
222. curs in order to keep the consistency of the memory areas data while a MainTask is not running MODBUS Master Protocol Configuration for Direct Representation Q To configure this protocol using direct representation Q the following steps must be performed e Configure the general parameters of the MODBUS Master protocol such as communication times and direct representation variables Q to receive diagnostics e The descriptions of each configuration are listed below in this chapter e Add and configure devices by setting address direct representation variables Q to disable the relations time outs and number of communication retries e Add and configure MODBUS relations specifying the data type and MODBUS function time outs direct representation variables Q to receive diagnostics of the relation and other to receive write the data amount of data to be transmitted and relation polling The descriptions of each configuration are listed below in this chapter 74 4 Configuration General Parameters of MODBUS Master Protocol setting by Direct Representation Q The General parameters found on the home screen of MODBUS protocol configuration Figure 4 15 are defined as EMU Stuff project Me File Edit View Project Build Online Debug Tools Window Help acu re Aala Devices Saal Configuration Gus J MODBUS_RTU_Master x x ES MU Stuff LZ MODBUS Master Configuration J Device Nx3030 Master Se
223. d the left NX5000 should be edited the ri NX5000 Modules Grouping with NIC Teaming Redundancy The NX5000 modules as the CPU NX3030 and NX3020 NET 1 interface present a screen of advanced configuration which defines if the module forms a redundant NIC Teaming pair with the module at its right The configuration is made as described in the NIC Teaming between NET 1 and NET 2 To group two NX5000 modules with a redundant pair the following conditions must be true e Both NX5000 modules must be inserted in close positions in the rack At doing this the right module has its parameters edition blocked and the left module parameters turn to be the same to both modules Unmarking the checkbox Redundancy of Communication at the left module causes the modules separation making them behaves as individual modules without NIC Teaming redundancy again Failure Vital Setting The NX5000 modules as well as the NET 1 and NET 2 interfaces allow you to configure if the interface will generate a switchover in case of failure as described in Ethernet Interfaces Use with Vital Fault Indication When configured in conjunction with the NIC Teaming redundancy vital failure will be considered when failure occurs in both modules of the redundant pair NX4010 Redundancy Configuration The configuration regarding the I Q and M redundant variables can be accessed through a double click on the NX4010 module following the selection of the tab
224. d The module is grounded through Nexto Series backplane rack The power supply comes from the backplane rack connection There is no need for external connections ee Ethernet Network Connection The NET 1 and NET 2 only for NX3020 and NX3030 isolated communication interface allows the connection with an Ethernet network however the NET 1 interface is the most suitable to be used for communication with MasterTool IEC XE The Ethernet network connection uses twisted pair cables 10 100Base TX and the speed detection is automatically made by the Nexto CPU This cable must have one of its endings connected to the interface that is likely to be used and another one to the HUB switch microcomputer or other Ethernet network point IP Address The NET 1 Ethernet interface is used for Ethernet communication and for CPU configuration which comes with the following default parameters configuration Suonetmas ess2ss2550 OOOO Table 3 1 Default Parameters Configuration for Ethernet NET 1 Interface The IP Address and Subnet Mask parameters can be seen on the CPU graphic display via parameters menu as described in Configuration CPU s Informative and Configuration Menu chapter First the NET 1 interface must be connected to a PC network with the same subnet mask to communicate with MasterTool IEC XE where the network parameters can be modified For further information regarding configuration and parameters modifications see
225. d either by symbolic mapping or direct representation are stored in T DIAG_MODBUS_ETH_CLIENT_1 variables For the direct representation mapping they are also in 4 bytes and 8 words which are described in Table 4 41 6699 where n is the configured value in the Q Initial Address of Diagnostic Area field 89 4 Configuration Direct Representation Variable Diagnostic Variable T_DIAG_MODBUS ETH _CLIENT_1 Descuipuon Diagnostic Bits AX N 0 B mode see bit 3 IT QX n 1 bNotRunning BIT blInterruptedByCommand QX n 2 The bit bNotRunning was enabled as the client was binterruptedByCommand BIT interrupted by the user through command bits QX n 3 Dia bConfigFailure BIT Discontinued diagnostics iag QX n 4 bRXFailure BIT 9 eo bTXFailure BIT QX n 6 Indicates if there is failure in the bModuleFailure BIT module or the module is not present QX n 7 Indicates that all devices pAlDoviees Comme allure BIT configured in the Client are in fail QB n 1 byDiag_1_reserved BYTE Reserved Command bits automatically initialized OX n42 0 OX N42 1 QX N 2 2 bResetCounter B QX n 2 3 tCommand bDiag_19_reserved The client is in execution mode The client is not in execution Discontinued diagnostics Discontinued diagnostics T Stop client Restart client Restart the diagnostic statistics counters Reserved Reserved Reserved Reserved BYTE Reserved Communication
226. d error 0x0022 Scheduled tasks erro 0x0023 Downloaded file Checksum with error current identity of the boot project program 0x0025 IEC task configuration failure 0x0155 FPU Overtow 0x0026 Application working with wrong target 0x0156 FPU Stack verification 0x0050 Illegal instruction 0x0157 FPU Underflow Table 7 8 RTS Exception Codes FPU Division by zero Notes Brownout Reset The brownout reset diagnostic is only true when the power supply exceeds the minimum limit required in its technical features remaining in low voltage without suffering any interruption The CPU identifies the voltage drop and indicates the power supply failure diagnostic When the voltage is reestablished the CPU is restarted automatically and indicates the brownout reset diagnostic Temperature For the temperature visualization straight in the memory address a conversion must be done as the data size is DINT and the monitoring is made in 4 bytes Therefore the utilization of symbolic variable association is indicated as it already offers the temperature final value User Partition The user partition is a memory area reserved for the CPU data storage E g files with PDF and DOC extension and other data Situations that may cause Application to Stop Codes of the possible situation that may cause application stop can be consulted below 316 7 Maintenance Code INITIALIZING This state is shown while
227. d for process under control answer time and optimize the CPU processing capacity The controllers that use tasks are called multitask It will only be allowed the creation of new tasks when the selected project profile is the Custom as in the other profiles the available tasks are automatically created and configured Therefore to include a new task in case the selected profile allows the Task Configuration must be clicked using the right mouse button and the Add Object and Task options must be selected as shown on Figure 5 11 193 5 Initial Programming Fle gdt Project Buld Online Debug Tools Window Help i2aeEliG4loe XB RxX M UIBTIS J Device Nx3010 PLCLogic ir il Library a RA Ma Configuration com1 com2 NETI E MainPrg PRG S E Nx3010 N e S E Neto Application Bill of Materials Configuration and Consumption Diagnostic Explorer Diagnostics Manager Copy Paste X Delete Properties Add Device Add Folder Edit Object Edit Object With Simulation lt E Start Page i Cor It Figure 5 11 Task Creation Following a screen will appear requesting the task name After click on Open to end the task creation open cancel _ Figure 5 12 Task Name 194 5 Initial Programming Task Configuration After the task is open the configuration wind
228. d produces an equivalent action to the ResetNET StatisticsLocal button on the 4 bResetNETStatisticsRemote PX2612 in the remote PLC FALSE The reset commands for the NETA NETB statistics in the remote PLC wasn t activated Table 6 10 Redundancy Commands User Information Exchanged between PLCA and PLCB The Diagnostics and Commands Exchange Synchronization service in each MainTask cycle exchange the following data structures between both PLCs using the NETA NETB synchronism channels e Redundancy Diagnostics RedDgnLoc and RedDgnRem already described in the Redundancy Diagnostics Structure section e Redundancy Commands RedCmdLoc and RedCmdRem already described in the Redundancy Commands section e 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 They allow the user to transfer each cycle 128 bytes of information from PLCA to PLCB and other 128 bytes from PLCB to PLCA RedUsrRem is a copy from the other PLC RedUsrLoc received through NETA NETB A specific PLC writes information on RedUsrLoc which are read in the RedUsrRem of the other PLC These data structures have many utilities E g supposing the SCADA system is connected only to the Active PLC and it s desired to visualize some information from the Non Active PLC The
229. d write in the relation variables Reading writing functions are filtered in other words they cannot be requested by any client independent from the IP address This information is detailed in the MODBUS Ethernet Server protocol When the MODBUS TCP protocol is used in the client mode it s possible to use the multiple requests feature with the same TCP connection to accelerate the communication with the servers When this feature isn t desired or isn t supported by the server it can be disabled relation level action It is important to emphasize that the maximum number of TCP connections between the client and server is 63 If some parameters are changed inactive communications can be closed which allows the opening of new connections Table 4 38 and Table 4 39 bring respectively the complete list of data and MODBUS functions supported by the Nexto CPUs Data type Size bits Description Digital output which can be read or written Input Status 1 Digital input which can be only read Holding Register Analog output which can be read or written Input Register Analog input which can be only read Table 4 38 MODBUS Data Types Supported by Nexto CPUs Function Type Description DEC j Coils reading FC 1 Input status reading FC 2 Holding registers reading FC 3 Input registers reading FC 4 Coil writing FC 5 Variables Access Holding register writing FC 6 Multiple coils writing FC 15 Multiples holdi
230. default settings The Everyone group cannot be deleted only renamed and its members can not be removed The project also features an Owner group that contains the user Owner Users can be added or removed from this group but at least one user must remain This group cannot be deleted and always has all access rights Both the Owner group as the Owner user can be renamed When starting the programmer and a project there is no user logged on However user login can be accomplished through a set account with name and password so he can get specific access rights Note that each project has its own user management for example to have specific access rights in a library the user must log on in this library separately Users and groups defined in different projects are not identical even if they have the same name ATTENTION User passwords are stored irreversibly If a password is lost the corresponding user account can no longer be used If the Owner password is lost the entire project may be unusable By default in new projects the password Owner user is empty 167 4 Configuration Users Compiler warnings amp Page Setup f Source Download 8 Users and Groups Visualization Profile Users and Groups Users Groups Settings Name 5 8 Owner 8 is member of group Everyone 98 is member of group Owner Full name Description Remove Cx La
231. development The MasterTool IEC XE software itself allocate a value from the range of output variables of direct representation Q not used yet The diagnostics and MODBUS protocol commands are described in Table 4 21 The communication times of the MODBUS Master protocol found on the button Advanced in the configuration screen are divided into Transmission Delay and Minimum Interframe further details are described in section Mappings Configuration Symbolic Mapping Settings 75 4 Configuration Devices Configuration Configuration for Direct Representation Q The configuration of the slave devices viewed in Figure 4 16 comprises the following parameters f Device Settings Name Slave Address 1 Communication Time out ms 1000 Maximum Number of Retries 2 Mapping Disabling 8192 Used range QX8192 0 QX8195 7 Figure 4 16 Device Configuration Configuration Default Value Option Identifier according to Name of the instance MODBUS_Device IEC 61131 3 The MODBUS slave Communication Sets the time out of the Time out ms application level 1090 10 t0 65539 A Sets the number of retries ena Number before reporting a 2 0to9 communication error Disabling area of Initial address used to reas disable MODBUS 0 to 2147483644 pping relations Table 4 29 Configuration Notes Instance Name this field is the identifier of the device which is checked according to IEC 61131 3 i e does no
232. dified a message will be displayed by MasterTool IEC XE programmer to choose the behavior for this area after charging the modified program The choice of this behavior does not affect the persistent area of direct representation which is always clean Nexto Series CPUs have the possibility of I O modules change in the bus with no need for system turn off and without information loss This feature is known as hot swap 40 4 Configuration CAUTION Nexto Series CPUs do not guarantee the persistent and retentive variables retentivity in case the power supply or even the CPU is removed from the energized backplane rack On the hot swap the related system behavior modifies itself following the configuration table defined by the user which represents the options below as described on Table 4 1 Disable for declared modules only Disabled Enabled with consistency in the start only for declared modules Enabled with startup consistency Enabled without consistency in the start Therefore the user can choose the behavior the system must assume in abnormal bus situations and when the CPU is in Run Mode Table 4 2 presents the possible abnormal bus situations Situation Possible causes Incompatible Some module connected to the bus is different from the model that is declared in configuration configuration The module was removed from the bus Absent module Some mal functioning module is not responding to CPU
233. discharges must be periodically inspected as they might be damaged or destroyed in case the absorbed energy is above limit In many cases the failure may not be visual In critical applications is recommendable the periodic replacement of the TVS diodes even if they do not show visual signals of failure Bus tightness and cleanness every six months For further information see Nexto Series Manual MU214600 323 8 Glossary 8 Glossary Active CPU ActivePrg Active IP Active PLC Adjust Bridge Addressable Variables Applicative Project Applicative Program AT Variable Bus Bit Backoff Baud rate Bridge Broadcast Byte Category 5 Cluster Commercial code Communication Network Configuration Module CPU CSMA CD Cycle Time Database Default Deterministic Communication Network Diagnostic Direct Representation Variable DG Download ESD EIA RS 485 EN 50170 Frame Freeze Full Duplex Gateway Hardkey 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 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 Strategy to facilitate the connection of Ethernet clients to Ethernet servers executed on a redundant PLC Half cluster PLCA or PLCB which is momentarily in Active state
234. ds and User Data Structure Each CPU has several data structure related to redundancy The following structure is AT variables mapped over Q variables e RedDgnLoc has diagnostics from the CPU local related to the redundancy as the CPU redundancy state for instance e RedDgnRem it s a copy from the other CPU RedDgnLoc received through NETA NETB synchronism channels This way this CPU local has access to the other CPU remote diagnostics e RedCmdLoc has commands which must be applied on this CPU when called Local or on the other CPU when called Remote E g the StandbyLocal field from this data structure corresponds to a command which must be executed in this CPU local while the StandbyRemote field corresponds to a command which must be executed in the other CPU remote e RedCmdRem it s a copy from the other CPU RedCmdLoc received through NETA NETB synchronism channels This way this CPU local can execute commands received from the other CPU remote e RedUsrLoc has 128bytes of data filled freely by the user e g communication diagnostics with a SCADA system These 128bytes of data can be interchanged with the other CPU remote e RedUsrRem it s a copy from the other CPU RedUsrLoc received through NETA NETB 232 6 Redundancy with NX3030 CPU On Maintenance section the following sub sections offer more details regarding these data structures e Redundancy Diagnostics Structure e Redundancy Comm
235. dules including undeclared and present on the bus The CPU enters in stop mode and the DG LED begins to blink 4x as 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 If a Reset Origin is done you need to download the project so that the CPU can return to normal Run The Reset commands Warm Cold and Reset Origin can be done by MasterTool IEC XE in the Communication menu Hot Swap Enabled with Consistency in the Start Only for Declared Modules Start is the interval between the CPU energization or reset command or application download until the first time the CPU gets in Run Mode after been switched on This configuration verifies if any abnormal bus situation has occurred as described on Table 4 2 during the start In affirmative case the CPU gets in Stop Mode and the LED DG starts to blink 4x according to Table 4 3 41 4 Configuration Afterwards in order to set the CPU in Run mode further to fix what caused the abnormal situation it is necessary to execute a Warm or Cold Reset command which can be done by the MasterTool IEC XE Communication menu If a Reset Origin is carried out it will be necessary to perform the download so that the CPU can return to the normal state Run After the start if any module present any situation described in the Table 4 2 the system will continue to work norma
236. dules Configuration NX5000 Modules Insertion or Removal NX5000 modules can be inserted or removed from the half cluster rack To execute this operation correctly one must be aware that the number of NX5000 modules in each half cluster can vary between zero and six Care must be taken to the fact that modules which form a redundant NIC Teaming pair must be inserted in side by side positions in the rack In the next project compilation MasterTool check the possible errors the user may have committed at inserting or removing NX5000 modules manually For instance if the user inserted more than 6 NX5000 modules an error occurs The interface of each module will be identified as NET 1 as they are identified physically on the product In case the user adds manually NX5000 modules in the bus the identification occurs the same way as the Wizard After inserting or removing the NX5000 modules the configuration of the NX5000 modules remaining in the rack must be checked 263 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 ATTENTION In case two consecutive modules form a redundant NIC Teaming pair only the basic parameters of ht NX5000 s parameters edition will be blocke
237. dundant component failure doesn t drop the system but during its repair a failure in its redundant pair could happen For this reason it s important that the failure is repaired quickly after diagnosed The higher the repair time the higher the probability of a second failure to occur in the redundant component during this time what would drop the system Therefore the higher the repair time the lower the system availability e Program periodic of line tests in components in order to detect not automatically diagnosable failures by the system The objective is to detect hidden failures especially in redundant components or simple components which aren t being requested e g a security relay Off line tests sometimes imply in system stopping what decreases the availability Normally special 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 The next sub sections analyze several failure types and how they are tolerated or not and if there are switchovers associated to the tolerated failures 252 6 Redundancy with NX3030 CPU Simple Failure with Unavailability Some components as they aren t doubled don t
238. dundant data synchronization and the redundant forcing list synchronization services are working correctly 248 6 Redundancy with NX3030 CPU Transition 6 Inactive to Not Configured e This PLC was switched off or restarted warm reset cold reset or origin reset or its CPU went to Stop mode e The STAND BY button was pressed on the PX2612 Besides going to the Not Configured state a configuration request is made This way the CPU goes out automatically from the Not Configured state for the Starting state The user typically presses this button after repairing the failure which has driven the CPU to the Inactive state e This PLC has its synchronization disabled and the project is different from the Active PLC at the STAND BY button pressing the PLC goes from Inactive to Not Configured Transition 7 Active to Not Configured e This PLC was switched off or restarted warm reset cold reset or origin reset or its CPU went to Stop mode Transition 8 Active to Inactive e NX4010 module not detected in the bus or its microprocessor failure This CPU knows the other CPU was in Stand by state before this failure happened This condition isn t analyzed in the first 2 seconds in Active state e This PLC has lost communication with another PLC through NETA and NETB due to an internal failure but knows the other PLC was in Stand by mode just before the failure occurred This condition isn t analyzed in the first 2 seconds
239. during reception UART FIFO or RX line 0 to 65535 Counter of frames with construction QW n 14 wRXIncompleteFrames errors parity or failure during reception 0 to 65535 Counter of CTS time out error using QW n 16 wCTSTimeOutErrors the RTS CTS handshake during the transmission 0 to 65535 QW n 18 wDiag_18_reserved WORD Table 4 33 MODBUS RTU Slave Diagnostic Note Counters all MODBUS RTU Master diagnostics counters return to zero when the limit value 65535 is exceeded Configuration of the Relations Symbolic Mapping Setting The MODBUS mapping configuration depicted on Figure 4 21 follow the parameters described on Table 4 34 Mappings Data Start Absolute Data Address Start Address Value Variable Data Type Data Size Data Range Figure 4 21 MODBUS Data Mappings Screen 82 4 Configuration Configuration Variable Value Symbolic variable name Name of a variable de G clared in a program or VL Coil 1 bit Input Status 1 bit Data T MODB atailype DBS data type Holding Register 16 bit Input Register 16 bit 1 to 65536 annie MODBUS data initial address Address MODBUS data size 1 to 65536 The data address range Table 4 34 MODBUS Mappings Configurations Notes Variable Value this field is used to specify a symbolic variable in MODBUS relation Data Type this field is used to specify the data type used in the MODBUS relation Datatype Size fits Desc
240. e Enabled gt Ethernet Interface NET x Keep Alive Interval ms 10000 Events Queue Size 1000 Communication Points Offset of Q Start Address 20480 Size of Area Q 1000 Used range QB20480 QB22479 Client Configuration Number of Clients 2 e TCP Port for Client 1 20000 TCP Port for Client 2 20001 Advanced Figure 4 7 Events Sequence Configuration Configuration Default Value Options General Configurations Enabl Enables the SOE Disabled nable Disabled Ethernet Selects the used NET NET1 Interface interface NET2 Keep Alive Keep alive ms interval 10000 0 to 4294967295 Interval ms messages Communication Points Offset of Q Initial address for static 20480 Any Q area address can Start Address data be used s Memory size to be used 9 Size of Area Q y the static data Q 1000 1 to 1000 Client Configuration Configuration Default Value Number of Defines the number of Clients clients Selects the Leia ak hs communication port for 20000 1 to 65535 the first client Selects the Loe setter communication port for 20001 1 to 65535 Client 2 the second client 2 Table 4 5 SOE Configuration 51 4 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 Keep Aliv
241. e NX3010 General Parameters S PLC Logic Diagnostics Area Application Q Start Address B Bill of materials 21492 Configuration and Consumption size 4 Diagnostic Explorer oe Diagnostics fD Library Manager E MainPrg PRG alas Task Configuration Q Start Address amp MainTask 14096 J Configuration Bus Size 8192 comi com2 NETI Used range QB21492 QB21997 Used range Q84096 QB12287 Persistent Area Q Start Address 12288 Size 8192 Used range QB12288 QB20479 elele x CPU Parameters Start User Application after a Watchdog Reset Disabled X Hot Swap Mode Enabled without startup consistency X TCP IP Parameters Initial Time out x100 ms ACK Delay x10 ms 10 Project Parameters Generate error on tasks watchdog consistency J Consist retain and persistent area in Q Memory Card Current user nobody Figure 5 15 CPU Configuration Besides that for the communication between the CPU and the MasterTool IEC XE to be possible the Ethernet NET linterface must be configured as described in the NET 1 Double clicking on the CPU NET 1 icon in the devices tree a new tab will appear for the configuration of the communication network where the module is connected A Nexto project MasterTool IEC XE Eile Edit View Project Build Online Debug Tools Window Help BLA 4 1B 71S Devices i a x Bl Start Page a Configuration Bus N
242. e Q output will be driven to FALSE at the end of it When the input IN is in logic level 1 TRUE the output Q remain in the same state TRUE even if this happened in the middle of the counting process The PT time can be changed during the counting as the block assumes the new value if the counting hasn t finished Figure 4 65 depicts the TOF_RET block and Figure 4 66 shows its graphic behavior Figure 4 65 TOF_RET Block input parameters BOOL This variable when receives a falling edge enables the block counting TIME This variable specifies the block counting limit time delay Table 4 100 TOF_RET Input Parameters This variable executes a falling edge as the PT variable BOOL time delay reaches its maximum value TIME This variable shows the current time delay Table 4 101 TOF_RET Output Parameters 151 4 Configuration 0 a vegum amp ai 1 L t0 tl4PT t2 16 PT Figure 4 66 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 END IF TON_RET The TON_RET implements a time delay to enable an output When the input IN has its state changed from FALSE to TRUE o
243. e While it is connected to a client keep alive messages will be sent in intervals according to what has been set If the client does not respond to these messages the connection is closed That is a connection between client and server may take a time equal to the interval set to be closed in case of error In the advanced options Advanced key it is possible to set the communication addresses regarding to the DNP3 protocol Configuration Description Default Value Options DNP3 Source ny DNP3 Destination Address of Client A ress of the first 3 0 to 65519 1 client DNP3 Destination Address of Client AS9ress of the first 3 0 to 65519 2 client Table 4 6 SOE Advanced Configurations Note DNP3 Address The DNP3 addresses from the range 65520 to 65535 cannot be set at the origin or at a destiny as they are used for messages in broadcast ATTENTION The DNP3 DataLink messages are not used by the Nexto series CPUs as the standard does not recommend its use them in TCP IP communications 52 4 Configuration Time Synchronization For the time synchronization NX3020 and NX3030 CPU use the SNTP Simple Network Time Protocol protocol For that the CPU will behave as a SNTP client which is it will send requests of time synchronization to a SNTP NTP server which can be in the local net or in the internet The SNTP client works with a 1 ms resolution 100 ms precision which means that when synchronizat
244. e Active state in order to avoid the possibility of both CPUs to assume the Active state simultaneously ATTENTION For a button to be considered it must be pressed for at least 1 second Furthermore during this second only this button must be pressed the other 2 buttons must be released ATTENTION There are alternative ways to generate the same effects of the STAND BY INACTIVE and TURN ON PLCx buttons Commands generated by the local CPU or the remote CPU can be used as described preliminary in the Diagnostics Commands and User Data Structure section A more detailed description of these commands can be found in the Redundancy Commands section PX2612 LEDs The PX2612 LEDs are used to inform the redundancy state as shown on the following Table 6 2 Redundancy state LED ACTIVE LED STAND BY LEDINACTIVE Not Configured oft Active switching off the other CPU sae ae Active recent and switching off the blinking blinking off other CPU Stand by mawe TCT Sot o Table 6 2 PX2612 LEDs 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 e At the first 2 seconds in Active state the LED ACTIVE led blinks and remains on afterwards This animation was created because in the first instants of the Active state the CPU won t accept commands to get
245. e MODBUS protocol instances Using symbolic mappings and by direct representation in conjunction in cases where the two types of protocols are used in conjunction when a type is used the maximum capacity of the other decreases For example if it is used 10240 symbolic mappings only 256 mappings by direct representation can be used The ratio of the two types of mappings is 40 symbolic mappings for each mapping by direct representation Number of instances The maximum number of instances competes between themselves that is between the MODBUS RTU Master and Slave there is only one instance that can be configured per interface on any CPU model Between Ethernet MODBUS Client and server only four NX3010 eight NX3020 or sixteen NX3030 instances can be configured per interface The MODBUS protocol limitations for the CPUs can be seen on the following Table 4 18 Limitations MODBUS RTU MODBUS RTU MODBUS Ethernet MODBUS Ethernet Master Slave Client Server Maximum number of mappings for 128 32 128 32 instance Maximum number Maximum number of mappings for 32 32 32 32 device Maximum number of simultaneous requests for instance 64 Maximum number of simultaneous requests for device Table 4 18 MODBUS Protocol Limitations for Direct Representation Notes Number of Mappings for Device Despite of being related in the table above the maximum number of mappings for device is also limited by the maximum number of protocol map
246. e PO letters followed by four numbers Group of devices nodes interconnected by communication channels Also called a module C It is a single module in a PLC program that contains various parameters required to the controller functioning such as the amount of variables and layout of the I O modules in the bus Abbreviation for central processing unit Controls the information flow interprets and executes program instructions and monitors the devices in the system Physical layer access protocol based in data collision used for Ethernet networks It is the time that the CPU takes to run a particular application task Data base Pre defined value for a variable used in case there s no definition Communication network where the transmission and reception of information between different nodes is guaranteed with a maximum known time Procedure used to detect and isolate failures It s also the data group used for such determination which serves for problem analysis and correction The variable can be accessed directly in memory using a web address For example QB0 MW 100 Used abbreviation to indicate dianostics in the LEDs Program or configuration load in the PLC Electrostatic discharge Industrial pattern physical layer for data communication In PROFIBUS networks it s the standard which defines the fieldbus An information unit transmitted through the network In PROFIBUS networks it s the network state whe
247. e device terminals as shown on Table 3 6 AL 1763 terminals Device terminal signals Table 3 6 COM 2 with RS 485 Connections with no Termination 24 3 Installation The Figure 3 5 diagram indicates how the AL 1763 connection terminals should be connected in the device terminals DEVICE NX3010 RS 485 NX3020 NX3030 AL 1763 11032101A Figure 3 5 COM 2 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 COM 2 In order to connect in a RS 485 network using the internal termination in COM 2 interface the cable AL 1763 identified terminals must be connected in the respective device terminals as shown on Table 3 7 AL 1763 terminals CPU terminal signals Shield Not connected ee b O Table 3 7 COM 2 with RS 485 Connections with Internal Termination PS The internal termination available in COM 2 is safe state type in open mode The Figure 3 6 diagram indicates how the AL 1763 connection terminals should be connected in the device terminals 25 3 Installation DEVICE NX3010 RS 485 NX3020 NX3030 AL 1763 11032103A Figure 3 6 COM 2 RS 485 Connections with Internal Termination Diagram Diagram Note The not connected terminals must be insulated so they do not make contact with each other RS 485 Communication with External Termination
248. e diagnostic is active 301 7 Maintenance 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 Diagnostics via LED Nexto Series CPUs have a LED for diagnostic indication LED DG and a LED for watchdog event indication LED WD Table 7 2 and Table 7 3 show the meaning of each state and its respective descriptions DG Diagnostic Green Red No power supply N pee o a Hardware problem un gt applications in stopping mode 3 Low amp Bus modules with diagnostic ALeas a bus module including the ot aus Modules with Bus modules with diagnosti CPU is with an active diagnostic a Some memory area is being forced Data forcing ao the user through MasterTool IEC om Blinking 4x Configuration or hardware error in The bus is damaged or is not 0 High the bus properly configured Table 7 2 Description of the Diagnostic LEDs States WD Watchdog Red LED EEE SS No watchdog indication Normal operation sBlinkingix Software watchdog User application watchdog Hardware wat hdo Damaged module and or _ __ High g operational system gh Table 7 3 Description of the Watchdog LED States Notes Software Watchdog In order to remove the watchdog indication make an application reset or turn off and turn on the CPU again This watchdog occurs when the user application execution time is higher
249. e in the Lib Logs library on MasterTool IEC XE 1 40 To perform the procedure of inserting a library consult Chapter Libraries ATTENTION The User Logs are available only until version 1 3 0 20 of Nexto Series CPUs In the same way to use this feature is necessary version 1 40 or higher of MasterTool IEC XE UserLogAdd This function is used to add a new user log message adding in a new line to the log file on the memory card The message must have a maximum length of 150 characters and the event type of the message Application variables can be registered using conversion to string and concatenation with the main message The date and time information in UTC timestamp is automatically added in the 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 However independent of each execution of the function in the application being on the same task or on different tasks all use the same feature to record the desired messages For this reason it is recommended that the addition of messages using the UserLogAdd function in the application be held every 50 ms to prevent the return of buffer overload If the function is performed in periods shorter than the indicated but respect the average time of 50 ms between ea
250. e is equal to 5 ms In machine profile the maximum time to MainTask is 100ms and minimum is 5ms It is recommended to set a task interval in a way that the cycle execution time be at most 80 of the interval The watchdog of the CPU is configured to prevent the locking of the user tasks The field Time sets the maximum time allowed for the task execution If the task takes longer than the watchdog configured time the application will go to Stop and enter into exception by the watchdog The field Sensitivity refers to how many times the watchdog will be achieved to activate the diagnostics If the task Cycle Time reaches the Sensitivity field value multiplied by the Time field the diagnostics will also be indicated It has to be paid attention to the fact that the watchdog of the CPU is not used to protect the user application from surge at Cycle Time but of crashes Therefore its time must be configured with a high value compared to the Cycle Time of the task that is referenced The ideal is to keep the average time to perform the tasks at the maximum of 50 of the watchdog time Thus the chances of occurring watchdog errors by any peak time in the execution of the task are reduced Aiming to protect the system regarding to possible configuration error the MasterTool IEC XE checks in all cyclic tasks during the compilation the watchdog Software Watchdog and the minimum and maximum limits of the task cycle time Interval It is importa
251. e mere symbolic names attributed to direct representation variables ol Q and M using the AT declaration Thus AT variables don t allocate any symbolic variables memory Symbolic variables are redundant in the following cases e When declared in POUs from the program type created in the user application exceptionally the NonSkippedPrg program e When declared in GVLs created in the user application and these GVLs marked as redundant e Symbolic variables aren t redundant in the following cases 230 6 Redundancy with NX3030 CPU the NonSkippedPrg section When declared in the NonSkippedPrg program This program has been described previously in 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 type this will be considered bad programming Such static variables in case they are created will be considered non redundant When declared in POUs from the function block type It can be observed the mere function block declaration doesn t allocate memory what allocates memory is to turn a function block into as instance It must be observed that the function blocks instances declared inside POUs from the program type or inside GVLs behave as symbolic vari
252. e or passive in the PROFIBUS 1 A network The master mode communicating with slaves is assumed by the Active PLC The passive mode communicating with the active master is assumed by the Non bFailedPBUS1A Active PLC This failure can also be indicated in case the NX5001 module has a microprocessor failure or in case it can t communicate with the NX3030 CPU via bus FALSE There aren t failures in the PROFIBUS 1 A network TRUE This PLC can t communicate in the master state active or passive in the PROFIBUS 1 B network The master mode communicating with slaves is assumed by the Active PLC The passive mode communicating with the active master is assumed by the Non bFailedPBUS1B Active PLC This failure can also be indicated in case the NX5001 module has a microprocessor failure or in case it can t communicate with the NX3030 CPU via FALSE There aren t failures in the PROFIBUS 1 B network TRUE This PLC can t communicate in the master state active or passive in the PROFIBUS 1 network In case the PROFIBUS 1 network is redundant FailurePROFIBUS_1 results from a AND logic between bFailureProfibus 1 FailedPBUS1A and FailedPBUS1B In case the z PROFIBUS 1 network isn t redundant FailurePROFIBUS_1 is a copy from FailedPBUS1A FALSE There aren t failures in the PROFIBUS network TRUE this PLC can t communicate in the master state active or passive in the PROFIBUS 2 A netwo
253. e previously reserved for it in an existent remote Step 7 Download the Off Line Modifications in the Non Active PLC At first MasterTool must be connected to the Non Active PLC see MasterTool Connection with a NX3030 CPU from a Redundant PLC section Next the off line modifications must be downloaded At doing it the Non Active PLC application is automatically interrupted goes out of the Run mode Step 8 Set the Non Active PLC Back to Run Mode to make go back to Stand by State The off line load being finished the Non Active PLC can go back to Run mode A few seconds later the Non Active PLC must assume the Stand by state In case the PLC doesn t assume the Stand by state the following problems may have caused this effect e The modifications executed changed the redundant variables structure which prevents the correct execution of the Redundant Data Synchronization service This can be verified through DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bRedDataSync 0 failure diagnostics in the Non Active PLC In this case the modifications must be undone recovering the previous project backup and restarting this procedure e Other problems may eventually prevent the transition to the Stand by state even though this is unexpected In this case the diagnostics and the redundancy log must be observed In case the PLC has assumed the Stand by state it s recommendable to verify if the projects are different between the
254. e process control The second warning informs that if the other PLC is in Stand by state it must be switched to Inactive state e g pressing the PX2612 INACTIVE button on this PLC This way the turn off of this PLC by the other PLC and its take over as Active is avoided When the user confirms these warnings reception the off line download starts At this moment the Active PLC goes out from the execution mode Run and therefore goes to Not Configured state 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 In this case thus the off line download can t be completed because the PLC connected to MasterTool is off 275 6 Redundancy with NX3030 CPU When the off line download finishes it s possible to restart the PLC program execution where the application was downloaded put in Run again After a few seconds this PLC takes over again the Active state After this PLC takes the Active state again the other PLC can go out from the Inactive state e g pressing the PX2612 STAND BY button on it This causes the transition of this PLC to the Not Configured state This PLC remains in the Not Configured state until the automatic project synchronization finishes Then it goes to Starting state and back to Stand by state afterwards Previous Pla
255. e silence time is higher than 65535 units The RX_TIMESTAMP of a character measures the time from a reference which can be any of the three options below e On most of the cases the end of the later character e Serial port configuration e The end of serial communication using the SERIAL_TX FB in other words when the last character is sent on line Besides measuring the silence between characters the RX_TIMESTAMP is also important as it measures the silence time of the last character on the RX line The silence measuring is important for the correct protocol implementation as MODBUS RTU for example This protocol specifies an inter frame greater than 3 5 characters and an inter byte less than 1 5 characters The serial interfaces Data Bits configuration limits the Stop Bits and Communication Parity fields Therefore the stop bits number and the parity method will vary according to the data bits number Table 4 9 shows the allowed configurations for COM 1 interfaces Data Bits Stop Bits NO PARITY ODD EVEN PARITY ALWAYS ONE PARITY ALWAYS ZERO NO PARITY ODD EVEN PARITY ALWAYS ONE PARITY ALWAYS ZERO 7 NO PARITY ODD EVEN PARITY ALWAYS ONE PARITY ALWAYS ZERO NO PARITY ODD EVEN PARITY ALWAYS ONE PARITY ALWAYS ZERO Table 4 9 Specific Configurations 56 4 Configuration Advanced Configurations The advanced configurations are related to the serial communication control in other words when it is necessary
256. e state controlling the system or in the stand by state overseeing the Active CPU It can t assume control of the system Half cluster PLCA or PLCB which is momentarily in any state other than Active Stand by Inactive Not configure or Starting Variables that are not shared between PLCA and PLCB in a redundant application These variables correspond to diagnostic or private command to each half cluster PLCA or PLCB POU from the program type created automatically which should be completed by the user It is executed in two PLCs PLCA and PLCB and used for actions and private variables management of each PLC PLCA and PLCB such as switchovers diagnostics and management due to not vital failures Eight bits group numbered from 0 to 7 Elements on which the instructions work They may represent constants variables or set of variables Type of communication where two nodes on a network exchange data and or warnings without relying on a master Acronym for programmable logic controller Denomination of one of the two controllers composing a redundant PLC The other is called PLCB Denomination of one of the two controllers composing a redundant PLC The other is called PLCA Program Organization Unit or Unit Program Organization is a subdivision of the application program that can be written in any of the available languages A group of rules and conventions used for a program creation Also called PLC Equipment which ex
257. e the CPU The available options are the following e Login with online change execute the login and send the new project without stopping the current CPU application see Run Mode item updating the changes when a new cycle is executed e Login with download execute the login and send the new project with the CPU stopped see Stop Mode When the application is initiated the update will have been done already 207 5 Initial Programming e Login without any change executes the login without sending the new project ATTENTION Before version 2 01 of MasterTool IEC XE when the Login with online change was executed the application was not saved in the program memory It was necessary to run the Create Boot Application in the Communication menu without logging out for the application to be recorded in program memory From version 2 01 this operation came to be carried out automatically without the need to run the command MasterTool IEC XE Ea The code has been changed since the last download What do you want to do Login with online change Login with download Login without any change ok _ _ Caneel Details Figure 5 29 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 30 shows a message the MasterTool IEC XE shows w
258. e the diagnostics generated by the system which are One Touch Diag Diagnostics via LED Diagnostics via WEB Diagnostics via Variables Diagnostics via Function Blocks The first one is an innovating feature of Nexto series which allows a fast access to the application abnormal conditions The second is purely visual generated through two LEDs placed on the panel DG and WD and also through the LEDs placed in the RJ45 connector exclusive for Ethernet connection The next feature is the graphic visualization in a WEB page of the rack and the respective configured modules with the individual access allowed of the operation state and the active diagnostics The diagnostics are also stored directly in the CPU variables either direct representation Q or attributed AT variable and can be used by the user application for instance being presented in a supervisory system The last ones present specific conditions of the system functioning These diagnostics function is to point possible system installation or configuration problems and communication network problems or deficiency One Touch Diag The One Touch Diagnostics or single touch is an exclusive feature the Nexto Series brings for the programmable controllers With this new concept the user can verify the diagnostics of any module connected to the system straight on the CPU graphic display with a single touch on the module Diagnostic Switch This is a powerful diagnostic tool w
259. e there are variations on them such variations are inserted as events in the Redundancy Event Log Consulting the history sequence of such events a switchover cause may be discovered for instance e They can be referenced in the user application ActivePrg or NonSkippedPrg E g the PLC state can be tested and in case it s not active a MODBUS RTU serial master I O driver can be disabled in NonSkippedPrg ATTENTION The _NX4010 tRedundancy RedDgnLoc sGeneral_Diag bExchangeSync defined next must be tested to verify if the data structure RedDgnRem was successfully read from the remote PLC in the last MainTask cycle In case this diagnostic value is 0 false this means the data structure RedDgnRem wasn t successfully read from the remote PLC thus the RedDgnRem values may be invalid or obsolete As RedDgnRem is a copy from the other PLC RedDgnLoc it can be concluded the two structures have the same format These are divided in other four substructures sGeneral_Diag Redundancy general diagnostics sNETA_Diag NETA synchronism channel diagnostics sNETB_Diag NETB synchronism channel diagnostics sNET_Stat Common statistics for the synchronism channels NETA and NETB for failure and success counting in the synchronization services The sGeneral_Diag substructure has the following fields for redundancy general diagnostics Direct Representation AT variable Variable DG_NX4010 tRedundancy R Description variable
260. e user during execution are not deleted The Figure 4 75 represents the function UserLogDeleteAll UserLogDeleteAll UserLogDeleteAll Figure 4 75 UserLogDeleteAll Function Utilization example in ST language PROGRAM MainPrg VAR eLogError USER LOG ERROR CODES END_ VAR IF m_DeleteLogs TRUE THEN eLogError UserLogDeleteAll m DeleteLogs FALSE eLogError variable gets possibles function errors END IF ATTENTION The UserLogDeleteAll function s return does not indicate operation completed just confirmation of execution that can take a large amount of time if there are hundreds of log files in the directory The function to record the new user log is unavailable right now returning the USER_LOG_PROCESSING option for any operation The result of the operation can also be checked in the system log 159 4 Configuration 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 This protocol uses the concept of agent and manager in which the manager sends read requests or write certain objects to the agent Through a MIB Management Information Base the manager is aware of existing objects in the agent and thus can make requests of these objects respecting the read permissions or writing the same
261. e variables The variables started with a specific value will assume exactly this value the other variables will assume the start standard value Reset Cold This command puts the CPU in Stop mode and starts all the application tasks variables except the persistent type variables The variables started with a specific value will assume exactly this value the other variables will assume the start standard value zero Reset Origin This command removes all the application tasks variables including the persistent type variables and deletes the CPU application Notes Reset When a Reset is executed the breakpoints defined in the application are disabled Command In order to execute a command from any type of Reset is necessary to be in Online mode on CPU 215 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 In case of a failure in the active controller damaging its process control the stand by controller switches automatically to Active within a very short time in order not to disturb the process and cause any discontinuities in its outputs The h
262. ePresenceStatu s modules in buses individually The Array 0 31 represents 32 backplane racks being each position made up by 32 bits Each bit of this DWORD represents a position in the bus being the Bit 0 equivalent to position 0 So if the module is present the bit will be true PS This diagnostic is valid for all modules except for non redundant power supplies non declared modules and CPUs that is do not present a presence in the bus in its respective positions bit remains in false Counter of failures in the WHSB bus This counter is restarted in the energization 0 to 255 WHSB byW HSBBusError s Informs the operation state of the CPU 01 All user applications are in Start Mode 03 All user application is in Stop Mode Application bForcedIOs Viat is one or more forced I O SNTP bServiceEnabled Indicates which server is active Counter of times in which the primary server is unavailable 0 to 65535 Application byCPUState SNTP byActiveTimeServe r SNTP wPrimaryServerDownCou nt SNTP wSecondaryServerDownC ount Counter of times in which the secondary server is unavailable 0 to 65535 SNTP Counter of times the RTC was dwRTCTimeUpdatedCoun updated by the SNTP service 0 to t 4294967295 Indicates status of the last update byLastUpdateSuccessfull Indicates which server was used in the last update SNTP 00 None update byLastUpdateTimeServer 01 Primary Server
263. eatures Note Application Layer The DNP3 and SNTP protocols are not available for NX3010 NET 2 NX3020 NX3030 Connector Shielded female RJ45 Auto crossover Maximum cable length TCP Transmission Control Protocol and UDP User Datagram Transport layer Protocol Client Server MODBUS TCP Client Server MODBUS RTU via TCP HTTP Web server Application layer MasterTool IEC XE programming protocol DNP3 event oriented data reporting SNTP clock synchronism SNMP Ethernet Network Management LEDs green speed yellow link activity Table 2 10 Ethernet NET 2 Interface Features 14 2 Technical Description Memory Card Interface The memory card can be used for different data to be stored such as user logs web pages project documentation and source files More information about how to use the memory card interface can be found Memory Card section NX3010 NX3020 NX3030 Table 2 11 Memory Card Interface Features Notes Maximum Capacity The memory card capacity must be less than or equal to this limit for correct operation on Nexto CPU otherwise the Nexto CPU may not detect the memory card or even present problems during data transfer Minimum Capacity The memory card capacity must be greater than or equal to this limit for correct operation on Nexto CPU otherwise the Nexto CPU may not detect the memory card or even present problems during data transfer File Syste
264. ececeesneeeeeessececeesnaeeecessaeeesessaeeseesaeees 232 Cyclic Synchronization Services through NETA and NETB ieee eeesseeeeeeeneeeeeesseeeceesaeeeeenaeees 233 Sporadic Synchronization Services through NETA and NETB 1 0000 eeeeseeceeeeseeeeeesseeeecesseeeseenaeees 234 Project Synchronization Disabling ce eeesececessseceeeessececcesseeeceessaeecessaeeesessaeeecesseeesessaeeseesaeees 235 Summary PROFIBUS Network Contisuration si ictisiaieiei inte E EEEE OE EEEE heii EEA 236 Redundant Ethernet Networks with NIC Teaming ou ceeeesceceesseeeeeessececeesseeeeessaeeesesseeeseesaeees 237 IP Change Methods isseire ekeren aee eer ee eee a eee eee ee eE Ee aeee Eee 238 NIC Teaming and Active IP Combined Use ceceecccccccceeeseeeenneeeeeceeeeeeeenaaeeeeeeceeeeeenuaaeeeeeeeeeeeeenaaaes 241 Ethernet Interfaces Use with Vital Fault Indication eeeesseeesesseesssreesssreesssrresssrrerssrreesssreerssrressees 241 OPC Communication Use with Redundant Projects ccecccsccccceceseeeeenneeeeceeeeeeeesaeeeeceeeeeeeeeanaeeeeeees 242 Redundant CPUS tates sa inerwae wawdurevesniisetiere iin eatin tut iui ee eine ten 243 PX2612 Redundancy Command Panel Functions eeeeeeeeesseeceeesseeeceessececessnaeeeeesseeesessaeeseesaeees 245 Transition between Redundancy States cccccecesssnceccceeeeeeeennnaeeceeceeeeeesaneeeeeeceeeeeeeaaeeeeeeeeeeeeenaaees 247 First Instants Active State sore oe ee ee fe i 250 Commo
265. echnical Characteristics English CT114903 Caracter sticas T cnicas do M dulo Ethernet NX5000 Portuguese CS114903 Especificaciones y Configuraciones Modulo Ethernet Spanish NX5000 CT112500 Caracter sticas T cnicas do Painel de Controle de Portuguese Redund ncia PX2612 MU214600 Nexto Series User Manual English MU214000 Manual de Utiliza o S rie Nexto Portuguese MU214300 Manual del Usuario Serie Nexto Spanish MU214605 Nexto Series CPUs User Manual English MU214100 Manual de Utiliza o CPUs S rie Nexto Portuguese MU214305 Manual del Usuario CPUs Serie Nexto Spanish MU299609 MasterTool IEC XE User Manual English MU299048 Manual de Utiliza o MasterTool IEC XE Portuguese MU299800 Manual del Usuario MasterTool IEC XE Spanish MP399609 MasterTool IEC XE Programming Manual English MP399048 Manual de Programa o MasterTool IEC XE Portuguese MP399800 Manual de Programaci n MasterTool IEC XE Spanish MU214601 NX5001 PROFIBUS DP Master User Manual English MU214001 Manual de Utiliza o Mestre PROFIBUS DP NX5001 Portuguese MU214301 Manual del Usuario Maestro PROFIBUS DP NX5001 Spanish MU219000 Ponto Series Utilization Manual English MU209000 Manual de Utiliza o da S rie Ponto Portuguese MU209508 Manual de Utiliza o Cabe a PROFIBUS PO5063V1 e Portuguese Cabe a Redundante PROFIBUS PO5063V5 MU219511 PO5064 PROFIBUS Head and PO5065 Redundant English PROFIBUS Head Utilization Manual MU209511 Manual de Utiliza o Cabe a
266. ect 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 above where we have a NIC Teaming pair and one independent Ethernet interface using three modules In order to put together two NX5000 modules as a redundant pair these two modules must necessary occupy adjacent positions on the backplane rack and the checkbox Redundancy of Communication from the module on the left must be selected as show in the figure above Figure 4 10 62 4 Configuration By doing this the parameters edition of the module on the right is blocked The parameters edited in the module inserted on the left get common for the two modules On the other hand clearing the Redundant Communication checkbox from the module on the left causes the separation of the modules which return to behave as individual modules without redundant NIC Teaming pa NextoRedundant project MasterTool IEC XE File Edit View Project Build Online Debug Tools Window Help 5s i 4 21 1S Device 4 X fS Startpage Configuration Bus ff NET 1 G NextoRedtndant T jn fj Device NX3030 EthemetPortParameters el PLC Logic Cluster IP Addressing Method Active IP xj Application j Bill of Materials Custer IP Addressing
267. ection RTC Data Structures RTC_STATUS Table 4 69 Output Parameters of SetDateAndTime When a rising edge occurs at the REQUEST input the function block will write the new DateAndTime values on the clock If the writing is successfully done the DONE output will be equal to TRUE Otherwise the ERROR output will be equal to TRUE and the error will appear in the STATUS variable Utilization example in ST language 118 4 Configuration PROGRAM MainPrg VAR SetDateAndTime SetDateAndTime xRequest BOOL DateAndTime EXTENDED DATE AND TIME xDone BOOL xExec BOOL xError BOOL Status RTC_STATUS xWrite BOOL END_ VAR IF xWrite TRUE THEN SetDateAndTime request xRequest done gt xDone exec gt XExec error gt xError status gt status DateAndTime DateAndTime xWrite FALSE END_IF 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 If the type value of 30 pm it is converted to 1 day and 6 hours and so on SetTimeZone The following function block makes the writing of the time zone settin
268. ecutes a control under the applicative program command It s composed by a CPU a power supply and a I O structure Part of the project corresponding to the source code The PLC project as a whole composed by the project archive source code and by the applicative project executable code Rules of procedures and standard formats that through control signals allow the establishment of a data transmission and error recovery between equipment Acronym for random access memory It s where all the memory addresses can be accessed directly at random and at the same speed It is volatile thus its contents are lost when the device is powered down unless you have a battery for retaining values System that contains reserve elements or doubled to perform a certain task which can tolerate certain types of failure without damaging the task execution Corresponds to the other system CPU e g the CPU1 in relation to CPU2 and vice versa Set consisting on a cluster PLCA and PLCB PX2612 control panel and remote I O systems Group of instructions and variables that allow an applicative program edition to be used in a PLC Ripple present in DC supply voltage It is a standard for serial data exchange between two points point to point It is a standard for serial data exchange between two or more points point to point full duplex It is a standard for serial data exchange between two or more points point to point half duplex See Cycle
269. ed during firmware versions of Nexto CPUs In firmware versions below 1 3 xx there are users and groups Everyone and Owner Table 4 113 Everyone Everyone Table 4 113 User and Groups for 1 3 x x or Lower Firmware Version Since firmware versions 1 4 xx or higher there are users Administrator and Everyone and groups Administrator Developer Everyone Service and Watch Table 4 114 Administrator Administrator Pp Everyone Pp Service ek ee Table 4 114 User and Groups for 1 4 x x or Higher Firmware Version 177 4 Configuration For versions 1 3 x x or Lower Firmware For versions 1 3 xx firmware or lower the following groups and users are defined by default in the Nexto Series CPUs Everyone Group This is the default group to perform the hits on a CPU while there are no defined groups and users Owner Group This group has privileges and you can not remove it 1 3 xx versions of firmware or lower Everyone User The user Everyone is set in the Everyone group This user has no password set Owner User The Owner user is in the Owner group The default password of the user is Owner Owner and can be modified For versions 1 4 x x or Higher Firmware For versions 1 4 xx of firmware or above the following groups and users are defined by default in the Nexto Series CPUs This division into a larger number of groups is to present an initial proposal for different levels of users who can access the CPU Administra
270. ed in sequence form a program module POU form the program type created and filled automatically by MasterTool The user must not change this POU The only task allowed by a redundant PLC Calls the MainPrg program 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 Equipment connected to a communication network where the commands requests to the other network devices originate Communication network where information transfers are initiated only from a single node network master connected to the data bus The other network nodes slaves respond only when requested Set of options available and displayed by a program on video and that can be selected by the user to activate or perform a certain task In PROFIBUS networks it s a network with only one master Address which the PLC accesses a specific I O module Basic element of a complete system that has well defined functions Normally the system is connected by connectors and can be easily replaced Part of an application program capable of performing a specific function It can be run independently or in conjunction with other modules exchanging information via parameter passing Simultaneous dissemination of information to a particular group of interconnected nodes in a c
271. edCmdLoc bStandbyLocal TRU var StandBy command Serial relation FALSE END_IF Logic to put the local IF var _Inact DG_NX4010 tRedundancy var Inactive command E END_IF IF var Inactive command Serial relation DG_NX4010 tRedundancy var Inactive command Serial _ END IF ive _command_ Logic to switch on the IF var TurnOn command DG_NX4010 tRedundancy var TurnOn command Ethernet_relation PLC in Inactive therne Ethernet_relation TRUE RedCmdLoc bInactivel t_relation FALSE TRUE RedCmdLoc bInactiveLocal TRUI F TH EN Local F TH EN Gl TRU Gl Eaj local PLC switche 231 d o TRU RedCmdLoc bTurnOnLocal Ethernet _relation FALSE relation FALSE TH F EN TRUE ff by the PX2612 F 6 Redundancy with NX3030 CPU END IF IF var Turn command Serial relation TRUE THEN DG_NX4010 tRedundancy RedCmdLoc bTurnOnLocal TRUE var Turn command Serial relation FALSE END IF 7 g 7 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 w
272. edundancy RedDgnLoc sGeneral_Diag bExchangeSync diagnostic is indicating a Diagnostics and Commands Exchange service failure a command with Remote suffix isn t allowed to be transmitted to the remote PLC thus won t be executed To trigger a command the RedCmdLoc correspondent bit must be turned on This can be done through a SCADA system executing writing via MasterTool or even turning the bit on inside a POU as ActivePrg or NonSkippedPrg The user doesn t need to worry with the command bit deactivating which is automatically done by the redundancy manager e Incase of commands executed in the local PLC RedCmdLoc commands with Local suffix the bit is turned off as soon as the command is seen and executed e Incase of commands executed in the remote PLC RedCmdRem commands with Remote suffix o Inthe remote PLC the command is executed when the redundancy manager sees an up going edge in the command bit o Inthe local PLC where the command was generated the bit is turned off automatically in the next MainTask cycle 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 It s important to stress that a
273. eep its respective values even after a CPU s cycle of power down and power up The full list of when the retentive variables keep their values and when the value is lost can be found in the Table 2 6 Persistent symbolic variables memory Area where are allocated the persistent symbolic variables The persistent data keep its respective values even after the download of a new application in the CPU ATTENTION The declaration and use of persistent variables should be performed exclusively through the Persistent Vars object which may be included in the project through the treeview in Application gt Add Object gt Persistent Variables It should not be used to VAR PERSISTENT expression in the declaration of field variables of POUs The full list of when the 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 The Table 2 6 shows the behavior of retentive and persistent variables for different situations in which means the value is lost and X means the value is kept 11 2 Technical Description Reset warmPower onfoteyeie x J x ooo i x 4 C A S OOl from the rack while energized Downoad X RebootPre XX Table 2 6 Post command Variable Behavior In the case of Clean All comma
274. en will appear Select Setup Language 2 f Select the language to use during the installation Figure 3 14 Installation Screen Select the installation language and press OK to continue with the installation This action will start the MasterTool IEC XE setup program Then the following screens will appear 35 Setup MasterTool IEC XE fo ts Welcome to the MasterTool IEC XE Setup Wizard This will install MasterTool IEC XE 1 40 on your computer It is recommended that you close all other applications before continuing p Click Next to continue or Cancel to exit Setup Ww a N MasterTool IEC XE Figure 3 15 Initial Screen 32 3 Installation The license contract screen will appear which must be read carefully In case you agree with the license terms click Next to continue Please read the following important information before continuing Please read the following License Agreement You must accept the terms of this agreement before continuing with the installation License Agreement for Software This software belongs exclusively to Altus Sistemas de Automa o S A and it was developed to meet your needs with advanced technology IMPORTANT This is a hondins contract Unon installation I accept the agreement I do not accept the agreement Figure 3 16 License Screen The screen will display the what s new in this version o
275. equests was reached Deferred communications will be carried out in the same sequence in 9 which they were ordered to QX n 2 bystatus bCommPostponed avoid indeterminacy The time spent in this State is not counted for the purposes of time out The bCommldle and bCommExecuting bits are false when the bCommPostponed bit is true QX n 3 bCommDisabled 96 4 Configuration Communication terminated previously was held QX n 4 bCommOk BIT successfully Communication terminated QX n 5 bCommError BIT previously had an error Check error code Previously terminated QX n 6 bCommAborted BIT communication was interrupted due to connection failure QX n 7 bDiag_7_reserved Last error code enabled when bCommError true ERR_EXCEPTION 1 response reported in a code see eLastExceptionCode exception code ERR_CRC 2 response with invalid CRC ERR_ADDRESS 3 MODBUS address not found The address that answered the request was different than expected ERR_FUNCTION 4 invalid function code The function received in response was different from that expected by MASTER_ERROR_CODE request BYTE ERR_FRAME_DATA_COUNT 5 the amount of response data was different than expected ERR_INVALID_ PROTOCOL_ID 6 unidentified Protocol The response protocol is different than expected ERR_NOT_ECHO 7 response is not echo the question FC 5 and 6 ERR_REFERENCE_NUMBER 8 invalid reference numb
276. er 272 6 Redundancy with NX3030 CPU e NX3030_ lt IP address gt _PLCA identification related to the PLCA In this case the field lt IP address gt must be the same as the PLCA IP address configured in the project e NX3030_ lt IP address gt _PLCB identification related to the PLCB In this case the field lt IP address gt must be the same as the PLCB IP address configured in the project Next the PLC which MasterTool is to connect must be selected from the list and the button Set Active Path must be pressed Then at executing the command from the Online Login menu MasterTool connects to this PLC ATTENTION MasterTool can only connect to one PLC at a time To connect to several PLCs multiple instances must be open in MasterTool when care must be taken to open the correct project in each instance Modification Download in a Redundant Project After both PLCs PLCA and PLCB from the redundant pair had its initial program already downloaded as described in the Initial Downloading of a Redundant Project section it s possible to download successive changes in the project when such changes are necessary MasterTool connection to the PLCs responsible for the modifications download must be executed as described in MasterTool Connection with a NX3030 CPU from a Redundant PLC section In this section it is explained how it s possible to connect to a specific PLC PLCA or PLCB to the Active PLC or to the Non Acti
277. er FC 15 and 16 ERR_INVALID_FRAME_SIZE 9 reply less than expected QB n 1 eLastErrorCode Last exception code received by master NO_EXCEPTION 0 FUNCTION_NOT_SUPPORTED 1 MODBUS_EXCEPTION MAPPING_NOT_FOUND 2 BYTE ILLEGAL_VALUE 3 ACCESS_DENIED 128 MAPPING_DISABLED 129 IGNORE_FRAME 255 QB n 2 eLastExceptionCode Communication statistics Communications counter terminated with or without errors The user can test when communication has finished QW n 4 WE ORIMGOURIE WORD testing the variation of this counter When the value 65535 is reached the counter returns to zero Communications counter terminated with errors When the QW n 6 wCommErrorCounter WORD value 65535 is reached the counter returns to zero Table 4 48 MODBUS Client Relations Diagnostics 97 4 Configuration Exception Codes the definitions of the exception codes 128 129 and 255 are valid only with Altus slaves For slaves from other manufacturers these exception codes can have different meanings Disabling Variable field for the variable used to disable MODBUS requests individually configured within requests The request is disabled when the variable corresponding to the request is equal to 1 otherwise the request is enabled ATTENTION Unlike other tasks of an application when a mark is reached at MainTask debugging the MODBUS Ethernet Client instance task or any other MODBUS task will stop be
278. er files memory This memory area offers another way for the user to store files such as doc pdf images and other files This function allows data recording as in a memory card For further information check Configuration User File Memory Maximum number of tasks The maximum number of tasks defined for each CPU model and among different project profiles is better detailed in the chapter Maximum Number of Tasks Redundancy support half clusters The software version 1 1 0 0 or onwards product revision AB or onwards supports redundancy of NX3030 CPUs Event oriented data reporting SOE The data types are found in the Annex A Maximum number of PROFIBUS DP network From MasterTool IEC XE version 1 22 and onwards 4 PROFIBUS DP networks are supported for NX3020 and NX3030 CPUs Previous versions support 2 PROFIBUS DP networks The limit of PROFIBUS DP masters is 4 which means that only 2 redundant networks can be used 12 2 Technical Description Serial Interfaces COM 1 NX3010 NX3020 NX3030 Shielded female DB9 Physical interface RS 232C Modem signals RTS CTS DCD Baud rate 200 300 600 1200 1800 2400 4800 9600 19200 38400 57600 115200 bps Protocols Master Slave MODBUS RTU Open protocol Table 2 7 COM 1 Serial Interface Features COM 2 NX3010 NX3020 NX3030 Shielded female DBS Physical interface RS 422 or RS 485 depends on the cable choice Communication direction RS 422 full duplex
279. er information about the use of the memory card see Configuration Memory Card chapter RTC Clock Nexto Series CPUs have an internal clock that can be used through the NextoStandard lib library This library is automatically loaded during the creation of a new project to perform the library insertion procedure see Libraries chapter Figure 4 39 shows how to include the blocks in the project E Configuration Bus J Device i Library Manager X Add library X Delete library Properties 7 Details Name Namespace 3 NextoStandard WAA NextoStandard gt LibDataTypes Manufacturer LibDataTypes NX3030 Diagnostic Structs WAA NX3030_Diagnostic_Structs NX5001 Diagnostic Structs WAA NX5001_Diagnostic_Structs NX1001 Diagnostic Structs WAA NX1001_Diagnostic_Structs NX1005 Diagnostic Structs WAA NX1005_Diagnostic_Structs gt NX2001 Diagnostic Structs WAA NX2001_Diagnostic_Structs NX2020 Diagnostic Structs WAA NX2020_Diagnostic_Structs 2G9 NX4000 Diagnostic Structs WAA NX4000_Diagnostic_Structs NX5000 Diagnostic Structs WAA NX5000_Diagnostic_Structs gt NX6000 Diagnostic Structs WAA NX6000_Diagnostic_Structs NX6100 Diagnostic Structs WAA NX6100_Diagnostic_Structs NX6010 Diagnostic Structs Manufacturer NX6010_Diagnostic_Structs NX6020 Diagnostic Structs Manufacturer NX6020_Diagnostic_Structs Standard System Standard NXModbus Diagnostic Structs WA
280. er this first download the IP address discovered in the first step of this procedure usually isn t valid anymore This IP Address change in NET 1 causes a connection loss between MasterTool and the CPU which is showed on the screen For further details regarding MasterTool reconnection see MasterTool Connection with a NX3030 CPU from a Redundant PLC section MasterTool Connection with a NX3030 CPU from a Redundant PLC After executing the procedure described in the Initial Downloading of a Redundant Project section in both PLCs PLCA and PLCB MasterTool connection through the NET 1 interface from NX3030 CPU can be made through one of the following addresses e PLCA IP address NET1 address exclusive for PLCA e PLCB IP address NET1 address exclusive for PLCB Independent from the PLC state MasterTool can only connect to it using the PLC exclusive address configured in PLCX IP Address But in case the PLC is in Active state all other services can connect to it either by the PLCX IP address or by the Active IP address To connect to a specific CP at first a double click must be done on the Device NX3030 CPU in the Device Tree go into Communication Settings tab click on the Gateway and press Scan Network button to list all PLCs detected by MasterTool in the network 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 us
281. erTool sends the following message and waits for authorization If the other PLC is in Standby State it will assume as Active and turn off this PLC If not this won t happen but the automated process will no longer be controlled Warning before Logging to the Non Active PLC In normal circumstances it isn t usual MasterTool to connect to the Non Active PLC This way when there s a try to execute this type of command MasterTool sends the following warning You are logging in to a Non Active PLC and this is not usual Are you sure you want to execute this command On the other hand there are circumstances not so usual in which it s necessary to login in the Non Active PLC and in these cases the user must authorize the login Such circumstances may occur e g e For initial configurations as described in Initial Downloading of a Redundant Project section 284 6 Redundancy with NX3030 CPU e 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 e 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 CPU Redundancy State The PLC redundancy state described in Redundant CPU States is seen in
282. erate vital failures This option is important for applications in which the modules of inputs and outputs are distributed over Ethernet network In this case if a failure occurs on the Ethernet port this will generate a switchover This behavior is applicable only to Ethernet ports where there is at least a communication driver that manages fault The communication drivers that generate vital failure are MODBUS client and MODBUS Symbol Client all references to MODBUS Client in the following sections apply to both cases The MODBUS Server drivers MODBUS Symbol Server and EtherCAT Master do not generate vital failure Thus if an Ethernet port has a MODBUS Client driver configured and a failure occurs in the Ethernet port a switchover will be generated if vital fault option is enabled If the driver configured on the Ethernet port is a MODBUS Server even if there is failure in the door it will not generate a vital failure that causes a switchover To a fault be considered a vital failure in an Ethernet port on a MODBUS Client all servers configured in the driver must be faulty That is if there is more of a MODBUS Client driver configured in the same Ethernet port is considered vital fails when all servers of both Clients are faulty When the Ethernet port is configured to operate with NIC Teaming the vital failure will be considered only when the two pair of doors fails 241 6 Redundancy with NX3030 CPU Failure in Ethernet Inter
283. erties dialog The access rights to the objects are inherited If the object has a main object the access rights of this become the standard secondary object settings e g If an action is assigned to a program it is inserted in its structure Thus the program is the object main action With regard to access rights usually relations of the main objects side correspond to the relations shown in the POUs or Devices tree and are indicated in the Permissions dialog using the syntax lt main object gt lt secondary object gt Example Action ACT is attributed to MainPrg object POU Thus in the window of the POUs ACT is shown in the object tree in MainPrg In the Permissions dialog ACT is represented by MainPrg ACT indicating that MainPrg is the principal of ACT If the right changes was 172 4 Configuration explicitly denied to MainPrg and to a certain group of users the default value of this right to ACT would also be denied automatically To access the Permissions screen should click this option in the Project gt User Management menu This will open the screen in Figure 4 85 Permissions Actions 0 Commands Q Object types Project objects Device 8 add or remove children Configuration NX3030 lt Empty gt COM 1 COM 2 NET 1 NET 2 NX5001_A NX8000 PLC Logic Application Bill of Materials Danfinsuratian and Danniumnetinn Permissions G
284. es shall always be global For the declaration of retentive symbolic variables it must be used the key word RETAIN For example for local variables PROGRAM MainPrg VAR RETAIN wLocalSymbolicRetentiveVariable_01 WORD END_VAR Or for global variables declared within a list of global variables 44 4 Configuration 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 These variables will be global and will be declared in the following way within the object VAR_GLOBAL PERSISTENT RETAIN wGlobalSymbolicPersistentVariable 01 WORD END _ VAR TCP Configurations Some of the advanced configurations affect the Nexto Series CPUs supported protocols as they are connected to the TCP network layer as following e Initial Time out e ACK Delay The CPU Nexto before it responds to any request and as any other Ethernet equipment which uses the TCP transport layer demands a communication door opening in other words the connection establishment The Interface connections quantity is limited and simply does not establish any other connection after its limit is reached This can cause problems for the established connections in the server mode as the connections closing depends on the other equipment the client The TCP transport laye
285. es there is no application in the memory card to be APPLICATION NOT FOUND transferred to the CPU CRC NOT FOUND Indicates that the CRC application does not exist MCF FILE NOT FOUND Indicates there is no MCF file in the memory card NO TAG e is no configured tag for the CPU in the MasterTool IEC There is no configured description for the CPU in the NO DESC MasterTool IEC XE Indicates that there are error s on diagnostics message s o Moe ERROR the requested module s Indicates the product presented an unexpected problem Get in SIGNATURE MISSING contact with Altus Technical Support sector APP ERROR RESTARTING Indicates that occurred an error in the application and the Runtime is restarting the application APP NOT LOADED Indicates that the runtime will not load the application LOADING APP Indicates that the runtime will load the application WRONG SLOT Indicates that the CPU is in an incorrect position in the rack Indicates that there are serious problems in the CPU startup FATAL ERROR such as CPU partitions that were not properly mounted Please contact Altus customer support Indicates that the CPU hardware and software are not HW SW MISMATCH compatible because the product presented a unexpected problem Please contact Altus customer support UPDATING FIRMWARE Indicates the firmware is being updated in the CPU RECEIVING FIRMWARE Indicates the updating file is being transferred to the CPU UPDATED Shows the firmware version u
286. esccchscsescssevsecscnecesecstecscuseneceseessveseeacessestssssuseensesesssseseursenseseesecsseudsencesecses 210 Writing and Forcing Variables ccccsssssssssssssccsssssssssscccssssssssssssccsscscsssssssssccssssssssssssscsssssscssssseeees 211 J ENET ii aA EEE AAAA A AA RA AAAA 211 SUIT AEOME NEOUS AE AT T TT a T T S 212 Project Upload iesscccscscscssscscsssvecsseseconssssesonssasouccssodsvecasocvencnsesvescesesteuconsssdecoascsveconscsdessosssdseecndsdsescncs seusoastets 214 CPU Operatine States ciccccciccccccssecscocccesessssvedesscecesecsdsvedenscecetecs ssesesscecesessdstevesececesesssstesesecesedecssssevesenesesesss 215 BRU a ects isc a tne snc esau esas unas oxi enaes sav wana nai ana va sac uae uni ene ve uae taunanai anaes nee eaan sentence E E EO 215 SLOP Sa sciscsresepaicsescsscessrcsaicsesssaccssedsscesseeosiepessyssepeseyseusesesseueseesseuesecesocssecssecssecsssepansesapanctseasscresnssestases 215 Break pott yeee oeer erreser sso e ono onan goes oe so sone 215 EX COPUOM E E E E E N E A EE E sibbetks sheuates 215 Rese Warmia a E a a E a a S a a E 215 MRCS CEC OLU T e T e E e P e Te Te T e T E T T T a T E a e ee ee ee T 215 Reset Or 81 iasororaiora rane natia A EE E ENE E ai 215 REDUNDANCY WITH NX3030 CPU 00 cssscsssccscssccsscceescseesscceesscceesscessscceesscssesscessscsessscseesscssessseees 216 EHEC UCENON sass Sssssvsss soso sitisSuiese satioksdobiSobwiin elivnniionu Setlist Snip iho Subp Suse Susp take eoe aa Eaa
287. escsticsenestcansseuetetooues coscacseasesasesesoccSecedecotecssecndeccbacesestsesesesesec sectsecoecssecedescbesebasabesokesse 115 Function Blocks for RTC Reading and Writing 0 eee ceseseeecessneeeeeesnaeecsessaeeeeessaeeesessaeeeeesaeees 116 RIG Data Strictires ioon asana a E TOET OEE OEE OEE OEE OEE OEE OEE OE EEE 120 Sa DESA ET a e AE E A E E A A 122 Memory CILA EEE EEA AE E A ENEA AEN EAA EN EA AE AA e 124 MasterT ool ATES rai E IERA AA ENEE EENE a 126 CPU s Informative and Configuration Menu ssososssooesssoesessocssssoosessoocesssocssssoessssoosessoosesssoessssoesesssoe 127 Function Blocks and Functions sscsccsssssssssssesssseesssceessseesscceessssessscessscseesscsessscessscssesscseesscsseseseees 130 Special Function Blocks for Serial Interfaces 0 0 0 eeesceeessseceeeessceeeesseeeceessaeeeeessaeeesessaeesessaaeees 130 Inputs and Outputs Update ees eeesscecceesseeeceessececeessaceccesseeecesseeecsesaeecessnseeesessaaeesessaeeseesaaeees 145 PID Function BlOCK testes ck sect eee eee 148 Bini toil ROUT eepeeeererenererererererereeerererene rererere tererene rere rere tere rere rere rere rere rere tere rere rere rere tere rere tere rere tere rerererererer 151 Won e dundant nET eaa 154 User Lofer E a E E EEE EEEE E E EOE OE OEE OEE E EAR 157 SINIVEB EE E E A E E E EN T E E 160 TIMPOGUCH OM EAE EE ETE TE E TE E TE E en E E E E E E ENA 160 SNMP in Nerto CPUS Cura A ARAETA AKARATA RAKAA TA RREA AAA AE 160 Private
288. esired 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 SERIAL_CFG Figure 4 52 Serial Configuration Block Input parameters Type REQUEST BOOL This variable when true enables the function block use Select the serial port as described in the RORT SERIA PORT SERIAL_PORT data type This structure defines the serial port PARAMETERS SERIAL_PARAMETERS configuration parameters as described in the SERIAL_PARAMETERS data type Table 4 78 Serial_CFG Input Parameters Output parameters Type BOOL This variable is true when the block is completely executed It is false 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 is ERROR BOOL false otherwise It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR ILLEGAL_SERIAL_PORT ILLEGAL_SERIAL_MODE ILLEGAL_BAUDRATE ILLEGAL_DATA_BITS STATUS SERIAL_STATUS ILLEGAL PARITY ILLEGAL_STOP_BITS ILLEGAL_HANDSHAKE ILLEGAL_UART_RX_THRESHOLD PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE DCD_INTERRUPT_NOT_ALLOWED CTS_INTERRUPT_
289. essoossssoosesssosssssocssssoesessoosssssosssssossesssesse 15 Performa ne oss scecsescecscccscscsecedsscscscessscescscsecescscsecescscscccsccdscccscscscccscscscscscscscscsescscccscedscccecedscccecedecccecsesccesecose 16 Application limes ve croc eeetce uae ot eusn cet E E cetn sibecets A ER A E a E 16 Time for Instructions Execution ana E E E E E E E E E EE E E 16 Minaa oin T E SEa a E a ALI ALOACEAE 16 Diterva Wel Gil na cep ee pe a E E E E E EEE EE E E E E E E 16 Physical BITA EITO A EE 17 Porchase Data ucccrararirrrarararrara stat ctes ches ches ctes ches stesctesstesstesstesstasstesstesstasstasstacctecctesctesctescteccteccbetstetetetetie 17 teorann TSS ee re a I I I a I TER TE OS OT 17 Product COde sy sss gases ieesstesdeep ete saee jee sasa a Saou Suse suse Sabo saue Se sedans nese dase nese dase uusesauebubesadebeSanateseSanales 17 Related Product vicccccccccccccscccecccecesecscecssesesesesecesesusecesesnsecececnsecececnsecesecnsesecesesececececececectcececectcecscecscecsescscesecs 18 Be MINS IPATE ATION A A 20 Mecha miGalTnistanlatiOns ccccicccecececacace cece ce acetate acetate sete a teva de ace vate ate vade aleve te ate cate ate tate etetitetetetetetetavs 20 Electrical Tmstallationiccssssssccsscstessteschesctesctesctusshuschesstessbesstesstassbenstasssunstasscunsbassbucsbessbecctusstecctessbescbebebenstebetes 20 Ethernet Network Connection ccccccccccsssssssssssssssscssssccscccsscsccccsccccsscsssscssccsssscscsccssscssssscsscsss
290. et NET1 QW n 207 QW n 207 QW n 207 SE EIEOE ore Ethernet NET1 QW n 209 QW n 209 QW n 209 wRXDropErrors Ethernet NET1 wRXFrameErrors QW n 211 QW n 211 QW n 211 QW n 213 QW n 213 QW n 213 Ethernet NET1 wMulticast 311 7 Maintenance QW n 215 QW n 215 QW n 215 QW n 217 QW n 217 QW n 217 ee NA QX n 220 0 cea NA NA QB n 222 A QB n 238 QX n 220 2 QX n 220 3 QB n 221 A QB n 254 A QB n 270 A QB n 288 A QB n 292 A QB n 296 A QB n 300 A QD n 306 QD n 310 QD n 314 QD n 318 QW n 322 Zz QW n 324 Zz QW n 326 Zz QW n 328 Zz QW n 330 Zz QW n 332 Zz QW n 334 Zz QW n 336 QX n 220 0 QX n 220 1 QX n 220 2 QX n 220 3 QB n 222 QB n 238 QB n 221 QB n 254 QB n 270 QB n 288 QB n 292 QB n 296 QB n 300 QD n 306 QD n 310 QD n 314 QD n 318 QW n 322 QW n 324 QW n 326 QW n 328 QW n 330 QW n 332 QW n 334 QW n 336 WORD WORD BIT WORD BIT BIT BIT BIT BYTE STRING 15 STRING 15 STRING 15 STRING 17 BYTE ARRAY 4 BYTE ARRAY 4 BYTE ARRAY 4 BYTE ARRAY 6 DWORD DWORD DWORD DWORD WORD WORD 312 Ethernet NET1 wReserve do Ethernet NET1 wReserve d1 Ethernet NET2 bLinkDow n Ethe
291. etween the CPUs projects are allowed e A configuration request is already existent at the beginning of the Not Configured state This occurs in the moment the CPU is switched on and also other situations described in the next sub sections e The STAND BY button was pressed during the Not Configured state This causes a manual configuration request The user typically presses STAND BY after fail repairing which had driven this CPU to the Not Configured state Transition 2 Starting to Not Configured This CPU was turned off or restarted warm reset cold or origin or its CPU went to Stop mode The identification register of this CPU is invalid different than PLCA or PLCB There are logic configuration errors in the project received from MasterTool IEC XE The other CPU is in the Active state and the firmware version in this CPU is incompatible with firmware version in it e The other CPU is in Active state and the project in this CPU is different from the project in it Besides going to the Not Configured state a configuration request is made This way after the projects are synchronized the CPU goes out automatically from the Not Configured state to the Starting state This condition isn t analyzed if the project automatic synchronization is disabled Project Synchronization Disabling section Transition 3 Starting to Inactive e NX4010 module not detected in the bus or its microprocessor failure e Asynchronism channel
292. etwork is redundant both composing networks must fail double failure e Total failure of an Ethernet network in active CPU if this network is configured with vital failure If the Ethernet network is redundant both networks that compose it must be faulty double fault Failures Associated to Switchovers between Half Clusters Managed by the User Among the described transition in the Transition between Redundancy States section some turn possible the user to manage switchovers between half clusters due to failures that don t generate automatic switchovers There are very particularly cases which depend on the philosophy of each client E g a case where the SCADA system loses the communication with the Active CPU but keeps communicating with the Stand by CPU Some clients would rather to have a manual switchover where the operator presses the PX2612 STAND BY button to the Active CPU The switchover causes a communication retry with the new Active CPU An alternative solution would be to cause a switchover by sending a command from the SCADA system to the Stand by CPU which would transmit to the Active CPU through NETA NETB using the RedCmdLocal Stand by CPU and RedCmdRem Active CPU data structures to transport a command equivalent to the PX2612 STAND BY button It would be also possible the Active CPU detect its communication lost with the SCADA system itself and to activate a command in the RedCmdLocal equivalent to the PX26
293. even tolerate a simple failure without causing some kind of unavailability In a redundant CPU using CPU NX3030 this is related to the following components e PROFIBUS remotes slaves in a non redundant PROFIBUS network e Ethernet remotes slaves in a non redundant network e I O Modules The failure intolerance of a non redundant PROFIBUS network can be solved if a redundant PROFIBUS network is used which is advisable in systems that demand a high failure tolerance Figure 6 1 shows an example of a redundant PROFIBUS network architecture Likewise intolerance to failure of a non redundant Ethernet network can be solved by using a redundant Ethernet network configuration with NIC Teaming Regarding the I O module unavailability it must be observed that it doesn t imply total system unavailability It constitutes a partial unavailability only in the control mesh that uses this I O module Even though there s no redundancy prevision for I O modules the user application can manage it in special cases E g the user can insert 3 analog input modules in 3 different PROFIBUS remotes and implement a vote scheme between analog inputs triples for a critic system However as mentioned such solutions must be managed by the user There s no automatic support for them Such solutions generally speaking also imply in the field transducers and actuators redundancy Simple Failure without Unavailability Causing a Switchover Some redundant com
294. ex the most significant byte in other words the QD4 will always have as most significant byte the QB4 Therefore it will not be necessary to make calculus to discover which DWORD correspond to defined bytes The Table 5 1 shows little and big endian organization MSB lt Little endian Traditional LSB BYTE QB7 QBE6 QB5 QB4 QB3 QB2 QB1 QW3 WQW 2 QW 1 CP UN EX QB0 WORD QW0 4 4 DWORD LWORD QLO CPUNEXTO HSB lt Big endian NEXTO gt LSB BYTE QBO QB1 QB2 QB3 QB4 QB5 QBE6 AAWO APAW2 APAW 4 CP UN EX QB7 WORD A QW6 4 4 DWORD LWORD QLO CPUNEXTO Table 5 1 Example 182 5 Initial Programming HSB LSB QB00 QB01 QB02 QB03 QB04 QB05 Table 5 2 Memory Organization and Access ee E E QW 00 QW 02 QW 04 183 QW 01 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 Single 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 With the diversity of application types supported by the Nexto Series Runtime System following a profile is a way to simplify the programming complex
295. f TRUE The PX2612 LED STAND BY is blinking FALSE The PX2612 LED STAND BY is on bStandbyLED or off TRUE The PX2612 LED INACTIVE is on FALSE The PX2612 LED INACTIVE is off or blinking bBlinkInactiveLED TRUE The PX2612 LED INACTIVE is blinking FALSE The PX2612 LED INACTIVE is on bInactiveLED or off TRUE The PX2612 panel is in test mode FALSE The PX2612 panel is in normal mode This diagnostics inform this PLC identification 0 non redundant 2 PLCA 3 PLCB It s a copy from the non volatile variable used to identify the PLC as described in the NX3030 CPU Identification section In the Initial Downloading of a Redundant Project section MasterTool command used to write on this non volatile variable is described informs the redundancy state of this PLC Not Configured 0 Starting 2 Stand by 3 Active 4 Inactive 5 Measures for how long milliseconds the current redundancy state has been assumed This time 6 Redundancy with NX3030 CPU Cor __ steps inarementing when reaches 65505 Error code discovered during the configuration QW n 13 wConfigErrorCode process in the Not Configured state See ConfigError diagnostics described previously 32 bits applicative project CRC used to detect QD n 15 dwApplicationCRC differences between the applicative projects of the 2 PLCs 32 bits project archive CRC used to detect QD n 19 dwArch
296. f MasterTool IEC XE that was just installed 33 3 Installation Please read the following important information before continuing When you are ready to continue with Setup dick Next MasterTool IEC XE MT8500 Version 1 40 Changed the installer based in Microsoft InstallShield to installer based in Inno Setup This change reduces the installation time Added MODBUS devices with mappings of symbolic variables Added Import Export command to CSV files This command imports or exports the project configurations Added Import Export support to the MODBUS Symbolic drivers A ddod e mer ee ele UI mee ele SIVAN A OR Th wwe mere ee ee ee Figure 3 17 Version Info Screen On the next screen can be set if a shortcut will be created on the desktop of the computer Select the desired option and then press Next to continue Which additional tasks should be performed Select the additional tasks you would like Setup to perform while installing MasterTool IEC XE then click Next Additional icons Create a desktop icon Figure 3 18 Desktop Icon Option 34 3 Installation On the next screen a review of the selected components to be installed is executed Click Next to continue or Back to modify any feature Setup is now ready to begin installing MasterTool IEC XE on your computer Click Install to continue with the installation or dick Back if you want to review or change any sett
297. f authentication trials r Source Download V Automatically logoff after time of inactivity 83 Users and Groups Visualization Profile Compiler warnings Figure 4 84 Project Settings Users and Groups Settings The following basic settings for the user accounts can be performed e Maximum number of authentication trials If this option is enabled the user account will become invalid after the specified number of attempts to carry out the login with the wrong password If the option is not enabled the user can perform as many attempts as you want Default enabled option 3 attempts Allowed values 1 10 e Automatic logoff after time of inactivity if this option is enabled the user account of the connection will be automatically lost after a certain period of inactivity lack of actions via mouse or keyboard Default enabled option 10 minutes Allowed time values 1 180 minutes Access Rights Management User management in a project is only useful if combined with the management of access rights In a new project basically all access rights are not set automatically but set to a default value that is usually the rights are guaranteed During project execution each right can be explicitly granted or denied and set back to the default The management of access rights is made in the Permissions dialog or to access rights to objects the Access Control dialog which is part of the Object Prop
298. f input variables Q REFRESH_OUTPUT REFRESH_OUTPUT Figure 4 62 Block for Output Updating Input parameters byRackNumber Position number where the module is Table 4 97 REFRESH_OUTPUT Input Parameters Possible ERRORCODE e NoError Execution success e JOModuleAbsent The module was configured but is absent e YJOModuleNotConfigured The module was not configured e ParameterMismatch This error is returned in case the Always Update Variable option is not set or in case the REFRESH_OUTPUT function is called for a module that has only inputs e OutputWriteFail Module internal critical failure the function transmitted frame was not returned within the defined time out e FrameTransmitError Module internal critical failure error during the frame transmission in the function e BusBusy Module internal critical failure o the bus isn t enabled for frame transmission in the function Utilization example in ST language PROGRAM MainPrg VAR Info ERRORCODE byRackNumber BYTE bySlotNumber BYTE END_ VAR INPUTS byRackNumber 0 bySlotNumber 10 FUNCTION Function call Info REFRESH OUTPUT byRackNumber bySlotNumber Variable Info receives possible function errors 147 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 projec
299. face A switchover can be generated due to failure in the Ethernet interface such as a loss of link The link loss may be caused for example by a cable breakage or failure of a switch on the Ethernet network Accordingly it is necessary that in addition to being configured to generate vital failure there is a MODBUS Client instance configured on the Ethernet interface When the interval of MainTask is greater than or equal to 100 ms after the fault is detected the switchover will occur in up to two cycles of MainTask When the interval of MainTask is less than 100 ms switchover will occur within 100 ms plus the time of MainTask after detection of failure 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 bAllIDevicesCommFailure diagnostic see Modbus Diagnostics used at Redundancy section used in changes its state to TRUE When this happens the switchover will happen 3 seconds after this transition OPC Communication Use with Redundant Projects The OPC protocol can be configured to communicate with redundant clusters over SCADA systems When this option is selected in the creation of a redundant project the Symbol Configuration object is added to the project In this object are set system variables that will be sent to the SCADA system This communication option is enabled in the CPU of t
300. false Table 4 99 PID Block Output Parameters Figure 4 64 shows the block diagram of a PID loop as the Nexto CPU execution DeadBand EnableP Proportional Term Kp x Er Enablel Integral f Kp x Er Term T DerivPY EnableD Derivative dEr Term Me x TX dt MinMV MaxMV MaxVarMV Manual ManualMy CONTROLLED PROCESS Figure 4 64 PID Diagram 150 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 ATTENTION It is important to stress that for the correct functioning of the Timer Retain blocks the variables must be declared as Retain VAR_RETAIN The three blocks already available in the MasterTool IEC XE software Nexto library are described below for the library insertion proceeding see Libraries chapter TOF_RET The function block TOF_RET implements a time delay to disable an output When the input IN has its state changed from TRUE to False or a falling edge the specified time PT will be counted and th
301. filled by the user Main POU programs NonSkippedPrg this POU is executed in both CPUs PLCA and NonSkippedPrg and ActivePrg PLCB independent on the redundancy state Active or Inactive It s used for diagnostics and special commands management ActivePrg this POU is executed only in the Active CPU and is used for the final user s process control Table 6 1 General features of a redundant CPU Purchase Data The minimum configuration for a redundant CPU implies on the purchase of the following modules Two racks which must be chosen between the three available models according to the modules to be installed o NX9001 12 positions 6 double modules o NX9002 16 positions 8 double modules o NX9003 24 positions 12 double modules Two NX8000 Two NX3030 Two NX4010 Two AL 2319 Furthermore it may be necessary to purchase the following additional modules One PX2612 One AL 2317 A One AL 2317 B Two modules NX5001 for each simple PROFIBUS network Four modules NX5001 for each redundant PROFIBUS network Two modules NX5000 for each additional simple Ethernet network Four modules NX5000 for each additional redundant Ethernet network NIC Teaming ATTENTION It can be installed up to 4 PROFIBUS modules in each half cluster This means that we can configure up to 4 simple PROFIBUS networks or up to 2 redundant PROFIBUS networks 225 6 Redundancy with NX3030 CPU Principles of Operation In
302. fined as 1464 bytes The figure below illustrates the redundant and non redundant Q direct representation variables allocation where RQS is the Q output quantity configured as redundant in the first section and RQD is the Q diagnostics quantity configured as redundant in the second section 229 6 Redundancy with NX3030 CPU 0 redundant sei outputs OS kbytes ROS 0 65535 Res erved for 65 kbytes redundant 0 output expansion 65536 ROS 96 kbytes Redundant 0 ROD kbytes diagnostic ROD ROS 81919 Reserved for redundant 0 diagnostic 80 kbytes expansion 81920 RQD Non redundant an 16 kbytes Figure 6 8 Redundant and Non redundant Q Allocation Redundant and Non redundant M Variables The NX3030 CPU allocates 64kbytes of M variables MB0 MB65535 All the 65535 bytes can be redundant MBO0000 MB65535 By default the redundant M variables quantity is 0 The M variable use must be avoided and the use of symbolic variables preferred see Redundant and Non redundant Symbolic Variables section Redundant and Non redundant Symbolic Variables Besides the direct representation variables I Q and M which are allocated automatically The user can explicitly declare symbolic variables inside of POUs or GVLs The maximum size allowed for redundant symbolic variables allocation is 512kbytes ATTENTION Symbolic variables must not be confused with AT variables The AT variables ar
303. ght be blocked There are eight tasks already completely defined as shown on Table 5 6 as the respective programs associated to the chosen language The intervals and trigger events of any task and the event tasks priorities can be configured by the user At the application development using the Expert project profile a special care is necessary with the event task scaling In case there is information and resources sharing among these tasks or between these tasks and the basic tasks it is strongly recommended to adopt strategies to guarantee the data consistence Prony Type Interval Evom Table 5 6 Expert Profile Tasks The Custom project profile allows the developer to exploit all Runtime System potentialities implemented in the Nexto Series processing centrals No functionality is disabled no priority task and programs association or nomenclature is imposed The only exception is for the MainTask which will always exist with this name is this Profile Besides the real time tasks with 00 to 15 priorities which are scaled by priority this profile also allows the tasks definition with smaller priorities smaller from 16 to 31 In this range it is used the Completely Fair Scheduler time sharing which is necessary for the execution of the codes that might be blocked e g the use of sockets 186 5 Initial Programming Machine The developer is free to partially follow or not the organization defined in the othe
304. gs SetTimeZone SetTimeZone Figure 4 44 Writing of the Time zone Settings input parameters Structure with time zone to be configured See TIMEZONE TIMEZONESETTINGS section RTC Data Structures TIMEZONESETTINGS Table 4 70 SetTimeZone Input Parameters Returns the error occurred during the SetTimeZone RTC_STATUS reading setting See section RTC Data Structures RTC_STATUS Table 4 71 SetTimeZone Output Parameters When called the function will configure the TimeZone with the value configured at system time zone 119 4 Configuration Utilization example in ST language PROGRAM MainPrg VAR Status RTC_STATUS TimeZone TIMEZONESETTINGS xWrite BOOL END _ VAR FB SetTimeZone IF xWrite TRUE THEN Status SetTimeZone TimeZone xWrite FALSE END_IF ATTENTION To perform the clock should be used time and date values within the following valid range 00 00 00 hours of 01 01 2000 to 12 31 2035 23 59 59 hours otherwise is reported an error through the STATUS output parameter For details of the STATUS output parameter see the section RTC_STATUS RTC Data Structures The reading and setting function blocks of the Nexto series CPUs RTC use the following data structures in its configuration EXTENDED_DATE_AND_TIME This structure is used to store the RTC date when used the function blocks for date reading setting w
305. gs Slave Address 1 Communication Time out ms 3000 Maximum Number of Retries 2 Figure 4 12 Device General Parameters Settings Slave Address MODBUS slave address 0 to 255 Communication Defines the application Time out ms level time out 3009 TO 1069939 A Defines the numbers of R numser retries before reporting a 2 Oto9 communication error Table 4 22 Device Configurations 68 4 Configuration Notes Slave Address According to the MODBUS standard the valid slave addresses are from 0 to 247 where the addresses from 248 to 255 are reserved When the master sends a writing command with the address configured as zero it is making broadcast requests in the network Communication Time out The communication time out is the time that the master waits for a response from the slave to the request Fora MODBUS RTU master device it must be taken into account at least the following system variables the time it takes the slave to transmit the frame according to the baud rate the time the slave takes to process the request and the response sending delay if configured in the slave It is recommended that the time out is equal to or greater than the time to transmit the frame plus the delay of sending the response and twice the processing time of the request For more information see Protocols Configuration Communication Performance chapter Maximum number of retries Sets the number of retries before reporting a communi
306. guration which causes a switching from the Not Configured to the Starting state typically after the failures that caused the transition to the Not Configured state are repaired After the Starting state normally the CPU is supposed to go to the Stand by state or Active if the other CPU isn t in the Active state e To request a switching from the Inactive state to the Not Configured state requesting a configuration already This occurs typically after the failures which caused the transition to the 245 6 Redundancy with NX3030 CPU Inactive state were corrected After the Not Configured state the configuration must take it to the Starting state After the Starting state normally the CPU is supposed to go to the Stand by state or Active if the other CPU isn t in the Active state The INACTIVE button requests a switching from the Stand by state to the Inactive state which can be useful to execute a programmed maintenance in the Stand by CPU After this maintenance the STAND BY button may be used to make it go back to the Stand by state passing by the Not Configured and Starting state see previous description of the STAND BY button The TURN ON PLCx x B for PLCA or x A for PLCB button is used to cause a reactivating in the other CPU in case the local CPU has switched off As it is described in the Transition between Redundancy States section there are exceptional situations when a CPU switches off the other at assuming th
307. h o SPANISH Changes the language to Spanish e Visualization of information about the network set in the device o NET 1 IP ADDR Address Ex 192 168 0 1 o NET 1 MASK Sub net mask Ex 255 255 255 0 o NET 2 IP ADDR address Ex 192 168 0 2 o NET 2 MASK Sub net mask Ex 255 255 255 0 e Information about the software versions o FIRMWARE CPU software version Ex 1 0 0 0 o BOOTLOADER CPU boot loader version Ex 1 0 0 0 o AUX PROC CPU auxiliary processor version Ex 1 0 0 0 e Access to the PLC redundancy information o PLC ID Informs the PLC identification in the redundancy Possible information CPA CPB o REMOTE STATE Informs the state of the remote redundant PLC Possible states ACTIVE STANDBY INACTIVE NOT CONFIG STARTING UNAVAILABLE PROJ SYNC Informs if the synchronization of the projects is enabled CONNECTED NOT CONNEC DISABLED START SYNC SYNCHRONIZED e Access to the Memory card data o MEMCARD gt CPU Transference of the memory card project to the CPU o CPU gt MEMCARD Transference of the CPU project to the memory card o FORMAT Formats the card to the FAT32 files system Figure 4 51 describes an example of how to operate the Nexto CPUs menu through the contrast adjust menu procedure from the Status screen Besides to make the configuration easy it is possible to identify all screen levels the touch type to navigate through them and to modify other para
308. h allow its use in a redundant CPU but it doesn t imply in configuration differences These commands normally must be executed in the NonSkippedPrg program E g a MODBUS RTU master driver in a RS 485 serial network must be disabled in a non Active CPU using the code inserted by the user in NonSkippedPrg More information regarding administration of MODBUS driver in a redundant system can be found in the MODBUS Instances Managing in Redundant System section In the case of PROFIBUS network there are also special different commands for the CPUs in Active and Non Active states In this case however the redundancy management executes such commands automatically without any user management To configure Profibus I O remotes including remotes and I O modules see NX5001 Modules Configuration section from this manual MainTask Configuration The configuration screen associated to the only task of a redundant CPU called MainTask which is cyclic can be accessed through a click on the MainTask in the Device Tree Two parameters must be adjusted on this screen e The MainTask cycle time e Watchdog time Furthermore the screen shows an estimative of the necessary time to manage the redundancy calculated by MasterTool Such estimative is only reliable after the project is complete with all POUs developed and redundant memory areas defined Several considerations must be taken in order to adjust correctly the MainTask cycle time e The c
309. he Ethernet ports NX3030 When enabled this option a code is generated automatically in NonSkippedPrg Program The code NonSkippedPrg program is as follows in ST language PROGRAM NonSkippedPrg VAR attribute symbol read OPCRedundancyActive BOOL END_ VAR IF fbRedundancyManagement m fbDiagnosticsLocal eRedState REDUNDANCY STATE ACTIVE THEN OPCRedundancyActive TRUE ELSE OPCRedundancyActive FALSE END IF The code in NonSkippedPrg program can be edited by taking care to keep the above code unchanged This code tests the state of redundancy and fills a variable of type BOOL called OPCRedundancy Active in view of this state If the PLC is the active one the variable value is TRUE otherwise FALSE This variable receives the attribute symbol read to allow the OPC Server to access its contents and set from which the information should be read If the user decides to add OPC communication option to an already existent project it can be configured by adding the above code in NonSkippedPrg program and adding the Symbol object configuration to the project 242 6 Redundancy with NX3030 CPU Redundant CPU States In a redundant system a CPU PLCA or PLCB may assume the following states Active Stand by Inactive Not Configured Starting ATTENTION Frequently this manual will use the designation Non Active for each state different from Active in othe
310. he MODBUS RTU Slave must address a subgroup of this mapping and this group must have at most the data size depending on the function code which is defined below Read coils FC 1 2000 Read input status FC 2 2000 Read holding registers FC 3 125 Read input registers FC 4 125 Write single coil FC 5 1 Write single holding register FC 6 1 Force multiple coils FC 15 1968 Write holding registers FC 16 123 Write register mask FC 22 1 Read Write holding registers FC 23 o Read 121 o Write 121 ATTENTION Differently from other application tasks when a depuration mark in the MainTask is reached the task of a Slave MODBUS RTU instance and any other MODBUS task will stop running at the moment that it tries to perform a writing in a memory area It occurs in order to keep the consistency of the memory areas data while a MainTask is not running 86 4 Configuration MODBUS Ethernet The multi master communication allows the Nexto CPUs to read or write MODBUS variables in other controllers or HMIs compatible with the MODBUS TCP protocol or MODBUS RTU via TCP The Nexto CPU can at the same time be client and server in the same communication network or even have more instances associated to the Ethernet interface It does not matter if they are MODBUS TCP or MODBUS RTU via TCP as described on Table 4 17 Figure 4 25 represents some of the communication possibilities using the MODBUS TCP protocol simultane
311. he Project Synchronization Disabling section The project synchronization is disabled in the local or remote PLC This way it s enough to execute the disabling command in one PLC for the project synchronization to be disabled The enabling and disabling project synchronization commands are described in the Project Synchronization Disabling section FALSE The project application and project archive will be synchronized between the PLCs TRUE Firmware version is incompatible between this CPU and the remote one FALSE Firmware version is compatible between this CPU and the remote one TRUE The project application between this CPU and the remote one is different FALSE The project application between this CPU and the remote one is equal TRUE The project archive between this CPU and the remote one is different FALSE The project archive between this CPU and the remote one is equal TRUE Some alteration was done online in the application and it hasn t been synchronized yet with the stand by PLC FALSE There wasn t alterations online in the 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 6 Redundancy with NX3030 CPU FALSE The NX4010 module is working properly TRUE This PLC can t communicate in the master state activ
312. he respective data structure RedCmdLoc fields and interconnect these commands if necessary e To manage switchovers controlled by the user in case of not vital failures such as the communication with a SCADA system or with a MODBUS device e Enable and disable some specific I O drivers depending on the redundancy state Active or Non Active E g a MODBUS RTU master driver in a RS 485 bus must be disabled in the Non Active CPU For further information see MODBUS Instances Managing in Redundant System section ATTENTION It s not recommended to use function blocks TOF RET TON RET TOF and TON in the NonSkippedPrg program See Limitations on a Redundant PLC Prog Redundancy Configuration Object This object located in the device tree is automatically created by the Wizard It is used to determine which POUs and GVLs are redundant and therefore synchronized between CPs By default POUs and GVLs created by the user are marked as redundant leaving the option to the user to reverse the marking when needed ATTENTION PV PIDControl and PidRetainGVL objects can t be individually marked In case of need to modification the Select All option must be marked GVL Diagnostics This special GVL is created and filled automatic by the Wizard and can t be modified by the user System diagnostics and commands including redundancy data structure RedDgnLoc RedDgnRem RedCmdLoc RedCmdRem are placed within direct representation spe
313. he user must cause a switchover between PLCs Active x Non Active in order to test the relay in both PLCs 297 6 Redundancy with NX3030 CPU When the PLC which was switched off is reactivated and restarted it returns with the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal off thus the test mode is canceled The DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal bit must be turned on again in this PLC and set it to Active state before testing its relay When the test mode is finished the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal command bit is automatically turned off in case the user has forgotten it on Suggested Sequence for PX2612 Test Executing The following sequence is suggested in order to execute the PX2612 tests Turn on the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal command bit in both PLCs PLCA and PLCB It must be observed if the 6 LEDs are blinking Press one at a time the 6 buttons and verify if the correspondent LED stops blinking and remain on while the button is pressed It must be remembered the button must remain pressed for at least one second before the LED stops blinking and remains on and that the LED returns to blinking after the button is released Turn on the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal command bit in the Active PLC It must be observed the Non Active PLC switching off Turn off the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal command bit in the Active PLC It must be
314. hen only changes in the application variables were done turning impossible the new project sending and updating on a CPU new cycle which is in run mode see Run Mode Therefore the MasterTool IEC XE requests whether the login must be executed as download and the CPU stopped see Stop Mode or the operation must be canceled PS The button Details presents the changes made in the application MasterTool IEC XE No online change possible due to severe changes Do you want to perform a download Figure 5 30 Variable Changes At the first time an application is sent to the CPU the message shown on Figure 5 31 will appear on the MasterTool IEC XE screen 208 5 Initial Programming MasterTool IEC XE Application Application does not exist on device Do you want to create it and proceed with download Figure 5 31 First Application Sending Run Mode Right after the project has been sent to the CPU the application will not be immediately executed only if an online online change transmission were made For that to happen the command Start must be selected This function allows the user to control the execution of the application sent to the 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
315. hich allows the disabling of the project application and project archive synchronization services This register can be adjusted using MasterTool It s enough to disable the project synchronization in one of the two CPUs to guarantee it doesn t work anymore 235 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 e Enable e Disable The option Disable must be selected and the combo box correspondent Write button pressed A message informs if the operation is successful or not The disabling configuration of project synchronism isn t part of the redundant project developed in the MasterTool Such configuration is only in a non volatile memory area in the CPU which can be read or written using MasterTool MasterTool doesn t save this configuration in any file This configuration is copied on each cycle of MainTask from the non volatile memory to the DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectS yncDisable The user can verify this diagnostics in the PLC to see if the command succeeded since the PLC is in Run mode DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectSyncD
316. hich can be used off line with no need of supervisory or programming software making easier to find and solve quickly possible problems The diagnostics key is placed on the CPU upper part in an easy access place and besides giving active diagnostics allows the access to the navigation menu described in the CPU s Informative and Configuration Menu chapter Figure 7 1 shows the CPU switch placement 299 7 Maintenance DIAGNOSTIC SWITCH 11052005A 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 This process is executed twice on the display Everything occurs automatically as the user only has to execute the first short touch and the CPU is responsible to show the diagnostics The diagnostics of other modules present on the bus are also shown on the CPU graphic display by a short press in the diagnostic module button in the same presentation model of diagnostics Figure 7 2 shows the process starting with the short touch with the conditions and the CPU times presented in smaller rectangles It is important to stress the diagnost
317. hich will execute the command to put the local Half Cluster in Stand By var_StandBy_command_Serial_relation Bool type variable attributed to a Serial communication Coil which will execute the command to put the local Half Cluster in Stand By DG_NX4010 tRedundancy RedCmdLoc bStandbyLocal this command executes an action similar to the button STAND BY from the PX2612 in the local PLC var_Inactive_command_Ethernet_relation Bool type variable attributed to an Ethernet communication Coil which will execute the command to put the local Half Cluster in Inactive var_Inactive_command_Serial_relation Bool type variable attributed to a Serial communication Coil which will execute the command to put the local Half Cluster in Inactive DG_NX4010 tRedundancy RedCmdLoc bInactiveLocal this command executes an action similar to the button INACTIVE from the PX2612 in the local PLC var_TurnOn_command_Ethernet_relation Bool type variable attributed to an Ethernet communication Coil which will execute the command to reactivate the local Half Cluster after switched off by the PX2612 relay var_Turn_command_Serial_relation Bool type variable attributed to a Serial communication Coil which will execute the command to reactivate the local Half Cluster after switched off by the PX2612 relay DG_NX4010 tRedundancy RedCmdLoc bTurnOnLocal this command executes an action similar to the button STAND BY from the PX2612 in the local PLC Diagnostics Comman
318. iable Allocation Further information regarding the size and type of memory allocated for each module can be found in the PROFIBUS DP NX5001 Master Utilization Manual After executing the planning for the 3 areas initial and final address of each area the initial addresses must be inserted in the projected started in step 2 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 Second the first network I O module must be found starting with the NX5001 which allocate I variables for inputs At finding it the correspondent Address parameter must be altered Third the first network I O module must be found starting with the NX5001 which allocate Q variables for outputs At finding it the correspondent Address parameter must be altered ATTENTION At this moment it s recommended to verify the allocated address range for the 3 variable areas verifying if the final addresses of each area are within the planned range and if there s a good free area for expansion for new future remotes insertion 278 6 Redundancy with NX3030 CPU Previous Planning for Other Hot Modifications There are other hot modifications which though they don t affect the PROFIBUS network also demand off line downloading Next it s presented some
319. iagnostics Redundancy Diagnostics Structure or the diagnostics from a PROFIBUS remote presents also non redundant diagnostics diagnostics from the modules NX5000 NX5001 NX3030 etc These non redundant diagnostics could be invalid and must not be considered at the first instants in Active state until they have valid values Typically the time during which the diagnostics should not be considered is 5 s The example below shows how to not consider the diagnostics bSlaveNotPresent and bPbusCommFail from the NX5000 PROFIBUS Master module Logic in NonSkippedPrg PROGRAM NonSkippedPrg VAR TON DiagEnable TON NR bDiagEnable BOOL bIsActiveState BOOL bIsActiveState_ old BOOL END_ VAR bIsActiveState DG _NX4010 tRedundancy RedDgnLoc sGeneral Diag eRedState REDUNDANCY STATE ACTIVE TON DiagEnable IN bIsActiveState bIsActiveState old PT T 5S Q gt bDiagEnable bIsActiveState old bIsActiveState Logic in ActivePrg IF NonSkippedPrg bDiagEnable THEN IF DG _NX5001 tGeneral bSlaveNotPresent OR DG _NX5001 tGeneral bPbusCommFail THEN Actions executed when the diagnostics are active END IF END IF 269 6 Redundancy with NX3030 CPU 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 do
320. ial 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 19 Neto 5 J Device Nx3010 5 PLC Logic application B Bill of Materials F Configuration and Consumption 3 Diagnostic Explorer Diagnostics i Library Manager E MainPrg PRG Task Configuration mainTask a Configuration Bus 5 f nxso10 NX3010 E Seda Yi N Copy Paste Delete Properties Add Object a Add Folder O Edit Object Edit Object With Simulation L Figure 5 19 Adding an Instance After that the available protocols for the user will appear on the screen Define the protocol configuration mode selecting MODBUS Symbol RTU Slave for symbolic mapping setting or MODBUS RTU Slave for direct addressing Q and click on Add Device as depicted on Figure 5 20 201 5 Initial Programming Append device Insertdevice Plug device Update device Device Vendor l lt All vendors gt Name mopsus J movsus Serial J MODBUS Master J MODBUSRTU Master WAA MODBUS Symbol RTU Master Altus S A f MODBUS Slave J MODBUSRTU Slave WAA MODBUS Symbol RTU Slave Altus S A E Display outdated versions Information
321. icatedRacks that morethan ons racic with the same identification number Each bit presents a rack identification Rack dwNonDeclaredRac number if the bit is TRUE it means O O 9 3 LAD n514 ee ODN SOL ks there is a rack configured with a non declared identification number QW n 518 QW n 678 QW n 678 Rack wReserved_0 Applicationinfo 32 bits CRC of Application When the QD n 520 QD n 681 QD n 681 has eaer che application is modified and sent to PP the CPU a new CRC is generated Table 7 7 Description of Detailed Diagnostics Notes Diagnostic Structures Visualization The Diagnostics Structures added to the project can be viewed by accessing the item Library Manager in the tree view window MasterTool IEC XE This makes it possible to visualize all the data types defined in the structure Counters All counters of the CPU diagnostics return to zero when the limit value is exceeded 6699 Direct Representation Variables The n represents the value configured in the CPU through the MasterTool IEC XE software as initial diagnostic address AT Directive In the description of the symbolic variables which use AT directive in order to do the mapping in direct addressing variables the syntax which must be put before the desired summarized diagnostic is DG_Module tSummarized when the Module word is replaced by the used CPU For example just use the variable DG_NX3010 tSummarized bConfigMismatch fo
322. ics may have more than one screen in other words the specified time in the block diagram below is valid for one of them 300 7 Maintenance LEVEL 1 Short Press STATUS SCREEN DIAGNOSTIC 1 DIAGNOSTIC N 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 Table 7 1 shows the difference between the short touch time the long touch time and stuck button Touch type Minimum time Maximum time __ Indication condition Notouch asm P y Short touch Long touch More than 1s till 20 s Locked Switch 20 01 s Diagnostics eyes see on Table Table 7 1 One Touch Time The messages presented on the Nexto CPU graphic display correspondent to the diagnostics are described in the Diagnostics via Variables section on Table 7 6 and Table 7 7 If any situation of stuck button occur in one of the I O modules the diagnostic button of this module will stop of indicate the diagnostics on CPU graphic display when is pressed In this case the CPU 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 th
323. ill 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 If necessary the user can create other folders in the root directory or subfolders inside the InternalMemory folder The memorycard folder is the directory where the memory card is mounted if it is inserted into the CPU Files which are transferred to the memorycard are being transferred directly into the memory card ATTENTION In the case where the memory card is inserted after the CPU startup an username and password will be requested to perform the MasterTool IEC XE access and or file transfers to the memory card or vice versa The standard user with privileges to access the CPU is Owner and the default password for that user is Owner In order to perform a file transfer from the microcomputer to the CPU just select the desired file in the left column and press the gt gt key located in the center of the screen as shown in Figure 4 46 The download time will vary depending on file size and cycle time execution of the current application of the CPU and may take several minutes The user does not need to be in Run Mode or connected to the CPU to perform the transfers since it has the ability to connect automatically when the user performs the transfer 122
324. ill suffer discontinuities output deactivation when the off line download is executed Next the planning steps that must start at the creation of a new redundant PROFIBUS network are described Step 1 Plan Future Expansion of the Remotes Inserted in the PROFIBUS Network Initial Version At first a list must be made of the I O modules which compose each redundant PROFIBUS remote from the Ponto Series in the PROFIBUS network initial version The list must have the position where each I O module is inserted in the remote rack Next the future expansion of each remote must be planned For that a complementary list must be made consisting in I O modules which might be inserted in the future In it the position where each T O module might be inserted in the remote rack must be listed 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 In case this detail isn t observed it will be necessary to switch off the specific remote as it s not possible a base hot insertion in the remote It can be observed that the remote stopping in some cases can be tolerable but not always 276 6 Redundancy with NX3030 CPU ATTENTION The original I O module bases must be
325. ilure Supplying failure Power supply CPU stop in the MainTask execution NX4010 Failure in both synchronism channels NETA and NETB and the cause isn t in the Reserve CPU In this case the Reserve CPU besides assuming the Active state switches the other CPU off Failure of some synchronism channel NETA and NETB and the cause is in the Active CPU Failure in some vital PROFIBUS network Commands via redundancy control panel PX2612 Commands received from MasterT ool or from a SCADA system through this CPU local or the other CPU remote Commands generated by user application e g in case of other diagnostics as Ethernet communication failure through this CPU local or the other CPU remote Supplying failure Power supply CPU stop in the MainTask execution NX4010 Failure in both synchronism channels NETA and NETB and the cause is in the Reserve CPU Failure in the synchronism service for redundancy data Failure in the synchronism service for the redundant forcing list Total failure in some vital PROFIBUS network Different project from the Active CPU with project automatic synchronization enabled Firmware version incompatible with the Active CPU Commands via redundancy control panel PX2612 Commands received from MasterTool or from a SCADA system through this CPU local or the other CPU remote Commands generated by user applica
326. ime equal to the configured polling and after will be performed a new communication as soon as possible Mapping Diagnostic Area this field is limited by the size of output variables addressable memory Q at CPU which can be found in the chapter Technical Description The configured MODBUS relations diagnostics are described in Table 4 27 Reading Writing Data Size details of the data size supported by each function are described in the notes of the section Configuration of the Relations Symbolic Mapping Setting IEC Reading Variable if the MODBUS data type is Coil or Input Status 1 bit the initial address of the IEC reading variables will have the format IX10 1 for example However if the MODBUS data type is Holding Register or Input Register 16 bit the initial address of the IEC reading variables will be IW This field is limited by the size of input variables addressable memory at CPU which can be found in the chapter Technical Description IEC Writing Variable if the MODBUS data type is Coil the initial address of the IEC writing variables will have the format QX10 1 for example However if the MODBUS data type is Holding Register 16 bit the initial address of the IEC writing variables will be 7QW This field is limited by the size of output variables addressable memory Q at CPU which can be found in the chapter Technical Description Writing Mask the function Write Mask FC 22 employs a logic between the
327. ime out while waiting for the transmission TATIME OY TERROR ending in the SERIAL_TX block Time out while waiting for all characters in RX_TIME OUT_ERROR the SERIAL_RX block or the SERIAL_RX_EXTENDED block The SET_CTRL block can t be used in case FB_SET_CTRL_NOT_ALLOWED the handshake is different from R232_MANUAL The GET_CTRL block can t be used in case FB_GET_CTRL_NOT_ALLOWED the handshake is different from R232_MANUAL The SERIAL_RX isn t available for the RX FB_SERIAL_RX_NOT_ALLOWED queue extended mode FB_SERIAL_RX_ EXTENDED NOT ALLOWED The SERIAL_RxX isn t available for the RX queue normal mode The interruption by the DCD signal can t be DCD_INTERRUPT_NOT_ALLOWED enabled in case the serial port doesn t have the respective pin The interruption by the CTS signal can t be enabled in case the handshake is different from R232_MANUAL or in case the serial port doesn t have the respective pin CTS_INTERRUPT_NOT_ALLOWED The interruption by the DSR signal can t be DSR_INTERRUPT_NOT_ALLOWED enabled in case the serial port doesn t have the respective pin NOT_CONFIGURED The function block can t be used before the serial port configuration STOPBITS_1 TRF SERIAL_STOPBITS List all stop bits possibilities STOPBITS_2 132 4 Configuration Ooo STOPBITS_1_5 re Table 4 77 Serial Function Blocks Data types SERIAL_CFG This function block is used to configure and initialize the d
328. in Active state e This CPU can t control all PROFIBUS networks configured in vital fail mode and knows the other CPU is in Stand by state This condition isn t analyzed in the first 2 seconds in Active state e This CPU detected a total failure in Ethernet networks configured in vital failure mode and knows that the other CPU is in Stand by state Transition 9 Active to Stand by e Both PLCs for some reason are in Active state and this conflict must be solved The PLCA switches to Stand by state in case this conflict remains The PLCB does the same after a delay smaller than PLCA This way in this case PLCA has priority to remain in Active state e The STAND BY button was pressed and this CPU knows the other CPU is in Stand by state This condition isn t analyzed in the first 2 seconds in Active state Transition 10 Stand by to Not Configured e This PLC was switched off or restarted warm reset cold reset or origin reset e The other PLC is in Active state and it s known this PLC project is different from the Active PLC Besides going to the Not Configured state a configuration request is made This way after the projects synchronization the PLC goes automatically from the Not Configured state to the Starting state This condition isn t analyzed if the project automatic synchronization is disabled Project Synchronization Disabling section e The other PLC is in Active state and firmware version of this PLC is incom
329. in the format QX10 1 However if the MODBUS data type is Holding Register or Input Register 16 bit the IEC variables initial address will be in the format QW This field is limited by the memory size of the addressable output variables Q from each CPU which can be seen on Technical Description Specific Features chapter 101 4 Configuration Write Mask of IEC Variables the Register Write Mask function FC 22 employs a logic between the value already written and the two words that are configured in this field using QW O for the AND mask and QW 2 for the OR mask allowing the user to handle the word This field is limited by the size of output variables addressable memory Q of each CPU which can be found in the chapter Technical Description Specific Features Factory default Factory default cannot be set for the fields of Mapping Diagnostics Area Variable IEC Variable in reading writing and writing Mask of IEC Variables because the creation of a relationship can be performed at any time on application development making the software itself MasterTool IEC XE allocate a value the range of output variables of direct representation Q still unused Factory default cannot be set to the size of the data fields of reading and writing data Size as they will vary according to the MODBUS data type selected Default Value the factory default value cannot be set for the Mapping Diagnostic Area IEC Read Variable IEC Write V
330. ing executed at the moment it tries to write in the memory area This occurs in order to maintain data consistency of memory areas while MainTask is not running MODBUS Ethernet Client configuration via Direct Representation Q To configure this protocol using direct representation Q the user must perform the following steps e Configure the general parameters of MODBUS protocol client such as protocol and direct representation variables Q to receive diagnostics e The descriptions of each configuration are listed below in this chapter e Add and configure devices by setting address direct representation variables Q to disable the relations and communication port e 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 The descriptions of each configuration are listed below in this chapter General parameters of MODBUS Protocol Client configuration for Direct Representation Q The General parameters found on the home screen of MODBUS protocol configuration Figure 4 30 are defined below D O l O OOOO Bile Edit Vew project Buld Onine Debug Tools Window Help Bsa ET Devices ax i Configuration Bus J MODBUS_Client x x MustufF Lm Mopgus Client Configuration 3 fj Device Nx3030 Client Settings 5
331. ings Destination location C Program Files Altus MT8500 Start Menu folder MasterTool IEC XE Additional tasks Additional icons Create a desktop icon Figure 3 19 Installation Review Screen Initially it is necessary to install the software prerequisites packages like Microsoft NET Framework 9 Setup MasterTool IEC XE Preparing to Install Setup is preparing to install MasterTool IEC XE on your computer Installing prerequisites Installing Microsoft Net Framework 4 Full Figure 3 20 Software Prerequisites Packages Installation 35 3 Installation A screen will appear during installation to extract the files from the Microsoft NET Framework Extracting files exa Preparing C ee850f5224d29742e83ad3e91d3e20 netfx_Core mzz Figure 3 21 Installation Process Next the Microsoft NET Framework Installation will be initiated Microsoft NET Framework 4 Setup Ex Installation Progress TATA Please wait while the NET Framework is being installed Microsoft File security verification All files were verified successfully a e D Installation progress Installing NET Framework 4 Extended Figure 3 22 NET Framework Package Installation At this step the MasterTool IEC XE installation has begun and the necessary files are being installed in your PC This operation can take a few minutes depending on your PC configuration 36 3 Installation j5 Setup M
332. interrupted by the user through command bits Discontinued diagnosis Discontinued diagnosis l QX n 3 bConfigFailure bRXFailure bTXFailure Discontinued diagnosis Indicates if there is failure in the module or the module is not present bModuleFailure bDiag_7_reserved Error Codes 0 there are no errors 1 invalid serial port 2 invalid serial port mode 3 invalid baud rate 4 invalid data bits 5 invalid parity 6 invalid stop bits 7 invalid modem signal parameter 8 p 9 invalid UART RX Threshold rameter invalid time out parameter 10 busy serial port 11 UART hardware error 12 remote hardware error 20 invalid transmission buffer size 21 invalid signal modem method SERIAL_STATUS 22 CTS time out true BYTE 23 CTS time out false 24 transmission time out error 30 invalid reception buffer size QB n 1 eErrorCode 31 reception time out error 32 flow control configured differently from manual 33 invalid flow control for the configured serial port 34 data reception not allowed in normal mode 35 data reception not allowed in extended mode 36 DCD interruption not allowed 37 CTS interruption not allowed 38 DSR interruption not allowed 39 serial port not configured 50 internal error in the serial port Command bits automatically initialized QX n 2 0 bStop BIT Stop master QX n 2 1 bRestart BIT Restart master QX n 2 2 tCommand Restar
333. ion is performed the updated time in the client may be up to 100 ms early or late in relation to the server The CPU sends the cyclic synchronization requests according to the time set in the SNTP Synchronization Period field In the first synchronization attempt just after the service start up the request is for the first server set in the first server IP address In case it does not respond the requests are directed to the second server set in the second server IP address providing a redundancy of SNTP servers In case the second server does not respond either the same process of synchronization attempt is performed again but only after the Period of Synchronization having been passed In other words at every synchronization period the CPU tries to connect once in each server it tries the second server in case the first one does not respond The waiting time for a response from the SNTP server is defined by default in 5 s and it cannot be modified If after a synchronization the difference between the current time of the CPU and the one received by the server is higher than the value set in the Minimum Error Before Clock Update parameter the CPU time is updated As the SNTP uses the time in the UTC Universal Time Coordinated format the Time zone parameter needs to be set correctly so the time read by the SNTP will be properly converted to a local time The execution process of the SNTP client can be exemplified with the following steps
334. ion mode Run Mode There are two ways to configure this protocol The first one makes use of direct representation Q in which the variables are defined by your address The second one through symbolic mapping where the variables are defined by your name 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 MU299048 or in the chapter Inserting a Protocol Instance The remaining configuration steps are described below for each mode e Add the MODBUS RTU slave Protocol instance to the serial channel COM 1 or COM 2 or both in cases of two communication networks e To execute this procedure see Initial Programming chapter e Configure the serial interface choosing the communication speed the RTS CTS signals behavior the parity the stop bits channel among others e See Serial Interfaces Configuration section MODBUS Slave Protocol Configuration via Symbolic Mapping To configure this protocol using symbolic mapping you must perform the following steps e Configure the MODBUS slave protocol general parameters as slave address and communication times available at the Slave advanced configurations button e Add and configure MODBUS relations specifying the variable name MODBUS data type and data initial address Automatically the data size a
335. ion of a single programming unit POU called MainPrg This program and this task are similar to the only task and only program of the Single profile but here the application can integrate additional user tasks This other tasks are called CyclicTask00 CyclicTask01 etc each one responsible for the execution of the respective program CyclicPrg lt nn gt The CyclicPrg lt nn gt tasks are always from the Cyclic type with priority fixed in 13 equal to MainTask These two types form a group called basic tasks which the associated programs can call other POUs from the Program function or Function Block types Furthermore this profile can include event tasks with higher priority than the basic tasks which can preempt these tasks execution at any time The task called ExternInterruptTask00 is an event task from the type Extern which the execution is triggered by some external event as control signal variation on a serial port or a digital input variation on the Nexto bus This task priority is fixed in 02 and it is responsible exclusively for the execution of the ExternInterruptPrg00 program The task called TimelInterruptTask00 is an event task from the cyclic type with priority fixed in 01 and it is responsible for the execution exclusively of the TimeInterruptPrg00 program In the Normal project model there are five tasks already completely defined as shown on Table 5 5 The developer needs to create the associated programs choosing any language f
336. ion will have the same effect as a download in the Non Active CPU This service isn t executed if the automatic Project Synchronization Disabling as it s described on Project section No synchronization service between CPUA and CPUB works in case the synchronism channels cables are inverted E g to connect the NETA channel in the NETB channel from CPUB and the NETB from the CPUA in the NETA in the CPUB ATTENTION In the update from the version 1 20 to later versions of MasterTool IEC XE was done a modification in the communication protocol between the synchronism channels Therefore is not possible to sync data between two PLCs when one of the applications has been created in a version prior to 1 21 and another application has been created in an equal or higher version To be able to perform the synchronization you should perform the actions described at section Not Loading the Application at Startup in the PLC with the oldest project Doing this the application will not be loaded but when this PLC goes to Non Configured state during the system initialization the applications will be synchronized automatically ATTENTION Before version 2 01 of MasterTool IEC XE when sending the source code to the active CPU the Stand by CPU went for Non Configured state to sync it However to complete the synchronization operation the CPU remained in the state Non Configured being necessary to pass the CPU to Stand by status via STAND BY button on
337. ion window will appear on the screen where the user must put the POU name and select the language type to be implemented Then the button Open must be clicked AddPOU Or i Create a new POU Program Organization Unit Name NextoPOU Type Program _ Function Block Extends Implements Structured Text ST Function Implementation language Structured Text ST Figure 5 9 POU Classification For a POU editing the tab with the correspondent name must be selected and the application development in the chosen language started The same procedure is valid for the POUs created automatically by the project profile 192 5 Initial Programming fe Start Page E Configuration Bus B MainPrg 1 PROGRAM MainPrg S 2 VAR 3 iVar_0 INT iVar_1 INT 4 x bVar BOOL war WORD END_VAR gt ange E enxe L i l IF bVar TRUE THEN war wartl iVar_0 iVar_1 END_IF m m Figure 5 10 POU Editing Creating Tasks For a POU to be executed it must be connected to a task This scaling mechanism called task is very useful for real time systems which are defined by the periodic execution or under request of an event change of state of any Boolean variable The tasks control the program execution in different rates according to the application features The need to execute programs in different rates has the goal to reach the deman
338. isable must be 1 In case the PLC isn t in Run mode it s possible to verify configuration straight on the NX3030 CPU display in the PLC see Redundancy Diagnostics on the NX3030 CPU Graphic Display section The DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectSyncDisable diagnostic can also be observed also in the remote PCL through the DG_NX4010 tRedundancy RedDgnRem sGeneral_Diag bProjectSyncDisable since the Non Active PLC is in Run mode A PLC Active or Non Active stops the project synchronization service every time any of the following bits are true e DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectSyncDisable o This PLC local bit This PLC is with the project synchronization disabled e DG_NX4010 tRedundancy RedDgnRem sGeneral_Diag bProjectSyncDisable o The other PLC remote bit The remote PLC is with the project synchronization disabled ATTENTION The Project Synchronization Disabling register isn t part from the redundant CPU project thus it s not saved as part of it in the computer where MasterTool is being executed The register is saved only in the nonvolatile CPU memory PROFIBUS Network Configuration It s possible to install up to 4 PROFIBUS Master NX5001 modules in each half cluster So we can define up to two redundant PROFIBUS networks called PROFIBUS 1 and PROFIBUS 2 or up to four simple PROFIBUS networks called PROFIBUS 1 PROFIBUS 2 PROFIBUS 3 and PROFIBUS 4 PROFIBUS Redundancy
339. ithin milliseconds of accuracy It is described in the Table 4 72 C swum type Variable Description TENDED TE Table 4 72 EXTENDED_DATE_AND_TIME DAYS_OF_WEEK This structure is used to store the day of week Description 0 INVALID_DAY SUNDAY MONDAY DAYS_OF_WEEK ea WEDNESDAY THURSDAY SATURDAY Table 4 73 DAYS OF _ WEEK Structure 120 4 Configuration RTC_STATUS This enumerator is used to return the type of error in the RTC setting or reading and it is described in the Table 4 74 Enumerator Vale scription ERROR_WRITING_RTC 6 ERROR _ eae SYSTEM_TIME 7 Error in the update of the system s date and hour NTERNAL_ERAOR INVALID_TIME 9 Invalid date and hour INPUT_OUT_OF_RANGE Out of the limit of valid date and hour for the 10 system SNTP_NOT_ENABLE 11 Error generated when the SNTP service is not enabled and it is done an attempt for modifying the time zone Table 4 74 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 75 stucture Tye variable Description geal Seine ae mie Table 4 75 TIMEZONESETTINGS Note Function Blocks of Writing and Reading of Date and Hour different libraries of NextoStandard which have function blocks or functions that may perform access of reading and writing of date and hour in the system are no
340. itial Address of Diagnostics in Q field since the creation of a protocol instance can be made at any moment within the application development The MasterTool IEC XE software itself allocate a value from the range of direct representation output variables Q still unused The diagnostics and MODBUS commands are described in Table 4 41 Device Configuration Configuration via Direct Representation Q The configuration of client devices displayed in Figure 4 31 includes the following parameters Device Settings Name Destination IP 0 0 0 TCP Port 502 Mapping Disabling 8192 Used range QX8192 0 QX8195 7 Figure 4 31 Configuring MODBUS Client Configuration Factory default Options Instance Identifier according to Name of the instance MODBUS_Device IEC 61131 3 Destination IP IP addr f th rver 0 0 0 1 100 1 esiinatio agCTaSS O MA Seve See 255 255 254 the TCP Port TCP Port 2 to 2065534 Disabling of Initial address used to disable Mappings MODBUS relations oo 0102147483044 Table 4 50 Configuration of Client Devices 99 4 Configuration Notes Instance Name this field is the identifier of the device which is checked according to IEC 61131 3 i e does not allow spaces special characters and starting with numeral character It is limited to 24 characters TCP Port if there are multiple instances of the protocol added in a single Ethernet interface different TCP ports must be selected for ea
341. ity The applications can be created according the following profiles Single Basic Normal Expert Custom Machine For each profile defined for the RTS the MasterTool IEC XE can provide numerous compatible templates When the user selects a template as a model in project creation the new application will be developed as a specific profile adopting rules characteristics and standards defined by the profile associated with the template Each project profile defines standard names for the tasks and programs which are pre created by the project templates The developer is required to follow the nomenclature strictly for the tasks but can follow or not the suggested names for the respective programs For compatibility guarantee of a project being developed using a specific profile two approaches are used e MasterTool IEC XE allows the project creation only based on a template selected at the same time as the profile to be used e At the code generation the MasterTool IEC XE executes the verification of all defined rules for the user valid profile The next sections bring details regarding the features and patterns of each profile which increase gradually in complexity It is recommended the user to apply always the simplest profile that meets his application needs migrating to another profile more sophisticated only when the correspondent rules are bringing more problems than helping It is important to stress that the programming
342. iveCRC differences between the project archive of the 2 PLCs F This PLC firmware version used to verify the 9 3 The IEC Timer synchronization is necessary for the bump less operation of some function block as TON and TOF Through this diagnostic the IEC Timer from the Active PLC is received and QD n 27 dwlECTimer updated in the Non Active PLC since the Diagnostics and Commands Exchange service has been executed successfully The counting starts at 0 and is incremented up to 4294967295 After counting overflow restarts with 0 16 bits counter used as sequence auxiliary information in the Redundancy Event Log In the Active PLC it s incremented each MainTask cycle In the Non Active PLC receives a copy of QW n 31 wCycleCounter the value existent in the Active PLC since the Diagnostics and Commands Exchange service has been executed successfully The counting starts at 0 and is incremented up to 65535 After counting overflow restarts with 0 Table 6 6 Redundancy General Diagnostics Notes Diagnostics Structures Visualization The diagnostics structures added to the project can be visualized accessing the Library Manager from the tree view in the MasterTool IEC XE window With that it s possible to visualize all data types defined in the structure 6699 Direct Representation Variables The n represents the configured value in the NX4010 module through MasterTool IEC XE software as a Diagnostics Initia
343. ject development environment creation This procedure may take a few seconds Adding Modules By default the CPU and the hardware modules selected at the moment of project creation are already inserted in the system configuration The user must include the other modules if necessary then In case the tab Product Library is not available on the MasterTool IEC XE screen it must be included through menu View clicking on the item Product Library as shown on Figure 5 6 File Edit view Project Build Online Debug Te a GD Pous At o fh 4 Devices S Devices Alt 1 Netd Messages Alt 2 v Ca Element properties 7 2 Product Library 32 ToolBox Watch gt on Breakpoints Call Stack Cross Reference List nn Start Page 0 eaa FullScreen Ctrl Shift F 12 Figure 5 6 Library Visualization Then the module to be inserted in the project must be selected and dragged to the bus configuration area pressing the mouse left button 190 5 Initial Programming File Edit View Project Build Online Debug Tools Window Help fae ICJ a 8 19 ees a X f startpage E Configuration Bus Said Neto g T Digital 1 0 4 J Device Nx3010 PLC Logic Nx1001 Application 24 Vdc 16 DI Module Bill of Materials B Configuration and Consumption EH Diagnostic Explorer Diagnostics BD Library Manager E MainPrg PRG NX1005 24Vde 8 DO T
344. l This feature is extremely useful during maintenance and troubleshooting procedures DHW Double Hardware Width TM Nexto Series modules were designed to save space in user cabinets or machines For this reason Nexto Series delivers two different module widths Double Width two backplane rack slots are required and Single Width only one backplane rack slot is required This concept allows the use of compact I O modules with a high density of I O points along with complex modules such as CPUs fieldbus masters and power supply modules High speed CPU All Nexto Series CPUs were designed to provide an outstanding performance to the user allowing the coverage of a large range of applications requirements For example Nexto CPUs can execute a sum multiplication and subtraction instruction in less than 31 ns for integer type 1 Introduction values and in less than 68 ns for real type values Nexto CPUs are able to perform 1 000 PID loops in less than 5 ms ance iF Product Design Award 2012 Nexto Series was the winner of iF Product eure Design Award 2012 in industry skilled trades group This award is recognized internationally as a seal of quality and excellence considered I the Oscars of the design in Europe 1 Introduction 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
345. l Address in Q This definition is true for all diagnostics structure AT Directive The AT directive is a word reserved in the programming software which is connected to a variable address In case of a NX4010 module the DG_NX4010 variable is related to the module diagnostics initial address DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bExchangeSync When this diagnostic variable is with value FALSE is not possible to define the state of some other diagnostics such as bIncompatibleFirmware bApplicationProjectDiff and bProjectArchiveDiff There will not represent the correct value because they depend on the correct functioning of the communication between the two CPUs so that information can be correctly generated 290 6 Redundancy with NX3030 CPU The sNETA_ Diag substructure has the following fields for NETA synchronism channels diagnostics Direct Representation AT Variable Variable DG_NX4010 tRedundancy Re Description dDgnLoc sNETA_Diag TRUE The synchronism channel has some type of failure The 3 next diagnostics will bGeneralFailure indicate the specific failure FALSE The synchronism channel is working properly TRUE The detected failure has its cause within this PLC Such failures are treated in a binternalFailure special way FALSE The NX4010 module is working properly TRUE The AL 2319A cable is disconnected from the NX4010 module or broken in one of the 2 bLinkDownFailure PLCs
346. l address of each area it s important to reserve expansion for the device which allocates addresses immediately before the beginning of this area On the other hand at defining the final address of each area it s important to reserve expansion for this PROFIBUS network Next an example of such planning is shown for I variables area for inputs e PROFIBUS 1 network o IBO IB499 addresses allocated to already installed remotes o IB500 IB999 addresses allocated future remotes e PROFIBUS 2 network o IB1000 IB1499 addresses allocated to already installed remotes o I1B1500 IB1999 addresses allocated future remotes e Modbus TCP server o 1B2000 IB2999 addresses allocated to current mapping o 1B3000 IB3999 addresses allocated to future mapping For the two other areas output Q and diagnostic Q similar examples could be executed It s possible to predict the initially allocated and future expansion areas size using the following Table 6 5 which indicates the byte quantity allocated for the 3 phases for each module Module Inputs l bytes Output bytes Diagnostic Q bytes o xsoon d R S S fk Posossvs o o k Posos o o PO9999 2 bytes output PO9999 2 bytes input Table 6 5 I and Q variables allocation for PROFIBUS network modules Oo oe d o o Po x o 2 k e o aao ee oA gt oa o w Note Var
347. l 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 2 interface the cable AL 1763 identified terminals must be connected in the respective device terminals as shown on Table 3 10 po Stiett k PERM Ss TX SESS ESE Ee RX Table 3 10 COM 2 with RS 422 Connections with Internal Termination PS The internal termination available in COM 2 is secure state in open mode The Figure 3 9 diagram indicates how the AL 1763 connection terminals should be connected in the device terminals DEVICE NX3010 RS 422 NX3020 NX3030 AL 1763 11032105C Figure 3 9 COM 2 with RS 422 Connections with Termination Diagram Diagram Note The not connected terminal must be insulated so they do not make contact with each other RS 422 Communication with External Termination In order to connect in a RS 422 network using the COM 2 interface external termination the cable AL 1763 identified terminals must be connected in the respective device terminals as shown on Table 3 11 28 3 Installation AL 1763 Terminals CPU terminal signals Not connected ee ee Sas TH O Ee a ll PC Ee pO Notconnected E EE S Table 3 11 COM 2 with RS 422 Connections with External Termination The Figure 3 10 diagram indicates how the AL 1763 connection terminals should be connected
348. lane Rack Choose the power supply model nxeo00 Altus S A 30 W 24 Vdc Power Supply Module Choose the redundancy configuration Without Redundancy Figure 5 3 Hardware Modules Then the user must select the profile for the project and the standard language for POUs programs In this case the new project is exemplified as Single profile and ST language Click Next to continue or Cancel to abort the creation of the project 5 MasterTool Standard Project Choose the project profile configuration and the wizard will create the following objects within the project Choose the project profile Single Choose the default language for all programs Structured Text ST lt Previous Cancel Figure 5 4 Features Selection The next screen defines the POU language created by the selected profile As the profile is Single there is only one POU MainPrg and the ST language remains Click on Previous to return to the last screen Finish to end or Cancel to cancel 189 5 Initial Programming I a MasterTool Standard Project Se Al Choose the language and the wizard will create the following objects within the project Common Task Programs Preempt Free Tasks Program associated with Main Task MainPrg in Structured Text ST X Ca Cee Figure 5 5 Programming Language When the Finish button is pressed the MasterTool IEC XE will start the pro
349. lation configuration depicted on Figure 4 37 and Figure 4 38 follow the parameters described on Table 4 58 Coil Figure 4 37 MODBUS Data Type 108 4 Configuration Y MODBUS_Server_Mapping 000 Coil Mapping Settings Data Start Address Data Size h 8 Used range 1 8 IEC Variable 8196 Y Used range QX8196 0 QX8196 7 Read only Filters Cancel Figure 4 38 MODBUS Function Configuration Description Default Options Coil 1 bit i Holding Register 16 bits Data Type MODBUS data type Input Status 1 bit Input Register 16 bits Data Initial MODBUS data initial Address address 1 to 65536 1 to 65536 Holding Register Data Size MODBUS data quantity s o Status IEC Variable AE address 0 to 2147483647 Read only Allow reading only Disabled Enabled or Disabled Table 4 58 Server Mappings Notes Options the values written in the column Options may vary according with the configured MODBUS data Data Size the Data Size value sets the maximum amount of data that a MODBUS relation can access from the initial address Thus to read a continuous range of addresses it is necessary that all addresses are declared in a single relation This field varies according to the set MODBUS data type that is when selected Coil or Input Status the field data size must be a number multiple of 8 It is also important to take care so the maximum value is not g
350. le 4 88 SERIAL_RX Input Parameters 139 4 Configuration Output parameters BOOL This variable is true when the block is completely executed It is false otherwise EXEC BOOL ERROR BOOL STATUS SERIAL_STATUS RX_RECEIVED UINT Table 4 89 SERIAL_RX Output Parameters 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 is false otherwise It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR ILLEGAL_SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE ILLEGAL_RX_BUFF_LENGTH RX_TIME OUT_ERROR FB_SERIAL_RX_NOT_ALLOWED NOT_CONFIGURED Returns the received characters number This number can be within zero and the configured value in RX_BUFFER_LENGTH In case it is smaller an error will be indicated by the function block Returns the number of characters which are still in the RX queue after the function block execution Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Receive
351. ling time along with the user application Execution Time It is important to stress that the running MODBUS devices number also changes its performance In a user application with Execution Time of 60 ms and interval of 100 ms there are 40 ms left for the CPU to perform all tasks of lower priority Therefore a CPU with only one MODBUS Ethernet Server will have a higher performance than a CPU that uses four of these devices CPU s Local Interfaces For a device MODBUS Ethernet Server we can assert that the device is capable to answer an x number of requisitions per second Or in other words the Server is able to transfer n bytes per second depending on the size of each requisition As smaller is the cycle time of the MODBUS Server task higher is the impact of the number of connections in his answer rate However for cycle times smaller than 20 ms this impact is not linear and the Table 4 60 must be viewed for information The Table 4 60 exemplifies the number of requisitions that a MODBUS Server inserted in a local Ethernet interface is capable to answer according to the cycle time configured for the MODBUS task and the number of active connections Number of Active Connections Answered requisitions per second Answered requisitions per second with the MODBUS task cycle at 5 ms with the MODBUS task cycle at 20 ms 395 470 570 111 4 Configuration 605 640 665 10 Connections fe 0 2 Table 4 60 Communication Rate of
352. lly and will signalize the problem via diagnostics If there is no other abnormality for the declared modules the CPU will go to the normal state Run even if a non declared module is present on the bus ATTENTION In this configuration when a power fault occurs even temporally Reset Warm Command Reset Cold Command or a new application Download has been executed and if any module is in an abnormal bus situation the CPU will get into Stop Mode and the LED DG will start to blink 4x according to Table 4 3 This is considered a start situation This is the most advised option because guarantee the system integrity on its initialization and allows the modules change with a working system Hot Swap Enabled with Startup Consistency This setting checks whether there has been any abnormal situation in the bus as shown in Table 4 2 during the start even if there is no declared modules and present on the bus if so the CPU goes into 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 If a Reset Origin is done you need to download the project so that the CPU can return to normal Run The Reset commands Warm Cold and Reset Origin can be done by MasterTool IEC XE in the Communication menu Hot Swap Enabled without Consistency in the Start Allows the syste
353. local for instance through write commands from a SCADA system or generated in POUs in this PLC ActivePrg or NonSkippedPrg This section is described in Redundancy Commands o RedCmdRem It s a copy from the other PLC remote RedCmdLoc received through Synchronism channels NETA NETB This section is described in Redundancy Commands o RedUsrLoc Used to allow the user to exchange information between PLCA and PLCB This section is described in User Information Exchanged between PLCA and PLCB o RedUsrRem Used to allow the user to exchange information between PLCA and PLCB This section is described in User Information Exchanged between PLCA and PLCB It is important to stress that the redundancy diagnostics structures are refreshed only when occurs with success a new data synchronization Therefore until a new synchronization doesn t occur the diagnostics will remain with the last read value Furthermore the diagnostics structures from the remote PLC are read only that is values written to these structures will be overwritten in the next synchronization Thus is not possible to use the RedCmdRem structure to execute a command in the remote PLC Always use the structure RedCmdLoc to execute commands 285 6 Redundancy with NX3030 CPU Redundancy Diagnostics The Redundancy Diagnostics may have several uses such as e They can be consulted in order to verify the existence of a problem that needs to be solved e Every tim
354. lready fully defined as shown below Not necessary careful with the scheduling of tasks Task POU Priority Type Cycle Time Event MainTask MainPrg 13 Cyclic 100 ms Figure 6 18 Project profile and standard language To finish the user must select the program language common and associated to the redundancy Program associated to the MainTask MainPrg It must be obligatory in ST language as MasterTool disables the other options e Programs associated to the main redundancy tasks 257 6 Redundancy with NX3030 CPU MasterToo IEC XE Standa Choose the language and the wizard will create the following objects within the project Common Task Programs Preempt Free Tasks Programs associated with Main Task MainPrg in Structured Text ST Programs associated with redundancy Main Tasks NonSkippedPrg in Structured Text ST ActivePrg in Structured Text ST 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 The MainPrg POU will always be automatically generated in ST language and cannot be changed by the user This POU calls the ActivePrg only in the Active PLC and NonSkippedPrg in both
355. ls RTS and DTR when they are available in the serial port It can also set a busy condition for the transmission through BREAK parameter and it can only be used if the modem signal is configured for RS232_MANUAL SERIAL_SET_CTRL Figure 4 59 Block for Control Signals Writing 142 4 Configuration Input parameters REQUEST BOOL This variable when true enables the function 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 DTR_VALUE BOOL Value to be written on DTR signal DTR_EN BOOL Enables the DTS_VALUE parameter writing BREAK BOOL In case it s true enables logic 0 busy in the transmission line Table 4 92 SERIAL_SET_CTRL Input Parameters Output parameters BOOL This variable is true when the block is 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 It is false ERROR BOOL otherwise It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR STATUS SERIAL_STATUS ILLEGAL
356. lse BOOL f 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 It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR STATUS SERIAL_STATUS ILLEGAL_SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE NOT_CONFIGURED SERIAL_PARAME This structure receives the serial port configuration parameters as described PARAMETERS TERS in the SERIAL_PARAMETERS data type 134 4 Configuration Table 4 81 SERIAL_GET_CFG Output Parameters Utilization example in ST language after the library is inserted in the project PROGRAM MainPrg VAR GetConfig SERIAL GET CFG Port SERIAL PORT COM1 Parameters SERIAL PARAMETERS Status SERIAL STATUS END_ VAR INPUTS GetConfig REQUEST TRUI GetConfig PORT Port EUNCTION GetConfig OUTPUTS GetConfig DONE GetConfig EXEC GetConfig ERROR Status GetConfig STATUS If it s necessary to treat the error Parameters GetConfig PARAMETERS Receive the parameters of desired serial port Di
357. m It is recommended to format the memory card using the Nexto CPU otherwise it may result in performance loss in the memory card interface 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 1 2 0 9 or lower 1 00 to 1 28 1 2 1 0 to 1 2 4 0 1 29 to 1 40 Table 2 12 Compatibility with other products Note Compatibility between versions some features are available only from a particular version To further information see the Manual section to verify the availability of some characteristic in a specific product version 15 2 Technical Description Performance The Nexto Series CPU performance relies on User Application Time Application Interval Operational System Time Module quantity process data input output among others Application Times The execution time of Nexto CPUs application depends on the following variables e Input read time local and remote e Tasks execution time e Output write time local and remote It is important to stress that the execution time of the Main Task will be directly influenced by the Configuration system task a task of high priority executed periodically by the system The Configuration task may interrupt the Main Task and
358. m to start working even if a module is in an abnormal bus situation as described on Table 4 2 The abnormal situations are reported via diagnostics during and after the start ATTENTION This option is advised for the system implementation phase as it allows the loading of new applications and the power off without the presence of all configured modules 42 4 Configuration How to do the Hot Swap CAUTION Before performing the Hot Swap it is important to discharge any possible static energy accumulated in the body For that touch with bare hands on any metallic grounded surface before handling the modules Such procedure guaranties that the module static energy limits are not exceeded ATTENTION It is recommended the hot swapping diagnostics monitoring in the application control developed by the user in order to guarantee the value returned by the module is validated before being used The hot swap proceeding is described below Unlock the module from the backplane rack using the safety lock Take off the module pulling firmly Insert the new module in the backplane rack Certify the safety lock is completely connected If necessary push the module harder towards to the backplane rack In case of output modules is convenient the points to be disconnected when in the changing process in order to reduce the generation of arcs in module connector This must be done by switching off the power supply or by forcing the
359. me gt pplication Layer Maximum number of octets Transmitted in an Application Layer Fragment Fixed at 2048 Maximum number of octets that can be received in an Application Layer Fragment Fixed at 2048 Timeout waiting for Application Confirm of solicited response message Fixed at 10000 ms Device Trouble Bit IIN1 6 This bit will be set if PLC is not in Run mode Event Buffer Overflow Behavior Discard the oldest event Sends Multi Fragment Responses Yes Outstation Unsolicited Response Support Supports Unsolicited Reporting No 328 Annex A DNP3 Interoperability DNP V3 0 Implementation Table DNP OBJECT GROUP amp VARIATION REQUEST RESPONSE Master may issue Master must parse Outstation must parse Outstation may issue Group Var Description Function Qualifier Function Qualifier Num Num Codes Codes Codes Codes dec hex dec hex 1 0 Binary Input Any 1 read 00 01 start Variation stop 06 no range or all 1 1 Binary Input Packed 1 read 00 01 start 129 00 01 format stop response start stop 06 no range or all 2 0 Binary Input Event Any 1 read 06 no range Variation or all 07 08 limited qty 2 2 Binary Input Event With 1 read 06 no range 129 17 28 absolute time or all response index 07 08 limited qty 60 1 Class Objects Class 0 1 read 06 no range dat
360. meters as language and the Memory Card using the same access logic The short touch shows the contrast is being incremented clearer and in the next touch after its maximum value it returns to the minimum OO O20 Oo 128 4 Configuration value less clear The long touch shows the confirmation of the desired contrast and its return to the previous level LEVEL 1 Short Press STATUS SCREEN gt NETWORK Short LEVEL 2 Press Long Press HARDWARE gt TEMPERATURE Shon LEVEL 3 Press Long Press CONTRAST Ss CONTRAST EDIT 000000 0000 Short Short Press Press DATE AND TIME Short Long Press Press SOFTWARE 4 RETURN Short Press LANGUAGES Short l Press CONTRAST EDIT 00 0000000 s y Figure 4 51 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 e Short touch at any moment in the other modules existent on the bus make the CPU disconnect from the menu and show the desired module diagnostic e Idle time at any level superior to 5 s 129 4 Configuration Function Blocks and Functions Special Function Blocks for Serial Interfaces The special function blocks for serial interfaces make possible the local access COM1 AND COM2 and also access to remote serial ports expansion modules Therefore the user can crea
361. module positions 4 and 5 These modules must not be removed from the original project generated by the Wizard Any different configuration in these positions results in an error displayed by MasterTool at the project compilation Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 IP Address Configuration Figure 6 20 presents the CPU NX3030 NET 1 port configuration the screen for NET 2 port configuration has a subgroup of these parameters In order to open this screen a double click must be executed on NET 1 or NET 2 below the CPU NX3030 in the device tree f StartPage ff Configuration Bus fj NET1 Ethernet Port Parameters Cluster IP Addressing IP Address Active 192 168 15 1 IP Address PLC A 192 168 15 69 IP Address PLC B 192 168 15 70 Subnetwork Mask 255 255 255 0 Gateway Address 192 168 15 253 Advanced Figure 6 20 Ethernet NET 1 port parameters Next the basic parameters of the NET 1 and NET 2 interfaces must be edited The address has to be set according to the IP Active Change method as described in Active IP ATTENTION The NET 1 and NET 2 interfaces IP addresses as the Gateway Address must belong to the same subnet 259 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 configuratio
362. mplete the old username and password and the new username and password The other user information SNMPv3 cannot be changed To change the data of SNMPv1 v2c communities the process is similar just click the Change button below the information community A new screen will open where the new data to the rocommunity fields and rwcommunity will be inserted If you fail any of the fields blank their community will be disabled That way if the user leaves the two fields blank access to the SNMP agent will only be possible through SNMPv3 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 79 English Espa ol Portugu s 4 yin altus NEXTO SNMPv3 User Authentication Protocol MD5 Privacy Protocol Privacy Password Communities Change rocommunity public rwcommunity private Change Figure 4 79 SNMP status configuration screen ATTENTION If the displayed screens are different from displaying in the browser a browser cache cleanup is necessary ATTENTION The user and password to login on the website of SNMP settings and to access the agent via SNMP protocol are equal 165 4 Configuration User and SNMP Communities To access the SNMPv1 v2c of the Ne
363. n Therefore the memory card must be inserted following the depiction on the CPU frontal part or the way showed on Figure 3 12 10081212B Figure 3 12 Memory Card Insertion in the CPU When the card is correctly installed a symbol will appear on the CPU graphic display For card secure removing the MS key must be pressed then there is a little delay and the card symbol will disappear from the graphic display The card is now ready to be taken off For that the card must be pressed against the CPU until a click is heard then release it and withdraw it from the compartment as showed on Figure 3 13 At this moment the card will be loose 10081213B Figure 3 13 Memory Card Withdrawal 31 3 Installation Architecture Installation Module Installation on the Main Backplane Rack Nexto Series has an exclusive method for connecting and disconnecting modules on the bus which does not require much effort from the operator and guarantee the connection integrity For further information regarding Nexto Series products fixation please see Nexto Series User Manual MU214600 Programmer 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 Then close all programs that might have been executed in your PC and double click the installation file The following installation scre
364. n Ctrl Shift F12 Properties iJ Configuration Bus Figure 5 27 Including the Messages on the Screen After the application has been compiled and the errors found corrected the project must be sent to the CPU For that to be possible the operation Login in the MasterTool IEC XE software must be executed This operation may take a few seconds depending on the size of the generated file To execute the Login go to Online menu and click on the option Login as shown on Figure 5 28 Nexto project Master EO File Edit View Project Build online Debug Tools Window Help SrA IEI 3 Logn mara 9 mje Logout Ctrl F8 i Joje Create boot application irs Neto ogoff current online user a Device NX3010 P PLC Logic Application Ps B Bill of Materia B Configuration S Cluster Basic Configuration 4 Diagnostic Ex Diagnostics fi Library Manag old 2 MainPrg PRG R rigir Task Configu Simulation SB MainTask wT Figure 5 28 Sending the Project to the CPU After the command execution some user interface messages may appear which are presented due to differences between an old project and the new project been sent or simply because there was a variation in some variable Figure 5 29 shows the message the MasterTool IEC XE presents in case the new project which is being sent is different from the project already existent insid
365. n Failures which Cause Automatic Switchovers between Half Clusters 0 ee eeeeeeeeeeneees 250 Failures Associated to Switchovers between Half Clusters Managed by the User ee eeeeeeeeeeeees 251 PaultMolerance ss svc cc eves inssavtacestassiesseasceusrsceonestsenssusesenssis ssnessstcobassstconanuatssasas TAS 252 Redundancy Overhead cc iti when e anna an sake dade ied aaen ona 254 Redundant CPU Prosramiming j i277 05 2ce sescsescsssssesaeexssevascusenvassossevesssesevessoasesescvesssssasesssasssesssasasssssscsteevs 255 Wizard for a New Redundant Project Creation cc eeessecccesssececeesceeeeesnaeeeeessaeeeeesseeesessaeeesesaeees 255 Hali Clusters Conf Surdtion v v xceeae series eean aS E E EEE reset renee ee 259 Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 eee eeeesseeeeeesneeeeeenneeees 259 NX5001 Modules Configuration 0 0 0 0 eecsceeesssccccessseeeeeessaceccessececesseeeceessaeeesessaeeeeessaeesessaeessesaeees 261 NX5000 Modules Configtiration i cc tcesccctreseeetieesesencbis eei ee E Eeen Ee EEE eee e Eeee eiee a eese abies 263 NX4010 Redundancy Configuration seesesseseeeeessssssseeresssssssssreeesssssssereesssssssseeeeesssssssseeesssssssseees 264 VO Drivers Configurations a ie n ee ee se e 265 Main LASK Configuration iooni e EEE EEEE venient 265 Redundancy Configuration Object rororo iriiria a a E E EEE EEEE EE 267 CAVA DA 1a STOSTICS E AE EET A E S SS 267 GVLs with Redundant Symb
366. n blocked for edition Some network parameters are identical to the other network while others are calculated automatically from network parameters of the left NX5001 It s recommended for the configured address for a NX5001 master in a redundant PLC to be 2 as the master NX5001 address in the Non Active PLC is decremented one unit thus the NX5001 master address results 1 Besides that it s important to remember e The addresses from 3 to 125 are usually used for PROFIBUS slaves e The 0 addresses are frequently used for device configuration and diagnostics e The address 1 is reserved to be taken dynamically by the PROFIBUS master in the Non Active PLC PROFIBUS master in passive mode e The 126 address is frequently used for slave devices when comes from the manufacturer e The 127 address is used for broadcast frames In the next project compilation MasterTool check the possible errors the user may have made at inserting or removing NX5001 modules manually Important to note that during the execution of a project previously configured with redundant NX5001 modules bit 0 Command Channel Enable Interface QXn 0 at Bus tab I O Mapping is handled by the redundant application The interfaces must remain qualified throughout the program 262 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
367. n 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 In case the checkbox for Redundancy of Communication is marked the NET 1 and NET 2 interfaces form a redundant pair with NIC Teaming as described in the Redundant Ethernet Networks with NIC Teaming section Automatically other parameters are enabled and must be configured e Redundancy Test Period ms Period to transfer the communication test frame between the two NETs It can be configured with values between 100 and 9900 e Retries of Redundancy Test Maximum number of times the NET which has sent the frame will wait for an answer It can be configured with values between 1 and 100 e Switching Period s Maximum time the Active NET will wait for any package It can be configured with values between 1 and 25 Advanced Ethemet Settings x Redundancy of Communication Z Redundancy of Communication Period of Redundancy Test ms 500 Retries of Redundancy Test 4 Switching Period s 10 cna Figure 6 21 Ethernet advanced configuration In case the answer time for the Redundancy Test reaches the Test Period times the Number of Retries and the active interface remains for a while longer than the Switching Period without receiving any package a switchover will occur turning active the interface that was inactive It is important to s
368. n the maximum of 18 answers per second With more active connections the number of answers will increase linearly exactly like the local interfaces however being limited at the maximum of 90 answers per second So for a remote Ethernet interface we will have the following forms to calculate his performance For T lt 55 ms is used N C x 18 18 18 18 0 055 x 1000 And for T gt 55 ms is used N C x Z Z T x 1000 Where N is the medium number of answers per second C is the number of active connections and T is equal to the cycle time of the MODBUS task in seconds The user must pay attention to the fact that the maximum performance of a device MODBUS Server in one remote Ethernet interface is 90 answers of requisitions per second 112 4 Configuration Communication Rate of a Device with OPC Server To the communication performance tests with OPC server project were created and designs for the PLC declaring variables of type INT and separating them into POUs with 1 000 variables in each The exception was in the case of 2 000 variables where we used only a single POU In all scenarios the Single profile was used MainTask with execution time of 100 ms To realize the communication was used attribute symbol readwrite attribute in order to provide data in the OPC server In OPC Client point of view a driver was used in a SCADA system The time set update was 500 ms The performance results under these
369. n the input data are frozen Indicates that the devices can perform communication by transmitting receiving data in both directions simultaneously ie can transmit and receive at the same time Equipment for connecting two networks with different communication protocols Connector normally connected to the parallel interface of a PC in order to avoid the execution of software 324 8 Glossary Hardware Half cluster Half Duplex HSDN Hot swapping IEC IEC 61131 IEC 61131 3 Interface Interruption Interval 1 0 1 0 Modules I O Subsystem input output ISOL Kbytes LCD LED Logic MainPrg MainTask MasterTool IEC XE Master Master Slave Communication Network Menu Monomaster Module address Module referencing hardware Module referencing software Multicast Multimaster Multimaster Communication Network NET 1 and NET 2 NETA NETB Network Access illegal copies Physical equipments used in data processing where the programs software are executed Alternative name for each of the two controllers PLCB and PLCA that form a cluster Indicates that the devices can perform transmitting communications receiving data but only in one direction at a time or can transmit or receive data High Speed Deterministic Network Deterministic network often redundant used for exchanging interlocking messages between interlocking PLCs Procedure for replacement of system modules without the
370. nabled in a passive state The passive mode is used to test the transmission and reception PROFIBUS circuits and the physical layer to avoid an occult failure to happen Verify if the CPU identification is correct must be PLCA or PLCB Verify if there are problems in the configuration parameters extracted from MasterTool project Verify the NX4010 module integrity The cyclic synchronization services are executed see Cyclic Synchronization Services through NETA and NETB section if the conditions for its execution are true Verify the firmware compatibility version between both CPUs e Verify if the projects from both CPUs are equal if the project automatic synchronization is enabled see Project Synchronization Disabling section e Incase the other CPU is in Active state verify the possibility to establish a passive PROFIBUS communication with it The passive mode is used to test the transmission and reception PROFIBUS circuits and the physical layer to avoid an occult failure to happen e Incase the other CPU is in unknown state due to failures in NETA and NETB verify the possibility of establishing a passive PROFIBUS communication with it Depending on the results of these verifications and tests the CPU can go from the Starting state to any from the other 4 states Active State In this state the CPU controls the automated process using the ActivePrg program executed only in this state The Active CPU also updates the PROFIB
371. nal CPU Internal software is in normal execution state CPU Memory card interface is operational CONFIG COM 1 configuration has no error s CONFIG COM 2 configuration has no error s CONFIG NET 1 configuration has no errors Figure 7 6 System Status Besides the user can choose to visualize three language options Portuguese English and Spanish It is just to change the upper right menu for the desired language The correspondent Firmware 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 Diagnostic Explorer The Diagnostic Explorer is the inclusion of the diagnostics via WEB in the MasterTool IEC XE in order to make the process faster and direct The access to this feature happens in two ways Accessing the Diagnostic Explorer option in the device tree placed on the MasterTool IEC XE screen left and putting the correct IP in the field indicated on Figure 7 7 Remembering that for the diagnostics page to be shown the user must be connected to the CPU Login chapter WS Wate project MasterToal EC XE Sle ee Ble Edt Mew moet Bd Onine Debug Tools Window tep anaga o x E Steag il Configroton mus a Diagnostic Explorer x cE System
372. nd if the application has been modified so that persistent variables have been removed inserted into the top of the list or otherwise have had its modified type the value of these variables is lost when prompted by the tool MasterTool to download Thus it is recommended that changes to the persistent variables GVL only include adding new variables on the list Total redundant data memory Redundant data memory is the maximum memory area that can be used as redundant memory between two redundant CPUs This value is not a different memory note that the sum of all redundant variables addressable input variable addressable output variable addressable variable symbolic variable retain symbolic variable persistent symbolic variable must be less than or equal to the available redundant data memory Program memory Program memory is the maximum size that can be used to store the user application This area is shared with source code memory being the total area the sum of program memory and source code memory Source code memory backup This memory area is used as project backup If the user wants to import the project MasterTool IEC XE will get the information required in this area Care must be taken to ensure that the project saved as a backup is up to date to avoid the loss of critical information This area is shared with source code memory being the total area the sum of program memory and source code memory Us
373. nd range will be filled in accordance to the variable type declared MODBUS Slave Protocol General Parameters Configuration via Symbolic Mapping The general parameters found on the MODBUS protocol initial screen Figure 4 19 are defined as General Parameters g Settings Slave Address 1 Advanced Figure 4 19 MODBUS RTU Slave Configuration Screen Slave Address MODBUS slave address 1 to 255 Table 4 31 Slave Configurations The MODBUS slave protocol communication times found in the Advanced button on the configuration screen are divided in Task Cycle Send Delay and Minimum Interframe as shown in Figure 4 20 and in Table 4 32 79 4 Configuration 7 MODBUS Advanced Setti x Settings Task Cycle ms bo Send Delay ms 0 Minimum Interframe chars 3 5 ok Canc Figure 4 20 Modbus Slave Advanced Configurations Configuration Description Defaut Possibilities Time for the instance execution within the Task Cycle ms cycle without 50 20 to 100 considering its own execution time Transmission Delay for the Delay ms transmission response oe 0 to 65535 ini Minimum silence time Setar e chars between different 3 5 3 5 to 100 0 frames Table 4 32 Modbus Slave Advanced Configurations Notes Task Cycle the user will have to be careful when changing this parameter as it interferes directly in the answer time data volume for scan and mainly in the CPU resou
374. necessary that both fail for the system as a whole become unavailable e High diagnostics coverage especially in redundant components The component redundancy isn t very useful for the availability increase when is not possible to discover which component failed In this case the first failure in one component still doesn t drop the system but remains hidden until the second failure occurs dropping the system as the first failure wasn t yet repaired The failures can be classified between diagnosable and hidden It s strongly recommended that all redundant components failures are diagnosable e It s also important that non redundant components have wide diagnostics coverage as frequently the system can continue working even with a non redundant component failure The component may not being requested e g a relay with NO contact which rarely has its coil activated doesn t have its failure detected until the moment the system requires its closing e Low repair time for non redundant components A non redundant component failure can drop the system and during the repair the system will be unavailable e Possibility of repairing or substituting a redundant component without stopping the system If this possibility exists a great availability increase it got Otherwise a stop must be programmed in order to substitute the component and the repair time is computed as unavailable time e Low repair time for redundant components A re
375. nfiguration to a file In the new Nexto CPU or updated CPU run Disk Load command and select the previously generated file finally run the Download to the Device command thus sending the settings for the CPU ATTENTION If the old project is in its versions 1 3 xx or lower firmware before saving the configuration to a file create an user and a group with the name Administrator This ensures that the configuration will be loaded on projects with versions 1 4 xx or higher firmware Access Rights This dialogue is provided on Device dialog tab Device Editor It is part of the Online User Management and serves to grant and deny permissions to certain user group defined at the time thus determining the access rights to files and objects an application for example when the CPU is running Note that these permissions can only be assigned to groups and not to single users Therefore a user must be defined as a member of a group The configuration of users and groups is done in the device editor Users and Groups tab Figure 4 90 shows permission to add and remove to child nodes to CPU Logic object granted to the group Everyone and Owner users E Configuration Bus j Device x X Communication Settings Files Log Users and Groups Access Rights Information Upload from device Download to device G Load from disk ge Save to disk Actions Permissions QJ File system objects Grant Deny Clear 0 Runtime objects Devi
376. nfigured in the Exchange IP method IP Address Active PLCA communication address IP Address Non Active PLCB communication address Subnetwork Mask Gateway Address This method is used in the redundant NX3030 CPU NETs and is also possible to be configured in the NX5000 modules In this method there s an IP for the Active half cluster and two more IPs one for the PLCA and another for the PLCB In the redundant NX3030 CPU NETs the Active IP address is added to the interface of the Active PLC and it can use either the Active IP address or the PLCX IP address in order to establish communication with the PLC On the other hand in the NX5000 Ethernet modules the Active IP address substitutes the Non Active PLCX IP address when the PLC is in Active mode Ethernet Port Parameters Cluster IP Addressing IP Address Active 192 168 15 1 IP Address PLC A 192 168 15 69 IP Address PLC B 192 168 15 7 Subnetwork Mask 255 255 255 0 Gateway Address 192 168 15 253 Advanced Figure 6 11 Active IP method Redundant NX3030 Parameters that must be configured in the Active IP method for the NETs of a redundant NX3030 CPU IP Address Active IP address added to the interface when the PLC is in Active state IP Address PLC A PLCA communication address apart from its current state IP Address PLC B PLCB communication address apart from its current state Subnetwork Mask 239 6 Redundancy with NX3030 CPU
377. ng registers writing FC 16 Writing mask of a holding register FC 22 Multiples holding registers reading writing FC 23 Table 4 39 MODBUS Functions Supported by Nexto CPUs Independent of the configuration mode the steps to insert an instance of the protocol and configure the Ethernet interface are equal The remaining configuration steps are described below for each modality e Add one or more instances of the MODBUS Ethernet client or server protocol to Ethernet channel NET 1 or NET 2 or both in the case of more than one communication network e To perform this procedure refer to the section Initial Programming Inserting a Protocol Instance e Configure the Ethernet interface e To perform this procedure see section Ethernet Interfaces Configuration 88 4 Configuration MODBUS Ethernet CLIENT This protocol is available for all Nexto Series CPUs on its Ethernet channels When selecting this option at MasterTool IEC XE the CPU becomes a MODBUS communication client allowing the access to other devices with the same protocol when it s in execution mode Run Mode There are two ways to configure this protocol The first one makes use of direct representation Q in which the variables are defined by your address The second one through symbolic mapping where the variables are defined by your name The procedure to insert an instance of the protocol is found in detail in the MasterTool IEC XE User Man
378. ng successful or not MasterTool informs the calculated looseness and the redundancy overhead predicted on the message window ActivePrg Program NonSkippeaPrg Program This program is executed in both CPUs PLCA and PLCB independent on the redundancy state It s typically used for functions such as e To organize non redundant diagnostics to report to a SCADA system e To receive and execute non redundant commands from a SCADA system e To manage switchover conditions normally not automatically contemplated by the redundant CPU that can vary from user to user E g a user will be able to execute a switch over to the Reserve CPU if the Active CPU isn t communicating with the SCADA system while another user may not want a switchover on this situation e To enable or disable I O drivers according to the redundancy state e g disable a Modbus RS 485 master in the Inactive CPU e To detect failures in I O drivers in an inactive CPU in order to avoid obscure failures Some I O drivers don t include such failures automatically detection while others such as the PROFIBUS does it automatically e Other activities which for some reason need to be executed either in the Active CPU and the Reserve CPU 227 6 Redundancy with NX3030 CPU For further information see MainTask Configuration NonSkippedPrg Program chapter Redundant and Non redundant Variables The redundant CPU variables can be classified among redundant and
379. ng the IP address or part of it 270 6 Redundancy with NX3030 CPU For instance the bytes between square brackets form the CPU address The right byte inside the brackets indicate the IP address end in hexadecimal If the bytes form the address 0010 this means the byte with value 10 indicates that the CPU IP address end is xxx xxx xxx 16 Next the CPU in the list must be clicked and the Set active path button pressed This done the selected CPU must appear stressed on the list indicating MasterTool is prepared to connect to this CPU Forth Step Identifying the NX3030 CPU and Verifying the CPU Display The forth step consists in identifying the half cluster as PLCA or PLCB This is made through the Online Cluster Basic Configuration menu Next the combo box PLC Identification allows selecting one out of the three following options e PLCA e PLCB e Non redundant CPU j W Cluster Basic Configuration 192 168 15 21 s PLC Identification l Write Non Redundant PLC A PLCB Project Syncronization Enable Z Write Figure 6 24 PLC Identification In case of a redundant CPU the user must select PLCA or PLCB After selecting the desired option the Write button correspondent to this combo box must be pressed MasterTool returns a message indicating command success or failure after the Button is pressed MasterTool returns a message warning that the CPU will be
380. nging in case there s a failure in any NIC Teaming pair port Each of the Ethernet interfaces that form the NIC Teaming pair have a unique diagnostics structure to point to failures which eventually might appear in any port of a NIC Teaming pair For further details regarding NIC Teaming configuration and diagnostics see the following sections e Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 e NX5000 Modules Configuration 237 6 Redundancy with NX3030 CPU IP Change Methods Fixed IP A redundant cluster from Nexto Series has four methods for IP change in the Ethernet ports of the NX5000 modules in each half cluster and one method for IP change in the NET1 and NET2 ports of the NX3030 CPU These methods define the ports behavior regarding its IP according to the current state of the half cluster Active or Non Active and with the half cluster PLCA or PLCB The methods are Fixed IP Exchange IP Active IP and Multiple IP Overall it can be listed up to four IPs according to the IP change method 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 Apart from the redundancy state PLC Active or Non Active the PLCA will always answer by the configured IP as also will PLCB Ethernet Port Parameters Cluster IP Addressing Method Fixed IP X
381. ngs present on the Filters button described in Table 4 53 are relative to the TCP communication filters Configuration Default Value Options Specifies a range of IPs with write ne uel access in the variables declared in 0 0 0 0 See ae the MODBUS interface San Specifies the subnet mask in Write Mask A 0 0 0 0 to y conjunction with the parameter IP 0 0 0 0 Filter filter for writing 255 255 255 255 r Specifies a range of IPs with read es tor access in the variables declared in 0 0 0 0 a ee 9 the MODBUS interface nema Specifies the subnet mask in eae conjunction with the IP filter 0 0 0 0 See ee parameter for reading ere Table 4 53 IP Filters Note Filters filters are used to establish a range of IP addresses that have write or read access to MODBUS relations being individually configured The permission criteria is accomplished through a logical AND operation between the Write Mask Filter and the IP address of the client If the result is the same as the IP Filter for Writing the client is entitled to write For example if the IP Filter for Writing 192 168 15 0 and the Mask Filter for Writing 255 255 255 0 then only customers with IP address 192 168 15 x shall be entitled The same procedure is applied in the Read Filter parameters to define the read rights The communication times of the MODBUS server protocol found on the Advanced button of the configuration screen are divided into Task Cycle
382. nnections between Half Clusters and the Redundancy Control Panel PX2612 219 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 Possibility to switch off the other half cluster One Touch Diag TM Electronic Tag on Display Display and LEDs for diagnostics indication Other features generals electrical mechanic and environment are presented in the NX4010 Redundancy Module Technical Features CE114900 Redundancy Control Panel PX2612 Figure 6 4 shows the redundancy control panel while Figure 6 5 shows the frontal panel with details Through the DB9 connector called CONTROL PLC A the connection with the CONTROL connector from PLCA NX4010 is made using the AL 2317 A cable Through the DB9 connector called CONTROL PLC B the connection with the CONTROL connector from PLCB NX4010 is made using the AL 2317 B cable Furthermore there s a connector with 5 male terminals GND terminal for ground connection 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 220 6 Redundancy with NX3030 CPU RL B 2 terminals
383. nning for Off Line Modifications without Process Control Interruption The following section Previous Planning for Hot Modifications in Redundant PROFIBUS Networks describes a very important procedure which allows the off line modifications download without interrupting the process control Even though this procedure doesn t apply to any modification that demand off line download it applies to the most used modifications However in order to apply this procedure the projects must be developed with a previous planning especially for modification that affects the PROFIBUS network The following subsections describe such previous planning for modifications that affect the PROFIBUS network and also other modifications Previous Planning for Hot Modifications in Redundant PROFIBUS Networks Among the modifications that affect a PROFIBUS network and demand an off line download the following are supported by the procedure which allows executing off line downloads without interrupt the process control if the PROFIBUS network is redundant Insert a new PROFIBUS network Insert a new Ponto Series remote Insert a new I O module in a Ponto Series remote Modify parameters in Ponto Series remotes or in I O modules in Ponto Series remotes ATTENTION It s possible to insert non redundant remotes under a redundant PROFIBUS network using the AL 2433 module ProfiS witch as the example shown on Figure 6 1 However such non redundant remotes w
384. non redundant Redundant variables are copied from the Active CPU to the Inactive CPU at the MainTask beginning of each 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 The redundant variables regard the shared information connected to the process control The variables associated to the I O modules are typical examples of redundant variables Redundant and Non redundant Variables The NX3030 CPU allocates 96kbytes of I variables IBO IB98303 The first 82kbytes can be redundant IBO IB81919 The last 16kbytes are always non redundant 1IB81920 IB98303 The 80kbytes area which can be redundant is allocated for inputs which can be read from an I O remote module PROFIBUS MODBUS etc The 16kbytes non redundant area is allocated for a half cluster quick private diagnostics and also for the redundancy command panel PX2612 buttons Quick diagnostics are the ones that must be updated each MainTask cycle The user may configure the redundant I variables quantity between 0 and 81920 Kbytes in 1kbyte multiples o valor default 16384 bytes IBO
385. nt PLC section After enabling the project synchronism in the Active PLC the user must verify if this command was successful verifying if DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag bProjectSyncDisable 0 in the Active PLC As soon as the project synchronism is enabled again the following action sequence is expected e The Non Active PLC Stand by state which already knows the different between both projects goes out from the Stand by state and goes to the Not Configured state 282 6 Redundancy with NX3030 CPU e The modified project new is copied from the Active PLC to the other temporarily in Not Configured state e As soon as the projects are synchronized again the Not Configured PLC goes to Starting state and then it s supposed to go back to Stand by state Step 11 Optional Reorganization of PLC and PROFIBUS Networks in Active State At the end of the procedure for standardization or organization reasons the user may execute a switchover for the PLCA assumes as Active and for all remotes PROFIBUS heads in Active state are in the network A 283 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 e Verify if the half cluster which won t be modified is in Active or St
386. nt to highlight that the user will have to be careful when changing the pre defined values by the project profiles as in this way it may put in risk the system execution So it is recommended to use the default values with the watchdog configured at 1000 ms 195 5 Initial Programming E StertPage i Configuration Bus g gt MainTask x Configuration Priority 0 31 13 Type Cydic Interval e g t 200ms 100 ms v Watchdog Time e g t 200ms 50 Sensitivity 1 POUs Add POU POU Comment Remove POU MainPrg Figure 5 13 Configuring Created Task The Table 5 9 shows the verifications done by the MasterTool IEC XE being the Sensitivity field equal to one For the Customized Profile it is not made any consistency in the task interval and in the watchdog time Minimum Cycle Time Maximum Cycle Time CyclicTask 2147483 ms TimelnterruptTask00 2147483 ms Table 5 9 Maximum Configurations Allowed ATTENTION When more than one task is used the access to I O must only be performed in the main task MainTask context POU Task Connection As described previously for a POU to be executed in the application it must be connected to a task In the project profiles without considering the Custom the POUs are already associated to its respective tasks However in case the Custom profile is being used or new POUs are created they must be connected to the tasks To associate a crea
387. ny command activating or deactivating are registered in the Redundancy Event Log which is important for the history analysis e g to determine a switchover cause Next the RedCmdLoc and RedCmdRem structure fields are defined Direct Representation AT variable Variable DG_NX4010 tRedundancy Re Description Variable Bn dCmdLoc TRUE It s a processed copy from the TURN ON PLCx button written on the PX2612 panel This bit is activated 1 second after the button pressing and deactivated immediately at its releasing It s important to bButtonTurnOnLocal stress that this bit will be activated when the TURN ON button on the remote PLC is pressed as this type of command is always sent by the remote PLC FALSE The button TURN ON PLCx isn t pressed TRUE It s a processed copy from the STAND BY button written on the PX2612 QB n 55 panel This bit is activated 1 second after the 1 bButtonStandbyLocal button pressing and deactivated immediately at its releasing FALSE The button STAND BY isn t pressed TRUE It s a processed copy from the INACTIVE button written on the PX2612 panel This bit is activated 1 second after the button pressing and deactivated immediately at its releasing FALSE The button INACTIVE isn t pressed TRUE This diagnostics inform an automatic bAutoConfigLocal configuration request necessary to let the Not Configured state in some situations bButtonInactiveLocal
388. o performs the processing of the bus This way different from other profiles the machine profile needs not context switch bus for the treatment which reduces the overall processing time This profile may further include an interruption task called TimeInterruptTask00 with higher priority than the task MainTask and consequently it can interrupt the execution at any time Prony Type interval Evom TimelnterruptTask00 TimeinterruptTaskoo ot cyclic 4m Table 5 8 Machine Profile Tasks Note The suggested names for the POUs associated to the tasks are not consisted in any profile They can be substituted since they are also substituted in the tasks configurations 187 5 Initial Programming New Project As previously described there are different types of project profiles depending on the technical knowledge of each user In this chapter only the creation of a new project using the Single profile will be described using the Wizard tool which presents all configuration options from the user system Some questions regarding other profiles are commented but for further information about programming the user must see the MasterTool IEC XE User Manual MU299609 the MasterTool IEC XE Programming Manual MU399609 or the IEC 61131 3 standard Initially the user must create a new MasterTool IEC XE project from the File menu followed by New Project as shown on Figure 5 1 w MasterTool IEC XE
389. observed the Non Active PLC switching on Wait until the Non Active PLC is restarted and assumes the Stand by state The test mode is active as the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal bit is turned off at the restarting in Stand by mode PLC Cause a switchover between PLCs pressing the Active PLC STAND BY button The normal use of the STAND BY button is possible because the test mode isn t active Turn on the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal command bit in the new Active PLC which has just gotten out the Stand by state This way the test mode is reactivated Turn on the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal command bit in the Active PLC It must be observed the Non Active PLC switching off Turn off the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal command bit in the Active PLC It must be observed the Non Active PLC reactivating Turn off the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal command bit in the Active PLC to finish the test mode It s not necessary to do this in the Stand by PLC as it has just initialized with the DG_NX4010 tRedundancy RedCmdLoc bTestModeLocal bit off 298 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 visualiz
390. of a redundant HSDN High Speed Deterministic Network for the communication between several redundant CPUs Through this network many redundant CPUs can exchange messages in a totally segregated network in order to guarantee determinism and a fast communication Furthermore configuring this network as redundant with NIC Teaming pairs an excellent availability may be reached In order to build such network redundant HSDN two NX5000 modules must be inserted in each half cluster Figure 6 1 shows a redundant HSDN example using two NX5000 modules in each half cluster Applications where input and output modules are connected to Ethernet networks may require extra interface modules NX5000 to connect to these networks In these cases the network that connects the modules of inputs and outputs can be a simple or redundant network Furthermore the interfaces can be configured with the option of generating life failure In this case a network failure will cause a switch over Figure 6 1 also shows an example with a NX5000 module used in the isolated form without NIC Teaming redundancy inserted at the right side from the other modules in each rack NX4010 Module The NX4010 model as shows Figure 6 3 was conceived in order to provide the interconnection between the two PLCA and PLCB half clusters and also to connect these half clusters to the redundancy control panel PX2612 For further information regarding this module connections see Interco
391. of the MODBUS requests displayed in Figure 4 29 follows the parameters described in Table 4 46 93 4 Configuration Diagnostics Variable Type NXMODEUS DIAGNOSTIC_STRUCTS T_DIAG MODBUS_ETH_MAPPING_1 Figure 4 29 MODBUS Data Request Screen 94 4 Configuration 3 s a Default Function Code MODBUS function type 01 Read Coils 02 Read Input Status 03 Read Holding Registers 04 Read Input Registers 05 Write Coil 06 Write Register 15 Write multiple Coils 16 Write Multiple Registers 22 Masked Writing of Register 23 Read Write Multiple Register Initial Address of Initial address of the the Read Data MODBUS read data Read Data Size MODBUS read data size MODBUS read data address Initial Address of Initial address of the the Write Data MODBUS write data Write Data Size MODBUS write data size Write Data Range MODBUS write data address range Diagnostics Diagnostic variable name Variable used to disable MODBUS 1 to 65536 Depends on the function used 0 to 2147483646 1 to 65536 Depends on the function used 0 to 2147483647 Name of a variable declared in a program or GVL Field for symbolic variable used to disable MODBUS requests individually configured This variable must be of BOOL type The variable can be simple or array element and can be in structures Table 4 46 MODBUS Client Relations Configuration Period of communication ms 100 0 to 3600
392. og Users and Groups Access Rights Information I co S Host Location J C Temp a e Runtime Location amp Name Size Modified Name Size Modified W Others Ory device devdesc xml 233 17 KB 238 768 9 29 2014 4 39 PM H File_01 b 428 bytes 9 1 2014 6 19 PM LJ Nexto b 226 bytes 10 2 2014 12 52 PM Figure 4 49 Root Directory with Memory Card Inserted The file transference happens in a similar way to the user memory utilization User Files Memory Access the folder MemoryCard and send the files as depicted on Figure 4 50 StartPage Configuration Bus J Device x Communication Settings Files Log _ Users and Groups Access Rights Information Host Location C Nexto ft Runtime Location ij MemoryCard i GR ee Name Size Modified Name Size Modified 1 a 0 Fileo1 13 54 MB 14 197 176 bytes 7 17 2012 2 15 PM Gy NextoMemCard E Backup 5 Fileo2 384 bytes 7 31 2012 7 20 Figure 4 50 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 126 4 Configuration ATTENTION The files transferen
393. olic Variables 20 0 0 eee eeessceccesssececeesneeeeessnaeeecsssaeeecesseeesesssaeeseesaeees 267 POUs from the Program Type with Redundant Symbolic Variables eesseeeeessseeeeeesneeeeeesnaeees 267 Breakpoints Utilization in Redundant Systems 20 0 0 eeeeccceeessececessnececeessaceceessaeeecesseeeseesaeeeeesaeees 268 MODBUS Instances Managing in Redundant System ee eeeeesseceeeessceeeesnaeeeeessaeeesessaeeesensaeees 268 Limitations on a Redundant PLC Programming cess eeeessseeeceesnececeessaeeceessaeeesessaeeesessaeeesesaeees 268 Getting the Redundancy State of a Half Cluster eee ee cessseeeeeesnececeesnaceceesseeeeesseeesessaeeseesaeees 269 Reading Non Redundant Diagnostics 00 0 0 eeescceceessececeesseeecessseeecesseeeceessaeeesesseeeesssaaeeseesaeeseesaeees 269 Redundant CPU Program Downloading ccccssssssssssssccccsssssssssscccsscssssssssssccsssssssssssssscsssssssssseseees 270 Initial Downloading of a Redundant Project ieee eeessscecceesneeecesseeeesessaeeceessaeeesessaaeesesssaeessenaeees 270 MasterTool Connection with a NX3030 CPU from a Redundant PLC 000 0 eee eeeeseeeeeesneeeeeennaeees 272 Modification Download in a Redundant Project ce eesseceessseeeceesneeeceessaeecsessaeeeeessaeeesesssaeeeeesaeees 273 Off Line and On Line Modifications Download eeeseeessecceeeesceeeesseeecesssaeeeeessaeeesessaeeesessaeees 273 On Line Download of Modifications eeesceeeessscecce
394. om the range of direct representation output variables Q still unused 84 4 Configuration The MODBUS protocol diagnostics and commands are described in the Table 4 33 The communication times of the MODBUS Slave protocol found on the button Advanced of the configuration screen are described in Table 4 32 Mappings Configuration Configuration via Direct Representation Q The settings of the MODBUS relations viewed in Figure 4 23 and Figure 4 24 follow the parameters described in Table 4 37 Data Start Address Data Size 1 Used range QX8196 0 QX8196 7 Read only Figure 4 24 Configuring the MODBUS Relation Configuration Description Default Value Options Coil 1 bit Holding Register 16 bit Input Status 1 bit Input Register 16 bit Data Type MODBUS data type Data Initial Initial address of the Number of MODBUS data 1 to 65536 IEC Variable oe address of variables Les 0 to 2147483647 fo Read Only Only allows reading Disabled Enabled or disabled Table 4 37 Slave Mappings 85 4 Configuration Notes Options the values written in the column Options may vary according with the configured MODBUS data 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
395. ommunication network In PROFIBUS networks it s a network with more than one master Communication network where information transfers are initiated by any node connected to the data bus Logical names for the Ethernet interfaces present in the NX3010 CPU NET 1 and NET 2 and modules NX5000 The CPU NX3010 and the NX5000 modules have only the NET1 interface Denomination of one of the two synchronism channels between PLCA and PLCB The other is called NETB Denomination of one of the two synchronism channels between PLCA and PLCB The other is called NETA Method used by all nodes in a communication network to synchronize data transmissions and resolve potential conflicts of simultaneous transmissions 325 8 Glossary NIC Teaming Node Non Active CPU Non Active PLC Non Redundant Data NonSkippedPrg Octet Operands Peer to peer PLC PLCA PLCB POU Programming language Programmable controller Project Archive Project Protocol RAM Redundant System Redundant CPU Redundant PLC Relays language and Altus blocks Ripple RS 232C RS 422 RS 485 RunTime RX SCADA ScTP Serial Channel Slave SNTP SOE Software Socket Stand by CPU Stand by PLC Start up Subnet Strategy to define pairs of redundant ports within a half cluster sharing the same Ethernet IP address Any station network with an ability to communicate using a protocol established It s the CPU that is not in the activ
396. on The account is automatically disabled when they made repeated logon attempts with the wrong password Memberships this list all the groups are presented in addition to the Everyone group that owns the new user automatically Selecting the respective items W is defined to which the new user groups must belong To set the new user close the dialog with OK In the event of any inconsistency incorrect password login name of absence existing user an error message will appear To modify an existing user account use the Edit button and open the corresponding dialog These fields are the same as the Add User dialog The password fields for security reasons produce 32 asterisks After changing the desired items close the dialog with OK to apply the new settings 169 4 Configuration Groups To delete one or more user accounts select their users in the appropriate list and press Remove Note that this action does not require confirmation You cannot delete all group members at least one must remain If you try this an error message will be shown Compiler warnings amp Page Setup Security E sce Source Download e Users and Groups Visualization Profile Users Groups Settings Name 8 Everyone H 8 Owner Description Remove Figure 4 82 Project Settings Groups Dialog The available current groups are listed in a tree structu
397. on as shown in the System Log section Note The CPU s system logs of the Nexto Series NX3010 NX3020 and NX3030 starting from firmware version 1 4 0 33 now reloaded in case of a CPU reset or a reboot of the Runtime System that is you can view the older logs when one of these conditions occurs 1 0 Scan Time For a project that uses digital I O modules being them inserted into the bus and declared in the project the MainTask time will increase according to the number of modules The Table 4 62 illustrates the average time that is added to the MainTask 114 4 Configuration Declared Modules in the Bus Added Time in the Main Task Cycle Time us ee 1000 Table 4 62 I O Scanning Time In projects that use remote I Os for example using the NX5001 PROFIBUS DP Master module the manual of the respective module has to be consulted for information about performance and influences of the module in the execution of user tasks 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 The time required to read write files on the card will be directly affected by the Cycle Time of the user application since this application has priority in execution Furth
398. oncludes the execution with an error It is false ERROR BOOL otherwise It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are STATUS SERIAL_STATUS NO_ERROR ILLEGAL_SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE NOT_CONFIGURED Returns the RX queue status error as RXQ_STATUS SERIAL PX QUEUE described in the SERIAL_RX_QUEUE_STATUS data type Table 4 85 SERIAL_GET_RX_QUEUE_STATUS Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured PROGRAM MainPrg VAR Get Status SERIAL GET RX QUEUE STATUS Port SERIAL PORT COM1 Status SERIAL STATUS Status RX SERIAL RX QUEUE STATUS END_ VAR INPUTS Get_Status REQUEST TRUE Get_Status PORT Port FUNCTION 137 4 Configuration Get_ Status OUTPUTS Get_Status DONE 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 por
399. onfiguration Memory Card There are two functions available one for log information and another to remove all records The following is a description of the types of data used by the functions Data type Option S Ciescription O USER_LOG_EVENT_ERROR The user is free to use the best indication USER LOG EVENT DEBUG according to log message severity USER_LOG_EVENT_TYPES USER_LOG_EVENT_INFO USER_LOG_EVENT_WARN USER_LOG_MESSAGE i 8 eth sil Log message with 150 character max USER_LOG_OK The operation was performed successfully The operation was not performed successfully The reason for the failure can be checked in the system logs see chapter Maintenance System Log USER_LOG_FAILED USER_LOG BUFFER_FULL Messages are being added beyond the processing capacity At the time there were no resources to perform USER_LOG_NO_MEMORY the operation USER_LOG_ERROR_CODES There was an error while accessing the memory card or there is no available space USER_LOG_FILE_SYSTEM_ERROR Error information can be verified in the logs of system see chapter Maintenance System Log USER_LOG_NO_MEMORY_CARD There is a memory card present in the CPU USER_LOG_MEMORY_CARD_FULL There is no free space available on the memory card USER_LOG PROCESSING The resource is busy executing the last operation for example deleting all log files Table 4 106 Data Type for User Log The following are described the two functions availabl
400. ons demand an off line download in the PLC In these cases the user has the option to interrupt the process control according to the procedure defined in the Off Line Download of Modifications with Process Control Interruption section For 279 6 Redundancy with NX3030 CPU that usually it s necessary to previously program a process stopping what isn t always possible at the moment the modification is needed Fortunately the PLCs redundancy and in some cases the PROFIBUS network redundancy make possible to execute the off line download without interrupting the process control for most of the modifications needed For reaching this objective it s necessary to follow carefully a procedure which the steps are described in the following sub sections Step 1 Verify Basic Requirements Attending For the off line downloading with no interruption of the process control to be possible the following basic requirements must be attended e The original project must have been created according to the recommendations of the Previous Planning for Off Line Modifications without Process Control Interruption section e The PLC must be redundant e Incase the modification affects the PROFIBUS network it s necessary this network to be redundant Such modifications may be o New remotes insertion o TO modules insertion in existent remotes in previously reserved positions for correspondent virtual modules For the remote not have to
401. ons to calculate the new time out Example of the initial time out and the communication time out parameters inside the MODBUS TCP Server considering a not received acknowledge for the following values 300 for initial time out 300 ms and 3000 for communication time out 3000 ms 1 2 3 4 5 6 time 300 ms 600 ms 1200 ms 900 ms Hli 2400 ms __ Figure 4 1 Initial Time out and Communication Time out 45 4 Configuration Legend 1 Message transmission instant 2 First attempt for message transmitting after initial time out 3 Second attempt for message transmission after two times the initial time out 4 Third try for message transmission after two times the latter time out 5 Quit of message transmission and failure indication after the communication time out exceeds total time until the given up 300 600 1200 900 3000 ms It would be the fourth message transmission attempt after two times the latter time out but the communication time out configured inside the protocol was exceeded and the failure was indicated e ACK sending delay defines the maximum time waited by the interface for the TCP ACK transmitting This ACK is responsible for the message receiving conformation in case of MODBUS by the destiny device The set of this field decreases the amount of messages circling through the network This mechanism is explained below o All request messages sent by
402. ontext each rack PLCA or PLCB is called half cluster while the group formed by these two racks is called cluster In this example a PROFIBUS network Ethernet supervision network and Ethernet HSDN control network duplication can also be observed 216 6 Redundancy with NX3030 CPU a MasterTool Ethernet A Other CPUs Redundant or not 4 CPUs gt cluster PROFIBUS 14 half cluster PROFIBUS 1B Non redundant Ethernet Ethernet HSDN A Ethernet HSDN B PROFIBUS Redundant Network Non redundant PROFIBUS s lawes Figure 6 1 Example of redundant architecture with NX3030 CPU 217 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 e Two identical half clusters e The rack itself where the modules are inserted which can be one of the following o NX9001 with 12 positions o NX9002 with 16 positions o NX9003 with 24 positions e The power supply NX8000 at rack positions 0 and 1 e The NX3030 CPU at rack positions 2 and 3 e The module NX4010 at rack positions 4 and 5 Figure 6 2 shows an example of a redundant CPU minimum configuration using the smallest rack NX9001 with 12 positions In this case it can be observer that the three modules inserted in the rack have double width occupy two rack positions Synchronism channel NETA
403. or the RX line with normal format the SERIAL_RX block must be used to receive data MODE Defined at SERIAL_MODE When true all the received byte during the tothe RX line Used to dis abie the fulkduplex operation in the RS 422 interface ee ea SERIAL_PARITY List all parity possibilities PARITY_SPACE List all available serial ports COM 10 COM 11 COM 12 COM 13 COM 14 COM 15 SPRASPORI COM 2 COM 16 COM 17 COM 18 and COM 19 expansion modules Defines a character in the RX queue in extended mode RX_CHAR Data byte SERIAL_RX_CHAR_EXTENDED Silence due to the previous character or due to another event which has happen before RX TIMESTAME this character serial port configuration transmission ending It has some fields which deliver information regarding RX queue status error used when the normal format is utilized no error and timestamp information Frame errors counter character incorrect formation no stop bit incorrect baud rate RX_FRAMING_ERRORS among other since the serial port configuration Returns to zero when it reaches the maximum value 65535 Parity errors counter since the serial port SERIAL_RX_QUEUE_STATUS RX_PARITY_ERRORS configuration Returns to zero when it reaches the maximum value 65535 Interruption errors counter since the serial port configuration in other words active line RX_BREAK_ERRORS higher than the character time Returns to zero when it reaches the ma
404. or this service to be executed several conditions must be satisfied e The previous synchronization service in this MainTask cycle Diagnostics and Commands Exchange must be completed with success e Incase this CPU is in Active state the other must be in Non Active state On the other hand in case this CPU is in Non Active state the other must be in Active state e Both projects 2 CPUs must be identical except when the project automatic synchronization is disabled see Project Synchronization Disabling section e At least one synchronism channel NETA and or NETB must be operational If both synchronism channels NETA and NETB are operational the communication is distributed between both load balances in order to reduce the synchronization time In case only one channel is operational the synchronism will continue to be executed only by this channel keeping the redundant data synchronization 233 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 e Both synchronization services previous to this cycle Diagnostics and Commands Exchange must be completed with success e Incase this CPU is in Active state the other must be in Non Active state On the other hand in case this CPU is in Non Active state the other must be
405. ortant for systems which need high availability It s possible to connect to a specific CPU PLCA or PLCB using a private IP address to obtain half cluster specific diagnostics for instance The PLCA IP address will always be associated to the PLCA NET i interface while the PLCB IP address will always be associated to the PLCB NET i interface Name of a strategy that allows the Ethernet client connect to a server from the redundant CPU using always the same IP address This prevents the necessity of complex scripts to change the IP address when switchovers occur due to redundancy The Active IP address will always be associated to the NET i interface from the Active CPU Name of the strategy which allows two Ethernet interfaces from a half cluster to form a redundant pair sharing a same IP address 224 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 PROFIBUS Network and Vital redundant or not It s also possible to configure if each Failures Configuration PROFIBUS network failure is considered vital causes switchover or not Single and cyclic user task oi ag user task is allowed called MainTask This task is At a redundant project creation MasterTool generates automatically two empty POU programs which must be
406. ot standby redundancy is a method used to increase failure tolerance and consequently increase the availability of automation systems The basic idea is to ensure that no simple failure in duplicated components causes the process control interruption The hot standby redundancy is applied on Oil exploration platforms Energy generation and distribution plants Security interlock Instrumented Security Systems Continuous processes such as chemical plants oil refinery paper production etc In the Nexto Series CPUs hot standby redundancy as it has already been described the controllers are doubled Besides the field buses PROFIBUS DP can also optionally be doubled as well as the Ethernet supervisory networks and the Ethernet HSDN High Speed Deterministic Network control networks By choosing the networks duplication the availability becomes even higher The Nexto Series CPUs hot standby redundancy is not applied to I O modules In case the I O module redundancy is desired it can be treated by the user in the application level For instance the user can duplicate or even triplicate an analog input module and create a vote scheme to define which input will be considered in an application specific time Figure 6 1 shows a typical example of redundant architecture using the NX3030 CPU The redundant CPU central part is formed by two identical racks called PLCA and PLCB and a redundancy control panel PX2612 In the redundancy c
407. otoco 00 Without protocol Ethernet NET1 wProtocol QX N 93 0 QX n 93 0 QX n 93 0 BIT bMODBUS_RTU_ETH_Cl Bit O MODBUS RTU Client via TCP ient Ethernet NET1 wProtocol P QX n 93 1 QX N 93 1 QX n 93 1 BIT bMODBUS_ETH Client MODBUS TCP Client Ethernet NET1 wProtocol QX N 93 2 QX n 93 2 QX n 93 2 BIT bMODBUS_RTU_ETH_S MODBUS RTU Server via TCP erver QX n 93 3 QX n 93 3 QX n 93 3 BIT Ua ea ag MODBUS TCP Server QB n 95 QB n 95 QB n 95 STRING 15 Ethernet NET1 szIP IP NET 1 Address QB n 1 11 QB n 1 11 QB n 111 STRING 15 Ethernet NET1 szMask NET 1 Subnet Mask QB n 127 QB n 127 QB n 127 STRING 15 rere NET 1 Gateway Address QB n 1 43 QB n 1 43 QB n 143 STRING 17 Ethernet NET1 szMAC MAC NET 1 Address BYTE O QB n 161 QB n 161 QB n 161 ARRAY 4 Ethernet NET1 abyIP IP NET 1 Address QB n 165 QB n 165 QB n 165 Peon 4 EthemnetNET1 abyMask NET 1 Subnet Mask BYTE Ethernet NET1 abyGatew QB n 19 QB n 19 QB n 19 ARRAY 4 ay y NET 1 Gateway Address QB n 173 QB n 173 QB n 173 ARATO Ethernet NET1 abyMAC MAC NET 1 Address Ethernet NET1 dwPackets Counter of sent packages through O O 9 QD n 179 QD n 179 QD n 179 DWORD Sent NET 1 port 0 to 4294967295 Counter of received packages through NET 1 port 0 to 4294967295 Ethernet NET1 dwBytesS Counter of sent bytes through NET 1 ent port 0 to 4294967295 Etherne
408. ously with the MODBUS RTU via TCP protocol Supervision System MODBUS TCP GATEWAY MODBUS TCP MODBUS RTU HX30x0 HX30x0 Ethernet Network I O MODBUS RTU MODBUS RTU Network MultiDrop lt gt MODBUS TCP messages with HX30X0 Server Mode MODBUS TCP messages with HX30X0 Client Mode Figure 4 25 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 This information is detailed in the description of each protocol All relations in client mode or server mode can be disabled through direct representation variables Q identified as Mapping Disabling by MasterTool IEC XE The disabling may occur through general bits which affect all relations of an operation mode or through specific bits affecting specific relations 87 4 Configuration For the server mode relations IP addresses clusters can be defined with writing and reading allowance called filters This is made through the definition of an IP network address and of a subnet mask resulting in a group of client IPs which can read an
409. out from this state For further details regarding this Active CPU behavior see Transition between Redundancy States and First Instants in Active State sections e Incase this CPU is switching off the other CPU through its PC2612 relay the LED STAND BY blinks It remains off otherwise 246 6 Redundancy with NX3030 CPU PX2612 Relays The PX2612 has two NO relays The PLCA can control the RL B to command the PLCB switching off The PLCB can control the RL A to command the PLCA switching off Such switching off situations happen in exceptional situations described in the Transition between Redundancy States section Transition between Redundancy States The following figure shows the redundancy state machine illustrating all the possible transitions between redundancy states Not Configured Figure 6 14 Redundancy State Machine The following sub sections describe all these transitions and the causes which can trigger them In order to interpret correctly this state machine functioning some rules and sequences must be established Transitions which originate from the same state must be analyzed in the sequence established by their number E g the transitions 2 3 4 and 5 are originated from the Starting state In this example the transition 2 is first analyzed then 3 4 and finally 5 In case the transition 2 is triggered the transitions 3 4 and 5 won t be analyzed Inside a specific sub section describing
410. output points using the software tools If the load is small there is no need for disconnecting It is important to note that in the cases the CPU gets in Stop Mode and the LED DG starts to blink 4x according to Table 4 3 due to any abnormal bus situation as described on Table 4 2 the output modules have its points operation according to the module configuration when CPU toggles from Run Mode to Stop Mode In case of application startup when the CPU enters Stop Mode without having passed to the Run Mode the output modules put their points in failure secure mode in other words turn it off 0 Vdc Regarding the input modules if one module is removed from energized backplane rack the logic point s state will remain in the last value In the case a connector is removed the logic point s state will be put in a safe state it means zero or high impedance ATTENTION Always proceed to the substitution of one module at a time for the CPU to update the modules state Below Table 4 3 presents the bus conditions and the Nexto CPU LED DG operation state For further information regarding the diagnostics LEDs states see Diagnostics via LED chapter 43 4 Configuration Enabled with Enabled with 5 Consistency in Condition Startup Consistency Enabled without Disabled for the Start Only for Consistency in the Disabled declared modules Declared Modules Sei oniy Non declared LED DG 2x LED DG 2x LED DG Blinks 2x LED DG
411. ow will appear for the user to define and classify its functioning The field Priority 0 31 establishes the priority in which the task will be executed in the application where zero is the highest priority For instance the MainTask created in the majority of the project profiles has priority 13 so this task is considered with high priority for the system The space Type defines which type and the method used to execute the task where the following items can be selected e Cyclic the task is executed in cycles or it is called every time interval configured in the field at its side E g t 100ms e Event the task is executed when the variable is from the BOOL type configured in the field at its side receives a rising edge in other words the variable value goes from FALSE to TRUE e External the task is executed when an external event occurs It is configured in the side field For further information about external event please consult the chapter External Event Configuration e Freewheeling the task is always executed according to its priority in other words tasks with higher priority are executed first e Status the task is executed when the BOOL variable configured in the side field is true Besides the fields described above it still has to be set the Interval only for cyclic tasks that is the time interval which the task is called to run maximum time for MainTask is equal to 750 ms and the minimum tim
412. owing One byte for the received data RX_CHAR BYTE Store the five six seven or eight bits from the data received depending on the serial communication configuration One byte for the signal errors RX_ERROR BYTE It has the format described below 55 4 Configuration e Bit 0 0 the character in bits 0 to 7 is valid 1 the character in bits 0 to 7 is not valid or it cannot be valid due to problems indicated in bits 10 to 15 e Bit 1 Not used e Bit 2 Not used e Bit 3 UART interruption error The serial input remained in logic 0 parity always zero for a time greater than a character start bit data bit parity bit stop bit e Bit 4 UART frame error The logic 0 space was read when the first stop bit was expected and it should be logic 1 parity always one e Bit 5 UART parity error The parity bit read is not correct according to the calculated one e Bit 6 UART overrun error Data was lost during the FIFO UART reading New characters were received before the later ones were removed This error will only be indicated in the first character read after the overrun error indication This means some old data were lost e Bit 7 RX line overrun error This character was written when the RX line was completed overwriting the unread characters Two bytes for the timestamp signal RX_TIMESTAMP WORD Indicates the silence time within the 0 to 65535 interval using 10us as base It saturates in 655 35ms if th
413. patible with the firmware version of the Active PLC Transition 11 Stand by to Inactive e NX4010 module not detected in the bus or its microprocessor failure e The INACTIVE button was pressed on the PX2612 This is made typically in order to execute a programmed maintenance in the Non Active CPU Any programmed maintenance must be avoided in the Stand by CPU thus is recommended to switch to Inactive mode e The other CPU is in Active state However the redundant data synchronization or the redundant forcing list synchronization services haven t worked in last four cycles of the MainTask or the diagnostics synchronization service haven t worked in the last two cycles of the MainTask 249 6 Redundancy with NX3030 CPU e The other PLC is in Active state However this PLC can t monitor traffic in every PROFIBUS network configured as vital fail mode e The other CPU is in Active state However this CPU detected failure in Ethernet ports configured as Vital Failure mode Transition 12 Stand by to Active e The other CPU state is unknown due to NETA and NETB failures In this case besides going to Active state for safety reasons this CPU switches off the other CPU using the PX2612 relay When the Redundancy does not use PX2612 panel and there PROFIBUS DP this condition is not generated the remaining CP in state reserve In this condition the fault if it has been generated by other CP to regain control of the process is to
414. pdated in the CPU Indicates an error has occurred during the CPU firmware UPDATE ERROR updating caused by communication failure or configuration problems REBOOTING SYSTEM ae the CPU is being restarted for the updating to have Table 7 12 Other Messages of the Graphic Display 320 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 In order to access these Logs just go to the Device Tree and double click on Device then go to the Log tab where hundreds of operations can be seen such as task max cycles user access application download online change application download and upload application synchronization between CPUs firmware update between another events and actions In order to view the Logs just need to be connected to a CPU Selected Active Path and click on lel When this button is pressed the Logs are displayed and updated instantly When the button is not being pressed the Logs will be hold in the screen it means these button has two stages one hold the logs state being upda
415. pings Must also be considered the maximum CPU mappings as Table 4 17 Maximum number of concurrent requests per device in the case of the MODBUS Server driver this limit is implemented by the communications driver being this limit fixed As for the MODBUS Server there is only one device for each instance This number is the same as the maximum number of requests per instance 64 4 Configuration Limitations MODBUS RTU MODBUS RTU MODBUS MODBUS Meter Slave Ethernet Client Ethernet Server Maximum number 64 64 1 of devices Maximum number of lines for 5120 5120 5120 5120 devices Maximum number of simultaneous requests for instance 128 64 Maximum number of simultaneous requests for device Table 4 19 MODBUS Protocol Limitations for Symbolic Mappings Notes Number of rows per devices the maximum number of lines in the configuration of a device mappings despite being referenced above is also limited by the maximum number of Protocol mappings Must also be considered the maximum CPU mappings as in the Table 4 17 Maximum number of concurrent requests per device in the case of the MODBUS Server driver this limit is implemented by the communications driver limit fixed As for the MODBUS Server there is only one device for each instance and this number is the same as the maximum number of requests per instance ATTENTION Communication drivers for symbolic mappings are available only from 1 3 0 20 version of Nexto
416. ponents tolerate simple failures without causing unavailability but do cause switchover Racks NX9001 NX9002 or NX9003 Power Supply NX8000 CPUs NX3030 NX4010 modules NX5001 modules PROFIBUS masters in non redundant PROFIBUS network configuration NX5000 module Ethernet in configurations without NIC Teaming PROFIBUS slave interface in a redundant remote PO5063V5 POS5065 or AL 3416 In this case different from the previous the switchover happens inside the remote between the PROFIBUS A and B networks ATTENTION In case of failure of the CPU NX3030 or NX4010 module in architectures where panel PX2612 or PROFIBUS network is not used the CPU will remain in its current state In this case if the failure occurs in the half cluster active system downtime occurs Double Failure without Unavailability Causing a Switchover Some components are doubled in each half cluster this way before causing a switchover both must fail e NX5001 modules PROFIBUS masters in redundant configuration configured in vital failure mode e NX5000 modules Ethernet in configurations with NIC Teaming redundancy managed by the user 253 6 Redundancy with NX3030 CPU Redundancy Overhead A redundant application implies on an application processing time increase when compared to the necessary time for a non redundant equivalent application This additional time happens due to cyclic synchronization services execution des
417. ption After the desired CPU has to be selected and the OK button clicked as shown on Figure 5 38 Communication Settings Fles_ Log Users and Groups Access Rights Information Select the network path to the controller Gateway 1 0164 m Set active path gt the Gateway t N3030 199 168 17 100 J Nx3030_192 168 17 100_Antonio 0164 active Paria Add gateway Device Address 0164 Add device Target ID 16410264030 Target Name Scan network INEXTO PLC Target Type Filter 1641000 Target ID m Target Vendor Altus Sorting order Name x Target Version 1 5 0 1 E Don t save network path in project E Secure online mode Figure 5 38 Selecting the CPU ATTENTION The memory size area to store a project in the Nexto CPUs is defined on Table 2 5 214 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 Run When a CPU is in Run mode it indicates that all application tasks are in execution Stop When a CPU is in Stop mode it indicates that the application tasks are stopped The variable values in the tasks are kept with the current value and output variables assume defined values by the user When a
418. puts are not used the update is performed at every cycle of the MainTask ATTENTION At the startup of a Nexto CPU the inputs and outputs are only updated for reading and prepared for writing when the MainTask is performed All other system tasks that run before MainTask will be with the inputs and outputs invalid 145 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 ATTENTION REFRESH_INPUT must only be used in MainTask task ATTENTION REFRESH_INPUT function does not support inputs that have been mapped to symbolic variables For proper operation it is necessary that the input is mapped to a variable within the memory direct representation of input variables I REFRESH_INPUT Figure 4 61 Block for Input Updating Input parameters byRackNumber bySlotNumber BYTE Position number where the module is connected Table 4 96 REFRESH_INPUT Input Parameters Possible ERRORCODE e NoError Execution success e YJOModuleAbsent The module was configured but is absent e JOModuleNotConfigured The module was not configured e ParameterMismatch This error is returned in case the
419. question about uninstall this version before installing the new one If the installed version is lower than the version 1 40 the uninstall process is different and after its completion it will be necessary to start the setup program again 38 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 CPU Configuration General Parameters The parameters related below are part of the CPU configuration inserted in the application Each item must be correctly revised for the project perfect execution Besides these parameters it is possible to change the name of each module inserted in the application by clicking the right button on the module In the Properties item from the Common sheet change the name what is limited to 24 characters Configuration Q Initial Address Q Initial Address Q Initial Address Start User Application After a Watchdog Reset Description CPU diagnostics initial address Q Diagnostics area size in bytes Retentive data memory initial address Q Retentive data memory size in bytes Persistent data memory initial address Q Persistent data memory size in bytes When enabled st
420. r MODBUS Client for direct addressing Q and click on Add Device as depicted on Figure 5 22 203 5 Initial Programming J Add Device Ex Name MODBUS_Symbol_Client Action Append device Insert device Plug device Update device Device Vendor lt All vendors gt Z Name Vendor iz J MODBUS Ethernet J MODBUS Client J mopsus Client WAA J MODBUS Symbol Client Altus S A J MODBUS Server J MoDBUS Server WAA J MODBUS Symbol Server Altus S A m E Display outdated versions Information J Name MODBUS Symbol Client Vendor Altus S A Categories MODBUS Client Version 1 0 0 21 Order Number Description MODBUS TCP Client or MODBUS RTU over TCP Client M Append selected device as last child of NET1 You can select another target node in the navigator while this window is open _ cose Figure 5 22 Selecting the 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 In the tab Communications Settings select the Gateway and click on Scan network On the Communication Settings tab select the Gateway or in case there is no Gateway or the user wants to add a new gateway click the Add Gateway setting your IP in the window that opens Fo
421. r responsible for the messages deliver from the origin to destiny has some parameters with time outs very common in general communication protocols Such parameters are intended to recover the communication after the failures are determined The user must be aware with the time outs configuration as it some conflicts might occur with the values configured inside the 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 e 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 At each retransmission the time out is doubled The number of transmission tries is connected to the communication time out configured inside the protocol It will be the maximum time before it gives up the message delivering when the transmission failure is concretized In addition it is important to stress that exists a maximum limit of attempts for the Nexto Series CPUs This number is set in five attempts before the connection is set up and in three attempts after that See Protocols Configuration section further details regarding time out parameters utilization as they can be different depending on the situation It is important to stress this parameter is only used in the connection setting up after that it is used statistics from the last communicati
422. r a rising edge the specified time PT will be counted and the Q output will be driven to TRUE at the end of it When the input IN is in logic level 0 FALSE the output Q remain in the same state FALSE even if it happens in the middle of the counting process The PT time can be changed during the counting as the block assumes the new value if the counting hasn t finished Figure 4 67 depicts the TON_RET block and Figure 4 68 shows its graphic behavior TON_RET Figure 4 67 TON_RET Function Block Input parameters Description BOOL This variable when receives a rising edge enables the function block counting PT TIME This variable specifies the block counting limit time delay Table 4 102 TON_RET Input Parameters This variable executes a rising edge as the PT BOOL variable time delay reaches its maximum value TIME This variable shows the current time delay 152 4 Configuration Table 4 103 TON_RET Output Parameters tO tl t2t3 t4 t5 n a y tO PT tl t4 PT t5 PT SUAS 0 tO tl t2 t3 t4 t5 Figure 4 68 TON_RET Block Graphic Behavior Utilization example in ST language PROGRAM MainPrg VAR RETAIN bStart BOOL TON RET TON RET EN D 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 END_IF TP_RET The T
423. r allows certain actions for each group of users in the CPU To edit these rights in the CPU the user needs to access a project in MasterTool IEC XE software without the need to be logged in the CPU You should then click the Device Tree located in the left of the program click in Device item and after select the CPU in the Communication Settings tab that opens Only the tabs Users and Groups and Access Rights relate to this topic Figure 4 86 illustrates the steps to access these tabs CPU 2 Configuration Bus C Device x ommunication Settings Files Log El Users and Groups Access Rights Fformation Select the network path to the controller Gateway 1 0164 a Set active path Fie Gateway 1 Device Name INX3030_192 168 17 100 a Antonio Add gateway J M NX3030_192 168 18 144_R mulo maciel 0297 pavor Li Add device NX3030_192 168 18 28 021C NX3030_192 168 19 131_MasterTool 0383 16 1026A030 NX3030_192 168 19 226_Adriano 03E2 Scan network J Nx3030_192 168 19 50 0332 Lark a E SuperTeste_BCSNX3030_192 168 23 38_PLCA_Beijer 0726 Filter q Target Type EE el a SuperTeste_NX3030_192 168 23 1_PLCA_Roberto 0701 16 1000 Target ID Mi SuperTeste_NX3030_192 168 23 2_PLCB_Roberto 0702 Target Vendor Sorting order Altus pisi Name Zi Target Version 1 5 0 5 Don t save network path in project Secure online mode Figure 4 86 User and Groups and Access Rights tabs ATTENTION
424. r and the firmware version installed For example for a CPU with serial number 445627 and firmware version 1 4 0 4 the location where the log files should be written to the memory card is MemoryCard UserLog 445627 1 4 0 4 The names of the log files are formed by the date and time timestamp of the first message Except when there s a problem to use this name for example another existing file with the same name in this situation it is used the instant date and time The filename follows the following pattern year month day hour minute second millisecond CSV In case of file access problem due to defective sector not enabling to continue writing will be added to the name of this file the extension corrupted and a new file will be created The amount of logs per file is not fixed varying depending on the size of messages The amount of created files is limited to 1024 with maximum size of 1 MB each so the memory card requires 1 GB of free space When it reaches the limit of 1024 files created on the memory card during CPU operation the oldest files are removed so that files with latest logs are preserved even in cases of partial manual removal of the files in the directory where the files are being written The viewing of the log files can be performed through worksheets or conventional text editors The concatenated information for improved visualization may use semicolons between the strings of the message to separate them One must be
425. r is out of both NET1 and NET2 subnets interfaces the request may be done by any of both interfaces which can find a route for the server For the SNTP client the user must set the following parameters in the SNTP Configuration tab accessed by the CPU in the devices tree 53 4 Configuration fb Start Page el Configuration Bus fj NX3030 General Parameters SNTP Configuration SOE Configuration General Configuration SNTP Service Enabled X Period for SNTP Synchronization x1 sec 60 Minimum Error Before Clock Update x1 ms 100 Time Zone 03 00 First SNTP Server IP Address of First SNTP Server RB OR SO 258 Second SNTP Server IP Address of Second SNTP Server E aE Figure 4 8 SNTP Configuration Configuration Standard Default Options Disabl SNTP Service Enables the SNTP service Disabled era Enabled Period for SNTP Time interval of the 1 to 255 Synchronization x1 synchronization requests sec seconds Time zone of the user Time zone hh mm location Hours and minutes 3 00 12 59 to 13 59 can be inserted IP Address of the First IP Address of the primary 192 168 15 10 0 0 0 1 to SNTP Server SNTP server toe 255 255 255 254 IP Address of the 2 IP Address of the secondary 192 168 15 11 0 0 0 1 to Second SNTP Server SNTP server RRA 255 255 255 254 Table 4 7 SNTP Configurations Minimum Error Before Offset value acceptable between the server and 100 100 to 65519 Clock Update x
426. r mapping devices present in the network click on Scan Network Then the user must wait until the MasterTool IEC XE software searches and show the available CPUs in the network 204 5 Initial Programming StartPage iif Configuration Bus J Device x Communication Settings Fies Log Users and Groups Access Rights Information Select the network path to the controller Gateway 1 b Set active path Gateway 1 Node Name PiolGatewaya pede ee Add gateway Driver TCP IP Add device IP Address localhost O oaan Port Scan network fj 1217 Filter Target ID X Sorting order Name x E Don t save network path in project Secure online mode Figure 5 23 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 StartPage if Configuration Bus ff Device x Communication Settings Files tog Users and Groups I Access Rights I Information Select the network path to the controller Gateway 1 0380 ba Set active path le Gateway 1 eer fe eaaa M Nx3030_192 168 19 128 0380 active at Add gateway Node Address et 0380 Add device Target ID 16 1026A030 Target Name Scan network INEXTO PLC Target Type Filter 16 1000 foie ae S Target ID
427. r project profiles according to the particularities of his application On the other hand the custom model associated to this does not require elements pre defining as a task program or parameter leaving the developer to create all the elements that make up the application However the user can generate the same elements available to the Expert profile Tak POU Priority Type Interval Event MainTask Mang 13 Cyc t00ms CyclicTaskoo CyclcPrgoo 13 Cyoic 20msf Cyctictaskor CycicPrgo1 13 Cyoic somsf ExterninterruptTask00 ExterninterruptPrgoo o2 External IO_INT_0 TimeinterruptTaskoo TimeinterruptPrgo0 o1 Cyoic 20ms f ExterninterruptTask01 ExterninterruptPrgoi 11 External ionta TimeinterruptTasko1 TimeinterruptPrgot_ o9 Cycic_ soms f FreeTask FreePg 31 Freewheeling Table 5 7 Tasks in the Customized Profile In machine profile by default the application has a user task Cyclic type called MainTask This task is responsible for implementing a single programming unit type Program called MainPrg This program can call other programming units of the type Program Function or Function Block but any user code will run exclusively by MainTask task This profile is characterized by allowing shorter intervals in MainTask task allowing faster execution of user code This optimization is possible because the MainTask als
428. r the incompatible configuration diagnostics The AT directive is a reserved word in the software programmer and some symbolic variables using this directive serve to indicate the diagnostics Exception Code The exception code generated by the RTS can be consulted below 315 7 Maintenance 0x0000 There is no exception code 0x0010 Watchdog time of the expired IEC task Privileged instruction Software Watchdog 0x0012 I O configuration error Page failure 0x0054 Stack overflow 0x0013 Checksum error after the program Invalid disposition download Fieldbus error 0x0056 0x0015 I O updating error 0x0057 Protected page 0x0016 Cycle time execution exceeded 0x0058 Double failure 0x0018 External references not resolved 0x0100 Data type misalignment 0x0019 Download rejected Arrays limit exceeded 0x0017 Program online updating too long 0x0059 Invalid OpCode 0x001A Project not loaded as the retentive variables Division by zero cannot be reallocated oono Overiow Si 0x001B Project not loaded and deleted Out of memory stack 0x0104 Cannot pe continued 0x001C Out of memory stack 0x001D Retentive memory is corrupted and cannot be mapped 0x001E Project can be loaded but causes a drop later on Watchdog in the processor load of all IEC task detected 0x0021 Target of startup application does not match FPU Operand is not normal to the current target FPU Not specifie
429. r words to design any one from the other 4 states Stand by Inactive Not Configured and Starting An Active CPU is the one that is in Active state and a Non Active CPU is the one that isn t in Active state In the following sections these five states are briefly described Further details regarding the redundant CPU states are described in the Transition between Redundancy States section when the state machine and the transition causes are also described Not Configured State This is the initial redundancy state The CPU is found in this redundancy state By convention while the CPU is OFF Before starting the MainTask Before the Starting state is switched After switching from any other state to Not Configured In case there s a restart through a command as reset warm reset cold or reset origin In case the MainTask is being executed in the Not Configured state the following tasks are executed e The PROFIBUS masters are disabled e The cyclic synchronization services are executed see Cyclic Synchronization Services through NETA and NETB section if the condition for its execution are true e The sporadic synchronization services can also be executed see Sporadic Synchronization Services through NETA and NETB section The CPU will be blocked in the Not Configured state if the other CPU is in Active state and this CPU project is different from the Active CPU project except if the project automatic synchronization is
430. rPLC_TestMode bActiveLED bBlinkActiveLED bStandbyLED bBlinkStandbyLED bInactiveLED bBlinkInactiveLED QB n 10 QW n 11 289 bRedPanelT estMode QB n 8 ePLC_ID a Previous RedState value before the data wRedStateDuration rok SSOS S SSCCCCC TRUE This PLC can t communicate in the master state active or passive with at least one of the PROFIBUS networks configured in vital failure mode FALSE There aren t failures in the PROFIBUS networks configured in vital failure TRUE This PLC can t communicate in the master state active or passive with all the PROFIBUS networks configured in vital failure mode FALSE There aren t failures in the PROFIBUS networks configured in vital failure TRUE This PLC is closing the PX2612 relay to keep the other PLC off in normal conditions and not due to PX2612 panel test FALSE The PX2612 relay is on bTurnOffOtherPLC_TestMode or off TRUE this PLC is closing the PX2612 relay to keep the other PLC off due to PX2612 panel test mode FALSE The PX2612 relay is on bTurnOffOtherPLC_Normal or off TRUE The PX2612 LED ACTIVE is on FALSE The PX2612 LED ACTIVE is blinking bBlinkActiveLED or off TRUE The PX2612 LED ACTIVE is blinking FALSE The PX2612 ACTIVE is on bActiveLEDI or off TRUE The PX2612 LED STAND BY is on FALSE The PX2612 LED ACTIVE is blinking bBlinkStandbyLED or of
431. ransistor 8 DI Mixed Module f Task Configuration l NX2001 MainTask 24Vdc 16 DO Transistor Module Configuration Bus J n010 Nx3010 comi sea com2 s Modul NETI Ha Q S x n E z I T 7 g Accessories g Analog 1 0 A coms J Digital 1 0 J fieldbus tntertaces Power Supplies g Racks J special modules Current user nobody Figure 5 7 Adding Modules Creating POUs A POU Program Organization Unit is a subdivision from the applicative program which can be written in any language available in the MasterTool IEC XE software With the project creation through a selected profile some POUs are already created but the user can create as many as he wants limited by the program memory size Table 2 5 To insert a new POU one must click using the mouse right button on Application default name created for the application select Add Object and POU as depicted on Figure 5 8 File Edit View Project Build Online Debug Tools Window Help Mg Ei46lo 4 BX MUIBTIS a a mela Neto Device NX3010 i PLcLogic Cut Copy Paste d p i 4 7 d Add Device External File Configur S neo Add Folder Global Variable List q Edit Object i Edit Object With a NO Login Library Manager Simulation Figure 5 8 Inserting POUs 191 5 Initial Programming A configurat
432. rant Deny Clear Everyone Key to the symbols For this group permission for the selected actions is s explicitely granted explicitely denied Not specified but granted by default not specified but denied by default Please note Members of the group Owner are granted all permissions Figure 4 85 Permissions Actions window shows all possibilities of rights it means all actions that can be executed in the project The tree is structured as follows e At the top of the tree are the names of some categories configured to visually organize access rights These categories refer to the Command implementation user accounts configuration and groups the creation of types of objects and also to view edit delete and treatment of secondary objects in the project Objects e F In each category we found nodes with specific actions that can be executed against the command user account group object type or object project These nodes have also just visual function Possible actions Run run a menu command Create create a new object in the current project Add or remove children of an existing object Modify editing an object in the editor Remove delete or cut an object View display of an object in the editor Each item action may contain devices that is objects the project The Permissions window provides a list of all available user groups except the Owner g
433. rces balance between communications and other tasks Transmission Delay the answer toa MODBUS protocol may cause problems in certain moments as in the RS 485 interface or other half duplex Sometimes there s a delay between the slave answer time and the physical line silence slave delay to put RTS in zero and put the RS 485 in high impedance state To solve this problem the master can wait the determined time in this field before sending the new request On the opposite case the first bytes transmitted by the master could be lost Minimum Interframe the MODBUS standard defines this time as 3 5 characters but this parameter is configurable in order to attend the devices which don t follow the standard The MODBUS Slave protocol diagnostics and commands configured either by symbolic mapping or direct representation are stored in T DIAG_MODBUS_RTU_SLAVE_1 variables For the direct representation mapping they are also in 4 bytes and 8 words which are described in Table 4 33 where n is the configured value in the Q Initial Address of Diagnostic Area field Direct p 2 i Diagnostic Variable nti DVRA T_DIAG_MODBUS_RTU_SLAVE 1 EEN pescripuon Diagnostic Bits QX n 0 bRunning The slave is in execution mode R The slave is not in execution see bit xaxa xaxa pNorR nNINg blnterruptedByCommand tDiag The bit bNotRunning was enabled as QX n 2 binterruptedByCommand BIT the slave was interrupted by the user th
434. re The members of each group can be viewed or not by the plus and minus sign respectively Remember that the member must be part of a group To add a new group use the Add button and open the corresponding dialog 170 4 Configuration Figure 4 83 Adding Group The following fields must be filled e Name the new group name e Description description of the new group Serves only as additional information e Members this list shows all users and groups Select those that should be part of the current group To configure the new group close the dialog with OK In the event of any inconsistency no name existing group select a group that would cause a group cycle an error message will appear To modify an existing group use the Edit button to open the Edit Group dialog The fields are the same as the Add Group dialog Figure 4 83 The password fields for security reasons produce 32 asterisks After changing the desired items close the dialog with OK to apply the new settings To remove one or more groups select the respective groups in the tree and press Remove Note that this action does not require confirmation Members of excluded groups remain unchanged You cannot delete the Everyone and or Owner groups If you try this an error message 171 4 Configuration Settings Page Setup users Groups gt i Security B SFC V Maximum number o
435. re of the redundant variables exchanged between the Active and Non Active PLC through the Redundant Data Synchronization and Redundant Forcing List services These two services must continue to working properly even while there are temporary differences between the PLCs 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 e Insertion of symbolic variables redundant or not within a POU or GVL existing or in a new POU or GVL e Removal of symbolic variables redundant or not within a POU or within existing GVL The removal of a POU or GVL can also involve the removal of symbolic variables e Change in size structure of symbolic variables redundant or not in an existing POU or GVL 280 6 Redundancy with NX3030 CPU Step 3 Previous Project Backup Before editing the modifications that must be loaded off line without interrupting the process control for safety reasons a backup of the project previous version must be run It may be necessary to reinstall the previous version in case an error is committed during this procedure executing ATTENTION The backup recommendation for all loaded versions in the PLCs may not be followed only in this specific procedure It must be a usual practice Step 4 Cares in Editing the Off line Downlo
436. reater than the addressable output memory size and the attributed values aren t the same already used during the application IEC Variable in case the MODBUS data type is Coil or Input Status bit the IEC variables initial address will be in the format for example Q10X 1 However if the MODBUS data type is Holding Register or Input Register 16 bits the IEC variables initial address will be in the format 7QW This field is limited by the memory size of the addressable output variables Q from each CPU which can be seen on the Technical Description Specific Features chapter Read only when enabled it only allows the communication master to read the variable data It does not allow the writing This option is valid for the writing functions only Default the default cannot be defined for the IEC Variable field as the creation of a protocol instance can be made at any moment within the applicative development making the MasterTool IEC XE software allocate a value itself from the direct representation output variables range Q 109 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 59 are related to the TCP communication filters Specifies a IP interval with writing access to the declared variables in the MODBUS relation s Specifies a subnet mask py e
437. rectly one must be aware of the following rules The number of NX5001 modules in each half cluster may vary between zero and four It can be defined up to 4 simple PROFIBUS networks or 2 redundant PROFIBUS networks respecting the limit of 4 PROFIBUS Master NX5001 modules in each half cluster When a PROFIBUS network is simple it needs a single NX5001 module in each half cluster When it s redundant it needs 2 NX5001 modules in each half cluster Two NX5001 modules used to form a redundant PROFIBUS network must occupy side by side positions in the rack The NX5001 modules quantity in the rack must be compatible with the number of existent PROFIBUS networks and with the redundancy attribute of each network on other words o 0x NX5001 No PROFIBUS network o 1x NX5001 One simple PROFIBUS network o 2x NX5001 In this case there are two options Two simple PROFIBUS network One redundant PROFIBUS network o 3x NX5001 In this case there are two options Three simple PROFIBUS networks One redundant PROFIBUS network and one simple PROFIBUS network o 4x NX5001 In this case there are three options Four simple PROFIBUS networks One redundant PROFIBUS network and two simple PROFIBUS networks Two redundant PROFIBUS networks After inserting or removing the NX5001 modules the configuration of the NX5001 modules remaining in the rack must be checked NX5001 Modules Parameters Adjust Each NX5001 module used in a simple PROFI
438. restarted and waits for the user to confirm the action Then a message indicating command success or failure will appear If there s success the CPU will be restarted ATTENTION The NX3030 CPU can t be in Run mode when this command is executed Before executing this command the user must put the CPU to Stop mode In case the CPU is in Run mode the command isn t executed and MasterTool warns the command has failed Just after executing the identification command with success it can be observed that the selected identification appears on the Redundancy Diagnostics on the NX3030 CPU Graphic Display The CPU identification is also available in an internal diagnostic DG_NX4010 tRedundancy RedDgnLoc sGeneral_Diag ePLC_ID This diagnostic is updated from the non volatile memory each MainTask cycle so it s necessary for the CPU to go back to Run mode to update it The codes returned by the diagnostics and their respective limitations are listed below e Non Redundant 0 e PLCA 2 e PLCB 3 271 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 In case one NX3030 CPU must be replaced e g af
439. riables are stored Addressable variables means that the variables can be accessed directly using the desired address For instance QBO QW100 Addressable output variables can be used for mapping digital or analog output points As reference 8 digital outputs can be represented per byte and one analog output point can be represented per two bytes The addressable output variables can be configured as retain persistent or redundant variables but the total size is not modified due to configuration The Nexto Series NX3030 CPU allows defining an area of redundant variables inserted inside of the addressable output variables Q The subset of addressable output variables memories are part of the total size of available memory Addressable variables memory M Area where the addressable marker variables are stored Addressable variables means that the variables can be accessed directly using the desired address For instance MBO MW100 Symbolic variables memory Area where the symbolic variables are stored Symbolic variables are IEC variables created in POUs and GVLs during application development not addressed directly in memory Symbolic variables can be defined as retain or persistent In these cases it will be used the memory area of retain symbolic variables memory or persistent symbolic variables memory respectively Retain symbolic variables memory Area where are allocated the retentive symbolic variables The retentive data k
440. ription Input Status 1 Digital input readonly Holding Register Input Register Table 4 35 Data types supported in MODBUS RTU Slave Analog output that can be read or written Analog input read only Data Initial Address data initial address of the MODBUS relation Data Size the Data Size value sets the maximum amount of data that a MODBUS relation can access from the initial address Thus in order to read a continuous range of addresses it is necessary that all addresses are declared in a single relation This field varies according to the configured type of MODBUS data Data Range this field shows the user the memory address range used by the MODBUS relation ATTENTION Differently from other application tasks when a depuration mark in the MainTask is reached the task of a Slave MODBUS RTU instance and any other MODBUS task will stop running at the moment that it tries to perform a writing in a memory area It occurs in order to keep the consistency of the memory areas data while a MainTask is not running MODBUS Slave Protocol Configuration via Direct Representation Q To configure this protocol using Direct Representation Q you must perform the following steps e Configure the general parameters of MODBUS slave protocol such as communication times address and direct representation variables Q to receive diagnostics and control relations e Add and configure MODBUS relations specifying the
441. rk The master mode communicating with slaves is assumed by the Active PLC The passive mode communicating with the active master is assumed by the Non bFailedPBUS2A Active PLC This failure can also be indicated in case the NX5001 module has a microprocessor failure or in case it can t communicate with the NX3030 CPU via bus FALSE There aren t failures in the PROFIBUS 2 A network TRUE This PLC can t communicate in the master state active or passive in the PROFIBUS 2 B network The master mode communicating with slaves is assumed by the Active PLC The passive mode communicating with the active master is assumed by the Non bFailedPBUS2B Active PLC This failure can also be indicated in case the NX5001 module has a microprocessor failure or in case it can t communicate with the NX3030 CPU via bus FALSE There aren t failures in the PROFIBUS 2 B network 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 bFailureProfibus_2 FailedPBUS2A and FailedPBUS2B In case the PROFIBUS 2 network isn t redundant FailurePROFIBUS_2 is a copy from FailedPBUS2A FALSE There aren t failures in the PROFIBUS 288 6 Redundancy with NX3030 CPU bProfibusVitalFailureAny bProfibusVitalFailureAll bTurnOffOtherPLC_Normal QB n 7 bTurnOffOthe
442. rk Mask 255 255 255 0 Gateway Address 192 168 15 253 Advanced Figure 6 13 Multiple IPs method 240 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 IP Address PLC B Active PLCB communication address when in Active state IP Address PLC B Non Active PLCB communication address when in Non Active state Subnetwork Mask Gateway Address NIC Teaming and Active IP Combined Use In case a determined port pair form a NIC Teaming in a redundant CPU these ports can implement at the same time the strategies NIC Teaming and Active IP E g if the NX3030 CPU NET 1 and NET 2 ports form a NIC Teaming pair then e IP Address PLC A IP address of the NET 1 NET 2 ports in the PLCA NX3030 CPU e IP Address PLC B IP address of the NET 1 NET 2 ports in the PLCB NX3030 CPU e IP Address Active IP address of the NET 1 NET 2 ports in the NX3030 CPU in the Active CPU This way the excellent availability from the NIC Teaming strategy is associated with the practicality of the Active IP strategy which doesn t need scripts in SCADA systems or in other clients connected to the Active CPU server Ethernet Interfaces Use with Vital Fault Indication The Ethernet ports of NX3030 and NX5000 modules can be configured to gen
443. rnet NET2 wProtocol Ethernet NET2 wProtocol bMODBUS_RTU_ETH_CI ient Ethernet NET2 wProtocol bMODBUS_ETH_Client Ethernet NET2 wProtocol bMODBUS_RTU_ETH_S erver Ethernet NET2 wProtocol bMODBUS_ETH_Server Ethernet NET2 wProtocol byReserved_0 Ethernet NET2 szIP Ethernet NET2 szMask Ethernet NET2 szGatewa y Ethernet NET2 szMAC Ethernet NET2 abyIP Ethernet NET2 abyMask Ethernet NET2 abyGatew ay Ethernet NET2 abyMAC Ethernet NET2 dwPacketsSent Ethernet NET2 dwPacketsReceived Ethernet NET2 dwBytesS ent Ethernet NET2 dwBytesReceived Ethernet NET2 wT XErrors Ethernet NET2 wT XFIFOErrors Ethernet NET2 wT XDropErrors Ethernet NET2 wT XCollisionErrors Ethernet NET2 wT XCarrierErrors Ethernet NET2 wRXErrors Ethernet NET2 wRXFIFOErrors Ethernet NET2 wRXDropErrors Reserved Reserved Indicates the link state in NET 2 Protocol selected in NET 2 00 Without protocol MODBUS RTU Client via TCP MODBUS TCP Client MODBUS RTU Server via TCP MODBUS TCP Server Reserved IP NET 2 Address NET 2 Subnet Mask NET 2 Gateway Address NET 2 MAC Address IP NET 2 Address NET 2 Subnet Mask NET 2 Gateway Address NET 2 MAC Address Counter of packages sent through NET 2 port 0 to 4294967295 Counter of packages received through NET 2 port 0 to 4294967295 Counter of bytes sent through NET 2 port 0 to 4294967295 Counter of bytes received through NE
444. rnet networks configured as vital cause a switch to the Inactive status A total failure in an Ethernet network reaches the two networks that comprise enabled Communication 244 6 Redundancy with NX3030 CPU Redundancy option or the only network that compose Redundancy option disabled Communication Inactive State This state is normally reached after some failure types or due to a manual request before a programmed maintenance PROFIBUS masters are enabled in the passive state The passive mode is used to test the transmission and reception PROFIBUS circuits and the physical layer to avoid an occult failure to happen Before switching to another state first the diagnosed failures must be corrected or the programmed maintenance executed if those have driven the CPU to Inactive state After a transition for the Not Configured state must be done requesting a configuration Then a switch to the Starting state must be executed After the Starting state the CPU can Return to the Inactive state if determine failure types remain Return to the Not Configured state in case of other failure types Go to Stand by state if the other CPU is in Active state Go to Active state if the other CPU isn t in Active state PX2612 Redundancy Command Panel Functions The PX2612 redundancy command panel is shown on Figure 6 4 while Figure 6 5 shows its frontal view with more details Besides this Figure 6 6 shows how this panel must
445. rom the IEC 61131 3 standard The intervals and task trigger events can be configured by the developer and the unnecessary task can be eliminated 185 5 Initial Programming Expert Custom Task POU Priority Type interval Event Maintask Mang 13 Cyoic 100ms CyolioTaskoo CyclicPrgoo 13 Cyoic 200ms CyclicTask01 CyclicPrg01 13 Cyeie sooms ExternInterruptT ask0O ExternInterruptPrg00 o2 exten o IO_INT_O TimelnterruptTaskoo TimelnterruptPrgo0 01 leya 20ms Table 5 5 Normal Profile Tasks The Expert project profile includes the same basic tasks MainTask CyclicTask lt nn gt ExternInterruptTask00 and TimelInterruptTask00 with the same priorities but it is an expansion comparing with the previous profiles as it allows multiple event tasks Therefore the application can include several ExternInterruptTask lt nn gt or TimelInterruptTask lt nn gt tasks executing the ExternInterruptPrg lt nn gt and TimelInterruptPrg lt nn gt programs The event tasks additional priorities can be freely selected from 08 to 12 In this profile besides the standard programs each task can execute additional programs In this project profile the application can also include the user task FreeTask from the Freewheeling task with priority 31 responsible for the FreePrg program execution As this task is low priority it can be interrupted by all others so it can execute codes that mi
446. ror s 1 warning s 10 message s Lastbuid 0 1 Precompie NI Current user nobody Figure 5 36 Simulation Mode In Simulation mode the application runs on a virtual device in the computer where the MasterTool IEC XE is installed For this reason some presented characteristics are related to the architecture of hardware computer not of Nexto Series CPUs The main feature in this sense is related to the format of the data in memory areas of direct representation The Simulation Mode works with little endian format where the first memory address is the least significant of the data On the other hand the Nexto Series CPUs work with big endian format where the first memory address is the more significant of the data In this case the same written data for example in QD0 will be written differently in the simulation and in the CPUs of Nexto Series If the written data is 16 1234ABDC the distribution of data in the PLC memory will be as follows FQWO 16 1234 QW2 16 ABCD QBO 16 12 QB1 16 34 QB2 16 AB e QB3 16 CD For the same written data in QD0 on Simulation Mode the data distribution in memory will be as follows QWO0 16 ABCD JQW2 16 1234 QBO 16 CD QB1 16 AB oQB2 16 34 e QB3 16 12 Considering these differences and in order to facilitate the application development using the MasterTool IEC XE and the Nexto Series resources it is recommended to use symbolic variables In this c
447. rough command bits QX n 3 3 bConfigFailure Discontinued diagnosis 80 4 Configuration axma 4 bRXFailure BIT Discontinued diagnosis QX n 5 bTXFailure BIT Discontinued diagnosis QX n 6 bModuleFailure BIT Discontinued diagnosis Error codes QB n 1 there is no error invalid serial port invalid serial port mode invalid baud rate invalid data bits invalid parity invalid stop bits invalid modem signal parameter invalid UART RX Threshold rameter invalid time out parameter serial port busy UART hardware error remote hardware error invalid transmission buffer size invalid modem signal method time out of CTS true time out of CTS false transmission time out error invalid reception buffer size reception time out error 32 flow control configured differently from the manual 33 invalid flow control for the configured serial port 34 data reception not allowed in the normal mode 35 data reception not allowed in the extended mode 36 DCD interruption not allowed 37 CTS interruption not allowed 38 DSR interruption not allowed 39 serial port not configured 50 internal error in the serial port SERIAL_STATUS eErrorCode BYTE Command bits initialized Stop slave Restart slave Restart diagnostics statistics counters KTD 0 amat 1 bRestart ema 2 bResetCounter aX n 2 3 EAR Command bDiag_19_reserved omman
448. roup and a toolbar to set access rights to the group To the left of each group name are icons indicating the current permission for the selected device in the Actions window e F the currently selected action in the Actions window is guaranteed to the group e the currently selected action in the Actions window is denied to the group e the right to perform one or more actions selected in the Actions window is not guaranteed explicitly but by default due to that right has been guaranteed to the main object Basically this is the default setting for all rights not been explicitly configured 173 4 Configuration the right to perform one or more actions selected in the Actions window is not explicitly denied but by default for example in cases where that right has been assigned to the main object The icons are not displayed if several actions are selected without the unique settings for the selected group right now To set up the rights to a group select the action and the desired group in the Shares and permissions windows respectively After use the appropriate buttons in the window s toolbar permissions e Parant Ensure explicitly e Deny Deny explicitly Clear The rights guaranteed to the currently selected action in the Actions window will be deleted return to the default setting User Management and Access Rights of the CPU Nexto CPUs have user permissions management system which blocks o
449. rt touch on the diagnostic key the digits are incremented and with a long touch are confirmed At the sixth confirmed digit the CPU will consider the password and begin the process When both the passwords from the application which is in the CPU and from the application which is in the memory card are equal it is not requested the passwords insertion in the CPU menu in order to make the application transferences For further information regarding the diagnostic key utilization see One Touch Diag chapter To remove the memory card press the MS button with a long touch and wait until the card icon disappears from the status screen on the graphic display ATTENTION If there is any file at memory card root named NextoMemCard or Backup it will be deleted to create the system folders with the same name used by the CPU to store the project application and the project archive Folders with these names will not be overwritten 125 4 Configuration MasterTool Access The memory card access is connected to the same user memory screen in the MasterTool IEC XE software being it mounted in the folder called Memory Card NextoMemCard and Backup folders are created into the memory card every time the latter is inserted into the CPU In case these folders already exist the system will recognize them and will not overwrite the folders Configuration Bus J Device x X Communication Settings Fis L
450. run the command to pass the CP to the Idle state and then the command to move the CP to the state reserve When this sequence is performed this CP will assume the Active e The other CPU state is known and different than Active First Instants in Active State Common In the first 2 seconds in Active state as already described in PX2612 Redundancy Command Panel Functions section the LED ACTIVE blinks and remains on after this time has passed While the LED ACTIVE blinks several transitions which usually could take the CPU from the Active state aren t analyzed see previous sub sections that define transitions from the Active state E g during this time it doesn t work to press the STAND BY button to try and make the CPU go to Stand by state Only two conditions allow the CPU to go out of the Active state while the LED ACTIVE blinks They are the following e This PLC was switched off or restarted warm reset cold reset or origin reset causing a transition to Not Configured state e Both PLCs for some reason are in Active state and this conflict must be solved The PLCA switches to Stand by state in case this conflict remains The PLCB does the same after a delay smaller than PLCA This way in this case PLCA has priority to remain in Active state Furthermore in the very first instants that a PLC assumes the Active state some non redundant diagnostics may not be valid such the diagnostics of the NX5000 and NX5001 modules
451. s Storage capacity of the Memory Card in Kbytes Informs the abnormal situation in the bus which caused the application stop for each mode of hot swapping See Table 7 9 for more information Reserved 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 O equivalent to position 0 So it is performed a OR logic operation among four summarized diagnostics and the operational state of a certain position and if the result is positive the analogic bit will be true Under the considered diagnostics Incompatible configuration bConfigMismatch Absent modules bAbsentModules Exchanged modules bSwappedModules Modules with fatal error oModuleFatalError Module is not in Operational Mode Status of presence of declared I O 7 Maintenance yy QB n 503 QB n 630 QB n 630 QB n 504 QB n 631 QB n 631 QX n 505 0 QX n 632 0 QX n 632 0 A QX n 633 0 QX n 633 0 QB n 634 QB n 634 QW n 635 QW n 637 QD n 639 QB n 643 QB n 644 ae oe ee oe QB n 650 BYTE QW n 635 QW n 637 QD n 639 QB n 643 QB n 644 N N N N N N N N N N N N N QB n 651 QB n 651 QB n 654 QB n 654 A A A A A A A A A A A A A A 314 adwModul
452. s s address can be found on the back cover Altus is not responsible for supplying information about its equipment without formal request COPYRIGHTS Nexto Ponto Series MasterTool Quark ALNET and WebPLC are the registered trademarks of Altus Sistemas de Automa o S A Windows NT 2000 and XP are the registered trademarks of Microsoft Corporation These products use EtherCAT technology www ethercat org OPEN SOURCE SOFTWARE NOTICE To obtain the source code under GPL LGPL MPL and other open source licenses that is contained in this product please contact opensource altus com br In addition to the source code all referred license terms warranty disclaimers and copyright notices may be disclosed under request Summary Table of Contents COV RIG UTES ei orcs A Pes aoe ore as oa ooo oh sees oh A A ou due su cb dub eu cb duu en AAA i OPEN SOURCE SOFTWARE NOTICE o cccesscadacesscadacesscadacesscadaceiscadacesssataceisssiaseissaiataisssiassssestvecvastensseneass i 1 INTRODUCTION co cseccceccceletecncuistecnclistecevscedccsvecddvcstsctdvestscsdvesdscddvesdscsdscddscsdscsdecevsesdssvecsdcssvcessvcsdsestvesteesdecs 1 Nela SONICS boecciccicctecccecccucctecctecctcactucctccstuccivectuccivcctuccivcctuccivcctucctvcc vccUvcc vccOvocdvccOvoc vccvec vccdvec vcccsevevesevevesccce 2 Mova Ve Fea ULES aa oar rss toss ascsa woe an ess a sot Ts ss a SS TSN San DIR NTE aT RAEN 3 Documents Related to this Manual cccccsssssssss
453. se the type of Ethernet network of the CPU o Single Network with Failure Mode Disabled do not generates switchover in failure case o Single Network with Failure Mode Enabled generated switchover in failure case o Redundant Network with Failure Mode Disabled operates in conjunction with the other interface and do not generates switchover in failure case o Redundant Network with Failure Mode Enabled operates in conjunction with the other interface and generates switchover in failure case Choose the amount of Ethernet networks In this case the Wizard allows the user to create up to four single networks or up to three redundant networks or none It s important to stress that this is only the architecture proposed by the Wizard After that MasterTool allows the creation up to six networks total three redundant maximum always respecting the maximum limit of six Ethernet modules NX5000 in each half cluster Select the Ethernet network type o There s none no NX5000 module allocated o Single Network with Failure Mode Disabled allocates one NX5000 and do not generates switchover in failure case o Single Network with Failure Mode Enabled allocates one NX5000 and generates switchover in failure case o Redundant Network with Failure Mode Disabled allocates two NX5000 and do not generates switchover in failure case o Redundant Network with Failure Mode Enabled allocates two NX5000 and generates switchover in failure case
454. sistencies done with success I O modules are being prepared to system startup Not possible to set the Application to Run Mode NORMAL_OPERATING_STATE Application in Run Mode 10 MODULE_CONSISTENCY_OK Internal Use APPL_STOP_DUE_TO_EXCEPTION Application in Stop Mode an exception occurred in the CPU DUPLICATED_SLOT_HOT_SWAP_DISABLED Application in Stop Mode due to Duplicated Slot diagnostic activation when hot swap is configured as disabled or disabled for declared modules only DUPLICATED_SLOT_HOT_SWAP_STARTUP_CON Application in Stop Mode due to Duplicated Slot SISTENCY diagnostic activation when hot swap is configured as enabled with startup consistency or enabled with consistency in the start only for declared modules DUPLICATED_SLOT_HOT_SWAP_ENABLED Application in Stop Mode due to Duplicated Slot diagnostic activation when hot swap is configured as enabled without consistency in the start NON_DECLARED_MODULE_HOT_SWAP_START Application in Stop Mode due to Non Declared diagnostic UP_CONSISTENCY activation when hot swap is configured as enabled with startup consistency NON_DECLARED_MODULE_HOT_SWAP_DISABL Application in Stop Mode due to Non Declared activation ED diagnostic when hot swap is configured as disabled Table 7 9 Code Situations that May Cause Application Stop o N 3 Code 00 01 o9 10 Diagnostics via Function Blocks The function blocks allow the visualization of some p
455. ssable input I addressable output Q addressable memory M data memory and redundant data memory For applications that require non volatile functionality Nexto Series CPUs bring retain addressable memory Q retain data memory persistent addressable memory Q persistent data memory program memory source code memory CPU file system doc PDF data and memory card interface One Touch Diag TM One Touch Diag is an exclusive feature that Nexto Series brings to PLCs With this new concept the user can check diagnostic information of any module present in the system directly on CPU s graphic display with one single press in the diagnostic switch of the respective module OTD is a powerful diagnostic tool that can be used offline without supervisor or programmer reducing maintenance and commissioning times OFD On Board Full Documentation Nexto Series CPUs are capable of storing the complete project documentation in its own memory This feature can be very convenient for backup purposes and maintenance since the complete information is stored in a single and reliable place ETD Electronic Tag on Display Another exclusive feature that Nexto Series brings to PLCs is the Electronic Tag on Display This new functionality brings the process of checking the tag names of any I O pin or module used in the system directly to the CPU s graphic display Along with this information the user can check the description as wel
456. ssneeecessseeeesessaeeceessaeeecsesaeeesessaeeesessaeeseesaeees 274 Off Line Download of Modifications with Process Control Interruption ceceeesseeceeseseeeeeeeneeees 275 Previous Planning for Off Line Modifications without Process Control Interruption eee 276 Exploring the Redundancy for Off Line downloading of Modifications without Interruption of the PLOCESS CONUTOL 2 sass ishsevascsaseessisenssastossastoesbeseuseshonstanracrousssapuscsactondesuchssssoude eessustiapaoueesapasbespaenseseetens 279 IVESUTALOTIATIC Os cissie eeaeee e aeanoea aaeeea eataa oaae eeaeee a asaos 284 Modules Hot Swapping in a Redundant PLC esseeesseeesessressssrerssrresssrressssreesssrresssrrersereesssrressereessst 284 Master Tool Warning Messages annononener sridi e e a Ee T a 284 Redundancy Diagnostics on the NX3030 CPU Graphic Display seeeeeeeeeeeeeeeeeeserrerserrresssrrerserrerseres 285 Redundancy Diagnostics Structure seeesesseeessseeesesrersssreesssrierssrtesssrteessrteerssteessstiesssrieesssteesssteessetet 285 PX2612 Panel Nest antenna nasa eae aa Rotem E EEEE eE E E 296 Tae WEAN PENANG Eivcs svsssssscssnsocssudecucvuncececesedscvasdedtdess dese decsiecucscsdeuscsdedssdeuedecuceesisdudtdedsdetsdetadeoscssuisduapinsninindsun 299 Module Diad nOStics visicivecessccsscissssvecevecsecssecsvsccnscenscsseecusecssdanscsteeeveosuscuecsstecesoueesdensesteceseseusceueccssssdeuseosssees 299 One Touch Diase wns anes Res eee ae ae ae el oe ne ae A
457. ssscccscess 21 TP AGGIES Saini sane yova ane soviet aa ae ae eA INN RONAN 21 Gratuitous AR Pies sc swagiexsivtinrsoassiaxssavanasavavananaaavanasaaasavangoasavanseasanaranaa snare vananava anatase E a a 22 Network Cable Installatiom cvccissssvssasssestassscssiasess enesan es sash ones snebon 0s se baan ss anes aa es ieee ses Shae Os Shoe O EEANN 22 Serial Network Connection COM1 ccccccccccssssssssssscccccccssscsssssccccccceeescsscccccccceeccesscccccccceeecccssccccsoeeees 23 RS 232C Communi CattOMs asc cisssrrreecrarracrsrarnavesrarascarsararereanrad ancerrareerrresssnerravseenrravacendarsererraverrardaresernete 23 Serial Network Connection OIMI2 osccccce oescccsscccscccccvsccccscssacacscvescesasesecccedssessdedeveccsudssedstesevacsevessesstsceeseoce 24 RS 485 Communication without termination cccccccccceeecccceesecccceesecceceseccseusecscuueceseueeceseueeeceeuees 24 RS 485 Communication with Internal Termination ccccccccccccccessecccceeseccceeeecscueeccseueeeceseueeeseeuees 25 RS 485 Communication with External Termination cccccccccccccessscccceseccceesecsceeeceseueseceseueeeceeeees 26 RS 422 Communication without Termination ccccccccccecccceesecccceessccccueseccceusececuueceseueeeceseueeeceeuens 27 RS 422 Communication with Internal Termination ccccccccccccccessscccceseccceesececeeeceseueseceeeueeeceeuues 28 RS 422 Communication with External Termination cccccccc
458. ssssssscsssccscsssscssccscccsssssccscccssssssccscssscccccssssssccssscscccccses 5 Visual Ns Pe Chios 2 o5 ss S he casecscasesschccccaocscvenasersvevenenevasencessencscesseusoabes sonsenessossensecoatensoevancasoeneuensocecssesocnsoses 6 Mechnical SUppPOre c lt 2 25 ccsevsesscsevescesosvescosveseseseucsossvsucseesvonceesssbscsesssecvessevesvossesvcseacssvcssesvsscatesvossaceevesseseessees 6 Warning Messages Used in this Manual scccccssssssssssssscccssssssssssscccscssssssssscccscscsssssssssccssssssssssssssssssees 6 27 5 TECHNICAL DESCRIPTION ssccescciscscossieseicseiaseics ea seecs sees SASAE AONO A SLEA ON SASAE AONO A SAAANA AUS CONCURA SURUS URUS UAA en eee eee 7 Panels And Connections v ccccccccccccccccccscececccscesscccscesscccscesscccscesscsvscesscccssesscscssesscccscecscccdcesscccccccsccccecsscecececececese 7 General FeaturesS eeeccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccceccccccccccccccccceccccccccccccccccccccccccccccceccceee 9 Common General FeatteS eiric eette esT eE eei AET EEE AEE EEEE EREE AE EEE EE Eek 9 Specific Peaturesy 2 c e tersveversreeovevabeevkssabaeels eb eee ee ee eee e urbensbanrbeebbaaubenbbauebetbbepbeetberserneests 10 Se tial Interfaces nnana a aaa aaa a a a a aa aa a aa aAa 13 Ethernet Intertaces 2 cssssenssesexes e E EEE E E E EEN E EES 14 Memory Card Jnterfad e nigiri tiia E EEEE EEEE EA a 15 Compatibility with Other Products ssoooossoossssoosssssosesssocsessoes
459. stance 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 Slave address according to the MODBUS standard the valid address range for slaves is 0 to 247 where addresses 248 to 255 are reserved When the master sends a command of writing with the address set to zero it is performing broadcast requests on the network The parameters in the advanced settings of the MODBUS Client device found on the button Advanced in the General Parameters tab are divided into maximum number of concurrent requests Time out Time out Mode of Connection and Downtime Maximum Simultaneous Number of simultaneous Requests request the client can ask from 1 1108 q the server Communication Time out Application level time out in ms 3000 10 to 65535 Connection is never closed in normal situations r Connection is BDA Defines when the connection cl sedafter n Connection is closed at the a server finished by the inactive time of end of each communication s 10 to 3600 Connection is closed after an inactive time of s 10 to 3600 Table 4 43 MODBUS Client Advanced Configurations 91 4 Configuration Notes Maximum Simultaneous Requests it is used with a high scan cycle This parameter is fixed in 1 not editable when the configured protocol is MODBUS RTU via TCP Communication Time out the Communication time out is the
460. t for the library insertion proceeding see Libraries chapter My EFFST EFF3ST MaxEFFST MinEFFST ErrorCode IntegralAction Figure 4 63 PID Block Input parameters Set point SP The unit and the interval must be the same in comparison with the PV as both variables can be compared Process variable PV The unit and the interval must be the same in comparison with the SP as both variables can be compared G Proportional gain used to calculate the PID block P proportional action Td Derivative time in seconds used to calculate the PID block derivative action 3 Integral time in seconds used to calculate the PID block integral action Compensation added to the handled variable Value attributed to the manipulated variable when ManualMV using the manual mode Manipulated variable maximum variation between the actual cycle and the previous cycle In case is Mesa zero or negative the PID block has no MV variation limit Manipulated variable maximum value MaxMV In case the calculated value is higher than the configured the MV will be the same as MaxMV Manipulated variable minimum value MinMV In case the calculated value is smaller than the configured the MV will be the same as MinMV 148 4 Configuration Dead band Minimum error value able to generate a MV DeadBand correction in automatic mode in other words little errors Smaller than the DeadBand won t cause any variation in the defined
461. t NET1 Counter of received bytes through dwBytesReceived NET 1 port 0 to 4294967295 Counter of errors of transmission through NET 1 port 0 to 65535 Counter of errors in the buffer of transmission through NET 1 port 0 to 65535 Counter of connection losses in the transmission through NET 1 port 0 to 65535 Counter of errors of collision in the transmission through NET 1 port 0 to 65535 Counter of errors of the carrier in the transmission through NET 1 port 0 to 65535 Counter of errors of reception through NET 1 port 0 to 65535 Counter of errors in the buffer of reception through NET 1 port 0 to 65535 Counter of connection losses in the reception through NET 1 port 0 to 65535 Counter of errors of frame in the reception through NET 1 port 0 to 65535 Counter of multicast packages through NET 1 0 to 65535 Ethernet NET 1 dwPackets QD n 183 QD n 183 QD n 183 DWORD Received QD n 187 QD n 187 QD n 187 DWORD QD n 191 QD n 191 QD n 191 DWORD QW n 195 QW n 195 QW n 195 WORD Ethernet NET1 wTXErrors Ethernet NET1 QW n 197 QW n 197 QW n 197 WORD WTXFIFOErrors Ethernet NET1 QW n 199 QW n 199 QW n 199 wTXDropEtrors Ethernet NET1 O QW n 201 QW n 201 QW n 201 wTXCollisionErrors Ethernet NET1 O QW n 203 QW n 203 QW n 203 wTXCarrierErrors QW n 205 QW n 205 QW n 205 Ethernet NET1 wRXErrors Ethern
462. t Networks with NIC Teaming Figure 6 1 shows two redundant Ethernet networks examples with NIC Teaming In the first case the NX3030 CPU connects to the supervision network SCADA also used for configuration through MasterTool Both NX3030 CPU Ethernet ports NET 1 and NET 2 forma NIC Teaming redundant pair interconnected in two different switches Ethernet A and Ethernet B In some point these two switches must be interconnected for the two NIC Teaming ports connection and for an even higher availability against double failures In the second case two NX5000 modules also form a NIC Teaming redundant pair interconnected in two different switches Ethernet HSDN A and Ethernet HSDN B In some point these two switches must be interconnected for the two NIC Teaming ports connection and for an even higher availability against double failures Such Ethernet architectures turn possible an excellent availability against Ethernet port failures in cables and switches ATTENTION If two modules or Ethernet interfaces form a NIC Teaming redundant pair the configuration and device inclusion will be only possible in the first interface The second interface will have his configuration parameters blocked for edition A cluster of two Ethernet ports forming a NIC Teaming pair has a single IP address related to the port pair This way a client as SCADA or MasterTool connected to a CPU server doesn t need to worry in IP address cha
463. t RX queue local and remote The UART RX FIFO is restarted too SERIAL_PURGE_RX_QUEUE Figure 4 56 Block Used to Clean the RX Queue Input parameters REQUEST BOOL This variable when true enables the function block use Select the serial port as described in the PORT SERIAL_PORT SERIAL PORT data type Table 4 86 SERIAL_PURGE_RX_QUEUE Input Parameters BOOL This variable is true when the block is completely executed It s false otherwise This variable is true while the block is being i BOOL executed It s false otherwise This variable is true when the block concludes the execution with an error It s false otherwise PRROR BOOS It is connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are STATUS SERIAL_ STATUS NO_ERROR ILLEGAL_SERIAL_PORT PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE NOT_CONFIGURED Table 4 87 SERIAL_PURGE_RX_QUEUE Output Parameters Utilization example in ST language after the library is inserted in the project and the serial port configured 138 4 Configuration PROGRAM MainPrg VAR Purge Queue SERIAL PURGE RX QUEUE Port SERIAL PORT COM1 Status SERIAL STATUS
464. t allow spaces special characters and start with numeral character It s limited in 24 characters Disabling Area of Mappings composed of 32 bits used to disable individually the 32 MODBUS relations configured in Device Mapping space The relation is disabled when the bit corresponding to relation is equal to 1 otherwise the mapping is enabled This field is limited by the size of outputs variables Q addressable memory of each CPU which can be found in chapter Technical Description Default Value the factory default value cannot be set to the Disabling Area of Mappings field because the creation of a Protocol instance may be held at any time on application development The MasterTool IEC XE software itself allocate a value from the range of output variables of direct representation Q not used yet For further details on the slave address time out and maximum number of retries parameters see notes in section Devices Configuration Configuration for Direct Representation Q 76 4 Configuration Mappings Configuration Configuration for Direct Representation Q The MODBUS relations settings viewed in Figure 4 17 and Figure 4 18 follow the parameters described in Table 4 30 az Coil Figure 4 17 MODBUS Data Type MODBUS Device Map ing_000 Function Read Settings Read zj Read Data Stat Address Read Data Size Read Coils FC 1 1 aj fi Polling ms Re
465. t diagnostics statistics bResetCounter BIT counters QX n 2 4 bDiag_20_reserved BIT 67 4 Configuration bDiag_21_reserved BIT Reserved awas bDiag_22_reserved BIT Reserved bDiag_23_reserved BIT Reserved byDiag_03_reserved BYTE Reserved Communication Statistics Counter of request transmitted by the master 0 to 65535 QW n 6 wRXNormalResponses WORD ee received QW n 8 wRXExceptionResponses WORD QW n 10 wRxillegalResponses WORD tStat QW n 12 wRXOverrunErrors WORD QW n 14 wRXIncompleteFrames WORD QW n 16 wCTSTimeOutErrors WORD QW n 4 wT XRequests WORD Counter of responses with exception codes received by the master 0 to 65535 Counter of illegal responses received by master invalid syntax not enough received bytes invalid CRC 0 to 65535 Counter of overrun errors during reception UART FIFO or RX line 0 to 65535 Counter of answers with construction errors parity or failure during reception 0 to 65535 Counter of CTS time out error using RTS CTS handshake during transmission 0 to 65535 QW n 18 WORD Table 4 21 MODBUS RTU Master Diagnostics Note Counters All MODBUS RTU Master diagnostics counters return to zero when the limit value 65535 is exceeded Devices Configuration Symbolic Mapping configuration The slave devices configuration shown on Figure 4 12 follows the parameters below Mappings Requests General Parameters Settin
466. t indicated The NextoStandard library has the appropriate interfaces for writing and reading the system s date and hour accordingly and for informing the correct diagnostics 121 4 Configuration User Files Memory Nexto Series CPUs have a memory area destined to the general data storage in other words the user can store several project files of any format in the CPU memory This memory area varies according to the CPU model used check Technical Description Specific Features chapter In order to use this area the user must access a project in the MasterTool IEC XE software and click on the Devices Tree placed at the program left Double click on the Device item and after selecting the CPU in the Communication Settings tab which will be open select the Files tab and click on Refresh both in the computer files column left and in the CPU files column right as shown on Figure 4 45 Configuration Bus J Device x X Communication Settings Fies 3 Log Users and Groups Access Rights Information Host Location J C Temp Runtime Location z a Name Size Modified Name Size Modified t 4 MemoryCard d Others E InternalMemory E xXtorm be 428 bytes 9 1 2014 6 19 PM device devdesc xml 233 17 KB 238 768 9 29 2014 4 39 PM Nexto bt 226 bytes 10 2 2014 12 52 PM Figure 4 45 User Files Access After updating the CPU column of files the root directory of files stored in the CPU w
467. t use turning possible a higher flexibility at the program development However some specific resources depending on the Nexto CPUs hardware are not possible to be simulated The resources unavailable in the simulation mode are the following RTC Clock Bus Scan T O Modules Bus Event Serial Ports Ethernet communication Communication protocols such as MODBUS PROFIBUS Interface PROFIBUS Slave Operations on memory card Diagnostics in variables Diagnostics Explorer Other functions that access the PLC hardware For this reason the simulation mode has to be used to test the application logic not depending on hardware access functions These resources have to be tested with the hardware to ensure the functioning of the application in this way In order to change the MasterTool IEC XE for Simulation Mode it is necessary to select this option in the Communication Menu as shown in Figure 5 36 After that it is displayed a warning at the bottom bar of the IEC MasterTool XE indicating that the tool is operating in Simulation Mode 212 5 Initial Programming Ble Edit View Project Build Online Bsa a a mi E F a 100 g 100 200 300 400 500 600 700 800 300 1000 1100 be ror Main HJ Configuration Bus LY Simulation J nx3030 3030 NX9002 00 Z 2 jessages Totally 0 er
468. te his own protocols and handle the serial ports as he wishes following the IEC 61131 3 languages available in the MasterTool IEC XE software The blocks are available inside the Nexto Serial library which must be added to the project so it s possible to use them to execute the library insertion procedure see Initial Programming Libraries The special function blocks for serial interfaces can take several cycles consecutives calls to complete the task execution Sometimes a block can be completed in a single cycle but in the general case needs several cycles The task execution associated to a block can have many steps which some depend on external events that can be significantly delayed The function block cannot implement routines to occupy the time while waits for these events because it would make the CPU busy The solution could be the creation of blocking function blocks but this is not advisable because it would increase the user application complexity as normally the multitask programming is not available 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 Datatype Potions escription SERIA
469. ted POU the desired task must be accessed through a double click on it in the device tree and the Add POU option selected After this a screen called Input Assistant will appear on the screen where the desired POU must be selected as shown on Figure 5 14 196 5 Initial Programming Input Assistant ea Categories Items Programs Em Type Origin Application plicat E MainPrg GRA V Structured view V Show documentation Documentation PROGRAM MainPrg Figure 5 14 Connecting POUs to Tasks Maximum Number of Tasks The maximum number of tasks the user can create is only defined for the Custom profile the only one which has this permission The others already have their tasks created and configured Table 5 10 describes the maximum IEC task quantity per CPU and project profile where the protocol instances are also considered communication tasks by the CPU 197 5 Initial Programming NX3010 NX3020 NX3030 Task Type SS ae n e c m sj s nj e c m s s nfEe c m oxa oe o SR peo dts fis fos 2 ffs es eo as fe fs ot ot ot 2 oo SEBO oDooR ee User Ta reesen ols e s e e e i ee o e o e fo Femeia Jojifofifsloelehi teelle alo n ee el rede le ar ae eee eee eee eee NETs Client or Server Instances TOTAL Table 5 10 IEC Tasks Maximum Number Notes Profile Legend The S B N E C and M letters correspond to the Single Basic Normal
470. ted and in the state the updating is disabled To no longer show the Logs press It is possible to filter the Logs in 4 different types Warning s Error s Exception s and Information s Another way to filter the messages displayed to the user is to select the component desired to view It is important to stress that the timestamp from the Logs will always be according to the UTC time For further information about the System Logs please check the MasterTool IEC XE User Manual MU299048 Note CPU System Log The system logs for the Nexto Series CPUs NX3010 NX3020 and NX3030 are not reloaded in case of a CPU reboot or a restart of the Runtime that is it will not be possible to view the oldest logs when one of these conditions occur Not Loading the Application at Startup If necessary the user can choose to not load an existing application on the CPU during its startup For it just energize the CPU with the diagnostics button pressed and keep it pressed for at least two seconds During the CPU startup it will be shown on the display a message warning that the application will not be loaded and will start in Stop Mode If a login is made the MasterTool IEC XE software will indicate that there is no application on the CPU For reloading the application the CPU must be reset or a new application download must be done Power Supply Failure The Nexto Series Power Supply NX8000 has a failure detection system according to the le
471. tem Overview Fimware Update System Overview Rack View Figure 7 4 System Information When the module with diagnostics is pressed the module active s diagnostic s are shown as illustrated on Figure 7 5 ATTENTION When a CPU is restarted and the application goes to exception in the system s startup the diagnostics will not be valid It is necessary to fix the problem which generates the application s exception so that the diagnostics are updated M altus System Overview System Overview E OE To saan ie pe eon tte Diagnostic OTD switch error Figure 7 5 System Diagnostics 304 7 Maintenance In case the Status tab is selected the state of all detailed diagnostics is shown on the screen as illustrated on Figure 7 6 4 English Espa ol Portugu s altus A System Overview Updates on Sth August 2012 19 02 26 To refresh this page click on the icon Status list gt gt Rack 0 gt gt NX3030 Slot 2 Status CONFIG There are not errors in bus configuration CONFIG There are not declared modules absent in the bus CONFIG There are not swapped modules in the bus CONFIG There are not non declared modules present in the bus CONFIG There are not modules with active diagnostics CONFIG There are not modules in non operational state CONFIG There are not modules with parameters error in the bus CPU Bus access hardware is operational CPU Internal hardware is operatio
472. ter a damage the new CPU must be previously identified with the same identification of the damaged one The CPU display must be used to verify if both CPUs are correctly identified Fifth Step Redundant Project Downloading This step describes the redundant project downloading in the CPU This project must be prepared according to the Redundant CPU Programming section A simple project basic can be prepared following at least the next sub sections presented in this section e Wizard for a New Redundant Project Creation e Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 Obviously it s also possible to build a complete project and only later download it in the PLCA and PLCB for instance in case these CPUs hardware aren t available during the project developing in MasterTool The first download of a redundant project in a CPU previously identified as PLCA or PLCB still must be done using the IP address discovered in the first step and selecting the third step of this procedure The project download is run through the Online Login menu ATTENTION Inside the developed project using MasterTool and downloaded in the CPU in this step were defined new IP addresses for the NET 1 interface in the PLCA and PLCB IP_A_1 and IP_B_1 as well as a IP address for the NET 1 interface in the Active CPU IP_Active_1 see Ethernet Ports Configuration in the CPU NX3030 NET 1 and NET 2 section Therefore aft
473. tes project data reception For further information about the project synchronization see Project Synchronization section Besides the characters described above Nexto CPUs can present some messages on the graphic display correspondent to a process which is being executed at the moment Table 7 12 present the messages and their respective descriptions 319 7 Maintenance FORMATTING Indicates the CPU is formatting the memory card FORMATTING ERROR Indicates that an error occurred while formatting the memory card by the CPU WRONG FORMAT Indicates that the memory card format is incorrect INCORRECT PASSWORD Indicates the typed password is different from the configured password TRANSFERRING Indicates the project is being transferred TRANSFERRING ERROR Indicates there is been an error in the project transference caused by some problem in the memory card or its removal during transference TRANSFERRING COMPLETE Indicates the transference has been executed successfully TRANSFERRING TIMEOUT Indicates a time out has been occurred communication time expired during the project transference Message CPU TYPE MISMATCH Indicates the CPU model is different from the one configured in the project within the memory card Indicates the CPU version is different from the one configured VERSION MISMATCH in the project within the memory card APPLICATION CORRUPTED Indicates the application within the memory card is corrupted Indicat
474. the PLCA and another for the PLCB Each CPU will consider the correspondent one after analyzing its identification register Redundant Project Structure Redundancy Template A redundant CPU project is created automatically from a model called Redundancy Template The template starts from the minimum redundant CPU configuration as defined in the Minimum Configuration of a Redundant CPU section Besides this some dialogs with the user are made for the insertion of additional modules in the half clusters such as PROFIBUS masters NX5001 and Ethernet modules NX5000 PROFIBUS remotes must be inserted by the user below the NX5001 PROFIBUS masters already inserted Furthermore tasks and basic POUs from the program type are created as described in the following sections Single and Cyclic Task MainTask The redundant CPU project has a single task called MainTask which is cyclic The user can adjust the task cycle time MainPrg Program The MainTask is connected to a single POU from the program type called MainPrg The MainPrg program is created automatically The MainPrg code is the following in ST language 226 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
475. the other are not ready RESET_WATCHDOG Application in Stop Mode due to reset by watchdog or by Runtime reboot when Start User Application After a Watchdog Reset option is enabled by the user ABSENT_MODULES_HOT_SWAP_DISABLED Application in Stop Mode due to Absent Modules diagnostic activation when hot swap is configured as disabled or disabled for declared modules only CFG_MISMATCH_HOT_SWAP_DISABLED Application in Stop Mode due to Mismatch Configuration diagnostic activation when hot swap is configured as disabled or disabled for declared modules only ABSENT_MODULES_HOT_SWAP_STARTUP_CON Application in Stop Mode due to Absent Modules SISTENCY diagnostic activation when hot swap is configured as enabled with startup consistency or enabled with consistency in the start only for declared modules CFG_MISMATCH_HOT_SWAP_STARTUP_CONSI Application in Stop Mode due to Mismatch Configuration STENCY diagnostic activation when hot swap is configured as enabled with startup consistency or enabled with consistency in the start only for declared modules APPL_STOP_ALLOWED_TO_RUN Application in Stop Mode and all consistencies done with success Application allowed to go to Run Mode APPL_STOP_MODULES_NOT_READY Application in Stop Mode and all consistencies done with success but I O modules are not able to system startup Not possible to set the Application to Run Mode APPL_STOP_MODULES_GETTING_READY_TO_R Application in Stop Mode and all con
476. the utilization of a more accurate data transmission and reception control Advanced Port Parameters Executes the request control for a command transmission through RS 232C interface Handshake UART RX Threshold RX on TX RX DCD Event RX CTS Event Bytes quantity which must be received to generate a new UART interruption Low values make the TIMESTAMP more precise when the EXTENDED MODE is used and minimizes the overrun errors However values too low may cause several interruptions delaying the CPU Serial When true all received bytes during transmission will be discharged instead of going to the RX line Used to disable the full duplex operation of the RS 232C interface When true generates an external event due to DCD signal change When true generates an external event due to CTS signal change RTS OFF Events Disabled Enabled Enabled RTS Enabled at the beginning of transmission and restarted as fast as possible after the end of it E g The RS 232 RS 485 external converter control RTS OFF Always disabled RTS ON Always enabled RTS CTS In case the CTS is disabled the RTS is enabled Therefore the CTS enabling must be waited until the transmission can start again and the RTS restarted as fast as possible at the end of transmission E g the radio modems control using the same modem signal Manual RTS the user is responsible for all control signals
477. then contact Altus Technical Assistance Hardware Failure In case the Hardware Failure diagnostic is true the CPU must be sent to Altus Technical Assistance as it has problems in the RTC auxiliary processor or other hardware resources Software Exception In case the software exception diagnostic is true the user must verify his application to guarantee it is not accessing the memory wrongly If the problem remains the Altus Technical Support sector must be consulted The software exception codes are described next in the CPU detailed diagnostics table Diagnostic Message The diagnostics messages can be visualized by the CPU graphic display using the OTD key or using the WEB through the CPU diagnosis page Ethernet Interfaces The diagnostics regarding to the NET 2 interface are only available for the NX3020 and NX3030 CPUs 308 7 Maintenance Detailed Diagnostics Table 7 7 shows the CPU detailed diagnostics CPU Direct Representation Variable NX3030 QD n 4 QD n 4 QD n 4 QD n 8 QD n 8 QD n 8 QD n 12 QD n 12 QD n 12 QD n 16 QD n 16 QD n 16 QX n 20 0 QX n 20 0 QX n 20 0 QX n 20 1 QX n 20 1 QX n 20 1 QX n 20 2 QX n 20 2 QX n 20 2 QX n 20 3 QX n 20 3 QX n 20 3 QW n 21 QW n 21 QW n 21 QB N 23 QB N 23 QB n 23 QB n 24 QB N 24 QB n 24 QB n 25 QB n 25 QB n 25 QW n 26 QW n 26 QW n 26 QW n
478. tic project synchronization with the Active PLC e Incase it s in the Stand by or Starting state it switches to the Not Configured state and remains in it until the projects are synchronized again After that returns automatically to the Stand by state e Incase it s in the Not Configured or Inactive state the STAND BY button from the PX2612 panel must be pressed or an equivalent command must be executed This way after the project synchronization it goes out from the Not Configured state and can go to Stand by state or go back to the Inactive state if there s a failure Off Line Download of Modifications with Process Control Interruption In the present section it s defined a procedure to execute an off line download which interrupts the process control Such situation is acceptable in specific process types and during programmed process stopping An off line download from this type must be executed connecting MasterTool to the NET 1 channel of the Active PLC using the exclusive IP address from the Active PLC CLPX Active IP Before beginning an off line in the Active PLC the user receives two MasterTool warnings e Ifthe other PLC isn t in Stand by state the process control will be interrupted e Ifthe other PLC is in Stand by state it will turn off this PLC and take over as Active Before the off line download switch it to Inactive The first warning reminds the user that this off line download will interrupt th
479. ting command Ctrl F7 leaves the variables to be overwritten when new readings are done 209 5 Initial Programming P aina Inical E Configuration Bus 2 MainPrg Device Application MainPrg Express o iVar0 Vari bVar war Tipo INT INT BOOL WORD 4 x Valor Valor Preparado Comentario seqe Fy ienaa het b UNH Ez bVarfaise TRUE THEN wara war 0 i iVar_o 0 ivar_1flo_ ti CEET gt Figure 5 33 Program Being Executed 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 option available at the menu Debug as shown on Figure 5 34 a IEI Devices J Configuration Bus f Nx3030 Nx3030 Bill of Materials B Configuration and Consi Diagnostic Explorer Diagnostics i il Library Manager E MainPra PRG P Task Configuration MainTask MainPra 6 comi com2 GD NETI OD NET2 Debug Tools Window Help File Edit View Project Build Online Start m Stop im New Breakpoint Toggle Breakpoint Step Over Step Into Step Out Run to Cursor Set next Statement gt Show next Statement Write values Force values FS
480. tion e g in case of other diagnostics as Ethernet communication failure through this CPU local or the other CPU remote Up to 3 cycles from the MainTask depending on the stimulus for state change command or failure In case of PROFIBUS network failure 2 MainTask cycles 500 ms A switchover doesn t cause discontinuities in the controller outputs nor in the inner variables Maximum value automatically calculated by MasterTool and informed to the user considering an empty redundant forcing list Typical average value of 60ms for 224kbytes of redundant data in a system with a redundant PROFIBUS network and two redundant Ethernet HSDN networks Among other diagnostics shows the redundancy state Active Stand by Inactive Not configured and Starting together with the CPU identification PLCA or PLCB 223 6 Redundancy with NX3030 CPU Redundancy Control Panel PX2612 Redundancy diagnostics Redundancy commands Redundancy events SNTP Simple Network Time Protocol Commands and diagnostics synchronization Redundant data synchronization Redundant forcing list synchronization Single project for PLCA and PLCB CPU identification Automatic project synchronization On line expansion of modules and PROFIBUS remotes Private IP addresses for PLCA and PLCB NIC Teaming Through buttons allows commands of switchover or redundancy states transition for maintenance LE
481. tool allows the profile change from an existent project but it is up to the developer to adjust what is necessary to guarantee the project compatibility with the new rules from the selected profile Note While the project profiles are being described some tasks are named which are described in the Task Configuration section In the Single project profile the application has only the MainTask user task This task is responsible for the execution of a single Program unit called MainPrg This single program can call other programming units from the Program Function or Function Block type but all user code will be executed exclusively by the MainTask In this profile the MainTask is cyclic with priority fixed in 13 and executes exclusively the MainPrg program in a closed loop The MainTask is already completely defined and the developer must create the MainPrg program using any of the IEC 61131 3 languages It is not always possible to convert a program to another language but it is always possible to create a new program with the same name constructed with a different language The MasterTool IEC XE standard option is to use MasterTool Standard Project associated to the Single profile which also includes the MainPrg program created in ladder language LD This type of application never needs to consider issues as data consistence resource sharing or mutual exclusion mechanisms 184 5 Initial Programming Basic Normal T
482. tor Group This group has all the privileges and you can not remove it in versions 1 4 xx firmware or higher The Developer group is part of this group Developer Group Group created to define access rights to users who are application developers The service group is part of this group If not used this group can be deleted Everyone Group This is the default group to perform the hits on a CPU while there are no defined groups and users Service Group Group created to define access rights to users to provide some kind of service in CPs such as maintenance crews Watch The group is part of this group If not used this group can be deleted Watch Group Group created to define access rights to users who can only view without making any modification in the application if not used this group can be deleted Administrator User The Administrator user is defined in the Everyone and Administrator groups The default password for the Administrator user is Administrator and can be modified Everyone User The user Everyone is set to Everyone and Administrator groups This user has no password set 178 4 Configuration User and Groups of Old Projects To keep users and old project groups in new projects after the firmware update the CPU or in new Nexto CPUs is needed that in the old project with the original firmware running execute Load Device command so seeking the CPU settings and after Save Disk command thus saving the current co
483. tress that there is a delay between the failure detection and the activation of the inactive interface due to the time necessary to interface configuration This delay could be up to a few dozens of milliseconds When one of the NETs is active it assumes the IP address configured and the inactive NET remains with its configured IP address parameters Subnet Mask and Gateway Address blank in the CPU diagnostics ATTENTION When a Reset Origin is performed in a CPU configured with NIC Teaming enabled for local Ethernet interfaces NET1 and NET2 only the last active interface before the reset will be accessible After the reset command the accessible interface could be viewed in the CPU s Informative and Configuration Menu 260 6 Redundancy with NX3030 CPU Vital failure setting in NET 1 and NET 2 The Advanced option in the setup screen of the NET 1 interfaces and NET2 opens a configuration screen where in addition to enable communication redundancy is also possible to configure if the interface will generate a switchover in case of failure as described in Ethernet Interfaces Use with Vital Fault Indication 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 cor
484. ttings a f PLC Logic Q Start Address of Diagnostics Area g Q Application 66942 5 LA Bil of Materials Sue B Configuration and Consumpti 55 EH Diagnostic Explorer Diagnostics fD Library Manager 2 MainPrg PRG Name Slave Address Task Configuration MainTask B MainPrg ff Configuration Bus j Nx3030 Nx3030 com1 E mMopsus_RTU_Master com2 a Nera Add a NET2 Advanced Used range QB66942 QB66961 Devices Data Type Read Data Start Address Read Data Size Read IEC Variable Write Data Start Address Write Data Size Write IEC Variable Last build 0 0 Precompie 7 Current user nobody Figure 4 15 MODBUS RTU Master Setup Screen Direct representation variables Q for the protocol diagnostic Configuration Description Default Value Initial Address of Initial address of the Diagnostics in Q diagnostic variables os 7 91014 283058 Sie sd Size of diagnostics area Table 4 28 Direct representation variables for the protocol diagnostic Disabled for editing Notes Initial Address of Diagnostics in Q this field is limited by the size of outputs variables Q addressable memory of each CPU which can be found in chapter Technical Description Default Value the factory default value cannot be set to the Initial Address of Diagnostics in Q field because the creation of a Protocol instance may be held at any time on application
485. ual MU299048 or on Initial Programming Inserting a Protocol Instance section MODBUS Ethernet Client Configuration via Symbolic Mapping To configure this protocol using Symbolic Mapping it s necessary to execute the following steps e Configure the general parameters of MODBUS protocol client with the Transmission Control Protocol TCP or RTU via TCP e Add and configure devices by setting IP address port address of the slave and time out of communication available on the Advanced Settings button of the device e 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 e 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 MODBUS Client Protocol General Parameters Configuration via Symbolic Mapping The general parameters found on the MODBUS protocol configuration initial screen Figure 4 26 are defined as General Parameters Settings Connection Mode RTU over TCP TCP Figure 4 26 MODBUS Client General Parameters Configuration Screen Connection Mode Protocol selection TCP ae Table 4 40 MODBUS Client General Configurations The MODBUS Client protocol diagnostics and commands configure
486. uded in its content and it is also sent First set up s password s and click on OK The password in this case should contain only numeric characters At this time passwords were recorded and the next step is run in the Communication menu the command Create boot Application In order to perform this procedure it is not possible to be logged on the CPU After running this command two files are created one with the app extension and another with crc extension In order to finish the setup operation of the password s it is necessary to click again the Memory Card key which is in the configuration of the CPU General Parameters and then locate the file with the crc generated in the previous step using the Find File key Performed these steps the MasterTool IEC XE will send all the files necessary to perform the operations of sending and receiving projects via memory card In case the card is mounted the password will be recorded on it otherwise the set password in MasterTool will be requested if the user try to transfer the project from the CPU to the card To execute the CPU sending to the memory card or vice versa the user must enable the function in the MasterTool IEC XE software type the password and access the Memory Card menu in the CPU using the diagnostics key and then select the desired transference option After this the password will be requested if the user configured so during the application So with a sho
487. ugh open protocols MODBUS TCP client and server MODBUS NX3020 RTU via TCP client and server NX3030 For further utilization information see Ethernet Interfaces Configuration section RJ45 communication connector pattern 10 100Base TX Allows the point to point or network communication through NX3020 open protocols MODBUS TOP client and server MODBUS NEU a NX3030 RTU via TCP client and server For further utilization information see Ethernet Interfaces Configuration section DB9 female connector for RS 232 pattern communication NX3010 Allows the point to point or network communication through COM 1 NX3020 open protocols MODBUS RTU slave or MODBUS RTU NX3030 master For further utilization information see Serial Interfaces Configuration section DB9 female connector for RS 485 and RS 422 pattern NX3010 communication Allows the point to point or network COM 2 NX3020 communication through open protocols MODBUS RTU NX3030 slave or MODBUS RTU master For further utilization information see Serial Interfaces Configuration section Memory card slot Allows the use of a memory card for NX3010 different types of data storage such as user logs Web MEMORY SLOT NX3020 pages project documentation and files NX3030 For further utilization information see Memory Card Interface section Table 2 3 Connection Interfaces 2 Technical Description General Features Common General Features NX3010 NX3020 NX3030 Backplane ra
488. um tolerance 30 e calculated Overhead for redundancy 50 ms In this case the total time used is 60ms 10 ms 50 ms which consists in 60 of the MainTask cycle 100ms This way the maximum looseness is 40 and the minimum looseness of 30 is being respected ATTENTION A compilation error is produced in case the minimum looseness isn t respected if it is configured in the CPU Project Parameters ATTENTION The compilation being successful or not MasterTool informs the calculated looseness and the redundancy overhead predicted on the message window ActivePrg Program In this POU the user must create the main application responsible for its process control This POU is called by the main POU MainPrg being executed only in the Active CPU The user can also create additional POUs program function or function block and call or instance them inside the ActivePrg POU in order to structure his program It s possible to call functions and instance function blocks defined in libraries too It must be remembered that all symbolic variables defined in the ActivePrg POU as the instances of function blocks are redundant variables Symbolic variables defined in additional POUs from the program type which are called inside the ActivePrg are also redundant variables ATTENTION Variables from the type VAR_TEMP must not be used in the redundant program NonSkippeaPrg Program This POU is used for controls which must be
489. und to justify that FALSE The NX4010 module is working properly bReserved 4 7 Reserved Table 6 8 NETB Interface Specific Diagnostics QB n 34 291 6 Redundancy with NX3030 CPU 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 Representation DG_NX4010 tRedundancy Description Variable RedDgnLoc sNET_Stat QW n 35 wSuccessExchDgCmdSync Success counting of the Diagnostics and Commands service 0 to 65535 F Failure counting of the Diagnostics and 9 QW n 37 wFailedExchDgCmdSync Commands service 0 to 65535 Success counting of the Redundant Data QAW n 39 wSuccessRedDataSyne Synchronization service 0 to 65535 Failure counting of the Redundant Data AAW n 41 wFailedRedDataSync Synchronization service 0 to 65535 Success counting of the Redundant Forcing List panes wSuccessHedForceSyne Synchronization service 0 to 65535 Failure counting of the Redundant Forcing List QW n 45 wFailedRedForceSync Synchronization service 0 to 65535 QB n 47 byReserved 1 8 Reserved Table 6 9 Interface Specific Diagnostics Note Counters
490. unter is deactivated END IF Non Redundant Timer TOF_NR The non redundant timer is used in applications for the redundant NX3030 CPU which need a timer in the non redundant program of a half cluster This timer does not use the IEC timer therefore it will not be synchronized in case the reserve half cluster assumes the active status and the active one goes for reserve The three types of blocks already available in the NextoStandard library of the MasterTool IEC XE software are describe as follows for doing the procedure of library s inclusion check Libraries chapter The TOF_NR function block implements a delay time for disabling an output and has its functioning and configuration similar to the TOF_RET function block differentiating itself only for not being redundant nor retentive 154 4 Configuration TON_NR Figure 4 71 TOF_NR Function Block Utilization example in ST language PROGRAM NonSkippedProg VAR bStart BOOL TRU Gl TOF NR TOF_NR 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 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
491. ured in the Initial Address of Diagnostics in Q field Direct Variable of type Representation T_DIAG_MODBUS _ETH_SERVER_1 Description Variable Diagnostics Diagnostic bits QX n 0 QX n 1 bRunning The server is running The server is not running see bit bInterruptedByCommand QX n 2 The bit bNotRunning was enabled BIT because the server was interrupted by the user through the command bit bConfigFailure BIT Discontinued diagnostic bNotRunning binterruptedByCommand QX n 3 QX n 4 bRXFailure BIT Discontinued diagnostic QX n HAX bTXFailure BIT Discontinued diagnostic QX n 6 bModuleFailure BIT Discontinued diagnostic QX n 7 bDiag_7_reserved BIT Reserved J D QB n 1 byDiag_1_reserved BYTE Reserved Command bits restarted automatically QX n 2 0 bStop BIT QX n 2 1 bRestart BIT Restart the server QX n 2 2 bResetCounter BIT Reset diagnostics statistics counters aX n 2 3 Command BIT Reserved AX n 2 4 BIT aK 5 sr ET sr 104 Stop the server Reserved Reserved Reserved 4 Configuration waxine2 7 bDiag_28 reserved QB n 3 byDiag_03_reserved Communication statistics Number of established connections QW n 4 we CONNECHONS WORD between client and server 0 to 64 Connections counter between the S f client and server interrupted after QW n 6 wTimeoutClosedConnections WORD a period of inactivity time out 0 to 6553
492. ust be temporarily disabled The Project synchronization disabling is explained in the section Project Synchronization Disabling and must be executed in the Non Active PLC Step 6 Physical Modifications Executing At this moment the physical modifications can be executed such as e 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 e Install a new redundant PROFIBUS network The NX5001 can be hot inserted in each half cluster rack Then the redundant PROFIBUS network can be connected to them e Install a new Ponto Series redundant remote In this case a remote head must be installed at a time e g first in the network B and then in the network A o To install the head in the network B it may be necessary to open the cable or the contacts thus perturbing the communication with the other heads already installed in the network B Before doing that all the operating active heads must be placed in the network A and the operating reserve heads in the network B o To install the head in the network A it may be necessary to open the cable or the contacts thus perturbing the communication with the other heads already installed in the network A 281 6 Redundancy with NX3030 CPU Before doing that all the operating active heads must be placed in the network B and the operating reserve heads in the network A e Install an I O module in a bas
493. ut mere ESSE EXTENDED_DATE_A This variable returns the value of date and DATEANDUME ND_TIME hour of RTC in the format shown at Table 4 72 Table 4 63 Input and Output Parameters of GetDateAndTime input Parameters GETDATEANDTIME RTC_STATUS Ae the function error state see Table Table 4 64 Output Parameters of GetDateAndTime Utilization example in ST language PROGRAM MainPrg VAR Result RTC_STATUS DATEANDTIME EXTENDED DATE AND TIME xEnable BOOL END_VAR IF xEnable TRUE THEN Result GetDateAndTime DATEANDTIME xEnable FALSE END IF 116 4 Configuration GetTimeZone The following function reads the Time Zone configuration this function is directly related with time in Time Zone at SNTP synchronism service GetTimeZone GetTimeZone Figure 4 41 Configuration Reading of Time Zone Input and Output ae z This variable present the reading of Time Zone Table 4 65 Input and Output Parameters of GetTimeZone Output Parameters GetTimeZone RTC_STATUS Returns the function error state see Table 4 74 Table 4 66 Output Parameters of GetTimeZone Utilization example in ST language PROGRAM MainPrg VAR GetTimeZone Status RTC_STATUS TimeZone TIMEZONESETTINGS xEnable BOOL END_ VAR IF xEnable TRUE THEN GetTimeZone Status GetTimeZone
494. ut parameters EXEC ERROR execute connect showed In case SERIAL_STATUS HW_E ILLEG STATUS 144 This variable when true enables the function block use Select the serial port as described in the SERIAL_PORT data type Pointer of a byte array to transmit the buffer values Specify the expected character number in the byte array to be transmitted TX queue maximum size is 1024 characters Specify the time out to complete the transmission including the handshake phase The specified value in ms must be positive and different than zero Specified the delay in ms between the function block call and the transmission beginning This variable can be used in communications with some modems When true the RX queue and the UART FIFO RX are erased before the transmission beginning This behavior is typical in half duplex master slave protocols Input Parameters This variable is true when the block is completely d It is false otherwise 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 is false otherwise It is ed to the variable DONE as its status is after the block conclusion the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR ILL
495. uted on line in the PLC where MasterTool is connected In this case there are two options e To interrupt the process control executing the procedure described in the Off Line Download of Modifications with Process Control Interruption section e Use the PLC and the PROFIBUS networks redundancy in order to avoid interruption of the process control even with the necessity to execute off line downloads in each half cluster PLCA or PLCB A procedure to reach this objective is described in the Exploring the Redundancy for Off Line downloading of Modifications without Interruption of the Process control section 273 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 e Modifications in the redundant memory areas changes in the Redundancy Parameters from the module NX4010 ATTENTION Will not be possible to change the size of redundant memory areas without the interrupt of the process control Thus these areas must be carefully planned and previously configured Modifications which Demand Off Line Download The following modifications demand off line downloads in the PLC where MasterTool is connected e To add or remove devices from the device tree such as o Modules in the main rack NX5001 PROFIBUS masters NX50
496. utes after being turned on finishing automatically the test mode LEDs Testing Thus during the test mode the 6 LEDs must blink losing its normal utility which is showing the redundancy state Buttons Test At pressing a button in the test mode a correspondent LED stops blinking and remains on The following Table 6 12 presents the connection between the pressed button and the LED which remains on Tested button Correspondent LED TURN ON PLC A ACTIVE PLC B STAND BY PLC A STAND BY PLC A Table 6 12 Connection between buttons and LEDs in the PX2612 button test 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 During the test mode the buttons don t allow the execution of functions which would be executed out of this mode such as to cause a redundancy state change Relay Test To test the relays it was created the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal bit At turning on this bit if the PLC is in test mode and in Active state it activates the relay which must cause the other PLC Non Active switching off Turning off the DG_NX4010 tRedundancy RedCmdLoc bTestRelayLocal the relay is released allowing the other PLC reactivating The command has no effect in the Non Active PLC to prevent it turns off the Active PLC T
497. ve CPU through the synchronism channels NETA and NETB This list includes only forced redundant variables this way PLCA and PLCB can have different non redundant data groups forced as these variables are not synchronized There s a single project for the PLCA and PLCB generated by MasterTool The project is composed by the applicative project executable code and the archive project Source code Through MasterTool a NX3030 CPU identifies itself as PLCA PLCB or non redundant CPU This identification isn t part of the applicative project generated by MasterTool even though is written in a CPU using MasterTool The CPU identification allows the feature of a single project for PLCA and PLCB If the Active CPU project becomes different from the Inactive CPU it is copied from the first to the second This synchronization can take several MainTask cycles One must remember the project is composed by the applicative project executable code and the archive project Source code and both are synchronized This synchronization can be disabled in special cases in order to allow visualization of project modifications which can only be downloaded off line in non redundant CPUs There are project modifications that can t be done on line in a non redundant CPU such as the inclusion of new modules or PROFIBUS remotes However using the CPU and the PROFIBUS network redundancy it was defined a procedure to accomplish this goal very imp
498. ve PLC Usually the modifications must be downloaded to the Active PLC and next automatically synchronized with the Non Active PLC through synchronism channels NETA NETB Therefore MasterTool normally must use the Active PLC exclusive IP address PLCX IP address to connect to NET 1 channel from the NX3030 CPU in the Active PLC In order to verify which PLC is in Active state the same step described in Initial Downloading of a Redundant Project Forth Step Identifying the NX3030 CPU and Verifying the CPU Display can be followed ATTENTION To download a project in the Non Active PLC is usually useless as the project automatic synchronization Active to Non Active PLC would cancel the effect of this download However there are special situations when the project synchronization must be disabled temporarily being possible and useful to download a different project in the Non Active PLC These special situations are discussed in the Exploring the Redundancy for Off Line downloading of Modifications without Interruption of the Process control section Off Line and On Line Modifications Download Project modifications may be downloaded off or on line Off line downloads require the PLC where the downloaded is supposed to be executed stopping On the other hand on line downloads allow the PLC to continue executing its application while the modification is downloaded Some modification types require off line download and can t be exec
499. vels defined in its technical features see Power Supply 30 W 24 Vdc Technical Features CE114200 There are two ways to diagnose a failure 1 In case the NX8000 power supply is on with voltage lower than the required minimum limit a power supply failure diagnostic is generated which is recognized by the CPU and the message POWER SUPPLY FAILURE is shown on the display When the supply is within the established limits the CPU recognizes it and automatically is restarted with the user application The diagnostic will still be active to show to the user that the last initialization suffered a power supply failure 2 In case the NX8000 has a voltage drop to an inferior value than the minimum required limit and it returns to a higher value within 10 ms the power supply failure is not recognized by the CPU and the diagnostic is not generated as the system remains intact during this time But if the voltage drop takes 321 7 Maintenance longer than 10 ms the POWER SUPPLY FAILURE message is shown on the CPU screen and the diagnostic is activated POWER FAILURE Figure 7 10 Power Supply Failure Message The user can change the value of the variable attributed to the power supply failure to FALSE during the applicative execution facilitating the verification and treatment of this diagnostic The POWER SUPPLY FAILURE diagnostic is already mapped in a specific memory region defined as CPU Detailed Diagnostic This
500. voltage surge Watchdog Information unit composed by 16 bits Electronic circuit used to verify the equipment function integrity Physical layer for Ethernet type defined in the IEEE 1990 standard supports 802 3i baud rates of 10 Mbps over two pairs of category 3 twisted strands 327 Annex A DNP3 Interoperability 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 Methods to set Configurable Parameters Software Master Tool IEC XE IP Networking Type of End Point TGP Listening Outstation Only Accepts TCP Connections from Allows all IP Address es from which TCP Connections are accepted KR EK TCP Listen Port Number Configurable range 1to 65535 TCP Keep alive timer Configurable range 0 to 4294967295 Multiple master connections Supports up to two masters Based on TCP port number Time synchronization support SNTP Link Layer Data Link Address Configurable range 0 to 65519 Self Address Support using address OxFFFC No Requires Data Link Layer Confirmation Never Maximum number of octets Transmitted in a Data Fixed at 292 Link Frame Maximum number of octets that can be Received Fixed at 292 in a Data Link Fra
501. ware used only for diagnostic indication Configuration Mismatch The incompatible configuration diagnostic is generated if one or more present modules physically do not correspond to the declared one The changed modules diagnostic will turn on in case there is a change of two modules between themselves it is a complementary information to the incompatible configuration The modules inserted in the bus as well as the declared ones in the project do not enable this diagnostic bit This condition is valid only in case of absent or different modules Swapped Modules If only two modules are changed between themselves in the bus then changed diagnostic can be identified 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 Module with Parameterization Error In case the parameterization error diagnostic is true it must be verified the module in the bus are correctly configured and if the firmware and MasterTool IEC XE software version are correct Bus Error Considered a fatal error interrupting the access to the modules in the bus In case the bus error diagnostic is true an abnormal situation due to the hot exchange configuration selected might have occurred or a hardware problem in the bus communication lines
502. with NX3030 CPU General Features Allowed CPUs Redundancy types Failure tolerances Half cluster 5 redundancy states Main failures which cause switchover between the Active CPU and the Reserve CPU The reserve CPU switches for the Active and the Active can go to Inactive or Not configured Commands that cause switchover between the Active CPU and the Reserve CPU Main failures which prevents a CPU to go to the reserve state or remain in it Such failures drive the CPU to a Not Configured or Inactive state Commands that drive the CPU out of the reserve state Switchover time No discontinuities switchover bump less Redundancy overhead MainTask cycle CPU consuming increased by redundancy CPU display Redundant CPU General Features NX3030 Hot standby Tolerates at least simple failures in doubled equipments in the 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 Starting temporary state assumed after Not configured where some tests will define the next state Inactive Active Stand by or back to Not configured Inactive state reached after some types of failures or for programming maintenance Active controlling the user process Stand by ready to switch to Active and control the user process in case there s such demand e g Active CPU fa
503. wnload this project in a redundant CPU are described considering situations such as Downloading the project in a brand new NX3030 CPU or in a CPU with an unknown project On line modifications downloading Off line modifications downloading with the process control interruption during a programmed process stopping Off line modifications downloading without the process control interruption using redundancy features Initial Downloading of a Redundant Project This section describes the necessary steps to run the first download of a redundant project in a NX3030 CPU This is necessary for instance for a brand new CPU recently manufactured or for a CPU that has an unknown project ATTENTION The following steps must be executed for both half clusters PLCA and PLCB which compose a redundant CPU First all steps must be executed for one CPU and then for the other First Step IP Address Discovering for MasterToo l Connection The first step is to discover the IP address from the NET 1 channel in this CPU for MasterTool connection This must be done through NX3030 CPU display and button as described in the Configuration CPU s Informative and Configuration Menu chapter The NETWORK menu informs the IP address which can be used for MasterTool connection Second Step Verifying IP Addresses Conflict Before executing the third step one must be sure there s no other equipment with the same IP address connected to
504. ximum size equal to 1024 characters Specify the time out to receive the expected character quantity In case it is smaller than the necessary to receive the characters the RX_TIME OUT UINT RX_TIME OUT_ERROR output from the STATUS parameter will be indicated When the specified value in ms is equal to zero the function will return the data within the buffer Table 4 90 SERIAL_RX_EXTENDED Input Parameters BOOL This variable is true when the block is completely executed It is false 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 is false otherwise It is ERROR BOQI connected to the variable DONE as its status is showed after the block conclusion In case the ERROR variable is true the STATUS structure will show the error found during the block execution The possible states already described in the SERIAL_STATUS data type are NO_ERROR ILLEGAL_SERIAL_PORT STATUS SERIAL_STATUS PORT_BUSY HW_ERROR_UART HW_ERROR_REMOTE ILLEGAL_RX_BUFF_LENGTH RX_TIME OUT_ERROR FB_SERIAL_RX_EXTENDED_NOT_ALLOWED NOT_CONFIGURED Returns the received characters number This number can be within zero and the configured RX_RECEIVED UINT value in RX_BUFFER_LENGTH In case it is smaller an error will be indicated by the function block 141 4 Configuration RX_SILENCE UINT in
505. ximum value 65535 RX_FIFO_OVERRUN_ERRORS FIFO RX overrun errors counter since the serial port configuration in other words error 131 4 Configuration in the FIFO RX configured threshold Returns to zero when it reaches the maximum value 65535 RX queue overrun errors counter in other words the maximum characters number RX_QUEUE_OVERRUN_ERRORS 1024 was overflowed and the data are being overwritten Returns to zero when it reaches the maximum value 65535 Sum the last 5 error counters frame parity RX_ANY_ERRORS 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 Each block returns specific errors which will be described below NO_ERROR Return the parameters with invalid values or out of range SERIAL_PORT BAUDRATE DATA_BITS PARITY EEGs STOP_BITS HANDSHAKE UART_RX_THRESHOLD TX_BUFF_LENGTH HANDSHAKE_METHOD RX_BUFF_LENGTH Indicates the serial port is being used by HW_ERROR_UART Hardware error detected in the UART HW_ERROR_REMOTE Hardware error at communicating with the remote serial port Time out while waiting for the CTS enabling CTS_TIME OUT_ON in the RS 232 RTS CTS handshake in the SERIAL_TX block Time out while waiting for the CTS disabling CTS_TIME OUT_OFF in the RS 232 RTS CTS handshake in the SERIAL_TX block SERIAL_STATUS x T
506. xto Series CPUs there are two communities according to Table 4 110 Default String Only read Read and Write Table 4 110 SNMP v1 v2c Default Communitis info It s possible to access SNMP v3 using default user see table below Type Authentication Authentication Private Private Es Password Protocol Password Administrator oo o o o Table 4 111 SNMP v3 User info For all settings of communities user and password some limits must be followed as the table below shows Configurable item Minimum Size MaxSize Allowed Characters 0 9 fa zI A Z S _ Q glla zI A ZI S _ Table 4 112 SNMP settings limits 166 4 Configuration User Management and Access Rights Provide functions to define user accounts and configure access rights to the project Note that the user management specific of the device must be supported to control the access rights in the CPU file system and objects at runtime The rights to access the project objects via specified actions are assigned only to groups and therefore each user must belong to a group User Management and Access Rights of the Project User Management The configuration of users and groups is made in the Project dialog in the Project Settings window The projects include automatically with a default group called Everyone All users of other groups are members of this particular group Thus each user account is automatically provided with at least the
507. y Card presence indication Further details regarding its installation see Memory Card chapter 3 COM traffic indication The up arrow A indicates data transmission and the down arrow indicates data reception For further information regarding the COM 1 interface see Serial Interfaces section 4 COM 2 traffic indication The up arrow A indicates data transmission and the down arrow Y indicates data reception For further information regarding the COM 1 interface see Serial Interfaces section 5 Indication of the CPU active diagnostics quantity In case the number shown is different than 0 zero there are active diagnostics in the CPU For further details regarding their visualization on the CPU graphic display through diagnostic key see One Touch Diag section 6 Forced variables in the CPU indication In case the F character is shown in the graphic display a variable is being forced by the user whether symbolic direct representation or AT For further information regarding variable forcing see Run Mode section 7 Identification of the CPU redundancy state message only valid in NX3030 in redundant mode If the CPU is the active PLC the ACT information will be presented The other possible states are NCF Not configured STR Starting INA Inactive and SBY Stand by 8 Indication that the project synchronization is being executed The up arrow A indicates project data transmission and the down arrow V indica
508. y in test mode Normally the user must turn off the TestModeLocal bit on both PLCs as soon as the PX2612 tests are concluded but in case he forgets to do that the bit will be turned off automatically 15 minutes after being turned on FALSE The command which puts the PX2612 panel in test mode is deactivated TRUE This command is used to test the PX2612 NO relay and consequently the external NC relay too used to eventually QB n 56 turn off the other PLC This command is only accepted while the PX2612 is in test mode being automatically switched off and ignored if the PX2612 isn t in this mode Normally the user must turn off the TestRelayLocal bit as bTestRelayLocal soon as the relay test is concluded but if it s forgotten the bit is turned off as soon as the test mode is finished It s important to stress this command is only accepted in the Active PLC to avoid the Non Active PLC to switch it off FALSE The command used to test the PX2612 NO relay is deactivated TRUE This command produces an equivalent action to the STAND BY button on bStandbyRemote the PX2612 in the remote PLC FALSE The STAND BY button on the remote PLC isn t pressed TRUE This command produces an equivalent action to the INACTIVE button on blnactiveRemote the PX2612 in the remote PLC FALSE The INACTIVE button on the 294 6 Redundancy with NX3030 CPU TO SCSCCCC S remote PLC ist pressed TRUE This comman
509. ycle time must be sufficiently low to allow the proper process control taken in account all control feedback times e The cycle time must be high enough for allowing at least the sum of the following times o The NonSkippedPrg and ActivePrg POUs maximum execution time together o The necessary time to manage the redundancy redundancy overhead e Besides this the cycle time must have an additional looseness necessary for the other processes execution times PROFIBUS communication Ethernet communication with SCADA systems etc MasterTool has conditions of calculating the necessary time for redundancy management redundancy overhead after the project is finished all developed POUs and redundant memory areas defined Regarding the NonSkippedPrg and ActivePrg POUs execution maximum time they are possible to be measured after these POUs are already developed Initially MasterTool estimates 10ms for these two POUs maximum time together but the user must revise this field afterwards when measuring using the final project 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 265 6 Redundancy with NX3030 CPU E g e Parameters configured in the MainTask screen o MainTask cycle time 100 ms o POUs NonSkippedPrg ActivePrg estimated time 10 ms o Minim
510. ystem 3 5 RTSResetCounter 0 to 65535 4 1 BrownOut CPU reboot due to a power supply failure in the last initialization a Reset CPU reboot due to watchdog active in the last u W IVe I Alarm generated due to internal temperature be in 0 5 Thermometer 3 2 CPUColdStartCounter 3 Retaininfo 3 3 CPUWarmStartCounter Alarm generated due to internal temperature be in 5 2 OverTemperatureAlarm 85 C or above Reports the operating status of the CPU oe 7 1 CPUState 01 All user applications are in Start Mode 7 Application 03 All user applications are in Stop Mode 7 2 ForcedlOs There are one or more forced IO points 8 1 ServiceEnable SNTP service enabled Indicates which server is active 00 No server active 01 Primary server active 02 Secondary server active Counter of how many times primary server was 8 3 PrimaryServerDownCount unavailable 0 to 65535 Counter of how many times secondary server was 8 4 SecondaryServerDownCount unavailable 0 to 65535 Counter of times the RTC has been updated by the Bie BST IneU dated unt SNTP service 0 4294967295 163 8 2 ActiveTimeServer 4 Configuration 8 6 LastUpdateSuccessfull 8 7 LastUpdateTimeServer 8 8 LastUpdateTimeDayOfMonth 8 9 LastUpdateTimeMonth 8 10 LastUpdateTimeYear 8 11 LastUpdateTimeHours 8 12 LastUpdateTimeMinutes 8 13 LastUpdateTimeSeconds 8 14 LastUpdateTimeMilliSeconds 9 1 1 ConnectionStatus1 9 1 2 OverflowStatus1 9 1 3 EventsCounter1
511. zation is enabled the following files and services will be synchronized Project application executable code Project archive source code User and groups Access rights Trace The synchronization service will start within thirty seconds after one of the CPUs goes to Active state and after its beginning the project CRC will be checked every five seconds When synchronization is started the Non Active CPU goes to Stop mode at the Not Configured state After the transferring of all necessary files the Non Active CPU goes to Run at Starting state In case the transfer fails the CPU goes back to Not Configured state The time the synchronization will take to be fully executed depends on the project size In average a transfer rate between the synchronism channels is approximately 500 Kbytes s In case the synchronization is interrupted communication loss between synchronism channels during the files transferring from the Active CPU to the Non Active CPU the procedure is aborted and restarted when the communication is restored Only after the conclusion of the whole procedure the Non Active CPU goes to Run mode 234 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 synchronizat

1. Introduction - Beijer Electronics

Contents

Download Pdf Manuals

Related Search

Related Contents