In this section

In this section

Learn about Dryad's Silvanet Suite which 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 data from the Site's Wildfire Sensors to Dryad's apps - the Site Management and Deployment apps.

Documentation highlights

User Guides

This tutorial walks you through the steps required to plan the deployment of Silvanet devices using the Site Management app's Planning tool.

The example plan in this tutorial includes high density Sensor zones called Paths and low density Sensor zones called Areas.

To ensure the Sensors have connectivity to the Silvanet Cloud, the plan includes a Connectivity Mesh that consists of a Border Gateway and several Mesh Gateways.

After completing the plan, it is then released to the Deployment app and exported as a summary document.

Goal

After completing this tutorial, you should know how to:

• Open the Planning tool in the Site Management app

• Search for an appropriate Site location

• Save the planning file (custom_name-site_number.dryad)

• Define Areas and Paths and a Connectivity Mesh

• Export a summary document (*.docx) and release the plan to the Deployment app

Prerequisites

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

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

• Deployment app installed on your Smartphone.

• Site created in the Site Management app. To learn how to create a Site, see here.

1. Find Site location

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

1. Open the Site Management app.

2. Select Site view, then select Planning tool from the ellipsis menu (upper-right corner).

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

4. Save your project by selecting Save from the dropdown menu (upper-left corner).

2. Draw three paths

Draw a hiking path

Add the first path which i s a line of Sensors that follow a hiking path in the Site.

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

   • Name: Enter a descriptive name.

   • Path type: Select Hiking Path.

   • Protection Level: Select Mid. The slider is used to determine Wildfire Sensor density (Low, Mid, High).

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

2. Save the project.

Draw a power line path

Add another path but In this case select Power Line from the Path type dropdown.

Notice how the Planning tool wraps each power line tower with four Sensors.

Draw a roadway path

Add the third path but in this case select Roadway from the Path type dropdown.

Notice the increased density of Sensors for a roadway compared to a hiking path.

You should now have three paths shown on the map.

3. Draw three areas

Add the first area

Find an area on the map to add the first of three areas. In this case, we use the area that includes a valley, a hillside and areas that are sparsely wooded.

It follows the contours of the hiking path and crosses the power line path. Name it the North ridge.

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

   • Name: Enter a descriptive name, such as North Ridge.

   • Surface area: This is automatically generated.

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

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

3. Save the project.

Draw a second area

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

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

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

3. Save the project.

Draw an inaccessible area

In this area, define an inaccessible area. This is an area that is off-limits and cannot be used to deploy Sensors.

Use the Draw Area tool to define this area but in this case, slide the Accessible selector to Off. The area then is defined without Wildfire Sensors.

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

2. Save the project.

4. Add connectivity zones

Connectivity zones have the following properties:

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

• Open areas: Bounded areas within a connectivity zone indicates topology such as a hill or rock face that interferes with Sensor connectivity with Gateways. These areas may require additional Mesh Gateways but they must be added within existing blue areas.

Add a Border Gateway

First add a Border Gateway. Look for a location at the forest edge where the Gateway can expect clear line-of-sight to mobile towers and free of trees or structures to ensure good solar radiation on the solar panel.

2. Select Add Gateway and place the Gateway icon on the map. Remember, it needs to be placed where it can get mobile connectivity and good access to solar irradiation. Double-click the Gateway icon to add the Gateway.

3. Select the Gateway from the side menu to open the Edit Gateway dialog, then select the following:

   • Gateway type: Border Gateway

   • Installation Height: 5m Pole

   • Network: Cellular

   • Power Type: Solar

   • Latitude/Longitude: GPS location of the Border Gateway is automatically generated.

4. Save the project.

Add Mesh Gateways

Next, add Mesh Gateways to build up a Connectivity Mesh.

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

2. Save your project.

Add additional Mesh Gateways

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

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

2. Save your project.

5. Add comments

6. Release Deployment Plan

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

1. Select Release Deployment Plan.

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

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

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

1. Save your project.

7. Export summary

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

1. From the Planning tool, select Export Summary.

1. Save to a local drive for use by teams deploying Silvanet devices in a Site.

In this section

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 Wildfire Sensors now have an updated, endurable casing and incorporates NFC for offline device registration and local debugging.

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

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.

Key Features

Gen 3 Silvanet Wildfire Sensors have an updated design for better gas sensing and allows device registration using NFC.

New features

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

• New gas sensor: Updated gas sensor for improved fire detection capabilities.

Deployment features

• Detection radius: 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.

• Maintenance free:

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

• Weatherproof casing design:

  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 powered

  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.

• LoRaWAN connectivity:

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

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

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 temperature, humidity and air pressure.

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: 300 hPa to 1100 hPa

