Skip to content

Releases

mups18-3 (v1.18.0.mups3)

Choose a tag to compare

@m0urs m0urs released this 15 Nov 16:43

Use at your own risk. This firmware may contain bugs, and I accept no liability for its use.
Before flashing, make a backup if at all possible. Back up the device's private key first and keep it safe –
without it a device gets a new identity after a full erase or a change of firmware.

mups18-3 – MeshCore v1.18.0.mups3

Custom MeshCore firmware based on IoTThinks PowerSaving-v18 (MeshCore main v1.18.0, PowerSaving-v18 as of 2026-11-14).
Full documentation: MUPS18.md

Third release of the mups18 line, mainly a bug-fix release: please update from mups18-2. Same pull requests as mups18-2; the changes are listed below.
Behaviour that only shows over several days of operation (long-term power saving, resend statistics) is still being observed. Please report problems.

What is new compared to mups18-2

  • Fix: the trailing-blank handling of mups18-2 is removed again (repeater, room server, sensor). mups18-2 cut off blanks at the end of every CLI command. Some official commands need exactly that blank, so they failed:

    • "Remove All Neighbours" in the app (it sends neighbor.remove with a blank as an empty prefix) was rejected – the app showed "Firmware Update Required".
    • set owner.info with an empty value (clears the owner info) did not work.

    The CLI now behaves exactly like the official firmware again. This also means that get txdelay with a trailing blank is rejected again, as in the official firmware.

  • TRACE packets (path trace), contributed by Sebastian van de Meer (#25, #26): a repeater in the middle of a trace path no longer re-sends each trace up to max.resend times after the next hop has already forwarded it. The last hop before the trace destination now sends once through the normal channel check and is no longer counted as a resend in get max.resend. Normal messages are not affected. Both issues come from PR meshcore-dev#2670 and were reported there.

  • Base: PowerSaving-v18 as of 2026-11-14, among others: companion GPS follows the companion's powersaving setting (GPS on and off in cycles), new companion CLI commands gps, gps on, gps off, gps sync, GPS fix for the GAT562 30S, support for the INA228 current sensor.

  • File list: all devices of mups18-2, including the ones that were added to mups18-2 afterwards.

Defaults

No changed defaults compared to mups18-2. The packet filter is still off by default and in dry-run mode: after filter on the repeater only counts what it would drop and still forwards everything; check filter stats, then use filter dryrun off to really filter.

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powersaving (companion), powerlog, sensor, reboot.interval IoTThinks PowerSaving-v18 base
Release fixes MeshCore main pinned to v1.18.0
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeater reply path (outpath) PR #2586 repeater
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving); with the TRACE fixes from #25 / #26
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev (7df3767c) repeater only, off by default; own defaults (dry-run on); own fixes: channel block by key (MAC), limiter setup
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Companion: hardware CAD before TX (cad) on by default, as on the repeater (set cad on|off).

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 238 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 15 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 0 (off)
cad on

WiFi companions: the firmware contains no WiFi credentials of mine. The Heltec V3 WiFi image has the placeholders myssid / mypwd compiled in. Set your own with the companion CLI or the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

set wifi.ssid <your SSID>
set wifi.pwd <your password>

then reboot. get wifi.status shows the state, set wifi.clear removes the stored credentials. The Heltec V3 BLE companion, the Heltec V4 (OLED) BLE companion and the Heltec V4.3 (OLED) BLE companion also contain the WiFi interface, but keep WiFi off until an SSID is set. The Heltec V4.3 TFT BLE companion is built without the WiFi interface.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 15, … on the repeater; rescue CLI or companion CLI on the companion).

Devices and files

Repeater: Heltec V3, Heltec V4 (OLED), Heltec V4.3 (R8, OLED and TFT), Heltec T096, Heltec T114 (without display), RAK4631, SenseCAP Solar, Xiao S3 WIO, Xiao nRF52, T1000-E, Wio Tracker L1 (standard variant, not 1W), ThinkNode M6, GAT562 30S Mesh Kit.
Room server: Heltec V3.
Companion (BLE): Heltec V3, Heltec V4 (OLED), Heltec V4.3 (R8, OLED and TFT), RAK WisMesh Tag, GAT562 30S Mesh Kit, T1000-E, Wio Tracker L1, LilyGo T-Echo, Xiao S3 WIO. Companion (WiFi): Heltec V3.

