Hello all!
I would like to ask if there is way to customize LoRa frequency plan in case of private TTN backend deployment.
From what I understand, for EU region LoRa Specification introduces 3 basic frequencies (868.1, 868.3 and 868.5), and the rest of channels may be chosen by the user. I also understand, that TTN provides common Frequency Plans that should be used in TTN community network. However, I believe that user deploying private TTN backend may provide his own plan (as long as it’s compliant with LoRa specification and rules of ISM band).
Could you be so kind to recommend best way to configure TTN to work with custom frequency plan?
I tried to find way to configure other channels, but it looks like additional channels on CFList are hard-coded in TTN source - do I need to compile code with custom value, or maybe I’ve missed some configuration option?
Compiling a custom binary is probably the easiest solution for now. We’ve had more requests like this, so in our v3 backend it will be easier to use custom channel plans.
We’re currently working hard on laying the groundwork for v3, which will be a full rewrite of our existing functionality, incorporating all the lessons we learned from our previous versions.
Our planning is to publish that some time this quarter, after which we’ll rely on open source contributors to help us in getting it ready for release. It’s therefore hard to give an estimate for a release date, it all depends on the help we get from you guys
I really look forward for some news about v3 - good to know it will be published soon!
Actually, I would like to add some additional questions regarding to that topic:
Are you able to say what part of total functionality may be ready in moment of publishing - so also how much will have to be done by contributors?
What version (v2 or v3) would you use on production (and recommend to others) after publishing v3, but before releasing it?
Would you keep v2 code on github after v3 will be released?
However, I would be glad to talk about this in some dedicated topic if there is one - I can also create one if you think it’s a good idea.
We will make the announcements around v3 at The Things Conference (see thethingsconference.com). Until then we’re trying to spend as much time as possible on development, so I think it’s better to not start a (time consuming) discussion right now.
I don’t think we should set expectations right now. We are doing our best to spend as much time on it as possible, but there are always other things that come in between.
Until v3’s official release, I wouldn’t recommend it for production use, but I do expect it to be ready for development/test installations.
Yes, just as our previous versions can still be found on Github, we also plan to keep our v2 code accessible.
Maybe that would be great to have a public beta deployment (along the stable one) to be able to test it easily (be more to test) and report bugs and missing features?
