GTecLink Gateway Manual

1. INSTALLATION 4 

1.1 Equipment 4 

1.2 Description (Gateway overview) 5 

1.3 Gateway power system 7 

1.3.1 Ethernet cable power (using PoE Injector) 7 

1.3.2 External power supply 10 

1.4 Enclosure mounting 11 

1.5 Internet communication 14 

1.5.1 SIM Card 14 

1.5.2 Ethernet connection 15 

2. CONFIGURATION 16 

2.1 Gateway connection 16 

2.1.1 Local management interface (USB) 16 

2.1.2 Fast connection (3G/GPRS or Ethernet) 18 

2.2 Setup menu 19 

2.2.1 Networks 19 

2.2.2 Status 22 

2.2.2.1 Gateway status 22 

2.2.2.2 Logs 25 

2.2.3 Configuration 26 

2.2.3.1 General 26 

2.2.3.2 FTP client 26 

2.2.3.3 Compacted CSV 28 

2.2.3.4 ModBUS gateway (ModBUS TCP server) 30 

2.2.3.5 Internet 32 

2.2.3.6 GPRS/3G 37 

2.2.3.7 Radio 39 

2.2.3.8 Remote Access 41 

2.2.3.9 Upload firmware 43 

1 

2.2.3.10 Delete All 44 

2.2.3.11 Reboot 45 

3. DATA VISUALIZATION AND RETRIEVAL 46 

3.1 Data recovery directly from the NODE 46 

3.2 Data retrieval and visualization from the gateway 47 

3.2.1 Engineering units conversion 47 

3.2.2 Data visualization from the gateway 49 

3.2.3 Data retrieval from the gateway 50 

3.2.4 Sending files by FTP 52 

3.2.5 Last messages (API format) 53 

4. REST API calls 54 

5. RADIO 57 

5.1 Loadsensing radio system introduction 57 

5.2 Radio specifications 61 

61 

62 

63 

3G/GPRS modem settings

5.2.1 58821000 (CE)

5.2.2 58822000 (FCC)

5.2.3 58823000 (Asia/Pacific)65 

5.3 Number of nodes, sampling rate and slot time 67 

70 

71 

6. RESULTS OF SIGNAL COVERAGE TEST

7. CONTACT DGSI.

8. TROUBLESHOOTING REFERENCE TABLE 72 

2 

52 

53 

53 

60 

61 

63 

66 

66 

67 

70 

71 

72 

TABLES

Table 01: API Calls (Inventory).

Table 02: API Calls (Data) .

Table 03: API Calls (Monitoring) .

Table 04: 58821000 (CE): Radio settings details.

Table 05: 58822000 (FCC): Radio settings details.

Table 06: 58823000 (Asia/Pacific): Radio settings details.

Table 07: Slot time table: VW, ANALOG TILT nodes.

Table 08: Slot time table: RST / SisGeo networks at digital node.

Table 09: Slot time table: MDT Smartlink networks at digital node.

Table 10: TroubleShooting: GPRS/3G connectivity.

Table 11: TroubleShooting: Ethernet connectivity.

Table 12: TroubleShooting: Data errors.

 

 

   

3 

1. INSTALLATION

1.1 Equipment 

The DGSI GTecLink Gateway is shipped with the following accessories: 

- Antenna

- Cable antenna

- Power over Ethernet (PoE) injector for wired network interface

- USB local administration interface

- Mounting kit

Not included: 

- Data line surge protector

- Antenna surge protector

4 

1.2 Description (Gateway overview) 

The  GTecLink  Gateway  is  made  of  high-impact  resistant  polycarbonate,  engineered 

to  withstand harsh industrial and outdoor environments. It offers an excellent

flammability rating, good UV and chemical resistance and is rated IP67. 

We  recommend  setting  up  and  configuring  the  gateway  in  an  office  environment  rather 

than going through the startup procedure in an outdoor or industrial environment. 

GTecLink Gateway, with all the parts indicated  

The GTecLink Gateway has the following parts: 

1. The casing

2. Cable gland for RJ45 PoE or DC power cable

3. N connector for the sensor network radio antenna

4. Pressure stabilizer to protect against condensation

5. Sensor network radio antenna with N connector

5 

6. Mounting kit

7. PoE injector and power supply cable

The gateway casing can be opened with a flat-head screwdriver via the small holes on                             

either side of the door. You will need to open the gateway to perform the initial installation                                 

and configuration procedure. 

GTecLink Gateway, with all the parts indicated 

Note:  PoE  power   supply   should   be   installed   inside   a   box   or   indoors   since   it  is  not  

waterproof. 

6 

1.3 Gateway power system 

The  gateway  can  be  powered  either by PoE (Power over Ethernet) or DC. Only one power 

source is needed. Nominal power consumption is about 3.2 W (270 mA at 12 V); peaks reach

3.84  W  of  consumption,  while  idle  is  2.16  W.  In  any  case,  the  device  allows  a  11-30  V 

functioning range. 

1.3.1 Ethernet cable power (using PoE Injector) 

PoE  connection  to  the GTecLink Gateway complies with the IEEE 802.11af standard. The 

device is provided with a PoE compatible internal power supply. 

On the gateway side, the Ethernet cable (not included) must first be inserted into the case

through the cable gland. This cable gland allows a 4 mm to 8 mm diameter cable. The cable

must be unshielded and stripped and connected to the terminal blocks in the correct order,

as shown in the image below 

Ethernet cable connection scheme (Gateway side) 

We recommended using wire terminators to ensure better contact between cable wires and

the  connection  pad. We also recommended using a shielded Ethernet cable (STP cable) in 

order to avoid external interference.  

7 

Detail of the connections for the Power through PoE 

Note that when grounding the gateway, a suitable Ethernet cable (shielded, as shown in                           

the following image) should be inserted through the cable gland. The shield of the cable                             

must be clamped in the “earthing clip” to get good earth shielding, as depicted in the image                                 

below. 

a)  b) 

a) Cross section of a shielded Ethernet cable; b) Detail of the power connection 

through PoE using a shielded Ethernet cable. 

The other end of the Ethernet cable must be connected to the PoE injector through a                               

standard, T568A/B specified Ethernet connector (RJ45). 

8 

It must be connected to the PoE injector port named “DATA AND POWER OUT”. The PoE                               

injector must be connected to a power source. 

The PoE injector may be replaced by a PoE powered switch port since the gateway does                               

not require more than 48 V (the standard voltage provided by PoE switches). 

Note: A suitable weatherproof Ethernet cable should be used if the gateway is to be placed 

outdoors (e.g. Ubiquiti TOUGHCable). Alternatively, a normal Ethernet cable may be used in 

combination with a protection tube. 

Wiring of the cable at the RJ45 connector (following T-568A/B specifications) to be 

inserted in the PoE Injector 

9 

1.3.2 External power supply 

The gateway can also be powered using direct current (DC) through an external power                           

supply, which may vary between 11 and 30 V. This alternative method has been developed                             

for installations in which PoE (Ethernet cabling) is not possible due to the facilities. 

For example, external waterproof housing can be mounted with an AC cable input, and a                             

12V or 24V exit (AC/DC power supply), a battery, or a solar or thermal solar kit.  

In such installations, the power cable connected from the external power supply is cabled                           

to the “CC” connection pad shown in the image below, passing through the cable gland                             

used for the Ethernet PoE connection. This means Ethernet and CC connections are not                           

compatible. 

Note: If the gateway is powered using a generator or a power source that may induce                               

surges or spikes, a voltage stabilizer may be installed in the power input of the gateway.  

DC power connector

● The cable gland allows for an external cable diameter of 4 mm to 8 mm.

Note: Powering down the gateway takes some time. Therefore, even if the power is                           

disconnected, the gateway may still be active.  

10 

1.4 Enclosure mounting 

● The gateway enclosure comes with a mounting kit designed for various                   

configurations:

● Pole mounting by U-bolt

Gateway mounted on a pole.

● Wall mounting

Gateway mounted on a wall 

11 

● Metallic strapping mounting (tube, pipe, flue)

Gateway mounted on a pole 

The metallic mounting kit must be grounded for safety reasons. 

The antenna must also be mounted in place on the mounting kit 

Gateway antenna mounting

12 

The supplied antenna cable must be connected to the gateway enclosure, as shown in the 

image below: 

Connection of the antenna cable to the connector

Finally, the antenna cable must be strapped to the mounting kit to reduce accidental wear. 

Fixing of the antenna cable 

Note: Surge protection (for both Ethernet and power supply) is not provided with the gateway as  it is with data loggers. However, if this kind of protection is desired, external devices may be used  (58820200 for ethernet or 58820100 for antenna). Contact DGSI technical support for further  information.

13 

1.5 Internet communication 

A SIM card or a wired Ethernet network (with Internet access) can be used to connect the                                 

Gateway to the Internet, which is necessary for remote access and to communicate with a                             

monitoring data server. In the second case, the gateway and stored data can also be                             

managed on LAN environment (local network without Internet access). 

1.5.1 SIM Card 

If you wish to use the gateway with a GPRS/3G connection, you must insert the SIM card. 

To insert a SIM card: 

● Open the gateway enclosure with a flat-head screwdriver.

● Push the SIM extraction button with a small screwdriver or the point of a pen.

● Place the SIM card in the tray, with the contacts facing out.

● Place the tray back into the gateway.

SIM card slot. Extraction button indicated.

14 

1.5.2 Ethernet connection 

If you wish to connect the gateway to the Internet through an Ethernet cable, use the PoE                                 

injector.  

The cabling between the gateway and the PoE injector is the same used for feeding the                               

device (see point 1.3.1). To connect to a LAN network, you must connect a direct Ethernet                               

cable from the “DATA IN” PoE injector port to the Local network (switch). 

Note: The Ethernet cable should be connected before plugging in the PoE injector to                           

230VAC. Once the gateway is initialized, the Ethernet connection should be established in                         

order to avoid problems with default Internet access configuration. 

