Skip to content

Configuring diagnostic settings

Buffer Mechanism

In buffer mechanism, there are two options:

  • Default Buffer Mechanism: It provides parallel upload from cache and real time data. It prioritises newest data to old data while storing (works as a last in, first out (LIFO))
  • Chronological Buffer Mechanism: It is chronological upload of data. If "Chronologic Upload" is selected, the buffer mechanism will prioritise oldest data to new data (works as first in, first out (FIFO)).

You can configure the buffer behavior from "Network and Diagnostic Settings" screen.

Note

  • If the buffer behavior is changed, it will restart the data collection process and this process will take few minutes.

Note

Data loss

The data collection will be stopped during the time of buffer behavior change. The amount of data collection is stopped for few minutes, it depends on restart of the device. It may take longer time on slow devices like, IoT2040.

To perform a buffer behavior change proceed as follows:

  1. In "Asset" tab, select the asset.
  2. Open "MindConnect" plugin.
  3. Click Settings, next to "Onboarding Status".
  4. In "Buffer Behavior" section, select "Chronological Upload".
  5. Click “Save”.

    communication-settings

    Note

    Chronologic Upload Specification

    • If there is a bad network connection or no connection at all, the data is going to be stored in cache memory. In "Chronologic Upload", overwritten of cache memory is not possible. Only if there is any space on cache memory, the data is going to be written to it. If the cache memory reaches out it's limit and filled with data, then the data is not going to be saved on cache memory. It will cause data loss until some data is uploaded.

    • As chronological upload the flow of real data to cloud will take longer time comparing to default behavior.

    • The events are not cached in any case of the disconnection. Therefore, "Chronologic Upload" is not applicable for the event upload.

Diagnostic Settings

This section contains the configurations related with logging. To perform a diagnostic settings change, follow these steps:

  1. In "Asset" tab, select the asset.
  2. Open MindConnect plugin.
  3. Click Settings, next to "Onboarding Status".
  4. In “Diagnostic Settings” section, make the changes in Auto Log Upload or Log Level.

    diagnostic-settings-configure

  5. Click “Save”.

Auto Log Upload

If Auto Log Upload is enabled, the device is going to upload all generated logs to MindSphere periodically. Log upload functionality for the device is enabled by default.

Note

If Auto Log Upload is disabled, MindConnect device stops logging and uploading log files. However, there are some third party applications that keep logging on device. These logs will be uploaded when Auto Log Upload is enabled again.

Log Levels

Log level represents the log level of MindConnect device. There are five possible log levels, and the hierarchy is as follows in lowest (TRACE) to highest (ERROR) priority. In “TRACE” mode, the device will log extensively and in “ERROR” mode device will only log error messages.

log-level

The selected log level and logging mechanism works as logging only selected level and the higher levels.

Log level is set to “INFO” by default.

Note

Auto Log Level Change

  • “TRACE/DEBUG” log levels provide more verbose logs which will be helpful to troubleshoot issues, however they produce more files. If the log level is set to “TRACE/DEBUG”. It will be automatically changed to INFO after one day.
  • Auto log level change operation will not be synchronized with the asset’s device configuration.

MindSphere Remote Services Integration

The integration of MindSphere Remote Services to MindConnect Nano aims to provide solution for accessing factory related device via Nano. There are plenty of different services and protocols offered by MRS to connect to the field devices and data. For more information on MRS application, refer to MindSphere Remote Services documentation.

To integrate MRS application with MindConnect Nano, follow these steps:

  1. Create asset.

    Note

    To create an asset, see Creating an asset for MindConnect Nano.

  2. Onboard agent.

    Note

    To onboard an agent, see Overview of onboarding MindConnect Nano.

  3. Link asset id with MRS application.

  4. Enable MRS Services on the agent using toggle button and configure use cases in MRS applications.
  5. Click "Save".

Warning

  • Be aware that enabling MRS application might effect on the time-series data transfer. Ensure that MindConnect Nano is able to perform operations smoothly via Operations Insight occasionally.
  • MRS Application does not support proxy authentication, thus enabling the proxy authentication will disable the MRS application if it is enabled.
    mrs-not-enabled

Notice

  • Starting or stopping MRS application is an asynchronous task, during this ongoing phase the toggle on or off operations will be neglected.
  • MRS application itself has a separate management system of devices, the user needs to create a device on MRS application and associate it with MindConnect Nano’s asset via their id’s. Thereafter, user can able to enable the application from the MindConnect element UI.
    mrs-device-not-created
  • If the MRS application is not provisioned for the customer tenant then the user will not be able to enable the application and will see the below message on MindConnect element UI. To provision the application contact MindSphere Support Team.
    mrs-not-supported

Any questions left?

Ask the community


Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.


Last update: January 27, 2023