I have updated Conduit to 1.4.16, but gateway stats still not working.

Home Forums Conduit: AEP Model I have updated Conduit to 1.4.16, but gateway stats still not working.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #23378
    10350 2058
    Blocked

    This is my gateway config. How do I solve the problem?

    {
       "gateway_conf":{
          "gateway_ID":"<WILL-BE-AUTO-REPLACED-WITH-LORA-EUI>",
          "keepalive_interval":10,
          "stat_interval":30,
          "push_timeout_ms":100,
          "forward_crc_disabled":false,
          "forward_crc_error":false,
          "forward_crc_valid":true,
          "server_address":"...",
          "serv_port_up":1700,
          "serv_port_down":1700,
       }
    }
    • This topic was modified 7 years, 1 month ago by 10350 2058.
    • This topic was modified 7 years, 1 month ago by 10350 2058.
    • This topic was modified 7 years, 1 month ago by 10350 2058.
    #23382
    Jason Reiss
    Keymaster

    Hello 10350 2058,

    What is the issue and what are you trying to do?

    Looks like you may be attempting to connect to the things network?
    https://www.thethingsnetwork.org/docs/gateways/multitech/aep.html
    https://www.thethingsnetwork.org/docs/gateways/packet-forwarder/semtech-udp.html

    Basic AEP instructions.

    Conduit AEP: Convert to Basic Packet Forwarder

    AEP 1.4.16 has a GUI to help configure of the packet forwarder
    http://www.multitech.net/developer/software/aep/lorawan-aep/lorawan-network-settings/

    Select Channel Plan US915 or EU868 or Other region
    Select FSB 2 if using US915
    Set server address and up/down ports to the remote server.
    Click Submit
    Restart LoRa Services to enact changes.

    Save or Save and Restart to make changes permanent.

    #23383
    10350 2058
    Blocked

    I hid my IP address. I setup LoRa Server, and I want the gateway sends its stats every 30 secs, but my LoRa Server didn’t received. I have searched the Google, someone said packet-forwarder must have protocol version 2, but I already updated Conduit to latest version (1.4.16). How can I modify packet-forwarder protocol version?

    #23386
    Jason Reiss
    Keymaster

    What is the model of installed MTAC-LORA card?
    MTAC-LORA-1.5 is required for v2 protocol packet forwarder.

    AEP Dashboard lists the card information.

    Accessory cards

    Card 2 (AP2)
    Model Number MTAC-LORA-868
    Serial Number xxxxxxxx
    Hardware MTAC-LORA-1.0

    #23391
    10350 2058
    Blocked

    My card is MTAC-LORA-1.0. So the only way is replacing my LoRa card with MTAC-LORA-1.5 version?

    Card 1	(AP1)
    Model Number	MTAC-LORA-915
    Serial Number	XXXXXXXX
    Hardware	MTAC-LORA-1.0
    #23392
    Jason Reiss
    Keymaster

    Yes, that is the easiest way, USB interface to the MTAC card is not included with the updated packet forwarder using v2 protocol.

    It may be possible to use a UDP bridge between the packet forwarder and network server to modify the protocol version byte to mimic v2.
    The uplink and downlink UDP packets are compatible between versions. v2 has added feedback from the packet forwarder JIT queueing.

    https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT

    #23393
    Jason Reiss
    Keymaster

    Otherwise if you are able to modify the lora server code to accept v1 or v2 UDP packets.

    #23403
    10350 2058
    Blocked

    Do you mean the LoRa server’s source code or configuration file? Because I couldn’t find any tutorial about changing accepted UDP version in configuration file of LoRa server.

    #23404
    Jason Reiss
    Keymaster

    I assume it is in source code.

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