PoE. The left port (Data & Power Out) is for the power cable and the right port 

(Data-In) is for data transmission to the network. 

15 

2. CONFIGURATION

Configuration  is carried out with a desktop or laptop computer. 

The GTecLink  Gateway has a  web interface for all configuration and data retrieval tasks. The interface is accessible through any of the gateway’s network connections,

which will be explained in this section. 

2.1 Gateway connection 

Factory  configuration  has  been  deployed  to  communicate  outside  (Internet)  without  the 

need for any configuration. When connecting any two interfaces (3G/GPRS or Ethernet)

and  booting  the  gateway,  it  will  automatically  be  configured  to  connect  via  the  LAN 

network using DHCP settings, and if not available (no link to the network) it will switch to

3G/GPRS using the installed SIM card with default APN settings. 

In  any case, a wired network limited by security policies or lack of an Internet connection, 

will deny any internet connection. In this case local management interface access will be

required. This makes configuration of the device possible in a local environment. 

2.1.1 Local management interface (USB) 

In order to connect to the gateway on-site without depending on an external network, you

may  use  the  local administration interface. This interface provides all the features of web 

administration, including network configuration and access to GTecLink data. 

In order to use the local administration interface, you must: ● Open the gateway box with a flat-head screwdriver.

● Connect the supplied USB Ethernet adapter to the USB port on the front plate of                           

the gateway.

● Connect an Ethernet cable from the gateway’s USB adapter to your laptop                     

computer.

● Ensure that your computer is configured to acquire an IP address automatically                     

using DHCP.

● Open the following website on your Internet browser:

o http://169.254.0.1

o user: admin

o password: VMjG6z

16 

o An SSL certification error will appear. This is normal as this gateway uses a                         

self-signed certificate for SSL authentication. Add a security exception for                 

this certificate to allow the connection. Check your browser’s               

documentation for instructions on how to do this.

o Introduce the provided user and password.

Notes: 

Should you experience difficulty connecting, check these steps: 

● Use the USB-to-Ethernet adapter provided by WorldSensing (other adapters may                 

not work depending on the driver).

● If the computer used to configure the gateway does not have an Ethernet port, use                           

two USB-to-Ethernet adapters of the same model.

● Check if the USB-to-Ethernet adapter associated network Interface has received a                   

valid IP address (169.254.XXX.YYY with Subnet Mask 255.255.0.0). If not, manually                   

set a valid IP address on the same network range. E.g.: IP address: 169.254.0.3 and                           

Subnet Mask 255.255.255.0. Default gateway and DNS are not required as it is a                         

direct communication without Internet access.

● Disable any other network interfaces enabled on the computer (Wi-Fi, secondary

Ethernet Port, etc.).

The local administration interface should be used for: 

● Initial configuration of a new gateway.

● On-site data retrieval and configuration of a gateway without an internet

connection.

● In the case of a forgotten remote access password, the local administration

interface has a fixed password, which cannot be changed.

17 

2.1.2 Fast connection (3G/GPRS or Ethernet) 

Due to factory configuration, the gateway launches a process during booting to connect to                           

the Internet automatically through these steps: 

1) When booting, the gateway automatically detects if there is Ethernet connection to                     

a LAN network (link). In this case, the gateway requests network configuration from                       

the DHCP server and attempts to go outside with the received settings.

2) If the network link isn’t detected, the gateway attempts to go outside via SIM Card.

3) If connection isn’t possible, the gateway will work in standalone mode without an                       

Internet connection.

This default setup may not be successful. In this case, USB interface connection is required                             

for manual configuration. Unsuccessful default setup may be the result of the following: 

● The Ethernet cable has been connected after the gateway has been turned on. The

test to check if there is LAN connection is done at the very beginning when

the device is turned on. All Ethernet cabling must be wired before turning the

Gateway on.

● The  SIM  card  does  not  have  default  configuration,  so  3G/GPRS  settings  must 

be manually configured.

● The network has no Internet access (only Ethernet connections).

● The  SIM  card  has  not  been  registered,  does  not  have  DATA,  or  works  in  a

non-compatible frequency with the internal 3G/GPRS modem of the gateway.

● It is a 4G ONLY SIM card. 4G is not supported by GTecLink Gateway.

Once  connected  to  the  Internet,  the  connection  to  the  gateway  is  carried  out  by 

Loadsensing servers. The gateways connected to the Internet create a secured tunnel to

the  device  for  remote  management  and  maintenance. For this purpose, data traffic must 

be enabled through SSH port: TCP 22. In this case, access the Gateway through this URL: 

https://gteclink.wocs3.com/{GATEWAY_ID}

The ‘admin’ user has admin properties and the password is that provided by WorldSensing

in  the  device  datasheet.  Unlike  the  local  administration  password  (USB-Ethernet 

connection), this password may be modified in the Setup menu. A View_Only user may also

be enabled. 

Once  the  IP address is known (in the case of a fixed IP address), the gateway can also be 

accessed through this URL: 

18 

https://{GATEWAY_IP_ADDRESS} 

In this case, the access credentials are the same. This method may always be used, but it is                                   

meant for cases in which the network does not provide internet access to the gateway or                               

the TCP 22 port is closed. 

2.2 Setup menu 

2.2.1 Networks 

The first page of the gateway’s Web Configuration Interface displays the network ID and 

three different menus: networks, status and configuration. If the network ID has been 

changed for a specific gateway (the same serial number), several networks will appear in 

this tab under different IDs. A personalized name may be given to the network under the 

feature “Name”. Finally, the number of both active and inactive data loggers is displayed in 

green or red according to their status (active/inactive).  

When entering the network, several node features can be viewed: status, model, serial 

number. Serial and node ID coincide by default, but ID may be changed. On this page you 

may: 

● Download the compacted DAT/CSV files with the data collected by the network

(raw data or engineering units). (See section 2.6 for further information.)

● View the signal coverage test map in which test results are geographically plotted.

● See basic data logger information: status, ID, serial number, model.

● Access all gateway configuration interface menus.

● Visualize data sent from data loggers. Additionally, messages lost and received by

the gateway are counted (under the Status tab). The green number indicates

messages received, the red number corresponds to lost radio messages and the

orange number to messages lost due to gateway power interruption.

● Change the sampling rate of the data loggers remotely.**This feature requires gateway software version 1.7 or higher and data logger 

firmware version 2.15 or higher.  Please contact DGSI  for further information on firmware 

and  software versions.   

19 

Home page of the gateway. This is the first page displayed in the Web Configuration 

Interface. 

Summary of data logger status and history of received/lost messages  

Changing sampling rate remotely: 

20 

● The sampling rate can be changed remotely for one or several data loggers.

It is important to set the definitive sampling rate from the gateway interface for all the 

nodes. This procedure confirms that communication is OK in both directions (gateway to 

node and vice versa) and decreases the compacted files delay, which is one hour by 

default. Any new node should also be configured in this way (otherwise the compacted file 

delay would once again be set to one hour). 

● When the check box to the left of the corresponding line is selected and “Change

sampling rate” is applied, the new sampling rate option can be selected from a

pop-up menu.

● Once the process is completed and changes have been saved, a clock icon with the

value of the new sampling rate next to it will appear in the ID column of the node.

● Should it appear with an orange label, this means that the change has not yet been

applied.

● If the orange label disappears, this means that the change is effective.

● While the orange label is active, the changes may be cancelled.

● If you try to introduce an unsuitable sampling rate according to the slot times

required for the network, a message will appear asking you to accept that he/she

understands the risk.

By changing the sampling rate remotely, you allow the gateway to access information 

about when it is going to receive data from the sensors. The advantage of letting the 

gateway access this information is that the compacted files (including data from the entire 

network) can be closed and uploaded to the FTP as soon as the sampling of the entire 

network is completed.  

More information at Data retrieval and monitoring 

21 

2.2.2 Status 

In the status tab, you can view the gateway status and logs. 

2.2.2.1 Gateway status  

In the gateway status menu, the following information is displayed: 

● General information

o Gateway serial number

▪ Displays the hardware’s serial number. This value cannot be

changed.

o Gateway model

▪ Displays the hardware model.

o Firmware version

▪ Displays the current firmware version. The gateway’s firmware can

be updated remotely by Worldsensing Technical Support as long as

the gateway has an Internet connection and remote access is

working (see below). Version 1.14 allows local upgrading by file.

o Date

▪ Displays the current date, according to the gateway’s internal clock,

always in UTC.

o Uptime in minutes

▪ Displays the time in minutes since the gateway was connected or

rebooted.

o Input voltage

▪ Displays the voltage that powers the gateway. This reading has a

precision of +/- 0.35 V.

o Voltage history

▪ Links to a CSV file that includes the historical records of voltage,

every 15 minutes. This is not divided by months.

● Application status

o Network ID

▪ Displays the current sensor radio network ID.

o Internet connection (ping)

▪ Indicates whether or not the gateway is able to connect to the

Loadsensing server in order to check for connection.

22 

▪ Review the “Internet configuration” section for more information on

this check.

o Status reporting

▪ Indicates whether or not the gateway is able to send status reports

to DGSI.

▪ These reports are sent via HTTP (port 80) to gteclink.wocs3.com and

provide information on the gateway’s status to DGSI Technical

Support.

o Remote access

▪ Indicates whether or not the gateway is able to open a remote

access connection to the GTecLink server.

▪ This service uses a TCP connection to gteclink.wocs3.com, on port

22.

▪ The remote access mechanism is used to:

● Provide DGSI Remote Access Service, which allows remote

access to the Web Configuration Interface.

● Provide remote access capability to DGSI Technical Support,

which allows for remote support and remote updates of

deployed gateways.

● Network information

Displays the parameters of the currently active network configuration. 

o Selected interface

▪ Displays Internet connection selected manually or by default.

o Ethernet status, IP and Netmask

▪ Displays the status of the Ethernet interface (up/down) and the

current address if there is one.

o GPRS/3G status and IP

▪ Displays the status of the GPRS/3G interface (up/down) and the

