MultiTech Developer Resources » Topic: RN2903A based device does not join (OTAA) Conduit AP anymore

RN2903A based device does not join (OTAA) Conduit AP anymore

This topic has 2 replies, 1 voice, and was last updated 6 years, 3 months ago by Albert Beukman.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts

December 29, 2017 at 6:41 pm #22211

Participant

Summary
RN2903A based device joined directly after setting up the Conduit AP. A day later, they don’t join anymore, but still join to other Conduit AEP devices.

Join fail on: MTCAP-LNA3-915-001A Firmware1.4.4 LNSv1.0.41
Join OK on: MTCDT-H5-210A-US-EU-GB v1.4.3 LNSv1.0.31
Confirmed network server settings identical on the two devices.

Any feedback on how I can get the RN2903A based devices to join the Conduit AP would be greatly appreciated.

Detail
Summary of sequence of events.
# Configured Conduit AP
# Multiple units joined OK
# 2-way comms confirmed OK
# Approx. 1 day elapsed
# Units joined to other Conduit IP67 gateway v1.4.3 LNSv1.0.31 for undetermined amount of time.
# Power down other gateway
# Units did not join Conduit AP v1.4.4 LNS v1.0.41
# Power cycle end units.
# Soft reset network server
# Soft reset Conduit.
# Roll back LNS to v1.0.26
# Upgrade LNS back to v1.0.41
# Tried to manually add nodes based on [forum article|http://www.multitech.net/developer/forums/topic/join-issue-with-microchip-lora-radio-rn2903/]
# Join fail up until this point.
# Join OK within 45 s to Conduit v1.3.3 LNS v1.0.26.
# Join OK within 45 s to Conduit v1.4.3 LNS v1.0.31.

Conduit AP Network server configuration

{
  "udp": {
    "appPortUp": 1784,
    "appPortDown": 1786,
    "downstreamPort": 1782,
    "upstreamPort": 1780
  },
  "log": {
    "syslog": true,
    "path": "/var/log/",
    "console": true,
    "level": 50
  },
  "whitelist": {
    "enabled": true,
    "devices": []
  },
  "addressRange": {
    "start": "00:00:00:01",
    "end": "FF:FF:FF:FE"
  },
  "db": "/var/run/lora/lora-net-server.db",
  "mqtt": {
    "host": "127.0.0.1",
    "enabled": true,
    "port": 1883
  },
  "__v": 1,
  "test": {
    "disableRxWindow2": false,
    "disableDutyCycle": false,
    "disableRxWindow1": false,
    "disableRxJoin1": false,
    "disableRxJoin2": false
  },
  "lora": {
    "channelPlan": "US915",
    "frequencyBand": 915,
    "rx2Datarate": 8,
    "antennaGain": 3,
    "frequencyKR": 922900000,
    "frequencySubBand": 1,
    "dwelltimeUp": 0,
    "frequencyEU": 869500000,
    "netID": "000000",
    "dutyCyclePeriod": 60,
    "packetForwarderConfig": "",
    "frequencyAS": 922600000,
    "packetForwarderMode": false,
    "lbtEnabled": false,
    "rx1Delay": 1,
    "minDatarate": 0,
    "nodeQueueSize": 16,
    "maxEIRP": 20,
    "maxTxPower": 26,
    "rx1DatarateOffset": 0,
    "joinDelay": 5,
    "dwelltimeDown": 0,
    "enabled": true,
    "ADRStep": 30,
    "maxDatarate": 4,
    "enableStrictCounterValidation": false
  },
  "network": {
    "key": "<Key>",
    "leasetime": 86400,
    "name": "",
    "baseKey": "",
    "passphrase": "",
    "eui": "<EUI>",
    "salt": "",
    "public": true
  }
}

/var/log/messages shows debug regarding packet forwarder being quiet

2017-12-29T16:24:53.530626-08:00 mtcap lora-network-server: Packet forwarder not seen in 720 s
2017-12-29T16:25:23.530655-08:00 mtcap lora-network-server: Packet forwarder not seen in 750 s
2017-12-29T16:25:53.530751-08:00 mtcap lora-network-server: Packet forwarder not seen in 780 s

January 10, 2018 at 11:06 am #22298

Albert Beukman

Participant

