Sim7020 - Revision history

Bertrik Sikken: /* Support in my LoraLuftdatenForwarder */

2022-08-18T23:04:53Z

Support in my LoraLuftdatenForwarder

← Older revision		Revision as of 23:04, 18 August 2022
Line 109:		Line 109:
	Data messages always have one report, with resourcepath set to "uplinkMsg/0/data".		Data messages always have one report, with resourcepath set to "uplinkMsg/0/data".

	=== Support in my ~~LoraLuftdatenForwarder~~ ===		=== Support in my sensor-data-bridge ===
	I've added preliminary support for this, see:		I've added preliminary support for this, see:
	https://github.com/bertrik/sensor-data-bridge/tree/master/sensor-data-bridge/src/main/java/nl/bertriksikken/nbiot		https://github.com/bertrik/sensor-data-bridge/tree/master/sensor-data-bridge/src/main/java/nl/bertriksikken/nbiot

Bertrik Sikken: /* Support in my LoraLuftdatenForwarder */

2022-08-18T22:50:54Z

Support in my LoraLuftdatenForwarder

← Older revision		Revision as of 22:50, 18 August 2022
Line 111:		Line 111:
	=== Support in my LoraLuftdatenForwarder ===		=== Support in my LoraLuftdatenForwarder ===
	I've added preliminary support for this, see:		I've added preliminary support for this, see:
	https://github.com/bertrik/~~LoraLuftdatenForwarder~~/tree/~~nbiot~~/~~LoraLuftdatenForwarder~~/src/main/java/nl/bertriksikken/nbiot		https://github.com/bertrik/sensor-data-bridge/tree/master/sensor-data-bridge/src/main/java/nl/bertriksikken/nbiot

	== References ==		== References ==

Bertrik Sikken: /* What */

2021-05-02T13:47:31Z

What

← Older revision		Revision as of 13:47, 2 May 2021
Line 8:		Line 8:

	== What ==		== What ==
	This page is about the SIM7020 NB-IOT ~~module.~~		This page is about the SIM7020 module and using it to send data through the NB-IOT network

	I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).		I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).
	~~The t-mobile portal at http://portal.iot.t-mobile.nl is dead.~~ Use the [https://portal.iotcreators.com/ iotcreators] portal.		Use the [https://portal.iotcreators.com/ iotcreators] portal.

	Status:		Status:
	* I can send data from the SIM7020 to the network		* I can send data from the SIM7020 to the network
	* I can receive the data from the network in my ~~own~~ application, using the webhook		* I can receive the data from the network in my Java application, using the webhook

	Next steps:		Next steps:

Bertrik Sikken: /* Receiving data from the device */

2021-04-03T08:05:47Z

Receiving data from the device

