High Intensity Training-AdvancedDescripción completa
Advanced Reiki Training
LearnFull description
sprint trainingFull description
Descripción completa
PROII Advanced TrainingFull description
The catalog showing training for optimization tool. Geo-locations.Full description
Descripción completa
Advance Training for STAAD
LearnFull description
High Intensity Training-AdvancedFull description
advance steelDescripción completa
iX HMI Software
Area for red ”header box” (8,09x1,26)
Area for ”big and left” picture
Area for ”right” picture
Position from top left corner:
Position from top right corner:
Horizontal 0,5 cm Vertical 0,5 cm
Horizontal 0 cm Vertical 0,5 cm
iX Developer – Advanced Training Version 2.0.7
Agenda Basic
Advanced ▪
A1.
Visualizatio Visualization n - Objects Objects
▪
B1.
General
▪
A2.
Alarm Client / Server
▪
B2.
Basic Steps I
▪
A3.
Alarm Distribution
▪
B3 .
Basic Steps II
▪
A4.
Data Exchange
▪
B4.
Dynamics
▪
B5.
Controller Control ler + Tags
▪
A5.
Datalogger/Trend Dynamics
▪
B6.
Actions
▪
A6.
Chart
▪
B7.
Alarm Server
▪
A7.
Audit Trail
▪
B8.
Security / User Management
▪
A8.
Report Generator
▪
B9.
Trend
▪
A9.
Screen Alias
▪
B10.
Recipe
▪
A10.
Expressions
▪
B11.
Media Controls
▪
B12.
Multi Language
▪
A11.
Web Server
▪
B13.
Text Library
▪
A12.
OPC UA Client / Server
▪
B14.
Project / Panel Handling
▪
B15.
Hints + Error Support
Agenda ▪
A1. Visualization – Objects Action Action Menu Menu - Genera Generall Action Menu – Settings Action Menu – Actions Touch Objects – General Touch Objects – Settings Screen ID Exercise [A1]
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Action Action Menu Menu - Genera Generall ▪
Inspired by mobile GUI
▪
Touch scroll and gesture support
▪
Actions are executed when clicking on an item
▪
Three different styles (Tab, (Tab, Expand and Bar)
Tab
Expand
Bar
Action Action Menu Menu - Settin Settings gs Style: Can be either Tab, Expand or Bar Item Width/Height: Size of each item in the menu Picture Width/Height: Size of picture (included in item) Scrollbar Width: Decides the width of the scrollbar. Value 0 removes the scrollbar
Scroll Sensitivity: Sets the sensitivity of the scroll. Minimum value is 1, maximum value is 10.
Action Action Menu Menu - Action Actionss
Edit Actions: Configure Groups, Symbol, Text and Action for each item in the menu
Menu Groups: Possible to Add/Delete groups Each group consists of: Name: Also serves as the group’s text Picture: Select which picture that should be used
Actions: Possible to Add/Delete items in each group Each item consists of: Text: The item’s text Picture: Select which picture that should be used Action: Decide what should happen when clicking on the item
Touch Touch Obje Objects cts - Genera Generall ▪
Inspired by mobile GUI
▪
Touch scroll and gesture support
Touch ListBox
Scrollable through gestures The item’s item’s height is i s configurable
Roller Panel
User can “roll” with touch gestures, thereby changing tag value
Touch Combobox
Scrollable through gestures The item’s item’s height is i s configurable
Touch Touch Obje Objects cts - Settin Settings gs Configuration of the objects is very similar
Settings: Mainly size properties (e.g height of item, width of scrollbar) Configure Texts: Opens dialog where texts can be defined
Scroll Sensitivity: Sets the sensitivity of the scroll. Minimum value is 1, maximum value is 10.
Configure Texts Dialog: Select tag that shall control which text that is focused Each text is mapped towards a Start/End Value range. If the value of the tag is within the range then that text gets focus
Screen ID ▪
A Tag Tag can control which screen that should be opened, this is done with the Screen ID
▪
Example: Jump to a specific screen when an alarm condition is fulfilled
Each Screen can be assigned a ScreenID The ScreenID needs to be unique
System Tags Current Screen ID: Displays value/ID of the current screen New Screen ID: When value is changed iX RT will look for screen with that ID (and change screen)
Exerc Exercise ise 1 - Menu Menu Exercise [A1] 1. Open the templa template te application application 2. Update the PopupMenu screen, it shall be possible to navigate to the following screens: - Home - AlarmH AlarmHist istory ory - TrendHistory rendHistory - Config Configura uratio tion n - AuditH AuditHist istory ory It shall also be possible to Login/logout from the PopupMenu screen 3. Test the application application and and make sure sure that the the menu works as intended
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2. Alarm Client/Server General Alarm Server Alarm Client Exercise [A2]
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Alarm Alarm Client Client / Server Server - General General ▪
The Alarm Server distributes alarms to all connected Alarm Clients (via Ethernet)
▪
The alarm configuration and storage is done only on the Alarm Server
▪
Simple and efficient method, to have the same, actual alarms synchronized on different Panels
▪
Changes (e.g. Acknowledge) in one Client updates all connected Clients
Alarm Server Topology: Alarm1 Alarm2 Alarm3
Alarm1 Alarm2
Alarm1
Alarm3
Alarm2 Alarm3
Alarm Client Alarm Client
Remote Alarm Server ▪
Alarm Server = Definition, creation and generation of alarms Alarm Client = Synchronizes with the server and displays displays the server server alarms.
Clic Click k on Settings and select the Server Mode tab
Server Mode: Both Server Port: 1000 1000 is just an example, Client Panels must use the same Port
Alarm Basics is covered in the BASIC Training
Alarm Client ▪
Alarm Server = Definition, creation and generation of alarms Alarm Client = Synchronizes with the server and displays displays the server server alarms.
Click on the Alarm Viewer Control
Extended Settings (available in Property Grid) Server Address: [IP of the Server] Clients connect to the entered IP Address Server Port: 1000 1000 is just an example, configuration must correspond correspond to the server setting
Exercise 2 – Remote Alarm Server Exercise [A2] 1. Work two two and two two 2. Configure Configure the Remote Remote Alarm Server Server functionalit functionality y on panel one 3. Configure the Remote Remote Alarm Client/Viewer on panel two 4. Run the applications and make sure that the alarm viewers are synchronized
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3. Alarm Distribution General Configuration Enable Distribution Server Demonstration
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Alarm Distribution ▪
The Alarm Distributor Server makes it possible to send alarm notifications via printer, SMS or E-mail
▪
The function can be either local (connecting to an “internal” server) or external (connecting to another panel acting as alarm distributor server)
Alarm Distributor Client
Alarm Distributor Server
Printer
E-mail
SMS
Alarm Distributor – Configuration
Add Alarm Distributor to the application Insert Alarm Distributor
Add: Adds a route to the server A route defines a number of filtering rules for distribution distribution of alarms. Multiple routes makes it possible to send different kinds of notifications to various receivers.
Delete: Deletes the selected route Address Book: Contains list of all users (e-mail/phone (e-mail/phone number) Receiver Selection: Select which users that should be notified when alarm occurs Configure Distribution Devices: Configure Printer, Printer, SMTP Client and SMS provider
Alarm Distributor – Address Book
Address Book: Each user needs to have: First Name (mandatory) Last Name (optional) E-mail (optional) Phone number (optional)
Receiver Selection: Select which users that should receive SMS or Email. It’s also possible to decide if the alarms should be printed. Use the << or >> buttons to add/remove receivers to routes.
Alarm Distributor – Schedule & Filter
Filter (Optional): Define which alarms that should be distributed, e.g alarms in a Group named “Critical” Define which alarm states that should be distributed (default: Active only)
Scheduler (Optional): Scheduling of each alarm distribution route can be configured in the Scheduler tab. Only alarms that occur between the start and stop times will be distributed. distributed.
Example: One route per production shift (day, evening, night)
Alarm Distributor – Email Settings E-mail Device Settings From name: Name From Email Address: Optional E-mail SMTP Server Name/IP: Address of SMTP server that will receive the alarm E-mails. Port: SMTP Server’s port number (default 25) Code page: 65001 = Unicode. If a limited E-mail client is used then it’s possible to define other code pages Authentication Mode: Decide if Authentication should be used or not. User Name/Password: Required in order to connect to Email server that requires ASMTP Subject/Body: Define the e-mails subject and content. {n} Texts are populated automatically by iX Runtime (e.g Alarm text = {3})
Alarm Distributor – Print Settings
Print Settings Buffer settings: Decide if alarms shall be printed directly or when the buffer is filled Text Font Size: Font size used for the printout Body: Define the text that shall be printed. {n} Texts are populated automatically by iX Runtime (e.g Alarm text = {3})
Alarm Distributor – SMS Settings
SMS Device Settings Basic URL: URL to http service (e.g 42it.eu) Distribution: Number of retries and interval between each retry Body: Define the text that shall be sent via SMS. {n} Texts are populated automatically by iX Runtime (e.g Alarm text = {3})
Alarm Distributor – Enable Distribution Server
To enable sending alarms to printer, via SMS or e-mail, the Alarm Distributor Service must be enabled
Internal: Alarm Server sends events to internal Alarm Distributor Service External: Alarm Server sends events to an Alarm Distributor Service running on another panel/runtime
In addition to the settings above, the Enable Distribution option for the alarm groups and alarm items also has to be checked
Demonstration We will... 1. Add a few alarms alarms to the application application 2. Add the Alarm Distributor service to the template application 3. Configure the service so that it sends alarm e-mails to [email protected], [email protected], SMTP: 192.168.98.1 4. Run the application and make sure that the alarms are distributed as e-mails
E-mail
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4. Data Exchange General Configuration Triggers Exercise [A3]
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Controller Controller Data Exchange Exchange - General General ▪
Allows for real-time data exchange between controllers, even of different brands
▪
Selectable per tag
▪
Exchange can be triggered on event or time
Controller Controller Data Exchan Exchange ge - Configurat Configuration ion Open the Tag Editor
By clicking on the “…”-button it’s possible to configure the direction of the Data Exchange It’s possible to transfer a value from one controller to several other controllers
Example The value of D0 [Melsec] will be transferred to both DB10.DBW0 [Siemens [Siemens]] and Temperature [AB ControlLogix]
Controller Controller Data Exchange Exchange - Trigger Trigger The data exchange can be triggered when: Value Change (default): When iX detects that the value has been updated then it will write the new value to the other controller(s)
Trigger: Can either be triggered on Time or when a tag changes it’s value Performance Considerations: Value Change will generate separate Write requests which might affect the application’s performance If a Trigger is used iX will try to fit as many tags in one write telegram as possible. Therefore it’s recommended to use consecutive addresses in the data exchange configuration.
Exercise 3 – Data Exchange Exercise [A3] 1. Add Add a new new Modbus driver to the application 2. Confi Configur gure e the Modbus driver to connect to the localhost Simulator.
Controller Settings: Communication Mode = Ethernet IP Address = 127.0.0.1 (localhost), Port = 502 3. Configure Configure the applicati application on so that TankLevel1 (D0) is moved to ModbusReg0 (40000) 4. Use a data trigger as initiator (to get the best performance) performance),, try both tag tag and time time 5. Run the application and make sure that data is transferred between the two Controllers
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5. Datalogger/Trend Dynamics General Historical Dynamics Exercise [A4]
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Advanc Advanced ed Trendi Trending ng - Genera Generall ▪
In the basic training we introduced the Datalogger and T Trend rend Object
▪
In the advanced course we will dig deeper in the trend object‘s dynamics
▪
First parts will be repetition Edit Curves: Name of the curve Tag that displays the actual value Log Item for historical trend data Expression(e.g. Expression(e.g. Gain, Offset) Color of the curve Thickness of the curve Tag (Optional) (Opt ional) Minimum Value Tag Maximum Value Tag Tag (Optional) (Op tional)
Value Scale Scal e Min./Max. Value of the Scale Major/ Minor Ticks of the Scale
Tren Trend d - Gene Genera rall
Time Scale Time Range: Time Span which is displayed Major Ticks for Time Scale
Visibility Show Scale Show Grid
Style Different predefined Styles for the Trend Viewer
Trend – Historical ▪
Add new Logitem
Delete selected Logitem
Free definable name (= ColumnName in database Table)
By clicking on Insert Data Logger a new Data Logger is added to the Project
Configure DataLogger Settings
Tag that shall be logged
Trend – Historical
Log on time or triggered by a tag (minium: 1s)
Max number of logged rows
Trend – Historical ▪
Select which log items that should be presented/visualized
Trend – Dynamics
Trend Dynamics – Value Scale Min/Max Min /Max Tags that define the maximum/minimum Value of the Trend‘s Y-axis Y-axis Can be used to Zoom in/out to get a more Detailed view
Runtime The tags (Ymax and Ymin) controls the Trend Viewer‘s Viewe r‘s Y-axis Y-axis properties
Trend – Dynamics Trend Dynamic Dynamicss – Time Span Tags that defines the time range of the TrendViewer‘s X-axis (in seconds) Can be used to Zoom in/out to get a more Detailed view
Runtime The tag (TimeSpan) controls the Trend Viewer‘s Viewe r‘s X-axis X -axis property
38
Trend – Dynamics Trend Dynamics – Time Offset Tag that defines a historical offset If the tag value is 60 it means that the Trend Viewer will jump 60 seconds back in time. Can be used to Pan forward/backward in time
Runtime (Trend is in History mode) – Example 1 Tag value = 0 -> X-axis start time = time when Trend Viewer entered history mode (19:58:00) Since the trend is in History mode the automatic Update is paused.
39
Trend – Dynamics Runtime (Trend is in History mode) – Example 2 Time when Trend Viewer entered history mode is: (19:58:00) Offset value: 30 seconds X-axis time = 19:58:00 – 30 = 19:57:30 Since the trend is in History mode the automatic Update is paused.
Runtime (Trend is in History mode) – Example 3 Time when Trend Viewer entered history mode is: (19:58:00) Offset value: 30 seconds X-axis time = 19:58:00 – 30 = 19:57:30 Time Span = 2 minutes X-axis end time = 19:58:00 – 30s – 120s = 19:55:30
40
Trend – Curve Visibility Trend Viewer Legend Shows a predefined Dialog to: Make Curves visible/invisible visible/invisible Show the actual Tag Values Values
Script Alternative With script it’s possible to control the visibility of each curve Can be useful if the end-customer wants a certain look or prefers bigger/smaller buttons
41
Exercise 4 – Historical Trend Exercise [A4] 1. Add a Trend Viewer object to TrendHistory screen 2. Add a DataLogger to the application, it shall log the following tags (every second): - TankLevel1 ankLevel1 - Valve alve1 1 3. Connect the Trend Trend Viewer to the data logger. logger. Use an Expression to add Offset/Gain to the boolean curve 4. Configure the Trend Trend Viewer so that it‘s possible to Zoom and Pan Pan (both X- and Y-axises Y-axises)) 5. Add buttons that toggles the visibility of curves (using C#-script) 6. Run the application
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6. Chart General Configuration Actions Exercise [A5]
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Chart - General ▪
The chart object is used to display values of connected array tags
▪
The Chart object has support for many different styles, see a few examples below:
Area
Pie
Bar
Chart Chart - Config Configura uratio tion n
Array Tags The Chart object presents values from Array tags Array tags are defined in the normal Tag Editor. Select Data Type and the number of elements that should be included in the array ( Array Size).
Configuration Most of the Chart‘s settings are found in the General ribbon tab
Style: As for most other objects it‘s possible to select the Object‘s style (e.g Chrome or Black) Visibility: Defines if Scale, Header and Legend should be visible or not.
Chart Chart - Config Configura uratio tion n Axis Settings Visible/Grid Visible: Defines if Axis/Grid Axis/Grid shall be visible or not Automatic Min/Max: When Automatic Automatic is enabled the object checks the data series/array and determines min/max values automatically
Chart Settings Chart Types: Select which type of chart that should be used in runtime (e.g Bar or Area) 3D View: Enable/Disable 3D-drawing. More CPU-intensive!
Chart Chart - Config Configura uratio tion n
Name: Symbolic name for the data series
Size: Number of data points that will be presented
X/Y Tag: Array tags that will be presented
Axis Type: Which Axis (Y1 or Y2) that the series shall be connected to
Labels: It’s possible to associate each data point with a text (e.g Monday,Tuesday, .., Sunday)
Char Chartt - Acti Action onss Actions
Description Pan Down, Left, Right, Up Used to navigate in the Chart Reset View Chart is reset to default, Zoom and Pan values are reset Zoom In/Out Used to Zoom in or out in order to get a better overview of the presented data
Exerc Exercise ise 5 - Char Chartt Exercise [A5] 1. Add Add a Chart obje object ct to the the LevelChart screen and connec connectt it to the follow following ing tag: tag: TankLevelPerWeekday 2. Use TankLevelMonday – TankLevelSunday to simul simulat ate e diff differ eren entt arra array y valu values es 3. Test the different different settings/chart types 4. Run the application
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7. Audit Trail User Actions Tag Value Changes Viewer Backup Exercise [A6]
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Audit Trail – User Actions ▪
Audit Trail = Makes it possible to log/track operator actions – it‘s it‘s possib possible le to define which actions and tags that should be logged
Configuraton Log All/None : Check all/no checkbox FDA - Log entries entries are not overwritten - When 80% of the database database is filled: User warning + request to export data When Max. Database size is reached: Logging will be stopped and operator will be promted to export the database Cyclic Buffering - Logged Logged entries entries will will be overwritten (FIFO – oldest row will be deleted) Max. Database size [MB] Size of Audit Trail Database
Audit Trail – Tag Value Changes When Audit Trail is added two new columns becomes visible in the Tag Editor ( Others needs to be checked)
1. Log to Audit Trail Selects which Tags that should be logged 2. Audit Trail Trail Description Customized description
Custom Audit text: Static Static descript descriptions ions – not dependent dependent on tag’s tag’s value {0} = Tag‘s value berfore Write {1} = Tag‘s value after Write
Custom Audit text: Dynamic description, based on Tag value
Audit Trail – Viewer ▪
Audit Trail Trail Viewer presents the database‘s content (in runtime)
Configure Columns: Double click on the control Available, addable columns: Message: System generated message Description: Customizable description Value Before: Tag value before change Value After: Tag value after change Time Stamp: Date/Time when event occurred User Name: Name of user/operator user/operator
Audit Trail – Database Backup Auditt Tra Audi rail il Actions Database: can be exported/copied to:
USB media
Database Database -> -> CSV-file: CSV-file: can be exported/copied to:
USB media
SD Card
the Project folder “Project Files” The Project Files folder can be accessed via FTP . FTP functionality is enabled in the System tab (ribbon)
Exercise 6 – Audit Trail Exercise [A6] 1. Add AuditT AuditTrail to the application application 2. Enable ”Log to Audit Trail” Trail” for the following contro controlle llerr tags: tags: - Valve alve1 1 - Valve alve2 2 3. Add Add an AuditT AuditTrail Viewer Viewer object to the AuditHistory screen. Configure and decide which columns that shall be presented 4. Run the application
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8. Report Report Generat Generator or General Report Actions Exercise [A7]
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Repor Reports ts - Gene Genera rall ▪
The report generator generates excel reports based on an Microsoft Excel made report template
▪
The generated report can be printed or saved as an excel file (USB, SD or FTP)
Excel Template
Actions
1. Print
2. Save Save as *.xls *.xls
Generated Report
Reports – Tag values All Formattings, Graphics, Charts, Fonts, Colors, … can be freely configured. iX Tag values can be inserted into a cell by using a special Syntax:
<#Tag(TagName)> Examples: <#Tag(Application_PLC_PRG_Temp1)> = CoDeSys CoDeSys Tag <#Tag(SystemTagDateTime)> = iX System Tag
Excel Template has to be saved in the following format “Excel 97-2003-Worksheet (*.xls) ” Operator Panels (e.g TxA and TxB) can only print text. This means that included charts, symbols etc. are excluded
Reports – Database Step 1 Create a new Sheet and name it <#Config>. This sheet will contain all database querys. When the report is generated this sheet will not be included
Step 2 The database querys needs to be defined on Row10 (and below)
Step 3 The data retrieved from the SQL database, using the queries in the configuration sheet, can be presented in the report using Named ranges in Microsoft Excel. Select the needed number of columns (in this sample 2 (Time and LogItem1)) Select Insert
Name
Define
Reports – Database Step 4 Enter a name for the range. The name must be entered in the following format: “__QueryName__”. Replace “QueryName” with the name that you have chosen for your SQL query
Step 5 To present the data in the report, enter the following syntax into the cells included in the named range: <#QueryName.DatabaseColumnName>
Reports – Add Template to application
Add Template: Add Select Template
Excel Template will be copied to the folder: Project Files\Reports\Templates Files\Reports\Templates
Option 2: Save template in (Excel-) file with timestamp e.g. Farm_Report 01.05.2012 12.45.12.xls
Locations to save: - Project Project files folder folder
Project Files\Reports
- Brow Browse se Save as Dialog will be opened - Path ath
Input of absolute saving path
Exerc Exercise ise 7 - Repor Reports ts Exercise [A7] 1. Open the suppli supplied ed Excel templat template e 2. Mo Modi dify fy the the Basic Template sheet so that it presents the following information - Curren Currentt Time Time (SystemTagDateTime ) - Tank Level Level 1 (TankLevel1) - Tank Level Level 2 (TankLevel2) 3. Modify Modify the Advanced Template sheet so that it presents historical data collected by the the DataLogger 4. Insert Insert a button button with with a Generate Report action on the Configuration Screen 5. Simulate the application and make sure that the generated report is OK
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9. Scree Screen n Alia Aliass General Alias Definition Connect Alias to Object Instances Show Screen Instance Exercise [A8]
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Screen Screen Alias Alias - Genera Generall ▪
Screen Alias = An alias should be treated as a property of a screen and can act as a stand-in for a tag. The alias can be used to reference a tag wherever that tag can be referenced directly. directly.
▪
Using aliases will enable reuse of screens without having to create a new duplicated screen. 1.
Definition of Aliases, that can be defined as a stand-in stand- in for a “normal” tag
2.
Assign Alias to Objects
3.
Create (Screen-) Instances I nstances and assign the Original Tags Tags to them
Example: Popup with Alias function
Example: Screen Alias function
Screen Alias – Alias Definition
Add: Inserts a new Alias Delete: Delete Alias Checkbox Data Type: Show tag data type Alias Name: Free definable stand-in name for tags Default Value: Optional definition of a default tag Data Type: Optional selection of tag data type
Screen Alias – Connect Alias to Object
Normal/Default: Selects a Tag Alias Function: In the Tag selector dialog: Select Aliases and choose an Alias
Connect Alias instead of “real” tag to the object
An Alias always starts with a “#“-character
Screen Alias – Instances with Original Tags Add: Adds a new instance Delete: Deletes a screen instance Instance: Column is used to define a symbolic instance name Other Columns: Columns show the projected aliases (here with default values)
Filling / Pressure (Alias names): Columns show the projected aliases. Font Regular: Regular: Default Tags Tags Font Bold: Inserted, projected Original Tags
Screen Alias – Show Screen Instance
Instance Call: Use the Show Screen Action and select which Instance that should be opened/shown
In the Show Screen Action there is a list where the different instances can be selected
Exerc Exercise ise 8 - Alia Aliass Exercise [A8] 1. Th The e Val Valve vess on the the Hom Home e scre screen en shal shalll be controlled controlled from a common Popup/F Popup/Facepl aceplate ate 2. Add a new screen screen to the applicatio application n and define two aliases: (TankLevelAlias & ValveAlias) 3. Create 2 Screen instances, configure so that the aliases aliases are connected connected to tags tags as below: Screen Instance 1: Valve, TankLevel1 Screen Instance 2: Valve2, TankLevel2 4. When When clic clicki king ng on the the valv valves es the the corr correc ectt Faceplate Faceplate (= ScreenInsta ScreenInstance) nce) should should be opened
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. Express Expression ionss General Define Reuse Exercise [A9]
▪
A11.
Web Server
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Express Expression ionss - Genera Generall ▪
Expressions are used in order to scale and modify a tag’s actual value. It’s It’s only the presentation that is affected, not the tag’s “real” value
▪
Expressions enable the developer to e.g. extract a bit from an word, add a dynamic offset or gain, and then to use this value for a specific object
Value in PLC
Tag Value
23.1
Expression
Presentation
Express Expression ionss - Creati Creating ng
By clicking on the “…”“…”-button it’s possible to connect an Expression to the selected object/tag
New: Creates a new Expression Edit: Edit an existing Expression Delete: Delete the selected Expression
Express Expression ionss - Creati Creating ng Name: Name of the Expression Group: The Expression can be stored in a Group, this makes it easier to organize the Expressions Description: Comment/description, Comment/description, what is the purpose of the Expression?
Expression Code When the Expression has been created it‘s time to write the actual code
Expression Code Code that will execute every time the tag value updates. Follows normal C#-syntax Value is the tag‘s “raw” value The Expression Code can contain Tag-values, Operators and standard C#-functions (e.g Math.ABS) When an object is connected to an Expression the “…” will be replaced with a “+”-character “+”-character
Expressions – Reuse Expressions can be saved/loaded This makes it possible to reuse the Expression in future applications Library Expressions Load: Opens a dialog where the user can select which Expression(s) Expression(s) that should be imported Save: Saves the current Expression to a Library Delete: Deletes an Expression from a Library
iX Developer contains a few pre-installed pre-ins talled Libraries Bit Operators: Used to extract bits from words Math: Log, Log10, Sin, Cos, Tan Temp conversion: Celsius <-> Fahrenheit
Exerci Exercise se 9 - Expres Expression sionss Exercise [A9] 1. Add an alarm alarm indicator indicator to the the Home screen, make sure that it‘s Visible and Blinks when the Tank Level (TankLevel2) is greater than 90 %
2. Run the application and make sure that the configured Expression works as intended
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11. Web Server General HTML Configuration Writing Values Exercise [A10]
▪
A12. A1 2.
OPC OP C UA Cli Clien entt / Serv Server er
Web Server – General Web Server = On each iX panel, a simple web server can be activated. ▪
iX remote maintenance
▪
Screens can be projected with every ever y HTML editor
▪
Compact information (overview)
▪
JavaScript
Ethernet / Internet
iX 2.20: Webserver supports 2 connections
Web Server – General Configuration
Description Web Server Configuration: System Web Server
Web Server Activation: Enables/disables the Web Server function Port: Free definable definable Port. Default: 80 Authentication settings: - Checkb Checkbox ox unch uncheck ecked: ed: Anonymous authentication - Checkb Checkbox ox check checked: ed: Username and password can be set
Web Server – General Configuration
Description - The files must must be stored in the folder: folder: [Project]\Project Files\WebSite
- Start art pa page: ge: index.html - For panel targets it’s necessary to download the websites via FTP
Attributes can be combined Additional info available in the iX Reference manual manual
Web Server – Writing values Syntax
Description
data-ix-setter="Tag1"/> Change value:
Example: Write Write value to tag when pressing submit button
Exerci Exercise se 10 10 - Webserv Webserver er Exercise [A10] 1. Enab Enable le Webserver in the application (with authentication) 2. Modify the basic HTML-page template, this allows you to read/write read/write values 3. Modify the Advanced HTML-page template, this contains 3:rd party graphical controls 4. Store Store the HTML-fil HTML-files es in the the Project Project Files/W Files/Websit ebsite e folder folder and run the application. Make sure that that the the pages pages are are work workin ing g corre correct ctly ly
Agenda ▪
A1.
Visualizati Visual ization on - Obje Objects cts
▪
A2.
Alarm Client/Server
▪
A3.
Alarm Distribution
▪
A4.
Data Exchange
▪
A5.
Datalogger/Trend Dynamics
▪
A6 .
Chart
▪
A7.
Audit Trail
▪
A8.. A8
Repo Re port rt Ge Gene nera rato torr
▪
A9 .
Screen Alias
▪
A10. A1 0. Ex Expr pres essi sion onss
▪
A11.
▪
A12. A12. OPC OPC UA Clie Client nt / Serv Server er
Web Server
General Server Configuration Client Configuration Tag Configuration Exercise [A11]
OPC UA – General OPC UA = OPC communication type (UA = unified architecture), which has evolved f rom the drawbacks of the existing OPC technology. Features: ▪
Setting up Panel Network (via Ethernet) for Tag Tag value exchange
▪
Panels can be configured as Server or Client (or both)
▪
Direct Communication to PLC‘s/Controller‘s or to generic ERP Systems
OPC UA – Server Configuration Server Configuration System OPC UA-Server
OPC UA-Server Activation Checkbox enables the OPC UA Server function
Port: Free definable Port. Default: 4840 Login: - Checkbox Checkbox enabled enabled:: Anonymous login is possible - Checkbox Checkbox not set set Username and password can be defined
OPC UA – Client Configuration
Add OPC UA Client driver Controller Control ler In Tag Editor - Check Check OPC UA-Ser UA-Server ver - Enter Enter IP Address Address of Server Server
OPC UA – Tag Configuration Tag Configuration Tag Configuration: Server
Tag Configuration: Client
Description - OPC UA Server Server (e.g. (e.g. T7A Panel) Panel) communicates communicates via ModBusTCP ModBusTCP protocol to a PLC Tag Name
Tag Address
Temperature Pressure
40000 40010
- OPC UA Client Client (e.g. (e.g. PC as control control station station)) communicates with OPC UA Server Tag Name
Tag Address
Temp_T7A Pressure_T7A
Temperature Pressure
Client
Tag Address = Name of Server Tag
Client Tag Name can be freely defined (does not need to match the the server syntax)
Exercise 11 – OPC UA Exercise [A11] 1. Work two two and two two 2. Configure one of the applications to act as OPC UA Server, Server, the other as OPC UA Client 3. Share at least least one tag via via the OPC UA-network, UA-network, make sure that it’s possible to both read/write values and that both Server/Client updates as expected