Running connectivity tests

Run connectivity tests to ensure Border Gateways and Mesh Gateways have connectivity before deploying sensors.

Gateway Connectivity Plan

Deploying Border Gateways and Mesh Gateways should be deployed based on the Connectivity Plan the installers should have been provided before entering the forest. This is described in Plan Gateway connectivity.

Border Gateways needs to have Internet connectivity to Silvanet Cloud.
Each Mesh Gateway need to have connectivity with another Mesh Gateway. Connectivity to a second Mesh Gateway provides redundancy.

The Gateway connectivity plan is then used during gateway deployments. The following shows an example connectivity plan.

Prerequisites

Range testing requires the Deployment app running on a Smartphone with connectivity to a reliable mobile network. If mobile connectivity is unavailable in the deployment location, communicate via a handheld transceiver (Walkie-Talkie) to a worker who is in a location with mobile network connectivity.

Border Gateway connectivity to Silvanet Cloud

Without the Border Gateway having connectivity to the Silvanet Cloud via Internet, a sensor has no means of sending messages to the Silvanet Cloud to inform users of potential fires in the forest. Consequently, ensuring Border Gateway connectivity is a critical first step.

Pausing connectivity test

The connectivity test can be paused at any time. For example, when the deployment team finishes the deployment, or wants to pause at the end of the day, tap the Stop button. The app sends a message to the Border Gateway to stop deployment mode and go back to power saving mode

Scan the Border Gateway QR Code to register the Device ID, as described in Deploy Border Gateways.
Attach the gateway to a pole or tree and provide it with a power supply, as described in Deploy Border Gateways.
In the Deployment app, tap Start to test the Border Gateway's connectivity.

Begin connectivity test
The Silvanet Cloud then begins to test the connectivity. This may take some time.

Connectivity test in progress
If the Deployment app does not get a response from the Border Gateway, the Border Gateway is currently in Power Saving mode. You can wait for it to return to Normal mode or cancel the test.
If successful, a message appears indicating Device connectivity is good.

Successful connectivity
If unsuccessful, a message appears indicating Device not reachable. The app provides troubleshooting suggestions to fix the connectivity problem.

Device not reachable
- Check the power supply: Try checking the power supply. Is the PoE cable correctly plugged? Is the solar panel correctly oriented towards the sun?
- Wait for the device to be charged: Allow the Border Gateway to be fully charged. Did you try a connectivity test before it was fully charged or was the device left in a location without sunlight before deployment?
- Find another location: If the Border Gateway is fully charged, it has a good power supply and all the cables are correctly connected, you may need to find another location for deploying the Border Gateway
After troubleshooting, rerun the Connectivity test.
After a successful deployment, you can go ahead and begin testing the Mesh Gateway connectivity.

Mesh Gateway connectivity to Border Gateway

After a successful connectivity test between the Border Gateway and the Silvanet Cloud, deploy the Mesh Gateway nearest the Border Gateway and test its connectivity to the Border Gateway.

Pausing connectivity test

The connectivity test can be paused at any time. For example, when the deployment team finishes the deployment, or wants to pause at the end of the day, tap the Stop button. The app sends a message to the Mesh Gateway to stop deployment mode and go back to power saving mode

Begin with deploying a Mesh Gateway that is nearest to the Border Gateway.
Scan the Mesh Gateway QR Code to register the Device ID, as described in Mesh Gateway deployment.
Attach the gateway to a pole or tree and allow it at least one day to fully charge.
In the Deployment app, tap Start to begin the connectivity test.

Begin connectivity test
The Deployment app sends a message to the Mesh Gateway to broadcast messages to any device that can receive its messages. This may take some time.

Connectivity test in progress
If the Mesh Gateway is in Power Saving mode, you can wait for it to return to Normal mode or cancel the test.
If the Mesh Gateway can connect with the Border Gateway, the map indicates this with a line to the connected device.

Mesh Gateway receives a response from the Border Gateway
If unsuccessful, the app provides troubleshooting suggestions, depending on the issue.

Device not reachable: Check the device orientation towards the sun, wait for the device to be charged, find a more suitable location for the Mesh Gateway (for example, move the Mesh Gateway 60 m closer to another Mesh Gateway, or Border Gateway, and retry the test). Also, if the range test result shows a link but red, this means the Backend can reach the Mesh Gateway but signal is too weak.

Connectivity too low: In this case, the Silvanet Cloud can reach the Mesh Gateway but the signal is too weak. To troubleshoot this problem, check the network map and ensure the devices have been deployed at the correct locations, unmount the Mesh Gateway and check if it has been mounted improperly or something is interferring with the signal, or if all else fails, move the Mesh Gateway closee to active gateways.
After a successful deployment, you can continue with the next Mesh Gateway in the Site.

Mesh Gateway connectivity to Mesh Gateway

After verifying connectivity between a Mesh Gateway and Border Gateway, you can begin deploying the remaining Mesh Gateways and testing connectivity between Mesh Gateways.

Connectivity to other Mesh Gateways

Each Mesh Gateway needs good connectivity to another Mesh Gateway. Connectivity to a second Mesh Gateway ensures redundancy should messages need another route for transmission to the Border Gateway.

Using the deployment plan, deploy the next Mesh Gateway.

Deploy the next Mesh Gateway
Once the location is found, tap Install.

Install the next Mesh Gateway
Scan the Mesh Gateway QR Code to register the Device ID, as described in Mesh Gateway deployment.
Attach the gateway to a pole or tree and allow it at least one day to fully charge.
In the Deployment app, tap Start to begin the connectivity test.

Begin connectivity test
The Deployment app sends a message to the Mesh Gateway to broadcast messages to any device that can receive its messages. This may take some time.

Connectivity test in progress
If successful, the Mesh Gateway received a response from nearby Mesh Gateways and at least one of those responses were good. Weak responses are indicated in red lines.

Successful connection, but with only one Mesh Gateway
If unsuccessful, the app provides troubleshooting suggestions, depending on the issue.

Device not reachable: Check the device orientation towards the sun, wait for the device to be charged, find a more suitable location for the Mesh Gateway (for example, move the Mesh Gateway 60 m closer to another Mesh Gateway, or Border Gateway, and retry the test). Also, if the range test result shows a link but red, this means the Backend can reach the Mesh Gateway but signal is too weak.

Connectivity too low: In this case, check the network map and ensure the devices have been deployed at the correct locations, unmount the Mesh Gateway and check if it has been mounted improperly or something is interferring with the signal, or if all else fails, move the Mesh Gateway closee to active gateways.
After troubleshooting, such as moving the Mesh Gateway closer, the Mesh Gateway now has two good connections. The third connection is weak and indicated by a red line. This can be ignored.

Successful connection with two Mesh Gateways
After a successful deployment, you can continue with the next Mesh Gateway in the Site.