This tutorial guides you through the basic steps of planning a Site, preparing to deploy Silvanet devices and then deploying each Silvanet device type in a forest.

Goal

After completing this tutorial, you should know how to:

• Use the Site Management app to estimate the required Gateways and Sensor to cover a Site

• Use the Deployment app to deploy Silvanet devices in a Site

• View the status of deployed Silvanet devices in the Site view of the Site Management app

Prerequisites

You need the following before beginning this tutorial:

• Login credentials to the Site Management app

• At least one Site provided in the Site Management app

• The Silvanet Deployment app installed on a smartphone

1. Plan the Site

The Planning tool is part of the Site Management app. It is used to estimate the amount and location of Border Gateways, Mesh Gateways and Wildfire Sensors to cover a Site.

Login to the Site Management app (dryad.app)

Your user credentials (Username and Password) give you access to the Dryad Site Management app (dryad.app) and the Dryad Deployment app.

1. Go to dryad.app. Dryad recommends using Chrome.

1. Select Login and then in the Sign In form, enter your username and password.

Select or create a Site

1. In the Site Management app, select Sites view. The Site is where you prepare the deployment plan.

1. If no Site appears, select Create Site.

2. Give the Site a name, select a region, then select Create Site.

Plan coverage estimation

Use the Planning tool to estimate coverage requirements for your site. It is accessed within the Sites view page.

Draw paths (hiking, roads, power lines of higher Sensor density), areas (wide areas of lighter Sensor density) and connectivity zones (mesh network of gateways).

The result is a total number of Gateways and Sensors needed to cover the Site.

1. Run the Planning tool: From the ellipse menu (top-right), select Planning tool.

2. Find a deployment location: Use the Search form to find any suitable location as this is only an example plan.

3. Draw some paths and areas: Look at the map and experiment with the drawing tools.

   1. If you see a trail, railroad or other linear area, use the Draw Path tool to draw a path along the route. Notice the dots along the path. These are estimated Sensor locations. Give the path a name and then try out some of the settings.

   2. For larger forested areas, use the Draw Area tool to follow the perimeter of the area to be protected by Sensors. Notice the dots inside the area. These are estimated Sensor locations. Give the area a name and move the slider to increase or decrease Sensor density.

4. Build up the mesh network using the Connectivity Mesh: This adds Border Gateways and Mesh Gateways. First, add a Border Gateway. Afterwards, select in the blue zone of the Border Gateway and then add a Mesh Gateway. Continue adding Mesh Gateways until the Site is covered. Make sure you select in a blue zone before adding another Mesh Gateway.

5. Optionally, add a few comments: Use the Comment tool to add one or two comments.

6. You can always delete a route or area and add new ones. Just try the tools and get comfortable using the Planning tool.

1. Save your plan using the menu on the upper left of the tool to select Save.

Completed plan

With the coverage estimation completed, it is ready to be exported.

1. Print a Summary document.

   1. Select Export Summary to save the estimation as a printable document (.docx).

   2. After downloading the document, it can be saved as PDF for later printing to be used to deploy the devices.

2. Release the deployment plan to the Dryad Deployment app.

   1. Select Release Deployment Plan to send the deployment plan to the Deployment app associated with your user credentials.

   2. Before releasing the plan, the Planning tool checks if there are any issues that need to be resolved. If found, use the provided troubleshooting information to fix the issues. For example, if a sensor is outside a connectivity zone, fix this by selecting the Sensor icon and moving it inside a blue zone.

   3. After all issues in the Plan have been resolved, release the Deployment plan.

   4. The plan appears in the Deployment app as a new Site.

2. Prepare to deploy Silvanet devices

Required tools for deployment

The following are suggested deployment tools:

• Toolbox to carry all the necessary tools

• Hammer for treenails, chisel to shave off tree bark and shears for trimming branches and for cutting lengths of garden wire

• Binoculars to ensure line of sight between devices

• 10 mm wood drill bit and a 6 mm wood drill bit

• Cordless drill and extra fully charged battery

• Chainsaw for quickly cutting large branches (optional)

• 17 mm wrench used for U-Clamps

• Garden wire for temporary installations

• 16 foot (5 meter) foldable ladder

• Handheld radio (walkie-talkie) or other alternative means of communication for locations with no cell connectivity

3. Deploy Border Gateway

Deploy the Border Gateway to make a connection with the Silvanet Cloud Platform.

Select the Border Gateway in the Deployment app

1. In the Deployment app, tap the Site generated by the Planning tool.

2. From the list of devices, tap a Border Gateway.

3. The Install Device screen appears. Your location is indicated by a blue dot on the map.

1. Using the Deployment app, move towards the deployment location.

Mount the Border Gateway

1. Once at the location, tap Install Device, then go ahead and mount the Border Gateway.

1. Fina a healthy tree or stable pole.

2. Determine the mounting location of the solar panels (towards the sun at noon) and height on the tree or pole of the Border Gateway (3 m) and solar panels (above or below Gateway).

3. Mount the (3) brackets for the Border Gateway and solar panels on a tree (using tree nails) or pole (using the U-Clamps).

4. Attach the Border Gateway and solar panels to the brackets. To secure them against theft, use locks in the holes provided.

5. Connect the cables from the solar panels to the Border Gateway (as well as PoE, if used).

Start registration

1. Tap Confirm and Register Device to begin activating the Border Gateway.

2. Bring the Smartphone running the Deployment app near the NFC logo on the front of the Border Gateway and hold it there for a few seconds.

Connectivity test in progress

Wait about three to five minutes for the Border Gateway to attempt to connect with the Silvanet Cloud.

Check results

1. Tap the NFC tag again to see the results of the Connectivity text.

1. If unsuccessful, follow the troubleshooting information provided in the app, then restart the Connectivity Test.

2. If successful, tap Show Device Details.

4. Deploy Mesh Gateways

Deploy the Mesh Gateways to build up a Silvanet Mesh Network.

Select a Mesh Gateway in the Deployment app

1. From the list of devices in the Site, tap a Mesh Gateway.

2. The Install Device screen appears. Your location is indicated by a blue dot on the map.

1. Using the Deployment app, move towards the deployment location.

Mount the Mesh Gateway

1. Once at the location, tap Install Device, then go ahead and mount the Border Gateway.

1. Find a healthy tree or stable pole.

2. Find the location on the tree or pole that is at a minimum of 3 m above ground level and is oriented towards the sun (at 12:00 noon).

3. Mount the bracket on a tree (using tree nails) or on a pole (using U-Clamps).

4. Attach the Mesh Gateway to the mounting bracket and lock the Gateway to the bracket.

Start registration

Ensure the Mesh Gateway is mounted correctly before starting the registration.

1. Tap Confirm to begin activating the Mesh Gateway.

2. Bring the Smartphone running the Deployment app near the NFC logo on the front of the Mesh Gateway and hold it there for a few seconds.

Connectivity test in progress

Wait about three to five minutes for the Mesh Gateway to attempt to connect with the Silvanet Mesh Network (Border or Mesh Gateways).

Check results

1. Tap the NFC tag again to see the Connectivity results

2. If unsuccessful, follow the troubleshooting information provided in the app, then restart the Connectivity Test.

3. If successful, tap Show Device Details.

Next Mesh Gateways

Use the same procedures to deploy the remaining Mesh Gateways.

We recommend each Mesh Gateway should have connectivity to two Mesh Gateways to ensure a reliable Mesh Network.

5. Deploy Wildfire Sensors

With the Border Gateway and Mesh Gateways deployed, the Silvanet Mesh Network is ready for the deployment of Wildfire Sensors.

The Deployment plan developed by the Planning Tool indicates how many Wildfire Sensors are to be deployed and where each Sensor is to be located.

Select a Wildfire Sensor in the Deployment app

1. Tap a Wildfire Sensor from the list of devices.

2. The Install Device screen appears. Your location is indicated by a blue dot on the map.

3. Move towards the Sensor deployment location.

Mount the Wildfire Sensor

1. At the deployment location, tap Install Device.

1. Select a healthy tree and find a location on the tree that is at least 3 m above the ground level.

2. Use a chisel or axe to remove any protruding bark at the location. Do not overly damage the bark of the tree.

3. At the mounting location, drill a hole approximately 6-7 cm into the tree using the 10 mm wood drill bit. We recommend drilling a 6 mm pilot hole first.

4. Using a tree nail and a spacer, mount the Wildfire Sensor to the tree.

5. Ensure the Sensor is securely attached to the tree.

6. If the Sensor is to be mounted temporarily, use garden wire.

Start registration

1. Tap Confirm to begin activating the Sensor.

1. Bring the Smartphone running the Deployment app near the Sensor and hold it there for a few seconds.

2. After a few moments, the Sensor is registered.

3. When complete, the Installation successful screen appears.

1. Tap Show Device Details. You can add additional information about the deployment location in the Notes field, such as near a campground, in the shadow of a cliff-face and so on.

Calibrate the Wildfire Sensor

Allow the Sensor to fully charge (1 day), then let the Sensor calibrate for 14 days.

Next steps

After calibration, the Silvanet Suite of Gateways and Sensors are now ready for fire detection.

Review the Site details section of a Site in the Site Management app to ensure all Sensors are sending data.

Dryad's Silvanet Suite is designed to detect forest fires in their ultra-early smoldering phase. It consists of a mesh network of , and deployed throughout a Site.

Border Gateways are connected (via the Internet) to the which provides data from the Site's Wildfire Sensors to Dryad's and , including .

Get started now.

Jump in and read our for our new Gen 3 Silvanet Suite to learn how easy Silvanet can be deployed in a Site.

Read the to learn the latest features of Silvanet Suite and Silvanet apps.

In this section

In this section

Any registered user can set preferences for measurement units and date/time formats.

1. Hover over the user profile image (upper-right corner) to reveal a menu, then select Settings.

2. Set your preferences:

   • Unit system: Select Metric or Imperial for measurements, distance, area, temperature, pressure.

   • Date format: Select from either (DMY) dd/mm/yyyy or (YMD) yyyy-mm-dd. Other traditional methods such as mm/dd/yyyy are not supported.

   • Time format: Select 24 hour clock (22:00) or 12-hour clock (10:00 PM).

3. Select the Dryad logo to return to the Dashboard Overview.

Dryad's Silvanet Wildfire Sensors are attached directly to trees using tree nails to detect environmental air quality within a radius of 80 m to 100 m (260 ft to 320 ft).

These solar-powered devices monitor the microclimate of the forest using an internal gas sensor along with a Machine Learning model to detect the presence of a smoldering fire within range of the sensor.

Key features

• Attached directly to trees The Wildfire Sensor is designed with a sturdy loop that allows the device to be attached directly to trees using treenails (permanent attachment) or with garden wire (temporary use only).

• Solar powered Energy is harvested by its built-in solar panel to allow the sensors to operate without the need of batteries. Energy is stored in supercapacitors which provide maintenance-free operation for 10 to 15 years. Storing energy is supercapacitors rather than batteries is a precaution against the device itself starting a fire. As an added benefit, this avoids the use of lithium and other toxic materials.