Device type File Use
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, RAK WisMesh Tag, GAT562 30S Mesh Kit, SenseCAP Solar, Heltec T096, Heltec T114, Xiao nRF52, ThinkNode M6, T1000-E, Wio Tracker L1, LilyGo T-Echo) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.18.0.mups3 (ver).

Default TX power (Heltec V4, Heltec V4.3 and Heltec T096; repeater and companion builds): the default is taken unchanged from the base (IoTThinks PowerSaving-v18) and is 17 dBm on these boards. The base's source comments say that 17 gives roughly 28 dBm at the antenna on these boards (the amplifier stage adds gain). I have not measured the real output. Please check what is permitted in your region and with your antenna, and set your own value with set tx <dBm> if needed. Like all defaults, this only applies to new installs / after erasing the settings.

The Heltec V4 repeater and companion (BLE) builds are the OLED variant (same environments as the official heltec_v4_repeater and heltec_v4_companion_radio_ble); the Heltec T114 repeater build is the variant without display. For the Heltec V4.3 there is one OLED and one TFT build each (heltec_v4_r8_… and heltec_v4_r8_tft_…); the name "V4.3 = R8" is taken from the base's commit message, so please check that your board is an R8 before flashing.

The LilyGo T-Echo build covers only the LilyGo T-Echo companion (BLE), not the T-Echo Lite or T-Echo Card.

mups18-2 (v1.18.0.mups2)

Choose a tag to compare

@m0urs m0urs released this 06 Nov 15:55

Use at your own risk. This firmware may contain bugs, and I accept no liability for its use.
Before flashing, make a backup if at all possible. Back up the device's private key first and keep it safe –
without it a device gets a new identity after a full erase or a change of firmware.

mups18-2 – MeshCore v1.18.0.mups2

Custom MeshCore firmware based on IoTThinks PowerSaving-v18 (MeshCore main v1.18.0, PowerSaving-v18 as of 2026-11-04).
Full documentation: MUPS18.md

Second release of the mups18 line. Same base and the same pull requests as mups18-1; the changes are listed below.
Behaviour that only shows over several days of operation (long-term power saving, resend statistics) is still being observed. Please report problems.