• Humidity: 0% to 100% condensing

• 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

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

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

Firmware update

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.

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 or for linear deployments such as railroads, wooden bridges, power lines, hiking trails and more.

Key features

Gen 3 Silvanet Mesh Gateways have an updated design for ease of installation including a new separate mounting bracket and internal antennas. It also provides improved energy capacity, NFC registration and satellite connectivity.

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

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

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.

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

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

Key features

• Mount directly to trees or poles

• Includes a solar panel and PoE Injector

• Uses LoRaWan to connect with the Silvanet Mesh Network.

• Internet connectivity:

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

  • Ethernet using the PoE Injector.

  • Satellite for remote deployments and for backup.

• Energy source:

  • mains power supply using the supplied PoE Injector.

  • Solar panel to provide daily energy requirements.

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

• Supports deployment of up to 20 Mesh Gateways.

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

Delivered components

Each shipment of a Border Gateway includes the following components:

• Silvanet Border Gateway

• Solar panel

• Treenails (for permanent deployment)

• U-Bolt Clamps, M10 nuts and washers

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

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

• LTE-M antenna

• Satellite antenna

• PoE Injector and one power cable

• RJ45 CAT6 Ethernet network cable for use with the PoE

Dimensions

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

Mains using PoE

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

Solar panel

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

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

Power outage

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

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

Power saving mode

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

Supercapacitors

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

Internet connectivity

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

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

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

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

Firmware updates (FUOTA)

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

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

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

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.

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

Goal

After completing this tutorial, you should know how to:

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

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

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

Prerequisites

You need the following before beginning this tutorial:

• Login credentials to the Site Management app

• At least one Site provided in the Site Management app

• The Silvanet Deployment app installed on a smartphone

1. Plan the Site

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

Login to dryad.app

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

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

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

Select or create a Site

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

1. If no Site appears, select Create Site.

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

Plan coverage estimation

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

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

The result is a total number of Gateways and Sensors needed to cover the Site. You then export this plan to the Deployment app for use in the deployment Site.

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

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

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

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

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

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

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

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

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

Completed plan

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

1. Print a Summary document.

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

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

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

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

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

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

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

2. Prepare to deploy

Required deployment tools

The following are suggested deployment tools:

• Toolbox to carry all the necessary tools

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

• Binoculars to ensure line of sight between devices

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

• Cordless drill and extra fully charged battery

• Chainsaw for quickly cutting large branches (optional)

• 17 mm wrench used for U-Clamps

• Garden wire for temporary installations

• 16 foot (5 meter) foldable ladder

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

3. Deploy Border Gateway

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

Select the Border Gateway in the Deployment app

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

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

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

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

Mount the Border Gateway

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

1. Find a healthy tree or stable pole.

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

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

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

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

Start registration

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

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

Connectivity test in progress

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

Check results

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

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

2. If successful, tap Show Device Details.

4. Deploy Mesh Gateways

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

Select a Mesh Gateway in the Deployment app

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

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

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

Mount the Mesh Gateway

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

1. Find a healthy tree or stable pole.

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

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

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

Start registration

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

1. Tap Confirm to begin activating the Mesh Gateway.

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

Connectivity test in progress

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

Check results

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

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

3. If successful, tap Show Device Details.

Next Mesh Gateways

Use the same procedures to deploy the remaining Mesh Gateways.

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

5. Deploy Wildfire Sensors

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

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

Select a Wildfire Sensor in the Deployment app

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

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

3. Move towards the Sensor deployment location.

Mount the Wildfire Sensor

1. At the deployment location, tap Install Device.

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

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

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

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

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

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

Start registration

1. Tap Confirm to begin activating the Sensor.

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

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

3. When complete, the Installation successful screen appears.

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

Calibrate the Wildfire Sensor

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

Next steps

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

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

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

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.

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

In this section

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.

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.

Key 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:

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

• Integrated 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 plus an external SIM slot

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

Connectors

Connectors are located on the lower side of the Border Gateway.

• SIM Card slot for a customer-specific M2M SIM card that supports NBIoT / LTE-M.

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

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.

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.

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.

The Site details page is accessible from the Dashboard, Sites view and Map view.

Use this page to do the following:

• Plan Site coverage estimations: The Planning tool is used to generate a coverage estimation for the Site.

• Monitor the Site: Environmental data provided by each deployed Wildfire Sensor is provided.

• Locate source of fire alerts: Locate which Wildfire Sensor(s) has detected a fire. GPS coordinates are provided to identify where the Sensor is that triggered a fire alert.

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

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 or rename the Site.

• Open the Planning tool to generate a coverage estimation for the Site