• Bosch gas sensor The Wildfire Sensor includes a Bosch gas sensor that combines ultra-low-power Air Quality sensing with a precise gas sensing mode. Carbon monoxide, hydrogen and VOCs (Volatile Organic Compounds) are detected at the ppm level with built-in artificial intelligence (AI) to reliably detect a fire and avoid false positives.

• LoRa/LoRaWAN connectivity Connectivity to the Silvanet Network (Mesh Gateways and Border Gateways) is provided by a LoRA-integrated radio to send and receive messages across a robust LoRaWAN-enabled mesh network. This network allows the sensors to be deployed across large forested environments or along linear areas such as rail lines, power lines and hiking paths.

Delivered components

Wildfire Sensors are shipped in a box containing the following components:

• Ten Silvanet Wildfire Sensors

• Ten treenails and spacers (to keep the sensor away from the tree bark)

Dimensions and weight

The dimensions of the Silvanet Wildfire Sensor are (LxWxH) 19 cm x 9.2 cm x 1.34 cm. It weighs 136 g.

Environmental detection

The Silvanet Wildfire Sensor uses a Bosch gas sensor to monitor the microclimate of the forest. It is a low-energy hydrogen sensor that detects the presence of a smoldering fire over distances of up to 115 m.

The gas sensor detects the presence of CO (Carbon Monoxide), H2, (Hydrogen), VOCs (Volatile Organic Compounds) and VSCs (Volatile Sulfur Compounds). It detects VOC and VSC compounds at <20 ppm. It monitors the microclimate of the forest by providing measurements under the following conditions:

• Air pressure: 300hPa to 1100 hPa

• Humidity: 0% to 100%

• Temperature: -40°C to 85°C

Energy harvesting

The Silvanet Wildfire Sensor includes a 60 mm x 60 mm solar cell on its front housing. It continuously generates energy during the daytime and recharges the device with sufficient power for the next 24 hours. After sunset, it begins to discharge until sunrise. After sunrise, it begins to recharge to 100% within about an hour.

Each day the solar panel harvests 7Ws in the constrained conditions of a forest.

As a precaution against the device itself starting a fire, the sensor stores its energy in supercapacitors rather than batteries.

The solar panel provides sufficient energy supply to support continuous operation over a 24 hr period while still having enough reserve power to support the powering of the gas sensor and to send a burst of messages when a smoldering fire is detected.

Energy consumption

The Silvanet Wildfire Sensor has very low energy consumption which is provided by its built-in solar panel. The two key components that consume energy are the gas sensor and the LoRa radio. The gas sensor consumes ~3.9 mA in standard gas scan mode.

The Wildfire Sensor consumes the following energy:

0.7 mW per day (63 Joule per day)

This allows it to operate in a shaded location for ~6 hrs.

Idle/active modes

Normally, the Silvanet Wildfire Sensor is in idle mode. Every 60 seconds it enter active mode to read the air quality. Then, every 2 hours it reads the environment, after which it sends a single packet to the Silvanet Cloud Platform via Mesh Gateways and Border Gateways.

These data packets contain normal (non-fire detection) environmental data which includes temperature, pressure and humidity internal values. These values are then displayed in the Site Details section of the Site Management app.

Supercapacitor Energy Storage

The Silvanet Wildfire Sensor uses a set of supercapacitors to store energy for use by the radio, gas sensor and other components. It stores the energy for day-to-day tasks and has a reasonable amount of reserve power to operate the gas sensor and radio module in case a potential fire is detected. As supercapacitors have an expected lifespan of 10 years or more, the sensors are essentially maintenance free. This allows for an expected lifespan of the sensor between 10 and 15 years.

Supercapacitors have a high capacity but a small maximum voltage of 2.7 V so a series of capacitors are loaded to 4 V. Capacitors are fully charged to 5.2 V.

Calibration

After deployment, the Wildfire Sensor requires 14 days to calibrate. Until then it can generate false-alarms. See Sensor Calibration for details.

Each forest is unique with varied topology and changing terrain such as hills, slopes, rock outcroppings, even mountains, valleys and cliffs. Linear areas such as railroad tracks, power lines, hiking trails can also have the same varied topology. So, each forest can have features that can interfere with reliable transmissions between devices. These challenges are overcome by using Dryad's Silvanet Mesh Gateways.

The Silvanet Mesh Gateway acts as a range extender by using the same Mesh Network used by the sensors to receive and forward messages to other Mesh Gateways and/or Border Gateways.

By forwarding messages, large-scale deployments of Silvanet sensors can be implemented throughout extensive forested areas or along remote stretches of rail lines, power lines and hiking trails.

Key features

• Connects to the Silvanet Mesh Network (including Border Gateways) using LoRaWAN.

• Range between Gateways (Mesh and Border) is typically between 2 km to 6 km depending on topology and physical placement of the Mesh Gateways.

• Low power consumption that allow it to operate using only its solar panel for its daily energy requirements. The power consumption is calculated to be 3997Ws.

• Firmware is remotely updated using FUOTA (Firmware Update Over-the-Air).

• Each Mesh Gateway supports up to 100 sensors.

• Automatically registers with the Silvanet Cloud during the deployment process using the Device ID (scanned using a QR code).

Delivered components

Each shipment of a Mesh Gateway includes the following components:

• Silvanet Mesh Gateway

• Treenails (for permanent deployment)

• U-bolt Clamps, M10 nuts and washers

• 5 meter roll of garden wire (for temporary deployment)

• LoRa antenna (North America: 915 MHz, EU: 868 MHz, Asia: 433 MHz)

Dimensions

The dimensions of the Silvanet Mesh Gateway are (LxWxH) 68 cm (87 cm with antenna) x 29 cm x 5 cm and weighs 2.8 kg.

Large scale deployments

Messages from Wildfire Sensors hop from Mesh Gateway to Mesh Gateway until they reach the Silvanet Border Gateway. This allows for a Silvanet Mesh Network to be extended to a very large-scale deployment consisting of hundreds or even thousands of sensors.

The patent-pending architecture uses a multi-hop mesh network of Mesh Gateways each serving as a standard LoRaWAN gateway to Silvanet Wildfire Sensors.

It is an integrated suite of tools for planning and deploying Silvanet devices, for monitoring Site health monitoring and for identifying the Wildfire Sensors triggering alerts.

The Silvanet Cloud Platform provides a comprehensive set of tools to alert users of a forest fire in its ultra-early stage. The Web-based Site Management app is the starting point for planning a Site while the Smartphone-based Deployment app is used for device deployment.

Amongst other features, the Site Management and Deployment apps are used to access the following tools:

• Site Planning tool in the Site Management app for coverage estimation, including the amount and location of Gateways and Sensors. It results in a printable plan and a deployment plan accessible from the Deployment app.

• Interactive Map that shows the location of Gateways and Sensors on an embedded map. The map provides a fire risk overlay that provides insights into the fire risk of an area.

• Device overview which displays the Sensor data that shows the health of a forest at a glance as it monitors the microclimate including temperature, humidity and air pressure.

• Multichannel alerts to deliver notifications through in-app messages, emails and push notifications to ensure a timely and reliable communication of critical events.

In this section

This tutorial guides you through the basic steps of planning a Site, preparing to deploy Silvanet devices and then deploying each Silvanet device type in a forest.

Goal

After completing this tutorial, you should know how to:

• Use the Silvanet Site Management app to estimate the required Gateways and Sensor to cover a Site

• Use the Silvanet Deployment app to deploy Silvanet devices in a Site

• View the status of deployed Silvanet devices in the Site view of the Site Management app

Prerequisites

You need the following before beginning this tutorial:

• Login credentials to the Site Management app

• At least one Site provided in the Site Management app

• The Silvanet Deployment app installed on a smartphone

1. Plan the Site

The Planning tool is part of the Site Management app. It is used to estimate the amount and location of Border Gateways, Mesh Gateways and Wildfire Sensors to cover a Site.

Login to dryad.app

Your user credentials (Username and Password) give you access to the Dryad Site Management app (dryad.app) and the Dryad Deployment app.

1. Go to dryad.app. Dryad recommends using Chrome.

1. Select Login and then in the Sign In form, enter your username and password.

Select or create a Site

1. In the Site Management app, select the Sites view. The Site is where you prepare the deployment plan.

1. If no Site appears, select Create Site.

2. Give the Site a name, select a region, then select Create Site.

Plan coverage estimation

Use the Planning tool to estimate coverage requirements for your site. It is accessed within the Sites view page.

Draw paths (hiking, roads, power lines of higher Sensor density), areas (wide areas of lighter Sensor density) and connectivity zones (mesh network of gateways).

The result is a total number of Gateways and Sensors needed to cover the Site.

1. Run the Planning tool: From the ellipse menu (top-right), select Planning tool.

2. Find a deployment location: Search for a suitable location using the Search form. You can find any location as this is only an example plan.

3. Draw some paths and areas: Look at the map and experiment with the drawing tools.

   1. If you see a hiking trail, railroad or other linear area, use the Draw Path tool to draw a path along the route. Notice the dots along the path. These are estimated Sensor locations. Give the path a name and then try some of the settings.

   2. For larger forested areas, use the Draw Area tool to follow the perimeter of the area to be protected by Sensors. Notice the dots inside the area. These are estimated Sensor locations. Give the area a name and move the slider to increase or decrease Sensor density.

4. Build up the mesh network using the Connectivity Mesh: This adds Border Gateways and Mesh Gateways. First, add a Border Gateway. Afterwards, select in the blue zone of the Border Gateway and then add a Mesh Gateway. Continue adding Mesh Gateways until the Site is covered. Make sure you select in a blue zone before adding another Mesh Gateway.

5. Optionally, add a few comments: Use the Comment tool to add a comment or two.

6. You can always delete a route or area and add new ones. Just try the tools and get comfortable using the Planning tool.

1. Save your plan using the menu on the upper left of the tool to select Save.

Completed plan

With the coverage estimation completed, it is ready to be exported.

1. Print a Summary document.

   1. Select Export Summary to save the estimation as a printable document (.docx).

   2. After downloading the document, it can be saved as PDF for later printing to be used by forestry workers to deploy the devices.

2. Release the deployment plan to the Dryad Deployment app.

   1. Select Release Deployment Plan to send the deployment plan to the Deployment app.

   2. Before releasing the plan, the Planning tool checks if there are any issues that need to be resolved. If found, use the provided troubleshooting information to fix the issues. For example, if a sensor is outside a connectivity zone, fix this by selecting the Sensor icon and moving it inside a blue zone.

   3. After all issues have been resolved, release the Deployment plan.

   4. The plan appears in the Deployment app as a new Site.

2. Prepare to deploy Silvanet devices

Required tools for deployment

Bring the appropriate deployment tools:

• Toolbox to carry all the necessary tools

• Hammer for treenails, chisel to shave off tree bark and shears for trimming branches and for cutting lengths of garden wire

• Binoculars to ensure line of sight between devices

