Jason Reiss
Forum Replies Created
-
With whitelist disabled how do you expect end-devices to join the network?
An empty whitelist would have the same effect as disable.
This will work.
admin@mtcdt:~# curl 127.0.0.1/api/loraNetwork/whitelist -X PUT -d '{"enabled":false}' -H 'Content-Type: application/json'If using the NetworkID/NetworkKey end-devices are accepted regardless of whitelist as the end-device has the correct credentials.
Whitelist is a method to allow unique deveui/appkey pairs.
They are not the same and the mts-fpga-loader utility will not install them.
We may look at including the 863 version of firmware in a future version.They should be functionally equivalent. The versions installed on the Conduit have unique signatures that are verified by the mts-fpga-loader utility.
It appears the v33 LBT firmware does not support frequencies below 915 MHz.
LBT is not required for LoRaWAN use in EU868, LoRaWAN uses duty-cycle.
See lines 125-140. The minimum lbt frequency is pulled from the FPGA firmware. A new FPGA firmware may be needed to support LBT for these frequencies.
https://github.com/Lora-net/lora_gateway/blob/master/libloragw/src/loragw_lbt.cUpgrading the FPGA is only supported on MTCAP-0.1
admin@mtcap:~# mts-io-sysfs show hw-version MTCAP-0.1<code></code>admin@mtcap:~# mts-fpga-loader -c Checking hardware compatibility Found Valid Hardware: MTCAP-LORA-1.5 Valid FPGA version: 31FPGA v33 is needed for LBT
admin@mtcap:~# /etc/init.d/lora-network-server stop admin@mtcap:~# mts-fpga-loader -i /usr/lib/mts-flash-binaries/mtcap-fpga-v33.hex admin@mtcap:~# mts-fpga-loader -c Checking hardware compatibility Found Valid Hardware: MTCAP-LORA-1.5 Valid FPGA version: 33admin@mtcap:~# /etc/init.d/lora-network-server startEDIT: FPGA upgrade only on MTCAP-0.1, not MTCAP-0.0
