- Newest
- Most votes
- Most comments
Hi Patryk. I take it you've followed this video? https://www.youtube.com/watch?v=0Yd6PFwL-IM
I have problem with multicast group FUOTA on Lorawan that send package to only one device even though there are more devices in the group
Is there a particular command you're referring to? REMOTE_MCAST_SETUP_MC_GROUP_CLASS_C_SESSION_REQ? Or FRAGMENTATION_PKG_VERSION_REQ? Or maybe FRAGMENTATION_FRAG_SESSION_SETUP_REQ? Can you please clarify which of these are not reaching some devices? And do your devices send uplinks between you creating the FUOTA task and the multicast session starting? (So that the setup messages can be sent in downlinks.)
All devices work in class C.
Does this mean they are class A that changes into Class C for the FUOTA multicast? Or do you mean Class C all the time?
Sometimes when setting the multicast group, the REMOTE_MCAST_SETUP_MC_GROUP_CLASS_C_SESSION_REQ does not arrive to the end device. I see on the Network Analyzer tool that the message leaves AWS but gets lost. However, the FRAGMENTATION_PKG_VERSION_REQ and FRAGMENTATION_FRAG_SESSION_SETUP_REQ are received in the end device and I see the end device sent the Answer for both messages. I end up with a forever multicast Session attempting. Only solution I have found until now is manually deleting the session and creating another.
Is there another solution, like AWS realizing the REMOTE_MCAST_SETUP_MC_GROUP_CLASS_C_SESSION_REQ message was not answered and keep trying it?
Relevant content
- asked a year ago
- asked a year ago
AWS OFFICIALUpdated 10 months ago- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 7 months ago
Yes i followed this video https://www.youtube.com/watch?v=0Yd6PFwL-IM . I'm not following any specific command. After creating a multicast group, I added devices to it manually and then, as in the video, I created a FUOTA task and set the execution to a specific time. When the FUOTA task starts, only one device receives data as in the example. The devices did not want to go from class A to class C by default, as in the video, so I changed the default class to C for testing.
The
REMOTE_MCAST_SETUP_MC_GROUP_CLASS_C_SESSION_REQcommand is handled inMiddlewares/Third_Party/LoRaWAN/LmHandler/Packages/LmhpRemoteMcastSetup.c. So that's where you can add extra prints.The
REMOTE_MCAST_SETUP_MC_GROUP_CLASS_C_SESSION_REQconfigures the multicast session. If your class A device receives that, it should swap to Class C at the scheduled time. If that didn't happen, I think you should debug that first. You can use the Network Analyzer and/or add additional print messages to the firmware. I think you should first establish whether this message was ever sent to the devices. Note: it can only be sent if your device sends an uplink after the FUOTA task is created and before the multicast session start time.