Set up RAK 7268 on LORIOT

I am having problems setting up two RAK 7268 gateways on loriot, I was told that the process would be the same as for the RAK 7258 gateway whereby I would access the gateway via SSH once it was set up with an LTE sim and access to my WIFI network and run the following code from LORIOT to install the relevant software:

cd /tmp

wget http://eu4pro.loriot.io/home/gwsw/loriot-rak-7249-SPI-0-latest.sh -O loriot-install.sh

chmod +x loriot-install.sh

./loriot-install.sh -f -s eu4pro.loriot.io

Then once that has installed, if it doesn’t connect that I should run this to disable other pre-installed packet forwarding that may conflict with LORIOT:

/etc/init.d/packet_forwarder disable ; /etc/init.d/loriot-gw enable ; reboot now

But, unlike my previous set up neither of the 7268 gateways I haven’t been successful with connecting them on LORIOT.

For your information, the output from the PS command in SSH is:

BusyBox v1.23.2 (2021-07-21 15:56:56 UTC) built-in shell (ash)


    LoRaWAN Gateway (WisGateOS 1.1.2_RAK 20210721)

[email protected]:~# ps
PID USER VSZ STAT COMMAND
1 root 1508 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
5 root 0 SW< [kworker/0:0H]
6 root 0 SW [kworker/u2:0]
7 root 0 SW< [khelper]
83 root 0 SW< [writeback]
85 root 0 SW< [bioset]
88 root 0 SW< [kblockd]
91 root 0 SW [kswapd0]
92 root 0 SW [fsnotify_mark]
94 root 0 SW [spi32766]
244 root 0 SW< [deferwq]
342 root 0 SW [mmcqd/0]
345 root 0 SW [kworker/u2:3]
402 root 0 SWN [jffs2_gcd_mtd7]
533 root 904 S /sbin/ubusd
556 root 768 S /sbin/askfirst /bin/login.sh
1081 root 0 SW< [ipv6_addrconf]
1349 root 1500 S {syslog.sh} /bin/sh /usr/bin/syslog.sh
1369 root 1208 S logread -f -F /tmp/log/20210924113244.log -p /var/ru
1386 root 1104 S /sbin/logd -S 64
1395 root 1820 S /sbin/rpcd
1408 root 3108 S /usr/sbin/quectel -s 3iot.com
1432 root 1164 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p
1633 root 1248 S /usr/sbin/odhcpd
1691 root 1496 S /usr/sbin/crond -f -c /etc/crontabs -l 5
1778 root 0 SW [RtmpCmdQTask]
1780 root 0 SW [kworker/0:3]
1783 root 0 SW [RtmpWscTask]
1786 root 0 SW [RtmpMlmeTask]
1836 root 5392 S /usr/sbin/uhttpd -f -h /www -r RAK7268C -x /cgi-bin
1855 root 776 S /usr/sbin/rteswplugd -r /etc/eswplug.action
1875 mosquitt 3776 S mosquitto -c /etc/mosquitto/mosquitto.conf
1932 root 4964 S /usr/bin/lua /usr/bin/data-broker.lua
1990 root 5492 S /usr/sbin/lorasrv -S -D /mnt/mmcblk0p1/lorasrv/mote_
2030 root 0 SW [kworker/0:4]
2522 root 1684 S /sbin/netifd
2666 root 1496 S udhcpc -p /var/run/udhcpc-apcli0.pid -s /lib/netifd/
2670 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 wwan0
2674 root 1496 S udhcpc -p /var/run/udhcpc-eth0.2.pid -s /lib/netifd/
2681 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 apcli
2689 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 eth0.
2765 root 784 S /sbin/ap_client ra0 apcli0 EE-Hub-x7He [I REMOVED MY WIFI PASSWORD]
3080 root 1496 S udhcpc -p /var/run/udhcpc-wwan0.pid -s /lib/netifd/d
3751 nobody 1000 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k -x /va
3869 root 1500 S {mwan3track} /bin/sh /usr/sbin/mwan3track wwan wwan0
4353 root 1496 S {loriot-gw} /bin/sh /opt/lrt/loriot-gw -f -s eu4pro.
4401 root 1500 S /usr/sbin/ntpd -n -S /usr/sbin/ntpd-hotplug -p 0.ope
4419 root 1536 S {breathing_light} /bin/sh /sbin/breathing_light
4437 root 1500 S {mwan3track} /bin/sh /usr/sbin/mwan3track wan0 apcli
4474 root 812 S /usr/bin/mpstat -f -t -u 5
10816 root 1232 R /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p
11357 root 1488 S sleep 5
11416 root 1488 S sleep 5
11417 root 1500 S -ash
11482 root 1488 S sleep 1
11519 root 1488 S sleep 1
11524 root 6468 S ./loriot_rak_7249_spi -f -s eu4pro.loriot.io
11527 root 1496 R ps

