lora network server logs documentation

Home Forums Lora Network Server lora network server logs documentation

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #19910
    Chad Goyette
    Participant

    Is there documentation that someone can point me to that explains the debug log messages. for the most part i understand what i am seeing but it would be nice to have a key to ensure everything is being interpreted correctly.
    below is a chunk of log for example. My question is more around descriptors for labels in frames such as |PER| and |Frame-RX|.

    user.info lora-network-server: GW:00:80:00:00:a0:00:01:3d|FRAME-RX|Parsing 1 packets
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: GW:00:80:00:00:a0:00:01:3d|FRAME-RX|DATA: 400700000080ea42014c23ccf91b66010197
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: GW:00:80:00:00:a0:00:01:3d|FRAME-RX|FREQ: 903.000000 MHz DR4 RSSI: -17 dB SNR: 100 cB
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: GW:00:80:00:00:a0:00:01:3d|FRAME-RX|TYPE: Unconfirmed Up
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: GW:00:80:00:00:a0:00:01:3d|PACKET-RX|ADDR: 00:00:00:07 FCnt:42ea
    Jul 12 04:50:34 mtcdt user.info lora-network-server: ED:00-80-00-00-00-00-af-47|CHECK-PKT|FCNT: 000042ea LAST-FCNT: 000042e9 Duplicate: no
    Jul 12 04:50:34 mtcdt user.info lora-network-server: ED:00-80-00-00-00-00-af-47|CHECK-MIC|ADDR: 00:00:00:07 passed
    Jul 12 04:50:34 mtcdt user.info lora-network-server: ED:00-80-00-00-00-00-af-47|PER|2.089329%
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: ED:00-80-00-00-00-00-af-47|PACKET-RX|GW:00:80:00:00:a0:00:01:3d Time_us:3850993603
    Jul 12 04:50:34 mtcdt user.debug lora-network-server: ED:00-80-00-00-00-00-af-47|PACKET-RX|Downlink Packets Queued: 0
    Jul 12 04:50:34 mtcdt user.info lora-network-server: ED:00-80-00-00-00-00-af-47|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0
    Jul 12 04:50:34 mtcdt user.info lora-network-server: ED:00-80-00-00-00-00-af-47|SCHED-TX|Use RX1 TOA:21 ms

    #19915
    Jason Reiss
    Keymaster

    FRAME-RX is processing something received and reported by the gateway hardware
    PACKET-RX has been able to parse it as a LoRaWAN packet
    PER is packet error rate, the FCNT of each packet is tracked and missed FCNT values count against the error rate of uplink packets.

    #19916
    Chad Goyette
    Participant

    Is this documented anywhere so I can reference as needed?

    #21231
    Andrew Neil
    Participant

    I would like to second the request for documentation on this!

    #22777
    Mike Brazier
    Participant

    Last post in 2017 and no reply..

    Is there any documentation on how to interpret these logs? It seems like it would be obvious how necessary this is for development purposes. Unsurprising that these are nowhere to be found.

    This terrible web interface for documentation is a complete bust, in my opinion.

    Hopefully Multitech can adapt to norms and provide some simple pdfs for the Conduit platform..

    Frustrated.

    #22783
    Jason Reiss
    Keymaster

    We have created a guide for the next version AEP 1.4.12 with network server v2.0.16.

    https://www.multitech.net/developer/wp-content/plugins/download-monitor/download.php?id=44

    Please post if additional details are needed and we will incorporate them in the guide.

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