i’m using RAK811 firmware v2.0.2.2 EU868
all work as expected using TTN and class A mode.
but i can’t successful use the class C. TTN announced that stack v3 is working with class C.
the only think i do to use class C is : “at+set_config=class:2”.
when i send a frame from TTN to my device, the frame stay “scheduled” and is used after some minutes, exactly same as class A !
please what did i wrong ?
did i need to config anything more on TTN console ?
or did i miss something on the RAK811 side ?
I am not completely sure, however TTN V3 is not functional in the Community Network.
Thus in order to use it you need to compile the repo with Docker for example.
It matters not if your device supports Class C, because TTN doesn’t at this point.
When they release it on the public network than we can play and see
By the way loraserver.io has support for both Class B and Class C.
So if you want to make tests with class C, at this point I would recommend you use LoRaserver instead of TTN.
thanks for the tips about loraserver.io …
i will try to test it ! but i’m not sur to know how to do it !
i have some RPI3, some local server and a LAIRD RG186 gateway only
are you sure that TTN class C is not usable now ? that was announced in the V3 stack, which is now released !?
what do you mean by “TTN V3 is not functional in the Community Network” …? not available for free ? or i need to compile myself the stack and run on my own server ?
Precisely what I thought. Both comments state that V3 is not commercially supported yet. They have been promising it for a long time, however is going to take a while, probably it is quite complex to do.
Thus for now your best bet is loraserver.io. I can help you with running it if you decide to go this route.
I hope you have a RAK gateway you can use for the setup? I myself am running loraserver.io on a RAK831 together with a mate of mine (he is the technical brains I am the idea guy). So perhaps I can help?
Ok so things are as follows:
We only have 2x RAK831, so the Gateway you have used we have no experience with. My more tech savvy mate will take a look at the documentation tomorrow and we will know more. At this point it looks as it runs some king of custom UI over Linux so we need to find out how we can access the CLI interface. It should be possible with some reading and trial and error.
However bare in mind you will eventually have a Gateway with a packet forwarder and a separate LoRa Server on a PC. The gateway will not be able to route packets unless the PC is always on. This is not an optimal setup. This is the nice thing about the RAK831, it has a Raspberry Pi 3B+ built-in, which can run the whole LoRaServer stack and always be on.
Will let you know how things go tomorrow, hopefully we got good news ) @Fomi@velev
For now using class c is a bit tricky :D, not impossible.
Your Gateway, the LAIRD RG186 comes with LoRa Gateway-bridge preinstalled after version 93.7.2.9. You can read more about it here LAIRD Lora Gateway-bridge. This means you only need to connect it to the MQTT broker.
In case you really want to try working with the TTN V3 stack, at least for now you have to do it on a local server (the cloud platform does not support it yet). You can find the repository for it and a tutorial in this link TTN V3
And as you can probably already see, that is why the RAK831 is so popular. You can run it all locally since it uses an RPi at its core. You can have the servers (LoRa or another type), we also run our database (we use InfluxDB as it is compatible with loraserver.io), graphical tools (we use Grafana), etc.
So lots of options to choose from. I myself went with everything on the gateway, perhaps you go another route and share your experience.
It is for anything supported, Linux based in general. Actually there is official support for your exact gateway. https://www.loraserver.io/lora-gateway-bridge/gateway/laird/
This is the official page guide. All the instructions apply for your gateway
Take a look, give it a try and if you get stuck we will try to help
You mean the *.rat.gz. I just downloaded it, used 7 zip to extract it and ran it in the CLI.
It runs, except that it can’t find the MQTT broker, which is expected as I have not installed one on the machines, as I mentioned my setup has all components on the Gateway.
Are you sure you downloaded the right archive?