Hi,
I followed the instruction here: MultiTech Conduit Configure AEP model and successfully connected the Conduit to TTN Gateway.However, when i try to use LoRa demo on mDot Box, it shows ‘joining’ and doesn’t have any connection.
So i’m wondering could there be any problem with the TTN packet forwarder?
I’m new to LoRa network so let me know if you need more information.
Thanks.
Bill
Check the TTN console for the gateway to check i you are seeing any traffic. If there is traffic on that page, switch to the application and check for traffic there as well.
Check both show traffic (and the gateway traffic shows two colors lightning symbols). If it does we’ll go from there…
There is no traffic shown on the gateway… I checked it the first time I installed the ttn-pkt-forwarder and nothing showed up on traffic. I thought it was because i didn’t turn on the mDot box but when i use the mDOt box, they aren’t been able to connect…
Bill
Where on the globe are you located? Which frequency plan are you using?
LoRaWAN <> WiFi. Nodes do not connect to a gateway. Nodes transmit and any and all gateways within RF reach will get the data. If the CRC is valid the gateway will forward it to the back-end, in your case TTN. Check /var/log/lora-pkt-fwd.log to check the statistics and see if there are any percentages <> 0 in the line:
# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
I’m in Pennsylvania, US. The frequency is US915.
Is your mDot set to use sub-band 1?
Yes, the sub-band is 1.
I’m not sure which command i should use. But here is the result i got…
admin@mtcdt:~# tail /var/log/lora-pkt-fwd.log
15:19:28 INFO: Ghoststream data is disabled
15:19:28 INFO: Radiostream data is enabled
15:19:28 INFO: Statusstream data is enabled
15:19:28 INFO: Beacon is disabled
15:19:28 INFO: Packet logger is disabled
15:19:28 INFO: Flush output after statistic is disabled
15:19:28 INFO: Flush after each line of output is disabled
15:19:28 INFO: Watchdog is disabled
15:19:28 INFO: Contact email configured to "yc013@bucknell.edu"
15:19:28 INFO: Description configured to "Starter"There should be a lot more output after those lines. Use ‘tail -f’ and keep the gateway running for some time. Look for a line with the text ‘INFO: [main] Starting the concentrator’ followed by ‘INFO: [main] concentrator started, radio packets can now be received.’.
Here’s the output:
15:52:26 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)
15:52:28 *** Multi Protocol Packet Forwarder for Lora Gateway ***
Version: 3.0.20Again, there should be a lot more output. Have you spotted the lines I quoted in my previous message in the output?
Sorry for the wrong codes and the late reply. The results are zero. Here’s the code:
##### 2018-06-27 14:01:07 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 0 (0 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 0 (0.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: 0.00%.
### [ CONNECTIONS ] ###
# bridge.us-west.thethings.network: Connected
# Semtech status report send.
##### END #####That is encouraging as it shows the packet forwarder is running correctly.
If both node and gateway are using the same frequencies (sub band 1 == channels 8-15) you should see percentages <> 0.00% when the node is sending data.
Can you post the output of ‘ps ax’?
Good to hear the connection is successful.
Here’s the output:
PID TTY STAT TIME COMMAND
1 ? Ss 0:06 init [5]
2 ? S 0:00 [kthreadd]
3 ? S 0:01 [ksoftirqd/0]
5 ? S< 0:00 [kworker/0:0H]
6 ? S 0:00 [kworker/u2:0]
7 ? S 0:01 [rcu_preempt]
8 ? S 0:00 [rcu_bh]
9 ? S 0:00 [rcu_sched]
10 ? S< 0:00 [khelper]
11 ? S 0:00 [kdevtmpfs]
12 ? S< 0:00 [writeback]
13 ? S< 0:00 [bioset]
14 ? S< 0:00 [crypto]
15 ? S< 0:00 [kblockd]
16 ? S 0:00 [khubd]
17 ? S 0:00 [kworker/u2:1]
27 ? S< 0:00 [rpciod]
28 ? S 0:00 [khungtaskd]
29 ? S 0:00 [kswapd0]
30 ? S 0:00 [fsnotify_mark]
31 ? S< 0:00 [nfsiod]
32 ? S< 0:00 [cifsiod]
65 ? S< 0:00 [deferwq]
77 ? SN 0:00 [jffs2_gcd_mtd6]
87 ? Ss 0:00 /lib/udev/udevd -d
170 ? S 0:00 /lib/udev/udevd -d
197 ? S 0:00 /lib/udev/udevd -d
253 ? SN 0:07 [jffs2_gcd_mtd8]
407 ? Ss 0:00 /usr/bin/dbus-daemon --system
428 ? S 0:00 /sbin/klogd -n
729 ? S 0:00 /sbin/lighttpd-angel /usr/sbin/lighttpd -D -f /etc/li
730 ? S 0:09 /usr/sbin/lighttpd -D -f /etc/lighttpd.conf
732 ? S 0:01 /usr/sbin/lighttpd -f /etc/lighttpd_nrs.conf
735 ? Sl 1:41 /usr/bin/rcell_api -d /var/config/db.json
796 ? S 0:01 /sbin/syslogd -n -l 7 -O /var/log/messages -s 512 -b
812 ? S 0:28 /usr/sbin/mosquitto -d -c /etc/mosquitto/mosquitto.co
1765 ? Ss 0:00 udhcpc -i eth0 -p /var/run/udhcpc_eth0.pid
1917 ? Ss 0:00 /usr/sbin/sshd
2048 ? S 0:00 dnsmasq --conf-file=/var/run/dnsmasq_dns.conf --pid-f
2187 ? Ss 0:10 /sbin/smsd
2200 ? Ss 0:01 /usr/sbin/crond
2203 ? Ssl 0:25 /sbin/wan-manager
2204 ? S 0:56 /bin/bash /sbin/led_cd_ss
2214 ? S 0:00 /bin/bash /sbin/monitor-annexcd
2327 ? Sl 0:27 annexcd --account-key DEB686A7-D1A3-4CAF-9F24-E8D7B79
2535 ? S 0:00 /sbin/node-angel /bin/bash -c exec /usr/bin/node --ma
2536 ? Sl 1:29 node-red
2591 ? Ss 0:00 stunnel /etc/stunnel.conf
2643 ? S 0:00 /bin/bash /opt/lora/run_forwarder
2659 ttyS0 Ss+ 0:00 /sbin/getty 115200 ttyS0
2660 ttyGS0 Ss+ 0:00 /sbin/getty 115200 ttyGS0
2674 ? Sl 45:37 /opt/lora/mp_pkt_fwd -c /var/config/lora -l /var/log/
2707 ? S 0:01 watchdog --device /dev/watchdog --ppp
7447 ? S 0:00 [kworker/0:1]
9132 ? S 0:00 [kworker/0:2]
9235 ? Ss 0:00 sshd: admin@pts/0
9239 pts/0 Ss 0:00 -bash
9247 ? S 0:00 sleep 4
9248 pts/0 R+ 0:00 ps ax
31922 ? S 0:00 [kworker/0:0]Everything looks alright. Do you keep sufficient distance between the node and the gateway while testing? At least 7 feet?
Does the gateway have an antenna connected to the reverse SMA connector on the LoRaWAN card? (Not the cellular antenna on the main chassis, the connector on the inserted card)
Is this a ‘recent’ gateway or one that has been purchased some years ago? I’m asking because MultiTech had some issues with the LoRa cards at some point a few years ago where the range of the gateway suffered and was only a few feet.
The mDot box may be set to private sync word by default.
Connect to command console and issue
AT+PN=1
AT&W
http://www.multitech.net/developer/products/multiconnect-dot-series/multiconnect-mdot-box-and-evb/
Hi Kersing,
Are you saying that after installing your packet forwarder, the lora network should still be able to connect?
I made some progress these days:
However, they have only activation data file on the application console. There’s no other uplink or downlink data file shown.
I haven’t set up any flows on the Conduit node-red (I’m not sure how to). But when I tried to install the ttn nodes it shows:
npm WARN package.json mts-gpio@ No repository field.
npm WARN package.json mts-gpio@ No README data
npm WARN package.json mts-mcard@ No description
npm WARN package.json mts-mcard@ No repository field.
npm WARN package.json mts-mcard@ No README data
npm WARN package.json mts-serial@ No description
npm WARN package.json mts-serial@ No repository field.
npm WARN package.json mts-serial@ No README data
npm ERR! not a package /tmp/npm-13400-6z8QQDGg/github.com/thethingsnetwork/api
npm ERR! Error: ENOENT, open '/tmp/npm-13400-6z8QQDGg/github.com/thethingsnetwork/api-unpack/package.json'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Linux 3.12.27r13
npm ERR! command "node" "/usr/bin/npm" "install" "node-red-contrib-ttn"
npm ERR! cwd /opt/node-red
npm ERR! node -v v0.10.40
npm ERR! npm -v 1.4.28
npm ERR! path /tmp/npm-13400-6z8QQDGg/github.com/thethingsnetwork/api-unpack/package.json
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! not ok code 0
I don’t know what you are asking. If you are referring to the Lora network server on the conduit? That is not being used once you install MP forwarder. Neither is the MultiTech supplied packet forwarder. Using the setup pages for these components might result in MP forwarder not running correctly.
Regarding your node-red issue, did you bother to read the replies in Connecting the Multi tech gateway to things networks, your other thread? The TTN node will not work on the Conduits node-red.
Yes, that’s what i meant. I’m having trouble receving uplink or downlink. No data is passed from the end-device to TTN server.
I’ve read this one but someone from MultiTech support said i should install nodes. I don’t know what to do with it. Instead of installing the nodes, what nodes should i use to transfer the data?
Transfer from where to where?
Regarding the ‘missing’ data, did you check the antenna etc as I suggested?