In this section

Goal

Learn the basic steps to successfully deploy Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors in a Site.

For an overview, take a look at this video. You can always pause it and return to it after reading the steps below.

Prerequisites

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

• You have access credentials to the Site Management app - you can contact Dryad Sales if you don't already have one.

• You have installed the Deployment app on your Smartphone.

Step 1: Plan the Site

Use the Planning tool to plan the amount and location of Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors.

Login to the Site Management app (dryad.app)

Use the login credentials provided by Dryad or your reseller to access the Site Management app.

1. Go to dryad.app.

2. Select Login and then in the Sign In form enter your Username (or email address) and password.

Create a Site

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

1. Select Create Site.

Plan coverage estimation for your Site

Use the Planning tool to estimate coverage requirements for your site. With this tool, you draw paths, areas and connectivity zones. The result is a total number of Border Gateway, Mesh Gateway and Wildfire Sensors needed to cover the Site.

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

2. Find you 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: Experiment with the drawing tools. Look at the map and experiment with the drawing tools.

   1. If you see a hiking trail or railroad, use the Draw Path tool to draw a path that follows the trail or railroad. Give it a name try out some of the settings.

   2. Use the Draw Area tool to draw an area. Notice the dots inside the area. These a estimated Wildfire Sensor locations. Give it a name and move the slider to increase or decrease the density of Sensors in the area.

4. Add Border Gateways and Mesh Gateways: Use the Connectivity Mesh tool to add one Border Gateway and then a couple of Mesh Gateways. This is done using the Connectivity Mesh tool. Make sure you have placed a Mesh Gateway in the blue zone of another Gateway.

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

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

2. Notice as you add paths, areas and connectivity zone, the device counters increment. This gives you an estimate of the number of Silvanet devices you need to provide coverage in your Site.

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

Export a planning summary document

After completing a coverage estimate, select Export Summary to save a summary document (.docx) of the deployment plan. This can be printed and used by the workers who deploy the Silvanet devices.

Send deployment plan to Deployment app:

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

The Planning tool checks if the plan has issues that need to be resolved before releasing. These issues need to be fixed before the tool releases it to the Deployment app. The most likely reason is a Sensor icon is outside a connectivity zone. You can easily fix this by selecting the Sensor icon and moving it inside a blue zone.

Step 2: Prepare to deploy

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

• Shears for trimming branches and for cutting lengths of garden wire

• Binoculars to scout the area and ensure line of sight between devices

• 10 mm wood drill bit and a 6 mm wood drill bit to drill a pilot hole

• Cordless drill and extract fully charged battery

• Chainsaw for quickly cutting large branches (optional)

• 17 mm wrench for C-Clamps used for installing on poles

• Soft-coated garden wire for temporary installation of devices

• 16 foot (5 meter) foldable ladder (or telescoping ladder)

Install the Deployment app on a fully charged Smartphone:

Ensure the Deployment app is installed on a Smartphone and the Smartphone is fully charged. Launch the app in an area where mobile connectivity is good before heading into the deployment area, then select the Site.

Step 3: Deploy Border Gateway

First task is to deploy the Border Gateway to make a connection with the Silvanet Cloud Platform.

Select the Border Gateway in Deployment app

Using the Deployment app, select the Border Gateway from the list of devices. This shows where the Gateway is to be deployed. Your location is shown by a blue dot on the map.

Register the 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 scan the device's QR Code to register the Border Gateway.

Mount the Border Gateway

1. Find the location on the tree or pole that is at a minimum of 3 m above ground level.

2. Use treenails (for trees) or C-Clamps (for poles) to mount the Border Gateway. The Dryad logo must be right side up.

3. Mount the solar panel vertically, ideally above the Border Gateway and facing towards the sun (where it would be at 12:00 noon). Ensure the solar panel is connected to the Border Gateway. Don't mount the Solar Panel behind the Border Gateway.

4. If a mains is available to provide a power supply, use the PoE Injector to connect to the mains. If a router is available, connect the router to the PoE Injector, as described in Border Gateway scenarios.

Run a Connectivity test

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

Tap Confirm & Start Connectivity Test to begin.

After running the range test and (if successful), go ahead and deploy the Mesh Gateway.

Step 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 the Mesh Gateway in the Deployment app

Using the Deployment app, select the Mesh Gateway from the list of devices. This shows where the Gateway is to be deployed. Your location is shown by a blue dot on the map.

Register the Mesh Gateway

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

2. Once at the location, tap Register Device to scan the QR Code which registers the Mesh Gateway.

Mount the 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 C-Clamps (for poles), mount the Mesh Gateway.

Run a Connectivity test

Run a range test (Connectivity test) to ensure it is online and has a good signal with line-of-sight to other planned Gateways and sensors.

After running the range test and (if successful), you can now go ahead and deploy the next Mesh Gateway.

Deploy the next Mesh Gateway

Use the same procedures to deploy the remaining Mesh Gateways.

Step 5: Deploy Wildfire Sensors

Select a Wildfire Sensor in the Deployment app

Using the Deployment app, select a Wildfire Sensor from the list of devices. This shows where the Sensor is to be deployed. Your location is shown by a blue dot on the map.

Register the Wildfire Sensor

Using the Deployment app, move towards the deployment location. Once at the location, select Register Device to scan the QR Code to register the Wildfire Sensor.

Mount the 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. Using a tree nail and spacer, mount the Wildfire Sensor.

Calibrate the Wildfire Sensor

Allow 14 days for the Wildfire Sensors to calibrate.

We have provided a video for an overview of deploying Silvanet Suite in a Site.

Prerequisites

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

• You have access credentials to the Site Management app - you can contact Dryad Sales if you don't already have one.

• You have installed the Deployment app on your Smartphone.

