Difference between revisions of "Sim7020"
|Line 72:||Line 72:|
== References ==
== References ==
Revision as of 14:39, 24 January 2021
|SIM7020 NB-IOT modem|
This page is about the SIM7020 NB-IOT module.
I plan to experiment with this kind of network connectivity for perhaps a bat activity monitor or air quality monitoring.
Update: this escalated quickly ... the NB-IOT stuff at t-mobile already seems dead: Chromium complained about an expired certificate for the https website, otherwise seems down (error 503).
bertrik@zenbook:~$ wget http://portal.iot.t-mobile.nl/ --2021-01-23 19:01:06-- http://portal.iot.t-mobile.nl/ Resolving portal.iot.t-mobile.nl (portal.iot.t-mobile.nl)... 22.214.171.124 Connecting to portal.iot.t-mobile.nl (portal.iot.t-mobile.nl)|126.96.36.199|:80... connected. HTTP request sent, awaiting response... 503 Service Unavailable: Back-end server is at capacity 2021-01-23 19:01:06 ERROR 503: Service Unavailable: Back-end server is at capacity. bertrik@zenbook:~$ wget https://portal.iot.t-mobile.nl/ --2021-01-23 19:02:35-- https://portal.iot.t-mobile.nl/ Resolving portal.iot.t-mobile.nl (portal.iot.t-mobile.nl)... 188.8.131.52 Connecting to portal.iot.t-mobile.nl (portal.iot.t-mobile.nl)|184.108.40.206|:443... connected. ERROR: The certificate of ‘portal.iot.t-mobile.nl’ is not trusted. ERROR: The certificate of ‘portal.iot.t-mobile.nl’ has expired. The certificate has expired
I wired it up like this:
|G||nc||looped to SIM7020-K|
|K||nc||looped to SIM7020-G|
Receiving data from the device
First of all, a comparison to how things work with TheThingsNetwork:
- TTN publishes incoming data using MQTT
- MQTT is a light-weight publish-subscribe framework that decouples producers of data from consumers of data. So for example you can easily have one producer (the node) and several consumers, for example a logger, a data handler, or even a 3rd party that does its own thing with the data.
- TTN runs its own MQTT server, so you don't have to. There's no need for setting up your own server, with a public facing ip address, a firewall, security policies, etc.
- MQTT distinguishes different types of message by different "topics", you can only access topics you are authorised to (your own). So for example, you can easily authorise someone to see device messages, but not allow device registration access.
In my opinion, a very good match to the nature of the messages in such a network.
NB-IOT uses a different approach:
- You configure an "endpoint" and t-mobile pushes data towards that
- The endpoint is your own server that has to be ready to ready to receive incoming data. You have to manage this server yourself w.r.t. security. If you want other parties to use the data, you'll also have to come up with your own solution to that.
So, not as smart as TTN does it, but still very powerful.
I followed roughly this guide:
- Ordered a SIM7020 and a starter kit, see https://www.hackster.io/voske65/arduino-nb-iot-with-sim7020-and-t-mobile-027f8f
- Account page: https://portal.iot.t-mobile.nl/auth/login
- Actual page: https://portal.iotcreators.com/ ?