What is new compared to mups18-1

  • New repeater commands for diagnosing reception (also usable remotely from the app's command line):
    • get rx.errors – receive errors by cause (ok, crc split into payload / header / unknown, other, error share). get rx.errors snr, rssi, len show histograms of correctly received frames against CRC-error frames; get rx.errors last lists the latest CRC-error frames (age, RSSI, SNR, length, first bytes).
    • get cad now also shows blocked (a send attempt found the channel busy and had to wait) and forced (transmitted anyway after the maximum busy time) counters. clear stats resets them.
  • Fix in the channel check before sending (all roles): the busy-wait timer is reset when no packet is due any more. Before, an old busy episode (PR meshcore-dev#2670 removes a queued resend when the downstream forward is overheard) could make the next packet that found the channel busy go out immediately.
  • CLI: trailing blanks are ignored (repeater, room server, sensor). get txdelay now works like get txdelay. password … and set guest.password … are left exactly as typed. Companions are unchanged.
  • Packet filter: filter age also applies to the future. Taken over from Dutch-MeshCore (47d3d2de, filter state 7df3767c). A group text whose timestamp is more than the age limit away from the repeater's clock is now dropped in either direction. Before, only old messages were dropped. Example with filter age 30: a message from a phone whose clock runs 40 minutes ahead is now dropped. This only matters once the filter is on and filter dryrun is off.
  • Base: PowerSaving-v18 as of 2026-11-04 (includes: the version text of repeater, room server and sensor no longer contains the build date).
  • New in the file list: Xiao S3 WIO (repeater and companion BLE).
  • Added to this release afterwards (same commit and same version): Repeater: Heltec V4 (OLED variant, heltec_v4_repeater), Heltec T096, Heltec T114 (without display, Heltec_t114_without_display_repeater), Xiao nRF52, T1000-E, Wio Tracker L1 (standard variant, WioTrackerL1_repeater, not the 1W variant) and ThinkNode M6 (ThinkNode_M6_repeater). Companion (BLE): Heltec V4 (OLED variant, heltec_v4_companion_radio_ble), RAK WisMesh Tag (RAK_WisMesh_Tag_companion_radio_ble). Heltec V4.3 (R8), OLED and TFT variants, repeater and companion (BLE): heltec_v4_r8_repeater, heltec_v4_r8_tft_repeater, heltec_v4_r8_companion_radio_ble, heltec_v4_r8_tft_companion_radio_ble. GAT562 30S Mesh Kit, repeater and companion (BLE): GAT562_30S_Mesh_Kit_repeater, GAT562_30S_Mesh_Kit_companion_radio_ble. Note on the default TX power of the V4, V4.3 and T096: see "Default TX power" below.

Changed defaults (new installs / after erasing the settings only)

Setting mups18-1 mups18-2
advert.interval (repeater) 240 min 238 min
agc.reset.interval (repeater) 12 s 0 (= off, the official default)
Packet filter hop limit for REQ (00), RESPONSE (01), ANON_REQ (07) 6 5

Existing devices keep their stored settings. To change a repeater by hand: set advert.interval 238, set agc.reset.interval 0.
The packet filter is still off by default and in dry-run mode: after filter on the repeater only counts what it would drop and still forwards everything; check filter stats, then use filter dryrun off to really filter.

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powersaving (companion), powerlog, sensor, reboot.interval IoTThinks PowerSaving-v18 base
Release fixes MeshCore main pinned to v1.18.0
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeater reply path (outpath) PR #2586 repeater
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving)
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev (7df3767c) repeater only, off by default; own defaults (dry-run on); own fixes: channel block by key (MAC), limiter setup
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Companion: hardware CAD before TX (cad) on by default, as on the repeater (set cad on|off).

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 238 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 15 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 0 (off)
cad on

WiFi companions: the firmware contains no WiFi credentials of mine. The Heltec V3 WiFi image has the placeholders myssid / mypwd compiled in. Set your own with the companion CLI or the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

set wifi.ssid <your SSID>
set wifi.pwd <your password>

then reboot. get wifi.status shows the state, set wifi.clear removes the stored credentials. The Heltec V3 BLE companion, the Heltec V4 (OLED) BLE companion and the Heltec V4.3 (OLED) BLE companion also contain the WiFi interface, but keep WiFi off until an SSID is set. The Heltec V4.3 TFT BLE companion is built without the WiFi interface.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 15, … on the repeater; rescue CLI or companion CLI on the companion).

Files

Device type File Use
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3, Heltec V4, Heltec V4.3, Xiao S3 WIO) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, RAK WisMesh Tag, GAT562 30S Mesh Kit, SenseCAP Solar, Heltec T096, Heltec T114, Xiao nRF52, ThinkNode M6, T1000-E, Wio Tracker L1, LilyGo T-Echo) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.18.0.mups2 (ver).

Default TX power (Heltec V4, Heltec V4.3 and Heltec T096; repeater and companion builds): the default is taken unchanged from the base (IoTThinks PowerSaving-v18) and is 17 dBm on these boards; the other builds listed as added afterwards default to 22 dBm. The base's source comments say that 17 gives roughly 28 dBm at the antenna on these boards (the amplifier stage adds gain). I have not measured the real output. Please check what is permitted in your region and with your antenna, and set your own value with set tx <dBm> if needed. Like all defaults, this only applies to new installs / after erasing the settings.

The Heltec V4 repeater and companion (BLE) builds are the OLED variant (same environments as the official heltec_v4_repeater and heltec_v4_companion_radio_ble); the Heltec T114 repeater build is the variant without display. For the Heltec V4.3 there is one OLED and one TFT build each (heltec_v4_r8_… and heltec_v4_r8_tft_…); the name "V4.3 = R8" is taken from the base's commit message, so please check that your board is an R8 before flashing.

The LilyGo T-Echo build covers only the LilyGo T-Echo companion (BLE), not the T-Echo Lite or T-Echo Card.

