There are two SX1257s, both need to be enabled and set to a certain centre frequency. Next for each frequency we want to use the radio and the frequency offset need to be specified.
Any specific configuration lines you want explained? (See TTN github repo for configurations with comments added)
Hi Kersing,
Tkx for your answer.
The thing I don’t understand is (for exemple) how to configure the channels for USA 915?
In theory we have 63 channels but the SX1301 can only demodulate 8channels so is that means that I only need to add 8 channels in the global_conf ? Or I can add more to avoid collision ?
The last thing is about the tx_lut ? what does it means ?
Thanks for everything
For the US 915 band you need a special gateway 64ch with 8x SX1301, Senet has it.
Or you can use a normal 8ch gateway with 1x SX1301 in HYBRID but you have to configure gateways and nodes to use only 1 of the 8 sub-bands.
tx_lut are calibration values not very important, they don’t affect to performance, are just to calibrate RSSI values
Thank you for the explanation nestorayuso.
Someone has a link to download the new RN2903 firmware ? Both RN2483 and RN2903 (0.9.5) have a huge bug with updating frame counters so I want to put the RN2903 with a new firmware.
If you have a link like the RN2483 I’m waiting for it pleaaaasseee.
Thx
I am not doubting you, but where can I read up on this bug?
Thanks.
Hi terrence,
When you send a set uplink counter command the module returns OK but when you read back the counter the value has not been updated.
Start module
Send : mac set upctr 12
Receive : ok
But when you send a frame the sequence number is not 12.
This bug has been seen on every rn2483 0.9.5 and rn2903 0.9.5
@kersing Hi Jac are you going/willing to provide an ipk package for the latest version of the Packet forwarder? would be great to experiment with a private backend.
Sorry, no, I will not be attempting to build the newest software for MultiTech conduits, the reason:
v2.2.0 - 2015-10-08
Removed FTDI support in makefiles to align with HAL v3.2.0.
As the MultiTech gateways are FTDI based it won’t be possible to run the newest versions of the HAL and packet forwarder on them. The new software requires SPI communications to meet timing requirements.
Ok thanks for the info. Does that mean the Multitech conduit hardware is obsolete with regards to the development of the packet forwarder? In other words, why buy this gateway if it won’t support future functionality/requirements?
I’m at the same point, lora-pkt-pwd is running and registering to TTN. But the Lora server did not.
I want to join my mDot. Any suggestions?
I am working with MULTITECH’s “MultiConnect Conduit IoT Starter Kit for LoRa Technology”. I have been able to connect to TTN by following the guide: https://www.thethingsnetwork.org/docs/gateways/multitech/aep.html
I have the following queries:
The kit comes with an mDot box node and it has stopped connecting to the Lora signal. It only connects when from mLinux I launch the lora-network-server but this causes my gateway to stop connecting to TTN.
So, when I run ttn-pkt-forwarder does the Lora Radio service launch? When I used the command sh installer.sh will the packet forwader and the server be installed?
MDot box firmware does not support ttn-packet-forwarder? I just want the mdot to detect the radio signal.
I haven’t used my gateway in awhile. Sorry.
Have you configured the mDot to use the TTN keys and frequencies?
The ttn-pkt-forwarders interfaces between the conduit radio and the network forwarding all valid LoRaWAN packets to TTN. No additional software in the conduit is required.
I’ll be working on it, thank you so much.
Let’s Keep in touch.
Hello,
I have problem with Multitech gateway. I’m using ttn-pkt-forwarder with 2 uplink servers. One is for our private purposes, connected via semtech protocol. Second is for ttn network. Uplink messages is fully functional to both servers. Problem is with downlink messages. These messages are not sent to nodes. Messages have arrived to gateway, but ther are not sent to nodes.
There is a log from gateay:
lgw_receive:1165: FIFO content: 1 10 0 5 13
lgw_receive:1184: [2 17]
Note: LoRa packet
Info: packet will be sent without CRC
INFO: Enabling TX notch filter
59.20.0.0.9b.ee.8f.9.0.1c.c.1c.0.8.0.0.60.11.1b.1.26.20.5e.1.87.84.5e.74.end
lgw_receive:1165: FIFO content: 1 33 0 5 13
lgw_receive:1184: [1 17]
Note: LoRa packet
Info: packet will be sent without CRC
INFO: Enabling TX notch filter
59.13.33.0.f7.77.47.9.0.1c.c.1c.0.8.0.0.60.11.1b.1.26.20.5f.1.b6.c9.c6.af.end
When I used default lora-packet-forwarder, downlink messages are fully functional, but there is a limitation to one network server, so I cannot expand my gateway to ttn network. Can you tell me, where can be a problem?
Thank you.
The log you are showing does not contain any downlink message, just uplink. Is the gateway receiving downlink data?
Hello, yes, gateway is receiving downlink data. There is more info from log:
lgw_receive:1165: FIFO content: 1 eb 3 5 19
lgw_receive:1184: [5 17]
Note: LoRa packet
lgw_receive:1165: FIFO content: 1 14 0 7 14
lgw_receive:1184: [2 17]
Note: LoRa packet
lgw_receive:1165: FIFO content: 1 38 0 7 13
lgw_receive:1184: [0 17]
Note: LoRa packet
lgw_receive:1165: FIFO content: 1 5b 0 7 16
lgw_receive:1184: [2 17]
Note: LoRa packet
lgw_receive:1165: FIFO content: 1 81 0 5 19
lgw_receive:1184: [4 17]
Note: LoRa packet
lgw_receive:1165: FIFO content: 1 aa 0 5 13
lgw_receive:1184: [0 17]
Note: LoRa packet
Info: packet will be sent without CRC
INFO: Enabling TX notch filter
59.6.66.6.f2.c1.87.9.0.1c.c.1c.0.8.0.0.60.11.1b.1.26.20.66.1.f6.ca.b8.81.end
lgw_receive:1165: FIFO content: 1 cd 0 5 13
lgw_receive:1184: [1 17]
Note: LoRa packet
##### 2017-12-20 12:54:52 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 10
# CRC_OK: 80.00%, CRC_FAIL: 20.00%, NO_CRC: 0.00%
# RF packets forwarded: 8 (201 bytes)
# PUSH_DATA datagrams sent: 9 (2129 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### BEACON IS DISABLED!
### [JIT] ###
# INFO: JIT queue contains 0 packets.
# INFO: JIT queue contains 0 beacons.
### GPS IS DISABLED!
### [PERFORMANCE] ###
# Upstream radio packet quality: 80.00%.
# Upstream datagram acknowledgment quality for server "home.jump-soft.com" is 100.00%.
# Downstream heart beat acknowledgment quality for server "home.jump-soft.com" is 100.00%.
# Downstream datagram content quality for server "home.jump-soft.com" is 0.00%.
# Downstream radio transmission quality for server "home.jump-soft.com" is 100.00%.
# Semtech status report send.
##### END #####
##### 2017-12-20 12:55:22 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 5
# CRC_OK: 80.00%, CRC_FAIL: 20.00%, NO_CRC: 0.00%
# RF packets forwarded: 4 (96 bytes)
# PUSH_DATA datagrams sent: 5 (1165 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### BEACON IS DISABLED!
### [JIT] ###
# INFO: JIT queue contains 0 packets.
# INFO: JIT queue contains 0 beacons.
### GPS IS DISABLED!
### [PERFORMANCE] ###
# Upstream radio packet quality: 80.00%.
# Upstream datagram acknowledgment quality for server "home.jump-soft.com" is 100.00%.
# Downstream heart beat acknowledgment quality for server "home.jump-soft.com" is 100.00%.
# Downstream datagram content quality for server "home.jump-soft.com" is 0.00%.
# Downstream radio transmission quality for server "home.jump-soft.com" is 100.00%.
# Semtech status report send.
##### END #####
INFO: tx_start_delay=1493 (1493.562500) - (1497, bw_delay=1.500000, notch_delay=1.937500)
13:55:52 INFO: Disabling GPS mode for concentrator's counter...
13:55:52 INFO: host/sx1301 time offset=(1513774429s:741029µs) - drift=-28µs
13:55:52 INFO: Enabling GPS mode for concentrator's counter.
Info: packet will be sent without CRC
INFO: Enabling TX notch filter
59.13.33.7.4e.50.5f.9.0.1c.c.1c.0.8.0.0.60.11.1b.1.26.20.67.1.4.67.e0.8a.end
lgw_receive:1165: FIFO content: 1 f0 0 5 13
lgw_receive:1184: [0 17]
Note: LoRa packetAnd there is a tcpdump communication:
root@mtcdt:~# tcpdump -i any port 1700i
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
13:53:52.171425 IP 10.202.3.10.52582 > lora_server1700: UDP, length 12
13:53:52.174004 IP lora_server1700 > 10.202.3.10.52582: UDP, length 4
13:53:56.763379 IP 10.202.3.10.50524 > lora_server1700: UDP, length 230
13:53:56.766245 IP lora_server1700 > 10.202.3.10.50524: UDP, length 4
13:53:57.079007 IP lora_server1700 > 10.202.3.10.52582: UDP, length 168
13:53:57.080646 IP 10.202.3.10.52582 > lora_server1700: UDP, length 12
13:54:02.271861 IP 10.202.3.10.52582 > lora_server1700: UDP, length 12
13:54:02.274458 IP lora_server1700 > 10.202.3.10.52582: UDP, length 4
13:54:03.759242 IP 10.202.3.10.50524 > lora_server1700: UDP, length 231
13:54:03.761959 IP lora_server1700 > 10.202.3.10.50524: UDP, length 4
13:54:04.075545 IP lora_server1700 > 10.202.3.10.52582: UDP, length 169
13:54:04.076596 IP 10.202.3.10.52582 > lora_server1700: UDP, length 12
13:54:08.760092 IP 10.202.3.10.50524 > lora_server1700: UDP, length 231
13:54:08.762751 IP lora_server1700 > 10.202.3.10.50524: UDP, length 4
13:54:09.074455 IP lora_server1700 > 10.202.3.10.52582: UDP, length 169
13:54:09.075512 IP 10.202.3.10.52582 > lora_server1700: UDP, length 12Thank you.
Please learn how to format forum messages so people can read them. Do not just dump a lot of text in a message and expect us to sort it out.
Your gateway is not receiving any downlink data (at least not in this partial log). Just uplink (node to back-end) traffic which is forwarded according to the log. If you are receiving downlink data (back-end to node) the counters in the [DOWNSTREAM] section (apart from PULL_DATA which is just a heart beat) would be <> 0.
Hello, sorry for previous format of my message. My mistake.
In DOWNSTREAM section is PULL_DATA sent:3 , so this is data which network server want to send to end node,or not?
My end device is Adeunis RF field tester. If I send data through basic multitech lora-packet forwarder, I got ack back to Adeunis tester. Buf If I send data throuth ttn-pkt-forwarder, I never got ack back to Adeunis tester. Configuration of multitech gateway for both packet forwarders is the same.
There is a log from basic lora packet forwarder from multitech:
root@mtcdt:/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 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 00800000A0001B6D
INFO: server hostname or IP address is configured to "localhost"
INFO: upstream port is configured to "1680"
INFO: downstream port is configured to "1680"
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
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: server hostname or IP address is configured to "home.jump-soft.com"
INFO: upstream port is configured to "1700"
INFO: downstream port is configured to "1700"
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=(1513780985s:130772µs) - drift=-1713180908µs
INFO: Enabling GPS mode for concentrator's counter.
INFO: [down] PULL_ACK received in 2 ms
lgw_receive:1125: FIFO content: 1 39 0 5 c
lgw_receive:1144: [6 17]
Note: LoRa packet
INFO: Received pkt from mote: EB001043 (fcnt=15081)
JSON up: {"rxpk":[{"tmst":3716452,"chan":6,"rfch":0,"freq":867.700000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":-13.0,"rssi":-119,"size":12,"data":"YEMQAOsg6TrLBU2c"}]}
INFO: [up] PUSH_ACK received in 2 ms
lgw_receive:1125: FIFO content: 1 10 0 5 19
lgw_receive:1144: [7 17]
Note: LoRa packet
INFO: Received pkt from mote: EB001031 (fcnt=18537)
JSON up: {"rxpk":[{"tmst":3763180,"chan":7,"rfch":0,"freq":867.900000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":-17.0,"rssi":-118,"size":25,"data":"gDEQAOsAaUgC8GNbuGyqDkifdwUL+IK76w=="}]}
INFO: [up] PUSH_ACK received in 2 ms
lgw_receive:1125: FIFO content: 1 55 0 5 16
lgw_receive:1144: [2 17]
Note: LoRa packet
INFO: Received pkt from mote: A1010058 (fcnt=2861)
JSON up: {"rxpk":[{"tmst":5592268,"chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-3.5,"rssi":-110,"size":22,"data":"QFgAAaGALQsFSQVPBcwK+gUhGXxXEg=="}]}
INFO: [up] PUSH_ACK received in 3 ms
lgw_receive:1125: FIFO content: 1 7b 0 5 15
lgw_receive:1144: [1 17]
Note: LoRa packet
INFO: Received pkt from mote: 26011B11 (fcnt=6)
JSON up: {"rxpk":[{"tmst":9103028,"chan":1,"rfch":1,"freq":868.300000,"stat":1,"modu":"LORA","datr":"SF12BW125","codr":"4/5","lsnr":10.0,"rssi":-74,"size":21,"data":"gBEbASaABgABXji3vIhZhBaE7g4R"}]}
INFO: [up] PUSH_ACK received in 3 ms
INFO: [down] PULL_RESP received - token[0:0] :)
JSON down: {"txpk":{"imme":false,"tmst":10103028,"freq":868.3,"rfch":0,"powe":14,"modu":"LORA","datr":"SF12BW125","codr":"4/5","ipol":true,"size":12,"data":"YBEbASYg1QGkZnia"}}
59.13.33.0.9a.23.18.9.0.9c.c.18.0.8.0.0.60.11.1b.1.26.20.d5.1.a4.66.78.9a.end
INFO: [down] PULL_ACK received in 2 ms
lgw_receive:1125: FIFO content: 1 a0 0 7 e3
lgw_receive:1144: [7 17]
Note: LoRa packet
lgw_receive:1125: FIFO content: 1 93 1 5 14
lgw_receive:1144: [2 17]
Note: LoRa packet
INFO: Received pkt from mote: 070707A5 (fcnt=11878)
JSON up: {"rxpk":[{"tmst":19684644,"chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-12.8,"rssi":-118,"size":20,"data":"QKUHBweAZi4ITO+ef2sslI2FW+k="}]}
INFO: [up] PUSH_ACK received in 2 ms
INFO: [down] PULL_ACK received in 2 ms
##### 2017-12-20 14:43:37 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 6
# CRC_OK: 83.33%, CRC_FAIL: 16.67%, NO_CRC: 0.00%
# RF packets forwarded: 5 (100 bytes)
# PUSH_DATA datagrams sent: 5 (1013 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 1 (169 bytes)
# RF packets sent to concentrator: 1 (12 bytes)
# TX errors: 0
# TX rejected (collision packet): 0.00% (req:1, rej:0)
# TX rejected (collision beacon): 0.00% (req:1, rej:0)
# TX rejected (too late): 0.00% (req:1, rej:0)
# TX rejected (too early): 0.00% (req:1, rej:0)
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:448:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# GPS sync is disabled
##### END #####
Via this packet forwarder is ACK received successfully.