Current Version: 4.5
LoggerNet-SDK is a flexible and powerful programming tool that creates innovative client applications (such as Setup, Connect, Status Monitor) for communicating with our dataloggers. It includes a reduced LoggerNet server that only allows direct RS-232 and IP communication links. LoggerNet-SDK can also be used to customize client applications that extend an existing LoggerNet installation with all of its possible communication links.Read More
LoggerNet-SDK includes ActiveX controls that encapsulate some of the fundamental tasks users want to perform with our dataloggers. It also provides a limited LoggerNet Server that allows direct RS-232 and IP port connections with a single datalogger.
LoggerNet-SDK supports any datalogger that can be supported by the LoggerNet server. It is compatible with the mixed array, PakBus®, and TD datalogger operating systems for the CR510, CR10X, and CR23X dataloggers.
Number of FAQs related to LOGGERNET-SDK: 6
Expand AllCollapse All
Check the connection between the SDK app and the LoggerNet server. This, of course, assumes that the LoggerNet server is remote and accessible to the SDK app via TCP/IP. Is the physical TCP/IP connection constant? Is there intermittent service?
The other possibility is that the LoggerNet server is being stopped from time to time. When the LoggerNet server stops, the SDK app gets this error code.
Yes, as part of the SDK—the CSIDataSource control.
This can only be done by sending a different program using the FileControl() or File_Send() instruction. Data tables in a datalogger cannot be added or deleted at datalogger runtime using any of our datalogger communication software, such as LoggerNet, PC400, PC200W, or any of the SDKs. Changes (additions, deletions, or modifications) to data tables within a datalogger have to be changed inside the actual datalogger program using a program editor such as CRBasic. After the data tables are modified within the program, the program must be resent to the datalogger. Compiling the new program on the datalogger will reset and create new tables as defined by the program.
To clear a data table (zero out the data), the CoraScript control, found in either the LoggerNet-SDK or the LoggerNet Server SDK, would need to be used. This functionality does not exist in the BMP5 Direct SDK.
This is not supported in the BMP5 Direct SDK. The options available are to specify a starting record number, get the most recent record, or collect all available records. When specifying a starting record, all data from that record forward is then retrieved. The burden is on the programmer that uses the SDK to keep track of the last record number retrieved within the program and then to retrieve what is needed or desired in the future.
The functionality to specify a date/time data collection range is available in the LoggerNet-SDK and the LoggerNet Server SDK. Both the LoggerNet-SDK and the LoggerNet Server SDK are available for purchase from Campbell Scientific.
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.