Data Sheets in Digital Sensor Twins

The LegalLab repository contains an example smart contract for creating digital sensor twins. This template, together with the LegalLab utility, has been updated to support uploading and presentation of data sheets for the underlying sensors being mirrored digitally.

The process of attaching such data sheets is straight-forward:

• Publish the new digital sensor template to your Neuron®, and get it approved.

• Create a smart contract based on this template, pointing to the sensor you want to mirror.

• Before signing the contract, upload any number of data-sheets appropriate for the digital twin. If these attachments are in the following formats, they will be presented together with sensor data from the sensor:

  • Plain text file (*.txt)
  • Markdown text file (*.md)
  • Image files (*.jpg, *.png, *.webp, and other supported formats)
  • Microsoft Word files, in the interoperable OpenXML format (*.docx)
  • Microsoft Excel files, in the interoperable OpenXML format (*.xlsx)
• Once data sheets have been uploaded, sign the contract accordingly.
• Once the token has been created, create a Present Report to view sensor data, together with associated data sheets.

Note: For performance reasons, it might be less resource-intensive and quicker to pre-convert MS Word files to Markdown, and upload the Markdown file.

Note 2: For security reasons, only files (actually Internet Content-Types) recognized by both LegalLab and the Neuron® will be accepted.

Note 3: To be able to upload and process Microsoft Word documents and Excel spreadsheets, you need to install the Microsoft Interoperability package. You can also check microsoft for more information related to Microsoft interoperability.

#new, #features, #contracts, #legallab, #sensor, #iot

Stockholm weather station for testing and development purposes

There’s a harmonized weather station of the Stockholm Weather available for anyone who needs to test or develop services that include sensor communication. The sensor is a bridge to the OpenWeatherMap API, and bridges incoming requests on XMPP to requests to the API, and back, live.

You can connect to it here:

Capabilities

Following is a brief list of some of the capabilities of the sensor:

• It contains momentary, identity, status, peak, computed and historical values, so it is suitable for testing different categories of data.
• It maintains a historical log of sensor data, so it can be used to test historical plots.
• It reports a variety of physical units: Speed, Time, Temperature, Distance, Angles, Pressure, Percentage.
• It reports a variety of field types: Numerical, physical quantities (i.e. numerical with precision and physical units), date and time, strings, links.

Authorization

The sensor will accept all connection requests, and all sensor data readout request, but will reject, by default, configuration requests. The owner of the node will receive notifications when someone wants to configure it, and may approve such requests on demand.

Setting up your own weather station sensor

You can setup your own OpenWeatherMap sensor, publishing weather station information for your location. Just follow the steps in the article Creating a harmonized and provisioned sensor for test.

#demo, #iot, #sensor, #api

Creating a harmonized and provisioned sensor for test

The OpenWeatherMapSensor repository contains a bridge between https://openweathermap.org/ and XMPP, and provides regular readouts, local storage of historical values, as well as harmonized interfaces for sensor data, control and provisioning. It can be used for testing purposes, or to introduce weather information into your smar city projects.

The sensor is provisioned, meaning it can be claimed by an owner. Access to, and authorization to read data (wholly or partially), as well as to enable or disable it, is controlled by the owner. You can use any client that supports IoT Harmonization to control the sensor. Examples include the TAG ID App, or the Simple IoT Client in the IoT Gateway repository. You can also access the sensor programmatically, via NuGets, as described in Mastering Internet of Things.

Download

You don’t need to clone and compile the OpenWeatherMapSensor repository repository to run the sensor on your machine. You can download it directly from the following link, and install it. Note that you may need to approve running the file on your machine, depending on what protection software you use: https://lab.tagroot.io/Downloads/OpenWeatherMapSensor/setup.exe

Configuration

Once the application is installed, it will run in a terminal window (it’s a console application). It will ask you for the following information in order. Correct information will be saved, and you will not be asked again. If you need to reconfigure the sensor later, you need to delete the Data folder that is generated in the folder of the application, and restart it.

Note: If running intro trouble during the configuration, you can always stop the console application using CTRL-Z, and resume where you left off, by running the console application again. You will find the application in the Start menu, under the name OpenWeatherMapSensorConsole.

API parameters

First, you need to provide information on how to connect to the API:

