diff --git a/Console/Makefile b/Console/Makefile
index 88373cd..8ce0d55 100644
--- a/Console/Makefile
+++ b/Console/Makefile
@@ -21,7 +21,7 @@ pages-debug:
sourcepack:
@echo Packing firmware sources...
- zip --junk-paths -r build/rnode_firmware.zip ../arduino-cli.yaml ../Bluetooth.h ../Config.h ../Console.h ../Device.h ../Display.h ../Framing.h ../Graphics.h ../LICENSE ../LoRa.cpp ../LoRa.h ../Makefile ../MD5.cpp ../MD5.h ../partition_hashes ../Power.h ../README.md ../release_hashes.py ../RNode_Firmware.ino ../ROM.h ../Utilities.h
+ zip --junk-paths -r build/pkg/rnode_firmware.zip ../arduino-cli.yaml ../Bluetooth.h ../Config.h ../Console.h ../Device.h ../Display.h ../Framing.h ../Graphics.h ../LICENSE ../LoRa.cpp ../LoRa.h ../Makefile ../MD5.cpp ../MD5.h ../partition_hashes ../Power.h ../README.md ../release_hashes.py ../RNode_Firmware.ino ../ROM.h ../Utilities.h
data:
@echo Including assets...
diff --git a/Console/assets/images/3_conv.webp b/Console/assets/images/3_conv.webp
new file mode 100644
index 0000000..85d0ecd
Binary files /dev/null and b/Console/assets/images/3_conv.webp differ
diff --git a/Console/assets/images/an1.webp b/Console/assets/images/an1.webp
new file mode 100644
index 0000000..d8ae21e
Binary files /dev/null and b/Console/assets/images/an1.webp differ
diff --git a/Console/assets/images/bg_h_2_orig.webp b/Console/assets/images/bg_h_2_orig.webp
deleted file mode 100644
index 81473d5..0000000
Binary files a/Console/assets/images/bg_h_2_orig.webp and /dev/null differ
diff --git a/Console/assets/images/g2p.webp b/Console/assets/images/g2p.webp
new file mode 100644
index 0000000..d645739
Binary files /dev/null and b/Console/assets/images/g2p.webp differ
diff --git a/Console/assets/images/g3p.webp b/Console/assets/images/g3p.webp
new file mode 100644
index 0000000..e9dac9f
Binary files /dev/null and b/Console/assets/images/g3p.webp differ
diff --git a/Console/assets/images/g4p.webp b/Console/assets/images/g4p.webp
new file mode 100644
index 0000000..523c0cd
Binary files /dev/null and b/Console/assets/images/g4p.webp differ
diff --git a/Console/assets/images/lora_rnodes.webp b/Console/assets/images/lora_rnodes.webp
new file mode 100644
index 0000000..d475b43
Binary files /dev/null and b/Console/assets/images/lora_rnodes.webp differ
diff --git a/Console/assets/images/nn_an.webp b/Console/assets/images/nn_an.webp
new file mode 100644
index 0000000..63c4245
Binary files /dev/null and b/Console/assets/images/nn_an.webp differ
diff --git a/Console/assets/images/nn_conv.webp b/Console/assets/images/nn_conv.webp
new file mode 100644
index 0000000..c66d18a
Binary files /dev/null and b/Console/assets/images/nn_conv.webp differ
diff --git a/Console/assets/images/nn_init.webp b/Console/assets/images/nn_init.webp
new file mode 100644
index 0000000..3b3a46f
Binary files /dev/null and b/Console/assets/images/nn_init.webp differ
diff --git a/Console/assets/stl/Handheld_RNode_v2.1_Parts.7z b/Console/assets/stl/Handheld_RNode_Parts.7z
similarity index 100%
rename from Console/assets/stl/Handheld_RNode_v2.1_Parts.7z
rename to Console/assets/stl/Handheld_RNode_Parts.7z
diff --git a/Console/source/builds/handheld.md b/Console/source/builds/handheld.md
index b76b9f1..0156af2 100644
--- a/Console/source/builds/handheld.md
+++ b/Console/source/builds/handheld.md
@@ -62,7 +62,7 @@ In addition to the board, you will need a few other components to build this RNo
### Step 4: 3D Print Parts
-To complete the build of this RNode, you will need to 3D-print the parts for the casing. Download, extract and slice the STL files from the [parts package]({ASSET_PATH}3d/Handheld_RNode_v2.1_Parts.7z) in your preffered software.
+To complete the build of this RNode, you will need to 3D-print the parts for the casing. Download, extract and slice the STL files from the [parts package]({ASSET_PATH}3d/Handheld_RNode_Parts.7z) in your preffered software.
- Two of the parts should are LED light-guides, and should be printed in a semi-translucent material:
- The `LED_Window.stl` file is a light-guide for the NeoPixel LED, mounted in the circular cutout at the top of the device.
diff --git a/Console/source/guides/install_firmware.md b/Console/source/guides/install_firmware.md
index d4bd4c5..64bb14f 100644
--- a/Console/source/guides/install_firmware.md
+++ b/Console/source/guides/install_firmware.md
@@ -1,6 +1,6 @@
[date]: <> (2023-01-12)
[title]: <> (Installing RNode Firmware on Supported Devices)
-[image]: <> (images/a801c7a0-b75b-48c5-8ce7-8cb07012fc96-400x275.jpg)
+[image]: <> (images/g2p.webp)
[excerpt]: <> (If you have a T-Beam or LoRa32 device handy, it is very easy to get it set up for all the things that the RNode firmware allows you to do.)
{DATE}
# Installing RNode Firmware on Supported Devices
@@ -18,8 +18,8 @@ So let's get started! You will need either a **LilyGO T-Beam v1.1**, a **LilyGO
It is currently recommended to use one of the following devices: A **LilyGO LoRa32 v2.1** (also known as **TTGO T3 v1.6.1**) or a **LilyGO T-Beam v1.1**.
-
-*Some of the device types compatible with this installation guide*
+
+*Some of the device types compatible with this installation guide*
## Device Variations
diff --git a/Console/source/guides/loracomms.md b/Console/source/guides/loracomms.md
index a8fa550..e8657d6 100644
--- a/Console/source/guides/loracomms.md
+++ b/Console/source/guides/loracomms.md
@@ -6,7 +6,7 @@
# Private, Secure and Uncensorable Messaging Over a LoRa Mesh
*Or: How to set up a completely private, independent and encrypted communication system in half an hour, using stuff you can buy for under $100.*
-
+
In this post, we will explore how two people, Alice and Bob, can set up a LoRa mesh communication system for their use that has the following characteristics:
@@ -39,7 +39,7 @@ First of all, Alice and Bob need to get a compatible piece of radio hardware to
They take a look at the RNode Firmware [Supported Devices List](https://unsigned.io/rnode_firmware/#supported-hardware) , and decide to go with a couple of LilyGO T-Beam devices. They could have also used others, and they don't need to choose the same device, as long as they are within the same frequency range, all compatible devices work with Reticulum and can communicate with each other, as soon as the RNode Firmware has been installed on them.
-
+
Once the devices arrive, it is time to get the firmware installed. For this they will need a computer running some sort of Linux. Alice has a computer with Ubuntu installed, so they decide to use that. Since Python3 came installed as standard with the OS, Alice can go ahead and install the RNode configuration program by simply opening a terminal and typing:
@@ -74,7 +74,7 @@ nomadnet
All required directories and configuration files will now be created, and the client will start up. After a few seconds, Alice will be greeted with a screen like this:
-
+
Confirming that everything is installed and working, it is time to add the LoRa radio as an interface that Reticulum can use. To do this, she opens up the Reticulum configuration file (located at `˜/.reticulum/config`) in a text editor.
@@ -218,19 +218,19 @@ For an LXMF address to be reachable for direct-delivery instant messaging on a R
To make sure his public cryptographic key is known by the network, Bob taps the **Announce** button in the Sideband app:
-
+
After a few seconds, Bobs announce shows up in the **Announce Stream** section of the Nomad Network program on Alices computer:
-
+
Using the received announce, Alice starts a conversation with Bob. Either one of them could also have started the conversation by manually typing in the others LXMF address in their program, but in many cases it can be convenient to use the announces. Now that everything is ready, they exchange a few messages to test the system. On Bobs Android phone, this looks like this:
-
+
And on Alices computer running Nomad Network, it looks like this:
-
+
Although pretty useful, what we have explored here does not even begin to scratch the surface of what is possible with Reticulum and associated software. I hope you will find yourself inspired to explore and read deeper into the documentation and available software.
diff --git a/Console/source/guides/make_rnodes.md b/Console/source/guides/make_rnodes.md
index c002fc1..b9483e4 100644
--- a/Console/source/guides/make_rnodes.md
+++ b/Console/source/guides/make_rnodes.md
@@ -1,6 +1,6 @@
[date]: <> (2023-01-10)
[title]: <> (How To Make Your Own RNodes)
-[image]: <> (images/e4261dcb-49e5-4cd3-856e-c44fb7522b32-400x275.jpg)
+[image]: <> (images/g3p.webp)
[excerpt]: <> (This article will outline the general process, and provide the information you need, for building your own RNode from a few basic modules. The RNode will be functionally identical to a commercially purchased board.)
{DATE}
# How To Make Your Own RNodes
@@ -11,8 +11,8 @@ Once you have learned the put together a custom RNode with your own choice of co
If you haven't already, you migh also want to check out how to [install the RNode firmware directly on pre-made LoRa development boards](https://unsigned.io/installing-rnode-firmware-on-supported-devices/).
-
-*A homemade RNode, based on an ESP32 board and a transceiver module, ready for use*
+
+*A homemade RNode, based on an ESP32 board and a transceiver module, ready for use*
Since there is not *one right way* to cut this pie, this article will probably not give the *exact* steps for the combination of components you choose, but will instead attempt to provide you with the information you need to build RNodes from a wide variety of microcontroller boards and LoRa modules. Generally speaking, you will need three things to construct a working RNode:
diff --git a/Console/source/guides/tnc_mode.md b/Console/source/guides/tnc_mode.md
index da38576..a2a549b 100644
--- a/Console/source/guides/tnc_mode.md
+++ b/Console/source/guides/tnc_mode.md
@@ -1,6 +1,6 @@
[date]: <> (2023-01-07)
[title]: <> (Using RNodes With Amateur Radio Software)
-[image]: <> (images/xastir2-e1643321757361-400x275.jpg)
+[image]: <> (images/g4p.webp)
[excerpt]: <> (If you want to use an RNode with amateur radio applications, like APRS or a packet radio BBS, you will need to put the device into TNC Mode. In this mode, an RNode will behave exactly like a KISS-compatible TNC, which will make it usable with any amateur radio software.)
{DATE}
# Using RNodes With Amateur Radio Software
diff --git a/Console/source/help.md b/Console/source/help.md
index c50cd08..d6dd72d 100644
--- a/Console/source/help.md
+++ b/Console/source/help.md
@@ -2,7 +2,6 @@
## Get Help
If you are having trouble, or if something is not working, this RNode contains a number of useful resources.
-- The [unsigned.io](https://unsigned.io/) website
- Read [Questions & Answers](qa.html) section
- Read the [Reticulum Manual](m/index.html) stored on this RNode
- Browse a copy of the [Reticulum Website](r/index.html) stored on this RNode
diff --git a/Console/source/learn.md b/Console/source/learn.md
index 27aa71b..9175c6f 100644
--- a/Console/source/learn.md
+++ b/Console/source/learn.md
@@ -2,10 +2,10 @@
## Learn More
This RNode contains a selection of tutorials and guides on setting up communications, creating RNodes, building networks and using Reticulum. You can find additional information in the following sections:
-- The [unsigned.io](https://unsigned.io/) website
- The [Questions & Answers](qa.html) section
- The [Reticulum Manual](m/index.html) stored on this RNode
- A copy of the [Reticulum Website](r/index.html) stored on this RNode
+- The [unsigned.io](https://unsigned.io/) website
## Guides
diff --git a/Console/source/replicate.md b/Console/source/replicate.md
index f455aea..899078f 100644
--- a/Console/source/replicate.md
+++ b/Console/source/replicate.md
@@ -5,7 +5,7 @@ This section contains the tools and guides necessary to create more RNodes. Crea
In addition, you are very much **encouraged** to create RNodes for sale or commercial purposes. Doing so requires buying a copy of the RNode Firmware for each unit produced for commercial purposes. Please read the [selling RNodes]({ASSET_PATH}sell_rnodes.html) section for more details.
### Firmware Source Code
-If you would like to inspect or compile the RNode Firmware source code yourself, you can download a copy of the [RNode Firmware source-code]({ASSET_PATH}rnode_firmware.zip) stored in this RNode.
+If you would like to inspect or compile the RNode Firmware source code yourself, you can download a copy of the [RNode Firmware source-code]({ASSET_PATH}pkg/rnode_firmware.zip) stored in this RNode.
### Getting Started
To create your own RNodes, there are generally three distinct paths you can take:
diff --git a/Console/source/sell_rnodes.md b/Console/source/sell_rnodes.md
new file mode 100644
index 0000000..7537bc5
--- /dev/null
+++ b/Console/source/sell_rnodes.md
@@ -0,0 +1,2 @@
+[title]: <> (Sell RNodes)
+## Build & Sell RNodes
diff --git a/Console/source/software.md b/Console/source/software.md
index 8dfaf27..37a544e 100644
--- a/Console/source/software.md
+++ b/Console/source/software.md
@@ -6,7 +6,11 @@ This RNode contains a repository of downloadable software and utilities, that ar
If possible, you can check that the `SHA-256` hashes of any downloaded files correspond to the list of release hashes published on the [Reticulum Release page](https://github.com/markqvist/Reticulum/releases).
-**You Have The Source!** Due to the size limitations of shipping all this software within an RNode, we don't include separate source-code archives for the below programs, but *all the source code is included within the Python .whl files*! You can simply unzip any of them with any program that understands `zip` files, and you will find the source code inside the unzipped directory (for some zip programs, you may need to change the file ending to `.zip`).
+**You Have The Source!** Due to the size limitations of shipping all this software within an RNode, we don't include separate source-code archives for the below programs, but *all the source code is included within the Python .whl files*!
+
+You can simply unzip any of them with any program that understands `zip` files, and you will find the source code inside the unzipped directory (for some zip programs, you may need to change the file ending to `.zip`).
+
+You can also download the copy of the [RNode Firmware source-code]({ASSET_PATH}pkg/rnode_firmware.zip) that is stored in this RNode.
Choose a software package to get started
diff --git a/Release/spiffs.bin b/Release/spiffs.bin
index aac51b2..46347f4 100644
Binary files a/Release/spiffs.bin and b/Release/spiffs.bin differ