"no address is available for the new devices" when node try to join.
Home › Forums › Lora Network Server › "no address is available for the new devices" when node try to join.
Tagged: no address
- This topic has 5 replies, 2 voices, and was last updated 6 years, 1 month ago by
Jason Reiss.
-
AuthorPosts
-
February 20, 2019 at 4:06 am #27287
chaoslans
ParticipantHi,
I’m upgrading the gateway MTCDT-H5-210A to 1.7, the nodes are all EU868. But at the same time only one node can join the network by OTAA, for the others, the trace shows “no address is available for the new devices” although the MIC check is ok. My devices have different appkey, the same appeui, so I have added the map in the key management page.
Then I downgrade the gateway to 1.6.4, the issue keeps.
Finally to 1.4.17, the issue disappear. All nodes work well. Could you help to check, we need to upgrade to 1.7 to support Ru864 test in the future. Thanks.
February 20, 2019 at 7:55 am #27290Jason Reiss
KeymasterHave you modified the Address Range Start or End values?
February 20, 2019 at 8:27 pm #27293chaoslans
ParticipantHi Jason,
Yes I modified the address range, but I’m sure it’s a big range, from 20000001 to 2FFFFFFF.
And today a new issue raised. In 1.4.17, the nodes have joined, but soon it shows the following error, what’s “not found in memory list”?
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|FRAME-RX|TYPE: Join Request
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|JOINREQ-RX|00ae01010000ac5900ff67180000ac5900b6cd
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|DEV-EUI|00-59-ac-00-00-18-67-ff
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|JOIN-EUI|00-59-ac-00-00-01-01-ae
Feb 21 10:42:19 mtcdt user.debug lora-network-server: GW:00-80-00-00-a0-00-30-8f|DEV-NONCE|cdb6
Feb 21 10:42:19 mtcdt user.info lora-network-server: ED:00-59-ac-00-00-18-67-ff|WL-SEARCH|Device found in whitelist
Feb 21 10:42:19 mtcdt user.debug lora-network-server: ED:00-59-ac-00-00-18-67-ff|CHECK-KEY|MIC Valid
Feb 21 10:42:19 mtcdt user.debug lora-network-server: ED:00-59-ac-00-00-18-67-ff|APP-NONCE|c7bcd1
Feb 21 10:42:19 mtcdt user.info lora-network-server: ED:00-59-ac-00-00-18-67-ff|DEV-ADDR|Found End Device in DB 670b756a
Feb 21 10:42:19 mtcdt user.err lora-network-server: ED:00-59-ac-00-00-18-67-ff|JOINREQ|Device not found in memory list
Feb 21 10:42:19 mtcdt user.err lora-network-server: SQL error: [no such column: class] on first call
Feb 21 10:42:19 mtcdt user.err lora-network-server: Failed to load device from databaseFebruary 21, 2019 at 1:42 am #27297chaoslans
ParticipantSeems it’s a bug of the parameter setting, I recover the addr range to 00000001-1fffffff, all nodes can join and send data normally.
February 21, 2019 at 6:11 am #27299Jason Reiss
KeymasterDowngrade does not keep database tables consistent. Need to factory default after downgrade or upgrade back to 1.7.0
February 25, 2019 at 10:11 am #27311Jason Reiss
KeymasterThe to 7 bits of the DevAddr are reserved for the NETID signature 7 least-significant-bits. The range is then limited to 0x01 – 0x01FFFFFE by the network server, Unfortunately the UI does not impose the same limitations.
The 0x20000001 value is above the maximum and only one address is available.
-
AuthorPosts
- You must be logged in to reply to this topic.