Chapter 1 - I: Ntroduction
Chapter 1 - I: Ntroduction
Chapter 1 Contents
DESCRIPTION ....................................................................................................... 1–2
Matching Products for Release ............................................................. 1–2
SYSTEM REQUIREMENTS ...................................................................................... 1–3
SUITE INSTALLER FUNCTION ................................................................................ 1–4
Supported Scenarios ............................................................................. 1–4
Unsupported Scenarios ......................................................................... 1–6
OWS DEFAULT DIRECTORIES .............................................................................. 1–7
NEW INSTALLATION ............................................................................................. 1–7
Workstation Number ............................................................................. 1–8
Concise: Installation Procedure ........................................................... 1–9
To install Delta products from the ORCA Suite CD: .............. 1–9
To install Delta products from the desktop: .......................... 1–10
Detailed: Installation Procedure ........................................................ 1–11
To install ORCAview from the ORCAview CD: .................. 1–11
MS HTML Help ................................................................................... 1–18
UPGRADE INSTALLATION ................................................................................... 1–18
Upgrade Procedure............................................................................. 1–19
To upgrade ORCAview from the ORCAview 3.40 CD: ....... 1–19
COEXISTANCE INSTALLATION ............................................................................ 1–23
To coexist ORCAview from the ORCAview 3.40 CD: ........ 1–23
APPLICATION MAINTENANCE: ........................................................................... 1–27
Add/Remove Software ......................................................................... 1–27
Repair Software .................................................................................. 1–29
Uninstall Software............................................................................... 1–30
CONCISE INSTALLATION OF HISTORIAN ............................................................. 1–31
To install Historian from the ORCA Suite CD:..................... 1–32
To install Historian from the desktop: ................................... 1–32
Historian Install Microsoft SQL Server 2005 Setup ........................... 1–33
WINDOWS XP / WINDOWS 7 SENTINEL DRIVER UPDATE ................................... 1–39
To manually update the Sentinel driver from the
ORCAview 3.40 CD: ....................................................... 1–39
CUSTOMIZING THE DESKTOP SHORTCUT FOR AUTOMATIC LOGIN ..................... 1–41
To create a shortcut for automatic ORCAview login: ........... 1–42
SYSTEM ARCHITECTURE .................................................................................... 1–43
Networking Information in Other Chapters ........................................ 1–43
Architecture Design ............................................................................ 1–44
Ethernet – BACnet MS/TP .................................................................. 1–45
Operator Workstation Connections .................................................... 1–46
Thank you for buying the Delta Controls ORCAview® program. ORCAview
operates in a graphical Windows world and has powerful facilities management
tools. We trust that this product will satisfy your building control needs.
We are continuing our efforts to more fully express the vision Integrated Facilities
Management Solutions Simplified in the ORCAview product.
Description
The ORCAview software is a native Windows® application and has been written
to look and operate like most Windows applications.
The operator can view project data graphically or with the interactive Microsoft
Windows Explorer™ style Navigator. Both these interfaces to the DDC system
provide real-time data to the PC, with updates as quick as five second if needed.
Real-time data can be shown in a group of objects, single objects, multiple
objects, on-line graphics, or in any combination.
The user interface has an object-oriented design. This approach allows quick
access to menus by just clicking on an object using the right mouse button.
At the click of a button, the operator can change from viewing a graphic to editing
the graphic using the optional Illustrator tool created by Delta Controls. This
makes it easier to draw and test graphics.
For more detailed information on the drawing program Illustrator, see the
Illustrator Technical Reference Manual which is included on the release CD.
ORCAview currently has four methods to access a DDC system through Windows
networking. The LAN/WAN connections from the PC to the DDC system are:
• BACnet IP (UDP/IP)
• BACnet Ethernet (10 Mbits/s)
• BACnet MS/TP (Up to 76.8K Baud) PC to controller CON-768/ CON-768BT
• BACnet PTP RS-232 (Up to 38.4Kbytes/s) Local and Dial-in/Dial-out
• DSC/DAC – BN155693
• Tetra – EN155693
• DFM /DRP– FM155693
• V2 Micro – – RC114575
• DCU – 340.3073
System Requirements
To run the Delta Controls ORCAview® software, Delta Controls offers the
following minimum requirements:
Minimum Requirements
Operating Windows XP 32 Pro; Server 2003/Win2K3; Vista 32/64
System (Business, and Ultimate); 2008 Server; Windows 7 32/64 (Pro,
Business and Ultimate).
Processor Pentium or Athlon @ 1 GHz
ORCAview supports multi-core processors.
RAM at least 2 GB
Disk Drive CD-ROM if installing from a CD, otherwise an electronic form
can be used
Hard Disk Drive 2 GB of free space for ORCAview
Video Settings 1024 x 768 resolution with 16-bit color
Modem USRobotics modem if dialup needed
Serial ports COM Ports for PTP direct use and Service Port Access
USB Ports For Service Port Access over a wireless connection
Windows 95, Microsoft Windows 98, Windows NT and Windows Millennium
Edition (ME), are NOT supported.
Windows 2003 and 2008 Server are supported for installing and running the
ORCAweb product.
Although ORCAview will run on many less capable machines, performance may
be much slower in many cases (e.g., Multi-Trends), and you risk other
performance-related problems. If any performance problems are encountered on
PCs not meeting these specifications, the first recommendation will be to upgrade
to a more suitable machine.
To run the Delta Controls ORCAview™ software, Delta Controls offers the
following recommended requirements:
Recommended Specification
Operating Vista 32/64 (Business, and Ultimate); 2008 Server; Windows 7
System 32/64 (Pro, Business and Ultimate).
Processor Intel Core 2 Duo – 2.6 GHz
RAM 4 GB+
Disk Drive CD-ROM if installing from a CD, otherwise an electronic form
can be used
Supported Scenarios
All scenarios will be supported for both default and custom install locations. If
you change only the disk drive letter in a default path, ORCAview still treats the
path as the default directory. For example, you might just change the C: to D: and
leave the rest of the default path unchanged. A custom install is one that has the
names in the default path changed.
Note: All scenarios will be supported for both default and custom install
locations.
Supported Scenarios
Case See Action
Clean Install New Suite installation with no existing Delta
Installation product installed
section on
page 1–3
Suite Build-to- Upgrade Upgrade ALL installed product from older
Built upgrade Installation build to latest build of the current version.
section on
page 1–18 All site specific files are upgraded if
necessary.
E.g. 3.40.2159 suite ->
3.40.3073 suite
Upgrading from a beta build is NOT
recommended. Uninstall the Beta build and
then re-install a released version..
Suite Version Upgrade Upgrade ALL installed product from older
Upgrade Installation version to current version.
section on
page 1–18 All site specific files are upgraded.
E.g. 3.33.1917 suite ->
3.40.3073 suite
Suite Version Upgrade If Historian is installed, it will not be possible
Upgrade, keep Installation to keep old OWS on upgrade.
previous OWS section on
page 1–18 The old OWS is not upgraded. A new 3.40
OWS is installed alongside it. All other
components are upgraded.
E.g. 3.33.1917 suite ->
3.33.1917 OWS and 3.40.3073
suite
Coexistence Coexistance Install the current version of OWS and
of OWS only Installation on Loaders alongside the existing older version
(with 3.40 now page 1–23 suite (excluding Historian).
includes
Coexistence Or, install the current version suite
of Loaders) (excluding Historian) alongside the existing
older version OWS and Loaders.
No site specific files are upgraded. Both
installations are treated as separate.
E.g. 3.33.1917 suite ->
3.33.1917 suite and 3.40.3073
OWS/SystemLoader ***
*** Once in this
configuration, and you want
to upgrade your suite to
3.40, you must remove 3.40
OWS and Loaders and then
upgrade your 3.33 suite.
E.g. 3.33.1917
OWS/FlashLoader -> 3.33.1917
OWS/FlashLoader and 3.40.3073
Supported Scenarios
Case See Action
suite
Complete Uninstall Uninstall ALL installed product of current
Removal Software topic Version only.
in Application
Maintenance E.g. 3.40.3073 suite -> no
section on product
page 1–30
Modify Add/Remove Add and/or Remove individual suite
Components, Software topic components to current installation of Delta
Add or in Application product.
Remove Maintenance
section on E.g. 3.40.3073 OWS and
page 1–27 ORCAweb -> 3.40.3073 OWS and
Historian
Repair Repair If a malfunction occurs such as power failure
Software topic and a software application no longer runs, it
in Application is possible to repair the installation quickly.
Maintenance The core files are refreshed and it is not
section on necessary to do an uninstall / install of the
page 1–29 software product and this approach saves
time.
Unsupported Scenarios
If the Suite Installer does not offer a particular install option, then this scenario is
not allowed by the installer.
Unsupported Scenarios
Partial Build-to-Build upgrade resulting in mixed builds of the current version.
Version Upgrade of versions older than 3.33 R2.
Version Coexistence if Historian installed.
Add or Remove components during an Upgrade.
Upgrade of versions older than 3.33 R2. Those version would first need to be
upgraded to 3.33 R2.
Uninstall of older versions.
Install mixed versions of various non-OWS/Loader products in the suite (e.g., 3.33
Web and 3.40 ODBC Driver).
In some cases, you would uninstall the Suite and then re-install it.
C:\Users\Public\Delta Controls\3.40\
New Installation
With 3.40, ORCAview has a suite installer which provides a choice of six
applications to install. You may have a CD or downloaded folder with an
executable install file named ORCA Suite Setup.exe.
In the previous figure, the checkbox for Delta ODBC Driver is Red indicating that
the software key does not have this product enabled. You can still select this
product for installation or press the Cancel button to exit. If installation is
completed without the software key fully enabled, the disenabled products will not
run.
Before you begin your installation you will need to do the following:
• Choose a directory – You may let the install program place ORCAview in the
default directory or choose a different destination. See OWS Default
Directories on page 1–71–7
If the directory does not exist, then the install program will create it.
• Determine the name of the site. For example, you could enter International
Airport.
• Determine the name of the workstation on your local network. For example,
you could enter Main ORCAview PC.
• Determine the number of the workstation on the network. See the following
section titled Workstation Number.
Workstation Number
Every device on the same site must have a unique controller number. ORCAview
calls this the workstation number. The PC that will receive the new ORCAview
installation must have a unique workstation number.
Note: Choose the workstation number carefully, as you must re-install the
software to change it. To avoid conflicting workstation numbers, maintain a
list of device numbers for large sites.
The PC where the new ORCAview is being installed must have a unique
workstation number assigned to it. The workstation number must:
• be different than any other workstation number,
• be different than any other controller address,
• not be 0, 254, 65534 or 65535
• not be greater than 4194302 if only V3 hardware
• not be within any Micro Panel range.
1. If the autorun does not bring up the interface, use the My Computer icon or
the Explorer view to find the ORCA Suite Setup.exe file.
See the detailed Installation Procedure section starting on page 1–11 for more
information.
See the detailed Installation Procedure section following on this page for more
information.
Note: If you plan to use Ethernet, install an Ethernet card before installing
ORCAview.
See the tables in the Suite Installer Function section starting on page 1–4 for
supported and unsupported install scenarios.
b. Turn off the PC and attach a software key to your USB or Parallel port.
When the key is attached, turn on the PC.
• USB Port: This software key that attaches to your USB port.
Caution: Never remove or attach the software key to the PC while the
power is on. The key may be damaged if this caution is not heeded.
e. Use the My Computer icon or Explorer to view the contents of the CD.
• If the autorun brings up the interface: Select the installer and follow the
instructions to complete the installation process. Go to step 2 of this
procedure.
• If the autorun does NOT bring up the interface: Find and open the
ORCAview 3.40 in the Delta V3.40 Software Suite Installer software
folder. Double click ORCA Suite Setup.exe file to start the Suite
Installer.
f. The install screen displays and the ORCAview installation starts.
2. Welcome screen.
a. At the Welcome screen, click Next.
a. Click next.
4. Select Products
For this example, the ORCAview OWS, Delta Flash loader and Delta System
loader are selected in the following figure. The other product options must be
unchecked. A red checkbox (Delta ODBC Driver) indicates that a product is not
enabled on the hardware key.
a. The install program chooses default folders for you. Click Browse to
choose or create another folder.
Note: If you change only the disk drive letter in a default path, ORCAview
still treats the path as the default directory. For example, you might just
change the C: to D: and leave the rest of the default path unchanged.
6. Workstation Setup
a. Enter the Site Name information. You must enter the Site Name.
b. Enter a Workstation Name for ORCAview.
Note: The Site and Workstation Name fields do not allow invalid
characters ( \ /:*?"’< >| $ #) and accept a maximum of 79 characters
assuming an installation that uses the default path.
9. Setup Complete.
a. All necessary files have been loaded onto your hard drive.
b. Click finish to complete Setup.
The Installation Procedure is finished. You may need to read First Time Login
Problems section on page 2–6 in Chapter 2 – Getting Started of the ORCAview
Technical Reference Manual.
Note: The firewall included with Windows XP may block the Siserver,
when you first run ORCAview after installation. On the Windows Security
Alert dialog, click Unblock to allow the Siserver program to run. This
message will only appear when logging in via UDP/IP.
MS HTML Help
ORCAview now uses the MS HTML help format (.chm) and the viewer is
included with Windows. Previously, it was necessary to download the
non-distributable Winhelp viewer from a Microsoft site.
Upgrade Installation
Caution: Although the Upgrade procedure will save site graphics and databases,
we strongly recommend that you back up these items. Also back up any other files
or objects you have created for your system.
During an upgrade, the installation program searches your computer for previous
versions of the Delta Controls ORCAview. If the previous version is found to be
incompatible with version 3.40, the installation program offers to uninstall the
previous version. If you click Yes, the previous version is uninstalled.
See the New Installation starting on page 1–7.
If the previous version is found to be compatible with version 3.40, the installation
program continues.
See the tables in the Suite Installer Function section starting on page 1–4 for
supported and unsupported install scenarios.
The 3.40 Suite Installer can only upgrade from 3.33. If you have an earlier version
(3.20 to 3.30), you need to first upgrade to 3.33 using the 3.33 Installer. The 3.40
Suite Installer can handle the upgrade from 3.33 to 3.40.
Note: If the palette, database or graphics files are large or numerous, the
upgrade process could be lengthy. The upgrade process might take an
hour depending on the size of the site and the performance of the PC.
Upgrade Procedure
Note: If the user stops the Upgrade process by clicking Cancel, then all
files are automatically restored to the original version by the Upgrade
Installation program.
Note: If you plan to use Ethernet, install an Ethernet card before installing
ORCAview. No special driver is needed to get Ethernet working as it uses
the Windows drivers.
4. Welcome screen.
5. Setup
If ORCAview detects an incompatible previous installation:
• You may need to upgrade from versions before 3.33 using the 3.33R2
installer which is included with the ORCA 3.40 suite.
• You may also need to uninstall the current products and then re-install them.
–OR–
6. The Ready to Upgrade dialog box appears. Click Next to continue the
Upgrade procedure.
a. The install program now begins copying files to your PC. When all files
are copied over to your PC, the install program upgrades any existing
graphics, palettes, or panel database files. If the palette, database or
graphics files are large or numerous, the upgrade process could be
lengthy.
b. The installation program shows the status of the file conversions and
upgrades.
Note: The ORCAview Installation program will now remove SNS, UDP,
and Tunnelling adapters from OWS databases during an upgrade. The
OWS will re-create these adapters from the registry bindings
automatically. This applies to upgrade of older pre 3.33R2 installations.
Coexistance Installation
Coexistance allows ORCAview Version 3.20/ 3.21/ 3.22/ 3.30/ 3.33 and 3.40 to
be installed on the same computer. With Windows XP, 3.33 can co-exist only with
3.30 or 3.22a.
ORCAview 3.40 does not support version independence which means that you
cannot have more than one instance of ORCAview 3.40 running at the same time.
See the tables in the Suite Installer Function section starting on page 1–4 for
supported and unsupported install scenarios.
4. Welcome.
b. Click Next.
6. Select Products
a. Select the products for installation and uncheck the one that you do not
want installed.
b. Click Next.
7. Destination Folder
a. Select the Program and data folders. You can just accept the default
paths.
b. Click Next.
8. Workstation setup
b. Click Next.
9. Ready to Install
Application Maintenance:
The Suite Installer allows you to change your install by adding, removing,
repairing or uninstalling selected software.
See the tables in the Suite Installer Function section starting on page 1–4 for
supported and unsupported install scenarios.
Add/Remove Software
1. In the following figure, the Add/remove 3.40 ORCA Suite software option is
selected.
2. Click Next.
Note: You cannot use the Add/remove option to uninstall the whole ORCA
Software suite. At least one option must be selected. To uninstall the
whole suite, you use the Uninstall your 3.40 ORCA Suite software option.
The following figure shows that Flash Loader will be removed. The ORCAview
OWS (333.1917) and (3.40.3073) will remain.
4. Ready to Modify
Repair Software
The Repair option provides a way to put the core files of a selected product back
to their initial conditions. For example, if a product malfunction occurs after a
power failure, Repair would refresh the core files quickly. It avoids the need to
take the time to do a complete uninstall / re-install sequence.
1. Application Maintenance
b. Click Next.
2. Ready to Repair
Uninstall Software
Uninstall provides a way to remove selected software.
1. Application Maintenance
b. Click Next.
2. Ready to Uninstall
3. Setup Complete
a. Click Finish.
See the tables in the Suite Installer Function section starting on page 1–4 for
supported and unsupported install scenarios.
The releases build will be 3073 or later. This example uses Build 3.40.3051.
Note: With the ORCA 3.40 Suite Installer, you do NOT need to install
OWS first and then log in over the desired network connection before
beginning to install Historian. This approach was necessary with 3.33R2.
1. If the autorun does not bring up the interface, use the My Computer icon or
the Explorer view to find the ORCA Suite Setup.exe file.
2. Double-click ORCA Suite Setup.exe file to start the Suite Installer.
3. Follow the instructions from the Welcome screen to complete the installation
process.
With Microsoft SQL Server 2005 Express, you need to define a strong password
which means that the password contains a variety of character types. A strong
password contains a combination of lowercase, uppercase, numbers and special
characters such as $ or # etc.
a. Enter a password.
b. Click next.
2 License Agreement
b. Click Next.
3 Installing Prerequisites
5 Completing Setup
a. Inspect the summary logs to see if any failures occurred during setup.
6 Password
c. Click Next.
b. Click Next.
8 ORCA Suite
a. Click Finish.
The 3.40 CD includes the version 7.5.1 Sentinel System Driver Installer in \Delta
Software Suite - V3.40 Release 1.0\Delta V3.40 Software Suite Installer\Third
Party Software.
To manually update the Sentinel driver from the ORCAview 3.40 CD:
1 Close all programs.
2 Insert the CD into the CD-ROM drive.
3 Use the My Computer icon or Explorer to view the contents of the CD.
4 Open the Delta V3.40 Software Suite Installer\Third Party Software folder on
the release CD.
5 Find the Sentinel_System_Driver_Installer_7.5.1 file and double click it.
6 Sentinel System Driver – InstallShield Wizard
Caution: Do not use a shortcut providing automatic login unless you are
certain the site does not need username and password security, or, that
the username automatically logged in lacks permission to alter security
objects such as the SUA and UA objects or objects otherwise important to
site functions.
When you use the shortcut for automatic login, the following objects will exist on
your system:
• A System User Access (SUA) object in the ORCAview PC that uses the
automatic-login username and password. — If not, then you must create a
SUA object in the ORCAview PC containing the username and password.
(See the Creating a New User section in the System Security chapter.)
• A System User Access (SUA) object in the Network Security Panel that uses
the automatic-login username and password. — If not then you must create
such a SUA object. (See the Creating a New User section in the System
Security chapter.)
• A Site Settings (SS) object in the ORCAview PC that uses the site-name.
If not then you must create a SS object using the site name that you intend to
enter for automatic login. You cannot alter an existing SS object. (See the
Multiple Sites section in the Navigator chapter.)
2. In the Shortcut tab, there is a Target field that specifies the shortcut path. In
Windows 7- 32 bit:
"C:\Program Files (x86)\Delta Controls\3.40\System\ORCAview.exe"
In Windows XP:
“C:\Program Files\Delta Controls\3.40\System\ORCAview.exe”.
After the last quotation mark in the shortcut path, leave one space and then
type the following information:
user=username/password site=sitename.
You place your username/password and sitename after the shortcut path in the
target field. The modified target field will read:
Note: The username and password must not contain spaces. The
sitename may contain a space between the first and last letter of the
sitename but must be in quotations. Example: site= “site name”. The
following invalid characters cannot be used in the username, password, or
site name: ! \ / * ? : “ ‘ < > | $ #
System Architecture
System architecture is defined as the design of a communications system, which
includes the hardware, software, access methods, protocols, and method of
control.
The following figures explain the ORCA hardware architecture and illustrate the
use of Delta Control hardware in typical networks.
• Architecture Design
• Ethernet – BACnet MS/TP
• Operator Workstation Connections
See Appendix E — Working with MS/TP and LINKnet of this manual to configure
and program these products.
See Appendix F — Service Port Access of this manual for an explanation of how
to use ORCAview typically on a laptop to connect to a network using the Service
Jack on a DAC, DSC or BACstat controller. Use of the CON-768 and newer
CON-768BT converters is explained.
Architecture Design
The ORCA Hardware architecture is based on a hierarchical design. This allows
for simple and efficient communications in large Wide Area Networks and small
stand-alone systems. The ORCA® architecture is extremely flexible and can be
built up in a variety of configurations.
There are four levels to the ORCA hardware architecture: AREA level, SYSTEM
level, SUBNET level, and LINKnet level. AREA Level controllers are primarily
used to break-up large segments of a WAN. One controller per segment may be
configured as an AREA Level controller.
AREA Level
DSC-1212E, DSC-1616E,
DSC-1280E, DSM RTR
SYSTEM Level
SUBNET Level
LINKnet Level
Ethernet
System Level
DSC-1616E or
DSC-1212E or DSC DSC DSC
DSC-1280E or
DSC-1616EX
Subnet Level
DAC
DACs
DAC
communicating @ 76.8 Kbaud
LINKnet Newtork
LINKnet Level
DNS-24
DFM-202
There are also several standard connection points such as EIA-232 ports using
BACnet PTP, directly or through a modem.
There is a service port on most Delta ORCA hardware. This service port supplies
power to the EIA-232/485 converter (CON-768) or wireless Bluetooth to wired
RS-485 CON-768BT converter so that the operator does not have to provide a
separate power supply for powering the converter.
Ethernet
INTERNET
BACnet MSTP connection
through the Service Port
Modem using Delta's CON-768
BACnet MSTP Network
DSC-1616E, DSC-1212E,
DSC-1280E, DSC-1616EX, BACnet MSTP connection
DSM RTR through the Service Port
using Delta's CON-768
(EIA-232 / EIA-485 Converter)
Laptop computer
communicating @ 76.8 Kbaud
Workstation
LINKnet Newtork
DFM-202
Object created virtually
in Device 101