Related Manuals for Campbell CSIOPC
Summary of Contents for Campbell CSIOPC
- Page 1 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 .
- Page 3 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.
-
Page 4: Limited Warranty
Campbell Scientific has been advised of the possibility of such damages. Campbell Scientific is not responsible for any costs incurred as a result of lost profits or revenue, loss of use of the software, loss of data, cost of re-creating lost data, the cost of any substitute program, telecommunication access costs, claims by any party other than licensee, or for other similar costs. -
Page 5: Table Of Contents
Application..............2 4. Identifying Data Values ..........4 4.1 Data Tags....................4 4.2 CSIOPCServer Browser ................5 5. Data Reliability .............5 5.1 OPC Technology and Campbell Scientific Dataloggers......5 5.2 Data Quality....................5 6. Technical Notes ............6 6.1 Registering the CSIOPCServer..............6 6.2 DCOM ......................6 6.3 Server and Device Operational Statistics..........6 6.3.1 Device History Statistics..............7... -
Page 7: What Is Opc And Csiopcserver
Programs | Campbell Scientific OPC Server from the Windows start button. An icon, similar to that shown above, will appear in the... -
Page 8: Providing Data To Multiple Computers
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). - Page 9 CSIOPCServer The diagram below depicts the flow of information between the datalogger network, LoggerNet communications server, LoggerNet client applications, and remote clients. Datalogger Network Options: * Direct Connect * Phone Telecommunications * RF * TCP/IP * MD485 * etc. PC Running LoggerNet Communications Server LoggerNet’s Data Cache...
-
Page 10: Identifying Data Values
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. -
Page 11: Csiopcserver Browser
5. Data Reliability 5.1 OPC Technology and Campbell Scientific Dataloggers OPC technology relies on consistent data from the OPC server. It expects that the structure of the data being passed from the server will not change. -
Page 12: Technical Notes
CSIOPCServer /UnregServer 6.2 DCOM CSIOPCServer has not been tested for DCOM compatibility. Therefore, DCOM implementation is not supported by Campbell Scientific. We do not support running the CSIOPCServer on one DC to feed ODC clients on other PCs. 6.3 Server and Device Operational Statistics The server controller and individual devices maintain statistics that help to describe their operation. -
Page 13: Device History Statistics
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. - Page 14 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.
- Page 15 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.7 Last Clk Chk Type: stamp...
- Page 16 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.
- Page 17 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.
- Page 18 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.
- Page 19 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.
- Page 20 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...
-
Page 21: Server Statistics
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... - Page 22 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.
- Page 24 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)