[Ismo Penttinen]

I have same problem.

[Ismo Penttinen]

we have a round antenna. I think it becomes with mtac-1.50…

sorry.. IMST is closer. We have to move conduit to longer distance, cause there were lots of problems when Conduit was in same room as 40 end devices…

but -107 should be ok.

[Ismo Penttinen]

and IMST -forwarder shows data in TTN with right sequence..

[Ismo Penttinen]

I tried to login support. There was already account to my email.. i tried to reset… no luck..

root@kausala0218:/dev# mts-io-sysfs show lora/*
1
1
19498611
00:80:00:00:A0:00:1F:11
MTAC-LORA-1.5
MTAC-LORA-H-868
1
Multi-Tech Systems

Devices should communicate in 2 min sequence… but there is still sometimes long holes in data. RSSI is – 104,

4:56:28:724|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
4:56:28:724|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.833332%
4:56:28:725|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 245104 ms
4:56:28:725|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
4:56:29:291|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
5:0:50:561|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000041 LAST-FCNT: 00000040 Duplicate: no
5:0:50:562|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:0:50:562|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.710058%
5:0:50:562|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 261839 ms
5:0:50:563|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:0:51:81|INFO| ED:37-41-50-0d-00-5f-00-58|MAC-COMMAND|ADR CMD 0300ff0001
5:0:51:81|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 110
5:4:57:216|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000043 LAST-FCNT: 00000041 Duplicate: no
5:4:57:216|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:4:57:216|INFO| ED:37-41-50-0d-00-5f-00-58|MISSED-PKT|Count: 1
5:4:57:217|INFO| ED:37-41-50-0d-00-5f-00-58|PER|21.052631%
5:4:57:218|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 246655 ms
5:4:57:218|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:4:57:784|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
5:9:27:302|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000044 LAST-FCNT: 00000043 Duplicate: no
5:9:27:303|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:9:27:303|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.930233%
5:9:27:303|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 270088 ms
5:9:27:304|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:9:27:825|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
5:9:51:952|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000044 LAST-FCNT: 00000044 Duplicate: yes
5:9:51:953|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:9:51:953|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.809248%
5:9:51:953|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 24651 ms
5:9:51:954|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:9:52:484|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
5:14:46:652|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000045 LAST-FCNT: 00000044 Duplicate: no
5:14:46:652|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:14:46:653|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.689655%
5:14:46:653|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 319351 ms
5:14:46:654|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:14:47:282|INFO| ED:37-41-50-0d-00-5f-00-58|MAC-COMMAND|ADR CMD 0300ff0001
5:14:47:283|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 110
5:18:51:975|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000046 LAST-FCNT: 00000045 Duplicate: no
5:18:51:975|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:18:51:976|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.571428%
5:18:51:977|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:2 LAST-PKT: 245324 ms
5:18:51:977|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:18:52:517|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
5:24:52:495|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 00000048 LAST-FCNT: 00000046 Duplicate: no
5:24:52:496|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:24:52:496|INFO| ED:37-41-50-0d-00-5f-00-58|MISSED-PKT|Count: 1
5:24:52:497|INFO| ED:37-41-50-0d-00-5f-00-58|PER|20.903955%
5:24:52:497|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 360521 ms
5:24:52:498|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Use RX1 TOA:214 ms
5:24:53:43|INFO| ED:37-41-50-0d-00-5f-00-58|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115

HERE 12 MINUTES….

5:31:0:944|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-PKT|FCNT: 0000004a LAST-FCNT: 00000048 Duplicate: no
5:31:0:944|INFO| ED:37-41-50-0d-00-5f-00-58|CHECK-MIC|ADDR: 03-12-12-e6 passed
5:31:0:944|INFO| ED:37-41-50-0d-00-5f-00-58|MISSED-PKT|Count: 1
5:31:0:945|INFO| ED:37-41-50-0d-00-5f-00-58|PER|21.229050%
5:31:0:945|INFO| ED:37-41-50-0d-00-5f-00-58|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 368449 ms

[Ismo Penttinen]

i was tailing /var/log/lora-network-server.log and same time having open console in TTN.

It is joined with whitelisting in Conduit. TTN shows only crypted packages like this:
{
“gw_id”: “eui-b827ebfffe8ad57f”,
“payload”: “QF2ozQKAZg8Cs9eEoqlGGpelAvl9jJET3YaZPC4pJ5aa”,
“f_cnt”: 3942,
“lora”: {
“spreading_factor”: 9,
“bandwidth”: 125,
“air_time”: 246784000
},
“coding_rate”: “4/5”,
“timestamp”: “2018-08-28T11:53:19.927Z”,
“rssi”: -51,
“snr”: 11.5,
“dev_addr”: “02CDA85D”,
“frequency”: 868300000
}

Dev-addr is same as addr in Conduit session list. This way we were tracing up -messages. So device is joined Conduit.

We have earlier also lost packages, but not so much.

[Ismo Penttinen]

No help…. devices are sending data, but Conduit is deaf…

[Ismo Penttinen]

OTA. Devices are joined to our system. They are “Whitelisted” there. There is no data in network-server-log, no parsed or rejected… in current timestamp.

I’ll check tcpdump.

[Ismo Penttinen]

and… after clearing whitelist… and restarting lora-network-server:

we have 5. devices.

2 pc tries join..

and 3 devices:

10:23:24:172|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-44-fa-e1 VALUE: 45
10:23:35:704|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-f9-56-48 VALUE: 45
10:23:48:835|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-44-fa-e1 VALUE: 45
10:24:0:364|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-f9-56-48 VALUE: 45
10:24:13:494|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON:

