and your question is ?
Why are there only 2 messages showing up?
- 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.
hello all, i just install ttgo singlechannel gateway and test another node is ttggo 868 mhz node
node keep sends uplink data to gateway but how can i send downlink message to node?
for example
turn on or off message to node
thanks
@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!
Hello
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
Greets
I used this code in my esp32 (https://github.com/things4u/ESP-1ch-Gateway-v5.0), everything is working, however I wanted to register my gateway at the gateway console, but there is a gateway key and I do not know where to put it in the code. How I do this?
I think you have to go about this the other way around. Load the sketch on your ESP and either look at the ESPs gateway dashboard / website or the serial monitor and find the âGateway IDâ. Use this ID to register your single chanel gateway with TTN. Make sure click the âIâm using the legacy packet forwarderâ checkbox on the gateway registration page and the form will change to accept your gateway ID.
2 Likes
I know this apply for uplink, does this apply for downlink too? Do you need to force a node to receive information in a specific downlink channel?
Anything change at TTN? I doubt it as I see no news - but my Single Channel Gateway that has been happily working for a year and half suddenly stopped forwarding data around 2AM (EDT US) last night. Occasionally the gw will need a reboot but that does not help now. I have changed nothing!
Reset gateway, reset all frame counters.
It shows up as online, active a few seconds ago, but none of my devices have shown any traffic for over 12 hours now - they all (5 active devices) send a few bytes of data every 30 minutes. The gateway counter increments normally, showing 28 packages received since resetting over 3 hours ago (~5x3x2)
It is a Wemos esp8266 with https://github.com/dlarue/ESP-1ch-Gateway-v2.0 and an InAir9b module.
Iâll plug in a serial terminal when I get home.
I see on the status page https://status.thethings.network/ there was an update to a subset of server on 8/6/2018 - with only minor service interruptions expected, otherwise all normal.
It is setup to use:
$ nc -uv router.us.thethings.network 1700
Connection to router.us.thethings.network 1700 port [udp/*] succeeded!
altho in the console the router is set for ttn-router-us-west or us-west.thethings.network
Those resolve to different IPs?
router.us.thethings.network canonical name = bridge.us-west.thethings.network.
Name: bridge.us-west.thethings.network
Address: 13.66.213.36
Non-authoritative answer:
Name: us-west.thethings.network
Address: 13.66.229.235
And my application is set for ttn-handler-eu â Iâll try setting that to ttn-handler-us-west, but that states that all devices registered to this application will be lost!!
I can even see gateway traffic coming in on the console - but nothing in the application devices:
Got one device back online - itâs starting to look like where the handlers could be different in gateway and applications, now they have to be the same? I created a new app with the us-west handler, and registered a new device, programmed it with the new ID and now it works. That is probably documented somewhere I should have been reading
Hey all, Iâve built a small 1CH gateway based on a Wemos D1 mini, Ch. Hallardâs connection board (V1.3) and a RFM95. I configured things4u/ESP-1ch-Gateway-v4.0 is used to run it âŚ
Now, on the serial monitor I am getting
âŚ
Unrecognized transceiver, version: 0
Abort called
âŚ
and the gateway is not connecting to ttn (nor to my wifi)
Interestingly, I had it once running when - for preliminary tests - the D1 and the Hallard board (with RFM95 and diodes D2, D3, D4 soldered on to it) were connected with wires, omitting RST and D0. After soldering everything, I can not get it up and running again. I checked all the connections several times, tried to improve the soldering joints, ⌠still not working. Could it be any other issue than bad soldering? Has anybody experienced similar problems? If so, how was it solved? Thanks a lot for any hints!
(Sorry, I am pretty much a beginner. But I try my bestâŚ)
Have a look at the following YouTube clip from @SensorsIOT: https://youtu.be/ZV_ZY-0Q1lo.
I built one up following it step by step and it worked jusr fine. Note the comments on which diodes to solder in and which ones not.
How I put a fixed IP? I using Esp LoRa 32
Hi, I am using an Heltec LoRa 32 v2 Board to create a GW. SS:18, RST:14, DIO0:26, DIO1:34, DIO2:35 (working ok as node)
I have it connected to TTN but I donât receive any message from nodes.
Using library from Kersing
Both GW and nodes are using channel 0.
From the Serial log I get:
and sometimes
SCAN:: CADDETD,
loop:: readUdp calling
PKT_PULL_ACK:: size 4 From 52.169.76.203, port 1700, data: 1:93:25:4:
readUdp:: returning=4
SCAN:: CADDETD,
STAT <stat update: <232> {âstatâ:{âtimeâ:â2018-10-05 14:55:17 CETâ,âlatiâ:0.00000,âlongâ:0.00000,âaltiâ:8,ârxnbâ:0,ârxokâ:0,ârxfwâ:0,âackrâ:0.0,âdwnbâ:0,âtxnbâ:0,âpfrmâ:âESP32 HELTEC",âmailâ:"rodri16@gmail.comâ,âdescâ:âMy ESP32 Gateway HELTECâ}}
WiFi connected
What am I doing wrong?
Hello,
To help can you provide answers to the following :
-
Can you show the logs or serial output of the the nodes?
-
Are you running ABP or OTAA on the nodes?
-Arinze
Hi Arizne,
I am using both ABP and also OTAA
Log from ABP, using DR_SF7
Location: INVALID Date/Time: 0/0/2000 00:00:00.00
13208 Sending⌠Packet queued
13367 Waiting⌠968236: EV_TXCOMPLETE (includes waiting for RX windows)
15531 TX_COMPLETE
Location: INVALID Date/Time: 0/0/2000 00:00:00.00
27145 Sending⌠Packet queued
27303 Waiting⌠1839262: EV_TXCOMPLETE (includes waiting for RX windows)
29467 TX_COMPLETE
log from OTAA, keep trying to join
376 Sending⌠Packet queued
406 Waiting⌠26891: EV_JOINING
Both nodes work on a full GW, this is the metadata I get from the full gateway (ABP mode)
