C type node is working fine when in use OTA method.
But, when i use ABP, then the node behaves as A type even if i configure it as C type i.e. the downlink is sent to the node only after receiving the next uplink.
Please note that when your node is configured as Class-C device, LoRa App Server will request LoRa Server to directly emit this frame:
However, when your node is not configured correctly to operate in Class-C, it is possible that the frame stays in the queue and is re-transmitted (in case of confirmed: true) on an uplink (thus falling back on Class-A receive window).
In the snapshot, the “pending” is shown to be “true”, but in the frame logs section, the “immediately” field is shown to be “true”. This is shown in my next reply (as a new user i cant have two images in a single comment)
In the snapshot, the “pending” is shown to be “true”, but in the frame logs section, the “immediately” field is shown to be “true”
So it seem from the network-server side, there is no issue. As you sent your frame using confirmed: true, it is set to pending: true until your node acknowledges the frame The frame has been transmitted to your node as you see in the screenshot above.
No, pending: true means (in this case) that the frame has been sent, but that the server is waiting for an ACK from your node. When subscribing to the gateway/+/tx topic, you’ll probably see that it is sent with immediately: true to one of your gateways. The output will be more or less the same as in your screenshot.
I believe C-type ABP device is not working due to mismatch in RX2 SF. The RX2 SF for IN_865_867 as defined by LoRa Alliance is SF8 but when i send a downlink to my C-type ABP device then it is sent on RX2 SF12.
Let me know how i can modify the RX2 SF for IN_865_867 .