bridging multitech conduit with raspberry pi

[jessica perez]

Hello, so currently I am having an issue with the range of the pi. The mdot cannot join to the pi so my boss said to make it join the multitech conduit since the tx power is much higher than the pi, and have it send over the packets to the pi since we have our own server. How would i go about that? Would I need to just install the loragateway bridge on the conduit and then have the packetforwarder and lora server run on the pi? Anything will help thank you.

[Fernando Luis]

Hi Jessica,
Could you explain your problem in other words (or in spanish)?. I guess you have a MDOT connected to the Raspberry and want to connect to the Conduit but the concepts you use are really confusing.
Regards

[jessica perez]

Oh yea no worries, so the plan is to have the conduit be the gateway as well as setting it up as the packet forwarder. Then have it communicate with the raspberry pi 3 using mqtt broker. The raspberry pi 3 will have lora server, lora app server, and mqtt installed in order for that happen and once that packet gets to the pi, then have it send up our own server.

I followed the steps to set the lora gateway bridge and packet forwarder as instructed in this link https://www.loraserver.io/lora-gateway-bridge/install/gateway/multitech/

To make sure my packet forwarder is running I ran this command tcpdump -AUq -i lo port 1700
i get this

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes

while the output should be something like this
11:42:00.114726 IP localhost.34268 > localhost.1700: UDP, length 12
E..(..@.@.”…………….’…..UZ…..
11:42:00.130292 IP localhost.1700 > localhost.34268: UDP, length 4
E.. ..@.@.”…………………
11:42:10.204723 IP localhost.34268 > localhost.1700: UDP, length 12
E..(.&@.@………………’.x…UZ…..
11:42:10.206503 IP localhost.1700 > localhost.34268: UDP, length 4
E.. .’@.@………………..x..
11:42:10.968420 IP localhost.43827 > localhost.1700: UDP, length 113
E….h@.@…………3…y…….UZ…..{“stat”:{“time”:”2017-09-11 11:42:10 GMT”,”rxnb”:0,”rxok”:0,”rxfw”:0,”ackr”:100.0,”dwnb”:0,”txnb”:0}}
11:42:10.970702 IP localhost.1700 > localhost.43827: UDP, length 4
E.. .i@.@..b………..3……..
11:42:20.284752 IP localhost.34268 > localhost.1700: UDP, length 12
E..(..@.@………………’…..UZ…..
11:42:20.289256 IP localhost.1700 > localhost.34268: UDP, length 4
E.. ..@.@…………………..
11:42:30.364780 IP localhost.34268 > localhost.1700: UDP, length 12
E..( .@.@………………’.S7..UZ…..
11:42:30.366310 IP localhost.1700 > localhost.34268: UDP, length 4
E.. .@.@………………..S7.

now when i do this /basic_pkt_fwd-usb to see whats going in the packet forwarder i get this output

*** Basic Packet Forwarder for Lora Gateway ***
Version: 1.4.1
*** Lora concentrator HAL library version info ***
Version: 1.7.0; Options: ftdi sx1301 sx1257 full mtac-lora private;
***
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: radio 0 enabled, center frequency 902700000
lgw_rxrf_setconf:894: Note: rf_chain 0 configuration; en:1 freq:902700000
INFO: radio 1 enabled, center frequency 903500000
lgw_rxrf_setconf:894: Note: rf_chain 1 configuration; en:1 freq:903500000
INFO: Lora multi-SF channel 0> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: 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:998: 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:998: Note: LoRa ‘multi’ if_chain 2 configuration; en:1 freq:0 SF_mask:0x7e
INFO: Lora multi-SF channel 3> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 3 configuration; en:1 freq:200000 SF_mask:0x7e
INFO: Lora multi-SF channel 4> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 4 configuration; en:1 freq:-400000 SF_mask:0x7e
INFO: Lora multi-SF channel 5> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 5 configuration; en:1 freq:-200000 SF_mask:0x7e
INFO: Lora multi-SF channel 6> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 6 configuration; en:1 freq:0 SF_mask:0x7e
INFO: Lora multi-SF channel 7> radio 1, IF 200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:998: Note: LoRa ‘multi’ if_chain 7 configuration; en:1 freq:200000 SF_mask:0x7e
INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8
lgw_rxif_setconf:972: Note: LoRa ‘std’ if_chain 8 configuration; en:1 freq:300000 bw:1 dr:4
INFO: FSK channel 8 disabled
lgw_rxif_setconf:919: Note: if_chain 9 disabled
INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to 00800000A0000781
INFO: server hostname or IP address is configured to “localhost”
INFO: upstream port is configured to “1700”
INFO: downstream port is configured to “1700”
INFO: synch word is configured to 34
INFO: downstream keep-alive interval is configured to 12 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 be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: Auto-quit after 60 non-acknowledged PULL_DATA
INFO: found local configuration file local_conf.json, parsing it
INFO: redefined parameters will overwrite global parameters
INFO: local_conf.json does not contain a JSON object named SX1301_conf
INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to 00800000A0000781
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will be forwarded
INFO: packets received with no CRC will NOT be forwarded
ERROR: FAIL TO CONNECT BOARD
ERROR: [main] failed to start the concentrator

I checked my json files and I made sure the port was 1700 along with the correct gateway eui so i am unsure why it is failing to connect to the concentrator. I hope this is much clear.

• This reply was modified 5 years, 10 months ago by jessica perez.

[Jason Reiss]

What type of card do you have?

# mts-io-sysfs show lora/*

If it is MTAC-LORA-1.5 then the lora_pkt_fwd process should be used.
basic_pkt_fwd uses USB for MTAC-LORA-1.0

[jessica perez]

I ran that command and i got this
19045431
00:80:00:00:A0:00:07:81
MTAC-LORA-1.0
MTAC-LORA-915
1

My card should be MTAC-LORA-915 because when i type this command admin@mtcdt:~# mts-io-sysfs show lora/product-id
MTAC-LORA-915
i get that card . And on here https://www.loraserver.io/lora-gateway-bridge/install/gateway/multitech/ it says i should be using the web interface since my conduit mode is AEP. I installed the linux based packet forwarder then…Not sure how i go about that then to remove that packet forwarder

[Jason Reiss]

You can perform the firmware upgrade with AEP 1.4.16 image from downloads.
This will reset the firmware files to the correct packet forwarder.
After that you can use the GUI to configure the packet forwarder to point to an external network server.

[jessica perez]

Ok thank you! It is up and running now

[Author]

Posts