IOT-S300WS7 is an ultimate all-in-one RS485 Modbus weather monitoring system for various and continuous atmospheric conditions including air temperature, relative humidity, barometric pressure, light intensity, rainfall(optical), wind speed, and wind direction (ultrasonic). It boasts high resolution and accuracy with rugged and aesthetic housing.

IOT-S300WS8, it is LINOVISION 8-in-1 Professional Environment Monitor with Sensors of Ultrasonic Wind, PM2.5, PM10 and Noise, Remote Management via RS485 ModBus, Accurate Weather Station for Pollution Detection.

Outstanding Features:

• 8-in-1 Environment Monitor - Integrated sensors of temperature, humidity, pressure, wind speed, wind direction, noise, PM2.5, PM10, ideal for pollution detection, city environmental monitoring.
• Pro-Grade Accuracy - For scientific research or commercial weather station integration.
• Ultrasonic Sensor - Provides highly precise measurement and much more reliable without using any movable parts.
• RS485 Modbus - Support remotely management when bundling with Modbus gateway or 4G Cellular DTU.
• Industrial-Level Design - IP66 outdoor rated, and working in cold weather with built-in heater (-40 ℃ ~ + 85℃)
• Accessories - Comes with pole mount bracket. Free subscription to Linovision AIoT RemoteMonit Cloud.

Applications: 

 Q1: Is there API for Linovision gateway to get historical data?

Answer: There is no API to get historical data. If you have any requirements about it please contact Linovision about it.  

Q2: What kind of the material does the IOT-G67’s outer shell made of

Answer: Polycarbonate+ die-casting aluminum.

Q3: Is it possible to connect multiple IOT-G65 to the network server of one IOT-G65?  How many can I connect?

Answer: Yes, you can connect up to 4 units of devices.

Q4: I want to ask if the gateway could perform end device localization based on TDoA (Time Difference of Arrival)? 

Answer: Currently cannot. Linovision gateways support the gateway GNSS positioning now.

Q5: What are the main factors that will affect the number of the IOT-CX controller that gateway manage?

Answer: The number of IOT-CX controller that connect to gateway would be affected by factors like reporting interval, distance in between, payload length, Lora frequency band and spread factor.

Q6: What is the maximum length of the PoE cable supported for the IOT-G67 gateway ? 

Answer: The length is up to 80-100 meters.

Q7: What is the difference between LoRaWAN 1.0.2 and 1.0.3? If I am using class B, which version shall I use? And can version 1.1 compatible with 1.0.3?

Answer: LoRaWAN1.0.3 supports unicast & multicast class B devices. Class A and class C sections are unchanged compared to LoRaWAN1.0.2 with the exception of a new MAC command "DeviceTimeRequest" used to synchronize the real time clock of a device. For devices operating in class A or class C, there is no need to upgrade to LoRaWAN 1.0.3. Click here for more information about LoRaWAN 1.0.3.

Q8: What are the new features for the  LoRaWAN V1.1 compared with  LoRaWAN  v1.0.2?

Answer: LoRaWAN V1.1 protocol is optimized for battery-powered end-devices and adds support for handover roaming, Class B and security enhancements. Click here for more information about LoRaWAN 1.1.

Q9: How many super capacitors in your IOT-G67? How many Farad for each one?

Answer: IOT-G67 has 5 capacitors inside, and each one is 25 Farad.

Q10: Can the IOT-G65 and IOT-G67 support external 4G antenna?

Answer: IOT-G65 can be customized to connect external antenna, while the IOT-G67 cannot. Please contact Linovision sales if you need external antenna customization.

Q11: Why the time stamp of message that received on Network Server is different from the set time of Linovision LoRaWAN Gateway?

Answer: In standard LoRaWAN protocol, the upload time is defined on UTC time zone. So the time displayed on Chirpstack server is different due to different time zone.

Q12: Can the LoRaWAN sensor data collected by the Linovision LoRaWAN gateway be sent to cloud/websites other than the Linovision IoT Cloud?

