Problem at OTAA Join Request

[lgkoyuncu]

Hi I have trouble to parse Join Accept. I am tring with Helium Console. OTAA 1.0.2

pi@raspberrypi:~/deneme/lora-mote-emulator $ mote -v 1.0.2 join -n

2023-10-04 03:40:15,727 - INFO - Forming a join request message - NwkKey: 01010101010101010101010101010101, AppKey: 01010101010101010101010101010101, AppEUI: a100000000000001, DevEUI: a100000000000001, DevNonce: 15, MIC: 3c55be3e,Final Join Req: 0001000000000000a101000000000000a10f003c55be3e --

2023-10-04 03:40:15,728 - INFO - Sending a PUSH DATA - Verson: 02, Token: 2faf, Identifier: 00, GatewayEUI: aa555a0000000000

2023-10-04 03:40:15,730 - INFO - Receiving a PUSH ACK - Version: 02, Token: 2faf, Identifier: 01

2023-10-04 03:40:18,033 - ERROR - Bad config file format, please copy a new file from template.

Where i did mistake?

[houluy]

Hi, please check the last line of log: ERROR - Bad config file format, please copy a new file from template.

You need to copy a configure file from the template file, and modify the configures according to your environment. All the configure templates are in the path src/template. Also, please notify that all the configure files are in JSON format. Make sure that the format is strictly correct as JSON format.

BTW, the LoRaWAN 1.0.2 is not fully tested, there may be some issues. Let me know if you run into sth bad. Thanks!

[lgkoyuncu]

Hi,

