Professional Documents
Culture Documents
IWS v70 Quick Start Guide PDF
IWS v70 Quick Start Guide PDF
I
nduS
oft.
com
i
nfo@I
nduSof
t.
com
InduSoft® is a registered trademark of InduSoft, Inc.
InduSoft Web Studio™ is a trademark of InduSoft, Inc.
Windows, Windows, Windows XP, Windows XP Embedded, Windows Embedded Standard 7, Windows Embedded Com-
pact, Windows 2003 Server, Windows 2008 Server, Windows Vista, Windows 7,
Windows CE, and Internet Explorer are registered trademarks of Microsoft Corp. in the United States and other coun-
tries.
The information contained within this document is subject to change without notice.
InduSoft, Inc. does not guarantee the accuracy of the information.
PN: 092310-GSG-IWS-A-EN-PT
Contents
Contents
INTRODUCTION......................................................................................................................... 3
Product Overview................................................................................................................. 4
Product Features...........................................................................................................5
Conventions used in this documentation..............................................................................8
INSTALLATION......................................................................................................................... 10
System requirements..........................................................................................................11
Installing the Software........................................................................................................ 14
Starting the Software.......................................................................................................... 19
Uninstalling the Software....................................................................................................20
THE DEVELOPMENT ENVIRONMENT....................................................................................21
Title bar...............................................................................................................................22
Status bar........................................................................................................................... 23
Application menu................................................................................................................ 24
Quick Access Toolbar......................................................................................................... 25
Ribbon................................................................................................................................ 27
Home tab.....................................................................................................................27
View tab.......................................................................................................................28
Insert tab..................................................................................................................... 28
Project tab................................................................................................................... 29
Graphics tab................................................................................................................ 29
Format tab................................................................................................................... 30
Help tab....................................................................................................................... 31
Project Explorer.................................................................................................................. 32
Global tab.................................................................................................................... 32
Graphics tab................................................................................................................ 33
Tasks tab..................................................................................................................... 34
Comm tab....................................................................................................................36
Screen/Worksheet Editor....................................................................................................38
ABOUT TAGS AND THE PROJECT DATABASE....................................................................39
Tag Name Syntax............................................................................................................... 41
Tag Data Type.................................................................................................................... 42
Using Array Tags................................................................................................................ 44
Using Indirect Tags............................................................................................................. 48
List of Tag Properties..........................................................................................................50
Reset Tags Database......................................................................................................... 58
Introduction
InduSoft Web Studio (or IWS) is a powerful, integrated tool that exploits key
features of Microsoft operating systems and enables you to build full-featured
SCADA (Supervisory Control and Data Acquisition) or HMI (Human-Machine
Interface) programs for your industrial automation business.
This InduSoft Web Studio Quickstart Guide is intended for individuals using
IWS for the first time. This publication will help you quickly familiarize
yourself with the basic functions of IWS.
Product Overview
InduSoft Web Studio projects run on microcomputers connected in real-time
to machines or processors through programmable controllers, remote I/O
devices, and other data-acquisition equipment.
These projects consist of animated operator-interface screens, configurable
PLC (programmable logic controller) drivers and other controllable I/O
devices, a project tags database, and optional modules such as alarm
monitors, logic, trend charts, recipes, schedulers, and a security system.
IWS projects interface with industrial I/O systems and other Windows
applications in the runtime environment using the following protocols:
• ODBC (Open Database Connectivity)
• DDE (Dynamic Data Exchange)
• NetDDE (Network Dynamic Data Exchange)
• OPC (Open Connectivity)
• TCP/IP (Transmission Control Protocol/Internet Protocol)
After developing a project, you can run it on your development workstation
or download the project to a runtime workstation (using a serial or TCP/
IP connection) and run it using InduSoft Web Studio or CEView runtime
software. The workstation processes scan data from connected devices
according to parameters defined in the project and then react to, display,
store and upload the data.
The product consists of two parts:
• The development system software runs on a desktop, laptop, or industrial
PC running a currently supported Microsoft Windows desktop or server
operating system.
• The runtime system software runs on an operator interface workstation
running a currently supported Microsoft Windows desktop operating
system or Windows Embedded.
Product Features
The InduSoft Web Studio product provides the following features:
• Integrated Windows development environment with toolbars, dialogs, and
menus:
• Drop-down (pop-up) menus, which you activate by right-clicking on
any area of the development environment (Options vary according to
context.)
• Customizable fly-over toolbars
• Tasks, objects, and controls organized in a tree-view explorer
• Full-featured objects and animations (the ability to modify object
properties, execute commands, or inset values to tags used to build
screens on the fly at runtime):
• Configurable objects such as buttons, rectangles, ellipse, polygons,
lines, and text
• Object animations such as bar graphs, color, resizing, position, hide/
unhide, rotation, command, hyperlink, and text input/output
• On-line and historical alarm list displays
• On-line and historical trending
• Alignment and distribution tools
• Background bitmap layer creation and editing
• Graphics importation
• ActiveX object containers
• On-line remote management and configuration
• Microsoft DNA architecture compliance, with full OPC and XML support
• Web interface enabled, which exports project screens to a "thin" client
through the Internet/intranet and by exchanging data on-line through the
TCP/IP protocol
• Symbols library with more than 100 pre-made objects, such as
pushbuttons, meters, sliders, switches, text and numeric displays, LED-
style indicators, pipes, bumps, icons, vehicles, valves, frames, motors,
gauges, and common controls
• Debugging tools:
Note: IWS provides different product types for each level of project
responsibility. However, IWS does not support some features in
certain product types. For more information, see About target
platforms and product types.
Text conventions
This documentation uses special text formatting to help you quickly identify
certain items:
• Titles, labels, new terms, and messages are indicated using italic text (for
example, Object Properties).
• File names, screen text, and text you must enter are indicated using
monospace text (for example, D:\Setup.exe ).
• Buttons, menu options, and keyboard keys are indicated using a bold
typeface (for example, File menu).
In addition, this documentation segregates some text into Tip, Note, and
Caution boxes:
• Tips provide useful information to save development time or to improve
the project performance.
• Notes provide extra information that may make it easier to understand
the nearby text, usually the text just before the note.
• Cautions provide information necessary to prevent errors that can cause
problems when running the project, and may result in damage.
• Select also means you should use your pointing device to highlight
or specify an item on the computer screen. Selecting an item with a
touchscreen is usually the same as selecting with a mouse, except that
you use your finger to touch (select) a screen object or section. To select
items with your keyboard, you typically use the Tab key to move around
options, the Enter key to open menus, and the Alt key with a letter key to
select an object that has an underlined letter.
• Drag means to press down the appropriate mouse button and move the
mouse before releasing the button. Usually an outline of the item will
move with the mouse cursor.
Windows conventions
This documentation uses the following Windows conventions:
• dialoges (or dialogs) are windows that allow you to configure settings and
enter information.
• Text boxes are areas in dialogs where you can type text.
• Radio buttons are white circles in which a black dot appears or
disappears when you click on the button. Typically, the dot indicates the
option or function is enabled (selected). No dot indicates the option or
function is disabled (not selected).
• Check boxes are white squares in which a check ( ) appears or
disappears when you click on it with the cursor. Typically, a check
indicates the option or function is enabled (selected). No check indicates
the option or function is disabled (not selected).
• Buttons are icons in boxes appear "pressed" when you click on them.
• Lists are panes (white boxes) in windows or dialogs containing two or
more selectable options.
• Combo boxes have arrows that, when clicked, show part or all of an
otherwise concealed list.
• Dockable windows are windows that you can drag to an edge of the
interface and merge with that edge.
Installation
System requirements
These are the minimum system requirements to install and run the InduSoft
Web Studio software.
Note:
• You must have Administrator privileges on your PC in order to
install or uninstall the development application.
• You must uninstall an older version of the development
application (or move it to a different directory) before installing
a new version. Also, you cannot install the same version of the
development application in two different paths on the same PC.
The instructions for installing InduSoft Web Studio and CEView are provided
inthe following two sections.
4. Click Run.
The product's installation wizard will begin.
5. Follow the wizard's instructions to proceed with the installation.
6. When the installation is finished, select Yes, I want to restart my computer now
and then click OK.
After your PC has restarted, you can run the development application. See
Starting the Software for instructions.
The build for your specific device is located in the following directory:
…where:
• version is the version of the operating system on the device where
CEView will be installed:
• The\WinCE 5.0 folder contains the files for Windows CE and Windows
Mobile 5.0 or later; and
• The\WinEmbedded folder contains the files for Windows XP Embedded
and Windows Embedded 7.
• processor is the processor used by your Windows CE device. We provide
a CEView runtime for every processor that is currently supported by the
Windows CE operating system (e.g., Pocket2003-ArmV4, ArmV4i, x86).
For more information, consult the manufacturer's documentation for the
device.
To install the files on your device, use the Remote Management tool in the
development application.
Installing via TCP/IP (Ethernet)
There are different ways to install the file — for example, you can use
Microsoft ActiveSync (for Windows 2000 and Windows XP) or Windows
Mobile Device Center (for Windows Vista) to communicate directly with
the device or you can map the device as a shared folder on your PC.
For more information about copying and executing files, consult the
manufacturer's documentation for the device.
3. In the Remote Agent dialog, click Setup and then configure the
communication settings for the device's network connection. In particular,
note the IP address of the device.
4. Start the development application on your PC.
5. On the Home tab of the ribbon, in the Remote Management group, click Connect.
The Remote Management dialog is displayed:
Tip: You can run the IWS development environment under any
video setting. However, we recommend that you configure the video
settings to a resolution of 800x600 (or higher) and use more than
256 colors for a more pleasing environment. The project resolution
(screen size) is independent of the operating system resolution.
If you find it necessary to remove IWS from your system, follow these
instructions:
1. From the Windows task bar, select Start > Settings > Control Panel to open the
Control Panel.
2. Double-click on the Add/Remove Programs icon in the Control Panel window.
3. When the Add/Remove Programs Properties dialog displays, select
InduSoft Web Studio from the list and click Add/Remove.
4. When the Confirm File Deletion dialog displays, click Yes.
The Uninstall Shield Wizard and the Remove Programs from Your Computer
dialogs display.
5. When the Uninstall successfully completed message displays and
the OK button becomes active, click OK.
Verify that InduSoft Web Studio is no longer listed in the Add/Remove
Programs Properties dialog.
6. Click the Cancel button or the close button ( ), to close the Add/Remove
Programs Properties dialog, then close the Control Panel window.
7. Open the Windows Explorer and browse to IWS program directory.
8. Verify that all of the IWS files and folders were deleted. (You must
manually delete any that remain.)
Note: The uninstall tool cannot delete files you created or modified
in your IWS projects folder.
You must have administrator privileges to uninstall (and install)
InduSoft Web Studio.
Title Bar
The Title Bar located along the top of the development environment displays
the application name (e.g., InduSoft Web Studio) followed by the name of the
active screen or worksheet (if any).
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 reduces the window to its original (default) size.
• Maximize button enlarges the window to fill your computer screen.
• 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.
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.
The Status Bar fields (from left to right) are described in the following table:
Field Description
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.
Application button
The Application button opens a menu of standard Windows application
commands like New, Open, Save, Print, and Close.
Ribbon
The new ribbon combines the numerous menus and toolbars from the
previous version of IWS into a single, user-friendly interface. Almost all
application commands are now on the ribbon, organized into tabs and
groups according to general usage.
Home tab
The Home tab of the ribbon is used to manage your project within the
development environment.
View tab
The View tab of the ribbon is used to customize the look of the development
environment itself.
Insert tab
The Insert tab of the ribbon is used to insert new tags, screens, worksheets,
and other components into your project.
Project tab
The Project tab of the ribbon is used to configure your project settings.
Graphics tab
The Graphics tab of the ribbon is used to draw project screens.
Note: This tab is available only when you have a project screen
open for editing.
Format tab
The Format tab of the ribbon is used to format and arrange objects in a project
screen.
Note: This tab is available only when you've selected one or more
objects in a project screen.
Help tab
The Help tab of the ribbon provides additional help with using the software.
Project Explorer
The Project Explorer organizes all of the screens, worksheets, and other
components that make up your project and presents them in an expandable
tree-view.
Click the Expand icon or double-click the folder to view the contents of the
folder. Click the Collapse icon to close the folder.
If you right-click on any component in the Project Explorer, a shortcut menu
is displayed with options for that component.
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 security and UI
translation.
The folders on the Global tab are described on the following pages:
• Project Tags contains tags you create during project development (such as
screen tags or tags that read from/write to field equipment).
• Classes contains compound tags, called class tags, created to associate a
set of values (rather than a single value) with an object.
• Shared Database contains tags that were created in a PC-based control
program and then imported into the project tags database.
For example you can import SteepleChase tags into your project so that it
can read/write data from a SteepleChase PC-based control product.
• System Tags contains predefined tags with predetermined functions that are
used by the project for specific, supervisory tasks (for example, Date tags
hold the current date in string format).
All system tags are read-only, which means you cannot add, edit, or
remove these tags from the database.
• Security contains all of the group and individual user security accounts
configured for the current project.
• Procedures contains VBScript functions and sub-routines that can be called
by any other script in the project.
• Event Logger contains logging and event-retrieval features.
• Translation contains the translation worksheet that defines how your
project's user interface should be translated into another language.
Graphics tab
The Graphics tab of the Project Explorer contains all of the screens, screen
groups, and symbols in your project.
The folders on the Graphics tab are described on the following pages:
• Screens contains all of the screens created for the current project.
Tasks tab
The Tasks tab of the Project Explorer organizes the worksheets that are
processed as background tasks during project runtime.
The folders on the Tasks tab are described on the following pages:
• Alarms contains the Alarm worksheets used to configure alarm groups
and the tags related to each alarm group in the project. You also use
the Alarm task to define the alarm messages generated during project
runtime.
• Trend contains the Trend worksheets used to configure history groups that
store trend curves for the project. You can use the Trend task to declare
which tags must have their values stored on disk, and to create history
files for trend graphs. Your project stores the samples in a binary history
file (*.hst), and displays both history and on-line samples in a trend
graph screen.
• Recipes contains the Recipe worksheets used to configure how data is
exchanged between the project database and disk files in ASCII or DBF
format, and how values are transferred between files and real-time
memory.
• Reports contains the Report worksheets used to configure reports (text
type) that are sent to a printer or a disk. Reports tasks allow you to
configure text reports with system data, which makes report creation
easier and more efficient.
• ODBC contains the ODBC worksheets used to configure how the ODBC
interface runs in a network environment and uses standard Windows
ODBC configuration. You configure ODBC tasks to exchange data
between your project and any database supporting the ODBC interface.
• Math contains the Math worksheets used to configure and implement
additional routines to work with different tasks. Your project executes
Math worksheets as Background Tasks during runtime. You can configure
Math worksheets to provide free environments for logical routines and
mathematical calculations required by the project.
• Script contains the Startup Script and other Script Groups.
• Scheduler contains the Scheduler worksheets used to configure events
using defined mathematical expressions, which are executed according to
time, date, or other monitored event.
• Database/ERP contains the Database worksheets that communicate
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 establish
communication with another device or software using available protocols.
The folders on the Comm tab are described on the following pages.
• Drivers contains the Driver worksheets used to configure a communication
interface (or interfaces) between the project and remote equipment (such
as a PLC or transmitters).
A communication driver is a .DLL file that contains specific information
about the remote equipment and implements the communication
protocol.
• OPC DA 2.05 contains the OPC worksheets used to configure
communications between your project (which acts as an OPC client) and
any other device that implements the classic OPC standard.
• OPC UA contains the OPC UA worksheets that are used to connect to OPC
Servers via the new OPC Unified Architecture protocol.
• OPC .Net contains the OPC .Net worksheets that are used to connect to OPC
Servers via the new OPC .NET 3.0 protocol.
• OPC XML/DA contains the OPC XML/DA worksheets that are used to
connect to OPC Servers via the new OPC XML-DA protocol.
• TCP/IP contains the TCP/IP worksheets used to configure TCP/IP Client
interfaces for other IWS stations.
IWS TCP/IP Client and Server modules enable two or more projects to
keep their databases synchronized using the TCP/IP protocol.
• DDE contains the DDE worksheets used to configure a DDE Client for a
DDE Server application (such as Microsoft Excel or any other Windows
program that supports this interface).
DDE (Dynamic Data Exchange) is a protocol that enables dynamic data
exchange between Windows applications. A DDE conversation is an
interaction between server and client programs. IWS provides interfaces
that run as clients or as servers.
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.
Screen/Worksheet Editor
Tags are a core component of any IWS project. Simply put, tags are variables
used by IWS 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. IWS includes a real-time database
manager that provides a number of sophisticated functions such as time-
stamping of any value change, checking tag values against runtime minimum
and maximum values, comparing tag values to alarming limits, and so on. A
IWS tag has both a value and various properties that can be accessed, some
at development and others only at runtime.
All tags are organized into one of the following categories, which are
represented by folders on the Global tab of the Project Explorer:
• Project Tags are tags that you create during project development. Places
where project tags are used include:
• Screen tags
• Tags that read from/write to field equipment
• Control tags
• Auxiliary tags used to perform mathematical calculations
• Shared Database tags are created in a PC-based control program and
then imported into IWS's tags database.
For example you might create tags in SteepleChase and import them into
IWS so IWS can read/write data from a SteepleChase PC-based control
product.
You cannot modify shared tags within IWS — you must modify the tags in
the original PC-based control program, and then re-import them into the
Tags database.
• System Tags are predefined tags with predetermined functions that are
used for IWS supervisory tasks. For example,
• Date tags hold the current date in string format
• Time tags hold the current time in string format
Most system tags are read-only, which means you cannot add, edit, or
remove 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 above
figure shows a partial list of system tags.
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.
[Options]
BooleanTrueAboveZero=value
• When you write any numeric value less than or equal to 0 (i.e., ≤0) to a
Boolean tag, the tag assumes a value of 0 (false).
• When you write any numeric value greater than 0 (i.e., >0) to a Boolean
tag, the tag assumes a value of 1 (true).
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]
Caution: 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].
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 (using 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 "+".
ArrayTagName[NumValue1+NumValue2]
Using array tags in any IWS 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
• temperature3: high temperature on tank 3
• temperature4: high temperature on tank 4
Using array tags simplifies this task, as follows:
• temperature[j]: high temperature on tank {j}
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.
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.
You can use array tags to:
• Simplify configurations
• Enable multiplexing in screens, recipes, and communication interfaces
• Save development time during tag declaration
ArrayTagName[ArrayIndex]
• For a complex array tag (where the array index is an expression consisting
of a tag and an arithmetic operation), type:
ArrayTagName[ArrayIndex+c]
Where:
• ArrayTagName is the tag name;
• [ArrayIndex] is the unique index (fixed value or another tag);
• + is an arithmetic operation; and
• 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").
When you create an n-position array tag, IWS 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 IWS 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], IWS regards a[second
as the tag and considers it invalid because IWS 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 configuration method is:
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.
To refer to a class-type tag, you can declare a string-type tag that points to a
class tag. For example:
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 class-type that points to a class
member.
For example:
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.
Indirect Tags
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.
• 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.
• 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 Tank.Level member.
• 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.
tag_name->property_name
Class.Member-
>MemberName
Example: Tank.Lvl-
>MemberName = Lvl
Tag[Index]->Index
Example: Tag[1]-
>Index = 1
Note:
Note: The tags stored in the System Tags folder and in the Shared
Tags folder (if any) are not affected by this command.
For this example, select Windows Embedded Standard. This is a tag and
feature-limited product type that can be safely deployed on Windows
Embedded devices.
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.
3. Click OK.
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.
• 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.
For this tutorial, select Server.
Tip: You can sort the data in the Project Tags datasheet or insert/
remove additional columns by right-clicking on it and then choosing
the applicable option from the pop-up menu.
4. On the Graphics tab of the ribbon, in the Screen group, click Background Color.
A standard color picker is displayed.
5. In the color picker, select a light gray color.
Color picker
• The Object Properties dialog 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:
• 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
is on the top, the keyboard commands (Ctrl+C, Ctrl+V, Ctrl+X, or Del)
are sent directly to the objects.
• 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.
4. Click Fonts to open Font dialog, and then specify the font settings.
For this tutorial…
• Font is Arial
• Font style is Regular
• Size is 20
• Color is Blue
4. In the Caption box, type the following text: Click here to open the
synoptic screen.
You can specify a screen that you have not yet created.
This figure shows how your screen should look after you've created the date
and time objects.
The symbol will be displayed in the symbol viewer to the right of the menu
tree.
You may select any tank you like; they all function basically the same
way.
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.
This figure shows how your screen should look after you've created the tank
object.
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.
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.
9. Click the Application button at the top-left of the development application,
and then click Save on the Application menu.
This figure shows how your screen should look after you've created the level
slider object.
5. In the Project Explorer, right-click the MODBU folder, and then click Settings
on the shortcut menu.
register_type:initial_offset
0X Coil Status
1X Input Status
3X Input Register
4X Holding Register
ID Slave ID Number
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.
Startup dialog
c) Select Automatic, and then click OK.
d) Click OK to close the Execution Tasks dialog.
3. Save and close all open screens and worksheets.
4. Click the Application button at the top-left of the development application,
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).
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 IWS project and
exchanges data with the clients) do not need to be the same computer.
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.