Additional detail Multitech Support requested requested as follows for the reader of this article’s reference.
* Did not reconfigure the for ABP during manual add process – was throwing the kitchen sink at the problem at this stage.
* Experimental setup did change slightly between join and not join. Change deemed to be negligible as it was approx. 0.002 of observed effective end-device range. (e.g. if we’ve established reliable 1000 ft range, relative position changed by approximately 2 feet).
* We do not have Multitech end-devices to test with.
* I believe there is a firmware update available for the Microchip device. That being said, I’d still appreciate attention to the posted logs.
** Downgrading the Lora Network Server (LNS) did not have an effect. If it was a later conformancy issue, I’d expect join with earlier LNS versions.
* I don’t have access / tools to RN2903A logs / terminal output at the moment. Will try to get these if at all possible.

January 10, 2018 at 11:09 am #22299

Albert Beukman

Participant

Worked with Multitech support and posting some details in case the next developer runs into the same issue.

Attempted solutions
They suggested I try to manaully reset the packet forwarded (“Packet forwarder not seen” debug). This might work for the next reader of this post, but did not work for me; I got a segmentation fault. Sending hardware back to Multitech for investigation.

Suggested course of action if you’re experiencing the same issue: Contact Multitech Support directly.

Expected terminal commands & output

admin@mtcap:~# ps auxw | grep lora
admin      344  0.2  0.4   2632  1140 ?        S    Jan05   8:47 /bin/bash /usr/sbin/lora-led-updater
admin     1907  0.0  0.1   1912   408 ?        S    Jan05   0:04 /sbin/angel /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin     1909  1.0  1.4  17348  3608 ?        S<l  Jan05  44:18 /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin     1928  0.0  0.1   1912   408 ?        S    Jan05   0:04 /sbin/angel /var/run/lora/1/lora_pkt_fwd
admin     1929  2.9  0.3  35436   960 ?        S<l  Jan05 125:57 /var/run/lora/1/lora_pkt_fwd
admin    19680  0.0  0.2   2980   584 pts/0    S+   15:33   0:00 grep lora
admin@mtcap:~# kill 1928
admin@mtcap:~# ps auxw | grep lora
admin      344  0.2  0.4   2632  1140 ?        S    Jan05   8:47 /bin/bash /usr/sbin/lora-led-updater
admin     1907  0.0  0.1   1912   408 ?        S    Jan05   0:04 /sbin/angel /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin     1909  1.0  1.4  17348  3608 ?        S<l  Jan05  44:20 /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin     1928  0.0  0.1   1912   412 ?        S    Jan05   0:04 /sbin/angel /var/run/lora/1/lora_pkt_fwd
admin    20076  0.0  0.2   2980   584 pts/0    S+   15:37   0:00 grep lora
admin@mtcap:~# kill 1928
-bash: kill: (1928) - No such process
admin@mtcap:~# ps auxw | grep lora
admin      344  0.2  0.4   2632  1140 ?        S    Jan05   8:48 /bin/bash /usr/sbin/lora-led-updater
admin     1907  0.0  0.1   1912   408 ?        S    Jan05   0:04 /sbin/angel /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin     1909  1.0  1.4  17348  3608 ?        S<l  Jan05  44:21 /opt/lora/lora-network-server -c /var/config/lora/lora-network-server.conf --lora-eui 00:80:00:00:00:00:F0:B6 --lora-hw-1 MTCAP-LORA-1.5 --lora-prod-1 MTCAP-LORA-868 --lora-path /var/run/lora --db /var/config/lora/lora-network-server.db --noconsole
admin    20154  0.0  0.2   2980   584 pts/0    S+   15:37   0:00 grep lora
admin@mtcap:~# cd /var/run/lora/1
admin@mtcap:/var/run/lora/1# ./lora_pkt_fwd 
*** Beacon Packet Forwarder for Lora Gateway ***
Version: 3.1.0
*** Lora concentrator HAL library version info ***
Version: 4.1.3;
***
INFO: Little endian host
INFO: found global configuration file global_conf.json, parsing it
INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
INFO: lorawan_public 1, clksrc 0
lgw_board_setconf:397: Note: board configuration; lorawan_public:1, clksrc:0
INFO: LBT is disabled
INFO: antenna_gain 0 dBi
INFO: Configuring TX LUT with 16 indexes
INFO: radio 0 enabled (type SX1257), center frequency 868500000, RSSI offset -162.000000, tx enabled 1, tx_notch_freq 129000
lgw_rxrf_setconf:458: Note: rf_chain 0 configuration; en:1 freq:868500000 rssi_offset:-162.000000 radio_type:2 tx_enable:1 tx_notch_freq:129000
INFO: radio 1 enabled (type SX1257), center frequency 869400000, RSSI offset -162.000000, tx enabled 0, tx_notch_freq 0
lgw_rxrf_setconf:458: Note: rf_chain 1 configuration; en:1 freq:869400000 rssi_offset:-162.000000 radio_type:2 tx_enable:0 tx_notch_freq:0
INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 0 configuration; en:1 freq:-400000 SF_mask:0x7e
INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 1 configuration; en:1 freq:-200000 SF_mask:0x7e
INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 2 configuration; en:1 freq:0 SF_mask:0x7e
INFO: Lora multi-SF channel 3>  radio 0, IF 300000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 3 configuration; en:1 freq:300000 SF_mask:0x7e
INFO: Lora multi-SF channel 4>  radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 4 configuration; en:1 freq:-400000 SF_mask:0x7e
INFO: Lora multi-SF channel 5>  radio 1, IF 125000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 5 configuration; en:1 freq:125000 SF_mask:0x7e
INFO: Lora multi-SF channel 6>  radio 1, IF 400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 6 configuration; en:1 freq:400000 SF_mask:0x7e
INFO: Lora multi-SF channel 7 disabled
lgw_rxif_setconf:485: Note: if_chain 7 disabled
INFO: Lora std channel> radio 0, IF -200000 Hz, 250000 Hz bw, SF 7
lgw_rxif_setconf:551: Note: LoRa 'std' if_chain 8 configuration; en:1 freq:-200000 bw:2 dr:2
INFO: FSK channel> radio 0, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
lgw_rxif_setconf:607: Note: FSK if_chain 9 configuration; en:1 freq:300000 bw:3 dr:50000 (50000 real dr) sync:0xC194C1
INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to 008000000000F0B6
INFO: server hostname or IP address is configured to "127.0.0.1"
INFO: upstream port is configured to "1780"
INFO: downstream port is configured to "1782"
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 20 seconds
INFO: upstream PUSH_DATA time-out is configured to 120 ms
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: FPGA supported features: [TX filter]  [Spectral Scan] 
lgw_start:793: Note: calibration started (time: 2300 ms)
lgw_start:814: Note: calibration finished (status = 191)
Info: Initialising AGC firmware...
Info: putting back original RADIO_SELECT value
INFO: [main] concentrator started, packet can now be received