Open Weather Map API Key

You must get this API Key from https://home.openweathermap.org/api_keys, once you’ve created an account on their web page. Enter the API key when the app prompts you for it.

Location

This is the location you wish to publish weather for. It must be a recognizable location name, such as the name of the city you wish to get the weather from.

Country Code

This is the 2-letter country code in which the Location above is located.

Once these three parameters have been provided, the app will attempt to connect to the API and read data for the current location. If successful, the configuration will be saved, and you don’t have to enter it again. If not successful, you will be prompted to enter the information again.

XMPP parameters

The next step is to provide configuration for XMPP connectivity. The folllowing parameters have to be provided:

XMPP Broker

This is the domain name of the broker you wish the sensor to connect to.

Port

This is the port to connect to. (Application does not perform a DNS SRV lookup.). Default port is 5222.

User Name

The name of the account you wish to use.

Password

The password necessary to login to the account provided.

Once these parameters have been provided, the app will attempt to login to the XMPP network. If successful, parameters are saved, and you can continue. If not, you will be provided an opportunity to correct your entries.

Thing Registry

Next step is to provide locale-information for the Thing Registry. A Thing Registry is a service that allows the owner to find the device, and if the owner chooses to, also let other users find the device. The following parameters are optional, and are used when other users try to find devices of interest, based on location.

Country

Country code associated with device.

Region

Region (or state)

City

Name of the city

Area

Area within city.

Street

Name of street (without number)

StreetNr

Street number, including sub-numbering letters, etc.

Building

Building number

Apartment

Apartment number

Room

Room number

Name

Name associated with location

Ownership

Once the device has registered itself in the registry, it is time for you to claim ownership of the device. Ownership allows you to control who has access to the device, and what data they are permitted to read.

Ownership is claimed, by presenting the Thing Registry with exactly the same information as the device has presented to the Thing Registry. Apart from the information you’ve already entered, there are information about make and model, etc., as well as a secret key. To help you provide this information, the application presents you with a QR code, with all the information included. The QR-code is available in three different ways:

• First, it is presented using block-characters, in the terminal window. If your terminal window supports block characters, you can simply scan the QR code from there.

• The application also saves a Sensor.iotdisco text file in the installation folder. (You can find the installation folder, by simply clicking on the tab of the terminal window, and requesting to rename it.) Open this file in a text editor, and you’ll find the contents of the QR-code. If you’re a developer, you can paste this link manually into the app, to claim the device.

• There is also a Sensor.iotdisco.url file saved in the installation folder. Click it to open a tab in your browser, showing a QR-code. Scan this QR code with your app, to claim the device.

Note: When claiming the device, you have the option to let the device be public. This does not mean everyone has access to the data in the device, or can control it. It just means anyone with access to the Thing Registry, is permitted to find it. If they want to read data from it, you, as an owner, will be asked if this is OK before any data can actually be read.

Connecting to device

Once the device has been claimed, you, or anyone else, can try to connect to it using the XMPP Address (JID) created when the application connected to the XMPP network. The format of the JID is UserName@Domain, where the Domain is the domain name (or host name) of the XMPP broker.

You connect to the device, by subscribing to presence of the device. At first, this request will be rejected by the device. At the same time as the request is rejected, a notification is sent to the owner, who can manually choose to accept, reject or ignore the request. Once accepted, your application will either automatically connect to the device, or you will have to manually subscribe to presence again. This second time, after the owner has accepted the request, the sensor app will accept the request. This does not mean you can read it yet however.

Reading device

Once you’re connected to the sensor, and can see it is online (i.e you have its full JID), you can request to read the sensor-data from it. As earlier, the first request will be rejected, if no formal approval has been given before. The first attempt, will generate a notification to the owner, who can choose how to handle this request. The owner can choose to deny access, or grant access, either fully, or partially (i.e. only to partial content). The decision can be based on your network identity, or based on other principles. Once granted access, you can try to read again, and this time, you will get access to the sensor data in the device.

Chat

The sensor app also supports chat. Once you’ve added the device to your contacts list, you can chat with it to read sensor data, or perform control actions. Try sending hi, or # to it, via chat, to see what happens.

#iot, #api, #repository

Semantic Web technologies for real-time Web of Things

