From a5360c9801fb9fdafbc83ce95e13528ed4aacd30 Mon Sep 17 00:00:00 2001 From: ab7pa Date: Mon, 5 Aug 2024 08:26:13 -0700 Subject: [PATCH] newUI-65 --- arednGettingStarted/downloading_firmware.rst | 4 ++-- arednGettingStarted/selecting_devices.rst | 8 +++----- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/arednGettingStarted/downloading_firmware.rst b/arednGettingStarted/downloading_firmware.rst index 75aa536..3046e9a 100644 --- a/arednGettingStarted/downloading_firmware.rst +++ b/arednGettingStarted/downloading_firmware.rst @@ -5,7 +5,7 @@ Downloading AREDN® Firmware Types of Firmware ----------------- -**Stable Release** firmware has been tested and shown work on the devices that were supported at the time of the release. This firmware is considered to be stable and suitable for production devices deployed in the field. Stable Release firmware is identified by numbers such as ``3.23.4.0``. In this example ``23.4`` indicates the year (2023) and month (April) of the Stable Release. +**Stable Release** firmware has been tested and shown to work on the devices that were supported at the time of the release. This firmware is considered to be stable and suitable for production devices deployed in the field. Stable Release firmware is identified by numbers such as ``3.24.6.0``. In this example ``24.6`` indicates the year (2024) and month (June) of the Stable Release. **Nightly Build** firmware contains the latest bug fixes, features, and support for new devices. It allows the wider mesh community to test new code before it is included in a Stable Release. The Nightly Build is considered more experimental or cutting-edge and may not be suitable for production nodes. However, it might make sense to install the Nightly Build if you are having a specific issue that has been addressed in newly developed code or if you are loading AREDN® firmware onto a device that is newly supported. The Nightly Build filename shows the build date and the software commit identifier for that specific firmware build. Be aware that when a new nightly build appears, any older builds automatically become obsolete. If you want to install add-on packages for nodes running a nightly build, understand that specific packages are not available for an *older* build if a *newer* build has superseded it. Be sure to upgrade to the current nightly build before installing packages. @@ -37,7 +37,7 @@ Mikrotik If you are loading firmware on Mikrotik devices for the first time you must download **both** the *KERNEL* and *SYSUPGRADE* images. Otherwise download only the *SYSUPGRADE* firmware image. GL.iNET - For GL.iNet devices you will only see the *SYSUPGRADE* image for both first-time installs or firmware upgrades. + For GL.iNet devices you will only see the *SYSUPGRADE* image for both first-time installs and firmware upgrades. Click the appropriate button to download the image file to your local computer. Make a note of the download location on your computer, since you will use the downloaded image(s) to install the AREDN® firmware on your device. diff --git a/arednGettingStarted/selecting_devices.rst b/arednGettingStarted/selecting_devices.rst index de8c7c8..493f8c7 100644 --- a/arednGettingStarted/selecting_devices.rst +++ b/arednGettingStarted/selecting_devices.rst @@ -2,7 +2,7 @@ Selecting Radio Hardware ======================== -The amateur radio community has recognized the benefits of using inexpensive commercial :abbr:`WISP (Wireless Internet Service Provider)` radios to create AREDN® networks. Each of these devices come with the vendor's firmware pre-installed, but by following a few instructions this firmware can be replaced with an AREDN® firmware image. +The amateur radio community has recognized the benefits of using inexpensive commercial :abbr:`WISP (Wireless Internet Service Provider)` radios to create AREDN® networks. Each of these devices comes with the vendor's firmware preinstalled, but by following documented procedures this firmware can be replaced with an AREDN® firmware image. Several open source software projects have been adapted and enhanced to create the AREDN® firmware, including `OpenWRT (Open Wireless Router) `_ and `OLSR (Optimized Link State Routing protocol) `_. @@ -10,15 +10,13 @@ The AREDN® team builds specific firmware images tailored to each type of radio, When selecting a device for your AREDN® hardware there are several things to consider in your decision. -- Radios should be purchased for the specific frequency band on which they will operate. Currently AREDN® supports devices which operate in several bands. Check the `frequency and channel chart `_ on the AREDN® website for the latest information. - -- Many devices have an integrated dual-polarity :abbr:`MIMO (Multiple Input-Multiple Output)` antenna which helps to leverage multipath propagation. AREDN® has always supported and recommended using MIMO hardware, since these devices typically outperform single chain radios when used as mesh nodes. +- Radios should be purchased for the specific frequency band on which they will operate. Currently AREDN® supports devices which operate in several bands. Check the `frequency and channel chart `_ on the AREDN® website for the latest information. - Radios can be purchased separately from the antenna, so it is possible to have more than one antenna option for a radio in order to optimize AREDN® nodes for varying deployment conditions. - Costs of devices range from $25 to several hundred dollars for a complete node/antenna system, so there are many options even for the budget-conscious operator. -- Some older or lower cost devices have a limited amount of onboard memory, but firmware images continue to grow in size and functionality. Consider purchasing a device with more memory over one with less memory. +- Some older or lower cost devices have a limited amount of onboard memory. Consider purchasing a device with more memory over one with less memory. - Check the maximum power output of the device, since some devices have lower power capabilities.