current address if there is one.

o Default gateway and DNS servers

▪

● GPRS Modem Info (This information is provided by the carrier, it may not be shown)

o Status

▪ Indicates whether or not the current GPRS modem status is correct.

o IMSI

▪ Identification number of a given user in a cellular network.

o Operator

23 

▪ Telecommunication operator used for the GPRS modem.

o Roaming

▪ Indicates whether or not roaming mode is activated.

o Mode

▪ Indicates the technology (algorithm) used in telecommunications to

define the channels and bandwidth to be used (CDMA or WCDMA).

o Signal

▪ Indicates the signal coverage of the telecommunications operator in

percentages.

o LAC

▪ Location area code, an identification number.

o CI

▪ Cell identity.

Gateway status page 

24 

2.2.2.2 Logs 

On the “Logs” page, status actions are reported and you can select the logs to be displayed 

by date. 

This tab provides information about system actions, (node erase, time update, geographical                       

area change…) node irregularities (data logger out of date, etc.), unsuccessful actions, (FTP                         

data upload failure, etc.) and regular actions carried out manually or automatically by the                           

device (file overwriting on gateway memory, new data file creation, etc.). 

Records are organized by two types: 

● INFO (event information)

● ALERT (events that should not occur, normally due to a configuration error)

LOG messages 

25 

2.2.3 Configuration 

The “Configuration” tab displays different gateway configuration options for three different                     

areas: data retrieval, communication interfaces, and maintenance tasks. 

2.2.3.1 General 

The gateway has an internal clock configured in UTC used to register all sensor readings,                             

events and possible incidents. 

However, you can introduce a different time zone in the gateway software interface. By 

doing so, you will be able to retrieve and visualize the data in local time, thus simplifying 

monitoring tasks. 

We recommended setting the time zone when connecting to the gateway for the first time 

in order to avoid any timestamp issues with CSV file generation. 

2.2.3.2 FTP client 

In the configuration tab, you can enable an FTP client to push data from the gateway                               

automatically to the server every three minutes at most (for node CSV files only, depending                             

on the sampling rate set from the gateway; compacted CSV files are pushed every 15                             

minutes). The most common use of this feature is automatically uploading data to a                           

monitoring server to create and display reading charts. 

These are the configurable features of the FTP client: 

HOSTNAME: IP or URL of the FTP server where data are going to be uploaded 

PORT NUMBER:TCP PORT. 21 by default. It can be changed according to FTP server                         

configuration. 

USERNAME & PASSWORD: User and password for login to the FTP server. An anonymous                           

user is also available. (“Use anonymous FTP” must be checked to use an anonymous user,                             

leaving User and Password in blank.) 

PROTOCOL: FTP protocol to use. GTecLink Gateway supports 3 different types: 

● FTP: Standard FTP server, without data encryption of communication. We do not                     

recommended sending data through the Internet, except for controlled LAN                 

environment servers or VPN connected networks.

● FTPS: This option allows configuration of data upload to a secure FTP server. It                         

requires an authentication certificate issued by a Certification Authority (CA) such                   

as Thawte, Verisign, etc. All communication is encrypted using SSH protocol.

26 

● FTPS (ignoring self-signed certificates). This option allows configuration of the                 

connection to a secure FTP server with self-signed certificates not issued by a                       

Certification Authority. This option eliminates the display of invalid certificate                 

messages, which must be manually accepted, to allow automatic data upload. This                     

method has the same security level as the FTPS.

FTP MODE: This may be configured in passive or extended passive mode, depending on                           

server configuration. Should you have questions, contact the server administrator or IT                       

department. Most servers are configured in passive mode. 

OUTPUT: Select how node readings are to be uploaded to the FTP server. One file per                               

reading can be generated at the server (Create unique file at every upload) or a line for                                 

each new reading sent can be added to an existing file (Append to end of file). This second                                   

method dumps the whole file again in the case of errors (unable to read the file to be                                   

overwritten stored in the server, file writing error, file unavailable, etc.). 

TYPE OF FILE: In this area the files to be uploaded to the server are selected by clicking the                                     

appropriate checkbox. Checking a file type enables the Path to upload the file or data. You                               

can set a full path by typing ‘/’, or a relative path (associated with the login user) by typing                                     

‘./’ (most common configuration, as it saves the files in the folder assigned by the FTP                               

server). Files can also be stored in specific folders inside the relative path. For example,                             

Health files may be set at ./Health/, while customized files may be set in a different folder                                 

./Customized_readings. All paths must be set without commas.

The file to FTP Server upload process is as follows: 

● The gateway checks the last file or data uploaded to the server.

● It then uploads the latest data (Append to an existing file or creates a new file).

● Should an error occur in the previous step, the reading file is uploaded again, or the                             

full file from the beginning of the month (append mode) is uploaded.

When configuring the FTP client for the first time, the client should test server connection                             

by uploading a test file and deleting it once the test is done. If this procedure is completed                                   

successfully, the web interface will show a configuration OK message. 

A gateway with a stable connection using a SIM card uses about 150 MB per month for FTP                                   

data upload. 

27 

FTP client configuration tab

Check Data Visuali zation and Retrieval for more information. 

2.2.3.3 Compacted CSV 

This feature allows you to create a self-configured CSV file with the desired columns,                           

customized header names, column order, etc. The default number of columns is 600                         

but can be upgraded up to 1000 for bigger networks.  

Note: Changing from 600 to 1000 columns in a production environment modifies the                         

CSV file structure, which may corrupt data files if uploaded to the FTP server. We                             

recommended closing the existing CSV file on the server (disable FTP client on the                           

gateway and rename the current files on the FTP server) Then modify the column                           

28 

number (gateway reboot is required) and enable the FTP client again to start uploading                           

the new 1000 column CSV file once more. 

Once saved, a CSV file called “compacted-custom-readings-XXXX-current.dat” (XXXX               

being the network ID) is created. Every time a new compacted CSV file is created, the                               

old one is saved with a variation of the suffix “current” by “yyyy-mm-changeX”. This file                             

appears on the Networks main page, where the files to download are visible. 

View of the tool to create a self-configured CSV file of network data 

29 

2.2.3.4 ModBUS gateway (ModBUS TCP server) 

This feature gives access to the latest data received from GTecLink nodes stored in the

gateway,  using  ModBUS  TCP  protocol since GTecLink  Gateway acts as a ModBUS TCP 

server. It also provides several data such as Health files (Battery status, etc.). 

Once  configured,  the  gateway  stores  the  last  RAW  reading  received  from  each  sensor 

connected to a data logger on ModBUS memory records available by using this protocol

through port TCP:502. 

When configuring the ModBUS server, ([Configuration]>[ModBUS Gateway]), a UNIT ID must

be  associated with each node (data logger or wireless tiltmeter). The gateway stores data 

from each node in the records associated to each UNIT ID.  

The interface can also be configured to connect to this server (wired interface (Ethernet) or

all of them (Ethernet + GPRS/3G)) and the message TimeOut. This last parameter should be

associated to the sampling rate of the readings to avoid incorrect readings (data are stored

on ModBUS records until the message TimeOut. Then they are erased. If a reading is done

after  TimeOut,  and  no  new  data  have been received from data loggers, NULL data will be 

shown on ModBUS client.) 

Once  a  reading  is  received  and  stored  on  ModBus  records,  it  will  be  available  until  the 

defined message TimeOut. From then on, when attempting to read that record, an error

value will be returned by the ModBUS TCP Server. 

A  ModBUS  Records  annex  for  each  type  of  node  can  be  found  in  this document.

30 

View of the Modbus Configuration tab of the gateway 

31 

2.2.3.5 Internet 

In the configuration tab, you can also change Internet connection details. By default, these                           

are set on automatic mode.  

It is possible to select a custom NTP server (from a local network). A custom SMTP server                                 

can also be configured.  

The gateway is factory-configured to communicate with the Internet as fast as possible: by                           

connecting to the Ethernet using configuration provided by the DHCP server or, if Ethernet                           

connection (link) is not detected, by connecting to a 3G/GPRS network using the SIM card                             

with a default configuration (PIN number deactivated) and mobile network configuration                     

settings stored in the internal database of the device. 

Internet communication is available with this setup. However, this configuration is not the                         

best. Once the gateway Internet connection type has been selected, the deployed interface                         

should be selected to avoid future connection problems. 

For example, in the case of a gateway with default Internet configuration and an Ethernet                             

connected, the gateway discards the Ethernet connection and attempts to connect using                       

3G/GPRS interface should there be physical problems (broken or disconnected Ethernet                     

cable, data switch turned off, etc.) when attempting to reboot the device during                         

troubleshooting procedures. 

View of the Internet configuration tab of the gateway (default configuration). 

32 

● Network Watchdog

o The Network Watchdog is the mechanism that checks whether the Internet

connection is working properly.

o This mechanism checks the Internet connection every minute by sending a

ping request to gteclink.wocs3.com.

o If the gateway is unable to communicate with the server for 40 minutes, it

will assume there is a problem with the connection, and reboot

the gateway.

o The  Network  Watchdog  must  be  disabled if the gateway does not have an

Internet connection.

▪ If  the  Network  Watchdog  is  left  enabled  for  a  gateway  with  no

Internet connection, it will start a reboot cycle every 40 minutes.

This will lead to sensor data loss, as data entering during the reboot

cycle will not be stored.

o The Network Watchdog is enabled by default.

● Network connection

o Automatic (default)

▪ In  automatic  mode,  the  network  connection mode is automatically

configured upon gateway startup.

▪ It is the default configuration for a fast connection.

▪ If  a  connected  Ethernet  cable  is detected, an Ethernet connection

with DHCP will be used.

● An  Ethernet  cable 

is considered to be connected if there is some kind of

network equipment (for example a router or a switch) on

the other side of the cable. The PoE injector doesn’t

count.

▪ If  no  Ethernet  cable  connection  is  detected,  the  GPRS connection

will be launched with its configured parameters.

▪ Once the Internet connection method has been defined, we strongly

recommend modifying this setup to avoid connection in production

environments in case of reset, network failure, etc.

Manual configuration should be selected and accordingly

configured.

33 

o Manual Configuration.

Options for manual configuration

This setting overrides auto-detection and always launches a selected connection type. 

▪ GPRS/3G

● This adjustment discards automatic network detection and           

always launches a GPRS or 3G connection with the settings                 

configured in the [Configuration]>[GPRS/3G] area.

● Ethernet interface is deactivated, but can be used for               

feeding the device with PoE injector.

▪ Ethernet with DHCP

● This setting overrides auto-detection and always launches           

an Ethernet connection, receiving configuration       

automatically through DHCP. (Dynamic IP)

● This option is the easiest to configure for an Ethernet                 

interface but it may not be ideal for connecting directly to                   

the gateway as the IP address may vary. Usually DHCP                 

servers provide a specific IP address for a configured time.                 

After a reset or once this time has ended, the provided IP                     

address may vary, affecting any NAT or VPN Tunnel               

configuration. In this case, we recommend a static IP               

address.

▪ Ethernet with Static IP

● This setting overrides auto-detection and always launches           

an Ethernet connection.

34 

● In this mode, you need to manually set all parameters of                   

network configuration:

o IP address

o Netmask

o Default gateway

o DNS servers

● NTP server (to synchronize the gateway’s clock)

o By default, the NTP server must be accessible through the Internet. In                     

general, if the gateway is connected to the Internet, it is common to use an                           

NTP server.

o Even in situations in which the gateway is not connected to the Internet, it                         

is still common have a custom NTP server, which may be in a local server.

o We recommend using the same NTP server for the gateway as that used for                         

the data monitoring server (if applicable).

35 

● SMTP Server (e-mail sending server configuration)

o The default option is to use an SMTP server through the Internet. Should                       

the gateway not be connected to the Internet, this option would not be                       

valid.

A custom SMTP server can be defined if the gateway is not connected to the Internet or if                                   

you choose to use a default mail account. However, monitoring e-mails are still required. A                             

custom SMTP server can be placed in a local server. 

In this case, the CUSTOM option must be selected and the e-mail account to be used must                                 

be configured: 

IP address and TCP port of the server, e-mail account (the one that sends the e-mails),                               

TLS/SSL encryption method (if applicable) and authentication (user, password). 

SMTP configuration settings for a G-MAIL account

36 

2.2.3.6 GPRS/3G 

The GPRS/3G configuration tab contains some configuration parameters specific to this                     

type of connection. 

Settings for the configuration of the GPRS/3G connection. 

This configuration is applied whenever a GPRS/3G connection is used, regardless of                       

whether it was the result of an automatic or manual configuration in the Internet tab. 

● PIN setting

o Off (default)

▪ In this mode, the gateway will not attempt to unlock the SIM card.

▪ If the SIM card is protected by a PIN code, the GPRS/3G connection                       

will fail.

o On

▪ This setting allows you to enter the PIN code for a PIN-locked SIM                       

card.

▪ Be careful not to boot the gateway with a PIN-protected SIM card                     

with the wrong PIN set here. The gateway will automatically attempt                   

to unlock the SIM card, and exhaust the three possible attempts.

▪ There is no way to enter the PUK code in the gateway. If your card                           

gets PUK-locked, you will have to unlock it using a mobile terminal.

37 

● APN settings

o APN Auto selection (default)

▪ Every  mobile  operator  must  set  a  specific  configuration  for

connection to its network.

▪ The  GTecLink  Gateway  features  a  database  of  the 

correct configurations for hundreds of operators around the

world. This setting will attempt to configure the connection

automatically based on the SIM card that is inserted.

▪ This  setting  may fail if your operator is not in the database or your

configuration is non-standard.

o Manual APN configuration

▪ This  setting  allows  manual  input  of  the  mobile  operator

configuration values.

▪ Use  this  setting  if  auto-selection  didn’t  work,  or  if  specific,

non-standard configuration values are required.

38 

2.2.3.7 Radio 

This  page  allows  you  to  configure  the parameters for the Wireless Sensor Radio Network. 

There are three different gateway models, according to the geographical areas in which

they’ll  be  placed.  In  addition,  depending  on  the  country’s  regulations,  the  radio 

configuration will be set specifically.  

Note  that  for  some  countries,  an  advanced  menu  may  be  displayed.  This  refers  to  the 

possibility of choosing different channels through which data can be sent in each

spreading factor. This is useful for projects with many (hundreds) data loggers sampling at

a high rate. Some data loggers would be set at one group (and also one gateway) and some

other nodes at a different frequency group (as well as a second gateway configured to this

other group), thus preventing potential collisions.  

Note: If you change the default configuration under advanced options, these settings must 

also  be  changed in the data logger or wireless sensor configuration. The network type, ID 

and  password  must   be   the   same   at   both   gateway   and   nodes.   Otherwise,   no  radio  

communication will be available, and data will not be dumped into the gateway. 

In  order  for  the  GTecLink  data  loggers  to  connect  to  this  gateway  and  send  data, 

both the  gateway and all participating data loggers must be configured with the same

parameters. 

● Country and frequency (Network type)

o Depends on the country and gateway type.

o Depending on the network model, different channel groups, channels or                 

specific spreading factors may be chosen.

o It must match the exact configuration of the node (network model, channel                     

group, and SF, if applicable).

o Depending on the network model, channel groups, channel and specific SFs                   

may be selected.

o It must match the exact configuration of the node (network model, channel                     

group, and SF, if applicable).

● Network ID

o A numeric identifier of the wireless sensor network.

o Set by default to the serial number of the gateway.

o It should only be changed when a gateway is replaced and you do not wish                           

to reconfigure all data loggers in the network.

39 

● Network Password

o This password is used to encrypt all data in transit on the Wireless Sensor                         

Network.

o The default factory password is printed on the Gateway Information Sheet.

o Once the password has been changed, there is no way to recover it. The                         

password will have to be changed to a new one in the gateway as well as in                               

all data loggers in the network.

Radio configuration tab, inside the gateway interface 

Three different gateway models are available. Each includes different network models valid                       

for different countries, since radio regulations are different. For more information check                       

RADIO. 

40 

2.2.3.8 Remote Access 

This page allows you to change the password for remote access to the Web Configuration

Interface.

The  new,  or  the  initially  provided,  password  is  required  to  access  the  gateway  either 

through the public network interface or through the Loadsensing Remote Access Service. 

Be  careful  not  to  set  weak  passwords.  Doing  so  makes  your  gateway  accessible  from 

anywhere on the public network or the Internet if you have an Internet connection. 

In  order  to  change  the  password  from  the  public  interface  or  from  the  Remote  Access 

Service, the previous password must be entered. This is not required if you are connected

through the local administration interface. 

The  default  factory  password  is  printed  on  the  Gateway  Information  Sheet.  Once  it  has 

been changed, there is no way to recover it. 

In  case  of  a  lost  or  forgotten  remote  access  password,  you  must  use  the  Local 

Administration Interface to change it to a known one (section 2.1.1).  

View only password 

This  view  is  designed  to  provide  access  to  users  that  are  only  allowed  to  see  the  data 

collected in the network and are not allowed to change any of the configuration

parameters. The “view only” user has to be defined by the administrator.  

Remote tunnel 

Gateway  firmware  version  v.1.13  or  higher  allows  deactivating  the  VPN  tunnel  between 

DGSI servers and the gateway, which uses port TCP 22. 

Deactivating this tunnel means: 

● Access  is  not  available  from  https://gteclink.wocs3.com.  Connection  is  only

available through the local IP address.

● There  is  no  possibility  of  remote  check  or  support  from  the DGSI  technical

team.

● There is only remote access from Internet when the SIM card has a Public IP.

● For  3G/GPRS  interfaces,  the  Modem  firewall  will  also  be  deactivated. 

Therefore, there may be huge data usage as the gateway may be exposed to

external attacks.(Firewall rules discard all incoming requests from 3G/GPRS

interface except those coming from the VPN tunnel.)

41 

Remote Access tab, inside the gateway interface 

42 

2.2.3.9 Upload firmware 

This  option  allows  you  to  upgrade  the  gateway  locally  by  uploading  firmware  versions  provided by the DGSI support department when internet access is not available. 

This feature is available in version 1.14 or higher. For lower version gateways, this feature is only available after upgrading remotely to version 1.14. 

This  feature  also  allows  you  to  add  new  radios  to  the gateway or radios existing in other  gateway models.  

Click the “Select file” button to select a file stored in your computer and then click the                                 “Upload & install new firmware” button to start the upgrade. The gateway will check the                             uploaded file and display an error message if the file does not fit with a valid radio or                                   firmware version (in the case of corrupted files or another file type selected by mistake). 

43 

2.2.3.10 Delete All 

In order to delete all the data contained in the gateway (but not the entire configuration),                               

you have to access the “Delete all data” tab and follow the instructions. 

This option also erases the FTP client configuration, so this must be reviewed after the data                               

have been erased. 

This option also erases all the nodes and the networks. As the nodes communicate with the                               

gateway again (Radio configuration isn’t erased), the configured network and the nodes                       

appear once more and generate new data files. 

If a node or network needs to be erased (if created by mistake), check API CALLS. 

Delete all tab, inside the gateway interface 

44 

2.2.3.11 Reboot 

After changing gateway configuration parameters, the gateway must be rebooted to apply                       

the changes. The gateway will inform you about this requirement. 

Reboot tab, inside the gateway interface 

Occasionally, the gateway may undergo a WEB connection. A call will first reboot the device

and then it will attempt to connect. 

https://gteclink.wocs3.com/{GW_ID}/reboot.html

Resetting  the  Gateway  may take several minutes depending on the Firmware version and 

device configuration. 

45 

3. DATA VISUALIZATION AND RETRIEVAL

This  paragraph  explains  how  data  can  be  monitored,  retrieved  and  received  from  the 

