Repository navigation
mups18-1 (v1.18.0.mups1)
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 cyclebalancedby default, fullradio.rxpscommands on all roles. - Official v1.18.0 commands replace own mups17 code.
af,dutycycle,cad,max.resendandset pinnow work in the rescue CLI and in the companion CLI. WiFi settings are the officialset wifi.ssid/set wifi.pwd/set wifi.enabled/set wifi.clearandget 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.resendalso 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_clearand the file/wifi_configno 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 pinare not part of mups18 (set pinexists). - Updating a companion from mups17 has not been tested separately: after the update check
get af,powersavingandget 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.