[wojtek t]

Thanks, so we are using the same hardware.
We already have the support case open #5078000

[wojtek t]

Bryan,
Let me ask you a question. Did you guys release new version of the lora radio with SPI instead of USB? If yes, are you using JIT or the version 1 protocol to communicate between the packet forwarder and your network server?
Anyway, i am glad that it works for you, so Yuqian should be able to get it going as well.

[wojtek t]

I will leave it to Yuqian to explain in details his testing methodology, but we take duty-cycle into consideration and he waits between subsequent requests.
Just to clarify, the server indicated successful join but the node reports denied, meaning that as you said the join confirmation message is not being delivered back to the node.

[wojtek t]

We did check the config on the Multitech server side, but we will make
sure that RN2483 is also set correctly (and we can also try with private
just to see how it will behave).
I would expect that Rn2483 is set properly as we can operate without any
problems with Kerlink and also no problem at all with actual
operators/network providers.

[wojtek t]

Jon,
It all makes sense, but we don’t want to operate as private network “mac set sync 12”. We are making some additional tests and it seems that the devil is in the new network server implementation from Multitech. Basically, the old and the new packet forwarders behave the same way if using a 3rd party Lora bridge and network servers. It more less works, indicating that the packet forwarder code is fine (as expected). More to come, as Yuqian is testing other combinations. On the RN2483 we use the latest RC…so we should be alright .

Wojtek

[wojtek t]

1.0.1 is the latest publicly available firmware on these modules…

[wojtek t]

Microchip is a single radio with a proper lora alliance approvals. We use it in our devices for both EU and NA without any problems except for this which again only present itself with Multitech…

[wojtek t]

Anyone from Multitech?

[wojtek t]

The proper start should be with 3 frequencies as Yuqian is doing. Then, through CFlist upon joining the radio will receive the list of additional frequencies from Conduit….but the problem is that his radio is timing out waiting for join confirmation ….

• This reply was modified 7 years, 3 months ago by wojtek t.

[wojtek t]

I can respond on Yuqian’s behave… he is testing it in OTAA mode…

[wojtek t]

Great,
Thank you
W

[wojtek t]

basic_pkt forwarder uses those ports for communication with the Network server,
so its SENDING packets out using those ports…unless you are referring to downlink which will only happen after you send a packet (class A)

[wojtek t]

Hi,
You always need a packet forwarder!
So, if you speak to TTN, you have a semtech bridge converting RF signal (Lora) to IP and packet forwarder sends it to the TTN LoraNetwork Server. If you use the server on your local conduit, its similar, except that you send it to the localhost for further processing. In case of 3rd party server, there is still no difference, you just agree on a port (udp 1700 for example) and configure your packet forwarder to speak on that port to your lora network server
Here is an example of 3rd party, http://loraserver.readthedocs.io/en/latest/

[wojtek t]

What is happening exactly?
I use this one and Polypacket forwarder on modified mLinux (to AEP) without any problems.

[wojtek t]

I posted instructions on my blog

https://iotblog.org/connect-aep-ttn-lorawan/
Enjoy

• This reply was modified 7 years, 11 months ago by wojtek t.
• This reply was modified 7 years, 11 months ago by wojtek t.

[wojtek t]

still plenty of room there, also I manually installed it and it worked just very, very slow. I think its unintentional, but we will know soon.
Thanks
Wojtek

[wojtek t]

You can add nodes manually, but npm is important due to dependencies and easy of use.
you can add npm manually, however it seems to be extremely slow. I believe it actually installs all dependencies for each node instead of checking for them globally. I have a ticket opened,…

[wojtek t]

very weird, but i am missing npm command after upgrade to 1.1.2….

[wojtek t]

“udp” : {
“allowPublic” : true,

Thanks 😉
Wojtek

[wojtek t]

Jason,
This is what I get with a browser:
{
“code” : 400,
“error” : “Error parsing URL JSON data [* Line 1, Column 2\n Missing ‘}’ or object member name\n]”,
“status” : “fail”
}

and this is what I get with curl:
admin@mtcdt:~# {
“code” : 400,
“error” : “path [loraNetwork] leads to an incompatible element. Path Element Type [OBJECT] Update Data Element Type [NULL]”,
“status” : “fail”
}

Again this is AEP version now upgraded to 1.1.2

[wojtek t]

Just for clarification, I am still on 1.0.33, so perhaps it will be available with the latest 1.2?
Wojtek

[wojtek t]

great,
However, I am having difficulty adding it on the AEP unit.

curl -m 5 -s 127.0.0.1/api/loraNetwork?method=PUT&data={“udp”:{“allowPublic”:true}}
returns unknown element.
and actually i don’t see it there:
admin@mtcdt:~# curl -m 5 -s 127.0.0.1/api/loraNetwork
{
“code” : 200,
“result” : {
“addressRange” : {
“end” : “FF:FF:FF:FE”,
“start” : “00:00:00:01”
},
“db” : “/var/run/lora/lora-net-server.db”,
“log” : {
“console” : true,
“level” : 100,
“path” : “”,
“syslog” : false
},
“lora” : {
“enabled” : true,
“frequencyBand” : 915,
“frequencyEU” : 869500000,
“frequencySubBand” : 7,
“maxTxPower” : 26,
“nodeQueueSize” : 16,
“rx1DatarateOffset” : 0,
“rx2Datarate” : 12
},
“mqtt” : {
“enabled” : true,
“host” : “127.0.0.1”,
“port” : 1883
},
“network” : {
“eui” : “02:00:….”,
“key” : “2b:7e……..”,
“leasetime” : 86400,
“name” : “”,
“passphrase” : “”,
“public” : true
},
“udp” : {
“appPort” : 1784,
“appPortDown” : 1786,
“appPortUp” : 1784,
“downstreamPort” : 1782,
“upstreamPort” : 1780
},
“whitelist” : {
“devices” : [],
“enabled” : true
}
},
“status” : “success”
}

Thanks
Wojtek

[wojtek t]

Anyone?

[wojtek t]

Brandon,
Could you please elaborate on how to configure it to listen on the public interface and not only on the localhost address?
Wojtek

[wojtek t]

I also experienced problems with Safari, switching to Chrome helped.
Also, it takes some time to start node-red, so if you are trying right after boot…
WT

[wojtek t]

Confirmed, system with only one sub-band enabled works smoothly and as expected.
Thanks
WT

[wojtek t]

Thanks Bryan,
This makes perfect sense, I will try tomorrow, however I already tried more than 8 times. Statistically, I should get lucky couple of times already…
I will report back.
BTW: my colleague has no problem with RN2983 which makes perfect sense…
WT

[wojtek t]

I have similar problem but with RN2903. ABP join works no problem but OTAA always times out. Basically, conduit indicates that successfully accepted join request, but RN2903 shows “denied”.

[wojtek t]

Brandon,
My result without antennas:

AT+PING
-101,11.5

OK
AT+RSSI
-93, -97, -93, -95

Can I assume that my module is alright?
Wojtek

[Author]

Posts