No olvidéis que lo que hacéis durante vuestra vida trasciende en la eternidad.
TALLERES DE APLICACIÓN DEL MÓDULO DE INVESTIGACIÓN Taller No 1 DETERMINACION DEL TEMA O TITULO
Functions (continued)
Modicon® Automation Platform
0
Unity Pro™ software
Integrated diagnostics
The system diagnostics for the Modicon M340, Atrium, Premium, and Quantum platforms supports the monitoring of system bits/words, and I/O modules, and the activity times (minimum/maximum) of SFC steps. After the user chooses the relevant option in the application configuration, any event will result in time-stamped messages logged inside the diagnostic buffer in the PLC. These events are displayed on a diagnostics viewer (1) automatically without the need of any additional programming. With the assistance of Unity Pro's integrated diagnostics, this function can be used to perform 1stlevel diagnostics of the elements in the configuration, up to and including each I/O module channel.
(1) Diagnostics viewers are tools used to display and acknowledge error messages relating to diagnostics. They are supplied as standard with Unity Pro, Vijeo Designer and Monitor Pro software, with Magelis terminals, and with the PLC web server which is accessible through a thin client Magelis iPCterminal.
Presentation
Diagnostics integrated into Modicon® M340™, Atrium™, Premium™ and Quantum™ automation platforms
The diagnostics offer for Modicon M340, Atrium, Premium, and Quantum platforms is based on three components:
b System diagnostics
b DFB and EFB diagnostic function blocks (for system and application diagnostics) b Error message display system or viewers supplied as standard with Magelis® XBT GT and iPC® terminals, Vijeo™ Designer/Monitor Pro™ supervisory software and Unity Pro setup software.
Functions
System diagnostics
Processor for system bits and words In-rack I/O modules Remote I/O modules on Fipio® bus or CANopen Higher-level M.E.S. Cell level Machine level Unity Pro Diagnostics viewers System diagnostics Application diagnostics Ethernet TCP/IP Vijeo Designer Monitor Pro
Thin client Magelis iPC
Magelis XBT GT Quantum,
Premium, Modicon M340
PC
Configuration level Module level
Channel level Viewer window (example with Unity Pro software)
4
Functions (continued)
Modicon® Automation Platform
0
Unity Pro™ software
Integrated diagnostics
Unity Pro software also has a library of function blocks for monitoring, called diagnostic DFBs and EFBs. The library of diagnostic function blocks contains:
b Manufacturer blocks for system diagnostics
v IO_DIA input/output fault, which is used to monitor the state of inputs/outputs. v ASI_DIA, which monitors whether an error has occurred on the AS-Interface bus (module or bus fault, no slave, slave not configured or faulty).
b Manufacturer blocks for application diagnostics, for example:
v EV_DIA, which monitors whether an event (bit status) has the correct value at a given time (no notion of timing).
v MV_DIA, D_GRP, D_REA, which monitor whether an event (the change in the status of a bit) occurs within the specified time conditions.
v ALRM_DIA, which monitors the combination of the status of 2 bits.
v NEPO_DIA and TEPO_DIA, which can be used to check, control and perform diagnostics for elements in the working part of the system made up of the combination of 2 actuators and 2 sensors.
b Open diagnostics blocks
These enable users to create their own diagnostic function blocks to meet the specific requirements of their applications and therefore to supplement the manufacturer DFBs and EFBs described above. They can be created from 2 model blocks, which must be written in Ladder (LD), Structured Text (ST), Function Block Diagram (FBD) or Instruction List (IL) language.
When a fault occurs, Unity Pro analyzes the program sections concerned and opens a second window displaying the causes and probable sources of the fault. The user or process operator is guided though the fault-finding process, enabling machine downtimes to be reduced.
The configuration module or instruction which is the source of the fault can also be accessed via the diagnostics viewer integrated into Unity Pro, directly from the alarm in the viewer output window (see page 4/22).
Application diagnostics
Diagnostics with fault cause analysis
ED COND ERROR STATUS AREA_NR OP_CTRL Usrst_dia Outputs Inputs
Fault cause analysis
Presentation: page 4/4 Setup: pages 4/5 to 4/8 Structure: pages 4/9 to 4/11 IEC language: pages 4/12 to 4/17 References: pages 4/29 and 4/31
4
Functions (continued)
Modicon® Automation Platform
0
Unity Pro™ software
Integrated diagnostics
Diagnostic viewers in Modicon® M340™, Atrium™, Premium™, and Quantum™ platforms automatically display diagnostic events for management of faults and alarms.
The viewer function is supplied as standard with: b Vijeo™ Look and Monitor Pro™ V7 supervisory software b Unity Pro programming software
b Magelis® XBT GT and Magelis®iPC HMI terminals
The viewer integrated in Unity Pro can also access the instruction or module which is the source of the fault. See “Diagnostics with fault cause analysis”, page 4/21. Modicon M340, Atrium, Premium and Quantumplatforms have multiviewer capability (can be used with a maximum of 15 viewers). A PC-compatible station with the viewer function can be multi-PLC (can be used with a maximum of 15 ModiconM340, Atrium, Premium, and/or Quantum platforms).
The viewer structure supports:
b A single point for fault management in each application b Time-stamping of the occurrence of faults at the source b Storage of intermittent faults in memory
b Viewer functioning that is independent of the viewer used. The frame is identical for all viewers.
b Automatic archiving of all error messages Output window
The diagnostics viewer takes the form of an output window divided into 2 sections: b A message list indicating, for each alarm: state, DFB type, geographical zone, dates and times of occurrence/correction associated message and status b An area for additional information about the selected message: type, comment, date of occurrence, specific data, variables in error state, etc.
The operator screen tool is integrated into Unity Pro. The operator screens are designed to facilitate the operation of automated processes during debugging, startup and maintenance. The operator screens provide a set of information (explanatory texts, display of dynamic values, push buttons, and synoptics), enabling users to act quickly and easily to modify and dynamically monitor PLC variables. The operator screens editor provides all the HMI elements needed for the animated design and viewing of processes. It enables these screens to be designed using specific tools:
b Screen: Create runtime screens, which can be classified according to family. b Message: Create messages to be displayed.
b Objects: Create a graphic objects library using:
v Geometrical elements (line, rectangle, ellipse, images, such as controller front panels.)
v Control elements (buttons, data entry fields, screen browsing controls, etc.) v Animation elements (colors, flashing elements, bar graphs, etc.)
When the station on which Unity Pro has been installed is connected to the PLC, the user can obtain a dynamic display of the screens according to the state of the process. Screen sequencing is possible, depending on the priority attributed, either via the keyboard or a PLC request.
When online, the Unity Pro application program can be accessed directly from the operator screens by clicking the selected object in a synoptic screen view. It is also possible to activate the animation table or cross-reference functions by selecting one or more variables on the screen. To make the display easier to read, the synoptic views can be displayed in full-screen view.
Since it is possible to build or modify an operator screen while the PLC is running, this service increases the productivity during the commissioning and maintenance phases. Diagnostics viewers
Operator screens
Viewer Presentation: page 4/4 Setup: pages 4/5 to 4/8 Structure: pages 4/9 to 4/11 IEC language: pages 4/12 to 4/17 References: pages 4/29 and 4/314
Functions (continued)
Modicon® Automation Platform
0
Unity Pro™ software
Unity Pro enables changes to be made to the program when the PLC connected to the programming terminal is in RUN. These modifications are made by performing the following operations:
b When necessary, transferring the application from the PLC to the PC terminal running Unity Pro.
b Preparing the program changes. These program modifications can be of any type and in any language (IL, ST, LD, FBD, and SFC), for example adding/deleting SFC steps or actions. Furthermore, modifications can be made to the code of a DFB user function block (although its interface cannot be modified).
b Updating the program in the PLC (in RUN) to reflect these program changes. This function allows program code and data in different parts of the application to be added or modified in a single modification session (thus making modification unified and consistent with regard to the controlled process). This increased flexibility comes at a cost in terms of the program memory volume required.
The Unity Pro Cross-References function, which is available in standalone mode (offline) and when connected to the PLC (online), allows users to view all the elements of a PLC application by searching for variables of any type. This view indicates where the declared variable is used as well as the mode in which it is used (write, read, etc.).
This function also provides access to the Search/Replace function for variable names.
The variables search can be initialized from any editor (language, data, runtime screen, animation table, etc.).
The import/export function available in Unity Pro supports the following operations from the structural and functional project views:
b Via the import function, to reuse all or part of a project created previously in the current project
b Via the export function, to copy all or part of the current project to a file for subsequent reuse
The files generated on export are generally in XML format (1). However, variables can also be exported or imported in the following formats:
b .xvm format compatible with OFS data server software
b Source format, in a .scy file compatible with PL7™ design software
b Text format with separator (TAB), in a .txt file for compatibility with any other system On import, data can be assigned to new instances of the following elements via an assistant:
b DFB function blocks b DDT data structures b Simple data
Furthermore, when importing a function module, the data associated with animation tables and operator screens is also reassigned.
The XML import function also supports the transfer of a Modicon® M340™, Atrium™, Premium™ or Quantum™ PLC configuration prepared in the SIS Pro costing and configuration tool for use in the creation of a project in Unity Pro.
This import function means that the user does not have to repeat the PLC configuration process when this has already been completed in the SIS Pro tool. (1) XML language: Open text-based language providing structural and semantic information.