Issues with class C device about iotedge-lorawan-starterkit

[jsaez868]

We've resolved it

[ronniesa]

Out of curiosity what was the solution so it may help others?

[jsaez868]

Nothing too creative - just restarted everything and including clearing redis cache =)

A couple of follow up questions unrelated - if we needed to support a new region, where would be a good starting point? and what are all the different components we have to implement? Secondly, is the NetworkSrvModule compatible with the TTN packet forwarder?

[ronniesa]

Glad that it worked out.

What frequencies/regions you would like to add? As you know currently we support EU and US only mostly due to testing challenges.
We can provide some guidance on which classes you would need to modify to support other regions.
The first step for a new frequency/region is to test as is with the right packet forwarder and config settings and use ABP, no ADR and only unconfirmed up messages, as this does not require any down stream communication it should work out of the box. Once you get this you need to implement the settings in the classes that we can guide you through to get down stream communications that will enable OTAA, downstream messages, acknowledgement, ADR etc...
If you want to go this route we can support you a bit so hopefully you can PR back the changes so we can support other regions.

NetworkSrvModule is compatible with the Semtech Packet Forwarder, as basically almost all gateways ssupport this or have a forked one they works with our NetworkSrvModule. Never tested with the TTN one but I believe they have some particularities to communicate with their network server so I doubt it will work.

[jsaez868]

We're looking to support AS923 region. We've already tested the kit and we see upstream messages getting to the hub. The issue we're running into now is with downstream messages - they're not reaching the device. Please provide guidance on what we need to implement in order to fully support this new region.

For downstream messages from an ABP class C device, how would the NetworkSrvModule resolve which region to use? Do we have to set any device twin info?

Thanks.

[ronniesa]

Let's move the conversation here: #225
As said we can help you a bit @Mandur in my team owns the regions parts

We infer the frequency by the upstream message. So as with others NtwSrv a Class C needs first to send an upstream messagee or a join.