gateway.

The  information generated by sensors connected to data loggers feed reading files in real 

time in the node. This information is stored when the sensor is activated and readings are

sent to the data logger. This happens according to the configured sampling rate. 

Depending  on  the  radio  configuration  of  the  node  network,  data  loggers  and  wireless 

sensors send the data to the gateway at the stipulated time intervals for each one (slot

time). This means data are not available in real time but are delayed. The maximum delay to

real-time  data  is  this  period,  which  is  called  SLOT  TIME.  (See  RADIO  section  for  more 

information.)

3.1 Data recovery directly from the NODE 

Data  are  stored  in  data  loggers  in  comma  separated  value  files  (CSV).  These  files  are 

available to download using the Android GTecLink application. 

For this purpose, an Android device must be connected to the Mini USB port node through

a USB on the go (OTG) cable. When the GTecLink application loads, data can be

downloaded by clicking on Download icon at [SENSORS DATA] tab. A Start and End date

must be set, and data from that period will be downloaded. The android device will allow these

CSV files to  be opened with downloaded applications such as e-mail or cloud apps. Files

are also stored on the device memory, in the GTecLink folder. 

GTecLink application: Readings dump to the Android device 

46 

3.2 Data retrieval and visualization from the gateway 

Data (readings and Health information) are sent to the gateway from the nodes, where they                             

can be either visualized or retrieved. The device has an 8 GB internal memory, which allows                               

network data to be stored for years. Depending on the configured sampling rate and the                             

network size, it can store data for up to 10 years. 

3.2.1 Engineering units conversion 

It is possible to visualize the data received from each node, both raw and transformed into                               

engineering units. This information is displayed on the Web interface. 

In the second case, the gateway transforms the received RAW data into engineering units.                           

For this purpose, the variables and parameters required for each sensor must be                         

configured. Depending on the type of sensor, these parameters may vary. The gateway                         

always offers default configuration (showing the associated polynomial function), fields to                     

add variable values, such as units, and maximum accepted readings. 

Engineering units for each sensor must be activated and configured in the “Networks” tab                           

by selecting the node of the network and clicking on the gear icon beside the last readings                                 

(Last readings and time series Graphs tab). This option enables the menu where the                           

settings associated to the sensor can be edited. 

The polynomial function is displayed when selecting measure from the menu. The unit to                           

be shown is also indicated. 

In the “Last readings” tab, a gear icon appears on the right to edit the formula of the 

sensor.

47 

Menu to edit the formula for transforming raw sensor data into engineering units.  

48 

3.2.2 Data visualization from the gateway 

The gateway displays the latest sensor readings in both text and graph formats. To access 

these displays, you must click on the “Networks” tab and select the sensor node. 

Readings are displayed in the paragraph [Last readings and Time series Graphs] where all                           

the RAW readings are shown, as well as the readings converted into engineering units, if                             

this function has been configured. 

This paragraph shows the last reading of each connected sensor. If the graph icon of the                               

header is selected, a chart with the data associated to the selected column will be shown.                               

The chart displays a maximum of 400 readings on a timeline. Sensors connected to that                             

node can be shown or hidden, and the timeline can be modified. 

Note: It is important to configure the correct time zone in [CONFIGURATION]>[GENERAL] so                         

that the chart will be shown in real time. If the correct time zone is not configured, readings                                   

will be shown in UTC, the default configuration. 

Circled in red, the icon to display the charts of each of the sensors. 

49 

3.2.3 Data retrieval from the gateway 

Data received are stored in CSV files, which can be downloaded from the device web                             

interface. 

Each node sends the generated data (readings and Health information) through the radio                         

network connection. This information is appended to the existing files or the gateway                         

generates new files to store this information if the appropriate file does not exist. 

Files are generated with the name XXXXX-current and in CSV format (for node readings                           

files) or DAT format (for Gateway generated files). At the end of the month, the file is closed                                   

and renamed as XXXXX-yyyy-mm (where yyyy represents the current year and mm the                         

current month) and a new empty current file is generated. 

In both cases (node and gateway files), the current and previous month files are displayed                             

and all existing older files are available in ZIP compressed format. This means historical                           

information can be recovered (one file per month) unlike with the node, where a start and                               

end date are required to generate and download the file. 

These are the different type of files, depending on the information they store: 

NODE FILES: These are the files generated with the information received from the node.                           

One file is generated per node connected to the network. They are available in the                             

“Networks” tab by clicking on the network, and then the node. These files are updated                             

every time a node communicates with the gateway, so the most immediate information                         

available on the gateway is stored here. 

[Node_ID]-health-current.csv: Contains information related to the node. Battery status (in                   

volts), Node temperature (in º C degrees) and UpTime (time since last reset of the node, in                                 

seconds) 

[Node_ID]-readings-current.csv: Contains the readings in RAW of each sensor, and if                     

configured, also in engineering units. 

50 

GATEWAY FILES (COMPACTED): The gateway periodically generates compacted files with                   

the information received by all the nodes. This information is stored in the same way node                               

information is stored. However, unlike with node information, it waits for a period of time                             

(slot time) to retrieve new information available from each node and append it. These files                             

are available in the “Networks” tab by clicking the radio. These are the files: 

● compacted-readings-[Network_ID]-current.dat: Contains all the readings of all the             

nodes connected to the network in RAW format.

● compacted-eng-[Network_ID]-current.dat: The same as above, but in this case               

displays the engineering units.

● compacted-custom-readings-[Network_ID]-current.dat: Displays data from the       

selected sensors in RAW or engineering units. Previous configuration of this file is                       

required. It can be configured in [Configuration]>[Compacted CSV].

Data displayed in compacted files are delayed one hour with respect to the existing node                             

files. The reason for this delay is to prevent conflicts between recently received data and                             

old data. When a compacted file is being generated, it is possible that not all of the                                 

information has arrived to the gateway yet, which could generate empty slots in                         

compacted files.  

This one hour delay is a default parameter. Changing the sampling rate from the gateway                             

instead of the node may decrease this delay up to the Slot time, so the compacted                               

information will be that received in the previous slot time. 

Bear in mind that current files are designed to support up to 1000 columns and 600 by 

default. (See chapter 2.2.3.3 Compacted CSV.)  

51 

3.2.4 Sending files by FTP 

The gateway has an internal FTP client that allows connecting to a FTP server to send the                                 

files stored on the gateway. (To see the configuration in [CONFIGURATION]>[FTP client]                       

check paragraph 2.2.3.2.) 

FTP is commonly used to send reading information to Data Monitoring Servers, as well as to                               

store them in a data backup system. It can be deployed in both LAN environments                             

(Ethernet without Internet access) as well as WAN environments (using any of the internet                           

interfaces, 3G/GPRS or Ethernet). 

The FTP Server sends information (generating new files or appending data to an existing                           

file) every three minutes in version 1.14 or higher, and every 15 minutes in previous                             

versions. This amount of time may not be configured. 

Due to the completion of this automatic task every three minutes, the information stored                           

on the FTP Server may be delayed with regard to the reading carried out in real time by the                                     

sensor Slot time (time to send information to the server) + three minutes (FTP task period). 

If sampling rate has not been modified from the gateway for all the connected nodes, the                               

delay will be 1 hour and 3 minutes. 

If the information to be sent to the FTP server is a compacted file, as these files already                                   

have a 1 hour delay with respect to the node times, existing data in the FTP server will have                                     

a maximum delay of 1 hour (generation of compacted files) + Slot time (sending information                             

from the nodes to the gateway) + 3 minutes (FTP process). 

52 

3.2.5 Last messages (API format) 

Alternatively, the last messages received by the gateway are displayed in API format. This 

information is usually checked for troubleshooting purposes. These messages can be 

viewed under the tab “Last Messages” of the software interface for each node. 

These messages may be received: 

● CoverageTestV1 (Coverage test carried out usually during the installation of the                   

node)

● xxxReadingsVx (Last reading message received by the gateway from a specific                   

node)

● spstAggCfgV1 (Configuration message with all the radio settings of the node)

● healthV2 (Last Health message received by the gateway)

View of last messages received by the gateway, displayed in API format. 

53 

4. REST API calls

The Gateway supports incoming REST API calls to receive and send information in real time.                             

These calls can be made with applications such as Advanced REST client by Google Chrome                             

or Postman (both available at Google Chrome Web Store) or they can be implemented in a                               

third party application to carry out planned tasks. 

They are organized in three different types: Inventory (related to the radio network status                           

and its components, gateway and nodes), Data (information received by the gateway                       

related to the latest readings) and Monitoring (Receives data monitoring of network                       

elements, such as lost messages, node uptime, coverage test, etc.). 

At the same time, these calls can carry out different actions: GET (shows information                           

required depending on the API call) or POST (valid only at Inventory, allows data creation,                             

such as setting).  

This is the list of API calls organized by type: 

INVENTORY  

TYPE  API CALL  Comments 

GET  /api/v1/inventory/networks  Receives a list of the existing networks. 

GET  /api/v1/inventory/networks/{networkID} Receives a list of the networks and nodes 

existing on the gateway. 

GET  /api/v1/inventory/nodes/{NodeID}  Receives node information. 

Table 1: API Calls (Inventory) 

54 

DATA 

TYPE  API CALL  Comments 

GET  /api/v1/data/nodes/{nodeID} Receives the last message from the 

selected node. 

GET  /api/v1/data/networks/{networkID} Receives the last message from all the 

nodes of the selected network. 

Table 2: API Calls (Data)

MONITORING 

TYPE  API CALL  Comments 

GET  /api/v1/monitoring/nodes/{nodeID} Receives monitoring information from a 

specific node. 

GET  /api/v1/monitoring/networks/{networkID} Receives monitoring information from all 

the nodes connected to a network. 

GET  /api/v1/signaltest/nodes/{nodeID} Receives the test coverage information 

from a specific node. 

POST  /api/v1/signaltest/nodes/{ID}/token/{Token} Finishes test, sets GPS location and gets 

