KPN LoRa Developer Portal

  • 22 September 2016
  • 30 reacties
  • 30443 keer bekeken
michieljol
Rank
Reputatie 2
Badge +1

Getting started with the free KPN LoRa developer portal


The LoRa developer portal was built to enable developers free access to the KPN LoRa network. This portal allows testing with up to 10 devices for a period of 6 months.
The developer portal can be used for testing with Class A Activation-By-Personalisation (ABP) and Class A Over-The-Air-Activation (OTAA) devices. Note that on the KPN live network, only OTAA devices are allowed and it is thus recommended to start developing with OTAA right away.
All a developer has to provide is a forwarding address (endpoint) for the Application Server to get the device credentials (DevEUI, AppSKey and NwkSKey, in case of an ABP device). Upload these credentials to your LoRa device and you are good to go.

Differences between ThingPark and the Developer Portal


The aim of the KPN Lora Developer Portal is to enable users to quickly connect their LoRa device to the KPN Lora network. Where possible, the functionalities and concepts similar to those used in ThingPark (the portal for contracted customers) are applied for using the Developer Portal. This means that a device and Application Server working with the Developer Portal should also work with ThingPark. But there are a few differences:
  • The NwkSKey and AppSKey are generated by KPN (as a consequence, device-clientserver encryption is not possible).
  • Only device Class A is supported.
  • The same processes, elements and formats are used where possible, however there will remain some differences with full-scale implementation on the KPN LoRa network.
  • The Developer Portal is provided based on 'Best effort' support. This means no direct support and no uptime guarantees.
  • The Developer Portal is meant for testing purposes, no commercial exploitation is allowed
  • Fair use policy applies, limited downlink and uplink capacity (average 6 uplink/hour, 2 downlink/hour)
  • A limited duration of 6 months applies. After 6 months, accounts are automatically locked
  • An important difference between the developer portal and the KPN live environment is that the restriction on the ports that can be used is not implemented on the developer portal. In the live environment port 443 should be used for forwarding messages.

More technical information can be found in the documentation on the developer portal itself.

30 reacties

Tim
Reputatie 7
Badge +11

  • Only device Class A is supported.

Is het nog steeds zo dat het Developer Portal alleen Class A ondersteund?

Nee, voor zover ik weet ondersteunen we momenteel Class A & C. Zowel op de productie omgeving als op de developer portal.
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
K
  • Only device Class A is supported.



Is het nog steeds zo dat het Developer Portal alleen Class A ondersteund?
Martijn van der Plaat
Hi Tim,

I did a new test this evening.
You can see the packets in the screenshot. The screenshot also gives you the timestamp of the packets.


I also did an uplink test, and again ONLY this packet was received correctly and the packets from the screenshot not. I can even show you my proxy logging as a proof:
By reading the proxy logging I also discovered that my server time is one hour behind. I have to fix this.
So, please calculate +1 hour of the date/time you read below. (ps. Time= parameter from KPN is correct)

As you can see below I did two uplink test from the KPN dashboard to /kpnlora on the 16th of january; 13:24:27.295 and on 22:00:24.552.

nodered.searocket.io 213.154.238.21 - - [16/Jan/2017:12:24:27 +0000] "POST /kpnlora?LrnDevEui=0059AC00001811BD&LrnFPort=1&LrnInfos=null&AS_ID=XXXXXX&Time=2017-01-16T13:24:27.295+01:00&Token=XXX HTTP/1.1" 200 60 "-" "Jakarta Commons-HttpClient/3.1"

nodered.searocket.io 213.154.238.21 - - [16/Jan/2017:21:00:24 +0000] "POST /kpnlora?LrnDevEui=0059AC00001811BD&LrnFPort=1&LrnInfos=null&AS_ID=XXXXXX&Time=2017-01-16T22:00:24.552+01:00&Token=XXXXXX HTTP/1.1" 200 60 "-" "Jakarta Commons-HttpClient/3.1"

The screenshot from the KPN dashboard tells me that there were lora packets received on the 16th of january on; 20:55:01, 21:00:01, 21:05:02, 21:10:07, 21:15:07, 21:25:05, 21:30:01, 21:35:01, 21:40:02, 21:45:00

None of them showed up in my proxy logging.
1 Bijlage
Martijn van der Plaat
Hello Martijn, welcome to the LoRa Forum :)

However, these packets are not received at the given destination endpoint. (a node-red application server). I know this endpoint works because the same evening I also did some tests with the uplink test button in the developer portal, and those messages were successfully received in node-red.
Could you try and sent some (new) lora packets from the device to your application server? We already know your DevEui (from the image - thanks!). If you can let us know at what times the packets has been sent, we can try to look them up.

Well, I have a practical issue, the packets you see in my screenshots are transmitted during my car trip yesterday evening. The timestamps in the screenshot are correct.
From home I don't have enough signal to the closest KPN antenna...

Since you now have my DevEUI, is it an idea to do the same car trip this evening so you check the log tomorrow or don't you save any logging.. I can't do a car trip during the day...
Tim
Reputatie 7
Badge +11
Hello Martijn, welcome to the LoRa Forum :)

However, these packets are not received at the given destination endpoint. (a node-red application server). I know this endpoint works because the same evening I also did some tests with the uplink test button in the developer portal, and those messages were successfully received in node-red.
Could you try and sent some (new) lora packets from the device to your application server? We already know your DevEui (from the image - thanks!). If you can let us know at what times the packets has been sent, we can try to look them up to see what's going wrong.
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
Martijn van der Plaat
Hi KPN,

I succesfully receive lora packets witin the developer portal, as you can see in the added screenshot.