mups18-1 (v1.18.0.mups1)

Choose a tag to compare

@m0urs m0urs released this 28 Oct 14:59

Use at your own risk. This firmware may contain bugs, and I accept no liability for its use.
Before flashing, make a backup if at all possible. Back up the device's private key first and keep it safe –
without it a device gets a new identity after a full erase or a change of firmware.

mups18-1 – MeshCore v1.18.0.mups1

Custom MeshCore firmware based on IoTThinks PowerSaving-v18 (MeshCore main v1.18.0).
Full documentation: MUPS18.md

This is the first release of the mups18 line. It replaces the mups17 line (last release: mups17-3, MeshCore v1.17.1).
Tested on repeaters and companions; behaviour that only shows over several days of operation (long-term power saving, resend statistics) is still being observed. Please report problems.

What is new compared to mups17-3

  • Base: PowerSaving-v18 / MeshCore v1.18.0. Power saving now also works on companions: powersaving on|off (default on), RX duty cycle balanced by default, full radio.rxps commands on all roles.
  • Official v1.18.0 commands replace own mups17 code. af, dutycycle, cad, max.resend and set pin now work in the rescue CLI and in the companion CLI. WiFi settings are the official set wifi.ssid / set wifi.pwd / set wifi.enabled / set wifi.clear and get wifi.status / get wifi.ip.
  • outpath (repeater) now comes from PR #2586 (PowerSaving-v18 no longer contains it).
  • PR meshcore-dev#2670 (repeated sending of direct packets) ported to the v1.18.0 code, merged with the v1.18.0 change meshcore-dev#3573. New: the channel check before a resend no longer reads RSSI while the receiver is in its power-saving sleep phase (repeater and room server). get/set max.resend also works on the companion.
  • Repeater: first sleep phase of RX power saving after 5 minutes.
  • ESP32 BLE companions: BLE sleep and CPU 10–80 MHz without light sleep.

Update from mups17 – please note

  • WiFi credentials are not carried over. The mups17 commands wifi_ssid, wifi_pwd, wifi_commit, wifi_show, wifi_clear and the file /wifi_config no longer exist. Set the credentials again: set wifi.ssid <SSID>, set wifi.pwd <password>, reboot.
  • The own mups17 rescue-CLI fix for CRLF/LF line endings and get pin are not part of mups18 (set pin exists).
  • Updating a companion from mups17 has not been tested separately: after the update check get af, powersaving and get radio.rxps.

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powersaving (companion), powerlog, sensor, reboot.interval IoTThinks PowerSaving-v18 base
Release fixes MeshCore main pinned to v1.18.0
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeater reply path (outpath) PR #2586 repeater
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving)
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev (ecfb2d41) repeater only, off by default; own defaults (dry-run on); own fixes: channel block by key (MAC), limiter setup
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Companion: hardware CAD before TX (cad) on by default, as on the repeater (set cad on|off).

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 240 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 15 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 12 s
cad on

Packet filter (repeater): off by default and in dry-run mode. After filter on the repeater only counts what it would drop and still forwards everything; check filter stats, then use filter dryrun off to really filter.

WiFi companions: the firmware contains no WiFi credentials of mine. The Heltec V3 WiFi image has the placeholders myssid / mypwd compiled in. Set your own with the companion CLI or the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

set wifi.ssid <your SSID>
set wifi.pwd <your password>

then reboot. get wifi.status shows the state, set wifi.clear removes the stored credentials. The Heltec V3 BLE companion also contains the WiFi interface, but keeps WiFi off until an SSID is set.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 15, … on the repeater; rescue CLI or companion CLI on the companion).

Files

Device type File Use
ESP32 (Heltec V3) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, SenseCAP Solar, T1000-E, Wio Tracker L1, LilyGo T-Echo) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.18.0.mups1 (ver).

LilyGo T-Echo companion (BLE) was added to this release after the first upload (same source, tag mups18-1). It has been tested successfully on a device. Only the LilyGo T-Echo is covered, not the T-Echo Lite or T-Echo Card.

mups17-3 (v1.17.1.mups3)