• 10 mm wood drill bit, 6 mm wood drill bit, cordless drill and extra fully-charged battery

• Chainsaw for quickly cutting large branches (optional)

• 17 mm wrench used for U-Clamps

• Garden wire for temporary installations

• 16 foot (5 meter) foldable ladder

• Handheld radio (Walkie-talkie) or other alternative means of communication for locations with no cell connectivity

Install the Deployment app on a fully charged Smartphone

3. Deploy Border Gateway

Deploy the Border Gateway to make a connection with the Silvanet Cloud Platform.

Select Border Gateway

1. In the Deployment app, tap the Site generated by the Planning tool.

2. From the list of devices, tap a Border Gateway.

3. The Register Device screen appears. Your location is indicated by a blue dot on the map.

Register Border Gateway

1. Using the Deployment app, move towards the deployment location for the Border Gateway.

2. Once at the location, tap Register Device to open the Scanning screen.

3. Scan the device's QR Code to register the Border Gateway.

5. The Registration successful screen appears.

Mount Border Gateway

1. Use treenails (for trees) or U-Clamps (for poles) to mount the Border Gateway 3 m above ground level.

2. Use garden wire to vertically mount the solar panel above the Border Gateway and face it towards the sun (at 12:00 noon).

3. Connect the solar panel to the Border Gateway using the provided cable and connector.

1. If available, use a mains power supply and router, with the PoE Injector. as described in Border Gateway scenarios.

Run Connectivity test

Run the connectivity test to ensure the Border Gateway has connectivity to the Silvanet Cloud.

1. Tap Confirm & Start Connectivity Test to begin.

1. If unsuccessful, follow the troubleshooting information provided in the app, then restart the Connectivity Test.

2. If successful, tap Close or Show Device Details.

4. Deploy Mesh Gateways

With the Border Gateway connected to the Silvanet Cloud, you can begin deploying the Mesh Gateways to build up a Silvanet Mesh Network.

Select Mesh Gateway

1. Tap a Mesh Gateway from the list of devices.

2. The Register Device screen appears. Your location is indicated by a blue dot on the map.

1. Using the Deployment app, move towards the deployment location.

Register Mesh Gateway

1. Once at the location, tap Register Device to open the Scanning screen.

2. Scan the device's QR Code to register the Mesh Gateway.

Mount Mesh Gateway

1. Find the location on the tree or pole that is at a minimum of 3 m above ground level and is oriented towards the sun (at 12:00 noon).

2. Using tree nails (for trees) or U-Clamps (for poles), mount the Mesh Gateway at least 3 m above ground level.

Run Connectivity test

1. Ensure the Mesh Gateway is securely mounted.

2. Tap Confirm & Start Connectivity Test to run a Connectivity test. This test ensures the device has connectivity to the Border Gateway and/or Mesh Network.

3. If the Border Gateway cannot be reached, follow the information provided in the app and restart the test.

4. If the Mesh Gateway can communicate with neighboring Gateways but the signal is too weak, follow the information provided in the app and restart the test.

5. If successful, tap Close or Show Device Details, then go ahead and deploy the next Mesh Gateway.

Deploy next Mesh Gateway

Use the same procedures to deploy the remaining Mesh Gateways.

5. Deploy Wildfire Sensors

Select Wildfire Sensor

1. Tap a Wildfire Sensor from the list of devices.

2. The Register Device screen appears. Your location is indicated by a blue dot on the map.

1. Move towards the Sensor deployment location.

2. Once at the location, find a stable tree that is healthy and unlikely to be cut down.

3. Tap Register Device to open the Scanning screen.

Register Wildfire Sensor

1. Before mounting the Sensor, use the Deployment app to scan the QR Code on the Sensor. This app then registers the Wildfire Sensor.

2. After connecting with the Silvanet Cloud via the Silvanet Mesh Network, the Registration successful screen appears.

Mount Wildfire Sensor

1. Find the location on the tree that is at a minimum of 3 m above ground level. Use a chisel or axe to remove any protruding bark at the location. Do not overly damage the bark.

2. Use a tree nail and spacer to mount the Wildfire Sensor.

1. Ensure the Sensor is securely attached to the tree.

2. Tap Confirm to complete the deployment.

3. The Installation successful screen appears.

1. Tap Close or Show Device Details.

Allow Wildfire Sensor to calibrate

Allow 14 days for the Wildfire Sensors to calibrate.

Next steps

After calibration, the Silvanet Suite of Gateways and Sensors are now ready for fire detection.

Review the Site details section of a Site in the Site Management app to ensure all Sensors are sending data.

Use the Site Management app to plan your deployment of Silvanet and to view Sensor status information.

In this section

Use the Map view to locate Sites on an embedded world map.

Each Site is shown as an icon. Once located, zoom in to view the Site. Choose between 2D/3D Terrain views or add a Fire Risk overlay to the map.

2D/3D Terrain views

Selecting 3D Terrain displays the terrain otherwise hidden hills and valleys (in 2D view) may cause problems with communication between sensors and gateways.

• Toggle to 3D view by selecting the Enable Terrain button.

• Use the arrows to rotate the view.

• Toggle to 2D view by selecting the Enable Terrain button again.

Fire risk overlay

Select the Fire risk icon displays a Fire Risk overlay which shows various levels of fire risk on the map.

The default period is 24 hours. Select a time period for the displayed data sent in a range of 6 hours, 12 hours, 24 hours, 3 days or 10 days.

Deployment steps

Deployment scenarios

The Gen 3 Border Gateway can be deployed using the supplied PoE (Power over Ethernet) to connect to a mains power supply. The solar panels must be connected to the Border Gateway.

The Gen 3 Border Gateway can also be deployed using solar panels only without use of the PoE.

Mount to metal/wood poles

If a 60 mm (2.3 inch) wooden or metal pole is available, use the provided U-Clamps to attach the Border Gateway and solar panels to the pole.

1. Prepare U-Clamps: Place the U-Clamps around the pole, through the mounting bracket and hand tighten the bolts to the U-Clamps.

2. Tighten U-Clamps: After placing the mounting bracket at the correct location on the pole, use the 17 mm wrench to tighten the nuts. Do not use excessive force to prevent damage to the mounting bracket.

3. Repeat for solar panel brackets: Repeat these steps for the two solar panel mounting brackets. The mounting bracket for the Border Gateway can face the Silvanet Mesh Network while the solar panels can be directed towards the sun at 12:00 noon.

4. Mount Border Gateway and solar panel to brackets: Clip the Border Gateway and solar panels to the brackets. You can use locks to secure the devices to the brackets.

5. Attach cables to Border Gateway: Connect the solar panels to the Border Gateway using the supplies cables.

6. (Optionally) Use PoE to provide power: If a mains power supply is available, connect the PoE Injector to the mains.

Mount to trees

If the Border Gateway is attached to tree, the tree must be stable, healthy and and unlikely to be removed. It should survive most typical wind storms.

1. Find a mounting location at least 3 m above forest floor: Once a tree has been selected, use a safety strap to hold the ladder to the tree. Then, with an assistant stabilizing the ladder at the bottom locate a position on the tree that is approximately 3 m above forest floor.

2. Prepare mounting areas: For the Border Gateway and solar panels, remove any branches and other obstructions at the deployment height. This allows the solar panel to have good irradiation from the sun to charge the device. Carefully remove a small portion of the bark with an axe or chisel where the holes in the tree will be drilled. This allows the gateway to hang vertically on the tree.

1. Drill two holes 70 mm apart for top loops: With a distance between the holes at 70 mm, drill approximately 6-7 cm (2 1/5 inches) into the tree for the top loops of the mounting brackets. Ensure you do not split the tree or drill on an angle. Use the 10mm drill bit.

1. Hammer the top treenails into the tree:

   Carefully hammer the treenails through the top loops of the mounting brackets.

2. Drill the bottom holes: With the mounting brackets attached at the top, carefully drill the bottom two holes using the lower holes as templates. Be careful not to damage the bracket while doing so. Also, use a drill bit with a sufficient length to ensure the holes are at the correct depth.

3. Hammer the bottom treenails into the tree: Carefully hammer the treenails through the bottom loops into the tree. Check to ensure the mounting bracket is securely attached to the tree and cannot move.

4. Attach the devices to the mounting brackets: Clip the Border Gateway and solar panels to the brackets. You can use locks to secure the devices to the brackets.

5. Connect the cables: Connect the solar panels to the Border Gateway using the supplies cables.

6. (Optionally) Use PoE to provide power: If a mains power supply is available, connect the PoE Injector to the mains.

Next steps

1. After mounting the Border Gateway and providing it with a power supply, allow the superconductors to fully charge.

2. With the Border Gateway mounted and powered, run the Connectivity Test to ensure the Border Gateway connects with the Silvanet Cloud.

Device status tabs

Devices are sorted into Active, Inactive, Fire Alert and Calibrating tabs. Troubleshooting messages are displayed when expanding a device that shows alerts or warnings.

Device information

For each Border Gateway, Mesh Gateway and Wildfire Sensor planned or deployed in a Site, the following is provided:

Troubleshooting messages

If a device is not responding as expected, alert or warning icons are displayed which notify the user of an underlying issue that needs to be resolved. Expanding device details provides troubleshooting information.

Device not reachable. May be due to connectivity and/or charging issues. These issues need to be resolved immediately to ensure the device continues normal environmental monitoring and returns to Active state.

Silvanet device is currently experiencing delays in sending environmental data to the Silvanet Cloud. However, the device is still monitoring the environment. Fire detection is still operational.

Warning should be resolved as soon as possible to allow the device to return to normal functioning.

Additional information that does not require user-interaction but may affect device performance.

Access roles

The Dryad Site Management app defines two types of users: Standard and Admin, as well as a Reseller role. Access to features of the Site Management app is dependent on the type of user role.

• Admin Users with an Admin role are responsible for team organization. Admins can invite new users, edit user information and independently create new sites.

• Standard Users with a Standard role have access to the platform, can use the User Management app to plan and prepare Sites. They can also update their name and contact details. However, they cannot edit other users' details or invite new users.

• Reseller Resellers can create Admin users for their clients.

User roles and rights

The following table shows an overview of the roles and rights:

Search users

Use the Search field to search for an existing user.

Add new users

You must have Admin rights (or a Reseller) to add new users.

1. From the site menu, select User Management, then select Add User. The New User form opens.

2. Add new user details:

   • First Name (required) and Last Name (required).

   • Email (required): Enter the new user's email address. This becomes the Username.

   • Organization (Reseller only): Select a client from the available options. Resellers can select from multiple clients. Standard or Admin users can only select from a Client to which they belong.

   • Permission level (required): Select from Standard User or Admin.

3. Select Submit to add the new user.

4. Dryad (or Reseller) sends an invitation to the email provided in the form to the new user, such as the following:

This is to inform you that an update request for your account has been initiated by the administrator.

We request you to update your Dryad Networks account by performing the following action(s): Update Password. Click on the link below to start this process. Link to account update This link will expire within 3 days.

If you are unaware that your administrator has requested this, just ignore this message and nothing will be changed.

