September 2000
Monitor Pro v7 Release Notes
Table of Contents:
I. INTRODUCTION ____________________________________________________ 3
II. NEW FEATURES ___________________________________________________ 4
Client/Server Environment ___________________________________________________ 4
NT Service _________________________________________________________________ 4
Configuration Explorer ______________________________________________________ 4
New Development Tools ______________________________________________________ 4
Client Builder ______________________________________________________________ 4
License Manager ____________________________________________________________ 5
III. INSTALLATION ____________________________________________________ 6
Minimum Hardware and Software Requirements ________________________________ 6
Detailed Hardware Recommendations __________________________________________ 6
Monitor Pro v7 CDs _________________________________________________________ 7



Client and Server _____________________________________________________________ 7
Device Interfaces and Value-Added Products * ______________________________________ 7
Microsoft SQL Server 7.0 _______________________________________________________ 7
Microsoft Subsystems ________________________________________________________ 7
Installation Procedure _______________________________________________________ 8
Anti-Virus Software _________________________________________________________ 8
SQL Server 7.0 _____________________________________________________________ 8
Memory Size Setup __________________________________________________________ 8
Starter Application __________________________________________________________ 8
Installing Monitor Pro v7 to Run on a Stand-alone Computer ______________________ 9
Monitor Pro v2.1 and Monitor Pro v7 on the Same Computer ______________________ 9
Installing OPC Factory Server ________________________________________________ 9
License Authorization ________________________________________________________ 9
Korean Windows NT _______________________________________________________ 10
IV. CONVERTING EXISTING APPLICATIONS ___________________________ 11
ECSConvert -D option ______________________________________________________ 11
Conversion of PowerVB Code ________________________________________________ 11
V. DOCUMENTATION_________________________________________________ 12
Corrections________________________________________________________________ 12
Installation Guide, English, page 109 (item 14) – Client Licenses ___________________________ 12
Updates ___________________________________________________________________ 12
VI. SUPPORTED LAYERED PRODUCTS _________________________________ 13
VII. MISCELLANEOUS ISSUES ________________________________________ 15
DB IV Files ________________________________________________________________ 15
Increasing Relational Database Performance ___________________________________ 15
Unreferenced Tags _________________________________________________________ 15
Using Multiple Languages with Monitor Pro ____________________________________ 15
Using Multiple Languages with Client Builder __________________________________ 15
Setting up Loopback for PCs not connected to network ___________________________ 16
Uninstalling Monitor Pro ____________________________________________________ 17
New Features in Client Builder _______________________________________________ 17
Viewing Math and Logic Error Messages ______________________________________ 17
Trending __________________________________________________________________ 17
Alarm Control ____________________________________________________________ 177
OPC Server Startup _______________________________________________________ 178
Device Interfaces ___________________________________________________________ 18
RSLinx _______________________________________________________________________
Sinec_H1 EDI-S5 _______________________________________________________________
Siemens Sinec H1 _______________________________________________________________
A-Line Devices _________________________________________________________________
SFB Devices ___________________________________________________________________
188
188
188
189
189
Legacy Graphics - PowerVB ________________________________________________ 199
VIII. Known Software Problems __________________________________________ 20
2
I. INTRODUCTION
Schneider Automation is pleased to announce the release of Monitor Pro v7, the latest version of its multi-user,
real-time supervisory control and data acquisition software product. Schneider Automation has been offering a
SCADA solution and the Monitor family of products for over 10 years, providing its customers with the latest in
technology to meet the ever changing demand in the automation arena.
To continue providing cutting edge technology to its customers, Schneider Automation has formed a long term
partnership with USDATA Corporation of Richardson Texas, USA in providing the Monitor Pro offer, the core of
which is based on the FactoryLink product. This partnership offers a proven SCADA solution with a team of
dedicated engineers focused solely on automation technologies associated with supervisory control and data
acquisition applications.
As you work with and use the product you will see references to the core FactoryLink product in both the
documentation and help files. This is not to be considered an error or misprint; Monitor Pro is distinctly different
from the core FactoryLink product in the Add-On Modules offered.
These Add-On modules provide a tight integration with the Schneider Electric family of controllers as well as
provide added benefit to our users when configuring applications.
With Monitor Pro v7 the following Add-On modules are provided with the base system:
•
DOCAuto
•
DiagViewer
•
Communication Set-up Starter Application
•
Multiplexing Actions
•
Symbol Database Linker
•
Trend Charts
•
Communication Drivers to all Schneider Electric devices (including OFS)
If you have any questions on the use or application of this product, please contact your local sales
representative or the Schneider Automation Technical Support Team.
North Andover, MA USA
Telephone: 00+(1) 800-468-5342, option 1
Fax: 00+ (1) 978-975-9301
Carros, France
Telephone: +33 (0)4 92 08 82 33
Fax: +33 (0)4 92 08 82 67
Also, please refer to our web site for additional information:
www.schneiderautomation.com or www.modicon.com
The Monitor Pro v7 Release Notes contain the information on the new features of Monitor Pro v7 and some
late-breaking news.
3
II. NEW FEATURES
Several new features are included in this release.
Client/Server Environment
Monitor Pro v7 provides a more standard client/server approach to development and runtime environments. The
Monitor Pro v7 installation procedure reflects this by prompting for both server and client options. While both types
of options can be installed on the same computer, they can also be installed on different computers on an enterprise
network. The server installation installs what would have previously been referred to as the runtime components
(such as executable files and supporting utilities to run applications). The Client Installation(s) install the
configuration and visualization tools (including the legacy graphics, Configuration Manager, and WebClient).
NT Service
Monitor Pro v7 provides support to run server applications as an NT Service. This allows a Monitor Pro
Application to be configured to start automatically when the server is booted even when no user has logged in. It
also allows an Application to be started and stopped from a remote Configuration Explorer without a user being
logged into the server.
Configuration Explorer
Monitor Pro v7 provides a new configuration tool that replaces the Configuration Manager. The Configuration
Explorer utilizes Microsoft DNA component architecture, has the look and feel of a standard Microsoft product, and
functions as a client so that it can be used to configure and run applications on any Monitor Pro server on the
Enterprise network. It also supports simultaneous application development by multiple developers.
New Development Tools
The Generate Records tool provides the ability to create large numbers of records in a configuration table by
defining record-generation rules in a user-friendly editor.
The Application Objects capability allows developers to assemble multiple types of configuration information (such
as PLC read, scaling, alarming, and logging) in a single hierarchical object, such as a pump object or a switch object
that represents a real-world object. These objects can then be used to instantiate one or many pumps or switches in
an application, with all the associated information automatically configured.
Both these tools support multiple data sources, such as spreadsheets or text files, to provide specific data for the
instantiated configuration objects.
Client Builder
Monitor Pro v7 provides a new graphics product with a standard Microsoft look and feel that utilizes ActiveX
technology and is a true client implementation (actually interfaces to the Monitor Pro server as an OPC client of the
Monitor Pro OPC Server). This product is for both design time and run time.
In addition to the same basic graphics-animation capabilities as supported by the legacy graphics product, Client
Builder includes ActiveX controls for viewing alarm and trend data and for browsing database information. Client
Builder can host third-party ActiveX controls, including the WebClient control.
For information about upgrading existing applications to use Client Builder, please refer to the Conversion Guide in
the Schneider Automation\Monitor Pro\Documentation\{lang} directory.
4
License Manager
In addition to the server-side licensing in pre-7.0 versions, Monitor Pro v7 introduces a License Manager on the
server to manage the run-time instances and/or connections of the following five client products:





Configuration Explorer
Client Builder
WebClient
Graph
Third-party OPC Clients
For more information, please refer to Chapter 7, "License Manager," of the Installation Guide.
5
III. INSTALLATION
Minimum Hardware and Software Requirements
Minimum hardware and software requirements for Monitor Pro v7 are published in the manuals. While the software
will run on these minimum requirements, they may not be adequate for satisfactory performance on some systems;
especially larger, complex systems. Since it is impossible to define the exact requirements for each system due to
the flexibility and scalability of Monitor Pro and other layered software involved, we have prepared additional
guidelines to help you select the “best estimate” of system requirements. Your exact requirements may be
somewhat less or more than what is stated here.
Hardware Requirements:
 CPU: Pentium 233
 CD-ROM drive for installation
 128 MB RAM
 XVGA Monitor and graphics processor (1024 X 768, with at least 65K colors)
 Keyboard and Windows NT-compatible mouse
 Hard drive space: 1.0 GB or larger for a Monitor Pro Client; 2GB for a Monitor Pro Server. More space will
be required if you plan to install SQL Server or to keep a large amount of historical data.
If you are planning to install SQL Server on the same machine as the Monitor Pro Server, then you should consider
using a dual processor Pentium and increasing the memory by at least 64 MB RAM.
For additional information on SQL Server 7.0 requirements, please check the Microsoft website at:
http://www.microsoft.com/SQL/productinfo/datasheet.htm
Software Requirements:
 Microsoft NT 4.0, Service Pack 4 or higher, or
 Windows 2000
 Internet Explorer 4.01
Follow these links to install the required versions of service packs:
 Microsoft Windows NT: http://www.microsoft.com/NTServer/all/downloads.asp
 Internet Explorer (latest version): http://www.microsoft.com/windows/ie/default.htm. For earlier versions, click
the « download » link on that page.
 MDAC: http://www.microsoft.com/data/download_250rtm.htm
 Active Directory Services (ADS) : http://www.microsoft.com/ntworkstation/downloads/Other/ADSI25.asp
Note: These are minimum requirements and may not be appropriate for your particular application. Please contact
the Schneider Automation Technical Support Team to discuss recommended hardware and software for your specific
needs.
Detailed Hardware Recommendations
Hardware Requirements:
System Type: Micro Server (64 I/O limit with up to 1,024 User-Defined Tags), 1 client typical.
CPU: 300 MHz Pentium or faster.
Memory: 128 MB
6
Notes: Add an extra 2MB RAM for each Client Builder client used. Add an extra 10 MB RAM for each
FactoryLink ECS client used.
System Type: Lite Server (256 I/O limit with up to 4096 User-Defined Tags), 1 client typical.
CPU: 400 MHz Pentium or faster.
Memory: 128 MB
Notes: Add an extra 2MB RAM for each Client Builder client used. Add an extra 10 MB RAM for each
FactoryLink ECS client used.
System Type: Midsize Server (1024 I/O limit with up to 16,384 User-Defined Tags), 5 clients typical.
CPU: 600 MHz Pentium or faster.
Memory: 192 MB
Notes: Add an extra 2MB RAM for each Client Builder client used. Add an extra 10 MB RAM for each
FactoryLink ECS client used.
System Type: Enterprise Server (Unlimited I/O and User-Defined Tags), 10 or more clients typical.
CPU: 750 MHz Pentium or faster for up to 5 clients; dual for 5 to 15 clients, quad for 15 or more clients.
Memory: 256 MB up to 15 clients; 320 MB for more clients.
Notes: Add an extra 2MB RAM for each Client Builder client used. Add an extra 10 MB RAM for each
FactoryLink ECS client used. More than one server is recommended if more than 40 clients are needed.
System Type: Client used for development.
CPU: 500 MHz Pentium or faster.
Memory: 192 MB
System Type: Client used for operator interface only.
CPU: 400 MHz Pentium or faster.
Memory: 128 MB
Monitor Pro v7 CDs
The Monitor Pro v7 package contains three CDs:
 Client and Server
 Device Interfaces and Value-Added Products *
 Microsoft SQL Server 7.0
* The CD contains over 40 drivers that work with Monitor Pro v7, which are purchased as options separately from
the Monitor Pro standard package. It also contains the documentation and the entire suite of value-added products.
For a list of the Monitor Pro drivers, refer to Chapter 4, "Installing Device Interfaces," in the Monitor Pro
Installation Guide. For information on value-added products, see the “Value-Added Products” document in the
Program Files\Schneider Automation\Monitor Pro\Documentation\{lang} directory.
Microsoft Subsystems
The installation process updates these Microsoft subsystems:
1.
2.
3.
Microsoft Active Directory Services
Microsoft Data Access Component, version 2.1, Service Pack 2
Microsoft Visual Studio Component DLLs
7
Installation Procedure
For installation help, please refer to the Installation Guide in your Monitor Pro package.
Note: The Monitor Pro v7 installer does not provide the capability to add and remove single components of the
product. To add a component, it is necessary to uninstall the product and reinstall with the new component.
Note: Installs on Terminal Server must be done in Terminal Server's "Install Mode." Otherwise, the program will
only be available to the user who installed it. Because of this, the AutoRun feature will not work for the installation
of Monitor Pro on the Terminal Server. You need to go to the Control Panel and use Add/Remove to run the
installation program. If AutoRun is enabled, then cancel it and use Add/Remove to run the installation programs
after each reboot.
Anti-Virus Software
Some anti-virus software can interfere with the operation of install programs based on InstallShield. If you
experience a decompression or unpacking error in the install process, it is recommended that you disable virus
checking and re-run the installation.
SQL Server 7.0
If you will use SQL Server 7.0 with the Starter Application, install it before installing Monitor Pro. Both SQL
Server 7.0 and its Service Pack 2 are supplied on the SQL Server 7.0 CD. Both must be installed for proper
operation.
For more information, please refer to the Installation Guide.
Note: When you install the SQL Server, you can install either the Desktop or Standard version. If you choose to
install the Enterprise version, a license key must be obtained from Microsoft.
Memory Size Setup
After you have installed Microsoft SQL Server 7.0, you need to set up a maximum memory limit on the SQL Server.
This prevents the SQL Server from consuming all the memory available to it and ensures the operation and speed of
Monitor Pro tasks.
Perform the following steps to set up the memory size for the SQL Server:
1.
2.
3.
4.
5.
6.
7.
8.
9.
From the Windows Start menu, select Programs>Microsoft SQL Server 7.0.
Select Enterprise Manager and the Console Root/Microsoft SQL Servers window appears.
From the Console Root folder, select SQL Server Group>Host Name (Windows NT).
Right-click the Host Name (Windows NT) and select Properties from the pop-up menu.
In the SQL Server Properties dialog box, click the Memory tab.
In the Memory dialog box, change the default setting "Dynamically configure" to "Use a fixed
memory (MB)."
Use the lever to set the memory size in the range of 40 to 80 MB, as recommended by Microsoft,
depending on your system's RAM size and virtual memory size.
Click Apply. Then click OK.
Close the Console Root/Microsoft SQL Servers window.
Starter Application
8
The Starter Application is included in the installation program as an optional server component. For information,
please refer to Chapter 2, "Starter Application," in Concepts Manual.
Installing Monitor Pro v7 to Run on a Stand-alone Computer
Monitor Pro v7 is designed to run in a distributed environment. It requires certain services that are supplied by the
Windows NT or Windows 2000 networking layer. In order to run Monitor Pro v7 on a stand-alone computer, it is
necessary to install the TCP/IP network protocol. If the computer does not have a network card, it is also necessary
to install the Microsoft Loopback Adapter. The loopback adapter is software from Microsoft that simulates a
network card. It allows network protocols to be installed and bound to the loopback adapter as if it were a real
network interface card.
To add a loopback adapter, it is necessary to have the Windows (NT or 2000) installation media. Open the control
panel (Start / Settings / Control Panel) and open the Network control. Click on the Adapters tab and click the button
to "Add" an adapter. A list of Network Adapters will be displayed. Select "MS Loopback Adapter" and click OK.
In “MS Loopback Adapter Card Setup”, take the default settings.
To add the TCP/IP protocol, open the control panel and open the Network control. Click on the Protocols tab, and
click the “Add…” button. A list of network protocols will be displayed; select “TCP/IP Protocol” and click OK.
Once the TCP/IP protocol has been installed, use the “Bindings” tab of the Network control panel app to make sure
that TCP/IP is bound to the network adapter (either the loopback adapter or the actual network adapter).
The TCP/IP protocol will provide the network services that are required to run Monitor Pro v7 on a stand-alone
computer.
Monitor Pro v2.1 and Monitor Pro v7 on the Same Computer
Monitor Pro v7 uses some of the same environment settings as Monitor Pro v2.1. When Monitor Pro v7 is installed,
the Monitor Pro v2.1 settings will be overwritten or removed. In the BIN directory of the Monitor Pro v2.1
installation, there is a batch file that contains the environment settings that are required. This file is
FLSETUP.BAT; it can be run in a command window to change the environment settings (for that session only), or
the settings can be manually entered in the Environment tab of the System control panel applet. Do not alter the
Monitor Pro v7 environment settings, as Monitor Pro v7 will not run without these settings. There is no way to
automatically restore them if they are altered.
Note, however, that Monitor Pro v7 uses system environment settings, while Monitor Pro v2.1 uses user
environment settings. Therefore, the Monitor Pro v2.1 settings can be added on a per-user basis, and users that have
Monitor Pro v2.1 settings will run 2.1, while users that do not have these settings will run Monitor Pro v7. To move
a user back to Monitor Pro v7, just remove the Monitor Pro v2.1 user settings.
Installing OPC Factory Server
As a part of the Monitor Pro v7 installation process, it is possible to install the Schneider Automation OPC Factory
Server (OFS). This installs two components, the OPC Factory Server itself, and the OPC Factory Server
Configurator. These install programs are launched at the same time, and can appear on the screen at very nearly the
same time. It is recommended that only one of these be allowed to proceed at a time. Wait until the first of these is
complete before proceeding with the other install.
License Authorization
Once an authorization code has been obtained, using the registration code displayed during the installation process,
the Monitor Pro v7 license must be authorized. This is done through the Add/Remove Programs applet in the
9
Control Panel. Run this applet, and scroll down to “Schneider Automation Monitor Pro v7.” Select this entry and
click the Add/Remove button (or just double-click the entry) to bring up the Maintenance Wizard. Make sure that
the Authorize License radio button is selected, and click the Next button. Follow the directions in the wizard to
authorize your license. The process of obtaining an authorization code and authorizing your license is described in
greater detail in the Installation Guide (available in the Documentation folder of the Client and Server installation
CD).
Once the license has been authorized, it is necessary to restart the Monitor Pro License Manager. This can be done
by rebooting the computer, or by using the Services applet in the Control Panel. To use the Services applet, click
Start/Settings/Control Panel, and double-click the icon labeled “Services.” In the resulting dialog, select the
“Monitor Pro License Manager.” It should show as “Started” and “Automatic.” Click on the Stop button at the
right of the dialog. Respond “Yes” to the resulting question (you do really want to stop the service). Wait until the
Monitor Pro License Manager has stopped (the word “Started” disappears). Then click the Start button. Wait for
the word “Started” to appear, then click the Close button to terminate the dialog. The authorized license is now
fully available to all Monitor Pro components.
Korean Windows NT
The Client Builder clipart contains files that have a degree symbol in the filename. This is not a legal character for
Korean Windows NT filenames. Installing these files will cause the installation process to fail. In the Component
Selection dialog of the installation, highlight Monitor Pro Client in the left pane, and scroll the right pane down to
Client Builder Clipart. Uncheck the box. Contact the Schneider Automation Technical Support Team for
replacement clipart files.
10
IV. CONVERTING EXISTING APPLICATIONS
Before trying to convert an application, it is strongly recommended that you make a save first!
Monitor Pro v7 includes all the legacy components of the 2.1 release, and existing applications can be converted and
run without modification in 7.0. Application conversion, while always a requirement of previous upgrades, is more
significant for this upgrade, in order to support the new features in the release. Existing applications must be
converted using the FLCONV utility before any attempt to access them with Monitor Pro v7. Protection has been
added to prevent the use of Monitor Pro v7 development and run-time modes with previous application versions.
Once converted to Monitor Pro v7 compatibility, applications will NOT be accessible using previous Monitor
Pro versions.
For information on converting graphics, Database Browser, Alarm, and Trend, please refer to the Conversion Guide.
ECSConvert -D option
There is a known problem with documenting PowerVB code with the released version of ECSConvert. Not all of
the code in an ECS graphics file is correctly exported. Updates to the conversion utilities will be distributed to our
Tier One Partners, as they become available.
As a workaround, to document the PowerVB code in a drawing, use the Appedit option File/Document PowerVB.
This will leave the PowerVB documentation in %FLAPP%\user\drw\[drawingname].SRC.
Conversion of PowerVB Code
Existing PowerVB code is not converted by the current version of ECSConvert. Due to the difficulty of
implementing a PowerVB-to-VBScript translator, PowerVB code is optionally saved to a text file. Conversion is
left to the application implementer.
11
V. DOCUMENTATION
Documentation is installed in the Schneider Automation\Monitor Pro\Documentation directory, in three languages that
can be accessed from the De, En, and Fr subdirectories. All documents have been translated to French and German
for this release. The documentation is in PDF format, which you can view by using Adobe Acrobat Reader 4.0
(provided on the first Monitor Pro CD).
The Application Objects API Reference Manual is available with this release. It documents the functionality of each
object in the Application Objects hierarchy as well as the way in which they fit together. This manual also refers to
an object or subsystem provided with Monitor Pro v7 when it is relevant to Application Objects.
Corrections
Installation Guide, English, page 109 (item 14) – Client Licenses
This item indicates that you should enter 50 or more for the number of Client Access Licenses. This is incorrect.
You should enter the number of purchased "Monitor Pro v7 Client Seats" often referred to as CALs.
Updates
The complete French and German translations of the Device Interface Guide and Schneider Add-Ons User Guide
were not complete at the time the CDs were created. Please refer to the web site described in the above Section I
INTRODUCTION for Internet downloads of these fully translated manuals.
12
VI. SUPPORTED LAYERED PRODUCTS
COMPILER
Product: CML/PAK/EDIPAK
Vendor:
Microsoft
Product:
Microsoft Visual C++ 6.0
Platform:
WIN2000 and Windows NT 4.0
DBMS
Product: ODBC Historian
Vendor:
IBM
Product:
DB2 v.5
Platform:
WIN2000 and Windows NT 4.0
Additional Info: IBM DB2 ODBC Driver version 5 1
Product: ODBC Historian
Vendor:
Merant
Product:
DataDirect ODBC Driver Pack Version 3.50
Platform:
WIN2000 and Windows NT 4.0
Additional Info: Verified support: Oracle 7, Oracle 8, Sybase System 11.5.1 2
Product: ODBC Historian
Vendor:
Microsoft
Product:
Microsoft Access2000
Platform:
WIN2000 and Windows NT 4.0
Additional Info: Use Microsoft ODBC Driver ver 4.00.4202.00, which is installed by MDAC 2.1
Service Pack 2
Product: ODBC Historian
Vendor:
Microsoft
Product:
Microsoft SQL Server 7.0 SP2
Platform:
WIN2000 and Windows NT 4.0
Additional Info: Microsoft SQL Server Client Driver version 3.70.06.90, which is installed by
MDAC 2.1 Service Pack 2
Product: Oracle Historian
Vendor:
Oracle
Product:
Oracle 7.x and 8.x
Platform:
WIN2000 and Windows NT 4.0
Additional Info: Oracle Version Verified: 7.3.4 SQL NET version verified: 2.3.4 (Use
OR7_HIST), 8.1.5 OracleNet8 (Use OR8_HIST)
Product: Sybase Historian
Vendor:
Sybase
Product:
Sybase System 11 ODBC Driver
Platform:
WIN2000 and Windows NT 4.0
Additional Info: Sybase System 11.5.1 & 11.9.2 2
LAN
Product: FLLAN, POWERNET, WEBCLIENT
Vendor:
Microsoft
Product:
LAN
Platform:
WIN2000 and Windows NT 4.0
Additional Info: WINSOCK Compatible TCP/IP supplied by O/S Vendor OS
13
Operating System
Product: Monitor Pro v7
Vendor:
Microsoft
Product:
Microsoft Windows NT 4.0
Platform:
Windows NT 4.0
Additional Info: Verified with NT4.0 Service Pack 4, 5, and 6 on NTFS
Product: Monitor Pro v7
Vendor:
Microsoft
Product:
Microsoft Windows 2000
Platform:
Microsoft Windows 2000
Additional Info: Verified with Windows 2000
1
Using NT box with MDAC 2.1, DB/2 version 5 client software and its DB2 ODBC driver: Trigger a Database
Logger insert to a non-existent table for which a valid schema exists. The table is created, however, the inserts which
follows fail with a describe error. (Create and insert together fails). If dblog is shutdown and restarted, and then
Database Logger inserts to the already created table are triggered, they go through fine. Workaround is to try insert
again or restart ODBC Historian. (Create and insert separately succeeds). PowerSQL does not fetch back values
when using Dynamic SQL Statements. PowerSQL 10000-row array insert into DB/2 table fails. Stored Procedure
calls from PowerSQL for these database/driver combinations have not been tested. Contact the Schneider
Automation Technical Support Team for updated information regarding any new testing results.
2
Stored Procedure calls from PowerSQL for these databases and drivers have been tested with INPUT parameters
only. Contact the Schneider Automation Technical Support Team for updated information regarding any new
testing results.
14
VII. MISCELLANEOUS ISSUES
This section lists some other issues about this release:
DB IV Files
In Monitor Pro v7, to work with the new Trend control and Database Browser control, files created by the DB4
Historian must have a DBF extension instead of the usual CDB extension. For newly created files, this requires the
use of the -dbase program argument for the DB4_HIST in the System Configuration table.
Because of a problem with the Microsoft dBase ODBC driver and multi-user access to DB IV files, the FoxPro
ODBC driver must be used instead.
Increasing Relational Database Performance
If you have a table greater than 10 MB, we suggest that you use SQL Server, Sybase, Oracle, or a similar
high-performance relational database, rather than Access or dBase IV. Microsoft Access and dBase IV are both
good for small databases but are not optimized for larger databases.
Unreferenced Tags
Unreferenced tags are tags that have been created, but have not been associated with any task. Such tags are not
deleted, but they are also not allocated at run time. In other words, unreferenced tags are usable during
configuration, but not while the system is running. To avoid this problem, always create tags in reference to a
specific task.
Using Multiple Languages with Monitor Pro
This release of Monitor Pro v7 supports English, French, and German. To change the Monitor Pro language, use
the utility FLSetLng.EXE. This utility is in the FactoryLink\Bin directory in your Monitor Pro installation. Note
that the utility cannot change the language if any Monitor Pro task (apart from the NT services for licensing and
autostart) is running. Changing the Monitor Pro language does not affect the language of the Client Builder user
interface, which utilizes a separate language setting, due to the fact that Client Builder Mimic files contain
language-specific data.
Using Multiple Languages with Client Builder
Client Builder has the capability to present a multilingual user interface. It can support two languages at a time.
The initial languages are configured based upon the language chosen for the install process. This release delivers
support for English, French, German, and Spanish (Note that Spanish is available only in Client Builder, not in the
remainder of the Monitor Pro product). To change the Client Builder language, use the Tools/Language submenu.
The two active languages are chosen in the MUI.INI file, in the Client Builder\Program directory of your Monitor
Pro installation. It is strongly recommended that you back up this file before editing it. The standard installation
only configures English, French, and German. If you chose to use Spanish in Client Builder, you must manually
edit the MUI.INI file. See the comments at the top of this file for information on how to configure this file.
The Client Builder language carries through to the project files created in the application. All text entities are
tagged with an identifier indicating if they are in language 1 or language 2 (the language selected at the time the item
was created). Note that changing the language settings in MUI.INI can result in contradictory language settings.
Also, changing the language setting in Client Builder can cause the text in a Mimic file to seem to disappear, since
there may be no text entities that correspond to the newly selected language. If you set out to create multilingual
Mimic files, it is also important to pay attention to text sizing issues.
15
Note that it is possible to run Client Builder in a language different from the remainder of the Monitor Pro
installation. This is discouraged, because it will result in the Client Builder user interface and Mimic text being in
one language, while text that comes from the Monitor Pro application will be in another language.
Setting up Loopback for PCs not connected to network
To avoid licensing error messages on computers not connected to or routinely disconnected from a network, use a
loopback adapter to ensure TCP/IP communication services are available and allow program licensing to use the
hard drive disk volume for identification.
If you have not already installed your software, disconnect your computer from the network, follow the procedure
given below to install a loopback adapter and install the software.
If you have already installed your software, disconnect your computer from the network, follow the procedure given
below to install a loopback adapter and re-license the software using the 'Add/Remove Software' dialog found in the
'Control Panel'.
Procedure to install a loopback adapter in Windows NT4.0:
1. Left Click 'Start', 'Settings' and then 'Control Panel' to open the 'Control Panel' window
2. Double Click on the 'Network' icon to view the 'Network' property dialog box
3. Left Click on the 'Adapters' tab.
4. Click on the 'Add' button to view the 'Select Network Adapter' dialog
5. Scroll down the list to select 'MS Loopback Adapter' and Left Click on 'OK' button
6. Install might require the 'Win NT Workstation CD' to copy the necessary files
7. Left Click 'OK' to accept the default value on the 'MS Loopback Adapter Card Setup' dialog
8. Left Click the 'Close' button to close the dialog
9. The necessary bindings are configured automatically
10. A 'Microsoft TCP/IP Properties' dialog will appear
11. From the 'Adapter' field, select 'MS Loopback Adapter'
12. Specify a suitable 'IP Address' (192.1.1.1) and 'Subnet Mask' (255.255.255.0)
13. Left Click 'OK'
14. Reboot the computer
Procedure to install a loopback adapter in Windows 2000 (NT5.0):
1. Left Click 'Start', 'Settings' and then 'Control Panel' to open the 'Control Panel' window
2. Double Click on 'Add/Remove Hardware' to start the 'Add/Remove Hardware Wizard'
3. Continue with a Left Click the 'Next' button
4. After a moment, the 'Choose Hardware Device' panel will appear
5. Left Click the top line in the 'Devices' list labeled 'Add a new device'
6. Left Click the 'Next' button
7. Left Click the 'No, I want to select the hardware from a list' radio button
8. Left Click the 'Next' button to continue
9. At the 'Hardware Type' panel, navigate to and Left Click 'Network adapters'
10. Left Click the 'Next' button to continue
11. At the 'Select Network Adapter' panel, navigate to and Left Click 'Microsoft'
12. Left Click the 'Next' button to continue
13. At the 'Start Hardware Installation' panel, Left Click the 'Next' button to continue
14.After the necessary files are copied, Left Click 'Finish' to complete the addition
Uninstalling Monitor Pro
All processes related to Monitor Pro should be shutdown before initiating uninstall. This also includes shutting
down any Monitor Pro server or client applications that are running locally. In some instances, there might be
16
certain processes that might still be running after the application is shutdown. Uninstalling Monitor Pro while such
processes are running might result in errors during uninstall. To avoid this, it is recommended to “Log Off” and
“Log In” before initiating uninstall so that such processes are removed from memory.
New Features in Client Builder
Client Builder has been upgraded since the initial (English) release of Monitor Pro v7. The Client Builder
documentation applies to the initial release. The new features that have added since the documentation was written
are Path Animations and Server Filtering in the Variable Browser. In addition to these new features, Send
Animations have been enhanced for bit, register, and text types.
Path Animation allows a shape to be moved along a path. Eligible paths are lines, polylines, polygons, and Bézier
(poly-Bézier) curves. This feature is accessible through the Animate/Position submenu. The animation is set up in
a manner similar to other position animations, and a specific object is selected as the path.
When working with OPC Servers that support tag filtering in the server itself, it is possible to use Server Filtering in
the Variable Browser. This feature utilizes the server filter capabilities defined in the OPC specification, and can
significantly improve the performance of browsing for tags. The tags displayed can be filtered by type and name.
The enhancements to the Send Animation for bit, register, and text types enable constant values or tag values to be
sent by the animations. In the Animate/Send/Bit dialog, the “Variable” button allows a constant value to be typed or
a tag to be selected. In the Animate/Send/Register dialog and the Animate/Send/Text dialog, the “Default” button
offers the same capability. See the Client Builder manual for a more detailed explanation of animations in general,
and Send animations in particular.
Viewing Math and Logic Error Messages
Before attempting to execute a Math and Logic procedure, it is recommended that you first verify that there are no
errors. This is done manually by using the validation [] button or automatically when you are saving a procedure
file. When there is an error in the file, a red bookmark  will appear on the left side of Math and Logic.
Right-click on the error line and select "Error Help" from the bottom of the pop-up menu. You will see a message
describing the nature of the error.
Trending
On a client-only install, the Client Builder->Tools->Servers->ServerTypes settings must to be configured to point to
the server node. Refer to the Trend section of the Task Configuration Reference.
Alarm Control
Currently, the alarm control does not support the equivalent of the -f parameter to al_view. This issue is under
investigation and will be resolved in a future release of Monitor Pro.
OPC Server Startup
In previous versions, the Monitor Pro OPC Server would autostart when an OPC Client attempts to make a
connection. This is no longer the case. In Monitor Pro v7, the OPC Server must be added as a Monitor Pro task
and started when Monitor Pro is started.
17
Device Interfaces
RSLinx
Any Monitor Pro driver that uses RSLinx communication software will not work on Windows 2000 until Allen
Bradley's RSLinx software is updated. Versions 2.10 and earlier of RSLinx are not supported under Windows 2000.
Rockwell Software Support Library Technote ID R487 04/19/2000.
RSLinx Version 2.10.118.0 is supplied on the Device Interfaces and Value Added Products CD. To install these
files, refer to page 1-1 of the Rockwell Software Installation Guide and point to the CD directory Rslinx\Disk1 and
run the Setup file. Continue to follow the installation procedure for proper setup. There is also a required patch for
this version. This patch must be obtained from Rockwell.
Sinec_H1 EDI-S5
Prior to Monitor Pro v2.0, the Sinec_H1 driver experienced loss of communication after continuous operation for
duration ranging from a few hours to a few days. The typical symptom is that after having run and communicated
normally for varying periods of time the driver experiences a protocol timeout.
The driver then unsuccessfully attempts a disconnect/reconnect on the next access. After a protocol timeout all the
disconnect and reconnects also report a protocol timeout and the EDI task had to be stopped and restarted to
successfully reestablish communications.
The error has bee isolated to Microsoft’s DLC layer. Microsoft’s current position is that this is not a technology they
will actively support. Microsoft indicates the problem is a timing issue between the DLC code and the hardware. No
more specific information is available.
Schneider Automation has incorporated changes to the H1MP Driver that enable it to operate under normal CPU
loading conditions. However, under heavy CPU loads, the problem may occur and slow down the driver. Schneider
Automation has done everything possible within the constraints of the driver design to recover from severe
conditions. Occurrences of the problem should be rare. If they do occur, one solution is to upgrade to Schneider
Automation’s Sinec_H1 RAPD driver. There is currently no utility available to convert from the EDI Sinec H1MP
S5 driver to the RAPD H1 S5/S7 driver. The conversion must be done manually.
Siemens Sinec H1
The Siemens Sinec H1 Driver has been tested on Windows NT 4.0, but is not yet supported on Windows 2000. As of
June 19, 2000, the Siemens low-level driver (provided by Deltalink) is not available for the Windows 2000 operating
system.
A-Line Devices
The A-Line device interface tasks appear near the end of the device interface tasks in Configuration Explorer. They
include the tasks “Bitbus SEAB Configuration,” “BKOS DEF-Configuration PLC->PC,” and “BKOS
REF-Configuration PC->PLC.”
SFB Devices
The SFB device interface tasks normally appear near the end of the device interface tasks in Configuration Explorer.
They include these tasks: “Configuration V.24 KS-Interface,” “KS-V.24 Read(DEF)-Configuration (PLC->PC),”
and “KS-V.24 Write(REF)-Configuration (PC->PLC).”
18
Legacy Graphics - PowerVB
Consider the following warning when using the PowerVB NOT operator with digital tags.
For example,
dig_tag = NOT dig_tag
will always set dig_tag to 1.
The reason for this is that digital tags are not identical to PowerVB booleans. A PowerVB boolean's value is 0 for
false and -1 for true. Since NOT is a bit-wise operator, it converts all 0s in binary into all 1s or -1, and all 1s into 0s
or 0.
Monitor Pro digital tags take the value of 0 for false and 1 for true, not 0 and -1. So NOT operating on a 0 produces
-1. Writing any non-0 value to a digital tag produces a true value or 1. So NOT 0 becomes 1. However NOT 1
becomes a bit-wise value of -2, which, when written back to the digital tag, is still true or 1.
The internal behavior of digital tags cannot be changed, because in many applications the digital value is used in an
analog tag, and the application expects a 0 or 1, not 0 or -1.
A workaround for this is always to use an intermediate boolean value.
For example,
PVB_bool = NOT dig_tag
dig_tag = PVB_bool
Bear in mind that if PVB_bool is assigned to any analog value (PVB local or Monitor Pro tag), it will have the value
of 0 or -1, and if dig_tag is assigned to any analog value, it will have the value of 0 or 1.
19
VIII. KNOWN SOFTWARE PROBLEMS
Problems to be aware of:
SPR# 3838 Application Objects - Memory leak when instantiating Application Objects
Configuration Explorer has a memory leak when using Application Objects. Memory is not freed
until Configuration Explorer is shut down.
This problem is caused by a Microsoft ISAM driver bug, which is encountered when an Excel2000
spreadsheet has a reference error. We are working with Microsoft to fix this problem.
SPR# 3900 Certain fields do not show up in Config Explorer
When viewing some tables in Configuration Explorer, the tag type or tag description fields may
not appear, even though they are part of the table (when viewed through FLCM). The problem
occurs in both the grid view and the form view. This is an architectural problem with CfgPAK,
which could not be fixed for this release.
To view tag attributes not present in the view, highlight the tag, and open the tag editor by pressing
<ctrl>-T or by right-clicking on the tag name and selecting “Properties” in the resulting context
menu.
SPR# 4107 Uninstall on Windows 2000 hangs on uninstall of sub-components
On Windows 2000, when the master uninstall tries to uninstall its sub-components, the uninstall
process hangs.
The workaround is to manually uninstall all sub-components before uninstalling Monitor Pro.
The list of sub-components that must be manually uninstalled are:
 Schneider Automation Monitor Pro Add-Ons
 Schneider Automation Monitor Pro Device Interfaces
 OFSconf
 OPC Factory Server
