Академический Документы
Профессиональный Документы
Культура Документы
How to Contact Us
Phone Fax Internet World Wide Web Bulletin Board (510) 297-5800 (510) 297-5828 (510) 357-8136 techsupport@osisoft.com http://www.osisoft.com (510) 895-9423 Telebit WorldBlazer modem (Hayes, MNP, or PEP compatible) 8 data bits, 1 stop bit, no parity, up to 14400 bps download protocols: Xmodem, Ymodem, Zmodem, Kermit OSI Software, Inc. P.O. Box 727 San Leandro, CA 94577-0427 USA OSI Software GmbH Hauptstra e 30 D-63674 Altenstadt 1 Deutschland OSI Software, Ltd P. O. Box 8256 Level One, 6-8 Nugent Street Auckland 3, New Zealand (main number) (technical support)
Unpublished -- rights reserved under the copyright laws of the United States. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 Trademark statementPI is a registered trademark of OSI Software, Inc. Microsoft Windows, Microsoft Windows for Workgroups, and Microsoft NT are registered trademarks of Microsoft Corporation. Solaris is a registered trademark of Sun Microsystems. HP-UX is a registered trademark of Hewlett Packard Corp.. IBM AIX RS/6000 is a registered trademark of the IBM Corporation. DUX, DEC VAX and DEC Alpha are registered trademarks of the Digital Equipment Corporation. 84314134.doc
1997 OSI Software, Inc. All rights reserved 777 Davis Street, Suite 250, San Leandro, CA 94577
10/15/2004 10:48:00 AM
ii
Table of Contents
OSI PINET DECNET................................................................................................................i How to Contact Us..................................................................................................................ii Table of Contents...................................................................................................................iii Introduction.............................................................................................................................1 Installation and Upgrades.......................................................................................................2 Directories...............................................................................................................................3 Startup and Shutdown............................................................................................................4 Satellite Node Utilities.............................................................................................................5 IORates Tags..........................................................................................................................6 Shutdown Events....................................................................................................................7 Satellite Node Processes........................................................................................................8 Toolkit.....................................................................................................................................9
January 9, 1997
iii
Introduction
This chapter describes the software that supports distributed applications for a PI System. The distributed applications are usually interface programs which run in a VAX which is connected by DECnet to a PI System. These applications can also be programs developed with the PI Toolkit. The DECnet node with the distributed application program is called the satellite node. The node with the PI System is called the home node. There can be several satellite nodes connected to a PI home node. The software on the satellite node is a subset of a full PI System. Programs on the satellite node can read the following data: Point Attributes (Tag, Description, Zero, Span, etc.) Snapshot Archive Engineering Unit Strings Digital State Strings Point Source Table
The satellite node can also send values and messages to the home node. The previous chapter lists the routines from the PI Toolkit library which are supported on satellite nodes. The satellite node set its system time to match that of the home node. It compares its system time to that of the home node every hour. The satellite node time is updated if it is different from the home node time by more than 10 seconds. Process PINetSync performs this check and writes a message to PINet:PIMessLog.txt whenever it changes the VMS time. The satellite node can buffer data for times when PI is not running on the home node or the network is down. The satellite node can be restarted even if PI is not running on the home node.
January 9, 1997
Directories
There are two pertinent directories on the satellite node, PINet and PINetBuild. These are system logical names that usually translate to global directories [PINet] and [PINetBuild]. The PINet directory includes files that are found in the PISysExe, PISysMgr, and PISysDat directories on the home node. The PINetBuild directory combines the PIBuild and PILink directories of the home node. Directories PINet PISysEx e PISysMg r PISysDa t PINetBuil d PIBuild PILink
January 9, 1997
January 9, 1997
IORates Tags
The IORates tag for an interface program works the same as on a home node. The only difference is that the tag should be put in PINet:IORates.dat on the satellite node instead of PISysDat:IORates.dat on the home node. Three other rate tags can be defined which have to do with satellite nodes. On the home node, a tag can be added to IORates.dat to record the rate of events from all the satellite nodes. This tag uses counter number 42. Add a line to IORates.dat that looks like: SY:SRV001,42 On the satellite node, tags can be added to IORates.dat to record the snapshot rate (event counter 47) and the rate that the Event Manager is sending events to programs using the EVM routines (event counter 46). These are the same counter numbers that are used on the home node but the tag names must be different.
Shutdown Events
The satellite node should add shutdown events for tags for which it collects data. Modify PINet:ShutdownEvents.com and PINet:CheckForCrash.com to add shutdown events for those tags. All satellite nodes add shutdown events for the tags in IORates.dat. Most satellite nodes also add shutdown events for tags with the point source code for the distributed interface program. The last non-comment line in each command file looks like: $ ShutDownEvents 'TimeDate',PINet:IORates.dat,F On the home node, modify PISysExe:ShutdownEvents.com and PISysExe:CheckForCrash.com to avoid adding shutdown events for tags from the satellite node. The PI System on the home node can shutdown and restart without losing data from the distributed interface.
January 9, 1997
Toolkit
The Interface Standard chapter of this manual lists the PI Toolkit routines which work on PINet nodes. Also, the PI Toolkit manual shows with each routine whether or not it is supported on PINet nodes. PINet nodes keep track of which points are being collected on that node. The first time a value is sent to PI for a tag (with PutSnapshot or PISendExceptions), a flag is set. This flag is reset only when PINet is restarted. Routine GetSnapshot uses this flag to determine whether to retreive the snapshot value locally or whether to make a network read to retrieve a snapshot value from the home node. This prevents unnecessary network traffic for applications which use only points collected on the PINet node. This may cause a problem if a point is updated both from the PINet node and from the home node. When routine GetSnapshot is used with one of these points, the value returned will be the most recent value entered from the PINet node. Routine PINetGetSnapshot has the same calling sequence as GetSnapshot but always makes a network read from the home node to ensure that it is returning the most recent value for a tag. This routine should be used only in programs which run on a PINet node look at snapshot values for tags with GetSnapshot are using tags which are receiving values from the PINet node and some other node.
If some tags are collected locally and some tags are updated from the home node, GetSnapshot works fine. PINetGetSnapshot is necessary only when tags receive values from multiple sources.
January 9, 1997