After logging in to the Site Management app, the Dashboard is displayed.

The Dashboard provides access to all available Sites.

Sidemenu

The side menu provides options for accessing the Sites:

• Sites view (displays a provides access to each Site)

• Map view (displays a world map showing the location of each Site)

• Alert center (displays fire alerts generated by any Site)

User Management list users in your organization that are registered to use the Site Managment app. Administrators can add users here.

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.

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

Total Gateways

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

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

Total Number of 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 Sites view displays sites that you (admin users only) or a Reseller have created or to which you access.

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.

Create Site

Only users with an Admin Role can add a new Site to their own organization. If you are a reseller, you can add new Sites for your clients.

If you are a user with a Standard Role, request a new Site from your organization's Admin user or from your reseller.

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. If required, you can 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 Edit.

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

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

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.

The 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 in a Site.

The Silvanet Border Gateways are connected via the Internet to the Silvanet Cloud which provides data and alerts from the deployed Wildfire Sensors to the Site Management and Deployment apps.

In this section

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

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

LoRaWAN and Silvanet devices

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

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

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

LoRa frequency bands

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

• Europe: 868 MHz

• North America: 915 MHz

• Asia: 923 MHz

Sensor frequency channels - Europe

Sensor frequency channels - North America

Max radio frequency power - EU and North America

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

• EU Max Tx power: 25 mW EIRP

• US Max Tx power: 25 mW EIRP

LoRa Frequency bands (MHz) - select countries

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.

Accessing the Site Management app (dryad.app) requires a user who has been given access rights by a user with Admin rights.

Login to dryad.app

After registration, a user is provided with login credentials. After logging in, the user is required to change their password.

1. Enter the app URL dryad.app. 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.

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.

Silvanet Border Gateways receive data sent from Wildfire Sensors via Mesh Gateways. This data is then sent over the Internet - via mobile networks, an Ethernet connection or satellite - to the Silvanet Cloud Platform and made available in the Silvanet Site Management app and the Silvanet Deployment app.

Registered standard and admin users are given access to the web-based Site Management app available at dryad.app to plan deployments of Silvanet devices and to monitor environmental conditions after the devices have been deployed.