Answer: Yes. Linovision gateway supports data transmission via MQTT/HTTP/HTTPS. You can refer to articles below:

How to Connect LoRaWAN Gateway to MQTT Broker

How to Connect Linovision LoRaWAN Gateway to HTTP(s) Server

Q13: Does the Node-RED of Linovision LoRaWAN gateway start up on boot or it needs to be started manually?

Answer: It starts up when it's enabled on Web GUI.

Q14: Is it possible to send a payload to the Linovision LoRaWAN gateway to send an instruction to a LoRaWAN Controller using HTTP like we do posting a message to a specific topic in MQTT?

Answer: No. When the gateway is connected to HTTP/HTTPS server, it only supports uplink. If you want to send downlink, one way is to use the Node-Red feature on the gateway. In that case, the gateway works as HTTP server and it requires a public IP (Cellular or WAN) to allow connection from HTTP client.

Q15: Are the IOT-G67 gateway able to use nanosecond timestamp for geolocation? 

Answer: Not supported now. Linovision have plans to upgrade chip which is suitable for geolocation. Please contact Linovision if you have any applications requiring for it.

Q16: Do you have any recommendations regarding lightning protection?

1. If we mount the gateway on relatively low height (4-5 m, on top of fiber optic PoP), and we connect the gateway body (by original metal mount) with the lightning protection of the PoP, do we need the surge protection on the antennas and LAN cable?

2. Do you have to offer some directional antennas, in cases where we want to cover only a part of space, for example 90 degrees? This would improve our reception in cases where the gateway is mounted outside of a city.

Answer:

1. The height is not the most important. The critical thing is whether there is other devices/buildings higher than your gateway. Antenna needs lightning surge protectors separately. If your network cable has passed any surge protection system, there is not need to add extra protection.

2. Not by default. If necessary, please share your directional antenna requirements to Linovision in details.

Q17: The gateway disappears from TTN quite often, how to check the issue? 

Answer: Regarding the disconnection between the gateway and TTN, you can check the following points:

1. Whether the network of the gateway is normal: Fail to Access the Network of Linovision Gateway.

2. If you use Semtech type packet forwarder, you can change to TTN type which is more stable: Linovision Gateway -The Things Stack(TTN) Integration via Basic Station

Q18: Can you inform about the difference in range between IOT-G65-L04EU-868M without external antennas and IOT-G65-L04EU-868M -EA with external antenna in an Indoor application?

Answer: The gain of external antenna is 2dB, while the gain of internal is about 1dB.

 If the gateway just need to cover the end devices in the building (2 floors nearby), the internal antenna version is enough, the signal quality (Average SNR) is 2dB less than the external antenna). The distance (max) can reach 1 km in building/park/city.

If the gateway needs to cover wider area, the external antenna version is recommended, the signal quality (Average SNR) is 6dB more than the internal antenna version.

The distance (max) can reach 2 km in buildings/parks/cities.

Q19: What is the maximum number of channels we can configure in LoRaWAN gateway to receive or send data from Nodes(Channels)?

Answer: The max number of channels that can send and receive is 8. One channel of the gateway can deal with a data packet one second, so if the interval is 1 min, it can deal 480 data packet (nodes); if your sensor interval is 1 hour, it's sure that the gateway can work with 100 devices.

Q20: What's the meaning of the packet with different colors under "Network Server->Packet" tab?

Answer: Blue and white means normal transmission and grey means the message is in queue and waiting for sending. This always happens in sending downlinks to Class A type device.

Q21: Can we connect & configure 2 sensors to the same Application in Linovision gateway? If yes, how to separate every sensor data?

Answer: If the sensor modules are the same, you can use the same application including the same decoder and the MQTT destination. You can configure decoder to add device EUI of every sensor to distinguish every sensor. For more details please refer to How to Use Payload Codec on Linovision Gateway.

Q22: Is it possible to select all international frequencies (for all LoRaWAN frequencies) in one chip with IOT-G67?

Answer: It's unable to select all LoRaWAN frequencies in only one hardware.