results. 

Table 3: API Calls (Monitoring) 

55 

Example of an API CALL using "Chrome advanced REST client" to receive information about                           

the Radio networks for GW 13340. 

Example of a REST API call from “Chrome REST API Client”

More  details  and  information  about REST API calls can be found in the "Data Server REST 

public API v1.pdf" document in the GTecLink Knowledge Base. 

56 

5. RADIO

5.1 GTecLink radio system introduction

GTecLink  devices  use  a  long-range  and  low-power-consumption  radio  system  called 

LoRa. This is an IoT-oriented, long-range network system. 

This network uses star topology to connect all the nodes in the network (data loggers and

wireless  sensors)  directly  to  the  gateway.  The  gateway  acts as an interface between the 

radio network and the Internet network. 

Radio  communication  is  bidirectional.  It  allows  node-to-gateway  traffic  (sensor readings, 

coverage tests, etc.) and gateway-to-node communication (sampling rate change, etc.). 

It  works  over  license-free radio frequency bands, but always in accordance with the local 

regulations of each country. Therefore, both the gateway and nodes have different types of

networks to configure. Some networks are valid for more than one country. 

Due  to  these  regulations,  the  GTecLink  radio  system  allows  configuring  some  LoRa 

parameters on each network type. These parameters limits may vary between different

radio types: 

Spreading factor (SF) 

LoRa  networks  send  data  modulated as pulses, called chips. Spreading factor defines the 

relationship between the transmission power and transfer rate of these chips. 

Higher  SFs  provide  more  reliable  data  transmission,  thus  allowing  for  longer  distances 

between nodes and the gateway and better immunity against interferences. Lower SFs

provide faster data transmission. This means that a data logger with a lower SF needs less

time to send the same data and more data loggers may share the same radio space, since

using a higher SF implies repeating data sending to ensure it arrives to the node.  

GTecLink devices allow configuring a parameter called Maximum SF, which defines the

highest SF allowed to transmit data for a node. This parameter is defined by regulations. 

LoRa  networks have six different SFs (SF7-SF12). SF 12 is usually discarded as it does not 

guarantee reliable communication and data loss may occur. Moreover, some regulations

limit usage to the lowest SF (SF7-SF9). We recommend using the lowest SF. 

57 

Sampling rate (SR) 

This is not a network parameter in itself. Rather, it is just the sampling rate configured for                                 

sensors connected to a node (how often a reading is taken). Nevertheless, this parameter,                           

together with the number of nodes connected to the network, defines the slot time.  

Loadsensing equipment allows a sampling rate of 30 s, 1 min, 5 min, 15 min, 30 min, 1 h, 2 h,                                         

4 h, 6 h, 12 h, and 24 h. 

Slot Time 

This parameter shows the time period that all nodes share to communicate with the                           

gateway. This parameter cannot be configured; it is automatically defined depending on                       

the Sampling Rate and number of nodes in the network. (See paragraph 5.3 for more                             

information.) 

Adaptive data rate (ADR) 

ADR is the mechanism used by LoRa networks to allow the nodes to automatically                           

negotiate the lowest SF possible with the gateway. If this parameter is disabled,                         

communication will be carried out using the highest configured SF (according to the                         

maximum SF configured parameter at the node). 

Channels and groups (frequencies) 

Regulations in each country indicate which channels (in MHz), and which bandwidths per                         

channel (in KHz) are allowed for data transmission (for both upload and download). Some                           

regulations allow only a fixed number of channels while others allow selecting different                         

channel groups. 

Using different channel groups allows configuration of different networks in the same area                         

(different nodes connected to different gateways), thus preventing data collision. Node                     

networks will be separated between them in different frequencies. 

Most regulations share some predefined fixed channels for upload and download. In some                         

cases, such as the Malaysian network (923M), there are two channel groups to select. In                             

other cases, there are different channel groups for upload and download, such the as                           

Australian network (923A). 

58 

Federal Communications Commission (FCC) regulations allow configuration of eight                 

different groups of eight different 125 KHz bandwidth channels for upload and a unique                           

channel group of eight 500 KHz channels for download. 

Transmission Power (Tx Pw) 

This allows adjusting the transmission power in dB. Maximum Tx Pw is defined by                           

regulations in each country. 

Tx Pw is usually 14 dB or 20 dB, depending on these regulations. 

ETSI limit duty cycle 

This is relevant only in Europe. The European Telecommunications Standards Institute                     

(ETSI) defines a time limit of one hour in which a radio device may transmit in a specific                                   

frequency. Some exceptional cases (high sampling rates and high SF) may cause the node                           

to surpass this time period. In such cases, the node will stop transmitting until an hour has                                 

passed. This option may be deactivated for testing purposes or to be used in locations                             

where this regulation does not apply (e.g. inside a mine). 

Region and country (network type) 

Each country or region defines parameters and values to comply with regulations. These                         

values are defined in Loadsensing equipment as a selectable network type. This network                         

type must be selected in compliance with the regulations of the region where the gateway                             

and nodes are installed. A different gateway model with several radio network types exists                           

for each geographical area. (See paragraph 5.3.) The gateway and nodes must be                         

configured with the same settings in order to establish radio communication. 

Due to different country/region regulations, some specific parameters may be configured                     

in advanced settings. 

ID and password. 

These values are used to identify a radio network and to protect (encrypt) the data in                               

transit. A strong password will prevent a malicious attacker from both reading data from                           

your sensors and from inserting bogus data posing as a sensor. 

The radio network ID is set by default to the gateway serial number, but it can be changed.                                   

For example, if you are replacing a gateway, you might want to set the new gateway (with a                                   

new serial number) to the old gateway’s network ID so that data loggers don’t have to be                                 

reconfigured. 

59 

The network password is set by default to a randomly generated value and is printed on 

your Gateway Information sheet. The generated password is unique to each gateway unit, 

so it is safe to use. 

In order to achieve communication, the gateway and all the data loggers in a network need 

to be configured with the same network ID and password. 

For security reasons, the network password cannot be read from a data logger by the

GTecLink  Android app. For this reason, when entering the radio configuration dialog, the

password  displayed is the last one that was set using this Android device. 

60 

5.2 Radio specifications 

There  are  three  different  gateway  models,  each  with  different  configurable  radio  and  3G/GPRS modem models.  

The  gateway  model  must  be  selected  in  compliance  with  local  regulations  in  the  region  where the installation is going to be carried out. Should you have questions, we recommended  consulting  Worldsensing  about  the  local  regulations and the most suitable  gateway model and radio type for each country.  

3G/GPRS modem settings 

The  network  must  also  be  available  in  the  country  of  installation.  This  table  shows  the  3G/GPRS frequencies available for each gateway model, which must match with the existing network in the country (and must also be accepted by the SIM card provider). 

58821000 (CE)

GPRS/3G Radio type  Available frequency  Upload/Download Bandwidth 

HDSPA UMTS 

900/2100 MHz  DL 7.2 Mbps/ UL 5.6 Mbps UL/DL 384 Kbps 

GPRS  900/1800 MHz  UL/DL 85.6 Kbps UL/DL 236.8 Kbps 

Available frequency  Upload/Download Bandwidth 

850/1900 MHz  DL 3.6 Mbps/ UL 384 Kbps 

850/1900 MHz  UL/DL 384 Kbps 

850/1900 MHz  UL/DL 85.6 Kbps 

850/1900 MHz  UL/DL 236.8 Kbps 

Available frequency  Upload/Download Bandwidth 

900/2100 MHz  DL 7.2 Mbps/ UL 5.6 Mbps UL/DL 384 Kbps 

EDGE

58822000 (FCC/IC)

GPRS/3G Radio type  HDSPA

UMTS

GPRS

EDGE

58823000 (Asia/Pacific)

GPRS/3G Radio type  HDSPA

UMTS

GPRS EDGE

900/1800 MHz  UL/DL 85.6 Kbps UL/DL 236.8 Kbps 

61 

a 868 band and

5.2.1 58821000 (CE) 

This  model  includes  radios  for  Europe,  Malaysia-Legacy  (which works on         can be used until January 2018) and India (866I). Depending on local regulations, these                           

1

radios can be also used in other countries. 

58821000 (CE) EUROPE  MALAYSIA LEGACY (868) INDIA 866I (865-867) 

Upload 

Channel number  6  5  8 

Frequencies 

868.1 MHz 

868.3 MHz 

868.5 MHz 

868.85 MHz 

869.05 MHz 

869.525 MHz 

869,1 MHz 

869,3 MHz 

869,5 MHz 

869,7 MHz 

869,9 MHz 

865.3 MHz 

865.5 MHz 

865.7 MHz 

865.9 MHz 

866.1 MHz 

866.3 MHz 

866.5 MHz 

866.7 MHz 

Channel bandwidth (KHz)  125  125  125 

Download 

Channel number  6  5  8 

Frequencies 

868.1 MHz 

868.3 MHz 

868.5 MHz 

868.85 MHz 

869.05 MHz 

869.525 MHz 

869,1 MHz 

869,3 MHz 

869,5 MHz 

869,7 MHz 

869,9 MHz 

865.3 MHz 

865.5 MHz 

865.7 MHz 

865.9 MHz 

866.1 MHz 

866.3 MHz 

866.5 MHz 

866.7 MHz 

Channel bandwidth (KHz)  125  125  125 

U/D on same channels?  YES  YES  YES 

Default Tx Pw  14 dB  14 dB  14 dB 

Default Spreading factor  SF11  SF9  SF11 

Available Spreading factor SF7, SF8, SF9, 

SF10, SF11 SF7, SF8, SF9 

SF7, SF8, SF9, SF10, 

SF11, SF12 

Data logger configuration ADR, Tx Pw, ETSI, 

Max SF ADR, Tx Pw, Max SF  ADR, Tx Pw, Max SF 

Gateway configuration  -  -  - 

1 For India, the SAW filter must be modified to extend the lower part of the frequency band. A 862-867 MHz cavity filter is also recommended to avoid saturation and desensitization of the radio receiver due to co-located LTE850 or CDMA800 base stations. 