← Older revision		Revision as of 08:05, 3 April 2021
Line 75:		Line 75:

	=== Receiving data from the device ===		=== Receiving data from the device ===
	~~First of all~~, a ~~comparison~~ to how ~~things work with~~ TheThingsNetwork:		I'm using the so-called 'custom integration', which is based on a [https://en.wikipedia.org/wiki/Webhook web-hook]
			This means that I have configured an URL in the iotcreators dashboard.

			When a message from my node comes in, the CDP sends a HTTP POST containing a JSON message to that specific URL and port.
			The URL is a server under my control that has an HTTP REST-JSON service running and can process it further.

			This is a bit different from how (for example) TheThingsNetwork works:
	* TTN publishes incoming data using MQTT		* 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.		* 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.		* 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.		* 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, I think this is called a [https://en.wikipedia.org/wiki/Webhook web-hook]:~~
	* In the t-mobile dashboard you configure an "endpoint". When data comes in, t-mobile pushes data towards that using a HTTP POST.
	* 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.~~

	~~How I'm making this work:~~
	* I have a service running on a specific port on a VPS, with a Java REST API behind it (based on jersey)
	* I enter the URL of the service, including the port, into the iotcreators dashboard.
	~~If the service is not actively running at that time, this will trigger an error message in the dashboard, but the URL is still accepted.~~

	Incoming data received by HTTP POST looks like this:		Incoming data received by HTTP POST looks like this:
Line 112:		Line 107:
	</pre>		</pre>

	Data messages always have a report, with resourcepath set to "uplinkMsg/0/data".		Data messages always have one report, with resourcepath set to "uplinkMsg/0/data".

	=== Support in my LoraLuftdatenForwarder ===		=== Support in my LoraLuftdatenForwarder ===

Bertrik Sikken: /* Software */

2021-04-03T07:37:36Z

Software

← Older revision		Revision as of 07:37, 3 April 2021
Line 64:		Line 64:

	== Software ==		== Software ==

			=== Network setup ===
			See:
			* https://docs.iotcreators.com/docs/general-settings for general network settings
			* https://docs.iotcreators.com/docs/_-2-attach-to-nb-iot-network for specific AT-commands

			Things that need to be configured for the network and the backend:
			* network: band (8), operator (20416), APN (cdp.iot.t-mobile.nl)
			* backend: UDP server ip (172.27.131.100) and port (15683)

	=== Receiving data from the device ===		=== Receiving data from the device ===

Bertrik Sikken: /* References */

2021-04-01T14:19:57Z

References

← Older revision		Revision as of 14:19, 1 April 2021
Line 113:		Line 113:

	* Ordered a SIM7020 and a starter kit, see https://www.hackster.io/voske65/arduino-nb-iot-with-sim7020-and-t-mobile-027f8f		* Ordered a SIM7020 and a starter kit, see https://www.hackster.io/voske65/arduino-nb-iot-with-sim7020-and-t-mobile-027f8f
			* Regional settings for the network: https://docs.iotcreators.com/docs/general-settings
	* t-mobile IOT configuration page: https://portal.iotcreators.com/ ?		* t-mobile IOT configuration page: https://portal.iotcreators.com/ ?

Bertrik Sikken: /* What */

2021-03-25T12:41:13Z

What

← Older revision		Revision as of 12:41, 25 March 2021
Line 12:		Line 12:
	I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).		I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).
	The t-mobile portal at http://portal.iot.t-mobile.nl is dead. Use the [https://portal.iotcreators.com/ iotcreators] portal.		The t-mobile portal at http://portal.iot.t-mobile.nl is dead. Use the [https://portal.iotcreators.com/ iotcreators] portal.

			Status:
			* I can send data from the SIM7020 to the network
			* I can receive the data from the network in my own application, using the webhook

	Next steps:		Next steps:

Bertrik Sikken: /* What */

2021-03-22T08:56:50Z

What

← Older revision		Revision as of 08:56, 22 March 2021
Line 11:		Line 11:

	I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).		I want to experiment with this kind of network connectivity for either a bat activity monitor or air quality monitoring (particulate matter).
			The t-mobile portal at http://portal.iot.t-mobile.nl is dead. Use the [https://portal.iotcreators.com/ iotcreators] portal.

	~~The t-mobile portal at http~~:~~//portal.iot.t-mobile.nl is dead. Use the [https://portal.iotcreators.com/ iotcreators] portal.~~		Next steps:
			* find an Arduino library for this
			** what things need to be configured? put these in EEPROM?
			* think about encoding data
			* start sending data!

	== Hardware ==		== Hardware ==

Bertrik Sikken: /* Receiving data from the device */

2021-03-18T15:51:59Z

Receiving data from the device

← Older revision		Revision as of 15:51, 18 March 2021
Line 93:		Line 93:
	}		}
	</pre>		</pre>

			Data messages always have a report, with resourcepath set to "uplinkMsg/0/data".

	=== Support in my LoraLuftdatenForwarder ===		=== Support in my LoraLuftdatenForwarder ===

Bertrik Sikken: /* Receiving data from the device */

2021-03-18T15:51:11Z

Receiving data from the device

← Older revision		Revision as of 15:51, 18 March 2021
Line 64:		Line 64:
	In my opinion, a very good match to the nature of the messages in such a network.		In my opinion, a very good match to the nature of the messages in such a network.

	NB-IOT uses a different approach, I think this is called a [https://en.wikipedia.org/wiki/Webhook]:		NB-IOT uses a different approach, I think this is called a [https://en.wikipedia.org/wiki/Webhook web-hook]:
	* In the t-mobile dashboard you configure an "endpoint". When data comes in, t-mobile pushes data towards that using a HTTP POST.		* In the t-mobile dashboard you configure an "endpoint". When data comes in, t-mobile pushes data towards that using a HTTP POST.
	* 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.		* 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.