Current Version for iOS: 1.3
Current Version for Android: 1.3.2
LoggerLink Mobile Apps are simple yet powerful tools that allow an iOS or Android device to communicate with our CR200X, CR800, CR850, CR1000, CR3000, or CR6 dataloggers via an IP device (NL115, NL116, NL120, NL121, NL201, NL240, RavenXTV, RavenXTG, LS300G). LoggerLink for Android also supports Bluetooth communication for these same dataloggers using an RS-232-Bluetooth adapter. The apps support field maintenance tasks such as viewing and collecting data, setting the clock, and downloading programs.
Note: An Android device will not, by default, connect to an ad hoc network. However, some smartphones and tablets may be configured so that they will work in an ad hoc network. Consult with your wireless provider for information on setting up your device for connection to an ad hoc network. For more information about ad hoc networks, see the Compatibility information.Read More
The LoggerLink apps have the following pages that allow access to the features in the software:
1Refer to the Compatibility section for more information about the mobile device and datalogger compatibility.
iOS-based and Android-based devices are compatible. (See the table.)
|Supported Device||Required Operating System|
|iPod Touch||iOS 6 or later|
|iPad||iOS 6 or later|
|iPhone||iOS 6 or later|
|Android tablet||Android OS 4.0.3 or later|
|Android smart phone||Android OS 4.0.3 or later|
The iOS or Android device communicates with the datalogger via an IP device (NL115, NL116, NL120, NL121, NL201, NL240, RavenXTV, RavenXTG, LS300G). LoggerLink for Android also supports Bluetooth communication for the same dataloggers using an RS-232-Bluetooth adapter.
The following table illustrates which communication options are appropriate for the two LoggerLink applications (Android and iOS).
|Wired Ethernet||Wireless Infrastructure Network||Wireless Ad Hoc Network||Bluetooth 2.0|
|LoggerLink Android||See explanation below|
LoggerLink for Android can be used to communicate with any of its supported dataloggers over IP-based or Bluetooth 2.0 communication. There are some items of note, however, when considering your communication options.
IP-based communication options include wired Ethernet devices (such as Campbell Scientific’s NL116 and NL121) and devices that use a wireless communication protocol (such as our NL240). Wireless networks can be set up in infrastructure mode where a central router or access point is in place, or in ad hoc mode where there is no central point of access and all devices in the network communicate with each other on a peer-to-peer basis.
If the communications link to the datalogger is via a wired Ethernet connection, simply type in the IP address of the datalogger to connect. If the communications link is via a wireless network configured in infrastructure mode, the Android device can connect to the network’s Wi-Fi access point or cellular network, which, in turn, provides an IP connection for LoggerLink to use.
However, by default, the ability for an Android device to join an ad hoc network that is initiated by another device is disabled in the Android OS. In this situation, the Android device can be configured as a Wi-Fi hotspot, and the wireless device in the ad hoc network that provides the connection to the datalogger can be set up to connect to it. This situation would occur, for example, if an NL240 was used without an external wireless or cellular network. The Android device would be set up as a wireless hotspot, and the NL240 would connect to that hotspot.
LoggerLink for iOS supports IP-based communication only (both wired and wireless Ethernet). Ad hoc networks are fully supported by iOS. Support for communication over Bluetooth is not available, because Apple does not allow serial port protocol over Bluetooth 2.0 for commercial use.
Number of FAQs related to LoggerLink: 14
Expand AllCollapse All
LoggerLink stores datalogger setup information in a file named logger_settings.sqlite. This file can be accessed through iTunes and File Sharing, and it can be saved to a computer and then copied onto any number of iOS devices.
By default, the graph doesn’t have any data configured. It is necessary to select a data table and the fields to be graphed. The data range for the graph may also need to be modified to accommodate the range of data to be displayed.
No. LoggerLink is not compatible with FTP.
No. There are currently no plans to develop a cabled connection to LoggerLink, as there are too many different connection types and certification requirements to pursue cabled connection options.
LoggerLink supports all TCP connections with Campbell Scientific dataloggers. However, some network types are not supported by all devices. For example, ad-hoc networks are supported on iOS devices, but they are not supported on Android devices.
The creation of new datalogger programs is currently not operational in LoggerLink. LoggerLink does support the editing of existing program files, but it does not currently provide an editing environment similar to the CRBasic Editor. The level of program editing supported by LoggerLink allows for small tweaks to parameters or the modification of constants.
No. LoggerLink is not currently compatible with alarming.
Valid security codes for dataloggers are 1 through 65535. However, the datalogger OS will allow a negative code or a code greater than 65535 to be entered. If a code is greater than 65535, either the datalogger will cut off the most significant 16 bits or a negative value will be entered with the 65535.
LoggerNet allows this invalid range, and the datalogger does the math to derive the proper code. With LoggerLink, however, the field has been restricted to the valid range. Therefore, the math needs to be done to enter the real code in the datalogger. An easy way to do the math is to use Windows Calculator:
No. LoggerLink doesn’t require a static IP address, but the current IP address is needed for communication with the datalogger. This may require changing the datalogger setup frequently in LoggerLink. On some networks, the LoggerLink UDP discovery setup option may make dataloggers with dynamic addresses easier to find.
With static IP addresses or domain names, it should not be necessary to change the datalogger setup in LoggerLink.