Image Not Available
Current Version: 2.1
The PC-OPC/10 offers ten licenses of PC-OPC at a reduced cost per copy. It is intended to allow data to be transferred from a LoggerNet server to multiple client computers.
The CSI OPC Server uses the OPC standard interface to allow third-party, OPC-compatible graphics packages to view data from the LoggerNet server. This software provides a simple browser interface that allows you to easily select the values you want to display. It also allows you to view input locations, final storage data, and LoggerNet communications server statistics, as well as perform control operations.Read More
PC-OPC/10 provides ten licenses of PC-OPC at a reduced cost per copy. It is intended to allow data to be transferred from a LoggerNet server to multiple client computers.
The PC-OPC server provides a standard interface that allows third-party OPC-compatible graphics packages to display the datalogger data. Specifically, the PC-OPC Server:
|Operating System||Windows 7, Vista, 2000, or XP|
|Data Access Standard||Supports Data Access Standard 2.05a only.|
|Requirement||Requires a licensed copy of LoggerNet running on the same PC or a remote PC that is accessible via TCP/IP.|
Requires a licensed copy of LoggerNet running on the same PC or a remote PC that is accessible via TCP/IP.
Many software and hardware products support OPC. Products that have been tested by Campbell Scientific include Iconics Genesis, Intellution IFIX, and National Instruments Lookout. PC-OPC supports Data Access Standard 2.05a only.
Minimum recommended hardware is 300 MHz Pentium II processor with 128 Mbyte of RAM and screen resolution of 800 x 600. Recommended computer operating systems are Windows Vista, 2000, and XP.
|CR200(X) Series||CR800/CR850||CR1000||CR3000||CR9000X||CR300 Series||CR1000X|
*For our CR510, CR10X, and CR23X dataloggers, LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
**The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.
Number of FAQs related to PC-OPC/10: 5
Expand AllCollapse All
The PC-OPC Server works with OPC Data Access Specification 2.05a.
The PC-OPC Server demo enables users to verify if an OPC client will work with Campbell Scientific’s OPC server. The trial version doesn't actually connect to a LoggerNet server or provide any true data. It only provides mock data.
The blog article "How to Navigate the World of Software Upgrades, Patches, and Trials" explains the difference between patches (free of charge) and upgrades (for a fee). This example quickly shows the difference between an upgrade and a patch:
Major version change, such as 1.3 to 2.0
Minor version change, such as 1.3 to 1.4
Typically requires purchase for a fee
Free of charge
Campbell Scientific dataloggers cannot communicate directly with LabVIEW. However, after retrieving data collected by any of the Campbell Scientific dataloggers and placing the data in the LoggerNet data cache, the data can be shared with LabVIEW using a LoggerNet client called PC-OPC. A trial version of PC-OPC is available in the Downloads section of the PC-OPC product page.
The PC-OPC Server software provides a standard interface that allows third-party OPC-compatible graphics packages, including LabVIEW, to display the datalogger data.
In addition to using the PC-OPC Server and the data socket feature in LabVIEW, communication can also be established using LoggerNet-SDK with ActiveX controls.
If the OPC client software supports getting data from an SQL server, LoggerNet Database Software (LNDB) may be a more appropriate option than PC-OPC. LNDB stores a complete history of data tables retrieved from the dataloggers in an SQL server. In contrast, PC-OPC only provides the last record from each data table in the LoggerNet cache when it is first started and any new records that are collected by LoggerNet while the PC-OPC Server is running. If the OPC client is storing PC-OPC data in its own database, gaps will be created (missing data) in the OPC client database if the PC-OPC Server, the OPC client, or both are not running when LoggerNet collects the data.