Best Regards, Dryad Support

1. After selecting the link, the new user enters a new password in the Update password form, then selects Submit.

2. The new user now has access to the Site Management app.

Edit user profiles

Users having a Standard role can ONLY update their own profile, except Email address and Permission level.

Users having an Admin role can update profiles of ALL users in an Organization, except a user's Email address.

1. Select the Edit User icon (Pencil icon) next to a user.

2. In the Edit User form, make changes as required, then select Submit.

Delete a user

Users with an Admin or Standard role cannot delete a user. Currently, only Dryad can delete a user.

Send a request to Dryad Support to have a user deleted.

Run Connectivity Test

Use the Deployment app to begin the Connectivity test to determines if the Border Gateway can connect with the Silvanet Cloud.

1. After mounting the Border Gateway, tap Confirm & Start Connectivity Test.

1. The Silvanet Cloud attempts to reach the Border Gateway. A popup dialog appears over the map with a progress indicator. This popup can be minimized by selecting Collapse Pop-Up.

1. If the Silvanet Cloud could reach the Border Gateway, a Connectivity Test successful message appears. Tap Show Device Details or Close to dismiss the popup dialog.

1. If you have tapped Show Device Details, the following screen appears. You can add additional information in the Notes field.

1. After making changes, close the Device details screen. The changes are then updated in the Silvanet Cloud.

Troubleshooting errors

Border Gateway not reachable

If the Silvanet Cloud could not reach the Border Gateway, troubleshooting information is provided.

1. If the Border Gateway could not be reached, the following dialog appears.

1. Check the following to troubleshoot connectivity:

• Power supply: Check the power supply. Is the PoE correctly connected to mains power source? Is the solar panel correctly connected to Border Gateway, correctly oriented towards the sun (at noon), and no obstructions in front of the solar panel.

• Border Gateway not fully charged: Wait for the Border Gateway to be fully charged. If the device has not had sufficient time to charge its superconductors, wait until it has been fully charged.

• Border Gateway has no connection to a mobile network: It is possible the planned location for the Border Gateway does not have connectivity to a mobile network. In this case, the device needs to be relocated to a location where it has connectivity.

1. After troubleshooting, tap Confirm & Restart Connectivity Test.

1. If you have moved the Border Gateway to a new location, tap Reset Device to Current Location. If the Border Gateway is still in the same location, tap Keep Device Original Location.

1. After restarting the Connectivity Test, the Silvanet Cloud attempts to reach the Border Gateway. If successful, the Connectivity Test successful message appears.

1. Tap Close to dismiss the dialog or tap Show Device Details.

Next Steps

With the Border Gateway now connected to the Silvanet Cloud, Mesh Gateways can now be deployed based on the deployment plan.

If possible, visit the Site and make notes about the natural features such as hills, valleys, rock formations, streams and rivers. Also, note the locations of high human use such as paths or any structures within the site. Use this information when planning deployments.

• Forest variations and density Look for areas of the forest that are lightly or thickly wooded, open areas, bushland and grasslands. Note the density of the trees in various parts of the forest as a thicker forest can have an effect on signal propagation through the forest. Also, take note of how much undergrowth does the forest have and is there evidence of recent unauthorized logging activity which may result in a tree with a deployed device being cut down.

• High human use areas Identify paved roads, lanes, gravel logging roads, hiking trails, woodland paths and other means of traversing through the forest. Where are areas of high human use such as campsites, trailer parks, bridges, power lines or other wooden structures.

• Areas that are difficult or impossible to traverse Note areas that are difficult to hike through to locate deployment positions, such as streams, steep hillsides, ravines, narrow bridges, etc. This may affect the time required to deploy the devices. Note restricted areas where Silvanet cannot be implemented.

• Power supply availability For Border Gateways, identify locations that could provide a mains power supply. Otherwise, the Border Gateway needs to be powered only from its solar panel.

• Mounting poles Ideally Border Gateways should be mounted on poles, but this is not a requirement. Mesh Gateways can also be mounted on poles, if available.

• Topology Mesh Gateways need line-of-sight to communicate with other Mesh Gateways and Border Gateways. Identify areas of the forest topology that might interfere with line-of-sight such as hills, ravines and hidden areas. This may require mounting the Mesh and Border Gateways higher than the recommended 3 meter to as much as 5 or 6 meters. Mounting a Gateway on a hilltop may also be a solution. In all cases, ensure line-of-sight between Mesh Gateways.

Ratio of Wildfire Sensors to Mesh Gateways

100 sensors to 1 Mesh Gateway

For every 100 Wildfire Sensors deployed, use at least one Mesh Gateway or more, if necessary. This is dependent on Site topology which may or may not interfere with connectivity to Mesh Gateways.

Ratio of Wildfire Sensors to Border Gateways

No limit but must be in range:

The Border Gateway does not have a limit on the number of Wildfire Sensors it can support. However, it can support sensors that are within range of the Border Gateway.

In this section

If the Silvanet system detects a smoldering fire, then fire alerts are immediately sent to registered users via email and are displayed in the Site Management app. An MQTT interface is also available for fire alerts.

Fire alert dialog

When opening the Site Management app, if a Wildfire Sensor has triggered a fire alert, it appears as a persistent popup dialog and a blinking Fire Alert icon, regardless of the view currently open. This dialog provides a quick view of the Site and Sensor that triggered the Alert.

Selecting Go to Alert Center opens the Alerts overview page. Selecting Mute Alerts hides alerts triggered from the Sensor identified in the Fire alert dialog. Alerts from other Sensors continue to appear.

Fire alerts sent via email

When a sensor detects a fire, a fire alert email is immediately sent to registered users who can then act to extinguish the fire.

MQTT interface for fire alerts

An MQTT interface is available for 3rd party alarm interfaces / apps.

Current alerts

The Alerts overview shows an All Clear indicator if all Sites to which you have access have not triggering any Fire alerts. This page is automatically refreshed.

All alerts that have not be attended to are shown in the Current Alerts tab.

• Site name (Filter): Site which triggered the Fire alert. Select the Filter icon to sort the list by Site name.

• Site ID: ID of the Site as shown in the URL.

• Detected At: Time and date when the Fire alert was triggered.

• Cleared At: Shows time and date if the Fire alert was cleared. Otherwise shows Ongoing.

• Sensors Triggered: Number of Sensors that triggered the Fire alert in a given Site.

• Status: Current status of the alert. Options include

  • Fire Alert: An actual fire, which needs to be attended to immediately.

  • Alert Time Out: An alert was not attended to (for example, cleared) and no other alerts were sent by the Sensor in the past 6 hours, the alert times out.

  • False Alert: An alert labelled as

  • Fire Test: Labelled as the result of a fire test.

• Open icon: Opens the alert in the Alert details page.

Alert details page

Selecting a Fire alert from the Current alerts tab opens the Alert details page in a new window. It lists all Wildfire Sensors in a Site that triggered the alerts.

This page provides specific actionable details of the alert, including the location of the fire as displayed as a dropped pin in Google Maps. This shows precisely where the fire was detected.

• Type (sortable): Indicates type of alert:

  • Fire alert: Indicates a Phase 2 alert, which the Sensor has determined a developing fire as the most likely cause of the deterioration in air quality.

  • Warning: Indicates a Phase 1 alert, which is a decline in air quality in the surrounding area. It may be an indication of a developing fire or a fire outside the range of the Sensor.

• Sensor: Descriptive name of the Sensor as assigned by Silvanet Cloud.

• Detected At (sortable): Time the alert was triggered and sent by the Sensor.

• AI index: Air quality index. >85% indicates a Phase 3 alert (Fire alert), which a value lower than 85% (<85%) indicates a Phase 2 alert (Warning).

• GPS Coordinates: Latitude and Longitude of the Sensor triggering the alert.

• Location: Opens a map (Google Maps) with a pin showing the location of the sensor that triggered the fire alert. If Google Maps is not installed, it launches a browser and opens Google Maps in the browser.

Clear alerts

A fire alert can be cleared after it has been resolved.

1. From the Alert Center, select an Alert to open the Alert details page.

2. Select Clear Alert.

3. In the dialogue that appears, choose a reason for clearing the alert:

   • Fire Extinguished: Detected fire that caused the fire alert to be sent has been extinguished.

   • Test Alert: Alert sent during testing the deployment with a controlled burn.

   • False Alert: Alert sent during the sensor calibration phase.

4. The alert is cleared from the Current Alerts tab and moved to the Past Alerts tab.

5. After all alerts are cleared, the Alert Center shows an empty list.

Past alerts

In Alerts overview, the Past Alerts tab lists cleared Fire alerts.

• Site name (Filter): Site which triggered the Fire alert. Select the Filter icon to sort the list by Site name.

• Site ID: ID of the Site as shown in the URL.

• Detected At: Time and date when the Fire alert was triggered.

• Cleared At: Shows time and date if the Fire alert was cleared. Otherwise shows Ongoing.

• Sensors Triggered: Number of Sensors that triggered the Fire alert in a given Site.

• Status: Current status of the alert. Options include

  • Alert Time Out: An alert was not attended to (for example, cleared) and no other alerts were sent by the Sensor in the past 6 hours, the alert times out.

  • False Alert: An alert sent to indicate no fire detected although an alert was triggered.

  • Fire Test: Labelled as the result of a fire test.

• Open icon: Opens the alert in the Alert details page in a new tab.

Run the Deployment app to find the planned deployment locations. Use it to register the Device ID and then after mounting the device, use it to test connectivity.

Install the app

1. Search for Silvanet Deployment on your Smartphone's App Store or Google Play, then install the app.

1. Ensure you have given the Silvanet Deployment app the appropriate permissions, including Location and Cellular Data.

Sign in

• Open the app, then in the Sign In screen enter your user credentials and tap Sign In. If required, you can change the language used.

Select a Site

1. After signing in, the Select Site screen appears. It displays all Sites to which you have access. Any Site within your Organization is displayed in the Silvanet Deployment app.

1. From the list of Sites, tap a Site or arrow to open the Site. The Site's devices appear.

Device list

The Device list shows all planned and/or deployed devices for a Site.

For each device in the Site, the app shows:

• Name of device.

• Packet in which the device was added.

• Status of device (see below).

• Link (arrow) to open map show location of the device.

• Button to show all devices on the map.

Device status icons:

• Planned (all devices): State of device after a Silvanet device has been added during a Site planning. The device has not yet been deployed.

• Registered (all devices): State of device after scanning the QR Code.

• Connectivity Test Running (Border and Mesh Gateways): State of a Gateway if it's currently running a connectivity test.

• Connectivity Test Failed (Border and Mesh Gateways): State of a Border or Mesh Gateway if a Connectivity test fails between two Gateways. Reasons for the failure could include insufficient sunlight to charge the device, the device is currently charging or the device may need to be relocated.

• Deployed (Border and Mesh Gateways): State of a Border Gateway or Mesh Gateway after the installer has performed Connectivity tests and the device is connected to the Mesh Network.

