Glossary

Area of the myDatanet server for the installation and management of the IoT apps. The app models that serve as a basis for the IoT apps are obtained via the rapidM2M Store . When installing an IoT app on the myDatanet server the default settings defined when developing the app models are initially applied. These default settings can then be adjusted. Any number of IoT apps can be created based on a single app model by setting the appropriate default settings.

An app model is developed in the rapidM2M Studio and forms the basis for creating IoT apps. It essentially contains the executable program files (device logic, backend logic, portal view, etc.) from which an IoT is created by adding the default settings. Distribution to the individual myDatanet servers is carried out via the rapidM2M Store . The available app models are displayed in the app centre of the respective myDatanet server.

The device logic is the intelligence installed on the device that determines the local functionality of the device. The device logic is part of the app model and is created in a C-like scripting language built on "PAWN".

Specifies the hardware platform installed in the device and its hardware version (e.g. rapidM2M M2 HW1.4). The part of the hardware ID string, that specifies the hardware version, is only increased if changes relevant to the rapidM2M firmware have been made to the hardware platform. When developing an app model, it can be specified on which hardware platform the app model can be installed and which version of the hardware platform is required as a minimum. The hardware ID string is displayed in the TESTbed of the rapidM2M Studio or in the "Identification" field of the input screen for configuring the device.

IoT apps form the basis for creating sites. They consist of an app model and corresponding default settings that are applied as default values for the site when the site is created. The app centre can be used to create any number of IoT apps based on a single app model by setting the appropriate default settings. This makes sense if several use cases need to be covered by a single app model and they each require a different default site configuration (e.g. if a data logger with different external sensors is to be sold as a package).

The myDatanet  uses special encoding to display different error statuses in the measurement values, for example. By setting a measurement value to "NaN", it is clearly marked as invalid and is thus not used for any further calculations. In the measurement value graphs, a measurement value that has been set to "NaN" is indicated by an interruption in the graph. When downloading the data, a measurement value set to "NaN" is indicated by an empty data field.

Specifies the revision of the product. The revision is increased every time the product is modified (i.e. electronic system, mechanics, etc.) and is marked on the type plate of the product.

Is responsible for distributing the app models to the individual myDatanet servers. When installing and updating IoT apps the myDatanet server access the app models provided in the rapidM2M Store . The developer of the respective app model defines which myDatanet servers are allowed to access an app model via the rapidM2M Studio .

Depending on the required accuracy, one of two special encodings can be used for the time stamp in rapidM2M. If the accuracy requirements are moderate, the "stamp32" data type (seconds since 1999-12-31 00:00:00 UTC) can be used. If a higher accuracy is required, the "stamp40" data type (1/256 seconds since 1999-12-31 00:00:00 UTC) can be used. Converting the "stamp32" data type into the UNIX timestamp (seconds since 1970-01-01 00:00:00 UTC) can be achieved by adding 946598400.