1. Scope of Supply............................................................................................................................................... 8
2. General Safety Information ........................................................................................................................... 10
4.3.Earth Ground Point ................................................................................................................................ 20
4.4.Connecting the GOES/METEOSAT/INSAT antenna ................................................................................ 20
4.5.Connecting the GPS Antenna ................................................................................................................. 21
4.6.Connecting the Power Supply ................................................................................................................ 21
4.12.Connecting 0-5V Analog Sensors ........................................................................................................... 25
4.13.Connecting 4-20ma Analog Sensors ....................................................................................................... 25
4.14.Connecting Status Sensors ..................................................................................................................... 26
4.23.Connecting Digital Outputs .................................................................................................................... 33
4.24.Connecting Samplers Triggered by Stage ............................................................................................... 34
4.25.Connecting to the Switched Power ........................................................................................................ 34
4.26.Connecting Protected Power ................................................................................................................. 34
5. Installing and Running LinkComm ................................................................................................................. 37
5.1.Installing the LinkComm mobile app ...................................................................................................... 37
5.2.Installing the PC version of LinkComm ................................................................................................... 37
5.3.Stations List View ................................................................................................................................... 37
5.4.Main Menu ............................................................................................................................................. 42
5.13.Password Menu ...................................................................................................................................... 57
5.14.Quick Status Dialog ................................................................................................................................ 58
6.7.Examine Transmission Data ................................................................................................................... 60
6.8.Entering Manual Data ............................................................................................................................ 60
6.11.Downloading Log Data ........................................................................................................................... 60
6.12.Viewing/Clearing the Status ................................................................................................................... 61
6.13.Software Version .................................................................................................................................... 61
6.14.Setting Time ........................................................................................................................................... 61
6.15.USB Thumb Drive (Flash Drive) Operation ............................................................................................. 62
10.6.Telemetry Status .................................................................................................................................. 111
11. Other Setup ................................................................................................................................................ 115
12.3.Missing Data Retrieval .......................................................................................................................... 125
13.1.Downloading the Log ........................................................................................................................... 128
13.3.Logged Time ......................................................................................................................................... 129
15. Transmission Data Formats ......................................................................................................................... 134
15.1.Pseudobinary B Data Format ............................................................................................................... 134
15.2.Pseudobinary C Data Format ............................................................................................................... 139
15.3.Pseudobinary D Data Format ............................................................................................................... 141
15.4.Six Bit Binary Encoded Format ............................................................................................................. 143
15.5.Pseudobinary over SMS ....................................................................................................................... 144
15.6.SHEF and SHEFFIX Data Format ............................................................................................................ 144
15.7.Sutron Standard CSV ............................................................................................................................ 146
16. Connecting to Another Logger .................................................................................................................... 152
16.3.Transmit Data ....................................................................................................................................... 154
17.7.Downloading the Log ........................................................................................................................... 161
17.8.Machine-to-Machine Communication ................................................................................................. 162
18. See the Security .......................................................................................................................................... 165
18.1.Steps to Take to Protect your Station ....................................................... Error! Bookmark not defined.
19. More about SDI-12 ...................................................................................................................................... 169
GOES/METEOSAT/INSAT/GMS Satellite transmitter including 11 physical input
channels (1xRS485, 2xSDI-12, 2xpulse/status, 2x5V analog, 3xDifferential
Analog, 1x 4-20mA), 4 isolated switched supplies, 1 isolated non-switched
supply, 2 switched open collector outputs, RS232, USB host, USB device, Wi-Fi,
power supply/ground connector, 9 2/3/4 pin connectors for sensors, 32 MB (1
million readings) measurement memory, 2 status LED, multifunction button
with LED, GPS receiver, 2 slots for expansion cards: optional Iridium modem,
optional LTE modem
1 quick start guide
1 factory acceptance test (FAT) certificate
1 USB cable
1 screwdriver
SL3-SDI-1
GOES/METEOSAT/INSAT/GMS Satellite transmitter including 2 physical input
channels (2xSDI-12) RS232, USB host, USB device, Wi-Fi, power supply/ground
connector, 32 MB (1 million readings) measurement memory, 2 status LED,
multifunction button, GPS receiver
1 quick start guide
1 factory acceptance test (FAT) certificate
1 USB cable
1 screwdriver
SL3-XMTR-1
GOES/METEOSAT/INSAT/GMS Satellite transmitter including RS232, USB host,
USB device, power supply/ground connector, 2 status LED, multifunction
button, GPS receiver
Protective earth ground. Connect to an earth ground electrode for lightening
protection of internal components.
Digital ground. Attach digital sensor ground to this terminal. Batteries and solar
panel negative terminals are also connected to this terminal.
Signal ground. Attach analog sensor ground to this terminal.
Chassis ground.
Shock hazard.
Do not dispose in trash.
2. General Safety Information
Read this manual before using Satlink for the first time. Become familiar with the
installation and operation of Satlink and its accessories.
Make sure that Satlink is protected against moisture (NEMA 4, IP 66 or better).
Operate Satlink only with approved antenna connected.
Protect the line of the battery supply voltage with a safety fuse (10A/fast).
Before connecting the power supply, check that all wires are properly attached to the
screw terminal strips.
Do not open Satlink. There are no user serviceable parts inside.
Have a defective Satlink checked and repaired by the Sutron repair center. Do not
attempt to repair Satlink yourself.
Operate Satlink only with approved antenna connected.
Sutron’s Satlink 3 is a datalogger with a built-in satellite transmitter that is especially designed for
hydrometry, meteorology and environmental monitoring. It is available in three models: SL3-1,
SL3-SDI-1, and SL3-XMTR-1.
Satlink 3 can:
Make measurements from sensors monitoring the environment
Perform special calculations
Record data into non-volatile memory
Transmit data to automated receiving systems.
Satlink 3 is certified to operate on the following satellites:
GOES Domestic 300, 1200 bps, timed and random reporting
GOES International
Meteosat, MSG (Meteosat Second Generation), Meteosat HDR, timed and alert
reporting
GMS 100 bps domestic and international channels
INSAT 4800 bps domestic channels
FY2B 100 bps domestic channels
Satlink 3 improves on its predecessor SatLink2. Satlink 3 does everything that Satlink 2 did with
the following and other enhancements:
Expanded measurements from 16 to 32
Improved analog accuracy & additional channels
The figure below shows the connections provided by the SL3-SDI-1. A description of each of the
connections is provided in the following paragraphs.
3.3. SL3-XMTR-1
SL3-XMTR-1 is similar to the SL3-SDI-1 with the following changes:
The 2 SDI-12 ports are replaced with an auxiliary DB9 connector. This connector is for
factory use only.
There is no Wi-Fi module in the SL3-XMTR-1. The button will not turn on Wi-Fi but is
only for failsafe reset.
SL3-XMTR-1 is designed to connect to another logger via the RS232 port. The logger will
setup the SL3-XMTR-1 and regularly transfer data to it for transmission. The logger may
use Sutron’s Satlink Communicator Protocol (SCP) or command line protocol for setup
and data transfer functions.
Contact Sutron customer service for additional information.
3.4. Multi-function Button
Satlink3 has a multi-function button installed on the front.
Briefly pressing this button will turn on the Wi-Fi.
Additionally, if the failsafe has been tripped, briefly pressing this button will reset the
failsafe.
The multi-function button is also used to reboot Satlink. If the button is held down for 5
seconds, the red LED will come on. Keep holding the button until the red LED turns off
in order to reboot Satlink.
The status LEDs give information on how Satlink is operating. The LED are multi-colored. The
following table describes the different colors and states of the LED.
3.6. RS232
The RS232 connection is a standard DB9-F connection for serial communications to a PC or other
device. The RS232 port has a default baud rate of 9,600 (No parity, 8 data bits, 1 stop bit, HW
flow control) but other baud rates are supported. The primary use of the RS232 port is for
connecting to a PC for setup, maintenance, and troubleshooting. The PC will typically run
LinkComm software which will allow the user complete control over Satlink subject to the
password protection in Satlink.
The RS232 port also allows the connection of Sutron’s 8310, 9210 and Xpert loggers to Satlink.
With this connection, the Sutron logger can use Satlink as transmitter to send data that it
collects, rather than have Satlink collect the data. This is normally done where the field station is
very complex and the user desires the advanced capabilities of 8310, 9310, Xpert for the
collection and processing of the data.
3.7. USB Micro (OTG)
The USB OTG port is the primary port for connecting a PC to Satlink. The USB port is a micro-B
and compatible with a standard micro-B to Type A male USB cable that works with most PC’s.
The primary use of the connection is to allow the PC to setup, maintain and troubleshoot Satlink.
The PC will typically run LinkComm software which will allow the user complete control over
Satlink subject to the password protection in Satlink.
3.8. USB Host
The USB Host connection provides a simple way to download data from a SL3-1 or update the
firmware in the unit using a USB flash drive (aka USB thumb drive). Plugging in a flash drive will
automatically download all logged data since the last download and store the log on the flash
drive. It will also store station setup and status on the flash drive.
It is possible to change station setup, upgrade Satlink firmware, and execute a batch file via a
flash drive. Please see section USB Thumb Drive for details.
3.9. RF Output
Satlink has a type N connector on the bottom of the Satlink and side of the SL3-SDI. See
Connecting the GOES/METEOSAT/INSAT antenna for details on how to connect an antenna to
Satlink. Never operate Satlink without connecting either an antenna or dummy load to this
connection.
Switched Main Power (9-20VDC) (turned on during
warm-up and analog sensor measurement)
7
Ground
Ground
8
WS/DIG IN 1
Wind Speed or Digital Input 1
9
Ground
Ground for sensor
10
TB/DIG IN 2
Tipping Bucket or Digital Input 2
11
Ground
Ground
12
+SW POWER 2
Switched Main Power (9-20VDC) (turned on via
equations and commands)
13
Ground
Ground
14
SDI-12 PWR
Isolated Main Power (9-20VDC) to SDI-12 sensors
(500 ma max)
15
SDI-12 DATA
SDI-12 Data (Port 1)
16
Ground
Ground
17
SDI-12 PWR
Isolated Main Power (9-20VDC) to SDI-12 sensors
(500 ma max)
18
SDI-12 DATA
SDI-12 Data (Port 2)
3.10. SL3-1 Left Terminal strip
Two terminal strips built into SL3 provide the connections for sensors, and outputs. The table
below describes the purpose of each connection on the left terminal strip. Additional information
on using the connections is given in Chapter 4.
Differential voltage input for bridge type sensors
32
Diff C-
Differential voltage input for bridge type sensors
31
Analog Ground
Analog ground
30
VREF
2.5V output (turned on during warm-up and analog
sensor measurement)
29
Diff D+
Differential voltage input for bridge type sensors
28
Diff D-
Differential voltage input for bridge type sensors
27
Analog Ground
Analog ground
26
VREF
2.5V output (turned on during warm-up and analog
sensor measurement)
25
Diff E+
Differential voltage input for bridge type sensors
24
Diff E-
Differential voltage input for bridge type sensors
23
4-20 mA
Input for 4-20ma sensor
22
GND
21
PROT +12V
Isolated main power (9-20VDC), 1amp max
20
DOUT #1
Digital Output (open collector, turned on manually,
with alarms, or via equations)
19
DOUT #2
Digital Output (open collector, turned on manually,
with alarms, or via equations)
Earth Ground
Attach via a heavy gauge (4 to 10 AWG) wire to
earth ground rod driven 6 feet into earth.
3.11. SL3-1 Right Terminal Strip
Two terminal strips built into Satlink provide the connections for sensors, and outputs. The table
below describes the purpose of each connection on the left terminal strip.. Additional
information on using the connections is given in Chapter 4.
Requirements of the intended installation site are:
Sufficient protection from moisture for an IP 63 device.
Proper space for the electrical cables
Temperature range -40C to +70C.
Space for installation using the mounting ears
Earth ground point for the connection of the SL3 earth ground.
Closed control cabinet or fire protection cabinet if the power supply is not a low power
source 12-20VDC.
The dimensions for SL3-1 are shown in figure below along with the locations of the mounting
ears.
Requirements of the intended installation site are:
Sufficient protection from moisture for an IP 51 device.
Proper space for the electrical cables
Temperature range -40C to +70C.
Suitable mounting plate or DIN rail clip with Standard top hat rail (TS35) mounted at the
installation site.
Earth ground point for the connection of the SL3 earth ground.
Closed control cabinet or fire protection cabinet if the power supply is not a low power
source 12-20VDC.
The dimensions for SL3-SDI-1 & SL3-XMTR-1 are shown in the figure below.
A connection point has been provided for an Earth ground on SL3-1. On SL3-SDI-1 the chassis is
the earth ground point. Always connect the earth ground to a suitable ground at the site as
described below.
Any time a sensor cable is attached to the terminal strip, the unit may be exposed to electrical
surges such as those that come from nearby lightning strikes. The SL3 includes spark gaps and
other protection devices that shunt the energy to the earth ground. If there is no connection to
the earth ground point on SL3, the energy has nowhere to go and the unit can be damaged.
Failure to properly connect the Earth ground point will lead to failures in the field due to
surges.
To install a proper ground connection point:
Use a copper ground rod driven into the ground at least 6 feet.
Attach a very heavy gauge (#4 Solid Copper) wire between the rod and the Satlink Earth
ground point. The connection point can accept up to a 4 gauge solid copper wire. If a
heavier gauge copper wire is used to connect to the ground rod, a reducer may be
necessary to connect to the terminal on Satlink.
Firmly secure the screw on the ground point firmly on the copper wire. Do not rely on AC
power ground connections as they are not always properly grounded and may introduce other
surges.
Satlink features gas tube protection on all sensor inputs.
4.4. Connecting the GOES/METEOSAT/INSAT antenna
The transmitter must be connected to an approved antenna to operate with the selected
satellite system. Sutron offers a variety of antennae including YAGI and dome types that provide
between 3 and 11 dB gain. Satlink will adjust its transmission power based on the type of
antenna connected. As a part of the setup process, the type of the antenna will be entered into
the setup.
The typical antenna cable is 10 to 20 feet long. Outdoor antenna connections should we
wrapped with a self-vulcanizing tape to make sure they are water/weather resistant.
Users are encouraged to use a separate lightning arrestor for the antenna such as the one shown
below.
The GPS antenna connection is at the top of the SL3-1. On SL3-SDI-1, the SMA connector is to
the right of the power connection. Sutron provides a GPS antenna with each Satlink. Satlink has
special circuitry to detect whether the GPS antenna is connected.
Take care to setup the GPS antenna such that it has a clear view of the sky. A site with a strong
GPS signal will reduce overall power consumption of the station.
The GPS antenna is normally mounted outdoors. Occasionally, you may mount the GPS antenna
indoors if the GPS signal penetrates the structure or enclosure where it is located.
The GPS antenna should be installed in a way to reduce the buildup of snow that might affect its
operation.
Only approved GPS antennae should be connected to Satlink.
Satlink requires a well positioned GPS antenna in order to operate correctly.
4.6. Connecting the Power Supply
The Power/Battery connection for the SL3-1 is at the top left of the unit. A two position
removable plug is provided for the connection. SL3 operates off 9-20VDC and can use up to 4
amps. Because of the high amperage requirements, an AWG 18 wire should be used.
Note: Even though SL3 will operate below 12V some sensors will not operate when the power
supply is below 12V.
A standard 12VDC lead-acid or Gel battery is typically used as the power source for SL3. Do not
power SL3 off AC power supplies without additional precautions to ensure the power supply is
properly rated and the system is enclosed in a fire protection cabinet.
It is a good practice to make all sensor connections with the unit powered off.
As soon as power is applied, the LED will flash as the unit goes through a self-test sequence. Then
the LED will flash depending on the setup of SL3. The LED will flash green when everything is OK.
Red means an error. Normally the button will flash blue every 4 seconds indicating that Wi-Fi is
turned on and ready for a connection. Other combinations are possible if the unit has been
previously setup. See section 3.5
Please note that it is normal for SL3 to flash red when power is first applied. Once SL3 has
verified good GPS signal (and optionally good Iridium signal), it will switch to flashing green. Do
not walk away from the site until Satlink is flashing green! Connect with LinkComm to see why
Satlink is flashing red.
4.7. Connecting SDI-12 sensors
SL3 supports two independent SDI-12 sensor busses. Each is provided with its own isolated
power connection rated for 500mA. Because SDI-12 sensors are addressable, multiple SDI-12
sensors may be connected to these terminals as long as no two sensors on the same bus have
the same address.
When multiple new SDI sensors are connected to a bus, they should be connected one at a time
so the address can be made unique using the SDI A command. For details, please see the section
titled Setup of SDI sensors.
The figure below shows the typical SDI-12 sensor connections.
SL3 supports RS485 sensors that use the SDI-12 protocol for its messaging. SL3 will not be able to
read data from RS485 sensors that do not support SDI-12.
The typical connection of the RS485 sensor is shown below:
4.9. Connecting Tipping Bucket Rain Gauge
SL3-1 supports a tipping bucket rain gauge using its TB/DIN2 connection. This connection
provides a pullup resistor (100K) to 3.3V to provide power for the contact switch in the rain
gauge. Each time the bucket in the rain gauge “tips” the internal switch closes momentarily
causing a pulse on the TB/DIN2 connection. This pulse is counted and used to provide
accumulated precipitation or precipitation rate data.
The key settings for a tipping bucker rain gauge are:
Measurement Type: Precip Accumulation or Precip Rate
Slope: 0.1mm, 0.2mm, 0.01inches or other value to match the calibration of the sensor.
Note: Measurement type: digital/counter1 or counter2 can also be used for tipping bucket rain
gauges. Be sure to select “debounce” for this measurement type as most tipping bucket rain
gauge switches are noisy and can produce multiple counts per tip if they are not de-bounced.
The typical connection of the tipping bucket rain gauge is shown below.
SL3-1 supports up to two sensors with pulse output. The pulse output can come from a switch
that is momentarily closed (as in most flow meters and tipping buckets) or it can come from a
device that actively puts out pulses to represent the value to be measured. Pulses are measured
by the Digital inputs DIN #1 or DIN #2. SL3 can count at a rate up to 10,000 counts per second
(de-bounce off). If the signal provided by the device is not clean, de-bouncing should be enabled.
Otherwise, Satlink may count noise as signal. To ensure that the de-bouncing does not interfere
with the pulse counting, de-bouncing should only be enabled for signals occurring less than 100
times per second.
The key settings for pulse sensors are:
Measurement Type: Digital
Digital type: Counter 1 or Counter 2
Debounce: yes/no
4.11. Connecting Frequency Sensors
SL3-1 supports up to two sensors with frequency output. The pulse output can come from a
switch that is momentarily closed as in most flow meters and tipping buckets or it can come from
a device that actively puts out pulses to represent the value to be measured such as a soil
moisture probe with frequency output or an anemometer..
The pulse output sensors connect to the DIN #1 or DIN #2 inputs. DIN #1 supports sensors with a
low level AC output (100 mVp-p) or high level output while DIN#2 supports only sensors with a
high level output (switch closure, 0-3VDC, or 0-5VDC).
The frequency measurement circuitry can measure frequencies from 3Hz to 10KHz with an
accuracy of 0.01%. The system takes 0.75 seconds to make the measurement.
The key settings for frequency sensors are:
Measurement Type: Digital
Digital type: Frequency 1 or Frequency 2
Note: Use Frequency 1 for sensors with a low level AC output voltage (such as an
RMYoung) and specify (AC Low Level). Frequency 2 is always expecting a DC high level
signal.
4.12. Connecting 0-5V Analog Sensors
SL3-1 supports up to two sensors with an output voltage up to 5 VDC. The sensor must be
connected to the signal ground and may be powered from VREF, PROT+12V, SWD+12V. These
inputs are compatible with sensors thermistors, potentiometers, strain gauges, etc.
The key settings for 0-5V analog sensors are:
Measurement Type: Analog
Analog Type: 0-5V A or B.
4.13. Connecting 4-20ma Analog Sensors
SL3-1 supports up to three sensors with a 4-20mA output. One sensor can connect directly to
the 4-20mA input (terminal 23) as shown below. The other sensors can connect to A or B (0-5V)
analog channels with an external load resistor. The sensor/loop must be powered from
PROT+12V, SWD+12V, main power, or other source with common ground to SL3.
The key settings for 4-20mA sensors connected to the 4-20mA input are:
Measurement Type: Analog
Analog Type: 4-20mA
The built-in 4-20mA connection has an internal 200 ohm load consisting of transient protection
and a precision 100 ohm sense resistor. External load resistors should also be 100 ohm in order
for the system to operate down to voltages between 10-12VDC. In some cases, the 4-20mA
sensor may need supply voltages > 12VDC to operate. The supply voltage needs to be greater
than the minimum voltage the sensor requires plus the maximum voltage across the load
resistance (2V for 100 ohms).
The key settings for 4-20mA sensor connected to A and B are:
Measurement Type: Analog
Analog Type: 0-5V A or B.
Add a 100 ohm load resistor between A or B and Signal ground.
4.14. Connecting Status Sensors
A status output is a switch that is open or closed. SL3-1 supports up to two status outputs using
either of the digital inputs (DIN#1 or DIN#2). An internal pullup resistor on DIN#1 or DIN#2
provides the excitation voltage for the switch.
SL3 will return a 0 when the switch is open and a 1 when the switch is closed.
The key settings for pulse sensors are:
Measurement Type: Digital
Digital type: Level 1 or Level 2
Steinhart((10000)*X/(vref-X), A, B, C) (see table below for A, B, C)
Note: The 10000 is the reference resistor value in ohms.
Slope: 1.8; Offset: 32 to convert to Fahrenheit.
Campbell Scientific’s CS205 & CS107 temperature probe requires different wiring than the
above since it has a reference resistor built into the probe. The wires are connected as indicated
below on the left and the equation will use the built in template for CS205/107. The image on
the right indicates the probe’s internal wiring for reference.
Jumper C+ to Vref
Purple (AG) ----------------- C+
Red (HI) ---------------------- C-
Black (EX) -------------------- AGND
Clear (G) --------------------- Earth Ground
4.18. Connecting Thermocouples
Thermocouples connect to SL3 to the C, D or E channels as shown below.
Measurement Type: Analog
Analog type: Diff C, D or E.
Input Range: 39mV with Bias
Equation: 24716*X+Terminal_temp {K type thermocouple, -8C to 64C}
For more accurate results, here are some other K-Type Equations:
Linear delta T range of ± 20°C. Approximation error is ±0.20°C.
Strain gauges connect to SL3 to the C, D or E channels as shown below.
The key settings for strain gauge sensors are:
Measurement Type: Analog
Analog type: Diff C, D or E
Input Range: 39mV or 312mV (**no bias needed)
Slope: as needed to scale the reading.
4.20. Programmable Excitation References
The built-in excitation reference voltage in SL3-1 is 2.5 volts available on pins 26 and 30. SL3-1
also supports a programmable excitation reference voltage via an optional plug in card. This may
be used in addition to or instead of the 2.5VREF when you need a different excitation voltage for
a sensor.
The optional card (Sutron part 6461-1328) can be plugged into either Option port 1 or 2.
The outputs have a range of 0 to 5VDC. The desired output is set via the menu on the options
tab:
Where G1/G2 are grounds and E1/E2 are the PREF1 and PREF2 voltages.
4.21. Connecting Prop/Vane or Anemometer/Vane Wind
Sensors
The prop/vane or anemometer/vane wind sensors like the RMYoung wind sensor typically have a
potentiometer for direction and frequency output for speed. The RMYoung connects to SL3 as
shown below. WS/DIN#1 is used for the frequency as it can handle low level AC as well as high
level DC pulses for speed.
* A 1.0 MOhm resistor needs to be placed from VREF (or SIGNAL GROUND) to AZ SIG. This
ensures that the value always goes to 355 (or 0 with SIGNAL GROUND) when the potentiometer
is in the open region.
Setup two measurements for the RMYoung – one for the direction and one for the speed.
Setup for Direction Measurement
Measurement Type: Analog
Analog Type: 0-5A
Equation: X/VREF*355 {converts to degrees}
Setup for Speed Measurement
Measurement Type: Digital
Digital Type: Frequency 1 or Frequency 2 (amplified version only)
Wind Speed (avg) *units based on
settings in the WS200
1
Wind Speed (max)
2
Wind Direction (vector)
3
Wind Direction (act)
4
Compass Heading (act)
5
Wind Speed (act)
6
Wind Speed (min)
7
Wind Speed (vct)
8
Wind Quality
9
Wind Direction (min)
10
Wind Direction (max)
11
Wind Direction corr (act)
DC high or AC low: AC low level (for unamplified RMYOUNG)
Slope:
To setup for wind vector measurements, go to 9.3.6 Measure Type: Wind.
4.22. Connecting Lufft Wind Sensors
Lufft has a family of smart weather sensors capable of measuring a variety of parameters,
including wind speed, direction, air temperature, relative humidity, and air pressure. In addition,
it is possible to setup the Lufft sensor to automatically perform average and vector average
calculations on the wind speed and direction in which case you do not need to use the Wind
Measurement type in SL3.
The Lufft sensor connects to SL3 as an SDI sensor to either SDI#1, SDI#2 or RS485 (SL3-1). To set
the units use the SDI command aXUu for US units or aXUm for metric. To set the averaging wind
averaging interval to 5 minutes use the following SDI command: aXAw+5. See the Lufft Manual
Family of Smart Weather Sensors for details.
Use the C or C4 commands to read wind data from the Lufft sensor. The C commands are
needed as the Lufft sensor often has more than 9 parameters in its output. The response to the
C command may provide different data based on what model is connected. For example, the
WS200-UMB provides the following data in response to the C command:
Other Lufft sensors with temperature and other measurements provide the wind speed and
direction as parameters 3 (average speed), 4 (max speed) and 5 (vector direction) and 14 (vector
speed) with detailed wind information available using C4. Consult the Lufft manual for details.
4.23. Connecting Digital Outputs
SL3-1 provides two digital output lines: DOUT#1 and DOUT#2.
Turned on during each measurement of Analog/Digital/SDI sensor. Warmup can
increase the time
SWD#2
Turned on only from an equation OUTPUT function or Command line command
Please see section Digital Output DOUT for details.
4.24. Connecting Samplers Triggered by Stage
Many samplers can be triggered to collect a sample by SL3’s Digital outputs DOUT#1 or DOUT#2.
Simply connect DOUT#1 or 2 to the “trigger” line of the sampler along with ground and program
an equation to generate the pulse based on the desired criteria.
For example, to trigger a sample when the stage is > 12.50 feet do the following:
Setup a measurement for stage, type to match the sensor you are using
Setup a measurement to control the sampler, type: Meta.
Set the Index to point to the stage measurement
Set the equation to: OUTPUT(X>12.5,2,1,1000) for DOUT#2, PULSE, 1000 ms.
4.25. Connecting to the Switched Power
There are two switched power connections SWD#1 and SWD#2. Each will provide up to 1A of
the input power. The setup and software control when the switched power lines are turned on
and off.
4.26. Connecting Protected Power
The protected power is labeled PROT+12V. This power provides 1A of the main power. This can
be used for sensors or equipment that needs to remain powered at all times. It can be turned
on/off/pulsed via the equation OUTPUT function and via the POWER command.
4.27. Connecting External Modems
You can connect an external modem to SL3 and use it to communicate with SL3 remotely using
LinkComm or other communication programs. The modem must be Sutron’s 8080-0005-1B
modem with a special configuration saved in its profile. The modem will connect to the SL3
RS232 port via a male-male null modem cable.
Here are the details of how the modem must be configured to work with SL3.
The following table summarizes the AT commands that will be issued:
- &F - factory reset the modem
- &D0 - ignores DTR from SL3
- &S1 - modem asserts DSR when connection established
- &W - save the settings to non-volatile memory of the modem
Connect to the modem with Hyperterminal (or similar) using a PC. For the best performance,
connect at 115200,N,8,1. The modem remembers the baud rate at the time of the AT&W, so be
sure to communicate at the rate you intend to communicate with the SL3 at. 9600 baud is the
SL3's default rate, but smart modems can go quite a bit faster.
Here's how to configure a modem to be used with the SL3 (assuming it's at factory defaults):
1) enter AT and then press ENTER until the modem responds with 'OK'
2) paste the following command to the modem:
AT&F&D0&S1&K3S0=1S2=255
3) press ENTER and the modem should reply 'OK'
4) paste the following command to the modem:
ATE0Q1&W
5) press ENTER
After the modem has been dumbed down by these commands it will not even say 'OK' to an AT
command anymore. To see if it's still working you may try a command with a non-simple
response such as AT&V
To configure the SL3 to answer at 115200, connect to your SL3 with LinkComm and use the
Diagnostics, Terminal window. Press ENTER to get the ">" prompt and issue the following:
RS232 Baud Rate=115200
Then reboot the SL3 for the new baud rate to take effect by issuing the Reboot command or
power cycling the unit.
The modem will now automatically answer calls and provide remote communications to SL3.
See “Connecting via Analog Modem” for instructions on how to use LinkComm with the external
modem.
4.28. Connecting External Cell Modems
You can connect an external cell modem to SL3 and use it to communicate with SL3 remotely
using LinkComm or other communication programs. The following details show how to do this
using Sutron’s GPRS-1-O modem that is preconfigured to operate as a client serial bridge to
accept connections and pass data between Satlink and the remote caller. The modem will
connect to the SL3 RS232 port via a male-male null modem cable.
Follow these steps to configure the GPRS-1-O modem to operate in serial bridge mode.
1) Creating/selecting the script. Some readymade scripts are provided based on typical settings
and common APNs. Go ahead and use ATT_script.txt, T-Mobile_script.txt, or Rogers_script.txt if
you are using either of these providers. Otherwise, contact Sutron for help in creating the proper
files for the modem.
2) Load the script in to a thumb drive. The file must be copied in to the station folder, and must
be renamed with the station as part of the file name. For instance if the station was named S01
then the file must be renamed "S01_script.txt"
3) Attach the modem to the Rs232 port an SL3 and insert the thumb drive. Look for a
script_results.txt in the daily sub-folder and examine it for errors. Once the modem is working,
enable passwords to help secure the station.
The script is designed to be run on a factory fresh modem or one that's already running the
script. The script will switch the speed of the RS232 port to 115200 baud.
See “Connecting via TCP/IP” for instructions on how to use LinkComm with the external modem.
LinkComm is a software application designed setup and operate Satlink. LinkComm is used to:
Check Satlink status
Set up Satlink
Download and graph the log from Satlink
Upgrade Satlink firmware
Calibrate connected sensors
5.1. Installing the LinkComm mobile app
Mobile versions of LinkComm are available to run on Apple iPad and iPhone, and on Google
Android phones and tablets. They can be found on the Apple® App Store™, and Google® Play
Store™, respectively. These applications are installed just like any other app for the device that is
being used.
5.2. Installing the PC version of LinkComm
The PC version of LinkComm is available for download from
http://www.sutron.com/downloads.htm. The PC version is supported on Windows 7 and higher.
After downloading LinkComm, run the program and follow the instructions on the screen. For
Windows, extract all files to a folder on your computer. You may run LinkComm directly from this
folder by double-clicking “LinkComm.exe”, or, to install LinkComm so that it appears on the Start
menu, double-click “setup.exe” (Administrator privileges are required to install LinkComm).
If your PC is running windows 7, you will need to install the USB drivers after installing
LinkComm. Note: this is not needed for Windows 8 and beyond.
5.3. Stations List View
When LinkComm starts, it displays the Stations List View, containing a list of stations that have
previously been setup in the software, along with the details of the selected station. The details
include the station name, type, connection settings, notes and images.
On small displays, the station list is hidden. Press < Stations to see the station list.
To work with the selected station, press “Connect”. The software will use the assigned
connection settings (USB, RS232, Modem, or Wi-Fi), to try to communicate with the site.
If you have problems connecting to the site, check your communication settings and or
cables/Wi-Fi settings and see the following sections that detail USB and Wi-Fi connections.
To create a new station, select “New Station” at the top of the station list (1). Then set the
Station Type (2) to match your type of Satlink, set “Connect type” (3) to Wi-Fi, USB, Serial or
Modem, and press Connect (4). Additional information on the Wi-Fi, USB and modem
connections are provided in the next sections.
You can set the software to get recent data (5). “Get recent data on connect”, when checked,
will cause LinkComm to download the last week of data for display in a graph on the dashboard
tab, every time you connect to Satlink. This can be a considerable amount of data (several kbytes). You may choose to disable this feature to reduce data costs (e.g., when communicating
over cellular links).
The “Check setup on connect” option (visible only for low bandwidth connections like
“Redirector”), will cause LinkComm to retrieve the setup from Satlink every time you connect.
You may choose to disable this feature to reduce data costs (e.g., when communicating over
cellular links).
5.3.1. Connecting via USB
LinkComm can connect directly to Satlink via a USB cable. Simply connect a USB cable from your
computer to Satlink and select “USB” as the Connect type.
LinkComm can also talk to a Stalink with the with the optional cell modem installed. To do so,
the Listening setting needs to be enabled.
Alternatively, to reduce power consumption, the system can be configured to check for messages
periodically. A message can be sent to the station asking it to temporarily turn on listening.
Please see the Telemetry section.
5.3.2.1. TCP/IP
If the IP address of a Satlink is known, it can be connected to directly. It is up to cell service
provider to
Give a static IP address. This means that the IP address of Satlink does not change over
time. Alternatively, you may send an SMS to the Satlink asking what its current IP
address is.
Provide VPN access. It is not always possible to directly connect to Satlink over the
internet because it is protected by the cell service provider’s firewall. In this case, it is
necessary to first connect to a VPN provided by the cell service provider.
5.3.2.2. The Redirector
Sutron provides a “redirector” service that can be used to access a Satlink station that uses a SIM
card provided by Sutron. The IP addresses of these SIM cards are behind a firewall, and so need
special steps to be taken for access.
When obtaining one of these SIM cards from Sutron, you will also receive a user name,
password, and station name to use when setting up your station connection in LinkComm. After
entering your user name and password, you may press the “Update Station Names” button to
retrieve the list of stations that are associated with your redirector account.
5.3.3. Connecting via Wi-Fi
Satlink can provide a Wi-Fi hotspot that LinkComm can connect to. The Wi-Fi feature is useful for
connecting to Satlink on-site with a mobile phone, tablet, or laptop.
Satlink’s Wi-Fi hotspot is not connected to the internet.
To connect to Satlink via Wi-Fi, follow this sequence:
Have Satlink turn on the Wi-Fi by pushing the wakeup button located on the front.
Satlink will blink the blue halo LED to acknowledge the button press.
Have your computer (Laptop, iPhone, or Android) connect to Satlink’s Wi-Fi hotspot.
Satlink will name its hotspot SL3_xxxx_aaaa, where xxxx is the station name and aaaa is
a unique number.
Create a new station in LinkComm with “Connect type” set to “Station Wi-Fi”
(LinkComm may detect you are connected to Satlink via Wi-Fi, and set this type by
default)
If you need to manually enter the IP address for Satlink, it is 192.168.88.1:3001.
LinkComm is now connected to Satlink. It is possible to check status, change setup,
download log, and perform almost all other operations.
Once the LinkComm session is complete, make sure to disconnect from Satlink's Wi-Fi
hotspot.
In order for LinkComm to connect to Satlink via Wi-Fi, the device that is
running LinkComm must first connect to the Wi-Fi hotspot provided by Satlink.
Here’s an example mobile Wi-Fi Settings screen showing several Satlink devices available for
connection:
5.3.4. Connecting via Analog Modem
LinkComm can connect to a Satlink with Display and Modem or a Satlink with an external modem
via a telephone modem. Connect the modem to your computer, select the “Modem” Connect
Type, and enter COM port. Press the “…” button to enter phone number and other modem
details. Note, LinkComm expects the modem to support ASCII result codes (“OK”, “CONNECT”,
etc.), and DTR call control.
5.3.5. Connecting via TCP/IP
LinkComm can connect to Satlink with an external Cell modem via TCP/IP. See “Connecting
External Cell Modems” for instructions on connecting the modem to SL3. LinkComm will need to
be run on a device that has access to the same network that the modem is operating on. If the
modem is on a private network, the PC will need VPN access to that network.
Select Connect type: TCP/IP
Enter URL or IP address for the station
Make sure that the IP port matches the port you have enabled in the modem (usually
To “work offline” means to make changes to the setup in LinkComm setup while disconnected
from Satlink. You enter this mode by selecting “Work Offline” in the station view. The changes
you make to the setup are automatically saved in LinkComm but not in the Satlink.
When you later connect to Satlink, you need to send the setup to Satlink to bring the setups “in-
sync”. If you checked “Get setup on connect” in the station’s Connection Settings, then when you
first connect, LinkComm will prompt to overwrite your changes. If you answer “No”, LinkComm
will then prompt to send your changes to Satlink. Answer “Yes” at this point to bring the setups
“in-sync”.
5.3.7. Notes
This section is used to enter notes in this section related to station setup and maintenance. For
example, you might store information about the last time the station was visited, plans for future
visits, and notes on calibrations, etc.
Note: All settings (station and connect settings, notes, and site images) for
every station you define are saved automatically as you make changes. Hence,
there is no need to select any kind of “Save” menu item.
5.3.8. Site Images
This section allows you store pictures of the site. Click “Add New Image” to browse for images to
store. If a camera is available, you’ll have the option to take pictures to store as new site images.
When you click a site image, it expands to fill the available window.
To delete a site image, right-click (or press-and-hold) the image and select “Delete Site Image” in
the subsequent prompt.
5.4. Main Menu
Press the button in the upper left to access the main menu. The menu shows different
options, depending on whether you are connected to – or working offline with – a station.
Import a stations database previously saved using “Export
Database…” Note that this will overwrite all existing station
definitions with those from the imported database. The action
cannot be undone., You may want to export the current database,
just in case you need to restore it
Export Database…
Export all station definitions to a database file. You can then use
“Import Database…” on another PC or mobile device to import the
station definitions.
About…
Display a dialog showing information about LinkComm, including
version
Sutron Website…
Visit the Sutron website
Event Log…
Show LinkComm event log. This is a text file showing diagnostic
information about LinkComm operation.
Exit
Exit and close the LinkComm application. This item is not displayed
when running on mobile platforms
The following menu is displayed in the Stations List View:
LinkComm prompts for password and then attempts to log in to
Satlink
Change Password…
LinkComm prompts for new password to use to log in to Satlink
Show Quick Status…
Show the Quick Status dialog, showing a summary of Satlink status
Import Setup…
Load a setup from an external file. The setup file was typically saved
by a prior “Export Setup…” action
Export Setup…
Save the current setup to an external file. The setup file is a text file
containing property-value assignments
Send Setup to Station
Send the current setup to Satlink (shown only if connected)
Get Setup from Station
Get the setup from Satlink (shown only if connected)
Stop Recording
Start (or Stop, if applicable), recording (shown only if connected)
The following menu items are displayed in Station Detail View (i.e., when connected or working
offline):
5.5. Station View
After you press either “Connect” or “Work Offline” in the stations list view, LinkComm transitions
to the “Station View”, where you see several tabs, e.g., Dashboard, Measurements, Data, etc.,
each showing information about status and/or setup for the selected Satlink.
The following picture is of the station view with the Dashboard tab selected:
Pressing the button in this state will cause LinkComm
to disconnect from Satlink
LinkComm is not
connected to Satlink
Pressing the button in this state will cause LinkComm
to try to connect to Satlink
5.5.1. Connect Button
The right header button is the “Connect Button”. It shows the status of the current connection
from LinkComm to Satlink. The button has two possible states:
5.5.2. Setup Status Button
The left header button is the “setup status button”. This button shows status related to the
setup, including whether the setup is “in-sync”, i.e., the same in both LinkComm and Satlink, and
recording status.
Pressing the setup status button typically prompts the user to take the next logical step towards
getting the setup in-sync between LinkComm and Satlink, with recording on.
LinkComm is connected
to Satlink, recording is
ON, and the setups are
“in-sync”
Press the button to turn off recording. LinkComm
will prompt for confirmation.
A change has been made
to the setup in LinkComm
(it no longer matches the
setup in Satlink)
Press the button to send setup changes to Satlink.
LinkComm will prompt for confirmation. If “Yes”,
only the changes required to be “in-sync” are sent. If
“No”, LinkComm prompts to retrieve the setup from
Satlink, overwriting local changes
The setup in Satlink is
unknown, and so may
differ from the one
displayed by LinkComm
Press the button to send the setup to Satlink.
LinkComm will prompt for confirmation. If “Yes”,
LinkComm first sets the setup in Satlink to defaults,
and then sends the changes required to be in-sync
Recording is OFF in
Satlink. This means no
measurements are being
made
Press the button to turn recording ON in Satlink.
LinkComm will prompt for confirmation
LinkComm is working off
line (not connected to
Satlink)
Press the button to connect to Satlink
Note: When the setup displayed by LinkComm is the same as the setup in
Satlink, then we say the setups are “in-sync”. When the setups are not the
same, the setup status button displays a warning sign, and you must send the
setup to Satlink to get the setups “in-sync”.
After making changes to the setup locally, you need to send those changes to Satlink to bring the
setups “in-sync”. You do this by pressing the setup status button (or by selecting the main menu
item, “Send Setup to Satlink”).
The following table describes the different states maintained by the setup status button, and
describes what happens when you press the button in each of the states:
The setup that is shown in LinkComm is not necessarily the same setup that is
in a connected Satlink
To read a setup from a Satlink and show it in LinkComm, you may either use the setup
status button as described in the previous section, or select the Get Setup From Satlink
To give a setup created by LinkComm to Satlink, you may either use the setup status
button as described in the previous section, or select the Send Setup To Satlink item
from the main menu
Unless the setup status button menu item is selected, or the Send Setup to
Satlink button is clicked, none of the changes made to the setup in LinkComm
will be in Satlink!
5.5.3. Handling Setup Differences Following Setup Send
On some occasions, LinkComm will detect that differences remain after sending setup changes to
Satlink. This can happen because of a communication error, but more commonly, it occurs
because Satlink doesn’t allow certain changes to occur remotely.
In any case, when LinkComm detects such a difference exists, LinkComm warns you that changes
still exist, and will offer a dialog to “View Differences”. To rectify the situation, it is usually best to
get the setup from Satlink to again be “in-sync”, and then try making and sending your changes
again.
5.5.4. Setup Files
You can save a Satlink setup to a file and later re-use that setup by loading it into LinkComm. To
save a Satlink setup to a file, select Export setup… from the main menu.
You may find it helpful to save reference copies of setups outside of LinkComm, as a backup in
case you accidentally overwrite changes to the setup in LinkComm. Use the export setup menu
item to achieve this.
To load a Satlink setup from a file, select Import setup… from the main menu. After loading the
setup file, you still need to send the changes to Satlink. As always, use either the setup status
button, or the Send Setup to Satlink menu item, to send the setup to Satlink.
5.5.5. Metadata - Pictures, Wiring Diagrams, and Special Text
LinkComm enables you to associate pictures, wiring diagrams, and special text items with your
Satlink station definitions. This “metadata” is NOT stored in the Satlink logger, since the logger
needs to use its storage space for more important things like sensor readings.
Some examples of metadata in LinkComm:
o Station picture, notes, and site images
o Measurement picture, model, manufacturer, description, units
This station metadata is not stored in the station setup files created by Export Setup…. The
metadata is saved, however, when saving the stations database using the Export Database…
menu item from the Station View main menu.
The Dashboard tab is the first tab displayed after you connect to Satlink. When LinkComm
connects to Satlink, it retrieves the current station status, and current data values for
measurements, and displays this data on the Dashboard.
The data displayed on the Dashboard always reflects the state of Satlink the
last time you refreshed status, regardless of the measurements you may or
may not have defined under Measurements.
To refresh the current status, click the Refresh Status button
To reset the station status, including the transmission counters, tallies and system
errors, click the Clear Status button. Once the status is reset, the previous status is lost
To show the status text actually received from the logger, press the Show Details button
To measure and update all sensors, press Measure All button
High level telemetry status is also shown on this page (below current sensor values). To
see low level details about telemetry, see the Telemetry tab.
If the station has any active errors, these are shown in RED just below the status area.
Right-clicking on any trend graph (or touching the graph in the mobile app), reveals a pop-up
menu that allows you to:
Refresh recent data (all items, not just the selected)
View the current data item in the larger graph on the Data tab
The station name can only be changed from the Dashboard tab, and is actually the only setup
item that can be changed from the Dashboard tab. To change the station name, press the blue
“edit” text, next to the station name.
LinkComm will prompt for the new station name. Just as with every other station setup change,
the change is not complete until you have sent the setup to Satlink. Do this using either the setup
status button in the main header, or the Send Setup to Satlink item in the main menu.
5.7. Measurements Tab
The measurements tab is the first tab displayed when you select Work Offline in the stations list
view. This is the tab where all sensors are configured. Up to 16 sensors may be enabled and
configured. The measurements tab also provides some test functions to help you ensure the
sensor is properly configured.
The left side of the measurements tab shows a list of all possible measurements. The right side of
the measurements tab shows the details of the selected measurement. The details are the
settings used to determine how the measurement is taken and how the data is processed by the
system. The settings include schedule, Configuration (including wiring diagram), Processing,
Alarms, Logging, Tx Content.
The data tab shows historical measurement readings made by Satlink. If recent data was
downloaded when connecting to Satlink, the graph displays this data the first time you select the
Data tab.
To zoom-in on subsets of data, click-and-drag to create a rectangle around the data you want to
zoom to. To restore the zoom to all data, double-click. When using a touchscreen, you may use
your finger to draw the rectangle, and double-tap to reset the zoom.
Right-clicking (or touching) the graph will show a menu allowing you to select all series, deselect
all series, or show points. You may select or deselect individual data series for display using the
legend just below the graph.
Change the span of the period to graph using the Span control. Several options are available.
Whenever a change to span is made, you must press the Download button to retrieve the data
for display. When the defined span no longer matches the displayed span, the download button
text changes to “Download***”.
Press Save File… to save the raw data to a text file. Press Save Image… to save an image of the
graph to disk. On mobile platforms, rather than save files to disk, you are prompted to “share”
the files via other services like Email, Dropbox (if installed), etc.
Change View to Table to see a table view of the data, rather than a graph.
Enabling Disable Graph causes the graph (or table) view to remain empty while data is being
downloaded. This can improve performance for very large downloads.
The Telemetry tab is used to configure a station for Environmental Satellite (GOES), Iridium or
Cellular communications. The contents of the tab differ for each telemetry type.
Telemetry tab showing Environmental Satellite shows the following:
The telemetry status section is below the setup area, and is accessed by scrolling down.
The status text is retrieved from Satlink the first time you display the telemetry tab, and can be
refreshed as needed on demand.
Please see the TELEM ETRY STATUS section for more info.
Iridium and Cell Telemetry types offer a Radio Diags button which provides diagnostics
information on the modems. Please see section DIAGNOSTICS TAB.
Information provided includes signal strength, time when the modem last connected to the
network, contents of the last received message, and IMEI.
Besides showing the diagnostic information, the Radio Diagnostics tab allows one to check for
Iridium messages immediately, and to send an SMS to a specific cell number.
5.10. GPS Tab
Every Satlink Logger transmitter has a built-in GPS module. The GPS module provides time and
frequency information needed for the on-going operation of SL3. SL3 is certified to operate for
30 days without GPS.
There is only one setting on the GPS tab: Local Time Offset (min). GPS provides UTC time to
Satlink. The field labeled “Local Time Offset” can be used to have Satlink use local time instead
of UTC. Enter the offset from UTC in minutes to have Satlink use local time. Leave the setting at
zero to have Satlink use UTC. E.g. to have Satlink run on US Eastern Standard Time, enter -300,
indicating that EST is 300 minutes behind UTC. Note: Satlink will not automatically switch
between daylight savings time and standard time. Note: if you set a local time offset, all times
used by Satlink will be in local time – even the scheduled transmit time. You may need to adjust
your scheduled transmission time to local time if you use a local time offset.
In order to give the user a better idea of the quality of the GPS signal, Satlink Logger provides
messages that indicate how long the GPS module was powered before a time sync was initiated.
If the last GPS sync was a part of a transmission, this number should roughly be equal to the GPS
acquire time. If the last sync was user initiated, then this number will indicate how long it took
the GPS module to acquire the signal necessary to provide an accurate time.
The Signal Quality reported by Satlink consists of a graph of the signal strength for each satellite
in view of the station. The satellite number is on the bottom of each bar and the signal strength
is the height of the bar. The signal strength is also color coded for easy recognition of how well
the satellites are being received. Note that it is natural for the signal strength to be below 40 as
satellites orbit out of view. The GPS needs at least 4 satellites to get valid time and frequency
information.
The only controls on the tab are to refresh the screen and start a new sync. Normally, Satlink will
attempt to get a time sync from GPS 10 minutes before a scheduled transmission. The sync will
happen at least once every 30 minutes. The synchronization process takes about a minute and
ensures that Satlink is ready to transmit on time. If the sync fails for any reason, the transmission
will still be able to operate for up to 30 days. In fact, just one sync in thirty days is all that Satlink
needs to operate indefinitely.
5.11. Other Setup Tab
Various settings are displayed in the Other Setup dialog, which is accessed from the Telemetry
tab by pressing the Other Setup button. The settings shown include those for:
See section OTHER SETUP for more information setting in this page.
Iridium and Cell Telemetry types offer Iridium Diags and Cell Diags buttons which provides
diagnostics information on the modems. Please see the RADIO DIA GS section for details.
5.12. Diagnostics Tab
This tab provides extensive diagnostics information, and offers tools for performing various
diagnostics and maintenance operations. For example:
Get diagnostics information including software versions and data usage
Terminal and Data Flow views
SDI-12 command utility
Set the clock in Satlink
Upgrade Satlink
Resetting Satlink to factory defaults
The top two text areas on the Diagnostics tab display information about the firmware installed in
the connected Satlink.
The Firmware Versions section displays the current versions of firmware installed in Satlink. If
LinkComm detects a newer version of firmware is available, this text area contains a message
saying such. The Firmware Diagnostics area displays recent diagnostics information reported by
Satlink.
Press the Refresh… button to update this data to the latest. Press the Save to file… button to
save all diagnostic text data to an external file.
5.12.2. LinkComm Versions and Diagnostics
The bottom two text areas on the Diagnostics tab display information about LinkComm.
The LinkComm Data Usage section displays the total byte counts between LinkComm and Satlink
for the current session. The LinkComm Diagnostics section displays LinkComm’s version
information.
Press the Refresh… button to update this data to the latest. Press the Save to file… button to
save all diagnostic text data to an external file.
5.12.3. Terminal
LinkComm features a built in terminal monitor program. All communications between LinkComm
and Satlink uses the command line interface. The Terminal window can be used to view a history
of command traffic, and can be used to access the command line interface directly.
To see the details of the communication between LinkComm and Satlink, bring up the terminal
window via the Terminal button on the Diagnostic tab.
You may type into the terminal window. Data typed will be sent to Satlink. Any replies from
Satlink will be shown in the Terminal window.
5.12.4. Data Flow
The Data Flow dialog shows recent command line traffic in Hexadecimal, and shows traffic
direction and timestamp information. To open the dialog, press the Data Flow button on the
Diagnostic tab.
When “Autoscroll on data” is checked, the window advances when new data becomes available.
5.12.5. Firmware Upgrade
The software running in Satlink can be upgraded. The latest version of Satlink firmware is
delivered as part of the LinkComm download package obtained from the Sutron web site.
LinkComm may be downloaded from http://www.sutron.com/downloads.htm (search on
“LinkComm”).
Upgrades may be done over RS232, USB, USB thumb drive or Wi-Fi.
Upgrade files are packaged into the same download with the LinkComm program. Upgrade files
will have names such as SL3EuropaActual_800r1695.sl3u
To initiate an upgrade of your Satlink, select the Upgrade button on the Diagnostics tab. If
LinkComm detects a newer version of firmware on your PC, LinkComm will suggest that an
upgrade be made using it. If you select “No”, then use the file-open dialog that follows to browse
for, and select, the upgrade file to use.
You can also upgrade the firmware via USB. See section 6.15.3 Update the Firmware via USB
Thumb Drive.
5.12.6. Setting to Factory Defaults
Setting the station to factory defaults will permanently erase all setup and status. The setup will
be set to defaults. To set Satlink to factory defaults, press the Factory Defaults button on the
Diagnostics tab and answer “Yes” to the prompt for confirmation.
5.12.7. Rebooting Satlink
Clicking the Reboot button on the Diagnostics tab will have LinkComm issue the reboot
command to Satlink. Satlink will perform a software reset. LinkComm will then disconnect from
Satlink.
If you are issuing the command remotely, please note that Satlink will need a minute to get back
on the internet before it is ready to talk again.
5.13. Password Menu
LinkComm provides Password related items in the menu that can be used to log in, change the
password, and log out. LinkComm will prompt for a password when it is needed.
For details on password operation, please see the Error! Reference source not found. section.
A green check signifies the item is in the expected state
A warning triangle signifies the item isn’t as expected, and may need attention
A red stop sign signifies the item is likely incorrect, and needs attention
5.14. Quick Status Dialog
When disconnecting from a Satlink3 station, LinkComm displays a Quick Status dialog, containing
a summary of important status information.
The dialog displays system time and battery voltage information at the top. The scrollable list of
status items in the center of the dialog display status for particular items, as follows:
o Errors
o Recording status
o Measurement status, including number of parameters to transmit
o Scheduled transmission status
o Random transmission status
You can prevent the dialog from being shown when disconnecting from SL3 by checking Do not
automatically show this dialog. To see the dialog when this is checked, select Show Quick Status
The following scenarios describe how to perform some common functions with a Satlink. They
assume that Satlink is powered up and that LinkComm is running and can connect to the station
via USB, RS232, or Wi-Fi. For help connecting to a station, refer to Connecting via USB or
Connecting via Wi-Fi.
6.1. Creating a New Station in LinkComm
Select “New Station” from the top of the station list.
Set station type to Satlink3, and set connect settings, as needed.
Press “Connect” (or “Work Offline”, if SL3 hardware isn’t connected).
On the Dashboard tab, edit the station name.
Use the Measurements and Telemetry tab to make other settings (consider using
Factory Defaults on Diagnostics tab to start from a blank slate).
Select “Save Station” from the main menu. The station will be added to the station list.
6.2. Connecting to an SL3 in Your Station List
Select the station in the station list.
Update the connection type and related settings, if needed.
Press “Connect”.
LinkComm will read the setup from the station and report any differences it finds. If no
message is displayed, the setups match.
If the setup differs, a message will be displayed. Press “View Diffs…” to see the
differences. Then press YES to send the LinkComm setup to SL3, or NO to have a chance
to use the setup received from SL3 as the correct setup.
6.3. Importing Setups From Another User Or Station
Create or connect to an SL3, following the steps in either 8.1 or 8.2, above.
Select “Import Setup …” from the main menu.
Locate the desired setup file and press Open
o Note, the setup file is a .txt file and it may have been created via Export Setup,
or Diagnostics.
If prompted that LinkComm will “replace the current setup…Continue with import?”,
select YES. The setup is now resident in LinkComm.
6.4. Testing Measurements
Go to the measurements tab.
Select a measurement
Scroll to the Processing Section
Press Refresh to view last measurement
Press Force to make a new measurement.
Go to the Dashboard
Press “Refresh Status” to see latest data from each measurement
Right click and select “Refresh recent data” to update graphs.
6.6. Examine Transmissions
Go to Dashboard
Select “Show Details”. Statistics on the Scheduled and Random Tx will be displayed
You may also see the telemetry statistics on the Telemetry tab, Telemetry Status
section.
6.7. Examine Transmission Data
Go to Telemetry
Select “Show Tx Data”. The data from the last transmission is displayed along with data
that would be transmitted if one were made now. Details on the size and time required
to transmit are also displayed.
6.8. Entering Manual Data
Go to Measurements
Select the desired measurement
Scroll to Processing, select “Calibrate”, and enter the desired value and press OK.
6.9. Calibrating Sensors
Go to Measurements
Select the desired measurement
Scroll to Processing, select “Calibrate”, enter the desired sensor reading and press OK.
Whenever a sensor reading is calibrated, the system will log two readings – the value
before and the value after the calibration.
6.10. Configuring SDI-12 Sensors
Go to Measurements
Select the desired measurement of an SDI-12 sensor
Scroll to Configuration and press “Send SDI-12 Command”. A menu will be provided
that allow you to select Port1/Port2, Address, and commands for SDI-12.
If the desired command is not in the Command drop-down list, simply enter it yourself
in the command box.
You may also access the SDI command menu from the Diagnostics tab.
6.11. Downloading Log Data
Go to Data
Select desired “Span” and press “Download”.
Press “Refresh Status” to update the status.
Press “Show Details” to see additional information.
Press “Clear Status” to clear any errors.
6.13. Software Version
You can find the version of the software on the diagnostics tab of LinkComm. The Serial Number
of the product is listed there as well.
You can also obtain the version of the software using the VER command via command line.
6.14. Setting Time
You do not need to set the time yourself in Satlink. Every Satlink Logger transmitter has a built-in
GPS module. The GPS module has the ability to get the time from the GPS satellites. The GPS
module needs to be connected to an antenna and that antenna needs to have a clear view of the
sky so the GPS can track the satellites. Satlink will frequently update its clock to the time
reported by the GPS module.
Should GPS fail for any reason, the Satlink will continue to operate the transmitter for up to 30
days. During this time, Satlink will be using its own accurate internal clock to maintain the
correct time. After 30 days without GPS, there is a chance that the internal clock has drifted too
far. At this point transmissions are suspended until GPS signal is found again. Please note that
even though transmissions are suspended, normal data collection and logging continues.
Satlink time can be viewed via LinkComm on the Dashboard tab. Note that the time shown in the
dashboard is a snapshot of the time. To see the current time, press refresh for an update. The
time displayed will be UTC or local time depending on the Local time offset setting. Note that
the time may be off by a second or two because of the time needed to retrieve the status from
Satlink.
You can get additional information on how well the GPS is performing via the GPS tab.
Use the Local Time Offset to convert the time from UTC to a local time zone. The change will
take effect after the next good transmission.
6.15. USB Thumb Drive (Flash Drive) Operation
Satlink provides several convenient functions via the USB Host port. A USB thumb drive (aka
Flash drive) is required to use the port. The drive must be pre-formatted with the FAT32
operating system.
6.15.1. Download data to USB Thumb Drive
To download data to a USB drive, simply insert a USB drive (already formatted FAT32) in to the
Satlink3. When you do, the green LED (red if an error condition is present) will start blinking
rapidly while processing the drive. SL3 will write the log data since the last download to a file
along with setup and diagnostics information. The thumb drive may be removed once the LEDs
resume normal blink pattern.
The following folder structure is used on the Thumb Drive (and will be created if not present):
\Sutron\Satlink\<station>\<date>
where <station> is the name of the station and <date> is the current date in yyyymmdd format
(ex: "20160204")
Output files are always placed under the full path and given a unique name by appending _01,
_02, _03, ..., _99 to the name as necessary.
The files include:
log data (ex: "TestStation_log_20161231_02.csv")
diagnostic data (ex: "TestStation_diag_20161231.txt")
setup files (ex: "TestStation_setup_20161231.txt")
results from setup import (ex: "TestStation_setup_results_20161231.txt")
output from script execution (ex: "TestStation_script_results_20161231.txt")
It is possible to change Satlink’s setup by plugging in a USB drive that contains the new setup.
LinkComm’s Setup files can be exported by LinkComm and then copied to a USB drive such that
they will automatically installed when the USB drive is plugged into the USB Host slot in SL3. The
setup is specific to the station. For every station you wish to setup, a different setup file must be
created and placed on the drive.
To update Satlink’s setup with a USB drive:
Use LinkComm to create a setup.
Use LinkComm’s export setup menu option to create a setup file.
The setup file must be named “StationName_setup.txt”, where “StationName” is the
current name of the station that will have its setup updated. If you do not know the
name of the station to update, you will not be able to update it with the USB thumb
drive.
Copy the setup file to a USB drive and place in in the \Sutron\Satlink\StationName
directory, where StationName is the current name of the station that will have its setup
updated.
Plug the USB drive into the Satlink.
After the setup has been processed it will be renamed to prevent it from being processed in the
future (ex: "TestStation_setup_installed.txt"). This means you cannot use the same setup file to
update multiple stations.
Example: to upload a new setup to the station named “TestStation”, place the setup file in the
following folder of the USB drive: \Sutron\Satlink\TestStation\TestStation_setup.txt. Then plug
the thumb drive into the SL3 USB Host connector.
6.15.3. Update the Firmware via USB Thumb Drive
The firmware is Satlink may be upgraded with a USB drive. To do so, place the upgrade files (eg:
SL3EuropaActual_800r1811.sl3u) in the Satlink folder of a USB drive. When the USB drive is
inserted into SL3 USB Host, SL3 will look for the upgrade file and check to see if the station is
running an older version of firmware. The version and revision numbers in the file name are used
to make this determination. If the revision on the USB drive is newer than what Satlink is
running, Satlink will be upgraded.
Example: to upgrade the firmware to 801r1900, place the upgrade file in the following folder of
the flash drive and insert the flash drive into the USB Host:
\Sutron\Satlink\SL3EuropaActual_801r1900.sl3u
Upgrade files are shipped with LinkComm and may be found in the same directory that
LinkComm is installed in.
Satlink provides means of protection against unwanted access. Password protection is at the
heart of the security.
Whether accessing Satlink with a USB cable, an RS232 cable, via the Wi-Fi hotspot, through a USB
thumb drive, over Iridium SBD messages, over cell TCP/IP, or over cell SMS messages, password
protection guards access to Satlink. In order to access Satlink, the correct password must be
provided.
For remote access over Cell, additional protection is provided over TCP/IP via the use a VPN. To
access Satlink, one first connect to the appropriate VPN.
For Iridium access, additional protection is provided by the Iridium system itself, which blocks
access from unauthorized sources. Anyone who seeks to send messages to Satlink must be on a
white list provided to Iridium.
Each SMS message sent to Satlink needs to include the password if Satlink is to process it. The
same holds true for Iridium SBD messages.
Satlink’s Wi-Fi hotspot provides an additional layer of security. It uses WPA2-AES protection,
meaning that a Wi-Fi password must be provided to connect to the hotspot. Additionally, the
Wi-Fi hotspot is generally off until the site is physically visited and the front panel button on
Satlink is pressed. Please note that Satlink’s Wi-Fi hotspot provides access only on site. It does
NOT make Satlink accessible over the internet.
7.1. Steps to Take to Protect your Station
Please take the following steps in order to ensure the integrity of your Satlink station.
Physical access to Satlink must be restricted.
Passwords should be setup and enabled. See section PASSWORD PROTE CTION for details.
Wi-Fi password protection should be enabled. Wi-Fi enable should be turned off to
prevent Wi-Fi from turning on automatically. Please see section WI-FI.
7.2. Password Protection
Password protection can be configured to prevent unauthorized access. To setup password
protection, please use LinkComm’s Change Password menu. Please see the Command Reference
section for command line access.
Read access is the lowest access level. A customer with read access may not make
any changes to the system. Read access allows one to view measurement readings,
view status, and view setup, and the like.
Maintenance access
Maintenance access provides everything that read access does, plus the ability to
calibrate sensors, clear status, reboot unit, and other station maintenance related
functions.
Full access
Full access provides complete access to the station.
Each tier has its own password. Access granted depends on the password entered.
The default passwords are SUTRON1 for read access, SUTRON2 for maintenance access, and
SUTRON3 for full access. Please change ALL THREE passwords when securing your system.
Blank passwords are NOT allowed. All ASCII bytes are allowed except comma, equals, and white
space. Passwords may be up to 19 bytes long.
7.2.2. Password Protection Setting
A setting called Password Protection needs to be set in order to secure a station. Password
Protection may be set to one of the following:
DISABLED
In this scenario, full access is allowed without a password. This is the default.
SETUP
In this scenario, the system’s setup is write-protected. Maintenance and read
access are allowed without a password.
Station setup cannot be changed. Transmissions may not be started.
Status may be cleared, measurements may be calibrated and forced, failsafe may
be reset, unit may be rebooted, clock may be set.
MAINTENANCE
System write and maintenance operations are restricted. Read access is allowed
without a password.
Setup can be read, but not written. Status can be checked, but not cleared.
FULL
System is fully protected.
No access at all is allowed without a password, except for the following commands:
If LinkComm is used to connect to a password protected station, LinkComm will automatically
prompt for a password.
When sending a message to a password protected station, the first line of the message must
have the login command LOGIN=XXX, where XXX is the password.
7.2.4. Logging Out
Logging out is accomplished by one of the following:
Disconnect with LinkComm
Type EXIT in the command line
Disconnect the USB cable
Power down the unit
Satlink operation is controlled by its setup. The user has the option of changing any part of the
setup. The setup is stored in non-volatile memory and will not be affected when the unit loses
power.
The LinkComm application is the easiest and fastest way to program your station..
Setup can be changed while Satlink is collecting data. However, if the station is in the middle of
making a measurement when the relevant setup is changed, unexpected effects may occur. Even
if unexpected effects occur, the next measurement will be made correctly.
Changes to setup will not affect previously logged data.
Every time setup is changed, it is noted in the log with the entry setup changed. Details of the
setup change are not logged.
If a password is enabled, changes to setup cannot be made until the password is entered.
The setup is broken into three sections discussed in detail in the next chapters:
measurement setup
telemetry setup
other setup
Remember that if you ever see at the top of LinkComm, the setup in LinkComm differs from the
setup in the SL3. If the change is deliberate, press the “changed” control to update the SL3
setup. If the change is accidental, use the Main Menu, Get setup from Satlink3 function.
You can also change the setup by sending messages to Satlink via one of the optional modems.
As an alternative to LinkComm, you can use any terminal program to access all of Satlink’s
features via the command line interface described in Chapter 15.
The measurements tab in LinkComm is where the measurement setups are managed.
A measurement is the process of collecting data from a sensor. SL3 provides the ability to
establish up to 32 measurements, each with its unique settings. Each measurement will occur
periodically and provide one sensor reading. How a measurement behaves is governed by its
setup. Each of the 32 measurements has its own setup. Changing the setup of one measurement
will not affect other measurements (except for Meta measurements).
Measurement results may be logged or just used for alarms or by other measurements. The log
can hold over 1,000,000 readings (may be expanded to 1,000,000,000 readings). Logged
measurement results may be transmitted via GOES or other telemetry installed.
The measurement setup is divided into the following sections described below.
9.1. Sensor Setup
9.1.1. Active
Making a measurement active is the first step in setup of a measurement. If a measurement is
not active, you can still enter a setup; however, the measurement will not be performed.
9.1.2. Sensor Template
LinkComm provides templates for many sensors often used with Satlink. The template configures
settings for the most important sensor parameters, and also includes sensor metadata, e.g., a
picture of the sensor, its wiring diagram, manufacturer, model, description, and units. Setting up
a sensor using the Sensor template is a great way to avoid setup mistakes.
Note: Sensor metadata (picture, wiring diagram, etc.), is NOT stored in the
Satlink logger, but only in the station definition in LinkComm.
The following is an example of a template for an air temperature/relative humidity
sensor.
To use the template:
Use the right and left arrows on the sides of the sensor picture to scroll between
the available sensor templates.
Use “Filter Options” to restrict the available sensor templates on the basis of
manufacturer or interface.
Once you are displaying the desired sensor template, select the related parameters
such as interface, parameter before pressing select.
9.1.3. Measure Type
This setting tells Satlink what kind of a measurement to make: SDI-12, analog, battery,
etc.
This setting partially determines what physical connection on Satlink the sensor needs
to be wired to.
Measure Type also controls the configuration that follows in the setup. For example,
when you select Analog, the configuration section will allow you to enter Analog Type
and other related settings.
For details on the different measure types, please see section 9.3.1.
9.1.4. Label
User set name given to measurement, up to 11 bytes. This is used to identify and differentiate
measurements. This value will be placed in the log each time a measurement is made, so that
changing a label will not affect previously logged data. Example labels: AT, Stage, Baro, Precip,
Batt.
Please use unique labels for each different measurement. Failure to do so will result in a hard to
understand log file. When downloading the log, Satlink identifies each logged value with the
label.
9.1.5. Model
Model is a text field available to enter the model name or number for a sensor. This is metadata
stored in LinkComm but not in SL3.
9.1.6. Manufacturer
Manufacturer is a text field available to enter manufacturer information for the sensor. This is
metadata stored in LinkComm but not in SL3.
9.1.7. Description
Description is a text field available to enter additional information for the sensor. This is
metadata stored in LinkComm but not in SL3.
9.1.8. Right Digits
The number of digits shown after the decimal place is referred to as the right digits. To make the
measurement read 10.12 rather than 10.12345, set the right digits to 2. Note that Satlink will
round to the requested number of digits before logging the data.
9.1.9. Units
Units can be specified for any measurement and will be stored with the data when it is logged.
Use the dropdown list to pick from the built-in list of units. You may also enter the units text
directly into the text box. The units text can only be 3 characters long.
You can select an Icon for the measurement. The icon will show on the dashboard and
measurement list. Press “Change” to choose an image in the computer or take a picture.
Remember the icon is small and cannot show detailed information.
9.1.11. Picture
A picture of the sensor is shown to the right of the sensor information. LinkComm includes
pictures for many common sensors and Measurement Types. Press “Change” to choose an
image in the computer or take a picture to use.
9.1.12. Defaults
Press the Defaults control to set all the settings for a specific measurement to default values.
Note the default measurement type is SDI-12. Setting defaults will also set the meta data
(picture, icon, description etc.) to default values.
9.2. Schedule
9.2.1. Measurement Interval
Measurement interval is simply the time between scheduled measurements. See Measurement
Time.
9.2.2. Measurement Time
Measurement interval and time dictate when the measurement will be made. The interval
controls how often the measurement is made, and the time controls when the measurement is
started.
Example 1 (The measurement is logged every 10 minutes at 0 seconds past the minute):
time 00:00:00 interval 00:10:00
o 00:10:00 data measured and logged
o 00:20:00 data measured and logged
o 00:30:00 data measured and logged
o and every 10 minutes afterwards…
Example 2 (The measurement is taken and logged every 5 minutes at 30 seconds past
the minute): time 00:00:30 interval 00:05:00
o 00:00:30 data measured and logged
o 00:05:30 data measured and logged
o 00:10:30 data measured and logged
9.2.3. Averaging Time, Sampling Interval, Subsamples, and Results
Satlink can collect multiple samples and average them in order to produce a single result.
Averaging is useful for measuring changing conditions, such as wind and water level. For
example, correctly measuring the level of choppy water requires that wave action be cancelled.
That can be accomplished by averaging over several minutes.
Setting the Averaging Time to 00:00:00 (zero) disables averaging -- one sample is to be
collected. This is the default setup. If Averaging Time is zero, Sampling Interval and Subsamples
will not be shown in the setup.
When averaging, Satlink takes several samples and averages them into a final result. Each sample
may also be composed of several subsamples.
Averaging Time determines how long to collect samples for.
Sampling Interval dictates how often to collect each sample.
Subsamples tell how many sensor readings to include in each sample. Do not use
Subsamples unless you need two levels of averaging.
Result lets you specify what statistical value to log: average, min, max, running average,
running min or running max.
The simplest averaging requires only the use of Averaging Time.
9.2.3.1. Example: Average Temperature Over an Hour
If you want to know the average temperature for an hour, you would set up the Averaging Time
to one hour. Sampling Interval or Subsamples would not need to be changed. Satlink will collect
sensor data all throughout the hour as fast as possible.
However, if the power consumption for measuring the sensor continuously for an hour were
unacceptable, you would use the Sampling Interval.
To take one sample every minute, the Sampling Interval should be set to one minute. That way,
Satlink will take 60 samples every hour, with approximately a one-minute break between each
sample.
If the sensor being used was noisy and needed filtering, Satlink could take several Subsamples
and average them into each sample.
In the setup for temperature above, if the number of Subsamples were set to five, Satlink would
take five readings at the start of every minute and average them. That result would be used as a
sample. Once an hour, 60 samples would be averaged into a final result.
Data collection starts at Measurement Time + Measurement Interval – Averaging Time + Sampling Interval, and the last sample is taken at Measurement Time + Measurement Interval.
In the example below, temperature is measured every 15 minutes and averaged for an hour:
Measurement Time 00:00:00
Measurement Interval 01:00:00
Averaging Time 01:00:00
Sampling Interval 900 (900 seconds is 15 minutes)
Data Collection
o 00:15:00 first sample collected
o 00:30:00 next sample collected
o 00:45:00 next sample collected
o 01:00:00 last sample collected
o 01:00:00 all four samples are averaged and the result is logged with the
01:00:00 timestamp
The Results field will be shown only if averaging is enabled. If it is enabled, you can select
average, minimum, maximum, running average, running minimum, running maximum to be
the logged result value. The difference between average and running average is as follows:
Average – Starts a new average each measurement interval. Computes average only at the end
of all the samples. Tracks min/max of each sample as it is measured.
Running Average – Running averages continue across measurement intervals. Satlink
recomputes the running average with each sample. It tracks min/max of the running average
(not individual samples) throughout the interval. As a result, the running minimum and running
maximum will be less extreme than the simple minimum and maximum .
If you want to transmit average, minimum, and maximum results, you need to set up three
identical measurements except for the Results field: one measurement would choose results
average, one minimum and one maximum. Note: even though you setup 3 separate
measurements, as long as the schedule is identical, the system will only be reading the sensor
once.
9.2.3.2. More on the Running Average
A Running Average is used when readings need to be averaged over a time period that is longer
than the logging interval.
For example, if you would like to produce an hourly average every 15 minutes, you would use a
Running Average. In that case, the Averaging Time should be 01:00:00 and the Measurement
Interval should be 00:15:00.
For Running Average, Averaging Time may be longer than Measurement Interval. In fact, unless it
is longer, there is no point in using a Running Average as the result will be the same as a Simple
Average.
The Measurement Interval and Measurement Time will determine how often a reading
is produced.
Averaging Time dictates the time span over which samples will be averaged.
Sampling Interval tells the system how often to sample the sensor.
If you are interested in logging a five minute average every minute, set Averaging Time to five
minutes, Measurement Time to one minute and Sampling Interval to 60 seconds. Here is the
timeline of the data produced:
12:01 Sample sensor (reading = 1.0). There are not enough samples to produce an
average. System will still compute and log a result producing a value of 1.0;
12:02 Sample sensor (reading = 2.0). There are not enough samples to produce an
average. System will still compute and log a result producing a value of 1.5;
12:03 Sample sensor (reading = 3.0). There are not enough samples to produce an
average. System will still compute and log a result producing a value of 2.0;
12:04 Sample sensor (reading = 4.0). There are not enough samples to produce an
average. System will still compute and log a result producing a value of 2.5;
12:05 Sample sensor (reading = 5.0). Compute and log 5 minute average. Result = 3.0,
computed as (1.0+2.0+3.0+4.0+5.0)/5;
12:06 Sample sensor (reading = 6.0). Compute and log 5 minute average. Result = 4.0,
computed as (2.0+3.0+4.0+5.0+6.0)/5;
12:07 Sample sensor (reading = 7.0). Compute and log 5 minute average. Result = 5.0,
computed as (3.0+4.0+5.0+6.0+7.0)/5;
Compare this to a simple average. A simple average over five minutes would produce a reading
every five minutes. It would be setup with Measurement Interval of five minutes, an Averaging
Time of five minutes, and a Sampling Interval of 60 seconds.
12:01 Sample sensor (reading = 1.0). No reading is logged.
12:02 Sample sensor (reading = 2.0). No reading is logged.
12:03 Sample sensor (reading = 3.0). No reading is logged.
12:04 Sample sensor (reading = 4.0). No reading is logged.
12:05 Sample sensor (reading = 5.0). Compute and log 5 minute average. Result = 3.0,
computed as (1.0+2.0+3.0+4.0+5.0)/5;
12:06 Sample sensor (reading = 6.0). No reading is logged.
12:07 Sample sensor (reading = 7.0). No reading is logged.
A Result of Running Min and Running Max produce results which are the minimum and
maximum of the Running Average during the interval. Just like the simple minimum and
maximum, running minimum and maximum values are logged with the time stamp of when the
minimum and maximum occurred rather than when the measurement was scheduled.
The system holds up to 180 samples for the Running Average. How many samples are to be used
is computed by dividing the Averaging Time with the Sampling Interval. If the setup is such that
more than 180 samples are required, the system will show a setup error:
Setup Errors: M1 Too many samples setup for running average
Additionally, every time a measurement is completed without all the samples, the system will log
a “Missingsamples” error.
9.2.3.3. Logging and Transmitting Minimum and Maximum
The time for the average will be computed based on the measurement time and interval, as
described previously. However, the time stamp for the minimum and maximum will be the
actual time when the minimum or maximum occurred. For example, you may see the following
in the log for an hourly average with samples every minute where the data is not in time
sequence:
4/14/2016 16:00:00 AVG 30.335 G
4/14/2016 15:24:00 MX 31.248 G
4/14/2016 15:15:00 MN 25.661 G
4/14/2016 17:00:00 AVG 30.225 G
4/14/2016 16:12:00 MX 32.060 G
4/14/2016 16:39:00 MN 28.454 G
Explanation of the logged data above: At 16:00 the hourly measurement that started at 15:00 is
complete. The average gets timestamped with 16:00. However, the actual maximum value of
31.248 happened at 15:24 and the minimum value of 25.661 happened at 15:15.
Likewise, at 17:00, the measurement that started at 16:00 is complete. The maximum happened
at 16:12 and the minimum at 16:39.
When it comes time to transmitting minimum and maximum results, Satlink will include a unique
timestamp with each value transmitted. An example below illustrates the formatting:
:ATMIN 91 #60 22.47 means that a minimum of 22.47 occurred 91 minutes ago.
:ATMIN 101 #60 22.50 means that a minimum of 22.50 occurred 101 minutes ago.
Contrast that format with :ATAVG which provides four readings on the same line, most recent
one 41 minutes ago, and subsequent readings each an hour later.
9.3. Configuration Settings
9.3.1. Measurement Type
The Measurement Type setting (in the Sensor section) will determine what kind of measurement
is made. Each of the different types will unlock other settings. For example, choosing Analog as
the Measurement Type will unlock the Analog Type setting.
The available Measurement Type options are
Precip Accumulation
Precip Rate
SDI-12
Analog
Battery Voltage
Wind (future release)
Digital
Meta
Manual Entry
Internal Temp
Below are listed all the Measurement Types available.
9.3.2. Measure Type: Precip Accumulation and Precip Rate
Connection: terminals 10, TB/DIN#2 and 9, Ground
Precip Accumulation and Precip Rate are designed to measure the pulses from a tipping bucket
type rain gauge.
Precipitation accumulation is used to tally the total amount of precipitation since the station has
powered up. Count must be set to zero by the user when the station is installed. Counts persist
between power-ups.
Precipitation rate, unlike precipitation accumulation, measures the precipitation that has
occurred since the last measurement. So, if the measurement interval is 15 minutes, this
measurement will report the rainfall in the last 15 minutes only.
Multiple measurements can be set up with the same input. For example, if you wanted to know
the daily rainfall and the rainfall during the last hour, set up two measurements: one a Precip Rate with an interval of one hour, and another as Precip Rate with an interval of one day.
Usually, a slope is applied to convert the counts from the tipping bucket into inches of rain. For
example, setting the Slope to 0.01 means that each tip of the bucket is 0.01”.
Precip readings are de-bounced for 4ms.
9.3.3. Measure Type: SDI-12
Connection:
PORT 1: terminals #13 GND, #14, +12V and #15, Data.
PORT 2: terminals #16 GND, #17, +12V and #18, Data
Note: each port is independent with isolated +12V power and Data connections. Power
is limited to 500mA. Sensors that use more than 500mA (such as bubblers) must
connect to an independent power supply.
SDI-12 is a standardized three wire digital interface. Many manufacturers provide SDI-12 sensors
that measure different environmental effects. SDI-12 sensors provide digital data which improves
their reliability and accuracy in terms of logger sensor communications.
For details on SDI-12, please see the section MORE ABOUT SDI-12.
9.3.3.1. SDI-12 Port
SDI-12 sensors can be assigned to Port1, Port2 or RS485. Remember that multiple sensors can
be connected to either bus as long as each sensor has a unique address. Use RS485 when you
need long cable runs to the sensor and the sensor supports SDI-12 over RS485.
9.3.3.2. SDI-12 Address
Multiple sensors can be connected to the same SDI-12 bus. However, each sensor needs a
unique address. The address is a single ASCII character. Most sensors default with the address 0.
If you are connecting several sensors, connect them one at a time. As each sensor is connected,
issue the 0Ax! command, changing the sensor’s address from 0 to x, where x is a unique number
or letter of your choice.
9.3.3.3. SDI-12 Command
Select the desired SDI-12 command from the drop-down list or enter a unique command into the
text box. The drop-down list includes M!, M1!, MC!, C!, CC!, M2!. Consult the operating manual
for the sensor to know what command to use. The software automatically adds the address
when issuing the command. The software also automatically issues the commands to retrieve
the data after the measurement command is issued.
Most SDI-12 sensors will respond to the measure command with multiple data values. The SDI-12
Param designates which of these data values the user is interested in.
Setting the parameter to 1 tells Satlink to use the first value returned from the device; setting
parameter to 3 tells Satlink to use the third value returned from the device.
If you want to record (and transmit) more than one parameter from a single SDI-12 sensor, a
different measurement needs to be set up for each parameter. These measurements should
have identical setups, except for the SDI-12 Param setting. Be sure to keep the measurement
time and interval the same for these measurements and SL3 will make a single measurement to
provide the data for both. If you vary the time and interval, Satlink will end up taking multiple
sensor measurements even though one would have sufficed (thus slowing down the system and
using more power).
In the case of devices which require multiple commands to be issued (e.g. 0M1! retrieves
pressure, 0M2! retrieves temperature) multiple measurements need to be set up. It does not
matter if these measurements are scheduled for the same time, as Satlink will have to issue
multiple commands to the sensors.
When multiple measurements of type SDI-12 are scheduled to go at the same time, Satlink
orders the measurement commands so that concurrent measurements are commanded first.
Non-concurrent measurements occur while waiting for concurrent results. Also, Satlink is able to
recognize when two different measurement schedules rely on data from a single measurement
command (e.g., measurement 1 commands 0M! and expects parameter 1 while measurement 2
commands the same and expects parameter 2, both scheduled at the same time). In such cases,
Satlink outputs the measurement command only once.
9.3.3.5. Warmup
If this number is not zero, then the Switched Power line (terminal #6, SWD#1 +12V) and VREF
(terminal #26 and #30) will be turned on for warmup seconds prior to talking to the SDI-12
sensor. The line will be kept on until the measurement completes.
You may use SWD#1 12V instead of SDI-12 Power to supply power to the SDI-12 sensor as long as
the sensor does not require to be powered on all the time. Some sensors (such as the Sutron
SDR) need to be powered on all the time and will not work correctly if powered from the
Switched Power line.
If you power the sensor via Switched Power, you must setup the Warmup to at
least one second!
Why use Switched Power instead of SDI-12 Power? To reduce power consumption of the SDI-12
sensor. SDI-12 Power is turned on all the time, while Switched Power is only turned on during
the measurement if Warmup is not zero.
Please note that using LinkComm's Send SDI-12 Command window will NOT turn on Switched
Power. However, doing a Live/Forced measurement will.
The SDI-12 command utility dialog is used to send SDI-12 commands to sensors connected to
Satlink. It can also be used to quickly find what sensors are connected to the SDI-12 bus.
To send a command to an SDI-12 device connected to Satlink, enter the Address and Command
fields, and then press the Send button. Be sure to check SDI-12 over RS-485, if you need to send
the command over the RS-485 bus. The results of the command are shown in the SDI-12 history
window.
To have Satlink look for any and all sensors on the SDI-12 bus, press the Find Devices button.
Information regarding what sensors are found is displayed in the SDI-12 history window.
Press the Clear button to clear the SDI-12 history window.
9.3.4. Measure Type: Analog
Analog measurements involve reading a voltage or current provided by a sensor. Analog sensors
come with instructions that provide information on how to translate the output voltage into
desired units. Translating the analog sensor output into environmental units can be done via
slope and offset for simple sensors, and via equations for non-linear sensors.
9.3.4.1. Analog Type
This setting directs the input channel to which the sensor should be connected and the type of
analog measurement to make. These options are available
0-5V A
0-5V B
Diff C
Diff D
Diff E
4-20 mA
Connection A: 0-5V A Terminal #36 and Signal ground Terminal #37
Connection B: 0-5V B Terminal #34and Signal ground Terminal #35
Inputs 0-5V A and 0-5B are designed to be general purpose 0-5 Volt DC input. While sometimes
referred to as a single ended input, it is designed to measure voltage with respect to analog
signal ground. These inputs have a high impedance (>2 Meg Ohms) and will not load down or
draw significant current. The input range is 0V to 5V. Negative voltages with respect to SIGNAL
GROUND may NOT be measured on these inputs.
To connect a sensor:
The voltage output by the sensor should be connected to either A or B.
The analog ground from the sensor needs to be connected to Signal ground.
The sensor will likely require power – connect that to VREF if 2.5V is appropriate or to
+SWD#1 POWER which is 12V (or whatever power Satlink is supplied with). Make sure to set
up the warmup (the amount of time to power the sensor before reading its output) as
required by the sensor.
If the sensor has a power ground, connect that to Signal Ground.
9.3.4.3. Diff C, Diff D , Diff E
Connection: Diff C (Terminal #32 and #33)
Connection: Diff D (Terminal #28 and #29)
Connection: Diff E (Terminal #24 and #25)
Optional connection to VREF (#26 or #30) and Signal ground (#27 and #31) as needed
Measurements Diff C, Diff D, and Diff E are designed to operate with a special type of analog
output found on many sensors that use a bridge configuration or any sensor that outputs a very
small voltage. This input type has a + and - input that connects to the sensor output.
Typically, a bridge sensor will be powered on VREF (sometimes referred to as excitation), have a
signal + and signal –, and provide a wire for the analog ground. NOTE: If after wiring the sensor, it
displays a negative reading, you may reverse the + and - leads coming from the sensor.
Reading Negative Output Voltages on Differential Inputs:
In limited cases, sensors with negative outputs may be used on the differential inputs with the
following limitations:
The negative line from the sensor must not connect to the digital ground of the sensor
with the sensor making a ground connection to the ground (including antenna ground)
of the Satlink logger. (i.e. the sensor outputs must be able to be floated with respect
the grounding of the sensor itself)
The negative voltage (or positive voltage) must remain within the range of the
differential input range selected.
The common mode input range of the differential inputs must not be exceeded (see
While the differential inputs are capable of reading negative voltages, it is important to keep the
voltages with respect to ground within in the common mode input range of 0.5 to 3.7 volts. In
the case of a bridge sensor, by using the vref and signal ground to establish the voltage on the
network, you are assured of having a positive voltage with respect to signal ground. In the case
of the bridge, you simply need to remain within the voltage range selected (see 6.1.4.12 below)
and simultaneously remaining in the common mode range of the inputs or 0.5 volts to 3.7 volts.
9.3.4.4. Input Range
This setting is relevant only to analog differential measurements. Remember that the system
must read a voltage that falls into the common mode range mentioned in the above note.
Voltages that are negative with respect to the SIGNAL GROUND terminal may not be measured.
The following options are available:
-39 to +39mV
-312 to +312mV
-2.5 to +2.5V
-39 to +39mV with Bias
-312 to +312mV with Bias
Note that the ranges for absolute measurements are nominal. Guaranteed analog input
range over temperature is 0-4.98 V, ± 2.49 V, ± 311 mV, and ± 38.9 mV.
Choose the option that is close to and greater than the input range of the sensor that is being
connected.
For example, if a sensor provides a reading from 0 to 100mV, choose the 312mV option. If you
were to choose the 39mV option, when the sensor provided a reading greater than 39mV, the
unit would indicate a sensor failure.
Use the range “with Bias” if the sensor is not powered by Satlink such as a pyranometer or
thermocouple.
9.3.4.5. 4-20 mA
Connection: 4-20ma IN (Terminal #23)
This input is designed to function with sensors that have a 4 to 20ma current loop interface. This
type of interface is superior to voltage outputs when the cables to the sensors must travel a long
distance or when the equipment is located in electrically noisy environments. Satlink will
measure the current flowing when connected to the 4-20ma Input. Typical 4-20ma sensors will
give a 4 to 20ma current for a 0 and 100% FS. Readings that are greater than 21mA will be
considered a fault. The current required for the sensor is provided by the 2 wire loop and does
not typically require additional connections.
NOTE: Satlink does not provide a dedicated power supply for 4-20ma sensors. The sensor shall
have its own supply or run off the 12 volt supply of Satlink. While the internal 4-20 measurement
is made using an accurate 100 ohm resistor, the overall loop resistance is 200 ohms due to an
additional 100 Ohms series protection resistor. This means that a sensor at a full 20 ma current
output, approximately 4 volts should be allotted for overhead voltage. This is typically not an
issue when an external voltage source is provided to operate the sensor that may be in the 18 to
24 volt range. However, if a 12.5 volt battery is used to source the voltage for the sensor in the
current loop, then only 8.5 volts will be supplied to the sensor at max sensor current output.
Therefore if a full 12 volts is necessary for the sensor, an external loop supply will be necessary or
alternately the sensor may be wired to a single ended voltage input with the use of an external
100 Ohm accurate and stable resistor also attached to the voltage input port.
9.3.4.6. Warmup
Analog sensors are powered by Satlink via one of several outputs:
VREF (reference voltage) which provides 2.5V, terminal #26 and #30.
Switched Power which provides whatever voltage is powering Satlink, presumably 12V,
terminal #6
Normally, these outputs are off. Prior to making an analog measurement, Satlink will turn on
these outputs. After that, Satlink waits Warmup amount of time (which is expressed in seconds)
before measuring the output of the sensors. This Warmup time gives the sensors a chance to
power up and prepare their outputs.
If Warmup is set to zero, Satlink will not wait at all prior to measuring. The value Warmup should
be set to depends on the analog sensor being measured.
Warmup is also used for Digital and SDI-12 type sensors. If a such a sensor (or
a wind sensor that uses digital or SDI-12 inputs) is set up with a warmup, then
VREF and Switched Power (SWD#1) will both be turned on. If warmup is set to
zero, those output lines will not be turned on. This is different for Analog
measurements which turn on the lines regardless whether warmup is zero.
9.3.5. Measure Type: Battery
This type measures the voltage of the battery connection to Satlink. This measurement is a useful
diagnostic for tracking the performance of the battery and any solar panel or other charging
equipment.
9.3.6. Measure Type: Wind
The Wind measure type makes it possible to do vector averages of data from wind speed and
direction sensors. The normal average function does not typically work for wind sensors because
of the circular nature of the direction measurement. The vector averages take into account the 0
to 360 degree crossover to produce accurate average.
Follow these steps to setup for Wind averages:
Step 1) Setup a measurement to measure the wind speed (see CONNECTING PROP/VANE
OR ANEMOMETER/VANE WIND SENSORS)
Set measurement interval for how often you want the speed measured
Use slope/offset/equation to properly scale the speed to the desired units.
Disable logging for the data (log interval = 24:00:00)
Disable transmission of the data (TX Data Content = Exclude)
Step 2) Setup a measurement to measure the wind direction (see Connecting Prop/Vane
or Anemometer/Vane Wind Sensors)
Set measurement interval for how often you want the direction measured
Use slope/offset/equation to properly scale the direction to degrees.
Disable logging for the data (log interval = 24:00:00)
Disable transmission of the data (TX Data Content = Exclude)
Step 3) Setup measurement(s) to do the wind calculations with the desired results
Select Wind measure type
Configure the speed and direction index to the measurements setup in steps 1 and
2
Pick the desired result type.
Set the schedule interval and averaging time for the duration of the averaging.
Set the sampling interval equal to the measurement interval of the speed and
direction sensors.
Repeat Step 3 for additional result types.
9.3.6.1. More on the Wind Measure Type
When you select the Wind Measure type, the configuration section will allow you specify where
to get the speed and direction data and what kind of result to log. The Wind measure type
requires you to setup separately the speed and direction measurements and provide the index in
the configuration. Normally, you will want to setup these measurements before setting up the
Wind type. Speed index is the measurement setup separately to get the speed. Direction index
is the measurement setup separately to get the direction. Make sure each input is configured to
provide the data in the proper units (mph, mps … for speed and degrees for direction). You will
want to schedule these measurements to occur at the interval you want for your vector
processing (e.g. 00:00:10 or 00:01:00). You will also want to disable logging for the sensor by
setting log interval = 24:00:00 and also exclude the data from transmission tx content = exclude.
Configuration also allows you to specify what kind of result you’re looking for from the wind
processing. The available types are shown below. If you want more than one of the results,
setup a separate measurement for each:
Mean Speed Scalar
Mean Magnitude Unit
Mean Magnitude Wind
Mean Direction Unit
Mean Direction Wind
STD Speed Scalar
STD Direction Unit
STD Direction Wind
Min Speed Scalar
Max Speed Scalar
After picking the result, set the schedule for the calculation. The following schedule computes a
15 minute average of wind data collected every 60 seconds. The sampling interval (e.g. 60
below) must match with the interval set for the speed and direction sensors setup separately.
Here’s the setup for wind processing to compute a 10 minute average with data collected every 5
seconds. Again, the sampling interval 5 much match the measurement interval setup for the
speed and direction sensors.
When you setup multiple results, make sure each has the same schedule.
The following sections give details on each of the results.
9.3.6.2. Wind Results
The Wind Measurement type processes data using Vector Average techniques
that are needed to any sensor that has a circular discontinuity, such as a wind
direction sensor with the crossover from 0 to 359 degrees. In these cases,
simple averaging does not work -- the mean of 0 and 359 is 179.5, which is
clearly incorrect. Calculating a vector average provides a way around this
problem.
When the data is processed the software automatically performs several
different types of vector calculations, each conveying slightly different
information. It is up to the user to pick which results meet the requirements for
the measurement. While the wind processing is geared toward wind sensors, it
could be used any time performing a vector average is desired.
The results of Wind processing are as follows, with vector math shown below.
Mean Speed Scalar – This is the scalar wind speed, not taking direction into
account. The scalar average of 10mph for an hour and 20mph for an hour is
15mph, regardless of changing direction. This result is identical to the value
you’d get with a simple average of the speed.
Mean Magnitude Unit – This is the vector average of the wind speed using unit
vectors. The mean magnitude unit of 5mph at 0 for 1 hour and 100mph at 90
for 1 hour is 0.707. This is found by adding the two vectors, finding the
magnitude of the resultant vector, and dividing by the number of vectors in the
average (two, in this case). Since the mean magnitude unit is an average of unit
vectors, it will always be between 0 and 1.
Mean Magnitude Wind – This is the vector average of the wind speed which
takes direction into account. Here, the average of 10mph at 0 for 1 hour and
20mph at 90 for 1 hour is 11.2 mph.
Mean Direction Unit – This is the wind direction (in degrees) not weighted for
wind speed. Here, the average of 10mph at 0 with 20mph at 90 is 45. This is
the value you’d get with a simple average of the direction if no 0-360 crossover
occurred.
Mean Direction Wind – This is the wind direction (in degrees) weighted for wind
speed. Here, the average of 10mph at 0 with 20 mph at 90 is 63.4.
STD Speed Scalar – This is the standard deviation of the scalar wind speed.
STD Direction Unit – This is the standard deviation of the direction unit.
STD Direction Wind – This is the standard deviation of the direction wind.
Min Speed Scalar – This is the minimum of the scalar wind speed.
Max Speed Scalar – This is the maximum of the scalar wind speed.
Max Direction – This is the direction taken at the time the max speed is
detected.
Count – This is the number of samples that have been taken.
Time of Max Speed – This is the time in seconds past midnight, when the
maximum speed was recorded.
9.3.7. Measure Type: Digital
Use the setting Digital Type to tell Satlink what kind of sensor is connected.
9.3.7.1. Digital Type
Satlink supports the following digital types:
Level 1&2 (terminal 8 and 10)
Counter 1&2 (terminal 8 and 10)
Frequency 1&2 (terminal 8 and 10)
Period 1&2 (terminal 8 and 10)
Frequency will have Satlink sample the input for 750ms. It will provide a result that is the average
frequency of the input during that time span.
10kHz is the maximum input frequency that Satlink supports.
When Period is the chosen type, Satlink will watch the input line for up to 10 seconds. Satlink
stops watching as soon as one wave period is noticed on the input. Please note that a period
measurement could take just over 20 seconds to complete (up to 10 seconds per edge of the
signal). If such a slow signal may appear on the input, please make sure that the measurement
interval is long enough (longer than 20 seconds) to prevent missing measurements.
Digital measurements also use the Warmup setting. If Warmup is not zero, then switched power
and VREF will be turned on during a Digital measurement. See the section on analog
measurement types for details on Warmup.
Counter type readings may be optionally de-bounced for 4ms using the Debounce setting. The
4ms de-bouncing eliminates false counts from tipping buckets and other devices with noisy
switches.
Counter type readings may also be limited by a rollover value. With rollover set to 0, the counter
will increase until it reaches 4,294,967,296 (2^32). With rollover set to a non-zero value, the
counter will be reset to 0 when it exceeds the rollover value. For example, if rollover is set to
9999, the counter will be reset to 0 on the 10000 count.
Please note that counter and tipping bucket measurements will keep counting even when
recording is off.
Satlink will allow the setup of multiple measurements on the same digital input. For example, it is
possible to setup both a tipping bucket rate and a tipping bucket accumulation on the same
input.
That being said, some setups that share digital inputs will yield unpredictable results.
o Setting up any number of tipping bucket and counters on DIn2 with debouncing
will work well.
o Setting up a tipping bucket and counters without debouncing on DIn2 will not
work correctly as far as debouncing is concerned.
o Setting up a level measurement will work in combination with any other
measurement.
o Setting up multiple frequency and period measurements on the same input will
work as long as the measurements do not overlap.
o For frequency and period readings on the same input, one measurement must
finish before a second one starts for the readings to be correct.
o For frequency and period readings, SL3 will not hold up one measurement until
another completes.
o Overlapped frequency and period measurements are not considered a
meaningful setup.
o Setting up a frequency or period measurement on the same input as a tipping
bucket or counter will not work correctly.
If you want to measure both frequency and count from an input you will need to jumper
it to both digital inputs and setup one measurement for the counter (e.g. counter 1) and
the other for a frequency (e.g. frequency 2).
9.3.8. Measure Type: Meta
Meta measurements use the result of another measurement as their basis. Usually, a Meta
measurement is used to average results of another measurement.
9.3.8.1. Meta Index
This setting tells Satlink what other measurement this Meta measurement refers to.
Why use meta measurements? If you had set up an hourly averaged temperature measurement,
a Meta measurement could be set up to be the daily average of all those hourly readings.
Measurement M1 (used for Hourly Temperature)
Measurement Type: Analog
Analog Type: 0-5VA
Measurement Interval: 1 hour
Averaging Time: 1 hour
Sampling Interval: 1 second
Measurement M2 (used for Daily Temperature)
Measurement Type: Meta
Meta Index: 1 (meaning it refers to measurement M1)
Measurement Interval: 24 hours
Averaging Time: 24 hours
Sampling Interval: 1 hour
When scheduling meta measurements, take care that they occur at the same time or after the
measurement they reference. If the meta and the reference are scheduled for the same time,
Satlink will try to delay the meta measurement until the reference completes.
9.3.9. Measure Type: Manual Entry
Manual entry measurement types allow the user to enter a reading manually. That value
becomes the reading of the measurement. Satlink will store the user entered value in the Offset
field.
To enter a manual entry reading, use LinkComm's Calibrate button.
9.3.10. Measure Type: Internal Temperature
Internal Temperature measurements use a temperature sensor installed inside Satlink. Every
Satlink comes with a built in temperature sensor. The reading provided is in degrees Celsius. To
convert from Celsius to Fahrenheit set the slope to 1.8 and the offset to 32.
9.4. Processing Settings
9.4.1. Slope
See Offset below.
9.4.2. Offset
Every measurement is computed by taking the sensor reading, multiplying it by slope and adding
offset to it.
Measurement result = (sensor output)*slope + offset
Slope defaults to 1.0 and offset defaults to 0.0, meaning they will not affect measurement result
by default.
Traditionally, when using an analog sensor, slope and offset are required to convert the voltage
output by the sensor into desired units. The required slope and offset are provided by the sensor
manufacturer.
Satlink supports more complex equation processing (see Equations below).
Slope and offset are applied after equations.
The reading before slope and offset are applied is referred to as the raw reading. For example, if
an analog sensor were to provide a voltage of 2 volts, and the user had set up the Slope as 5 and
Offset as 1, the final reading would be 11 (2*5 + 1). The raw reading would be 2. If Details is
enabled, the raw reading is displayed on the command line by typing MEAS or LAST.
Satlink offers easy ways to change the current reading of the measurement by modifying just the
offset or both the slope and offset via the calibration functions.
9.4.3. Use Equation
Select “Use Equation” to allow an entry of the equation in the box below it. See the next section
for examples.
9.4.4. Equation
Data collected from sensors to be processed by an equation. If the reading provided by the
sensor needs more than just an offset and a slope applied, equations provide that functionality.
The field Use Equations can be set to enabled or to disabled. It determines whether equation
processing is to be applied to the raw data. The field Equation can be set to an ASCII string no
longer than 128 bytes (per measurement). That field contains the equation to be applied.
If both Equations and Slope and Offset are used, Slope and Offset are applied after the equation
is processed.
For example, to convert Fahrenheit to Celsius, type into command line:
M1 EQUATION = (X-32.0)*5/9
In the example above, X refers to the sensor reading.
LinkComm comes preloaded with equations for many types of sensors. To see the equations,
press “Template…” and then select the desired equation from the dropdown box.
Equation processing can take a while to complete (up to several seconds). If
you are using a lengthy equation, Satlink may not be able to complete a
measurement every second, or even every two seconds (see Bad Schedule in
the Error section).
9.4.5. Equations: Syntax
The equation is expressed in terms of "X" which will be applied to incoming sensor data.
SQRT is square root, eg SQRT(9) = 3
To raise a number to a power, multiply it by itself. So, for
example, to find x squared, input x*x.
EXP, if EXP(x) = y, then LN(y) = x, eg EXP(1) = 2.718282
LN, natural log, eg LN(2.718282) = 1
LOG, 10 based log, eg LOG(10) = 1
INT returns the integral portion of a real number
INT(11.456) = 11.000 INT(-1.345) = -1.000
FRACT returns the fractional portion of a real number.
FRACT(11.456) = 0.456 FRACT(-1.345) = -0.345
ABS returns the absolute value of a real number.
ABS(11.456) = 11.456 ABS(-1.345) = 1.345
RND provides random integer number between 1 and x.
RND(100) will produce whole number between 1 and 100
POLY is used to compute up to a 5th level polynomial equation:
POLY(x, A, B, C, D, E, F) equates to A + Bx + Cx^2 + Dx^3 + Ex^4 +
Fx^5
STEINHART(x, A, B, C) is used for Steinhart-Hart equations,
where x is the resistance and result is the temperature in Celsius
A, B and C are thermistor specific constants
Steinhart result is computed like so: 1/(A + B*ln(x) +C*(ln(x)^3))
- 273.15
MINDAY returns minutes into the day.
SECDAY returns seconds into the day.
VREF returns the exact analog voltage reference.
Comparisons can be performed using <, >, <=, >=, !=, and =. The
result of a comparison is 1 for true or 0 for false.
Modulo can be performed using % operator, e.g., 10%2=0, 10%3=1.
The following bitwise boolean operators are supported: AND, OR,
XOR, SHL, and SHR. The last two are shift-left and shift-right. For
instance (X SHL 4) would shift X left by 4 bits. AND & OR can also
be used in logical expressions. For instance (X>100) OR (X<50)
would result in 1 if X is above 100 or below 50; otherwise it would
result in 0.
The NOT operator is logical not bitwise. This means that NOT 0 is 1
and NOT 1 is 0. Also, the NOT of any non-zero number is 0, eg. (X
AND 128) != 0 results in a 1 if bit 7 in X is set or 0 if bit 7 is
clear. The bit mask 128 is 2^7. This assumes bit 0 is the least
significant bit. In general, the bit mask for any bit N is 2^N.
OUTPUT(A,B,C,D) controls one of the 2 digital outputs or 3
switchable voltages.
A is the conditional. If 0, no output happens; if 1 output
activates.
B is the output (1 = DOUT#1, 2 = DOUT#2, 3 = SWD#1, 4 = SWD#2, 5 =
PROT12
C tells whether to switch (0) or to pulse (1)
if switching (C=0), D is direction to drive (0 open, 1 closed.
line is open by default.)
if pulsing (C=1), D is duration of the pulse in ms
Equations can also contain references to other sensors: eg. (X +
M4)/2, would add X to the value of measurement M4 and divide by 2.
Use Prev1, Prev2, Prev3.. to access the previously made reading by
said measurement. And, use DeltaT1, DeltaT2, Delta T3.. to access
the amount of time in seconds between the most recent and the
previous measurements.
12:00:00 Measurement M1 has made a reading of 1.0
At this point, we do not have enough data to compute Prev1 or
DeltaT1
12:05:00 Measurement M1 has made a reading of 2.0
At this point, M1 = 2.0, Prev1 = 1.0, DeltaT1 = 300
12:15:00 Measurement M1 has made a reading of 3.0
At this point, M1 = 3.0, Prev1 = 2.0, DeltaT1 = 300
Comments can be contained within braces { }. For example:
{convert from degrees Celsius to degrees Fahrenheit} X*9/5+32
Other examples:
SIN(X)+COS(X)+X^3+LOG(X)
(X>1000)*1000 + (X<=1000)*X {would limit the value so that it could
never be greater than 1000}
Troubleshooting:
The only true test of equation processing is to hit Force Measurement after the equation has
been set.
9.4.6. Equations: Referencing other measurements
If you are setting up an equation that references another measurement, set the measurement
type to meta, and make sure the measurement time and interval are the same as the referenced
measurement. In the equation, reference the other measurements as M1, M2, M3, etc.
If you wish to use the analog reference voltage in the equation, use VREF.
For example, if you wanted to trigger a sampler via the digital output when a conductivity sensor
reading exceeded 80, do the following:
Setup measurement M1 to collect data from the conductivity sensor.
Setup measurement M2 as a Meta measurement, with the Meta Index set to 1 in order
to reference M1. This ensures that M2 will wait for M1 to complete before producing a
result. Make sure the schedule for M1 and M2 is the same.
Setup the equation of M2 to OUTPUT(M1>80, 1, 1, 2000). That will cause Satlink to
pulse DOUT#1 for 2 seconds whenever the conductivity sensor exceeds 80.
9.5. Alarm Settings
Alarms are used to send immediate notifications when sensor readings read a certain threshold.
They can also be used to control an output (page 118.)
When a measurement is made, if alarms are enabled for that measurement, the sensor reading is
compared to the Alarm Threshold and Alarm Deadband. If certain criteria are met, the alarm
triggers (see below).
When a sensor reading reaches a certain threshold, the station is said to go into alarm.
While that sensor reading stays above the threshold, the system is considered to be in
alarm.
After the sensor reading drops below the threshold, the system goes out of alarm.
When the station is in alarm, it is noted in the station's status.
When a station goes into or out of alarms, the reading causing the alarm is logged. Additionally,
an event is recorded in the log.
Satlink can be set up to send transmissions when it goes into alarm. Alternatively, Satlink can be
set up to make a transmission when it goes into alarm and to make another transmission when it
goes out of alarm.
All enabled transmissions that are of the Random and of the Alarm kind will trigger with alarms.
Satlink can control its digital output based on alarm conditions. See the Output section for
details.
Most sensor readings cause alarms at the time the measurement is scheduled. If a temperature
sensor is set up for alarms with a Measurement Interval of 15 minutes, the station will read the
sensor every 15 minutes and decide whether to go into alarms.
Some sensors, including the tipping bucket and sensors setup as digital counter and level, can
cause instant alarms. When the tipping bucket tips, Satlink is immediately notified. If the tip
causes an alarm condition, the station goes into alarms right away, even if it was not time to
make a measurement.
Each measurement may be set up with up to three different alarms. This way, it is possible to get
an alarm when the stage reaches 3 feet, another alarm when it reaches 4 feet, and a third alarm
when it reaches 6 feet.
If more than three alarms are needed for one sensor, set up two measurements to read the same
sensor, but give them different alarm conditions.
9.5.1. Alarm 1, Alarm 2, and Alarm 3
Each of these settings can have one of the following values
Off
High
Low
ROC
These settings are used to determine what kind of computation is made when checking a sensor
for alarms. Read on for a complete explanation.
9.5.2. Threshold 1, Threshold 2, and Threshold 3
The threshold is a value that is compared to the sensor reading in order to determine whether to
go into or out of alarms.
9.5.3. Deadband
The Deadband, along with the Threshold value is used to compute whether the measurement
will go out ofalarms. Deadband helps the system ignore noise on the input that would cause the
measurement to go in and out of alarm on each measurement.
For example, if a High Alarm with a the Threshold of 10.5 and a Deadband of 3.0 were setup, the
system would go into alarm once the reading was equal to or greater than 10.5. The system
would stay in alarms as long as the reading was equal to or greater than 7.5. Once the reading
dropped below 7.5, the system would go out of alarms.
Alarm Tx Mode determines whether transmissions are made when the station goes (into alarm)
or (when it goes into and out of alarm).
If the Alarm Tx Mode is Tx In, the station will only make a transmission when it goes into
alarm.
If the Alarm Tx Mode is Tx In And Out, the station will make a transmission when it goes
into alarm and it will make another transmission when it goes out of alarm.
Random and Alarm transmissions are the only types of transmissions triggered by
alarms.
The telemetry setting Alarm Interval can be used to keep transmitting as long as a
station is in alarm. Please see the Telemetry section for details.
ROC alarms setup for Since Last Tx do not generate out of alarm events or
transmissions.
9.5.5. Alarm Logging
If Alarm Logging is set to Every Measurement, the system logs on the Measurement
Interval.
If Alarm Logging is set to Use Logging Interval, the system logs on the Logging Interval.
This setting is only relevant if the customer setup the Measurement Interval to be more
frequent than the Logging Interval. In that case, the system can be configured to log
more frequently when it is in alarm.
Here is an example of a system setup to log more frequently while in alarms. The system is set up
to read the temperature sensor every two minutes and check for alarms. If the temperature
exceeds 20 degrees, the system will go into alarm. The system will log once every two minutes
when in alarm, and once an hour when not in alarm.
Measurement Interval = 00:02:00
Logging Interval = 01:00:00
Alarm Logging = Every Measurement
Alarm 1 = Hi
Threshold = 20
9.5.6. Alarm ROC Interval
This setting affects ROC (Rate of Change) alarms. When set to Since Last Meas the system will
compare two consecutive scheduled readings when deciding whether to trigger alarms.
When it is set to Since Last Tx, the system will compare the current sensor reading with the last
transmitted reading. If there is no past transmission, the first reading made after boot up is used.
9.6. Alarm Computation Details
This section contains details on how Satlink decides whether to go into alarms. The section is
broken down by the user chosen Alarm Type setting:
When the Alarm Type is set to Hi, if the sensor reading is greater than or equal to Alarm
Threshold, the station goes into alarm.
That station will go out of alarm when the sensor reading goes below Alarm Threshold minus
Alarm Deadband.
9.6.2. Low Alarm
When the Alarm Type is set to Low, if the sensor reading is less than or equal to Alarm Threshold,
the station goes into alarm.
That station will go out of alarm when the sensor reading goes above Alarm Threshold plus Alarm
Deadband.
9.6.3. ROC Alarm
ROC stands for Rate Of Change. ROC alarms compare the current measurement reading with a
past reading. If Alarm ROC Interval is Since Last Meas, the past reading is the last scheduled
reading made according to Measurement Time and Measurement Interval.
If Alarm ROC Interval is Since Last Tx, the past reading is the one that was included in the last
alarm transmission. If there is no past transmission, the first reading made after boot up is used.
If the absolute difference between the two readings (absolute of current reading minus past
reading) is greater or equal to the Alarm Threshold, the station goes into alarm.
The same station goes out of alarm if the absolute difference between the two readings
(absolute of current reading minus past reading) is less than the Alarm Threshold minus Alarm Deadband.
Exception: ROC alarms setup for Since Last Tx do not generate out of alarm events or
transmissions.
9.7. Logging Settings
9.7.1. Logging Interval
Logging Interval dictates how often to log sensor data.
Change the Logging Interval to measure sensors more frequently than to log them. This is useful
for alarm setups, in which you want to check the water level once a minute in order to detect
fast rising water, but one only wants to log the water level data once an hour. For this scenario,
the Measurement Interval would be one minute, and the Logging Interval would be one hour.
For alarm conditions, it is possible to set Alarm Logging to Every Reading. That would result in
the water level in the example above being logged once a minute when the system was in alarm,
and logging once only once an hour when not in alarm.
If Logging Interval is set to zero, Satlink will log every measurement. It is the same as having the
Logging Interval equal to the Measurement Interval.
LinkComm provides a Log All checkbox: when checked Satlink will measure and log at the
Measurement Interval.
Having a Logging Interval that is shorter than the Measurement Interval is a bad setup.
Only logged readings may be transmitted.
It is not possible to entirely disable logging of measurement results. However, one can set the
logging interval as slow as once a day.
9.7.2. Log Error Value
When Satlink cannot get valid data from a sensor (more specifically, when a sensor failure error
occurs), Satlink will change the sensor reading to match the user-set Log Error Value, which
defaults to -99999. Such atypical numbers are used to attract the user’s attention when viewing
the log.
9.7.3. Transmission Data Content Settings
9.7.4. Tx Data Content
Tx Data Content tells Satlink which readings to include in the transmission. Each measurement
has the Tx Data Content setting.
The options are All, Individual, Last, and Exclude.
By selecting All, all the measurements that are logged are also set to be transmitted.
Only readings made since the last transmission are included. This setting is dependent
on the Log Interval setting.
Last means to transmit a set number of the most recent readings (determined by
Number of Values to Tx).
Use Last for alarm transmissions to ensure that the value that caused alarms is
transmitted!
By selecting Exclude, no readings of this measurement are transmitted.
See Tx Data Time and Interval below for the Individual setting.
9.7.5. Tx Data Time And Interval
If Individual is selected for Tx Data Content, the fields Tx Data Time and Tx Data Interval will
appear, allowing the choice of what data to include in the transmission.
This options should only be used to measure and log data more frequently than to include it in
transmissions. For example, if one wanted to measure and log data once a minute, one would set
the Measurement and Logging Intervals to one minute. Since it may be expensive to transmit all
that data, one can choose to transmit only every 10th reading by setting the Tx Data Interval to
00:10:00.
The example below uses Measurement and Logging Intervals of 15 minutes. Tx Data Content is
set to Individual.
11:00 measure and log data
11:15 measure and log data
11:30 measure and log data
11:45 measure and log data
11:50 transmission
Setup options:
The user could set up to transmit all four of those values:
Tx Data Content = All
The user could set up to transmit the data from 11:15 and 11:45:
TX Data Time = 00:15:00, Tx Data Interval = 00:30:00
The user could set up to transmit only the data from 11:45:
Tx Data Time=00:45:00, Tx Data Interval = 01:00:00
The user could set up to transmit only the data from 11:00:
Tx Data Time=00:00:00, Tx Data Interval= 01:00:00
Setup to transmit the most recent two readings from 11:30 and 11:45
Tx Data Content = Last, Number of Values to Tx = 2
Tx Data Interval must be a multiple of the Logging Interval. Setting Logging
Interval to15 minutes and Tx Data Interval to 20 minutes is not a good idea.
9.8. Measurement Setup Defaults
To change the setup of a single measurement to its defaults, type M1 SETUP DEFAULT on the
command line to reset measurement one. This will affect only one measurement.
9.9. Measurement Calibration
Satlink offers an easy way to change the current reading of any measurement. Press the Calibrate
button on the Measurements tab in LinkComm and enter the desired reading.
Via command line, type M1=10.5 to set the reading of measurement one to 10.5
This calibration procedure has the effect of modifying the measurement’s Offset.
When a sensor is calibrated, Satlink will log the readings before and after the calibration along
with a calibration event:
You can set up multiple measurements with the same input. For example, to log the daily rainfall
and the rainfall during the last hour, set up two measurements: one as a precipitation rate with
an interval of one hour, and another as precipitation rate with an interval of one day.
To log the daily temperature and the hourly temperature, only one physical temperature sensor
is needed. Set up two measurements with the same setup; change the Measurement Interval and
the Averaging Time and use a different Label for each. One would happen once a day
(Measurement Interval 24 hours, Averaging Time 24 hours), and the other once an hour
(Measurement Interval 1 hour, Averaging Time 1 hour). It would be a good idea to set up the
sampling Interval to one minute for both sensors in order to save power (See page 71).
If two separate measurements are scheduled to measure the same sensor at the same time (as
they will in the examples above), only one reading of the sensor is made and the result is shared
by both measurements.
Satlink has a built-in environmental satellite transmitter certified by NESDIS, Eumetsat, Insat and
other satellite agencies. These satellites provide reliable one way communications of data from
remote locations to receive stations/computer systems around the world.
The setup for the transmitter and its status is provided on the Telemetry tab as shown below.
The column on the left shows that up to four independent telemetry setups are possible.
The first two setups are reserved for Environmental Satellite transmissions: the first setup is
reserved for scheduled transmissions (aka self-timed transmissions), and the second for random
transmissions.
The last two setups may be setup for any kind of telemetry, including Iridium, Cell, and
Environmental Satellite.
Each telemetry setup is configured and enabled separately. If no telemetry setups are enabled,
the system will show an error on the dashboard.
Please note that the transmission data content is governed by measurement setup. Please see
the section TRANSMISSION DATA CONTENT SETTINGS for details.
The column on the right has two main sections – Telemetry Setup and Telemetry Status. You
may need to scroll down to see the Telemetry Status
The setup consists of information that tells Satlink when to transmit, what type of satellite to
use, the channel, the antenna type and other critical information. Most of this information
originates from the agency that operates the satellite (e.g. NESDIS) and is unique for each
station. Incorrect information can cause the system to mishandle the information you send or
interfere with the operation of another station. Always check to make sure the information you
have for the station is unique for that station and correct.
Some of the settings are common to different Radio Types.
10.1.1. Enable
This is the master switch for enabling the telemetry setup.
10.1.2. Radio Type
Which radio is to be used for the telemetry? Satlink comes with an Environmental Satellite radio
built in. Optional radios include Iridium and Cell.
10.1.3. Kind
Several different transmission kinds may be setup:
Scheduled
Random
Alarm
Please read on for details on each Tx Kind. Note that not all Tx Kinds are available for all Radio
Types.
10.1.4. Transmission Schedule
When Satlink should make a transmission depends on the transmission schedule. The time is
generally computed based upon these settings:
Scheduled Time
Scheduled Interval
The interval controls how frequently the transmission is made, and the time controls when the
transmission is started.
This section describes Environmental Satellite Scheduled transmissions. Scheduled transmissions
happen periodically at a fixed time.
TX1 setup is reserved for scheduled transmissions using an environmental satellite. Additional
scheduled transmissions may be setup on TX3 and TX4.
Satlink is certified to operate with NESDIS, EUMETSAT, INSAT and other agencies who operate
their respective satellite systems. The governing agency will assign to each transmitter a unique
Satellite ID, channel (and associated type) and scheduled time and interval. The combination of
these settings is unique to each field station.
Warning: Any errors entering the information may cause the transmitter to interfere with other
stations in the field.
10.2.1. Tx Enable
Enables scheduled (sometimes called self-timed) transmissions. If this setting is enabled, Satlink
will periodically deliver sensor data to the designated destination. If disabled, Satlink will not
initiate any scheduled transmissions.
10.2.2. Transmission Schedule
The governing agency will assign a specific transmission time and interval for scheduled
transmissions. Enter the assigned schedule via the Scheduled Time, Scheduled Interval, and
Window Length settings.
For example, a station may be assigned to transmit on GOES 300 baud channel 195 at a time of
00:02:30, an interval of 04:00:00 and the time slot is 30 seconds long. That means the
transmitter is allowed to transmit at 00:02:30, 04:02:30 …20:02:30 and transmissions are to last