Go Down

Topic: Connecting to Private Network via OTAA (Read 364 times) previous topic - next topic

AlexSneedMiller

I am trying to connect my MKR-WAN-1300 to a private LoRa network that I have at my location.

According to the documentation, if I have my network set up with a EUI and password I should be able to just call modem.joinOTAA("network_EUI_goes_here", "network_password_goes_here"). However, I am getting failures back from that call.

I spent some time and dug into the MKRWAN.h file and think I have pin pointed the problem. When the function set(APP_EUI, appEui) gets called on line 279 of the MKRWAN.h file the AT command that goes out is AT+APPEUI=MY_NETWORK_NAME, but the response back from the Murata CMWX1ZZABZ is just "+ERR"

Anybody have any ideas why that's giving an error back?



I've been trying to find some good documentation about the AT command set, but have been only able to come up with this one and I'm not sure if that's even correct: http://www.st.com/content/ccc/resource/technical/document/application_note/group0/db/8c/4f/5a/95/9e/40/69/DM00346311/files/DM00346311.pdf/jcr:content/translations/en.DM00346311.pdf

Marco_Benini

I suppose that is a private LoRAWAN network.
What is the format and size of the application EUI and application key?

Application EUI has to be a 8 hexadecimal values, if You have a shorter one than You need to add "00" at the beginning.
For example "00AABBCCDDEEFFAA"

Application key is 16 hexadecimals.

horace

does it work OK connecting to The Things network?

Marco_Benini

I used MKR 1300 WAN with the The Things Network in Europe (868 MHz) with the MKRWAN library.

One has to get the device EUI from the MKR 1300 in order to register the device on a TTN application.

The join, with the gateway not far away, is made at spread factor 7 / 125 KHz, but messages (uplinks) are instead made at SF12 (unfortunately).

I have also to find a way to store the session parameters (join data, frame counter, ...) so to use after sleep.
It is bad practice to make a new join every time one has to send a message.

horace

you could use an SD card or an FRAM to store your data

Marco_Benini

#5
Apr 13, 2018, 02:18 pm Last Edit: Apr 13, 2018, 02:19 pm by Marco_Benini
An addendum to my previous post.
I updated to firmware of the Murata chip to version 1.1.5 before testing with TTN.
One of the MKRWAN library examples allow to update the firmware with a pre-compiled version.

Firmware Github project "mkrwan1300-fw" can be found here: https://github.com/arduino/mkrwan1300-fw

AlexSneedMiller

I updated my private network gateway to have a hex EUI and hex password. I am seeing the AT commands working for setting the mode to OTAA and setting the EUI and password. Then the AT+JOIN goes out and OK comes back.

Is there any more debugging we can get from the Murata chip?

AlexSneedMiller

An addendum to my previous post.
I updated to firmware of the Murata chip to version 1.1.5 before testing with TTN.
One of the MKRWAN library examples allow to update the firmware with a pre-compiled version.

Firmware Github project "mkrwan1300-fw" can be found here: https://github.com/arduino/mkrwan1300-fw
I was able to update the Murata firmware to version 1.1.5, but I was still not able to get it to connect to my network.

My gateway has one dedicated rx channel (right now set to "7"). It sounds like the standard is for 64 channels, but the gateway just does a modulo/7 operation to trim the 64 channels down to 8 (0-8)

Do you know if there is a way to configure the Murata chip to connect only one on channel?

Marco_Benini

Most LoRa gateways in the market are 8 channels.

Using OTAA, if I remember well, it should the gateway that says the end node the frequencies plan to use, but I could be wrong.

Are You sure that the join process arrives to the end? Are the paramenters in the MKR1300 written in their registers?

Go Up