[Bug]: RX packets ignored with error=-7 in LONG_MODERATE preset (Wio Tracker L1 Pro)

[spawnrider]

Category

Other

Hardware

Other

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.22.96dd647

Description

Bug: RX packets ignored with error=-7 in LONG_MODERATE preset (Wio Tracker L1 Pro)

Description

When using the LONG_MODERATE modem preset on a Wio Tracker L1 Pro, received packets are consistently ignored with error=-7 and classified as noise.

The issue does not occur when switching to LONG_FAST with the same configuration and environment.

This suggests a potential issue with the LONG_MODERATE preset handling (modem parameters, decoding, or compatibility).

---

Hardware

• Device: Seeed Wio Tracker L1 Pro
• Chipset: SX126x (assumed)
• Antenna: stock antenna

---

Firmware

• Meshtastic firmware version: 2.7.22.96dd647
• Other nodes firmware version: (same issue with 2.7.15.567b8ea Beta)

---

Region / Radio Settings

• Region: EU_868
• Frequency: 869.4625 MHz
• Modem preset:
  • ✅ LONG_FAST → works correctly
  • ❌ LONG_MODERATE → issue occurs
• TX Power: tested from 10 to 22 dBm
• RX Boosted Gain: ON
• Channel / PSK: identical on all nodes

---

Steps to Reproduce

1. Configure two nodes (including Wio Tracker L1 Pro) with:
   • same region (EU_868)
   • same frequency (869.4625 MHz)
   • same channel / PSK
2. Set modem preset to LONG_MODERATE on both nodes
3. Send messages between nodes

---

Expected Behavior

• Packets should be received and decoded normally
• ACK / rebroadcast should occur as expected

---

Actual Behavior

• Packets are received but ignored
• Logs show repeated errors:

ERROR [RadioIf] Ignore received packet due to error=-7
DEBUG [RadioIf] Packet RX (noise?)

• rxGood=0 while rxBad increases
• Reliable send fails and results in NAK

---

Additional Observations

• Same setup works immediately when switching to LONG_FAST
• Issue appears specific to LONG_MODERATE preset
• Devices tested at short range (2–5 meters)
• TX power variations do not change behavior
• Behavior suggests packets are received but not decodable

---

Logs

See below / attached log

---

Possible Cause (hypothesis)

• Incorrect modem parameters in LONG_MODERATE (SF/BW/CR mismatch)
• Demodulation or decoding issue specific to this preset
• Potential incompatibility between devices or firmware handling of LONG_MODERATE

---

Impact

• LONG_MODERATE preset unusable on this device in current conditions
• Prevents use of a balanced range/throughput configuration

---

Additional Info

Happy to provide additional logs, configs, or run targeted tests if needed.

Relevant log output

