Руководство пользователя Point of View (англ.)

Руководство пользователя Point of View (англ.)
Point of View Software Reference Guide
PV-SWREF-M
WARNING Thank you for purchasing automation equipment from Automationdirect.com®, doing business as,
AutomationDirect. We want your new automation equipment to operate safely. Anyone who installs or
uses this equipment should read this publication (and any other relevant publications) before installing or
operating the equipment.
To minimize the risk of potential safety problems, you should follow all applicable local and national codes
that regulate the installation and operation of your equipment. These codes vary from area to area and
usually change with time. It is your responsibility to determine which codes should be followed, and to
verify that the equipment, installation, and operation is in compliance with the latest revision of these
codes.
At a minimum, you should follow all applicable sections of the National Fire Code, National Electrical
Code, and the codes of the National Electrical Manufacturer's Association (NEMA). There may be local
regulatory or government offices that can also help determine which codes and standards are necessary for
safe installation and operation.
Equipment damage or serious injury to personnel can result from the failure to follow all applicable codes
and standards. We do not guarantee the products described in this publication are suitable for your
particular application, nor do we assume any responsibility for your product design, installation, or
operation.
Our products are not fault-tolerant and are not designed, manufactured or intended for use or resale as online control equipment in hazardous environments requiring fail-safe performance, such as in the
operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life
support machines, or weapons systems, in which the failure of the product could lead directly to death,
personal injury, or severe physical or environmental damage ("High Risk Activities"). AutomationDirect
specifically disclaims any expressed or implied warranty of fitness for High Risk Activities.
For additional warranty and safety information, see the Terms and Conditions section of our catalog. If
you have any questions concerning the installation or operation of this equipment, or if you need
additional information, please call us at 770-844-4200.
This publication is based on information that was available at the time it was printed. At
AutomationDirect we constantly strive to improve our products and services, so we reserve the right to
make changes to the products and/or publications at any time without notice and without any obligation.
This publication may also discuss features that may not be available in certain revisions of the product.
Trademarks
This publication may contain references to products produced and/or offered by other companies. The
product and company names may be trademarked and are the sole property of their respective owners.
AutomationDirect disclaims any proprietary interest in the marks and names of others.
Copyright 2013, Automationdirect.com® Incorporated
All Rights Reserved
No part of this manual shall be copied, reproduced, or transmitted in any way without the prior, written
consent of Automationdirect.com® Incorporated. AutomationDirect retains the exclusive rights to all
information included in this document.
ADVERTENCIA Gracias por comprar equipo de automatización de Automationdirect.com®. Deseamos que su nuevo equipo de
automatización opere de manera segura. Cualquier persona que instale o use este equipo debe leer esta
publicación (y cualquier otra publicación pertinente) antes de instalar u operar el equipo.
Para reducir al mínimo el riesgo debido a problemas de seguridad, debe seguir todos los códigos de seguridad
locales o nacionales aplicables que regulan la instalación y operación de su equipo. Estos códigos varian de área
en área y usualmente cambian con el tiempo. Es su responsabilidad determinar cuales códigos deben ser
seguidos y verificar que el equipo, instalación y operación estén en cumplimiento con la revisión mas reciente
de estos códigos.
Como mínimo, debe seguir las secciones aplicables del Código Nacional de Incendio, Código Nacional
Eléctrico, y los códigos de (NEMA) la Asociación Nacional de Fabricantes Eléctricos de USA. Puede haber
oficinas de normas locales o del gobierno que pueden ayudar a determinar cuales códigos y normas son
necesarios para una instalación y operación segura.
Si no se siguen todos los códigos y normas aplicables, puede resultar en daños al equipo o lesiones serias a
personas. No garantizamos los productos descritos en esta publicación para ser adecuados para su aplicación en
particular, ni asumimos ninguna responsabilidad por el diseño de su producto, la instalación u operación.
Nuestros productos no son tolerantes a fallas y no han sido diseñados, fabricados o intencionados para uso o
reventa como equipo de control en línea en ambientes peligrosos que requieren una ejecución sin fallas, tales
como operación en instalaciones nucleares, sistemas de navegación aérea, o de comunicación, control de tráfico
aéreo, máquinas de soporte de vida o sistemas de armamentos en las cuales la falla del producto puede resultar
directamente en muerte, heridas personales, o daños físicos o ambientales severos ("Actividades de Alto Riesgo").
Automationdirect.com específicamente rechaza cualquier garantía ya sea expresada o implicada para
actividades de alto riesgo.
Para información adicional acerca de garantía e información de seguridad, vea la sección de Términos y
Condiciones de nuestro catálogo. Si tiene alguna pregunta sobre instalación u operación de este equipo, o si
necesita información adicional, por favor llámenos al número 770-844-4200 en Estados Unidos.
Esta publicación está basada en la información disponible al momento de impresión.
En
Automationdirect.com nos esforzamos constantemente para mejorar nuestros productos y servicios, así que
nos reservamos el derecho de hacer cambios al producto y/o a las publicaciones en cualquier momento sin
notificación y sin ninguna obligación. Esta publicación también puede discutir características que no estén
disponibles en ciertas revisiones del producto.
Marcas Registradas
Esta publicación puede contener referencias a productos producidos y/u ofrecidos por otras compañías. Los nombres de las
compañías y productos pueden tener marcas registradas y son propiedad única de sus respectivos dueños. Automationdirect.com,
renuncia cualquier interés propietario en las marcas y nombres de otros.
PROPIEDAD LITERARIA 2013, AUTOMATIONDIRECT.COM® INCORPORATED
Todos los derechos reservados
No se permite copiar, reproducir, o transmitir de ninguna forma ninguna parte de este manual sin previo consentimiento por escrito de
Automationdirect.com® Incorprated. Automationdirect.com retiene los derechos exclusivos a toda la información incluida en este
documento. Los usuarios de este equipo pueden copiar este documento solamente para instalar, configurar y mantener el equipo
correspondiente. También las instituciones de enseñanza pueden usar este manual para propósitos educativos.
AVERTISSEMENT Nous vous remercions d'avoir acheté l'équipement d'automatisation de Automationdirect.com®, en faisant des
affaires comme, AutomationDirect. Nous tenons à ce que votre nouvel équipement d'automatisation fonctionne en
toute sécurité. Toute personne qui installe ou utilise cet équipement doit lire la présente publication (et toutes les
autres publications pertinentes) avant de l'installer ou de l'utiliser.
Afin de réduire au minimum le risque d'éventuels problèmes de sécurité, vous devez respecter tous les codes locaux et
nationaux applicables régissant l'installation et le fonctionnement de votre équipement. Ces codes diffèrent d'une
région à l'autre et, habituellement, évoluent au fil du temps. Il vous incombe de déterminer les codes à respecter et
de vous assurer que l'équipement, l'installation et le fonctionnement sont conformes aux exigences de la version la
plus récente de ces codes.
Vous devez, à tout le moins, respecter toutes les sections applicables du Code national de prévention des incendies,
du Code national de l'électricité et des codes de la National Electrical Manufacturer's Association (NEMA). Des
organismes de réglementation ou des services gouvernementaux locaux peuvent également vous aider à déterminer
les codes ainsi que les normes à respecter pour assurer une installation et un fonctionnement sûrs.
L'omission de respecter la totalité des codes et des normes applicables peut entraîner des dommages à l'équipement
ou causer de graves blessures au personnel. Nous ne garantissons pas que les produits décrits dans cette publication
conviennent à votre application particulière et nous n'assumons aucune responsabilité à l'égard de la conception, de
l'installation ou du fonctionnement de votre produit.
Nos produits ne sont pas insensibles aux défaillances et ne sont ni conçus ni fabriqués pour l'utilisation ou la revente
en tant qu'équipement de commande en ligne dans des environnements dangereux nécessitant une sécurité absolue,
par exemple, l'exploitation d'installations nucléaires, les systèmes de navigation aérienne ou de communication, le
contrôle de la circulation aérienne, les équipements de survie ou les systèmes d'armes, pour lesquels la défaillance du
produit peut provoquer la mort, des blessures corporelles ou de graves dommages matériels ou environnementaux
(«activités à risque élevé»). La société AutomationDirect nie toute garantie expresse ou implicite d'aptitude à
l'emploi en ce qui a trait aux activités à risque élevé.
Pour des renseignements additionnels touchant la garantie et la sécurité, veuillez consulter la section Modalités et
conditions de notre documentation. Si vous avez des questions au sujet de l'installation ou du fonctionnement de cet
équipement, ou encore si vous avez besoin de renseignements supplémentaires, n'hésitez pas à nous téléphoner au
770-844-4200.
Cette publication s'appuie sur l'information qui était disponible au moment de l'impression. À la société
AutomationDirect, nous nous efforçons constamment d'améliorer nos produits et services. C'est pourquoi nous
nous réservons le droit d'apporter des modifications aux produits ou aux publications en tout temps, sans préavis ni
quelque obligation que ce soit. La présente publication peut aussi porter sur des caractéristiques susceptibles de ne
pas être offertes dans certaines versions révisées du produit.
Marques de commerce
La présente publication peut contenir des références à des produits fabriqués ou offerts par d'autres entreprises. Les
désignations des produits et des entreprises peuvent être des marques de commerce et appartiennent exclusivement à
leurs propriétaires respectifs. AutomationDirect nie tout intérêt dans les autres marques et désignations.
Copyright 2013, Automationdirect.com® Incorporated
Tous droits réservés
Nulle partie de ce manuel ne doit être copiée, reproduite ou transmise de quelque façon que ce soit sans le
consentement préalable écrit de la société Automationdirect.com® Incorporated. AutomationDirect conserve les
droits exclusifs à l'égard de tous les renseignements contenus dans le présent document.
Notes:
Point of View Software Reference Guide
Please include the Manual Number and the Manual Issue, both shown below,
when communicating with Technical Support regarding this publication.
Manual Number:
Issue:
Issue Date:
PV-SWREF-M
1st Edition
11/13
Publication History
Issue
Date
Description of Changes
1st Edition
11/13
Original
Notes:
TABLE OF CONTENTS
INTRODUCTION...................................................................................................................1-2
CONVENTIONS USED ........................................................................................................... 1-2
ABOUT THIS SOFTWARE............................................................................................................ 1-3
COMPARISON OF POINT OF VIEW SOFTWARE COMPONENTS................................................................. 1-7
INSTALL THE FULL POINT OF VIEW SOFTWARE.................................................................................. 1-8
EXECUTION MODES............................................................................................................... 1-12
THE DEVELOPMENT ENVIRONMENT................................................................................... 2-2
TITLE BAR.............................................................................................................................2-3
STATUS BAR.......................................................................................................................... 2-4
APPLICATION BUTTON.............................................................................................................. 2-5
QUICK ACCESS TOOLBAR......................................................................................................... 2-6
RIBBON................................................................................................................................ 2-7
PROJECT EXPLORER.............................................................................................................. 2-11
SCREEN/WORKSHEET EDITOR................................................................................................. 2-16
ABOUT TAGS AND THE PROJECT DATABASE...................................................................... 3-2
UNDERSTANDING THE TAG NAME SYNTAX......................................................................................3-4
CHOOSING THE TAG DATA TYPE................................................................................................... 3-5
USING ARRAY TAGS................................................................................................................. 3-6
ABOUT INDIRECT TAGS............................................................................................................. 3-9
TUTORIAL: BUILDING A SIMPLE PROJECT.........................................................................4-2
CREATING A NEW PROJECT........................................................................................................ 4-3
SPECIFYING THE STARTUP SCREEN.............................................................................................. 4-5
CREATING TAGS.....................................................................................................................4-6
CREATING THE MAIN SCREEN..................................................................................................... 4-8
CREATING THE SYNOPTIC SCREEN.............................................................................................4-13
Table of Contents
CONFIGURING THE COMMUNICATION DRIVER................................................................................4-22
DEPLOYING YOUR PROJECT AS A WEB APPLICATION.......................................................................4-26
II
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
CHAPTER
INTRODUCTION
1
INTRODUCTION...................................................................................................................1-2
CONVENTIONS USED ................................................................................................................ 1-2
ABOUT THIS SOFTWARE............................................................................................................ 1-3
COMPARISON OF POINT OF VIEW SOFTWARE COMPONENTS................................................................. 1-7
INSTALL THE FULL POINT OF VIEW SOFTWARE.................................................................................. 1-8
EXECUTION MODES............................................................................................................... 1-12
Chapter 1: Introduction
1
2
Introduction
Point of View (or POV, for short) is a powerful, integrated tool that exploits key features of
Microsoft operating systems and enables you to build fullfeatured SCADA (Supervisory Control
and Data Acquisition) or HMI (Human- Machine Interface) programs for your industrial
automation business. This Point of View Quick Start Guide is intended for individuals using POV
for the first time. This publication will help you quickly familiarize yourself with the basic functions
of POV.
3
Conventions Used
4
When you see the “note pad” icon in the left-hand margin, the paragraph to its immediate right will be a special
note. Notes represent information that may make your work quicker or more efficient. The word NOTE: in
boldface will mark the beginning of the text.
5
When you see the “exclamation point” icon in the left-hand margin, the paragraph to its immediate
right will be a warning. This information could prevent injury, loss of property, or even death in
extreme cases. Any warning in this manual should be regarded as critical information that should be
read in its entirety. The word WARNING in boldface will mark the beginning of the text.
6
7
Key Topics for Each Chapter
8
The beginning of each chapter will list the key topics
that can be found in that chapter.
9
Getting Started!
CHAPTER
1
In This Chapter...
Introduction .............................................................................1-2
Purpose of this Manual ....................................................................1-2
About Getting Started! ......................................................................1-2
Supplemental Manuals and Other Help ............................................1-2
Technical Support .............................................................................1-2
10
Conventions Used ....................................................................1-3
11
A
B
1-2
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
About This Software
1
Point of View is powerful software for developing HMI, SCADA, and OEE/Dashboard projects
that can be deployed anywhere.
2
Each POV project consists of:
• A project tags database to manage all runtime data, including both internal variables and scanned
I/O
3
• Configurable drivers to communicate in real-time with programmable logic controllers (PLCs),
remote I/O devices, and other data-acquisition equipment
• Animated HMI screens and OEE dashboards
4
• Optional modules such as alarms, events, trends, recipes, reports, scriptable logic, schedulers, a
security system, and a complete database interface.
Product Features
5
Alarms:
In addition to all the alarm functions you’d expect, POV v7.1+SP2 also sends alarms using multimedia formats like PDF. Use remote notification to have alarms sent right to your inbox, a printer,
or a smartphone. Alarms are real-time and historical, log data in binary format or to any database.
Animation:
POV gives you great command over graphics. Paste images and even rotate them dynamically.
Fill bar graphs with color, or adjust the scale of objects with easy-to-use configurations. Other
animations include “command” (for touch, keyboard and mouse interaction), hyperlink, text data
link, color, resize (independent height and width), position, and rotation (with custom rotation
point).
Database:
Connect to any SQL database (MS SQL, MySQL, Sybase, Oracle), or MS Access, or Excel, and
ERP/MES systems (including SAP). Flexible enough to have a built in interface without the need
for knowing SQL (for trends, alarms/events, grid and other objects), or use any SQL statement you
need anywhere you need it.
Drivers:
POV v7.1+SP2 contains 18 built-in drivers for most PLCs.
7
8
9
10
11
Email:
Send email using SMTP to desktop, email enabled phone, or any enabled device. Get real-time
information on alarms, process values, and other events. Point of View v7.1+SP2 supports SSL
encryption allowing the use of web based providers such as Gmail.
A
Events:
POV v7.1+SP2 offers traceability for operator initiated actions or internal system activity. Log events
such as security system changes (user logon or off ), screen open/close, recipe/report operations,
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
6
1-3
B
Chapter 1: Introduction
custom messages and system warnings. Also any tag value changes including custom messages.
1
2
3
4
5
6
7
8
9
10
11
A
B
FDA Traceability:
Take advantage of built-in functionality to create 21 CFR part 11 compliant projects with
traceability and e-signatures. These features are often used for pharmaceutical and food applications,
but also for any application where traceability is a must.
FTP:
Automatically upload or download files during runtime to/from remote storage locations using FTP
protocol and flexible scripting functions. Configure FTP via scripting or the included configuration
interface.
Graphics and Design Tools:
Create powerful screens to meet any application need using the improved tools in our graphic
interface. Combine built-in objects to create any functionality required. Store graphics in the library
for future use, or easily make projects across a product line share a consistent “look and feel”.
Historical Performance:
We have optimized the trend history module and designed it to load millions of values from
SQL Relational Databases with high performance and with built-in data decimation in the Trend
Control. Easy to use tools provide quick access to Statistical Process Control (SPC) values without
any need for programming.
Intellectual Property Protection:
Screens, documents, scripts and even math worksheets can be individually password protected. This
prevents unauthorized viewing or editing of your corporate custom functionality. Protect the entire
project with just a few mouse clicks.
Multi-Language:
Develop your application in one of many development languages, including English, Portuguese,
German and French.
.NET and ActiveX:
Use third-party controls to enhance your project. POV is a container for ActiveX and .NET
controls. Add functionality such as browsers, media players, charting, and other tools that support
the ActiveX or .NET interface standards.
OPC:
Drivers for several major brands of PLCs are built in, but any OPC server may optionally be used.
POV supports OPC DA (Server/Client), OPC HDA(Server), UA (Client) and OPC .NET 3.0
(Client).
PDF Export:
Send Alarms, Reports, or any file (including .doc or .txt) to a production supervisor, quality
manager, or maintenance staff using the included PDF writer.
1-4
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
Recipes:
Save time and maintain consistency by automating part parameters or productions quantities with
any triggering event.
1
Redundancy:
For critical applications where data is vital, POV v7.1+SP2 supports web server, database and overall
system redundancy.
2
Reports:
Create clear, concise reports in text format, graphical RTF, XML, PDF, HTML, and CSV or
integrate with Microsoft Office. Get the data you need, in the format you need it, to make informed
decisions, fast.
Scalable:
Develop once and deploy everywhere. Take an application created for Windows XP and deploy it on
any supported Microsoft operating system, including Windows 7, Windows 8, and Server editions.
Scheduler:
Schedule custom tag changes on date/time, frequency, or any trigger. Use this for simulation, to
trigger reports or other functionality at a particular time of day, or even to trigger driver worksheets
to read/write at a scan rate you choose.
3
4
5
6
7
Scripting:
Two powerful scripting languages are supported. Use built-in Automationdirect.com functions
or use standard VBScript to take advantage of widely available resources. Both can be used
simultaneously to give you the functionality you need.
8
Security:
POV includes support for group and user accounts, esignatures, and traceability, as well as support
for the ADAM Server, in addition to standard LDAP Servers. Integrate your project to the Active
Directory (Users and Groups).
9
SSL Support for Emails:
Native support for Secure Socket Layer (SSL), makes it easy and secure to send emails from Point of
View using web based tools such as Gmail.
10
Standards:
Take advantage of common industry standards to develop applications that are compatible with
any format. TCP/IP, .Net, ActiveX, OPC (client and server), ADO/ODBC, COM/DCOM, OLE,
DDE, XML, SOAP, and HTML are supported.
11
SNMP:
Easily configure managed networked devices on IP networks (such as switches and routers) using
incorporated SNMP configuration commands and an easy-to-use configuration interface.
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
A
B
1-5
Chapter 1: Introduction
1
2
3
4
5
6
7
8
Symbols:
Included library features: push buttons, pilot lights, tanks, sliders, meters, motors, pipes, valves
and other common objects. Use the included symbols in your project, modify existing symbols to
suit your needs, or create your own from scratch. Plus support for third-party symbol libraries and
graphic tools.
Tag Database:
POV features an object oriented database with boolean, integer, real, strings, arrays, classes
(structures), indirect tags and included system tags.
Thin Clients:
Remotely view screens as web pages using Internet Explorer web browser, or Automationdirect.com
Secure Viewer. Use SMA (Studio Mobile Access) to monitor or access process values and alarms
with remote devices such as tablets and mobile phones. Enhanced SMA offers data in easy-to-read
widgets that can be viewed on any WebKit (HTML5) based web browser found on iPads, and
Android phones and tablets.
Trends:
Real-time and Historical trends are supported. Log data in binary format or to any database locally
and remotely. Color or fill trends with graphic elements to enhance clarity of data. Date/Time based
or numeric (X/Y plot) trends give you the flexibility to display information that best suits your
application.
Troubleshooting:
Quickly debug and verify a project using local and remote tools for troubleshooting, including
status fields, DatabaseSpy and LogWin. Capture screen open and close times, see communications
in real-time, and messages related to OPC, recipes/reports, security, database errors and even custom
messages. Quickly get your project finished using these powerful tools.
9
10
11
A
B
1-6
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
Comparison of Point of View Software Components
1
The Point of View software suite actually comprises several individual components that can be
installed on different computers to perform different functions.
2
Comparison of Point of View Software Components
Component
Point of View
Web Tunneling Gateway (WTG)
Mobile Access Runtime
Automationdirect.com Thin Client
(a.k.a. Secure Viewer)
ISSymbol
Functions
Platforms
3
• Project development
• Tag integration
• Remote management
• Project runtime server
• Project runtime client
• Windows
• Windows Server
• Windows Embedded
Standard
• Enables a public-facing web
server to pass data between
your project runtime server and
web thin clients, when your
project runtime server is located
on a secure, internal network
• Microsoft IIS for Windows
• Enables your project runtime
server to deliver HTML5enhanced project screens to
tablets and smartphones
• Microsoft IIS for Windows
6
• Web thin client (standalone
application)
• Windows
• Windows Server
7
• Web thin client (browser plugin)
• Internet Explorer for Windows
4
5
The architecture of your finished POV project depends on which components you install, where
you install them, and how you connect them to each other.
8
In most cases, you should first install the full Point of View software on your primary workstation.
Not only does it set up the project development environment on your computer, it also unpacks the
rest of the components so that they can be installed on other computers.
9
10
There are separate, downloadable installers only for the web thin clients (i.e., Secure Viewer and
ISSymbol).
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
1-7
Chapter 1: Introduction
1
2
Install the Full Point of View Software
Install the full Point of View software on your Windows computer in order to develop POV
projects, or to use the computer as a project runtime server and/or client.
To install and run the full Point of View software, you must have:
3
1)
A Windows-compatible computer with a standard keyboard, pointer input (e.g., mouse,
trackpad, or touchscreen) and SVGA-minimum display
2)
A Windows, Windows Server, or Windows Embedded Standard operating system that is
currently supported by Microsoft, which at this time includes:
• Microsoft Windows XP Service Pack
• Microsoft Windows Vista Service Pack 2
4
• Microsoft Windows 7 Service Pack 1
• Microsoft Windows 8
• Microsoft Windows Server 2003 Service Pack 2
5
• Microsoft Windows Server 2008 Service Pack 2
• Microsoft Windows Server 2008 R2 Service Pack 1
• Microsoft Windows Server 2012
6
7
8
9
10
3)
Microsoft .NET Framework 3.5.1 (see note below);
4)
Microsoft Internet Explorer 6.0 or later;
5)
2 GB free hard drive space or non-volatile memory; and
6)
An Ethernet or Wi-Fi network adapter, for TCP/IP networking or Serial COM ports and
adapters to be used for direct communication with PLCs and other devices.
7)
A USB port, to be used with hardkey licensing.
We recommend the Home Premium, Professional, Enterprise, and Ultimate editions of Windows
because they include Microsoft Internet Information Services (IIS) as a pre-installed feature that
may be turned on. IIS is used to make your projects accessible to web thin clients and mobile
devices. We do not recommend the Starter and Home Basic editions because they do not include
IIS, but you may still use them if you do not plan to use those features.
The following items are optional but recommended:
• A DVD-ROM drive, to install the software from disc. This is optional because you may also
download the installer to your computer.
11
• Microsoft IIS installed and turned on, if you want to make your projects accessible to mobile
devices. For more information, see the description of Mobile Access Runtime later in this chapter.
This is optional because you may choose not to install the Mobile Access Runtime feature.
A
B
1-8
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
1
NOTE: You must have Administrator privileges on the computer in order to install software.
NOTE: Only Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012 are under what
Microsoft calls “mainstream support”, which means they are actively maintained and additional service packs
may be released for them in the future. The rest of the listed operating systems are under what Microsoft calls
“extended support”, which means they are no longer actively maintained.
2
3
NOTE: We do not support Point of View on Windows operating systems that Microsoft is not supporting or on
XP 64 bit.
4
NOTE: Microsoft .NET Framework 3.5.1 is a pre-installed feature on newer versions of Windows, but it may
not be turned on by default. To turn it on in Windows Vista, Windows Server 2008, Windows 7, or Windows
Server 2008 R2, use the Programs and Features control panel (Control Panel > Programs > Programs and
Features > Turn Windows features on and off ).
On older versions of Windows, Microsoft .NET Framework 3.5.1 must be installed separately. The Point of View
installer will attempt to do this for you (see Step 2 below), but depending on your computer’s security settings,
the installation may fail without notice. If you experience problems later, while trying to run Point of View,
then you should at least confirm that Microsoft .NET Framework 3.5.1 was installed successfully. To do this
in Windows XP or Windows Server 2003, use the Add/Remove Programs control panel (Control Panel > Add/
Remove Programs).
Please note that Microsoft .NET Framework 4 does not include Microsoft .NET Framework 3.5.1.
5
6
7
To install the full Point of View software:
1)
Do one of the following:
• Download the zipped installer to your computer, either from our website (www.automationdirect.com) or from another location on your network where you have previously saved it.
Extract the zip archive, open the resulting folder, and then locate and double-click setup.exe.
• Insert the installation disc into your DVD-ROM drive. If it does not autorun, then manually
run D:\automationdirect.htm. When the page opens in your browser, follow the instructions
for Product Installation.
The installation wizard runs and asks you to select a language for the installation.
2)
9
10
Select a language from the list, and then click OK.
This selection determines what language the installation wizard will use, as well as what
language the project development application’s user interface will be in. You may change the
language of the user interface later, after you have installed the software.
11
The wizard prepares for installation. During this step, it automatically installs SafeNet’s Sentinel
drivers.
3)
On the Welcome page of the wizard, click Next to proceed with the installation.
4)
On the License Agreement page, click either Yes to accept the agreement and proceed or No to
refuse the agreement and exit the wizard.
5)
On the Customer Information page, enter your user name and company name, and then click
Next.
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
8
1-9
A
B
Chapter 1: Introduction
6)
On the Choose Destination Location page, select the folder where the software should be
installed, and then click Next. By default, the software will be installed at: C:\Program Files\
AutomationDirect\Point of View v7.1\ (Program Files X86 if 64 bit operating system).
7)
On the Select Features page, select which software features and components you want to install
on your computer, and then click Next. The following features are available:
1
2
• Program Files - The main program files for the project development application, the project
runtime server, and the project runtime client. This feature cannot be deselected.
• Demos - Premade projects that demonstrate the capabilities of the Point of View software.
3
• Hardkey Support - Additional drivers to support the use of hardkey (USB port) software
licenses. This feature cannot be deselected.
• OPC Components - Additional components to communicate with other OPC compatible
devices. This includes OPC DA (a.k.a. OPC Classic), OPC UA, OPC .NET (a.k.a. OPC
Xi), and OPC XML-DA.
4
• PDF Printing - Software for printing run-time reports directly to PDF files.
• Security System Device Driver - An additional keyboard driver to control user input for
project security.
5
• Symbol Library - A library of premade but configurable screen objects such as pushbuttons,
toggle switches, gauges, dials, indicator lights, and so on.
6
• Windows Mobile - Additional runtime software for older Windows Mobile devices.
• Mobile Access Runtime - Additional software to automatically configure IIS to make your
project runtime accessible to mobile devices such as tablets and smartphones. This feature
requires that you have IIS turned on and configured with ASP, ASP.NET, and ISAPI
Extensions enabled. The Point of View installation wizard will attempt to verify that you do,
and if you do not, then it will not install this feature.
For more information, see the “Turn on Microsoft IIS for thin client access over the Internet”
help file topic.
7
8
You do not need to install this feature at this time. You may install it later, after you have
turned on IIS, or you may install it on another computer that is acting as your project
runtime server. There is a separate Mobile Access Runtime installer (MobileAccessSetup.exe)
that is unpacked with the rest of the software.
9
NOTE: To use Mobile Access Runtime, your Point of View software license must have the necessary add-on. You
may still develop projects that include Mobile Access features, even without the license add-on, but mobile devices
will not be able to access them.
10
11
A
8)
On the Ready To Install page, click Install and the installation proceeds.
9)
On the final page, click Finish and the wizard closes.
When you have finished the installation, you should find the Point of View software in your Start
menu at Start > All Programs > AutomationDirect > Point of View v7.1. It includes the following
components:
B
• Point of View v7.1+SP2 - The project development application, project runtime server, and
project runtime client.
1-10
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
• Register - A utility that manages your Point of View software license.
• StartUp - A shortcut that automatically starts the project runtime server and runs the most recent
project.
• Remote Agent - A utility that allows Point of View running on other computers to connect to
your computer and send projects to it.
1
2
• Quick Start Guide - A brief guide to installing and using the project development application,
including a tutorial for building a simple project.
• Help Manual - A complete technical reference and user guide for the Point of View software.
3
• Release Notes - A list of changes in the the Point of View software.
• There should also be a shortcut icon on your desktop.
4
NOTE: You may encounter the following error message during installation: “Error 1628: Failed to complete
script based install.” For more information about this error and how to resolve it, go to: http://consumerdocs.
installshield.com/selfservice/viewContent.do?externalId=Q108464
5
To run the project development application, do one of the following:
• Double-click the shortcut icon on the desktop
6
• Click, Start > All Programs > AutomationDirect > Point of View v7.1 > Point of View v7.1.
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
1-11
Chapter 1: Introduction
1
Execution Modes
Evaluation Mode
2
NOTE: When Windows UAC (User Account Control) is enabled, you will need to run POV as administrator
(at least once) to enable Evaluation Mode (otherwise, it will not have the rights to access the Windows Registry,
which is required for the Evaluation Mode). Please right-click on the POV icon (from the Desktop) and select
the option “Run as administrator”.
3
4
5
Enables all of the product’s engineering and runtime features. The first time you install Point of
View on a computer, the product runs for forty (40) hours in Evaluation Mode. This evaluation
period includes any time you run a product module (engineering or runtime). You can use this
evaluation period continuously or not; for example, 10 hours a day for 4 days, or 5 hours a day for 8
days, or 10 hours a day for 3 days plus 5 hours a day for 2 days, and so on.
After running for 40 hours in the Evaluation Mode, the evaluation period ends and the program
automatically converts to Demo Mode until you install a valid licensed hardkey. You cannot
reactivate Evaluation Mode, even if you reinstall the software on your computer.
6
NOTE: Each version of Point of View has an evaluation period that is independent of every other version. For
example, if your Point of View v7.0 evaluation period has expired and you are running in Demo Mode because
you have not installed a license, when you install Point of View v7.1+SP2 on the same computer, the newer
version will begin its own 40-hour evaluation period and the older version will continue running in Demo
Mode.
7
Demo Mode
8
9
Allows you to download projects to remote stations and to run projects for testing or demonstration
purposes. You can execute runtime tasks and use the debugging tools (LogWin and Database Spy),
but they shut down automatically after running for two hours continuously. You can restart the
Demo Mode again and run for another two hours, and so on.
You cannot create or modify screens, worksheets, or project settings in Demo Mode.
10
Licensed for Engineering Only
11
Enables all workbench options for an unlimited time. This mode also allows you to execute the
runtime tasks and debugging tools (Database Spy, Output window, and LogWin module) for 24
hours continuously. After the 24-hour period these tasks shut down, but you can restart them again
and run for another 24 hours, and so on. You can use this license for development and testing only.
A
Licensed for Runtime Only
B
Enables you to run all runtime and debugging tools (Database Spy, Output window, and LogWin
module) for unlimited time, but you cannot create or modify screens and/or worksheets.
The menu options available in Runtime Only mode are the same as the options listed for Demo
Mode.
1-12
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 1: Introduction
Licensed for Engineering + Runtime
Enables all engineering tools, runtime tasks, and debugging tools (Database Spy, Output window,
and LogWin module) for an unlimited period of time.
1
2
NOTE: The Remote Management tool is always available, regardless of the execution mode, so that you can
upload files from or download files to remote stations.
To see which execution mode you are currently running, click About on the Help tab of the ribbon;
the About dialog shows the execution mode, including the time remaining if you are in Evaluation
Mode.
3
4
5
6
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
1-13
Chapter 1: Introduction
1
Notes:
2
3
4
5
6
7
8
9
10
11
A
B
1-14
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
THE DEVELOPMENT
ENVIRONMENT
CHAPTER
2
THE DEVELOPMENT ENVIRONMENT.................................................................................... 2-2
TITLE BAR.............................................................................................................................2-3
STATUS BAR.......................................................................................................................... 2-4
APPLICATION BUTTON.............................................................................................................. 2-5
QUICK ACCESS TOOLBAR.......................................................................................................... 2-6
RIBBON................................................................................................................................ 2-7
PROJECT EXPLORER.............................................................................................................. 2-11
SCREEN/WORKSHEET EDITOR................................................................................................. 2-16
Chapter 2: The Development Environment
1
The Development Environment
Point of View incorporates a modern, Ribbon-based Windows interface to provide an integrated
and user-friendly development environment.
2
3
4
5
6
7
The POV Development Environment
8
9
10
11
A
B
2-2
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
Title Bar
The Title Bar located along the top of the development environment displays the application name
(e.g., Point of View) followed by the name of the active screen or worksheet (if any).
1
2
Example of Title Bar
3
The Title Bar also provides the following buttons (from left to right):
• Minimize button
: Click to minimize the development environment window to the Taskbar.
• Restore Down / Maximize: Click to toggle the development environment window between two
sizes:
• Restore Down button
• Maximize button
4
reduces the window to its original (default) size.
enlarges the window to fill your computer screen.
5
• Close button
: Click to save the database and then close the development environment. If
you modified any screens or worksheets, the application prompts you to save your work. This
button’s function is similar to clicking Exit Application on the Application menu.
6
NOTE: Closing the development environment does not close either the project viewer or the runtime system, if
they are running.
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-3
Chapter 2: The Development Environment
1
Status Bar
The Status Bar located along the bottom of the development environment provides information
about the active screen (if any) and the state of the application.
2
Example of Status Bar
3
The Status Bar fields (from left to right) are described in the following table:
Field
Execution Mode
4
CAP
Indicates whether the keyboard Caps Lock is on
(black) or off (grey).
NUM
Indicates whether the keyboard Num Lock is on
(black) or off (grey).
SCRL
Indicates whether the keyboard Scroll Lock is on
(black) or off (grey).
5
Object ID
6
7
8
9
Description
The current execution mode of the application.
The ID number of a selected screen object.
Cursor Position
The location of the cursor on the active screen or
worksheet. If it’s a screen, then the position of the
mouse cursor is given as X,Y coordinates, where X is
the number of pixels from the left edge of the screen
and Y is the number of pixels from the top edge of the
screen. If it’s a worksheet, then the position of the text
cursor is given as Line and Column.
Object Size
The size (in pixels) of a selected screen object, where
W is the width and H is the height.
No DRAG
Indicates whether dragging is disabled (No DRAG) or
enabled (empty) in the active screen.
Tag Count
The total number of tags used so far in the project.
10
11
A
B
2-4
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
Application Button
1
The Application button opens a menu of standard Windows application commands like New,
Open, Save, Print, and Close.
2
3
4
5
6
7
Application Button Opens Menu of Commands
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-5
Chapter 2: The Development Environment
1
2
Quick Access Toolbar
The Quick Access Toolbar is a customizable toolbar that contains a set of commands that are
independent of the ribbon tab that is currently displayed.
Move the Quick Access Toolbar
The Quick Access Toolbar can be located in one of two places:
• Upper-left corner next to the Application button (default location); or
3
4
• Below the ribbon, where it can run the full length of the application window.
If you don’t want the Quick Access Toolbar to be displayed in its current location, you can move it
to the other location:
5
1)
Click Customize Quick Access Toolbar
2)
In the list, click Show Below Ribbon or Show Above Ribbon.
.
Add a Command to the Quick Access Toolbar
6
You can add a command to the Quick Access Toolbar directly from commands that are displayed on
the ribbon:
7
8
1)
On the ribbon, click the appropriate tab or group to display the command that you want to
add to the Quick Access Toolbar.
2)
Right-click the command, and then click Add to Quick Access Toolbar on the shortcut menu.
You can also add and remove commands — as well as reset the toolbar to its default — using the
Customize dialog:
9
1)
Click Customize Quick Access Toolbar
2)
In the list, click More Commands.
The Customize dialog is displayed.
3)
In the Choose commands from
menu, select the appropriate
Ribbon tab. The commands
from that tab are displayed in the
Commands list.
4)
In the Commands list, select the
command that you want to add to
the Quick Access Toolbar.
5)
Click Add.
10
11
A
Only commands can be added to the
Quick Access Toolbar. The contents of
most lists, such as indent and spacing
values and individual styles, which also
appear on the ribbon, cannot be added
to the Quick Access Toolbar.
B
2-6
.
Customize Quick Access Toolbar Dialog
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
Ribbon
1
The ribbon combines the numerous menus and toolbars into a single, user-friendly interface.
Almost all application commands are on the ribbon, organized into tabs and groups according to
general usage.
2
3
The Ribbon Interface
4
Home Tab
The Home tab of the ribbon is used to manage your project within the development environment.
5
6
Home Tab of the Ribbon
The tools are organized into the following groups:
7
• Clipboard: Cut, copy, paste, and find items in project screens and task worksheets.
• Local Management: Run and stop the project on the local station (i.e., where the development
application is installed), as well as manage the execution tasks.
• Remote Management: Connect to a remote station so that you can download the project to it,
and then run, stop, and troubleshoot the project on that station. For more information, see the
“About remote management” help file topic.
8
9
• Tools: Miscellaneous tools to verify the project, import tags from other projects, convert screen
resolutions, and register ActiveX and .NET controls.
• Tags: Manipulate tags and tag properties in the project database.
10
View Tab
The View tab of the ribbon is used to customize the look of the development environment itself.
11
A
View Tab of the Ribbon
B
The tools are organized into the following groups:
• Show/Hide: Show and hide the different parts of the development environment, as well as restore
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-7
Chapter 2: The Development Environment
the default layout.
1
• Zoom: Zoom in and out of the screen editor.
• Options: Change the language and font used in the development environment.
• Window: Arrange the windows in the development environment.
2
3
Insert Tab
The Insert tab of the ribbon is used to insert new tags, screens, worksheets, and other components
into your project.
4
Insert Tab of the Ribbon
5
The tools are organized into the following groups:
• Global: Insert tags, classes, translations, and procedures into the Global tab of the Project
Explorer.
6
• Graphics: Insert screens and screen groups into the Graphics tab of the Project Explorer.
• Task Worksheets: Insert task worksheets into the Tasks tab of the Project Explorer.
7
8
• Communication: Insert server configurations and communication worksheets into the Comm tab
of the Project Explorer.
Project Tab
The Project tab of the ribbon is used to configure your project settings.
9
Project Tab of the Ribbon
10
The tools are organized into the following groups:
11
• Settings: Configure the general project settings or set the project to run as a Windows service.
• Security System: Enable and configure the project security system.
• Web: Configure the project to accept connections from a variety of thin clients.
A
B
2-8
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
Graphics Tab
1
The Graphics tab of the ribbon is used to draw project screens.
2
3
4
Graphics Tab of the Ribbon
NOTE: This tab is available only when you have a project screen open for editing.
5
The tools are organized into the following groups:
6
• Screen: Configure settings for the project screen itself, such as its attributes, script, and
background color or image.
• Editing: Select and edit objects in the project screen.
7
• Shapes: Draw static lines and shapes.
• Active Objects: Draw active objects, like buttons and check boxes.
• Data Objects: Draw objects that display historical data, like alarms, events, and trends.
• Libraries: Select from libraries of premade objects, such as symbols, .NET and ActiveX controls,
and external image files.
• Animations: Apply animations to other screen objects.
8
9
Format Tab
The Format tab of the ribbon is used to format and arrange objects in a project screen.
10
11
Format Tab of the Ribbon
NOTE: This tab is available only when you’ve selected one or more objects in a project screen.
A
The tools are organized into the following groups:
B
• Arrange: Arrange objects in a project screen, including bring to front and send to back, group,
align, and rotate.
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-9
Chapter 2: The Development Environment
• Position: Precisely adjust the position of a screen object in a project screen.
1
• Size: Precisely adjust the size of a screen object.
• Style: Change the fill and line color of a screen object.
• Fonts: Change the caption font of a screen object.
2
Help Tab
The Help tab of the ribbon provides additional help with using the software.
3
4
Help Tab of the Ribbon
5
The tools are organized into the following groups:
• Documentation: Access the documentation for the development application, including this help
file/technical reference and notes for the individual communication drivers.
6
• Information: Access other information about Point of View, including the license agreement,
product website, and release notes, as well as system and support details that make it easier for
Customer Support to assist you.
7
8
9
10
11
A
B
2-10
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
Project Explorer
The Project Explorer organizes all of the screens, worksheets, and other items that comprise your
project and presents them in an expandable tree-view.
To open a folder and view its contents, either click the Expand icon to the left of the folder or
double-click the folder itself.
To close a folder, click the Collapse icon to the left of the folder.
If you right-click any item in the Project Explorer, then a shortcut menu will appear with contextual
commands for that item.
There are four main sections, or tabs, in the Project Explorer: Global, Graphics, Tasks, and Comm.
Global Tab
The Global tab of the Project Explorer contains the project tags database, as well as other features
that apply to the entire project such as the security system, VBScript procedures, and UI translation.
1
2
3
4
5
6
7
8
9
10
Global Tab of the Project Explorer
11
The folders on the Global tab are described in the following sections:
A
• Project Tags: The project tags database contains all of the data tags that you create during project
development, such as screen tags (e.g., button1_state) or tags that read from / write to connected
devices.
• Classes: Classes are compound tags that you can create to associate a set of values, rather than a
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-11
B
Chapter 2: The Development Environment
single value, with an object. For example, where you may normally create separate tags for a tank’s
pressure, its temperature, and its fill level, you can instead create a “tank” class that includes all
three.
1
• Shared Database: The shared database contains tags that were created in another program and
then imported into or integrated with your project.
2
• System Tags: System tags are predefined values such as the date, the time, the name of the current
user, and so on. You can use these values to develop supervisory functions and housekeeping
routines.
You cannot add, edit, or delete these tags from the database.
3
• Security: If you choose to enable it, you can use the project security system to control who may
log on to your project and what they may do during runtime.
4
• Procedures: Procedures are VBScript functions and sub-routines that can be called by any other
script in your project.
• Event Logger: The event logger saves important runtime messages and task results to an external
database.
5
6
7
• Translation: You can use the translation table to develop a multilingual user interface (MUI) for
your project.
Graphics Tab
The Graphics tab of the Project Explorer contains all of the screens, screen groups, and symbols in
your project.
8
9
10
11
A
B
Graphics Tab of the Project Explorer
2-12
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
The folders on the Graphics tab are described in the following sections:
1
• Screens: You create screens to provide a graphical interface for your project. Each screen can
contain many buttons, sliders, dials, indicators, graphs, and so on.
• Screen Groups: You can combine individual screens into screen groups, so that they all open
together at the same time.
• Thin Clients: You can deploy your project as a web application to be accessed by thin clients such
as desktop web browsers, tablets, and smartphones. You can even deploy different versions of your
project with different levels of functionality for each type of client.
• Project Symbols: This folder contains all of the custom symbols that you create for your project.
A symbol is a group of interconnected screen objects that work together to perform a single
function — for example, lines, rectangles, and text fragments that have been arranged to make a
slider control.
• Graphics Script: You can use this worksheet to define VBScript sub-routines that are called only
when the graphics module starts (i.e., when a client station connects to the server and displays the
graphical interface), while it is running, and when it ends.
• Symbols: The symbols library contains not only the custom symbols that you create (see
Project Symbols above), but also a large selection of premade symbols that are installed with the
development application.
• Layout: The layout editor displays all of the screens the are currently open for editing. You can use
it to visualize how the screens are arranged together and reuse screens in multiple layouts — for
example, to create a common navigation bar across your entire project.
2
3
4
5
6
7
Tasks Tab
The Tasks tab of the Project Explorer organizes the
worksheets that are processed as background tasks
(i.e., server-based maintenance tasks that are not
directly related to screen operations or device I/O)
during project runtime.
8
9
The folders on the Tasks tab are described in the
following sections:
10
• Alarms: You can use Alarm worksheets to
define when alarms are trigged, how they must
be handled, and what messages they generate.
(You can then use the Alarm/Event Control
screen object to display your alarms on screen,
but that is a separate procedure.)
11
• Trends: You can use Trend worksheets to select
project tags that should be displayed as data
trends and/or saved as historical data.
(You can then use the Trend Control screen
object to actually display your trends on
screen, but that is a separate procedure.)
A
B
Tasks Tab of the Project Explorer
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-13
Chapter 2: The Development Environment
• Recipes: You can use Recipe worksheets to select project tags that will load values from and/or save
values to an external file. These worksheets are typically used to execute process recipes, but you
can store any type of information such as passwords, operation logs, and so on.
(You can then call the Recipe function to actually run a configured Recipe worksheet, but that is a
separate procedure.)
1
2
• Reports: You can use Report worksheets to design runtime reports that are either sent to a printer
or saved to disk. (You can then call the Report function to actually run a configured Report
worksheet, but that is a separate procedure.)
3
• ODBC: You can use ODBC worksheets to set up connections and exchange data with other
ODBC-compliant databases.
• Math: You can use Math worksheets to develop complex runtime logic using the built-in scripting
language.
4
• Script: You can use Script worksheets to develop complex runtime logic using VBScript.
• Scheduler: You can use Scheduler worksheets to run commands at specified times, dates, or
trigger events.
5
6
7
• Database: You can use Database worksheets to set up connections and exchange data with
external databases using the standard ADO.NET interface (as an alternative to ODBC).
Comm Tab
The Comm tab of the Project Explorer organizes the worksheets that control communication with
remote devices, using either direct communication drivers or other common protocols.
8
9
10
11
A
B
Comm Tab of the Project Explorer
2-14
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 2: The Development Environment
The folders on the Comm tab are described in the following sections:
• Drivers: You can use Driver worksheets to communicate with PLCs and other hardware, using
any of the hundreds of direct communication drivers that are installed with the development
application.
1
• OPC DA 2.05: You can use OPC worksheets to communicate with OPC servers via the OPC
Classic protocol.
2
• OPC UA: You can use OPC UA worksheets to communicate with OPC servers via the new OPC
Unified Architecture protocol.
• OPC .Net: You can use OPC .Net worksheets to communicate with OPC servers via the new
OPC .NET 3.0 protocol (formerly OPC Xi).
3
• OPC XML/DA: You can use OPC XML/DA worksheets to communicate with OPC servers via
the new OPC XML-DA protocol.
4
• TCP/IP: You can use TCP/IP worksheets to configure communication between your own project
and other POV projects. The TCP/IP Client and TCP/IP Server modules enable two or more
projects to keep their databases synchronized using the TCP/IP protocol.
5
• DDE: You can use DDE worksheets to communicate with other Microsoft Windows applications,
such as Microsoft Excel, that support the Dynamic Data Exchange protocol.
6
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
2-15
Chapter 2: The Development Environment
1
2
Screen/Worksheet Editor
Use the powerful, object-oriented screen editor to create and edit a variety of screens and worksheets
for your projects. You can input information using your mouse and keyboard, output control data
to your processes, and automatically update screens based on data input from your processes.
3
4
5
6
7
Screen/Worksheet Editor
8
Other screen editor features include:
• Simple point-and-click, drag-and-drop interface
9
• Grouping objects to preserve the construction steps of individual objects
• Editing objects without having to ungroup internal object components or groups
• Handling bitmap objects and background bitmaps
10
• Status line support in project windows and dialogs
11
A
B
2-16
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
ABOUT TAGS AND THE
PROJECT DATABASE
CHAPTER
3
ABOUT TAGS AND THE PROJECT DATABASE............................................................ 3-2
UNDERSTANDING THE TAG NAME SYNTAX......................................................................................3-4
CHOOSING THE TAG DATA TYPE................................................................................................... 3-5
USING ARRAY TAGS................................................................................................................. 3-6
ABOUT INDIRECT TAGS............................................................................................................. 3-9
Chapter 3: About Tags and the Project Database
1
2
3
4
About Tags and the Project Database
Tags are a core component of any POV project. Simply put, tags are variables used by POV to
receive and store data obtained from communication with plant floor devices, from the results of
calculations and functions, and from user input. In turn, tags can be used to display information on
screens (and Web pages), to manipulate screen objects, and to control runtime tasks.
But tags are more than simple variables. POV includes a real-time database manager that provides a
number of sophisticated functions such as timestamping of any value change, checking tag values
against runtime minimum and maximum values, comparing tag values to alarming limits, and so
on. A POV tag has both a value and various properties that can be accessed, some at development
and others only at runtime.
5
6
7
8
9
10
11
All tags are organized into one of the following categories, which are represented by folders on the
Global tab of the Project Explorer:
a. Project Tags are tags that you create during project development. Places where project tags are used
include:
A
• Screen tags
• Tags that read from/write to field equipment
• Control tags
B
• Auxiliary tags used to perform mathematical calculations
b. Shared Database tags are created in a PC-based control program and then imported into POV’s
3-2
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 3: About Tags and the Project Database
tags database.
For example, you might create tags in Productivity Suite and import them into POV so POV can
read/write data from a P3000 PAC based control product.
You cannot modify shared tags within POV — you must modify the tags in the original PC-based
control program, and then re-import them into the Tags database.
c. System Tags are predefined tags with predetermined functions that are used for POV supervisory
tasks. For example,
1
2
• Date tags hold the current date in string format
3
• Time tags hold the current time in string format
Most system tags are read-only, which means you cannot add, edit, or delete these tags from the
database.
To see a list of the system tags, select the Global tab in the Project Explorer, open the System Tags
folder, and open the Tag List subfolder. The figure, shown on previous page, shows a partial list of
system tags.
4
5
After creating a tag, you can use it anywhere within the project, and you can use the same tag for
more than one object or attribute.
6
NOTE: System tags do not count against your project tag count.
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
3-3
Chapter 3: About Tags and the Project Database
1
Understanding the Tag Name Syntax
Observe the following guidelines when naming a tag:
• Your tag names must be unique — you cannot specify the same name for two different tags (or
functions). If you type an existing tag name, POV recognizes that the name exists and will not
create the new tag.
2
• You must begin each tag name with a letter. Otherwise, you can use letters, numbers, and the
underscore character (_) in your tag name.
3
• You cannot use the following symbols in a tag name:
`~!@#$%^&*()-=\+\[]{}<>?
• You can use a maximum of 255 characters for a tag name or a class member name.You can use
uppercase and lowercase characters. Tag names are not case sensitive. Because POV does not
differentiate between uppercase and lowercase characters, you can use both to make tag names
more readable. (For example: TankLevel instead of tanklevel.)
4
• Tag names must be different from system tag names and math functions.
5
NOTE: Use the @ character at the beginning of a tag name to indicate that the tag will be used as an indirect
tag in the project.
6
Some valid tag examples include:
• Temperature
7
• pressure1
• count
8
• x
9
10
11
A
B
3-4
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 3: About Tags and the Project Database
Choosing the Tag Data Type
1
Another consideration when designing a tag is what type of data the tag will receive. POV
recognizes the following, standard tag data types:
• Boolean (one bit): Simple boolean with the possible values of 0 (false) and 1 (true). Equivalent
to the “bool” data type in C++. Typically used for turning objects off and on or for closing and
opening objects.
2
• Integer (four bytes): Integer number (positive, negative, or zero) internally stored as a signed
32-bit. Equivalent to the “signed long int” data type in C++. Typically used for counting whole
numbers or setting whole number values. Examples: 0, 5, −200.
3
• Real (floating point, eight bytes): Real number that is stored internally as a signed 64-bit.
Equivalent to the “double” data type in C++. Typically used for measurements or for decimal or
fractional values.
4
• String (alphanumeric data, up to 1024 characters): Character string up to 1024 characters that
holds letters, numbers, or special characters. Supports both ASCII and UNICODE characters.
Examples: Recipe product X123, 01/01/90, *** On ***.
5
You can also assign a new tag to a class that you have previously created.
You can find these tag types (and their respective icons) in the Global tab of the Project Explorer.
6
See also: Understanding Tag Properties and Parameters help file topic
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
3-5
Chapter 3: About Tags and the Project Database
1
Using Array Tags
POV tags can consist of a single value or an array of values.
NOTE: The maximum array size is 16384 as long as it does not exceed the maximum number of tags supported
by the license (Product Type) selected for the project. Each array position (including the position 0) counts as one
tag for licensing restrictions, because each position has an independent value.
2
3
An array tag is a set of tags with the same name, which is identified by indexes (a matrix of n lines
and 1 column). The maximum array size depends on the product specification. You can use the
following syntax to access an array tag: ArrayTagName[ArrayIndex]
For example: tank[0], tank[1], tank[2], and tank[500].
4
WARNING: You must specify a maximum index for each array tag in the size column of any
datasheet. You can specify n to indicate the array tag has positions from 0 to n. For example, if the
size of TagA is 3, the tag elements could be TagA[0], TagA[1], TagA[2], and TagA[3].
5
NOTE: When using the PAC3K Driver, the index minimum is 1.
6
7
Use the array tag whenever possible because it optimizes memory use and simplifies the
configuration task. For example, if you want a display to monitor each tank, you could use
array tags to configure a single display containing tags linked to any tank. For example (use
the tk tag as an index containing the number of the tank): pressure[tk], temperature[tk], and
temperature[tk+1].
An array index can be a tag, a numeric value, or an expression with the arithmetic operator “+”.
8
NOTE: When you refer to an array with an index using the + arithmetic operation, you must use the following
syntax: ArrayTagName[NumValue1+NumValue2]
Where NumValue1 and NumValue2 can be an integer tag or a numerical constant. For example:
temperature[tk+2] or temperature[tk+6].
9
10
Using array tags in any POV task can save a signification amount of project development time.
For example, if you needed tag points related to the temperature of four tanks. The conventional
configuration method is the following:
• temperature1: high temperature on tank 1
• temperature2: high temperature on tank 2
11
• temperature3: high temperature on tank 3
• temperature4: high temperature on tank 4
Using array tags simplifies this task, as follows:
A
• temperature[j]: high temperature on tank {j}
NOTE: When you create a four-position array tag, the system creates five positions (from 0 to 4). For example:
tag_example[15] //start position=0, end position=15
Therefore, the tag_example[15] array has 16 elements.
B
3-6
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 3: About Tags and the Project Database
When using another tag to reference the index of an array, if the value of the tag is outside the size
of the array, then the following results are given:
• If IndexTag is greater than the size of the array, then MyArray[IndexTag] will point to the end
position of the array; and
• If IndexTag is less than 0, then MyArray[IndexTag] will point to the start position of the array.
1
2
Array Tags
An array tag consists of a set of tags that all have the same name, but use unique array indexes (a
matrix of n lines and one column) to differentiate between each tag. An array index can be a fixed
value, another tag or an expression. Maximum array sizes are determined by product specifications.
3
You can use array tags to:
4
• Simplify configurations
• Enable multiplexing in screens, recipes, and communication interfaces
5
• Save development time during tag declaration
You specify array tags in one of two formats:
• For a simple array tag, type:
6
ArrayTagName[ArrayIndex]
• For a complex array tag (where the array index is an expression consisting of a tag and an
arithmetic operation), type:
7
ArrayTagName[ArrayIndex+c]
Where:
8
• ArrayTagName is the tag name;
• [ArrayIndex] is the unique index (fixed value or another tag);
• “+” is an arithmetic operation; and
9
• “c" is a numerical constant.
NOTE: You must specify a maximum index for each array tag by typing a value (n) in the Array Size column
of an Project Tags datasheet or in the Array Size field on a New Tag dialog. (See “Creating project database
Tags” in help file).When you create an n-position array tag, POV actually creates n+1 positions (from 0 to n).
For example, if you specify ArrayTag[15], the array will have 16 elements, where 0 is the start position and 15
is the end position.
You must not use spaces in an array tag.
When POV reads a tag it begins with the first character and continues until it finds the first space or null
character. Consequently, the system does not recognize any characters following the space as part of the array tag.
For example, if you type a[second + 1], POV regards a[second as the tag and considers it invalid because POV
does not find (recognize) the closing bracket. However, if you type a[second +1], this is a valid array tag.
You can specify an array tag wherever you would use a variable name. Also, because array tags greatly
simplify configuration tasks and can save development time, we suggest using them whenever
possible.
For example, suppose you want to monitor the temperature of four tanks. The conventional
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
3-7
10
11
A
B
Chapter 3: About Tags and the Project Database
configuration method is:
1
• temperature1 — high temperature on tank 1
• temperature2 — high temperature on tank 2
• temperature3 — high temperature on tank 3
2
• temperature4 — high temperature on tank 4
You can use array tags to simplify this task as follows (where [n] represents the tank number):
• temperature[n] — high temperature on tank [n]
3
The following table contains some additional examples of an array tag:
4
Array Tag Examples
Array Tag Example
5
6
7
Description
Tank[1], Tank[2], Tank[500]
Simple arrays, where the array indexes (1, 2, and
500) are numerical constants. For example, tank
numbers.
Tank[tk]
A simple array, where the array index (tk) is a tag.
For example, a tag representing the tank number.
Tank[tk+1]
A complex array, where the array index (tk+1) is
an expression. For example, the value of tk (tank
number) plus 1.
NOTE: When using another tag to reference the index of an array, if the value of the tag is outside the size of the
array, then the following results are given:
· If IndexTag is greater than the size of the array, then MyArray[IndexTag] will point to the end position of the
array; and
· If IndexTag is less than 0, then MyArray[IndexTag] will point to the start position of the array (i.e.,
MyArray[0]).
8
9
10
11
A
B
3-8
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 3: About Tags and the Project Database
About Indirect Tags
POV supports indirect access to tags in the database. For example, consider a tag X of the String
type. This tag can hold the name of any other tag in the database (that is, it can provide a pointer to
any other type of tag, including a class type). The syntax for an indirect tag is straightforward:
@IndirectTagName.
For example, assume that a tag named X holds a "TEMP" string. Reading and/or writing to @X
provides access to the value of the TEMP variable.
1
2
3
NOTE: Any tag created as a string-type tag is potentially an indirect tag (pointer).
To refer to a class-type tag, you can declare a string-type tag that points to a class tag. For example:
Class
TANK with members Level
Tag
TK of the class TANK
Tag
XCLASS of the String type
5
To access the TK.Level value, you must store the " TK.Level" value within the XCLASS tag and use
the syntax, @XCLASS. You can also refer to a member of a class-type tag directly; identifying a classtype that points to a class member. For example:
Class
4
7
TANK with members Level
Tag
TK of the class TANK
Tag
XCLASS of the class TANK
6
8
To access the TK.Level value, you must store the "TK" value within the XCLASS tag and use the
syntax, @XCLASS.Level.
When creating tags for indirect use, place an X in the tag column rather than creating them
as strings. For the type, write the type of tag for which you are creating a reference. Follow the
XCLASS example: @Z Integer, @X Class:TANK.
9
Indirect Tags
10
Indirect tags "point" to other database tags (including class-type tags). Using indirect tags can save
development time because they keep you from having to create duplicate tags (and the logic built
into them).
You create an indirect tag from any string-type tag simply by typing the @ symbol in front of the tag
name @TagName.
11
• To reference a simple tag, assume the strX tag (a string tag) holds the value "Tank", which is the
name of another tag, then reading from or writing to @strX provides access to the value of the
Tank tag.
A
• To reference a class-type tag and member, you simply create a string tag that points to the class tag
and the member. For example, if a tag strX (a string tag) holds the value "Tank.Level", which is
the name of the class tag, then reading from or writing to @strX provides access to the value of the
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
3-9
Chapter 3: About Tags and the Project Database
Tank.Level member.
1
• You can also point directly to a class-type tag member; by identifying a class-type that points to
a class member. For example: to access the Tank.Level member of the class, you must store the
"Tank" value within the strX tag and use the syntax, @strX.Level.
2
3
4
5
6
7
8
9
10
11
A
B
3-10
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
TUTORIAL: BUILDING A
SIMPLE PROJECT
CHAPTER
4
TUTORIAL: BUILDING A SIMPLE PROJECT.........................................................................4-2
CREATING A NEW PROJECT........................................................................................................ 4-3
SPECIFYING THE STARTUP SCREEN.............................................................................................. 4-5
CREATING TAGS......................................................................................................................4-6
CREATING THE MAIN SCREEN...................................................................................................... 4-8
CREATING THE SYNOPTIC SCREEN.............................................................................................4-13
CONFIGURING THE COMMUNICATION DRIVER...............................................................................4-22
DEPLOYING YOUR PROJECT AS A WEB APPLICATION.......................................................................4-26
Chapter 4: Tutorial: Building a Simple Project
1
Tutorial: Building a Simple Project
This section explains, using a step-by-step tutorial, how to build a simple project, as well as how to
select and configure an I/O driver.
2
3
4
5
6
7
8
9
10
11
A
B
4-2
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
Creating a New Project
1
This part of the tutorial shows how to create a new project, including how to give it a name and
select the target platform.
1)
Click the Application button in the top-left corner of the development environment, and then
click New on the Application menu. The New dialog is displayed.
2)
Click the Project tab.
3)
In the Project name box, type the name of your project. For this tutorial, type Tutorial.
The development application automatically creates a new directory of the same name and
assigns your project file to that directory. (Notice the Configuration file text box in the figure.)
To put your project file somewhere other than in the default projects folder, click Browse and
navigate to the preferred location.
4)
In the Product type list, select the type of project that you want to build. For this example,
select Windows Standard. This is a tag and feature-limited product type that can be safely
deployed on Windows PC Platforms.
2
3
4
5
6
7
8
9
10
11
Selecting the target platform and product type
A
5)
Click OK.
The New dialog is closed and the Project Wizard dialog is displayed.
6)
In the Template list, select Empty Application.
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
B
4-3
Chapter 4: Tutorial: Building a Simple Project
7)
In the Resolution list, select 640 x 480.
1
2
3
4
5
Specifying an empty Application with 640x480 resolution
6
8)
7
Click OK.
The Project Wizard dialog is closed and the new project is created in the development
environment.
8
9
10
11
A
B
4-4
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
Specifying the Startup Screen
1
This part of the tutorial shows how to open the project settings and then specify which screen
should be displayed on startup.
• Use the Information tab to provide information that identifies the project (such as project
description, revision number, Company name, Author's name, field equipment, and general
notes).
2
• Use the Options tab to specify generic settings for the project, such as the Target System,
Automatic Translation, Alarm history and Events, Default Database and Shared Tags.
3
• Use the Viewer tab to enable/disable the runtime desktop parameters.
• Use the Communication tab to specify communication parameters relating to the project in
general.
4
• Use the Preferences tab to enable/disable warning messages when using the development
application.
5
To specify the startup screen:
1)
On the Project tab of the ribbon, in the Settings group, click Viewer.
The Project Settings dialog box is displayed with the Viewer tab selected.
2)
In the Startup screen box, type main.scr.
When you run the project, it will automatically display the main screen (or whichever screen
you specify) first. You can specify a screen before you create it, but if the screen has been
created, then you can also select it from the list.
3)
6
7
Click OK.
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-5
Chapter 4: Tutorial: Building a Simple Project
1
2
Creating tags
This part of the tutorial shows how to create new tags by adding them to the Project Tags datasheet.
A tag is any variable that holds a value. All tags created in an project are stored in the Project Tags
folder, on the Global tab of the Project Explorer.
3
4
5
6
Project Tags folder
7
1)
In the Project Explorer, click the Global tab.
2)
Double-click Project Tags to expand the folder.
3)
Double-click Datasheet View to open the Project Tags datasheet.
4)
Use the following parameters to create a tag for the sample project.
a. Name: Specify a unique tag name. For this tutorial, type Level.
8
b. Array: Specify the top array index of the tag. (Simple tags have an Array of 0.) For this
tutorial, type 3.
9
Each array index relates to one of the three tanks:
• Level[1] is the level of Tank #1
• Level[2] is the level of Tank #2
10
• Level[3] is the level of Tank #3
You will not use Level[0] in this tutorial, even though it is a valid tag.
c. Type: Specify the data type of the tag: Boolean, Integer, Real, String, or Class. For this
tutorial, select Integer.
11
d. Description (optional): Type a description of the tag for documentation purposes only.
e. Scope: Specify how the tag is managed between the Server and the Thin Client stations.
A
• Select Local if you want the tag to have independent values on the Server and Client
stations.
• Select Server if you want the tag to share the same value on the Server and Client
stations.
B
For this tutorial, select Server.
4-6
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
1
2
Creating the Level tag
5)
3
Save and close the Project Tags datasheet.
You will create additional tags as you build the project.
4
NOTE: You can sort the data in the Project Tags datasheet or insert/remove additional columns by rightclicking on it and then choosing the applicable option from the pop-up menu.
5
6
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-7
Chapter 4: Tutorial: Building a Simple Project
1
Creating the Main Screen
This part of the tutorial shows how to create your first screen, which will contain a single button
that opens another screen.
2
1)
In the Project Explorer, click the Graphics tab.
2)
Right-click Screens, and then click Insert on the shortcut menu.
The development application stores all screens created for an project in this Screens folder.
3
4
5
6
7
8
The Screen Attributes dialog box is displayed.
9
10
11
A
B
Screen Attributes dialog box
4-8
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
3)
Use this dialog to set screen properties such as size and type.
For this tutorial, click OK to accept the default settings.
The Screen Attributes dialog box is closed, and the new screen is opened in the workspace for
editing.
1
4)
On the Graphics tab of the ribbon, in the Screen group, click Background Color. A standard
color picker is displayed.
2
5)
In the color picker, select a light gray color.
3
4
5
Color Picker
6
That color is applied to the screen.
Drawing the Main Screen's Title
This part of the tutorial shows how to draw the main screen's title using a Text object.
1)
On the Graphics tab of the ribbon, in the Active Objects group, click Text.
Your mouse cursor changes from an arrow to a crosshair.
2)
Click on the screen, type Welcome to the Tutorial Application, and then press Return.
This creates a new Text object with the specified text.
3)
Double-click the object to open its Object Properties dialog box.
7
8
9
10
11
Object Properties: Text dialog box
• Double-clicking on any screen object opens an Object Properties dialog box containing the
properties for that object. The properties shown in the dialog change depending on the type
of object.
• The Object Properties dialog box also contains a pin button that controls whether this dialog
remains open. The button changes state (and function) each time you click on it, as follows:
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-9
A
B
Chapter 4: Tutorial: Building a Simple Project
• When the pin button is released, the focus is passed to the object on the screen as soon
as it is selected. It is recommended that this button is kept released when you want to
manipulate the objects (Copy, Paste, Cut, or Delete). Although the Object Properties
dialog box is on the top, the keyboard commands (Ctrl+C, Ctrl+V, Ctrl+X, or Del) are
sent directly to the objects.
1
2
• When the pin button is pressed, the focus is kept on the Object Properties dialog, even
when you click the objects on the screen. We recommend you keep this button pressed
when you want to modify the settings of the objects. You can click an object and type the
new property value directly in the Object Properties dialog (it is not necessary to click on
the window to bring focus to it). Also, when the pin button is pressed, the Object
Properties dialog does not automatically close when you click on the screen.
3
4)
4
Click Fonts to open Font
dialog box, and then specify
the font settings.
For this tutorial…
• Font is Arial
5
• Font style is Regular
• Size is 20
• Color is Blue
6
7
Specifying the font settings
5)
8
Click OK to close the Font dialog box.
The font settings are applied to the Text object.
9
10
11
A
B
Font settings applied to Text object
4-10
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
6)
Close the Object Properties dialog box (i.e., click the Close button in the dialog box's top-right
corner).
1
Drawing a Button to Open Another Screen
This part of the tutorial shows how to draw and configure a button that will open another screen.
1)
On the Graphics tab of the ribbon, in the Active Objects group, click Button.
Your mouse cursor changes from an arrow to a crosshair.
2)
Click and hold on the screen, and then drag the cursor to draw the Button object.
3)
Double-click the object to open its Object Properties dialog box.
4)
In the Caption box, type the following text: Click here to open the synoptic screen.
2
3
4
5
6
7
8
9
Adding a caption to the button
5)
Click Command.
The Object Properties dialog box changes to show the properties for the Command animation.
6)
In the Type list, select Open Screen.
7)
In the Open Screen box, type synoptic.scr.
10
11
A
B
Configuring an Open Screen command on the button
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-11
Chapter 4: Tutorial: Building a Simple Project
You can specify a screen that you have not yet created.
1
8)
Close the Object Properties dialog box.
Saving and Closing the Main Screen
2
This part of the tutorial shows how to properly save and close a screen.
3
1)
Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
A standard Windows Save dialog box is displayed.
2)
In the File name box, type main.
3)
Click Save.
The file is saved in your project folder (at […]\Documents\Point of View v7.1 Projects\
projectname\Screen\main.scr), and the Save dialog box is closed.
4)
Click the Application button at the top-left of the development environment, and then click
Close on the Application menu.
4
5
6
7
8
9
10
11
A
B
4-12
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
Creating the Synoptic Screen
1
This part of the tutorial show how to create your second screen, which will include an animated
tank of liquid and some basic controls for that tank.
1)
In the Project Explorer, click the Graphics tab.
2)
Right-click the Screens folder, and then click Insert on the shortcut menu.
The Screen Attributes dialog box is displayed.
3)
Use this dialog box to set attributes such as size and type.
For this tutorial, click OK to accept the default settings.
3
4)
Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
A standard Windows Save dialog box is displayed.
4
2
5)
In the File name box, type synoptic.
6)
Click Save.
The file is saved in your project folder (at […]\Documents\Point of View v7.1 Projects\project_
name\Screen\synoptic.scr), and the Save dialog box is closed.
5
Do not close the screen like you did the main screen when you saved it. You still need to draw the
synoptic screen.
6
Drawing the Synoptic Screen's Title
7
As in a previous part, this part of the tutorial shows how to draw the synoptic screen's title using a
Text object.
1)
On the Graphics tab of the ribbon, in the Active Objects group, click Text.
2)
Click on the screen, type Synoptic Screen, and then press Return.
3)
Double-click the object to open its Object Properties dialog box.
4)
Click Fonts to open Font dialog, and then specify the font settings.
For this tutorial…
8
9
• Font is Arial
• Font style is Bold
10
• Size is 20
• Color is Blue
11
5)
Close the Object Properties dialog box.
6)
Move the Text object to the top left corner of the screen.
7)
Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
A
This figure shows how your screen should look after you've created the screen title.
B
Finished screen title
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-13
Chapter 4: Tutorial: Building a Simple Project
Drawing "Date" and "Time" Displays
1
This part of the tutorial shows how to draw "Date" and "Time" displays by linking Text objects to
system tags. Date and Time are system tags that hold the current date and time of the local station.
These tags are available to any project.
2
3
4
1)
On the Graphics tab of the ribbon, in the Active Objects group, click Text.
2)
Click on the screen, type Date: ##########, and then press Return.
3)
Double-click the object to open its Object Properties dialog box.
4)
Click Text Data Link.
The Object Properties dialog changes to show the properties for the Text Data Link animation.
5)
In the Tag/Expression box, type Date.
5
6
7
Specifying the Date system tag
During runtime, the project replaces the ########## characters of the Text object with the
value of the system tag Date.
8
9
6)
Close the Object Properties dialog box.
7)
On the Graphics tab of the ribbon, in the Active Objects group, click Text.
8)
Click on the screen, type Time: ##########, and then press Return.
9)
Double-click the object to open its Object Properties dialog box.
10) Click Text Data Link.
The Object Properties dialog changes to show the properties for the Text Data Link animation.
10
11) In the Tag/Expression box, type Time.
11
A
B
Specifying the Time system tag
4-14
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
During runtime, the project replaces the ########## characters of the Text object with the
value of the system tag Time.
1
12) Close the Object Properties dialog box.
13) Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
2
This figure shows how your screen should look after you've created the date and time objects.
3
Finished date and time objects
4
Placing an "Exit" Icon
This part of the tutorial shows how to place an icon (by selecting and configuring a Linked Symbol)
that allows the user to exit the runtime project.
5
NOTE: If any part of the project doesn't work as expected (or to exit the runtime application), switch back to
the development application (ALT+TAB) and then click Stop on the Home tab of the ribbon. Then if needed,
begin troubleshooting.
6
1) On the Graphics tab of the ribbon, in the Libraries group, click Symbols.
The symbols library is displayed.
2)
In the Symbols menu tree, open the System Symbols folder and then open the Icons sub-folder.
3)
In the Icons sub-folder, select exit01.
The symbol will be displayed in the symbol viewer to the right of the menu tree.
4)
Click on the symbol.
The mouse cursor will change to show that the symbol is ready to be placed in a screen.
7
8
9
10
11
Selecting the "exit01" symbol
5)
A
Switch back to the screen where you want to place the symbol and then click in it. The symbol
is placed as a Linked Symbol object.
B
Placing the Linked Symbol object
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-15
Chapter 4: Tutorial: Building a Simple Project
1
2
6)
With the object still selected, click Command (on the Graphics tab of the ribbon, in the
Animations group) to apply this animation to the object.
7)
Double-click the object to open its Object Properties dialog box.
8)
In the Type list, select VBScript.
9)
In the On Down box, type $Shutdown().
Shutdown is one of Point of View's built-in scripting functions, but it can be used within
VBScript by prefacing it with a dollar sign ($).
3
4
5
Specifying the Shutdown command on the symbol
6
10) Close the Object Properties dialog box.
11) Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
7
8
Now, when a user clicks this icon during runtime, the project will stop and exit to the station's
desktop.
Testing the Project
This part of the tutorial show how to test the project so far.
9
10
11
1)
On the Home tab of the ribbon, in the Local Management group, click Run.
The project runs and the startup screen is displayed.
2)
Click the button to open the synoptic screen.
The synoptic screen is displayed.
3)
Click the exit icon to shut down the project.
If any part of the project doesn't work as expected, switch back to the development application
(ALT+TAB) and then click Stop on the Home tab of the ribbon.
Placing an Animated Tank
A
This part of the tutorial shows how to select an animated tank from the Symbol Library and place it
on the screen (similar to how you selected and placed the "Exit" icon), then associate some project
tags with the tank's properties.
B
4-16
1)
On the Graphics tab of the ribbon, in the Libraries group, click Symbols.
2)
In the Symbols menu tree, open the System Symbols folder and then open the Tanks
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
sub-folder.
3)
1
In the Tanks sub-folder, select a tank symbol.
You may select any tank you like; they all function basically the same way.
2
3
4
5
6
Selecting a tank symbol
4)
Click on the symbol.
The mouse cursor will change to show that the symbol is ready to be placed in a screen.
5)
Switch back to the screen where you want to place the symbol and click in it.
The symbol is placed as a Linked Symbol object.
6)
Double-click the object to open its Object Properties dialog box.
7
8
9
10
11
A
The tank symbol's properties
A tank is an arrangement of different objects and animations (for example a rectangle, a bar
graph, etc.), all combined together as a Linked Symbol. You can modify the properties of this
symbol by editing the properties list. For this tutorial, you will modify the tag associated with
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-17
B
Chapter 4: Tutorial: Building a Simple Project
the tank level.
1
7)
For the property TagLevel, delete the existing value and then type Level[Index].
Note that you do not need to reopen the Project Tags datasheet to create tags as you develop the
project.
Because you have not previously created the tag Index in the Project Tags database, an alert
message asks you if you would like to create it.
8)
Click Yes.
A New Tag dialog is displayed.
9)
Configure the new tag with Array as 0, Type as Integer, and Scope as Local.
2
3
4
5
6
Configuring a new tag
7
10) Click OK to close the New Tag dialog.
You can use the tag Index to set the array position of the tag Level, and show the level for any of
the three tanks in the same object:
8
• When Index equals 1, the tank object shows the level of Tank #1 (i.e., Level[1]);
• When Index equals 2, the tank object shows the level of Tank #2 (i.e., Level[2]); and
• When Index equals 3, the tank object shows the level of Tank #3 (i.e., Level[3]).
9
Also, because the tag scope is local, the tag can have different values for the Server and
Client stations at the same time. Consequently, the local user (i.e., the Server station) can be
monitoring the level of Tank #1 while the remote user (i.e., the Client station) is monitoring
the level of Tank #2.
10
11) Close the Object Properties dialog box.
12) Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
This figure shows how your screen should look after you've created the tank object.
11
A
B
Finished tank object
4-18
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
Placing a Level Slider
1
This part of the tutorial shows how to select a slider control from the Symbol Library and then
connect it to the animated tank.
1)
On the Graphics tab of the ribbon, in the Libraries group, click Symbols.
2)
In the Symbols menu tree, open the System Symbols folder and then open the Sliders
sub-folder.
2
3
4
5
6
7
Selecting a slider symbol
3)
In the Sliders sub-folder, select a slider control.
You may select any slider you like; they all function basically the same way.
4)
Click on the symbol.
The mouse cursor will change to show that the symbol is ready to be placed in a screen.
5)
Switch back to the screen where you want to place the symbol and click in it.
The symbol is placed as a Linked Symbol object.
6)
Double-click the object to open its Object Properties dialog box.
7)
For the property TagName, delete the existing value and then type Level[Index].
Just as with the tank, you need to modify the symbol property associated with the slider level.
8)
Close the Object Properties dialog box.
9)
Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
8
9
10
11
A
B
Finished level slider object
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-19
Chapter 4: Tutorial: Building a Simple Project
Drawing a Tank Selector
1
This part of the tutorial shows how to draw a text input box that can be used to change which realworld tank is represented by the animated tank on the screen.
2
3
4
5
1)
On the Graphics tab of the ribbon, in the Active Objects group, click Text.
2)
Click on the screen, type Tank: #, and then press Return.
3)
Double-click the object to open its Object Properties dialog box.
4)
Click Text Data Link.
The Object Properties dialog changes to show the properties for the Text Data Link animation.
5)
In the Tag/Expression box, type Index.
6)
Select the Input Enabled option.
This allows the operator to enter a new value for the tag during runtime.
7)
In the Minimum Value box, type 1.
8)
In the Maximum Value box, type 3.
6
7
8
Configuring the "Tank" text input
9
9)
Close the Object Properties dialog box.
10) Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
10
This figure shows how your screen should look after you've created the tank selector object
(shown with a red arrow).
11
A
B
Finished tank selector object during runtime
4-20
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
Testing the Project
1
This part of the tutorial show how to test the project again with the animated tank, the level slider,
and the tank selector.
1)
On the Home tab of the ribbon, in the Local Management group, click Run.
The project runs and the startup screen is displayed.
2)
Click the button to open the synoptic screen.
The synoptic screen is displayed.
3)
Type the tank number (1, 2, or 3) in the Tank label, and then use the slider to adjust the tank
level.
Note that you can view/adjust the level of each tank independently.
3
4)
Click the exit icon to shut down the project.
4
2
If any part of the project doesn't work as expected, switch back to the development application
(ALT+TAB) and then click Stop on the Home tab of the ribbon.
5
6
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-21
Chapter 4: Tutorial: Building a Simple Project
1
Configuring the Communication Driver
This part of the tutorial shows how to select and configure a driver to communicate with an external
I/O device.
NOTE: If you are using a DirectLOGIC or P3000 controller, see the Quick Start Guide for AutomationDirect
Drivers manual (PV-ADCDRV-M) for information pertaining to those controllers.
2
3
1)
In the Project Explorer, click the Comm tab.
2)
Right-click the Drivers folder, and the click Add/Remove Drivers on the shortcut menu.
The Communication Drivers dialog is displayed.
4
3)
Select a driver from the Available drivers list, and then click Select.
For this tutorial, select MODBU.
The driver is moved to the Selected drivers list.
5
6
7
8
9
MODBU driver selected
10
11
4)
Click OK.
The Communication Drivers dialog is closed, and the driver is added to the Drivers folder in
the Project Explorer.
5)
In the Project Explorer, right-click the MODBU folder, and then click Settings on the shortcut
menu.
A
B
4-22
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
The Communication Settings dialog is displayed.
1
2
3
4
5
Communication Settings dialog for MODBU driver
6)
Configure the communication settings as needed for the target device. For this tutorial, accept
the default settings.
6
NOTE: For more information about a specific driver, click Communication Drivers on the Help tab of the
ribbon.
7
7)
Click OK to close the dialog.
8)
In the Project Explorer, right-click the MODBU folder and then click Insert on the shortcut
menu.
A new driver worksheet named MODBU001.drv is created and opened for editing.
9)
8
Configure the worksheet header:
a. In the Description box, type Tutorial Modbus.
This setting is for documentation only; it does not affect the runtime project in any way.
9
b. In the Enable Read When Idle box, type 1.
This setting is a trigger that takes a Boolean value. A value of 1 — either entered manually
as above or evaluated from a tag/expression — forces your project to continue reading tag
values from the target device even when there are no changes in value.
c. In the Enable Write On Tag Change box, type 1.
This setting is also a trigger. A value of 1 forces your project to write tag values to the target
device only when those values change, rather than continuously. This saves system resources
and improves performance during rutime.
10
11
d. In the Station box, type 1.
This indicates the I/O device number to be accessed by this driver.
Typically, the PLC is specified as Device #1.
A
e. In the Header box, type 4X:0.
You must use a driver-specific format. The format for the MODBU driver is:
register_type:initial_offset
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-23
Chapter 4: Tutorial: Building a Simple Project
Register Type
1
2
Description
0x
Coil Status
1x
Input Status
3x
Input Register
4x
Holding Register
ID
Slave ID Number
3
4
5
6
7
Completed worksheet header
10) In the worksheet body, enter the tags and their associated device addresses — for each tag:
8
a. In the Tag Name field, type the name of the project tag.
b. In the Address field, type the value to be added to the header to form the complete device
address.
9
10
Tag Name
Address
Complete Device Address
Level[1]
1
4X:1 (Holding Register 1)
Level[2]
2
4X:2 (Holding Register 2)
Level[3]
3
4X:3 (Holding Register 3)
11
A
B
Completed worksheet body
4-24
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
11) Click the Application button at the top-left of the development environment, and then click
Save on the Application menu.
1
12) When prompted to choose the driver sheet number, type 1 and then click OK.
Monitoring Device I/O During Runtime
2
This part of the tutorial shows how to monitor device I/O during runtime by using the Log
window.
1)
On the Home tab of the ribbon, in the Local Management group, click Run.
The project runs and the startup screen is displayed.
2)
Press ALT+TAB to switch back to the development application.
3)
Right-click in the Output window, and then click Settings.
The Log Settings dialog is displayed.
4)
Select the Field Read Commands, Field Write Commands, and Protocol Analyzer options.
5)
Click OK to close the Log Settings dialog.
3
4
5
You can now monitor the device I/O during runtime.
6
7
8
9
10
11
A
B
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-25
Chapter 4: Tutorial: Building a Simple Project
1
2
3
Deploying Your Project as a Web Application
This part of the tutorial shows how to deploy your project as a web application, to which remote
users can connect with Internet Explorer.
For Internet Explorer to work as a web thin client, it must install an ActiveX control that "plays"
POV project screens. If your computer is connected to the Internet, then IE will automatically
download the control from AutomationDirect.com's public server when you connect to a project
runtime server for the first time.
To deploy your project as a web application:
1)
Configure the IP address of the data server.
a. On the Project tab of the ribbon, in the Thin Clients group, click Web.
The Project Settings dialog box is displayed with the Web tab selected.
4
5
6
7
8
Web tab of Project Settings dialog box
9
b. In the Data Server IP Address box, type the IP address of the web server.
For this tutorial, type 127.0.0.1, which is the standard loopback address (a.k.a. "localhost").
c. Click OK to close the dialog.
10
2)
Make sure the data server is set to start up when you run your project.
a. On the Home tab of the ribbon, in the Local Management group, click Tasks.
11
A
B
4-26
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Chapter 4: Tutorial: Building a Simple Project
The Execution Tasks dialog box is displayed.
1
2
3
4
5
6
7
Execution Tasks dialog box
8
b. In the list of tasks, select TCP/IP Server Runtime, and then click Startup.
The Startup dialog box is displayed.
9
10
Startup dialog box
11
c. Select Automatic, and then click OK.
d. Click OK to close the Execution Tasks dialog box.
A
3)
Save and close all open screens and worksheets.
4)
Click the Application button at the top-left of the development environment, and then click
Publish > Save All As HTML on the Application menu.
Your project screens are saved as HTML files in the Web sub-folder of your project folder
(i.e., \project_name\Web).
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
4-27
B
Chapter 4: Tutorial: Building a Simple Project
5)
1
2
Configure a web server to make the Web sub-folder available to the network.
For this tutorial, use NT Web Server, the free, lightweight web server program that is included
with POV. Simply copy the program file from […]\AutomationDirect\Point of View v7.1\Bin\
NTWebServer.exe to the Web sub-folder, and then double-click the file to run it. It
automatically serves the contents of whatever folder it is in, without any further configuration.
WARNING: NT Web Server is provided for testing purposes only. It should never be used in a real
production environment or on a secure network.
3
You can also configure the "root directory" or "home directory" setting of some other web
server program (e.g., Microsoft IIS) to point to the Web sub-folder, or you can copy the
Web sub-folder to an existing web server on your network. The web server (which makes the
HTML files available to clients) and the data server (which actually runs your POV project and
exchanges data with the clients) do not need to be the same computer.
4
5
6
6)
On the Home tab of the ribbon, in the Local Management group, click Run.
7)
Open a web browser (e.g., Microsoft Internet Explorer), and then enter the URL address of the
synoptic screen on the web server. For this tutorial, type http://127.0.0.1/synoptic.html and
then press Return. (127.0.0.1 is the standard IP address for the loopback network interface,
a.k.a. "localhost.")
After a few moments, during which the browser downloads and installs the ActiveX control, the
synoptic screen is displayed in the browser.
Notice that you can modify the level of any tank either locally using the project viewer or remotely
using the web browser, and changes on one client appear immediately on the other. They work
equally well.
7
8
9
10
11
A
B
4-28
Point of View Software Reference Guide, 1st Edition - PV-SWREF-M
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising