Operator Workstation Technical Bulletin

Transcription

Issue Date
12/21/01
TECHNICAL BULLETIN
Operator Workstation
Operator Workstation ..........................................................................5
Introduction......................................................................................................... 5
Key Concepts...................................................................................................... 6
Operator Workstation ......................................................................................................6
Theory of Operation.........................................................................................................6
Multiple Direct Connects..................................................................................................8
Fire OWS ......................................................................................................................11
Components..................................................................................................................11
Design Considerations: Configured or Non-configured Workstation ..............................13
Design Considerations: Direct or Dial-up Workstation ...................................................16
OWS Installation............................................................................................................17
Configuring a Printer for the Metasys System................................................................25
Configuring Metasys Workstations for Printers ..............................................................27
Example of Multiple OWSs with a Single Operating System and Three Printers............27
Mixed Operating Systems .............................................................................................30
Printing Change-of-State (COS) Reports.......................................................................30
Printing Reports and Summaries in Color......................................................................31
General Modem Configuration.......................................................................................33
Wiring—Modems...........................................................................................................34
Commissioning Overview ..............................................................................................36
Commissioning Hardware..............................................................................................37
Commissioning Software: New Job ...............................................................................40
Commissioning Software: Upgrading Existing Jobs.......................................................47
Detailed Procedures......................................................................................... 50
Direct Connecting to N1 LAN – Ethernet Network .........................................................50
© 2001 Johnson Controls, Inc.
Code No. LIT-636013
www.johnsoncontrols.com
Metasys Release 12.00
2
Direct Connecting to N1 LAN – ARCNET Network ........................................................50
Direct Connecting to NCM .............................................................................................51
Dial-up Connecting to NCM - with Modem .....................................................................51
Dial-up Connecting to NCM - with ISDN ........................................................................52
Adding a Windows Printer in Windows 98 Software.......................................................53
Adding a Windows Printer in Windows NT/2000 Software .............................................54
Adding a Generic/Text-only Printer................................................................................54
Adding an IBM Proprinter Device for NCM Printing .......................................................54
Configuring Metasys Workstations for Printers ..............................................................55
Fixing Line Feed Problems When Using a Serial Printer ...............................................58
Configuring a Printer for Change-of-State (COS) Reports .............................................62
Connecting and Configuring a Modem to an OWS ........................................................63
Connecting and Configuring a Modem to an NCM.........................................................65
Adding User-defined Modems .......................................................................................65
Configuring ISDN Modems ............................................................................................66
Installing the Microsoft Backup Utility.............................................................................68
Removing Additional Drivers .........................................................................................70
Installing Metasys PMI Software: New Job ....................................................................72
Installing Metasys PMI Software: Upgrading Existing Job .............................................73
Appendix A: Autoexec.bat and Config.sys Files ........................................... 77
Config.sys .....................................................................................................................77
Autoexec.bat .................................................................................................................78
Daylight Saving Time.....................................................................................................79
Date/Time Properties.....................................................................................................79
Appendix B: Printer Notes ............................................................................... 80
Supported NCM Printers ...............................................................................................80
Printing from Metasys Software .....................................................................................80
Defining the Printer........................................................................................................80
Printing from Third-party Packages ...............................................................................80
Draft and Quality Modes of Printing ...............................................................................81
Disabling Form Feeds ...................................................................................................81
Windows Printer Name..................................................................................................81
Windows-only (HP-PPA)-type Printers ..........................................................................81
Hewlett-Packard Printers...............................................................................................82
3
Printers with Mixed Operating Systems .........................................................................82
Panasonic Printers ........................................................................................................82
Appendix C: Sound Capabilities ..................................................................... 83
Alarm Sounds................................................................................................................83
Required Hardware .......................................................................................................83
Modifying the .INI Files ..................................................................................................84
Appendix D: Release 6.0 and Later NCM Memory Requirements ................ 85
Appendix E: Database Conversion ................................................................. 87
PREP-FOR Command ..................................................................................................87
Database Conversion Guidelines ..................................................................................88
Manually Starting the Conversion ..................................................................................88
Conversion Screens ......................................................................................................89
Convert.log....................................................................................................................89
Going Back to Previous PMI Software ...........................................................................91
Restoring Previous Release Database over Converted Database .................................92
Appendix F: Troubleshooting Chart................................................................. 93
Appendix G: ARCNET Troubleshooting .......................................................... 95
ARCNET Interrupt .........................................................................................................95
ARCNET I/O Address....................................................................................................96
ARCNET Base Memory Address...................................................................................97
ARCNET Node Address ................................................................................................99
N1 Bus/Star Setup.......................................................................................................100
N1 Enhanced/Compatible Setup .................................................................................100
ARCNET Model...........................................................................................................100
Config.sys and Autoexec.bat .......................................................................................101
Arcnet.ows ..................................................................................................................102
Appendix H: Windows NT/Windows 2000 Details........................................ 103
OWS Configuration......................................................................................................103
Using Database Backup and Restore..........................................................................104
Unsupported Features.................................................................................................105
Microsoft IntelliMouse Pointing Device......................................................................106
Using PREP-FOR with Windows NT Software.............................................................106
4
Appendix I: Connecting Metasys Release 9.01 OWS to a
Metasys Release 10.01 or Later Network ..................................................... 107
Interconnection Issues.................................................................................................107
Appendix J: Ordering Information ................................................................ 109
5
Introduction
The Operator Workstation (OWS) is an easy-to-use, high-level
interface for the operator of a Metasys Building Automation System
(BAS). This document describes the OWS and how to:
•
direct connect to N1 LAN – Ethernet Network
•
direct connect to N1 LAN – ARCNET Network
•
direct connect to NCM
•
dial-up connect to NCM (with modem)
•
dial-up connect to NCM (with Integrated Services Digital Network
[ISDN])
•
add a Windows printer in Windows 98 software
•
add a Windows printer in Windows NT/Windows 2000 software
•
add a generic/text-only printer
•
add an IBM Proprinter device for NCM printing
•
configure Metasys workstations for printers
•
fix line feed problems when using a serial printer
•
configure a printer for Change-of-State (COS) reports
•
connect and configure a modem to an OWS
•
connect and configure a modem to an NCM
•
add user-defined modems
•
configure ISDN modems
•
install the Microsoft Backup Utility
•
remove additional drivers
•
install Metasys Person-Machine Interface (PMI) software: new job
•
install Metasys PMI software: upgrading existing job
6
Note:
Use this document with the Metasys Installation and
Platform Requirements Technical Bulletin (LIT-12012),
which contains hardware and software requirements and
supported platforms.
IMPORTANT: Windows Version 3.1 software is not supported with
Metasys Release 10.01 or later. Windows 95 software
is not supported with Metasys Release 11.00 or later.
Key Concepts
The Operator Workstation (OWS) is an easy-to-use, high-level
interface for the operator of a Metasys BAS. With the workstation, the
operator:
•
monitors the facility.
•
controls the facility.
•
examines historical and current information about facility
operations.
•
defines objects and features.
Theory of Operation
The Metasys OWS hardware is a Personal Computer (PC) that consists
of a system unit, color monitor, keyboard, mouse, and a Network
Interface Card (NIC). An NIC, modem, and RS-232 allow the
workstation to communicate with other nodes such as other
workstations and NCMs on the N1 Local Area Network (LAN).
The modem provides dial-up communication between the nodes from
a remote location, and the RS-232 connection allows the workstation
to communicate with an NCM directly.
The workstation runs several software packages that provide advanced
BAS functions, including the Metasys OWS software, a
Microsoft Windows based program. Optionally, the workstation may
also have a printer.
The OWS is available in several different models from various
manufacturers. For a list of supported platforms, see the
Metasys Installation and Platform Requirements Technical Bulletin
(LIT-12012).
7
Types
The OWS can be one of five types, depending on how you connect the
workstation to the Metasys Network and whether the workstation is
configured. The workstation can connect directly to the N1 LAN, to
the NCM, or remotely connect to the NCM over telephone lines. Also,
the workstation can be a configured device capable of all Metasys
Network operations or a non-configured device capable of a limited set
of Metasys Network operations. Figure 1 summarizes the five OWS
types.
LAN Direct Connected
1. Configured
N1 LAN
NCM Direct Connected
2. Configured, or
3. Unconfigured
N2 Bus
N2 Bus
Note: For Integrated Services Digital
Network (ISDN) applications, use
terminal adapters in place of
modems.
NCM Dial-up Connected
4. Configured, or
5. Unconfigured
N2 Bus
Note: For multi-direct application,
see Figure 2.
OWSCONF
Modem
Modem
(internal or
external)
N2 Bus
Figure 1: OWS Configuration Options
8
Modes
An OWS has two modes of operation: online and offline.
The online mode offers the operator the following functions:
•
Basic Operator Control—Provides basic interaction with the
Metasys BAS. The operator receives data, adjusts operating
parameters, commands specific operations, reschedules events, and
performs uploads and downloads.
•
Automatic Data Output—Receives messages, warnings, alarms,
and reports to a printer or a workstation display or file.
•
Online Definition—Defines new objects, setup trends,
totalizations, demand limiting, and other features.
•
Dynamic Data Exchange—Provides the exchange of information
between the Metasys Network and third-party Windows
applications with Metalink software. These applications can use
Metasys data from objects and attributes both historically (offline)
and dynamically (online).
•
PC Operation—Performs ordinary PC tasks and runs third-party
software such as Microsoft Excel.
•
NCSETUP for Windows software—Configures the NCM.
The offline mode offers the operator or application engineer the
following functions:
•
Data Definition Language (DDL) Definition—Defines hardware
and software components of a Metasys Network.
•
Graphic Programming Language (GPL) Definition—Defines
software objects and creates control strategies for the NCM.
•
PC Operation—Performs ordinary PC tasks and runs third-party
software such as Microsoft Excel.
Multiple Direct Connects
The OWS can connect to multiple NCMs by way of its serial (COM)
ports. This application benefits jobs with remote NCMs and a central
OWS, where leased or dedicated lines are preferred. Multiple direct
connections are useful because you now only need one workstation to
connect to multiple NCMs.
If your remote NCMs are in different time zones, use the time zone for
the network to which you last connected. If several NCMs are active
and you change the time-of-day at one network, then only that network
has its time updated.
Figure 2 shows an example of a multiple direct-connect workstation.
9
N1 LAN
To other nodes
N1 LAN
RS-232 Direct Connects
Modem*
N2 Bus
Modem*
NCM
NCM
NCM
NCM
N2 Bus
* Leased line modem at 9600 baud.
NCM
NCM
MULTOWS
Figure 2: Multi-direct OWS
As shown in Figure 2, up to four NCMs can connect to
Communication (COM) ports of the OWS. The actual number of
NCMs that can connect directly to the workstation’s COM ports
depends on the type of personal computer. Also notice that a group of
NCMs on the N1 can connect from an NCM that is directly connected
to the OWS.
Each directly connected NCM (or group of NCMs) is on a separate
network, which means that each direct-connect network has an
individual global database. If you wish to have password access to all
directly connected NCMs, you need to define your password
separately at each direct-connect network. You can log on to all
directly connected networks at the same time. (Use the Network
Summary to switch between networks.) Each directly connected NCM
can communicate directly with control modules installed next to it in
the same NCM or with other NCMs on its remote N1 network.
Alarm messages can be broadcasted and acknowledged across
networks, even if the operator is not logged on the network that is
sending the message. For example, if you are logged on to Network A
and a COS occurs at Network B, the report appears on the workstation.
To act on this report, you do not need to log on to Network B, as long
as you have password access to that network. The system performs the
appropriate password checks internally.
10
Since each direct-connect network has a separate global database, the
direct-connect NCMs can share data between N1 or N2 devices on the
same network. These NCMs cannot perform any of the tasks that are
associated with Dynamic Data Access software (for example,
obtaining the value of an object from a remote network). These types
of tasks require the Metalink interface, a program included with the
OWS software.
When the Facility Management System (FMS) Logon dialog box
appears, a status window for each direct-connect network defined for
this PC is shown along the right side of the OWS screen (Figure 3).
These direct-connect status windows show the:
•
network name
•
OWS COM port being used by the NCM
•
status of the workstation
•
communication speed of workstation to NCM connection
•
the workstation as configured or non-configured
FMS Logon
OK
Select network:
Cancel
HDQTRS
NC Direct3
HDQTRS
EAST-BLD
HDQTRS
Toronto
NORTHBLD
SOUTHBLD
WEST-BLD
Enter Password:
NORTHBLD
COM3
Connected @ 9600 baud
Configured
NC Direct2
********
WEST-BLD
COM2
Configured
NC Direct
EAST-BLD
COM1
Configured
OWSLOG
Figure 3: Logon Dialog Box and Direct-Connect Status Windows
Direct-connect status windows can be minimized; in which case, they
appear in the task bar at the bottom of the screen.
11
After selecting a network and entering your password, the Network
Map displays for the chosen network. The direct-connect boxes remain
displayed. They move to the background when you perform a task,
such as displaying a summary.
A COS report from any directly connected NCM appears on the
screen, even when no one is currently logged on. If your password
allows, you may acknowledge the report without logging on. However,
if you do not have password access, you can only acknowledge that
you have read the report by selecting Look Later.
Editing DDL File for Multi-Direct Workstation
After you have installed the OWS and the PMI software, the last step
for configuring an OWS that supports multiple NCM direct
connections is to edit the workstation’s Network/Port Configuration
DDL file (@NET file). Specifically, add the PORT and NET
statements for each multiple network, making sure you follow proper
DDL syntax. See the DDL Programmer’s Manual for instructions and
a file example.
Fire OWS
The Fire OWS is an Underwriters Laboratories, Inc. (UL) Listed
OWS used for fire alarm reporting as part of the Metasys Intelligent
Fire Network. See the Fire Operator Workstation (Fire OWS)
Technical Bulletin (LIT-636014) for more information.
Components
The OWS consists of hardware and software components
recommended for the Metasys Network. For a list of supported vendor
configurations, refer to the Metasys Installation and Platform
Requirements Technical Bulletin (LIT-12012).
Hardware Components
The OWS consists of the following hardware components:
•
Computer—Includes a system unit, monitor with display stand,
keyboard, and mouse. The hard disk drive must have an absolute
minimum of 500 MB for loading the system (Windows software,
PMI, GPL, and a small database).
•
Disk Drive—One 1.44 MB 3.5-inch floppy drive is required for
loading and backup purposes. Metasys software does not support a
5.25-inch floppy diskette drive.
•
CD-ROM Drive—A CD-ROM drive (4x or higher) is required for
installing Metasys software.
12
•
NIC—Card that is installed into the OWS and used to make the
physical connection to the network. The type of card depends on
whether you connect to an ARCNET or Ethernet network. In both
cases, you must have an NIC installed and connected or the OWS
cannot communicate on either network.
Note:
If the NCM is configured to use an Ethernet connection,
always have the Ethernet NIC installed in the NCM to
prevent download failures.
•
Serial Communications Board (optional)—Computer board that
provides extra serial ports required for connecting one workstation
to multiple networks. The serial board needed depends on the
model of your PC. Refer to the Metasys Installation and Platform
Requirements Technical Bulletin (LIT-12012).
•
Additional Random Access Memory (RAM)—A minimum total of
64 MB of memory is required for Windows 98 software.
A minimum total of 128 MB of memory is required for
Windows NT and Windows 2000 software.
Note:
Windows 2000 software/operating system in this document
refers to Windows 2000 Professional software/operating
system.
•
Printer (optional)—An output device for printing Metasys
summaries and reports in black or color.
•
Sound Blaster Compatible Sound Board—Adds audio/tone
sound to Metasys operations for Change-of-State reporting to help
differentiate between alarm levels and enable the use of
multimedia technology (optional on Windows 98 software). For
Windows NT and Windows 2000 software, a sound board is
required. They do not provide support for the PC speaker.
•
Modems (optional)—Enable dial-up or leased line connections
between the OWS and the NCM. A modem is required at an NCM
and another at the workstation.
•
An Integrated Services Digital Network (ISDN) application uses
higher speed modems (optional). An ISDN modem is required at
the NCM and another at the workstation.
The modems supported for use with Metasys software are listed in the
Computer Price List (pcprices.doc) at The Advisor > Business Focus >
Purchasing/Strategic Procurement > ePurchasing > CG Computer
Purchasing. These modems have been thoroughly tested. The baud
rates of these modems vary, and the maximum baud rate used on the
OWS depends on the dial-up NCM. Refer to the Network Control
Module 300 Series Technical Bulletin (LIT-6360251) for specific
maximum baud rates.
13
The supported ISDN modem is the ADTRAN ISU Express. An
RS-232 cable is used to connect the external modems to the OWS or
NCM.
Software Components
The OWS consists of the following software components:
•
Metasys PMI Software—Programs that provide all operator
Metasys functions, including DDL and Metasys Metalink software.
Metalink software is an interface package for the OWS that allows
data sharing between the Metasys Network and third-party
Windows software packages that are Dynamic Data Exchange
(DDE) compatible.
•
Metasys GPL (optional)—Graphics-oriented programming
language for creating software objects and programming control
strategies.
•
Metasys GPL Heating, Ventilating, and Air Conditioning (HVAC)
Library (optional)—Set of tested GPL compounds that the
application engineer can use to program common BAS
applications.
•
Metasys JC-BASIC Programming Language (optional)—Textual
programming language for creating processes.
•
Third-party Software—Several software packages provided by
third-party software manufacturers. For a current list of
recommended third-party software packages, refer to the Metasys
Installation and Platform Requirements Technical Bulletin
(LIT-12012).
Design Considerations: Configured or Non-configured Workstation
Decide whether you want to set up the OWS as a configured or
non-configured workstation. A configured workstation, either direct or
dial-up connected, is a defined device in the Metasys database and has
the full set of communication functions with other nodes. All other
nodes on the network can identify a configured workstation.
A non-configured workstation is not defined as a hardware object in
the Metasys database and has a limited set of communication functions
with other nodes. Unlike the configured workstation, any other node
on the network cannot identify a non-configured workstation.
Therefore, a non-configured workstation does not automatically
receive reports from other nodes.
Table 1 lists the different capabilities of the configured and
non-configured OWS.
14
Table 1: Capabilities of OWS
Capability
Description
Online
Database
Generation
Workstation allows user to:
Purpose
Configured Nonconfigured
Online
Provides central
operator definition of all
Metasys operations.
Yes
Yes
Provides central user
override control of all
Metasys operations.
Also useful for system
test.
Yes
Yes
Keeps operator current
on status of facility.
Yes
No
Maintenance Provides maintenance flags to the
operator based on hours of usage,
number of cycles, etc.
Optimizes maintenance
efforts.
Yes
No
DDE
Interface
(Metalink
Software)
Provides data exchange between
the Metasys Network and third-party
Windows applications.
Provides useful reports,
spreadsheets, and work
orders.
Yes
Yes
Store
Historical
Data
Uploads and stores historical data
on system performance
automatically.
Provides convenient
record keeping, and
establishes database
accessible to third-party
programs.
Yes
No
Graphics
Allows both graphic and textual data
presentation.
Provides faster user
recognition.
Yes
Yes
Windows
Display is divided into regions that
can be sized and moved, and act as
separate displays.
Provides access to
several types of
information
simultaneously.
Yes
Yes
System
Archive
Stores operating programs and
parameter as backup.
Provides quick, easy
recovery after power
loss or system repair.
Yes
Yes
Password
Protection
Allows definition of different levels of
system access for various users as
defined by their password.
See the Non-configured Workstation
Security section.
Limits exposure to
errors or tampering by
unqualified users.
Yes
Yes
NCSETUP
for
Windows
Software
Allows you to set up, modify, and
configure NCMs for the Metasys
Network.
Configures NCM for use
on Metasys Network.
Yes
Yes
Commands
Monitor
Facility
•
define new objects.
•
modify setup for existing
objects.
•
implement feature actions.
Workstation allows access to:
•
start, stop, or reset operations.
•
communications.
•
change operational setpoints.
Workstation provides:
•
pop-up message windows to
alert user to special situations.
•
summaries automatically sent at
particular time or event.
Continued on next page . . .
Capability
(Cont.)
Description
Purpose
15
Configured Nonconfigured
Offline
GPL
Enables operator to program
Metasys software functions by
positioning and joining graphic
symbols.
Simplifies custom
programming of
Metasys BAS.
Yes
Yes
DDL
Enables operator to define PC
groups, systems, and objects using
lines of text.
Provides a quick
method for defining
large blocks of new
system/objects.
Yes
Yes
Archive
Allows archiving of trend,
totalization, follow-up, and status
reports.
Provides a method of
storing data.
Yes
No
Non-configured Workstation Security
Carefully consider your security needs when a person with a
non-configured workstation has access to a network. A security risk
may arise because a non-configured direct or dial-up connection
allows any person who has knowledge of the Metasys Network's name
and default Level 1 password to view and edit the password database.
Non-configured workstations do not have a PC name in the NET.ddl
file. See the following NET.ddl file example and note that the NET
Keyword string (located in the third line) contains no PC name, thus
preventing PC identification on a network.
@NET
PORT "LPT1", 3
NET "XYZ-BLDG", "XYZ-BLDG NETWORK",
NCDIAL "T", "123-4567"
The default password, METASYS, is created when the NET.ddl file is
compiled. If a workstation has never been connected to a network,
only the default password exists.
To prevent access to the Metasys system from a non-configured
workstation, delete the Metasys default password from the PMI
software. Refer to the Defining Passwords (LIT-120150) chapter of the
Operator Workstation User’s Manual. Once the Metasys default
password is removed, you cannot use non-configured access because a
non-configured workstation does not know any other password. Use a
configured workstation for dial-up capabilities.
16
Establishing a connection to a network for the first time with a
non-configured workstation requires the following steps:
1. Launch PMI.
2. Select a network.
3. Enter Password. (The only possible password is METASYS
because you do not have the current online global database.) A
direct or dial-up connection launches and establishes a link to the
network.
IMPORTANT: At this point, you are logged on to the network with
the default Level 1 password.
The network node manager checks to see if you have the latest online
global database. Since you do not have the latest online global
database, the latest version is provided including the network password
database.
IMPORTANT: You are now still logged on with the default Level 1
password and are able to view and edit the password
database. To protect your system from a possible
security breach using a non-configured
workstation, delete the default Level 1 password
from your system. Refer to the Defining Passwords
chapter (LIT-120150) of the Operator Workstation
User’s Manual.
Design Considerations: Direct or Dial-up Workstation
Consider how to connect the OWS: direct or dial-up. A directly
connected workstation connects to the N1 LAN or to an NCM via an
RS-232 cable. A dial-up workstation connects to a modem, which
allows access to the Metasys Network over telephone lines. The
primary difference between direct and dial-up connections is
communication speed. Refer to Table 2.
17
Table 2: Design Considerations
Type of Connection
Maximum Communication Speed
Direct
N1 LAN
10 Million bits per second (Mbps) Ethernet
network
2.5 Mbps ARCNET network
NCM100/200
NCM300 Series
1200 to 19,200 baud*
1200 to 57,600 baud
NCM100/200
NCM300 Series
1200 to 9600 baud
1200 to 38,400 baud*
57,600 for ISDN
Dial-Up
Notes:
A direct-connect default destination does not work, but a direct-connect
OWS can be a default destination.
For the NCM300 Series only: Above the 19,200 baud rate, use a
16-character First In, First Out (FIFO) serial card. The serial card must use
a 16550AF UART or equivalent. An example of a 16550AF serial card is
the BOCA I/O AT55.
When selecting the connection types, be sure to follow these rules:
•
Direct connections can use COM1, COM2, COM3, and COM4,
depending on PC type.
•
Dial-up connections can use COM1 and COM2 only; they cannot
use COM3 or COM4.
•
An expansion board may be required for additional COM in
multiple direct connection applications. Refer to the Metasys
(LIT-12012) for recommendations for your PC.
•
The maximum length allowed for the RS-232 is 50 feet
(EIA-232-D). If the NCM must be placed in a remote location, use
an alternate communication scheme such as dedicated line
modems.
OWS Installation
Physical Dimensions
Note:
The following specifications for physical dimensions and
power vary with the specific platform. See the
manufacturer’s literature for details.
Table 3 describes typical physical dimensions of the OWS
components:
18
Table 3: Physical Dimensions for OWS
Typical Area Required (Approximate)
System Unit
Monitor
Height x Width x Depth
Keyboard
Desktop
152 mm x 406 mm x 419 mm
(6 in. x 16 in. x 16.5 in.)
381 mm x 356 mm x 406 mm
(15 in. x 14 in. x 16 in.)
51 x 495 x 216 mm
(2 in. x 19.5 in. x 8.5 in.)
Floor
Standing
597 mm x 165 mm x 483 mm
(23.5 in. x 6.5 in. x 19 in.)
362 mm x 356 mm x 381 mm
(14.25 in. x 14 in. x 15 in.)
51 mm x 495 mm x 216 mm
(2 in. x 19.5 in. x 8.5 in.)
Portable
114 mm x 216 mm x 343 mm
(4.5 in. x 8.5 in. x 13.5 in.)
N/A
N/A
16.5 mm x 343 mm x 165 mm
(0.65 in. x 13.5 in. x 6.5 in.)
Type of
Chassis
Table 4 describes typical physical dimensions of the OWS accessories.
Table 4: Physical Dimensions of OWS Accessories
Accessory
Typical Area Required (Approximate) Height x Width x Depth
Printer
127 mm x 419 mm x 356 mm (5 in. x 16.5 in. x 14 in.)
Multi-Tech
 MultiModemII

