@Lauwie007

There are legal limitations imposed on us what we can commercially offer - but that might change in the future. However, then we also probably need to change the commercial offering of the public APN, because it’s basically raw connectivity what you would source from us.

As said the public APN is for TESTING ONLY. We are not planning on closing it down any time soon, but maybe we might at one point. So we cannot guarantee a continuity of this APN forever. Most likely it would change if we can commercially offer it at one point! Maybe it make sense if we have a quick call about it so I understand your requirements a bit better.

We have a partnership for NB-IoT with A1 Slovenija in Sovenia, so this was not intentional and will be fixed.
My previous suggestion unfortunately does not work properly, so contacting us directly is the best way to order in this case.
Sorry for the confusion.

Should be fixed now!

@florian-duecker I’ve revolved the issue by using the off the shelf OpenVPN option T-Mobile offers: Summarized for others&future:
The IoT Easy Connect LTE-M connectivity assings a private IP-range (in my case 10.42.242.0/24) to the sim-cards.
The IoT Easy Connect Portal>Settings>OpenVPN describes how to setup an OpenVPN connection to T-Mobile.
Activating this tunnel on my server enabled me to ping the devices and to carry out various connectivity test.

@Lucas05: I’m sorry, but I don’t really understand the question. What do you want to know? Are you asking if LoRa and Sigfox are the same? The answer to this is: no, not at all. Yes, both are providing LPWAN connectivity, but the technology and business models behind it are quite different.

If you are interested to learn more about this, you can find a detailed comparison of the technologies (+ NB-IoT) here: https://iot.telekom.com/resource/blob/data/492968/e396f72b831b0602724ef71056af5045/mobile-iot-network-comparison-nb-iot-lorawan-sigfox.pdf

I hope that helps :)

Florian

@florian-duecker That’s great. Thanks!

@florian-duecker test123 :)

edit: works

@MarPi said in Using NB-IOT for citizen-science:

Right - not right…to high - to low? It always depends. Which value exactly you doubt?
Or maybe there is a chance to improve your values?

The difference between nonIP and UDP is more than factor 2. The difference between nonIP and nonIP with RAI is negligible. This makes no sense. I suspect you used RAI for both nonIP cases?

To be fair, UDP + RAI will be in the area of fourhundred something.

I have achieved around 70 uWh (or 0.070 mWh) using nRF9160 using NB-IoT, UDP + RAI. 400 seems pretty high.

Hey @afzal_m,

Thanks for explaining. This helps.

Please consider making this a protocol when sending out emails about service interruptions (planned or not).

And please let us know what will happen with the sent data: Will devices need to send it again or will it arrive at our application after the update was successful?

Once we know this, we can tell our customers what to expect and how to act on degraded functionality,

@David-Thales I’m really looking forward to that!

@Stefan-de-Lange the PCBs for testing are open on Attribution-NonCommercial 4.0 International (CC BY-NC 4.0).
https://www.akoriot.com/akoriot_akor4range_l/
You have the freedom to copy it and re-measure it. But you will get the same result. Sometimes NB-IoT is better and sometimes LoRaWAN. You should also read before you judge something.