/up -messages disappearing…

Home › Forums › Lora Network Server › /up -messages disappearing…

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • August 27, 2018 at 3:46 am #26180
    Ismo Penttinen
    Participant

    Hi.

    We have Conduit with m-linux in our lab. Lora-network-server is version 2.0.19.

    We have 8 min cycle in our end devices. We have noticed that there are holes in data… over 1 hour.

    So. We put another lora-gateway (not Conduit) to our lab and forward data to The Things Network.

    1. Then we noticed that our end devices sends data.

    2. Things Network shows data in correctly sequence.

    3. Conduit did not catch any /up messages.

    We have two terminals same time. One in Things Network Console, One in Conduit terminal (mosquitto_sub, lora-query).

    Here is lora-section of our lora-network-server:
    “lora” : {
    “ADRStep” : 30,
    “antennaGain” : 3,
    “beaconDelay” : 0,
    “beaconInterval” : 0,
    “beaconPower” : 27,
    “channelMask” : “”,
    “channelPlan” : “EU868”,
    “deviceQueueSize” : 2,
    “dutyCyclePeriod” : 60,
    “dwelltimeDown” : 0,
    “dwelltimeUp” : 0,
    “eui_1” : “00:80:00:00:A0:00:1F:11”,
    “frequencyAS” : 922600000,
    “frequencyBand” : “EU868”,
    “frequencyEU” : 867500000,
    “frequencyIN” : 866385000,
    “frequencyKR” : 922900000,
    “frequencySubBand” : 1,
    “joinByteOrder” : “LSB”,
    “joinDelay” : 5,
    “lbtEnabled” : false,
    “lbtScanTime” : 5000,
    “lbtSxOffset” : -24,
    “maxDatarate” : null,
    “maxDatarateEU” : 5,
    “maxDatarateUS” : 4,
    “maxEIRP” : 25,
    “maxTxPower” : 10,
    “minDatarate” : null,
    “minDatarateEU” : 0,
    “minDatarateUS” : 0,
    “netID” : “000001”,
    “rx1DatarateOffset” : 0,
    “rx1Delay” : 1,
    “rx2Datarate” : 3,
    “rx2Frequency” : 869525000,
    “sxOffset” : -162
    },
    “mqtt” : {
    “enabled” : true

    August 27, 2018 at 6:18 am #26181
    Jason Reiss
    Keymaster

    Is it OTA or ABP provisioned device?

    If the OTA end device is joined to the ttn network server the conduit will not have session keys to authenticate and decrypt the packet.

    Tcpdump of the uplink port 1780 should show packets received. Also network server log should show parsed and rejected packets.

    August 27, 2018 at 7:35 am #26183
    Ismo Penttinen
    Participant

    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.

    August 28, 2018 at 5:58 am #26216
    Ismo Penttinen
    Participant

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

    August 28, 2018 at 6:26 am #26218
    Jason Reiss
    Keymaster

    Search Results

    August 28, 2018 at 6:49 am #26219
    Jason Reiss
    Keymaster

    What is network server log output?
    What is packer forwarder output?

    It was once working with Conduit and now nothing?

    It is not be expected for the device to be joined in both network servers via OTA.

    August 28, 2018 at 6:56 am #26220
    Ismo Penttinen
    Participant

    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.

    August 28, 2018 at 8:55 am #26221
    Jason Reiss
    Keymaster

    Do you have similar results if the Conduit is set in packet forwarder mode and pointed to TTN?

    Do you see the same channels being missed or is it random? For instance 868.3 MHz was missed above, is this channel always missed?

    What is the SNR/RSSI of packets received at the gateway?

    Can you provide output from conduit of the installed card?

    
$ mts-io-sysfs show lora/*
    August 28, 2018 at 9:59 am #26223
    Jason Reiss
    Keymaster

    Ismo,

    Can you create a ticket at support.multitech.com?

    Please upload full config from the Conduit and record network server logging at TRACE level there.

    August 30, 2018 at 4:10 am #26236
    Ismo Penttinen
    Participant

    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

    August 30, 2018 at 4:11 am #26237
    Ismo Penttinen
    Participant

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

    August 30, 2018 at 5:58 am #26238
    Jason Reiss
    Keymaster

    So IMST shows -51 vs -104 dBm.

    Gateway misses 20% according to the PER.

    Looks to be a hardware issue.

    August 30, 2018 at 6:08 am #26239
    Jason Reiss
    Keymaster

    Do have the correct antenna installed?

    August 30, 2018 at 6:56 am #26240
    Ismo Penttinen
    Participant

    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.

  • Author
    Posts
Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.