Modem
35 mm x 156 mm x 229 mm (1.4 in. x 6.2 in. x 9.0 in.)
ADTRAN ISU Express
Fiber-optic Transceiver
Mouse (and Pad)
203 mm x 229 mm (8.0 in. x 9.0 in.)
Power Requirements
Table 5 describes the typical power requirements for major OWS
components.
Table 5: Power Requirements
Component
Power Requirements
Desktop Computer
100 VAC-125 VAC at 2.5 A-3.2 A, 50/60 Hz
(200 VAC-240 VAC at 1.3 A-2.0 A , 50/60 Hz)
Floor Standing Computer
100 VAC-125 VAC at 5.3 A, 50/60 Hz
(200 VAC-240 VAC at 2.7 A, 50/60 Hz)
Portable Computer
120 VAC at 1.0 A, 50/60 Hz
(220 VAC-240 VAC, 50/60 Hz)
Printer
120 VAC at 1.0 A, 60 Hz
Multi-Tech MultiModemII
Modem
115 VAC at 0.3 A, 60 Hz
ADTRAN ISU Express
115 VAC, 60 Hz, 6.5 Watt Maximum Dissipation without Plain Old
Telephone Service (POTS) or Modem Options
220 VAC, 50 Hz, 13 Watt Maximum Dissipation with POTS and Modem
Options
19
Environmental Information
Note:
The following specifications for ambient operating
temperature and humidity vary with the specific platform.
See the manufacturer’s literature for details.
The OWS is rated for use in light industrial or office room
applications, specified as follows:
•
Ambient operating temperature: 10 to 40°C (50 to 104°F)
•
Ambient operating humidity: 20 to 80%
•
The atmosphere must be free of corrosive chemical vapors that
may damage electronic equipment.
Wiring—Sequence of Steps
The wiring procedure depends on whether the OWS is directly
connected to the N1 LAN, directly connected to an NCM, or dial-up
connected to an NCM. (The following instructions presume all boards
are installed and properly configured.) Table 6 provides a summary of
OWS connections.
Table 6: OWS Connections
*
Type of Connection
Parallel
Port
Serial Port
(COM1)
Direct
Connect
N1 LAN
Printer*
Not Used
N1 LAN
Not Used
NCM
Printer*
NCM
N/A
Up to 3 NCMs
Dial-up
Connect
NCM
Printer*
Modem
N/A
1 Modem (COM2 only)
Printer may be connected to a serial port.
Network Interface
Card Ports
Additional Serial Ports
(COM2 - COM4)
20
T
T
Parallel
NCM
NCM
Note: If the workstation is at the end of line, install 93 ohm
T
terminator cap on open end of T-connector.
= 93 ohm Terminator Cap
opwsts
Printer
Figure 4: Directly Connecting OWS to N1 LAN
to RS-232 Serial Port
or
to RS-232 Submodule
R ESET
NCM (door open)
Note that the cable used to
connect to the NCM Serial Port
is not the same cable used to
connect to the NCM submodule.
Parallel
to Serial Port
Printer
Figure 5: Directly Connecting OWS to NCM101
opwstsb
21
to RS-232 Serial Port
or
to RS-232 Submodule
RESET
NCM200 (door open)
to Serial Port
Parallel
Note that the cable used to
connect to the NCM Serial Port
is not the same cable used to
connect to the NCM submodule.
Printer
opwst200
Figure 6: Directly Connecting OWS to NCM200
After making the physical connection and turning on the workstation,
the initialization and connection process begins. A message window
appears on the workstation screen displaying the status of the
connection. Do not close this message window (by double-clicking
the Control menu box), unless you want to cancel the connection.
Closing the window cancels the connection.
During the connection process, the message changes to display the
current connection status. If the connection fails, the message explains
why. The explanation remains on the screen for 5 seconds before the
Metasys software begins in offline mode. (In offline mode, data from
the NCM is not available.) To retry the connection, correct the reason
for the failure and reboot the workstation.
Table 7 lists and explains the status and failure messages that can
occur in the message window.
22
When directly connecting an OWS to an NCM, follow these
guidelines:
•
The OWS PC port must be set to the same baud rate as the NCM
port.
•
The OWS must have the network to which it is connecting defined
in its database.
•
If you are downloading from the direct-connect workstation to the
NCM, the archive node address for the NCM must be the same as
the NCM node address. If it is not, the download does not occur.
For more information on specifying the archive node address, see
the NCM setup information in the NCSETUP for Windows
Technical Bulletin (LIT-6360251d).
•
If you are downloading from the direct-connect workstation to the
NCM, wait 2 to 3 minutes for the download to start before
assuming failure.
Table 7: Messages That Can Occur During Direct Connection
Message
Explanation
Code Downloading
Metasys PMI code is being downloaded from the
workstation into the NCM.
Connected @ XXXX Baud Configured
The actual baud rate of connection is displayed in
message. XXXX may vary depending on the rate
and quality of the connection and can be
significantly less than the selected baud.
The workstation and NCM are successfully
connected at the specified baud rate. The workstation
is configured.
Connected @ XXXX Baud Unconfigured
The actual baud rate of connection is displayed in
message. XXXX may vary depending on the rate
and quality of the connection and can be
significantly less than the selected baud.
The workstation and NCM are successfully
connected at the specified baud rate. The workstation
is not configured.
Connecting to NC . . .
Physical connection and initialization of workstation is
successful. Connection is occurring.
Data Downloading
Data is being downloaded from the workstation into
the NCM.
Disconnected, Failed! Cannot Read NC NOVRAM
The workstation cannot read the network name from
the NCM’s NOVRAM.
Disconnected, Failed! Cannot Read NC State
Every 30 seconds the workstation attempts to read
the state of the NCM. This message indicates the
state cannot be read and the workstation has lost
communication from the NCM.
Disconnected, Failed! Global Data Failed
The process of synchronizing global data has failed.
Disconnected, Failed! Memory Error
An OWS memory error has occurred. Need system
reboot.
Disconnected, Failed! Network Name Invalid
The network name read from the NCM’s NOVRAM is
not defined in the workstation’s network database.
Disconnected, Failed! No Communication
NCM initialization failed or the workstation has
become physically disconnected from the NCM.
23
Message (Cont.)
Explanation
Disconnected, Failed! Port Not Enabled
OWS port initialization failed (hardware failure).
Disconnected, Retrying Configured
Connection between workstation and NCM is lost
because the NCM is rebooted or the cable is
unplugged. Workstation is retrying connection. This
message also occurs immediately before a code or
data download.
Global Data Updating
Global data is synchronizing between NCM and
workstation.
Initializing . . .
The initialization process is occurring. (The
workstation must be initialized before the connection
process can begin.)
NC Must Force Download
NCM must be reset by using the reset button on the
front, by manual command, or by cycling power on
the NCM.
NC Needs a Download
The NCM needs a download from the workstation.
NC Not Defined
NCM is not defined. Need to define the NCM in the
global database source file. See the Source File
Development section (LIT-630020) of the DDL
Programmer’s Manual for instructions.
Dial-up Connections
Figure 7 shows how baud rates can differ between the OWS to the
modem, the NCM and the modem, and between the two modems.
The baud rate between the OWS
and its modem is set in the
PC configuration box. The full
range of baud rates are valid for
all four COM ports
(1200 through 57,600).
The baud rate between the modems depends
on the capability of the modems. The highest
baud supported should be used. It does not have to
match the baud rate between the PC and its modem or
between the NCM and its modem. The actual
rate can be significantly less than the selected rate.
The baud rate between the NCM and its
modem is set in the PC definition window in Metasys
software or in the NOVRAM View and Modify dialog
box (for download) in NCSETUP for Windows software.
The range of valid baud rates depends on
the NCM port in which the modem is connected.
The highest baud rate to the modem should be used,
even if it is not supported by the modem.
M ET AS YS
modem
Figure 7: Modem to Device vs. Modem to Modem Connections
The baud rate of connection is the actual rate of communication
established between the OWS and the NCM. It is typically the modem
baud rate but may be less depending on the quality of the phone line.
The rate may change each time a connection is established.
24
Note:
You can use an external
modem connected to an
RS-232 submodule instead
of an internal modem.
Telephone Line
MDM101
R
E
S
E
T
Serial
Parallel
RS-232 Line
Modem
Printer
OPWREM
Figure 8: Remote Connection between OWS and NCM
ISDN Line
NCM to ISDN modem
cable shown connects
to NCM Port 2.
ISDN
Modem
Serial
Parallel
RESET
ISDN
Modem
NCM200
Printer
Figure 9: ISDN Remote Connection between OWS and NCM
opwisdn
25
Configuring a Printer for the Metasys System
Printers that have Windows drivers, including many laser printers, can
be configured to print Metasys reports and messages. Color printers
can be configured to print various color reports and the Critical
summary. For details on color printing, see the Printing Reports and
Summaries in Color section of this technical bulletin.
Consider the complete system before installing any printers. There are
two configuration possibilities:
•
•
Single Operating System (OS)
-
One or more OWSs, all using a single OS, with one or more
printers connected to one or more of the OWSs. (A single
OWS with a single printer falls into this category.)
-
A Single OS is the recommended configuration and is
described in the Common Operating System section of this
document.
Mixed Operating Systems
-
Multiple OWSs, using mixed OSs, with one or more printers
connected to one or more of the OWSs.
-
Configuration of mixed Operating Systems requires special
care. See the Mixed Operating Systems section and
Appendix B: Printer Notes in this document for more help.
Common Operating System
Review the following instructions and the Adding a Windows Printer
in Windows 98 Software and Adding a Windows Printer in NT/2000
Software detailed procedures, and make the recommended changes to
prevent printer problems when using Metasys software with any
Windows OS. See Appendix B: Printer Notes in this document for
further hints.
To print properly in the system, two procedures must be completed:
1.
Install each printer on every OWS using standard Windows
installation procedures.
2.
Configure Metasys software to work with each printer.
26
Windows 98, Windows NT, or Windows 2000 Software
Repeat the Adding a Windows Printer in Windows 98 Software or
Adding a Windows Printer in Windows NT/2000 Software procedure
for every printer type installed on the Metasys Network. For example,
if you have three different printers connected to three of your five
OWSs, then you must install three printer drivers on every OWS, even
those that do not have printers connected. If you add a new printer
later, then you must add the new printer driver to all five OWSs.
IMPORTANT: Always reboot the PC when you finish making
changes to the Windows Printer configuration.
Summary
On every OWS, you must install a Windows printer for every printer
on the system, even if there are printers with the same name
(see Figure 10). Later, rename these printers to match the Metasys
printer object name. Each name must be unique.
Figure 10: Typical Screen after Installing All Windows
Printers for a Metasys Network
27
Configuring Metasys Workstations for Printers
After installing the Windows printers on all Metasys workstations, you
must configure the individual Metasys printer objects. This procedure
is independent of the OS. You must configure every printer on the
network. Each OWS with a physical printer connected must undergo
this configuration process. See the Configuring Metasys Workstations
for Printers detailed procedure.
Example of Multiple OWSs with a Single Operating System and
Three Printers
Here is an example of multiple OWSs with a single OS and
three printers.
Situation:
You have five OWSs all using Windows NT software. Assume the
OWSs are named OWS-210 through OWS-214. You have
three Hewlett-Packard® Company DeskJet 870C printers:
one connected to OWS-210, the second connected to OWS-211, and
the third connected to OWS-213. An IBM Proprinter III printer is
connected to OWS-214. No printer is connected to OWS-212.
Following the preceding process, you have installed the following
printers on OWS-214:
Local:
The default printer LP-214 (renamed from IBM Proprinter III)
Generic Text Printer
IBM Proprinters devices (renamed from IBM Proprinter devices)
Remote:
HP DeskJet 870C
HP DeskJet 870C (copy 2)
HP DeskJet 870C (copy 3)
Rename the remote printers as follows:
HP DeskJet 870C becomes LP-210
HP DeskJet 870C (copy 2) becomes LP-211
HP DeskJet 870C (copy 3) becomes LP-213
Repeat this process for each OWS (see Figure 11). Table 8 is a
complete description of this example.
28
Figure 11: Typical Screen after Windows Printer
Installation Complete
Table 8: Required Naming Conventions for Single Operating System
OWS and Printer
Printer After Initial Windows
Installation at OWS and Metasys
Configuration
Windows Printer Names After
Renaming the Remote Printers
OWS-210
Windows NT
Operating System
(OS)
Local:
Local:
Local Printer:
HP LaserJet
 870C
