A Connecticut Mesh Technologies User Group
-diff --git a/_redirects b/_redirects index b76d0ed..ff2885e 100644 --- a/_redirects +++ b/_redirects @@ -1 +1,7 @@ -/discord https://discord.gg/m4F328as3K 302 \ No newline at end of file +/discord https://discord.gg/m4F328as3K 302 +/merch https://ctmesh.redbubble.com 302 +/store https://ctmesh.redbubble.com 302 +/map https://map.ctmesh.org 302 +/resources https://ctmesh.org/meshcore-resources 302 +/coverage https://bdl.meshmapper.net 302 +/analyzer https://analyzer.letsmesh.net/packets?region=BDL 302 \ No newline at end of file diff --git a/favicon.png b/favicon.png index 0ee0f6e..8c4fed8 100644 Binary files a/favicon.png and b/favicon.png differ diff --git a/favicon_sq.png b/favicon_sq.png new file mode 100644 index 0000000..0ee0f6e Binary files /dev/null and b/favicon_sq.png differ diff --git a/index.html b/index.html index 854732b..76bd90e 100644 --- a/index.html +++ b/index.html @@ -9,12 +9,12 @@ - + - + @@ -22,23 +22,23 @@ - + - - - - - - - - + + + + + + + + - +
These tools use data reported to our MQTT server by nodes across the state.
Key size: 128 bit
Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own map and other web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage. If that describes your setup, follow the steps at on this page to get set up.
+Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own map and other web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage. If that describes your setup, follow the steps at on this page to get set up.
+
+ This guide walks through the full repeater workflow: choose or build a MeshCore-compatible repeater node, flash and configure it over USB, then finish programming it from your phone using a separate companion node.
+A repeater is the fixed radio that stays installed to relay traffic for the mesh. A companion is a second node you use to reach and manage that repeater from the MeshCore mobile app. The flow here is: build if needed, flash and configure over USB, test companion-based setup, then deploy the node.
+ + + +Start with the build section if you are assembling a repeater from parts. If you already have a finished repeater or an off-the-shelf device, begin at the flash section instead.
+If you already have a repeater build or a ready-made device, skip this section and go straight to Flash the Repeater Node.
+This is the point where everyone should start if the repeater hardware already exists.
+esptool.py, if flashing manuallyAn optional power-saving mode is covered in the addendum at the bottom of this guide.
+esptool.pyesptool.py if needed.esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 write_flash -z 0x0 firmware.bin.uf2.uf2 firmware file for your RAK device from the MeshCore GitHub releases page..uf2 firmware file onto that drive and allow the device to reboot when the copy finishes.After flashing by any supported method, finish the initial repeater configuration over USB before trying to complete setup through the companion.
+config.meshcore.io.set path.hash.mode 1 to set 2 byte mode. View screenshot View resultset path.hash.mode 2 for 3 byte mode, but that reduces the hop limit from 32 hops in 2 byte mode to 21 hops in 3 byte mode.For tree installs, a common approach is to use a slingshot to place a lightweight mason line over a suitable branch, then use that line to pull up a stronger rope for hoisting and securing the node. Choose a healthy branch, avoid power lines, and make sure the enclosure and antenna can hang clear without rubbing through on bark or hardware.
+Nodes can also be attached to the side of a structure, a mast, a fence post, or a utility-style pole using appropriate brackets, hose clamps, or other weather-resistant mounting hardware. Keep the enclosure secure, keep cable runs tidy, and position the antenna with as much clear exposure as practical.
+Other logical mounting options include sheds, garages, balcony rails, old TV antenna mounts, rooftop masts, and similar elevated locations with stable support and useful line-of-sight.
+If you want help validating a parts list, firmware choice, or deployment location, ask in Discord before you seal everything up and mount it.
+ + +If you are running a solar-powered repeater or otherwise want to reduce current draw, power saving is available as an optional post-setup change.
+After logging into the repeater, open the command line and run powersaving on.
This can be useful for deployments where power budget matters, especially small solar installations.
+If you want a lower-power firmware variant, you can also use the flasher's custom firmware option with releases from EasySkyMesh.
+ + Back to CT Mesh + +Start with our local guides, then review official project docs and community channels to choose the right platform for your goals.