However, these packets are not received at the given destination endpoint. (a node-red application server). I know this endpoint works because the same evening I also did some tests with the uplink test button in the developer portal, and those messages were successfully received in node-red.
In my proxy logging I see the POST messages of the uplink test but NOT the lora packets from the developer debugger. Therefore, I almost certainly know the KPN source did not automatically forwarded the lora packets to my application server.

Can you help me in troubleshooting this problem?
1 Bijlage
Tim
Reputatie 7
Badge +11
Hi Tim,
It was down till ~10:00 this morning.
Someone must have kicked it.
It's back up again.
tnx
Pim
Thanks for your reply, good to hear it's up and running again. I'll try to find out what was causing this down time! 😞
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
P
Hi Tim,
It was down till ~10:00 this morning.
Someone must have kicked it.
It's back up again.
tnx
Pim
Tim
Reputatie 7
Badge +11
Hello,
It appears the developer portal is down.
https://loradeveloper.mendixcloud.com/index.html does not produce any response, no login request, etc.

Pim
Hi Pim, I can login to the developer portal. I'm not sure if there was any down time this weekend. Do you also have access again?


Hello

for a project, I am interested in getting on touch with developers familiar with KPN LoRaWan as well as the development of IoT applications.

If interested, please contact me on my email : ensamine@gmail.com

Cheers

Amine
Hello Amine, I've noticed you also posted a call-up in another thread. Maybe it's better to create a new topic to get a better scope on your post!
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
Amine Mouadden MBA
Reputatie 1
Badge
Hello

for a project, I am interested in getting on touch with developers familiar with KPN LoRaWan as well as the development of IoT applications.

If interested, please contact me on my email : ensamine@gmail.com

Cheers

Amine
P
Hello,
It appears the developer portal is down.
https://loradeveloper.mendixcloud.com/index.html does not produce any response, no login request, etc.

Pim
Tim
Reputatie 7
Badge +11
Hello Guus,

The developer portal supports only DevEUI’s provided by KPN (for technical reasons). The commercial service allows for the use of your own DevEUI’s or those provided by hardware manufacturers.
The DevAddr will always be provided by the KPN network (in both ABP and OTAA situations).
I think you’re referring to OTAA devices, this is unfortunately not possible to test yet on the Developer Portal. We’re working on a version where OTAA is also supported.

If you want to develop a commercial Lora service and need to test OTAA devices, please contact iot@kpn.com to discuss the possibilities.
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
G
I have registered for the developer portal but most of the lora devices I have seen, do not have an option to change de devEUI. In de dev portal the only option was the provided keys AND devEUI by KPN. Also have no problem to register for a commercial service if those options are available..

Did I overlook something? What commercially available devices support to programm your own devEUI?
michieljol
Rank
Reputatie 2
Badge +1
@Robbrecht: Thank you for your message. Although I cannot see anything wrong right now I will forward your message to the technicians.
E
It's working. Before that the portal responded very slow before giving a login failure, so a memory probleem seems likely. Last time the service also stopped working in a weekend from saturday to sunday. Maybe a weekly scheduled job that causes a memory overrun?
michieljol
Rank
Reputatie 2
Badge +1
All, there was a memory problem somewhere which we are monitoring now. Right now, however, we cannot reproduce a problem at our side. Is the portal still not working at your side?
E
@michieljol Developer portal seems down again. Did you get a chance to look into the reason why it stopped working last week?
michieljol
Rank
Reputatie 2
Badge +1
Hi all,

We have done a reset and everything seems to work again. We will try to figure out what went wrong in the meantime.

Cheers,

Michiel
michieljol
Rank
Reputatie 2
Badge +1
Hi All, I have the same problem myself. Will check what's going on.
E
The same problem here. Sign in failed on the developer portal. Also this account was activated < 10 weeks.
abksheemskerk
@michieljol i got access to the developer portal through a workshop from the IOT acedemy, but now im not able to sign in anymore. It has only been 2 weeks ago since i made the developer account so i was wondering what was going on. I cant login or reset my password, making a new account is also not possible. Is there something wrong on the KPN side or have you terminated my account?
Tim
Reputatie 7
Badge +11
@michieljol
Is there a description somewhere of each of these properties what data they contain?

Hi mikenahh,

We've posted a new topic with all properties explained.
You can find the topic here: LoRa | Dictionary & Definitions.
Met vriendelijke groet, Tim | - Blij met een reactie? Met een Like geeft u waardering! -
M
@michieljol
Is there a description somewhere of each of these properties what data they contain?
code:

{
    "LrrSNR": "0",
    "Lrrid": null,
    "SpFact": 0,
    "SubBand": null,
    "CustomerData": null,
    "FPort": 1,
    "Channel": null,
    "FCntUp": -1,
    "Time": null,
    "DevEUI": "0059AC00001811D8",
    "payload_hex": "000000",
    "CustomerID": 0,
    "LrrRSSI": "0",
    "ADRbit": 0,
    "ModelCfg": 0,
    "mic_hex": null,
    "LrrLON": "0",
    "LrrLAT": "0",
    "FCntDn": 0,
    "Lrcid": null,
    "DevLrrCnt": 0
}
M
@michieljol

Thank you for the quick response, i tested it and now it works.
michieljol
Rank
Reputatie 2
Badge +1
Hi MikenAhh,

Seeing your payload I suspect you are using the Microchip RN2483 to send LoRa data. It so happens that I have some experience with it so I know what is going on. You are sending to LoRa port 88. The LoRa Developer Portal only supports sending on port 1. Any other port will result in encrypted data and cannot be guaranteed to arrive.

Please use
code:
mac tx uncnf 1 30
.

Michiel

Reageer


Forumvoorwaarden