Step 1: Plan your Site

Use the Planning tool to plan the amount and location of Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors.

Login to dryad.app

Use the login credentials provided by Dryad or your reseller to access the Site Management app.

• Go to dryad.app and with your user credentials, sign in to the Site Management app.

Select or create a Site

1. From the side menu, select Sites view.

2. Select Create Site. This is the geographical area where the Silvanet System is to be deployed.

3. The Site details page appears.

Estimate Site coverage

Use the Planning tool to estimate coverage requirements for your site. With this tool, you draw paths, areas and connectivity zones. The result is a total number of Border Gateway, Mesh Gateway and Wildfire Sensors needed to cover the Site.

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

2. Find you 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: Experiment with the drawing tools. Look at the map and experiment with the drawing tools.

   1. If you see a hiking trail or railroad, use the Draw Path tool to draw a path that follows the trail or railroad. Give it a name try out some of the settings.

   2. Use the Draw Area tool to draw an area. Notice the dots inside the area. These a estimated Wildfire Sensor locations. Give it a name and move the slider to increase or decrease the density of Sensors in the area.

4. Add Border Gateways and Mesh Gateways: Use the Connectivity Mesh tool to add one Border Gateway and then a couple of Mesh Gateways. This is done using the Connectivity Mesh tool. Make sure you have placed a Mesh Gateway in the blue zone of another Gateway.

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

1. 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

1. Print a Summary document.

   1. After completing a coverage estimate, select Export Summary to save a summary document (.docx) of the deployment plan.

   2. Print to PDF the Summary document to be used the forestry workers who deploy the Silvanet devices.

2. Release the Deployment plan.

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

   2. Resolve any issue found. The Planning tool checks if the plan has an issues that need to be resolved before releasing. These issues need to be fixed before the tool releases it to the Deployment app. The most likely reason is a Sensor icon is outside a connectivity zone. You can easily 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.

Step 2: Prepare to deploy devices

Review the Preparation guidelines and ensure you have the appropriate deployment tools.

Bring required tools

Pack the appropriate deployment tools, including:

• Toolbox to carry all the necessary tools

• Hammer for treenails

• Chisel to shave off tree bark

• Shears for trimming branches and for cutting lengths of garden wire

• Binoculars to scout the area and ensure line of sight between devices

• 10 mm wood drill bit and a 6 mm wood drill bit to drill a pilot hole

• Cordless drill with a fully charged battery

• Chainsaw for quickly cutting large branches (optional)

• 17 mm wrench for C-Clamps used for installing on poles

• Soft-coated crop wire (garden wire) for temporary installation of devices (optional)

• 16 foot (5 meter) foldable ladder (or telescoping ladder)

Launch Deployment app

Ensure the Deployment app is installed on a fully charged Smartphone.

Launch the app and select the Site in an area where the Smartphone has good mobile connectivity. Then head into the deployment area.

Step 3: Deploy Border Gateways

Register the Border Gateway

1. Using the Deployment app, find the deployment location.

2. Prepare the mounting location by determining the placement and height of the Border Gateway and Solar Panels on a healthy tree or pole.

3. Before mounting the Border Gateway, register the Border Gateway by scanning its QR Code or by using NFC.

Mount the Border Gateway

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

2. Attach the Border Gateway to the mounting bracket and lock the Gateway to the bracket.

3. Attach the solar panels to the mounting brackets and lock the solar panels to the brackets.

4. Connect the solar panels to the Border Gateway using the cables.

5. (Optionally) If a mains power supply is available, connect the PoE Injector to the mains.

Run Connectivity Test

1. Run the Connectivity Test using the Deployment app.

2. If successful, view the device details.

3. If unsuccessful, follow the steps in the Deployment app.

Step 4: Deploy Mesh Gateways

Register Mesh Gateway

1. Using the Deployment app, find the deployment location.

2. Prepare mounting location by determining the placement and height of Mesh Gateway on a healthy tree.

3. Before mounting the Mesh Gateway, register Mesh Gateway by scanning its QR Code or by using NFC.

Mount the Mesh Gateway

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

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

Run Connectivity Test

1. Run the Connectivity Test using the Deployment app.

2. If successful, view the device details.

3. If unsuccessful, follow the steps in the Deployment app.

Step 5: Deploy Wildfire Sensors

Register the Wildfire Sensor

1. Using the Deployment app, find the deployment location.

2. Prepare mounting location by determining placement and height of Wildfire Sensor on a healthy tree.

3. Before mounting the Wildfire Sensor, register the Sensor by scanning its QR Code or by using NFC.

Mount the Wildfire Sensor

1. At the appropriate location, drill a hole approximately 6-7 cm into the tree.

2. Mount the Wildfire Sensor using tree nail and spacer. Alternately, for temporary installation, use the crop wire to attach the Sensor to the tree.

Calibrate the Wildfire Sensor

1. Allow the Sensor to fully charge (1 day)

2. Let the Sensor calibrate for 14 days after mounting.

The Silvanet Suite of Gateways and Sensors are now ready for fire detection.

Next steps

Review the Device overview section of the Site view in the Site Management app to ensure all Sensors are sending data.

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.

In this section

Dryad's 3rd Generation proprietary Silvanet Mesh Gateway acts as a range extender using the patent-pending multi-hop LoRaWAN Mesh Network. It now incorporates NFC for offline device registration and local debugging.

Gen 3 Mesh Gateways are available in two models:

• SMG-3 (LoRaWAN only): This model provides LoRaWAN connectivity but does not include Satellite connectivity.

• SMG-3S (LoRaWAN and Satellite): In addition to LoRaWAN connectivity, this model provides Satellite connectivity. Available in North America and Europe only.

Overview