Q23: Does Linovision IOT-G6x gateway support Node Red? If so, do I need to expand the eMMC for it?

Answer: Linovision IOT-G6x gateway has supported Node Red with firmware version 60.0.0.35 or above. There is not need to expand the eMMC.

Q24: How to use the Node-Red of Gateway? 

Answer: Please refer to LoRaWAN Gateway User Guide about Node-RED introduction and application examples.

Q25: Can the gateway connect to the Ginjer platform?

Answer: Yes, this platform has integrated with TTN, gateway can connect Ginjer platform via TTN.

Q26: Will all the traffic go over the VPN tunnel if connect the gateway to Loriot and enable the VPN?

Answer: No, because VPN tunnels and Loriot traffic destination are different.

Q27: Why can't I see the cellular settings on the gateway Web GUI?

Answer: You can go to "Status->Overview->System information" webpage to check whether the product model contains "L0XX". If not included, it means this model doesn't support cellular. Otherwise please submit a ticket to support@linovision.com about it.

Q28: Is there a way to send data over http(s) to the gateway that will be forwarded to the lorawan-sensor? 

Answer: For the HTTP API to send the downlink message to the sensor, it's not supported in our gateway. It's suggested to use MQTT integration which supports both uplinks and downlinks.

Q29: Why can't I connect the gateway to the Internet through WLAN?

Answer: Please check the settings of WAN Failover, which supports Cellular and WAN interface there by default. You need to select WLAN as the primary interface to make the gateway access the network.

Q30: What is the DC power input connector type of IOT-G67?

Answer: The connector type for power input is M12 Connector. For detailed definitions, please refer to the chapter2.5 of IOT-G67 Quick Guide.

Q31: Can IOT-G6x gateway connect to SCADA system? 

Answer: Yes, if your SCADA supports MQTT protocol and can work as MQTT broker, you can connect Linovision gateway to SCADA system and transfer data to it. SCADA system can also poll Modbus data from IOT-C50x according to How to Achieve Modbus RTU to/over TCP between Linovision Gateways and Controllers. By the way, Linovision IOT-G6x gateway has integrated the Node-Red for flexible integration.

Q32: Can I connect gateway to Linovision IOT-G6x gateway build-in NS? How many gateways can I connect it at most? Can I use third-party gateway to connect?

Answer: One Linovision LoRaWAN gateway can connect to 4 Linovision IOT-G6x gateways at most, which is a feature of Linovision IOT-G6x gateways only.

Q33: Does the Linovision IOT-G65 support dual interfaces to connect network?

Answer: Yes, Linovision IOT-G65 supports main interface and back up interface to connect to network.

Q34: Can IOT-G6x gateway connect to multiple MQTT/HTTP servers?

Answer: Yes, Linovision IOT-G6x gateway supports to connect to 1 MQTT server and 1 HTTP/HTTPs server.

Description

When working as embedded network server, Linovision LoRaWAN gateways support sending data packets to third party MQTT/HTTP/HTTPS server. We can create a new application on gateway, which can define the method of decoding the data sent from LoRaWAN end-device and choosing MQTT data transport protocol to send data to MQTT server.

Requirement

•  LoRaWAN Gateway: IOT-G8x (Firmware version 80.0.0.64 or later), IOT-G65, IOT-G67, IOT-G56, IOT-G63 V1
• MQTT Server/Broker
• MQTT client tool: take MQTT Explorer as example

Configuration

Step1. Enable the gateway built-in network server.

Go to Packet Forwarder > General to enable the localhost server address.

Enable the Network server on Network Server > General page.

Step2. Add an Application

Go to Network Server>Applications to add a new application, click save.

Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Step3. Connect gateway to MQTT broker.

Go to Network Server > Applications to add a “data transmission” for the application. One application can add only one MQTT integration.

Fill in the MQTT broker information and create topic to store different data type, click save.

Broker Address: IP address/domain of MQTT broker

Broker Port: communication port of MQTT broker

Client ID: user-defined, a unique ID identity of the client to the server.

