By using AWS re:Post, you agree to the Terms of Use
/LoRaWAN FUOTA - Defining multicast group stuck in "Package attempting"/

LoRaWAN FUOTA - Defining multicast group stuck in "Package attempting"

0

Hi, I'm using STM32WL55 Nucleo with MW_RADIO_VERSION: V1.2.0.

I'm trying to follow the instruction in the YouTube "Get started with AWS IoT Core for LoRaWAN FUOTA"

I can see my device and my GW registered up-to-date on the AWS Core IOT console

After adding my device to a multicast group I don't see that the device is getting any data even though it is transmitting once every 30sec.

The console show under the device status in the multicast section that the device is "Package attempting"

Any idea what I'm doing wrong?

Thanks

Eyal

1 Answers
0

Hi Eyal. Please check the Basics Station logs and see if a dnmsg is sent by AWS IoT Core for LoRaWAN when you create the multicast group. And that it's sent in response to the uplink (not before).

If I were to hazard a guess, maybe you enabled Class C in the device profile? And hence the dnmsg might be getting sent right away instead of in the RX slots after the uplink. This is the device profile I used in the video (with the same version of ST Nucleo firmware except I added some additional logging so I could see the LoRaWAN MAC commands):

aws iotwireless get-device-profile --id 33f77a0b-d83c-43ac-9983-22e0526deed7
{
    "Arn": "arn:aws:iotwireless:us-east-1:012345678901:DeviceProfile/33f77a0b-d83c-43ac-9983-22e0526deed7",
    "Name": "ST Nucleo-WL55JC1",
    "Id": "33f77a0b-d83c-43ac-9983-22e0526deed7",
    "LoRaWAN": {
        "SupportsClassB": false,
        "SupportsClassC": false,
        "MacVersion": "1.0.3",
        "RegParamsRevision": "RP002-1.0.1",
        "RxDelay1": 1,
        "RxDrOffset1": 0,
        "RxDataRate2": 8,
        "RxFreq2": 9233000,
        "FactoryPresetFreqsList": [
            null
        ],
        "MaxEirp": 13,
        "MaxDutyCycle": 0,
        "RfRegion": "AU915",
        "SupportsJoin": true,
        "Supports32BitFCnt": true
    }
}

Forgetting about FUOTA for a moment, you could also check whether any downlink messages work for you. Even just a regular unicast downlink.

If my guess is wrong, please make use of Network Analyzer and IoT Wireless logging in CloudWatch to get greater visibility into the issue.

answered a month ago
  • Hello Greg

    Sorry for my basic questions but I have some misunderstanding regarding your reply.

    When you say "Basics Station logs" you mean the logs from my GW? Or some logs that I can see on the console?

    I'm able to see the logs on the GW, and when the unit is starting to work there are some two way messages so I assume I'm able toget downlink messages. I can see incoming messages when the device start but I did not see dnmsg.

    I'm able also to see logs on the network analyzer, but again, did not see dnmsg

    Also, when I try to see the device profile in the CLI I get this error:

    AWSCLIV2>aws iotwireless get-device-profile --id "661ee449-96b6-4e9e-9e74-515fa3bf359f"
    
    An error occurred (ResourceNotFoundException) when calling the GetDeviceProfile operation: Cannot complete the step because resource is not found, with resource type DeviceProfile,
     resource Id 661ee449-96b6-4e9e-9e74-515fa3bf359f
    

    My default class is A:

    #define LORAWAN_DEFAULT_CLASS CLASS_A

  • Hi Eyal. Yes Basics Station is the GW software. A dnmsg is a Basics Station station downlink message. You will see them in the Basics Station log if your logging level is XDEBUG.

  • A dnmsg in the logs looks like this:

    2022-05-29 23:55:20.648 [AIO:XDEB] [4|WS] < {"msgtype":"dnmsg","DevEui":"00-00-00-00-00-00-00-00","regionid":4,"dnmode":"updn","dC":0,"diid":8693,"pdu":"601cb733019503001100000000c8afc671d222","priority":1,"RxDelay":1,"RX1DR":13,"RX1Freq":926300000,"xtime":16044073883980668,"rctx":0}
    

    You don't need this to solve the problem. It's just that the Basics Station logs can be helpful.

  • The McGroupSetupReq message is sent on FPort 200. So in Network Analyzer you should be seeing downlink messages on FPort 200 (and perhaps also clock synchronization messages on FPort 202). This will not appear until you create the multicast group. Otherwise you will mainly see FPort 2 (the FPort used by the Nucleo data uplinks).

  • For the error on get-device-profile I think you are using the wrong ID. Please use aws iotwireless list-device-profiles to see your device profile IDs.

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