Choose a tag to compare

@m0urs m0urs released this 20 Oct 14:15

mups17-3 – MeshCore v1.17.1.mups3

Custom MeshCore firmware based on IoTThinks PowerSaving-v17 (MeshCore main v1.17.1).
Full documentation: MUPS17.md · Maintenance handbook (German): MUPS17-HOWTO.md

Changes since mups17-2

  • Base updated to the latest PowerSaving-v17 state (PowerSaving 17.1.6 and the later IoTThinks commits up to its "last build file for PowerSaving 17.1"), including RadioLib 7.8.1 (^7.8.1; previously pinned to a specific RadioLib git commit) and FEM support for Heltec V4.3 R8.
  • DMC packet filter – own defaults for new installs and filter reset: dry-run on, malformed scan on, advert window 24 h, age limit 30 min, no rate limits, hop limit 6 for REQ/RESPONSE/ANON_REQ (login), no hop limit for all other types. The filter itself stays off by default.
  • DMC packet filter – fix: rate limiters and the advert window were only set up when /filter_prefs already existed, and filter reset kept the old limits until reboot. Both now take effect immediately.
  • get cad – fix: the "channel busy" counter was never incremented; it now counts CAD scans before TX that do not report a free channel (reset with clear stats).
  • Repeater defaults changed: flood.max 15 (was 10), cad on (was off). New installs only – existing repeaters: set flood.max 15, set cad on.
  • MeshCore main stays at v1.17.1 (plus documentation updates). v1.18.0 will come with the next firmware line (mups18).

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powerlog, sensor, outpath, reboot.interval IoTThinks PowerSaving-v17 base
Release fixes MeshCore main merged
Fix 1970 date after crash/watchdog/brownout (ESP32) PR #1896 already in PowerSaving-v17
Time keeping across resets (nRF52) PR #2704 already in PowerSaving-v17
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving)
WiFi companion: credentials from flash (/wifi_config) PR #2706 adapted: credential loading only
WiFi companion: set SSID/password via rescue CLI PR #2720 adapted
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev repeater only, off by default; own defaults (dry-run on); own fixes: channel block by key (MAC), limiter setup
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 240 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 15 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 12 s
cad on

Companion rescue CLI: get/set af, get/set dutycycle, get/set max.resend, get pin; replies now display correctly in the flasher.meshcore.io web console.

WiFi companion (Heltec V3 WiFi): the firmware contains no WiFi credentials. Set them once in the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

wifi_ssid <your SSID>
wifi_pwd <your password>
wifi_commit

wifi_show shows the state, wifi_clear removes the stored credentials.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 15, … on the repeater; rescue CLI on the companion).

Files

Device type File Use
ESP32 (Heltec V3) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, SenseCAP Solar, T1000-E, Wio Tracker L1) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.17.1.mups3 (ver).

mups17-2 (v1.17.1.mups2)

Choose a tag to compare

@m0urs m0urs released this 09 Oct 14:08

mups17-2 – MeshCore v1.17.1.mups2

Custom MeshCore firmware based on IoTThinks PowerSaving-v17 (MeshCore main v1.17.1).
Full documentation: MUPS17.md · Maintenance handbook (German): MUPS17-HOWTO.md