• Deployed (Wildfire Sensors): State of a Wildfire Sensors after the installer has confirmed the device has been correctly mounted.

Device filter

The Deployment app provides a selection of filter to find specific devices. You can filter the devices by:

• Device type

• Status

• Deployment Packet

Tap a filter, then top Apply to view only the selected devices in the list. To view all devices again, tap Clear which clears the filter.

Map view

The Map view shows devices as Status Icons.

• Specific device: To view the location of specific device, tap the link to a device on the Site page. The map opens with the device selected at its planned or deployed location on a map. The Status Icon shows the state of the device.

• All devices: To view the Site to show all devices, tap Show Devices on Map on the Site page. Zoom or pan on the map in to locate specific devices.

Deploying a Silvanet Network in a forest is typically a two-stage process:

• Pilot (2 - 4 months): Small-scale deployment of up to 400 sensors that demonstrates Silvanet's scalability and Mesh Network to detect controlled test fires.

• Live (10-15 years): Large-scale deployment of the required Wildfire Sensors and Mesh/Border Gateways across a targeted forest area (the Site).

Pilot deployments

A Pilot deployment validates Silvanet System's core functionality and scalability. This type of deployment typically monitors an area of about 400 to 500 hectares (approximately 1000 acres to 1250 acres).

Use the to determine the required number of Wildfire Sensors, Border Gateways and Mesh Gateways.

• 400 Wildfire Sensors Garden wire can be used to temporarily mount the Wildfire Sensors to trees. Sensor spacing should be from 80m to 100m.

• Four to eight Mesh Gateways For an area of 400 to 500 hectares, deploy at least four up to eight Mesh Gateways, depending on the terrain and RF signal propagation conditions (line-of-sight).

• Topology and forest density determines number of Mesh Gateways Hilly areas need more Mesh Gateways. Less dense and relatively level forest floors need less Mesh Gateways where 4 should be sufficient.

• One Border Gateway Only one Border Gateway is typically needed. Additional Border Gateways can be added for redundancy.

Live deployments

A Live deployment can use the results of a Pilot deployment (but not necessarily) to determine the number of sensors and gateways needed to effectively cover the entire Site.

• Site dimensions The size of the Site in hectares determines the number and type of Silvanet devices to effectively cover the Site area.

• Topology and forest density determines number of Mesh Gateways Mesh Gateways require line-of-sight between other Mesh Gateways. Hills, ravines and other aspects of the topology may interfere with line-of-sight. Mounting Mesh Gateways higher than the recommended 3 meters or even mounting them on a hill may increase line-of-sight.

• Effect of interactions on sensor calibrations Emissions from vehicles on lanes and roadways may interfere with Wildfire Sensor calibrations. Similarly, human interactions with the devices can be reduced by placing them away from roadways and hiking trails.

• Device ratios Use the follow (maximum) device ratios:

  • Ratio of Wildfire Sensors to Mesh Gateways is 100 to 1.

  • Ratio of Mesh Gateways to Border Gateways is 20 to 1.

• Wildfire Sensor density Distances between Wildfire Sensors is based on human activity and the Wildlife Urban Interface:

  • For areas of high human activity, distances between Wildfire Sensors should be no further than 100 meters between devices.

  • For areas of low human activity, distances between Wildfire Sensors can be increased to 400 meters to 500 meters between devices.

• Prepare installation plans Consider how the deployment teams must traverse the forest so they can efficiently use the time. With such a large deployment area, several teams of two workers may be required to deploy all the sensors. Ensure you prepare one site Packet per team, considering how the team must navigate through the forest.

The range of a Border Gateway to a Mesh Gateway is approximately 2 km to 3 km.

At approximately 2 km to 3 km, Mesh Gateway to Border Gateway range is similar to Mesh Gateway to Mesh Gateway.

The actual range between Gateways may vary depending on the Site topology. With direct line of sight between Gateways, the range can exceed 3 km or even up to 8 km (during conducted tests).

Sensor density per hectare is based on:

• Human activity level in specific areas of the forest

• Presence of WUIs (Wildland Urban Interfaces) in the site

By determining these factors, you can approximate the density values per hectare (Metric) or acre (Imperial).

Using this approach of variable density (low and high sensor density), you can reduce the overall cost of deploying the Silvanet System in the Site while maintaining good wildfire detection.

Human activity level

Locations with high human activity require dense deployment of sensors. These include Sites that have hiking paths, campsites, roads, railroad tracks, wooden bridges, poles and power line towers, residential housing and other types of buildings. Low human activity areas include deep within forested areas, hillsides or hard to access locations.

The following table shows the recommended sensor density values.

Wildland Urban Interface (WUI)

A Wildland Urban Interface (WUI) is defined as areas of a forest where wildland and urban areas intersect. It is the line, area or zone where structures and other human development meet or interspersed with undeveloped wildland or vegetative fuels.

Warnings

Deployment overview

• Ensure correct range

  • 1 km to nearest Mesh Gateway: Ensure a Mesh Gateway is within range, which is no further than 1 km from the Wildfire Sensor.

• Sensor density

  • WUI: 0.7/ha to 0.1/ha Based on WUI (Wildland Urban Interface), Dryad recommends 0.7/ha sensors for a dense WUI and 0.1/ha sensors for a sparse WUI. Spacing between sensors should be 80 m to 100 m for areas of high human activity, 400 m to 500 m for areas of low human activity.

• Mount Wildfire Sensor correctly

  • Select a healthy, stable tree: The tree should be closest to the GPS coordinates set for a sensor using the Silvanet Deployment app. Also, ensure the tree is healthy and not likely to fall over or be harvested.

  • Above 3 m above forest floor: Install the sensor on the tree approximately 3 meters above the level of the forest floor. At this height, the device is most sensitive to fire detection and obtains an increased amount of light on its solar cell. Furthermore, at this height it avoids disturbances from most human and animal interactions.

  • Towards sun (at noon): The sensor needs to be oriented towards the direction of the sun (where it would be at 12:00 noon). Use a compass to identify true South (in the northern hemisphere) or true North (in the southern hemisphere). This maximizes the amount of light that hits the solar panel.

  • Use the spacer correctly: A 2 cm spacer is provided to deploy the sensor slightly away from the trunk of the tree. This avoids direct contact with the tree and allows tree sap to flow down the tree behind the sensor. The spacer also helps keep the sensor away from the moisture in the tree. Furthermore, the spacer allows the sensor to hang vertically rather than laying directly against the bark of the tree which could cause it to tilt at an angle. Also, hanging the sensor vertically improves the radio range of the device.

Overview

• Inform the local fire department of the fire test

• Use a realistic test location

• Use homogeneous material

• Burn a realistic test fire

• Ensure the test fire burns for at least 30 minutes

• Take note of smoke behavior

• Allow a four-hour gap between test fires

Inform local fire department

Before burning the test fire, ensure the local Fire Department and relevant authorities are notified of the test fire. Also, ensure a test fire is permitted.

Use a realistic test location

We strongly recommend running the fire test in a location that is similar to the Pilot or Live deployment. Do not run the test in a location that is vastly different from the intended deployment location.

For example, running a test fire in an urban parking lot causes discrepancies. Wildfire Sensors are primarily forest sensors and urban areas can affect the functionality.

Use homogeneous material

Use a collection of homogeneous plant material (uniform in size and composition) for the test fire. Material should be of various sizes all of which are fast-burning branches or twigs but not logs.

Review the requirements for plant material in the following table.

Burn a realistic test fire

To reflect conditions of real wildfires, the test fire should not diminish as the test runs, nor should the test fire resemble a BBQ fire.

As the wind direction cannot be controlled, provide sufficient time for smoke from the test fire to hit one or more Wildfire Sensors.

Ensure test fire burns for at least 30 minutes

Ensure you continually feed the fire with material to keep the fire burning for at least 20-30 minutes to allow smoke from the test fire to reach one or more Wildfire Sensors. They are designed to detect fire at the smoldering phase - before there is an open fire.

Normally, detection time is within minutes (less than 1 hour from ignition). This is dependent on fuel volume, wind speed and wind direction. A denser deployment will decrease the time to detection and detection rate.

Take note of smoke behavior

Because wildfire smoke behaves differently in different locations, select a location that is realistic and reflects the final deployment environment.

A parking lot, work yard or an urban area may not be the best location for a setup although it may be convenient. The results of a test in those type of locations would not be very useful. For example, under a forest canopy, wind behavior is different from wind behavior in an open area such as a work yard.

Four-hour gap between fire tests

When performing fire tests, repeatedly lighting a fire and checking the response in short time interval (less than 1 hour) results in poor Wildfire Sensor performance.

The sensor needs a 1-hour time window to settle and restore fire detection sensitivity.

Prepare Deployment app

• Ensure the Smartphone is fully charged: Smartphones need to be fully charged. Bring a backup power supply.

• Ensure Deployment app is installed: Make sure the Deployment app is installed on the Smartphone and you have signed in to the app. Also, ensure the app has been given Location and Cellular Data permissions.

• Launch Deployment app while the Smartphone has good mobile connectivity: Launch the Deployment app while you have a good wireless connection. This allows the app's local database to be updated with device information. Mobile connectivity may become unreliable in areas of the Site.

• Open the relevant Site in the Deployment app: Before entering the forest, open the Site in the Deployment app. For details, see Deployment app.

• Cache the Map: From the respective Site, load the Map view to cache the map. This ensures you have access to the Map view should a mobile connection become poor or unavailable.

• (Optional) Bring handheld transceivers: If mobile connectivity is unavailable in the deployment locations, use a handheld transceiver (portable two-way receiver) to communicate with a worker who is in a location with mobile network connectivity. This person can then enter the Device ID and location manually.

Suggested deployment tools

• Bring sufficient devices for a day's work: Before going to the forest, ensure you have the correct number of devices, spacers, treenails and garden wire (if required) for deploying devices for a day's work.

• Carefully carry devices while in the forest: Carry the required number and type of Silvanet devices in a strong backpack or toolbox.

• Use toolboxes for the required devices and tools: Use a waterproof toolbox to keep the devices safe and dry while in the forest. Use another toolbox for the required tools. For details, see Deployment tools.

• Bring a folding ladder: Provide a 16-foot (5 meter) ladder for installing sensors and gateways. A folding ladder is easier to carry through the uneven ground of a forest.

• Use sturdy workboxes: Provide a workbox or backpack for carrying devices, depending on how many and type of devices are planned for a day's deployment.

• Suggested tools for device deployment:

  • Hammer for treenails, chisel to shave off tree bark and shears (snips) for trimming branches (if required) and for cutting lengths of garden wire

  • Binoculars to ensure line of sight

  • Compass (analogue or an app on the Smartphone)

  • Cordless drill (min 18V) as well as a backup battery pack

  • 10 mm wood drill bit and a 6 mm wood drill bit (optional) to drill a pilot hole to prevent splitting, especially with hardwood trees

  • 17 mm wrench for the U-clamp bolts

  • Garden wire for temporary installations

  • Pencil and notepad

  • Backup power supply for Smartphones

  • Walkie-talkie or other alternative means of communication for locations with no cell connectivity