The Silvanet Mesh Gateway provides connectivity for large-scale deployments of Silvanet Wildfire Sensors. It allows the Silvanet Mesh Network to overcome signal interference from terrain such as hills, valleys, rock outcroppings, cliff faces, mountainous areas or any topology that prevents reliable communication.

It can be deployed for wide-area deployments in forests or for linear deployments such as railroads, wooden bridges, power lines, hiking trails and more.

Gen 3 features

Gen 3 Silvanet Mesh Gateways have an updated design for ease of installation, improved energy capacity and NFC registration.

• Mounting Bracket: A separate endurable mounting bracket is first attached to a tree or pole, after which the Mesh Gateway is clipped on to the bracket. This allows for an improved mounting experience as the light bracket can easily be carried up the ladder and attached to the tree or pole (min 3 m above forest floor). A lock can then be used to secure the Mesh Gateway to the attached mounting bracket.

• Built-in antennas: LoRaWAN (SMG-3 and SMG-S3), Satellite (SMG-3S only) antennas are now integrated. Users no longer need to attach antennas after mounting. It also prevents damage or theft of the antenna.

• NFC: Integrates NFC for registering and connectivity testing (using the Silvanet Deployment app) and for offline local debugging.

• Redesigned casing: New endurable casing design (weather/UV proof) provides IP67 Ingress protection.

• Improved energy capacity: 60% more power capacity compared to Gen 2 Mesh Gateway for a longer and more reliable power supply.

• EchoStar satellite connectivity: Ensures off-grid operations in remote areas. Provides data transfer to the Silvanet Cloud if the Mesh Gateway loses connection to the Silvanet Mesh Network (such as vandalism/theft of devices). Available in North America and Europe only.

General features

• Ease of use

  • Quickly mounted on trees or poles through the the use of mounting brackets.

  • Maintenance-free for 10 to 15 years.

  • Covers a radius of 2 km to 10 km depending on local topology and positioning.

  • No need for 4G/LTE or wired connections.

  • FUOTA support for remote firmware updates.

  • Supports paths to multiple Mesh Gateways in the Silvanet Mesh Network.

• Mesh network connectivity

  • LoRa connectivity to support Silvanet Wildfire Sensor

  • LoRaWAN enables communication with other Silvanet Mesh Gateways and Border Gateways.

  • Supports any LoRaWAN-compliant sensors and other third-party devices.

• Regulatory compliance

  • USA (FCC, PTCRB)

  • Canada (IC)

  • Europe (CE RED)

  • CB Scheme

Delivered components

• 1 Mesh Gateway

• 1 mounting bracket

• 2 C-Clamps + bolts

• 4 tree nails

Dimensions and weight

The dimensions of the Silvanet Border Gateway are (LxWxD) 82 cm x 34 cm x 6 cm (16 cm with mounting bracket) and weighs 6.8 kg (without Mounting Bracket).

Energy harvesting

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

Supercapacitor energy storage

The Silvanet Mesh Sensor uses a set of supercapacitors to store energy for use by the radio and other components. It stores the energy for day-to-day tasks and has a reasonable amount of reserve power to operate the radio module during the night.

As supercapacitors have an expected lifespan of 10 years or more, the Mesh Gateways are essentially maintenance free. This allows for an expected lifespan 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.

NFC for Provisioning

The Mesh Gateway provides NFC to allow users to configure the Mesh Gateway in locations without mobile connectivity (when offline). It also allows for local debugging.

With the Silvanet Deployment app running on a Smartphone, a deployer holds their Smartphone near the embossed NFC symbol on the Mesh Gateway to register the device. Afterwards the Gateway can be mounted on a tree or pole.

Firmware updates

The Mesh Gateway supports FUOTA (Firmware Update Over The Air). Using FUOTA, the Mesh Gateway can successfully and securely receive firmware updates even if its power supply is interrupted.

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.

Dryad's 3rd Generation Silvanet Wildfire Sensor is designed to detect forest fires within minutes, often during their early smoldering phase. This reduces the risk of the fire spreading out of control and allows firefighters to extinguish smoldering fires before they spread.

The Sensors are mounted directly on trees using tree nails or securely attached to poles or fenceposts using garden wire.

It now has an updated, endurable casing and incorporates NFC for offline device registration and local debugging.

Overview

The Silvanet Wildfire Sensor monitors the forest’s microclimate, measuring temperature, humidity, and air pressure within a radius of 80 m to 100 m (260 ft to 320 ft). It combines ultra-low-power air quality sensing with a precise gas sensing mode.

As the end-device, it uses LoRaWAN to communicate with the Silvanet Mesh Network and can operate maintenance-free for 10-15 years. Energy is stored in supercapacitors rather than batteries to prevent the Sensors from being a source of fires themselves.

Features

• Ease of use

  • Runs maintenance free for 10 to 15 years without the need of batteries.

  • Integrated NFC to allow deployment configuration (using the Deployment app) and offline local debugging.

  • Remotely update firmware using FUOTA (Firmware Update Over-the-Air).

  • Deployed every 100 m (typical) for a fire detection range of 100 m radius for 60 minute detection of a 2 m x 3 m fire.

• Updated casing design

  • New endurable casing design (weather/UV proof) with IP67 Ingress protection.

  • Integrated loop for quickly mounting on trees or wooden poles with a single tree nail and spacer (at minimum 3 m above forest floor).

• Solar power

  • Power is supplied by a built-in 6 x 6 cm solar panel.

  • As a precaution against the device itself starting a fire, it stores its energy in supercapacitors rather than batteries. This avoids the use of lithium and other toxic materials.

• Connectivity

  • LoRa-integrated radio sends and receive messages to the robust LoRaWAN Silvanet Mesh Network (Mesh Gateways and Border Gateways).