• Open the Packet tool to edit Packets created for the Site.

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.

The Planning tool generates 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.

Create Site

If you have an Admin or Reseller role, you can create a Site. It requires a unique name. 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 number 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.

The Site details page is displayed.

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:

• Dashboard

• Sites view: Displays a provides access to each Site.

• Map view: Displays a world map showing the location of each Site as icons.

• Alert Center: Displays fire alerts generated by any Site within an Organization.

• User Management: List registered users in an Organization. Administrators can add users here.

• API Integration: Create and manage webhooks to receive Sensor data from Silvanet Cloud for use by third-part applications.

Selecting Collapse minimizes the side menu. Selecting the right arrows maximizes the side menu.

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.

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.

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.

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

Fire alert dialog

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

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

Fire alerts sent via email

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

Silvanet API interface for fire alerts

Two Silvanet API interfaces are available for 3rd party alarm interfaces / apps:

Current alerts

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

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

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

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

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

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

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

• Status: Current status of the alert. Options include

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

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

  • False Alert: An alert labelled as

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

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

Alert details page

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

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

• Type (sortable): Indicates type of alert:
• Sensor: Descriptive name of the Sensor as assigned by Silvanet Cloud.

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

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

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

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

Clear alerts

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

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

2. Select Clear Alert.

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

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

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

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

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

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

Past alerts

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

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

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

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

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

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

• Status: Current status of the alert. Options include

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

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

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

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

In this section

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

Install the app

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

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

Sign in

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

Select a Site

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

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

Device list

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

For each device in the Site, the app shows:

• Name of device.

• Packet in which the device was added.

• Status of device (see below).

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

• Button to show all devices on the map.

Device status icons:

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

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

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

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

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

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

Device filter

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

• Device type

• Status

• Deployment Packet

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

Map view

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

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

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

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

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

Pilot deployments

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

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

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

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

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

Live deployments

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

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

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

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

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

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

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

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

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

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

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

Sensor density per hectare is based on:

• Human activity level in specific areas of the forest

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

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

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

Human activity level

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

The following table shows the recommended sensor density values.

Wildland Urban Interface (WUI)

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

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.

Import KML, KMZ and Shapefiles

The Planning tool allows for externally prepared Reference files to be imported as a starting point.

You can import KML, KMZ and Shapefiles as a geographical reference.

Import reference file

1. Open the Planning tool.

2. Select + next to Reference field label (or select the field).

3. Import a prepared reference file. It can be a .kmz, .kml, or Shapefile.

4. The Planning tool imports the paths, areas and pins from the reference file.

5. Make the required modifications, such as paths, area and connectivity zones.

6. Save the Planning tool file.

Warnings

Deployment overview

• Ensure correct range

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

• Sensor density

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

• Mount Wildfire Sensor correctly

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

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

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

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

User types

Access to the Site Management app requires user credentials. Access to features of the app is dependent on the type of user role:

• Standard User: Users with a Standard role can do the following:

  • Select from Sites to which they have access

  • Use the Planning tool to plan Sites

  • Cannot add new Sites

  • Cannot add new users

• Admin: Users with an Admin role are responsible for team organization. Admins can do the following:

  • Create new users and assign them to an Organization

  • Create new Sites

  • Use the Planning tool to plan Sites

  • Cannot add new Organizations

• Reseller: Users with a Reseller role have overall responsibility for client access to Dryad apps. Resellers can do the following:

  • Create new Organizations

  • Create Admin users and add them to Organizations

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

Organizations

Organizations typically represent a company or client using a Dryad Silvanet System to provide ultra-early wildfire detection for the client's Site or Sites. They are usually created by Resellers for their Clients. They can also be created by Dryad for specific clients.

How Organizations work

When a user is created, they are assigned to one Organization. A user cannot be part of multiple Organizations (see 1 in the figure below).

If a user is created in an Organization with multiple Sites, they have access to all those Sites (see 2 in the figure below).

When a Site is created, it is linked to at least one Organization which means multiple Organizations can be linked to a single Site. All users from all linked Organizations have access to the particular Site (see 3 in the figure below).

Creating Organizations

New Organizations can be created in the Create User form when adding a user.

1. Select Create new Organization.

2. Enter the name of the new Organization.

Create user

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

1. Select User Management from the side menu, then select Add User.

2. In the Create User form, add new user details:

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

   • Email (required): Enter the new user's email address. This becomes the Username. Once added, this cannot be changed.

   • Organization (required): Select an Organization from the dropdown menu. A user can only be a part of one Organization.

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

   • Receive fire alert emails: Select to send fire alerts to the user (at the email address provided).

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 profile

Currently, user profiles cannot be edited

Delete user