First, i mean by a ‘wifi lora 32’ a “Heltec WiFi LoRa 32 – ESP32 with OLED and SX1278”.
Then, actually i connect the board to a DHT11 sensor, to collect Temperature and humidity. Its work and the Data are displayed on the OLED Display. Now, I want to do something with these data, something like : store it in a database or use it on a web application … for example.
I also read that a LoRa network needs three things : end-devices (for me its a board with the sensor) , a LoRa Gateway and a LoRa network Server. So this why i am asking for a Gateway !
Could please suggest me something to do with the data i collect, and give me some explanation why i don’t need a gateway ?
sure… LEARN don’t expect us to do your ‘home work’
start reading and use search here on the forum and google to understand the basics of the things network.
“I need to make a low coast LoRa Gateway using Raspberry pi 3 and Wifi LoRa 32”, hence the answers you got and you do not need a node (Wifi LoRa 32) to make a Gateway.
Hi all,
does anyone know a working library for a Singol Channel Gateway (Raspberry PI3),
with the possibility of downstream messages?
I am currently using /tftelkamp/single_chan_pkt_fwd , but it does not have this feature.
In the summary at the beginning of this tread, for the gateways made with ESP8266 are indicated a couple of packages that have this possibility, but I have not found anything for raspberry PI3
Hi all
I found and verified the operation of a library to create a gateway with Raspberry PI3 and Dragino Hat v1.4, which allows the downstream messages
What is the difference between a “single-channel gateway” and a “real gateway”?
A real gateway is able to listen on 8 channels and all spreading
factors at the same time. Single-channel gateways are fixed to one
channel and spreading factor, so they will only receive about 2% of the
messages unless you specifically configure your nodes to send at the
exact same configuration as your single-channel gateway.
As LoRaWAN is a spread-spectrum radio protocol, single-channel
gateways are not LoRaWAN-compatible.
You can use a single channel gateway on the TTN network but you miss a lot of messages, if you use your own node you can match your gateway channel with that of the node and don’t miss messages because the channels are 'locked.
@telkamp Please excuse the completely noob question, but I am trying to use your hallard implementation, but can’t seem to find the Gateway Id. Everything seems to work fine but it just starts and stops without telling me what the id is, as per the below picture. Please could you explain where I’m going wrong?
In advance, thanks a lot! Several hours of Googling don’t seem to have helped, so lets try people!
It would be shown in the log file, or you can work around not seeing it by starting the packet forwarder like below:
./single_chan_pkt_fwd/single_pkt_fwd
Assuming that you are in the pi folder. Also this should be obvious but sometimes people forget so before you run that command make sure you stop the service with sudo systemctl stop single_chan_pkt_fwd.
Perfect, thanks very much @glbaum ! Just one point for anybody else with this problem in the future, running this command from the pi folder didn’t work (I assume a permission issue), but going into the single_chan_pkt_fwd folder and running ./single_chan_pkt_fwd worked perfectly.
I don’t necessarily remember if I needed to use sudo to run it outside of it’s folder but maybe that’s the case. I just know that I had been able to start it that way, but either way I’m glad you got it working @Paul_B!
I made a BOM at octoparts for the WeMos/LoLIN D1 mini SCGW for the PCB from @Charles and his solution at his Git .
At my BOM i made a little bit more.
Ad OLED, SMA, Conector for OLED … and so on. Describe a little bit at the end of the rows.
But before i spread, can someone have a look that BOM is ok? And give me response for improovements.
If interestet you can find it here: octoBOM