• Environmental monitoring

  • Bosch gas sensor combines ultra-low-power Air Quality sensing with a precise gas sensing mode. It is a low-energy hydrogen sensor that can detect the presence of a smoldering fire over distances of up to 115 m.

  • Detects the presence of Volatile Organic Compounds (VoCs) and Volatile Sulfur Compounds (VSC) and detects these compounds at <20 ppm.

  • The gas sensor detects CO (Carbon Monoxide), H2, (Hydrogen) and VOC (Volatile Organic Compounds) at the ppm level with built-in artificial intelligence (AI) to reliably detect a fire and avoid false positives.

  • Monitors the microclimate of the forest by reading the following environmental values:

    • Temperature range: 40℃ to +85℃.

    • Humidity range: 0% to 100% condensing.

    • Air pressure: 300 to 1100 hPa.

• Regulatory compliance

  • USA (FCC, PTCRB)

  • Canada (IC)

  • Europe (CE RED)

  • CB Scheme

• LoRa Radio

  • ISM Bands: NA902-928, AU915, EU868, AS923

  • Tx Power: 14 dBm

Delivered components

• 10 Wildfire Sensors

• 10 tree nails

• 10 spacers

• Garden wire

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 grams.

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 (solar panel)

The Silvanet Wildfire Sensor includes a 60 mm x 60 mm solar cell on its front housing.

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

The solar panel provides sufficient energy supply to support continuous operation over a 24hr 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.

It continuously generates energy during the daytime and recharges the device with sufficient power for after sunset. It then begins to discharge until sunrise. After sunrise, it begins to recharge to 100% within about an hour.

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.

Energy consumption (gas sensor and LoRa radio)

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.

• LoRa radio - see Idle/active modes.

Idle/active modes

Normally, the Silvanet Wildfire Sensor is in idle mode. Every 60 seconds it enters 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.

Sensor Calibration period

After deployment, the Wildfire Sensor requires 14 days to calibrate. Until then it can generate false alarms.

Firmware updates

The Silvanet Wildfire Sensor supports FUOTA (Firmware Update Over The Air).

Using FUOTA, the Wildfire Sensor can successfully and securely receive firmware updates even if its power supply is interrupted.

Create Site

If you have an Admin role, you can create a Site. It requires a unique name and region. Users with a Standard role can request a new Site from a user with an Admin role.

1. Select Sites from the side menu, then select Create Site.

2. In the Create Site dialog, enter a Site Name and select a Region.

3. Resellers only: Select an Organization or If required, create a new organization by checking Create new Organization.

4. When completed, Select Create Site.

5. The new Site appears in the Sites view.

Rename a Site

The name of a Site can be edited or changed as required. However, the Site ID cannot be changed.

1. Open a Site.

2. From the Ellipsis menu next to a Site name, select Site Name.

3. In the Edit Site dialog, enter a new name, then select Save Changes.

Open a Site

Open the Ellipsis menu next to a Site name and select Open to display a Site. Alternately, select a Site name to open a Site.

The Site details page is displayed.

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

Border Gateways are connected (via the Internet) to the Silvanet Cloud Platform which provides to Dryad's Site Management and Deployment apps data and alerts from a Site's Wildfire Sensors.

Jump in and read our Get started tutorial for our new Gen 3 Silvanet Suite to learn how easy Silvanet can be deployed in a Site. Read the Release Notes to learn about the latest app updates.

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

The Border Gateway operates using its solar panels or in combination with a mains power supply and solar panels. Connectivity to the Internet can use its built-in wireless modem (LTE-M/NB-IoT) or use a wired connection (Ethernet with PoE Injector). SBG-3 provides Satellite connectivity (Europe and North America only).

Satellite connectivity allows deployments in remote locations lacking mobile network coverage, ensuring reliable communication even in the most isolated areas.

Gen 3 features

Gen 3 Border Gateways have an updated design to provide a improved mounting experience and a better power supply. The new design simplifies installation and prevents theft/vandalism of the device. Other highlights include:

• Mounting bracket: A separate endurable mounting bracket is first attached to a tree or pole. Afterwards, the Border Gateway is clipped onto the bracket. Holes are provided to lock the Gateway to the bracket. The mounting bracket keeps the Border Gateway 10 cm away from the tree or pole to improve signal connectivity.

• Built-in antennas: All antennas are now integrated in the device: LTE-m/NB-IoT, LoRaWAN and Satellite (SBG-3S only). This prevents damage or theft of the antennas.

• NFC: Integrates NFC for registering and connectivity testing (using the Silvanet Deployment app) and for offline local debugging.

• Redesigned casing: New endurable casing design (weather/UV proof) provides IP66 Ingress protection for both Border Gateway and Solar Panels. Connectors are now integrated into the casing (with waterproof caps) for solar panels, PoE Injector and for an optional M2M SIM card.

• Improved energy capacity: 60% more power capacity compared to Gen 2 Border Gateway for a longer and more reliable power supply.

• Two solar panels: To increase energy supply, two solar panels are now provided that provide 40 W + 40 W = 80 W of energy supply to the supercapacitors. They use the same mounting system as the Border Gateway. The solar panels can be mounted facing the sun (at 12:00 noon) while the Gateway can be mounted in line of sight to the nearest deployed Mesh Gateway.

General features

• Ease of use

  • Quickly mount on trees or poles through the the use of mounting brackets for both Border Gateway and Solar Panel.

  • Maintenance-free for 10 to 15 years.

  • FUOTA support for remote firmware updates.

• Mesh network connectivity

  • LoRa connectivity to support Wildfire Sensors

  • LoRaWAN enables communication with other Mesh Gateways