User Credentials and TLS should be enabled and configured as required.

Note: if MQTT broker is HiveMQ, please do enable TLS and set the option as CA signed server certificate.

After MQTT configuration complete, you can check connection status here:

Step4. Add LoRaWAN nodes to the gateway.

Go to Network Server>Profiles to add a new profile, then click save. You can also use pre-defined profiles.

Name: user-defined, arbitrary value

Max TXPower: default value

Other parameters can be checked from LoRaWAN nodes user guide or you can keep all settings by default.

Go to Network Server>Device to add a new device, click Save&Apply.

Device Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Device-Profile: choose one of corresponding profiles added before.

Application: choose one of corresponding applications added before.

Other parameters can be confirmed with the LoRaWAN node manufacturers.

When the status shows as below, that’s mean above steps are done correctly.

Step5. Add uplink data topic.

Customize the uplink data to publish to MQTT broker and save the settings. If you add “$deveui” on your topic, you can replace it as real device EUI when subscribing topics. 

Example: /linovision/uplink/$deveui

Step6. Subscribe topic from MQTT client to get uplinks.

MQTT explorer is a comprehensive MQTT client and it can be replaced to other kinds of MQTT client tools(MQTT.fx, MQTT Box, etc.)

Open the MQTT Explorer, and fill in related MQTT server information in the popup window.

Name: user-defined

Protocol: mqtt://

Host: MQTT broker address

Port: broker port

User name/Password: if there is user credentials, please fill in it. If not, keep them blank.

Click ADVANCED,copy the Uplink data topic on the gateway, and paste it on the MQTT explorer, click +ADD.

Keep MQTT client ID by default,then click BACK and click CONNECT.

After while, the data will be forwarded to MQTT broker and the MQTT Exploerer can receive the data from MQTT server.

The uplink format is fixed as json and the content is as below.

{
  "applicationID": 1,                   // application ID
  "applicationName": "cloud",           // application name
  "deviceName": "24e1641092176759",     // device name
  "devEUI": "24e1641092176759",         // device EUI
  "time": "2020-0327T12:39:05.547336Z", // uplink receive time
  "rxInfo": [                           // lorawan gateway information related to lora
    {
      "mac": "24e124fffef021be",        // ID of the receiving gateway
      "rssi": -57,                      // signal strength (dBm)
      "loRaSNR": 10,                    // signal to noise ratio
      "name": "local_gateway",          // name of the receiving gateway
      "latitude": 0,                    // latitude of the receiving gateway
      "longitude": 0,                   // longitude of the receiving gateway
      "altitude": 0                     // altitude of the receiving gateway
    }
  ],
  "txInfo": {                           // lorawan node tx info
    "frequency": 868300000,             // frequency used for transmission
    "dataRate": {
      "modulation": "LORA",             // LORA module
      "bandwidth": 125,                 // bandwidth used for transmission
      "spreadFactor": 7                 // spreadFactor used for transmission
    },
    "adr": false,                       // device ADR status
    "codeRate": "4/5"                   // code rate
  },
  "fCnt": 0,                            // frame counter
  "fPort": 85,                          // application port
  "data": "AWcAAAJoAA=="                // base64 encoded payload (decrypted)
}

FAQ

Q1.How to send decoded or customize uplink content to MQTT broker?

A1:  Yes, this needs to use Payload Codec feature on the gateway. Reference articles:

IOT-G56/G65/G67: How to Use Payload Codec on Linovision Gateway

IOT-G63 V1/G8x: How to Use Payload Codec on Linovision Gateway (Old)

Q2.What’s the troubleshooting when the status of MQTT server connection is “Disconnected”.

A2: 

1) Go to Maintenance > Tools >Ping , check if the gateway can ping to the broker address successfully.

2) Check if your MQTT client tool can connect to MQTT broker well, then follow the settings of MQTT client tool to configure the gateway.
3) Check if the gateway MQTT client ID is conflict with other MQTT clients.
4) Check if CPU load is too high, and if there is little available RAM and eMMC.
5) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