Remote:
HP DeskJet 870C (Copy 2)
IBM Proprinter III
OWS-211
Windows NT OS
Local:
LP-2101
Generic/Text Only
IBM Proprinters2 devices
Remote:
LP-211
LP-213
LP-214
Local:
LP-2111
Generic/Text Only
Local Printer:
HP LaserJet 870C
LP-210
Generic/Text Only
IBM Proprinters devices
Remote:
IBM Proprinter III
LP-211
Generic/Text Only
Remote:
LP-210
LP-213
LP-214
1.
2.
This is the printer that has been installed and tested locally, and directly connected to the OWS.
This is an IBM Proprinter device renamed to IBM Proprinters devices.
29
OWS and Printer
(Cont.)
Printer After Initial Windows
Installation at OWS and Metasys
Configuration
Windows Printer Names After
Renaming the Remote Printers
OWS 212
Windows NT OS
Local:
Local:
Local Printer:
None
OWS-213
Windows NT OS
(None)
Generic/Text Only
Remote:
HP DeskJet 870C
IBM Proprinter III
Remote:
Local:
Local:
Generic/Text Only
Remote:
IBM Proprinter III
Local Printer:
IBM Proprinter III
Local:
LP-213
Generic Text Only
Remote:
LP-210
LP-211
LP-214
Local:
LP-2141
Generic/Text Only
Remote:
HP DeskJet 870C
1.
2.
LP-210
LP-211
LP-213
LP-214
LP-2131
Local Printer:
HP DeskJet 870C
OWS-214
Windows NT OS
(None)
Generic/Text Only
LP-214
Generic/Text Only
Remote:
LP-210
LP-211
LP-213
This is the printer that has been installed and tested locally, and directly connected to the OWS.
This is an IBM Proprinter device renamed to IBM Proprinters devices.
30
Mixed Operating Systems
Although installing printers that work across Metasys OWSs with a
common OS is relatively straightforward, configuring printers across
mixed OSs requires special care.
IMPORTANT: You must first ensure that every printer has a driver
that has the same name for all operating systems.
To ensure the printer driver name is the same for all OSs:
1. Install the printer in the usual way on the OWS to which the printer
is to be connected. Print a test page.
2. Move the same printer to another OWS with the alternate OS.
Install the printer in the usual way and print another test page. The
Windows printer driver names on each test print must match.
There is no guarantee that all printers work, even if the driver names
are identical. You may see General Protection Violation errors or no
printing at all.
Many printers emulate another printer. An emulated printer may use a
common driver across OSs. Examine your printer manual to check
printer emulation. Test the printer as described above to ensure the
driver names are the same.
When you have a common driver, the configuration is the same as
described in the Configuring Metasys Workstations for Printers
detailed procedure. You must print a focus window across every OWS
once the printers are fully installed.
If you add another printer to a Metasys Network with multiple OSs,
you must repeat the printer tests to ensure driver names match.
Printing Change-of-State (COS) Reports
Note:
You cannot use an OWS serial printer with Windows NT or
Windows 2000 software for COS reports.
When the Metasys Network prints COS and transaction reports, it sets
the printer to condensed type to ensure that these messages print
properly. The printer is set internally by assigning the printer to a
character code of 15. Most printers use character Code 15 as the
default switch for condensed print. However, if your printer does not
work with Code 15, you need to find the correct code in the printer’s
literature. Then, add a statement in the METASYS.INI file in the
[METASYS] section that identifies the code. (See the Initialization
Parameters Technical Bulletin [LIT-636345].) Follow the steps in the
Configuring a Printer for Change-of-State (COS) Reports detailed
procedure to configure the printer in either case:
31
Printing Reports and Summaries in Color
Printers that support color and style (bold and italic) printing can be
used with OWSs to provide consistent color and style options for
printing COS reports, critical summary messages, and various data that
appear in the Metasys windows.
If you have a color printer connected to an OWS and you are viewing
colored data on the screen (for example, a trend or totalization graph),
you can print that data in color. It is not necessary to reconfigure the
printer, use a specific printer, or set any parameters on the OWS.
Verify that you are using the correct printer driver when printing from
a color printer.
Printing reports and summaries, however, requires using specific
printers and/or making changes to the METASYS.INI file. You can
print COS reports in a variety of colors and styles using either dot
matrix printers that support ESC/P escape codes sequences or
Windows printers without using escape code sequences. The COS
Critical summaries can only be printed in red or black, but support any
type of color printer. To enable color printing in all cases requires
making changes to the METASYS.INI file.
Note:
Color printing is not supported on an NCM.
When using a color printer on an OWS, keep in mind that:
•
the OWS connected to the color printer must have the color
parameters added in that OWSs METASYS.INI file
•
if two or more printers are connected to a single OWS, both
printers must operate identically because both printers use the
same METASYS.INI file parameters
•
if a report is directed to an OWS printer, the destination OWS
METASYS.INI parameters take effect
•
if a critical summary is printed, the METASYS.INI file parameters
on the originating OWS take effect
•
if printing COS messages in color without using escape code
sequences, the proper driver must be installed for the color printer
Printing Reports
Dot matrix printers that can print in multiple colors usually have a
four-color ribbon containing the following colors:
•
Cyan (Blue)
•
Magenta
•
Yellow
•
Black
32
When mixed together, violet, orange, and green are additional options.
With the number of colors available, you can specify that you want a
particular report, for example a Critical Alarm 1, to print red.
In addition, you can print in each style, bold or italic, with any of
the colors.
Modifying the METASYS.INI
Add the specific parameters to the METASYS.INI file for printing
colors or special effects. See the Initialization Parameters Technical
Bulletin (LIT-636345) for detailed explanations of the defaults and
examples of how to change the parameters.
To assign a specific color, bold style, or italic style, to a particular
report type, add the following (each line specifies the particular
report):
RrPrintCritical1=xxxx
RrPrintOperatorTransaction=xxxx
RrPrintFollowup=xxxx
RrPrintStatus=xxxx
RrPrintCardReader=xxxx
xxxx=is a four digit number that defines the desired color/feature.
In addition to the RRPrintCritical parameters above, you must add a
group of escape codes to specify color and print style to the
METASYS.INI file. Open the METAPRN.INI file and identify the
block of parameters that correspond to your printer. Copy this block of
parameters from METAPRN.INI file and paste into the METASYS.INI
file under the section heading [METASYS]. When using Windows
printers for color printing of COS messages, no escape codes are
required. See the Initialization Parameters Technical Bulletin
(LIT-636345) for more information.
Printing Summaries
Unlike the COS reports that have a variety of color choices, COS
summaries can be printed only in red or black. The capability to print
in red operates independently from the report logging described in the
previous section. Any printer that supports color and is installed in
Windows software with compatible Windows driver software can be
used to print the COS summaries in red. To enable the red printing,
add the following single parameter to the METASYS.INI file:
CossumPrintColor=1
See the Initialization Parameters Technical Bulletin (LIT-636345) for
the parameter settings.
33
Modifying COS Buffer
The COS buffer stores COS reports for printing. Two methods of
configuring the buffer are available: Buffer Size and Buffer Interval.
The print Buffer Size parameter specifies the number of COS reports
buffered before they are sent to the printer. The print Buffer Interval
parameter specifies the number of minutes the Metasys system waits
until the buffer is sent to the printer, regardless of the number of
messages in the buffer. See the Initialization Parameters Technical
Bulletin (LIT-636345) for the parameter settings.
You may configure up to four printers on an OWS for use at one time.
When the COS buffer is enabled, all printers on that OWS are
buffered. Each OWS has its own buffer; however, the same
initialization parameter is used for all.
General Modem Configuration
For a list of qualified modems, refer to the Computer Price List
(pcprices.doc) at The Advisor > Business Focus >
Purchasing/Strategic Procurement > ePurchasing > CG Computer
Purchasing.
Metasys Release 11.00 and later allows you to select a modem from a
list. All supported modem strings are located in MODEM.INI. The
new file is referenced for setting up either OWS or NCM modem
applications. The MODEM.INI file includes all modems currently
supported by Metasys software. New modems can be added in the
field as the need arises. The MODEM.INI file is located in the same
directory as METASYS.INI. The MODEM.INI file is also available at
The Advisor > Products Focus > Field Support Center > System
Reps > View files! Browse here > modem.ini. Refer to the
Initialization Parameters Technical Bulletin (LIT-636345).
Updating MODEM.INI
Occasionally a new set of modems supported by the Metasys Network
is available from The Advisor Web site. To update a particular
customer, copy the entire MODEM.INI from The Advisor and replace
the present MODEM.INI on the Metasys Release 11.00 or later job
site.
Note:
Any user-defined modems are lost during the updating
process.
34
Wiring—Modems
See the Configuring ISDN Modems detailed procedure and refer to the
connections below.
OWS to Modem
The external modem connects to the OWSs serial port (COM1 or
COM2) with an RS-232 cable. The pinouts for this cable depend on
the type of PC. Use the pinouts for your system.
Several machines support the 25-pin COM port.
25-pin COM Port
(male)
Modem
(male)
1
Shell
2
In
Out
2
FG
TD Black
In
3
RD Brown
3
Out
Out
4
RTS Red
4
In
In
5
CTS Orange
5
Out
In
6
DSR Yellow
6
Out
7
SG Green
7
8
DCD Blue
8
Out
18
Unused Violet
18
In
DTR White
20
In
In
Out 20
OWS-MOD
Note: If you are using the Multi-Tech Modem V32L
(discontinued), cut pin 18 at the modem end.
Figure 12: Cable between 25-pin COM Port and Modem
(Allied Part CON94-3870-10)
35
Most machines support the 9-pin COM port. Use a null modem cable
or prepare the RS-232 cable as shown in Figure 13.
9-pin COM Port
( female)
25-pin
Modem
(male)
In
1
2
In
In
2
3
Out
Out
3
4
In
Out
4
5
Out
COM
5
6
Out
In
6
7
Out
7
8
Out
In
8
20
In
In
9
22
Out
Shell
FG
Shell
PORT-MOD
Figure 13: Cable between 9-Pin COM Port and Modem
(Allied Part CON94-3690-10)
NCM to ISDN Modem
This section shows the cable for connecting the NCM (Port 2) to the
ADTRAN ISU Express. Use a standard modem cable or prepare the
cable as shown in Figure 14. For more information on NCM cables,
see the Network Control Module 200 Series Technical Bulletin
(LIT-636025) and the Network Control Module 300 Series Technical
Bulletin (LIT-6360251).
NCM
(DTE)
DB25 (male)
1
Out
2
In
3
Out
4
In
5
In
6
7
Out
20
FG
TD
RD
RTS
CTS
DSR
SG
DTR
ISDN Modem
(DCE)
DB25 (male)
Shell
2
In
3
Out
4
In
5
Out
6
Out
7
20
In
NCM-TERM
Figure 14: Cable between NCM200 Port 2
and ADTRAN ISU Express
36
Commissioning Overview
The commissioning process depends on whether this is a new or
existing job. This section provides an overview of the two processes.
If the OWS does not function properly after installation, refer to
Appendix F: Troubleshooting Chart at the end of this document.
Notes:
The information in this document is current as of its printing
date. For updates, refer to the Readme.ows and Install.ows
text files provided with the new release of the software.
Perform a PREP-FOR command before database restoration
or conversion to set up environment variables. Refer to
Appendix E: Database Conversion.
Commissioning a New Job
To commission a new job:
1.
Install the hardware: memory (RAM), ARCNET board, extra
serial boards, and mouse. Some of these steps are optional
depending on your system. Refer to the instructions for your
particular platform in the Commissioning Hardware section.
2.
Install the Metasys PMI software. PMI installation involves setup
steps (such as installing third-party software, if necessary). Refer
to the Commissioning Software: New Job section.
3.
Connect the OWS to the Metasys Network. Refer to the steps in
the Connecting and Configuring a Modem to an OWS detailed
procedure and the Wiring—Modem section.
Commissioning an Existing Job
Commissioning involves installing the new Metasys software release
over the old software release if:
•
this is an existing job
•
the hardware configuration is correct
•
the job does not use multiple direct connections
Refer to the Commissioning Software: Upgrading Existing Jobs
section.
However, if the job uses multiple direct connections, but additional
serial boards are not already installed on your system, you need to
install serial boards. In this case, refer to Extra Serial Boards in the
Commissioning Hardware section. Refer to the Commissioning
Software: Upgrading Existing Jobs section to install the Metasys
software.
37
Commissioning Hardware
Commissioning hardware can involve the installation of the following
equipment: memory, an NIC, extra serial boards, and a mouse.
Specific procedures may depend on the model and brand of equipment
being used.
Computer Platforms
The hardware required for an OWS may include added memory, an
NIC, extra serial boards, and a mouse. Refer to the Metasys
(LIT-12012) for the specific requirements of your system.
IMPORTANT: When installing hardware, follow anti-static
precautions.
!
CAUTION: Disconnect the computer from all AC voltage
sources before installing boards. Dangerous voltages in the power
supply and display monitor can be present.
Memory
Computers may require additional memory to run Metasys software. A
Single Inline Memory Module (SIMM) or expansion board provides
memory. Install the module or expansion board, referring to the
manufacturer’s literature for instructions.
Network Interface Card (NIC)
Note:
The following information does not apply to any portable
OWS that directly or remotely connects to an NCM.
The OWS requires an NIC to communicate on the N1 LAN. (The
OWS cannot operate without an NIC on the N1 LAN.) You can use
either an ARCNET card or an Ethernet card. This section includes
instructions for installing the ARCNET card. For details on installing
the Ethernet card, see the N1 Ethernet/IP Network Technical Bulletin
(LIT-6360175).
If you are experiencing problems with the ARCNET N1
communications, refer to Appendix G: ARCNET Troubleshooting for
troubleshooting tips.
Contemporary Control Systems, Incorporated (CCSI) is the supplier
for ARCNET Network Adapter cards. Their model number is
PCA66-CXB. The card is configurable for either 8-bit or 16-bit
operation and can be used in both the NU-NCM300/350 and the OWS.
When ordering an ARCNET Network Adapter card from
Johnson Controls Customer Service, use model number
NU-NET101-0. This model number applies to the preferred Network
Adapter card for this application. At this time, it applies to the
PCA66-CXB ARCNET interface card supplied by CCSI.
The PCA66-CXB is not a Plug and Play Network Interface card
(Figure 15) and requires manual setup in an OWS. There are sufficient
jumpers to allow the selection of Base Input/Output (I/O) Address,
Base Memory Address, and Interrupt Request line settings compatible
with the operation of all components within the OWS. Use the
suggestions shown in Table 9 and Table 10 as starting points. Each PC
configuration may need to be examined and have the suggested
settings changed in order to make the OWS function properly. Please
refer to the PCA66-CXB ARCNET interface card user manual
supplied by CCSI to determine alternate jumper setting combinations.
See Table 9 and Table 10 for suggested jumper and interrupt settings
when using the CCSI ARCNET PCA66-CXB in an OWS.
IOS0
IOS1
IOS2
ENROM
IOS0
IOS1
IOS2
MS0
MS1
Ms2
MS3
MS4
CCSI Arcnet PCA66, 16-bit
MS0
MS1
MS2
MS3
MS4
(Not installed)
Bayonet-Neill-Concelman (BNC)
Standard
R
Microsystems
Corporation
(SMC)
COM90C66
Boot ROM
(Not installed)
IRQ15
IRQ14
IRQ12
IRQ11
IRQ10
IRQ7
IRQ6
IRQ5
IRQ4
IRQ3
IRQ2/9
Dual Light-Emitting Diode (LED),
Yellow=Accessed
Green=Transmitting
Typically No
Connections
Used for bus speed
compatibility settings.
12 3 4 5 6 78
E4
BALE
IOCHRDY
OWS
MEMEN16B
38
Least Significant Bit (LSB)
Open = 1
Close = 0
Most Significant Bit (MSB)
ccsiarcnet
Figure 15: CCSI ARCNET Board
Node
ID
39
Table 9: Jumper Settings for the CCSI ARCNET PCA66-CXB in an OWS
Switch
Value
Base I/O
Address
SW1
2E0h
Base
Memory
Address
SW1
CC000h
Note:
Jumper Settings
MS0 MS1
MS2
On
On
MS3
On
MS4
Off
IOS0
IOS1
IOS2
On
Off
On
On
Address jumper must be On in order to create a logic zero.
Table 10: IRQ (Interrupt) Settings for the CCSI PCA66-CXB in an OWS
Value
Interrupt IRQ5
Interrupt Setting
2/9
3
4
5
6
7
10
11
12
14
15
Off
Off
Off
Jumper
Off
Off
Off
Off
Off
Off
Off
Extra Serial Boards
The following information does not apply to any portable platforms.
If you want the OWS to connect to multiple NCMs, additional serial
connections are required. The workstation supports up to three serial
connections: COM1, COM2, and COM3. Standard systems typically
provide COM1 and COM2. For COM3, install an ISA serial board.
(For ordering information, refer to Metasys Installation and Platform
Requirements Technical Bulletin [LIT-12012].)
Mouse
Install the mouse, referring to the mouse literature for detailed
installation instructions.
For the portable platforms, install the mouse into serial port COM1,
the dedicated mouse port. (Use serial port COM2 for direct or dial-up
connection to an NCM.) Other portable platforms may have either a
dedicated mouse port or a built-in track ball.
40
Commissioning Software: New Job
This section includes instructions on how to install Metasys PMI at a
new job. Before installing Metasys PMI software, make sure your
system meets the necessary prerequisites listed below.
Table 11: Operating System Compatibility
Windows
Version 3.1
Windows 95
OS
Windows 98
OS
Windows NT
OS
Windows
2000
Professional
Metasys
Release
8.0
X
X
X
Not
Recommended
Not
Recommended
9.0
X
X
X
Not
Recommended
Not
Recommended
10.00
Not
Recommended
X
X
X
Not
Recommended
11.00
Not
Recommended
Not
Recommended
X
X
Not
Recommended
12.00
Not
Recommended
Not
Recommended
X
X
X
Prerequisites
Before loading the Metasys PMI software, verify the following:
•
An earlier release of Metasys PMI software is not installed on this
machine. The file C:\FMS\BIN\MFG$$$. OWS should not exist. If
there is a previous installation, install the Metasys software as
described in the Commissioning Software: Upgrading Existing
Jobs section.
•
Windows Version 3.1 and Windows 95 OSs are no longer
supported.
IMPORTANT: If you upgrade from Windows 95 to Windows 98
software, you must back up any pertinent data,
specifically your Metasys system (c:\fms).
•
Windows 98, Windows NT, or Windows 2000 software is required
with the Metasys software. Follow the instructions for the
Windows version you are using. Do not set up your PC to perform
a dual boot. Use Windows 98, Windows NT, or Windows 2000
software on a single OWS.
41
•
Metasys PMI software should be installed directly on a newly
installed Windows 98 system. Upgrading from Windows 95
systems to a Windows 98 system is not recommended because
extraneous files are left on the system. Also, a known problem
with Superbase 4™ software exists when running
Metasys software on an upgraded Windows 98 system.
•
Screen savers on PCs running Metasys PMI software should be
disabled.
•
GPL requires 525 K of conventional memory.
•
To use the Enhanced Report Group feature, all NCMs must have a
minimum of 4 MB of RAM.
•
The OWS platform must have a Pentium processor.
•
Hard disk space requirements are listed below.
PMI (including Metalink) 43 MB
(Note 1)
GPL Software (Optional) 7.0 MB
(Note 2)
JC-BASIC (JCB) Software
(Optional) 7.0 MB
(Note 2)
GPL HVAC Library (HLIB) Software
(Optional) 5.0 MB
(Note 2)
Metasys Application Enabler (MAE) Software
(Optional) 34.0 MB
(Note 1)
Note 1: Of this number, the installation program temporarily uses
5 MB for the install. This 5 MB is returned to the system
when the install is complete.
1 MB (approximate) for the install. This 1 MB is returned to
the system when the install is complete.
•
If you are installing all packages (except MAE), the total disk
space requirement is 34 MB (approximate).
•
Make sure that you are using PKZIP/PKUNZIP Version 1.02.
Do not use PKZIP/PKUNZIP Version 2.04. PKZIP and PKUNZIP
are used with SAVEDB and RESTDB Move utilities.
PKZIP/PKUNZIP Version 2.04 is backward compatible and works
with files that have been zipped with Version 1.02, but
Version 1.02 is not forward compatible. Files zipped with
Version 2.04 cannot be unzipped with Version 1.02.
42
Setup
Setup instructions include:
•
Installing Windows software
•
Installing Micrografx Designer software (not supported at
Metasys Release 11.00 or later)
•
Installing Metasys PMI software
IMPORTANT: Metasys software has not been qualified with
Novell IntraNetware software. Several problems
have been documented when customers attempt to run
Novell IntraNetware with Metasys software.
Johnson Controls strongly advises that you isolate the
Metasys Network.
The following problems have been documented on
Windows NT machines when Novell IntraNetware is
installed.
1.
When you reboot the PC, the time is set back
one hour.
Workaround: Remove IntraNetware and use
Microsoft Client Service software.
2.
Environment variables and paths are no longer
set when you open a DOS window. You cannot
run DDL.
Workaround: Do not log into IntraNetware
before loading PMI (or see Workaround No. 1
above).
3.
Analog software object commands (AI, AD,
AOS) cause PC problems.
Workaround: Ensure Netfinity System
Management drivers are not installed. (See
Workaround No. 1 above.)
43
Installing Windows 2000/Windows NT Software
Install Windows 2000/Windows NT software before installing
Metasys PMI. See your Windows software manual for more
information. Install 2 (SP2) for Windows 2000 software. Install
Service Pack 6a (SP6a) for a Windows NT Version 4.0 workstation
and any hot fixes. You can download Service Pack 2 and
Service Pack 6a from the Microsoft Web site,
www.microsoft.com/downloads/.
Note:
Make sure the Windows 2000/Windows NT Workstation is
running error-free on an in-house network (if applicable),
prior to installing Metasys software.
Refer to Appendix H: Windows NT/Windows 2000 Details for backup
information.
Installing Windows 98 Software
Install Windows 98 software before installing the Metasys PMI.
Windows software requires 35 to 40 MB of disk space.
Note:
The swap file size is controlled by Windows software.
Before installing Windows software, if the following commands exist
in the Autoexec.bat file, remove them or temporarily cancel them.
See the DOS manual for instructions on canceling the commands.
APPEND, ASSIGN, JOIN, SUBST
These commands redefine drive letters or directory names and can
prevent proper installation. After Windows and Metasys software
installation, you may add these commands back to the Autoexec.bat
file.
Install Windows 98 software as described in the Windows manual.
Perform a custom installation so that you can install the Microsoft
Backup Utility required to back up your Metasys databases. The
Microsoft Backup Utility is found in the Disk Tools selection in the
Installation program. After installing Windows software, see the
Installing the Microsoft Backup Utility detailed procedure.
44
ARCNET Driver Conflict
While not recommended, some users run Metasys database
applications in a DOS window while keeping Metasys software active
on the OWS. If the OWS has the ARCNET drivers that come with
Windows software loaded (instead of the Metasys ARCNET drivers),
this can cause a serious network (N1) corruption. The typical Metasys
database applications performed are DDL, UNDDL, or GPL. This
ARCNET Driver conflict causes NCMs to randomly reset.
The solution is to remove the additional ARCNET driver added by
Windows software, and do not run Metasys database generation tools
such as GPL, UNDDL, and DDL while Metasys PMI is currently
active on the same workstation. See the Removing Additional Drivers
detailed procedure.
Installing Designer
Install Micrografx Designer 3.1 (plus OLE) or Micrografx DRAW
software (optional). The Micrografx Designer or DRAW program is
required to create Metasys graphics on the system.
Notes:
Micrografx Draw and Designer software are supported
through Release 10.02. Use M-Graphics and
M5 Workstation software with Metasys Release 11.00 or
later.
Micrografx Designer 4.0 is not compatible with Metasys
software. It is recommended that you do not use Micrografx
Designer 4.0 for Metasys graphics.
Install Micrografx Designer or Micrografx DRAW as
described in the manuals provided with the software. The
Micrografx Designer installation program asks whether you
want to install various options. The recommendations
follow:
Table 12: Designer Options
Micrografx Designer Installation Option Recommended for Metasys Software
Micrografx Designer
Yes
Adobe Type Manager (ATM)
No
TypeAlign
No
Outline Fonts
optional*
Drivers
No
Telegrafx
No
Translators
AutoCAD DXF File Translator only
Samples
No
Clip Art
No
*
Windows 95 software: If you are using Roman fonts, you must install outline fonts.
45
Since you are not installing most of the options, you may be using
only one (or two) of the Designer disks during installation.
The Micrografx Designer program is installed under the
C:\WINDOWS\DESIGNER directory.
If Micrografx Designer is installed before the OWS software
(as described in this document), the DESIGNER parameter is
automatically set to Yes in the METASYS.INI file and the Designer
path is added to the Autoexec path line. If Designer is installed after
the OWS software, you must change the DESIGNER parameter to Yes
in the METASYS.INI file, and add the path of the Designer files to the
path line in the Autoexec.bat file.
Installing M5 Workstation Release 1.1 or Later and
Metasys OWS Release 10.01 or Later Software on a Single
Platform
Because Metasys OWS Release 10.01 or later software and
M5 Workstation software deliver different versions of common
components, it is important to follow the proper sequence of
installation to alleviate problems with integration of these products on
a single platform.
M5 Workstation Release 1.1 or later software and Metasys OWS
Release 10.01 or later software can be installed in any order. However,
installing M5 Workstation Release 1.1 or later software over existing
OWS Release 10.01 or later software disables the Metasys
Release 10.01 Duty/Standby feature. Therefore, M5 Workstation
Release 1.1 or later and Metasys OWS Release 10.01 or later
Duty/Standby configurations must follow these steps:
1.
Install Metasys OWS Release 10.01 or later.
2.
Save the four Metasys OWS Release 10.01 or later files listed in
Table 13. These files are located in the FMSPATH\bin Directory.
Table 13: Metasys OWS File Names
File Name
Date
Time
Size
ASYNCH.EXE
11/3/99
1:11 A.M.
147,760 bytes
LINKMETA.DLL
11/3/99
1:11 A.M.
230,320 bytes
METAHOST.EXE
11/3/99
1:11 A.M.
80,208 bytes
METASRVR.EXE
11/3/99
1:11 A.M.
36,352 bytes
Note:
If the Metasys OWS release is later than 10.01, the dates, times, and
sizes may be different from those shown in Table 13. This is fine. Copy
and save the files.
3.
Install M5 Workstation Release 1.1 or later software.
4.
Restore the files saved in Step 2.
5.
Restart the computer.
46
Installing M5 Workstation Release 1.1 or Later, Metasys
OWS Release 10.01 or Later, and M-Web Release 2.0
Software on a Single Platform
Because Metasys OWS Release 10.01 or later software, M-Web
software, and M5 Workstation software deliver different versions of
common components, it is important that proper sequence of
installation be followed to alleviate problems with integration of these
products on a single platform.
We recommend installing these three products in the following order:
1.
Metasys OWS Release 9.01
2.
M-Web Release 1.0
Note:
If the Duty/Standby feature is required, archive the files
listed in Table 13. Install M5 Workstation Release 1.0.
Restore the files in Table 13.
3.
Metasys OWS Release 10.01 or later, or M-Web QuickPatch
Version 1.00, in any order.
4.
M-Web Release 2.0
5.
M5 Workstation Release 1.1 or later
Notes:
The recommended steps refer to product installation
sequencing only, and do not imply that all products are
required.
If Metasys OWS Release 9.01 software, M-Web Release 1.0
software, or M5 Workstation Release 1.0 software are
already installed, skip that installation step.
Begin new installations at Step 4, installing Metasys OWS
Release 10.01 or later software first. Then follow with
Steps 5 and 6.
Installing Metasys PMI Software
Verify all of the prerequisites above and perform all of the setup
activities, then continue with the Installing Metasys PMI Software:
New Job detailed procedure. Refer to the Metasys Installation and
Platform Requirements Technical Bulletin (LIT-12012).
The Metasys PMI software product includes Metalink and DDL
software. However, the PMI installation procedure does not install
standalone programs like the Graphic Programming Language (GPL).
Note:
Do not use screen savers on Metasys Workstations.
47
IMPORTANT: You must have administrative privileges to install
Metasys PMI software on a PC running a
Windows NT or Windows 2000 operating system. If
not, an error message appears and you cannot install
PMI. However, you can install all other products on
the CD.
Commissioning Software: Upgrading Existing Jobs
Upgrading involves making sure your system meets the prerequisites
for an upgrade, setting up your system for the upgrade, and installing
the upgrade software.
Note:
If upgrading multiple OWSs, upgrade the archive OWSs
first.
IMPORTANT: Do not modify Password or Report/Access Groups or
perform a global download during the upgrade process
(from the time the first OWS is upgraded until the last
NCM is downloaded) any time you upgrade from
Release 9.01 or earlier to Release 10.01 or later. Refer
to Appendix I: Connecting Metasys Release 9.01 OWS
to a Metasys Release 10.01 or Later Network in this
document.
Prerequisites
Before loading the Metasys PMI software, verify the following:
•
An earlier release of the PMI is already installed on this machine.
Check the revision number in the file C:\FMS\BIN\MFG$$$.
OWS. If this file does not exist, install Metasys software as a new
job. See the Commissioning Software: New Job section.
•
Windows 98, Windows NT, or Windows 2000 software is required
with Metasys software. Follow the instructions for the Windows
version you are using. Do not set up your PC to perform a dual
boot. Use Windows 98, Windows NT, or Windows 2000 software
on a single OWS.
•
The PMI software should be installed directly on a newly installed
Windows 98 system. Upgrading from Windows 95 systems to a
Windows 98 system is not recommended because extraneous files
are left on the system. Also, a known problem with Superbase 4
software exists when running Metasys software on an upgraded
Windows 98 system.
IMPORTANT: If an attempt is made to upgrade from Windows 95 to
Windows 98 software, you must back up any pertinent
data, specifically the Metasys system (c:\fms).
48
•
Hard disk space requirements are listed below.
PMI (including Metalink) 43 MB
(Note 1)
GPL Software (Optional) 7.0 MB
(Note 2)
JCB Software (Optional) 7.0 MB
(Note 2)
HLIB Software (Optional) 5.0 MB
(Note 2)
MAE Software (Optional) 34.0 MB
(Note 1)
5 MB for the install. This 5 MB is returned to the system
when the install is complete.
1 MB (approximate) for the install. This 1 MB is returned to
the system when the install is complete.
If you are installing all packages (except MAE), the total disk space
requirement is 34 MB (approximate).
If you are upgrading all packages (except MAE), the total additional
disk space requirement must be available. Check the following:
•
All NCMs must have a minimum of 4 MB of RAM to use the
Enhanced Report Group feature.
•
Make sure you are using PKZIP/PKUNZIP Version 1.02.
Do not use PKZIP/PKUNZIP 2.04. PKZIP and PKUNZIP are used
with SAVEDB and RESTDB Move utilities. PKZIP/PKUNZIP
Version 2.04 is backward compatible and works with files zipped
with Version 1.02, but Version 1.02 is not forward compatible.
Files zipped with Version 2.04 cannot be unzipped with
Version 1.02.
Setup
The following actions must be performed before upgrading the PMI
software:
1.
Command all Demand Limiting Load Rolling (DLLR) load group
objects to Monitor Only.
2.
Upload all NCMs that are archived at this OWS. To upload an
NCM, select an NCM on the Network Map, go to the Action
menu, and select NC Upload to Archive PC.
3.
Verify that this OWS contains all models necessary to download
the NCMs archived on this OWS.
4.
Archive trend and totalization data, if desired.
5.
Verify that no global data items have been changed within the past
10 minutes. If a global data item has been changed, wait
10 minutes for global synchronization to propagate through the
network.
49
6.
Connect to each dial-up network on the system so that its global
database synchronizes with the OWS global databases. You may
disconnect after synchronization.
7.
Upload global data for each network. Use the Action menu on the
Network Map to upload the global data.
8.
Do not change any global data items or perform a global
download until instructed below.
9.
From the Network Map Exit menu, select Program Manager.
Select No when you are asked whether you want to keep the BAS
running. Terminate any other programs that might be running.
10. Back up the uploaded database. See the Move Utility Technical
Bulletin (LIT-636110) for instructions.
11. Clearly label the backup and store it.
12. Back up Metasys data and load Windows software before
upgrading the Metasys software if you are upgrading the
Windows version and are also installing Metasys software. Refer
to the Prerequisites section.
Installing Metasys PMI Software
Note:
If you are installing over Metasys Release 5.2 or earlier
software, a database conversion is required. The conversion
takes place automatically toward the end of the install
program. Follow the onscreen instructions given for the
conversion. Refer to Appendix E: Database Conversion for
further information on the archive database conversion.
Verify all of the prerequisites above and perform all of the setup
activities, then continue with the Installing Metasys PMI Software:
Upgrading Existing Job detailed procedure. Refer to the Metasys
(LIT-12012).
The Metasys PMI software product includes Metalink software and
DDL software. However, the PMI installation procedure does not
install standalone programs like the Graphic Programming Language
(GPL).
Note:
the CD.
50
Detailed Procedures
Direct Connecting to N1 LAN – Ethernet Network
To direct connect to N1 LAN - Ethernet Network (Refer to Figure 4.):
1.
Connect the Ethernet cable to the NIC. (The OWS cannot operate
without an NIC on the N1 LAN.) Follow the network installation
requirements for the selected Ethernet media.
Notes:
If the NCM is configured for an Ethernet connection, always
have the NIC installed in the NCM.
If you have a printer, connect the printer cable to the parallel
or serial port on the OWS.
2.
Connect the keyboard, monitor, and mouse to the appropriate
ports on the workstation.
Note:
After making the physical connection and turning on the
workstation, the initialization and connection process begins.
A message window appears on the workstation screen
displaying the status of the connection. Do not close this
message window (by double-clicking the Control menu
box), unless you want to cancel the connection. Closing the
window cancels the connection.
Direct Connecting to N1 LAN – ARCNET Network
To direct connect to N1 LAN - ARCNET Network (Refer to Figure
4.):
1.
Install a T-connector into the port of the workstation’s NIC.
(The OWS cannot operate without an NIC on the N1 LAN.)
2.
Connect the N1 LAN cable to one end of the T-connector. If the
workstation is at the end of line, connect a 93 ohm terminator cap
to the other end of the T-connector. If the workstation is not at the
end of line, connect the other segment of N1 LAN cable (that goes
to the next node) to the T-connector.
Note:
3.
If you have a printer, connect the printer cable to parallel or
serial port on the OWS.
Note:
51
Direct Connecting to NCM
To direct connect to NCM (Refer to Figure 5 and Figure 6.):
1.
If you are connecting one NCM to the OWS, connect a cable from
the RS-232 submodule or port on the NCM to the serial port on
the OWS. The cable pinouts vary depending on which RS-232
port and which PC you are using. Refer to the Network Control
Module 200 Series Technical Bulletin (LIT-636025) and Network
Control Module 300 Series Technical Bulletin (LIT-6360251).
If you are connecting two, three, or four NCMs to the OWS,
connect each cable from the RS-232 submodule or port on the
NCM to an available COM port on the OWS.
Note:
2.
If you have a printer, connect the printer cable to the parallel
or serial port on the OWS.
Note:
Dial-up Connecting to NCM - with Modem
To dial-up connect to NCM - with modem (Refer to Figure 8.):
1.
If you are using the internal modem submodule at the NCM,
install the modem into the NCM’s second submodule port.
If you are using an external modem at the NCM, connect the
RS-232 cable from the modem to the NCM’s RS-232 submodule.
Make sure the cable screws are fastened.
52
2.
If you are using an external modem at the workstation, connect
the RS-232 cable from the modem to the serial port on the OWS.
Refer to the Wiring—Modems section in this document for the
cable’s configuration.
If you are using the internal modem at the portable workstation,
install the modem in the system unit.
3.
Connect the modems to the telephone line.
Note:
4.
If you have a printer, connect it to the OWS.
Connect the keyboard, monitor, and mouse to the workstation.
Note:
The NCM makes multiple connections and disconnections
during a download from a dial-up PC. When the PC initiates
a download to the NCM, the PC calls the NCM, establishing
the connection, and the NCM terminates the connection. The
NCM calls the PC back, the code is downloaded, and the
NCM terminates the connection again. Finally, the NCM
calls the PC back (re-establishing the connection) and the
data is downloaded. When the NCM initiates the connection
(for example, for a reset), the NCM dials the PC, establishing
the connection, and the code is downloaded. Then the NCM
terminates the connection, calls the PC back (re-establishing
the connection), and the data is downloaded.
Dial-up Connecting to NCM - with ISDN
To dial-up connect to NCM - with ISDN (Refer to Figure 9.):
1.
Connect the RS-232 cable from the modem to the NCM’s RS-232
submodule port. Make sure the cable screws are fastened.
2.
Connect the RS-232 cable from the modem to the serial port
(COM1 or COM2) on the OWS. Refer to the Wiring—Modems
section in this document for the cable’s configuration.
3.
Connect the modems to the ISDN lines (following the instructions
provided with the adapter).
Note:
4.
If you have a printer, connect it to the OWS.
Note:
53
The NCM makes multiple connections and disconnections
during a download from a dial-up PC. When the PC initiates
a download to the NCM, the PC calls the NCM, establishing
the connection, and the NCM terminates the connection. The
NCM calls the PC back, the code is downloaded, and the
NCM terminates the connection again. Finally, the NCM
calls the PC back (re-establishing the connection) and the
data is downloaded. When the NCM initiates the connection
(for example, for a reset), the NCM dials the PC, establishing
the connection, and the code is downloaded. Then the NCM
terminates the connection, calls the PC back (re-establishing
the connection), and the data is downloaded.
Adding a Windows Printer in Windows 98 Software
Note:
Use standard Windows procedures to add a printer to each
OWS that should have a printer for the entire system.
To add a Windows printer in Windows 98 software:
1.
From the Start menu, select Settings > Printers. The Printers
dialog box appears.
2.
Double-click the Add Printer icon. The Add Printer Wizard dialog
box appears. Click Next.
3.
Select the Local printer option when a dialog box displays asking
how the printer should be attached: Local printer or Network
printer. Click Next.
4.
Select the manufacturer and model of the printer. Click Next.
5.
Select the port you want to use (usually LPT1). Click Next.
6.
Enter the printer name. The default printer name is usually fine.
Click Next.
7.
Print a test page to confirm you have a valid connection. Click
Finish. The driver is now loaded on the OWS.
8.
Repeat the steps above for every printer type installed on the
Metasys Network.
54
Adding a Windows Printer in Windows NT/2000 Software
Note:
Use standard Windows procedures to add a printer to each
OWS that should have a printer for the entire system.
To add a Windows printer in Windows NT/2000 software:
1.
From the Start menu, select Settings > Printers. The Printers
dialog box appears.
2.
Double-click the Add Printer icon. The Add Printer Wizard dialog
box appears asking how the printer should be managed: My
Computer or Network printer server. Select My Computer and
click Next.
3.
Select the port you want to use (usually LPT1). Click Next.
4.
Select the manufacturer and model of the printer. Click Next.
Note:
If the driver already exists on the computer, you may be
asked if you wish to keep the existing driver. Select the
Replace existing driver option. Always selecting this option
ensures any invalid drivers are overwritten.
5.
Enter the printer name. The default printer name is usually fine.
Click Next.
6.
Select the Not shared option when prompted to answer if you wish
to share the printer. Click Next.
7.
Print a test page to confirm you have a valid connection. Click
Finish. The driver is now loaded on the OWS.
8.
Repeat the steps above for every printer type installed on the
Metasys Network.
Adding a Generic/Text-only Printer
Note:
The Generic/Text-only printer supports file printing. Install
the Windows Generic/Text-only printer on every OWS after
you finish adding all physical printers.
To add a generic/text-only printer, use the procedure described above
for adding Windows printers.
Adding an IBM Proprinter Device for NCM Printing
To add an IBM Proprinter device for NCM printing:
1.
Use the procedure described above for adding Windows printers.
2.
Use the Windows Printer Settings option to change (rename) the
printer IBM Proprinters devices. The s in Proprinters devices is
required to ensure successful NCM printing.
Note:
55
The preceding procedure is essential for any Windows NT or
Windows 2000 OWS needing to print to NCM printers, but
we strongly recommend that you follow the same technique
for all OSs.
IMPORTANT: Always reboot the PC when you finish making
changes to the Windows Printer configuration.
Configuring Metasys Workstations for Printers
Note:
You must configure the individual Metasys printer objects
after installing the Windows Printers on all Metasys
workstations. Each OWS with a physical printer connected
must undergo this configuration process.
To configure Metasys workstations for printers:
1.
Make the connected printer the default Windows printer.
2.
Rename this printer with the appropriate Metasys printer object
name. The name is often LP-xxx (xxx=the OWS number). For
example, if the OWS is OWS-214, then the printer may be called
LP-214.
3.
Print a Windows printer test page for the default Windows printer
and note the three required parameters: Windows Printer Name,
Windows Printer Driver, and PC Port Address. The values for
these parameters are needed later in the Metasys Printer Focus
window.
Windows 98 Printer Test Page
Extract the values for the three parameters listed in Step 3 above from
the Windows 98 printer test page as shown by the bold print below:
Printer name: LP-214
Printer model: IBM Proprinter III
Driver name:
PROPRINT.DRV
Driver version:4.00
Color support: No
Port name:
LPT1:
Data format:
EMF
The three required parameters with their values in this example are:
Windows Printer Name:
LP-214
Windows Printer Driver:
PROPRINT
PC Port Address:
LPT1:
56
Windows NT Printer Test Page
the Windows NT printer test page as shown by the bold print below:
Machine name: OWS-214
Printer model: IBM Proprinter III
Color support: No
Port name:
LPT1:
Data format:
RAW
Share name:
Location:
Comment:
Driver name:
RASDD.DLL
Data file:
PROPRINT.DLL
Config file:
RASDDUI.DLL
Driver version:4.01
Environment:
Windows NT x86
LP-214
PROPRINT
PC Port Address:
LPT1:
Windows 2000 Printer Test Page
the Windows 2000 printer test page as shown by the bold print below:
Machine name: OWS-244
Printer model: HP DeskJet 890C
Color support: Yes
Port name(s): LPT1:
Data format:
RAW
Share name:
Driver name:
UNIDRV.DLL
Data file:
HPDJ890C.GPD
Config file:
UNIDRVUI.DLL
Help file:
UNIDRV.HLP
Driver version:5.0
Environment:
Windows NT x86
LP-244
HPDJ890C
PC Port Address:
LPT1:
Figure 16 shows typical settings after this stage.
57
Figure 16: Typical Screen after Renaming the
Default Windows Printer
Note:
4.
If the Metasys printer object does not already exist, add the
printer object as described in the Operator Workstation
User’s Manual.
In the Metasys Printer Focus window, set the Windows Printer
Driver Name field to the printer driver obtained during Step 3 of
this procedure. In Figure 17, the Windows Printer Driver Name
has been set to PROPRINT.
58
Direct connect PC Printer Focus
Item
Edit
View
Action
Go To
X
Accessory
Help
Status
Object Name
LP-214
Expanded ID
OWS-214 PRINTER
offline
Hardware
Graphic Symbol #
Operating Instr. #
0
Connection Type
PC-DIRECT
Default Report
0
PC Name
OWS-214
Destination
PC Port Address
LPT1
Baud Rate
Windows Printer - Driver Name:
PROPRINT
Windows Printer - Printer Name:
LP-214
Print9
Figure 17: Example Metasys Focus Window
5.
In the Metasys Printer Focus window, set the Windows Printer
Name to the Windows Printer Name obtained during Step 3 in this
procedure. Figure 17 shows the Windows Printer Name is LP-214.
6.
Save and close the Metasys Printer Focus window. Once the
information is updated across the network, you can print to this
device from any location in the network. Because this information
is global data, it is not complete until all printers are configured.
Fixing Line Feed Problems When Using a Serial Printer
Note:
If you are using a serial printer and are having line feed
problems after setting up your printers, try changing the
Printer Settings in the Properties dialog box.
To fix line feed problems when using a serial printer:
1.
From the Start menu, select Settings and then select Printers. The
Printers dialog box appears.
2.
Right-click on the icon for the printer and select Properties.
3.
Click the Details tab.
59
Figure 18: Properties Dialog Box with Details Tab Showing
4.
Click the Spool Settings button to display the Spool Settings
dialog box.
60
?
Spool Settings
X
Spool print jobs so program finishes printing faster
Start printing after last page is spooled
Start printing after first page is spooled
Print directly to the printer
Spool data format:
RAW
Enable bi-directional support for this printer
Disable bi-directional support for this printer
OK
Cancel
Restore Defaults
Print14
Figure 19: Spool Settings Dialog Box
5.
Select the Print directly to the printer option and click OK to
return to the Properties dialog box (Figure 19).
Note:
If you still have problems, and the printer is on a COM port,
skip to Step 11. If it is not on a COM port, try these
additional steps.
6.
Click the Port Settings tab to display the Port Settings dialog box.
7.
Click the Advanced button to display the Advanced Port Settings
dialog box.
X
Advanced Port Settings
Use FIFO buffers (requires 16550 compatible UART)
OK
Select lower settings to correct connection problems.
Select higher settings for faster performance.
Cancel
Receive Buffer: Low (1)
High (14)
Transmit Buffer: Low (1)
High (16)
Defaults
Print15
Figure 20: Advanced Port Settings Dialog Box
8.
Click and drag the Receive Buffer and Transmit Buffer settings to
Low 1 (Figure 20).
9.
Click OK to save the settings and return to the Port Settings dialog
box.
10. Click OK to return to the Properties dialog box.
61
11. Click OK to close the Properties dialog box and save all settings.
Note:
If your printer is on a COM port, look at the COM port status
by viewing the Communications Port Properties dialog box.
From the Start menu, choose Settings and Control Panel.
12. From the Control Panel dialog box, double-click on the System
icon. The System Properties dialog box appears.
13. Choose the Device Manager tab. See Figure 21.
System Properties
General
?
Device Manager
Hardware Profiles
View devices by type
X
Performance
View devices by connection
Computer
Disk drives
Display adapters
Floppy disk controllers
Hard disk controllers
Keyboard
Monitor
Mouse
Network adapters
3Com EtherLink III ISA (3C509/3C509b) in ISA mode
X Novell IPX Monolithic Driver
Ports (COM & LPT)
Communications Port (COM1)
Communications Port (COM2)
Printer port (LPT1)
System devices
Properties
Refresh
Remove
Print...
OK
Cancel
Devmgr
Figure 21: Device Manager Tab
14. Select Ports (COM and LPT). The list of ports appears
underneath.
15. Select the appropriate COM port and press the Properties button.
62
Figure 22: Communication Properties Dialog Box
16. Look under the Device status section on the screen for additional
troubleshooting information.
Configuring a Printer for Change-of-State (COS) Reports
Note:
You cannot use an OWS serial printer with Windows NT or
Windows 2000 software for COS reports.
To configure a printer for COS reports:
1.
Install the printer in both Windows and Metasys software as
described in the detailed procedures: Adding a Windows Printer in
Windows 98 Software or Adding a Windows Printer in Windows
NT/2000 Software.
2.
Identify the Windows Printer Name from the test page as
described in the Configuring Metasys Workstations for Printers
detailed procedure.
Notes:
63
If a printed report looks fine, the condensed code is set
correctly. If a printed report contains garbled text, the
condensed code is incorrect. Refer to the literature that
comes with your printer to find the code for condensed print.
If the printer requires more than one code, separate each with
a comma on the same line. Add the following line under the
[METASYS] section of the METASYS.INI file. See the
Initialization Parameters Technical Bulletin (LIT-636345).
<Windows Printer Name>=<condensed code char num>
[,<condensed code char num>]
For example, if your Metasys Printer Name is LP-217 and
the condensed code is 10, the statement is:
LP-217=10
For HP DeskJet series printers, the escape sequence for
condensed printing is as follows:
LP-217=27,40,115,49,52,72
where LP-217 is the Windows Printer Name identified
above.
3.
Update the following statement in the [METASYS] section of the
METASYS.INI file (by changing the 0 to 1) if you want to turn
off the automatic form feed at the beginning of every summary:
DisableFormFeed=1
Connecting and Configuring a Modem to an OWS
To connect and configure a modem to an OWS:
1.
Connect a straight-through cable between the modem and
workstation. To avoid disconnection, make sure the cable
jackscrews are fastened.
2.
Select PC Configuration. Figure 23 shows the PC Configuration
screen with the Modem Setup button.
64
NETWORK MAP - PC Configuration
COM1
COM2
COM3
Device Type
Baud Rate
NC Dial[modem]
1200
19200
NC Direct
2400
28800
Printer
4800
38400
Mouse
9600
57600
NC Dial[ISDN]
14400
OK
Cancel
Modem
Setup
Baud Rate
Device Type
NC Dial[modem]
1200
19200
NC Direct
2400
28800
Printer
4800
38400
Mouse
9600
57600
NC Dial[ISDN]
14400
Device Type
Baud Rate
NC Direct
1200
9600
28800
2400
14400
38400
4800
19200
57600
1200
9600
28800
LPT1
2400
14400
38400
LPT2
4800
19200
57600
COM4
Device Type
Baud Rate
NC Direct
pcConfig
Figure 23: PC Configuration Screen
3.
Select the Modem Setup button and the Modem Setup-PC
Configuration dialog box appears (see Figure 24). The dialog box
shows a communication port selection and a drop-down list box
selection that displays a list of currently supported modems.
MODEM SETUP - PC Configuration
Modem Port
OK
COM1
COM2
Cancel
Practical Peripherals PM144MT II External
modemselc
Figure 24: Modem Setup-PC Configuration Dialog Box
4.
Select a communication port and a modem brand from the list
box, and click OK to copy the selected modem setup string from
the MODEM.INI file to the correct spot in the METASYS.INI
file.
Note:
65
After restarting the OWS, the modem is initialized with the
desired setup string.
Connecting and Configuring a Modem to an NCM
To connect and configure a modem to an OWS:
1.
Connect a straight-through cable between the modem and the
terminal. To avoid disconnection, make sure the cable jackscrews
are fastened.
2.
Use WNCSETUP and the Write Modem operation. Selecting
Write Modem produces a dialog box similar to the one described
above for the OWS. See the NCSETUP for Windows Technical
Bulletin (LIT-6360251d) for details on Write Modem.
Adding User-defined Modems
Note:
If the brand modem you are using is not listed, you may add
the new modem to the MODEM.INI file. The file is located
in the same directory as the METASYS.INI file.
To add user-defined modems:
1.
Under the [OWS] section in the METASYS.INI file, find the User
Defined Modem entry as shown in Figure 25 and create a new
modem string definition by following the same format as the other
modem definitions. See Figure 25. The first line contains an
asterisk followed by the modem name. The second and third lines
contain the modem initialization string following the equal
(=) sign.
For OWS modem entry:
*ZOOM 56k External
SetCom1ModemProfile=AT&FE0V0X3M1W0S0=1S109=0&C1&D2&Q5&W0&Y0
SetCom2ModemProfile=AT&FE0V0X3M1W0S0=1S109=0&C1&D2&Q5&W0&Y0
*Practical Peripherals PM144MT II External
SetCom1ModemProfile=AT&FE0V0X3M1W0S0=1&C1&D2&W0&Y0
SetCom2ModemProfile=AT&FE0V0X3M1W0S0=1&C1&D2&W0&Y0
*User Defined Modem
SetCom1ModemProfile=REPLACE THIS LINE WITH YOUR STRING
SetCom2ModemProfile=REPLACE THIS LINE WITH YOUR STRING
Figure 25: Example of Excerpt from MODEM.INI File
Notes:
While editing this section, remember to insert the new
modem so a User-defined modem line still appears in the list
box.
If using V.90 modems with V.34 modems, add S109=0 to
the AT modem string. Insert it immediately after S0=1 in the
modem string.
66
Configuring ISDN Modems
Note:
The procedure for configuring an ADTRAN ISU Express is
the same as the other modems.
To configure ISDN modems (ADTRAN ISU Express):
1.
Connect a cable between the ADTRAN and either the OWS or the
NCM. For the OWS or NCM200, use a 25-pin cable. The cable
for a 25-pin COM port is shown in Figure 12 for the OWS and
Figure 30 for the NCM. Use a 9-pin cable for the NCM300 and
NCM350. The cable for a 9-pin COM port is shown in Figure 13.
2.
Start Windows on your OWS and use the terminal emulation
program to configure the ADTRAN ISU Express.
3.
Set up a HyperTerminal session when using Windows software.
The HyperTerminal wizard prompts you for a session name, a
communication connection type (referred to as a connector
[Table 14]), and the rest of the communication parameters. Use
the settings in Table 14. Following the configuration process,
Windows prompts you to save the session.
Table 14: HyperTerminal Parameters
Parameter
Setting
Baud Rate
19,200
(The baud rate must match the bit rate on the PC/NCM
configuration screen.)
Data Bits
8
Stops Bits
1
Parity
None
Flow Control
None
Connector
COM1 or COM2 (depends on current connection)
4.
Type the following commands to program the adapter. Press Enter
after each command. Note that these commands use the
number 0 (zero), not the letter O.
After typing the first line and pressing Enter, OK appears below
the line you have just typed. When you press Enter after typing
the last line, a 0 overwrites the first character of the line.
AT&F
<Enter>
ATV0E0&W
<Enter>
5.
67
Type AT!V. The ADTRAN PC or NCM configuration menu
appears as shown below. Verify that your settings match those in
the figures.
Note:
Lines 4 and 6 on the PC Configuration Menu show the phone
number of the OWS. Line 4 shows the phone number with
the area code and extension. Line 6 shows the phone number
without the area code. See Figure 26.
ISU Express Configuration Menu (PC)
1) NETWORK options = Dial Line 17) CTS Options = Follows RTS
2) Switch Protocol = DMS-100
18) CD Options = Normal
3) Call type = Data 64Kbps
19) DTR Options = Idle when
Off
4) SPID 1 = 41422727040111
20) DSR Options =DSR forced
on
5) SPID 2 =
21) Flow Control = Hardware
Flow
6) LDN 1 = 2272704
22) Data Bits = 8 Data Bits
7) LDN 2 =
23) Parity Bits = None
8) Dial options = AT commands
24) Stop Bits = 1 Stop Bit
9) Auto answer = Disabled
25) PROTOCOL = v.120
10) Answer tone =
26) QUICK Setup
No Answer tone
11) Connect Timeout =
30 sec (def)
12) Call Screening =
Answer any
13) Call Routing =
All types->DTE
14) DTE options = Asynchronous
15) Bit Rate = 19200
16) RTS Options = 1 ms delay
Figure 26: ADTRAN Configuration for PC
68
Note:
Lines 4 and 6 on the NCM Configuration Menu below show
the phone number of the NCM. Line 4 shows the phone
number with the area code and extension. Line 6 shows the
phone number without the area code. See Figure 27.
ISU Express Configuration Menu (NCM)
1) NETWORK options = Dial
17) CD Options = Normal
Line
2) Switch type = DMS-100
18) DTR Options = Idle when
Off
3) Call type = Data 64Kbps
19) DSR Options = Off idle +
test
4) SPID 1 = 41422727020111
20) Flow Control = Hardware
Flow
5) SPID 2 =
21) Data Bits = 8 Data Bits
6) LDN 1 = 2272702
22) Parity Bits = None
7) LDN 2 =
23) Stop Bits = 1 Stop Bit
8) Dial options = AT commands 24) PROTOCOL = v.120
9) Auto answer = Enabled
25) QUICK Setup
10) Answer tone = No Answer
tone
11) Connect Timeout = 30 sec
(def)
12) Call Screening = Answer
any
13) DTE options =
Asynchronous
14) Bit Rate = 19200
15) RTS Options = 1 ms delay
16) CTS Options = Follow RTS
Figure 27: ADTRAN Configuration for NCM
The ADTRAN ISU Express is programmed. Repeat Steps 1 through 4
for each adapter.
Installing the Microsoft Backup Utility
Note:
You must install Windows software before installing the
Microsoft Backup Utility.
To install the Microsoft Backup Utility:
1. Click the Start button on the Windows taskbar. The Start menu
appears.
2. Click the Settings - Control Panel menu option. The Control Panel
appears.
3. Double-click the Add/Remove Programs icon in the Program
Manager. The Add/Remove Programs Properties dialog box
appears.
69
4. Click the Windows Setup tab to bring it to the front of the dialog
box (Figure 28).
Refer to Appendix H: Windows NT/Windows 2000 Details for backup
information.
?
Add/Remove Programs Properties
Install/Uninstall
Windows Setup
X
Startup Disk
To add or remove a component, click the check box. A shaded box
means that only part of the component will be installed. To see
what’s included in a component, click Details.
Components:
Accessibility Options
0.4 MB
Accessories
4.2 MB
Communications
0.7 MB
Disk Tools
0.0 MB
Microsoft Exchange
4.6 MB
Space required:
1.6 MB
Space available on disk:
40.4 MB
Description
Includes options to change keyboard, sound, display, and
mouse behavior for people with mobility, hearing and visual
impairments.
Details...
1 of 1 components selected
Have Disk...
OK
Cancel
Apply
setup
Figure 28: Add/Remove Programs Properties Dialog Box
with Windows Setup Tab in Front
70
5.
Click the check box next to Disk Tools and click the Details
button to display the Disk Tools dialog box (Figure 29).
X
Disk Tools
To add or remove a component, click the check box. A shaded
box means that only part of the component will be installed. To see
what’s included in a component, click Details.
Components:
Backup
1.2 MB
2.7 MB
40.0 MB
Space required:
Space available on disk:
Description
Program to backup and save data and files. Supports backup
to floppy and tape drives.
Details...
Details...
OK
Cancel
Disktol
Figure 29: Disk Tools Dialog Box with Backup Selected
6.
Click the check box next to the Backup Utility to select it and
click OK. The dialog box closes and you return to the
Add/Remove Programs Properties dialog box.
Removing Additional Drivers
Note:
Remove additional drivers if the OWS has the ARCNET
drivers that come with Windows software loaded (instead of
the Metasys ARCNET drivers) because this can cause a
serious network (N1) corruption.
To remove additional drivers:
1.
In the Windows Control Panel, double-click the Network icon.
2.
Select the Configuration tab.
3.
Select an ARCNET driver.
4.
Click Remove (Figure 30).
Figure 30: Network Dialog Box
5.
Repeat Steps 3 and 4 for all ARCNET drivers.
6.
Reboot the PC.
Metasys Release 9.01 or later software provides the EnaArcChk
parameter to test for non-Metasys ARCNET drivers. For details, see
the Initialization Parameters Technical Bulletin (LIT-636345).
71
72
Installing Metasys PMI Software: New Job
Notes:
Verify all of the prerequisites in the Commissioning
Software: New Job section and perform all of the setup
activities, then continue with the installation steps below.
the CD.
To install Metasys PMI software (new job):
1. Keep Windows software running and close all other applications
(for example, Metalink software and MS Office).
2. Insert the Metasys CD into the CD-ROM drive.
3. Click the Start button on the Windows taskbar. The Start menu
appears.
4. Click the Run menu option. The Run dialog box appears.
5. Type d:/Setup in the Open box and press Enter. Use the
appropriate drive letter for the CD-ROM drive. For example, if the
CD-ROM is using Drive E, enter e:/Setup instead of d:/Setup.
6. Click on the appropriate check box to select the software you want
to install.
7. Select whether you want the program to automatically update your
Autoexec.bat file, or whether you want to update it yourself later.
If you select to have the file automatically updated, the changes are
made directly to the Autoexec.bat file.
Note:
If you select to not have the file updated automatically, the
Autoexec.bat file is not changed. Instead, a new file
containing the necessary changes is created. This file is
named Autoexec.jci. It is your responsibility to add the
necessary changes to the Autoexec.bat file at a later time.
These changes are required for Metasys to operate. If you are
installing additional software, you must make these changes
and reboot the PC before installing other software.
8. Select to reboot the PC.
Note:
Some PCs may not automatically reboot. If a reboot does not
occur within ten seconds after clicking the reboot button,
manually reboot the PC by pressing Ctrl\Alt\Del or by
cycling power.
73
9. In the Logon dialog box, type METASYS, the default password, or
type the password appropriate for the restored database to log on
the network. If you wait too long, the slide show program begins to
run. If this happens, press any key to return to the Logon dialog
box.
The Metasys PMI installation is complete. You may now use the OWS
functions. For instructions, refer to the Operator Workstation User’s
Manual.
Note:
The install process creates four temporary files. These may
not be automatically deleted from the hard drive. Check both
the WINDOWS and the TEMP directories for these files,
and delete them. (The TEMP directory location depends on
the directory specified by the TEMP environment variable).
The files that may be created are:
~INS0163.~MP
~INS0363.~MP
~INS0463.~MP
~INS0762.LIB
Installing Metasys PMI Software: Upgrading Existing Job
Notes:
If you are installing over Metasys Release 5.2 or earlier
software, a database conversion is required. The conversion
takes place automatically toward the end of the install
program. Follow the onscreen instructions given for the
conversion. Refer to Appendix E: Database Conversion for
further information on the archive database conversion.
Verify all of the prerequisites in the Commissioning
Software: New Job section and perform all of the setup
activities, then continue with the installation steps below.
the CD.
74
To install Metasys PMI software (upgrading existing job):
1.
Keep Windows software running and close all other applications
(for example, Metalink software and MS Office).
2.
Insert the Metasys CD into the CD-ROM drive.
3.
Click the Start button on the Windows taskbar. The Start menu
appears.
4.
Click the Run menu option. The Run dialog box appears.
5.
Type d:/Setup in the Open box and press Enter. Use the
appropriate drive letter for the CD-ROM drive. For example, if
the CD-ROM uses Drive E, enter e:/Setup instead of
d:/Setup.
6.
Click on the appropriate check box to select the software you want
to install.
7.
Select whether you want the program to automatically update your
Autoexec.bat file, or whether you want to update it yourself later.
If you select to have the file automatically updated, the changes
are made directly to the Autoexec.bat file.
Notes:
If you select to not have the file updated automatically, the
Autoexec.bat file is not changed. Instead, a new file
containing the necessary changes is created. This file is
named Autoexec.jci. It is your responsibility to add the
necessary changes to the Autoexec.bat file at a later time.
These changes are required for Metasys software to operate.
If you are installing additional software, you must make
these changes and reboot the PC before installing other
software.
A database conversion automatically occurs when upgrading
from Metasys Release 5.2 software or earlier. Follow the
onscreen instructions given for the conversion. Do not
interrupt the conversion. Refer to Appendix E: Database
Conversion for further information.
8.
Select to reboot the PC.
Note:
9.
Some PCs may not automatically reboot. If a reboot does not
occur within ten seconds after clicking the reboot button,
manually reboot the PC by pressing Ctrl/Alt/Del or by
cycling power.
Cancel the Metasys software load on Windows startup.
75
10. Verify that the Autoexec.bat file contains all the lines shown in
the sample files provided in Appendix A: Autoexec.bat and
Config.sys Files.
For information on the WIN.INI, METASYS.INI and
SYSTEM.INI file parameters, refer to the Initialization
Parameters Technical Bulletin (LIT-636345).
If the OWS is going to connect to the Metasys system via an
Internet Protocol (IP) network, see the N1 Ethernet/IP Network
Technical Bulletin (LIT-6360175) for additional configuration
requirements.
11. Back up the converted database if a database conversion occurred
(described in Step 7). Use the Windows Backup Utility.
12. Type METASYS at the C:\> prompt and press Enter. Or start
Windows software and click the Metasys icon.
13. In the Logon dialog box, enter your password to log on to the
network.
14. Perform a global download for each network (using the Action
menu on the Network Map).
Notes:
If the Metasys subnet (gate) address of any NCM is being
changed, the NCM DDL file must be recompiled before the
NCM is downloaded.
If upgrading from Release 5 software or earlier, run
WNCSETUP to select a new download file (Lighting
Control) for each NCM101 that has an Intelligent Lighting
Controller (ILC) device.
15. Download all NCMs that are archived at this OWS with Code
and Data. To download an NCM, select one NCM from the
Network Map, display the Action menu, and select NC Download.
In the Download dialog box, choose these options: Code and NC
Data, and This PC. Download one NCM at a time. Wait for each
download to complete before initiating the next download. During
the download, the NCM is not controlling equipment.
16. Command desired Demand Limit and Load Rolling (DLLR) load
groups to Shedding.
The Metasys PMI upgrade is complete. You may now use the
OWS functions. For instructions, refer to the Operator Workstation
User’s Manual.
76
Notes:
The install process creates four temporary files. These may
not be automatically deleted from the hard drive. It is
advised that you check both the WINDOWS and the TEMP
directories for these files, and delete them. (The TEMP
directory location depends on the directory specified by the
TEMP environment variable.) The files that may be created
are:
~INS0163.~MP
~INS0363.~MP
~INS0463.~MP
~INS0762.LIB
77
Appendix A: Autoexec.bat and Config.sys Files
During the setup program, you are asked whether you want the
program to automatically update the Config.sys and Autoexec.bat files
on your computer, or whether you want to make the updates later.
If you select to make the updates later, the setup program creates
two files with the necessary changes: Config.jci and Autoexec.jci. In
this case, it is your responsibility to make sure the changes are added
to the Config.sys and Autoexec.bat so that the Metasys system can
operate.
Verify that the Config.sys and Autoexec.bat contain the lines shown in
the following examples (your versions may contain additional lines).
These files are in the root directory. (See the Install.ows and
Readme.ows files on the Metasys CD for any changes.)
Config.sys
•
On Windows 98 platforms, the Config.sys file must contain the
following line:
SHELL=C:\WINDOWS\COMMAND.COM /P /E:2048
•
On Windows NT or Windows 2000 platforms, in the CONFIG.NT
file, normally located under
c:\winnt\system32\config.nt, the following line must
appear:
shell=%systemroot%\system32\command.com e:2048
Replace %systemroot% with the location where Windows NT
or Windows 2000 software was installed.
78
Autoexec.bat
For all platforms, the Autoexec.bat file should look similar to the
following example.
In this example, indented text indicates a continuation of a single line
that could not fit on one line on the page. These lines must be present,
but they may appear in a different order. The Autoexec.bat file might
also include additional lines that were present in the original
Autoexec.bat.
@ECHO OFF
PROMPT $p$g
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\BATCH;C:\
DFEDIT;C:\FMS\BIN;C:\FMS\BIN\GPL (Note 1)
SET DFEDIT=C:\DFEDIT
SET TMP=C:\GPLTMP
SET GPLUMAC=C:\CUSTUMAC
SET GPLCMP=C:\
SET GPLPATH=C:\FMS\DATA
SET FMSDATA=C:\FMS\DATA
SET DRIVE=A:
SET TEMP=C:\TEMP
SET FMSDOS=C:\FMS\DATA
SET FMSPATH=C:\FMS
*IF EXIST C:\BATCH\SETARCH.BAT CALL
C:\BATCH\SETARCH.BAT
Note 1: Though all elements of the path must be present in the path
line, they may be in a different order.
*
These lines do not appear for Windows NT or Windows 2000
software.
79
Daylight Saving Time
When transitioning from standard time to daylight saving time or
vice versa, it is possible that the time on the OWS and NCM is not set
correctly. This problem can also occur in time zones that do not
support daylight saving time. If you encounter this problem, add the
appropriate line from Table 15 to the Autoexec.bat file on each
workstation on the Metasys Network. You must restart the OWS after
making the change.
Table 15: Autoexec.bat Command
Command
Description
SET TZ=CST6
Central Standard Time
SET TZ=EST5
Eastern Standard Time
SET TZ=MST7
Mountain Standard Time
SET TZ=PST8
Pacific Standard Time
SET TZ=IND5
Indiana, a time zone that does not support daylight
saving time
SET TZ=ASTx
All other time zones. See Note.
Note:
For all other time zones, x is the time zone difference in hours from
Greenwich Mean Time (GMT). For example, in Hawaii the command is
SET TZ=AST10. In New Delhi, the command is SET TZ=AST5:30.
Date/Time Properties
For all platforms, you must disable the automatic adjustment for
daylight saving time. Disable this feature in the Date/Time Properties
dialog box in the Windows Control Panel.
Once the year changes in the Windows Date/Time window, it also
changes in the Johnson Controls Date/Time box. This change occurs
without clicking OK or Apply. The date change is also propagated to
all nodes of the Metasys Network. Date-sensitive programs on any
workstations on the Metasys Network, such as OEM Historian, may be
affected. This situation occurs with Windows 98 software. Windows
NT OS at Service Pack 4 or later and Windows 2000 software are not
affected. A patch is available from Microsoft Corporation and is
posted on The Advisor.
80
Appendix B: Printer Notes
These notes apply to printers attached to the OWS. For information on
printers directly attached to an NCM, see the Network Control Module
200 Series Technical Bulletin (LIT-636025) and the Network Control
Module 300 Series Technical Bulletin (LIT-6360251).
Supported NCM Printers
A printer directly connected to an NCM must be an IBM Proprinter
device. The specific control codes, which must be compatible, are:
Line Feed, Carriage Return, Form Feed, Compress Print On, and
Compress Off.
Printing from Metasys Software
The Metasys Network and applications that run with Metasys software
print to the printer specified with the Change Printer option in the Item
menu. The printer may be attached to a local port on the workstation or
to a printer on a remote workstation.
Defining the Printer
When defining the printer on the OWS, note that the Windows Printer
Name and driver settings in the Printer Definition and Focus windows
must match the settings as listed on the Windows printer test page.
From the Control Panel, select Printers and select this printer as the
default printer in the Printers dialog box.
Note:
This is also true for DDL, where the Windows Printer Name
and printer driver parameters must match the Control Panel
settings (the DDL default for Windows Printer Name is
IBM PROPRINTERS, and the default for Windows Printer
Driver Name is PROPRINT). Also, the settings must match
the Windows printer test page.
Printing from Third-party Packages
Third-party packages (for example, PC Paintbrush software) print to
the printer specified with the Change Printer option in the Item menu.
The printer may be attached to a port on the workstation or to a port on
another workstation.
81
Draft and Quality Modes of Printing
Summaries to any network printer are printed in Draft mode (for
printers whose Windows drivers support Draft mode). Windows with
graphic elements (for example, an Object Focus window with a Trend
line graph) are printed in Quality mode.
If you want summaries to print in Quality mode, set the following flag
in the [METASYS] section of the METASYS.INI file:
NearLetterQuality=1
Disabling Form Feeds
If you print frequently and want to cut down on paper usage by
disabling form feeds, set the following flag in the [METASYS] section
of the METASYS.INI file:
DisableFormFeed=1
Windows Printer Name
The Metasys Network does not support printer names longer than
24 characters. The Windows Printer Name field in the Metasys
Network allows for a maximum of 24 characters. One symptom of this
problem is that schedule summaries do not print. This problem can be
categorized by PCL-type printers and HP-PPA-type printers.
PCL-type Printers
To restore printing on printers that use the PCL printer language,
change the printer name to a name that is 24 characters or fewer.
Windows-only (HP-PPA)-type Printers
Do not purchase or use Windows only (HP-PPA)-type printers. The
printer name on HP-PPA-type printers, also known as Windows
only-type printers, cannot be changed, and there is currently no
workaround.
82
Hewlett-Packard Printers
The following points are issues with HP printers and Metasys
software:
•
Printing may be garbled or in the wrong font.
•
Improper characters appear on the screen.
•
There are Direct-Connect Printer (DCP) errors.
If you have problems when HP printers are installed with Metasys
software, try the following procedure.
1.
Install the HP printer using the correct drivers provided on the
OWS where the printer is physically connected. Ensure the printer
works correctly with any other applications installed on the
system.
2.
Install one of the following printers on the same OWS.
•
HP510 for black and white only printing (best option)
•
HP500C for color printing
Note:
These are generic printers; the drivers are on your Operating
System CD.
3.
Make this printer the default driver on this OWS.
4.
Install the same driver on all other OWSs in the system.
Configure as described in Configuring Metasys Workstations for
Printers detailed procedure.
Printers with Mixed Operating Systems
You must use printer drivers that have the same name if you are trying
to print among different OSs.
You may have to choose an emulation driver to effect printing across
mixed OSs. Printers change so quickly that you should confirm, before
you purchase it, that the printer works properly. Confirmation is
especially important if you intend to mix OSs across OWSs.
Panasonic Printers
Difficulties occur when using the Panasonic KX-P2180 printer
across multiple OSs.
83
Appendix C: Sound Capabilities
With the addition of a sound card to your OWS, you can use
multimedia technology, together with Metasys software, to
differentiate among Critical Alarm Levels 1 to 4. Previously, the OWS
received Critical 1, 2, 3, and 4 alarms with a sounded alarm that was
identical for each priority. The sound card together with the Windows
Multimedia drivers, allows you the flexibility to select a unique tone
for each alarm level. The alarm is sounded when the alarm level is
displayed in the dialog box.
In addition, the Reminder dialog box can have its own unique sound
assigned as well.
Alarm Sounds
There are four kinds of alarm sounds that correspond to the
four critical alarm levels. The Windows Multimedia sound driver
sounds the alarm by using a .WAV file. The .WAV file name is
defined in the Windows WIN.INI file, and any of the four sounds can
be tailored by the operator using the Windows Multimedia recording
functions. If the parameters are not defined in the WIN.INI file, then
the system default sound setting is used.
To enable sound, you must modify the METASYS.INI file and the
WIN.INI file, and enable the horn through the Metasys system.
Required Hardware
To utilize the multimedia features, you must install a 100%
Sound Blaster compatible sound card. You can use either the internal
PC or external speakers and the Windows Multimedia driver
automatically selects the proper speaker type.
If the OWS does not have any internal speaker (only a piezoelectric
reed), then you need to add the following METASYS.INI parameter:
MultiMediaSound=0
This parameter specifies that the default beep is used rather than the
multimedia sound .WAV file.
Note:
Windows NT and Windows 2000 software do not provide
support for the PC speaker. Install a compatible sound card
to utilize multimedia features.
84
Modifying the .INI Files
METASYS.INI
To enable multimedia sound, add the parameter listed above, but
change the 0 to 1. See the Initialization Parameters Technical Bulletin
(LIT-636345) for details.
Add the following parameters to the [METASYS] section of the
METASYS.INI file to enable sound for the Critical Alarm Reminder
Box:
SystemAlarmRem=
Add all the following parameters to the same section for the .WAV
files associated with each alarm:
SystemAlarmCrit1=
SystemAlarmCrit2=
SystemAlarmCrit3=
SystemAlarmCrit4=
SystemDefault=
Note:
Be sure to add all the parameters and write the .WAV file
name after the =. For example,
SystemAlarmCrit1=C:\WINDOWS\MEDIA\ALARM.WAV.
See the Initialization Parameters Technical Bulletin (LIT-636345) for
the description of each parameter.
85
Appendix D: Release 6.0 and Later NCM Memory
Requirements
This section applies only if you are upgrading from Release 5 or
earlier.
New features added to the PMI software at Release 6.0 and later
increase the size of some objects in the NCM. This size increase may
cause the data downloaded into the NCM to use more memory than
previous releases. Before starting the Release 6.0 or later upgrade,
verify that each NCM has enough available memory to handle the
additional memory requirements. You must have a minimum of 50 K
allocated memory to use at runtime after downloading is complete.
The NCMs most vulnerable to this increase are NCM101 class devices
(101, 102, and 401) and NCM200s with NIM102 or NIM202 modules.
Use Table 16 to determine the additional memory required for each
NCM on the job. Do this calculation for each NCM by entering the
number of objects of each type listed, multiply by the given impact
factor, and total accordingly.
The number of objects of each type can be found by using an UNDDL
listing for each NCM.
Table 16: Memory Requirements
NCM Number
Object Type
Number of
Objects
Multiply By
Binary Data (BD)
x 10
Binary Input (BI)
x 10
Binary Output
(BO)
x1
Multistate Data
(MSD)
x 10
Multistate Input
(MSI)
x 10
Multistate Output
(MSO)
x1
DLLR
x 122
LOADS
x2
FIRE
x 12
Additional Memory
Required (in bytes)
Additional Memory Required for this NCM
Note:
If the NCM type is a standard NCM101, you may reduce this Additional
Memory Required value by 3000 bytes. This decrease only applies to this
type.
86
To determine if the additional memory required may result in an NCM
memory problem, compare the total Additional Memory Required
number above to the Total available allocable memory in the NCM. If
the memory available is less than the additional memory required, the
NCM fails to download.
To get the Total available allocable memory in the NCM:
1.
Choose the NCM on the Network Map.
2.
Select Diagnostics from the Action menu.
3.
Choose NCM Miscellaneous Data.
87
Appendix E: Database Conversion
This section applies only if you are upgrading from Release 5.0 or
earlier.
Release 6.0 or later PMI software cannot function with
Release 1 through 5 databases. Therefore, the database must be
converted. The conversion program converts the archive database from
a previous release format to the current release format.
The following databases are converted: BD, BI, BO, MSD, MSI,
MSO, and FIRE object databases, and DLLR and Access
(Superbase 4) feature databases.
There are two ways of starting the conversion: automatic and manual.
Automatic: The automatic method occurs as part of an upgrade of
PMI software. After the upgrade, you are informed that a conversion is
required and asked whether to continue with the conversion. If you
answer yes, the conversion proceeds automatically. If you answer no,
no conversion occurs, and you are not allowed to use the PMI, GPL,
DDL, or UNDDL software on the unconverted database.
Manual: The second way of starting the conversion is to manually
type CONVERT at the DOS prompt. (The manual process is described
later in this section.)
PREP-FOR Command
The PREP-FOR command prepares the PC for database conversion or
restoration. When using a Windows NT or Windows 2000 based
operating system, issue the PREP-FOR command with c:\winnt
behind it to direct the PREP-FOR command to the location of the
win.ini file. The PREP-FOR command should look like this:
PREP-FOR C: \PROJECT\YOURJOB C:\WINNT
When using the PREP-FOR command with Windows NT software for
C:>PREP-FOR C: \PROJECT\99999999 C:\WINNT, use the
Cmd.exe file instead of the Command.com file. If you use the
Command.com file and press Enter twice, the PREP-FOR command
does not work, regardless of the resulting message.
88
Database Conversion Guidelines
When converting an older database for a software upgrade, adhere to
the following guidelines:
•
Before doing a conversion, save the previous database and clearly
label the backup.
•
Keep clearly labeled backup copies of both the old and new
databases. (Since databases converted to the current format do not
function with previous release PMI software, if you reinstall the
previous software, you must restore the previous database.)
•
Before doing a manual conversion (by typing CONVERT), do a
PREP-FOR to set up environment variables.
•
After the conversion is complete, save the database immediately
(using the SAVEDB function) so you have a backup of the
converted database.
•
Remember a Release 1-5 database is incompatible with Release 6.0
or later software, and a Release 6.0 or later database is
incompatible with Release 1-5 software. Therefore:
-
Do not use Release 6.0 or later tools (DDL and GPL) to
generate a database for a job at an earlier release.
-
Do not copy files from an earlier database into a Release 6.0 or
later database.
Manually Starting the Conversion
To manually start the conversion:
1.
Save the old database (using SAVEDB) and clearly label the
backup with its release number
(for example, Release 5.00 or 5.02).
2.
Do a PREP-FOR to ensure the environment variables are correct.
3.
Type CONVERT at the DOS prompt.
4.
Type Y (yes) when asked whether to continue. Then wait for the
conversion to complete. If errors were found, check the Log file
for their descriptions and locations.
5.
Save the converted database after the conversion completes (using
SAVEDB) and clearly label the backup as Release 7.0 (or the
appropriate release number).
89
Conversion Screens
When the conversion program first starts (before performing any
actual converting), it checks to see if there is a database to convert and
if there is enough available disk space for the conversion. If there is no
database to convert or if there is not enough disk space for the
conversion, the conversion program exits and, if appropriate, informs
you of how much disk space is required.
If there is a database to convert and enough disk space, a screen
message informs you that a database backup is strongly recommended
and asks whether you want to continue with the conversion (Y or N).
Enter N (no) if you need to first perform the backup. In this case,
perform the backup and then start the conversion manually by typing
CONVERT at the DOS prompt. Enter Y (yes) if you already have a
backup and want to go ahead with the conversion.
The screen informs you of the progress of the conversion. Specifically,
it tells you which network and which NCM is being converted at any
moment, and whether it is reading or writing the data. The conversion
reads all data from one network, writes all data back to that network in
Release 6.0 format, and then proceeds to the next network.
A Conversion Complete message appears at the end of the
process. If errors were found, a message directing you to the log file
also appears.
Convert.log
There is a log file that records the conversion and any errors that were
FMSDATA is the directory specified by PREP-FOR (FMS\DATA or
project\contract#).
Sometimes the conversion process detects errors in the old database
(for example, a parameter out of range). The conversion continues;
however, the errors are still in the converted database. The log file
describes these errors and their locations in a format similar to DDL
found. The log file resides in the FMSDATA directory, where syntax.
Then fix the errors in the converted database (through online
generation, DDL, or GPL). Use the DDL Programmer’s Manual to
check for valid ranges.
90
Convert.log Error Message Examples
Binary Outputs (BOs) Mapped to XRLs - The most common error
message in the CONVERT.LOG file is for BO objects mapped to
XRLs. The pulse duration of these BOs has a range of 12 to 3060.
However, on many jobs the value in the database is zero. An example
of the Convert.log entry for this database problem is:
Error Found in Database of BO: Chiller\P3-C
XMHW 3, 1, 0, Y
^ Parameter 3 value out of range
Conversion continued, error remains in the
database
Changed or Deleted Network Name - A database with a changed
network name or a deleted network may result in the following
message:
C:\project\contract\net.dob is a directory that
contains files which appear to be from an old
(but currently unreferenced) network. To
prevent problems this directory has been
renamed to C:\project\contract\net.old. It is
recommended that you delete this directory and
its corresponding directory
C:\project\contract\net.
In this case, check these directories for any files that may need to be
saved (DDL source, GPL source, Computer Aided Engineering (CAE)
drawings). Save the necessary files, and then delete the directories
from the disk.
Demand Limiting/Load Rolling - The following message appears in
the log file if:
•
All NCMs are not archived on the same OWS and a Demand
Limiting/Load Rolling object has loads on an NCM archived on a
different OWS.
- or •
The BO was deleted from the database but not from the Demand
Limiting/Load Rolling load list.
Load Group DEMAND\LOADGRP has a BO Load named
AHU1\BO7. This BO Load could not be found in
the archive database of this OWS. The BO’s Load
priority is 4. This load will need to be
entered manually.
91
The following message appears in the log file if:
•
All NCMs are not archived on the same OWS and the BO’s Load
Group is archived on a different OWS.
- or •
The Demand Limiting/Load Rolling object was deleted from the
database.
GEO1ST\FNST11 is a BO Load whose Load Group
cannot be found in the archive database of this
OWS. The BO’s Load information must be entered
manually after conversion. The following Load
information has not been converted and must be
entered manually:
load locked = N
load rating = 8
minimum release time in minutes = 30
maximum shed time in minutes = 10
comfort system name =
comfort object name =
minimum shed time in minutes = 0
Going Back to Previous PMI Software
If you need to go back to the old PMI software and old database after
you’ve already upgraded and converted to the new database, use the
following procedure:
1.
Delete the new database.
2.
Get the backup of the previous release database and restore it
using the RESTDB command (described in the Move Utility
Technical Bulletin [LIT-636110]).
3.
Delete the old manufacturing file (MFG$$$.OWS). An install of
old PMI software over new PMI software is not allowed unless
the manufacturing files are deleted. The manufacturing files are in
the C:\FMS\BIN directory (provided that the default, C:\FMS,
was selected during installation).
4.
Install the previous release PMI software.
92
Restoring Previous Release Database over Converted Database
If you need to restore a database saved at Release 5.0 or earlier, you
must convert the database after the restore is complete. Restoring a
previous release database over a converted database should be
done only if absolutely necessary. Note the following before
restoring the previous database:
•
If the Save of the previous database was a Save All, then you must
delete the entire archive database on the hard disk before restoring.
You must remove the FMSDATA directory and its entire contents
and subdirectories from the hard disk.
•
If the Save was of a single network, you must delete the entire
network database on the hard disk before restoring. You must
remove the FMSDATA\network directory and its entire contents
and subdirectories and the FMSDATA\network.dob directory
and its entire contents from the hard disk.
93
Appendix F: Troubleshooting Chart
Use Table 17 to help troubleshoot the OWS. Only problems specific to
the Metasys Network are covered. See Appendix G: ARCNET
Troubleshooting for ARCNET tips. For other hardware and software
problems, refer to the manufacturer’s literature.
Table 17: Troubleshooting Steps
Problem
Solution
The Windows desktop screen does not Check to see that:
display when you try to run Metasys
The PC has enough conventional and extended memory available.
software.
Conventional memory must be at least 530 K.
The following files are present and contain the proper statements:
AUTOEXEC.BAT, CONFIG.SYS, WIN.INI.
Metasys software is fully installed.
All required third-party software is properly installed.
All cables are securely attached.
The monitor is turned on.
Blank Windows desktop screen
appears and Metasys software will not
run.
Check to see that:
The PC has enough conventional memory. Conventional memory
must be at least 530 K.
ARCNET board is set up correctly.
The following error message appears
during Metasys startup if a
non-Metasys ARCNET driver is
detected:
Metasys load aborted due to
detection of an active
non-Metasys ARCNET driver.
Remove the driver via Control
Panel – Network then restart
Metasys.
The EnaArcChk parameter has detected a non-Metasys ARCNET
driver. Remove all non-Metasys ARCNET cards:
In the Windows Control Panel, double-click the Network icon.
Select the Configuration tab.
Select an ARCNET driver.
Click Remove.
Repeat this solution for all ARCNET drivers.
Reboot the PC.
Logon screen displays, but when you
try to log on, system hangs.
Check to see that the PC has enough extended memory.
The message N1 Initialization
Failure displays when you try to
run the Metasys Network.
Check to see that:
The ARCNET board is installed.
If you have an IBM computer, the interrupt level and I/O address of
the ARCNET board are set correctly, and match the settings in the
METASYS.INI file.
If you have a Compaq computer, interrupt level, I/O address, and
node ID of the ARCNET board are set correctly.
The node addresses on the switches match the node address on
the OWS.
The DDL file for the BAS is correct and compiled.
94
Problem (Cont.)
Solution
The Metasys Network begins to
boot, but a series of message
boxes display indicating that
certain files cannot be found.
Check to see that:
The statements DATA=C:\FMS and FMSDATA=C:\FMS\DATA are in the
METASYS.INI file. (If your system uses a different directory structure, for
example, C:\project\contract#, these statements reflect the settings
defined by the PREP-FOR command.)
OWS is not communicating with
other nodes on the N1 LAN.
Check to see that:
T-connector is secured to the ARCNET board on the Workstation.
One N1 LAN cable segment is attached to each side of the T-connector;
or, one N1 LAN cable segment and a 93 ohm terminator cap are attached
to the ends of the T-connector (only if this node is at the end of line).
The following parameters for the ARCNET board are properly configured:
node ID, interrupt level, I/O address, memory address, and topology
(SMC board only).
The DDL file for the BAS is correct and compiled.
Logon screen will not display.
Check to see that:
Global DDL file is present and compiled.
Network DDL file is present and compiled.
The message Archive
database is incompatible
with current software
release. DATABASE
CONVERSION IS REQUIRED
displays when the PMI software
is loading.
The archive database is at Release 5 or earlier and needs to be
converted. Run the manual CONVERT program as described in
Appendix E: Database Conversion.
The message Incorrect DOS
Version displays when doing a
SAVEDB.
Appears when a SAVEDB backup is attempted with the incorrect DOS
version.
An error message, either
Internal Error or Incoming
Call appears in Metasys
software when a laptop
computer with a PCMCIA modem
attempts to dial out.
The problem is a communication port problem.
To fix the problem:
Create a text file called fixcom1.deb if you are using COM1, containing
the following lines:
E40:0
F8 03
q
Create a text file called fixcom2.deb if you are using COM2, containing
the following lines:
E40:2
F8 02
q
Add the following line to the beginning of the autoexec.bat file:
debug<fixcom1.deb>NUL if you are using COM1, or
debug<fixcom2.deb>NUL if you are using COM2.
Reboot the laptop computer.
95
Appendix G: ARCNET Troubleshooting
This section contains tips for troubleshooting ARCNET boards.
ARCNET Interrupt
The ARCNET interrupt signals the PC when its buffer has information
that needs to be sent to the Metasys system. The default ARCNET
interrupt (IRQ) for Metasys software is 7. If IRQ 7 is not available,
then set up Metasys software to use an IRQ of 2, 3, 4, 5, or 6. If you
need a different interrupt other than 7, then the ARCNET board must
be configured for the new IRQ level and the METASYS.INI file needs
to be modified. Refer to the example below for specific details.
The majority of PC vendors define IRQ 7 as the local printer, LPT1.
In most cases, this does not affect the Metasys system since the use of
IRQ 7 by the printer is only in diagnostic mode. IRQ 7 can be
shared/used with the ARCNET board. There are some PCs that cannot
share IRQ 7. For these cases, Metasys software ARCNET IRQ must
be changed to an available interrupt.
Example
Problem Description—Typical problem scenario: N1 appears to be
online. However, the OWS cannot communicate to any nodes on the
N1. There may be several causes for this symptom. One cause is due
to an interrupt conflict.
Verification—Metasys software uses IRQ 7 as the default interrupt. To
determine which interrupts are available, run a diagnostic package
such as MSD (Microsoft Diagnostic software). MSD comes standard
with Windows software and can be run by typing MSD at the DOS
prompt (it is suggested that Windows software is not active when
running MSD). View the information block titled IRQ Status. Under
the IRQ column, all hardware interrupts used with this PC are
identified. From this list, determine the open IRQ levels.
Resolution—Once you have identified an unused interrupt and your
ARCNET board supports it, set the jumper on the ARCNET board
accordingly. Additionally, the METASYS.INI file needs to include
this interrupt change. Modify the following line in the METASYS.INI
file: ARCNETINT=x where x is the new interrupt level on the
ARCNET board. Add this line if it is not already in the
METASYS.INI file (this line is not automatically created by the
installation program).
96
Notes:
If the interrupt was changed from the default of IRQ=7, then
you must document this change. It is suggested that you
create an ARCNET.OWS file describing all ARCNET
settings for this PC. Keep this file in the BATCH
subdirectory. Do not keep it in the FMS subdirectory
because then it might be deleted during the next PMI update.
A sample of a typical ARCNET.OWS file is included in this
section, under ARCNET.OWS.
A second cause is a vendor conflict between the ARCNET
card and the PC. To solve the conflict, change the card to a
CCSI ARCNET Card.
ARCNET I/O Address
The ARCNET I/O address responds to commands being sent from the
PC to the ARCNET board and enables the ARCNET status to be
returned. The Metasys system default ARCNET I/O address for all
ISA bus boards is 2E0 (hex). If there is an I/O address conflict with
other controllers, then any unused I/O address may be used. If the
ARCNET I/O address is changed, then the METASYS.INI file needs
to reflect the same change. Specifically, in the METASYS.INI file,
change the line ARCNETIO=x, where x is the ARCNET I/O address
decimal equivalent of the hex address set on the ARCNET board.
Example
Problem Description—May exhibit same symptoms as an interrupt
conflict or the Metasys system could indicate N1 Initialization Errors.
There may be several causes for these symptoms. For this example,
assume an ARCNET I/O address conflict.
Verification—Metasys default is 2E0 (hex). Generally, all devices with
I/O capability require an I/O address (for example, CD-ROMs, tape
drives, communication ports, Ethernet boards, and video boards). To
determine which I/O addresses are being used, refer to the I/O device
manuals.
Resolution—Once all I/O addresses are identified, then refer to the
ARCNET manual for which addresses are configurable for the
installed ARCNET board. To change the ARCNET I/O address to an
unused address, both the ARCNET board and the METASYS.INI file
must be modified. On the ARCNET board, set the appropriate
jumper/switches per your ARCNET user’s manual. For the
METASYS.INI file, change the ARCNETIO=x line, where x is the
decimal equivalent to the hex address set on the ARCNET board
(2E0 hex = 736 decimal).
Note:
97
If the ARCNET I/O address was changed from the default of
2E0, then you must document this change. It is suggested
that you create an ARCNET.OWS file describing all
ARCNET settings for this PC. Keep this file in the BATCH
because it might be deleted during the next PMI update. A
sample of a typical ARCNET.OWS file is included in this
section, under the ARCNET.OWS section.
ARCNET Base Memory Address
The ARCNET base memory address is the input/output address buffer
for the ARCNET board. Up to a 16 K block of memory is mapped to
the ARCNET board. Any available 16 K block of memory that can be
set on the ARCNET board can be used (refer to the ARCNET user’s
manual for available base memory address settings). Metasys
documentation recommends default settings for some PC types. If
there is a conflict with other adapters using the same base memory
address, then an alternate 16 K memory block needs to be set on the
ARCNET board. A change in the METASYS.INI file is not required.
Example
Problem Description—Typical Metasys system error messages include
N1 Memory Failures and/or N1 Initialization
Failures. These are caused by the computer not recognizing the
16 K base memory segment block used by the ARCNET board.
Verification—To verify that the PC is communicating to the ARCNET
board, an N1 Signature test must be run. This test uses a DOS program
called Debug. In running this test, Debug reads the memory address
segment of the ARCNET board and responds with the N1 Node
address set on the ARCNET board. (Do not run the Metasys system
until after performing this test.)
To perform the N1 Signature test:
1.
Cycle power on your PC and boot up in DOS mode.
2.
Type debug at the DOS prompt (with no applications running)
and press Enter.
3.
Type D xxxx:0000, where xxxx = the starting ARCNET
memory address (as determined from board switch settings) and
press Enter.
To exit, type quit.
98
Here is an example of a CompuAdd PC whose ARCNET base
memory is set to C800.
c:\debug
-D C800:0000
C800:0000 D1
C800:0010 75
C800:0020 F8
C800:0030 74
C800:0040 B1
C800:0050 8C
C800:0060 94
C800:0070 EC
64
FF
EF
FF
FF
FF
FF
FF
EE
8B
FD
F5
F5
BB
7F
FB
FF
FF
FF
FF
FD
FF
FD
FF
DF
74
B9
CB
41
8F
E7
75
FF
FF
FF
FF
FF
FF
FF
FF
8F
F7
27
F9
5D
FC
B8
AE
FF-4D
FF-95
FF-D4
FF-C9
FF-3F
FF-03
FF-5F
FF-64
FF
FF
EF
FF
DF
FF
FF
F7
47
3A
3A
FA
6F
ED
EE
5E
F7
FF
FD
FF
FA
FF
FF
FF
D0
0E
49
F6
DD
77
FE
6F
FF
FF
7F
FF
FF
FE
FF
EF
B3
5D
9F
35
7A
FB
1F
7F
FF
FF
FF
FF
DF
FF
FF
DF
To verify that the computer can read the ARCNET base memory, the
first location dumped from debug must be the signature recognition of
D1. Immediately following the D1 is the ARCNET node address that
is set on the N1 node address switches. In the above example, the first
line dumped contains the signature of D1 immediately followed with a
64 (hex). The 64 converts to the N1 node address of 100 (decimal) set
on the ARCNET board of the PC.
If the first address is not D1, then a conflict exists.
Resolution—Remove the ARCNET board and run MSD (refer to the
ARCNET Interrupt section for details on MSD). View the information
block titled Memory to see if the 16 K block set on the ARCNET
board is being used by some other application. If you find this base
memory is already being used, then select an available 16 K block that
can be addressed by your ARCNET board (refer to your user’s manual
for available selections). Configure the new base memory address on
the ARCNET board. Install the ARCNET board and rerun the N1
Signature test.
Certain PC platforms disable the shared memory for ISA boards and is
controlled by the PC’s setup configuration utilities. Typically, if the
PC setup utilities disable ISA shared memory, the N1 Signature test
responds with all data at FF. For examples with resolution, refer to the
OWS troubleshooting tips on the Johnson Controls Intranet site,
The Advisor.
Note:
Since the ARCNET base memory address is PC
configurable, you must document this information. We
suggest creating an Arcnet.ows file describing all ARCNET
settings for this PC. Keep this file in the BATCH
because then it might be deleted during the next PMI update.
A sample of a typical Arcnet.ows file is included in this
section, under the Arcnet.ows section.
99
ARCNET Node Address
All ARCNET N1 devices require a node address. For the OWS, the
address is set by the node address switches on the ARCNET board. On
ISA boards, it is set via DIP switches. Additionally, this address needs
to match the address defined in the Net.ddl and Global.ddl files.
Example
Problem Description—A typical example of a node address mismatch
is N1 Initialization failure.
Verification—To ensure the address Metasys software is using for the
PC matches the ARCNET Node address, both the N1 Signature Test
and a decompile of the NET database must be done. Run the N1
Signature test as explained in the ARCNET Base Memory Address
section. The parameter immediately following D1 is the Hex node
address of the ARCNET board. Now do a decompile (UNDDL) of the
NET database operating on this OWS. Compare the Node address in
the decompiled NET file with that of the N1 Signature test. Both node
addresses must match. (Note, however, that the address displayed
during the signature test is in Hex, while the address in the NET file is
in decimal.)
Resolution—If a mismatch occurs, make the appropriate corrections.
Note:
Since the ARCNET address is PC configurable, you must
document this information. We suggest creating an
Arcnet.ows file describing all ARCNET settings for this PC.
Keep this file in the BATCH subdirectory. Do not keep it in
the FMS subdirectory because then it might be deleted
during the next PMI update. A sample of a typical
ARCNET.OWS file is included in this section, under the
Arcnet.ows section.
100
N1 Bus/Star Setup
The N1 Bus/Star setup configures the communication mode to be in
either a high impedance state (twisted pair wires for Bus mode) or in a
low impedance state (coax cable for Star mode). In a star
configuration, enable an internal End-of-Line (EOL) 93 ohm resistor.
In a bus configuration, the board is set to a high impedance state thus
requiring an external EOL. We recommend that all Metasys system
applications configure the ARCNET board in the bus configuration
setup. If this OWS is at the end of its N1 Bus, then a T-type coax
connector can be installed with one side being the N1 and the other
side being the external EOL terminator.
With the ARCNET board always being configured in the bus type
configuration, the placement of the EOL terminator can be easily
determined.
Example
Problem Description—Strange N1 communication problems are
occurring.
Verification—Always set the OWS ARCNET board to Bus
configuration. If the OWS is at the physical end of the N1 Bus, then
you must install a coax T-type connector with a 93 ohm terminator.
Verify that the other physical end of the N1 Bus also has a 93 ohm
terminator. If these are the only EOL installed, then double check the
ARCNET configuration setup on the board to make sure it is set for
Bus mode.
Resolution—Remove all incorrect EOL from the N1.
N1 Enhanced/Compatible Setup
The Thomas-Conrad ARCNET board has an Enhanced/Compatible
option. The Enhanced mode uses special Thomas-Conrad accelerator
drivers to optimize performance and minimize memory conflicts. In
the Compatible mode, non-Thomas-Conrad drivers are used to control
the ARCNET board. The Metasys Network uses its own driver to
control the ARCNET board in both the OWS and all NCMs. Thus,
Metasys software requires this setup option to be in the Compatible
mode for all applications.
ARCNET Model
The ARCNET model is defined in the METASYS.INI file. The
ARCNETMODEL=x line (where x is the style ARCNET board
installed in this OWS) is used by Metasys software to help determine
the base memory address.
101
Config.sys and Autoexec.bat
These two files are key elements in configuring the PC. When Metasys
or GPL programs are first loaded, both the Autoexec.bat and the
Config.sys files are changed. The current Autoexec.bat file is
appended to add specific setup information for Metasys or GPL
software. The Config.sys file is replaced with a new Config.sys file
specific to the operation of Metasys and GPL software.
Example
Problem Description—Metasys system is unable to directly
communicate to an NCM over the PC’s COM1 port. The PC runs
WNCSETUP over the COM1 port.
Verification—The latest revision of Metasys software was just loaded.
Both the Autoexec.bat and the Config.sys files matched the sample
files shown in Appendix A: Autoexec.bat and Config.sys Files of this
document.
Resolution—Prior to loading Metasys and GPL software, the
Config.sys file had specific drivers installed. These drivers are needed
to enable COM1 operation within the Windows environment. Since
both Metasys and GPL software replaced the Config.sys file with a
Metasys specific file, these drivers were no longer loaded on a reboot.
Reinstall the original drivers into the Config.sys file so the Metasys
system can communicate over COM1 to an NCM.
To prevent this problem from happening, review both the
Autoexec.bat and Config.sys files before installing Metasys or GPL
software. Check these files again after loading the new system and
modify if necessary.
102
Arcnet.ows
It is highly recommended that all OWS setup parameters be stored in a
text file for future reference. The recommended file, Arcnet.ows
should be stored in the BATCH subdirectory. Include base I/O
address, base memory, IRQ setting, or any other specific configuration
settings for the OWS to quickly identify the ARCNET parameter
settings needed for anyone who has to work on this OWS.
Here is a sample Arcnet.ows file:
Job Name: JCI Corporate Office Building
JCI Installing Engineer: Jerry Gervenak
Date ARCNET was commissioned: January 17, 1995
OWS Type: CompuAdd 450
OWS node address 101
ARCNET IRQ: 7
Other IRQs changed: Sound board changed to
IRQ=10
ARCNET I/O address: 2E0
ARCNET base memory address: C800
EOL terminator locations: OWS1 and NC14
Special configuration notes: none
103
Appendix H: Windows NT/Windows 2000 Details
The architectural design of Windows NT and Windows 2000 software
is different from Windows 98 software. This appendix contains details
regarding Windows NT and Windows 2000 software differences.
OWS Configuration
Table 18: Base Hardware Requirements
Component
Requirement
Processor
Pentium Processor
RAM Memory
256 MB recommended (128 MB minimum)
Bus
ISA, PCI
Hard Drive Capacity
8 GB minimum
Hard Drive Interface
IDE
CD-ROM
Required to install Windows software. Metasys media distributed on CD.
Printer and Cable
Must be supported by Windows software.
Mouse
Microsoft
Monitor
VGA (640 x 480), Super VGA, (800 x 600) or greater
Sound Card
Windows system compatible, PC speaker is not supported.
Tape Backup Device
Windows system compatible, back up to floppies is not supported.
Graphics Support
VGA or SVGA
Video chip EGA support required (for GPL).
Table 19: Minimum Software Requirements for Windows NT Software
Software
Revision
File System
Configured as FAT 16; FAT 32 is not supported. NTFS was not tested.
Metasys
Release 9.01 or later
Table 20: Minimum Software Requirements for Windows 2000 Professional
Software
Software
Revision
File System
Configured as FAT 32.
Metasys
Release 12.00 or later
IMPORTANT: Disable screen savers on Windows NT or
Windows 2000 workstations. If the screen saver is
enabled and the mouse/keypad is pressed to re-enable
the workstation, the system may reside in a hung state.
104
Using Database Backup and Restore
Follow these instructions to save and restore your database:
Saving a Database
If you are using Windows NT or Windows 2000 software, use the
following instructions to save your database to tape:
1.
From the Metasys Exit menu, click Backup Utility. A submenu
appears allowing you to choose either Backup or Restore.
2.
Choose Backup. A message appears stating that you are about to
exit the Metasys system. The Windows Backup/Restore procedure
is initiated.
3.
From the Window drop-down menu, click the Drives option.
4.
Select the files you want to back up by clicking inside the check
box next to each file. (Selecting a directory selects all of the files
within the directory.) You may select the files you want, or you
may select all files by selecting an entire directory. As a
minimum, we recommend you include the following:
\CUSTOMAC
\FMS\BIN\GPL\JCIMACS
\FMS\GRFXLIB
\FMS\ERRORLOG
\FMS\SAVE
\FMS\STATIC\*SBQ
\FMS\DATA\N1NET.DBF
\FMS\DATA\PCDEVICE.DBF
\FMS\DATA\Win.ini
\FMS\DATA\NETNAME.NDX
\FMS\DATA\PCCONFIG.DBF
\FMS\DATA\PCPORT.NDX
\FMS\DATA\DDL\*.DDL
\FMS\DATA\MODELS
\FMS\DATA\HVACPRO
\FMS\DATA\SYSTEM91
\FMS\DATA\“NETWORK NAME”
\FMS\DATA\“NETWORK NAME”.DOB
Note:
Replace the NETWORK NAME with the actual name of the
network being backed up.
105
5.
Click the Backup button when finished. The Backup Information
dialog box appears.
6.
Enter Full Metasys backup for the description.
7.
Click OK. The backup begins.
8.
Open the Metasys Full Save File and verify that all files selected
are present.
Note:
Blank directories are not saved.
Restoring a Database
Restoring the database copies the database on tape to the workstation.
The tape copy overwrites the database at the workstation. Use the
following procedure to restore the database.
Note:
A database saved using the DOS program SAVEDB.BAT
using either Windows Version 3.1, Windows 95, or
Windows 98 software can be restored on a Windows NT or
Windows 2000 machine using the DOS program
RESTDB.bat (DOS program).
1.
From the Metasys Exit menu, click Backup Utility. A submenu
appears allowing you to choose either Backup or Restore.
2.
Choose Backup. A message appears stating that you are about to
exit the Metasys system. The Windows Backup/Restore procedure
is initiated. The tape drive activates.
3.
Double-click the directory in the right window. A detail tree of the
files that reside on tape appears.
4.
Click on the check box next to the files you want to restore.
When the process is complete, check the \winnt\backup.log to
verify that the files were restored and no error messages are present.
Unsupported Features
The following features are not supported on Windows NT or
Windows 2000 workstations: Fire OWS, GWS Interface, Guard Tour,
and Remote User Interface.
106
Microsoft IntelliMouse
 Pointing Device
The Microsoft IntelliMouse pointing device is not supported on
Metasys Operator Workstations with Windows NT or Windows 2000
software at this time. Some manufacturers install the wheel feature on
this mouse as part of their standard features. To use this mouse with
the Metasys software, you must disable the wheel. If the wheel is not
disabled, problems such as system lockups may occur. To disable the
wheel:
1.
From the Start Menu, go to Settings > Control Panels.
2.
Double-click on the Mouse icon.
3.
From the wheel properties, disable the wheel function.
Using PREP-FOR with Windows NT Software
When running PREP-FOR (Prep.for) on a Windows NT machine, use
Cmd.exe, not Command.com, to execute the DOS window. Follow
these steps to change the shortcut to Cmd.exe:
1.
From the Windows Start menu, select Settings > Taskbar.
2.
Click the Start Menu Programs tab.
3.
Click the Advanced button.
4.
Click on the DOS icon.
5.
Right-mouse click on the icon and select Properties.
6.
Select the Shortcut tab.
7.
Enter Cmd.exe in the Target field if it does not already appear.
If the target name is not changed to Cmd.exe, and Prep.for is executed,
the program appears to work, but then returns an error.
107
Appendix I: Connecting Metasys Release 9.01 OWS
to a Metasys Release 10.01 or Later Network
When connecting an OWS with Metasys Release 9.01 or earlier
software (NC direct or NC dial) to a network at Metasys Release 10.01
or later, you may corrupt your global database. Symptoms of a corrupt
global database include dimmed and/or inaccessible system names
when logging in with the default Metasys password, and Network
Control Modules (NCMs) that go offline. Refer to Table 1 and Table 2
for interconnection details.
To correct the corrupt database, download the correct Metasys
Release 10.01 or later global database from a Metasys Release 10.01
OWS.
To avoid this problem, make sure your OWS is running the same
release as the network.
Note:
Do not use Metasys Release 10.00 software. Upgrade all
Metasys systems at Release 9.01 or earlier to Release 10.01
or later.
Interconnection Issues
Use the following tables to determine which OWS release can go with
which Metasys release.
Table 21: N1 Connections
OWS
NCM
OK?
9.01 or earlier
9.01 or earlier
Yes
9.01 or earlier
10.01 or later
Yes*
10.01 or later
9.01 or earlier
Yes*
10.01 or later
10.01 or later
Yes
*
Do not modify passwords or report groups, or perform global downloads if a
single network must temporarily run mixed revision nodes.
108
Table 22: NC Direct or NC Dial Connections
OWS
NCM
OK?
9.01 or earlier
9.01 or earlier
Yes
9.01 or earlier
10.01 or later
No1
10.01 or later
9.01 or earlier
Yes2
10.01 or later
10.01 or later
Yes
1.
2.
This could cause global database corruption and connection failure.
Do not change passwords or report group databases. You only need to
compile the Net file to connect. If you compiled the global file and
downloaded while not connected, be sure to delete the GLOBLREV.DBF file
from the online global database
(C:\PROJECT\CONTRACT\NETNAME\GLOBLREV.DBF) before connecting.
When upgrading from Metasys Release 9.01 or earlier software to
Metasys Release 10.01 or later software, make sure all nodes are at
Metasys Release 10.01 or later before changing password or report
group data. Where possible, update all nodes during one visit. If all
nodes are not upgraded to the same Metasys software release, global
database corruption may result. If global data becomes corrupt,
perform a global download from the archive PC (at Metasys
Release 10.01 or later) to resolve the issue.
109
Appendix J: Ordering Information
Refer to the Metasys Installation and Platform Requirements
Technical Bulletin (LIT-12012) to help you decide which hardware
and software components to order.
Controls Group
507 E. Michigan Street
P.O. Box 423
Milwaukee, WI 53201
www.johnsoncontrols.com
Printed in U.S.A.

Operator Workstation Technical Bulletin

Transcription

Similar documents

Prismacolor Nupastel Color Chart •www.hyatts.com •(800

Ejercicios

Halloween Party Invitations

ARMOR GENERIC RANGE

North America Executive Suite Review 2012

MAC OS 10.5.2 includes Drivers for Zebra Thermal Printers How to

Getting the Most From Your Printer With Custom Profiles Now that

INN-FORM Plus - Call Accounting Software

The ValueJet 1638X