Changes since mups17-1

  • Repeated sending (max.resend) is now a core feature, on by default with 3 attempts on all roles (was 2). Devices that already stored a value keep it: set max.resend 3 (companion: rescue CLI).
  • DMC packet filter – channel block by key: filter channel add #name now verifies the packet's MAC under the channel key instead of matching only the one-byte channel hash, so other channels sharing that byte are no longer blocked. The repeater still cannot read messages. The malformed scan no longer drops other channels that share the Public hash byte 0x11.
  • New: airtime reserve for scoped floods (repeater, off by default): set fwd.scoped.reserve <0-100> keeps a share of the repeater's TX time per 60 s free for floods with a region; unscoped floods are dropped first when the repeater is busy. get fwd.scoped.reserve, get fwd.scoped.stats. Idea from ACETyr/MeshCore.
  • Upstream updates from PowerSaving-v17 and MeshCore main since mups17-1.
  • Documentation: core vs. optional features, assessed but not included PRs (meshcore-dev#2997, meshcore-dev#1923), maintenance handbook.

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powerlog, sensor, outpath, reboot.interval IoTThinks PowerSaving-v17 base
Release fixes MeshCore main merged
Fix 1970 date after crash/watchdog/brownout (ESP32) PR #1896 already in PowerSaving-v17
Time keeping across resets (nRF52) PR #2704 already in PowerSaving-v17
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeated sending of direct packets (max.resend, on by default, 3) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving)
WiFi companion: credentials from flash (/wifi_config) PR #2706 adapted: credential loading only
WiFi companion: set SSID/password via rescue CLI PR #2720 adapted
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev repeater only, off by default; start with filter dryrun on; own fix: channel block by key (MAC)
Airtime reserve for scoped floods (fwd.scoped.reserve) own, idea from ACETyr/MeshCore repeater only, off by default

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 240 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 10 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 12 s

Companion rescue CLI: get/set af, get/set dutycycle, get/set max.resend, get pin; replies now display correctly in the flasher.meshcore.io web console.

WiFi companion (Heltec V3 WiFi): the firmware contains no WiFi credentials. Set them once in the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

wifi_ssid <your SSID>
wifi_pwd <your password>
wifi_commit

wifi_show shows the state, wifi_clear removes the stored credentials.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 10, … on the repeater; rescue CLI on the companion).

Files

Device type File Use
ESP32 (Heltec V3) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, SenseCAP Solar, T1000-E, Wio Tracker L1) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.17.1.mups2 (ver).

mups17-1 (v1.17.1.mups1)

Choose a tag to compare

@m0urs m0urs released this 08 Oct 21:06

mups17-1 – MeshCore v1.17.1.mups1

Attention: This is a complete new implementation and superseeds the old UFOx versions of my firmware!

Custom MeshCore firmware based on IoTThinks PowerSaving-v17 (MeshCore main v1.17.1).
Full documentation: MUPS17.md

Included

Component Source Notes
RX duty-cycle power saving (radio.rxps), powerlog, sensor, outpath, reboot.interval IoTThinks PowerSaving-v17 base
Release fixes MeshCore main merged
Fix 1970 date after crash/watchdog/brownout (ESP32) PR #1896 already in PowerSaving-v17
Time keeping across resets (nRF52) PR #2704 already in PowerSaving-v17
Allow setting the clock backwards, elapsed-time underflow fix PR #1349
Separate replay counters for login and messages PR #2834 repeater, room server, sensor
Flood ACK on DM retries PR #3260
Beeps for buzzer on/off, T1000-E button debounce 20 ms PR #3536 companion
Repeated sending of direct packets (max.resend) PR #2670 partial port: without noise-floor median estimator and RX-desync watchdog (both conflict with power saving)
WiFi companion: credentials from flash (/wifi_config) PR #2706 adapted: credential loading only
WiFi companion: set SSID/password via rescue CLI PR #2720 adapted
Repeater packet filter (filter …) Dutch-MeshCore dmc-dev repeater only, off by default; start with filter dryrun on

Own changes

Radio preset (all roles): 869.618 MHz, BW 62.5, SF 8, CR 8

Duty cycle (all roles): 10 % (af 9.0)

Repeater defaults:

Setting Value
rxdelay / txdelay / direct.txdelay 2 / 1.0 / 0.4
advert.interval / flood.advert.interval 240 min / 167 h
flood.max / flood.max.unscoped / flood.max.advert 10 / 3 / 3
multi.acks / path.hash.mode 1 / 2
loop.detect moderate
agc.reset.interval 12 s

Companion rescue CLI: get/set af, get/set dutycycle, get/set max.resend, get pin; replies now display correctly in the flasher.meshcore.io web console.

WiFi companion (Heltec V3 WiFi): the firmware contains no WiFi credentials. Set them once in the rescue CLI (long press of the PRG button within 8 s after boot, serial console 115200 baud):

wifi_ssid <your SSID>
wifi_pwd <your password>
wifi_commit

wifi_show shows the state, wifi_clear removes the stored credentials.

