Prepare a Gateway connectivity plan to ensure Mesh Gateways connect to the Border Gateway.
All Mesh Gateways need to reliably connect to the Border Gateway to ensure sensor messages are sent to the Silvanet Cloud. To ensure this, we recommend preparing an a Connectivity Plan before deploying the gateways.
This plan is then used by the installers during deployment to run Gateway Connectivity tests.
A reliable Gateway connectivity plan has the following features:
Border Gateway has an Internet connection to the Silvanet Cloud.
Mesh Gateways connect to at least one other Mesh Gateway to provide redundancy.
At least two Mesh Gateways are within range of the Border Gateway to provide redundancy.
The following simplified plan shows a reliable Mesh Network. One Mesh Gateway has one connection while the remaining Mesh Gateways connect to at least two Mesh Gateways.
After you prepare a Connectivity Test Plan, you print it for distribution to forest workers who deploy the devices.
Prepare Packets: Use the Pre-Planning tool to prepare a Packet contains Border Gateways and Mesh Gateways.
Next, enter Full Screen Mode: Select the Full Screen Mode icon in preparation for printing.
Take a screenshot: Take a screen capture (screenshot) of the Packet Planning page in full screen mode. On a MAC, press and hold three keys together: Shift-Command-5 (or Shift-Command-4 to select an area). On a Windows device, press the Windows logo key+Shift+S.
Use a graphics program to add connection lines: Paste the screen capture into a graphics program such as Paint (on Windows) or Preview (MAC OS), or even a Word document. Use the graphics tools to add lines between the Gateways that require connectivity.
Make printouts: Print out copies to be distributed to each deployment team for use during deployment.
Run the connectivity tests between gateways: You can then run a connectivity text on the devices during deployment.
Using the planned locations of the Border Gateways and Mesh Gateways prepared in the deployment Packets, ensure Mesh Gateways are connecting to the Border Gateway before deployment. Use the Connectivity Plan you have brought with you into the forest.
Pausing connectivity tests
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.
To perform range testing, the Silvanet Deployment app needs to be installed on a Smartphone and the Smartphone needs to have a reliable connection to a mobile network.
If mobile connectivity is unavailable in the deployment locations, use a handheld transceiver (portable two-way receiver) to communicate with to a worker who is in a location with mobile network connectivity. This person can then enter the Device ID and location manually.
A Border Gateway requires connectivity to the Silvanet Cloud (via router, mobile or satellite). Consequently, ensuring Border Gateway connectivity is a critical first step.
Scan the Border Gateway QR Code to register the Device ID.
Attach the gateway to a pole or tree and provide it with a power supply.
In the Deployment app, tap Start to test the Border Gateway's connectivity.
The Silvanet Cloud then begins to test the connectivity. This may take some time.
If the Deployment app does not get a response from the Border Gateway, then it is currently in Power Saving mode. You can wait for it to return to Normal mode or cancel the test.
A successful connection is indicated by Device connectivity is good.
An unsuccessful connection is indicated by Device not reachable. The app provides troubleshooting suggestions to fix the connectivity problem.
If unsuccessful, the app provides troubleshooting suggestions, depending on the issue.
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 completing the troubleshooting, rerun the connectivity test.
After a successful deployment, begin testing the Mesh Gateway connectivity.
After a successful connectivity test between the Border Gateway and the Silvanet Cloud, deploy a Mesh Gateway near the Border Gateway (at its planned deployment location), then test its connectivity to the Border Gateway.
After a successful connectivity test between the Border Gateway and the Silvanet Cloud, deploy a Mesh Gateway near the Border Gateway (at its planned deployment location), then test its connectivity to the Border Gateway.
Begin by deploying a Mesh Gateway that is planned to be nearest to the Border Gateway.
Scan the Mesh Gateway QR Code to register the Device ID.
Attach the gateway to a pole or tree and allow it at least one day to fully charge.
In the Silvanet Deployment app, tap Start to begin the 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.
If the Deployment app does not get a response from the Mesh Gateway, then it is currently 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.
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 interfering with the signal, or if all else fails, move the Mesh Gateway closer to active gateways.
After a successful deployment, you can continue with the next Mesh Gateway in the Site.
After verifying connectivity between a Mesh Gateway and Border Gateway, 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.
Once the location is found, tap Install.
Scan the Mesh Gateway QR Code to register the Device ID.
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.
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.
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.
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 interfering with the signal, or if all else fails, move the Mesh Gateway closer to active gateways.
After troubleshooting, the Mesh Gateway should now have two good connections.
In the example shown, the third connection is weak and indicated by a red line. This can be ignored.
After a successful deployment, continue with the next Mesh Gateway in the Site.
