- Newest
- Most votes
- Most comments
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.
Hello,
Was there ever a resolution to this? I'm experiencing the same problem with US915 and v1.2.0. I see multiple port 200 DL/UL events occur on the device log but the multicast session never starts. The only changes I've made to the stack are enabling US915 (vs default of EU868) and increasing the log information reported. GW is the Minihub Pro for AWS.
Thank you, Tim
Relevant content
- asked 10 months ago
- asked a year ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years 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:
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:
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-profilesto see your device profile IDs.