Q3.Why the connection status shows “connected” but MQTT client does not receive any data?
A3:
1)Ensure the devices has been added to gateway and go to Network Server > Packets to check if there are uplink packets from devices regularly.
2) Ensure the devices has been added to the correct Application.
3) Ensure the gateway firmware is upgraded to latest version. 
4) Change the log severity to Debug and replicate the disconnection problem, then download all log files and send them to support@linovision.com.

Description

When working as embedded network server, Linovision LoRaWAN gateways support both sending data packets to third party MQTT/HTTP/HTTPS server or receiving the downlink commands to transfer to LoRaWAN end devices.

Requirement

• Linovision LoRaWAN Gateway: IOT-G56, IOT-G63 V1, IOT-G65, IOT-G67, IOT-G8x (Firmware version 80.0.0.64 or later)
• MQTT Server/Broker
• MQTT Client tool: take MQTT Explorer as example

Configuration

Step1. Connect gateway to MQTT broker.

Refer article How to Connect LoRaWAN Gateway to MQTT Broker？to connect gateway to MQTT broker and ensure the broker and MQTT client can receive uplinks from devices.

Step2. Send Downlink Command from Gateway

Set the gateway to send downlink commands to device directly to check if the device can receive the downlink commands and take actions.

Device EUI: the device EUI to send downlink commands

Type: downlink command type. For Linovision devices, please select hex type.

Payload: downlink command content (get from device manufacturer). For Linovision devices, please refer to downlink command contents on corresponding user guides

Port: application port of device. It is 85 by default for Linovision devices.

Confirmed: after enabled, the device will send confirmed packet back to gateway if it receives the command. If not receive, the gateway will resend the downlink command 3 times at most.

Note: for class A type devices, the gateway will add the command to queue and send it when the class A device send uplinks.

Step3. Publish Topic on MQTT Explorer to send downlink data to device. 

Set a Downlink Data topic. If you need to send MQTT downlink to specific device, please add “$deveui” on the topic.

Example: /linovision/downlink/$deveui

Publish Topic Format :

/linovision/downlink/[devEUI]

Example :

From the gateway, we can get the device EUI about the device we want to control:

So we can publish a topic on the MQTT Explorer like below:

Topic: /linovision/downlink/24e124126a148401

Format: json

Content: 

send as below format and replace the data content as downlink command

{"confirmed": true, "fport": 85, "data": "CQEA/w=="}

JavaScript

After click Publish, we can go to Network Server > Packets to check. If the gateway have subscribe corresponding downlink topic data successfully, there will be at least one grayed message packet record.

Linovision Device Command Examples

The MQTT downlink command format is fixed as below:

{
"confirmed": true,       //Set as true or false
"fport": 85,            //application port of device
"data": "BwAA/w=="    //base64 format downlink command
}

----END---

Description

Linovision LoRaWAN gateways support sending data packets to third party MQTT/HTTP/HTTPS server. We can create a new application on gateway, which can define the method of decoding the data sent from LoRaWAN end-device and choosing HTTP(S) data transport protocol to send data to HTTP(s) server.

Requirement

• Linovison LoRaWAN Gateway: IOT-G6x, IOT-G8x
• HTTP/HTTPS Server

Configuration

Step1. Enable the gateway built-in network server.

Go to Packet Forwarder > General to enable the localhost server address.

Enable the Network server on Network Server > General page.

Step2. Add an Application and Profiles.

Go to Network Server > Applications to add a new application, then click save.

Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Payload Codec: None or custom your decoder

Go to Network Server>Profiles to add a new profile, then click save.

Name: user-defined, arbitrary value

Max TXPower: default value

Other parameters can be checked from LoRaWAN nodes user guides or you can keep all settings by default.

Step3. Add LoRaWAN nodes to the gateway.

Go to Network Server > Device, add a new device, click save&apply.

Device Name: user-defined, arbitrary value

Description: user-defined, arbitrary value

Device-Profile: choose one of corresponding profiles added before.