Learn how to use the Planning tool to prepare a coverage estimation for a Site with these step-by-step instructions.

Goal

In this tutorial, you will use a random Site location to draw three paths (hiking, power line and roadway paths) and three areas (including an inaccessible area) and then add connectivity zones (Border Gateway and Mesh Gateways). You can then add some comments to the plan

When completed, you then export a summary document and release the deployment plan.

Prerequisites

To complete this tutorial, you need to complete the following prerequisites. You can skip ahead if you've already completed these tasks:

• Access credentials to the Site Management app. Contact Dryad Sales if you don't already have one.

• Deployment app installed on your Smartphone.

• You have created a Site in the Site Management app. If you haven't already done so, you can learn how to create a Site here.

Find the Site location

Find a random Site location. This would be where the Silvanet Gateways and Wildfire Sensors are to be deployed.

You can select any location as an example. In this tutorial, we make a plan to deploy Silvanet in an area in northern British Columbia, Canada. It includes a deep valley, thick forests, a settlement, power lines, roadways and forestry paths.

1. From the Site view, select Planning tool from the ellipsis menu (upper-right corner).

2. In the Planning tool use the Search field to find the deployment location.

3. Save your project.

Draw three paths

Use the Draw Path tool to define high density areas the Site. They can be set as hiking paths, power lines, roads or railroads.

Draw a hiking path

1. Create a path: Select the Draw Path tool, then begin the path by selecting the starting point and dragging the path along the route. End the path by double-clicking on the map. Notice the white dots. These are the locations where the Planning tool determined where to place the Wildfire Sensors in the path.

2. Describe the path: In the Path Settings panel shown on the left enter the following information:

   • Name: Enter a descriptive name.

   • Path type: Select Hiking Path

   • Protection Level: Select Mid. The slider is used to determine Wildfire Sensor density (Low, Mid, High). The distance between Sensors affects the amount deployed. The higher the protection level, the shorter the distance between Sensors.

3. (Optional) Add Wildfire Sensors to path: Select Manual Planning, then select Add Sensor. Try placing an additional Sensor icon somewhere in the path. Notice the Sensor number incremented by 1.

4. Save the project

Draw a power line path

Add another path but In this case select Power Line from the Path type dropdown. Notice how the Planning tool wraps each power line tower with four Sensors.

Draw a roadway path

Add the third path but in this case select Roadway from the Path type dropdown. Notice the increased density of Sensors for a roadway compared to a hiking path.

You should now have three paths shown on the map.

Draw three areas

Use the Draw Area tool to define lower density areas of the Site. It also can be used to define inaccessible areas within the Site.

Add the first area

Find an area on the map to add the first of three areas. In this case, we use the area that includes a valley, a hillside and areas that are sparsely wooded. It follows the contours of the hiking path and crosses the power line path. We call it the North ridge.

1. Create an area: Using the Draw Area tool, begin the area by selecting a start point, then drag the path along the boundary of the area and then double-click on the map to complete the area. Notice how the Planning tool placed Sensors. These locations are automatically generated.

2. Describe the area: Enter the following information in the Path Settings panel:

   • Name: Enter a descriptive name.

   • Surface area: This is automatically generated.

   • Accessible: For this area, do not select this. This slider sets the area as inaccessible (such as private property, military area, restricted area).

   • Protection Level: Select Mid. Use the slider to determine Wildfire Sensor density (Low, Mid, High). The distance between Sensors affects the amount deployed. The higher the protection level, the shorter the distance between Wildfire Sensors.

3. Save the project.

Draw a second area

Add a second area is on the opposite side of the hiking path and crosses the power line path. We call it the South ridge.

1. Use the same procedure as for the first area to add a second area. Give it a unique name.

2. Use the same Area settings as the first area.

3. Save the project.

Draw an inaccessible area

In this area, define an inaccessible area. This is an area that is off-limits and cannot be used to deploy Sensors. Use the Draw Area tool to define this area but in this case, slide the Accessible selector to Off. The area then is defined without Wildfire Sensors.

1. Select the Draw Area tool and define this area using the same settings as the other areas but set the Accessible slider to off. This makes the area inaccessible and no Sensors are added to the area.

2. Save the project.

Add connectivity zones

Use the Plan Connectivity tool to define connectivity zones. Each zone (shown in blue) represents the areas around Border Gateways and Mesh Gateways where Wildfire Sensors can connect to the Gateway.

Connectivity zones have the following properties:

• Blue overlay: The line-of-sight of the Gateway is indicated by an irregular blue overlay that shows areas where the Gateway has connectivity.

• Open areas: Open areas in the connectivity zone indicates topology that prevents signals from reaching those areas. These areas require additional Mesh Gateways. They must be added within existing blue areas.

Add a Border Gateway

First add a Border Gateway. Look for a location at the forest edge where the Gateway can expect clear line-of-sight to mobile towers and free of trees or structures to ensure good solar radiation on the solar panel. If a structure is available that can provide a mains power supply, place the Border Gateway nearby the structure.

1. Select the Plan Connectivity tool.

2. Place a Border Gateway on the map.

3. The first Gateway is defined as a Border Gateway. Ensure Border Gateway is selected from the Gateway Type.

4. The GPS location of the Border Gateway is automatically generated.

5. Save the project.

Add Mesh Gateways

Use the Plan Connectivity tool to add a Mesh Gateway.

1. Add a Mesh Gateway using the same procedure as adding a Border Gateway but select Mesh Gateway from the Gateway Type. You must place the Mesh Gateway within the blue connectivity zone of the Border Gateway.

2. Save your project.

Add additional Mesh Gateways

1. Continue adding more Mesh Gateways until the Site has sufficient network coverage (minimum 95%)

1. Use the same procedure to add more Mesh Gateways until you see the Network Coverage progress bar reaching at least the 95% connectivity threshold. Ensure Mesh Gateway is the Gateway Type.

1. Save your project.

Add a comment

Add a few relevant comments to the map. They can be anything you notice about the terrain, the amount of human activity, anything you think needs to be noted directly in the plan.

Release Deployment Plan

When you are satisfied with the deployment plan, generate the Packets for use by the Silvanet Deployment app. You do this by releasing the deployment plan.

1. Select Release Deployment Plan.

2. The Planning tool may find problems with the plan: If the Planning tool identifies issues with the planned locations of Sensors and Gateways, it prevents Packets being generated. Go through the list of issues and fix them.

1. Example issue - unconnected Sensor: In this example a Sensor was placed outside a Connectivity Zone. You need to move the Sensor within the nearest blue zone. In the example below, notice the Sensor placed outside a connected area. After moving this Sensor a few meters into the Connectivity Zone, it resolved this issue.

1. Issues resolved: With all issues resolved, the Deployment Plan is ready to be released. Select Release Plan to generate the Packets. You can now find the Packets in your Deployment app under the same Site you used to start the Planning tool.

1. Save your project.

2. Select Quit to close the Planning tool.

Export Site Summary document

An editable .docx file can be exported for use during deployment.

1. From the Planning tool, select Export Summary.

1. Save to a local drive for use by Silvanet device deployers.

In this section

Mesh Gateways allows data from distant Wildfire Sensors to be received by a Border Gateway which is typically deployed where it has good wired or wireless connectivity.

Deployment overview

Deployment locations

After using the Planning tool, the GPS locations of each Mesh Gateway is determined by adding Mesh Gateways (Connectivity zones) to ensure a minimum of 95% network coverage. For example, in the Planning tool tutorial, the location of one of the Mesh Gateways was determined as shown.

In the Exported Summary document shows the planned location. The forest worker can use this file to deploy the Border Gateway in the Site.

The location of the Mesh Gateway should meet the following minimum conditions:

• Line-of-sight to Border Gateway or Mesh Gateway: Whether the Mesh Gateway is installed on a tree or pole, it needs a line-of-sight to at least one other Mesh Gateway (or Border Gateway if within range).

• Access to sufficient sunlight: To ensure the Mesh Gateway's solar panel has sufficient daylight to charge the Gateway's supercapacitors.

• Mounted in an elevated location: To maximize range, install the Mesh Gateway in a location than is higher than the surrounding area, if possible. If not, the Mesh Gateway can be installed at 5 m on a pole or 10 m on a tower.

Ensure correct range

• 2 km to 3 km to Border Gateways: The range of Mesh Gateways to Border Gateway is approximately 2 km to 3 km. Deploy at least one Mesh Gateway at least 2 km to 3 km from a Border Gateway. The distance is dependent on topology and type of forest.

• 2 km to 3 km to other Mesh Gateways: Each Mesh Gateway can be up to 3 km from other Mesh Gateways, depending on the topology and height at which the device has been deployed on a tree. Actual range my depend on environmental conditions.

• Ensure connectivity between two Mesh Gateways: Ensure each Mesh Gateway has connectivity to two other Mesh Gateways, or one Mesh Gateway if no other is within range.

• Line-of-sight: Ensure the Mesh Gateway has line-of-sight to at least one other Mesh Gateway.

• Maximum 1 km radius from Wildfire Sensors: Place Mesh Gateways in locations that enable them to cover nearby Wildfire Sensors in a radius of approximately 1 km.

Mounting guidelines

• Use a stable metal or wooden pole: If the Mesh Gateway is mounted to a metal or wood pole, ensure it is stable and is unlikely to be moved. Use the provided U-Clamps to securely attach the mounting bracket to the pole.

• 60.3 mm pole diameter: The diameter of a pole must not be greater than 60.3 mm. A 17 mm wrench is used to attach the M10-nuts to the U-Clamps.

• Mount at least 3 m high on pole or tree: Mount the Border Gateway at least 3 m high on the pole or tree and, if possible, higher for better signal propagation. Options in the Planning tool include 3 m standard, 5 m pole or 10 m tower.

• Use only healthy trees: When mounted on a tree, ensure it is healthy and unlikely to be removed.

• Clear away obstructions:

  • The Mesh Gateway's solar panel needs an unobstructed area to obtain sufficient sunlight to charge the Gateway's superconductors.

  • If the Mesh Gateway is installed on a tree, the solar panel should not be covered by branches.

  • Clear small branches away from the solar panel. Do not cut large branches, however.

• Mount facing sun at 12:00 noon (northern or southern hemisphere):

  • Use a compass to identify true South (in the northern hemisphere) or true North (in the southern hemisphere). This maximizes the amount of light that hits the solar panel.

  • Select a location with direct sunlight (such as a hillside) and keep it free from branches that obscure direct sunlight.

• Mount on a hillside, if possible: To increase connectivity, mount the Mesh Gateway on a hillside.

Mesh network reliability

In the following example, a message from a Wildfire Sensor has several routes to the Border Gateway. This ensures reliability in the network.

Border Gateways are designed to be deployed at the edge of the forest on a pole, tree or permanent structure. The Gateway needs to be free from obstructions, such as branches and structures. It also requires a reliable power supply and access to Internet connectivity.

Deployment overview

Deployment scenarios:

• Wired (mains and router): Uses mains power supply and a router.