INFO: Disabling GPS mode for concentrator's counter...
INFO: host/sx1301 time offset=(1515425896s:885569Âµs) - drift=-1773900479Âµs
INFO: Enabling GPS mode for concentrator's counter.

INFO: [down] PULL_ACK received in 0 ms
lgw_receive:1125: FIFO content: 1 10 0 5 12
lgw_receive:1144: [2 17]
Note: LoRa packet

INFO: Received pkt from mote: 00DD0006 (fcnt=7973)

JSON up: {"rxpk":[{"tmst":7633388,"chan":2,"rfch":0,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF8BW125","codr":"4/5","lsnr":4.0,"rssi":-89,"size":18,"data":"QAYA3QAAJR8B60z5DS+SK3/C"}]}
lgw_receive:1125: FIFO content: 1 32 0 5 12
lgw_receive:1144: [1 17]
Note: LoRa packet

Segmentation fault commands & output

admin@mtcap:/var/log# ps auxw | grep lora
admin      330  0.2  0.4   2632  1140 ?        S    Jan03   6:04 /bin/bash /usr/sbin/lora-led-updater
admin    29747  2.0  0.2   2980   584 pts/0    S+   11:53   0:00 grep lora
admin@mtcap:/var/log# cd /var/run/lora/l/
-bash: cd: /var/run/lora/l/: No such file or directory
admin@mtcap:/var/log# cd /var/run/lora/1/
admin@mtcap:/var/run/lora/1# ./lora_pkt_fwd
*** Beacon Packet Forwarder for Lora Gateway ***
Version: 3.1.0
Segmentation fault
admin@mtcap:/var/run/lora/1# ps auxw | grep lora
admin      330  0.2  0.4   2632  1140 ?        S    Jan03   6:04 /bin/bash /usr/sbin/lora-led-updater
admin    30020  0.0  0.2   2980   584 pts/0    S+   11:56   0:00 grep lora

EDIT: Fix second code block
EDIT: Try to fix post to show both code blocks reliably.

This reply was modified 6 years, 3 months ago by Albert Beukman. Reason: Fix second code block
This reply was modified 6 years, 3 months ago by Albert Beukman.

Author

Posts

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

RN2903A based device does not join (OTAA) Conduit AP anymore

User

Sitemap

Pages

Forums