Application: choose one of corresponding applications added before.

Other values can be confirmed with the LoRaWAN node manufacturers.

When the status of it is “activated”, that’s mean above steps are done correctly.

Step4. Forward data to HTTP(s) server.

Go to Network Server > Applications to add a “data transmission” for the application.

Fill in the HTTP(s) URL information for each data type, click save.

Uplink data: the URL address to receive all uplink data.

Join notification: the URL address to receive join notification.

ACK notification: the URL address to receive all ACK notification.

Error notification: the URL address to receive all error notification.

Note: If there is user credentials when we access to HTTP(s) server, please add HTTP header, and fill in correct account and password.

If we get data packet on the corresponding URL of HTTP server like below, that’s mean we have connected with HTTP server successfully.

Note: The difference of forwarding data to HTTPS server is that you need upload related gateway certification on your HTTPS server (Contact Linovision to get certification).

FAQ

Q1. Why did the server not receive the data sent by the gateway?

A1: Go to Maintenance > Tools > Ping, confirm the gateway can ping to the HTTP address you filled in successfully like below, then check all of above values filled in are correct.

Q2. How to send decoded data packet to HTTP/HTTPS server?

A2: Refer to How to Use Payload Codec on Linovision Gateway.

Q1: Is it possible expand the memory and flash of IOT-G65?

Answer: To upgrade the memory and flash, we will need to re-design and produce the hardware, which take quite a long time. Highly recommend you to contact your sales account for commercial evaluation if you are working on a certain project.

Q2: Could you please let me know when you can include LBT functionality in IOT-G65 LoRa gateway?

Answer: LBT is ready in Linovision sensors. 

Q3: Do you have a LoRaWAN gateway with an on board MQTT broker?

Answer: Currently our LoRaWAN gateway doesn't support as MQTT broker. If you have a certain project that requires this feature, you are welcome to contact us for more information.

Q4:  Is it possible to control the gateway, create/delete device and get last payload from sensor via REST API?

Answer: No. Currently REST API is not available. Our gateway allows to create /update/ remove devices from third party server via MQTT, and obtains the real-time data after the sensor uplinks the data. You can submit ticket to support@linovision.com for more information.

Q5:  Can I use IOT-G65 as WiFi AP with SIM card?

Answer: Yes. IOT-G65 supports WiFi as access point. You can configure it as AP with/without SIM card.

Q6: Is the gateway IOT-G65 compatible with the Thingsboard platform?

Answer: Yes, IOT-G65 is compatible with the Thingsboard. You can submit ticket to support@linovision.com for instructions.

Q7:  I am trying to set the IOT-G65 to access the WAN through the local network. I have changed IOT-G65 Wireless IP address to 192.168.1.100. I need to set the eth0 port IP address as 192.168.1.101 (or similar), with a gateway address of 192.168.1.1 to access the internet through my router. (255.255.255.0). I just get a fail message.

Answer: It’s not possible to configure the WAN IP and wireless IP address under the same subnet 192.168.1.0. You can configure in different subnets.

Q8:  Is it possible to monitor the internal temperature of the gateway?

Answer: The gateway does not install temperature sensor inside the device. The way is to open the case to measure temperature.

Description

The Things Network, a leading provider of LoRaWAN networks and services, is upgrading its stack to v3 (TTS v3). As a leading LoRaWAN end-devices and gateways provider, Linovision’s gateway can be easily connected to TTS, no matter it’s via ‘Semtech Packet forwarder’ or the Basic Station. 

This document will guide you how to connect Linovision LoRaWAN Gateway to TTI/TTS v3 via Semtech packet forwarder. 

If you prefer using Basic Station forwarder, please click here.

Requirement

• The Thing Stack Sandbox Account
• Linovision LoRaWAN Gateway

Configuration

Step1. Login The Thing Stack

Select the cluster according to your gateway location and login TTS using the TTS account/the things ID.

When done, you will see this console page successfully.

Step2. Add Gateway in The Thing Stack

