I’ve read a lot info that single channel GW or packet forwarder is not good options and it not worth to build it.
But there is different situations and projects where you dont need use 8+channels devices and you JUST NEED to have ability manually, time-to-time, send data from LoRaWAN-compatible devices to LoRaWAN network.
In this case you would need just simple packet forwarder that receives data via LoRa and transfer it to Network Server.
Am i wrong?
So - Im looking for way to configure RPI4 +Ubuntu 24.04 + Waveshare SX1262 LoRaWAN HAT to use it for packet forwarding to Chirpstack which is installed on the same RPI.
I use this LoRa Packet Forwarder for Linux
And it works for Node which run examples for simple LoRa - GW log shows the data transmitted from Node:
but when I use code (in my case CubeCell + Radiolib) which implement LoRaWAN stack - this GW just doesnt hear it…
And this is strange to me - as far I understand - Node and GW should work regardless of LoRa protocol level - RAW LoRa or LoRaWAN…
I use the same radio modem settings and settings for GW - but they cant communicate.
I sent questions to both maintainers of these projects but so far no results…
@d00m now this is information that you did not share on the RadioLib topic - yes, I am one and the same as the RadioLib maintainer - the main challenge of a single-channel gateway is that your gateway can only listen on one channel, one datarate. On the other hand, RadioLib cycles through a set of channels on default datarates.
Recently, an official single-channel ‘hub’ specification has been launched which is not yet available in RadioLib, but you are welcome to send in a PR for this EU868 single channel plan. Then if you also set the same datarate as your gateway is using, you should just be able to get it working.
But please, pretty please, provide any and all available information right from the get-go, as this is crucial in solving the problem at hand. So also share this setup on the RadioLib topic.
yes, I decided not to share details about GW because of two reasons.
One - to not clutter my question with a lot of info and second, which more important - to check first the “Node side” config and make sure that this side of my env works as expected.
But I was wrong this time and it was better to add all info.
Anyway it seems that now I understand why it doesnt work - because Cubecell with LoRaWAN firmware sends data via set of different channels but GW listen only one channel.
It is very clear now and I wonder why I didnt guess this…
hope that it will work with this “official single-channel ‘hub’” when it will be ready.
And sure I will update my RadioLib topic.
The art of supplying the right amount of information indeed is a tricky one - generally, whenever you do something slightly non-standard, it is best to share more details than fewer.
I hope to give the Single Channel stuff a go in a few weeks time (there’s a short holiday in ~3 weeks here), it should be relatively easy to setup and integrate.
thank you! but are there some examples how to do it?
especially stuff about MQTT server - Im still dont understand what the purpose of this component.
but I want to use LoRaWAN libraries (foe example - RadioLib) for Nodes firmware - I want to use the same code for RFM95 based devices and Cubecell’s so they can communicate with same GW.
Also - will Chirpstack Network Server work with this variant?
