hit counter script
Siemens MindConnect Nano System Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Switch
  5. MindConnect Nano
  6. System manual

Siemens MindConnect Nano System Manual

Insights hub
Hide thumbs Also See for MindConnect Nano:
Table of Contents

Advertisement

Quick Links

Insights Hub
MindConnect Nano
System Manual
07/2023
Introduction
Overview of onboarding
MindConnect Nano
Configuring data in Asset Manager
Configuring protocols
Firmware update for Mindconnect
Nano
Remote functions
Troubleshooting
Appendix
Glossary
1
2
3
4
5
6
7
8
9

Advertisement

Table of Contents
loading

Related Manuals for Siemens MindConnect Nano

Summary of Contents for Siemens MindConnect Nano

  • Page 1 Introduction Overview of onboarding Insights Hub MindConnect Nano Configuring data in Asset Manager MindConnect Nano Configuring protocols System Manual Firmware update for Mindconnect 07/2023 Nano Remote functions Troubleshooting Appendix Glossary...
  • Page 2 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.

  • Page 3: Table Of Contents

    3.4. Adding a data source for MindConnect Nano........… 3.5. Adding data points for MindConnect Nano........... … 3.6. Mapping an aspect to a data source for MindConnect Nano....… 3.7. Browsing datapoint of a data source for MindConnect Nano..... …...
  • Page 4 4.7. Overview of Rockwell protocol for MindConnect Nano......… 5. Firmware update for Mindconnect Nano............ … 5.1. Manual firmware update of MindConnect Nano........… 5.2. Firmware update in Asset Manager for MindConnect Nano....… 5.3. Automatic firmware update of MindConnect Nano......… 6. Remote functions.................... …...
  • Page 5 8.16. MindConnect General Security Principles..........… 9. Glossary......................… 9.1. Glossary...................... …...

  • Page 6: Introduction

    Introduction 1.1 Overview of MindConnect Nano MindConnect Nano is an embedded industrial PC to connect industrial data sources with Industrial IoT. It allows you to connect with Industrial IoT and collect data from the field and then transfer it with encryption to Industrial IoT.
  • Page 7 Performance Read performance (datapoints/sec) Maximum number of connections (data sources) Maximum number of datapoints 1150 Protocols Feature Overview Protocols Minimum read cycle MindConnect Nano Bi-Directional communication Browsing Basics 1 sec OPC UA 1 sec Modbus TCP IP 1 sec MindConnect Nano...
  • Page 8 Introduction 1.1 Overview of MindConnect Nano Protocols Minimum read cycle MindConnect Nano Bi-Directional communication Browsing Modbus RTU 1 sec Rockwell 1 sec �� Simatic I/O Shield 1 sec �� System 1 sec = supported = not supported �� = in development...

  • Page 9: Overview Of Onboarding Mindconnect Nano

    Overview of onboarding MindConnect Nano 2.1 Overview of onboarding MindConnect Nano This chapter describes the initial configuration of an asset and MindConnect Nano in order to onboard MindConnect Nano to Insights Hub. Onboarding is the process of attaching a MindConnect Element to Insights Hub. And also, it describes the process of connecting industrial data sources to Industrial IoT using MindConnect Nano.

  • Page 10: Logging In To Insights Hub

    2.2 Logging in to Insights Hub To log in to Insights Hub, follow these steps: 1. Click the link provided via mail by the Siemens AG. The Insights Hub landing page for login will appear. 2. Log in to Insights Hub using the configured Authentication Provider (WebKey by default).
  • Page 11 Overview of onboarding MindConnect Nano 2.3 Creating an asset for MindConnect Nano To connect your MindConnect Nano in Asset Manager, you need to create an asset. This process is the same for different types of MindConnect Elements that includes the Physical Asset type, and the Virtual Asset type.

  • Page 12: Enable Connection To Mindconnect Nano

    2.4 Enable connection to MindConnect Nano 2.4 Enable connection to MindConnect Nano To use a MindConnect Nano with Industrial IoT you have to enable the connection. Within enabling the connection you can assign a MindConnect Nano to an asset. Procedure To enable the connection to MindConnect Nano, follow these steps: 1.

  • Page 13: Configuring Network Settings

    (ethernet labeled with X2P1) and Industrial IoT (ethernet labeled with X1P1). If your company uses a proxy server, it must also be configured to connect MindConnect Nano to Industrial IoT. Contact your IT administrator for details on your local network settings.
  • Page 14 Overview of onboarding MindConnect Nano 2.5 Configuring network settings 1. Select the asset in the "Asset" tab. 2. Click on the asset icon, e. g. "MindConnect Nano". 3. Click next to "Status" on the button The following graphic shows the "Edit MindConnect" screen: 4.

  • Page 15: Configuring Diagnostic Settings

    Overview of onboarding MindConnect Nano 2.6 Configuring diagnostic settings If nothing else is configured manually, MindConnect Nano will try to obtain IP addresses for both adapters via DHCP. 6.Enter the available router gateways used in your company network. 7.Click on "Save", to complete the configuration.
  • Page 16 Overview of onboarding MindConnect Nano 2.6 Configuring diagnostic settings 3. Click , next to "Onboarding Status". 4. In "Buffer Behavior" section, select "Chronological Upload". 5. Click “Save”. 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.
  • Page 17 Overview of onboarding MindConnect Nano 2.6 Configuring diagnostic settings 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 uploads all the generated logs to Insights Hub periodically.Log upload functionality for the device is enabled by default.
  • Page 18 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...
  • Page 19 2.6 Configuring diagnostic settings Be aware that enabling RS application might effect on the time-series data transfer. Ensure that MindConnect Nano is able to perform operations smoothly via Insights Hub Monitor occasionally. RS Application does not support proxy authentication, thus enabling the proxy authentication will disable the RS application if it is enabled.

  • Page 20: Transferring Configuration To Mindconnect Nano

    2.7 Transferring configuration to MindConnect Nano Requirements A standard USB device with a single partition in FAT or FAT32 is formatted. You have enabled the connection to the MindConnect Nano. You have configured the network settings. Procedure USB stick information The configuration created in this step includes security relevant information.
  • Page 21 Overview of onboarding MindConnect Nano 2.7 Transferring configuration to MindConnect Nano 4. Insert the USB stick into the USB port of the MindConnect Nano, e. g. "MindConnect Nano" During the import of the configuration, the following LED-states are to be expected: 1.

  • Page 22: Configuring Data In Asset Manager

    After onboarding a MindConnect Nano, you need to configure the data in Asset Manager. You have to set up a data connection to receive data from your MindConnect Nano. In order to use the data from your MindConnect Nano you need to map the received data to the Asset Manager data model:...

  • Page 23: Adding A Data Source For Mindconnect Nano

    The data source defines the reading of the data from the MindConnect Nano. Mapping an aspect to a data source for MindConnect Nano In this final step you map the data of the MindConnect Nano to the aspects and variables.
  • Page 24 The new aspect type with its variables is available in the aspect list. 3.3 Creating a type in Asset Manager for MindConnect Nano To enable data mapping, you first have to create an asset type. An asset type is a pre-configured template for an asset.
  • Page 25 Configuring data in Asset Manager 3.4 Adding a data source for MindConnect Nano Procedure To create an asset type proceed as follows: 1. Click on the "Types" tab in Asset Manager. 2. Click on "BasicDevice". 3. To create a new asset type click 4.
  • Page 26 3.4 Adding a data source for MindConnect Nano To receive the data of your MindConnect Nano you need to add a data source. The data source specifies the protocol and reading cycle that is used to transfer the data from your asset to the MindConnect Nano.
  • Page 27 Configuring data in Asset Manager 3.4 Adding a data source for MindConnect Nano The default reading cycle is 86400 seconds, which is one day. You can find additional information on supported protocols in the chapter Overview of supported protocols for MindConnect Nano.

  • Page 28: Adding Data Points For Mindconnect Nano

    Configuring data in Asset Manager 3.5 Adding data points for MindConnect Nano 3.5 Adding data points for MindConnect Nano A data point is a measurable value of an asset that can be represented numerically and graphically. Examples of a data point are temperature or pressure. You can add data points to a data source to collect the data for example from a control unit.
  • Page 29 To add a data point to a data source, for example: "Pressure", follow these steps: 1. Click on the asset in the "Assets" tab, for example: "Wind turbine". 2. Click on the asset icon, for example: "MindConnect Nano". 3. To edit the data source you have to click on "Enter Edit Mode".

  • Page 30: Mapping An Aspect To A Data Source For Mindconnect Nano

    Configuring data in Asset Manager 3.6 Mapping an aspect to a data source for MindConnect Nano The units and data types specified here will need to match exactly with the aspects and variables. If they are different, the aspect cannot be connected to the data point.
  • Page 31 3.6 Mapping an aspect to a data source for MindConnect Nano Data points of a data source represent the data of the MindConnect Nano. To use the data of your MindConnect Nano you have to map them to the respective variables of an aspect.
  • Page 32 Configuring data in Asset Manager 3.6 Mapping an aspect to a data source for MindConnect Nano 8.Select the variable you want to link, e. g. "RotationSpeed". MindConnect Nano System Manual 7/2023...

  • Page 33: Browsing Datapoint Of A Data Source For Mindconnect Nano

    Configuring data in Asset Manager 3.7 Browsing datapoint of a data source for MindConnect Nano Only data types that match exactly with the aspects and variables are available. If they are different, the aspect can’t be connected to the data point.
  • Page 34 Configuring data in Asset Manager 3.7 Browsing datapoint of a data source for MindConnect Nano After adding the data source, you can browse the datapoints for the selected data source. This feature is only supported for OPC UA protocol. During configuration of data points via browsing feature, performance may get impacted depending on the configuration and data points in Data Sources.

  • Page 35: Importing Data Source Configurations For Mindconnect Nano

    DP; dp-name2;dp-description;LONG;dp-unit DP; dp-name3;dp-description;LONG;dp-unit Procedure To import the data source configuration for an asset of the type MindConnect Nano, follow these steps: 1. In the "Assets" tab, click asset. For example, "Wind turbine". 2. In "Connectivity" section, click MindConnect Nano plugin. For example, "MindConnect Nano".
  • Page 36 Configuring data in Asset Manager 3.8 Importing data source configurations for MindConnect Nano 3. To configure the data source, click "Configure your data sources" or "Enter edit mode" if the data source is already created. 4. To import a file, click "Import configuration".

  • Page 37: Configuring Mindconnect Nano Using Api

    3.9 Configuring MindConnect Nano using API AgentManagement API You can configure MindConnect Nano via api calls with public API’s that are offered from Industrial IoT. To update the data source configuration of AgentManagement api, refer to the endpoint "Data Source Configuration Operations" in Agent Management Service –...
  • Page 38 Configuring data in Asset Manager 3.9 Configuring MindConnect Nano using API In case the body structure is not as expected, the configuration might be rejected or may lead to corrupt configuration. Always verify the operation from MindConnect Element UI. The json configuration in body part of the request consists of below key-value pairs. All the documented key-value pairs given below are important.
  • Page 39 Configuring data in Asset Manager 3.9 Configuring MindConnect Nano using API The below json content can be changed as required, do not depend on it strictly. The free formatted fields "protocolData" and "dataPointData" has a specific configuration to S7 protocol.
  • Page 40 Configuring data in Asset Manager 3.9 Configuring MindConnect Nano using API To get the configurations details for other protocols such as Modbus, Ethernet IP etc, the API of AgentManagement can be used to get the configuration details. The initial configuration can be done via UI and then using the below API config, it can be extracted and used for API calls and later for structuring.

  • Page 41: Configuring Protocols

    Configuring protocols 4.1 Overview of supported protocols for MindConnect Nano The following are the supported protocols for MindConnect Nano: OPC UA Modbus TCP IP Modbus RTU System Rockwell 4.2 Overview of S7 protocol for MindConnect Nano The following image shows the data source input window for the S7 protocol:...
  • Page 42 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano You can choose between automatic and manual connection type. Automatic: This mode tries to find slot and rack number automatically. Manual: In this mode you can enter the rack and slot number manually.
  • Page 43 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano Address format examples Detailed examples: Example address format DB15.DBX6.3: DB15.DBX6.3 Data Offset Area indicator type address DB15 Offset Datablock address Separator Datablock Bool Offset Byte Separator Reads 3rd bit of byte 6 of datablock...
  • Page 44 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano Industrial INT ( 4 bytes ) LONG Byte DB15.DBB4²⁾ Reads an unsigned byte starting ( 8 bytes ) 1 byte / unsigned USInt DB15.DBBYTE4 from offset 4 out of datablock 15.
  • Page 45 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano Industrial The maximum string length (Byte10) is read first. Then the number of bytes that Byte10 indicates are number read. After that the of bytes that Byte11 indicates are extracted from the byte array that is the result of second read operation.
  • Page 46 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano Area indicator Area types Description Area indicator Area types Description Counter Reads Counter value of hardware. Datablock Reads datablock value from hardware. Instance Data Reads data directly from hardware. Process Input Reads Input value of Process image.
  • Page 47 Configuring protocols 4.2 Overview of S7 protocol for MindConnect Nano Data type Length Date range Bool 1 bit True to False Byte (unsigned) 1 byte 0 to 255 Word (unsigned) 2 bytes 0 to 65.535 DWord (unsigned) 4 bytes 0 to 4294967295 −128 to 127...

  • Page 48: Overview Of Opc Ua Protocol For Mindconnect Nano

    Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano * Tod L TOD#1:10:3.3 TIME_OF_DAY Time is in steps of 1 TOD#0.0.0.0 to (Time) TOD#23:59:59.999 TIME_OF_DAY#1:10:3.3 * Time Returns milliseconds. Format: The DT (DATE_AND_TIME) datatype saves the information on date and time of day in BCD format.
  • Page 49 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano For the OPCUA protocol, the data source input supports the following parameters: Parameter Description Protocol Shows the selected protocol type Name Name of the data source Description Add a description for data source...
  • Page 50 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano Parameter Description You can enable the transfer and takeover of events and alarms in the OPC UA protocol to Industrial IoT. Insights Hub Monitor shows all events and alarms in the Enable OPC "Events"...
  • Page 51 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano String IdentifierType Example ns=[id];s=[string] ns=5;s=Counter1 Attribute NodeId Value NodeId NamespaceIndex IdentifierType String Identifier Counter1 String for Identifier The string you enter at the four Identifier will be case sensitive.
  • Page 52 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano IEC61131 elementary datatypes OPC UA built-in datatypes Industrial IoT Type BOOL Boolean boolean SINT SByte USINT Byte Int16 UINT UInt16 DINT Int32 UDINT UInt32 LINT Int64 long ULINT UInt64...
  • Page 53 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano OPC UA Event Type You can choose default event type or one of the custom event types created in environment. OPC UA Event Types OPC UA plugins supports custom event types to be uploaded to Industrial IoT. Select the correct event type from the below drop-down menu, to get those events on Industrial IoT.
  • Page 54 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano Below is the api to call using a technical user /api/eventmanagement/v3/eventTypes The following template shows the payload of the call: "name": "SomeCustomEventType", "parentId": "core.connectivity.event.type.AgentBaseEvent", "ttl": 35, "scope": "LOCAL", "fields": [ "name": "Message",...
  • Page 55 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano The “name” field in body must be same as the “browseName” of the field which will be collected in the OPC UA Server. It is case-sensitive. Name for "Event Type" needs to be unique The “type”...
  • Page 56 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano The browsing result of a datasource will expire after a day. The OPCUA browsing operations are done sequentially on the device side not in parallel. The child of unsupported nodes type will not be shown in browsing result.
  • Page 57 Configuring protocols 4.3 Overview of OPC UA protocol for MindConnect Nano width=700px } !!! Warning Configuration jobs can only be applied after browsing operation is completed. If configuration job is applied during a browsing operation, below warning message is displayed on data source configuration page.

  • Page 58: Overview Of Modbus Tcp Protocol For Mindconnect Nano

    Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano OPC Type Cloud Type Integer UInt16 Int64 LONG UInt32 LONG UInt64 STRING String STRING If the connection to OPCUA Server is disconnected during browsing, then the whole operation of browsing is failed. It is expected from the customer to trigger the browsing result again in those situations.
  • Page 59 Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano The Modbus protocol is supported for the MindConnect Nano plugin. You can select the protocol type Modbus TCP while adding a new data source in Asset Manager. Modbus configuration The Modbus configuration view is only visible after a successful onboarding of the MindConnect Nano.
  • Page 60 Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano Parameter Description You can set the timeout interval used to wait for a response from the Modbus device. If the waiting before receiving the response is longer than responseTimeout the given timeout, an error will be generated.
  • Page 61 Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano Parameter Description Function type - depends on the type of the data (see manual of the Modbus device). 1: Read Coils, Function 2: Read Inputs, Type 3: Read Holding Registers, 4: Read Input Registers .
  • Page 62 Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano TCP Gateway slave number If you are using a TCP Gateway, you must select the appropriate slave number for the configuration of the data points. Addressing: The information is stored in the Modbus Slave device in 4 different tables. 2 tables store on/off discrete values (coils) and two store numerical values (registers).
  • Page 63 Configuring protocols 4.4 Overview of Modbus TCP protocol for MindConnect Nano Data Data type Length Data range type number short 16 bits 3 -32768 to 32767 unsigned 16 bits 4 0 to 65535 short −2147483648 to 2147483647 long 32 bits 5...

  • Page 64: Overview Of Modbus Rtu Protocol For Mindconnect Nano

    1. 4.5 Overview of Modbus RTU protocol for MindConnect Nano The Modbus protocol is supported for the MindConnect Nano plugin. You can select the protocol type Modbus RTU while adding a new data source in Asset Manager.
  • Page 65 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano For more information about how to create a new data source see chapter Adding a data source and data points for MindConnect Nano. Modbus RTU data source parameter In order to connect a Modbus RTU device, you need to select the Modbus RTU protocol and...
  • Page 66 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano Parameter Description Data bits for serial communication: Data bits - 8 (default) You can select the number of stop bits for serial communication: Stop bits - 1 (default) Parity for serial communication:...
  • Page 67 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano Pin RS 485 RS 422 RS 232 Pin RS 485 RS 422 RS 232 Data- Transmit / receive data - (I/O) for TX- Transmitted data - (O) for full-...
  • Page 68 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano Parameter Description Function type - depends on the type of the data (see manual of the Modbus device). 1: Read Coils Function Type 2: Read Inputs 3: Read Holding Registers 4: Read Input Registers Currently function codes 1..4 are supported.
  • Page 69 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano Coil/ Register numbers Data addresses Function type Table name 10001-19999 0 to 65535 Read Inputs 30001-39999 0 to 65535 Read Input Registers 40001-49999 0 to 65535 Read Holding Registers Coil / register numbers can be considered as location names since they do not appear in the configuration.
  • Page 70 Configuring protocols 4.5 Overview of Modbus RTU protocol for MindConnect Nano Response Response Data Function Start Variable Response Data Function Start Variable Response Example Address Example Address type type address type Quantity type type address type Quantity Offset Offset Read...

  • Page 71: Overview Of System Protocol For Mindconnect Nano

    4.6 Overview of SYSTEM protocol for MindConnect Nano You can use the protocol SYSTEM to implement a system information adapter for analysis purposes. The SYSTEM protocol can collect the following information from MindConnect Nano: Overall CPU load Overall memory consumption...
  • Page 72 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano You can choose the SYSTEM protocol as a data source without configuring specific system parameters, except the reading cycle. After creating the data source you can configure the following categories in a new data point:...
  • Page 73 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Data Variable Address Variable Address type type Name string /application/<subcategory>/name State stri /application/<subcategory>/state Tgid /application/<subcategory>/tgid Ngid /application/<subcategory>/ngid /application/<subcategory>/pid PPid /application/<subcategory>/ppid TracerPid /application/<subcategory>/tracerpid string /application/<subcategory>/uid string /application/<subcategory>/gid FDSize /application/<subcategory>/fdsize Groups string /application/<subcategory>/groups...
  • Page 74 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address type VmPTE long /application/<subcategory>/vmpte VmPMD long /application/<subcategory>/vmpmd VmSwap long /application/<subcategory>/vmswap HugetlbPages long /application/<subcategory>/hugetlbpages Threads /application/<subcategory>/threads SigQ string /application/<subcategory>/sigq SigPnd string /application/<subcategory>/sigpnd ShdPnd string /application/<subcategory>/shdpnd SigBlk string /application/<subcategory>/sigblk...
  • Page 75 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address type /application/<subcategory>/nonvoluntary_ctxt_s nonvoluntary_ctxt_switches int witches CPU information The following table shows the available variables for the category CPU information: Data Variable Description type Number of processes in state R(runnable) or D(disk sleep) averaged...
  • Page 76 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Variable Data type Address Description Size long /disk/dev/<subcategory>/size Partition size in bytes. Used long /disk/dev/<subcategory>/used Used space in bytes. KERNEL information The following table shows the available variables for the category KERNEL information:...
  • Page 77 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Variable Data type Address Restrictions DirectMap4M long /memory/directmap4m Dirty long /memory/dirty AnonHugePages long /memory/anonhugepages Only supported by MindConnect Nano. CmaTotal long /memory/cmatotal Only supported by MindConnect Nano. CmaFree long /memory/cmafree Only supported by MindConnect Nano.
  • Page 78 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Variable Data type Address Restrictions SHMem long /memory/shmem SLab long /memory/slab SReclaimable long /memory/sreclaimable SUnreclaim long /memory/sunreclaim SwapCached long /memory/swapcached SwapFree long /memory/swapfree SwapTotal long /memory/swaptotal Unevictable long /memory/unevictable VMAllocChunk...
  • Page 79 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type Number of delayed acks DelayedAcks long /network/delayedacks sent. Number of resets received EmbryonicRsTs long /network/embryonicrsts for embryonic SYN_RECV sockets. InBcastOctets long /network/inbcastoctets InBcastPkts long /network/inbcastpkts...
  • Page 80 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type OutBcastPkts long /network/outbcastpkts OutMcastOctets long /network/outmcastoctets OutMcastPkts long /network/outmcastokts OutOctets long /network/outoctets Bytes sent. ICMP packets dropped OutOfWindowIcmps long /network/outofwindowicmps because they were out-of- window.
  • Page 81 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type Connections aborted after TCPAbortOnLinger long /network/tcpabortonlinger user close in linger timeout. Connections aborted due to TCPAbortOnMemory long /network/tcpabortonmemory memory pressure. Connections reset due to TCPAbortOnSyn long /network/tcpabortonsync unexpected SYN.
  • Page 82 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type DSACKs sent for old TCPDSACKOldSent long /network/tcpdsackoldsent packets. TCPDSACKRecv long /network/tcpdsackrecv DSACKs received. Congestion window TCPDSACKUndo long /network/tcpdsackundo recovered without slow start using DSACK. Number of times reordering...
  • Page 83 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type Number of ACK packets TCPKeepAlive long /network/tcpkeepalive sent to keep TCP flow alive. TCPLossFailures long /network/tcplossfailures Timeouts in loss state. TCPLossProbeRecovery long /network/tcplossproberecovery TCPLossProbes long /network/tcplossprobes...
  • Page 84 Configuring protocols 4.6 Overview of SYSTEM protocol for MindConnect Nano Data Variable Address Description type TCPRcvCoalesce long /network/tcprcvcoalesce Packets collapsed in receive TCPRcvCollapsed long /network/tcprcvcollapsed queue due to low socket buffer. Timeouts after reno fast TCPRenoFailures long /network/tcprenofailures retransmit. Times recovered from...

  • Page 85: Overview Of Rockwell Protocol For Mindconnect Nano

    Configuring protocols 4.7 Overview of Rockwell protocol for MindConnect Nano Data Variable Address Description type TCPSlowStartRetrans long /network/tcpslowstartretrans Retransmits in slow start. TCPSpuriousRTOS long /network/tcpspuriousrtos TCPSpuriousRTXHostQueues long /network/tcpspuriousrtxhostqueues TCPSYNChallenge long /network/tcpsynchallenge TCPSYNRetrans long /network/tcpsynretrans TCPTimeouts long /network/tcptimeouts Other TCP timeouts.
  • Page 86 Configuring protocols 4.7 Overview of Rockwell protocol for MindConnect Nano Rockwell data source parameter In order to connect a Rockwell device, you need to select the Rockwell protocol and enter the following data source parameters: Parameter Description Shows available CPU types:...
  • Page 87 Configuring protocols 4.7 Overview of Rockwell protocol for MindConnect Nano The following table shows the data point parameter: Parameter Description Data type supported by backend (e.g. INT). Data Type STRING data type is currently not supported. Name of the tag that has to be recorded.
  • Page 88 Configuring protocols 4.7 Overview of Rockwell protocol for MindConnect Nano PCL data types Currently only these PLC data types are supported. MindConnect Nano System Manual 7/2023...

  • Page 89: Firmware Update For Mindconnect Nano

    Firmware update for Mindconnect Nano 5.1 Manual firmware update of MindConnect Nano To prepare your MindConnect Nano for V3 please follow the next two steps: Set MindConnect to factory settings Load new firmware on your MindConnect Nano Set MindConnect to factory settings This procedure is only necessary for boxes that were already connected to V2 (SAP).

  • Page 90: Firmware Update In Asset Manager For Mindconnect Nano

    2. Unzip the firmware on your local machine. 3. Copy the unzipped files to a USB stick. 4. Insert the USB stick into the MindConnect Nano and wait until the firmware update is complete. Update carried out: ERROR LED flashes orange...
  • Page 91 Firmware update for Mindconnect Nano 5.2 Firmware update in Asset Manager for MindConnect Nano 5. To select a firmware release click "Choose another firmware release". The "select firmware" dialog appears. 6. Select product and available version and click "Accept". 7. To update your firmware click "Update your firmware".

  • Page 92: Automatic Firmware Update Of Mindconnect Nano

    5.3 Automatic firmware update of MindConnect Nano 5.3 Automatic firmware update of MindConnect Nano In Asset Manager, the firmware of your MindConnect Nano is updated by both manually and automatically. If the auto firmware update option is enabled, MindConnect Nano is automatically updated with the new version when it is released.
  • Page 93 Firmware update for Mindconnect Nano 5.3 Automatic firmware update of MindConnect Nano 6. Click "Save" button to save the changes. MindConnect Nano System Manual 7/2023...

  • Page 94: Remote Functions

    Remote functions 6.1 Remote restart for MindConnect Nano By using the remote restart function in the MindConnect Element Plugin, you can restart your device without having to use the on / off button on the device. This makes it easier to restart boxes that are difficult to reach.
  • Page 95 Remote functions 6.2 Send commands for MindConnect Nano It is important to know the limitations of your devices, before you set a specific value for a datapoint. Failure to check value ranges within your controllers may result in damages to your devices.
  • Page 96 Remote functions 6.2 Send commands for MindConnect Nano Commanding Device via API In order to command the device, there are 3 critical id’s that needs to be get from the system. Those id’s are deviceId, datasourceId and datapointId. To get the id’s, follow these steps: Getting deviceId You can "GET"...
  • Page 97 Remote functions 6.2 Send commands for MindConnect Nano "readCycleInSeconds": "60", "protocolData": { "ipAddress": "192.168.1.1", "manualRackAndSlot": "Automatic", "rackNumber": "0", "slotNumber": "2" "dataPoints": [ "id": "6efc38d1-b4e7-4e6e-98ce-cb6b3b3f36b2", "dataPointId": "36cd56f91c154", "name": "Energy", "description": "description", "unit": "kw", "dataType": "DOUBLE", "dataPointData": { "address": "DB1.DBD1", "hysteresis": "0", "onDataChanged": false,...
  • Page 98 Remote functions 6.2 Send commands for MindConnect Nano "dataSourceId": "10d9c36c-69f7-4c33-8624-f67537e142a4", "dataPointId": "b932b9da42f04", "protocol": "some_protocol" In the below list, there are some fields which require certain data only: Field Name Allowed Values OPCUA, S7 protocol OPCUA, S7 version v1.0 type datapoint-write...

  • Page 99: Troubleshooting

    - No Internet connection company’s router, Ethernet cables etc. - Interrupted connection - IP address is configured via DHCP, but there is no internet connection. - Firewall blocks MindConnect Elements - Your company’s router is damaged MindConnect Nano System Manual 7/2023...
  • Page 100 - Check configuration of each data configuration point. (Network - Check configuration of your asset Connection) - (Network Configuration). Invalid ID of - Check if MindConnect Nano ID is MindConnect correct. Nano MindConnect Nano was offline MindConnect - Check outbound connection...
  • Page 101 USB stick Unknown USB commands You can run diagnostic and maintenance USB commands on your MindConnect Nano. The following lists various USB commands and the respective JSON format: Prerequisites A MindConnect device e.g. MindConnect Nano MindConnect Nano...
  • Page 102 The following command will copy all archived log files to a sub directory on the USB stick and delete the copied log files from the archive folder optionally. The USB stick should be larger than MindConnect Nano System Manual 7/2023...
  • Page 103 ConBox_Commands.json ChangeLogFileUploadConfiguration command on a USB stick. This reduces the amount of data that is stored for a environment on the backend side and reduces the mobile data costs for uploading data to Industrial IoT. MindConnect Nano System Manual 7/2023...
  • Page 104 USB stick. The network and BoxMgr settings will be reset to their initial state on MindConnect Nano. All BoxMgr and MERS logging files and temporary files will be then deleted. At the end the MindConnect device will be restarted automatically.
  • Page 105 Effects on online device configuration There is no indication in the asset configuration user interface that the device configuration has been restricted on MindConnect Nano device. If you try to change restricted device settings online, a message is logged in the diagnostic file on the MindConnect Nano device that this setting could not be applied.
  • Page 106 - false: Subnet mask can be changed (default) - true: Gateway address can not be changed Gateway - false: Gateway address can be changed (default) - true: DNS address can not be changed - false: DNS address can be changed (default) MindConnect Nano System Manual 7/2023...
  • Page 107 USB stick. Depending on the current network situation, it might be possible that the execution of all internally executed tests will take some minutes. This command is available from the version MindConnect Nano firmware V03.04.02.10 b003. CheckNetwork command Using following JSON command in a ConBox_Commands.json file, a network analysis will be...
  • Page 108 Log files are uploaded every time the device is started. All the log files are uploaded after midnight. Once a log file reaches its maximum file size, it is uploaded as zip file. Using "Upload Logs Now" option to upload log files manually. MindConnect Nano System Manual 7/2023...
  • Page 109 7.1 Troubleshooting Log files are uploaded in tar.gz format with a maximum file size limit of 10MB with following MindConnect Firmware version. MindConnect Nano V03.04.04.03 b001. Concatenating log file archive parts Linux On Linux, the downloaded log file archive parts is concatenated as follows: cat fileArchiv.tar.gz.parta* >...

  • Page 110: Appendix

    Appendix 8.1 User Roles and Scopes for MindConnect Nano There are multiple roles that are available for MindConnect device controlling. A device can be configured and can send the command to the device by an “Admin” user. If you want to ensure that a user cannot configure but can send a command, then you can use “DeviceCommander”...

  • Page 111: Using Quality Code

    The following graphic shows a dataflow overview of the quality code: If the data provider (e.g. S7 PLC, OPC UA Server) is not available, the MindConnect Nano or the data provider client will send up a "0" with a quality code. The value of the quality code shows that this is not a valid data.

  • Page 112: Quality Codes Opc Ua And S7 Protocol

    0x80100000 -2146435072 BAD_TOO_MANY_OPERATIONS because it specified too many operations. 0x80130000 -2146238464 BAD_SECURITY_CHECKS_FAILED Indicates security problems. 0x801F0000 -2145452032 BAD_ACCESS_DENIED Bad Access Denied - Access denied. 0x80210000 -2145320960 BAD_IDENTITY_TOKEN_REJECTED Bad Identity Token Rejected. MindConnect Nano System Manual 7/2023...
  • Page 113 Data is missing due to collection 0x809D0000 -2137194496 BAD_DATA_LOST started/stopped/lost. Bad Invalid Argument - all items 0x80AB0000 -2136276992 INVALID_ARGUMENT could not be read. 0x80AC0000 -2136211456 BAD_CONNECTION_REJECTED Connection problem. The server has disconnected from 0x80AD0000 -2136145920 BAD_DISCONNECT the client. MindConnect Nano System Manual 7/2023...

  • Page 114: Quality Codes Modbus Protocol

    The data or event was not successfully updated because 0x809F0000 -2137063424 Entry exists no matching entry exists MindConnect Nano System Manual 7/2023...

  • Page 115: Quality Codes System Protocol

    Data source 0x807D0000 -2139291648 Previous read request of data source is still in progress busy 8.6 Quality codes Rockwell protocol The following table shows the possible quality codes for devices that use the Rockwell protocol: MindConnect Nano System Manual 7/2023...
  • Page 116 Receive timeout occured 0x80B10000 -2135883776 No data available No more data available 0x80B60000 -2135556096 Invalid syntax Syntax error 0x80B80000 -2135425024 Request too large Buffer is too small 0x80CE0000 -2133983232 Invalid response Received an invalid reply MindConnect Nano System Manual 7/2023...

  • Page 117: Offline Buffer

    In order to calculate the buffer time for MindConnect Nano or MindConnect IoT2040 you can use the following formula: MindConnect Nano data buffer is 500 MB. When the buffer is at full capacity, the new incoming data will overwrite the oldest data.
  • Page 118 For MindConnect Software Agent, the readings are not applicable as it depends on the hardware for a particular agent and configuration. Example calculations (MindConnect Nano) It can be possible to read 300 data points per second out of a PLC. This is possible if the PLC is powerful and just one data provider is used.

  • Page 119: Firewall Settings

    All devices are around 75% full 8.9 Firewall Settings It is recommended to use a firewall between the Internet and the MindConnect Nano, this is also recommended for communication to the automation network. In the direction to Automation Network a firewall supporting NAPT (in case of DMZ, see section “List of abbreviations”) or supporting the “Ghost-Mode”...

  • Page 120: Return Of Defective Hardware

    IP address. Firewall/Proxy rules for MindConnect Nano MindConnect Nano require open HTTPS and DNS ports for communication with Industrial IoT. You can open port 443 to enable this. To communicate agent only, you will only need the southgate.eu1.mindsphere.io...

  • Page 121: List Of Abbreviations

    For ordering, provision and delivery of spare parts you can find more information in the SIOS Article - Delivery of Spare Parts. Siemens Contact Database You can find your personal contact for spare parts in the Siemens Contact Database. 8.11 List of abbreviations...

  • Page 122: Mindconnect Ethernetip - Cip Communication Path

    This means each bridge keeps a reference to the request package. 8.13 Case 1 – Accessing data inside an Allen- Bradley PLC MindConnect Nano System Manual 7/2023...

  • Page 123: Case 2 - Accessing The Allen- Bradley Plc Via Integrated Ethernet

    Ethernet port. In a CPU module with integrated Ethernet port, the Ethernet port is in the same slot as the CPU module. The CIP client in the MindConnect sends a request package to the CPU module at 192.168.0.32 addressing the processor module in slot 0. MindConnect Nano System Manual 7/2023...

  • Page 124: Case 3 - Accessing The Allen- Bradley Plc Via The Controlnet Interf

    The yellow line in the above image represents the communication path (route parameters). In the communication path, the red marked sections always contain a network specific address. The blue marked part identifies the backplane or the interface to be used. It is not important that MindConnect Nano System Manual 7/2023...
  • Page 125 The Initial Access Token (IAT) is physically entitled to onboard the agent. The initial access token is valid for 7 days for security measures to avoid the misuse. Registering an agent (example, MindConnect Nano) To register an agent at agent management, follow these OAuth 2.0 protocol in two cases: Case 1:: Compute limited agent will use a shared secret in further communication.
  • Page 126 Registration access tokens have no practical expiration times but each time a client refreshes its registration a new RAT is generated by Industrial IoT. API communication agent (e.g. MindConnect Nano) Except the one for onboarding and registration, all Industrial IoT APIs require an access token: The Agent requests an access token from Agent IAM using a self signed JSON Web Token (JWT).
  • Page 127 Appendix 8.16 MindConnect General Security Principles MindConnect Nano System Manual 7/2023...
  • Page 128 Asset Identifier is an identifier assigned by the manufacturer of the device, to which MindConnect Nano will be connected. After the onboarding process, MindConnect Nano is connected to this device. The serial number identifies the asset to which the data belongs.
  • Page 129 (e.g. “Please contact your hotline”) and priority (urgent, important or info) can be lodged. See also “request”, “rule". Last Connection "Last Connection" status in “Asset Manager” gives the information, when a MindConnect Element was online for the last time. MindConnect Element MindConnect Nano System Manual 7/2023...
  • Page 130 MindConnect Nano, MindConnect IoT2040 or MindConnect FB. Industrial IoT Industrial IoT is the Siemens Industrial IoT operation system comprising the core cloud services and applications, whereas the MindConnect Element provides secure and easy connectivity from the field or machine to Industrial IoT. In Industrial IoT, submitted data by a MindConnect Element is processed and stored for analysis and further management purposes.
  • Page 131 Time series is a sequence of measurements which are produced by data sources over time. Analysis and visualization tools (e.g. Insights Hub Monitor) can retrieve collected time series and present it to the user after processing. In Asset Manager, the measurements, that have to be collected, can be specified. MindConnect Nano System Manual 7/2023...

This manual is also suitable for:

Mindconnect iot2040

Table of Contents