• Multiple deployment scenarios

  • Wireless only: LTE-m/NB-IoT (Model SBG-3 only)

  • Wired + wireless: Ethernet and LTE-m/NB-IoT (Models SBG-3 and SBG-3S)

  • Satellite only: For remote, isolated areas (Model SBG-3S only)

• Energy supply

  • Solar panels only

  • Mains power supply and solar panels

• eSIM for wireless connectivity

  • Built-in IoT eSIM for worldwide network coverage.

  • Provides 4G/LTE-M (with 2G/GPRS fallback) and NB-IoT mobile connectivity.

• PoE Injector (included)

  • Allows for Ethernet connectivity.

  • For use with a mains power supply.

• EchoStar satellite connectivity

  • S-band EchoStar Mobile LoRa satellite network connectivity

  • Ensures off-grid operations in remote areas without mobile network coverage.

  • Available in North America and Europe only.

• Regulatory compliance

  • USA: FCC, PTCRB

  • Canada: IC

  • Europe: CE RED

  • CB Scheme

Delivered components

• 1 Border Gateway

• 2 Solar Panels

• 3 mounting brackets

• 6 C-Clamps

• 12 tree nails

• Cables for Solar Panels

• PoE Injector and power cable

• RJ45 CAT6 Ethernet network cable for use with PoE

Dimensions

The dimensions of the Gen 3 Silvanet Border Gateway are (LxWxD) 51 cm x 34 cm x 10 cm and weighs 4 kg (with mounting bracket). With the mounting bracket, it is 18 cm deep.

The dimensions of the Solar Panel is (LxWxD) 67 cm x 35 cm x 8 cm (18 cm with mounting bracket).

LoRa radio parameters

• ISM bands: NA902-928, AU915, EU868, AS923

• Tx Power: <27 dBm (local regulations)

• LoRa antenna gain: 0.75 dBi

• Receive channels: 5

• Transmit channels: 1

Power supply

As the Border Gateway must be "always on", how it obtains an energy source must be carefully considered.

Mains using PoE Injector

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

Solar panels

In most deployment cases, the two Solar Panels can provide sufficient energy (2 x 40 W = 80 W) to supply power for storage in the supercapacitors (which have a 30% increased storage capacity). This allows the Gateway to be "always on" under even the most challenging environmental conditions (such as where sunlight may be limited during part of the year).

If a mains power source is used, the Solar Panels guarantee the Border Gateway continues to receive an energy source should a temporary power outage occur.

NFC for provisioning

The Border Gateway provides NFC to allow users to configure the Border Gateway using the Deployment app in locations without mobile connectivity (or when offline). It also allows for local debugging.

With the Silvanet Deployment app running on a Smartphone, a deployer holds their Smartphone near the embossed NFC symbol on the Border Gateway to register the device. Afterwards the Gateway can be mounted on a tree or pole.

Firmware updates

The Device overview section provides access to the current status of each Silvanet device deployed in a Site.

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.

Silvanet Wildfire Sensors and Mesh Gateways form the Silvanet Mesh Network to forward messages from remote Wildfire Sensors to . 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

Login to dryad.app

After logging in, the user is required to change their password.

1. Before logging in, you must be provided with login credentials

2. Enter the app URL . The login page appears.

1. In the form, enter your username and password provided to you by Dryad, then select Sign In.

1. If this is your first log in, you are required to change your password. You cannot change your username.

2. Enter a new password in the Update Password form, then select Submit.

3. The Dashboard Overview appears.

Logout

To logout of the Site Management app, select the User Profile icon and from the dropdown menu, select Logout.

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

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.

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

In this section

After logging in to the Site Management app, the Dashboard is displayed, which provides access to Sites to which the user has access.

Sidemenu

The side menu provides options for accessing the Sites:

Sites summary lists

The Dashboard displays totals of Wildfire Sensor, Gateways and number of Sites in your organization. It also provides quick access to your Sites.

Sensors

• Total Sensors: Number of deployed Wildfire Sensors in all Sites associated with an organization (client)

• Sensors in each site: Number of Wildfire Sensors deployed in each Site. Site names are also linked to the Site Dashboard of a site.

Gateways

• Total Gateways: Number of deployed Mesh Gateways and Border Gateways in all Sites associated with an organization (client).

• Gateways in each site: Number of Mesh Gateways and Border Gateways deployed in each Site. Site names are also linked to the Site Dashboard of a site.

Sites

• Total Number of Sites: Number of Sites belonging to an organization (client).

• Covered area of each Site: Area (in hectares) protected by a Silvanet deployment for each Site. Site names are also linked to the Site Dashboard of each site.

The Site details page is accessible from the , and .

Use this page to do the following:

Site ID

After a Site is created, it is assigned a Side ID which cannot be changed.

You can find the Site ID in the URL of the Site as well as part of breadcrumbs on a Site details page.

Site name and Organization (Reseller only)

The Site name and Organization to which the Site belongs is shown in the line below the Site ID.

Ellipsis menu

The ellipsis menu provides access to Site tools:

Edit Site Name

Select to edit or rename the Site. As noted above, the Site ID cannot be changed.

Open Planning Tool

Select to open the Planning Tool. This tool is used to rapidly generate a coverage estimate for the Site. It estimates the amount and placement of Silvanet devices required to provide ultra-early fire detection.

It outputs a set of deployment Packets available in the Silvanet Deployment app.

Open Packet Editor

If any of the resulting Packets need to be modified, open the Packet Editor to make modifications. Packets can be added or deleted as required.

Number of deployed devices

Under the Site name, you can quickly see the current state of the deployed Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors.

Status of the devices can be one of the following states:

• Active - Device connected to the Silvanet Cloud and is transmitting messages.

• Inactive - Device not sending data to the Silvanet Cloud for 12 hours.

