Multilink Conduit install problems

Gateways MultiTech Gateways
1

Hi
I am trying to get a Multilink Conduit running on TTN. I did a return to factory on it and disabled the Multitech LoRa server.
I have installed the packet forwarder as per the instructions, run the installer etc but am not getting any connection on the TTN console.

After install I did a reboot but had to manually start it with:
/etc/init.d/ttn-pkt-forwarder start

I have listed the log: lora-pkt-fwd.log, and it ends with this:
… snip …
14:22:10 INFO: [Transports] Initializing protocol for 1 servers
14:22:11 INFO: [TTN] server “bridge.asia-se.thethings.network” connected
14:22:11 INFO: [main] Starting the concentrator
lgw_connect:532: INFO: no FPGA detected or version not supported (v103)
Note: success connecting the concentrator
lgw_setup_sx125x:407: Note: SX125x #0 version register returned 0x21
lgw_setup_sx125x:412: Note: SX125x #0 clock output enabled
lgw_setup_sx125x:469: Note: SX125x #0 PLL start (attempt 1)
lgw_setup_sx125x:407: Note: SX125x #1 version register returned 0x21
lgw_setup_sx125x:415: Note: SX125x #1 clock output disabled
lgw_setup_sx125x:469: Note: SX125x #1 PLL start (attempt 1)
ERROR: lbt_setup() did not return SUCCESS
14:22:13 ERROR: [main] failed to start the concentrator

This looks like there is a version issue ?

I can ping google.com from the command prompt by the way so have network connectivity.

I am running a MTCDT-210A Firmware1.4.1, with the older non SPI LoRa card. Is this a problem ?

Thanks
Guy

2

What frequency plan have you selected in the TTN console? Does that frequency plan require Listen Before Talk (LBT)? If so the older hardware does not support that and will not run.

1 Like
3

It is AS923 923-928 MHz (Asia.2)

4

That config (see my second question) uses LBT. Your hardware does not support LBT so it will not run. You need the newer SPI based LoRaWAN card for this frequency plan.

5

OK, thanks Jac. I was not aware LBT was in the LoRaWAN standard.

I guess an SPI card is on the shopping list.

6

@kersing Hi Jac. I notice that even with an SPI card we need to turn off LBT in global_conf, or we’ll get

ERROR: lbt_setup() did not return SUCCESS
14:22:13 ERROR: [main] failed to start the concentrator

In Australia, this is OK as we don’t need to run LBT (although it would be good). But I guess the question is, can we still use gateways with the USB LoRa card for AS923, or must it be the SPI card?

7

Hi Andrew,

I just received my gateway: MuliConnect Conduit MTCDT with MTAC-LORA-H-915 (SPI) and tried to setup the TTN packet forwarder on AS923.
It still doesn’t work as the TTN service fetch the TTN configuration from /var/config/lora/global_conf_src which point to:
https://account.thethingsnetwork.org/api/v2/frequency-plans/AS_923_925
or
https://account.thethingsnetwork.org/api/v2/frequency-plans/AS_920_923
Both these configs have lbt “enable”.

Is there an official TTN and clean way to disable the lbt? Eg: point to an TTN or Meshed config?
I could hack the scr file and disable lbt setting but this doesn’t seen very clean in case the other parameters change in the future.

Note: AU915 mode is working fine.

8

Quick update, AS923 is now working, I had to remove the lbt parameters from the global_conf_src and host the customised files on my own website: https://brizeconsulting.com.au/lorawan
Not super clean but this work so far.

Is there an AS923 Meshed or TTN configuration source (global_conf_src) for Australia?
Something that will be updated by official TTN partners?

9

As @brice mentions the TTN configuration file contains LBT setup for AS923. With the configuration set for LBT the hardware needs to support it. The USB card does not do LBT so it will not work if LBT is enabled. If you disable LBT anyway you can safely use the USB card.

BTW The MultiTech site suggests LBT is available, at least for some cards. Can someone with an MTAC-LORA-H-915 card post (or mail) a full startup log of the packet forwarder?

10

@kersing Happy to run a full startup log. Can you please let me know how to activate the full logging of the pack forwarder? (Sorry, I am just starting on TTN).

11

I did disable LBT and the packet forwarder did not start with a USB card. Similar log output as before.

lgw_connect:532: INFO: no FPGA detected or version not supported (v103)

I will try again when I have a chance to get the SPI version

12

@Guy
Could you provide more logging? This line by itself is not sufficient to determine why it won’t start.

(I’ve got the software running and in my logging there is lgw_connect:532: INFO: no FPGA detected or version not supported (v103) as well)

