Transition from Class A to Class C, LNS issue.

Question

My end node device operates in 2 modes depending on what it is doing , class A or class C. In the LNS i set up a device profile that supports class C but i see it downlink the  message as soon as i trigger one which is fine when i have my device in class C but not when it's in class A.  How do i setup my LNS so that i can have the downlink in Class A ( i.e when the device uplinks) and Class C (i.e asynchronously)  without having 2 different device profiles or having the device to reconnect when i change an attribute in the LNS?

Greg · Answer

Hi. It you set `SupportsClassC`, you're telling AWS IoT Core for LoRaWAN that your device is class C. So when you call [SendDataToWirelessDevice](https://docs.aws.amazon.com/iot-wireless/2020-11-22/apireference/API_SendDataToWirelessDevice.html), the downlink will be sent right away. To use Class C only intermittently, you will need to schedule messages to be sent at the right time. This will mean sending to a multicast group instead: [SendDataToMulticastGroup](https://docs.aws.amazon.com/iot-wireless/2020-11-22/apireference/API_SendDataToMulticastGroup.html). Please see this video for an example of a Class A device temporarily switching to Class C to receive a multicast downlink: https://www.youtube.com/watch?v=LcCR-1eKX1w

HemantG · Answer

![Enter image description here](/media/postImages/original/IMw2AHJvLRQlqyk96onOhSnQ)
I see in V1.1.x we have a device mode field , if i were to use the v1.1.x , what would that look like from the LNS perspective ?

Transition from Class A to Class C, LNS issue.

Add your answer

Relevant content