LoraWan Connection issue with ABP

[Ahsan-Averos]

Dear Sir
Please correct me what I am doing wrong, I done it number of serval trial to connect with gateway but unable to do this.
Although my Lora communication is working fine.

Reference code:
[(https://github.com/insightsip/ISP4520-examples)]

Hardware:

nrf52832
E22900M22S(Sx1262)

Please see the response in log file.

> app: LoRaWan end-device started.
app: Initializing fds...
app: Reading flash usage statistics...
app: Found 7 valid records.
app: Found 75 dirty records (ready to be garbage collected).
app: Record 3 at 7D06C
app: Record 4 at 7D1D0
app: Record 6 at 7D41C
app: Record 7 at 7D4F0
app: Record 80 at 7ED9C
app: Record 81 at 7EDDC
app: Record 82 at 7EE00
app: Data restored from NVM: 1208 bytes
app: MLME-Request: MLME_JOIN, OK
app: Uplink counter : 26
app: Uplink Data rate : DR_0
app: Uplink TX power : 0
app: Uplink frequency: 868500000
app: FDS update success! FileId: 0x3E8 RecKey:0x1
app: FDS update success! FileId: 0x3E8 RecKey:0x2
app: FDS update success! FileId: 0x3E8 RecKey:0x5
app: Data stored on NVM: 224 bytes
app: MCPS-Request: MCPS_UNCONFIRMED, OK
app: Uplink counter : 27
app: Uplink Data rate : DR_0
app: Uplink TX power : 0
app: Uplink frequency: 868300000
app: FDS update success! FileId: 0x3E8 RecKey:0x1
app: FDS update success! FileId: 0x3E8 RecKey:0x2
app: FDS update success! FileId: 0x3E8 RecKey:0x5
app: Data stored on NVM: 224 bytes
app: MCPS-Request: MCPS_UNCONFIRMED, OK
app: Uplink counter : 28
app: Uplink Data rate : DR_0
app: Uplink TX power : 0
app: Uplink frequency: 868300000
app: FDS update success! FileId: 0x3E8 RecKey:0x1
app: FDS update success! FileId: 0x3E8 RecKey:0x2
app: FDS update success! FileId: 0x3E8 RecKey:0x5
app: Data stored on NVM: 224 bytes
app: MCPS-Request: MCPS_UNCONFIRMED, OK

And also see what I changed in code

Server data
Device address:

Network + App session keys:

Graph:

I hope that someone helping me out in this.
Thanks in advance.....

[mluis1]

First I would like to clarify something. An end-device does not connect to a gateway. An end-device connects to a network server.
A gateway is just a dumb device that translates what is received on the RF to the IP world and vice versa.

Which Network Server are you using?

Most of the network servers that I'm aware of use big endian encoding for the DevAddr. The LoRaMac-node project also encodes the DevAddr as big endian (see comment above LORAWAN_DEVICE_ADDRESS definition).

On your screen shot you have entered the DevAddr encoded as little endian.

DevAddr should be: 60595857

In the future it would be nice if you could post this kind of questions on the project Discussions tab. It is a better place to engage discussions and then we can agree if it is an issue or not.
If you don't mind I move this issue to the Discussions tab.

[Ahsan-Averos]

Sir for ABP:

Network session key is same in this all byte:

F_NWK_S_INT_KEY
S_NWK_S_INT_KEY
NWK_S_ENC_KEY

and application session key.

APP_S_KEY
is this okay?

[Ahsan-Averos]

1B2E354658AED2A6ABF7158809CF4F3C (Network session key)
5B4E352618AED2A6ABF7158809CF4F3C (Apps session key).

[Ahsan-Averos]

Now receiving this :

[Ahsan-Averos]

after change to DevAddr to Big Endian 60595857

[mluis1]

Personally, I used that network server very long time ago (just a couple of hours trial) and I don't remember how the end-device must be setup on it.

From the screen shots you show the only thing that look to be wrong is the DevAddr value. However, I don't know what is expected by the network server you are using.

Maybe, @altishchenko can help you on this.

As shown in comments above keys definition the F_NWK_S_INT_KEY = S_NWK_S_INT_KEY = NWK_S_ENC_KEY = NWK_S_KEY in case of LoRaWAN 1.0.x specifications.

Key definitions:

        {                                                                                                           \
            /*!                                                                                                     \
             * Forwarding Network session integrity key                                                             \
             * WARNING: NWK_S_KEY FOR 1.0.x DEVICES                                                                 \
             */                                                                                                     \
            .KeyID    = F_NWK_S_INT_KEY,                                                                            \
            .KeyValue = { 0x2B, 0x7E, 0x15, 0x16, 0x28, 0xAE, 0xD2, 0xA6, 0xAB, 0xF7, 0x15, 0x88, 0x09, 0xCF, 0x4F, \
                          0x3C },                                                                                   \
        },                                                                                                          \
        {                                                                                                           \
            /*!                                                                                                     \
             * Serving Network session integrity key                                                                \
             * WARNING: NOT USED FOR 1.0.x DEVICES. MUST BE THE SAME AS \ref LORAWAN_F_NWK_S_INT_KEY                \
             */                                                                                                     \
            .KeyID    = S_NWK_S_INT_KEY,                                                                            \
            .KeyValue = { 0x2B, 0x7E, 0x15, 0x16, 0x28, 0xAE, 0xD2, 0xA6, 0xAB, 0xF7, 0x15, 0x88, 0x09, 0xCF, 0x4F, \
                          0x3C },                                                                                   \
        },                                                                                                          \
        {                                                                                                           \
            /*!                                                                                                     \
             * Network session encryption key                                                                       \
             * WARNING: NOT USED FOR 1.0.x DEVICES. MUST BE THE SAME AS \ref LORAWAN_F_NWK_S_INT_KEY                \
             */                                                                                                     \
            .KeyID    = NWK_S_ENC_KEY,                                                                              \
            .KeyValue = { 0x2B, 0x7E, 0x15, 0x16, 0x28, 0xAE, 0xD2, 0xA6, 0xAB, 0xF7, 0x15, 0x88, 0x09, 0xCF, 0x4F, \
                          0x3C },                                                                                   \
        },                                                                                                          \
        {                                                                                                           \
            /*!                                                                                                     \
             * Application session key                                                                              \
             */                                                                                                     \
            .KeyID    = APP_S_KEY,                                                                                  \
            .KeyValue = { 0x2B, 0x7E, 0x15, 0x16, 0x28, 0xAE, 0xD2, 0xA6, 0xAB, 0xF7, 0x15, 0x88, 0x09, 0xCF, 0x4F, \
                          0x3C },                                                                                   \
        },                                                                                                          \

Something you don't say is if the uplinks are being received by the packet_forwarder on the gateway and if they are forwarded to the network server.
Please try to look at the gateway logs and network server logs to see if the uplinks are being received.

[altishchenko]

Hello, as I can see, this is Petr's lorawan server.

1. Miguel is right about your DevAddr - it should be the same in both places.
2. Also, make sure that 'FCnt Check' in your device's profile is set to 'Reset on zero', you are using ABP and will definitely reset your device multiple times, this setting will help.
3. In your 'Areas' settings set 'Log Ignored' to 'true', this allows you to see the fact of device transmission even if it doesn't match your configured devaddr or keys.
4. Check your server's debug.log.
5. You are getting ack_lost messages, this means that your server to gateway connection is not very good or there is some misconfiguration on the TCP/IP level between the two.

[altishchenko]

Ok. I am back. Let's start from the top, step by step.

Area - something global, Gateways belong to Areas, Areas define the radio regional settings for the gateways, your Area should like this (mind the red selection!):

[altishchenko]

Gateways, simple devices. This is an example of my Kerlink Wirnet station:

[altishchenko]

Networks - define radio regional settings for devices, this is a working example for EU868. Pay attention to commas in the screens below. For the beginning, make sure your settings match mine!

General

ADR

Channels

[altishchenko]

Groups - define sets of devices belonging to a particular network and persons who can manage them:

[altishchenko]

Your profile and node configuration look pretty decent to me, with one correction - I'd leave the TX Window setting in your profile to Auto, this way, if anything goes wrong, the server will be able to retry ACK transmission in the standard RX2 window.

[Ahsan-Averos]

Hello Sir,
Sorry for late reply, I done all the things that you told me but still is not working!!!

[altishchenko]

Ok, @Ahsan-Averos can you send me your network server debug.log file?