“Over here,we will use the Lora Shileld,MEGA2560 and Raspberry Pi to build a single channel LoRaWAN gateway.”
Turn it off, disconnect from TTN and go use Forum search for SCPF, DCPF and/or SIngle Channel Packet Forwarders (Note what you have is NOT a LoRaWAN GW).
As it says further down the same post:
"Lora Gateway:
The RPi Lora Gateway will receive this data…"
Note key diffference - yes it used LoRa Technology, but a LoRa tranceiver alone does not a LoRAWAN Gateway make!
If you were indeed…
Then no problem you would be heading in the right direction.
“This single channel LoRaWAN gateway is a proof-of-concept implementation,that can be used for development and node testing. It is not a replacement for a real multi channel/multi SF gateway! It supports some LoRaWAN features, but due to its static nature (single channel) it is not fullyLoRaWAN compatible (and will never be)”.
By almeans use as POC and development environment if you must - but you will create more problems for yourself and others than you will solve…and do this using your own Private LoRa instance…DO NOT USE ON TTN as disruptive to other users… Better yet as it says
"This is not a real gateway, it is for testing purposes". Please go and get a real one (TTIG, LPS8 etc…they are not expensive and there is no excuse!)
Further on same line it says:
“It is LoRaWAN compatible, but not compliant.” WRONG! Running a SCPF is NOT even compatible - it is disruptive and should not be connected.
I see article is by DavidGuo (Dragino?) and he states:
" If you have any problem with this project,you can connact (sic) us by support@dragino.com or post the problems on the TTN forum (Special thanks to @CurlyWurly)."
By almeans hassle David and the Dragino support team, they shouldn’t perpetuate this stuff (ok, so it is a VERY old article and may not be possible to take down - the Ref to changes in “January” called out goes back to start of 2016 not currently 2022! or the recent V2 to V3 (TTS-CE) changes and I believe reflects transition from TTN V1 (Croft) to V2 but do not askhereas SCPF & DCPF are no longer supported on the TTN Forum!(3years +). (I suspect Pete would also disown now with what he now knows about LoRaWAN today )
TL::DR Get a LoRaWAN GW, try again and come back if you are then still having problems
p.s. you can turn your SCPF into a node, even if not battery friendly, so not a complete waste…
Ok, not clear or obvious from OP - comments wrt original article stand for anyone reading later!
I would point out that as noted this article is from 2 generations prior, near 6 years old and so in context VERY old so good chance it is drastically in need of update to reflect V3 TTN - not least use of suitable LoRaWAN libraries for use with the node to play nicely with the TTN NS… suggest update starting point and grab recent library for LMIC etc. Again and as always Forum search is your friend…
Update: I checked and the shield .ino is 6 years old grab an update…
No, no you didn’t, not even a little bit, you linked to an Instructable dated Mar 30th, 2016 that clearly states in its opening paragraphs:
Over here,we will use the Lora Shileld,MEGA2560 and Raspberry Pi to build a single channel LoRaWAN gateway.
LoRa Technology is a wireless modulation for long-range, low-power, low-data-rate applications. By achieving a range of more than 15 kilometers in a suburban environment and more than 2 kilometers in a dense urban environment, LoRa technology solutions target multiple application domains, such as Internet-of-Things (IoT), metering, security, and machine-to-machine (M2M).
This single channel LoRaWAN gateway is a proof-of-concept implementation,that can be used for development and node testing. It is not a replacement for a real multi channel/multi SF gateway! It supports some LoRaWAN features, but due to its static nature (single channel) it is not fullyLoRaWAN compatible (and will never be).
By default it works with the TTN backend, for testing and development.
If you’ve suddenly magic’d up a WaveShare Gateway concentrator HAT since then, please be honest enough to say so - we are all volunteers here and moving the goal posts on a topic is a waste of our time.
Granted the Ebyte part called out in Thread title, but no specific call out of its use (and links/instructions thereto), rather the implication that you were following the article and simply amending the packet forwarder on the SCPF to use the one from Git as used for the Ebyte part!, sorry.
Appeal to forumites & posters; help us help you by including all relevent information and background and explicit call out of what you are using - hardware & software/libs etc. to avoid such confusion
Done to death now so key is update your node lib, clue was in the LMIC lib you linked to (via the article) where you will see…
" This repository is no longer maintained. The recommended alternative is the MCCI version of LMIC, which is based on this one, but has seen much improvements over the years, has much better documentation and is mostly a drop-in replacement."
)