• Wireless (mains and mobile network): Uses mains power supply and mobile networks.

• Wireless (solar and mobile networks): Uses solar panels only and cellular networks for Internet connectivity.

• Satellite (solar only): Uses solar panels only and satellite connectivity.

Deployment locations

The Planning tool is used to determine the Latitude and Longitude the Border Gateway. For example, in the Planning tool tutorial, the location of the Border Gateway was determined as shown.

The Exported Summary document shows the planned location in detail. The forest worker can use this document to deploy the Border Gateway in the Site.

The location of the Border Gateway should meet the following minimum conditions:

• Have clear line-of-sight for mobile connectivity: Whether the Border Gateway is installed on a tree or a pole, it needs a clear line of sight for mobile connectivity or, if used, to connect without obstructions for satellite communication.

• Access to mains power supply (if available): If the Border Gateway can be powered by a mains available in a building such as a maintenance workshop, this provides a reliable 24-hour power supply.

• Near the edge of the forest: Deploying a Border Gateway near the edge of the forest ensures that it has a clear line of sight for mobile connectivity, satellite and at least one Mesh Gateway.

• Access to sufficient sunlight: By placing the Border Gateway at the edge of the forest, this ensures it has sufficient daylight free of obstructions to charge the Border Gateway's supercapacitors.

• Ideally, mounted in an elevated location: To maximize range, install the Border Gateway on a hill, or at least a higher location to maximize range, such as 5 m or 10 m.

Range to Mesh Gateways

• 2 km to 3 km to Mesh Gateway: The range of a Border Gateway to a Mesh Gateway is approximately 2 km to 3 km. The actual range may vary depending on environmental conditions.

• Ensure a Mesh Gateway is within range: Ensure one or more Mesh Gateways are within range of the Border Gateway.

• Line of sight: Ensure line of sight to at least one Mesh Gateway in range.

Reliable power supply

• "Always on": As the Border Gateway is considered "always-on", it needs a reliable power supply. As the Border Gateway's LTE-M radio (for connecting with mobile networks) uses a reasonable amount of power it needs a sufficient power supply.

• Mains power (recommended): Ideally, it should be installed in a location with mains power but its solar panel is sufficient to charge the supercapacitors throughout the day.

• Solar panels always connected: Ensure solar panel(s) are mounted and connected as they serve as a backup power supply, or in some cases, the primary power source.

Mounting guidelines

• Mount to a stable metal or wooden pole: Mount to a metal or wood pole that is unlikely to be moved. Use the provided U-Clamps to securely hold the mounting brackets (Gen 3). When mounted on a pole, the Border Gateway does not interfere with a living tree over the lifetime of the Border Gateway.

• 60.3 mm pole diameter: The diameter of a pole must not be greater than 60.3 mm. A 17 mm wrench is used to attach the M10-nuts to the U-Clamps.

• Use only healthy trees: When attached to trees, ensure they are healthy and unlikely to be removed.

• Mount at least 3 m high on pole or tree: Mount the Border Gateway at least 3 m high on the pole or tree and, if possible, higher for better signal propagation.

• Clear away obstructions:

  • The Border Gateway needs an unobstructed area to obtain sufficient sunlight to charge the solar panels.

  • If the Border Gateway is installed on a tree, the solar panel should not be covered by branches.

• Mount solar panels correctly:

  • Mount the solar panels (Gen 3) facing the sun at 12:00 noon (northern or southern hemisphere).

  • Use a compass to identify true South (in the northern hemisphere) or true North (in the southern hemisphere). This maximizes the amount of light that hits the solar panel.

  • If possible, select a location that has direct sunlight (such as a hillside) and keep it free from branches that obscure direct sunlight.

Load balancing

Use backup Border Gateway, if required. Ideally, for deployments greater than 1000 sensors, provide a backup Border Gateway. This also provides load balancing.

Deployment scenarios

The Gen 2 Border Gateway can be deployed using the supplied PoE (Power over Ethernet) to connect to a mains power supply. The solar panel must be connected to the Border Gateway.

The Gen 2 Border Gateway can also be powered using only the solar panel in deployments without access to a mains power supply.

Mount to metal/wood poles

If a 60 mm (2.3 inch) wooden or metal pole is available, you can use the provided U-Clamps to attach the Border Gateway to the pole.

1. Prepare U-Clamps: Loosely connect the U-Clamps to the Border Gateway, then slide the gateway onto the pole from the top (if possible).

2. Tighten U-Clamp: Hand-tighten the nuts, then use the 17 mm wrench to tighten the nuts. Do not use excessive force to prevent damage to the Border Gateway.

1. Attach the antennas: The LoRa antenna is attached to the top connector, LTE antenna on the bottom connector and satellite antenna is on the side.

2. Attach solar panel: Attach the solar panel to the pole above the Border Gateway. And if used, connect the Ethernet cable to a router.

3. Run connectivity test: Run a connectivity test to ensure the Border Gateway is connected to the Silvanet Cloud.

Mount Border Gateways to trees

If the Border Gateway is to be attached to a tree, ensure the tree is stable and unlikely to be cut.

1. Fina a mounting location at least 3 m above forest floor: Once a tree has been selected, use a safety strap to hold the ladder to the tree. Then, have an assistant stabilize the ladder, locate a position on the tree that is approximately 3 m above forest floor.

2. Prepare mounting area: Remove any branches and other obstructions at the deployment height. This allows the solar panel to have good irradiation from the sun to charge the device. Carefully remove a small portion of the bark with an axe or chisel where the holes in the tree will be drilled. This allows the gateway to hang vertically on the tree.

1. Drill two holes 70 mm apart for top loops: Using a 10 mm drill bit for wood, drill two holes approximately 6-7 cm (2 1/5 inches) into the tree with a distance of 70 mm apart. Ensure you do not split the tree or drill on an angle. We recommend drilling a pilot hole using a small drill bit (1/4 inch / 6mm) then drill the final hole with the 10mm drill bit.

1. Hammer the top treenails into the tree: Carefully hammer the treenails through the top loops of the Border Gateway into the holes.

1. Drill the bottom holes: Carefully drill the bottom two holes using the lower holes as templates. Be careful not to damage the Gateway case while doing so. Also, use a drill bit with a sufficient length to ensure the holes are at the correct depth.

2. Hammer the bottom treenails into the tree: Carefully hammer the treenails through the bottom loops into the tree. Check to ensure the Border Gateway is securely attached to the tree and cannot move.

3. Attach the antennas: The LoRa antenna is attached to the top connector, the LTE antenna to the bottom connector and the satellite antenna to the connector on side of the device.

4. Mount the solar panel: Attach the solar panel to the tree above the Border Gateway. And if used, connect an Ethernet cable from a router. See below.

Mount solar panel

After installing the Border Gateway, attach the solar panel to the same pole or tree to provide a backup power supply.

Mounting guidelines

After attaching the Border Gateway to either a pole or a tree, the solar panel needs to be attached to the same location, preferably above the Border Gateway. Garden wire is used to secure the solar panel to the support structure (tree or pole).

• Mount on same tree or pole as Border Gateway: Ensure the solar panel is attached to the same tree or pole used for the Border Gateway.

• Oriented towards sun at 12:00 noon (northern/southern hemisphere): Locate the deployment location towards where the sun would be at 12:00 noon. This allows the solar panel to have maximum sunlight irradiation during daylight hours.

• Protect cable from accidental damage: Ensure the solar panel cable is placed in such a way that it cannot be damaged by human or animal incidents.

• Mount above Border Gateway: If the deployment location is a public area, the minimum height for both the Border Gateway and the solar panel should be at least 3m above the forest floor with the solar panel mounted above the Border Gateway. A higher deployment allows for better connections to Mesh Gateways.

• Securely mount the solar panel to pole or tree: Ensure the solar panel is tightly connected to the tree or pole so that it cannot slip or turn during strong winds or other environmental actions.

Mounting steps

To mount solar panel to pole or tree:

1. Cut two equal lengths of provided garden wire, each being twice the circumference of the tree or pole.

2. With the solar panel is at ground level, insert garden wire through the holes.

3. Climb the ladder with the panel and place the solar panel on the opposite side of the tree or pole and pull it tight using the top wire, then twist the cable tight. Ensure the panel faces south towards where the sun would be at 12:00 noon.

1. Follow the same procedure with the lower wire.

2. Twist the two ends of the cables together and bring the twisted cable within the back of the panel.

3. Ensure the solar panel is tight against the tree and pole and cannot move.

The following shows a completed Border Gateway and solar panel deployment.

Connect Border Gateway to Ethernet (PoE)

If an Ethernet connection is available, use the PoE Injector to connect to a mains power supply. The Border Gateway provides a sealed RJ45 connector to attach an Ethernet cable to the device.

1. Open the Ethernet connector by unscrewing the cap.

2. Disassemble the Ethernet connector, including the end cap, sealing ring and housing.

1. Lead the Ethernet cable through the end cap, sealing ring and housing.

2. Connect the Ethernet cable into the Ethernet socket in the connector.

1. Reassemble the connector. Carefully seat the sealing rings in the housing without damaging the barbs, then screw the end cap on the housing and screw the housing to the connector.

1. Connect the supplied Ethernet cable to the PoE and then connect an Ethernet cable (not supplied) from the PoE to an available router.

2. Plug in the PoE to a mains power supply using the provided power cable.

Next steps

1. Let superconductors charge: After mounting the Border Gateway and providing it with a power supply, allow the superconductors to fully charge.

2. Run connectivity test: With the Border Gateway mounted and powered, run the Connectivity Test to ensure the Border Gateway connects with the Silvanet Cloud.

Register Device ID

To register the Border Gateway's Device ID, scan the QR Code (for Gen 2) or use NFC (for Gen 3).

1. In the Silvanet Deployment app, select a Site.

1. In the list of devices that appears, select a Border Gateway. Alternately, select Show Devices on Map.

1. On the map that appears, tap Register Device. The blue dot on the map shows your current location.

1. If you tapped Show Devices on Map, the maps shows on overview of your Site. Your location is indicated by a blue dot.

1. Once the deployment location is found, register the Device ID.

2. Use the Deployment app to scan the device's QR Code, which is attached to the back of the Border Gateway.

1. The Deployment app automatically fills in the Gateway's latitude and longitude using the Smartphone's GPS location.

2. After a few moments, the Registration successful message appears. The device icon changes from Planned to Deployed. For more information, see Status icons.

Next steps

After a successful Device Registration, the Border Gateway can be permanently mounted to the tree or pole. The Deployment app provided guidelines for mounting the Border Gateway.

Mount the Border Gateway to a metal or wood pole or on a tree, as described in the following sections. Afterwards, mount the solar panel(s). Alternately, use the PoE Injector to provide power from mains, if available.

Dryad's Silvanet Border Gateway provide the connectivity between the Silvanet Mesh Network and the Silvanet Cloud Platform. It is assumed to be always on (24-hour operation) to listen for messages sent by Wildfire Sensors in the Site. It can operate using its solar panel or in combination with a mains power supply and its solar panel. Internet connectivity can be wireless (mobile), wired (Ethernet) or satellite.