62 

6.2.2 58822000 (FCC/IC) 

This  model  includes  radios  for  FCC,  Peru  (923P),  Chile  (926C),  Australia  (923A)  and  Singapore (922S). 

FCC  923P PERU  926C CHILE 58822000 (FCC/IC)

 Upload Channel number  8  8  8 

Frequencies Group 0  Group 1  Group 2  Group 3 

902,3 MHz 902,5 MHz 902,7 MHz 902,9 MHz 903,1 MHz 903,3 MHz 903,5 MHz 903,7 MHz 

903,9 MHz 904,1 MHz 904,3 MHz 904,5 MHz 904,7 MHz 904,9 MHz 905,1 MHz 905,3 MHz 

905,5 MHz 905,7 MHz 905,9 MHz 906,1 MHz 906,3 MHz 906,5 MHz 906,7 MHz 906,9 MHz 

907,1 MHz 907,3 MHz 907,5 MHz 907,7 MHz 907,9 MHz 908,1 MHz 908,3 MHz 908,5 MHz 

Group 4  Group 5  Group 6  Group 7* 908,7 MHz 908,9 MHz 909,1 MHz 909,3 MHz 909,5 MHz 909,7 MHz 909,9 MHz 910,1 MHz 

910,3 MHz 910,5 MHz 910,7 MHz 910,9 MHz 911,1 MHz 911,3 MHz 911,5 MHz 911,7 MHz 

911,9 MHz 912,1 MHz 912,3 MHz 912,5 MHz 912,7 MHz 912,9 MHz 913,1 MHz 913,3 MHz 

913,5 MHz 913,7 MHz 913,9 MHz 914,1 MHz 914,3 MHz 914,5 MHz 914,7 MHz 914,9 MHz 

921,4 MHz 921,6 MHz 921,8 MHz 922 MHz 

922,2 MHz 922,4 MHz 922,6 MHz 922,8 MHz 

925,2 MHz 925,4 MHz 925,6 MHz 925,8 MHz 926,0 MHz 926,2 MHz 926,4 MHz 926,6 MHz 

Channel bandwidth  125 KHz  125 KHz  125 KHz 

Download  Channel number  8  8  8 

Frequencies  923,3 MHz 923,9 MHz 924,5 MHz 925,1 MHz 925,7 MHz 926,3 MHz 926,9 MHz 927,5 MHz 

921,4 MHz 921,6 MHz 921,8 MHz 922 MHz 

922,2 MHz 922,4 MHz 922,6 MHz 922,8 MHz 

925,2 MHz 925,4 MHz 925,6 MHz 925,8 MHz 926,0 MHz 926,2 MHz 926,4 MHz 926,6 MHz 

Channel bandwidth  500 KHz  125 KHz  125 KHz 

U/D on same channels? 

NO  YES  YES 

Default Tx Pw  20 dB  20 dB  14 dB 

Default spreading factor 

SF9  SF11  SF11 

Available spreading factor 

SF7, SF8, SF9  SF7 SF8 SF9 SF10 SF11 

SF7 SF8 SF9 SF10 SF11 SF12 

Data logger configuration 

ADR, Channel group (Group 0 by default), Tx Pw, Max SF  ADR, Max SF, Tx Pw 

ADR, Max SF, Tx Pw 

Gateway configuration 

Channel group (Group 0 by default)  -  - 

63 

58822000 (FCC/IC) 923A (HYBRID)  922S SINGAPORE 

Upload 

Channel number  8  6 

Frequencies 

917,2 MHz 917,4 MHz 917,6 MHz 917,8 MHz 918,0 MHz 918,2 MHz 918,4 MHz 918,6 MHz 

920,9 MHz 921,2 MHz 921,5 MHz 922,8 MHz 923,1 MHz 923,4 MHz 

Channel bandwidth  125 KHz  125 KHz 

Download 

Channel number  8  6 

Frequencies 

923,3 MHz 923,9 MHz 924,5 MHz 925,1 MHz 925,7 MHz 926,3 MHz 926,9 MHz 927,5 MHz 

920,9 MHz 921,2 MHz 921,5 MHz 922,8 MHz 923,1 MHz 923,4 MHz 

Channel bandwidth  500 KHz  125 KHz 

U/D on same channels?  NO  YES 

Default Tx Power  20 dB  20 dB 

Default spreading factor  SF11  SF11 

Available spreading factor  SF7, SF8, SF9, SF10,SF11  SF7 SF8 SF9 SF10SF11 

Data logger configuration  Max SF, ADR, Tx Pw  Max SF, ADR, Tx Pw 

Gateway configuration  -  - 

64 

5.2.3 58823000 (Asia/Pacific) 

This model includes radio 923A (Australia), 923M (Malaysia), 922S (Singapore, Vietnam, New Zealand, Hong Kong), 923T (Taiwan). 

This model also includes legacy radios for Australia (AU-500 KHz (short range radio), FCC                           Channel 7). 

Depending on local regulations, these radios can be also used in other countries. 

58823000 (Asia/Pacific) 923A (HYBRID) 

MALAYSIA 923M  AU 500 KHz  FCC CHANNEL GROUP 7 

Upload  Channel number  8  16  1 (4 Available)  8 

Frequencies 

917,2 MHz 917,4 MHz 917,6 MHz 917,8 MHz 918,0 MHz 918,2 MHz 918,4 MHz 918,6 MHz 

Group 0 922,1 MHz 922,3 MHz 922,5 MHz 922,7 MHz 922,9 MHz 919,1 MHz 919,3 MHz 919,5 MHz 

Group 1 919,7 MHz 919,9 MHz 920,1 MHz 920,3 MHz 920,5 MHz 920,7 MHz 920,9 MHz 921,1 MHz 

921,9 MHz 

922,5 MHz 

923,7 MHz 

924,3 MHz 

FCC Group 7 913,5 MHz 913,7 MHz 913,9 MHz 914,1 MHz 914,3 MHz 914,5 MHz 914,7 MHz 914,9 MHz 

Channel Bandwidth  125 KHz  125 KHz  500 KHz (low range)  125 KHz 

Download  Channel number  8  16  1 (4 Available)  8 

Frequencies 

923,3 MHz 923,9 MHz 924,5 MHz 925,1 MHz 925,7 MHz 926,3 MHz 926,9 MHz 927,5 MHz 

Group 0 922,1 MHz 922,3 MHz 922,5 MHz 922,7 MHz 922,9 MHz 919,1 MHz 919,3 MHz 919,5 MHz 

Group 1 919,7 MHz 919,9 MHz 920,1 MHz 920,3 MHz 920,5 MHz 920,7 MHz 920,9 MHz 921,1 MHz 

921,9 MHz 

922,5 MHz 

923,7 MHz 

924,3 MHz 

923,3 MHz 923,9 MHz 924,5 MHz 925,1 MHz 925,7 MHz 926,3 MHz 926,9 MHz 927,5 MHz 

Channel Bandwidth  500 KHz  125 KHz  500 KHz (low range)  500 KHz 

U/D on same channels? 

NO  YES  YES  NO 

Default Tx Power  20 dB  20 dB  20 dB  20 dB 

Default Spreading Factor 

SF11  SF12  SF9  SF9 

Available Spreading Factor 

SF7, SF8, SF9, SF10,SF11 

SF7, SF8, SF9, SF10,SF11, SF12 

SF7 SF8 SF9 SF10SF11  SF7, SF8, SF9 

Datalogger configuration 

Max SF, adr, Tx Pw 

Channel group (Group 0 by default), Tx Pw, Max SF, ADR 

Channel ,Tx Pw, Max SF  - 

Gateway configuration 

-  Channel group (Group 0 by default) 

Channel and SF  - 

65 

58823000 (Asia/Pacific)922S 

SINGAPORE 923T TAIWAN  CHILE 926C 

Upload 

Channel number  6  16  8 

Frequencies 

920,9 MHz 

921,2 MHz 

921,5 MHz 

922,8 MHz 

923,1 MHz 

923,4 MHz 

Group 0 921.9 MHz 922.1 MHz 922.3 MHz 922.5 MHz 922.7 MHz 922.9 MHz 923.1 MHz 923.3 MHz 

Group 1 923.5 MHz 923.7 MHz 923.9 MHz 924.1 MHz 924.3 MHz 924.5 MHz 924.7 MHz 924.9 MHz 

925,2 MHz 925,4 MHz 925,6 MHz 925,8 MHz 926,0 MHz 926,2 MHz 926,4 MHz 926,6 MHz 

Channel bandwidth  125 KHz  125 KHz  125 KHz 

Download 

Channel number  6  16  8 

Frequencies 

920,9 MHz 

921,2 MHz 

921,5 MHz 

922,8 MHz 

923,1 MHz 

923,4 MHz 

Group 0 921.9 MHz 922.1 MHz 922.3 MHz 922.5 MHz 922.7 MHz 922.9 MHz 923.1 MHz 923.3 MHz 

Group 1 923.5 MHz 923.7 MHz 923.9 MHz 924.1 MHz 924.3 MHz 924.5 MHz 924.7 MHz 924.9 MHz 

925,2 MHz 925,4 MHz 925,6 MHz 925,8 MHz 926,0 MHz 926,2 MHz 926,4 MHz 926,6 MHz 

Channel bandwidth  125 KHz  125 KHz  125 KHz 

U/D on same channels?  YES  YES  YES 

Default Tx Pw  20 dB  20 dB  14 dB 

Default spreading factor  SF11  SF9  SF11 

Available spreading factor 

SF7 SF8 SF9 

SF10SF11 SF7, SF8, SF9  SF7 SF8 SF9 SF10 SF11 

SF12 

Data logger configuration 

Max SF, ADR, Tx Pw 

Channel group (Group 0 by default), Tx Pw, Max 

SF, ADR ADR, Max SF, Tx Pw 

Gateway configuration  -  Channel group (Group 0 

by default)  - 