• Fire Alerts - Sensor detected a fire and has sent a Fire alert to the Silvanet Mesh Network.

Embedded map view

An embedded Site map allows you to easily navigate around the Site and get an overview of the Site's terrain without leaving the Site details page.

Use the tools to expand the map, toggle on/off 3D Map View, Fire Risk View and more.

Devices details list

The Device overview section lists all deployed devices in a Site.

Devices are sorted into Active, Inactive, Fire Alert as well as Calibrating.

Alerts and warnings

Devices are listed in a compact list sorted by device type. If a device icon shows an alert or warning, troubleshooting messages (alerts and warnings) are displayed when a device listing is expanded.

Sensor data

For Sensors, expanding a Wildfire Sensor in the list displays the data sent from the Sensor.

Device info

The Device Info link opens the Technical details page which displays device technical information.

Each Silvanet device sends data to the Silvanet Cloud. This data is then displayed as line graphs for a selected time period.

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.

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.

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.

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.

The Device Info link in the Device overview section opens the Technical details page which displays device technical information in a set of tabs.

Metadata tab

• Name: User-readable Device ID.

• Notes (editable): If a note was added during deployment, it appears here. Otherwise, a note can be added by making the field editable.

Location tab

• Installed device location (editable): Provides current GPS coordinates (Latitude/Longitude) set during deployment. If the device has been moved, update the GPS coordinates in these fields.

Technical Info tab

Displays uneditable technical information about the Silvanet device.

• Sensor ID: Identifies the device in the Silvanet System.

• EUI: 64-bit Extended Unique Identifier.

• Join EUI: Internal use only.

• LoRaWAN PHY Version: PHY Version.

• LoRaWAN Version: MSC version corresponding to the PHY Layer version.

• Device Address: 32-bit device address (non-unique).

• Firmware Version: Indicates which version (and related Region) installed on the device.

• ML Version: Indicates which Machine Learning (ML) firmware applied to the device.

• NS End Device ID: LoRaWAN Network Server (NS) End-Device ID.

Sensor Data tab

Display the sensor data based on a selected time range.

QR Code

Displays the QR Code used in the Silvanet Deployment App.

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.

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 alerts in Site Management app

Fire alerts appear in the Site Management app as a pop-up 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.

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.

Alert overview

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.

Current alerts tab

If an Sensor in all Sites to which you have access have triggered Fire alerts, they appear In the Current Alerts tab of the Alerts overview page.

It shows the Site name and ID, when the Fire alert was detected, if it has been cleared and how many Sensors have triggered the Fire alert within the past two hours.

It also shows the status of the alert. Selecting the Open icon displays the Alert details page.

Past alerts tab

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

It shows the Site that triggered the alert, the Site ID, when detected and cleared and how many Sensors triggered the Fire alert.

Selecting the Open icon displays details of the cleared Fire alert(s).

Alert details page

Selecting a Fire alert displays the Alert details page.

This page shows the following details of each fire alerts:

• List of Sensors that triggered the fire alert in the Site.

• Sensor ID

• Time fire detected

• AI index

• Location of the Sensor (GPS coordinates)

• Selecting the Map icon 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

Selecting Clear alert on the Alert details page opens a dialogue to apply a reason for clearing the alert.

Options include:

• 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.

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 (if Reseller): 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 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

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

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.

Sites list

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.

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 Widlfire 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).

This deployment typically has a duration of approximately 2-4 months.

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.

This has a deployment duration of 10-15 years.

• 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.

For every one Border Gateway deployed, up to 20 Mesh Gateways can be deployed, depending on the Site's topology. However, as Mesh Gateways act as repeaters, any number of Mesh Gateways can be deployed on a Site.

Ensure each Mesh Gateway can communicate with at least two other Mesh Gateways. This ensures a reliable Mesh Network in the forest.

In the following figure, one Border Gateway (plus a backup Border Gateway) receives communication from 20 Mesh Gateways. Note the connectivity paths between Mesh Gateways. With a few exceptions, each Mesh Gateway connects with at least two other Mesh Gateways.

• : Validate the scalability of the Silvanet System using a Pilot deployment followed by a full-scale Live deployment.

• : Dryad recommends visiting the Site prior to planning device locations to make notes about the topology and other features of the Site that might inform where to place Silvanet devices.

• : The amount of Mesh Gateways supported by Border Gateways is variable but should not exceed on Border Gateway for every 20 Mesh Gateways.

• : Ensure Border Gateways and Mesh Gateways are within specified ranges which is 2.0 km to 3.0 km.

• : Plan Border Gateway deployments based on requirements for Internet access and to ensure it has a reliable energy supply (for an always-on functionality).

• : The Border Gateway can be deployed in various scenarios based on the availability of a power supply, Internet connectivity and location.

• : Mesh Gateways need access to good solar irradiation and located where Wildfire Sensors have a reliable connection to the Silvanet Mesh Network.

• : Wildfire Sensors detect gases of a smoldering fire in its ultra-early stage within a range of between 80 m to 100 m around the Sensor. The maximum range between the Sensor and a Mesh Gateway is 1 km.

• : Each Mesh Gateway can support up to 100 Wildfire Sensors. Each Border Gateway has no limit on the number of Wildfire Sensors in can support.

• : The amount of sensors per hectare is dependent on human activity in a Site as well as the presence of WUIs (Wildland Urban Interface) in a Site.

In this section

If a Wildfire Sensor determines with a high probability that a smoldering fire has occurred, then fire alerts are immediately sent to notify users of the fire.

Continuous monitoring

After the Wildfire Sensor has been calibrated, the gas sensor continuously monitors the microclimate of the forest air to measure:

• Air pressure

• Temperature