And the system log is:

Fri Sep 24 11:55:54 2021 user.err loriot_rak_7249_spi[28182]: You might be running an incompatible version of the binary
Fri Sep 24 11:55:54 2021 user.notice loriot_rak_7249_spi[28182]: Concentrator stopped
Fri Sep 24 11:55:55 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Fri Sep 24 11:55:55 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Fri Sep 24 11:55:55 2021 user.notice loriot_rak_7249_spi[28290]: Using eth0 for GW EUI AC1F09FFFF053CF4
Fri Sep 24 11:55:55 2021 user.notice loriot_rak_7249_spi[28290]: Requesting system route
Fri Sep 24 11:55:56 2021 user.notice loriot_rak_7249_spi[28290]: Connecting config server eu4pro.loriot.io
Fri Sep 24 11:55:56 2021 user.notice loriot_rak_7249_spi[28290]: SSL: certificate database loaded
Fri Sep 24 11:55:58 2021 user.notice loriot_rak_7249_spi[28290]: HTTP response HTTP/1.1 200 OK
Fri Sep 24 11:55:58 2021 user.notice loriot_rak_7249_spi[28290]: Timestamp Fri, 24 Sep 2021 11:55:58 GMT
Fri Sep 24 11:55:58 2021 user.notice loriot_rak_7249_spi[28290]: Content-type application/json; charset=utf-8
Fri Sep 24 11:56:00 2021 user.notice loriot_rak_7249_spi[28290]: HTTP response HTTP/1.1 204 No Content
Fri Sep 24 11:56:00 2021 user.notice loriot_rak_7249_spi[28290]: Starting LoRa Concentrator
Fri Sep 24 11:56:00 2021 user.err loriot_rak_7249_spi[28290]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Fri Sep 24 11:56:00 2021 user.err loriot_rak_7249_spi[28290]: ERROR: FAIL TO CONNECT BOARD
Fri Sep 24 11:56:00 2021 user.err loriot_rak_7249_spi[28290]: lgw_start failed
Fri Sep 24 11:56:00 2021 user.err loriot_rak_7249_spi[28290]: You might be running an incompatible version of the binary
Fri Sep 24 11:56:00 2021 user.notice loriot_rak_7249_spi[28290]: Concentrator stopped
Fri Sep 24 11:56:01 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Fri Sep 24 11:56:01 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Fri Sep 24 11:56:01 2021 user.notice loriot_rak_7249_spi[28640]: Using eth0 for GW EUI AC1F09FFFF053CF4
Fri Sep 24 11:56:01 2021 user.notice loriot_rak_7249_spi[28640]: Requesting system route
Fri Sep 24 11:56:01 2021 user.notice loriot_rak_7249_spi[28640]: Connecting config server eu4pro.loriot.io
Fri Sep 24 11:56:02 2021 user.notice loriot_rak_7249_spi[28640]: SSL: certificate database loaded
Fri Sep 24 11:56:03 2021 user.notice loriot_rak_7249_spi[28640]: HTTP response HTTP/1.1 200 OK
Fri Sep 24 11:56:03 2021 user.notice loriot_rak_7249_spi[28640]: Timestamp Fri, 24 Sep 2021 11:56:03 GMT
Fri Sep 24 11:56:03 2021 user.notice loriot_rak_7249_spi[28640]: Content-type application/json; charset=utf-8
Fri Sep 24 11:56:04 2021 user.notice loriot_rak_7249_spi[28640]: HTTP response HTTP/1.1 204 No Content
Fri Sep 24 11:56:04 2021 user.notice loriot_rak_7249_spi[28640]: Starting LoRa Concentrator
Fri Sep 24 11:56:04 2021 user.err loriot_rak_7249_spi[28640]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Fri Sep 24 11:56:04 2021 user.err loriot_rak_7249_spi[28640]: ERROR: FAIL TO CONNECT BOARD
Fri Sep 24 11:56:04 2021 user.err loriot_rak_7249_spi[28640]: lgw_start failed
Fri Sep 24 11:56:04 2021 user.err loriot_rak_7249_spi[28640]: You might be running an incompatible version of the binary
Fri Sep 24 11:56:04 2021 user.notice loriot_rak_7249_spi[28640]: Concentrator stopped

I would really appreciate some help with this as I am due to deploy the gateways in three weeks.

Architecturally and operating system wise, these are all similar, but the RAK7258 and RAK7249 have the first generation SX1301 LoRa concentrator chip.

In contrast the RAK7268 has the 2nd generation SX1302, which is substantially better (and lower power!) however an SX1302 needs a different packet forwarder program than an SX1301 would.

Since the Loriot setup is replacing the stock packet forwarder rather than interfacing to it, you’re going to need to get a version from them which can work with an SX1302, specifically the RAK2287 card which is similar but very slightly different than the Semtech reference design for that chip.