66 

5.3 Number of nodes, sampling rate and slot time 

The number of data loggers that can be connected to a radio network is limited by the                                 

number of messages that can be transmitted over a period of time. All nodes in the network                                 

take their readings at a synchronized time (e.g. if reading every 5 minutes, readings are                             

taken every hour, at minute 0, 5, 10, 15 and so on.). These messages are then written in the                                     

internal node memory, but are not transmitted immediately. The readings are transmitted                       

to the gateway at a random time inside a communication slot. 

Summarized outline of data transmission over time in a LS-G6 network.  

The length of the communication slot depends on the number of nodes in a network (Table

7) and  is  chosen  automatically  by  the  Android  Configuration  app when  a  node  is

configured. There are also combinations of network sizes and sampling rates that are not

supported.  This  is  to  prevent  all  nodes  from  sending  readings  at  the  same  time  and 

saturating the network. 

This is why it is important to correctly define the number of nodes available in the network

using the GTecLink Android application. 

67 

This table shows estimated Slot times (in seconds) for                 analog (57804800), vibrating

wire (526160xx) and wireless tiltmeter (57803150). 

0-4 5-8 9-40 41-240 241-480 481-2000

30 s  25  NO  NO  NO NO NO

1 min  30  50  NO  NO NO NO

5 min  30  60  250  NO NO NO

15 min  30  60  300  NO NO NO

30 min  30  60  300  1500 NO NO

1 h  30  60  300  1800 3000 NO

2 h  30  60  300  1800 3600 NO

4 h  30  60  300  1800 3600 NO

6 h  30  60  300  1800 3600 15000 

12 h  30  60  300  1800 3600 15000 

24 h  30  60  300  1800 3600 15000 

Table 7: Slot times table for VW, analog nodes and wireless tiltmeter. 

The digital node doesn’t necessarily comply with the slot times table (Table 7) because

readings may take longer than VW or ANALOG data loggers. Slot Time may vary depending

on the type of sensor connected. 

RST / SisGeo networks over digital nodes: 

0-4 5-8 9-40 41-240 241-480 481-2000

30 s  NO  NO  NO  NO  NO  NO 

1 min  25  NO  NO  NO  NO  NO 

5 min  30  60  NO  NO  NO  NO 

15 min  30  60  300  NO  NO  NO 

30 min  30  60  300  NO  NO  NO 

1 h  30  60  300  1500  NO  NO 

2 h  30  60  300  1800  3000  NO 

4 h  30  60  300  1800  3600  NO 

6 h  30  60  300  1800  3600  NO 

12 h  30  60  300  1800  3600  15000 

24 h  30  60  300  1800  3600  15000 

Table 8: Slot times table for RST or SisGeo sensor networks using digital data logger. 

MDT SmartLink networks over digital nodes: 

68 

0-4 5-8 9-40 41-240 241-480 481-2000

30 s  NO  NO  NO  NO  NO  NO 

1 min  NO  NO  NO  NO  NO  NO 

5 min  30  60  NO  NO  NO  NO 

15 min  30  60  250  NO  NO  NO 

30 min  30  60  300  NO  NO  NO 

1 h  30  60  300  NO  NO  NO 

2 h  30  60  300  1800  NO  NO 

4 h  30  60  300  1800  3600  NO 

6 h  30  60  300  1800  3600  NO 

12 h  30  60  300  1800  3600  NO 

24 h  30  60  300  1800  3600  15000 

Table 9: Slot times table for RST or SisGeo sensor networks using digital data logger. 

As  these  parameters  have  been  locally  configured  at  the  node 

(using the GTecLink  app), the  gateway is not aware of the slot time, so it will use a

default value (1 hour) to generate compacted files. Forcing sampling rate from the

gateway once it has been updated on the nodes (a new sampling rate is set at the nodes

once they communicate with the gateway to  send  data)  allows  the  gateway 

to identify SR and, together with the connected nodes,  calculates the new slot time and

adjusts the delay between data reception and compacted file generation. (See paragraph

3.)

69 

6. RESULTS OF SIGNAL COVERAGE TEST

There are several ways to access signal coverage test results: 

1) Signal coverage test results are available in the Android Configuration app.

2) They are also displayed geographically in the gateway software. In this case, your

computer must be connected to the Internet to access the map. The position where

the tests have been carried out is displayed with a specific symbol that represents

coverage at that specific point. The symbol displayed (color legend) indicates the

maximum SF from which >50% of the information packages sent by the data logger

reached the gateway. In red, the places where ≤50% of the packages of SF 12 are

indicated. The gateway is also indicated on the map.

3) Additionally, signal coverage tests results can be downloaded from the gateway in

a CSV file (lower right-hand corner of the image). If the test is done “offline,” the

results only appear in this CSV.

Note: Whether or not the gateway has received the data from the tests, all the tests are 

saved in a CSV file inside the Android device (GTecLink directory). Geographical data are

also  saved there (if GPS is activated in the Android). In case the device is not connected

to  Internet, saved records will be 0. 

70 

7. CONTACT DGSI.

Phone : +1 770 465 7557 +1 423 495 6200  

Technical Support : support@dgeslope.com 

ADDRESS :

Durham Geo Slope Indicator

2175 West Park Court  12123 Harbour Reach Drive

Stone Mountain, Georgia 30087  Mukilteo, Washington 98275

(United States of America) (United States of America)

71 

8. TROUBLESHOOTING REFERENCE TABLE

ERROR  CAUSE  SOLUTION 

Connectivity error: 

Gateway not 

available 

(connected from 

3G/GPRS) 

Gateway not 

powered 

-Check that PoE injector is plugged in and

LED is green (PoE powering). 

-Check correct voltage on power supply

(External powering). 

No SIM card  -Insert SIM card.

Low 3G coverage -Move to a higher or different location.

-Change SIM card provider.

SIM card 

configuration 

problem 

-Check APN configuration of the network

operator. 

PIN key enabled 

-Check that PIN key is OK.

-Check that PIN key is not locked (using a

mobile device). 

-Disable PIN key and reconfigure device.

3G/GPRS not 

configured 

-Connect through USB-Ethernet interface

and configure 3G/GPRS area. 

SIM card out of data  -Check SIM card data availability.

Software issue 

-Reset device(https://gteclink.wocs3.com/[GW_ID]/

reboot.html)

Table 10:Troubleshooting Gateway 

72 

ERROR  CAUSE  SOLUTION 

Connectivity error: 

Gateway not 

available (connected 

from Ethernet 

interface) 

Gateway not 

powered 

-Check that PoE injector is plugged in and

LED is green (PoE powering). 

-Check correct voltage on power supply

(External powering). 

Incorrect 

connection 

-Check correct connection of Ethernet

cable to Gateway. 

-Check cables are connected from GW to

“DATA & POWER OUT” at PoE injector, and 

from “DATA IN” to Ethernet network. 

Incorrect Boot 

-Check that Ethernet wiring is complete

before restarting the gateway. If internet 

configuration is automatic, it will swap to 

3G/GPRS connection if there is no link 

between LAN and the gateway. 

Incorrect 

configuration. 

-Check that internet connection is not set

by default, using the USB-Ethernet 

interface. 

-Check PING to gateway IP.

-Check LAN access from the same subnet

Networking issues 

Software issue 

(https://[Gateway_ID] ). 

-Check that gateway and DNS are

correctly set. 

-Check that the network has internet

access through TCP22 port. 

-Check that the configured network has

access to internet from the connected 

network.

-Check Proxy/Firewall and other network

element configuration. 

-Reset device

(https://gteclink.wocs3.com/[GW_ID]/

reboot.html ) 

73 

Table 11: Troubleshooting (Ethernet access) 

ERROR  CAUSE  SOLUTION 

Gateway offline 

periodically on 

non-internet-acces

s installations 

Internet WatchDog 

provokes periodical 

resets. 

WEB error: “Internal 

Server Error” 

Blocked application 

by excess of CPU 

usage 

Data: Health file of a 

node unavailable 

Node has a higher 

version than the 

gateway. 

Data: Serial number 

of a node 

unavailable 

Node has a higher 

version than the 

gateway. 

-Deactivate WatchDog (resets gateway

every 40 minutes). 

-Reset device and check access again.

(https://gteclink.wocs3.com/[GW_ID]/

reboot.html).

-Request gateway upgrade from

Worldsensing technical department. 

-Request gateway upgrade from

Worldsensing technical department. 

Data: Readings from 

a node are 

unavailable 

Node has no battery 

or does not 

communicate 

-Check node troubleshooting.

Node is not 

up-to-date 

-Set actual time and date of the node

Data: Repeated 

TimeStamps on 

compacted files 

The date and time of 

some nodes are not 

synchronized with 

the Gateway 

Compacted  File has reached 

using GTecLink android application.

-Upgrade may be required: Solved at

Gateway fw version 1.12.1 or higher + data 

logger v.2.23 or higher + Wireless tiltmeter 

2.25 or higher. (More information here.) 

-Set actual time and date of the nodes by

using GTecLink android application. 

-Upgrade may be required: Solved at

Gateway fw version 1.12.1 or higher + data 

logger v.2.23 or higher + Wireless tiltmeter 

2.25 or higher. (More information here.) 

-Retrieve data from node files.

74 

readings: Last nodes 

are not appended 

600 columns. 

(Maximum number 

of columns per CSV) 

-Retrieve data from Compacted Custom.

-Close and rename the existing CSV file on

FTP site and change to 1000 Lines CSV. 

ModBUS: No data 

received and node 

type is displayed as 

‘Unknown’ 

No data are available 

at ModBUS registers 

-Check node radio connection to gateway.

-Check node’s ModBUS message timeout

is not smaller than node sampling rate. 

FTP: New readings 

are not appended to 

existing files 

FTP Server error 

-Check FTP configuration.

-Check that file is not corrupted.

-Check file read/write permissions.

-Erase file to be generated again.

Table 12:Troubleshooting (Data) 

75