advertisement
PX Developer Version 1
Operating Manual
(InTouch Interaction)
-SW1D5C-FBDQ-E
-SW1D5C-FBDQMON-E
SAFETY PRECAUTIONS
(Always read these instructions before using this product.)
Before using this product, thoroughly read this manual and the relevant manuals introduced in this manual and pay careful attention to safety and handle the products properly.
The precautions given in this manual are concerned with this product. For the safety precautions of the programmable controller system, refer to the User’s Manual for the CPU module.
In this manual, the safety precautions are ranked as " !
WARNING" and " !
CAUTION".
!
WARNING
!
CAUTION
Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.
Note that the !
CAUTION level may lead to serious consequences according to the circumstances.
Always follow the precautions of both levels because they are important for personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
[Startup/Maintenance Precautions]
!
CAUTION
The online operations have to be executed after the manual has been carefully read and the safety has been ensured.
Failure to do so may cause a miss operation which results in machine damage or an accident.
A-1 A-1
CONDITIONS OF USE FOR THE PRODUCT
(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions; i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the
PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.
(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.
MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED
TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT,
PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO
PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT
INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN
MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND
GUIDELINES FOR the PRODUCT.
("Prohibited Application")
Prohibited Applications include, but not limited to, the use of the PRODUCT in;
Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the public could be affected if any problem or fault occurs in the PRODUCT.
Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality assurance system is required by the Purchaser or End User.
Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for
Recreation and Amusement, and Safety devices, handling of Nuclear or Hazardous Materials or
Chemicals, Mining and Drilling, and/or other applications where there is a significant risk of injury to the public or property.
Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the
PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details, please contact the Mitsubishi representative in your region.
A-2 A-2
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print Date * Manual Number
Jun., 2008 SH(NA)-080773ENG-A First edition
Jun., 2008 SH(NA)-080773ENG-B Correction
Revision
Appendix 3.1
Jan., 2009 SH(NA)-080773ENG-C Correction
GENERIC TERMS, ABBREVIATIONS, AND TERMS, Section 2.1,
Section 3.4
Dec., 2009 SH(NA)-080773ENG-D Addition
CONDITIONS OF USE FOR THE PRODUCT
Correction
SAFETY PRECAUTIONS , Section 2.1, Section 3.4, Appendix 2
Dec., 2010 SH(NA)-080773ENG-E The manual name is changed from SCADA Interaction to InTouch
Interaction
Correction
GENERIC TERMS, ABBREVIATIONS, AND TERMS, Section 2.3
Oct., 2011 SH(NA)-080773ENG-F Addition
Appendix 4, Appendix 5
Correction
HOW TO USE THIS MANUAL, Section 2.3, Section 3.4,
Chapter 4, Appendix 2, Appendix 3.1, Appendix 3.2
Feb., 2014 SH(NA)-080773ENG-G Correction
Section 3.3.3, Appendix 2, Appendix 3.2
Jul., 2015 SH(NA)-080773ENG-H Front cover correction
Jan., 2017 SH(NA)-080773ENG-I
Correction
GENERIC TERMS, ABBREVIATIONS, AND TERMS, Section 2.1,
Section 2.3
Japanese Manual Version SH-080747-O
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.
2008 MITSUBISHI ELECTRIC CORPORATION
A-3 A-3
INTRODUCTION
Thank you for choosing the Mitsubishi MELSOFT series Integrated FA software.
Read this manual and make sure you understand the functions and performance of MELSOFT series thoroughly in advance to ensure correct use.
CONTENTS
SAFETY PRECAUTIONS................................................................................................................................A-1
CONDITIONS OF USE FOR THE PRODUCT ...............................................................................................A-2
REVISIONS ......................................................................................................................................................A-3
INTRODUCTION..............................................................................................................................................A-4
CONTENTS......................................................................................................................................................A-4
MANUALS ........................................................................................................................................................A-6
HOW TO USE THIS MANUAL ........................................................................................................................A-7
MANUAL ORGANIZATION .............................................................................................................................A-9
GENERIC TERMS, ABBREVIATIONS, AND TERMS .................................................................................A-10
1 OVERVIEW .............................................................................................................................................. 1-1
1.1
Overview............................................................................................................................................... 1-1
1.2
Features ............................................................................................................................................... 1-1
2 SYSTEM CONFIGURATION................................................................................................................... 2-1
2.1
System Configuration........................................................................................................................... 2-1
2.2
Software Configuration ........................................................................................................................ 2-2
2.3
Operating Environment........................................................................................................................ 2-2
3 BASIC OPERATION ................................................................................................................................ 3-1
3.1
Operating Procedures for Monitoring on InTouch............................................................................... 3-1
3.2
Operation to Communicate using PX Developer Process Control Tag Names in InTouch .............. 3-2
3.2.1
Registering access names............................................................................................................... 3-3
3.2.2
Defining tag source .......................................................................................................................... 3-4
3.2.3
Referring to and selecting tag names.............................................................................................. 3-8
3.3
Operation to Use Faceplates of PX Developer in InTouch............................................................... 3-10
3.3.1
Installing ActiveX control................................................................................................................ 3-11
3.3.2
Checking installation ...................................................................................................................... 3-12
3.3.3
Setting/pasting faceplate control ................................................................................................... 3-13
3.4
Operation to Display PX Developer Alarm Information on InTouch Alarm Viewer control.............. 3-14
3.4.1
Pasting Alarm Viewer control......................................................................................................... 3-18
3.4.2
Setting Alarm Query....................................................................................................................... 3-19
4 TROUBLESHOOTING ............................................................................................................................. 4-1
APPENDIX..........................................................................................................................................................B-1
Appendix 1 Details of Dot Field Name in the Tag Name Reference Function ..........................................B-1
Appendix 2 Main Tag Items.........................................................................................................................B-1
Appendix 3 Correspondence Table for Items of Monitor Tool and InTouch..............................................B-3
A-4 A-4
Appendix 3.1
Correspondence table for alarm items...............................................................................B-3
Appendix 3.2
Correspondence table for event items ...............................................................................B-4
Appendix 4 Security of Monitor Tool and InTouch .....................................................................................B-5
Appendix 4.1
Operating environment for using security of monitor tool and InTouch ............................B-5
Appendix 4.2
Setting procedure for using security of monitor tool and InTouch ....................................B-5
Appendix 4.3
Procedure for monitoring operation with security interaction between monitor tool and
InTouch .............................................................................................................................B-10
Appendix 5 Functions Added to and Changed from Old Version ............................................................B-11
INDEX .................................................................................................................................................................C-1
A-5 A-5
MANUALS
The following manuals are also related to this product.
Refer to the following table for ordering a manual.
Related manuals
Manual name
PX Developer Operating Manual (Programming Tool)
Explains FBD language programming, compilation, online operations, and debug methods with PX separately.)
PX Developer Operating Manual (Monitor Tool)
Explains the operation methods of the monitor tool and methods for monitoring and controlling DDC processing with tag FB.
PX Developer Programming Manual
(Sold separately.)
Explains details of programming with PX Developer, lists of FB parts, and the PID instructions.
(Sold separately.)
Manual number
(model code)
SH-080369E
(13JU38)
SH-080370E
(13JU39)
SH-080371E
(13JW00)
CAUTION
• Please note that we do not guarantee commercially available software compatible with Microsoft R Windows R Operating System introduced in this manual.
• The software copyright of this product belongs to Mitsubishi Electric Corporation.
• No contents in this manual can be reproduced or duplicated in any form or by any means without permission.
• Although we make utmost efforts, this manual may not completely follow the revisions of the software and hardware.
• In principle, this software should be purchased by one set per personal computer or by license purchase.
• This product (including this manual) can only be used under the software license agreement.
• Please note that we are not responsible for any influence resulting from operating this product (including this manual).
• The contents of this manual are subject to change without notice.
A-6 A-6
HOW TO USE THIS MANUAL
PURPOSE
Describes the purpose of operations for each chapter or section.
Setting on InTouch WindowMaker
Describes operating procedures.
A-7
Execution on InTouch WindowViewer
Describes functions to be executed.
Reference location
leads to the reference location.
A-7
There are also the following types of explanations.
BASIC OPERATION
Explains operation methods.
DISPLAY/SETTING SCREEN
Screen to display/set items.
DISPLAY/SETTING DATA
Explains items in DISPLAY/SETTING SCREEN.
POINT
Informs items to be noted and useful functions relevant to the contents in the chapter or section.
The following table explains symbols in this manual and their description.
Symbol
[ ]
( )
" "
<< >>
Description
Expresses an item in a window or dialog box, or a menu on the menu bar.
[ ] [ ] expresses the drop-down menu.
Example: [Special] [Configure]
Expresses a corresponding button.
Example: "Define Tag Source" button ( )
Expresses a command button.
Example: "OK" button
Expresses dialog box tab.
Example: <<General>> tab
A-8 A-8
MANUAL ORGANIZATION
This manual consists of four chapters and APPENDIX.
This manual is organized assuming that the interaction function of the PX Developer monitor tool and SCADA software are utilized in the following procedure.
< Procedure for leveraging the interaction function with InTouch>
Operating procedure 1: Using the tag name reference function of InTouch WindowMaker, assign process control tags of PX Developer to the tag variables.
• Set an access name.
• Refer to tag names and assign process control tags.
Reference
Section 3.2
Operating procedure 2: Paste a faceplate control of PX
Developer monitor tool on InTouch
WindowMaker.
• Install ActiveX control.
• Paste/set a faceplate control.
Reference
Section 3.3
• PX Developer Operating Manual
(Monitor Tool)
Operating procedure 3: Set to display alarm/event information of the PX Developer monitor tool on the
Alarm Viewer control of InTouch
WindowMaker.
• Paste/set Alarm Viewer control.
Operating procedure 4: Execute InTouch WindowViewer.
*For operating procedures and setting items, refer to the manual of InTouch.
Reference
Section 3.4.1
A-9 A-9
GENERIC TERMS, ABBREVIATIONS, AND TERMS
The following table shows the generic terms, abbreviations, and terms in this manual.
(1) Generic terms and abbreviations
Generic term/abbreviation
PX Developer
Description
Generic term for PX Developer Version 1 (SW1D5C-FBDQ-E) and PX Developer
Monitor Tool (SW1DNC-FBDQMON-E)
For PX Developer, Programming Tool and Monitor Tool are installed.
For PX Developer Monitor Tool, only Monitor Tool is installed.
Abbreviation for PX Developer programming tool Programming tool
Monitor tool
OPS
Server
Client
Abbreviation for PX Developer monitor tool
Abbreviation for Operator Station
Abbreviation for a monitor tool which starts up as Server in the server/client monitoring system interacting with multiple OPSs
Abbreviation for a monitor tool which starts up as Client in the server/client monitoring system interacting with multiple OPSs
InTouch
Windows Vista R
Abbreviation for Wonderware R
Generic term for Microsoft R
R Microsoft
Microsoft R
Windows Vista R
Windows Vista R
Microsoft
Microsoft
R
R
Windows Vista R
Windows Vista R
InTouch R Version 10.0 or 10.1
Windows Vista R Home Basic Operating System,
Home Premium Operating System,
Business Operating System,
Ultimate Operating System, and
Enterprise Operating System
Generic term for IBM-PC/AT-compatible personal computer Personal computer
(2) Terms
Term Description
WindowMaker Development environment of InTouch
WindowViewer Execution environment of InTouch
I/O server Communication driver for Wonderware R
DDE
DDC
FB
Tag
Tag data
Tag data item
Abbreviation for Dynamic Data Exchange
Windows R standard communication protocol between applications
Abbreviation for Direct Digital Control
A control of controller functions with a digital device.
Abbreviation for Function Block
A block with a specific function used in a program.
Tags for identification attached to process control equipment.
They are JIS-defined identification symbols attached to DDC processings.
Organized data (process condition data, process status data) attached to DDC processing which is indicated by tag.
Accessing this tag data allows monitoring and condition setting of a corresponding DDC processing.
Each data item that makes up tag data
Tag FB A function block works as a controller or an indicator containing tag data
Faceplate
SV
Gauge window on which an indicator such as a controller is displayed in image format
Values assigned to tag data are manipulated.
Setting value
PV Process variable
MV Manipulated variable
Assignment information database
"*.mdb" file which is created when compilation is executed in the programming tool
This file stores assignment information of variables for storing data such as tag data, global variable and device information of the CPU module.
A-10 A-10
1 OVERVIEW
MELSOFT
1 OVERVIEW
1.1 Overview
In addition to the basic monitoring function of the monitor tool, outstanding and easyto-use InTouch development/monitoring environment can also be available by using the interaction function of the PX Developer monitor tool and InTouch (SCADA software manufactured by Invensys Systems, Inc.).
This function supports the following four interaction functions.
(1) Incorporating faceplate control
(2) Communication function using process control tag names
(3) Reference function for PX Developer tag names
(4) Alarm integration function
1.2 Features
This section explains the main features of the four interaction functions.
(1) Faceplate control reduces development time of monitor screens
By simply pasting the faceplate control of PX Developer (ActiveX control) on the monitor screen of InTouch, faceplates can be easily used on InTouch.
This function reduces development time of monitor screens and tuning screens for process control tag data on InTouch.
[Image of incorporating faceplate control] PX Developer faceplate control
PX Developer monitor tool
InTouch
WindowViewer
1
Reading/writing process control tag data
Polling process control tag data
Faceplates can be used by only pasting
ActiveX control on the InToucn screen.
1-1 1-1
1 OVERVIEW
MELSOFT
1
(2) Without considering assigned devices, communications can be performed using process control tag names in InTouch
When registering tag variables in InTouch, PX Developer process control tag names can be used as item names, and process control tag data in the monitor tool can be read from/written to InTouch.
This eliminates the need for managing assigned devices and communicating through a communication driver such as an I/O server to read/write process control tag data.
Furthermore, high-speed response by the event notification receive function and the high-speed current value collection function of the monitor tool can be utilized on InTouch.
[Image of the communication function using process control tag names]
PX Developer monitor tool
InTouch
WindowViewer
PV value of the process control tag FIC001
Reading/writing process control tag data
Registration of tag variable with the process control tag name "FIC001.PV"
High-speed current value collection
Event notification receive
Unnecessary for reading/writing process control tag data .
Communication driver such as I/O server
Without considering assigned devices for the process control tags, communications can be performed by registering tag variables on
InTouch, using process control tag names defined in PX Developer.
*1: When reading/writing device data except the process control tag with InTouch, a communication driver such as I/O server is required.
1-2 1-2
1 OVERVIEW
MELSOFT
(3) Process control tag names can be selected easily from InTouch
When using the communication function with the aforementioned process control tag name, PX Developer process control tag names can be easily browsed/selected
*1 using the tag name reference function.
This function reduces key inputs and typing errors, and improves work efficiency.
[Image of the tag name reference function]
Programming with PX Developer
PX Developer programming tool Assignment information database
Development on the monitor control screen of InTouch
Registration
Compilation
Process control tag names defined in
PX Developer can be browsed/selected on
Tag Browser of InTouch.
InTouch
Tag Browser
InTouch
WindowMaker
1-3 1-3
1 OVERVIEW
MELSOFT
(4) Alarms/events of the PX Developer monitor tool can be monitored/checked on InTouch
By using the alarm integration function, alarm/event information of the monitor tool can be displayed on the Alarm Viewer control of InTouch. They can be monitored and checked in the same list with the alarm/event information of
InTouch.
[Image of the alarm integration function]
PX Developer monitor tool
InTouch
WindowViewer
Check
Management on alarms/events
Notification of alarms/events
Management on alarms/events
Notification of alarms/events
Alarms/events of PX Developer can be monitored/checked on the Alarm Viewer control of InTouch.
1-4 1-4
2 SYSTEM CONFIGURATION
MELSOFT
2.1 System Configuration
This section explains system configuration when using the interaction function of PX
Developer and InTouch.
For communication routes supported by PX Developer, refer to "SYSTEM
CONFIGURATION" in "PX Developer Operating Manual (Monitor Tool) ".
To use the interaction function, install PX Developer and InTouch to the same personal computer. If they are installed to different personal computers, the interaction function cannot be used.
2
[System configuration image]
English version of
PX Developer
Version 1.18U or later
English version of InTouch
Version 10.0 or 10.1
Use a communication driver depending on the situation.
*1
Communication route supported by the PX Developer monitor tool
*1: For reading/writing device data other than process control tags in InTouch, a communication driver such as an I/O server is required.
POINT
In the server/client monitoring system configuration, the alarm integration function is not available.
2-1 2-1
2 SYSTEM CONFIGURATION
MELSOFT
2
2.2 Software Configuration
This section explains software configuration when using the interaction function of PX
Developer and InTouch.
PX Developer
Assignment information database
Compilation
Reference
InTouch
WindowMaker
Tag name reference function
Programming tool
Monitor tool
Faceplate control
Paste
WindowViewer
ActiveX container function
Alarm/Event
Alarm provider *2
Data management
DDE interface
*1
Notification/
Check
Reading/ writing process control tag data
Alarm/Event
Alarm manager *3
DDE interface
*1
Data management
Data communication Reading/writing data other than the process control tag
CPU
Data communication
Communication driver such as I/O server
*1: InTouch reads/writes process control tag data in the monitor tool through DDE interface.
*2: The alarm provider is an alarm function supplied by Invensys Systems, Inc.
This function enables the monitor tool to notify/check alarms and events to the alarm manager of InTouch, and to receive a confirmation request for corresponding alarm from the Alarm Viewer control of InTouch.
*3: The alarm manager is an application that manages information on alarms and events to the alarm system of InTouch.
2.3 Operating Environment
2-2
PX Developer Version 1.18U or later and InTouch Version 10.0 or 10.1 are required for interacting themselves.
For the operating environment of PX Developer, refer to "Operating Environment" in
"PX Developer Operating Manual (Monitor Tool) ".
For the operating environment of InTouch, refer to "ReadMe" in InTouch installer.
The following are the applicable system software (operating system) to operate this interaction function.
• Microsoft R
• Microsoft R
• Microsoft R
• Microsoft R
• Microsoft R
Windows XP R
Windows Vista R
Windows Vista R
Professional Operating System
Business Operating System
Ultimate Operating System
Windows Vista
Windows R
R Enterprise Operating System
7 Professional Operating System
POINT
To execute InTouch in Windows Vista R
Windows Vista R .
, disable the user account control (UAC) in
2-2
3 BASIC OPERATION
MELSOFT
3 BASIC OPERATION
3.1 Operating Procedures for Monitoring on InTouch
This section explains procedures for monitoring on InTouch.
Setting basic settings and creating tag variables on InTouch WindowMaker
Refer to process control tags when creating tag variables.
( Section 3.2)
Developing monitor screens on InTouch WindowMaker
To develop monitor screens, use faceplate control of PX Developer.
( Section 3.3)
Setting the Alarm Viewer control of InTouch WindowMaker
Monitor/check alarms of PX Developer in the alarm monitor screen of InTouch.
( Section 3.4)
Executing InTouch WindowViewer
Execute InTouch WindowViewer while the PX Developer monitor tool is in operation.
POINT
• To monitor on InTouch WindowViewer using the faceplate control, communications using process control tag names, or alarm integration function, execute InTouch WindowViewer after starting the monitor tool.
• For basic operations of InTouch, refer to the manual of InTouch.
3
3-1 3-1
3 BASIC OPERATION
MELSOFT
3
3.2 Operation to Communicate using PX Developer Process Control Tag Names in
InTouch
PURPOSE
Register tag variables using process control tag names defined in PX Developer and read/write the process control tag data of the monitor tool in InTouch.
Setting on InTouch WindowMaker
Procedure 1) Register an access name for communicating with the
PX Developer monitor tool.
( Section 3.2.1) *1
Procedure 2) Create tag variables.
( Section 3.2.2)
Procedure 3) Define a tag source in the Tag Browser.
( Section 3.2.2) *1
Procedure 4) Refer/select tag names on the Tag Browser.
( Section 3.2.3)
*1: Required only when using InTouch application for the first time.
Execution on InTouch WindowViewer
The process control tag data can be read/written by executing WindowViewer after starting the monitor tool.
3-2
<Example of InTouch WindowViewer monitor screen>
3-2
3 BASIC OPERATION
3.2.1 Registering access names
OPERATION
MELSOFT
1. Click [Special] [Access Names…] from the menu of WindowMaker.
2. The Access Names dialog box is displayed.
Click the "Add…" button.
3. The Add Access Name dialog box is displayed.
Set the following items and click the "OK" button.
• Access
• Node Name
: Any specific name
: Blank
• Application Name
• Topic Name
• Which protocol to use
• When to advise server
: FBDQMon
: DA
: DDE
: Advise only active items
• Enable Secondary Source : Without a check
(Check this item when using the backup server.)
4. Check if the set access name has been added to the Access Names dialog box.
3-3 3-3
3 BASIC OPERATION
MELSOFT
3.2.2 Defining tag source
(1) Creating tag variables and setting tag sources
OPERATION
1. Create an object on Window Maker.
The Animation Links dialog box is displayed as shown on the left by double-clicking the object or selecting [Animation Links] from the menu displayed by right-clicking the object. Click a tag variable type to be assigned for the object.
2. The tag variable setting screen is displayed.
Double-click the input field of [Expression].
3. The Tag Browser is displayed.
Click the "Define Tag Sources" button ( ).
4. The Define Tag Sources dialog box is displayed. Click the "New…" button.
3-4
(To the next page)
3-4
3 BASIC OPERATION
(From the previous page)
MELSOFT
5. The Define Tag Source dialog box is displayed.
Set the following items and click the "Browse…" button.
• Tag Source Name : Any specific name
• Access Name : Set access name
( Section 3.2.1)
• Tag Source Type : PX Developer
* For details of the setting screen, refer to (2) in this section.
6. Select assignment information database of PX
Developer project to be referred (project name with .mdb extension), and click the "Open" button.
3-5
7. After completing the settings, the path for the selected project is stored to the Path field.
Click the "OK" button to close the Define Tag
Source dialog box.
8. Close the screen after checking that the set tag source is displayed on the Define Tag Sources dialog box.
3-5
3 BASIC OPERATION
MELSOFT
POINT
• When registering a tag variable using the process control tag declared with the same process control tag name with multiple projects with InTouch, the process control tag data of the highest priority
*1
project are read/written. Whether the same process control tag name has been declared or not can be checked on the
Monitor Target Project Setting screen of the monitor tool.
*1: The more the number at [No.] field on the Monitor Target Project Setting screen is small, the more the priority of its project becomes high.
Order of priority
3-6
<Example of Monitor Target Project Setting screen of PX Developer monitor tool>
• The assignment information database created with PX Developer Version 1.02C or later can be used for the tag name reference function. If the database is created Version 1.01B or earlier, convert it with the programming tool Version
1.02C or later. For details of the conversion, refer to "Precautions for the assignment information database" in "PX Developer Operating Manual
(Programming Tool)"
• To uninstall PX Developer, delete tag sources for the PX Developer project reference beforehand.
3-6
3 BASIC OPERATION
MELSOFT
(2) Specifications of the Define Tag Source screen
The following shows display items and setting items when "PX Developer" is selected for [Tag Source Type] on the Define Tag Source dialog box of InTouch.
DISPLAY/SETTING SCREEN
1)
2)
DISPLAY/SETTING DATA
No. Item Description
Input an absolute path to the assignment information database of a PX Developer project to be referred (path to the target mdb file of the project).The specified assignment information database is stored as a tag source.
Displays a dialog box for selecting a file.
Input restriction
Maximum 260 characters can be input.
----
The specified path in the dialog box is displayed at 1).
3-7 3-7
3 BASIC OPERATION
3.2.3 Referring to and selecting tag names
OPERATION
MELSOFT
1. Select a set tag source from a list in [Tag
Source] of the Tag Browser.
(To the next page)
2. The process control tags and their main tag items ( the list.
*1
Appendix 2) are displayed in
To access a tag item except for the main tag items, select a process control tag name, and then select a tag item corresponding to the process control tag type from [Dot Field]. ( Appendix 1)
*1: For a comment of main tag item, explanation on the tag item is displayed after "- " (a hyphen and a space).
3-8 3-8
3 BASIC OPERATION
(From the previous page)
MELSOFT
3. Select a tag item to be registered and click the "OK" button.
4. A tag name is automatically created at
[Expression] of the tag variable setting screen. A format of the created tag name is
"Access name:Process control tag name.Tag item".
*1
*1: The reference method is referred to as remote reference. For details, refer to the manual of InTouch.
POINT
• If changing the tag FB information of PX Developer project and recompile it after selecting a tag source and opening the list on the Tag Browser of InTouch
WindowMaker, the information is not reflected on the screen. To refer to the latest tag FB, select a tag source again.
• If the tag FB variable name has been set other than alphanumeric characters or underscore (_), InTouch cannot recognize the name. (The corresponding tag is not displayed in the tag list of the Tag Browser.)
3-9 3-9
3 BASIC OPERATION
MELSOFT
3.3 Operation to Use Faceplates of PX Developer in InTouch
PURPOSE
Use the faceplate control of PX Developer for developing process control monitor screens on InTouch to reduce development time.
Setting on InTouch WindowMaker
Procedure 1) Install ActiveX control.
( Section 3.3.1) *1
Procedure 2) Check that the installation is successful on the wizard menu.
( Section 3.3.2)
Procedure 3) Paste a faceplate control and configure its setting.
( Section 3.3.3)
*1: Required only when using InTouch application for the first time.
Execution on InTouch WindowViewer
By executing WindowViewer after starting the monitor tool, faceplates can be used, the process control data can be monitored, and the process control parameter can be tuned.
3-10
<Example of faceplate control screen of InTouch WindowViewer>
3-10
3-11
3 BASIC OPERATION
3.3.1 Installing ActiveX control
OPERATION
MELSOFT
1. Select [Special] [Configure]
[Wizard/ActiveX Installation...] from the
WindowMaker menu.
2. The Wizard/ActiveX Installation dialog box is displayed. Click the <<ActiveX Control
Installation>> tab.
3. Select "FBDQFP Control" and "FBDQTDA
Control" from the list in [Available ActiveX controls] and click the "Install" button.
4. After the installation, "FBDQFP Control" and
"FBDQTDA Control" are added to the list in
[Installed ActiveX controls].
3-11
3 BASIC OPERATION
3.3.2 Checking installation
OPERATION
MELSOFT
1. Click the "Wizard" button ( ) of
WindowMaker.
2. The Wizard Selection dialog box is displayed. Check that "FBDQTDACtrl" and
"FBDQFPCtrl" icons are added to the list in
[ActiveX Controls].
POINT
• "FBDQFPCtrl" can be pasted on the InTouch screen directly using the faceplate control.
• "FBDQTDACtrl" can read/write the process control tag data set to the tag data access control. Clicking the button can also display the pop-up faceplate screen.
For details of each control, refer to "ActiveX control" of "PX Developer Operating
Manual (Monitor Tool)".
3-12 3-12
3 BASIC OPERATION
MELSOFT
3.3.3 Setting/pasting faceplate control
OPERATION
Tag data access control Faceplate control
1. Select "FBDQTDACtrl" or "FBDQFPCtrl" from the list in [ActiveX Controls] of the
Wizard Selection dialog box and click the "OK" button.
2. The cursor changes to on InTouch.
Click a position where the faceplate control is to be pasted and adjust the control size by dragging the icon.
3. Double-click the control to display the property screen.
<Example of InTouch WindowMaker screen>
4. Click the <<General>> tab and set the process control tag name of PX
Developer for [TagName].
For the setting contents of the property, refer to "PX Developer Operating
Manual (Monitor Tool)".
POINT
If InTouch application is edited, overwritten, and saved after PX Developer is uninstalled, contents of the faceplate control and tag data access control originally set (such as tag names) are deleted when PX Developer is reinstalled.
3-13 3-13
3 BASIC OPERATION
MELSOFT
3.4 Operation to Display PX Developer Alarm Information on InTouch Alarm Viewer control
PURPOSE
Display alarm/event information of the monitor tool on the InTouch Alarm Viewer control and to monitor/check them in the same list with alarm/event information of
InTouch.
OVERVIEW OF ALARM
[Summary alarm and historical alarm of InTouch]
<Summary alarm>
Summary alarm is an alarm list on which records of current alarms and unchecked alarms are displayed. On the summary alarm, alarms can be checked by appending comments.
<Historical alarm>
Historical alarm is an alarm list on which records of occurred/recovered/checked alarms and occurred events are displayed. On the historical alarm, the alarm check operation is unavailable.
Setting on InTouch WindowMaker
Procedure 1) Paste the Alarm Viewer control.
( Section 3.4.1)
Procedure 2) Set the Alarm Query of the Alarm Viewer control.
( Section 3.4.2)
Execution on InTouch WindowViewer
Alarms of PX Developer can be monitored/checked on the InTouch Alarm Viewer control by executing InTouch WindowViewer after starting the monitor tool.
When the Alarm Viewer control type is summary alarm, only the alarm information can be monitored. When the Alarm Viewer control type is historical alarm, alarm information and event information can be monitored.
3-14 3-14
3-15
3 BASIC OPERATION
MELSOFT
POINT
• Alarms and events can be stored to the historical alarm buffer of InTouch, secured for PX Developer, up to 6,000 and 2,000, respectively. When capacity of the historical alarm buffer is full, stored alarm/event information is deleted from the oldest to store the latest information.
• Alarm Viewer control of InTouch displays only alarm/event information of PX
Developer occurred while the monitor tool is in operation. Therefore, histories of alarms/events occurred before starting the monitor tool is not reflected to alarms on InTouch.
• After exiting the monitor tool, the alarm/event information on PX Developer displayed on the Alarm Viewer control of InTouch are all deleted from the summary alarm and historical alarm. To display the alarm information on InTouch even after exiting the monitor tool, logging alarms with AlarmPrinter
*1
or accumulating the database with Alarm DB Logger Manager
*1
beforehand is necessary.
• In the server/client monitoring system configuration, the alarm integration function is not available.
*1: For details, refer to the manual of InTouch.
The following shows interlock operation of alarms and events.
For operation methods of InTouch, refer to the manual of InTouch.
(1) Operating alarm monitor screen
The following are an Alarm List screen of the monitor tool and a summary alarm screen of InTouch.
<Example of Alarm List screen of PX Developer monitor tool>
<Example of summary alarm screen of InTouch WindowViewer>
InTouch receives alarm notification/alarm check notification from the monitor tool and displays them.
However, system alarms of InTouch itself (SCADA interaction function error) are not notified to InTouch.
3-15
3-16
3 BASIC OPERATION
MELSOFT
[Operation from the monitor tool that interlocks with the alarms of
InTouch]
• Executing "Delete Recovered Alarms" deletes the corresponding alarms of
InTouch.
• Executing "Confirm All" checks all corresponding alarms of InTouch.
• Checking "Confirm" check box checks corresponding alarm of InTouch.
• Clearing "Confirm" check box of ongoing alarm regenerates corresponding alarm of InTouch.
• When alarms exceed 2,000 on the Alarm List screen of the monitor tool, old alarms are deleted. If corresponding alarm of InTouch exists in the summary alarm, the alarm is also deleted.
[Operation from InTouch that interlocks with the monitor tool]
• Checking alarms on InTouch checks "Confirm" check box for corresponding alarm on the Alarm List screen of the monitor tool.
POINT
• For correspondence table for alarm items notified by the monitor tool to InTouch, refer to Appendix 3.1.
• When checking the alarm in the monitor tool with InTouch, the user who operates the monitor tool is required with the authority of operation for checking the alarm/event.
(2) Operating event monitor screen
The following are an Event List screen of the monitor tool and a historical alarm screen of InTouch.
On InTouch, alarms and events are displayed on the historical alarm screen.
<Example of Event List screen of PX Developer monitor tool>
<Example of historical alarm screen of InTouch WindowViewer>
InTouch receives event notifications from the monitor tool and displays them.
3-16
3 BASIC OPERATION
MELSOFT
POINT
• For correspondence table for event items notified by the monitor tool to InTouch, refer to Appendix 3.2.
• A check operation can be performed on events of the message tag from the Event
List screen of the monitor tool. However, events of the message tag are not displayed on the historical alarm of InTouch for a check operation.
3-17 3-17
3 BASIC OPERATION
3.4.1 Pasting Alarm Viewer control
OPERATION
MELSOFT
1. Click the "Wizard" button ( ) of
WindowMaker.
2. The Wizard Selection dialog box is displayed. Select "AlarmViewerCtrl" from the list in [ActiveX Controls] and click the "OK" button.
3. The cursor changes to on InTouch.
Click a position where the faceplate control is to be pasted and adjust the control size by dragging the icon.
<Example of InTouch WindowMaker screen>
3-18 3-18
3 BASIC OPERATION
3.4.2 Setting Alarm Query
OPERATION
MELSOFT
<Setting example of summary alarm>
1. Double-click the Alarm Viewer control to display the property screen.
2. Click the <<Query>> tab, input a space after "\intouch!$system", and input
"\PXAlarm!$System" to interact the alarm information or
"\PXEvent!$System" to interact the event information in the [Alarm Query] field. Inputting both of them allows alarm/event information to be integrated.
However, the event information is stored only to the historical alarm.
3-19
<Setting example of historical alarm>
Integrated contents
Alarm
Added alarm query
\PXAlarm!$System
Valid query type
Both summary and history
POINT
• To register multiple alarm query items, separate each item with a space.
• The alarm query is not case-sensitive.
• By setting alarm query in the same way for "Distributed Alarm", included in
WindowMaker wizard, the alarm integration function can be used. For details, refer to the manual of InTouch.
3-19
3 BASIC OPERATION
MEMO
3-20
MELSOFT
3-20
4 TROUBLESHOOTING
MELSOFT
4 TROUBLESHOOTING
(1) Troubleshooting related to the communication function regarding process control tag names
This section explains troubleshooting for failures possibly occur in relation to the communication function regarding process control tag names.
While WindowViewer is in operation, the monitor data remains 0.
Although the process control tag data in PX Developer are changed while WindowViewer is in operation, the monitor data do not change.
The following are the possible factors.
• "Expression" may not be set correctly in InTouch.
• The monitor tool may not be started.
• The user who is operating the monitor tool does not have the authority of operation for changing the tag data items.
Check the following and make correct setting.
• Check if a format of "Expression" is "Access name:Process control tag name.Tag item".
• Check if the access name is set correctly.
• Check if the process control tag name exists in the target project of the monitor tool.
• Check if the monitor tool is in operation.
• If the tag variable is changed in WindowMaker while WindowViewer is in operation, restart WindowViewer.
• Change to a user who has the authority of operation for changing the process control tag data items in the monitor tool.
For cases other than above, refer to "Error list" in "ActiveX control",
"Setting Tagname property", and "Calling or Setting Tagname property" of "PX Developer Operating Manual (Monitor Tool)".
Section 3.2
(2) Troubleshooting related to the incorporation function of faceplate control
For troubleshooting for failures possibly occur in relation to the incorporation function of faceplate control, refer to "Error list" in "ActiveX control" section of "PX
Developer Operating Manual (Monitor Tool)".
4
4-1 4-1
4 TROUBLESHOOTING
MELSOFT
(3) Troubleshooting related to alarm integration function
This section explains troubleshooting for failures possibly occur in relation to the alarm integration function.
4
While WindowViewer is in operation, alarms of the monitor tool are not displayed on the Alarm
Viewer control of InTouch.
The monitor tool may not be executed or the Alarm Query may not be set correctly.
Check the following.
Right-click on the Alarm Viewer control of WindowViewer and check if the
Alarm Query is set as shown below in the [Stats] menu.
When the setting is correct and the execution rate of the Alarm Query
(the number is displayed at the area displayed as 100 on the screen below) is 0, check if the monitor tool is being activated.
Section 3.4
While WindowViewer is in operation, executing alarm check of the monitor tool with InTouch does not reflect.
<Alarm Statistics screen of InTouch WindowViewer>
The user who is operating the monitor tool may not have the authority of operation for checking the alarm/event. Execute the following setting.
Change to a user who has the authority of operation for checking the alarm/event in the monitor tool.
Section 3.4
4-2 4-2
APPENDIX
MELSOFT
APPENDIX
Appendix 1 Details of Dot Field Name in the Tag Name Reference Function
For lists of the tag items of process control tag that can be specified on the Tag
Browser (tag item that can be specified on the Dot Field when the process control tag is selected), refer to "List of Various Tag Type/Tag Data" in "PX Developer
Programming Manual".
The following table shows the data types and icons in InTouch corresponding to the data types of each tag item in PX Developer.
Data type in PX Developer Data type in InTouch Icon
BOOL Discrete
INT, DINT, WORD, DWORD Integer
REAL Real
Tag FB ----
Appendix 2 Main Tag Items
Main tag items of process control tag displayed on the Tag Browser is the tag items which perform the current value collection and event notification.
The following table shows the tag items which perform current value collection.
Tag FB name
DIM
Current value collection tag
VOUT
Command signal output status
Monitor input buffer
Tag FB name
PID, 2PID, PIDP,
SPI, IPD, BPI, R,
ONF2, ONF3 variable
MWM variable
2PIDH, SWM,
PFC_SF, PFC_SS,
PFC_INT
PV
SVC
SV
Process variable
Setting value (current)
Setting value (target)
SEL
PGS
BC
MV
SV
Manipulated variable
Setting value
TYP Operation type PSUM
NREV, REV,
MVAL1, MVAL2, PB
PGS2
STC
T
PV
TYP
Executing step No.
Time in the step
Process variable
Operation type
SV0C Start point (current)
ALM, ALM_64PT,
MONI PV MSG, MSG_64PT
PV
SVC
Motor valve opening
Setting value of valve opening (current)
TIMER1,
TIMER2,
COUNT1,
COUNT2
HTCL
PVAL SV
Setting value of valve opening (target)
B-1
MV
PV
Current value collection tag
PV
SV1
SV2
DIM
Manipulated variable
Process variable
Setting value 1
Setting value 2
Process variable
Monitor input buffer
PV
PSV
SV
Process variable
Setting value
Setting value
DIM Monitor input buffer
No corresponding current value correction tags.
MV_HT
MV_CL
Heating manipulated variable
Cooling manipulated variable
B-1
App
APPENDIX
MELSOFT
App
The following table shows the tag items which perform event notification.
Tag FB name
PID, 2PID, NREV,
REV, MVAL1, MVAL2,
PGS2, HTCL
2PIDH, SWM,
PFC_SF, PFC_SS,
PFC_INT, PVAL
PIDP, SPI, IPD, BPI, R,
ONF2, ONF3, MWM,
SEL, MOUT, PGS
MONI
Event notification tag
MODE *1 Mode
ALM *1 Alarm
CTNO
DIM
*1
Lookout tag No.
Monitor input buffer
MODE
*1
Mode
ALM
*1
Alarm
ALM2
*1
CTNO
DIM
*1
Lookout tag No.
Monitor input buffer
MODE *1 Mode
ALM
*1
Alarm
CTNO Lookout tag No.
ALM
*1
Alarm
CTNO Lookout tag No.
BC, PSUM,
TIMER1, TIMER2,
COUNT1, COUNT2
PB
Tag FB name
ALM
ALM_64PT
MSG
MSG_64PT
Event notification tag
ALM *1 Alarm
CTNO Lookout tag No.
DIM
*1
Monitor input buffer
MODE
*1
Mode
CTNO
DIM
*1
Lookout tag No.
Monitor input buffer
ALM
*1
Alarm
ALM_W1
*1
Alarm 1 to 16
ALM_W2
*1
Alarm 17 to 32
ALM_W3 *1 Alarm 33 to 48
ALM_W4
*1
Alarm 49 to 64
MSG
*1
Message
MSG_W1
*1
Message 1 to 16
MSG_W2
*1
Message 17 to 32
MSG_W3
*1
Message 33 to 48
MSG_W4
*1
Message 49 to 64
*1: This tag item consists of multiple BOOL type variables; however, it is displayed as a BOOL type variable on the Tag
Browser.
B-2 B-2
APPENDIX
MELSOFT
Appendix 3 Correspondence Table for Items of Monitor Tool and InTouch
Appendix 3.1 Correspondence table for alarm items
The following is a correspondence table for alarm items notified to InTouch by the monitor tool.
In the InTouch alarm screen, a display name, item, and display format can be selected in the Properties of the Alarm Viewer control.
For details, refer to the manual of InTouch.
PX Developer monitor tool
Alarm item Expression Alarm item
InTouch
Expression
Confirm check ON/OFF State
Tag FIC001
Tag Comment Tank 1 water level Name
Alarm Contents
*1
MHA
*2
Occurrence Date
Recovered Date
The format depends on the setting of OS.
Time
*4
Measured Value 100%
No correspondence
Format: "Tag.Alarm contents Tag comment"
Example) FIC001.MHA Tank 1 water level
*3
Depends on setting of time format in the Alarm Viewer control.
ACK/UNACK
Value
Minor: 500, major: 100
100%
Provider \PXAlarm
Group $System
Limit Blank
Class Blank
Type Blank
Tag Comment Blank
Operator Blank
Operator Domain
Operator Node
Operator Full Name
Alarm Comment
User1, 2
Blank
Blank
Blank
At alarm check: Check comment
0
User3 PX Developer project name
*1: The description corresponds to "Tag Data Item Display of Alarm" on the option setting of the monitor tool is displayed.
*2: "Item Name" is displayed all the time.
*3: If there is no tag comment, the format will be "Tag.Alarm contents".
*4: For summary alarm, occurrence date is displayed during an alarm occurrence and recovered date is displayed after an alarm is recovered. For historical alarm, occurrence and recovery are displayed on another record.
*5: The alarm level of InTouch is expressed by priority from 1 to 999. The more the number is close to 1, the more priority becomes high.
B-3 B-3
APPENDIX
MELSOFT
Appendix 3.2 Correspondence table for event items
The following is a correspondence table for event items notified to InTouch by the monitor tool.
In the InTouch alarm screen, a display name, item, and display format can be selected in the Properties of the Alarm Viewer control.
For details, refer to the manual of InTouch.
PX Developer monitor tool
Event item Expression Event item
InTouch
Expression
Confirm check ON/OFF
No correspondence
(State is left blank.)
Tag FIC001
Tag Comment Valve flow Name
Event Message
*1
SV
*2
Occurrence Date
The format depends on the setting of OS.
Time
Status *1 CAS
Set Value
*1
Value
*2
90.0
Previous Value
*1
Format: "Tag.Event message Tag comment"
Example) FIC001.SV Valve flow
*3
Depends on setting of time format in the Alarm
Viewer control.
CAS
90.0 admin
Blank
Provider \PXEvent
Group $System
Class EVENT
Priority 999
Tag Comment Blank
No correspondence
Operator Domain
Operator Node
Operator Full Name
Alarm Comment
Blank
Blank
Blank
Blank
User1,2 0
User3 PX Developer project name
*1: The description corresponds to "Tag Data Item Display of Event" on the option setting of the monitor tool is displayed.
*2: "Item Name" is displayed all the time.
*3: If there is no event message, the format will be "Tag Tag comment".
*4: "OPR" is displayed when the setting is changed by user, and "SYS" is displayed when the status is changed.
B-4 B-4
APPENDIX
MELSOFT
Appendix 4 Security of Monitor Tool and InTouch
The mixture of the user authority function of the monitor tool and the security function of InTouch enables to set the restrictions for operation of process control tag on the graphic screen of InTouch.
The access level of user who is logging on is stored on $AccessLevel system tag.
Using $AccessLevel system tag in conditional statement of [Disable] and [Visibility] of object enables to set the operation restrictions.
For details of the security function of InTouch, refer to the manual of InTouch.
Appendix 4.1 Operating environment for using security of monitor tool and InTouch
The following describes the operating environment for using security of the monitor tool and InTouch.
Application Version
PX Developer Version 1.31H or later
Appendix 4.2 Setting procedure for using security of monitor tool and InTouch
The following diagram describes the setting procedure for using the user authority function in the monitor tool and the security function in InTouch.
Start to set the items.
(1) Set the user authority function in the monitor tool.
(2) Set the security function in InTouch.
(3) Create the script to change users in the monitor tool with InTouch.
Completed
B-5 B-5
APPENDIX
MELSOFT
(1) Setting user authority function in monitor tool
Set the following items in the monitor tool.
For details, refer to "PX Developer Operating Manual (Monitor Tool) ".
1) User Authority Setting
Set the operation restrictions for each user authority.
2) User Setting
Set a user name, a password, and the authority of users who operate the monitor tool.
B-6 B-6
APPENDIX
MELSOFT
(2) Setting security function in InTouch
Set the following items in InTouch.
For details, refer to the manual of InTouch.
1) User setting
Select [Special] [Security] [Configure Users] on the WindowMaker menu, and set a user name, a password, and the access level of users who log on to
InTouch.
<User setting example of the monitor tool and InTouch>
The user authority (initial setting) of the monitor tool and the user access level of InTouch have the operation authority of high and low as shown below.
User setting of the monitor tool
(initial setting)
User access level of
InTouch
Operation authority
Operator 4
Operator 3
Operator 2
Operator 1
Therefore, match between user authority of the monitor tool and the user access level of InTouch is required.
The following table is a setting example.
User setting of the monitor tool
User name User authority
User setting of InTouch
User name Access level
B-7 B-7
APPENDIX
MELSOFT
2) Security setting for process control tag
As a security when inputting the data or displaying the values for process control tag, set with the mixture of Animation Links of [Disable] or [Visibility].
In this case, using $AccessLevel system tag in the conditional statement controls valid/invalid and display/hide of the touch function of object in accordance with user who is logging on.
Example) Security setting when executing touch action (data input) for
"PXDA:TIC001.PH" which is PV high limit alarm value of process control tag TIC001.
For data input of process control tag "PXDA:TIC001.PH", the operation authority higher than Operator2 in the monitor tool is required. The following indicate the setting procedure to execute the touch action (data input) by logon user whose access level is 4000 or higher only with InTouch.
1. Double-click the text object for displaying numerical value, or right-click the context menu, and select [Animation Links].
2. Select [Touch Links] [User Inputs] [Analog], and set
Tagname "PXDA:TIC001.PH".
B-8
3) Select [Miscellaneous] – [Disable], and set to valid the touch action execution for logon user whose access level is 4000 or higher.
Valid the touch action execution
(data input) for logon user whose access level is 4000 or higher.
B-8
APPENDIX
MELSOFT
(3) Creating script to change users of monitor tool with InTouch
Create the script as shown below to change users of the monitor tool automatically when changing logon user of InTouch. (For mode change of the monitor tool, execute the MonCtrl command. The file path of installation target folder of PX Developer is "C:\MELSEC" as an example.)
1) QuickFunction script
Function : PXChangeMode
Script :
{When a user is "User01"}
IF $Operator == "User01" THEN
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /u User01 /p User01";
ELSE
{When a user is "User02"}
IF $Operator == "User02" THEN
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /u User02 /p User02";
ELSE
{When a user is "User03"}
IF $Operator == "User03" THEN
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /u User03 /p User03";
ELSE
{When a user is "User04"}
IF $Operator == "User04" THEN
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /u User04 /p User04";
ELSE
{When a user is "admin"}
IF $Operator == "admin" THEN
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /u admin /p admin";
ELSE
StartApp "C:\MELSEC\Fbdq\MonCtrl.exe /changemode /Lock";
ENDIF;ENDIF;ENDIF;ENDIF;ENDIF;
CurrentUser = $Operator;
Description of functions and variables:
$Operator
CurrentUser
System tag
Data type : String
Description : Store the logon name of user who is logging on.
Local tag
Data type : Memory message
Description : Store the current user.
B-9 B-9
APPENDIX
MELSOFT
2) Application script
Condition Type : On Startup
Script :
CALL PXChangeMode();
3) Condition script
Condition : CurrentUser <> $Operator
Condition Type : On True
Script :
CALL PXChangeMode();
POINT
Modify a user name and a password specified for argument of MonCtrl command to correspond with the user setting of the monitor tool.
Appendix 4.3 Procedure for monitoring operation with security interaction between monitor tool and InTouch
When monitoring with security interaction between the monitor tool and InTouch, monitor by following the procedure described below.
1) Start the monitor tool.
2) Start InTouch WindowViewer.
3) Change the logon users with InTouch.
(The users in the monitor tool are changed by condition script described in Appendix
4.2 (3) 3).)
POINT
When an error message is displayed with the monitor tool by changing logon users with InTouch, log on with a user who does not have the authority ("None") with
InTouch once, and log on with the operation user again after the problem is solved.
B-10 B-10
APPENDIX
MELSOFT
Appendix 5 Functions Added to and Changed from Old Version
The following table indicates the functions added and changed with the upgrade.
Compatible version*
1
Added/changed function
Description Reference
Version 1.31H Supported OS Windows R 7 is supported. Section 2.3
*1: The compatible version can be confirmed in Product Information. For details, refer to the "PX Developer Operating
Manual (Programming Tool or Monitor Tool)".
B-11 B-11
INDEX
Ind
[A]
[C]
Alarm integration function ........................... 1-1, 4
Assignment information database ................A-10
Checking installation ..................................... 3-12
Communication function using process control tag names .......................................................... 1-1, 2
Correspondence table for alarm items ........... B-3
Correspondence table for event items ........... B-4
Correspondence Table for Items of Monitor Tool and InTouch..................................................... B-3
Creating tag variable/setting variables and setting tag sources ...................................................... 3-4
[D]
[F]
DDC ...............................................................A-10
DDE ...............................................................A-10
Defining tag source ......................................... 3-4
Details of Dot Field Name in the Tag Name
Reference Function......................................... B-1
[I]
Faceplate.......................................................A-10
FB ..................................................................A-10
FBD................................................................A-10
[M]
Incorporating faceplate control ....................... 1-1
Installing ActiveX control............................... 3-11
InTouch..........................................................A-10
I/O server .......................................................A-10
Main Tag Items................................................ B-1
Monitor tool....................................................A-10
MV..................................................................A-10
C-1
[O]
Operating Environment....................................2-2
Operating Procedures for Monitoring on InTouch
..........................................................................3-1
Operating alarm monitor screen....................3-15
Operating event monitor screen....................3-16
Operation from InTouch that interlocks with the monitor tool ....................................................3-16
Operation from the monitor tool that interlocks with the alarms of InTouch ....................................3-16
Operation to Communicate using PX Developer
Process Control Tag Names in InTouch.........3-2
Operation to Display PX Developer Alarm
Information on InTouch Alarm Viewer control
........................................................................3-14
Operation to Use Faceplates of PX Developer in
InTouch ..........................................................3-10
[P]
Pasting Alarm Viewer control ........................3-18
Personal computer........................................ A-10
Programming tool.......................................... A-10
PV.................................................................. A-10
PX Developer................................................ A-10
[R]
Reference function for PX Developer tag names
......................................................................1-1, 3
Referring to and selecting tag names .............3-8
Registering access names ..............................3-3
[S]
Security of Monitor Tool and InTouch ............ B-5
Setting Alarm Query ......................................3-19
Setting/pasting faceplate control ...................3-13
Software Configuration ....................................2-2
Specifications of the Define Tag Source screen
..........................................................................3-7
SV.................................................................. A-10
SYSTEM CONFIGURATION ..........................2-1
C-1
[T]
Tag.................................................................A-10
Tag data.........................................................A-10
Tag data item.................................................A-10
Tag FB ...........................................................A-10
TROUBLESHOOTING.................................... 4-1
Troubleshooting related to alarm integration function ............................................................ 4-2
Troubleshooting related to the communication function regarding process control tag names
......................................................................... 4-1
Troubleshooting related to the incorporation function of faceplate control ............................ 4-1
[W]
WindowMaker................................................A-10
WindowViewer...............................................A-10
C-2 C-2
Ind
Windows is a registered trademark or registered trademark of Microsoft Corporation in the United States and other countries.
Wonderware, InTouch, WindowMaker, and WindowViewer are trademarks or registered trademarks of
Schneider Electric, its subsidiaries, and affiliates.
All other company names and product names used in this manual are trademarks or registered trademarks of their respective companies.
SH(NA)-080773ENG-I(1701)KWIX
MODEL:SW1D5C-FBDQ-O-SCDA-E
MODEL CODE: 13JU62
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Specifications subject to change without notice.
advertisement
Related manuals
advertisement
Table of contents
- 3 SAFETY PRECAUTIONS
- 4 CONDITIONS OF USE FOR THE PRODUCT
- 5 REVISIONS
- 6 INTRODUCTION
- 6 CONTENTS
- 8 MANUALS
- 9 HOW TO USE THIS MANUAL
- 11 MANUAL ORGANIZATION
- 12 GENERIC TERMS, ABBREVIATIONS, AND TERMS
- 13 1 OVERVIEW
- 13 1.1 Overview
- 13 1.2 Features
- 17 2 SYSTEM CONFIGURATION
- 17 2.1 System Configuration
- 18 2.2 Software Configuration
- 18 2.3 Operating Environment
- 19 3 BASIC OPERATION
- 19 3.1 Operating Procedures for Monitoring on InTouch
- 20 3.2 Operation to Communicate using PX Developer Process Control Tag Names inInTouch
- 21 3.2.1 Registering access names
- 22 3.2.2 Defining tag source
- 26 3.2.3 Referring to and selecting tag names
- 28 3.3 Operation to Use Faceplates of PX Developer in InTouch
- 29 3.3.1 Installing ActiveX control
- 30 3.3.2 Checking installation
- 31 3.3.3 Setting/pasting faceplate control
- 32 3.4 Operation to Display PX Developer Alarm Information on InTouch Alarm Viewer control
- 36 3.4.1 Pasting Alarm Viewer control
- 37 3.4.2 Setting Alarm Query
- 39 4 TROUBLESHOOTING
- 41 APPENDIX
- 41 Appendix 1 Details of Dot Field Name in the Tag Name Reference Function
- 41 Appendix 2 Main Tag Items
- 43 Appendix 3 Correspondence Table for Items of Monitor Tool and InTouch
- 43 Appendix 3.1 Correspondence table for alarm items
- 44 Appendix 3.2 Correspondence table for event items
- 45 Appendix 4 Security of Monitor Tool and InTouch
- 45 Appendix 4.1 Operating environment for using security of monitor tool and InTouch
- 45 Appendix 4.2 Setting procedure for using security of monitor tool and InTouch
- 50 Appendix 4.3 Procedure for monitoring operation with security interaction betweenmonitor tool and InTouch
- 51 Appendix 5 Functions Added to and Changed from Old Version
- 52 INDEX