MeshCore Firmware v1.14.1

Releases
1

Companion Firmware - Change Log:

https://github.com/meshcore-dev/MeshCore/releases/tag/companion-v1.14.1

  • Added GPS support for SenseCAP Solar P1 in #1589

  • Added nRF52 power management for RAK3401 in #1984

  • Added token bucket based duty cycle enforcement in #1297

  • Added support for new GAT562 30S Mesh Kit device in #2009

  • Added support for new GAT562 Mesh Tracker Pro device in #1980

  • Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653

  • Added MCU temperature to telemetry responses from room servers in #2052

  • Migrated Heltec Tracker v2 to KCT8103L in #1936

  • Fixed bug where some queued packets would not get transmit in #1877

  • Fixed bug where BLE would stay on if turned off from companion screen when already connected in #1991

Repeater Firmware - Change Log:

https://github.com/meshcore-dev/MeshCore/releases/tag/repeater-v1.14.1

  • Added GPS support for SenseCAP Solar P1 in #1589

  • Power off switch long press support for SenseCAP Solar P1 #1871

  • Added nRF52 power management for RAK3401 in #1984

  • Added token bucket based duty cycle enforcement in #1297

  • Added support for new GAT562 30S Mesh Kit device in #2009

  • Added support for new GAT562 Mesh Tracker Pro device in #1980

  • Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653

  • Added MCU temperature to telemetry responses from room servers in #2052

  • Migrated Heltec Tracker v2 to KCT8103L in #1936

  • Nodes with GPS enabled will now auto sync time every 30 minutes in #1350

  • Fixed bug where some queued packets would not get transmit in #1877

  • Fixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f

Room Server Firmware - Change Log:

https://github.com/meshcore-dev/MeshCore/releases/tag/room-server-v1.14.1

  • Added GPS support for SenseCAP Solar P1 in #1589

  • Power off switch long press support for SenseCAP Solar P1 #1871

  • Added nRF52 power management for RAK3401 in #1984

  • Added token bucket based duty cycle enforcement in #1297

  • Added support for new GAT562 30S Mesh Kit device in #2009

  • Added support for new GAT562 Mesh Tracker Pro device in #1980

  • Added LNA toggle CLI commands radio.rxgain on and radio.rxgain off in #1653

  • Added MCU temperature to telemetry responses from room servers in #2052

  • Migrated Heltec Tracker v2 to KCT8103L in #1936

  • Nodes with GPS enabled will now auto sync time every 30 minutes in #1350

  • Fixed bug where some queued packets would not get transmit in #1877

  • Fixed bug where automatic adverts were not using the configured multibyte path setting in fcfdc5f

1 Like
2

Hat schon jemand heraus gefunden wie man den Duty Cycle konfiguriert der ja gemäss Release Notes nun richtig implementiert sein soll?

3

Duty Cycle Konfiguration in v.1.14.1:

Für Schweiz mit 10 % Duty-Cycle:

set AF 9

559719168-714d93f0-aa00-4750-97e6-40983e91d143
559719168-714d93f0-aa00-4750-97e6-40983e91d1431080×536 42.8 KB

implementiert mit PR 1297

Bereits vorhandener Vorschlag für Implementation jedoch erst als PR und noch nicht einmal in DEV release:

PR 1961 soll AF weiter unterstützen aber zusätzlich erlauben “set dutycycle xx” zu konfigurieren:

564187254-914f921e-c9e7-4f2b-9911-05d6832d5697
564187254-914f921e-c9e7-4f2b-9911-05d6832d56971080×1198 75.1 KB

Dies wird jedoch nur das CLI verändern, die Funktion bleibt so wie auch bereits in v.1.14.1 implementiert

1 Like
4

Aha, dann fehlen quasi einfach noch die richtigen Befehle aber wenn man jetzt “set af 9” macht wird die neue Art wie das implementiert wurde in #1297 bereits verwendet?

5

ja, so hab ich das verstanden.

momentan “set af 9”, später “set dutycycle 10”.

1 Like