DownLink Failed

0

"Number": 108, "ResourceId": "", "Timestamp": "2024-10-08T14:35:16.503351126Z", "MessageId": "", "fPort": "-", "devEui": "-", "Event": "Downlink_Data", "LogLevel": "ERROR", "Resource": "WirelessDevice", "messagePayload": { "ResourceId": "", "Timestamp": "2024-10-08T14:35:16.503351126Z", "CustomerLog": { "wirelessDeviceType": "LoRaWAN", "resourceId": "", "logLevel": "ERROR", "resource": "WirelessDevice", "messageId": "8b9e3f4f-4416-4394-a2be-66c22fe4f328", "event": "Downlink_Data", "message": "Downlink message failed. MessageId: 8b9e3f4f-4416-4394-a2be-66c22fe4f328. Downlink metadata: {"FPort":2}", "wirelessDeviceId": "9", "devEui": "", "timestamp": "2024-10-08T14:35:16.503351126Z" } }

I am seeing a lot of downlink message failed. I correctly configured my device profile to Class A device , which is what it is. I have my region in US915 A shown below:

dev Profile MacVersion 1.0.3 RegParamsRevision Regional Parameters v1.0.3rA RxDelay1 5 RxDataRate2 10 RxFreq2 9230000 FactoryPresetFreqsList 9039000,9041000,9043000,9045000,9047000,9049000,9051000,9053000,9046000 MaxEirp 15 MaxDutyCycle 10 RfRegion US915 SupportsJoin true Supports32BitFCnt true

Service Profile

RaAllowed false PrAllowed false UlRate 60 UlBucketSize 4096 DlRate 60 DlBucketSize 4096 AddGwMetadata true DevStatusReqFreq 24 DrMin 9 DrMax 13 MinGwDiversity 1

Can you please assist me with that?

asked a month ago50 views
1 Answer
0

Based on the information provided, it appears that you're experiencing issues with downlink messages failing and the LNS (LoRaWAN Network Server) selecting SF12 (Spreading Factor 12) for long downlink messages, despite having configured DR (Data Rate) settings in your service profile.

The problem likely stems from a mismatch between your device profile and service profile configurations. In your device profile, you've set RxDataRate2 to 10, which is appropriate for the US915 region. However, in your service profile, you've set DrMin to 9 and DrMax to 13.

For the US915 region, the valid data rates typically range from 0 to 4 (for 125 kHz channels) and 8 to 13 (for 500 kHz channels). Your DrMin and DrMax settings in the service profile are only covering the 500 kHz channels, which may be causing issues with downlink communication.

To resolve this, try adjusting your service profile settings:

  1. Set DrMin to 0 (or the lowest data rate you want to allow)
  2. Keep DrMax at 13 (or the highest data rate you want to allow)

This change will allow the network server to use a wider range of data rates, including slower ones that might be necessary for longer downlink messages or challenging radio conditions.

Also, ensure that your gateway is properly configured to support all the channels and data rates you intend to use. The FactoryPresetFreqsList in your device profile looks correct for US915, but verify that your gateway is set up to listen on these frequencies.

If you continue to experience issues after making these changes, you may need to investigate further by:

  1. Checking the signal quality and RSSI (Received Signal Strength Indicator) of your devices
  2. Verifying that there are no environmental factors interfering with signal propagation
  3. Ensuring that your devices are within range of the gateways

Remember that LoRaWAN is designed to adapt to different conditions, and sometimes slower data rates (like SF12) are necessary to ensure reliable communication over longer distances or in challenging environments.
Sources
LoRaWANGetServiceProfileInfo - AWS IoT Wireless
LoRaWANMulticastSession - AWS IoT Wireless
LoRaWANDeviceProfile - AWS IoT Wireless

profile picture
answered a month ago
  • I modified my question to highlight another problem , i solved the SF12 issue.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions