Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no data on aplication #89

Open
navoraul opened this issue Aug 2, 2021 · 3 comments
Open

no data on aplication #89

navoraul opened this issue Aug 2, 2021 · 3 comments

Comments

@navoraul
Copy link

navoraul commented Aug 2, 2021

Hello, I send data from a RAK4600 , and I see in the console activity ok, but I do not see nothing in the aplication-device live data section.

I am using ABP activation in TTN V3

@navoraul navoraul closed this as completed Aug 3, 2021
@navoraul navoraul reopened this Aug 3, 2021
@cstratton
Copy link

cstratton commented Oct 2, 2021

I am using ABP activation in TTN V3

TTN explicitly prohibits attempting to connect single and dual channel fake gateways such as this to their servers

@Gilverton
Copy link

Please look at this solved issue Link
It is similar to what happened to you and did the trick in my case. ;)

@cstratton
Copy link

cstratton commented Feb 28, 2022

You are mistaken; there can be no software solution to the actual problem, because the hardware is simply not capable of doing the job of a gateway. LoRaWAN requires that a gateway simultaneously monitor 42 frequency and spreading factor combinations, but this device can only monitor one. When you try to use this, you create a misleading situation where a gateway exists for only one combination, but does not exist for any of the other combinations that a proper LoRaWAN node is not just allowed, but actually required to make use of.

This completely screws up the ADR algorithm for settings spreading factor, and the fair channel selection algorithm required not only by the LoRaWAN spec, but actually by law.

Worse, when you do this on a public network, your mess things up for other people's nodes, even if you're not noticing the problem on you own nodes that you may have rigged to violate the LoRaWAN spec and radio laws, but only using a single frequency and spreading factor.

TTN absolutely prohibits connection of single-channel devices in the gateway role, because there is no software fix that can ever make them actually work correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants