Releases · Lora-net/SWL2001

This version is based on feature branch v4.3.1 of the LoRa Basics Modem.

Changed:

Printing of certification mode enabling status is changed so that the print is more visible when enabled. The enabling status is always reported.

Added

Add in stack lost connection in second since last downlink
CSMA and LBT could be both enabled
Compute CSMA and LBT power consumption statistics for radio planner
Get the Radio Planner power consumption statistics for all hooks in array
Add API to Get/Set the status to bypass the join_duty-cycle backoff
Add API smtc_modem_get_suspend_radio_communications()
Add Relay TX feature as defined in TS011 LoRaWAN® Relay Specification. The relay TX is the relayed end-device.

Fixed

Retrofit Bug fix of answer to FragSessionStatusReq command in fragmentation package v1.0.0
Join BackOff duty-cycle: add a check before join to be sure that the backoff duty-cycle is not exceeded according to current datarate (ie 36s on 1h, 36 s on 10hours and 8.7s on 24h)
Issue #26 Variable user_alarm_in_seconds will never be negative in modem_supervisor_engine
Issue #44 Flash porting test always failing due to array out of bounds access
Issue #48 FMP Unresponsiveness after Receiving multiple FMP_DEV_REBOOT_TIME_REQ msg's
Issue #49 Relay tx and rx not setting antenna switch manually
Issue #51 Makefile ignores MCU_FLAGS

Release v4.3.1

This version fix the 4.3.0 version.

LR-FHSS datarate decay certification test failing
LR-FHSS hop_sequence_id must in range [0:nb_max_hop_sequence-1] to avoid buffer overflow
FUOTA MPA (Multiple Package Access) multicast session not started when RMS commands are received through MPA package
FUOTA MPA (Multiple Package Access) package answering to MultiPackBufferReq plus other packages commands in same downlink when it should not
FUOTA MPA (Multiple Package Access) Coverity Overrun fix
LBM Application with nRF52840 target, the RTC wrapping reset the device
LBM Application with nFR52840 target, fix SPI HAL for radio sx126x and sx128x
Class B resets when counter "smtc_modem_hal_get_time_in_100us" wraps (occurs after 4.9 days), this time base is no more used
cloud DM DM_INFO_RXTIME payload do not report the correct duration since last received downlink

Full Changelog: v4.3.0...v4.3.1

Provide feedback