Downlink que not sent to device

Home › Forums › Conduit: mLinux Model › Downlink que not sent to device

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • January 4, 2019 at 6:11 am #27025
    Nicolas Carvallo
    Participant

    Hello,

    I have a problem with my gateway. It uses to send downlinks with no problem. Now it just add the paquets to the queu but never send to device.
    I have an mlinux. Here is the log of the log:

    root@mtcdt:~# cat /var/log/lora-network-server.log | grep "33:34:37:39:66:37:7f:08\|33-34-37-39-66-37-7f-08"
11:11:0:691|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-PKT|FCNT: 00002482 LAST-FCNT: 00002481 Duplicate: no
11:11:0:691|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-MIC|ADDR: 66:37:7f:08 passed
11:11:0:691|INFO| ED:33-34-37-39-66-37-7f-08|PER|1.369863%
11:11:0:692|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|GW:00:80:00:00:a0:00:17:a0 Time_us:1561186291
11:11:0:692|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|Downlink Packets Queued: 1
11:11:0:693|INFO| ED:33-34-37-39-66-37-7f-08|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0 
11:16:51:167|INFO| ED:33-34-37-39-66-37-7f-08|QUEUE-TX|DATA SIZE: 2
11:21:0:621|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-PKT|FCNT: 00002483 LAST-FCNT: 00002482 Duplicate: no
11:21:0:621|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-MIC|ADDR: 66:37:7f:08 passed
11:21:0:622|INFO| ED:33-34-37-39-66-37-7f-08|PER|1.360544%
11:21:0:622|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|GW:00:80:00:00:a0:00:17:a0 Time_us:2161124683
11:21:0:622|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|Downlink Packets Queued: 2
11:21:0:623|INFO| ED:33-34-37-39-66-37-7f-08|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0 
11:30:46:790|INFO| ED:33-34-37-39-66-37-7f-08|QUEUE-TX|DATA SIZE: 2
11:31:0:550|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-PKT|FCNT: 00002484 LAST-FCNT: 00002483 Duplicate: no
11:31:0:550|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-MIC|ADDR: 66:37:7f:08 passed
11:31:0:550|INFO| ED:33-34-37-39-66-37-7f-08|PER|1.351351%
11:31:0:551|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|GW:00:80:00:00:a0:00:17:a0 Time_us:2761063163
11:31:0:551|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|Downlink Packets Queued: 3
11:31:0:551|INFO| ED:33-34-37-39-66-37-7f-08|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0 
11:41:0:483|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-PKT|FCNT: 00002485 LAST-FCNT: 00002484 Duplicate: no
11:41:0:484|INFO| ED:33-34-37-39-66-37-7f-08|CHECK-MIC|ADDR: 66:37:7f:08 passed
11:41:0:484|INFO| ED:33-34-37-39-66-37-7f-08|PER|1.342282%
11:41:0:484|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|GW:00:80:00:00:a0:00:17:a0 Time_us:3361000707
11:41:0:485|DEBUG| ED:33-34-37-39-66-37-7f-08|PACKET-RX|Downlink Packets Queued: 3
11:41:0:485|INFO| ED:33-34-37-39-66-37-7f-08|FCTRL|ADR:0 ADRACK:0 ACK:0 CLASS:A OPTS:0 
11:48:34:698|INFO| ED:33-34-37-39-66-37-7f-08|QUEUE-TX|DATA SIZE: 2

    Any help on this?
    thanks

    January 4, 2019 at 6:36 am #27026
    Jason Reiss
    Keymaster

    Please create support ticket and provide sw and hw version info. Also provide full logs of state transition from working to non-working if possible.

    support.multitech.com

    January 4, 2019 at 6:48 am #27027
    Jason Reiss
    Keymaster

    Could be scheduling conflict or duty-cycle limits. What channel plan is used?

    January 6, 2019 at 1:48 am #27031
    Nicolas Carvallo
    Participant

    Hello Jason,

    How can I know the hw and sw version with SSH? My gtw is 12.000 km away at the client’s site.

    How can I see if it is a scheduling conflict or duty-cycle limits?

    Thanks
    Nicoalas

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