The following video is a recording of a presentation, where I introduce the new support for Semantic Web technologies in the TAG Neuron®, and how it can be used to query, join and consolidate information that is available in both external and local data sources (graphs), as well as real-time communication devices, such as sensors and actuators. The Semantic Web technologies presented are standardized by the W3C, so the solution (the only solution in the world?) provides a query language for stored and real-time information in a federated network that is 100% built on standards. No proprietary languages or APIs necessary, reducing costs and complexity of implementaton.

#new, #features, #tutorial, #semantic, #web, #iot

40 Simulated Modbus devices now online for test

40 simulated devices (mix of sensors, actuators and controllers) now available online, accessible via Modbus and XMPP (for comparison). They can be used for test, both of infrastructure, token generation, or interface via ID App, etc. The first 4 columns contain Modbus connection information. The three last columns, represents XMPP and 1451.99 connection information, using the concentrator avility to bridge procotols (in this case XMPP <-> Modbus). In XMPP and 1451.99 you can also address parent nodes directly. In Modbus, this representation is symbolic, as you only address registers directly. QR codes are be provided at the bottom. There’s also an import file that can be used to import references to the nodes on other development neurons, if this is of interest.

Modbus interface					XMPP interface
Host	Port	Device	Register	Description	JID	Node ID	Source ID
lab.tagroot.io	502	10		Outdoor temperature sensor 1.	lab.tagroot.io@tagroot.io	Outdoor__1	MeteringTopology
lab.tagroot.io	502	10	0	Outdoor temperature 1.	lab.tagroot.io@tagroot.io	Outdoor Temperature 1	MeteringTopology
lab.tagroot.io	502	11		Outdoor temperature sensor 2.	lab.tagroot.io@tagroot.io	Outdoor__2	MeteringTopology
lab.tagroot.io	502	11	0	Outdoor temperature 2.	lab.tagroot.io@tagroot.io	Outdoor Temperature 2	MeteringTopology
lab.tagroot.io	502	12		Outdoor temperature sensor 3.	lab.tagroot.io@tagroot.io	Outdoor__3	MeteringTopology
lab.tagroot.io	502	12	0	Outdoor temperature 3.	lab.tagroot.io@tagroot.io	Outdoor Temperature 3	MeteringTopology
lab.tagroot.io	502	13		Outdoor temperature sensor 4.	lab.tagroot.io@tagroot.io	Outdoor__4	MeteringTopology
lab.tagroot.io	502	13	0	Outdoor temperature 4.	lab.tagroot.io@tagroot.io	Outdoor Temperature 4	MeteringTopology
lab.tagroot.io	502	14		Outdoor temperature sensor 5.	lab.tagroot.io@tagroot.io	Outdoor__5	MeteringTopology
lab.tagroot.io	502	14	0	Outdoor temperature 5.	lab.tagroot.io@tagroot.io	Outdoor Temperature 5	MeteringTopology
lab.tagroot.io	502	15		Outdoor temperature sensor 6.	lab.tagroot.io@tagroot.io	Outdoor__6	MeteringTopology
lab.tagroot.io	502	15	0	Outdoor temperature 6.	lab.tagroot.io@tagroot.io	Outdoor Temperature 6	MeteringTopology
lab.tagroot.io	502	16		Outdoor temperature sensor 7.	lab.tagroot.io@tagroot.io	Outdoor__7	MeteringTopology
lab.tagroot.io	502	16	0	Outdoor temperature 7.	lab.tagroot.io@tagroot.io	Outdoor Temperature 7	MeteringTopology
lab.tagroot.io	502	17		Outdoor temperature sensor 8.	lab.tagroot.io@tagroot.io	Outdoor__8	MeteringTopology
lab.tagroot.io	502	17	0	Outdoor temperature 8.	lab.tagroot.io@tagroot.io	Outdoor Temperature 8	MeteringTopology
lab.tagroot.io	502	18		Outdoor temperature sensor 9.	lab.tagroot.io@tagroot.io	Outdoor__9	MeteringTopology
lab.tagroot.io	502	18	0	Outdoor temperature 9.	lab.tagroot.io@tagroot.io	Outdoor Temperature 9	MeteringTopology
lab.tagroot.io	502	19		Outdoor temperature sensor 10.	lab.tagroot.io@tagroot.io	Outdoor_10	MeteringTopology
lab.tagroot.io	502	19	0	Outdoor temperature 10.	lab.tagroot.io@tagroot.io	Outdoor Temperature 10	MeteringTopology
lab.tagroot.io	502	20		Indoor temperature sensor 1.	lab.tagroot.io@tagroot.io	Indoor__1	MeteringTopology
lab.tagroot.io	502	20	0	Indoor temperature 1.	lab.tagroot.io@tagroot.io	Indoor Temperature 1	MeteringTopology
lab.tagroot.io	502	21		Indoor temperature sensor 2.	lab.tagroot.io@tagroot.io	Indoor__2	MeteringTopology
lab.tagroot.io	502	21	0	Indoor temperature 2.	lab.tagroot.io@tagroot.io	Indoor Temperature 2	MeteringTopology
lab.tagroot.io	502	22		Indoor temperature sensor 3.	lab.tagroot.io@tagroot.io	Indoor__3	MeteringTopology
lab.tagroot.io	502	22	0	Indoor temperature 3.	lab.tagroot.io@tagroot.io	Indoor Temperature 3	MeteringTopology
lab.tagroot.io	502	23		Indoor temperature sensor 4.	lab.tagroot.io@tagroot.io	Indoor__4	MeteringTopology
lab.tagroot.io	502	23	0	Indoor temperature 4.	lab.tagroot.io@tagroot.io	Indoor Temperature 4	MeteringTopology
lab.tagroot.io	502	24		Indoor temperature sensor 5.	lab.tagroot.io@tagroot.io	Indoor__5	MeteringTopology
lab.tagroot.io	502	24	0	Indoor temperature 5.	lab.tagroot.io@tagroot.io	Indoor Temperature 5	MeteringTopology
lab.tagroot.io	502	25		Indoor temperature sensor 6.	lab.tagroot.io@tagroot.io	Indoor__6	MeteringTopology
lab.tagroot.io	502	25	0	Indoor temperature 6.	lab.tagroot.io@tagroot.io	Indoor Temperature 6	MeteringTopology
lab.tagroot.io	502	26		Indoor temperature sensor 7.	lab.tagroot.io@tagroot.io	Indoor__7	MeteringTopology
lab.tagroot.io	502	26	0	Indoor temperature 7.	lab.tagroot.io@tagroot.io	Indoor Temperature 7	MeteringTopology
lab.tagroot.io	502	27		Indoor temperature sensor 8.	lab.tagroot.io@tagroot.io	Indoor__8	MeteringTopology
lab.tagroot.io	502	27	0	Indoor temperature 8.	lab.tagroot.io@tagroot.io	Indoor Temperature 8	MeteringTopology
lab.tagroot.io	502	28		Indoor temperature sensor 9.	lab.tagroot.io@tagroot.io	Indoor__9	MeteringTopology
lab.tagroot.io	502	28	0	Indoor temperature 9.	lab.tagroot.io@tagroot.io	Indoor Temperature 9	MeteringTopology
lab.tagroot.io	502	29		Indoor temperature sensor 10.	lab.tagroot.io@tagroot.io	Indoor_10	MeteringTopology
lab.tagroot.io	502	29	0	Indoor temperature 10.	lab.tagroot.io@tagroot.io	Indoor Temperature 10	MeteringTopology
lab.tagroot.io	502	30		Heater 1.	lab.tagroot.io@tagroot.io	Heater__1	MeteringTopology
lab.tagroot.io	502	30	0	Heater enabled 1.	lab.tagroot.io@tagroot.io	Heater Enabled 1	MeteringTopology
lab.tagroot.io	502	30	2	Heater temperature 1.	lab.tagroot.io@tagroot.io	Heater Temperature 1	MeteringTopology
lab.tagroot.io	502	31		Heater 2.	lab.tagroot.io@tagroot.io	Heater__2	MeteringTopology
lab.tagroot.io	502	31	0	Heater enabled 2.	lab.tagroot.io@tagroot.io	Heater Enabled 2	MeteringTopology
lab.tagroot.io	502	31	2	Heater temperature 2.	lab.tagroot.io@tagroot.io	Heater Temperature 2	MeteringTopology
lab.tagroot.io	502	32		Heater 3.	lab.tagroot.io@tagroot.io	Heater__3	MeteringTopology
lab.tagroot.io	502	32	0	Heater enabled 3.	lab.tagroot.io@tagroot.io	Heater Enabled 3	MeteringTopology
lab.tagroot.io	502	32	2	Heater temperature 3.	lab.tagroot.io@tagroot.io	Heater Temperature 3	MeteringTopology
lab.tagroot.io	502	33		Heater 4.	lab.tagroot.io@tagroot.io	Heater__4	MeteringTopology
lab.tagroot.io	502	33	0	Heater enabled 4.	lab.tagroot.io@tagroot.io	Heater Enabled 4	MeteringTopology
lab.tagroot.io	502	33	2	Heater temperature 4.	lab.tagroot.io@tagroot.io	Heater Temperature 4	MeteringTopology
lab.tagroot.io	502	34		Heater 5.	lab.tagroot.io@tagroot.io	Heater__5	MeteringTopology
lab.tagroot.io	502	34	0	Heater enabled 5.	lab.tagroot.io@tagroot.io	Heater Enabled 5	MeteringTopology
lab.tagroot.io	502	34	2	Heater temperature 5.	lab.tagroot.io@tagroot.io	Heater Temperature 5	MeteringTopology
lab.tagroot.io	502	35		Heater 6.	lab.tagroot.io@tagroot.io	Heater__6	MeteringTopology
lab.tagroot.io	502	35	0	Heater enabled 6.	lab.tagroot.io@tagroot.io	Heater Enabled 6	MeteringTopology
lab.tagroot.io	502	35	2	Heater temperature 6.	lab.tagroot.io@tagroot.io	Heater Temperature 6	MeteringTopology
lab.tagroot.io	502	36		Heater 7.	lab.tagroot.io@tagroot.io	Heater__7	MeteringTopology
lab.tagroot.io	502	36	0	Heater enabled 7.	lab.tagroot.io@tagroot.io	Heater Enabled 7	MeteringTopology
lab.tagroot.io	502	36	2	Heater temperature 7.	lab.tagroot.io@tagroot.io	Heater Temperature 7	MeteringTopology
lab.tagroot.io	502	37		Heater 8.	lab.tagroot.io@tagroot.io	Heater__8	MeteringTopology
lab.tagroot.io	502	37	0	Heater enabled 8.	lab.tagroot.io@tagroot.io	Heater Enabled 8	MeteringTopology
lab.tagroot.io	502	37	2	Heater temperature 8.	lab.tagroot.io@tagroot.io	Heater Temperature 8	MeteringTopology
lab.tagroot.io	502	38		Heater 9.	lab.tagroot.io@tagroot.io	Heater__9	MeteringTopology
lab.tagroot.io	502	38	0	Heater enabled 9.	lab.tagroot.io@tagroot.io	Heater Enabled 9	MeteringTopology
lab.tagroot.io	502	38	2	Heater temperature 9.	lab.tagroot.io@tagroot.io	Heater Temperature 9	MeteringTopology
lab.tagroot.io	502	39		Heater 10.	lab.tagroot.io@tagroot.io	Heater_10	MeteringTopology
lab.tagroot.io	502	39	0	Heater enabled 10.	lab.tagroot.io@tagroot.io	Heater Enabled 10	MeteringTopology
lab.tagroot.io	502	39	2	Heater temperature 10.	lab.tagroot.io@tagroot.io	Heater Temperature 10	MeteringTopology
lab.tagroot.io	502	40		Thermostat 1.	lab.tagroot.io@tagroot.io	Thermostat__1	MeteringTopology
lab.tagroot.io	502	40	0	Thermostat enabled 1.	lab.tagroot.io@tagroot.io	Thermostat Enabled 1	MeteringTopology
lab.tagroot.io	502	40	2	Thermostat temperature 1.	lab.tagroot.io@tagroot.io	Thermostat Temperature 1	MeteringTopology
lab.tagroot.io	502	41		Thermostat 2.	lab.tagroot.io@tagroot.io	Thermostat__2	MeteringTopology
lab.tagroot.io	502	41	0	Thermostat enabled 2.	lab.tagroot.io@tagroot.io	Thermostat Enabled 2	MeteringTopology
lab.tagroot.io	502	41	2	Thermostat temperature 2.	lab.tagroot.io@tagroot.io	Thermostat Temperature 2	MeteringTopology
lab.tagroot.io	502	42		Thermostat 3.	lab.tagroot.io@tagroot.io	Thermostat__3	MeteringTopology
lab.tagroot.io	502	42	0	Thermostat enabled 3.	lab.tagroot.io@tagroot.io	Thermostat Enabled 3	MeteringTopology
lab.tagroot.io	502	42	2	Thermostat temperature 3.	lab.tagroot.io@tagroot.io	Thermostat Temperature 3	MeteringTopology
lab.tagroot.io	502	43		Thermostat 4.	lab.tagroot.io@tagroot.io	Thermostat__4	MeteringTopology
lab.tagroot.io	502	43	0	Thermostat enabled 4.	lab.tagroot.io@tagroot.io	Thermostat Enabled 4	MeteringTopology
lab.tagroot.io	502	43	2	Thermostat temperature 4.	lab.tagroot.io@tagroot.io	Thermostat Temperature 4	MeteringTopology
lab.tagroot.io	502	44		Thermostat 5.	lab.tagroot.io@tagroot.io	Thermostat__5	MeteringTopology
lab.tagroot.io	502	44	0	Thermostat enabled 5.	lab.tagroot.io@tagroot.io	Thermostat Enabled 5	MeteringTopology
lab.tagroot.io	502	44	2	Thermostat temperature 5.	lab.tagroot.io@tagroot.io	Thermostat Temperature 5	MeteringTopology
lab.tagroot.io	502	45		Thermostat 6.	lab.tagroot.io@tagroot.io	Thermostat__6	MeteringTopology
lab.tagroot.io	502	45	0	Thermostat enabled 6.	lab.tagroot.io@tagroot.io	Thermostat Enabled 6	MeteringTopology
lab.tagroot.io	502	45	2	Thermostat temperature 6.	lab.tagroot.io@tagroot.io	Thermostat Temperature 6	MeteringTopology
lab.tagroot.io	502	46		Thermostat 7.	lab.tagroot.io@tagroot.io	Thermostat__7	MeteringTopology
lab.tagroot.io	502	46	0	Thermostat enabled 7.	lab.tagroot.io@tagroot.io	Thermostat Enabled 7	MeteringTopology
lab.tagroot.io	502	46	2	Thermostat temperature 7.	lab.tagroot.io@tagroot.io	Thermostat Temperature 7	MeteringTopology
lab.tagroot.io	502	47		Thermostat 8.	lab.tagroot.io@tagroot.io	Thermostat__8	MeteringTopology
lab.tagroot.io	502	47	0	Thermostat enabled 8.	lab.tagroot.io@tagroot.io	Thermostat Enabled 8	MeteringTopology
lab.tagroot.io	502	47	2	Thermostat temperature 8.	lab.tagroot.io@tagroot.io	Thermostat Temperature 8	MeteringTopology
lab.tagroot.io	502	48		Thermostat 9.	lab.tagroot.io@tagroot.io	Thermostat__9	MeteringTopology
lab.tagroot.io	502	48	0	Thermostat enabled 9.	lab.tagroot.io@tagroot.io	Thermostat Enabled 9	MeteringTopology
lab.tagroot.io	502	48	2	Thermostat temperature 9.	lab.tagroot.io@tagroot.io	Thermostat Temperature 9	MeteringTopology
lab.tagroot.io	502	49		Thermostat 10.	lab.tagroot.io@tagroot.io	Thermostat_10	MeteringTopology
lab.tagroot.io	502	49	0	Thermostat enabled 10.	lab.tagroot.io@tagroot.io	Thermostat Enabled 10	MeteringTopology
lab.tagroot.io	502	49	2	Thermostat temperature 10.	lab.tagroot.io@tagroot.io	Thermostat Temperature 10	MeteringTopology

An XML file that can be used for importing devices is also available: SimModbus.xml.

Reference repository: https://github.com/rbrama79/dot99binding/blob/main/ModbusDevices.md

QR Codes

The following QR codes are available for ease of access to the above devices.

Outdoor temperature sensors

Indoor temperature sensors

Heaters

Thermostats

#simulation, #comsim, #iot