Admin users have additional privileges to manage users and add Sites.

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 ideally placed at the edge of a forest. As the 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 is (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.

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

Each Site is shown as an icon. Once located, zoom in to view the Site. You can choose between 2D and 3D Terrain views and add a Fire Risk overlay to the map. By selecting a device, the status of the device is displayed.

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.

• Select the Enable Terrain (mountain) button to switch to 3D Terrain view.

• Use the right mouse button or hold the control key + mouse pad movements to rotate the map in 3D View.

• Select the Reset button (compass) to toggle to 2D View.

Current readings

Selecting a status icon from a Site to display a device's latest status information.

Fire risk overlay

Selecting the Fire icon displays the Fire Risk overlay for a selected area shows areas of higher levels of fire risk.

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. This is the same data as displayed in Device Details.

QR Code

Displays the QR Code used in the Silvanet Deployment App.

The Site details page provides detailed information of the current status of a Site.

Use the Site details page to do the following:

• Access the : 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.

The Site details page is accessible from the , and .

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

Select the Ellipsis menu to access the following Site tools:

Site Name

Select to edit or rename the Site name. The Site ID cannot be changed (located as part of the breadcrumbs and URL).

Planning Tool

Select to open the Planning Tool used to rapidly generate Site details such as coverage area, number and placement of Border and Mesh Gateways as well as number and placement of Wildfire Sensor. The result is a set of deployment Packets available in the Silvanet Deployment app.

Packet Editor

Select to Packets make modifications to Packets prepared by the Planning tool. Packets can be added or deleted as required.

Deployed devices summary

Under the Site name, you can quickly see how many Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors are Active, Inactive and/or triggering Fire Alerts.

Embedded map

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.

Device overview

The Device overview section lists all deployed devices in a Site. Devices are sorted into Active, Inactive and Fire Alert. Troubleshooting messages are displayed when expanding a device that shows alerts or warnings.

Device info

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

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

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

Learn how to plan a Site and deploy Silvanet devices using our .

Browse by topic

Silvanet Suite deployment demo

When the Silvanet system detects a smoldering fire, fire alerts are immediately sent to registered users via and are displayed in the .

Continuous monitoring of air quality

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.

How Wildfire Sensors generate 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 alerts

fire alerts contain the following information:

• Total number of fire alerts sent from the detecting sensor.

• Number of alerts sent from the detecting sensor within the last two hours.

• Sensor ID of the Wildfire Sensor that detected the fire

• Date

• Timestamp

• Location (Latitude and Longitude) of the Wildfire Sensor.

• Link to Google Maps opens to show the location of the Wildfire Sensor that detected the fire. If Google Maps is not installed, it launches a browser and opens Google Maps in the browser.

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.

Fire alerts in Site Management app

When a sensor detects a fire, the same fire alert that is sent as an email also appears as a fire alert in the Site Management app.

Mute selected fire alerts

Fire alert notifications from specific sensors can be muted.

1. From the Alert Center, select a Site generating fire alerts.

2. From the Site, select a sensor generating fire alerts.

3. Select the checkbox next to the Sensor name. The Mute notification icon appears.

4. From the dropdown choose the reason for clearing the alert:

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

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

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

MQTT interface for fire alerts

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

The Silvanet Deployment app is used to deploy Border Gateways, Mesh Gateways and Wildfire Sensors. During deployment, a device's ID is into the app which links the current GPS location (longitude and latitude) to the device. This data is then saved to the Silvanet Cloud.

During Border and Mesh Gateway deployments, the Deployment app requires that a connectivity test is run before the device is mounted to the tree or pole. This ensures the gateways have reliable connectivity before the Wildfire Sensors are deployed.

Install

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 the language used for the Sign In screen.

Sites list

The Select Site screen appears displaying all Sites to which you have access. Any Site that has been added to an Organization in the Site Management app is displayed in the Silvanet Deployment app.

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

Site view

The Site view shows all planned and/or deployed devices in the Site, as well as the Packet to which each device belongs. You can either view the entire Site map or drill down to a specific device on the map.

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 (during deployment)

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

• To view a 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.

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

The Alert Center provides at a glance if any Wildfire Sensor from any accessible Site has generating a Fire Alert.

If no sensors are triggering alerts, this page indicates the status as All sites are currently safe.

Displayed alerts

If one or more sensors have triggered a Fire Alert, they are listed in the Alert Center. It shows which sensors triggered the alert and a Map of the Site that has the alerts.

Fire details

Expanding a sensor in the list displays which Wildfire Sensor triggered the alert, where it is located and a link which shows its location on a map.

Selecting the Location icon (arrow) opens a map (Google Maps) with a pin showing the location of the sensor that triggered the fire alert.

In this section

The Device overview section lists all deployed devices in a Site. Devices are sorted into Active, Inactive and Fire Alert. Troubleshooting messages are displayed when expanding a device that shows alerts or warnings.

Device listing

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

• Expand icon: Expand to display device information and data from the device shown as line graphs. Select the duration for the line graph from the Time dropdown (6 hours, 12 hours, 24 hours, 3 days or 10 days).

• Device icon: (Not sortable) Device type icon. Any alerts and warnings are overlaid on the icon.

• Name: (Sortable) Device name assigned to the device during deployment planning. This cannot be changed.

• Connectivity: (Sortable) Shows the device's level of signal strength based on RSSI (Receive Signal Strength Indicator) at the nearest Mesh Gateway.

• Energy: (Sortable) Shows the energy level of a Wildfire Sensor's supercapacitors.

• Firmware version: (Sortable) Current version of the firmware running in the device.

Device status

• Calibrating: (Wildfire Sensors) The Wildfire Sensor is in calibration mode, which takes 14 days after deployment. During this period, the Sensor does not provide reliable data and alerts.

• Active: (all devices) Indicates Silvanet Cloud can reach these devices and are sending data to the Silvanet Cloud.

• Pending: (all devices) The 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.

• Inactive: (all devices) Indicates device is not reachable. May be due to connectivity and/or charging issues. These issues need to be resolved immediately to ensure the device returns to Active state.

• Fire Alert: (Wildfire Sensors) Indicates a Wildfire Sensor has transmitted an alert. This also appears as a blinking icon in the app's Title Bar.

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.

The following shows an example Alert which need to be immediately resolved to ensure the device continues normal environmental monitoring.

The following shows an example Warning which should be resolved as soon as possible to allow the device to return to normal functioning.

Additional information that do not require user-interaction but affect device performance are provided as well.

Device data

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.

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.

In this tutorial, we demonstrate how to use the Planning tool to prepare a deployment plan.

The plan uses a Site that has paths, railways, roads and structures within a forested area. This is a typical WUI (Wildland Urban Interface) where wildland (forests and meadows) intersect with urban areas.

The Site also has areas that are typically inaccessible to most people which for deploying some Silvanet devices requires hiking off-trail through these forests with deployment tools and devices.

Steps

Views

After completing the Coverage planning, switch between views to ensure you have coverage in areas that may be hidden such as hills or valleys.

Terrain view (topology)

Switching to Terrain view shows the topology of the path and how it may affect message transmissions to/from the sensors.

Map view (urban/wilderness)

Switching to Map view highlights the urban and forested/park areas of the paths.

3D View (hills/valleys)

Select 3D View to rotate the site. This reveals areas that may not be covered by sensors or other deployment issues, such as steep hills that may be difficult to traverse.

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.

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

In this section

Gateway guidelines

Wildfire Sensor guidelines

The Planning tool provides a set of tools for rapidly estimating the number of Wildfire Sensors and Silvanet Gateways needed to cover a Site.

Overview

To generate an estimate of the number of Wildfire Sensors and Gateways needed for a given Site, use the Planning tool to do the following:

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

2. : Use the Area tool to define lower density deployment areas such as forested areas.

3. : 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.

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

5. : Export your plan which appears as a set of devices with their planned deployment locations.

Access the Planning tool

The Planning tool is accessible directly from the Site Dashboard of new and existing sites. Select Planning from the Ellipsis dropdown menu to open the Planning tool.

The Planning tool is displayed.

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.

• Help - Provides access to an external User Manual.

• Quit - Closes the Planning tool. Any work is lost if you do not save your work before closing.

Toolbar

The Toolbar provides access to tools for estimating the number of sensors in an area defined by polygon and line shapes, as well as gateways to ensure the area has connectivity. Comments can be added for relevant information.

• Select - Select items on the map.

• Path - Draw path-like areas to cover with sensors.

• Area - Draw areas to fill with sensors.

• Connectivity - Build a mesh of gateways.

• Comment - Add comments and annotation directly on the map.

Path tool (high density areas)

The Draw Path tool defines areas requiring a high density of sensors. Examples include hiking paths, lanes, roadways, rail lines, power lines or other areas that have linear dimensions.

Draw a path

1. Start path: Start creating a new path by clicking 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.

3. Settings: Use the Path Settings panel to name the path, set its type and distance between sensors. See below.

Path settings

The Path settings are accessed by selecting a path.

• Name - Give the path a descriptive name.

• Path type - Choose between different path presets which influence the placement of sensors on the path.

  • Hiking path

  • Road

  • Railway

  • Power line

• Level of protection - Adjust the level of protection of this item. A low level of protection is 100m between each sensor, a high level is 20m between each sensor.

• Distance between sensors - Level of protection slider sets the value in this field; however, you can enter a precise distance, as required.

• Amount of sensors - the value in this field is based on the length of the path and density; however, you can enter a precise number of sensors, as required.

Edit a path

1. Select a path, then in the Edit Path view, select the Pencil icon. The path becomes editable.

2. Make changes as required:

   1. Delete a point: Delete a point of the path by clicking on a white dot and press delete or backspace.

   2. Move a path: Move a path by selecting and dragging a white dot on the path.

   3. Add an angle: Add an angle (indicated by white dot) by selecting a yellow dot.

   4. Remove a path dot: Remove a path dot by selecting a white dot and press Delete or Backspace.

   5. Delete a path: When a path is active, select the Trash icon to delete a path.

3. Click anywhere on the map to deselect the path.

4. Save the project.

Area tool (low density areas)

The Draw Area tool defines large areas of a Site where a lower density of sensors is needed, such as areas of low human activity or almost no human activity. This can be areas typically off-limits to human activity, remote areas or forested areas. They even may have pathways running through them.

Draw an area

1. Start an area: Start creating a new area by clicking on the map where you want the area to start.

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

3. Settings: Use the Area Settings panel to name the area, define its accessibility (if inaccessible then no sensors are added), distance between sensors and amount of sensors.

Area Settings

The Area Settings is accessed by selecting an area.

• Name - Give the path a descriptive name.

• Surface covered - Automatically generated.

• Accessible - The slider defines the area as accessible or inaccessible. Making the area inaccessible prevents any sensors or gateway placed in this area. For example, it can be used to highlight areas which are physically or legally not accessible for your deployment.

• Protection Level - Slider to adjust the level of protection. A low level of protection is 500 m between each sensor, while a high level of protection is 100 m between each sensor. This is set by default at the mid-range of 200 m distance between sensors.

• Distance between sensors - Can be set manually or automatically using the Protection Level slider.

Edit an area

1. Select an area, then in the Edit Area view, select the Pencil icon. The area becomes editable.

2. Make changes as required:

   1. Add an angle: Select a a white dot, then drag it to add an angle. It also adds new midpoints.

   2. Delete an angle: Select a white dot, then press Delete or Backspace to remove the angle.

   3. Delete a dot: Select a dot, then press Delete or Backspace to remove the dot.

   4. Delete an area: Select the Trash icon to delete a area.

3. Click anywhere on the map to deselect the path.

4. Save the project.

Add or remove device manually

The Planning tool provides a Manual Planning tab when a path or area is selected. You can manually add or remove any type of device and edit a device's name and location for precise Site planning.

For example, when drawing a Path or an Area, the tool may have placed a sensor in a location free of trees or perhaps in a location where a sensor cannot be deployed such as on a building.

Add a Wildfire Sensor

1. Select an Area or a Path to display details.

2. Select the Manually Planning tab.

3. Select Add Sensor.

4. Move the mouse pointer over the map to move the new sensor to its final location, then click to place the sensor icon.

5. Save the project.

Edit/move/delete a Wildfire Sensor

1. In an area or path, select a Wildfire Sensor.

2. In the Edit Sensor dialog:

   • Change name: Change to a descriptive name as required.

   • Move Sensor: Using the mouse, move the sensor to update the latitude and longitude settings of the sensor.

   • Delete Sensor: Select Delete Sensor. This cannot be undone.

3. Save the project.

Define connectivity

After planning paths and areas, the sensors need LoRa connectivity to one or more gateways. The Plan Connectivity tool using the Site topology to define direct Line of Sight areas around a Border or Mesh Gateway. Each defined connectivity zone is identified by an irregular blue pattern on the map to show the range of a gateway based on the Site topology and the expected range of the gateway.

You first add a Border Gateway to ensure connectivity to the Internet. Find a location that is at the edge of a forest and, ideally, has access to a mains power supply. Then you add the Mesh Gateways to build up a Silvanet Mesh Network.

When placing a new gateway on the map, you can visualize the line of sight represented by a blue zone.

Add Gateways

1. Add Border Gateways: Place your first gateway by clicking on the map at the desired location. If you already know where your Border Gateway should be placed, start by placing your first gateway at this location.

2. Add Mesh Gateways: Extend network coverage by placing new gateways in the blue zone (connectivity zone) to extend the Mesh Network coverage. Place a gateway inside existing network coverage delimited by the blue zone.

3. Ensure sufficient network coverage: After placing gateways on the map, the tool estimates the network coverage. When it reaches a high enough coverage percentage, it is indicated by a Sufficient Coverage message.

4. Save the Project.

Edit Mesh Network

Location of Border and Mesh Gateways can be changed. Gateways can also be added or removed from the Connectivity Mesh (blue area).

1. Select the Connectivity Mesh.

2. Select a Gateway and make changes:

   • Change Name: Change the name as required.

   • Change Gateway type: Select either Mesh Gateway or Border Gateway to change the type of gateway to deploy.

   • Move Gateway: Move a Gateway by selecting a Gateway icon and dragging it to a new location. This updates the Latitude and Longitude settings.

   • Remove Gateway: Select a Gateway icon, then press Delete or Backspace to remove the Gateway from the map. This cannot be undone.

   • Moving Gateway outside of blue (connectivity) zone: By default, placing Gateways are not permitted outside of the mesh network coverage zone. However, you can override this limitation by holding Shift and placing a new gateway at the desired location.

3. Save the project.

Add comments

The Comments tool allows users to include additional information about the deployment or any other relevant topic. They can be added anywhere on the map.

• Add comment - select Comment and then click anywhere on the map to add a Comment field, then enter text. Remember to save the project.

• Deleted comment - erase the comment text to delete the comment item, then save the project.

Device estimation

Once you have created all the paths and areas you wish to protect and have placed gateways to ensure sufficient mesh network coverage, the device counter on top of the map will display the estimated number of sensors and gateways required. This estimation can be used for quoting purposes.

The Device Counter keeps track in real time of all Border Gateways, Mesh Gateways and Sensors placed on the Site.

• Gateway counters - shows estimated number of Border and Mesh Gateways required based on the number of gateways added to the map.

• Sensor counter - shows estimated number of sensors required based on the paths and polygons added to map.

Export planning summary

After completing the Site plan, export a Planning Summary. This generates an editable .docx file that includes an overview of site planning, details of the connectivity network and a comprehensive view of each planned packet. It also provides an estimate of the deployment time.

From the header bar of the Planning tool, select Export Summary.

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

• Density per hectare: This is related to sensor density, except that in this case you need to know where in the forest is the (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 .

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

Add new Packet

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

1. Log in to 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

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.

Before going to the Site to deploy the Silvanet devices, ensure you have prepared (at a minimum) for a day's Silvanet deployment efforts. You need to use the Deployment app to register the Device ID by scanning a QR Code on the device. Aftewards, you mount the device. Finally, you run Connectivity Tests for Border and Mesh Gateways. Wildfire Sensors need 14 days to calibrate (before this ends, the Sensor does not send usable data).

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

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

• Use toolboxes for the required devices and tools: Use a waterproof box with a handle to keep the devices safe and dry while in the forest. Another carry case can be used for the required tools. See Deployment tools.

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

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

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

• Open the relevant Site in the Deployment app: Before entering the forest, ensure you have the relevant Site opened. For details, see Deployment app.

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

Border Gateway deployment steps

1. Register the Border Gateway.

2. Mount the Border Gateway.

3. Run Connectivity Test.

Deployment overview

• Choose deployment scenario

  • Mains (via PoE) and router (via Ethernet): Uses mains power supply and a router for Internet connectivity

  • Mains (via PoE) and mobile networks: Uses mains power supply and cellular networks for Internet connectivity

  • Remote locations: Uses solar panel and cellular networks for Internet connectivity

  • Loss of Internet and power supply: Uses solar panel and satellite connectivity.

• Choose Border Gateway location

  • Forest edge: The Border Gateway location should be chosen carefully. If possible, mount the Border Gateway at the edge of a forest.

  • Sufficient sunlight: If the Border Gateway is powered by only by solar, select a sunny location with direct sunlight.

  • Mount in an elevated location: To maximize range, install the Border Gateway on a hill, or at least a higher location to maximize range.

• Ensure reliable Internet connectivity

  • Mobile or router: Based on selected scenario, use a router for Internet connectivity (recommended) or mobile connectivity with its built-in 4G/LTE-M with 2G/GPRS fallback.

  • Satellite for backup: For satellite connectivity, the Border Gateway needs a clear line of sight to connect to a satellite.

• Ensure within range to Mesh Network

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

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

• Mount Border Gateway correctly

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

  • Stable metal or wooden pole: Mount to a stable metal pole that is unlikely to be moved. Use the provided U-Bolt Clamps to securely hold the Border Gateway and can be tightened accordingly without damaging the device. Also, on a pole, the Border Gateway does not interfere with a living tree over the lifetime of the Border Gateway.

  • Correct diameter for pole (60.3 mm): The diameter of a pole used to support the Border Gateway must not be greater than 60.3 mm. A 17 mm wrench is used to attach the M10-nuts to the U-Bolt Clamps.

  • Mount towards the top of pole: To maximize the radio contact when attaching the Border Gateway to a pole, put the Gateway on top of the pole (if possible) so that the LoRa antenna is above the top of the pole.

  • Healthy tree: If the Border Gateway is attached to a tree, ensure it is attached to a healthy tree and not expected to be cut down.

• Clear any obstructions

  • Whether the Border Gateway is installed on a tree or a pole, it needs a clear line of sight to communicate via wireless mobile networks or satellite communication.

  • It also needs an unobstructed area to obtain sufficient sunlight for the solar panel to charge the Border Gateway in case of power failure.

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

• Mount solar panel correctly

  • Towards sun (at noon): Mount the solar panel facing the sun at 12:00 noon (northern or southern hemisphere).

  • True south/north: 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.

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

• Use backup Border Gateway, if required

  • For 1000 sensors or more: Ideally, for deployments greater than 1000 sensors, provide a backup Border Gateway.

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 propogation 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 also 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.

Mesh Gateway deployment steps

• Register the Mesh Gateway.

• Mount the Mesh Gateway.

• Run Connectivity Test.

Deployment overview

• Ensure correct range

  • 2 km to 3 km to Border Gateway: Deploy at least one Mesh Gateway at least 2 km to 3 km from a Border Gateway, depending on environmental conditions including topology and type of forest.

  • 2 km to 3 km to other Mesh Gateway(s): The range of a Mesh Gateway to other Mesh Gateways and Border Gateway is approximately 2 km to 3 km. The actual range may vary depending on environmental conditions.

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

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

• Mount Mesh Gateway correctly

  • Maximum 60.3 mm pole: U-Clamps are provide to attach the Mesh Gateway a (maximum) 60.3 mm metal pole that is at least 3 m high above the forest floor. Use a 17 mm wrench to attach the provided M10-nuts to the U-Bolt Clamps. Additionally, the device does not interfere with a living tree over the lifetime of the Mesh Gateway.

  • Above 3 m on pole or tree: To protect the Mesh Gateway from human or animal interference and to give a better line of sight to other Getaways within range, install the device at least 3 meters above the forest floor, or higher for better signal propagation.

  • Healthy tree: Deploy the Silvanet Mesh Gateway to a healthy tree or to a stable self-standing poles that is unlikely to be moved.

  • Towards sun (at noon): Mount the Mesh Gateway facing the sun at 12:0 noon (northern or southern hemisphere). To receive maximum sunlight, it is best installed on a pole.

  • Hillsides: To increase communication, mount on hillsides.

  • Free of obstructions: The Mesh Gateway has a large built-in solar panel to provide for the Mesh Gateway's increased power requirements. However, the solar panel needs an unobstructed area to obtain sufficient sunlight to charge the device.

  • Clear small branches: If installed on a tree, it should not be obstructed by branches. You may need to clear some branches away from the solar panel. Do not cut large branches.

Wildfire Sensor deployment steps

1. Register the Wildfire Sensor.

2. Mount the Wildfire Sensor to selected tree.

3. Wait 14 days for the Wildfire Sensor to calibrate.

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.

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.

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.

In this section

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.

Sensor range

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 (VOCs), 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.

Sensor ratios

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.

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

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

Provide at least the following tools for device deployment:

• Knife and shears (snips) for trimming branches (if required) and for cutting lengths of garden wire

• Small axe or chisel for removing small sections of the outer bark

• Compass (analogue or an app on the Smartphone)

• Cordless drill for drilling holes for treenails (min 18V) and backup battery pack

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

• Hammer for treenails

• 17 mm wrench for the U-clamp bolts

• Pencil and notepad

• Backup power supply for Smartphones

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.

Deploying Silvanet Border Gateways, Mesh Gateways and Wildfire Sensors takes three simple steps:

• Scan QR Codes

• Mount the devices on a tree or pole (in the case of Border Gateways, mount solar panels)

• Test connectivity (in the case of Gateways) or calibrate (in the case of Wildfire Sensors)

Each Silvanet Border Gateway has its own unique Device ID (also referred to as Serial ID). It is provided as a unique text string as well as a QR Code printed on a label attached to the Border Gateway. The Deployment app uses the smartphone's camera to allow the user to scan the device's QR Code.

After the Border Gateway is registered with the Silvanet Cloud, the latitude and longitude of the device in the Site is provided to the Site Details section of the Site Management app.

Scan QR Code

The following shows the steps to register the Device ID (Serial ID) by scanning the QR Code of the Border Gateway.

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

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

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

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

1. Once the deployment location is found, scan the device's QR Code which is attached to the back of the Border Gateway. The Deployment app automatically fills in the Gateway's latitude and longitude using the Smartphone's GPS location.

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

Next step

After a successful registration, mount the Border Gateway to a tree or pole.

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

Go ahead and mount the Border Gateway to a metal or wood pole or on a tree, as described in the following sections. Afterwards, mount the solar panel to provide a power supply. Alternately, use the PoE Injector to provide power from mains.

Mount Border Gateways to metal/wood poles

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

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

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

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

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

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

Mount Border Gateways to trees

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

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

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

1. With a distance between the holes at 70 mm, drill approximately 6-7 cm (2 1/5 inches) into the tree for the top loops. Ensure you do not split the tree or drill on an angle. Use the 10mm drill bit. When drilling into a tree, first drill a pilot hole using a small drill bit (1/4 inch / 6mm) then drill the final hole with the 10mm drill bit. Also, ensure you are using a drill bit for wood. This ensures the wood in the tree does not split.

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

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

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

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

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

Mount solar panel

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

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

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

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

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

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

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

To mount solar panel to pole or tree:

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

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

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

1. Follow the same procedure with the lower cable.

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

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

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

Connect Border Gateway to Ethernet (PoE)

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

1. Open the Ethernet connector by unscrewing the cap.

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

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

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

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

1. Connect the supplied Ethernet cable to the PoE and then connect an Ethernet cable from the PoE to a router.

2. Plug in the PoE to a mains power supply.

Next step

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

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

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

Go ahead and mount the Mesh Gateway to a metal or wood pole or on a tree, as described in the following sections.

Attach Mesh Gateways to poles

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

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

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

2. Attach the LoRaWAN antenna to the Mesh Gateway.

Attach Mesh Gateways to trees

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

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

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

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

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

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

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

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

2. Attach the LoRaWAN antenna to the Mesh Gateway.

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

Next step

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

Each Silvanet Wildfire Sensor has a unique Device ID (also referred to as Serial ID) provided as a unique text string as well as a QR Code printed on a label attached to the device.

Before mounting the Sensor, use the Deployment app to scan the device's QR Code. Afterwards, the Silvanet device is registered with the Silvanet Cloud. This provides the location of the device to the Silvanet Cloud. Afterwards, the registered device appears in the Site details section of the Site Management app.

Register Device ID

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

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

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

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

1. Once the deployment location is found, scan the device's QR Code which is attached to the back of the Sensor. The Deployment app automatically fills in the Sensor's latitude and longitude using the Smartphone's GPS location.

1. After successfully scanning the QR Code, the Deployment app shows a Registration successful screen. The device icon changes from Planned to Deployed. For more information, see Status icons.

Next step

After a successful registration, you can now mount the Wildfire Sensor to the tree.

Run Connectivity Test

Use the Deployment app to begin the Connectivity test. This checks if the Mesh Gateway can connect with any neighboring Mesh Gateways or Border Gateways.

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

1. The Deployment app begins to connect with a Border Gateway.

1. The Mesh Gateway then runs the connectivity test and attempts to connect to another Mesh Gateway or Border Gateway.

1. If the Mesh Gateway could connect, a success message appears. You can close the dialog and continue deploying the next device or tap Show Device Details.

1. The Device Details screen appears. You can add additional information in the Notes field such as relevant details about the deployment location.

Border Gateway not reachable

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

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

1. Review the information provided in Border Gateway not reachable for troubleshooting information.

Signal too weak from neighboring gateways

If the Mesh Gateway could reach another Mesh Gateway but the signal is too weak, troubleshooting information is provided.

1. If the Device connectivity is too low, the following dialog appears.

• Check the following to troubleshoot connectivity:

  • Check device orientation: Make sure the Mesh Gateway is oriented towards the sun at 12:00 noon (northern/southern hemisphere). After confirming it is oriented in the correct direction, retry the Connectivity Test.

  • Wait for the device to be charged: If the superconductors in the device discharged during transit or were stored in a box or backpack, it can take some time to charge the superconductors and switch on. Give the device at least a half-day to charge then retry the Connectivity Test.

  • Find another location: If after confirming the device is oriented properly and is charged, the Mesh Gateway may be deployed too far away from the neighboring gateways. Move the device 60m (200ft) closer to an active gateway using the network map, then restart the Connectivity Test.

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

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

Mesh Gateway not reachable

If the Silvanet Cloud cannot reach the Mesh Gateway you are deploying, use the same troubleshooting steps as described in Signal too weak from neighboring gateways.

Next Steps

With the Mesh Gateway now connected to the Silvanet Cloud, go ahead and continue mounting the remaining Mesh Gateways in the deployment plan.

After gas scans - 30 to 60 minutes to stabilize

After a Wildfire Sensor runs internal gas scans to test air quality, the sensor needs approximately 30 to 60 minutes to be ready to detect fires (stabilze).

When the Wildfire Sensor's internal Bosch gas sensor detects , it performs a set of gas scans to determine the type of VOC. After these gas scans are complete, it begins to stabilize and return to normal values.

This stabilization period allows for the dissipation of any smoke retained inside the sensor mesh (a small pot with a mesh cover used by the gas sensor). Ideally, the longer the wait, the more time the smoke has to dissipate.

After sensor interactions - 5 days to stabilize

Interactions cause the Wildfire Sensor to repeat of the calibration process, but not a complete 14-day recalibration. This type of recalibration takes at least 5 days.

This includes, but not exclusively, the following types of interactions:

• Touching the sensors, such as adjusting the angle of the sensor or attempting to pull it off the tree

• Moving the sensors to another tree or to another location on the tree

• Animals or humans breathing directly on the Wildfire Sensors.

• Exhaust from vehicles (especially diesel trucks).

• Bringing any source of VOC near the sensor such as cigarettes or fumes from running machinery.

Overview

Inform local fire department

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

Use a realistic test location

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

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

Use homogeneous material

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

Review the requirements for plant material in the following table.

Burn a realistic test fire

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

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

Ensure test fire burns for at least 30 minutes

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

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

Take note of smoke behavior