13

Full log should be available at /var/log/lora-pkt-fwd.log If you stop the packet forwarder (run /etc/init.d/ttn-pkt-forwarder stop) and start the software by hand with /opt/lora/mp_pkt_fwd -c /var/config/lora the log will be shown on your ‘terminal’.

14

Hi Jac

It works now. I upgraded the Multitech (with USB LoRa card) to version 1.4.16, went through the install process again, then (on Andrew’s advice)

  • Stopped the packet forwarder with /etc/init.d/ttn-pkt-forwarder stop
  • Patched out the code in /opt/lora/run_forwarder that pulls the latest global_conf file.
  • Edited the /var/config/lora/global_conf.json and changed it to set lbt_cfg : {“enable”:false, …}
  • Restarted the packet forwarder

It connected and is forwarding packets.

Don’t know what is different now other than upgrading from 1.4.1 to 1.4.16. Sometimes you just need to install - reset - install - reset 5 times to get it right :wink:

Thanks for your help.

1 Like
15

Here the log of the TTN packet forwarder with LBT on (config pointed to https://account.thethingsnetwork.org/api/v2/frequency-plans/AS_923_925)

admin@mtcdt:/var/config/lora# uname -a
Linux mtcdt 3.12.27r15 #1 PREEMPT Thu Mar 29 09:32:23 CDT 2018 armv5tejl GNU/Linux
admin@mtcdt:~# /opt/lora/mp_pkt_fwd -c /var/config/lora
17:48:33  *** Multi Protocol Packet Forwarder for Lora Gateway ***
Version: 3.0.20
17:48:33  *** Lora concentrator HAL library version info ***
Version: 5.0.1; Options: native;
***
17:48:33  INFO: Little endian host
17:48:33  INFO: found global configuration file /var/config/lora/global_conf.json, parsing it
17:48:33  INFO: /var/config/lora/global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
17:48:33  INFO: lorawan_public 1, clksrc 0
lgw_board_setconf:437: Note: board configuration; lorawan_public:1, clksrc:0
17:48:33  INFO: 8 LBT channels configured
17:48:33  INFO: antenna_gain 0 dBi
17:48:33  INFO: Configuring TX LUT with 16 indexes
17:48:33  INFO: radio 0 enabled (type SX1257), center frequency 923600000, RSSI offset -166.000000, tx enabled 1
lgw_rxrf_setconf:486: WARNING: NOT A VALID TX NOTCH FILTER FREQUENCY [126000..250000]Hz
lgw_rxrf_setconf:498: Note: rf_chain 0 configuration; en:1 freq:923600000 rssi_offset:-166.000000 radio_type:2 tx_enable:1 tx_notch_freq:0
17:48:33  INFO: radio 1 enabled (type SX1257), center frequency 924600000, RSSI offset -166.000000, tx enabled 0
lgw_rxrf_setconf:498: Note: rf_chain 1 configuration; en:1 freq:924600000 rssi_offset:-166.000000 radio_type:2 tx_enable:0 tx_notch_freq:0
17:48:33  INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 0 configuration; en:1 freq:-400000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 1 configuration; en:1 freq:-200000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 2 configuration; en:1 freq:0 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 3 configuration; en:1 freq:200000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 4>  radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 4 configuration; en:1 freq:400000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 5>  radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 5 configuration; en:1 freq:-400000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 6>  radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 6 configuration; en:1 freq:-200000 SF_mask:0x7e
17:48:33  INFO: Lora multi-SF channel 7>  radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12
lgw_rxif_setconf:617: Note: LoRa 'multi' if_chain 7 configuration; en:1 freq:0 SF_mask:0x7e
17:48:33  INFO: Lora std channel> radio 1, IF -100000 Hz, 250000 Hz bw, SF 7
lgw_rxif_setconf:591: Note: LoRa 'std' if_chain 8 configuration; en:1 freq:-100000 bw:2 dr:2
17:48:33  INFO: FSK channel> radio 1, IF 200000 Hz, 125000 Hz bw, 50000 bps datarate
lgw_rxif_setconf:647: Note: FSK if_chain 9 configuration; en:1 freq:200000 bw:3 dr:50000 (50000 real dr) sync:0xC194C1
17:48:33  INFO: /var/config/lora/global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
17:48:33  INFO: Found 1 servers in array.
17:48:33  INFO: Server 0 configured to "router.as2.thethings.network"
17:48:33  INFO: packets received with a valid CRC will be forwarded
17:48:33  INFO: packets received with a CRC error will NOT be forwarded
17:48:33  INFO: packets received with no CRC will NOT be forwarded
17:48:33  INFO: GPS is disabled
17:48:33  INFO: Upstream data is enabled
17:48:33  INFO: Downstream data is enabled
17:48:33  INFO: Ghoststream data is disabled
17:48:33  INFO: Radiostream data is enabled
17:48:33  INFO: Statusstream data is enabled
17:48:33  INFO: Beacon is disabled
17:48:33  INFO: Packet logger is disabled
17:48:33  INFO: Flush output after statistic is disabled
17:48:33  INFO: Flush after each line of output is disabled
17:48:33  INFO: Watchdog is disabled
17:48:33  INFO: found local configuration file /var/config/lora/local_conf.json, parsing it
17:48:33  INFO: redefined parameters will overwrite global parameters
17:48:33  INFO: /var/config/lora/local_conf.json does not contain a JSON object named SX1301_conf
17:48:33  INFO: /var/config/lora/local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
17:48:33  INFO: gateway MAC address is configured to 00800000A000291B
17:48:33  INFO: Found 1 servers in array.
17:48:33  INFO: Server 0 configured to "thethings.meshed.com.au"
17:48:33  INFO: packets received with a valid CRC will be forwarded
17:48:33  INFO: packets received with a CRC error will NOT be forwarded
17:48:33  INFO: packets received with no CRC will NOT be forwarded
17:48:33  INFO: GPS is disabled
17:48:33  INFO: Upstream data is enabled
17:48:33  INFO: Downstream data is enabled
17:48:33  INFO: Ghoststream data is disabled
17:48:33  INFO: Radiostream data is enabled
17:48:33  INFO: Statusstream data is enabled
17:48:33  INFO: Beacon is disabled
17:48:33  INFO: Packet logger is disabled
17:48:33  INFO: Flush output after statistic is disabled
17:48:33  INFO: Flush after each line of output is disabled
17:48:33  INFO: Watchdog is disabled
17:48:33  INFO: Contact email configured to "<removed>"
17:48:33  INFO: Description configured to "Brize Consulting Chatswood Epica"
17:48:33  INFO: [Transports] Initializing protocol for 1 servers
17:48:34  INFO: [TTN] server "thethings.meshed.com.au" connected
17:48:34  INFO: [main] Starting the concentrator
INFO: FPGA supported features: [TX filter]  [Spectral Scan] 
ERROR: lbt_setup() did not return SUCCESS
17:48:35  ERROR: [main] failed to start the concentrator
admin@mtcdt:~#
16

Hi @Guy , can you check that downlink packets are working reliably for you with AS923 on a USB LoRa card.

17

Seems to be working properly.

It was running OK overnight with one device connected. Interestingly the gateway reported packets going to my Kerlink on Thingpark, but did not forward them.

I just moved the gateway onto the roof with a short feeder onto a big Taoglas antenna.

I also note that ADR does not seem to be enabled for AS923 on TTN.

18

Further to this, there is something weird going on.

I have some devices connected to Thingpark via a Kerlink. They have different AppEUIs, AppKeys and of course DevEUIs.

The TTN gateway sporadically seems to pick up some of these packets. Not every one, but maybe one in every 5. It then forwards them on and then drops them. This is from the Gateway Traffic log (on the website):

0msbridge br-asia-se1 receive backend:mqtt
0.05msbridge br-asia-se1 forward backend:ttn
0.88msrouter ttn-router-asia-se receive gateway:pennywest
1.2msrouter ttn-router-asia-se build downlink options:2
2.01msrouter ttn-router-asia-se drop reason:no brokers

Is this expected behaviour ?

19

This line says it all. If LBT is supported this line should also contain [LBT].
It is a shame the current code does not print the FPGA version information, that might change in the future.

Yes. The gateway does not filter anything so all received LoRaWAN packets (without checksum errors) will be forwarded.

20

Hi @kersing

Checking the LORA card specs installed, it does support LBT

admin@mtcdt:/opt/lora# mts-io-sysfs show lora/product-id
MTAC-LORA-H-915
admin@mtcdt:/opt/lora# mts-io-sysfs show lora/device-id
19646858
admin@mtcdt:/opt/lora# mts-io-sysfs show lora/eui
00:80:00:00:A0:00:29:1B

There is a note regarding Recipes and Patches to support FPGA .31:


"Contact your third party packet forwarder provider to verify they have the latest release that
supports the MTAC-LORA-H with FPGA .31"

Should I apply these Patches?

Also, I am bit confused about the LoRa packet forwarder.
Can I manage it from the Conduit GUI? Or only from command line?
05