CSIOPCServer User’s Manual and Installation Guide Revision: 10/09 C o p y r i g h t © 2 0 0 1 - 2 0 0 9 C a m p b e l l S c i e n t i f i c , I n c .
License for Use This software is protected by United States copyright law and international copyright treaty provisions. The installation and use of this software constitutes an agreement to abide by the provisions of this license agreement. Campbell Scientific grants you a non-exclusive license to use this software in accordance with the following: (1) The purchase of this software allows you to install and use the software on one computer only.
Limited Warranty The following warranties are in effect for ninety (90) days from the date of shipment of the original purchase. These warranties are not extended by the installation of upgrades or patches offered free of charge. Campbell Scientific warrants that the installation media on which the software is recorded and the documentation provided with it are free from physical defects in materials and workmanship under normal use.
CSIOPCServer Table of Contents PDF viewers note: These page numbers refer to the printed version of this document. Use the Adobe Acrobat® bookmarks tab for links to specific sections. 1. What is OPC and CSIOPCServer?..............................1 2. Hardware/Software Requirements and Installation ..1 2.1 Running the CSIOPCServer .....................................................................1 2.2 Providing Data to Multiple Computers.....................................................2 3.
CSIOPCServer 1. What is OPC and CSIOPCServer? OPC is an acronym for "OLE (Object Linking and Embedding) for Process Control". It is a set of industry standards, based on Microsoft's OLE technology, designed to provide a common interface between automation and control hardware and software. The OPC specifications were developed by a group of organizations involved in the automation and control industries in conjunction with Microsoft Corporation.
CSIOPCServer NOTE Because the CSIOPCServer registration information is written to the Windows registry, if the executable is moved to another directory the registry must be edited to reflect this change. Refer to Section 6.1 for additional information. 2.2 Providing Data to Multiple Computers The CSIOPCServer is designed to run on the same computer as the OPC client(s). Therefore, a copy of the CSIOPCServer must be running on each computer for which it will be providing data.
CSIOPCServer The diagram below depicts the flow of information between the datalogger network, LoggerNet communications server, LoggerNet client applications, and remote clients. Datalogger Network Telecommunications LoggerNet’s Data Cache Options: * Direct Connect * Phone * RF * TCP/IP * MD485 * etc.
CSIOPCServer Note that data must be collected from a datalogger and stored in the LoggerNet data cache before that data will be available to OPC clients. Use LoggerNet's Setup screen client to define the data tables to be collected and the schedule on which the data should be stored in the data cache. 4. Identifying Data Values 4.1 Data Tags A data tag is a text-based identifier for a specific data value that is being passed from the LoggerNet communications server to an OPC client via the CSIOPCServer.
CSIOPCServer NOTE The format may vary somewhat from the examples given above, depending upon the client. 4.2 CSIOPCServer Browser The CSIOPCServer allows OPC Universal Tag compliant browsing so that data tag names can be searched for from within an OPC application. The browser provides a list of all dataloggers in the network map and their associated data tables.
CSIOPCServer • The specified data tag does not exist in the datalogger table (because an error was typed when entering the data tag directly, a new program was downloaded to the datalogger, or the data tag was removed from the datalogger program). • The table for a specified data tag does not exist or is not being collected by the LoggerNet communications server.
CSIOPCServer Each device in the network map is represented by two tables in the statistics device. The names of these tables are the result of appending the strings “_hist” and “_std” to the device name. The network controller also maintains statistics regarding the operation of the communications server as a whole. These statistics are available in the “_ _LgrNet_ _ _ _controller_ _” table. 6.3.
CSIOPCServer 6.3.2.1 Communication Enabled Type: boolean Applies to: all device types Description: Relates whether communication is enabled for this device. 6.3.2.2 Average Error % Type: float Applies to: all device types Description: A running average of the number of “W” or “F” messages that are logged in the communication status log for the device versus the total number of messages logged. 6.3.2.
CSIOPCServer Description: Describes the current communication state of the device. The following values are defined: 1. normal (last communication succeeded) 2. marginal (last communication needs to be retried) 3. critical (last communication failed) 4. unknown (No communication attempt has failed since last reset or the device was started) 6.3.2.
CSIOPCServer 6.3.2.11 Last Data Coll Type: stamp Applies to: 21X, CR7X, CR10, CR10X, CR500, CR510, CR23X, CR10T, CR10X-TD, CR510T, CR23X-TD, CR9000, CR5000, CR10X-PB, CR510-PB, CR23X-PB, CR200 Series, CR800, CR1000, CR3000 Description: The server time when the last data collection took place for the datalogger. This statistic will be updated after a manual poll or scheduled data collection succeeds or partially succeeds (brings in some data from some areas but not all data from all selected areas). 6.3.2.
CSIOPCServer 5. comm disabled - Communications for this device, one of its parents, or for the whole network is disabled. 6. invalid table defs - Collection for this station is disabled until the table definitions are refreshed. 7. network paused - Automated operations are paused for the network either because the scheduledOn setting is turned off or because the server application DLL (coralib3.dll and newer) has not yet been enabled for automation. 8.
CSIOPCServer 6.3.2.19 Line State Type: enumeration Applies to: All devices except BMP5 (PakBus) dataloggers Description: The current line state for this device. The following values are defined: 1. not-applicable — In its current configuration, this device will not communicate directly with the server. This value will appear in association with BMP1 dataloggers connected to the server through an RF95T. 2. off-line — The server has no communication resources open for this device. 3.
CSIOPCServer Description: Reflects the total number of final storage values that need to be collected from final storage area one of a classic datalogger if collection is active for that area. If collection is not active for that area, this statistic reflects the last count that should have been collected. 6.3.2.
CSIOPCServer 6.3.2.27 Prog Overrun Type: uint4 Applies to: 21X, CR7X, CR10, CR10X, CR500, CR510, CR23X Description: Relates the number of datalogger program overruns that have occurred since the last reset as given in the classic datalogger’s response to the “A” command. 6.3.2.28 Mem Code Type: uint4 Applies to: 21X, CR7X, CR10, CR10X, CR500, CR510, CR23X Description: Relates the memory size code as given by the classic datalogger’s response to the “A” command. 6.3.2.
CSIOPCServer 6.3.2.32 Lith Batt Volt Type: float Applies to: CR10X, CR500, CR510, CR23X Description: Reports the lithium battery voltage on classic dataloggers. This value is extracted from the results of the “A” command. 6.3.2.33 Table Defs State Type: enumeration Applies to: CR10T, CR10X-TD, CR510T, CR23X-TD, CR9000, CR5000, CR10X-PB, CR510-PB, CR23XPB, CR200 Series, CR800, CR1000, CR300 Description: Relates the current state of cached table definitions for a table based (BMP1, BMP3, or BMP5) datalogger.
CSIOPCServer 6.3.3.2 Avail Virt Mem Type: uint4 Description: Relates the amount of virtual memory that is available to the server process. 6.3.3.3 Used Virt Mem Type: uint4 Description: Relates the amount of virtual memory that is being used by the server process. This value is derived from the AvailVirtMem by subtracting the value of that statistic from the maximum size win32 memory space (2 31- 1).
Campbell Scientific Companies Campbell Scientific, Inc. (CSI) 815 West 1800 North Logan, Utah 84321 UNITED STATES www.campbellsci.com • info@campbellsci.com Campbell Scientific Africa Pty. Ltd. (CSAf) PO Box 2450 Somerset West 7129 SOUTH AFRICA www.csafrica.co.za • cleroux@csafrica.co.za Campbell Scientific Australia Pty. Ltd. (CSA) PO Box 444 Thuringowa Central QLD 4812 AUSTRALIA www.campbellsci.com.au • info@campbellsci.com.au Campbell Scientific do Brazil Ltda.
