Functional principle
In the graphic below, all of the components that are part of the myDatanet are illustrated in grey. All other components must be provided/created by the customer.
| 1 | myDatalogC3xx with integrated Managed Service SIM chip (including data transmission) |
| 2 | IoT application "myDataconC3" |
| 3 | myDatanet server to which the data is transferred |
| 4 | Client that accesses the interface of the myDatanet server via the web browser |
| 5 | Customer-specific server that provides clients with their own interface. The customer-specific server obtains the data via the API interface of the myDatanet server (see API). |
| 6 | Client on which a PC program is running that obtains its data via the API interface of the myDatanet server (see API) |
| 7 | Client that accesses the interface of the customer-specific server via the web browser |
Functions and components provided by myDatanet :
- myDatalogC3xx with installed
IoT application "myDataconC3"
Stationary data logger with integrated memory and standardised industrial interfaces (UI1-3, relay 1-2) to connect sensors and actuators to themyDatanet server (2G/3G/4G/M1/NB1)
- Managed Service
Managed Service is the basis for operating the devices and provides a wide range of services. Managed Service includes updates for device firmware, mobile data transmission on a global scale and free support - providing you with one contact person for the entire solution.
- myDatanet server
Database for saving the measurement data and configurations. Data is either accessed via the API (see API) or the web interface of the server.
Functions and components provided by the customer
- Sensors or actuators
Sensors or actuators that include interfaces that are compatible with the specifications listed in chapter "Specifications" (see Specifications)
- Customer-specific server with web interface for the clients (optional)
It can be used to create an individual web interface for the clients. Using this method, the data is read out of the myDatanet server via the API interface (see API) by the customer-specific server.