The Border Gateway is typically placed at the edge of a forest. As Border Gateways are LoRaWAN compliant, they can also communicate directly with Wildfire Sensors if any are within range of the Border Gateway.

Key features

• Mount directly to trees or poles

• Includes a solar panel and PoE Injector

• Uses LoRaWan to connect with the Silvanet Mesh Network.

• Internet connectivity:

  • 4G/LTE-M (with 2G/GPRS fallback) or NB-IoT.

  • Ethernet using the PoE Injector.

  • Satellite for remote deployments and for backup.

• Energy source:

  • mains power supply using the supplied PoE Injector.

  • Solar panel to provide daily energy requirements.

• Supports FUOTA (Firmware Update Over-the-Air) for remote firmware updates.

• Supports deployment of up to 20 Mesh Gateways.

• Directly receives messages from sensors if they are within range.

Delivered components

Each shipment of a Border Gateway includes the following components:

• Silvanet Border Gateway

• Solar panel

• Treenails (for permanent deployment)

• U-Bolt Clamps, M10 nuts and washers

• 5 meter roll of garden wire (for temporary deployment)

• LoRa antenna (North America: 915 MHz, EU: 868 MHz, Asia: 433 MHz)

• LTE-M antenna

• Satellite antenna

• PoE Injector and one power cable

• RJ45 CAT6 Ethernet network cable for use with the PoE

Dimensions

The dimensions of the Silvanet Border Gateway are (LxWxH) 27.5 cm (63 cm with antennas) x 46 cm (with the satellite antenna) x 4.5 cm and weighs 1.3 kg.

Mains using PoE

The Silvanet Border Gateway includes a PoE Injector to connect to a mains power source. If a router is available, it can be connected via Ethernet to the PoE.

Solar panel

For off-grid locations or when a mains power supply is unavailable, the solar panel provides the Border Gateway's daily energy requirements and ensures the supercapacitors are charged.

During the night when the solar panel loses generating capacity, the supercapacitors allow the device to continue receiving power. This ensures a continuous power supply to the Border Gateway.

Power outage

When a relatively short power outage occurs, the Border Gateway's supercapacitors allow the device to continue receiving power.

Should a power outage occur for an extended period, such as 10 hours of even several days, the solar panel guarantees a power supply to the Border Gateway by charging its supercapacitors until the power supply is restored.

Power saving mode

To reduce overall power requirements, the Border Gateway's modem wakes up ever hour and stays on for five minutes to send a message (a "heartbeat") to the Silvanet Cloud to indicate it is alive.

Supercapacitors

The Border Gateway's internal supercapacitors provide a power supply of 5415Ws. They provide a large amount of power for a short duration (for example, when it sends a "heartbeat") and are continuously recharged from an external power supply (PoE or solar panel).

Internet connectivity

The Border Gateway provides a range of options to connect to the Internet.

It supports LTE-M (Cat-M1)/NB-IoT which requires access to a 4G network with 2G fallback (GPRS). An LTE-M antenna is provided to connect to a 4G network.

If a router is available, the Border Gateway can be connected to the router using the PoE Injector and Ethernet.

Satellite (backup) connectivity is provided should Ethernet and LTE-M become unavailable or if the Border Gateway is deployed in a remote location without access to mobile towers. An antenna is provided for Satellite uplink.

Firmware updates (FUOTA)

The Border Gateway supports FUOTA (Firmware Update Over The Air) with high flexibility. Large file transfers are successfully made securely and reliably even with eventual interruptions of the power supply and, consequently, sensor operation.

Firmware is updated using a chunked image transfer (no compression). All Silvanet sensors in a Site are updated at the same time using Multicast. To do this, the LoRaWAN Network Protocol is temporarily switched to Class B which allows two-way communication.

To cope with low power and the various regional regulatory requirements, both the downlink fragment size as well as the periodicity are highly configurable allowing for stretching a FUOTA process even to a week.

Silvanet Wildfire Sensors and Mesh Gateways form the Silvanet Mesh Network to forward messages from remote Wildfire Sensors to Border Gateways. This network is designed to work in areas where mobile coverage is weak or non-existent, which allows for large off-grid deployments.

Silvanet devices use the long-range, low power LoRa modulation to communication between devices using LoRaWAN.

LoRaWAN and Silvanet devices

The Silvanet Mesh Network uses LoRaWAN, which allows large-scale deployment of Wildfire Sensors in the challenging environment of forests where leaves, trees, hills and topology often inhibit radio waves. In these types of environments, the range of traditional LoRaWAN gateways is very limited.

Border Gateways are responsible for transmitting messages to all devices in the Silvanet Mesh Network for firmware updates using FUOTA.

The Silvanet Mesh Network connects to Silvanet Border Gateways using LoRaWAN. This allows the Gateway to communicate with the proprietary Silvanet Mesh Gateways or directly to Wildfire Sensors if they are within range.

LoRa frequency bands

Silvanet devices - Border Gateways, Mesh Gateways and Wildfire Sensors - are IoT devices based on LoRa. The frequency bands used by these devices depend on the region in which they is deployed:

• Europe: 868 MHz

• North America: 915 MHz

• Asia: 923 MHz

Sensor frequency channels - Europe

Sensor frequency channels - North America

Max radio frequency power - EU and North America

Maximum radio frequency power transmitted (Tx) in frequency bands in which the sensor operates (EU and North America):

• EU Max Tx power: 25 mW EIRP

• US Max Tx power: 25 mW EIRP

LoRa Frequency bands (MHz) - select countries

Wired - Mains and router

In this setup, the Border Gateway uses a mains power supply (via PoE Injector) and a router (via Ethernet). The solar panel acts as a backup power supply.

• Internet connectivity: The Border Gateway is connected to a cable or ADSL router via Ethernet which is connected to the PoE injector. In case of loss of Internet connectivity via the router, the Border Gateway uses its built-in 4G/LTE-M (or 2G/GPRS) mobile radio or its satellite connectivity.

• Power supply: The Border Gateway uses the PoE Injector connected to a mains power supply.

• Backup power supply: In case of power failure, the solar panel is used.

Wireless - Mains and mobile networks

In this setup, the Border Gateway is deployed in a location without a fixed-line Internet connection (without a router) but has a mains power supplied by the PoE Injector.

• Internet connectivity: Provided by the Border Gateway's built-in 4G/LTE 2G/GPRS radio. In case of loss of Internet connectivity via 4G/LTE-M (or 2G/GPRS) mobile radio, the Border Gateway uses satellite connectivity.

• Power supply: The Border Gateway uses the PoE Injector connected to a mains power supply.

• Backup power supply: In case of power failure, the solar panel is used.

Wireless - Solar and mobile networks

Often Internet connectivity and a mains power source is unreliable in remote locations. Border Gateways deployed in these locations have neither fixed-line Internet connectivity nor a reliable power supply. In these cases, the Border Gateway uses its solar panel for a power supply. It uses mobile radio connectivity (if available) or a satellite uplink (to send fire alert signals to the Silvanet Cloud).

• Internet connectivity: Provided by the Border Gateway's built-in LTE-M 2G/GPRS mobile radio, if a mobile tower is accessible. If a mobile tower is inaccessible, the Border Gateway uses a satellite uplink.

• Power supply: Powered by the solar panel which charges the Border Gateway's internal energy storage. However, depending on the amount of sunlight, data transfer might be limited.

Satellite - No mobile and mains power source

Normally, as a fallback, the Border Gateway supports several methods to ensure uninterrupted Internet connectivity. If the Border Gateway does not have wired or wireless Internet connectivity and/or power supply, the solar panel and satellite ensures uninterrupted Internet connectivity.

• Satellite replaces wired or wireless Internet connectivity: If the Border Gateway loses Ethernet due to network failure and cannot connect to a mobile network, a satellite uplink provides as backup connection. However, only Fire alarms are sent.

• Solar panel replaces mains power supply: The solar panel provides a backup emergency power supply. The solar panel charges the internal batteries and allows the mobile data connection to be used. As the system runs in power saving mode, no other sensor data other than fire alerts can be transmitted.

After a successful Device Registration, the Mesh Gateway can be permanently mounted to the tree or pole. The Deployment app provided guidelines for mounting the Mesh Gateway.

Attach Mesh Gateways to poles

1. Loosely attach the U-Clamps to the Mesh Gateway, then slide the Mesh Gateway onto the pole from the top, if possible.

1. Ensure the Gateway is oriented properly (facing the sun at 12:00 noon) with the antenna connector facing upwards. You may need assistance holding the Mesh Gateway.

1. Hand-tighten the nuts on the U-clamps, then use the 17 mm wrench to tighten the nuts. Do not use excessive force to prevent damage to the Border Gateway. Ensure the Mesh Gateway is securely connected to the pole and cannot move.

2. Attach the LoRaWAN antenna to the Mesh Gateway.

Attach Mesh Gateways to trees

If the Mesh Gateway is to be attached to a tree, ensure the tree is stable and unlikely to be cut.

1. Once a tree has been selected, use a safety strap to hold the ladder to the tree. Then with an assistant stabilizing the ladder at the bottom, locate a position on the tree that is approximately 3 m above forest floor and facing the sun (at 12:00 noon).

2. Remove any branches that might interfere with maximum sunlight irradiation.

3. If required, carefully remove a small portion of the bark with an axe where the holes for the treenails will be drilled. This allows the Mesh Gateway to hang vertically on the tree.

1. Drill the top holes using the 10mm drill bit approximately 6–7 cm into the tree. The distance between the holes must be 70 mm.

1. Hammer the treenails through the top loops of the Mesh Gateway into the drilled holes. Be careful not to damage the device while doing so. You may need an assistant to support the Mesh Gateway while hammering the treenails into the tree.

1. With the Mesh Gateway attached to the tree at the top, drill through the bottom loops of the device approximately 6-7 cm into the tree. Do not damage the Mesh Gateway while drilling through the loops.

1. Carefully hammer the treenails through the bottom loops into the holes. Do not damage the device.

2. Attach the LoRaWAN antenna to the Mesh Gateway.

1. Check to ensure the Mesh Gateway is securely connected to the tree and does not move.

Next step

After mounting the Mesh Gateway and allowing it to fully charge, run the Connectivity Test to ensure the Mesh Gateway connects with either the Border Gateway or another Mesh Gateway.

Dryad's 3rd Generation Silvanet Border Gateway provides connectivity between the Silvanet Mesh Network and the Silvanet Cloud Platform. It is assumed to be always on (24 hour operation) to listen for messages sent by Wildfire Sensors in the Site. It now incorporates NFC for offline device registration and local debugging.

Gen 3 Border Gateways are available in two models:

• SBG-3S (with Satellite option): In addition to mobile and Ethernet connectivity, this model provides Satellite connectivity for deployment in areas lacking mobile network coverage. Available in North America and Europe only.

• SBG-3 (without Satellite option): This model provides mobile and Ethernet connectivity but does not include Satellite connectivity.

About