lora_pkt_fwd
Home › Forums › Conduit: mLinux Model › lora_pkt_fwd
Tagged: concentrator, error, fail, forwarder, LoRa
- This topic has 4 replies, 2 voices, and was last updated 7 years, 3 months ago by Máté Eckl.
-
AuthorPosts
-
August 14, 2017 at 9:37 am #20609Máté EcklParticipant
I am trying to configure a basic packet forwarder for my LoraWAN but nor the start script nor the manual way reaches to make it work.
With the init script it always seemed to start properly, but in the end there was no running packet forwarder process running, so I started trying to start it manually.
With the deamon I followed this tutorial and produced the steps necessarry for version <3.2 (mine is 3.12.27). I note that some of the steps were incorrect.The output was the following:
root@mtcdt:/opt/lora# /etc/init.d/lora-packet-forwarder start Found lora card MTAC-LORA-868 Starting lora-packet-forwarder: OK
The pid file is present, but the process is not running.
I started to debug this by running the program manually.
root@mtcdt:/opt/lora# ./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 867500000, RSSI offset -165.000000, tx enabled 1, tx_notch_freq 0 lgw_rxrf_setconf:446: WARNING: NOT A VALID TX NOTCH FILTER FREQUENCY [126000..250000]Hz lgw_rxrf_setconf:458: Note: rf_chain 0 configuration; en:1 freq:867500000 rssi_offset:-165.000000 radio_type:2 tx_enable:1 tx_notch_freq:0 INFO: radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -165.000000, tx enabled 0, tx_notch_freq 0 lgw_rxrf_setconf:458: Note: rf_chain 1 configuration; en:1 freq:868500000 rssi_offset:-165.000000 radio_type:2 tx_enable:0 tx_notch_freq:0 INFO: Lora multi-SF channel 0> radio 1, 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 1, 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 1, 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 -400000 Hz, 125 kHz bw, SF 7 to 12 lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 3 configuration; en:1 freq:-400000 SF_mask:0x7e INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12 lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 4 configuration; en:1 freq:-200000 SF_mask:0x7e INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12 lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 5 configuration; en:1 freq:0 SF_mask:0x7e INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12 lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 6 configuration; en:1 freq:200000 SF_mask:0x7e INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12 lgw_rxif_setconf:577: Note: LoRa 'multi' if_chain 7 configuration; en:1 freq:400000 SF_mask:0x7e INFO: Lora std channel> radio 1, 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 1, 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 AA555A0000000000 INFO: server hostname or IP address is configured to "192.168.63.10" INFO: upstream port is configured to "1784" INFO: downstream port is configured to "1786" INFO: downstream keep-alive interval is configured to 10 seconds INFO: statistics display interval is configured to 30 seconds INFO: upstream PUSH_DATA time-out is configured to 100 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 ERROR: FAIL TO CONNECT BOARD ERROR: [main] failed to start the concentrator root@mtcdt:/opt/lora#
I’ve already gone through a lot of forum topics and issues, but they were mostly related to GPS or cellular modules which I don’t have.
The lora-network-server seemed to work properly before I started to reconfigure it.
My hardware configuration is the following:
– Multitech MultiConnect Conduit (MTCDTIP-220L-868-OP)
– 553/686 Lora module
– Ethernet moduleThanks in advanced,
MátéAugust 14, 2017 at 9:45 am #20610Jason ReissKeymaster$ mts-io-sysfs show lora/product-id
MTAC-LORA-868
$ mts-io-sysfs show lora/hw-version
MTAC-LORA-1.0This card is a USB card and must use the /opt/lora/basic_pkt_fwd or gps_pkt_fwd binaries.
v3.x packet forwarder with V2 protocol is not available for USB cards.
V1 protocol is used in basic/gps pkt_fwdsAugust 14, 2017 at 9:52 am #20611Máté EcklParticipantI do not now and ever have had basic_pkt_fwd on my install. I thought it to be a mistake in the manual.
Could you tell me the name of the package from which I can install this executable?
August 14, 2017 at 9:58 am #20612Jason ReissKeymastermLinux lora recipes
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/loraSee lora-packet-forwarder-usb
Pre-built packages, match your mLinux version.
http://www.multitech.net/mlinux/feeds/3.3.7/arm926ejste/lora-packet-forwarder-usb_1.4.1-r10.0_arm926ejste.ipkAugust 15, 2017 at 2:47 am #20650Máté EcklParticipantThank you very much, it seems to be working fine.
-
AuthorPosts
- You must be logged in to reply to this topic.