DEBUG | 23:54:28 54 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:28 54 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:29 55 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:29 55 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
ERROR | 23:54:33 59 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x7ff0414d fr=0xe6ecdb54 to=0x8cffffff flags=0x4d rxSNR=-22 rxRSSI=-96 nextHop=0xc0 relay=0x5e)
DEBUG | 23:54:33 59 [RadioIf] Packet RX (noise?) : 3870ms
DEBUG | 23:54:34 60 SX126x AGC reset: warm sleep + Calibrate(0x7F)
DEBUG | 23:54:37 62 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x90921373, tries left=2
INFO  | 23:54:37 62 [Router] Packet History - insert: Reusing slot aged 9.092s TRACE MATCHED PACKET
DEBUG | 23:54:37 62 [Router] Expand short PSK #1
DEBUG | 23:54:37 62 [Router] Use AES128 key!
DEBUG | 23:54:37 63 [Router] enqueue for send (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x
DEBUG | 23:54:37 63 [Router] txGood=1,txRelay=0,rxGood=0,rxBad=1
DEBUG | 23:54:37 63 [Router] Setting next retransmission in 9096 msecs: 
DEBUG | 23:54:37 63 [Router]  (id=0x90921373 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x3 Portnum=1 rxtime=1776203668 hopStart=3)
DEBUG | 23:54:38 63 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:38 63 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:39 64 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:39 64 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
INFO  | 23:54:40 66 [DeviceTelemetry] Send: air_util_tx=0.057556, channel_utilization=9.903334, battery_level=98, voltage=4.163000, uptime=66
DEBUG | 23:54:40 66 [DeviceTelemetry] Partially randomized packet id 3239527930
DEBUG | 23:54:40 66 [DeviceTelemetry] updateTelemetry LOCAL
DEBUG | 23:54:40 66 [DeviceTelemetry] Node status update: 1 online, 2 total
INFO  | 23:54:40 66 [DeviceTelemetry] Send packet to phone
INFO  | 23:54:40 66 [DeviceTelemetry] Sending local stats: uptime=66, channel_utilization=9.903334, air_util_tx=0.057556, num_online_nodes=1, num_total_nodes=2
INFO  | 23:54:40 66 [DeviceTelemetry] num_packets_tx=2, num_packets_rx=1, num_packets_rx_bad=1
DEBUG | 23:54:40 66 [DeviceTelemetry] Partially randomized packet id 325431803
INFO  | 23:54:40 66 Tell client we have new packets 7
INFO  | 23:54:40 66 BLE notify fromNum
DEBUG | 23:54:40 66 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:40 66 phone downloaded packet (id=0xc11745fa fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x0 Portnum=67 rxtime=1776203680 priority=10)
DEBUG | 23:54:40 66 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:40 66 phone downloaded packet (id=0x1365b1fb fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x0 Portnum=67 rxtime=1776203680 priority=10)
DEBUG | 23:54:40 66 [Power] Battery: usbPower=0, isCharging=0, batMv=4163, batPct=98
DEBUG | 23:54:46 72 [Router] Sending retransmission fr=0x0,to=0xffffffff,id=0x90921373, tries left=1
INFO  | 23:54:46 72 [Router] Packet History - insert: Reusing slot aged 9.203s TRACE MATCHED PACKET
DEBUG | 23:54:46 72 [Router] Expand short PSK #1
DEBUG | 23:54:46 72 [Router] Use AES128 key!
DEBUG | 23:54:47 72 [Router] enqueue for send (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x
DEBUG | 23:54:47 72 [Router] txGood=2,txRelay=0,rxGood=0,rxBad=1
DEBUG | 23:54:47 72 [Router] Setting next retransmission in 9096 msecs: 
DEBUG | 23:54:47 72 [Router]  (id=0x90921373 fr=0x00000000 to=0xffffffff, transport = 0, WantAck=1, HopLim=3 Ch=0x3 Portnum=1 rxtime=1776203668 hopStart=3)
DEBUG | 23:54:47 72 [RadioIf] Started Tx (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0x3b pri
DEBUG | 23:54:47 72 [RadioIf] 0 packets remain in the TX queue
DEBUG | 23:54:48 73 [RadioIf] Packet TX: 1036ms
DEBUG | 23:54:48 73 [RadioIf] Completed sending (id=0x90921373 fr=0x10b9183b to=0xffffffff, transport = 0, WantAck=0, HopLim=3 Ch=0x3c encrypted len=29 rxtime=1776203668 hopStart=3 relay=0
DEBUG | 23:54:56 81 [Router] Reliable send failed, returning a nak for fr=0x0,to=0xffffffff,id=0x90921373
DEBUG | 23:54:56 81 [Router] Partially randomized packet id 3942054396
WARN  | 23:54:56 81 [Router] Alloc an err=5,to=0x10b9183b,idFrom=0x90921373,id=0xeaf6f9fc
DEBUG | 23:54:56 81 [Router] Enqueued local (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 priority=1
DEBUG | 23:54:56 81 [Router] cancelSending id=0x90921373, removed=0
DEBUG | 23:54:56 81 [Router] Rx someone rebroadcasting for us (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=177
DEBUG | 23:54:56 81 [Router] Didn't find pending packet
INFO  | 23:54:56 81 [Router] Packet History - insert: Using new slot @uptime 81.330s TRACE NEW
DEBUG | 23:54:56 81 [Router] handleReceived(REMOTE) (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 pr
DEBUG | 23:54:56 81 [Router] Module 'routing' wantsPacket=1
INFO  | 23:54:56 81 [Router] Received routing from=0x10b9183b, id=0xeaf6f9fc, portnum=5, payloadlen=2
DEBUG | 23:54:56 81 [Router] Routing sniffing (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 priority
DEBUG | 23:54:56 81 [Router] Received a NAK for 0x0, stopping retransmissions
DEBUG | 23:54:56 81 [Router] Delivering rx packet (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 prio
DEBUG | 23:54:56 81 [Router] Ignore update from self
DEBUG | 23:54:56 81 [Router] Forwarding to phone (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 prior
DEBUG | 23:54:56 81 [Router] Module 'routing' considered
INFO  | 23:54:56 81 Tell client we have new packets 8
INFO  | 23:54:56 81 BLE notify fromNum
DEBUG | 23:54:56 81 FromRadio=STATE_SEND_PACKETS
DEBUG | 23:54:56 81 phone downloaded packet (id=0xeaf6f9fc fr=0x10b9183b to=0x10b9183b, transport = 0, WantAck=0, HopLim=0 Ch=0x3 Portnum=5 requestId=90921373 rxtime=1776203696 p
ERROR | 23:55:02 87 [RadioIf] Ignore received packet due to error=-7 (maybe id=0x7ff09d70 fr=0x97ecdb54 to=0x88ffffff flags=0x4d rxSNR=-24.75 rxRSSI=-93 nextHop=0x79 relay=0xb1)
DEBUG | 23:55:02 87 [RadioIf] Packet RX (noise?) : 1904ms

[Nevermore-42]

I had the impression that "error =-7" is an generic error message when something goes wrong on the RX side.
Since (if I am not mistaken) LONG_MODERATE takes twice (or maybe even more) as much time on air to TX the same message vs LONG_FAST, couldn't this be just noise that there is in the band that gets amplified to unusable levels?

[GUVWAF]

Yes, this error means a packet was detected, but the CRC did not match, hence there was an error while decoding the packet. Your airtime is very long: Packet RX (noise?) : 3870ms, and yes, then this may happen more frequently especially if there is interference.

You mention "Configure two nodes (including Wio Tracker L1 Pro)"; are both nodes the Wio Tracker L1 Pro?

[spawnrider]

Yes, this error means a packet was detected, but the CRC did not match, hence there was an error while decoding the packet. Your airtime is very long: Packet RX (noise?) : 3870ms, and yes, then this may happen more frequently especially if there is interference.

You mention "Configure two nodes (including Wio Tracker L1 Pro)"; are both nodes the Wio Tracker L1 Pro?

No, the second one is a Lilygo T beam. The two nodes were spaced a maximum of 1m apart?

[GUVWAF]

Okay, that's good info to have. Which T-Beam version is it? Most of those do not have a TCXO, which can cause them to drift, especially with longer packets: https://youtu.be/PND1GlMSrEM

[spawnrider]

I think this is one the first version (T22_V1.0) :