Either that, or maybe there’s a way you can connect to their network server from the stock packet forwarder, rather than replacing it.

Really, network servers should only expect one of the standard protocols from a gateway’s packet forwarder, and not see to replace it with their own build, as that causes exactly the sort of incompatibility with “new and improved hardware” that you’re seeing.

Ok thanks, that clarifies what the issue is. I have contacted LORIOT and will provide an update on here when I hear back from them. Hopefully they’ll be able to help me resolve this.

I do find this a little frustrating as I had checked with RAK both on the forum and via email before ordering and was re-assured that the new chipset was compatible with the LORIOT installation/set up process. My 7258 gateway has been working really well and the setup process was straightforward, I would have been happy to order two more of that model instead had I known about these compatibility issues.

Hello @Gauldblimey,
I’ve just tested this again, and it is working on my side.

The differences between the configuration that I’ve used for this test and the configuration that you have shared are :

1 - I’m using the latest version of the WisGateOS (WisGateOS 1.2.1) and yours is using WisGateOS1.1.2. I doubt that this is the problem as the fixes in the newest version have nothing to do with
LORIOT, but on the other hand it is recommended to use the latest version, so please update to WisGateOS 1.2.1.

2 - I’m using a different LORIOT server, which also should not cause this problem.

Please flash the latest firmware and try again. Also, it is good that you have contacted LORIOT as well so they could confirm if the problem comes from their side.

As for the problem with the hall :

It is written with the SX1301 in mind which is in the RAK7258. The newer SX1302 in the RAK7268 is a bit different and they need to adapt the HAL.

There is a problem with the HAL, but the only aspect that this issue affects is forwarding the GPS data and this should not affect the packet forwarder as well.

Hi @cstratton ,

Actually the default packet forwarder should be replaced by LORIOT’s software, as their custom packet forwarder has some features added:
https://docs.loriot.io/display/LNS5/LORIOT+Gateway+Software

The register structure of the SX1301 and sx SX1302 are completely different. sx1301 hal code can’t operate an sx1302 at all, not even in the most basic ways to set up to be able to receive packets.

Dual HAL forwarders are possible, but in looking through the mentioned LoRIOT download yesterday nothing stood out as a hint of sx1302 (vs sx1301) support. Even if it is somehow is a program that knows how to talk to either chip, the problem is at the precise point of chip startup, which would suggest a reset issue, that it’s currently trying to talk to the wrong chip, or a hardware failure.

Your screenshot seems to indicate a RAK7268, can you absolutely confirm it was the stock configuration with an sx1302 card installed at the time of the test?

Knowing for certain if this “should work” seems really key - and if it should, does the packet forwarder auto detect sx1301 vs sx1302 chip type, or is there a setting it somehow reads?

Yes, I’ve tested it with 2 different units, that both use RAK2287(sx1302).

Moreover as far as I know LORIOT software is compatible with sx1303 as well.

I can’t give you information about the LORIOT custom packet forwarder, or the way that it does handle the chip types as it is a product of LORIOT and it is not open-source.

1 Like

Given the confirmation that this is “supposed to work” (Edit: or is it? Loriot seems to be saying it’s not supported?) then after updating to latest gateway image if it still doesn’t work it might be worth doing a factory reset and just quickly checking the gateway functionality in one of its more standard modes, eg with the internal server or something, to see that the radio starts up and gets packets visible in the raw frames log.

Seems very unlikely two units would both have something like a concentrator card that needed to be reseated in the socket, but debugging is about eliminating possible causes one by one, so a confirmation that the gateways can work with their stock software would be good.

1 Like

Hi @cstratton @Gauldblimey,
Actually, that is very good advice, thanks for the help @cstratton.

@Gauldblimey if the problem remains after the reflash, you can try to use the gateway in the Build-In network server so we could see if the problem is within the gateway, or the problem comes from the connection with LORIOT.
Some logs from these tests will be very helpful as well.

Thank you, I will try this tomorrow and let you know how I get on.

Hi guys,