1. Login the web interface of the gateway to check frequency plan. In this example, the frequency plan is EU868.

You will need to take a note of the Gateway ID and Gateway EUI, which is needed when Register a device in The Thing Stack.

The default Gateway ID in Linovision gateway is the same as Gateway EUI. You can change the Gateway ID to yours. In this example, Gateway ID= Linovision IOT-G65, Gateway EUI= 24E124FFFEF1272B. Note that the gateway ID must have less than 36 characters and only use lowercase letters, numbers and dashes(-).

2. Click +Register a Gateway and input the gateway information. Gateway ID and frequency plan are necessary parameters.

Note: The Gateway ID cannot be reuse if you delete it.

When done, the gateway is created well. And you can find gateway server address on it.

Step3. Create the Packet Forwarder in Gateway

For IOT-G65/IOT-G67/IOT-G56:

Go to Packet Forward > General page to create a new destination, select the type as Semtech, input eu1.cloud.thethings.network in this example as the destination and enable this destination.

Click Save and Apply the changes to take effect. 

For IOT-G63:

Go to Packet Forward > General page to select the type as Semtech, input eu1.cloud.thethings.network in this example as the destination and enable this destination. Click Save and Apply the changes to take effect.

You will find it’s connected still in both the gateway and The Thing Stack side.

In the above screenshots, we can see the packets from the gateway.

---END---

Linovision gateways provide multiple backhauls for network connection. Here are the symptoms about failing to access the network via Wi-Fi, Ethernet or cellular.

Symptom 1: Can not access the network via Wi-Fi.
Checklist:
Check if Wi-Fi status shows connected and gateway is assigned an IP by your Wi-Fi router.

1. If not, check if Wi-Fi configuration is correct.
2. If yes,

• Change the main link to WLAN;
  
• Connect a PC or mobile phone to the Wi-Fi access point to check if it works;
• Connect gateway to another Wi-Fi access point.

Symptom 2: Can not access the network via Ethernet Static IP mode.

Checklist:
Go to Maintenance-> Tool -> Ping to ping both www.google.com and 8.8.8.8 to check connection.

1. If only 8.8.8.8 works, go to Network -> Interface -> Port to check whether DNS server is configured. DNS server is used for resolving domain name to IP address.
   
2. If both not work,

• Check if Port setting is correct.
• Check if the IP address you type has been used by other devices.
• Change the main link to eth0/GE0.
  

Symptom 3: Can not access the network via cellular.

Checklist:
1. Check if your SIM card can use in other devices (smartphone, etc.).
2. Ensure you type the correct APN; username, password, PIN code and Roaming are necessary according to your SIM card type.

3. If you use private SIM card, delete or change a private network ICMP server.

If you need any help for deeper trouble-shooting, feel free to contact Linovision Technical Support. 

Description

LoRaWAN gateways can cover a wide range by the CSS chirp with Spreading Factor, the distance can reach 15-20KM maximum. But if it’s in building or in the city installation, the range will be decreased to 2km or so. This guide listed related methods to increase the signal strength of Linovision gateways and nodes.

Solution

Tip 1. Check the gateway’s installed in the right places, it’s recommended in higher places to cover wider range. It should not be covered or influenced by metal materials, especially the LoRaWAN antenna. You can install the external LoRaWAN antenna of gateway and node to obtain higher TX/RX gain

Tip 2. Check whether the antenna of gateway is installed well, the antenna must be installed vertically 

Tip 3. Check whether the antenna type configuration in the gateway is configured well. If external antenna is installed, the configuration should match to get better performance.

You can access the Linovision LoRaWAN gateway web GUI, and go to Packet Forwarder > Radios to check Antenna Type.

Tip 4. Disable the ADR mode of LoRaWAN nodes, and set the SF=12 (at least 10) to get better performance.When the ADR mode is enabled, the SF value may still use 7 for some time. If you are sure the signal is weak, we can configure it like this directly.

If you are using Linovision LoRaWAN nodes, you can configure it by ToolBox LoRaWAN Settings > Basic interface.