• Humidity

At the same time the Wildfire Sensor "smells" the air around the sensor for the presence of Volatile Organic Compounds (VOCs) and carbon monoxide.

This continuous monitoring allows the Wildfire Sensor to distinguish between normal and declining Air Quality:

• Normal Air Quality:

  • Normal Air Quality is the baseline reading of the Wildfire Sensor. It is the result of the 14 day calibration period of the sensor.

  • This process continues after calibration.

• Declining Air Quality:

  • When the Air Quality deviates from the baseline reading (Normal Air Quality), this is considered a decline of Air Quality.

  • However, this decline could have many causes. It could be the result of similar gasses which the sensor has detected. These gases could be diesel fumes from a passing truck, cigarette smoke or other factors that can cause a decline in air quality.

  • The role of the Wildfire Sensor is to determine if this decline is the result of a smoldering fire or some other source.

Sensors triggering Fire alerts

Once per minute, the Sensor wakes up and performs an environmental monitoring gas scan. During each gas scan, hydrogen, carbon monoxide and other Volatile Organic Compounds (VOCs) are measured. It also measures air pressure, temperature and humidity.

The Wildfire Sensor uses a default sliding time window of 5 minutes to "smell" the air. If the Wildfire Sensor detects a significant deterioration of air quality within the past four gas scans, a prescribed set of gas scans are triggered to determine if the observed deterioration is from a smoldering fire or from some other source.

For each gas scan, the results of the gas scan are compared with with a pre-trained Machine Learning (ML) Model. This is done to determine if the observed decline in air quality can be classified as wildfire smoke or from some other source. As these gas scans consume a lot of energy, they are kept to a minimum.

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.

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).

Border Gateways are designed to be deployed at the edge of the forest and ideally on a permanent structure. It needs to be free from obstructions, provided with mains power and access to Internet connectivity.

Guidelines

• Always on: As the Border Gateway is considered "always-on", it needs a reliable power supply. Ideally, it should be installed in a location with mains power but its solar panel is sufficient. The device's LTE-M radio (for connecting with mobile networks) uses a reasonable amount of power so ensure it has a sufficient power supply.

• Internet connection: It needs a reliable and continuous connection to the Internet, which can be Ethernet, mobile or satellite.

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

• Attached to healthy trees or stable poles: When attached to trees, ensure they are healthy and unlikely to be removed. When attached to metal poles, ensure they are to stable and unlikely to be moved or tampered with.

Load balancing

An additional Border Gateway can be added to provide a backup Border Gateway or to provide load balancing.

The Silvanet Network supports any number of Wildfire Sensors through the use of the Silvanet Mesh Network. However, this support is possible only if range and ratio values are followed. The Planning tool takes into account these range and ratio values when preparing a deployment plan.

Gas detection range

Gas detection range is 80 m to 100 m (260 ft to 320 ft)

Depending on the topology and density of the forest, the Silvanet Wildfire sensor can detect gases, especially Volatile Organic Compounds (), in the surrounding air within a radius of 80 m to 100 m (260 ft to 320 ft). It can also detect smoke from a smoldering fire that drifts into its detection zone from beyond the gas detection range.

Sensors connectivity range

Maximum distance to a Mesh Gateway is 1 km

Sensors communicate with Mesh Gateways and Border Gateways that are approximately 1 km away from the sensor, depending on topology. In dense forests, the range may be less while direct line of sight to the Mesh Gateway may have a longer range.

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.

To build up a Mesh Network, allow for the following conditions:

• Range to Border Gateway: Maximum distance between the Border Gateway and the nearest Mesh Gateway is 2 km to 3 km. Each Mesh Gateway can be up to 3 km from other Silvanet Gateways, depending on the topology and height at which the device has been deployed on a tree.

• Range to nearest Mesh Gateway: A Mesh Gateway must be within range of at least one other Mesh Gateway, which is 2 km to 3 km.

• Connectivity between two Mesh Gateways: Ensure each Mesh Gateway can connect to at least two other Mesh Gateways, or one Mesh Gateway if no other are within range.

In the following example, note the paths a message can take through the Mesh Network. A message has several routes to the Border Gateway, except one isolated Mesh Gateway. This ensures reliability in the network.

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 to replace 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 to replace 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.

Packet planning guidelines

Consider the following guidelines when planning where to place devices on the Map in the Site Management app:

• Sensor density: The density of sensors in areas of a Site is based on the human activity in an area and the topology of the forest floor. See Sensor density guidelines.

• Density per hectare: This is related to sensor density, except that in this case you need to know where in the forest is the Wildland Urban Interface (WUI) and where are the deep forest areas.

• Device ratio: Ensure sufficient Mesh Gateways are deployed for the number of sensors deployed. Similarly, ensure at least one Border Gateway and possibly a backup Border Gateway is deployed based on the amount of Mesh Gateways deployed. See Gateway ratios.

• Device range: Ensure sensors are deployed within range of at least one Mesh Gateway. See Sensor range.

Add new Packet

Packets are prepared using the Packet Planning page which displays any previously prepared Packets.

1. Log in to dryad.app and from the Sites dashboard, select open a Site.

2. In the Dashboard of the Site, select from the ellipsis menu (upper-right corner) the Packet editor. Any existing Packets appear in the editor.

3. Select + Add Packet to open the Create Packet page. A default location should be shown in the embedded map.

4. Provide a unique name for the Packet in the Packet name field, then select Add devices to packet.

5. After adding a new Packet, find the Site location by centering the map on the Site location using the Search field.

6. Use the Map tools (zoom in or out, move the map) to find the geographical area (Site location) where the devices in the Packet are to be deployed.

Border and Mesh Gateways

Add Gateways

1. On the Packet Planning page, select Add devices to packet.