SPR# 4163 INSTALL - Doesn't move existing Monitor Pro share
If you have existing Monitor Pro shares on your system, the Installation does not move them to the
new locations. Before installing Monitor Pro v7 remove all earlier Monitor Pro shares.
SPR# 4215 PSQL/Or8_hist: Do not convert 14-char stored proc string to SECTIME type value
SPR# 4218 PSQL/Odbchist: Do not convert 14-char stored proc string to SECTIME type value
There is a problem in any application in which PowerSQL calls an oracle8/MS SQL Server stored
procedure which does a select from a date-type column and converts the date to a 14-char string of
format yyyymmddhhmmss. Configure the receiving tag for this particular $OUTPUT column in
the PowerSQL Info panel to be longana. In such a case PowerSQL should be converting the
14-char string to a SECTIME type value. Instead, it gives an error message and no conversion is
done.
20
SPR# 4418 INSTALL: cancel install, keeps asking for language selection on reboot.
Canceling from an installation can cause the installation to continue after a reboot.
SPR# 4553 Install - Attempt to install on Korean Win NT.
This problem is caused by the use of the degree symbol (°) in certain file names in the Client
Builder clipart (Shared Libraries). This character is an illegal character for file names in Korean
Windows NT. In order to complete the installation, the Client Builder Clipart must be deselected
when installing Monitor Pro v7 (in the component selection dialog, uncheck this subcomponent of
the Monitor Pro Client component).
If you wish to use the clipart on Korean Windows NT, contact the Schneider Automation
Technical Support Team for an updated file set.
SPR# 4653 Annoying prompt when creating Application Objects with Tag Browser open.
Avoid having the Tag Browser open while creating multiple instances of Application Objects.
When a tag is created the Tag Browser gets notified and it sets a timer of five seconds, if a new tag
is created the timer will be reset. If an Application Object creates a tag and it takes more than five
seconds to create a second tag, then the prompt will display disrupting the Application Object,
after confirmation the process will continue.
This will be modified for a future release.
SPR# 4780 License Manager Does Not Allow Local Graph Without Admin Rights.
This problem prevents a user without administrative rights from running Config Explorer, Client
Builder, and other Monitor Pro components.
In order to run local graphics, Client Builder, Configuration Explorer, or Namespace Wizard on
Windows NT 4 or Windows 2000, a user must be a member of the Administrators group. Any
other user cannot unless they have the "logon as a service" right AND full control of the
HKEY_LOCAL_MACHINE\Software\Schneider Automation\ key in the registry.
The recommended procedure for allowing users to start Monitor Pro v7 follows:
1. Give the "logon as a service" right to the Users group on a local machine or in the Primary
Domain Controller (whichever applies).
Go to: Start, Programs, Administrative Tools, User Manager (For Domains).
Click Policies, User Rights.
Select Show Advanced User Rights (this box must be checked).
Click the drop-down box for Rights.
Select “Log on as a service”.
Click the Add button.
In the “Add Users and Groups” dialog, use the “List Names From” drop-down box to select
the domain from which you want users to be able to run Monitor Pro. This will normally
be either the local machine name or the network domain.
Select the group or specific users who need to be able to run Monitor Pro, and click the Add
button.
21
Click the OK button to add the selected group or users to those permitted to log on as a
service.
Click OK to close the User Rights Policy dialog.
Close the User Manager.
NOTE: The steps above vary slightly on Windows 2000.
2. Give full control access to the registry to the Users group on a local machine or in the Primary
Domain Controller (whichever applies).
Go to Start, Run and enter REGEDT32 and click the OK button.
Expand HKEY_LOCAL_MACHINE\Software\ and select the Schneider Automation key.
Click Security, Permissions
Select "Replace Permission on Existing Subkeys"
Click the Add button.
Add the users that will be allowed to run Monitor Pro, and make sure that “Type of Access” is
set to “Full Control.”
Click the OK button.
Click OK to close the Registry Key Permissions dialog.
Close the Registry Editor.
Now any member of the Users group can start Monitor Pro v7.
SPR# 4931 Layer information is lost when mimics are saved in ASCII form.
When a mimic is saved within Client Builder in ASCII, all layer information is lost.
If ASCII save is needed, layer information must be manually reentered.
SPR# 4995 Text animation with default, auto format doesn't work.
The Client Builder's "Auto Format" feature for a "Display Register" using an
OFS configured tag requires a ".CCN" file, if OFS is setup to use a Concept
symbol table. Presently, the Concept ".PRJ" file type will not work with
the Client Builder's "Auto Format" feature.
22