why i can see these??.. there are no sessions…

[Ismo Penttinen]

without / and tried lora-query too… still problems..

We are now testing with 6 devices…

Now lora network is jammed. Lora-network-server log:
– lora-network-server restarted
– mosquitto restarted
– conduit restarted…

9:28:26:80|INFO| GW:00-80-00-00-a0-00-20-80|UDP-TX|JSON-SIZE:312
9:28:26:83|WARNING| GW:00-80-00-00-a0-00-20-80|TX-ACK|ERROR: {“txpk_ack”:{“error”:”TOO_EARLY”}}
9:28:34:109|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
9:28:34:123|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 02-8f-33-88 VALUE: 45
9:28:37:973|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
9:28:37:979|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-f9-56-48 VALUE: 45
9:28:40:417|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
9:28:40:577|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-1f-ac-83 VALUE: 45
9:28:51:672|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
9:28:51:675|INFO| ED:37-41-50-0d-00-48-00-44|CHECK-PKT|FCNT: 00000004 LAST-FCNT: 00000004 Duplicate: yes
9:28:51:675|INFO| ED:37-41-50-0d-00-48-00-44|CHECK-MIC|ADDR: 03-44-fa-e1 passed
9:28:51:675|INFO| ED:37-41-50-0d-00-48-00-44|PER|0.000000%
9:28:51:676|INFO| ED:37-41-50-0d-00-48-00-44|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0
9:28:51:676|INFO| ED:37-41-50-0d-00-48-00-44|SCHED-TX|Use RX1 TOA:255 ms
9:28:52:432|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-TX|IP: 127.0.0.1:49856 CH: LC2 DEV: 03-44-fa-e1 FCNT: 0000000c REPEAT: 0
9:28:52:436|INFO| ED:37-41-50-0d-00-48-00-44|SCHED-TX|Q-SIZE: 1 PKT-ROOM: 115
9:28:52:445|INFO| Update DC Band: 1 Duration: 205 time-on-air available: 390 ms
9:28:52:445|INFO| GW:00-80-00-00-a0-00-20-80|UDP-TX|JSON-SIZE:312
9:28:52:449|INFO| GW:00-80-00-00-a0-00-20-80|TX-ACK|OK
9:28:58:382|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
9:28:58:386|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 02-8f-33-88 VALUE: 45

mosquitto_sub -v -t “#”:
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)
lora/37-41-50-0d-00-54-00-60/queue_full (null)
lora/37-41-50-0d-00-54-00-60/clear (null)

[Ismo Penttinen]

We have still problems….

suddenly lora-network-server started to fill log with:
12:40:7:52|WARNING| NULL message pulled from mqtt queue

and in the end, lora-network-server stopped to communicate with devices. We reboot Conduit and communication started…

There was also messages that queue was full. We tried to clear queue with /lora/<deviceid>/clear mosquitto topic.. no success..

and question: why command “lora-query -x packet queue ” shows messages to be queued with old timestamp. If you tried to delete these records with mosquitto topic, no success. But if you use:

lora-query -x packet queue delete 37-41-50-0d-00-65-00-60

queue record is removed…

We have 40 devices connected, but it seems that it is too much for Conduit… sad.

We are using mosquitto to connect lora-network-server.

[Ismo Penttinen]

hi.

We have six devices.

It seems that lora-network-server keeps device sessions alive, although we have deleted the device from whitelist and restarted lora-network-server.

The do not retry cause lora-network-server sends ack to they messages.

yrs.
Ismo

[Ismo Penttinen]

11:16:33:958|WARNING| Response packet dropped, could not schedule : 02-cb-a9-3d
11:16:33:959|WARNING| Cannot unschedule join response, tossing packet

[Ismo Penttinen]

Problems still exists… if device is whitelisted, lora-network-server does not send join-accepted message… we have 50 devices, 20 did not get join-accepted.

[Ismo Penttinen]

And we are using mlinux.

It seems once, that lora-network-server sent ack -signal to the device, which was not in session list …

[Ismo Penttinen]

Hi.

if you add a device only to configuration whitelist. Is it enough or do you have to add them manually to session and to devicelist ???

And if you remove a device from Whitelist. do you have to remove it from session and devicelists.

yrs.
Ismo

[Ismo Penttinen]

There are devices in three different lists:
* node-list, lora-query –node-list
* session-list, lora-query -x session list
* device-list, lora-query -x device list
* whitelist in configurations /var/config/lora/lora-network-server.conf

How to add device with whitelisting?
how to remove device with whitelisting?

Now lora-query -x device add … does not add device to lora-network-server configuration’s whitelist.

I assumed that if there are no devices in session list. There should not become log like this:

7:10:40:371|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
7:10:40:371|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|CRC-ERROR
7:10:41:705|INFO| GW:00-80-00-00-a0-00-20-80|FRAME-RX|Parsing 1 packets
7:10:41:708|WARNING| GW:00-80-00-00-a0-00-20-80|FRAME-RX|REJECTED|REASON: Message received from unknown device 03-27-80-f5 VALUE: 45

• This reply was modified 6 years, 9 months ago by Ismo Penttinen.

[Ismo Penttinen]

And we have 2.0.19 lora-network-server. We have also cleared session list.

We are wondering why lora-network-server send acks? our device will rejoin if there is no ack in /up/ -message.

yrs.
Ismo

[Ismo Penttinen]

Problem solved.. sim-adapter was poor… thanks.

[Author]

Posts