ALTUS Nexto Series User Manual
  1. Manuals
  2. Brands
  3. ALTUS Manuals
  4. Computer Hardware
  5. Nexto Series
  6. User manual

ALTUS Nexto Series User Manual

Hide thumbs Also See for Nexto Series:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
Table of Contents

Advertisement

Quick Links

Download this manual
User Manual
Nexto Series CPU
NX3030
MU214615 Rev. C
September 28, 2022

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for ALTUS Nexto Series

Summary of Contents for ALTUS Nexto Series

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

  • Page 3: Table Of Contents

    1.1. Nexto Series ..........
  • Page 4 CONTENTS 3.3.3. Network Cable Installation ........22 3.4.
  • Page 5 CONTENTS 4.14. Programs (POUs) and Global Variable Lists (GVLs) ......50 4.14.1. MainPrg Program ........50 4.14.2.
  • Page 6 CONTENTS 5.2.2. COM 2 ..........89 5.2.2.1.
  • Page 7 CONTENTS 5.5.8.2.1. General parameters of MODBUS Protocol Client - configuration for Direct Representation (%Q) ......139 5.5.8.2.2.
  • Page 8 CONTENTS 5.5.12.4.4. FMMU/Sync - Sync Manager ......184 5.5.12.4.5. Process Data and Expert Process Data ....185 5.5.12.4.6.
  • Page 9 CONTENTS 5.8.2. RTC Data Structures ........222 5.8.2.1.
  • Page 10 CONTENTS 6.2. Technical Description and Configuration ....... . 269 6.2.1. Minimum Configuration of a Redundant CPU (Not Using PX2612 Panel) .
  • Page 11 CONTENTS 6.3.14. OPC DA Communication Use with Redundant Projects ....292 6.3.15. Redundant CPU States ........293 6.3.15.1.
  • Page 12 CONTENTS 6.4.5.3.1. Failure Vital Setting ......312 6.4.6. NX4010 Redundancy Configuration .
  • Page 13 CONTENTS 6.5.8.3. Step 3 – Previous Project Backup ......329 6.5.8.4. Step 4 – Cares in Editing the Offline Downloaded Modifications .
  • Page 14 CONTENTS 7.4. Not Loading the Application at Startup ....... . . 374 7.5.

  • Page 15: Introduction

    Nexto Series uses an advanced technology in its bus, which is based on a high speed 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.

  • Page 16: Innovative Features

    CPU file system (doc, PDF, data) and memory card interface. One Touch Diag: 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.

  • Page 17: Documents Related To This Manual

    1. INTRODUCTION DHW – Double Hardware Width: Nexto Series modules were designed to save space in user cabi- nets 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).

  • Page 18: Visual Inspection

    Altus Technical Support is contacted. 1.5. 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 https://www.altus.com.br/en/...

  • Page 19: Warning Messages Used In This Manual

    1. INTRODUCTION If the equipment is already installed, you must have the following information at the moment of support requesting: The model from the used equipments and the installed system configuration The product serial number The equipment revision and the executive software version, written on the tag fixed on the product’s side CPU operation mode information, acquired through MasterTool IEC XE The application software content, acquired through MasterTool IEC XE Used programmer version...

  • Page 20: Technical Description

    Diagnostics LED Watchdog LED Table 2: LEDs Description Nexto Series CPUs has two switches available to the user. The table below shows the description of these switches. For further information regarding the diagnostics switch, see sections One Touch Diag CPU’s Informative and Configuration Menu.
  • Page 21 Switch placed on the frontal panel. Used to securely remove the memory card. Table 3: Keys Description On the frontal panel the connection interfaces of Nexto Series CPUs are available. The table below presents a brief description of these interfaces. Interfaces...

  • Page 22: General Features

    2. TECHNICAL DESCRIPTION 2.2. General Features 2.2.1. Common General Features NX3030 Backplane rack occupation 2 sequential slots Power supply integrated Ethernet TCP/IP local interface Serial Interface CAN Interface USB Port Host Memory Card Interface Real time clock (RTC) Resolution of 1 ms and maximum variance of 2 s per day.
  • Page 23 2. TECHNICAL DESCRIPTION NX3030 Electronic Tag on Display (ETD) Standards and Certifications IEC 61131-3 DNV Type Approval – DNV-CG-0339 (TAA000013D) IEC 61131-2 CE – 2014/35/EU (LVD) and 2014/30/EU (EMC) RoHS – 2011/65/EU UL Listed – UL61010-1 (file E473496) EAC – CU TR 004/2011 (LVD) and CU TR 020/2011 (EMC) Table 5: Common Features Notes:...

  • Page 24: Memory

    Nexto Series NX3030 CPU allows the definition of an area of redundant variables into the %Q direct representation output variables memory area. The subset of memory types of output direct representation variables are part of the total available memory.
  • Page 25 2. TECHNICAL DESCRIPTION Command VAR RETAIN VAR PERSISTENT Reset warm / Power on/off cycle Reset cold Reset origin Remove CPU or Power Supply from the rack while energized Download Online change Reboot PLC Clean All Reset Process (IEC 60870-5-104) Table 7: Post-command Variable Behavior In lower or equal 1.5.1.0 for NX3010, NX3020 and NX3030, the retentive and persistent symbolic memories and address- able output variables memory (%Q) used to have a fixed maximum size.

  • Page 26: Protocols

    2. TECHNICAL DESCRIPTION 2.2.3. Protocols NX3030 Interface Open Protocol COM1 / COM2 MODBUS RTU Master COM1 / COM2 MODBUS RTU Slave COM1 / COM2 MODBUS TCP Client NET1 / NET2 MODBUS TCP Server NET1 / NET2 MODBUS RTU over TCP Client NET1 / NET2 MODBUS RTU over TCP Server NET1 / NET2...

  • Page 27: Com 2

    2. TECHNICAL DESCRIPTION 2.2.4.2. COM 2 COM 2 Connector Shielded female DB9 Physical interface RS-422 or RS-485 (depending on the selected cable) Communication direction RS-422: full duplex RS-485: half duplex RS-422 max. transceivers 11 (1 transmitter and 10 receivers) RS-485 max. transceivers Termination Yes (optional via cable selection) 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400,...

  • Page 28: Net 2

    2. TECHNICAL DESCRIPTION 2.2.5.2. NET 2 NET 2 Connector Shielded female RJ45 Auto crossover Maximum cable length 100 m Cable type UTP or ScTP, category 5 Baud rate 10/100 Mbps Physical layer 10/100 BASE-TX (Full Duplex) Data link layer LLC (Logical Link Control) Network layer IP (Internet Protocol) Transport layer...

  • Page 29: Environmental Characteristics

    2.3. Compatibility with Other Products To develop an application for Nexto Series CPUs, it is necessary to check the version of MasterTool IEC XE. The following table shows the minimum version required (where the controllers were introduced) and the respective firmware version at that...

  • Page 30: Application Times

    < 5000 Table 17: Instruction Times 2.4.3. 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. 2.4.4. Interval Time The interval time of the main task of the CPU can be set from 5 to 750 ms.

  • Page 31: Purchase Data

    2. TECHNICAL DESCRIPTION Figure 4: CPU Physical Dimensions 2.6. Purchase Data 2.6.1. Included Itens The product package contains the following items: NX3030 module 2.6.2. Product code The following code should be used to purchase the product: Code Description High-speed CPU, 2 Ethernet ports, 2 serial channels, memory card in- NX3030 terface, remote rack expansion and redundancy support Table 18: Product Code...

  • Page 32: Related Products

    AL-1754: RS-232C standard cable with one DB9 male connector and one DB9 female connector for 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 Series CPUs and...
  • Page 33 AL-1762: RS-232C standard cable with two DB9 male connectors 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.

  • Page 34: Installation

    3.1. 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 MU214600 - Nexto Series User Manual .

  • Page 35: Ethernet Network Connection

    Serial interface RS-485/RS-422 standard for MODBUS RTU network connection or other protocols. The physi- cal interface choice depends on the cable used. 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.

  • Page 36: Gratuitous Arp

    3.3.3. Network Cable Installation Nexto Series CPUs Ethernet ports, identified on the panel by NET, have standard pinout 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...

  • Page 37: Serial Network Connection

    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 interface female con- nector and the cable male connector.

  • Page 38: Communication Without Termination

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

  • Page 39: Communication With Internal Termination

    3. INSTALLATION Figure 9: RS-485 Connections without Termination Diagram Diagram Note: 1. The not connected terminals must be insulated so they do not make contact with each other. 3.5.2. RS-485 Communication with Internal Termination In order to connect in a RS-485 network using the internal termination, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on table below.

  • Page 40: Communication With External Termination

    3. INSTALLATION 1. The not connected terminals must be insulated so they do not make contact with each other. 3.5.3. RS-485 Communication with External Termination In order to connect to a RS-485 network wih external termination, the AL-1763 cable identified terminals must be con- nected in the respective device terminals according to the table below.

  • Page 41: Communication Without Termination

    3. INSTALLATION Figure 12: Connection Diagram of a RS-485 Network with External Termination and Master Redundancy 3.5.5. RS-422 Communication without Termination In order to connect in a RS-422 network with no termination, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on table below.

  • Page 42: Communication With Internal Termination

    3. INSTALLATION Figure 13: Connections without Termination Diagram Diagram Note: 1. The not connected terminals must be insulated so they do not make contact with each other. 3.5.6. RS-422 Communication with Internal Termination In order to connect in a RS-422 network using the internal termination, the cable AL-1763 identified terminals must be connected in the respective device terminals, as shown on table below.

  • Page 43: Communication With External Termination

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

  • Page 44: Memory Card Installation

    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. 3.6. Memory Card Installation This section presents how to insert the memory card into the models Nexto Series CPUs. For further information see Memory Card section.

  • Page 45: Architecture Installation

    3.7.1. 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 –...

  • Page 46: Initial Programming

    4. INITIAL PROGRAMMING 4. Initial Programming The main goal of this chapter is to help the programming and configuration of Nexto Series CPUs, allowing the user to take the first steps before starting to program the device. Nexto Series CPU uses the standard IEC 61131-3 for language programming, which are: IL, ST, LD, SFC and FBD, and besides these, an extra language, CFC.
  • Page 47 4. INITIAL PROGRAMMING SIGNIFICANCE OVERLAPPING Byte Word DWord LWord Byte Word DWord %QX0.7 %QX0.6 %QX0.5 %QX0.4 %QB00 %QX0.3 %QX0.2 %QX0.1 %QX0.0 %QX1.7 %QX1.6 %QX1.5 %QX1.4 %QB01 %QX1.3 %QX1.2 %QX1.1 %QX1.0 %QX2.7 %QX2.6 %QX2.5 %QX2.4 %QB02 %QX2.3 %QX2.2 %QX2.1 %QX2.0 %QX3.7 %QX3.6 %QX3.5 %QX3.4...

  • Page 48: Project Profiles

    4. INITIAL PROGRAMMING The table above shows the organization and memory access, illustrating the significance of bytes and the disposition of other variable types, including overlapping. 4.2. Project Profiles A project profile in the MasterTool IEC XE consists in an application template together with a group of verification rules which guides the development of the application, reducing the programming complexity.

  • Page 49: Basic

    4. INITIAL PROGRAMMING 4.2.2. Basic In the Basic Project Profile, the application has one user task of the Continuous type called MainTask, which executes the program in a continuous loop (with no definition of cycle time) with priority fixed in 13 (thirteen). This task is responsible for the execution of a single programming unit POU called MainPrg.

  • Page 50: Custom

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

  • Page 51: General Table

    4. INITIAL PROGRAMMING This profile may further include an interruption task, called TimeInterruptTask00, with a higher priority than the MainTask, and hence, can interrupt its execution at any time. Tasks Priority Type Interval Event MainTask MainPrg Cyclic 20 ms TimeInterruptTask00 TimeInterruptPrg00 Cyclic 4 ms...

  • Page 52: Maximum Number Of Tasks

    4. INITIAL PROGRAMMING 4.2.8. Maximum Number of Tasks The maximum number of tasks that 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. However, the tasks that will be created must use the following prefixes, according to the type of each of the tasks: CyclicTaskxx, TimeInterruptTaskxx, ExternInterruptTaskxx, where xx represents the number of the task that being created.

  • Page 53: Libraries

    4. INITIAL PROGRAMMING Figure 19: CPU Configuration Besides that, by double-clicking on CPU’s NET 1 icon, it’s possible to configure the Ethernet interface that will be used for communication between the controller and the software MasterTool IEC XE. Figure 20: Configuring the CPU Communication Port The configuration defined on this tab will be applied to the device only when sending the application to the device (down- load), which is described further on sections Finding the Device...

  • Page 54: Inserting A Protocol Instance

    4. INITIAL PROGRAMMING 4.5. Inserting a Protocol Instance The Nexto Series CPUs, as described in the Protocols section, offers several communication protocols. Except for the OPC DA and OPC UA communication, which have a different configuration procedure, the insertion of a protocol can be...

  • Page 55: Finding The Device

    4. INITIAL PROGRAMMING of the protocol. Selecting the option MODBUS Symbol Client, for Symbolic Mapping setting or MODBUS Client, for Direct Addressing (%Q). Then, click Add Device, as shown in the figure below. Figure 22: Selecting the Protocol 4.6. Finding the Device To establish the communication between the CPU and MasterTool IEC XE, first it’s necessary to find and select the desired device.
  • Page 56 4. INITIAL PROGRAMMING Next, the desired controller must be selected by clicking on Set active path. This action selects the controller and informs the configuration software which controller shall be used to communicate and send the project. Figure 24: Selecting the CPU Additionally, the user can change the default name of the device that is displayed.

  • Page 57: Login

    4. INITIAL PROGRAMMING 4.7. Login After compiling the application and fixing errors that might be found, it’s time to send the project to the CPU. To do this, simply click on Login command located on Online menu of MasterTool IEC XE as shown on the following figure. This operation may take a few seconds, depending on the size of the generated file.
  • Page 58 4. INITIAL PROGRAMMING Figure 28: No application on the device If there is already an application on the CPU, depending on the differences between the projects, the following options will be presented: 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.

  • Page 59: Run Mode

    4. INITIAL PROGRAMMING Figure 31: Source code download Transferring the source code is fundamental to ensure the future restoration of the project and to perform modifications on the application that is loaded into the device. 4.8. Run Mode Right after the project has been sent to the CPU, the application will not be immediately executed (except for the case of an online change).

  • Page 60: Stop Mode

    4. INITIAL PROGRAMMING Figure 33: Program running If the CPU already have a boot application internally stored, it goes automatically to Run Mode when the device is powered on, with no need for an online command through MasterTool IEC XE. 4.9.

  • Page 61: Logout

    4. INITIAL PROGRAMMING Moreover, the forced writing command (F7) writes a value into a variable without allowing this value to be changed until the forced variables are released. 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 writing command (CTRL + F7) leaves the variables to be overwritten when new readings are done.

  • Page 62: Project Upload

    Figure 35: Finalizing the online communication with the CPU 4.12. Project Upload Nexto Series CPUs are capable to store the source code of the application on the internal memory of the device, allowing future retrieval (upload) of the complete project and to modify the application.

  • Page 63: Cpu Operating States

    4. INITIAL PROGRAMMING Figure 37: Selecting the CPU To ensure that the project loaded in the CPU is identical and can be accessed in other workstations, consult the chapter Projects Download/Login Method without Project Differences at the MasterTool IEC XE User Manual MT8500 - MU299609. ATTENTION The memory size area to store a project in the Nexto CPUs is defined on section Memory.

  • Page 64: Exception

    4. INITIAL PROGRAMMING 4.13.4. 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.

  • Page 65: Startprg Program

    4. INITIAL PROGRAMMING SpecialVariablesPrg(); isFirstCycle THEN StartPrg(); isFirstCycle := FALSE; ELSE UserPrg(); END_IF; MainPrg call other two POUs of program type, named StartPrg and UserPrg. While the UserPrg is always called, the StartPrg is only called once in the PLC application start. To the opposite of MainPrg program, that must not be modified, the user can change the StartPrg and UserPrg programs.

  • Page 66: Gvl Disables

    4. INITIAL PROGRAMMING Figure 38: System_Diagnostics GVL in Online Mode 4.14.5. GVL Disables The Disables GVL contains the MODBUS Master/Client by symbolic mapping requisition disabling variables. It is not mandatory, but it is recommended to use the automatic generation of these variables, which is done clicking in the button Generate Disabling Variables in device requisition tab.

  • Page 67: Gvl Ioqualities

    4. INITIAL PROGRAMMING VAR_GLOBAL MODBUS_Device_DISABLE_0001 : BOOL; MODBUS_Device_DISABLE_0002 : BOOL; MODBUS_Device_DISABLE_0003 : BOOL; MODBUS_Device_1_DISABLE_0001 : BOOL; MODBUS_Device_1_DISABLE_0002 : BOOL; END_VAR The automatic generation through button Generate Disabling Variables only create variables, and don’t remove automati- cally. This way, in case any relation is removed, its respective disabling variable must be removed manually. The Disables GVL is editable, therefore the requisition disabling variables can be created manually without need of fol- lowing the model created by the automatic declaration and can be used both ways at same time, but must always be of BOOL type.

  • Page 68: Gvl Qualities

    4. INITIAL PROGRAMMING the module, to which it belongs, when that is added to the project. The following picture shows an example of the presentation of this GVL when in Online mode. Figure 40: Module_Diagnostics GVL in Online Mode 4.14.8. GVL Qualities The Qualities GVL contains the quality variable of the internal variables MODBUS Master/Client of symbolic mapping.
  • Page 69 4. INITIAL PROGRAMMING Where: Device Name: Name that appear at the Tree View to the device. Mapping Number: Number of the mapping that was declared on the device mapping table, following the up to down sequence, starting with 0001. ATTENTION It is not possible to associate quality variables to the direct representation MODBUS Mas- ter/Client drivers’...

  • Page 70: Gvl Reqdiagnostics

    4. INITIAL PROGRAMMING Figure 41: Qualities GVL in Online Mode 4.14.9. GVL ReqDiagnostics The ReqDiagnostics GVL contains the requisition diagnostics variables of symbolic mapping MODBUS Master/Client. It is not mandatory, but recommended the use of these variables’ automatic generation, what is done by clicking in the button Generate Diagnostics Variables in device requests tab.

  • Page 71: Prepare_Start Function

    4. INITIAL PROGRAMMING ATTENTION The requisition diagnostics variables of direct mapping MODBUS Master/Client are de- clared at System_Diagnostics GVL. Example: Device.Application.ReqDiagnostics VAR_GLOBAL MODBUS_Device_REQDG_0001 : NXMODBUS_DIAGNOSTIC_STRUCTS. T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_REQDG_0002 : NXMODBUS_DIAGNOSTIC_STRUCTS. T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_REQDG_0003 : NXMODBUS_DIAGNOSTIC_STRUCTS. T_DIAG_MODBUS_RTU_MAPPING_1; MODBUS_Device_1_REQDG_0001 : NXMODBUS_DIAGNOSTIC_STRUCTS. T_DIAG_MODBUS_ETH_MAPPING_1; MODBUS_Device_1_REQDG_0002 : NXMODBUS_DIAGNOSTIC_STRUCTS. T_DIAG_MODBUS_ETH_MAPPING_1;...

  • Page 72: Prepare_Stop Function

    4. INITIAL PROGRAMMING 4.14.11. Prepare_Stop Function In this POU, the PrepareStop system event function is defined. It belongs to the communication task and is called before stopping the application. When there is active communication with the PLC, it is possible to observe the event status and the call count in the System Events tab in the Task Configuration object.

  • Page 73: Configuration

    5. CONFIGURATION 5. 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.
  • Page 74 5. CONFIGURATION Settings Description Standard Options - Denabled, only for de- Enabled, clared modules match - Disabled (with match con- consistency. Hot Swap Mode Module hot swap mode sistency) (may vary - Disabled, no match consis- according to tency CPU model) - Enabled, with match con- sistency only for declared modules...

  • Page 75: Hot Swap

    MainTask anymore. 5.1.1.1. Hot Swap 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.

  • Page 76: Hot Swap Disabled, For Declared Modules Only

    5. CONFIGURATION 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 Startup Consistency for Declared Modules Only do not take into consideration the modules that are in this condition.

  • Page 77: Hot Swap Enabled Without Startup Consistency

    5. CONFIGURATION that the CPU can return to normal Run. The Reset Warm, Reset Cold and Reset Origin commands can be done by MasterTool IEC XE in the Online menu. 5.1.1.1.6. Hot Swap Enabled without Startup Consistency Allows the system to start working even if a module is in an abnormal bus situation (as described on Table 43). The abnormal situations are reported via diagnostics during and after the startup.
  • Page 78 5. CONFIGURATION Enabled, with Startup Enabled, Disabled, Disabled, Enabled, Consistency without for declared without Condition with Startup Disabled for Declared Startup modules Startup Consistency Modules Consistency only Consistency Only clared Blinks 2x Blinks 2x Blinks 2x Blinks 4x Blinks 2x Blinks 4x module Application:...

  • Page 79: Retain And Persistent Memory Areas

    END_VAR As of versions 1.5.1.1 the Nexto Series CPUs allow flexibility on the usage of retentive and persistent memories. This means that the user will be able to choose the size that will be used for each type of memory, as long as the retentive and persistent memory sum don’t exceed the total limit available in each CPU model.

  • Page 80: Tcp Configurations

    In addition, it is important to stress that there’s a maximum quantity 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.
  • Page 81 5. CONFIGURATION 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 attempt 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).

  • Page 82: Project Parameters

    5. CONFIGURATION 5.1.1.4. Project Parameters The CPU project parameters are related to the configuration for input/output refreshing at the task that they are used of the project tasks and consistency of the retentive and persistent area in %Q and the options for reading and writing on the memory card.
  • Page 83 5. CONFIGURATION To configure an external event is necessary to insert a digital input module and perform the configurations described below, in the CPU, through the MT8500 programming tool software. Figure 46: 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 interrup- tion source, in the field Module Address: Name.

  • Page 84: Soe Configuration

    5. CONFIGURATION Figure 48: ExternInterruptTask00 Configuration Screen 5.1.3. 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.
  • Page 85 5. CONFIGURATION Figure 49: Events Sequence Configuration Configuration Description Default Value Options General Configuration Enabled SOE Service Enables the SOE Disabled Disabled NET 1 Ethernet Interface Selects the used interface NET 1 NET 2 Keep alive (ms) interval Keep Alive Interval (ms) 10000 0 to 4294967295 messages...

  • Page 86: Time Synchronization

    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 Data Link messages are not used by the Nexto Series CPUs as the standard does not recommend its use them in TCP/IP communications. 5.1.4. Time Synchronization For the time synchronization, Nexto Series CPUs use the SNTP (Simple Network Time Protocol) or the synchronism through IEC 60870-5-104.

  • Page 87: Iec 60870-5-104

    5. CONFIGURATION Configuration Description Default Options Time zone of the user loca- Time Zone (hh:mm) tion. Hours and minutes can -3:00 12:59 to +13:59 be inserted. Disabled SNTP Service Enables the SNTP service. Disabled Enabled Time interval of the syn- Period for SNTP Synchro- chronization requests (sec- 1 to 255...

  • Page 88: Sntp

    5. CONFIGURATION 5.1.4.2. SNTP When enabled, the CPU will behave as a SNTP client, which is, it will send requests of time synchronization to a SNT- P/NTP server which can be in the local net or in the internet. SNTP client works with a resolution of 1 ms, but with an accuracy of 100 ms.

  • Page 89: Internal Points

    5. CONFIGURATION 5.1.5. Internal Points A communication point is storage on the CPU memory under form of two distinct variables. One represents the point’s value (type BOOL, BYTE, WORD, etc. . . ), while another, represents its quality (type QUALITY). Internal Points are those which the value and the quality are calculated internally by the user application, that is, they don’t have an external origin like occur with points linked to IEDs (Communication drivers of type Master/Client) or to local I/O modules.

  • Page 90: Quality Conversions

    The Standards IEC 61850, DNP3 and IEC104 have their own formats to representation of point’s quality information. The Nexto Series, by its turn, have its own quality format (but quite similar to IEC 61850) called Internal Quality. This format is defined by type QUALITY (library LibRtuStandard) and it is used internally to quality storage, allowing to be done conversion between protocols without information loss.

  • Page 91: Internal Quality

    5. CONFIGURATION ATTENTION In case of internal points mapped to communication drivers, it is not recommended to modify the value of quality flags that dont have a correspondent on the given protocol (i.e, flags that are not described on the following tables). This will result on generation of events equal to the previous one (but with a more recent timestamp) and, this way, depending on the configuration selected for the transmission mode of analog inputs events, it could overwrite the previous event if this one was not delivered to the control center yet.

  • Page 92: Iec 60870-5-104 Conversion

    IED) Table 50: QUALITY Structure 5.1.5.1.2. IEC 60870-5-104 Conversion The tables below presents respectively the digital, analog and counters internal point’s conversion to IEC 60870-5-104 of Nexto Series available to MT8500. Internal-> IEC 60870-5-104 Digital Internal Quality Flags...

  • Page 93: Modbus Internal Quality

    5. CONFIGURATION Internal -> IEC 60870-5-104 Analog Internal Quality Flags VALIDITY IEC 60870-5-104 Quality FLAG_FILTER FLAG_OVERFLOW OVERFLOW FLAG_REFERENCE_ERROR INVALID FLAG_INCONSISTENT INVALID FLAG_OUT_OF_RANGE OVERFLOW FLAG_INACCURATE INVALID FLAG_OLD_DATA NOT TOPICAL FLAG_FAILURE INVALID FLAG_OPERATOR_BLOCKED BLOCKED FLAG_TEST VALIDITY_INVALID INVALID Table 52: Analog Points Conversion Internal to IEC 60870-5-104 Internal ->...

  • Page 94: Local Bus I/O Modules Quality

    5. CONFIGURATION Resulting Quality Resulting VALIDITY Description FLAG_COMM_FAIL AND Communication error. The VALIDITY_INVALID FLAG_RESTART point never was updated. An error has occurred but FLAG_COMM_FAIL AND VALIDITY_QUESTIONABLE the point was updated and FLAG_OLD_DATA now has an old value. It has received an exception FLAG_FAILURE VALIDITY_INVALID response and the point kept...

  • Page 95: Profibus I/O Modules Quality

    5. CONFIGURATION 5.1.5.1.5. PROFIBUS I/O Modules Quality Different from local bus, MasterTool doesn’t automatically create the PROFIBUS modules quality structures, and neither the PLC update such structures. Therefore the creation and cyclic update of PROFIBUS modules quality is user responsibility. To help on the development of such applications, there are following practical examples, in ST language, for the main PROFIBUS modules (DI, DO, AI, AO), based on Nexto Serie’s PROFIBUS slaves (NX5110).

  • Page 96: Profibus Digital Output Quality

    5. CONFIGURATION // If the point have ever been updated once ... IF NOT QUALITY_PB_NX1005_I.FLAGS.FLAG_RESTART THEN QUALITY_PB_NX1005_I.FLAGS.FLAG_OLD_DATA:= TRUE; END_IF END_IF END_IF // In PROFIBUS communication failure with the PROFIBUS slave ... ELSE QUALITY_PB_NX1005_I.VALIDITY:= VALIDITY_INVALID; QUALITY_PB_NX1005_I.FLAGS.FLAG_COMM_FAIL:= TRUE; QUALITY_PB_NX1005_I.FLAGS.FLAG_FAILURE:= FALSE; // If the point have ever been updated once ... IF NOT QUALITY_PB_NX1005_I.FLAGS.FLAG_RESTART THEN...

  • Page 97: Profibus Analog Inputs Quality

    5. CONFIGURATION END_IF END_IF // In PROFIBUS communication failure with the PROFIBUS slave ... ELSE QUALITY_PB_NX1005_O.VALIDITY:= VALIDITY_INVALID; QUALITY_PB_NX1005_O.FLAGS.FLAG_COMM_FAIL:= TRUE; QUALITY_PB_NX1005_O.FLAGS.FLAG_FAILURE:= FALSE; // If the point have ever been updated once ... IF NOT QUALITY_PB_NX1005_O.FLAGS.FLAG_RESTART THEN QUALITY_PB_NX1005_O.FLAGS.FLAG_OLD_DATA:= TRUE; END_IF END_IF 5.1.5.1.8. PROFIBUS Analog Inputs Quality // PROFIBUS analog input quality update, module NX6000 // In communication success case with PROFIBUS slave (address = 99) ...

  • Page 98: Profibus Analog Output Quality

    5. CONFIGURATION DG_NX6000_8_AI_Voltage_Current.tGeneral.bCalibrationError = TRUE THEN QUALITY_PB_NX6000.VALIDITY:= VALIDITY_QUESTIONABLE; QUALITY_PB_NX6000.FLAGS.FLAG_INACCURATE:= TRUE; ELSE QUALITY_PB_NX6000.FLAGS.FLAG_INACCURATE:= FALSE; END_IF // Condition to turns on out of range indication // (check first, because invalid validity must prevail) DG_NX6000_8_AI_Voltage_Current.tDetailed.tAnalogInput_00.bOverRange = TRUE OR DG_NX6000_8_AI_Voltage_Current.tDetailed.tAnalogInput_00.bUnderRange = TRUE THEN QUALITY_PB_NX6000.VALIDITY:= VALIDITY_QUESTIONABLE; QUALITY_PB_NX6000.FLAGS.FLAG_OUT_OF_RANGE:= TRUE;...
  • Page 99 5. CONFIGURATION // PROFIBUS analog output quality update, module NX6100 // In communication success case with PROFIBUS slave (address = 99) ... DG_NX5001.tMstStatus.abySlv_State.bSlave_99 = TRUE THEN // Waits the PROFIBUS slave become apt to exchange data and diagnostics // (It is necessary to wait, avoiding invalid quality generation) DG_NX5110.tPbusHeadA.tStatus1.bStation_Non_Existent = FALSE AND DG_NX5110.tPbusHeadA.tStatus1.bStation_Not_Ready =...

  • Page 100: Serial Interfaces Configuration

    5. CONFIGURATION QUALITY_PB_NX6100.FLAGS.FLAG_RESTART AND NOT DG_NX6100_4_AO_Voltage_Current.tDetailed.tAnalogOutput_00.bOpenLoop THEN QUALITY_PB_NX6100.FLAGS.FLAG_OLD_DATA:= TRUE; END_IF ELSE QUALITY_PB_NX6100.FLAGS.FLAG_RESTART:= FALSE; QUALITY_PB_NX6100.FLAGS.FLAG_FAILURE:= FALSE; QUALITY_PB_NX6100.FLAGS.FLAG_OLD_DATA:= FALSE; END_IF END_IF END_IF // In PROFIBUS communication failure with the PROFIBUS slave ... ELSE QUALITY_PB_NX6100.VALIDITY:= VALIDITY_INVALID; QUALITY_PB_NX6100.FLAGS.FLAG_COMM_FAIL:= TRUE; QUALITY_PB_NX6100.FLAGS.FLAG_FAILURE:= FALSE; // If the point have ever been updated once ... QUALITY_PB_NX6100.FLAGS.FLAG_RESTART DG_NX6100_4_AO_Voltage_Current.tDetailed.tAnalogOutput_00.bOpenLoop THEN...
  • Page 101 5. CONFIGURATION Configuration Description Default Options - Extended Mode: Extended Sets the serial port operation operation mode which de- Serial Mode Normal Mode mode configuration. livers information regarding the received data frame. - Normal Mode: Serial com- munication normal opera- tion mode.

  • Page 102: Advanced Configurations

    5. CONFIGURATION Data Bits Stop Bits Parity NO PARITY, ODD, EVEN, PARITY ALWAYS 1, 2 ONE, PARITY ALWAYS ZERO Table 57: Specific Configurations 5.2.1.1. 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.

  • Page 103: Com 2

    5. CONFIGURATION Configuration Description Default Options When true, generates an ex- - Enabled: Configuration en- RX DCD Event ternal event due to DCD sig- Enabled abled nal change. - Disabled: Configuration disabled When true, generates an ex- - Enabled: Configuration en- RX CTS Event ternal event due to CTS sig- Enabled...

  • Page 104: Ethernet Interfaces Configuration

    Nexto CPUs can provide more local Ethernet interfaces. The NX3030 CPU has NET 1 and NET 2. In addition of the local Ethernet interfaces, the Nexto Series also provides remote Ethernet interfaces through the inclusion of the module NX5000. NX5000 modules have only the NET 1 interface.

  • Page 105: Net 2

    5. CONFIGURATION 5.3.1.2. NET 2 The NET 2 interface is composed by a RJ45 communication connector 10/100Base-TX standard. 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.

  • Page 106: Nx5000 Module Configuration

    5. CONFIGURATION Service MasterTool MT8500 1217* 1740:1743 SQL Server 1433 MQTT 1883* / 8883* EtherNet/IP 44818 2222 IEC 60870-5-104 2404* OPC UA 4840 WEBVISU 8080 CODESYS ARTI 11740 PROFINET 34964 Table 64: Reserved TCP/UDP ports * Default port, but user changeable. 5.4.
  • Page 107 5. CONFIGURATION Figure 53: 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).

  • Page 108: Protocols Configuration

    Figure 54: NX5000 Redundancy Parameter 5.5. Protocols Configuration Independently of the protocols used in each application, the Nexto Series CPUs has some maximum limits for each CPU model. There are basically two different types of communication protocols: symbolic and direct representation mappings. The...
  • Page 109 5. CONFIGURATION devices of communication protocol IEC 60870-5-104 Server (does not include master or clients from MODBUS RTU Slave, MODBUS Server and DNP3 Server protocols). The limitations of the MODBUS protocol for Direct Representation and symbolic mapping for the CPUs can be seen in Tables and 67, respectively.

  • Page 110: Protocol Behavior X Cpu State

    Simultaneous requests per device: Quantity of requests that can be received simultaneously of each IEC 60870-5-104 Client device. 5.5.1. Protocol Behavior x CPU State The table below shows in detail the behavior of each configurable protocol in Nexto Series CPUs in every state of operation. CPU operational state STOP...

  • Page 111: Double Points

    5. CONFIGURATION CPU operational state STOP After down- After the After load, applica- Redundant After an break- Protocol Type before tion goes dundant Stand- exception point appli- to STOP or Active MainPrg cation (PAUSE) starts SOE (DNP3) Outstation IEC 60870-5-104 Server EtherCAT Master...

  • Page 112: Consumers

    5. CONFIGURATION ATTENTION In the Nexto PLC, the events queue is stored in a non-retentive memory area (volatile). This way, the events present in CPU’s queue, which haven’t been transmitted yet to the control center, are going to be lost in a CPU’s eventual power off. The CPU’s event queue is redundant, that means it is synchronized each cycle between both CPUs, when is used CPU’s redundancy.

  • Page 113: Overflow Sign

    IEC 60870-5-104 client. In Nexto Series case, there are no diagnostics available to watch the CPU’s events queue occupation, not even information about the queue overflow. However the consumers have a diagnostics group referred to its events queue. Further information can be found at the specific driver communication section.
  • Page 114 In Nexto Series it is only supported the interception of commands coming from protocol IEC 60870- 5-104. In protocol interception, any return different from SUCCESS results in a negative Acknowledge.
  • Page 115 5. CONFIGURATION ATTENTION It is not recommended the simultaneous commands interception to one same variable by two or more CommandReceiver function blocks. Just one of the function blocks will intercept correctly the command, being able to suffer undesirable interference from the others function blocks if addressed to the same variable.
  • Page 116 5. CONFIGURATION Parameter Type Description When true indicates a selection command reception with bSelectWithValue BOOL value. Table 74: Parameters sSelectConfig Parameter Type Description Received selection command configuration. This struc- sOperateConfig STRUCT ture parameters are described on Table Field of received operation command referred value. This sValue STRUCT structure parameters are described on Table...
  • Page 117 5. CONFIGURATION Parameter Type Description bValue BOOL Point operation value. The pulsed command configuration parameters are stored sPulseConfig STRUCT in this structure. This structure parameters are described on Table 83. Table 78: Parameters sSinglePoint Parameter Type Description bValue BOOL Point operation value. The pulsed command configuration parameters are stored sPulseConfig STRUCT...

  • Page 118: Modbus Rtu Master

    5.5.5. 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).
  • Page 119 5. CONFIGURATION Configuration Description Default Options Delay for the answer trans- Send Delay (ms) 0 to 65535 mission. Minimum Interframe Minimum silence time be- 3.5 to 100.0 (chars) tween different frames. Table 84: 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.
  • Page 120 5. CONFIGURATION Direct Repre- Diagnostic Variable sentation T_DIAG_MODBUS Size Description Variable _RTU_MASTER_1.* 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 SERIAL_STATUS %QB(n+1)

  • Page 121: Devices Configuration - Symbolic Mapping Configuration

    5. CONFIGURATION Direct Repre- Diagnostic Variable sentation T_DIAG_MODBUS Size Description Variable _RTU_MASTER_1.* tCommand. %QX(n+2).7 Reserved bDiag_23_reserved %QB(n+3) BYTE Reserved byDiag_3_reserved Communication Statistics: Counter of request transmitted by the mas- tStat. %QW(n+4) WORD ter (0 to 65535). wTXRequests Counter of normal responses received by tStat.

  • Page 122: Mappings Configuration - Symbolic Mapping Settings

    5. CONFIGURATION Configuration Description Default Options Communication Time-out Defines the application level 3000 10 to 65535 (ms) time-out Defines the numbers of re- Maximum Number of Re- tries before reporting a com- 0 to 9 tries munication error Table 86: Device Configurations 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.

  • Page 123: Requests Configuration - Symbolic Mapping Settings

    5. CONFIGURATION Configuration Description Default Options Name of a variable declared Value Variable Symbolic variable name in a program or GVL Coil - Write (1 bit) Coil - Read (1 bit) Holding Register - Write Data Type MODBUS data type (16 bits) Holding Register - Read (16 bits)
  • Page 124 5. CONFIGURATION Figure 59: Data Requests Screen MODBUS Master Configuration Description Default Value Options 01 – Read Coils 02 – Read Input Status 03 – Read Holding Regis- Function Code ters MODBUS function type 04 – Read Input Registers 05 – Write Single Coil 06 –...
  • Page 125 5. CONFIGURATION Configuration Description Default Value Options Name of a variable declared Diagnostic Variable Diagnostic variable name in a program or GVL Field for symbolic variable used to disable, individually, MODBUS requests config- Variable used to disable ured. This variable must be Disabling Variable MODBUS relation of type BOOL.
  • Page 126 5. CONFIGURATION Write Single Register (FC 06): 1 Write Multiple Coils (FC 15): 1968 Write Multiple Registers (FC 16): 123 Mask Write Register (FC 22): 1 Read/Write Multiple 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.
  • Page 127 Exception Codes: The exception codes presented in this field are values returned by the slave. The definitions of the ex- ception codes 128, 129 and 255 presented in the table are valid only when using Altus slaves. Slaves from other manufacturers might use other definitions for each code.

  • Page 128: Modbus Master Protocol Configuration For Direct Representation (%Q)

    5. CONFIGURATION 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 occurs in order to keep the consistency of the memory areas data while a MainTask is not running.

  • Page 129: Devices Configuration - Configuration For Direct Representation (%Q)

    5. CONFIGURATION Direct representation variables (%Q) for the protocol diagnostic: Default Configuration Description Options Value %Q Start Address of Diag- Initial address of the diag- 0 to 2147483628 nostics Area nostic variables Size Size of diagnostics area Disabled for editing Table 93: MODBUS RTU Master Configuration Notes: Initial Address of Diagnostics in %Q: this field is limited by the size of outputs variables (%Q) addressable memory of...

  • Page 130: Mappings Configuration - Configuration For Direct Representation (%Q)

    5. CONFIGURATION Default Configuration Description Options Value Initial address used to dis- Mapping Disabling 0 to 2147483644 able MODBUS relations Table 94: Device Configuration - MODBUS Master 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 start with numeral character.
  • Page 131 5. CONFIGURATION Figure 63: MODBUS Function In table below, 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 Description Default Value Options Read Function MODBUS function type Read Write...

  • Page 132: Modbus Rtu Slave

    5.5.6. 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 execution mode (Run Mode).

  • Page 133: Modbus Slave Protocol General Parameters - Configuration Via Symbolic Mapping

    5. CONFIGURATION Add and configure MODBUS relations, specifying the variable name, MODBUS data type and data initial address. Automatically, the data size and range will be filled, in accordance to the variable type declared. 5.5.6.1.1. MODBUS Slave Protocol General Parameters – Configuration via Symbolic Mapping The general parameters, found on the MODBUS protocol initial screen (figure below), are defined as.
  • Page 134 5. CONFIGURATION Configuration Description Default Possibilities Minimum Interframe Minimum silence time be- 3.5 to 100.0 (chars) tween different frames Enable the MODBUS Sym- Keep the communication bol Slave to run while the Unchecked Checked or unchecked running on CPU stop CPU is in STOP or after a breakpoint Table 97: Modbus Slave Advanced Configurations...
  • Page 135 5. CONFIGURATION Direct Repre- Diagnostic Variable sentation T_DIAG_MODBUS Size Description Variable _RTU_SLAVE_1.* 0: there is no error. 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 SERIAL_STATUS %QB(n+1)
  • Page 136 5. CONFIGURATION Direct Repre- Diagnostic Variable sentation T_DIAG_MODBUS Size Description Variable _RTU_SLAVE_1.* tCommand. %QX(n+2).7 Reserved. bDiag_23_reserved %QB(n+3) BYTE Reserved. byDiag_3_reserved Communication Statistics: Counter of normal requests received by the slave and answered normally. In case of tStat. %QW(n+4) WORD a broadcast command, this counter is in- wRXRequests cremented, but it is not transmitted (0 to 65535).

  • Page 137: Configuration Of The Relations - Symbolic Mapping Setting

    5. CONFIGURATION 5.5.6.1.2. Configuration of the Relations – Symbolic Mapping Setting The MODBUS relations configuration, showed on figure below, follows the parameters described on table below: Figure 66: MODBUS Data Mappings Screen Configuration Description Default Options Name of a variable declared Value Variable Symbolic variable name in a program or GVL...

  • Page 138: Modbus Slave Protocol Configuration Via Direct Representation (%Q)

    5. CONFIGURATION ATTENTION Differently from other application tasks, when a depuration mark in the MainTask is reached, the task of a MODBUS RTU Slave 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.

  • Page 139: Mappings Configuration - Configuration Via Direct Representation (%Q)

    5. CONFIGURATION Configuration Description Default Value Options %Q Start Address of Diag- Initial address of the diag- 0 to 2147483628 nostics Area nostic variables Size Size of diagnostics area Disabled for editing Slave Address MODBUS slave address 1 to 255 Initial address used to dis- Mapping Disabling 0 to 2147483644...
  • Page 140 5. CONFIGURATION Figure 69: Configuring the MODBUS Relation Default Configuration Description Options Value Coil (1 bit) Data Type MODBUS data type Coil Holding Register (16 bits) Input Register (16 bits) Input Status (1 bit) Initial address of the MOD- Data Start Address 1 to 65536 BUS data Data Size...

  • Page 141: Modbus Ethernet

    5. CONFIGURATION 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.
  • Page 142 5. CONFIGURATION Figure 70: 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.

  • Page 143: Modbus Ethernet Client

    5.5.8. 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).

  • Page 144: Modbus Client Protocol General Parameters - Configuration Via Symbolic Mapping

    5. CONFIGURATION 5.5.8.1.1. MODBUS Client Protocol General Parameters – Configuration via Symbolic Mapping The general parameters, found on the MODBUS protocol configuration initial screen (figure below), are defined as: Figure 71: MODBUS Client General Parameters Configuration Screen Configuration Description Default Options RTU via TCP Connection Mode...

  • Page 145: Device Configuration - Configuration Via Symbolic Mapping

    5. CONFIGURATION Direct Repre- Diagnostic Variable sentation T_DIAG_MODBUS Size Description Variable _ETH_CLIENT_1.* tCommand. %QX(n+2).1 Restart client. bRestart tCommand. %QX(n+2).2 Restart the diagnostic statistics (counters). bResetCounter tCommand. %QX(n+2).3 Reserved. bDiag_19_reserved tCommand. %QX(n+2).4 Reserved. bDiag_20_reserved tCommand. %QX(n+2).5 Reserved. bDiag_21_reserved tCommand. %QX(n+2).6 Reserved. bDiag_22_reserved tCommand.
  • Page 146 5. CONFIGURATION Figure 72: Device General Parameters Settings Configuration Description Default Options IP Address Server IP address 0.0.0.0 1.0.0.1 to 223.255.255.255 TCP Port TCP port 2 to 65534 Slave Address MODBUS Slave address 0 to 255 Table 107: MODBUS Client General Configurations Notes: IP Address: IP address of Modbus Server Device.

  • Page 147: Mappings Configuration - Configuration Via Symbolic Mapping

    5. CONFIGURATION 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 over TCP. Communication Time-out: the Communication time-out is the time that the client will wait for a server response to the request.
  • Page 148 5. CONFIGURATION Configuration Description Default Options Coil - Write (1 bit) Coil - Read (1 bit) Holding Register - Write Data Type MODBUS data type (16 bits) Holding Register - Read (16 bits) Holding Register – Mask And (16 bits) Holding Register –...

  • Page 149: Requests Configuration - Configuration Via Symbolic Mapping

    5. CONFIGURATION 5.5.8.1.4. Requests Configuration – Configuration via Symbolic Mapping The configuration of the MODBUS requests, viewed in figure below, follow the parameters described in table below: Figure 74: MODBUS Data Request Screen Configuration Description Default Value Options 01 – Read Coils 02 –...
  • Page 150 5. CONFIGURATION Configuration Description Default Value Options Field for symbolic variable used to disable, individually, MODBUS requests config- Variable used to disable ured. This variable must be Disabling Variable MODBUS relation of type BOOL. The variable can be simple or array el- ement and can be in struc- tures.
  • Page 151 5. CONFIGURATION Write Multiple Registers (FC 16): 123 Mask Write Register (FC 22): 1 Read/Write Multiple 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 for Master devices and T_DIAG_MODBUS_ETH_CLIENT_1 for Client devices and the mapping by direct representation are in 4-byte and 2-word, which are described in Table...
  • Page 152 Exception Codes: the exception codes show in this filed is the server returned values. The definitions of the exception codes 128, 129 and 255 are valid only with Altus slaves. For slaves from other manufacturers these exception codes can have different meanings.

  • Page 153: Modbus Ethernet Client Configuration Via Direct Representation (%Q)

    5. CONFIGURATION 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.

  • Page 154: Device Configuration - Configuration Via Direct Representation (%Q)

    5. CONFIGURATION Default Setting Description Options Value RTU via TCP Protocol Protocol selection Table 115: MODBUS Client settings Notes: %Q Start Address of Diagnostics Area: this field is limited by the size of output variables addressable memory (%Q) at CPU, which can be found in section Memory. Default Value: the default value cannot be defined for the %Q Start Address of Diagnostics Area field since the creation of a protocol instance can be made at any moment within the application development.

  • Page 155: Mapping Configuration - Configuration Via Direct Representation (%Q)

    5. CONFIGURATION TCP Port: if there are multiple instances of the protocol added in a single Ethernet interface, different TCP ports must be selected for each instance. Some TCP ports, among the possibilities mentioned above, are reserved and therefore cannot be used.
  • Page 156 5. CONFIGURATION Configuration Description Default Value Options Read Function MODBUS function type Read Write Read/Write Mask Write Slave Address MODBUS slave address 0 to 255 Period of communication Polling (ms) 0 to 3600000 (ms) Starting address of MOD- Mapping Diagnostics Area 0 to 2147483640 BUS interface diagnostics Starting address of the read...

  • Page 157: Modbus Client Relation Start In Acyclic Form

    5.5.9. 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).
  • Page 158 5. CONFIGURATION Configuration Description Default Options TCP Port TCP port 2 to 65534 RTU via TCP Connection Mode Protocol selection Table 118: MODBUS Server General 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.

  • Page 159: Modbus Server Diagnostics - Configuration Via Symbolic Mapping

    5. CONFIGURATION Figure 80: MODBUS Server Advanced Settings Configuration Screen Configuration Description Default Value Options Time for the instance execu- tion within the cycle, with- Task Cycle (ms) 5 to 100 out considering its own exe- cution time Maximum idle time between Connection Inactivity client and server before the...
  • Page 160 5. CONFIGURATION Direct Rep- Diagnostic Variable resentation T_DIAG_MODBUS Size Description Variable _ETH_SERVER_1 .* Diagnostic bits: tDiag. %QX(n).0 The server is running. bRunning The server is not running (see bit bInter- tDiag. %QX(n).1 ruptedByCommand). bNotRunning The bit bNotRunning was enabled, be- tDiag.

  • Page 161: Mapping Configuration - Configuration Via Symbolic Mapping

    5. CONFIGURATION Direct Rep- Diagnostic Variable resentation T_DIAG_MODBUS Size Description Variable _ETH_SERVER_1 .* Ethernet frames counter received by the tStat. %QW(n+10) WORD server. An Ethernet frame can contain wRXFrames more than one request (0 to 65535). Requests received by the server counter tStat.

  • Page 162: Modbus Server Ethernet Protocol Configuration Via Direct Representation (%Q)

    5. CONFIGURATION Default Configuration Description Options Value Starting address Data Start Address 1 to 65536 MODBUS data Absolute Data Start Ad- Start address of absolute dress data of Modbus as its type Data Size Size of the MODBUS data 1 to 65536 Data range address config- Data Range ured...

  • Page 163: General Parameters Of Modbus Server Protocol - Configuration Via Direct Representation (%Q)

    5. CONFIGURATION 5.5.9.2.1. General Parameters of MODBUS Server Protocol – Configuration via Direct Representation (%Q) The general parameters, found on the home screen of MODBUS protocol configuration (figure below), are defined as: Figure 82: MODBUS Server Setup Screen TCP port, protocol and direct representation variables (%Q) to control relations and diagnostics: Configuration Description Default Value...

  • Page 164: Mapping Configuration - Configuration Via Direct Representation (%Q)

    5. CONFIGURATION 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 Inactivity Time-out (s). Further details are described in MODBUS Server Protocol General Parameters – Configuration via Symbolic Mapping section.
  • Page 165 5. CONFIGURATION Configuration Description Default Options Coil (1 bit) Data Type MODBUS data type Coil Holding Register (16 bits) Input Status (1 bit) Input Register (16 bits) MODBUS data initial ad- Data Start Address 1 to 65536 dress 1 to 65536 (Holding Regis- Data Size MODBUS data quantity ter and Input Register)

  • Page 166: Opc Da Server

    MainTask is not running. 5.5.10. OPC DA Server It’s possible to communicate with the Nexto Series CPUs using the OPC DA (Open Platform Communications Data Access) technology. This open communication platform was developed to be the standard in industrial communications.
  • Page 167 A gateway enables the communication between the OPC DA Server and Nexto Series PLCs. A gateway in the same sub- Gateway for PLC Communica- net of the PLC is always necessary, as described in chapter...

  • Page 168: Creating A Project For Opc Da Communication

    5. CONFIGURATION Role Description The OPC Client Device module is responsible for the requests to Device Module OPC Client the OPC DA Server using the OPC DA protocol. The collected data is stored on the SCADA Server database. The SCADA Server is responsible for connecting to the various SCADA Server Level communication devices and store the data collected by them on a database, so that it can be consulted by the SCADA Clients.
  • Page 169 5. CONFIGURATION Figure 86: Symbol Configuration Object The table below presents the descriptions of the Symbol Configuration object screen fields. Field Description Symbols Variable identifier that will be provided to the OPC DA Server. Indicates what the possible access right level are in the declared symbol.
  • Page 170 5. CONFIGURATION Figure 87: Selecting Variables on the Symbol Configuration After this procedure, the project must be loaded into a PLC so the variables will be available for communication with the OPC DA Server. If the object Symbol Configuration screen is open and any of the variables, POUs or GVLs selected is changed, its name will appear with the red color.

  • Page 171: Configuring A Plc On The Opc Da Server

    5. CONFIGURATION ATTENTION The configurations of the symbols that will be provided to the OPC DA Server are stored inside the PLC project. By modifying these configurations it’s necessary to load the appli- cation on the PLC so that it’s possible to access those variables. ATTENTION When a variable is removed from the project and loaded on the PLC unchecking it from the object Symbol Configuration, the variable can no longer be read with the OPC Client.
  • Page 172 5. CONFIGURATION the OPC DA Server configurations. Default Set- Device Configuration Description Possibilities ting PLC description inside the This field is a STRING and OPC DA Server configura- it accepts alphanumeric (let- tion file. This field can have ters and numbers) charac- any name, but for organiza- ters and the “_”...

  • Page 173: Importing A Project Configuration

    PLC, also configured, will be accessed. This configuration is especially important for the communication between SCADA systems and the Nexto Series PLCs with Half-Cluster redundancy, where there’s a PLC in active state executing the process, and another PLC in stand-by state, ready to take control of the process if some kind of failure occurs.

  • Page 174: Opc Da Communication Status And Quality Variables

    5. CONFIGURATION right read only by the SCADA. When the value of the variable is TRUE, data is read by connecting with this PLC. This way, every time there is a status change among PLCs, the variable state will also change, remaining in the state TRUE in the PLC which is in the redundancy active state.
  • Page 175 5. CONFIGURATION State Value Description The PLC configured in the OPC DA Server is not con- nected. It can happen if the configuration is incorrect STATE_PLC_NOT_CONNECTED (wrong PLC and/or Gateway IP Address) or the PLC is unavailable in that moment. The PLC configured in the OPC DA Server is connected.

  • Page 176: Limits Of Communication With Opc Da Server

    The communication between the OPC DA Server and the PLC uses the same protocol used in the MasterTool IEC XE communication with the PLC. This protocol is only available for the Ethernet interfaces of the Nexto Series CPUs, it’s not possible to establish this kind of communication with the Ethernet expansion modules.
  • Page 177 5. CONFIGURATION Figure 89: Selecting the OPC DA Server in the Client Configuration In cases where the server is remotely located, it may be necessary to add the network path or IP address of the computer in which the server is installed. In these cases, there are two configuration options. The first is to directly configure it, being necessary to enable the COM/DCOM Windows Service.

  • Page 178: Opc Ua Server

    5. CONFIGURATION ATTENTION The simulation mode of MasterTool IEC XE software can be used for OPC communication tests. The information on how to configure it are presented in the Testing an OPC Commu- nication using the Simulator section of the MasterTool IEC XE User Manual – MU299609. 5.5.11.

  • Page 179: Creating A Project For Opc Ua Communication

    5. CONFIGURATION Role Description The field devices and the PLCs are where the operation state and plant control information are stored. The SCADA system ac- Programmable Controllers and cess the information on these devices and store on the SCADA Field Devices Level server, so that the SCADA clients can consult it during the plant operation.
  • Page 180 5. CONFIGURATION Figure 92: Object Symbol Configuration ATTENTION When enabling OPC UA protocol support, OPC DA protocol support is still enabled. You can enable OPC UA and OPC DA communications at the same time to report the variables configured on the Symbol Configuration object or via attributes. Another way to access this configuration, once already created a project with the Symbol Configuration object, is given by accessing the Settings menu of the configuration tab of the Symbol Configuration.

  • Page 181: Types Of Supported Variables

    5. CONFIGURATION 5.5.11.2. Types of Supported Variables This section defines the types of variables that support communication via the OPC UA protocol, when declared within GVLs or POUs and selected in the Symbol Configuration object (see previous section). The following types of simple variables are supported: BOOL SINT USINT / BYTE...

  • Page 182: Main Communication Parameters Adjusted In An Opc Ua Client

    5. CONFIGURATION 6. Click the icon to generate a certificate and select the following parameters: Key length (bit): 3072 Validity period (days): 365 (can be modified if desired) 7. Wait while the certificate is calculated and transferred to the controller (this may take a few minutes); 8.

  • Page 183: Publishing Interval (Ms) E Sampling Interval (Ms)

    5. CONFIGURATION 5.5.11.6.2. Publishing Interval (ms) e Sampling Interval (ms) The Publishing Interval parameter (unit: milliseconds) must be set for each subscription. The Sampling Interval parameter must be set for each variable (unit: milliseconds). However, in many OPC UA clients, the Sampling Interval parameter can be defined for a subscription, being the same for all the variables grouped in the subscription.

  • Page 184: Publishingenabled, Maxnotificationsperpublish E Priority

    5. CONFIGURATION According to the OPC UA standard, it is possible to define these parameters for each variable. However, many clients allow you to define common values for all variables configured in a subscription. The Filter Type parameter must be of DataChangeFilter, indicating that value changes in the variables should cause it to be transmitted in a Publish Response package.
  • Page 185 5. CONFIGURATION Figure 94: Selecting OPC UA Server in Client Configuration Once the Client connects to the Server, TAG import commands can be used. These commands query information declared in the PLC, returning a list with all the symbols made available by the PLC. Figure 95: List of Symbols Browsed by OPC UA The list of selected variables will be included in the Client’s communications list and can be used, for example, in screens of a SCADA system.

  • Page 186: Ethercat Master

    5. CONFIGURATION 5.5.12. EtherCAT Master EtherCAT (Ethernet Control Automation Technology) is a master-slave architecture protocol with high performance, for deterministic Ethernet, that allows real time performance as it updates 1000 distributed I/O in 30 S or 100 servomotors axis each 100 S using twisted pair cables or optic fiber. Besides, it supports flexible topology, allowing for line, tree and/or star connections.

  • Page 187: Scan For Devices

    5. CONFIGURATION Figure 96: EtherCAT Configuration Example ATTENTION - Only one EtherCAT Master instance per project is allowed. - Only available on the NET connectors of the PLC. - It cannot be used when the NETs are set as redundant. - It cannot be used when Project has cluster redundancy.

  • Page 188: Diagnostic Variables

    5. CONFIGURATION Figure 97: EtherCAT Devices Search Dialog 5.5.12.2. Diagnostic Variables By inserting an EtherCAT Master and Slave, a diagnostic variable is added for the device in the GVL System_Diagnostics. This variable provides information on the device status. There are two types of variables, one for the EtherCAT Master and one for the EtherCAT slaves.
  • Page 189 5. CONFIGURATION Variable Type Possible Values Description DG_EtherCAT_Master.* If DC is used, the PLC will be synchro- nized with the first EtherCAT slave whose DC setting is active. This variable is TRUE shortly after this synchronization is suc- cessfully completed. This signal, for ex- ample, can be used to initialize Soft Mo- tion function blocks in case of compati- tDiag.
  • Page 190 5. CONFIGURATION Code Enum Description Second network adapter uses the MAC-ID as first inter- ADAPTER_MISMATCH face. Error in slaves startup: There’s possibly missing slaves or NO_SLAVES_FOUND with no communication. VENDOR_ID_WRONG Vendor ID is not equal. PRODUCT_ID_WRONG Product ID is not equal. Reading Product ID or Vendor ID is unsuccessful, more NUMBER_DEVICE_MISMATCH slaves in the configuration than in real architecture.

  • Page 191: Ethercat Master Settings

    5. CONFIGURATION Variable DG_Slave.tDiag. Type Hexa Code Description tLastEmergency.* 00XX Reset Error or No Error. 10XX Generic Error. 20XX Current. 21XX Current, inside the device. 22XX Current inside the device. 23XX Current, outside the device. 30XX Voltage. 31XX Main Voltages. 32XX Voltage inside the device.
  • Page 192 5. CONFIGURATION Figure 98: EtherCAT Master Configuration Dialog Factory De- Device Configuration Description Possible Values fault Enable the Master and Slave Marked Autoconfig Master/Slaves Marked automatic configuration. Unmarked Sets the time period in Cycle time [ s] which a new data telegram 100000 2000 to 1000000 must be send to the bus.

  • Page 193: Ethercat Master - I/O Mapping

    5. CONFIGURATION Factory De- Device Configuration Description Possible Values fault First output logic address for Image Out Address 16#2000000 16#1 to 16#1F000000 the first Slave. Table 137: EtherCAT Master Configuration Notes: Autoconfig Master/Slaves: If this option is enabled, most of Master and Slave configuration will be made automatically, based on the description files and implicit calculations.

  • Page 194: Status And Information Tabs

    5. CONFIGURATION Figure 99: Master I/O Mapping Dialog 5.5.12.3.3. Status and Information Tabs The Status tab of the EtherCAT Master configuration editor provides status information (e.g. ’Running’, ’Stopped’) and diagnostic messages specific of the device and the internal bus system. The Information tab, present on the EtherCAT Master configuration editor, shows, if available, the following general information about the module: Name, Vendor, Type, Version Number, Category, Order Number, Description, Image.
  • Page 195 5. CONFIGURATION Figure 100: EtherCAT Slave Configuration Dialog Default Device Configuration Description Opções Value Auto incremental Address AutoInc Address (16-bit) defined by the Slave -65535 to 0 position in the network. Slave final address, assign by the Master during startup. EtherCAT Address This address is independent 1 to 65535...
  • Page 196 5. CONFIGURATION Default Device Configuration Description Opções Value Enable the Sync 0 synchro- Marked Enable Sync 0 Unmarked nization unit configurations. Unmarked By selecting this option, the Cycle Time will be deter- Marked Sync Unit Cycle (Sync 0) mined by the product of the Unmarked Unmarked factor and the Sync Unit Cy-...
  • Page 197 5. CONFIGURATION Default Device Configuration Description Opções Value Set a time reference (in microseconds) for the time- out check of the switch P -> S/S -> O from Pre-Operation 0 to 100000 Safe-Operation and from Safe-Operation to Opera- tional modes. Set the Unit Cycle to the lo- Marked Cyclic Unit...

  • Page 198: Fmmu/Sync

    5. CONFIGURATION Station Alias: These settings are only visible if the option Optional is activated or if the slave device supports alias addresses (defined in the Device Description File). Enable: If the setting Optional is not activated, this setting can be activated if explicitly supported by the device description of the slave.

  • Page 199: Process Data And Expert Process Data

    5. CONFIGURATION 5.5.12.4.5. Process Data and Expert Process Data The Process Data tab of the EtherCAT Slave configurator editor shows the slave input and output process data, each defined by name, type and index by the device description file, as seen in figure below. The selected input (to be read) and output (to be written) of the device are available in the EtherCAT Slave - I/O Mapping dialog as PLC inputs and outputs to which project variables might be mapped.
  • Page 200 5. CONFIGURATION Figure 103: Expert Process Data Dialog This dialog is divided in four sections and two options: Sync Manager: List of (Sync Manager) with data size and type of PDOs. PDO Assignment: List of PDOs assigned to the selected Sync Manager. The checkbox activates the PDO and I/O channels are created.

  • Page 201: Process Data And Expert Process Data - Editing The Pdo List

    5. CONFIGURATION 5.5.12.4.6. Process Data and Expert Process Data - Editing the PDO List Figure 104: Edit PDO List Dialog This dialog is opened through the context menu from the PDO List area, presented in Figure 103. Below are some explanations on the configuration options presented in this dialog.

  • Page 202: Startup Parameters

    5. CONFIGURATION Figure 105: Select item from object directory dialog 5.5.12.4.8. Startup Parameters In the Startup Parameters tab, parameters for the device can be defined, which will be transferred by SDOs (Service Data Objects) or IDN at the system’s startup. The options available in this tab, as well as the access possibilities, vary according to the EtherCAT Slave used and they are present in the Device Description File.

  • Page 203: Ethercat Slave - I/O Mapping

    5. CONFIGURATION State Machine: The buttons Init, Pre-Op (Pre-Operational), Op (Operational) and Safe-Op (Safe-Operational) can be used for debugging purposes. They make the slave transition to the respective state. File access over EtherCAT: If you want to transfer firmware files to or from the Slave, you have to click on the Bootstrap button to switch the slave in Bootstrap Mode.

  • Page 204: Ethernet/Ip

    5. CONFIGURATION Their runtime system can act as either Scanner or Adapter. Each CPU’s NET interface support only one EtherNet/IP instance and it can’t be instanced on an Ethernet expansion module. An EtherNet/IP Adapter instance supports up to 64 input or output modules, limited to 505 bytes in and 509 bytes out. These modules can be BYTE, WORD, SINT, INT, DINT, DWORD or REAL.

  • Page 205: Ethernet/Ip Scanner Configuration

    5. CONFIGURATION Figure 109: Adding an EtherNet/IP Adapter or Scanner 5.5.13.2. EtherNet/IP Scanner Configuration The Scanner requires at least one Adapter with which it will exchange data. New Adapters can be installed on MasterTool with the EDS and DCF Files. The configuration options may differ depending on the device description file of the added Adapter.

  • Page 206: General

    5. CONFIGURATION 5.5.13.2.1. General After open the Adapter declared under the Scanner it’s possible to configure it as needed. The first Tab is General, on it is possible to configure the IP address and the Electronic Keying parameters. These parameters must be checked or unchecked if the adapter being used is installed on MasterTool.
  • Page 207 5. CONFIGURATION 1. Only one of the Scanners can establish an Exclusive Owner connection. 2. The same value of RPI(ms) must be configured for the Scanners. The configuration data is defined in the EDS file. The data is transmitted to the remote adapter when the connection is opened.

  • Page 208: Assemblies

    5. CONFIGURATION Figure 113: EtherNet/IP New Connection’s Window 5.5.13.2.3. Assemblies The upper area of the Assemblies tab displays a list of all configured connections. When a connection is selected, the associated inputs and outputs are displayed in the lower area of the tab. Figure 114: EtherNet/IP Assemblies Output Assembly and Input Assembly: Configuration...

  • Page 209: Ethernet/Ip I/O Mapping

    5. CONFIGURATION Configuration Description Moves the selected In- Move Up put/Output within list. The order in the list deter- Move Down mines the order in the I/O mapping. These values can be changed Name by double-clicking into the text field. Help String This value must not be Bit Length...

  • Page 210: Module Types

    5. CONFIGURATION Figure 115: Adding an EtherNet/IP Module under the Adapter 5.5.13.3.1. Module Types There are 18 different modules which can be added under the adapter. Nine outputs and Nine inputs. They are of type BYTE, WORD, DWORD, REAL, SINT, INT, DINT and BIG. These types can be chosen in the General tab of the module. Figure 116: EtherNet/IP Module’s Type 5.5.13.3.2.

  • Page 211: Type Of Data

    The descriptions of each configuration are related below, in this section. 5.5.14.1. Type of data The table below shows the supported variable type by the Nexto Series CPU for each protocol IEC 60870-5-104 data type. Object Type IEC Variables Type...

  • Page 212: Double Points

    Consult the Double Points section of Utilization Manual for information about double digital points through DBP data type. Once the Nexto Series digital input and output modules don’t support DBP points mapping, some application trickery are needed to make it possible. Remembering that is also not possible to use the PulsedCommand function, defined at the...

  • Page 213: Digital Input Double Points

    The double point value variable must be mapped at the server IEC 60870-5-104 driver, and both simple variables at the Nexto Series digital input module (in that example, a NX1001). Typically the OFF (TRIP) state is mapped to the even input and the ON (CLOSE) state to the odd input.

  • Page 214: Digital Output Double Points

    5. CONFIGURATION Figure 120: Variables Mapping at the Module Inputs At last, the user must insert two code lines in its application, to be cyclically executed, to simple variables value attribution to double point: DBP value variable, index ON, receive simple point ON value DBP value variable, index OFF, receive simple point OFF value Figure 121: Variables’...
  • Page 215 5. CONFIGURATION fbPulsedCmd: PulsedCommandNexto; // Pulsed Command Instance byResult: BYTE; // Pulsed command result dbpIEC104: DBP; // Variable mapped in the IEC 104 bSetup: BOOL:= TRUE; // Interceptor initial setup END_VAR // Executes the function configuration in the first cycle bSetup THEN CmdReceive.dwVariableAddr:= ADR(dbpIEC104);...
  • Page 216 5. CONFIGURATION fbPulsedCmd( byCmdType:= 102, byPulseTime:= DWORD_TO_BYTE(CmdReceive.sCommand.sOperateParameters. sValue.sDoublePoint.sPulseConfig.dwOffDuration/10), ptDbpVarAdr:= ADR(dbpIEC104), stQuality:= IOQualities.QUALITY_NX2020[5], byStatus=> byResult); END_IF ELSE // Returns command not supported byResult:= 1; END_IF COMMAND_TYPE.CANCEL: // Returns command finished with success // (controlled by IEC104 protocol) byResult:= 7; END_CASE // Treats the pulsed command function result // and generates the answer to the intercepted command CASE byResult...
  • Page 217 5. CONFIGURATION and used a function block equivalent to PulsedCommand function of library LibRtuStandard. The PulsedCommandNexto() function block shows up coded in ST language. FUNCTION_BLOCK PulsedCommandNexto VAR_INPUT byCmdType: BYTE; // command type: // 100 = status // 101 = close/on // 102 = trip/off byPulseTime: BYTE;...
  • Page 218 5. CONFIGURATION byStatus:= 2; END_IF 102: // Execute pulse OFF // Valids the pulse duration byPulseTime > 1 THEN // Check if there is already an active command on this point ptDbpVarAdr^.ON ptDbpVarAdr^.OFF THEN // Returns that there is already an active byStatus:= 6;...

  • Page 219: General Parameters

    5. CONFIGURATION // Disable TRIP and CLOSE outputs ptDbpVarAdr^.ON:= FALSE; ptDbpVarAdr^.OFF:= FALSE; // Returns absent module byStatus:= 4; // Next state: initial byState:= 0; END_IF // Copy DBP output states to the simple outputs bON:= ptDbpVarAdr^.ON; bOFF:= ptDbpVarAdr^.OFF; 5.5.14.3. General Parameters To the General Parameters configuration of an IEC 60870-5-104 Server according to figure below follow the table below parameters: Figure 123: Server IEC 60870-5-104 General Parameters Screen...
  • Page 220 5. CONFIGURATION Figure 124: IEC 60870-5-104 Server Mappings Screen Factory De- Parameter Description Possibilities fault Name of a variable declared Value Variable Symbolic variable name in a POU or GVL Single Point Information Double Point Information Step Position Information Measured Value (Normal- 60870-5-104 object ized)

  • Page 221: Link Layer

    For example, case the destiny is an output card, which is not supported in native by Nexto Series. It must be checked at the module’s Datasheet what the minimum and maximum times, as well as the resolution, to running the pulsed commands.
  • Page 222 5. CONFIGURATION Figure 125: Server IEC 60870-5-104 Link Layer Configuration Screen Factory De- Parameter Description Possibilities fault Listened port address to client connection. Used Port Number 2404 1 to 65535 when the client connection isn’t through IP Connected client IP, used IP Address when the client connection 0.0.0.0...

  • Page 223: Application Layer

    5. CONFIGURATION Factory De- Parameter Description Possibilities fault Maximum number data messages (I-Frame) Parameter w (APDUs) 1 to 8 received and not acknowl- edged Table 146: IEC 60870-5-104 Server Link Layer Configuration Note: The fields Time-out t1 (s), Time-out t2 (s) and Time-out t3 (s) are dependents between themselves and must be configured in a way that Time-out t1 (s) be bigger than Time-out t2 (s) and Time-out t3 (s) be bigger than Time-out t1 (s).
  • Page 224 5. CONFIGURATION Factory De- Parameter Description Possibilities fault Option to Enable/Disable Use Local Time instead of Disabled the time stamp in local time Disabled UTC Time Enabled for events Time period in which the selection command will remain active (the count Maximum Time Between starts from the received 1 to 180...

  • Page 225: Server Diagnostic

    5. CONFIGURATION Function Type Configuration Description Equivalent to the counters acquisition D Mode (Integrated Totals) defined by Stan- Freeze by counter- dard IEC 60870-5-101. In this mode, interrogation com- Transmission Mode the control station’s counters interrogation mand, transmit commands, freeze the counters. Case the spontaneously frozen values have been modified, they are reported through events.

  • Page 226: Commands Qualifier

    5. CONFIGURATION Diagnostic variable type Size Description T_DIAG_IEC104_SERVER_1.* tClient_X.eConnectionStatus. Connected client. ENUM value (2) CONNECTED tClient_X.tQueueDiags. BOOL Client queue is overflowed bOverflow tClient_X.tQueueDiags. WORD Configured queue size wSize tClient_X.tQueueDiags. WORD Events number in the queue wUsage tClient_X.tQueueDiags. DWORD Reserved dwReserved_0 tClient_X.tQueueDiags.

  • Page 227: Communication Performance

    5. CONFIGURATION 5.6. Communication Performance 5.6.1. MODBUS Server 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.

  • Page 228: Remote Interfaces

    5. CONFIGURATION 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 = C x (1 / T ) Where: N is the medium number of answers per second; C is the number of active connections; T is the MODBUS task interval in seconds.

  • Page 229: Opc Ua Server

    5. CONFIGURATION 5.6.3. OPC UA Server For the performance tests of communication with OPC UA Server, projects were created for the PLC by declaring variables of type INT. All test scenarios have the following characteristics in common: Projects with Machine Profile and MainTask Interval configured in 100 ms; All variables of type INT are being modified every 100 ms interval.

  • Page 230: System Performance

    System Log section. ATTENTION The CPU’s system logs of the Nexto Series, 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.

  • Page 231: Rtc Clock

    5. CONFIGURATION 5.8. RTC Clock Nexto Series CPUs have an internal clock that can be used through the NextoStandard.lib library. This library is automati- cally loaded during the creation of a new project (to perform the library insertion procedure, see Libraries section).

  • Page 232: Getdateandtime

    5. CONFIGURATION 5.8.1.1.1. GetDateAndTime Figure 128: Date and Hour Reading Input Parameters Type Description This variable returns the value of EXTENDED_DATE DATEANDTIME date and hour of RTC in the format _AND_TIME shown at Table 165. Table 156: Input Parameters of GetDateAndTime Output Parameters Type Description...

  • Page 233: Getdayofweek

    5. CONFIGURATION Input Parameters Type Description This variable presents the reading TIMEZONE TIMEZONESETTINGS of Time Zone configuration. Table 158: Input Parameters of GetTimeZone Output Parameters Type Description Returns the function error state, see GetTimeZone RTC_STATUS Table 167. Table 159: Output Parameters of GetTimeZone Utilization example in ST language: PROGRAM UserPrg...

  • Page 234: Rtc Writing Functions

    5. CONFIGURATION PROGRAM UserPrg DayOfWeek : DAYS_OF_WEEK; END_VAR -------------------------------------------------------------------------- DayOfWeek := GetDayOfWeek(); 5.8.1.2. RTC Writing Functions The clock settings are made through function and function blocks as follows: 5.8.1.2.1. SetDateAndTime SetDateAndTime function is used to write the settings on the clock. Typically the precision is on the order of hundreds of milliseconds.

  • Page 235: Settimezone

    5. CONFIGURATION 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.

  • Page 236: Timezonesettings

    STATUS output parameter. For details of the STATUS output parameter, see the section RTC_STATUS. 5.8.2. RTC Data Structures The reading and setting function blocks of the Nexto Series CPUs RTC use the following data structures in its configuration:...
  • Page 237 5. CONFIGURATION 5.8.2.1. EXTENDED_DATE_AND_TIME This structure is used to store the RTC date when used the function blocks for date reading/setting within milliseconds of accuracy. It is described in the table below: Structure Type Variable Description BYTE byDayOfMonth Stores the day of the set date. BYTE ByMonth Stores the month of the set date.

  • Page 238: User Files Memory

    5.9. 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 Memory section).
  • Page 239 5. CONFIGURATION 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”...

  • Page 240: Memory Card

    For a CPU in Stop Mode or with no application, the transfer rate to the internal memory is approximately 150 Kbytes/s. 5.10. Memory Card Among other memories, Nexto Series CPUs allow the user the utilization of a memory card. It is defined according the features described in Memory Card Interface section which stores, among other files, the project and application in the CPU internal memory.

  • Page 241: Project Transfer

    5. CONFIGURATION Navigate to the Online menu and execute the command Create Boot Application, remembering that you cannot be logged into the CPU to perform this procedure. After you run this command, two files are created in the folder where the project is saved.

  • Page 242: Mastertool Access

    5. CONFIGURATION ATTENTION If the memory card is removed without have been unmounted through CPU’s menu, during a file transference, this process can cause the loss of card data as well as corrupt the files in it. This process may cause the need of another card formatting when it’ll be inserted on the CPU again.
  • Page 243 5. CONFIGURATION Level 1 Level 2 Level 3 Type TEMPERATURE Informative CONTRAST CONTRAST LEVEL Configurable HARDWARE DATE AND TIME Informative BACK Return level ENGLISH >ENGLISH Configurable PORTUGUES >PORTUGUES Configurable LANGUAGES ESPANOL >ESPANOL Configurable BACK Return level NET 1 IP ADDR. Informative NET 1 MASK Informative...
  • Page 244 5. CONFIGURATION • NET 2 MASK – Subnet mask (Ex.: 255.255.255.0) Access to the PLC redundancy information: • PLC ID – Informs the PLC identification in the redundancy. Possible information: PLC A PLC B • REMOTE STATE – Informs the state of the remote redundant PLC. Possible states: ACTIVE STANDBY INACTIVE...

  • Page 245: Function Blocks And Functions

    5. CONFIGURATION Besides the possibility of the Nexto CPUs menu to be closed through a long touch on the screen diagnostic button BACK from level 1, there are also other output conditions that are described below: 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.
  • Page 246 5. CONFIGURATION Data type Options Description Controls the RS-232C port of the RS232_RTS_ON Nexto CPU. The RTS signal is al- ways on. Controls the RS-232C port of the Nexto CPU. In case the CTS is dis- abled, the RTS is enabled. Then waits for the CTS to be enabled RS232_RTS_CTS to get the transmission and RTS...
  • Page 247 5. CONFIGURATION Data type Options Description PARITY_SPACE List all available serial ports (COM 10, COM 11, COM 12, COM 13, SERIAL_PORT COM 1 COM 14, COM 15, COM 16, COM 17, COM 18 and COM 19 – expan- sion modules). COM 2 Defines a character in the RX queue in extended mode.
  • Page 248 5. CONFIGURATION Data type Options Description List of critic error codes that can be returned by the serial func- tion block. Each block returns specific errors, which will be de- scribed below: NO_ERROR No errors. Return the parameters with invalid values or out of range: - SERIAL_PORT - SERIAL_MODE...

  • Page 249: Serial_Cfg

    5. CONFIGURATION Data type Options Description The interruption by the CTS sig- nal can’t be enabled in case CTS_INTERRUPT_ the handshake is different from NOT_ALLOWED RS232_MANUAL or in case the serial port doesn’t have the respec- tive pin. The interruption by the DSR signal can’t be enabled in case the serial DSR_INTERRUPT_ port doesn’t have the respective pin.
  • Page 250 5. CONFIGURATION Output parameters Type Description This variable is true when the block is com- DONE BOOL pletely executed. It is false otherwise. This variable is true while the block is be- EXEC BOOL ing executed. It is false otherwise. This variable is true when the block con- cludes the execution with an error.

  • Page 251: Serial_Get_Cfg

    5. CONFIGURATION Config.PARAMETERS := Parameters; //FUNCTION: Config(); //OUTPUTS: Config.DONE; Config.EXEC; Config.ERROR; Status := Config.STATUS; //If it is necessary to treat the error. 5.12.1.2. SERIAL_GET_CFG The function block is used to capture the desired serial port configuration. Figure 140: Block to Capture the Serial Configuration Input parameters Type Description...
  • Page 252 5. CONFIGURATION Output parameters Type Description In case the ERROR variable is true, the STATUS structure will show the error found during the block execution. The STATUS SERIAL_STATUS possible states, already described in the SERIAL_STATUS data type, are: - NO_ERROR - ILLEGAL_SERIAL_PORT - PORT_BUSY - HW_ERROR_UART...
  • Page 253 5. CONFIGURATION Figure 141: Block Used to Visualize the Control Signals Input parameters Type Description This variable, when true, enables the func- REQUEST BOOL tion block use. Select the serial port, as described in the PORT SERIAL_PORT SERIAL_PORT data type. Table 175: SERIAL_GET_CTRL Input Parameters Output parameters Type...
  • Page 254 5. CONFIGURATION 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 is necessary to treat the error. Get_Control.CTS_VALUE; Get_Control.DSR_VALUE; Get_Control.DCD_VALUE; 5.12.1.4. 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.

  • Page 255: Serial_Rx

    5. CONFIGURATION Output parameters Type Description This variable is true when the block con- cludes the execution with an error. It is ERROR BOOL false otherwise. It is connected to the vari- able DONE, as its status is showed after the block conclusion.
  • Page 256 5. CONFIGURATION Figure 143: Block Used to Clean the RX Queue Input parameters Type Description This variable, when true, enables the func- REQUEST BOOL tion block use. Select the serial port, as described in the PORT SERIAL_PORT SERIAL_PORT data type. Table 179: SERIAL_PURGE_RX_QUEUE Input Parameters Output parameters Type...
  • Page 257 5. CONFIGURATION Purge_Queue(); //OUTPUTS: Purge_Queue.DONE; Purge_Queue.EXEC; Purge_Queue.ERROR; Status := Purge_Queue.STATUS; //If it is necessary to treat the error. 5.12.1.6. SERIAL_RX This function block is used to receive a serial port buffer, using the RX queue normal mode. In this mode, each character in the RX queue occupy a single byte which has the received data, storing 5, 6, 7 or 8 bits, according to the serial interface configuration.
  • Page 258 5. CONFIGURATION Output parameters Type Description This variable is true when the block is com- DONE BOOL pletely executed. It is false otherwise. This variable is true while the block is be- EXEC BOOL ing executed. It is false otherwise. This variable is true when the block con- cludes the execution with an error.
  • Page 259 5. CONFIGURATION Receive.DONE; Receive.EXEC; Receive.ERROR; Status := Receive.STATUS; //If it is necessary to treat the error. Receive.RX_RECEIVED; Receive.RX_REMAINING; 5.12.1.7. 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.
  • Page 260 5. CONFIGURATION Output parameters Type Description This variable is true when the block is com- DONE BOOL pletely executed. It is false otherwise. This variable is true while the block is be- EXEC BOOL ing executed. It is false otherwise. This variable is true when the block con- cludes the execution with an error.

  • Page 261: Serial_Set_Ctrl

    5. CONFIGURATION 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 is necessary to treat the error. Receive_Ex.RX_RECEIVED; Receive_Ex.RX_REMAINING; Receive_Ex.RX_SILENCE;...
  • Page 262 5. CONFIGURATION Input parameters Type Description This variable, when true, enables the func- REQUEST BOOL tion 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. Enables the RTS_VALUE parameter writ- RTS_EN BOOL...

  • Page 263: Serial_Tx

    5. CONFIGURATION 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; Set_Control.ERROR; Status := Set_Control.STATUS; //If it is necessary to treat the error. 5.12.1.9. SERIAL_TX This function block is used to transmit a data buffer through serial port and it is only finalized after all bytes were transmitted or after time-out (generating errors).
  • Page 264 5. CONFIGURATION Input parameters Type Description When true, the RX queue and the UART CLEAR_RX_ FIFO RX are erased before the transmis- BOOL BEFORE_TX sion beginning. This behavior is typical in half-duplex master/slave protocols. Table 187: SERIAL_TX Input Parameters Output parameters Type Description This variable is true when the block is com-...

  • Page 265: Inputs And Outputs Update

    5. CONFIGURATION 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 is necessary to treat the error. Transmit.TX_TRANSMITTED;...

  • Page 266: Refresh_Output

    5. CONFIGURATION Figure 148: Block for Input Updating Input parameters Type Description byRackNumber BYTE Rack number. Position number where the module is con- bySlotNumber BYTE nected. Table 189: REFRESH_INPUT Input Parameters Possible TYPE_RESULT: OK_SUCCESS: Execution success. ERROR_FAILED: This error is returned if the function is called for a module that has only outputs, or also if the option Always update variables (located in the module’s configuration screen, tab I/O Mapping ) is not checked.
  • Page 267 5. CONFIGURATION 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 of input variables (%Q). ATTENTION The REFRESH_OUTPUT function updates only the direct variables %Q that are declared in the "Bus: I/O Mapping"...

  • Page 268: Pid Function Block

    5. CONFIGURATION 5.12.3. PID Function Block ATTENTION The PID function block described up to previous revision L of this manual became obsolete and was removed from this manual. The PID, PID_INT and PID_REAL function blocks described up to revision C of MP399609, also became obsolete and were also removed from newer versions of that man- ual.

  • Page 269: Tof_Ret

    5. CONFIGURATION Output parameters Type Description This variable executes a falling edge as the BOOL PT variable (time delay) reaches its maxi- mum value. TIME This variable shows the current time delay. Table 192: TOF_RET Output Parameters Figure 151: TOF_RET Block Graphic Behavior Utilization example in ST language: PROGRAM UserPrg...

  • Page 270: Ton_Ret

    5. CONFIGURATION Input parameters Type Description This variable, when receives a rising edge, BOOL enables the function block counting. This variable specifies the block counting TIME limit (time delay). Table 193: TON_RET Input Parameters Output parameters Type Description This variable executes a rising edge as the BOOL PT variable (time delay) reaches its maxi- mum value.

  • Page 271: Tp_Ret

    5. CONFIGURATION 5.12.4.3. TP_RET The TP_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).

  • Page 272: Non-Redundant Timer

    5. CONFIGURATION TP_RET( IN := bStart, PT := T#20S); bStart := FALSE; // Actions executed during the counting (TP_RET.Q = TRUE) THEN // Executes while the counter is activated ELSE // Executes when the counter is deactivated END_IF 5.12.5. Non-Redundant Timer 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.

  • Page 273: Ton_Nr

    5. CONFIGURATION 5.12.5.2. TON_NR The TON_NR function block implements a delay time to enable an output and has its functioning and configuration similar to the TON_RET function block, differentiating only for not being redundant nor retentive. Figure 157: TON_NR Function Block Utilization example in ST language: PROGRAM NonSkippedPrg...

  • Page 274: User Log

    5. CONFIGURATION bStart := FALSE; // Actions executed during the counting (TP_NR.Q = TRUE) THEN // Executes while the counter is activated ELSE // Executes when the counter is deactivated END_IF 5.12.6. 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.

  • Page 275: Userlogadd

    MasterTool IEC Programming Manual – MP399609, section 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.

  • Page 276: Userlogdeleteall

    5. CONFIGURATION The viewing of the log files can be performed through worksheets or conventional text editors. The concatenated informa- tion, for improved visualization, may use semicolons between the strings of the message to separate them. One must be careful in formatting cells with floating point values.

  • Page 277: Clearrtudiagnostic

    5. CONFIGURATION (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 confir- mation of execution that can take a large amount of time if there are hundreds of log files in the directory.

  • Page 278: Snmp

    By default, the SNMP agent is activated, i.e., the service is initialized at the time the CPU is started. The access to the agent information 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.

  • Page 279: Private Mib

    5. CONFIGURATION Figure 161: SNMP Manager Example 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.

  • Page 280: User And Snmp Communities

    The Username and Password to access the agent via SNMP protocol are the same used to login on the SNMP Settings web page. 5.13.5. User and SNMP Communities To access the SNMPv1 / v2c of the Nexto Series CPUs, there are two communities, according to table below. Communities Default String...

  • Page 281: User Management And Access Rights

    5. CONFIGURATION It’s possible to access SNMPv3 using default user, see table below: Authentication Privacy Pro- Privacy Pass- Username Type Password Protocol tocol word administrator rwuser administrator Table 202: SNMPv3 Default User info For all settings of communities, user and password, some limits must be respected, as described on the following table: Configurable Minimum Max Size...

  • Page 282: Redundancy With Nx3030 Cpu

    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.

  • Page 283: Technical Description And Configuration

    6. REDUNDANCY WITH NX3030 CPU Figure 164: Example of redundant architecture with NX3030 CPU 6.2. Technical Description and Configuration 6.2.1. Minimum Configuration of a Redundant CPU (Not Using PX2612 Panel) A redundant CPU is composed, at least, by: Two identical half-clusters Each half-cluster consists of at least the following modules:...

  • Page 284: Typical Configurations Of A Redundant Cpu

    6. REDUNDANCY WITH NX3030 CPU The rack itself where the modules are inserted, which can be one of the following: • NX9000, with 8 positions • NX9001, with 12 positions • NX9002, with 16 positions • NX9003, with 24 positions The power supply NX8000, at rack positions 0 and 1 The NX3030 CPU, at rack positions 2 and 3 The module NX4010, at rack positions 4 and 5...

  • Page 285: Nx5001 Modules Addition For Profibus Networks

    6. REDUNDANCY WITH NX3030 CPU 6.2.2.1. 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” a number between 1 and 4) be redundant, the two networks that belongs to this are named PROFIBUS “n”...

  • Page 286: Nx4010 Features

    6. REDUNDANCY WITH NX3030 CPU Figure 166: NX4010 6.2.3.1. 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 Electronic Tag on Display...
  • Page 287 6. REDUNDANCY WITH NX3030 CPU 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. RL B: 2 terminals connected to a relay NO (normally open) contacts, which can be commanded by PLCA to switch off PLCB.

  • Page 288: Px2612 Features

    6. REDUNDANCY WITH NX3030 CPU 6.2.4.1. 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 NO terminals used to switch off PLCA RL B: relay NO terminals used to switch off PLCB GND: grounding Other features (generals, electrical, mechanic and environment) are presented in the Redundancy Control Panel PX2612...

  • Page 289: General Characteristics Of A Redundant Cp

    6. REDUNDANCY WITH NX3030 CPU 6.2.6. General Characteristics of a Redundant CP Redundant CPU General Features Allowed CPUs NX3030 Redundancy type Hot-standby Tolerates, at least, simple failures in doubled equipment in Failure tolerances the half-clusters. In specific cases, it can tolerate multiple failures.
  • Page 290 6. REDUNDANCY WITH NX3030 CPU Redundant CPU General Features - Commands via redundancy control panel (PX2612). Commands that drive the - Commands received from MasterTool or from a SCADA CPU out of the reserve state 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).
  • Page 291 6. REDUNDANCY WITH NX3030 CPU Redundant CPU General Features Each MainTask cycle, the Active CPU copies redundant data Redundant data synchroniza- to the Inactive CPU through the synchronism channels NETA tion and NETB. Non-redundant data are not synchronized. Each MainTask cycle, the Active CPU copies the redundant forcing list to the Inactive CPU through the synchronism Redundant forcing list syn- channels NETA and NETB.

  • Page 292: Purchase Data

    6. REDUNDANCY WITH NX3030 CPU Redundant CPU General Features The CPU supports up to 4 simple PROFIBUS networks or PROFIBUS Network and Vi- up to 2 redundant PROFIBUS networks. It’s also possible to tal Failures Configuration configure if each PROFIBUS network failure is considered vital (causes switchover) or not.

  • Page 293: Principles Of Operation

    6. REDUNDANCY WITH NX3030 CPU 6.3. Principles of Operation In this section, the redundant CPU functions using a NX3030 CPU is described, along with its behavior and states. It’s also presented concepts and programming and configuration restrictions that will be used in the next sections. 6.3.1.

  • Page 294: Activeprg Program

    6. REDUNDANCY WITH NX3030 CPU fbRedundancyManagement.m_fbDiagnosticsLocal.eRedState = REDUNDANCY_STATE. ACTIVE THEN SpecialVariablesRedundantPrg(); END_IF; NonSkippedPrg(); fbRedundancyManagement.m_fbDiagnosticsLocal.eRedState = REDUNDANCY_STATE. ACTIVE THEN ActivePrg(); END_IF; END_IF; MainPrg call two POUs from the program type, called NonSkippedPrg and ActivePrg. NonSkippedPrg is always called, as it’s executed in both CPUs. On the other hand, ActivePrg is only called when the “RedDgnLoc.sGeneral.Diag.eRedState = Active”...

  • Page 295: Redundant And Non-Redundant Variables

    6. REDUNDANCY WITH NX3030 CPU 6.3.3.6. Redundant and Non-redundant Variables The redundant CPU variables can be classified among redundant and 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.

  • Page 296: Redundant And Non-Redundant %M Variables

    6. REDUNDANCY WITH NX3030 CPU The next bytes are reserved for diagnostics which can be redundant, from the I/O system (I/O modules diagnostics, communication interfaces diagnostics, PROFIBUS slaves diagnostics, etc.), for instance. Different from the quick diag- nostics (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 ...

  • Page 297: Redundant And Non-Redundant Symbolic Variables

    6. REDUNDANCY WITH NX3030 CPU 6.3.3.10. 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 512 kbytes.

  • Page 298: Diagnostics, Commands And User Data Structure

    6. REDUNDANCY WITH NX3030 CPU //Logic to put the local PLC in Inactive var_Inactive_command_Ethernet_relation = TRUE THEN DG_NX4010.tRedundancy.RedCmdLoc.bInactiveLocal:=TRUE; var_Inactive_command_Ethernet_relation:=FALSE; END_IF var_Inactive_command_Serial_relation = TRUE THEN DG_NX4010.tRedundancy.RedCmdLoc.bInactiveLocal:=TRUE; var_Inactive_command_Serial_relation:=FALSE; END_IF //Logic to switch on the local PLC switched off by the PX2612 var_TurnOn_command_Ethernet_relation = TRUE THEN DG_NX4010.tRedundancy.RedCmdLoc.bTurnOnLocal:=TRUE;...

  • Page 299: Cyclic Synchronization Services Through Neta And Netb

    6. REDUNDANCY WITH NX3030 CPU RedUsrLoc: has 128 bytes of data filled freely by the user (e.g. communication diagnostics with a SCADA system). These 128 bytes of data can be interchanged with the other CPU (remote) RedUsrRem: it’s a copy from the other CPU RedUsrLoc, received through NETA/NETB Redundancy Maintenance section, the following sub-sections offer more details regarding these data structures: Redundancy Diagnostics Structure...

  • Page 300: Redundant Forcing List Synchronization

    6. REDUNDANCY WITH NX3030 CPU 6.3.6.3. Redundant Forcing List Synchronization This service is responsible for the redundant forcing list transferring, from the Active CPU to the Inactive CPU. For this service to be executed, several conditions must be satisfied: Both synchronization services previous to this cycle (Diagnostics and Commands Exchange) must be completed with success In case this CPU is in Active state, the other must be in Non-Active state.

  • Page 301: Project Synchronization Disabling

    6. REDUNDANCY WITH NX3030 CPU 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.

  • Page 302: Profibus Network Configuration

    PO5065: PROFIBUS slave DP-V1 with Hart, for Ponto Series remotes AL-3416: PROFIBUS slave DP-V0 for AL-2004 CPU NX5210: PROFIBUS slave DP-V0 for Nexto Series remotes Figure also shows the possibility to connect non-redundant remotes to this type of redundant PROFIBUS network, through the AL-2433 module (ProfiSwitch).

  • Page 303: Ip Change Methods

    6.3.11. IP Change Methods 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 NET 1 and NET 2 ports of the NX3030 CPU. These methods define the ports’...

  • Page 304: Active Ip

    6. REDUNDANCY WITH NX3030 CPU Figure 173: IP Automatic Change Parameters that must be configured in the Exchange IP method: IP Address Active: PLCA communication address IP Address Non Active: PLCB communication address Subnetwork Mask Gateway Address 6.3.11.3. Active IP This method is used in the redundant NX3030 CPU NETs and it’s also possible to be configured in the NX5000 modules.

  • Page 305: Multiple Ip

    6. REDUNDANCY WITH NX3030 CPU Figure 175: Active IP method – NX5000 Parameters that must be configured in the Active IP method for the NX5000 Ethernet modules: IP Address Active: Active PLC communication address. Replaces the IP address from the Non-Active PLCX IP Address PLC A Non Active: PLCA communication address, when in Non-Active state IP Address PLC B Non Active: PLCB communication address, when in Non-Active state Subnetwork Mask...

  • Page 306: Nic Teaming And Active Ip Combined Use

    6. REDUNDANCY WITH NX3030 CPU 6.3.12. 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.

  • Page 307: Redundant Cpu States

    6. REDUNDANCY WITH NX3030 CPU 6.3.15. 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 other words, to design any one from the other 4 states (Stand-by, Inactive, Not- Configured and Starting).

  • Page 308: Starting State

    6. REDUNDANCY WITH NX3030 CPU 6.3.15.2. 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: PROFIBUS masters are enabled in a passive state.

  • Page 309: Px2612 Redundancy Command Panel Functions

    6. REDUNDANCY WITH NX3030 CPU 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 6.3.16.

  • Page 310: Px2612 Leds

    6. REDUNDANCY WITH NX3030 CPU 6.3.16.2. PX2612 LEDs The PX2612 LEDs are used to inform the redundancy state, as shown on the following table below: Redundancy state LED ACTIVE LED STAND-BY LED INACTIVE Not-Configured Starting Active Active (recent) blinking Active (switching off the other CPU) blinking Active (recent and switching off the other CPU) blinking...

  • Page 311: Transition 1 - Not-Configured To Starting

    6. REDUNDANCY WITH NX3030 CPU Figure 177: 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.

  • Page 312: Transition 2 - Starting To Not-Configured

    6. REDUNDANCY WITH NX3030 CPU 6.3.17.2. Transition 2 – Starting to Not-Configured This CPU was turned off or restarted (Reset Warm, 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 The other CPU is in Active state and the project in this CPU is different from the project in it.

  • Page 313: Transition 8 - Active To Inactive

    6. REDUNDANCY WITH NX3030 CPU 6.3.17.8. Transition 8 – Active to Inactive 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 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.

  • Page 314: Common Failures Which Cause Automatic Switchovers Between Half-Clusters

    6. REDUNDANCY WITH NX3030 CPU This PLC was switched off or restarted (Reset Warm, Reset Cold or Reset Origin), causing a transition to Not-Configured state 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.

  • Page 315: Fault Tolerance

    6. REDUNDANCY WITH NX3030 CPU 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. ((DG_NX3030.tDetailed.Ethernet.NET1.szIP = '0.0.0.0') (DG_NX3030.tDetailed .Ethernet.NET2.szIP = '0.0.0.0'))

  • Page 316: Simple Failure With Unavailability

    6. REDUNDANCY WITH NX3030 CPU Program periodic offline 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). Offline tests, sometimes, imply in system stopping what decreases the availability. Normally, special situations, such as process programmed maintenance, are used for that purpose.

  • Page 317: Redundancy Overhead

    6. REDUNDANCY WITH NX3030 CPU 6.3.22. 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, described in the Cyclic Synchronization Services through NETA and NETB section, and a smaller time for the redundancy management (state machines, etc.).
  • Page 318 6. REDUNDANCY WITH NX3030 CPU Figure 178: New Project Next, the Wizard which generates the redundancy project run some questions for the user, regarding the desired configura- tion that must be answered successively. The first point to be defined is the initial configuration for the half-cluster hardware: Select device category: NX3030 can be selected in two categories All Devices or in Modular Controllers Select the CPU model: As the redundancy is implemented only in NX3030, it must be selected by the user Select the rack model: There are four rack available models and the choice depends on the module quantity used in the...
  • Page 319 6. REDUNDANCY WITH NX3030 CPU Figure 179: Hardware Initial Configuration After, the user must define the communication networks used in the redundant application: Select device category: NX3030 can be selected from two categories All Devices or Modular Controllers Select the number of PROFIBUS networks: By the Wizard, can be created up to four PROFIBUS networks, and they can be single or redundant.
  • Page 320 6. REDUNDANCY WITH NX3030 CPU Figure 180: 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 Single project profile for the redundancy; hence the selection option is disabled Select the default 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...
  • Page 321 6. REDUNDANCY WITH NX3030 CPU Program associated with MainTask (MainPrg): It must be, obligatory, in ST language, as MasterTool disables the other options Programs associated with redundancy Main Tasks Figure 182: Specific Programs Language ATTENTION The ActivePrg and NonSkippedPrg POUs are created automatically, empty, in language se- lected on the previous questions.

  • Page 322: Half-Clusters Configuration

    6. REDUNDANCY WITH NX3030 CPU 6.4.2. Half-Clusters Configuration The Wizard is always used to generate the first version of a redundant project. This guarantees the initial version is generated quick and correctly. However, it’s possible that some modifications are necessary in a half-cluster, such as the insertion of new NX5001 and NX5000 modules that can be executed changing the half-cluster configuration screen.

  • Page 323: Nic Teaming Between Net 1 And Net 2

    6. REDUNDANCY WITH NX3030 CPU 6.4.3.2. 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 Principles of Operation Redundant Ethernet Networks with NIC...

  • Page 324: Nx5001 Modules Configuration

    6. REDUNDANCY WITH NX3030 CPU 6.4.4. NX5001 Modules Configuration 6.4.4.1. Insertion or Removal of NX5001 modules NX5001 modules can be inserted or removed from the half-cluster rack. To execute this operation correctly, one must be aware of the following rules: 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...

  • Page 325: Profibus Remotes Configuration

    6. REDUNDANCY WITH NX3030 CPU 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 remain blocked for edition. Some network parameters are identical to the other network while others are calculated automatically from network parameters of the left NX5001.

  • Page 326: Nx5000 Modules Configuration

    6. REDUNDANCY WITH NX3030 CPU 6.4.5. NX5000 Modules Configuration 6.4.5.1. 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.

  • Page 327: I/O Drivers Configuration

    6. REDUNDANCY WITH NX3030 CPU Configuration Description Default Options Memory (%M) Redundancy %M Memory Redundant %M memory ini- 0 (disabled) Offset tial address Redundancy %M Memory Redundant %M memory 0 to 65536 Length size Memory (%I) Redundancy %I Memory Redundant %I memory ini- 0 (disabled) Offset tial address...

  • Page 328: Activeprg Program

    6. REDUNDANCY WITH NX3030 CPU • The necessary time to manage the redundancy (redundancy overhead) Besides this, the interval 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).

  • Page 329: Redundancy Configuration Object

    6. REDUNDANCY WITH NX3030 CPU ATTENTION It must be avoided to call additional POUs from the program type inside the NonSkipped- Prg, as symbolic variables declared in this type of POU are redundant, and inside the Non- SkippedPrg 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 struc- ture.

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

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

  • Page 331: Limitations On A Redundant Plc Programming

    6. REDUNDANCY WITH NX3030 CPU 6.4.15. 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. 6.4.15.1. 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: Do not use variables from the type VAR_TEMP Do not mix variable types (VAR, VAR RETAIN, VAR PERSISTENT, etc...).

  • Page 332: Redundant Cpu Program Downloading

    6. REDUNDANCY WITH NX3030 CPU PROGRAM NonSkippedPrg 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=> bDiagEnable); bIsActiveState_old := bIsActiveState; Logic in ActivePrg: NonSkippedPrg.bDiagEnable THEN DG_NX5001.tGeneral.bSlaveNotPresent DG_NX5001.tGeneral.bPbusCommFail...

  • Page 333: Second Step - Verifying Ip Addresses Conflict

    6. REDUNDANCY WITH NX3030 CPU 6.5.1.2. 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 the network, discovered in the first step. This can be discovered, for instance, disconnecting the CPU from the network and executing a “ping”...

  • Page 334: Fifth Step - Redundant Project Downloading

    6. REDUNDANCY WITH NX3030 CPU 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.

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

    6. REDUNDANCY WITH NX3030 CPU 6.5.2. 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: IP Address PLC A: NET 1 address exclusive for PLCA IP Address PLC B: NET 1 address exclusive for PLCB...

  • Page 336: Modifications Which Demand Offline Download And The Interruption Of The Process Control

    6. REDUNDANCY WITH NX3030 CPU To interrupt the process control, executing the procedure described in the Offline Download of Modifications with Process Control Interruption section Use the PLC and the PROFIBUS networks redundancy in order to avoid interruption of the process control, even with the necessity to execute offline downloads in each half-cluster (PLCA or PLCB).

  • Page 337: Online Download Of Modifications

    6. REDUNDANCY WITH NX3030 CPU 6.5.5. Online Download of Modifications In the Offline and Online Modifications Download section, modifications which demand offline 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.

  • Page 338: Previous Planning For Offline Modifications Without Process Control Interruption

    6. REDUNDANCY WITH NX3030 CPU ATTENTION When the Active PLC goes out from the Run mode and goes to Not-Configured, if the other PLC was forgotten in Stand-by state, it takes over as Active and switches off the PLC which has just gone from Active to Not-Configured.

  • Page 339: Step 2 - Insert The Redundant Profibus Network Initial Version In The Project

    6. REDUNDANCY WITH NX3030 CPU ATTENTION The original I/O module bases must be 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 construct- ing this list, as the PO5063V1 PROFIBUS Head and PO5063V5 PROFIBUS Redundant Head Utilization Manual, and PO5064 PROFIBUS Head and PO5065 PROFIBUS Redun- dant Head Utilization Manual.

  • Page 340: Previous Planning For Other Hot Modifications

    6. REDUNDANCY WITH NX3030 CPU PROFIBUS 1 network: • %IB0 ... %IB499 (addresses allocated to already installed remotes) • %IB500 ... %IB999 (addresses allocated to future remotes) PROFIBUS 2 network: • %IB1000 ... %IB1499 (addresses allocated to already installed remotes) •...

  • Page 341: Incompatibility Of Applications

    6. REDUNDANCY WITH NX3030 CPU 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 –...

  • Page 342: Exploring The Redundancy For Offline Downloading Of Modifications Without Interruption Of The Process Control

    6. REDUNDANCY WITH NX3030 CPU Disable the Project Synchronization through the Online/Redundancy Configuration menu Download the updated Project into the Half-Cluster that’s in Stand-by state. A message will be displayed indicating the PersistentVars object memory area reorganization. The procedure must continue and by the end of the project download the Half-Cluster will remain in STOP with a redundancy state as Not-Configured Put the CPU in RUN.

  • Page 343: Step 2 - Don't Download In Group Modifications Which Can Be Downloaded Online

    6. REDUNDANCY WITH NX3030 CPU 6.5.8.2. Step 2 – Don’t Download in Group Modifications which can be downloaded Online Modifications which can be downloaded online must not be downloaded together with modifications which must be down- loaded offline without the process control interruption. When these two kinds of modifications are needed, they must always be loaded separately.

  • Page 344: Step 6 - Physical Modifications Executing

    6. REDUNDANCY WITH NX3030 CPU 6.5.8.6. Step 6 – Physical Modifications Executing At this moment, the physical modifications can be executed, such as: Install a new NX5000 module. This can be done through a module hot-insertion in each half-cluster rack, then connecting it to the Ethernet network Install a new redundant PROFIBUS network.

  • Page 345: Step 10 - Projects Synchronism Enabling In The Active Plc

    6. REDUNDANCY WITH NX3030 CPU 6.5.8.10. Step 10 – Projects Synchronism Enabling in the Active PLC In the step 5, the project synchronism was disabled in the Non-Active PLC. It can be observed this PLC is now in Active state. In this step, the project synchronism must be enabled again in this PLC.

  • Page 346: Alert Before Logging In To Non-Active Cp

    6. REDUNDANCY WITH NX3030 CPU 6.6.2.3. Alert before Logging in to Non-Active CP 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.

  • Page 347: Redundancy Diagnostics

    Not-Configured state, has fin- ished with errors. It’s a system error, nor- bConfigError mally not expected. Get in contact with ALTUS support to report it. Also inform the ConfigErrorCode diagnostic value for the ALTUS support. FALSE – The configuration process has finished successfully or wasn’t executed.
  • Page 348 TRUE – Intermediate data structure with insufficient size. It’s a system error, nor- %QB(n+4) bTemporaryBufferTooSmall mally not expected. Get in contact with ALTUS support to report it. FALSE – Intermediate data structure is within the expected. TRUE – The Diagnostic and Commands bExchangeSync Exchange synchronization service was ex- ecuted successfully in this MainTask cycle.
  • Page 349 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sGeneral_Diag.* Variable 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 the Project Synchronization Disabling...
  • Page 350 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sGeneral_Diag.* Variable TRUE – This PLC can’t communicate in the master state (active or passive) in the PROFIBUS 1 A network. The master mode (communicating with slaves) is as- sumed by the Active PLC. The passive bFailedPBUS1A mode (communicating with the active mas- ter) is assumed by the Non-Active PLC.
  • Page 351 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sGeneral_Diag.* Variable 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 as- sumed by the Active PLC. The passive bFailedPBUS2B mode (communicating with the active mas- ter) is assumed by the Non-Active PLC.
  • Page 352 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sGeneral_Diag.* Variable FALSE – The PX2612 LED ACTIVE is blinking (bBlinkActiveLED) or off. TRUE – The PX2612 LED ACTIVE is bBlinkActiveLED blinking. FALSE – The PX2612 ACTIVE is on (bActiveLEDl) or off. TRUE –...
  • Page 353 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sGeneral_Diag.* Variable Error code discovered during the configu- ration process in the Not-Configured state. %QW(n+13) wConfigErrorCode See ConfigError diagnostics described pre- viously. 32 bits application project CRC, used to %QD(n+15) dwApplicationCRC detect differences between the application projects of the 2 PLCs.
  • Page 354 6. REDUNDANCY WITH NX3030 CPU Variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sNETA_Diag.* Variable TRUE – The synchronism channel has bGeneralFailure some type of failure. The 3 next diagnos- tics will indicate the specific failure. FALSE – The synchronism channel is working properly. TRUE –...
  • Page 355 6. REDUNDANCY WITH NX3030 CPU Variable Direct Variable DG_NX4010.tRedundancy. Description RedDgnLoc.sNETB_Diag.* Variable TRUE – This failure is reported in case a synchronization service hasn’t been fin- ished successfully within a specific time- bTimeoutFailure out and failures from the type bInternal- Failure or bLinkDownFailure haven’t been found to justify that.
  • Page 356 6. REDUNDANCY WITH NX3030 CPU Variable DG_NX4010.tRedundancy Direct Variable Description .RedDgn- Loc.sGeneral_DiagExt.* Variable TRUE – This PLC can’t communicate in the master state (active or passive) in the PROFIBUS 3 A network. The master mode (communicating with slaves) is as- sumed by the Active PLC.
  • Page 357 6. REDUNDANCY WITH NX3030 CPU Variable DG_NX4010.tRedundancy Direct Variable Description .RedDgn- Loc.sGeneral_DiagExt.* Variable TRUE – This PLC can’t communicate in the master state (active or passive) in the PROFIBUS 4 B network. The master mode (communicating with slaves) is as- sumed by the Active PLC.

  • Page 358: Redundancy Commands

    6. REDUNDANCY WITH NX3030 CPU Variable DG_NX4010.tRedundancy Direct Variable Description .RedDgn- Loc.sGeneral_DiagExt.* Variable Bits reserved to future use. They aren’t 2..7 (Occulted reserved bits) shown at the symbolic structure (hidden). 5 reserved bytes to future use. They aren’t %QB(n+50) abyReservedBytes[1..5] shown at the symbolic structure (hidden).
  • Page 359 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedCmdLoc.* Variable TRUE – It’s a processed copy from the TURN ON PLCX button written on the PX2612 panel. This bit is activated 1 sec- ond after the button pressing and deacti- bButtonTurnOnLocal vated immediately at its releasing.
  • Page 360 6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedCmdLoc.* Variable FALSE – The reset commands for the NETA / NETB statistics in the local PLC wasn’t activated. TRUE – This command puts the PX2612 panel in test mode, allowing its com- ponents to be tested (LEDs, relays and buttons), as explained in PX2612 Panel...

  • Page 361: User Information Exchanged Between Plca And Plcb

    6. REDUNDANCY WITH NX3030 CPU variable Direct Variable DG_NX4010.tRedundancy. Description RedCmdLoc.* Variable TRUE – This command produces an equiv- alent action to the ResetNETStatisticsLo- bResetNETStatisticsRemote cal button on the PX2612 in the remote PLC. FALSE – The reset commands for the NETA / NETB statistics in the remote PLC wasn’t activated.

  • Page 362: Redundancy Event Log

    6. REDUNDANCY WITH NX3030 CPU 6.6.4.5. 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, register in the System Log relevant modifications in the diagnostics data structure fields and redundancy commands structure data.

  • Page 363: Buttons Test

    6. REDUNDANCY WITH NX3030 CPU 6.6.5.4. Buttons Test At pressing a button in the test mode, a correspondent LED stops blinking, and remains on. The following table presents the connection between the pressed button and the LED which remains on. Tested button Correspondent LED TURN ON PLC A...
  • Page 364 6. REDUNDANCY WITH NX3030 CPU Turn off the DG_NX4010.tRedundancy.RedCmdLoc.bTestRelayLocal command bit in the Active PLC. It must be ob- served 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.

  • Page 365: Maintenance

    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).
  • Page 366 7. MAINTENANCE 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.

  • Page 367: Diagnostics Via Led

    To remove this diagnostic from the CPU, a hot swap must be done in the module where the diagnostic is active. For further details on the procedure for viewing the diagnostics of the CPU or other bus modules, see description in the User Manual Nexto Series – MU214600. 7.1.2. Diagnostics via LED This product have a LED for diagnostic indication (LED DG) and a LED for watchdog event indication (LED WD).

  • Page 368: Rj45 Connector Leds

    Table 220: Ethernet LEDs Meaning 7.1.3. Diagnostics via WEB Besides the previously presented features, the Nexto Series brings to the user an innovating access tool to the system diagnostics and operation states, through a WEB page. The utilization, besides being dynamic, is very intuitive and facilitates the user operations. The use of a supervisory system can be replaced when it is restricted to system status verification.
  • Page 369 7. MAINTENANCE Figure 191: Initial Screen There is also the “System Overview” tab, which can be visualized through the Rack or the present module list (option on the screen right side). While there is no application on the CPU, this page will display a configuration with the largest available rack and a standard power supply, connected with the CPU.

  • Page 370: Diagnostic Explorer

    SNMP. 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 128 Kbps.

  • Page 371: Diagnostics Via Variables

    7.1.5. 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 System_Diagnostics created automatically by the MasterTool IEC XE.
  • Page 372 7. MAINTENANCE Diagnostics Mes- Variable Direct Variable Description sage DG_Module.tSummarized.* Variable There is no active diagnostic. NO DIAG TRUE – There is a configuration problem CONFIG. bConfigMismatch in the bus, as the module inserted in the MISMATCH wrong position. FALSE – The bus is configured correctly. TRUE –...
  • Page 373 7. MAINTENANCE Diagnostics Mes- Variable Direct Variable Description sage DG_Module.tSummarized.* Variable FALSE – The COM 1 serial interface con- figuration is correct. TRUE – Some error occurred during, or af- COM2 CONF. bCOM2ConfigError ter, the COM 2 serial interface configura- ERROR tion.

  • Page 374: Detailed Diagnostics

    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.
  • Page 375 7. MAINTENANCE Variable Direct representation Size Description DG_Modulo.tDetailed.* NX3003 = 0x3003 Target. NX3004 = 0x3004 %QD(n+4) DWORD dwCPUModel NX3005 = 0x3005 NX3010 = 0x3010 NX3020 = 0x3020 NX3030 = 0x3030 BYTE Target. %QB(n+8) Firmware version. ARRAY(4) abyCPUVersion BYTE Target. %QB(n+12) Bootloader version.
  • Page 376 7. MAINTENANCE Code Description Code Description 0x0019 Download rejected. 0x0100 Data type misalignment. Project not loaded, as the retentive 0x001A 0x0101 Arrays limit exceeded. variables cannot be reallocated. 0x001B 0x0102 Project not loaded and deleted. Division by zero. 0x001C Out of memory stack. 0x0103 Overflow.
  • Page 377 7. MAINTENANCE Variable Direct representation Size Description DG_Module.tDetailed.* The CPU was restarted due the active watchdog Reset. %QX(n+36).1 in the last startup. bWatchdogReset Table 228: Reset Detailed Diagnostics Group Description Note: Brownout Reset: The brownout reset diagnostic is only true when the power supply exceed the minimum limit required in its technical characteristics, remaining in low-voltage, i.e.
  • Page 378 7. MAINTENANCE Variable Direct Variable Size Description DG_Module.tDetailed.* Protocol selected in the COM 2: Serial.COM2. %QB(n+67) BYTE 00: Without protocol byProtocol 01: MODBUS RTU Master 02: MODBUS RTU Slave 03: Other protocol Counter of characters received from COM 2 (0 Serial.COM2.
  • Page 379 7. MAINTENANCE vari- Direct representation Size Description able_Modulo.tDetailed.* BYTE Ethernet.NET1. %QB(n+173) MAC NET 1 Address. ARRAY(6) abyMAC Counter of packets sent via NET 1 port (0 to Ethernet.NET1. %QD(n+179) DWORD 4294967295). dwPacketsSent Counter of packets received through NET 1 port Ethernet.NET1.
  • Page 380 7. MAINTENANCE vari- Direct representation Size Description able_Modulo.tDetailed.* STRING Ethernet.NET2. %QB(n+270) MAC NET 2 address. (17) szMAC BYTE Ethernet.NET2. %QB(n+288) NET 2 IP address. ARRAY(4) abyIP BYTE Ethernet.NET2. %QB(n+292) NET 2 Subnet Mask. ARRAY(4) abyMask BYTE Ethernet.NET2. %QB(n+296) NET 2 Gateway Address. ARRAY(4) abyGateway BYTE...
  • Page 381 7. MAINTENANCE vari- Direct representation Size Description able_Modulo.tDetailed.* Status of the memory where user logs are in- UserLogs. %QB(n+356) BYTE serted. byMounted UserLogs. %QW(n+357) WORD User log memory free space in Kbytes. wFreeSpacekB UserLogs. %QW(n+359) WORD User logs memory storage capacity in Kbytes. wTotalSizekB Table 235: Detailed Diagnostics Group UserLogs Variable...
  • Page 382 7. MAINTENANCE Code Enumerable Description This state is presented while other states are not ready. INITIALIZING Application in Stop Mode due to hardware watchdog re- RESET_WATCHDOG set or runtime reset, when the option “Start User Appli- cation After a Watchdog Reset” is unmarked. Application in Stop Mode due to Absent Modules diag- ABSENT_MODULES_HOT_SWAP_ nostic being set when the Hot Swap Mode is "Disabled"...
  • Page 383 7. MAINTENANCE Variable Direct representation Size Description DG_Module.tDetailed.* Informs the operation state of the CPU: Application. %QB(n+631) BYTE 01: All user applications are in Run Mode byCPUState 03: All user applications is in Stop Mode Application. %QX(n+632).0 There is one or more forced I/O points. bForcedIOs Table 239: Application Detailed Diagnostics Group Description vari-...

  • Page 384: Diagnostics Via Function Blocks

    7. MAINTENANCE vari- Direct representation Size Description able_Modulo.tDetailed.* SOE[1]. %QW(n+661) WORD Customer Queue Event Counter 01 wEventsCounter SOE[2]. %QX(n+663).0 Client Connection Status 02 bConnectionStatus Client event queue status 02: SOE[2]. %QX(n+663).1 FALSE - No overflow bOverflowStatus TRUE - Queue limit exceeded SOE[2].
  • Page 385 7. MAINTENANCE Below, the parameters that must be sent to the function for it to return the application information are described. Input parameter Type Description psAppName POINTER TO STRING Application name. psTaskName POINTER TO STRING Task name. POINTER TO stTask- Pointer to receive the application informa- pstTaskInfo Info...

  • Page 386: Graphic Display

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

  • Page 388: System Log

    7.5. Power Supply Failure The Nexto Series Power Supply (NX8000) has a failure detection system according to the levels defined in its technical features (see Power Supply 30 W 24 Vdc Technical Characteristics - CE114200). There are two ways to diagnose a failure: 1.

  • Page 389: Common Problems

    Is the Ethernet network cable properly connected to the Nexto CPU NET 1 or NET 2 port and to the network device? 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...

  • Page 390: Preventive Maintenance

    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.

  • Page 391: Annex. Dnp3 Interoperability

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

  • Page 392: Dnp V3.0 Implementation Table

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

This manual is also suitable for:

Nx3030

Table of Contents