Below is a list of actual, up-to-date RFM9x / SX127x-based single channel gateway implementations: (Last updated on: 2017-12-05)
For Raspberry Pi
https://github.com/hallard/single_chan_pkt_fwd
Supports ABP activation, single frequency and single spreading factor. Configuration via separate configuration file (configuration changes do not require recompilation but require the software to be re-started). (Written in C++.)
For ESP8266
https://github.com/things4u/ESP-1ch-Gateway-v5.0
Supports ABP and OTAA activation, downstream messages(?), single frequency with multiple spreading factors, Web interface, WifiManager, OTA, I2C OLED display and ‘use gateway as a node’. Configuration is (partially) hard-coded (some configuration changes require recompilation while others can be changed via web interface, if enabled). (Written in C++.)
https://github.com/JaapBraam/LoRaWanGateway
Supports ABP and OTAA activation, downstream messages and single frequency with multiple spreading factors. Configuration via separate file (but file also contains code). (Written in Lua.)
For ESP32
https://github.com/kersing/ESP-1ch-Gateway-v5.0
This fork of ‘things4u ESP-1ch-Gateway-v5.0’ for ESP8266 has added support for ESP32 and (Heltec) Wifi LoRa 32 modules.
Supports the same features as things4u’s implementation but currently does not support WifiManager and OTA. (Written in C++.)
https://github.com/pycom/pycom-libraries/tree/master/examples/lorawan-nano-gateway for the LoPy (ESP32 board running MicroPython interpreter).
Supports ABP and OTAA activation, downstream messages, single frequency (not clear if multiple spreading factors are supported), configuration via separate configuration file that can be uploaded via USB or FTP. Lacks description / instructions / readme.md. (Written in MicroPython.)
.
NOTES:
Don’t forget: each implementation requires that you configure the software with your own gateway parameters before compiling/running the software.
Hallard’s Raspberry Pi version installs flawlessly (but supports the least features).
The other implementations may require some tweaking.
If in the case it does not support OTAA, it means that gateway only have one way communication, right? It will be excepted by my country law if it does not transmit or transmit < 50mW (eirp).
OTAA requires downstream traffic from gateway to node (‘end-device’). ABP only requires upstream traffic from node to gateway. So upstream only.
In practice it would be possible to support downstream messages but not support OTAA, but hallard’s gateway for Raspberry Pi (currently) supports neither OTAA nor downstream messages.
True, but only if the node does not use ADR or other downlinks. (For ABP, there is simply no joining phase as the “session” keys have already been programmed into the device, so no downlinks are needed to join the network. Once those keys are known, OTAA and ABP devices act the same for uplinks, downlinks, ADR, and so on, until an OTAA device somehow loses its keys and needs to join again.)
Hmmm, assuming we’re referring to gateways for TTN: I doubt that. If TTN thinks a gateway can do downlinks, I don’t think it’s going to use that only for “data” downlinks, and not for OTAA (or ADR, or other MAC commands)? Gateways just forward whatever the node or backend gives them; they don’t know if a downlink is some OTAA Join Accept or any other type of downlink.
Thanks. If you or someone else can specify which features and MCU platforms this single channel gateway supports then I can update it in above list of single channel gateways.
It supports OTAA, ABP and downstream messages.
The configuration is kept separately in a dedicated file that can be uploaded to the board using USB or FTP - and maybe other network protocols on the wifi side like HTTP, haven’t tried.
It listens on a single frequency, but I’m not sure about multiple SF or not.
As for the MCU, this was written for a LoPy : ESP32 board running the micropython “interpreter” from pycom. I don’t know if it is possible to flash that on a different ESP32 board, but it should with some tweaking as it’s all opensource.
Thanks to LoRa ESP developers! Wanted to share idea to use Tic-Tac enclosure for the LORA ESP8266 single ch GW glued to the window glass and a Thing with Arduino and HTU21.
Tic-Tac plastic boxes can be easily cleaned from printed labels using WD-40.
In the Thing had to supply HTU21 from 5V and use a pullup 10k on SDA signal.
Example with SF7 works, but when tried to change registers to transmit in SF12 mode then the GW receives it but data are errorness.
I use simple wire antena. Range is ca 200 m in the city. Would it make big difference to use enamelled transformer wire for antena?
It has all the hardware needed for that yes, but I am not sure anyone have done the software part yet (porting a single channel gateway code to that platform).
While not as good as your external SMA antenna, for the fun factor using one of these small GSM PCB antenna’s could make it fit all inside a single tic tac box, antenna included.