2. From the Device Type dropdown menu, select Border Gateway and enter the number of Border Gateways. Then, select Add.

3. Repeat the same procedure for Mesh Gateways.

4. Select Save to save the Packet (you may need to scroll down to see the Save button).

Place Gateways on map

Placing Border Gateways on the map generates the GPS location for each Border Gateway. Ensure the map is centered on your Site location.

1. Select the Gateway(s), then select Add devices to map.

2. The Gateway(s) appears on the map as icons centered in the view.

3. Drag the Gateway icons to the approximate location of the planned deployment. The GPS coordinates appear next to the device in the list.

4. Select Save to save the Packet (you may need to scroll down to see the Save button).

5. Select Back to go the Packet Planning page.

Wildfire Sensors

Add Wildfire Sensors

Before adding Wildfire Sensor, review the guidelines for deploying Wildfire Sensors.

1. On the Packet Planning page, select Add devices to packet.Select Add devices to packet and select Sensor.

2. From the Device Type dropdown menu, select Sensor and enter the number of Sensors. Then, select Add.

3. Select Save to save the Packet.

Place Sensors on map

Placing sensors on the map generates the GPS location for each sensor. Ensure the map is centered on your Site location. Ensure you follow the guidelines in Device Ratio and Ranges and Sensor density when placing the sensors.

1. Select the sensors, then select Place on map. The sensors appear on the map in a default location in the center. The GPS coordinates of the sensors appear in the list next to the devices.

2. Drag the sensor icons to their respective deployment locations. When selecting a sensor icon, the distance between the Wildfire Sensor and the nearest devices and Gateway are highlighted

3. Select Save to save the Packet

4. Select Back to go the Packet Planning page.

Completed Packets

When the required number and type of Packets have been prepared, the new Packets appears in the Packet Planning page and in the Silvanet Deployment app.

Edit a Packet

The Packet Planning page allows for a Packet to be modified such as deleting a device from a Packet.

1. Open the Packet editor from the ellipsis menu in the Site Dashboard.

2. Select a Packet, then select the Pencil (Edit) icon to open the Packet in Edit mode.

3. From the list of devices, select the devices to be edited.

   1. To update GPS coordinates of a device, select the Pencil icon next to the device, make changes to the Latitude and Longitude, then save the changes.

   2. To delete a Sensor or Gateway, select the device then selecting Remove.

4. This only removes the Sensor from the Packet. If a

5. Select Save to save the changes. A Packet saved message appears.

Delete a Packet

If required, a Packet can be deleted from the Site Management app.

1. Open the Packet planning page in the Site Management app.

2. Select a Packet, then select the Trash (delete) icon.

3. Confirm the deletion.

4. Select Save to save the changes.

In this section

Sensor density per hectare is based on:

• in specific areas of the forest

• (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.

The Planning tool provides a set of tools for rapidly estimating the number of Wildfire Sensors and Silvanet Gateways needed to provide fire-detection coverage for a Site.

Access

From the Site Dashboard select Planning from the Ellipsis dropdown menu to open the Planning tool.

Main menu

The main menu provides access to saving and opening planning projects.

• Open: Access saved Planning work on a local or network drive.

• Save: Save and store your progress locally.

• Export to CSV: Export device coordinates to a CSV file.

• Quit: Closes the Planning tool.;

Toolbar

The Toolbar provides access to the tools for estimating coverage requirements.

• Select tool: Use to select paths, areas or Gateways on the map.

• Draw path tool: Use the Path tool to define high-density deployment areas such as hiking paths, rail lines, power lines.

• Draw area tool: Use the Area tool to define lower density deployment areas such as forested areas.

• Plan connectivity tool: Use the Connectivity tool to define the number and placement of Border Gateways and Mesh Gateways to build up a successful Mesh Network in the Site.

• Comment tool: Use the Comment tool to add relevant comments to the plan.

Views

You can view the Site in Terrain view, Map view, 3D view and Fire risk view.

Terrain view (topology)

Terrain view shows the topology of the path and how it may affect message transmissions to/from the sensors. Select the Terrain icon at the lower-left edge of the map.

Fire risk view

Selecting the Fire Risk icon displays an overlay that indicates areas of high to low risk of fires.

3D View

Select the 3D View icon to show a 3D map of the Site. It shows areas that may cause connectivity issues such as hills and valleys. It also may show areas that are challenging for deployments such as steep hills that may be difficult to traverse.

Draw path tool (high density)

Paths are typically areas that require a higher density of sensors. Examples of paths in the Planning tool include hiking paths, lanes and roadways, rail lines, power lines or other linear areas that have a higher level of human activity than a forested area.

Draw a path

1. Start path: Start creating a new path by selecting a location on the map where you want the path to start.

2. End path: End the path by double-clicking on the map where you want the path to end.

4. Save the project.

Path settings

The Path settings are accessed by selecting a path.

• Name: Give the path a descriptive name.

• Path type: Choose a path presets which influence the placement and amount of sensors on the path:

  • Hiking path

  • Road

  • Railway

  • Power line

• Protection Level: Set based on the path type. It can be adjusted. Low level of protection is 100m between each sensor. High level is 20m between each sensor.

• Distance between sensors: Distance set by Prediction Level slider. A precise value can be entered here, as required.

• Amount of sensors: Set by Prediction Level slider based on the length of the path and density. A precise number of sensors can be entered, as required.

Edit paths

Any path can be modified after it has been added and saved to the project file. Two types of dots are used that follow the route of the path:;

• White dots: Key points in the path that alter segments of the path. They can be deleted to straighten a path in that segment.

• Yellow dots: Mid-points between white dots. Selecting a yellow dot converts them into white dots which adds other mid-point yellow dots.