Legacy tools for preparing Packets for deployment
Topics in this section describe the legacy tools for preparing Deployment Packets and planning Gateway Connectivity.
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.
Packets are prepared using the Packet Planning page in the Site Management app. These Packets are then made available in the Silvanet Deployment app.
Whether your Site is a Pilot or a Live deployment, use these guidelines for preparing Packets:
One Packet for Gateways
Several Packets for sensors (ideally, maximum 25 sensors per Packet)
Consider the following guidelines when planning where to place devices on the Map in the Site Management app:
Sensor density: The density of sensors in areas of a Site is based on the human activity in an area and the topology of the forest floor. See Sensor density guidelines.
Density per hectare: This is related to sensor density, except that in this case you need to know where in the forest is the Wildland Urban Interface (WUI) and where are the deep forest areas.
Device ratio: Ensure sufficient Mesh Gateways are deployed for the number of sensors deployed. Similarly, ensure at least one Border Gateway and possibly a backup Border Gateway is deployed based on the amount of Mesh Gateways deployed. See Gateway ratios.
Device range: Ensure sensors are deployed within range of at least one Mesh Gateway. See Sensor range.
Editing Packets
Prepared Packets can be edited to change the Packet's devices or locations. A Packet can also be deleted.
Packets are prepared using the Packet Planning page which displays any previously prepared Packets.
No map displayed?
If no Packet has been prepared, a blank area appears in the Map area. If devices have already been deployed to this Site, a map of the Site and the number of currently active gateways and sensors appears.
Log in to dryad.app.
From the Dashboard select the Sites view.
Open a Site to display the Site Dashboard.
Select Planning to open the Packets page. Any existing Packets appear here.
Select + Add Packet. The Packet Planning page appears with a default location shown in the Map.
Provide a unique name for the Packet in the Packet name field.
After adding a new Packet, find the Site location by centering the map on the Site location using the Search field.
Use the Map tools (zoom in or out, move the map) to find the geographical area (Site location) where the devices in the Packet are to be deployed.
Ensure you have enabled Location services on the Laptop or PC running the Silvanet Site Management app, otherwise no Map appears.
On the Packet Planning page, select Add devices to packet.
From the Device Type dropdown menu, select Border Gateway and enter the number of Border Gateways to add. Select Add.
Repeat the same procedure for Mesh Gateways.
Select Save to save the Packet (you may need to scroll down to see the Save button).
Packets can be saved without placing devices
If the approximate location of the Border Gateway(s) is not known beforehand, you can save the Packet by selecting Save.
Use full screen mode
You can switch to full screen mode to view a larger map.
Placing Border Gateways on the map generates the GPS location for each Border Gateway. Ensure the map is centered on your Site location.
Select the Gateway(s), then select Add devices to map.
The Border Gateway appears on the map as an icon centered in the view.
Drag the Gateway icons to the approximate location of the planned deployment. The GPS coordinates appear next to the device in the list.
Select Save to save the Packet (you may need to scroll down to see the Save button).
Select Back to go the Packet Planning page.
Before building sensor Packets, you need to know the number of sensors required to effectively cover the Site. You also need to consider deployment density when placing the sensors on the Map.
You can create multiple Packets where each Packet contains sufficient sensors for a day's deployment activity. More Packets can be added as required.
Select Add devices to packet and select Sensor.
Enter the number of sensors to add to the Packet, then select Add.
Select Save to save the Packet (you may need to scroll down to see the Save button).
Placing sensors on the map generates the GPS location for each sensor. Ensure the map is centered on your Site location.
Do not place sensors near paths or streets
Plan for sensors to be deployed away from paths or streets. Place the sensors a meter or so away from a path or street to prevent the device from damage due to vandalism.
Select the sensors, then select Place on map. The sensors appear on the map in a default location in the center. The GPS coordinates of the sensors appear in the list next to the devices.
Drag the sensor icons to their respective deployment locations. Ensure you follow the guidelines in Device Ratio and Ranges and Sensor density when placing the sensors. You can view the map in full screen mode for easier placement. Use the standard map tools to move around the map. Distances between the three nearest sensors and the nearest gateway appear when an icon is selected.
Distances between devices highlighted
Select Save to save the Packet, then select select Back to go the Packet Planning page.
Continue preparing additional sensor Packets, as required.
When the required number and type of Packets have been prepared, the new Packets appears in the Packet Planning page and in the Silvanet Deployment app.
Silvanet Deployment app and Packets
New Packets are automatically accessible in the Silvanet Deployment app to all users who have access to the Site. In the Silvanet Deployment app, a user can browse through all Packets prepared for a Site and select the Packet that a team is ready to deploy.
The Packet Planning page allows for a Packet to be modified such as deleting a device from a Packet.
Open the Packet planning page in the Site Management app.
Select a Packet, then select the Pencil (Edit) icon to open the Packet in Edit mode.
From the list of devices, select the devices to be edited.
To update GPS coordinates of a device, select the Pencil icon next to the device, make changes to the Latitude and Longitude, then save the changes.
To delete a sensor or Gateway can be deleted by selecting a device, then selecting Remove.
Select Save to save the changes. A Packet saved message appears.
If required, a Packet can be deleted from the Site Management app.
Deleting a device only removes it from the Packet
If a device has not been deployed, it can be removed from the Packet. However, once a device has been deployed, removing a device requires sending a request to Dryad to remove the device from the Site database. In this case, send a Support Ticket to Dryad with the Device IDs of the devices you have removed from your Site.
Open the Packet planning page in the Site Management app.
Select a Packet, then select the Trash (delete) icon.
Confirm the deletion.
Select Save to save the changes.
Deleting a Packet cannot be undone
Once a Packet has been deleted, it cannot be undone.
