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 prioritizes 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 prioritize oldest data to new data (works as first in, first out (FIFO)).

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

To perform a buffer behavior change proceed as follows:

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

5. Click “Save”.

   

   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 , next to "Onboarding Status".

4. In “Diagnostic Settings” section, make the changes in Auto Log Upload or Log Level.

   

5. Click “Save”.

Auto Log Upload¶

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

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.

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.

Remote Services Integration¶

The integration of 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 RS to connect to the field devices and data. For more information on RS application, refer to Remote Services documentation.

To integrate RS 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 RS application.

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