4.1.33

mDot/xDot Firmware Release

Version Info

• LoRaWAN - 1.0.4
• Regional Paramerters - RP2 1.0.3
• Fragmentation - v1.0
• Multicast Setup - v2.0
• library - v4.1.31
• mts-lora - v4.1.22
• Bootloader
  • mDot 1.1.0
  • xDot 1.1.2

Region Support in GLOBAL firmware

• mDot
  • US915, EU868, AU915, AS923-1, AS923-2, AS923-3, AS923-4, AS923-JAPAN1, AS923-JAPAN2, KR920, IN865
• xDot
  • US915, EU868, AU915, AS923-1, AS923-2, AS923-3, AS923-4, AS923-JAPAN1, AS923-JAPAN2

Changes

• Passes LCTT v3.0.0 Tech Package 3.14.0_R1 LoRaWAN 1.0.4 Certification tests for US/EU/AU/AS/KR/IN

• Update Remote Multicast Setup to specification v2.0

  • Passes LCTT Package 3.14.0_R1

• Remote Multicast Setup fixes

  • Supports protocol messages
    • PackageVersionReq/Ans - was missing in previous releases
    • McGroupStatusReq/Ans - was missing in previous releases
    • McGroupSetupReq/Ans
    • McGroupDeleteReq/Ans
    • McClassCSessionReq/Ans
    • McClassBSessionReq/Ans - not supported
  • Will not start session if time-to-start is passed, send missed time to start in ANS
  • Calculates time-to-start just before ANS uplink in case packet was delayed and adjusts 3s for max packet time-on-air
    • Previous library release did not account for delay of packet transmit and received time-to-start calculated using server RX packet time was ahead of expected time-to-start, mPower FUOTA server would then send ForceAppTimeSync and delay the FragSetupReq.

Multicast Sessions

• 8 multicast sessions can be saved/restored, Remote Multicast Setup can be used for first four

Known Issues

• MC Class C Setup Ans does not account for delay of packet transmit and received time-to-start calculated by the server using RX packet time was ahead of expected time-to-start, mPower FUOTA server would then send ForceAppTimeSync and delay the FragSetupReq.