Defaults apply to new installs / after erasing the settings only – existing devices keep their stored settings (set dutycycle 10, set flood.max 10, … on the repeater; rescue CLI on the companion).

Files

Device type File Use
ESP32 (Heltec V3) *.bin Update (app image only) – web flasher (non-merged) or OTA; settings are kept
ESP32 (Heltec V3) *-merged.bin New install / recovery (bootloader + partitions + app, written at 0x0). The web flasher erases the whole flash when a merged image is selected
nRF52 (RAK4631, SenseCAP Solar, T1000-E, Wio Tracker L1) *.zip Update via DFU – web flasher (serial) or nRF Connect app (BLE); settings are kept
nRF52 (same) *.uf2 Update via drag & drop – enter bootloader (usually double reset), copy file to the USB drive; settings are kept

.zip and .uf2 contain the same firmware – two ways to flash it. Neither erases settings.
For a clean install on nRF52, erase first (web flasher erase function, or rescue CLI erase on a companion), then flash.

Firmware version on the device: v1.17.1.mups1 (ver).

v1.17.1.mu-ufo1

Choose a tag to compare

@m0urs m0urs released this 21 Aug 16:14

Custom MeshCore firmware based on v1.17.1

This firmware is now "repeater-only". You can use the original firmware for companions and room servers.

All additional CLI commands are listed here: https://github.com/m0urs/MeshCore/blob/ufo8/docs/mu.md

List of changes to original firmware

v1.17.0.mu-ufo1

Choose a tag to compare

@m0urs m0urs released this 09 Aug 16:46
3a17f37

Custom MeshCore firmware based on v1.17.0

All additional CLI commands are listed here: https://github.com/m0urs/MeshCore/blob/ufo7/docs/mu.md

Attention:

After upgrade to this version, make sure to verify these parameters and re-apply if needed!

set repeat on
set cad off
set agc.reset.interval 0
set max.resend 2
set flood.suppress.snr.lo 0
set flood.suppress.snr.hi 9
set flood.suppress.delay.factor 2
set trace.tx.power 10
set flood.suppress on
# for a quick neighbor detection:
discover.neighbors

After some time you can check statistics by:

get max.resend
-> > 2, resends 20/40 (50%)

get flood.suppress
-> > on, suppressed 3/6 (50%)```

List of changes to original firmware

v1.16.0.mu-ufo2

Choose a tag to compare

@m0urs m0urs released this 29 Jul 12:01

Custom MeshCore firmware based v1.16.0

All additional CLI commands are listed here: https://github.com/m0urs/MeshCore/blob/ufo/docs/mu.md

What's Changed since v1.16.0.mu-ufo1

Attention: With this firmware you should set the following configuration values (as these parameters are handled internally bei UFO):

set cad off
set int.thresh 0
set agc.reset.interval 0

Additional changes to original firmware

  1. feature/repeated-sending-2 for a more reliable deliverability of packages on a direct path by listening on following nodes and ACKs, see details at README-repeated-sending.md

  2. fix/noise-floor-ratchet to adapt the noise floor in both directions, see details at meshcore-dev#2933

  3. feature/flood-suppression to decide about skipping flood repetitions if strong neighborhood already repeated, see details at README-flood-suppression.md

v1.16.0.mu-ufo1

Choose a tag to compare

@m0urs m0urs released this 20 Jul 15:39

Custom MeshCore firmware based on the UFO branch (https://github.com/usrflo/MeshCore/tree/ufo) with some more PR included.

All additional CLI commands are listed here: https://github.com/m0urs/MeshCore/blob/ufo/docs/mu.md

Attention: With this firmware you should set the following configuration values (as these parameters are handled internally bei UFO):

set cad off
set int.thresh 0
set agc.reset.interval 0

Here is a list of PRs which are included in this version:

  1. feature/repeated-sending-2 for a more reliable deliverability of packages on a direct path by listening on following nodes and ACKs, see details at README-repeated-sending.md

  2. fix/noise-floor-ratchet to adapt the noise floor in both directions, see details at meshcore-dev#2933

  3. feature/flood-suppression to decide about skipping flood repetitions if strong neighborhood already repeated, see details at README-flood-suppression.md