So after flashing the firmware and installing the LORIOT software I now get this read out from the system log:

Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # PULL_DATA sent: 6 (100.00 acknowledged)
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # RF packets sent to concentrator: 0 (0 bytes)
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # TX errors: 0
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # BEACON queued: 0
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # BEACON sent so far: 0
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # BEACON rejected: 0
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: ### [JIT] ###
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # SX1301/SX1302 time (PPS): 0, offset us 0
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: ### [GPS] ###
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: # GPS sync is disabled
Thu Sep 30 15:40:43 2021 user.notice lora_pkt_fwd[2159]: ##### END #####
Thu Sep 30 15:40:46 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:40:46 2021 kern.info quectel-CM[11862]: Dail Failed 12
Thu Sep 30 15:40:51 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:40:51 2021 kern.info quectel-CM[11862]: Dail Failed 13
Thu Sep 30 15:40:56 2021 daemon.info dnsmasq-dhcp[2674]: DHCPREQUEST(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2
Thu Sep 30 15:40:56 2021 daemon.info dnsmasq-dhcp[2674]: DHCPACK(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2 uea5cg8357nmb
Thu Sep 30 15:40:56 2021 daemon.warn odhcpd[1646]: DHCPV6 SOLICIT IA_NA from 00010001234e33ddf43909803d6f on br-lan: ok fdda:d154:735::9ea/128
Thu Sep 30 15:40:56 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:40:56 2021 kern.info quectel-CM[11862]: Dail Failed 14
Thu Sep 30 15:40:57 2021 daemon.info dnsmasq-dhcp[2674]: DHCPREQUEST(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2
Thu Sep 30 15:40:57 2021 daemon.info dnsmasq-dhcp[2674]: DHCPACK(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2 uea5cg8357nmb
Thu Sep 30 15:40:57 2021 daemon.warn odhcpd[1646]: DHCPV6 SOLICIT IA_NA from 00010001234e33ddf43909803d6f on br-lan: ok fdda:d154:735::9ea/128
Thu Sep 30 15:40:57 2021 daemon.warn odhcpd[1646]: DHCPV6 SOLICIT IA_NA from 00010001234e33ddf43909803d6f on br-lan: ok fdda:d154:735::9ea/128
Thu Sep 30 15:40:58 2021 daemon.info dnsmasq-dhcp[2674]: DHCPREQUEST(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2
Thu Sep 30 15:40:58 2021 daemon.info dnsmasq-dhcp[2674]: DHCPACK(br-lan) 192.168.230.104 38:ba:f8:22:a8:b2 uea5cg8357nmb
Thu Sep 30 15:40:58 2021 daemon.warn odhcpd[1646]: DHCPV6 SOLICIT IA_NA from 00010001234e33ddf43909803d6f on br-lan: ok fdda:d154:735::9ea/128
Thu Sep 30 15:40:59 2021 daemon.warn odhcpd[1646]: DHCPV6 REQUEST IA_NA from 00010001234e33ddf43909803d6f on br-lan: ok fdda:d154:735::9ea/128
Thu Sep 30 15:40:59 2021 daemon.info dnsmasq[2674]: read /etc/hosts - 1 addresses
Thu Sep 30 15:40:59 2021 daemon.info dnsmasq[2674]: read /tmp/hosts/dhcp - 1 addresses
Thu Sep 30 15:40:59 2021 daemon.info dnsmasq[2674]: read /tmp/hosts/odhcpd - 1 addresses
Thu Sep 30 15:40:59 2021 daemon.info dnsmasq-dhcp[2674]: read /etc/ethers - 0 addresses
Thu Sep 30 15:41:01 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:01 2021 kern.info quectel-CM[11862]: Dail Failed 15
Thu Sep 30 15:41:07 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:07 2021 kern.info quectel-CM[11862]: Dail Failed 16
Thu Sep 30 15:41:12 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:12 2021 kern.info quectel-CM[11862]: Dail Failed 17
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]:

2021-09-30 15:41:13 UTC

Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: ### [UPSTREAM] ###
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # RF packets received by concentrator: 0
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # CRC_OK: 0.00, CRC_FAIL: 0.00, NO_CRC: 0.00
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # RF packets forwarded: 0 (0 bytes)
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # PUSH_DATA datagrams sent: 1 (135 bytes)
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # PUSH_DATA acknowledged: 100.00
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: ### [DOWNSTREAM] ###
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # PULL_DATA sent: 6 (100.00 acknowledged)
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # RF packets sent to concentrator: 0 (0 bytes)
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # SX1301/SX1302 time (PPS): 0, offset us 0
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: ### [GPS] ###
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: # GPS sync is disabled
Thu Sep 30 15:41:13 2021 user.notice lora_pkt_fwd[2159]: ##### END #####
Thu Sep 30 15:41:17 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:17 2021 kern.info quectel-CM[11862]: Dail Failed 18
Thu Sep 30 15:41:19 2021 daemon.info bufwr[2005]: bufwrInit Done.
Thu Sep 30 15:41:22 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:22 2021 kern.info quectel-CM[11862]: Dail Failed 19
Thu Sep 30 15:41:27 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:27 2021 kern.info quectel-CM[11862]: Dail Failed 20
Thu Sep 30 15:41:29 2021 daemon.info db[2005]: DataBase Backup
Thu Sep 30 15:41:32 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:32 2021 kern.info quectel-CM[11862]: Dail Failed 21
Thu Sep 30 15:41:37 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:37 2021 kern.info quectel-CM[11862]: Dail Failed 22
Thu Sep 30 15:41:42 2021 kern.info quectel-CM[11862]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 15:41:42 2021 kern.info quectel-CM[11862]: Dail Failed 23
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]:

2021-09-30 15:41:43 UTC

Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: ### [UPSTREAM] ###
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # RF packets received by concentrator: 0
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # CRC_OK: 0.00, CRC_FAIL: 0.00, NO_CRC: 0.00
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # RF packets forwarded: 0 (0 bytes)
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # PUSH_DATA datagrams sent: 1 (135 bytes)
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # PUSH_DATA acknowledged: 100.00
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: ### [DOWNSTREAM] ###
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # PULL_DATA sent: 5 (100.00 acknowledged)
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # PULL_RESP(onse) datagrams received: 0 (0 bytes)
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # RF packets sent to concentrator: 0 (0 bytes)
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # TX errors: 0
Thu Sep 30 15:41:43 2021 user.notice lora_pkt_fwd[2159]: # BEACON queued: 0

and this when connected via ssh and runnning the ps command:

BusyBox v1.23.2 (2021-08-26 13:50:51 UTC) built-in shell (ash)


    LoRaWAN Gateway (WisGateOS 1.2.1_RAK 20210826)

[email protected]:~# ps
PID USER VSZ STAT COMMAND
1 root 1508 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW< [kworker/0:0H]
7 root 0 SW< [khelper]
83 root 0 SW< [writeback]
85 root 0 SW< [bioset]
88 root 0 SW< [kblockd]
90 root 0 SW [kworker/0:1]
91 root 0 SW [kswapd0]
92 root 0 SW [fsnotify_mark]
94 root 0 SW [spi32766]
253 root 0 SW< [deferwq]
298 root 0 SW [kworker/u2:2]
342 root 0 SW [mmcqd/0]
345 root 0 SW [kworker/u2:3]
402 root 0 SWN [jffs2_gcd_mtd7]
533 root 904 S /sbin/ubusd
551 root 768 S /sbin/askfirst /bin/login.sh
1086 root 0 SW< [ipv6_addrconf]
1361 root 1500 S {syslog.sh} /bin/sh /usr/bin/syslog.sh
1368 root 1208 S logread -f -F /tmp/log/20210930150344.log -p /var/ru
1398 root 1164 S /sbin/logd -S 64
1407 root 1820 S /sbin/rpcd
1455 root 1164 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p
1646 root 1248 S /usr/sbin/odhcpd
1683 root 1500 S /usr/sbin/crond -f -c /etc/crontabs -l 5
1791 root 0 SW [RtmpCmdQTask]
1795 root 0 SW [RtmpWscTask]
1796 root 0 SW [RtmpMlmeTask]
1857 root 5392 S /usr/sbin/uhttpd -f -h /www -r RAK7268C -x /cgi-bin
1875 root 776 S /usr/sbin/rteswplugd -r /etc/eswplug.action
1892 mosquitt 3776 S mosquitto -c /etc/mosquitto/mosquitto.conf
1952 root 4964 S /usr/bin/lua /usr/bin/data-broker.lua
2005 root 5492 S /usr/sbin/lorasrv -S -D /mnt/mmcblk0p1/lorasrv/mote_
2159 root 19508 S /usr/bin/lora_pkt_fwd -g /var/etc/global_conf.json -
2571 root 1624 S /sbin/netifd
2674 nobody 1000 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k -x /va
2738 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 apcli
2767 root 1496 S udhcpc -p /var/run/udhcpc-apcli0.pid -s /lib/netifd/
2773 root 1496 S udhcpc -p /var/run/udhcpc-eth0.2.pid -s /lib/netifd/
2778 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 eth0.
2869 root 784 S /sbin/ap_client ra0 apcli0 WIFI DETAILS REMOVED
3823 root 1500 S {mwan3track} /bin/sh /usr/sbin/mwan3track wan0 apcli
4353 root 1500 S /usr/sbin/ntpd -n -S /usr/sbin/ntpd-hotplug -p 0.ope
4364 root 1536 S {breathing_light} /bin/sh /sbin/breathing_light
4379 root 812 S /usr/bin/mpstat -f -t -u 5
22153 root 3108 S /usr/sbin/quectel -s 3iot.com
22195 root 0 SW [kworker/0:2]
23028 root 0 SW [kworker/u2:0]
23109 root 1496 S udhcpc -p /var/run/udhcpc-wwan0.pid -s /lib/netifd/d
23110 root 804 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 wwan0
25293 root 1232 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p
25880 root 1488 S sleep 5
25906 root 1500 S -ash
25940 root 1560 S {mwan3} /bin/sh /usr/sbin/mwan3 status
25941 root 1492 S tee
25968 root 1488 S sleep 1
25991 root 1348 R {luci} /usr/bin/lua /www/cgi-bin/luci
25992 root 1496 R ps
[email protected]:~#

So this is similar to what I had with the 7528. And the status light flashes blue but it still doesn’t connect to LORIOT.

After running the command to turn off the other packet forwarder as recomended for the 7528 gateway ( /etc/init.d/packet_forwarder disable ; /etc/init.d/loriot-gw enable ; reboot now) I now get this and the status light flashes red so I think it is at this stage that something goes wrong:

Thu Sep 30 16:26:18 2021 user.err loriot_rak_7249_spi[11114]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:26:18 2021 user.err loriot_rak_7249_spi[11114]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:26:18 2021 user.err loriot_rak_7249_spi[11114]: lgw_start failed
Thu Sep 30 16:26:18 2021 user.err loriot_rak_7249_spi[11114]: You might be running an incompatible version of the binary
Thu Sep 30 16:26:18 2021 user.notice loriot_rak_7249_spi[11114]: Concentrator stopped
Thu Sep 30 16:26:18 2021 kern.info quectel-CM[1426]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 16:26:18 2021 kern.info quectel-CM[1426]: Dail Failed 31
Thu Sep 30 16:26:19 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:26:19 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:26:19 2021 user.notice loriot_rak_7249_spi[11331]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:26:19 2021 user.notice loriot_rak_7249_spi[11331]: Requesting system route
Thu Sep 30 16:26:19 2021 user.notice loriot_rak_7249_spi[11331]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:26:19 2021 user.notice loriot_rak_7249_spi[11331]: SSL: certificate database loaded
Thu Sep 30 16:26:22 2021 user.notice loriot_rak_7249_spi[11331]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:26:22 2021 user.notice loriot_rak_7249_spi[11331]: Timestamp Thu, 30 Sep 2021 16:26:10 GMT
Thu Sep 30 16:26:22 2021 user.notice loriot_rak_7249_spi[11331]: Content-type application/json; charset=utf-8
Thu Sep 30 16:26:23 2021 kern.info quectel-CM[1426]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 16:26:23 2021 kern.info quectel-CM[1426]: Dail Failed 32
Thu Sep 30 16:26:24 2021 user.notice loriot_rak_7249_spi[11331]: HTTP response HTTP/1.1 204 No Content
Thu Sep 30 16:26:24 2021 user.notice loriot_rak_7249_spi[11331]: Starting LoRa Concentrator
Thu Sep 30 16:26:24 2021 user.err loriot_rak_7249_spi[11331]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:26:24 2021 user.err loriot_rak_7249_spi[11331]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:26:24 2021 user.err loriot_rak_7249_spi[11331]: lgw_start failed
Thu Sep 30 16:26:24 2021 user.err loriot_rak_7249_spi[11331]: You might be running an incompatible version of the binary
Thu Sep 30 16:26:24 2021 user.notice loriot_rak_7249_spi[11331]: Concentrator stopped
Thu Sep 30 16:26:25 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:26:25 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:26:25 2021 user.notice loriot_rak_7249_spi[11632]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:26:25 2021 user.notice loriot_rak_7249_spi[11632]: Requesting system route
Thu Sep 30 16:26:25 2021 user.notice loriot_rak_7249_spi[11632]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:26:25 2021 user.notice loriot_rak_7249_spi[11632]: SSL: certificate database loaded
Thu Sep 30 16:26:28 2021 user.notice loriot_rak_7249_spi[11632]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:26:28 2021 user.notice loriot_rak_7249_spi[11632]: Timestamp Thu, 30 Sep 2021 16:26:28 GMT
Thu Sep 30 16:26:28 2021 user.notice loriot_rak_7249_spi[11632]: Content-type application/json; charset=utf-8
Thu Sep 30 16:26:28 2021 kern.info quectel-CM[1426]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 16:26:28 2021 kern.info quectel-CM[1426]: Dail Failed 33
Thu Sep 30 16:26:29 2021 kern.info quectel-CM[1426]: QmiWwanThread exit
Thu Sep 30 16:26:29 2021 kern.info quectel-CM[1426]: main exit
Thu Sep 30 16:26:31 2021 kern.info quectel-CM[11922]: WCDMA<E_QConnectManager_Linux&Android_V1.1.38
Thu Sep 30 16:26:31 2021 kern.info quectel-CM[11922]: /usr/sbin/quectel profile[1] = 3iot.com///0, pincode = (null)
Thu Sep 30 16:26:31 2021 user.notice root: echo 1 > /sys/class/gpio/gpio42/value
Thu Sep 30 16:26:31 2021 daemon.notice netifd: Network device ‘wwan0’ link is down
Thu Sep 30 16:26:32 2021 user.notice loriot_rak_7249_spi[11632]: HTTP response HTTP/1.1 204 No Content
Thu Sep 30 16:26:32 2021 user.notice loriot_rak_7249_spi[11632]: Starting LoRa Concentrator
Thu Sep 30 16:26:32 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity loss
Thu Sep 30 16:26:32 2021 daemon.notice netifd: Interface ‘wwan6’ has link connectivity loss
Thu Sep 30 16:26:32 2021 daemon.notice netifd: Interface ‘wwan’ is disabled
Thu Sep 30 16:26:32 2021 daemon.notice netifd: Interface ‘wwan6’ is disabled
Thu Sep 30 16:26:32 2021 daemon.notice netifd: wwan (2787): Read error: Network is down, reopening socket
Thu Sep 30 16:26:32 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:32 2021 user.err loriot_rak_7249_spi[11632]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:26:32 2021 user.err loriot_rak_7249_spi[11632]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:26:32 2021 user.err loriot_rak_7249_spi[11632]: lgw_start failed
Thu Sep 30 16:26:32 2021 user.err loriot_rak_7249_spi[11632]: You might be running an incompatible version of the binary
Thu Sep 30 16:26:32 2021 user.notice loriot_rak_7249_spi[11632]: Concentrator stopped
Thu Sep 30 16:26:32 2021 user.notice root: echo 0 > /sys/class/gpio/gpio42/value
Thu Sep 30 16:26:32 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:33 2021 daemon.notice netifd: wwan (2787): udhcpc: bind: No such device
Thu Sep 30 16:26:33 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:26:33 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:26:33 2021 user.notice loriot_rak_7249_spi[12051]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:26:33 2021 user.notice loriot_rak_7249_spi[12051]: Requesting system route
Thu Sep 30 16:26:33 2021 user.notice loriot_rak_7249_spi[12051]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:26:33 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:34 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:34 2021 user.notice loriot_rak_7249_spi[12051]: SSL: certificate database loaded
Thu Sep 30 16:26:34 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:35 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:37 2021 user.notice loriot_rak_7249_spi[12051]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:26:37 2021 user.notice loriot_rak_7249_spi[12051]: Timestamp Thu, 30 Sep 2021 16:26:26 GMT
Thu Sep 30 16:26:37 2021 user.notice loriot_rak_7249_spi[12051]: Content-type application/json; charset=utf-8
Thu Sep 30 16:26:40 2021 user.notice loriot_rak_7249_spi[12051]: HTTP response HTTP/1.1 204 No Content
Thu Sep 30 16:26:40 2021 user.notice loriot_rak_7249_spi[12051]: Starting LoRa Concentrator
Thu Sep 30 16:26:40 2021 user.err loriot_rak_7249_spi[12051]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:26:40 2021 user.err loriot_rak_7249_spi[12051]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:26:40 2021 user.err loriot_rak_7249_spi[12051]: lgw_start failed
Thu Sep 30 16:26:40 2021 user.err loriot_rak_7249_spi[12051]: You might be running an incompatible version of the binary
Thu Sep 30 16:26:40 2021 user.notice loriot_rak_7249_spi[12051]: Concentrator stopped
Thu Sep 30 16:26:41 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:26:41 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:26:41 2021 user.notice loriot_rak_7249_spi[12491]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:26:41 2021 user.notice loriot_rak_7249_spi[12491]: Requesting system route
Thu Sep 30 16:26:41 2021 user.notice loriot_rak_7249_spi[12491]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:26:42 2021 user.notice loriot_rak_7249_spi[12491]: SSL: certificate database loaded
Thu Sep 30 16:26:43 2021 user.notice loriot_rak_7249_spi[12491]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:26:43 2021 user.notice loriot_rak_7249_spi[12491]: Timestamp Thu, 30 Sep 2021 16:26:31 GMT
Thu Sep 30 16:26:43 2021 user.notice loriot_rak_7249_spi[12491]: Content-type application/json; charset=utf-8
Thu Sep 30 16:26:43 2021 user.notice loriot_rak_7249_spi[12491]: HTTP response HTTP/1.1 204 No Content
Thu Sep 30 16:26:43 2021 user.notice loriot_rak_7249_spi[12491]: Starting LoRa Concentrator
Thu Sep 30 16:26:43 2021 user.err loriot_rak_7249_spi[12491]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:26:43 2021 user.err loriot_rak_7249_spi[12491]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:26:43 2021 user.err loriot_rak_7249_spi[12491]: lgw_start failed
Thu Sep 30 16:26:43 2021 user.err loriot_rak_7249_spi[12491]: You might be running an incompatible version of the binary
Thu Sep 30 16:26:44 2021 user.notice loriot_rak_7249_spi[12491]: Concentrator stopped
Thu Sep 30 16:26:45 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:26:45 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:26:45 2021 user.notice loriot_rak_7249_spi[12661]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:26:45 2021 user.notice loriot_rak_7249_spi[12661]: Requesting system route
Thu Sep 30 16:26:45 2021 user.notice loriot_rak_7249_spi[12661]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:26:45 2021 user.notice loriot_rak_7249_spi[12661]: SSL: certificate database loaded
Thu Sep 30 16:26:46 2021 user.notice loriot_rak_7249_spi[12661]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:26:46 2021 user.notice loriot_rak_7249_spi[12661]: Timestamp Thu, 30 Sep 2021 16:26:46 GMT
Thu Sep 30 16:26:46 2021 user.notice loriot_rak_7249_spi[12661]: Content-type application/json; charset=utf-8
Thu Sep 30 16:26:46 2021 user.notice hotplug: Cannot find LORA usb proper mapping, exit
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan’ is enabled
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan6’ is enabled
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Network device ‘wwan0’ link is up
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan’ has link connectivity
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan’ is setting up now
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan6’ has link connectivity
Thu Sep 30 16:26:47 2021 daemon.notice netifd: Interface ‘wwan6’ is setting up now

So I guess a different command is required after installing the LORIOT software?

Thank you for your help / patience. I’m an ecologist so this kind of stuff is out of my comfort zone and I would like to get to the bottom of this so I can provide a straightforward set up guide for other colleagues like I have done for the 7258 gateway.

Running this command to reverse the previous effect of disabling the packet forwarder allows the gateway to start up again and the status light begins to flash blue again:

/etc/init.d/packet_forwarder enable ; /etc/init.d/loriot-gw enable ; reboot now

But it still doesn’t seem to connect to LORIOT and the message (“you might be running an incompatible version of the binary”) is displayed in the system log so this suggests an incompatibility issue with the LORIOT software:

Thu Sep 30 16:56:47 2021 user.notice loriot_rak_7249_spi[11382]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:56:47 2021 user.notice loriot_rak_7249_spi[11382]: Requesting system route
Thu Sep 30 16:56:47 2021 user.notice loriot_rak_7249_spi[11382]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:56:47 2021 user.notice loriot_rak_7249_spi[11382]: SSL: certificate database loaded
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: HTTP response HTTP/1.1 200 OK
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: Timestamp Thu, 30 Sep 2021 16:56:36 GMT
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: Content-type application/json; charset=utf-8
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: HTTP response HTTP/1.1 204 No Content
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: Starting LoRa Concentrator
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: lgw_start failed
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: You might be running an incompatible version of the binary
Thu Sep 30 16:56:48 2021 user.notice loriot_rak_7249_spi[11382]: Concentrator stopped
Thu Sep 30 16:56:49 2021 user.notice syslog: Gateway loriot_rak_7249_spi version 2.8.1560-JKS-EU4PRO-10
Thu Sep 30 16:56:49 2021 user.notice syslog: Openssl version OpenSSL 1.0.2j 26 Sep 2016
Thu Sep 30 16:56:49 2021 user.notice loriot_rak_7249_spi[11490]: Using eth0 for GW EUI AC1F09FFFF053CF4
Thu Sep 30 16:56:49 2021 user.notice loriot_rak_7249_spi[11490]: Requesting system route
Thu Sep 30 16:56:49 2021 user.notice loriot_rak_7249_spi[11490]: Connecting config server eu4pro.loriot.io
Thu Sep 30 16:56:49 2021 kern.info quectel-CM[1424]: requestRegistrationState2 MCC: 234, MNC: 30, PS: Detached, DataCap: UMTS
Thu Sep 30 16:56:49 2021 kern.info quectel-CM[1424]: Dail Failed 32
Thu Sep 30 16:56:49 2021 user.notice loriot_rak_7249_spi[11490]: SSL: certificate database loaded

Feedback from LORIOT:

Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: ERROR: NOT EXPECTED CHIP VERSION (v0)
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: ERROR: FAIL TO CONNECT BOARD
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: lgw_start failed
Thu Sep 30 16:56:48 2021 user.err loriot_rak_7249_spi[11382]: You might be running an incompatible version of the binary

“These errors is expected behavior because the Loriot binary could not start due to the HAL differences between RAK7268’s SX1302 and the SX1301 built in RAK7249”

I am currently trying to set up remote access so they can assist.

More updates to follow.

Jethro

Hi, as an update. Eventually I gave up trying to use the LORIOT software and set up the gateway on LORIOT using the Semtech Packet Forwarder. This should be sufficient for my needs as the gateways will be deployed in relatively remote locations.

The support team from LORIOT are keen to remotely access one of these gateways so they can provide suitable software for the new chipset. Perhaps tha tis something RAK staff could investigate? The contact is: [email protected]

Fow now I would advise anyone wanting to use LORIOT to purchase a 7258 gateway instead of the 7268 gateway and RAK should really warn customers about this issue. Once resolved though it will be a great product and very competitive with other brands.

Thanks,

Jethro