Join Requests are not be acknowledged

[chipmc]

I am using v2.3.1 of LMIC library and 0.5.2 of this library with MachineQ LoRaWAN service. I can see the Join MAC requests in the serial stream and the MachineQ sending a join accept. Yet, the device never acknowledges this and records EV_JOIN_FAILED after a few minutes. Any suggestions on what I can do to remedy this? Thanks, Chip

[terrillmoore]

@chipmc, sorry for the slow response. The emails get buried and then there's no good dashboard when managing multiple repos. (Probably there's an app for this.)

Anyway, it worked for me last time I tried it. Did you try changing your clock rate accuracy using LMIC_setClockError()? That's the most likely problem, opening the RX windows too late. What platform are you using?

[chipmc]

@terrillmoore , Thank you for responding and completely understand about having to track a number of message sources.

I do have a line in setup for clock error: LMIC_setClockError(MAX_CLOCK_ERROR * 1 / 100);

I am using the Adafruit Feather M0 LORA for this work.

Any other suggestions are greatly appreciated.

Thanks, Chip

[terrillmoore]

Hmm, I tested on a Feather M0 LoRa and it worked for me.

If you're adding a bare Feather M0 LoRa, you must jumper D6 to DIO1. MCCI's wings do this, so if you're using one of our wings, don't worry about this. Otherwise, jumper JP1-1 to JP3-9. (It's bizarre, I thought this was documented everywhere, but apparently not.)

After confirming that, try changing the clock error to 10%: LMIC_setClockError(MAX_CLOCK_ERROR * 10 / 100);.

If still no luck, you can try using MCCI's SAMD board package in the Arduino board selection menu, select the Catena 4410 as the target board. We fixed a number of things related to clock (ms-timer) handling, and it's possible that we inadvertently introduced a requirement to work with our BSP.

[chipmc]

Terry, Thank you! I had installed the jumper as required but will give your other suggestions a try when I get back home. Thank you!

…

-- Chip McClelland 919-624-5562 On February 10, 2019 at 4:02:11 PM, Terry Moore (notifications@github.com) wrote: Hmm, I tested on a Feather M0 LoRa and it worked for me. If you're adding a bare Feather M0 LoRa, you must jumper D6 to DIO1. MCCI's wings do this, so if you're using one of our wings, don't worry about this. Otherwise, jumper JP1-1 to JP3-9. (It's bizarre, I thought this was documented everywhere, but apparently not.) After confirming that, try changing the clock error to 10%: LMIC_setClockError(MAX_CLOCK_ERROR * 10 / 100);. If still no luck, you can try using MCCI's SAMD board package in the Arduino board selection menu, select the Catena 4410 as the target board. We fixed a number of things related to clock (ms-timer) handling, and it's possible that we inadvertently introduced a requirement to work with our BSP. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#74 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF5tbReTq4jhuTLor_OTRrZ7GSVj_ZL_ks5vMIjSgaJpZM4ZkPOg> .

[chipmc]

Terry,

Well, I finally got to this item on my queue. First, I tried adjusting the clock error as you suggest (LMIC_setClockError(MAX_CLOCK_ERROR * 1 / 100);). This did enable me to connect but, only after a couple dozen failed attempts. I also tried using your Catena 4410 BSP but, this did not seem to make any difference. Would it be possible for you to share the test sketch you used? Or, could you try my sketch on your device - just trying to isolate the issue. My Github repo is at: https://github.com/chipmc/Simple-Sense-LoRA-Prototype

Thank you in advance for your help.

Chip

[terrillmoore]

I'm running around today, but I'll try to take a look at the code during travel this afternoon.

[terrillmoore]

Very sorry @chipmc, this fell off my list. Is this still a problem?

[chipmc]

Terry,

Yes, and any help would be greatly appreciated.

Thanks, Chip

[terrillmoore]

I just re-noticed that this is for machineQ. My suggestions are as follows.

1. Please update to "current" LMIC and LoRaWAN. There are a number of fixes relative to JOIN that don't affect The Things Network but probably do affect machineQ.

2. Please try running the compliance script from current LMIC (changing credentials to match machineQ). It's very simple, but it's better instrumented. Send logs.

Thanks,
--Terry

[chipmc]

Terry,

OK, so I have updated to the latest LMIC (2.3.2), LoRAWAN (0.5.3) and ADK (0.2.0) libraries from MCCI. I can see the join requests coming to the MachineQ LogStream and, each time, I see a "Join Accepted" going back out. However, this accept is never acknowledged by the device which keeps sending Join requests.

So, I have completed your #1 above. I am happy to do #2 as well but, I need a little more direction as a Google search and a review of the LMIC documentation did not, for me, turn up a compliance script or how to run it.

Again, any help appreciated.

Thanks, Chip

[terrillmoore]

Ah, I wasn't clear.... you have to download the latest (post-release) versions of the LMIC and LoRaWAN libraries. For the compliance script, all you need is "current" LMIC -- it will show up as an example named "compliance-otaa-halconfig". Apart from the logging, which is done via a queue and therefore is a bit convoluted, I think it's pretty clear. The logging, however, is what we want, as it will show exactly what is going on during the JOIN-ACCEPT, including timestamps. If you're using git, clone the library and rename it to replace the existing library in ~/arduino/libraries.. definitely don't want the old one anywhere near by. If you have got it via the library manager, they insist on it being called mcci-lorawan-lmic-library; if you installed yourself, it's probably at arduino-lmic. In either case, zip up the old version and delete it, or move it somewhere altogether else (not in the arduino/libraries path). Then put the new version where the old version was (using git clone, unzip, etc.)

[chipmc]

OK, progress. Downloaded post release LMIC and LoRaLAN. Found the compliance script, edited it to add my credentials. But, I am getting a warning on compile and the following message in the serial terminal: "board not known to library; add pinmap or update getconfig_thisboard.cpp"

My board is the: Adafruit Feather M0

I then added the MCCI Catena Board Support Package and this got me past that issue.

Here is what I see in the serial terminal:

Starting
Packet queued
313397: EV_JOINING
313485: EV_TXSTART: ch 13 rps=0x4 (SF10 BW125 CR 4/5 Crc IH=0), datarate 0, opmode 88C
633646: EV_RXSTART: freq=926.3 rps=0x94 (SF10 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 336695, delta ms 4751
693650: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 336695, delta ms 5711
733654: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80
794117: EV_TXSTART: ch 65 rps=0x12 (SF8 BW500 CR 4/5 Crc IH=0), datarate 4, opmode 88C
1106334: EV_RXSTART: freq=923.9 rps=0x91 (SF7 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 795934, delta ms 4966
1152890: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 795934, delta ms 5711
1192894: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80
1478728: EV_TXSTART: ch 8 rps=0x4 (SF10 BW125 CR 4/5 Crc IH=0), datarate 0, opmode 88C
1798893: EV_RXSTART: freq=923.3 rps=0x94 (SF10 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 1501941, delta ms 4751
1858896: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 1501941, delta ms 5711
1898904: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80
1922948: EV_TXSTART: ch 65 rps=0x12 (SF8 BW500 CR 4/5 Crc IH=0), datarate 4, opmode 88C
2235165: EV_RXSTART: freq=923.9 rps=0x91 (SF7 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 1924765, delta ms 4966
2281721: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 1924765, delta ms 5711
2321795: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80
3130069: EV_TXSTART: ch 12 rps=0x4 (SF10 BW125 CR 4/5 Crc IH=0), datarate 0, opmode 88C
3450231: EV_RXSTART: freq=925.7 rps=0x94 (SF10 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 3153279, delta ms 4751
3510234: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 0, opmode 88C, txend 3153279, delta ms 5711
3550304: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80
3610194: EV_TXSTART: ch 65 rps=0x12 (SF8 BW500 CR 4/5 Crc IH=0), datarate 4, opmode 88C
3922410: EV_RXSTART: freq=923.9 rps=0x91 (SF7 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 3612011, delta ms 4966
3968967: EV_RXSTART: freq=923.3 rps=0x96 (SF12 BW500 CR 4/5 NoCrc IH=0), datarate 4, opmode 88C, txend 3612011, delta ms 5711
4008977: EV_JOIN_TXCOMPLETE: saveIrqFlags 0x80

It does not seem to get past this point. On the MachineQ Logstream, I see the same JoinRequest / JoinAccept endless loop.

Hope this helps and thank you again for your time.

Chip

[paulalting]

Hi Terry and Chip,
I am having a similar issue with the arduino-lmic library from Terry, and noticed your posts here Chip being similar to what I am having with that library.

So I thought I would use this library and see what results I get, so I downloaded the latest master of arduino-lorawan and use this with the compliance test as mentioned above.

My setup is Eclipse IDE with the Jantje plugin, Sloeber ver 4.3.
Boards platform is Adafruit samd ver 1.2.8

I set the lmic_project_config.h to use au921 as I am in Australia and have my gateway setup for this band. Gateway is RAK831 on RPi running LoraServer OS, that is, packet forwarder and app and network server all in one system, which seems ideal for for testing.

So, when I run up the example code: 'compliance-otaa-halconfig.ino' I get results that appear to match what you are getting Chip. The output from the Feather M0 with onboard LoRa 915MHz appears the same as what you are getting, as well as the live LoRaWAN packets as seen on the gateway/net/app server, simply a endless loop of UpLink JoinRequest followed by DownLink JoinAccept.

Terry, what advice can you suggest ?
Is there anything I can provide to assist ?

Edit: If I change both the gateway to US915 band plan and reset the lmic_project_config.h to us US915, the results appear the same both on the output of the Feather and LoRaServer.

Paul