[https://res.cdn.office.net/assets/mail/file-icon/png/generic_16x16.png]config.jsonhttps://1drv.ms/u/s!Ah04-WA4lDh7hsGjQwoSqwlrGn_MaM8 [https://res.cdn.office.net/assets/mail/file-icon/png/generic_16x16.png]device.jsonhttps://1drv.ms/u/s!Ah04-WA4lDh7hsGjRLksPG5T-pScQS4 [https://res.cdn.office.net/assets/mail/file-icon/png/generic_16x16.png]device102.jsonhttps://1drv.ms/u/s!Ah04-WA4lDh7hsGjRW7nEzsmRrIfqwU [https://res.cdn.office.net/assets/mail/file-icon/png/generic_16x16.png]gateway.jsonhttps://1drv.ms/u/s!Ah04-WA4lDh7hsGjRm065d-Rh_zfu4c [https://res.cdn.office.net/assets/mail/file-icon/png/generic_16x16.png]abp.jsonhttps://1drv.ms/u/s!Ah04-WA4lDh7hsGjRw_pvlDYSVWMe_w

I send all my config files. I am using with Helium Console. Helium is using v1.0.2. There is no Netwkey.

-v 1.0.2 does not work. I put Netwkey same as AppKey. I got Join Accept but when i send uplink data Helium does not response.

Also i try to decode uplink data, I saw MIC calculation error and Fcnt value as zero.

Also one more problem is, for my every join request DevAddr would be increased by one.

I can give remote access if you want.

Thank you

---

Gönderen: Hou Lu @.> Gönderildi: 7 Ekim 2023 Cumartesi 06:50 Kime: houluy/lora-mote-emulator @.> Bilgi: lgkoyuncu @.>; Author @.> Konu: Re: [houluy/lora-mote-emulator] Problem at OTAA Join Request (Issue #16)

Hi, please check the last line of log: ERROR - Bad config file format, please copy a new file from template.

You need to copy a configure file from the template file, and modify the configures according to your environment. All the configure templates are in the path src/template.

BTW, the LoRaWAN 1.0.2 is not fully tested, there may be some issues. Let me know if you run into sth bad. Thanks!

— Reply to this email directly, view it on GitHubhttps://github.com/houluy/lora-mote-emulator/issues/16#issuecomment-1751588374, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIDVRGHTCA63TU3ZH3BFPULX6DGQDAVCNFSM6AAAAAA5RZBD7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGU4DQMZXGQ. You are receiving this because you authored the thread.Message ID: @.***>

[lgkoyuncu]

https://onedrive.live.com/?authkey=%21AAoSqwlrGn%5FMaM8&id=7B38943860F9381D%2113652418&cid=7B38943860F9381D

File links not working above

[houluy]

Sorry, still cannot see the config files. For Join Req with 1.0.2 and OTAA, first to modify device infomation in device.json copied. An example:

{
    "Device": {
        "JoinEUI": "0000000000000000",
        "DevEUI": "0000000000000000"
    },
    "RootKeys": {
        "AppKey": "00000000000000000000000000000000",
        "NwkKey": "00000000000000000000000000000000"
    }
}

NOTE FOR V1.0: Set JoinEUI equal to AppEUI and set NwkKey equal to AppKey.

Then, use the following command:

mote pull
mote join -n

[lgkoyuncu]

{ "Device": { "JoinEUI": "A100000000000001", "DevEUI": "A100000000000001" }, "RootKeys": { "AppKey": "01010101010101010101010101010101", "NwkKey": "01010101010101010101010101010101" } }

This is my device config

[lgkoyuncu]

mote pull mote join -n

I tried. I got join accept. When try to send uplink data mic would be calculated wrong.

[lgkoyuncu]

LoRa Motes Information: DevEUI: a100000000000001 JoinEUI: a100000000000001 NwkKey: 01010101010101010101010101010101 AppKey: 01010101010101010101010101010101 Activation mode: OTAA Activation status: True

DevAddr: 480002b8 FCntUp: 1 ACKed Downlink Count: 0 ACKed Uplink Count: 0 JSIntKey: 687e3f1556d30d8b722548e7b890088c JSEncKey: 70f8024095ccf377bc142f682a8ccfa7 FNwkSIntKey: 7c0b01cf7e0efcd720e1f88fdc88cb2e SNwkSIntKey: 7c0b01cf7e0efcd720e1f88fdc88cb2e NwkSEncKey: 7c0b01cf7e0efcd720e1f88fdc88cb2e AppSKey: 0b313bf730b82957b26b181166df9358 JoinNonce: c6aec7 DevNonce: 57 Rjcount0: 0 Rjcount1: 0 Last message has not been acknowledged yet

[lgkoyuncu]

I have problem at uplink data.

[lgkoyuncu]

Helium is using version 1.0.2.

I created device details at Helium like that

Device EUI : A100000000000001 App EUI : A100000000000001 App Key : 01010101010101010101010101010101

[houluy]

Might be some problems in code which is inconsistent with the protocol. Consider using ChirpStack (Docker deployment is very convenient) and V1.1 or check the MIC calculation process code (calcmic_app function in src/mac.py).

[lgkoyuncu]

I need to use with Helium. Helium is using v1.0.2

Could you help me to fix this issue. I couldnt find anyone to fix this problem at freelancer. I can pay for your help

Android için Outlookhttps://aka.ms/AAb9ysg edinin

---

From: Hou Lu @.> Sent: Saturday, October 7, 2023 11:07:51 AM To: houluy/lora-mote-emulator @.> Cc: lgkoyuncu @.>; Author @.> Subject: Re: [houluy/lora-mote-emulator] Problem at OTAA Join Request (Issue #16)

Might be some problems in code which is inconsistent with the protocol. Consider using ChirpStack (Docker deployment is very convenient) and V1.1 or check the MIC calculation process code (calcmic_app function in src/mac.py).

— Reply to this email directly, view it on GitHubhttps://github.com/houluy/lora-mote-emulator/issues/16#issuecomment-1751645172, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIDVRGAN43LQ27VMMLQ2GWTX6EEVPAVCNFSM6AAAAAA5RZBD7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGY2DKMJXGI. You are receiving this because you authored the thread.Message ID: @.***>