[jessica perez]

Hello Balint,
Not sure if you are still experiencing problems but the issue turned out that our gateway was not properly sealed, so water made its way in the gateway hardware unfortunately.

[jessica perez]

Yes, I will go on ahead and open an issue for the device behavior. Thank you.

[jessica perez]

Hi again, so i flashed the latest firmware to my conduit and it is still resetting back to its default settings.

These are the steps I did, after flashing to latest firmware, I went ahead and changed its ip address to a custom one. I was able to successfully log in back into the conduit with the custom ip address. Then I went to lora settings to change it to be packet forwarder mode.After doing so, i got a message saying they recommend to restart lora service which I did, as well as save and restart which I did as well. I noticed it was taking a while to respond, so eventually, the page refreshed itself with the message the site cannot be reached. As I suspected, gateway reset itself again.

So I decided to reflash firmware just in case, repeated the following steps above and again, gateway cant be reached anymore.

Any other thoughts as to why this could be happening would be appreciated. Thank you.

[jessica perez]

Oh ok that explains. I will be updating my firmware to 1.7.4. Thank you.

[jessica perez]

Yea it did not help, been testing it for a while. So I think we have decided to upgrade to a 1.5 SPI card instead. One more question(thank you btw for all your help much appreciated), if I were to upgrade to this card, it comes with the packet forwarder that implements the JIT queue system or I would have to install it manually?

[jessica perez]

Not sure if im looking at the right one, but from the lora server, the downlink data delay is set to 100ms

[jessica perez]

Besides the warning message, it might just be within our own water management system, but when I try to turn a valve on, it will turn on, but only for a minute then it will go off. Then 3-4 minutes later, it will go on again, and then it will shut down. So I figured based on the logs from the packet forwarder, it is most likely dropping packets and in the code if it loses contact with the server then the valves will shut off. It cannot be range issue because our system has worked before with the conduit set up as the network server and using node red.

From the lora server, i am getting uplinks and downlinks so at this point I am not sure what else could be a potential issue besides probably upgrading the lora card

[jessica perez]

I apologize for late response, so I ended up upgrading the packet-forwarder to latest version Lora Packet Forwarder USB 1.4.1-r11. I tried looking for info on this latest patch but no luck. Does this have the latest patch for the queue or do i need to manually configure it with the link you gave me?
Second, how will that patch work if my conduit is not linux based bc this link you mentioned http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora/lora-packet-forwarder-usb/lora-packet-forwarder-add-queue.patch?h=3 is for the linux based only? Or can it work with aep?

And as far as the other https://github.com/Lora-net/packet_forwarder you mentioned it is for MTAC-LORA-1.5 SPI? mine is not spi and is a MTAC-LORA-1.0

[jessica perez]

Ok thank you! It is up and running now

[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

[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.

[Author]

Posts