MindSphere Getting Started October 2016 PDF

Preface
Safety Notes 1
1 4
MindSphere -
Getting Started Getting Started with
MindSphere 2
6 4
Prepare MindConnect
Nano for MindSphere 3
6 4
Onboard MindConnect
Nano to MindSphere 4
6 4
Configure Data Collection 5

6 4
Perform visual analysis

on Assets 6
6 4
Appendix 7
6 4
Glossary 8
6 4
Version October 2016
10/2016
Legal Information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to
prevent damage to property. The notices referring to your personal safety are highlighted in the manual
by a safety alert symbol; notices referring only to property damage have no safety alert symbol. These
notices shown below are graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of
danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a
warning relating to property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for
the specific task in accordance with the relevant documentation, in particular its warning notices and
safety instructions. Qualified personnel are those who, based on their training and experience, are
capable of identifying risks and avoiding potential hazards when working with these products/systems.
Proper use of Siemens products

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. The permissible ambient conditions must be complied with. The
information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights
of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and
software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency.
However, the information in this publication is reviewed regularly and any necessary corrections are
included in subsequent editions.
Siemens AG Copyright © Siemens AG, 2016, and

Division Digital Factory licensors. All rights reserved.
Postfach 48 48 Portions include Open Source Software. See
90026 NÜRNBERG ReadMe_OSS.txt for details.
GERMANY
Preface
This manual gives you an overview of MindSphere and MindConnect Nano, enabling you to
commission MindConnect Nano and start working with MindSphere.
Basic knowledge requirements

A solid background in personal computers is required. General knowledge in the field
automation control engineering is recommended.
Scope of validity of this document

This manual is valid for MindConnect Nano and MindSphere.
Scope of this documentation

The complete documentation for MindSphere consists of the following documents:
• “MindSphere - Getting Started”
• “MindConnect Nano - Quick Start” enclosed with device MindConnect Nano
• Product information “Important notes on your device” enclosed with device MindConnect
Nano
• MindSphere – FAQs
• Datasheets for MindConnect Nano, MindAccess Users, MindApp Fleet Manager
Convention
The term “device” is used to refer to MindConnect Nano and the term “cloud” is used to refer
to MindSphere in this documentation. The terms for MindSphere can be found in Glossary in
the Appendix of this documentation.
Screenshots and graphics which are used in this document shall be seen as examples. They
are not able to show all combinations of possible inputs, but have an informational
character and serve for a better understanding. The configuration parameters shall be
extracted out of the text or tables and depend respectively on the needs and constellation of
the individual system.
Online support
Country-specific telephone numbers for technical support are provided on the Internet under
Contact:
https://support.industry.siemens.com/
Find your contact person or open a Support Request
History
The following editions of these operating instructions have been published:
Edition Comment
10/2016 First edition
MindSphere – Getting Started, 10/2016 3

Table of Contents
Table of Contents
Legal Information .................................................................................................................................2
Preface ................................................................................................................................................3
Table of Contents ................................................................................................................................4
1 Safety Notes .................................................................................................................................9
1.1 General safety instructions .................................................................................................... 9
1.2 Notes on usage ................................................................................................................... 12
2 Getting Started with MindSphere ................................................................................................ 13
2.1 Aim of Getting Started ......................................................................................................... 13
2.2 Functional overview of MindSphere ..................................................................................... 13
2.3 Structure of MindSphere Service Provision .......................................................................... 14
2.4 Working with MindSphere .................................................................................................... 16
3 Prepare MindConnect Nano for MindSphere .............................................................................. 19
3.1 Overview ............................................................................................................................. 19
3.2 Check package upon delivery .............................................................................................. 19
3.3 Connect the device .............................................................................................................. 21
3.3.1 Connect the power supply ............................................................................................ 21
3.3.2 Connect device to networks .......................................................................................... 22
3.4 Commission the device........................................................................................................ 23
3.4.1 General information on commissioning ......................................................................... 23
3.4.2 Switch on the device ..................................................................................................... 23
3.5 Result .................................................................................................................................. 23
4 Onboard MindConnect Nano to MindSphere .............................................................................. 25
4.1 Overview ............................................................................................................................. 25
4.2 Log into MindSphere............................................................................................................ 26
4.3 Configure Asset data ........................................................................................................... 26
4.4 Configure MindConnect Nano.............................................................................................. 30
4.4.1 Network configuration ................................................................................................... 30
4.5 Transfer configuration to USB stick...................................................................................... 34
4.6 Connect Port X2P1 .............................................................................................................. 36
4.7 Result .................................................................................................................................. 37
5 Configure Data Collection ........................................................................................................... 39
5.1 Overview ............................................................................................................................. 39
4 MindSphere – Getting Started, 10/2016

Table of Contents
5.2 Log into MindSphere............................................................................................................ 40

5.3 Configure Aspects ............................................................................................................... 40
5.3.1 Configure S7 Protocol................................................................................................... 42
5.3.2 Configure OPC UA Protocol ......................................................................................... 44
5.4 Result .................................................................................................................................. 47
6 Perform visual analysis on Assets .............................................................................................. 48
6.1 Overview ............................................................................................................................. 48
6.2 Monitor Assets in the MindApp Fleet Manager..................................................................... 48
6.2.1 Find an Asset ............................................................................................................... 48
6.2.2 View Aspects and Requests ......................................................................................... 51
6.3 Configure Requests ............................................................................................................. 55
6.3.1 Create a Rule for automatically generated Requests .................................................... 55
6.3.2 Create a manual Request ............................................................................................. 59
6.4 Result .................................................................................................................................. 60
7 Appendix ....................................................................................................................................61
7.1 Technical Specifications of MindConnect Nano ................................................................... 61
7.1.1 ESD guideline ............................................................................................................... 64
7.1.2 Structure of MindConnect Nano interfaces ................................................................... 66
7.2 Mounting MindConnect Nano .............................................................................................. 69
7.2.1 Permitted mounting positions and surrounding temperature ......................................... 69
7.2.2 Connecting the protective earth .................................................................................... 70
7.2.3 Mounting types ............................................................................................................. 71
7.2.4 Installing the cable strain relief...................................................................................... 72
7.2.5 Installing Ethernet connector strain relief ...................................................................... 72
7.3 Maintaining MindConnect Nano ........................................................................................... 73
7.3.1 Replacing the backup battery ....................................................................................... 73
7.3.2 Firmware update of MindConnect Nano ....................................................................... 75
7.4 Handling of Asset ................................................................................................................ 76
7.4.1 Overview of OPC UA data types ................................................................................... 76
7.4.2 Overview of S7 data types ............................................................................................ 76
7.4.3 List of measuring units .................................................................................................. 77
7.4.4 Asset handling in Asset Configuration .......................................................................... 80
7.4.5 Save and share a configured view in the Fleet Manager............................................... 82
7.4.6 MindSphere Units for Data Modeling ............................................................................ 83

Table of Contents
7.5 Offboard MindConnect Nano ............................................................................................... 88

7.6 User Account management ................................................................................................. 89
7.6.1 User rights .................................................................................................................... 89
7.6.2 Create and modify a user and a customer user ............................................................ 91
7.6.3 Reset login password ................................................................................................... 94
7.7 Troubleshooting ................................................................................................................... 95
7.8 List of abbreviations ............................................................................................................. 97
8 Glossary .....................................................................................................................................98
Account Overview ....................................................................................................................... 98
Aspect ........................................................................................................................................ 98
Asset ..........................................................................................................................................98
Asset ID ...................................................................................................................................... 98
Asset Type ................................................................................................................................. 98
Data Point ................................................................................................................................... 98
Data Source................................................................................................................................ 99
Event ..........................................................................................................................................99
Last Connection .......................................................................................................................... 99
MindApp ..................................................................................................................................... 99
MindApp Fleet Manager.............................................................................................................. 99
MindConnect Nano ................................................................................................................... 100
MindConnect Nano ID .............................................................................................................. 100
MindSphere Customer Management ........................................................................................ 100
MindSphere Launchpad ............................................................................................................ 100
MindSphere .............................................................................................................................. 100
MindSphere Asset Configuration .............................................................................................. 100
MindSphere Units ..................................................................................................................... 101
MindSphere User Management ................................................................................................ 101
Offboarding Process ................................................................................................................. 101
Onboarded/Offboarded Mode ................................................................................................... 101
Onboarding Process ................................................................................................................. 101
Online/Offline Mode .................................................................................................................. 102
Operation Center ...................................................................................................................... 102
Request .................................................................................................................................... 102
Rule .......................................................................................................................................... 102

Table of Contents
Time Series .............................................................................................................................. 103

Table of Contents

Safety Notes
1 Safety Notes
1.1 General safety instructions
WARNING
Life-threatening voltages are present with an open control cabinet
When you install the device in a control cabinet, some areas or components in the open
control cabinet may be carrying life-threatening voltages.
If you touch these areas or components, you may be killed by electric shock.
Switch off the power supply to the cabinet before opening it.
System expansions
NOTICE
Damage through system expansions
Device and system expansions may be faulty and can affect the entire machine or plant.
The installation of expansions can damage the device, machine or plant. Device and
system expansions may violate safety rules and regulations regarding radio interference
suppression. If you install or exchange system expansions and damage your device, the
warranty becomes void.
Note the following for system expansions:
Only install system expansion devices designed for this device. Contact your technical
support team or the team where you have purchased your PC to find out which system
expansion devices may safely be installed.
Observe the information on electromagnetic compatibility (EMC). Refer to the chapter
Appendix Technical Specifications.
NOTICE
"Open Type" UL508
Note that the device is classified as "Open Type" for use in the area of Industrial Control
Equipment (UL508). Installation of the device in an enclosure complying with UL508 is a
prerequisite for approval or operation in accordance with UL508.

Safety Notes
Battery and rechargeable battery
WARNING
Risk of explosion and release of harmful substances
Improper handling of lithium batteries can result in an explosion of the batteries.
Explosion of the batteries and the released pollutants can cause severe physical injury.
Worn batteries jeopardize the function of the device.
Note the following when handling lithium batteries:

• Replace used batteries in good time; see the section "Replacing the
backup battery" in the operating instructions.
• Replace the lithium battery only with an identical battery or types
recommended by the manufacturer.
• Do not throw lithium batteries into fire, do not solder on the cell body, do
not recharge, do not open, do not short-circuit, do not reverse polarity, do
not heat above 100°C and protect from direct sunlight, moisture and
condensation.
Strong high-frequency radiation
NOTICE
Observe immunity to RF radiation
The device has an increased immunity to RF radiation according to the specifications on
electromagnetic compatibility in the technical specifications.
Radiation exposure in excess of the specified immunity limits can impair device
functionality resulting in malfunctions and therefore injuries or damages.
Read the information on immunity to RF radiation in the technical specifications.
ESD Guideline
Electrostatic sensitive devices can be labeled with an appropriate symbol
NOTICE
Electrostatic sensitive devices (ESD)
When you touch electrostatic sensitive components, you can destroy them through
voltages that are far below the human perception threshold.
If you work with components that can be destroyed by electrostatic discharge, observe the
ESD Guideline. Refer to the chapter “ESD guideline”.

Safety Notes
Disclaimer for third-party software updates

This product includes third-party software. Siemens AG only provides a warranty for
updates/patches of the third-party software, if these have been distributed as part of a
Siemens software update service contract or officially released by Siemens AG. Otherwise,
updates/patches are undertaken at your own risk. You can find more information about our
Software Update Service offer on the Internet at Software Update Service
(http://w3.siemens.com/mcms/topics/en/simatic/licenses/software-update-
service/Pages/Default.aspx).
Open Source Software

Siemens will identify the open source software components contained in MindConnect Nano,
including the applicable license text and will include such license text(s) in or provide them
together with MindConnect Nano. Should the license(s) applicable to any part of the open
source software require the distribution of the open source software’s source code and build
scripts together with MindConnect Nano (or, alternately, an offer to make the source code and
build scripts available upon request), then Siemens will provide such source code or such offer
to customer together with MindConnect Nano. No license fee is charged to customer for the
use of such open source software. Customer acknowledges and agrees that Siemens
provides no warranties, express or implied, and no indemnification for the open source
software itself. Customer hereby accepts that the open source software is subject to the
specific license terms included in or provided together with MindConnect Nano. To the extent
there is a conflict between these terms and the open source specific license terms, such terms
shall prevail with regard to the open source software.
Industrial Security
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems, machines and
networks. Systems, machines and components should only be connected to the enterprise
network or the internet if and to the extent necessary and with appropriate security measures
(e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. For more information about industrial security, please visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends to apply product updates as soon as available and to
always use the latest product versions. Use of product versions that are no longer supported,
and failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under http://www.siemens.com/industrialsecurity.

Safety Notes
1.2 Notes on usage

NOTICE
Possible functional restrictions in case of non-validated plant operation
The device is tested and certified on the basis of the technical standards. In rare cases,
functional restrictions can occur during plant operation.
Validate the correct functioning of the plant to avoid functional restrictions.
Note
Use in an industrial environment without additional protective measures
This device was designed for use in a normal industrial environment according to IEC 60721-
3-3

Getting Started with MindSphere
2 Getting Started with MindSphere

2.1 Aim of Getting Started
This Getting Started provides you with information to get acquainted with commissioning the device
MindConnect Nano and working with MindSphere. This manual does not contain a comprehensive list
of all possible functions, but includes all necessary information to start working with MindSphere.
By using the examples given in this manual, you will be able to develop or change your service. You
will know how to access and configure data of your Assets as well as create and answer Requests.
You will work through typical steps involved in configuring the device (MindConnect Nano) and your
Asset data. You will become familiar with the tools that MindSphere provides for configuration and
visualization of Assets and Requests, in addition to managing customers and users.
2.2 Functional overview of MindSphere

This part of Getting Started outlines a functional overview of MindSphere. Please refer to the glossary
section of the Appendix for a list of vocabulary used in this documentation.
MindSphere offers the means to monitor Asset status as well as support maintenance and services.
This requires sensor data, the tools to collect and transfer data as well as intelligent software that
offers the monitoring and support functions.
Mind Connect Nano provides the hardware for collecting data from Asset and transferring it to
MindSphere, which includes hosting the Web User Interfaces.
MindSphere records Events and environment information, including the timestamps.
Figure 2-1 MindSphere overview

With MindSphere and MindConnect Nano you can:

• Create and manage users and customers.
• Create, manage and change Assets in MindSphere Asset Configuration
• Onboard MindConnect Nano to MindSphere in order to collect data from your Assets
and transfer it to MindSphere.
• Collect data of data sources via (S7, OPC UA) via MindConnect Nano.
• Visualize the uploaded data (time series).
• Display Data Points and open Requests of an Asset.
• Manage the connected Assets and automate Rules.
• See available application (MindApps Fleet Manager) and all MindSphere Units per
App for current configuration for Asset
• Subscribe or unsubscribe MindAccess
2.3 Structure of MindSphere Service Provision

This chapter describes the overall structure of service provision of MindSphere.
MindSphere consists of the following elements:
Figure 2-2 MindSphere elements
MindConnect Nano
MindConnect Nano is a device that establishes the connection to MindSphere in order to
collect data from an Asset and transfer it to MindSphere.
After the initial onboarding to MindSphere, MindConnect Nano receives the required
configuration (e.g. network configuration, configuration of physical Asset) from MindSphere.

MindConnect Nano can be connected via Ethernet to SIMATIC S7-300/400 PLCs and OPC
UA server. It supports onboarding of an Asset to MindSphere on a one to one basis.
MindSphere Launchpad
MindSphere Launchpad is the entry point to the user interfaces (MindApps) for configuration
and data visualization. MindSphere Apps can be opened from an up to date browser with
HTML5 capabilities. In MindSphere you can create, configure, onboard and visualize a "Digital
Twin" of an Asset via graphical interfaces.
MindSphere Launchpad is comprised of the following elements:
MindSphere Asset Configuration

The Asset Configuration offers the means to do configurations on an Asset and MindConnect
Nano:
• Definition of the data structure and properties of an Asset.
• Connection setup. Definition of the required information of MindConnect Nano to
connect it to MindSphere.
• Asset metadata management - e.g. Asset Location.
MindApp Fleet Manager

Fleet Manager is used for getting an overview of existing Assets and their basic information as
well as visualization of Asset data. In the Fleet Manager you can monitor the status of all
Assets and detail data analyzation (variables with Aspects, view in different graphs etc.). It is
also possible to save as bookmark or share configured view.
Fleet Manager displays the configured Assets in a list or area. Furthermore, Aspects and
Requests of the selected Asset can be shown.
A search for specific Assets and Requests can be performed by setting filters, sorting or free
text searching.
In three different charts (line, pie and bar charts) the values of variables assigned to Aspects
can be displayed in different time frames (time picker).
Fleet Manager enables definition of Rules for automatic generating of Requests and creation
of manual requests.
MindSphere User and Customer Management

User Management
User Management is the administration of MindSphere user accounts. There are two roles of
users with different rights for managing and displaying: Admin and User.
Customer Management
At the Customer Management, the Admin can create accounts for their customers. Assets
can be assigned to a customer in Asset Configuration in order to let users of this customer
see the assigned Assets. Login for customer users can also be administrated by the Admin in
customer configuration.

Account Overview
In Account Overview you find a table with all available applications (e.g. MindApp Fleet Manager)
and all MindSphere Units per App for configured Assets.
For more information on MindSphere Units refer to chapter “MindSphere Units”.
2.4 Working with MindSphere

This part of Getting Started provides you with a brief summary of instructions described in detail in
this manual.
Requirements
• Internet Connection and browser for online User Interface. Browser supporting HTML5
(recommended are Firefox 43.0, Google Chrome 47.0, Safari iPad)
• Internet Connection for MindConnect Nano device. Provide standard HTTPS
capabilities for MindConnect Nano - outbound HTTPs connections on port 443
• Link to the online Launchpad with user and password data as it was submitted by
Siemens
• Device (PC, tablet etc.) with minimum screen resolution of 1024x768
Configuring steps
Prepare MindConnect Nano for MindSphere

• Mount MindConnect Nano on your physical Asset.
• Configure your corporate network to allow outbound traffic for MindConnect Nano.
• Commission your Asset hardware.
Onboard MindConnect Nano to MindSphere
• Log into your MindSphere account.
• Configure your Asset and MindConnect Nano, which is mounted to your physical
Asset.
• Configure Network Settings of MindConnect Nano and Proxy as needed to establish
internet connection to MindSphere.
• Establish the initial connection (onboarding) by transferring the configuration manually
by USB stick.
Configure data collection
• Log into MindSphere with your account.
• Configure the Data Points you want to acquire.
• MindConnect Nano receives the configuration from MindSphere via an existing
internet connection.
• MindConnect Nano starts the data acquisition.
• The time series can be displayed in the Visual Analyzer.
• If required, you can change Asset configuration, duplicate or delete Asset.
Perform visual analysis on Assets
• Monitor Assets in different views
• Monitor Aspects and thresholds of selected Data Points in different charts

• Create manual Requests or Rules for automatically generated Requests to monitor

values of Data Points.


3 Prepare MindConnect Nano for MindSphere

3.1 Overview
This chapter provides a general overview on connecting and commissioning of MindConnect Nano in
order to prepare it for MindSphere. For further details refer to the Appendix of this documentation
(chapters ”Technical Specifications of MindConnect Nano”, “Mounting MindConnect Nano”).
MindConnect Nano is a compact and embedded industrial PC. It is able to connect to MindSphere,
collect data from the field and transfer it encrypted to MindSphere. To connect MindConnect Nano to
MindSphere (onboarding), MindConnect Nano must be prepared: mounted, connected to MindSphere
network and commissioned.
Figure 3-1 MindConnect Nano
3.2 Check package upon delivery

1. When accepting a delivery, please check the package for visible transport damage.
2. If any transport damage is present at the time of delivery, lodge a complaint at the shipping
company in charge. Have the shipper confirm the transport damage immediately.
3. Unpack the device at its installation location.
4. Keep the original packaging in case you have to transport the unit again.
Note
Damage to the device during transport and storage
If a device is transported or stored without packaging, shocks, vibrations, pressure and moisture
may impact the unprotected unit. Damaged packaging indicates that ambient conditions may
have already had a massive impact on the device.
The device may be damaged.
Do not dispose of the original packaging. Pack the device during transportation and storage.

5. Check the contents of the packaging and any accessories you may have ordered for
completeness and damage.
6. If the contents of the package are incomplete, damaged or do not match your order, inform the
responsible delivery service immediately.
WARNING
Electric shock and fire hazard due to damaged device
A damaged device can be under hazardous voltage and trigger a fire in the machine or plant. A
damaged device has unpredictable properties and states.
Death or serious injury could occur.
Make sure that the damaged device is not inadvertently installed and put into operation. Label the
damaged device and keep it locked away. Return the device for immediate repair.
NOTICE
Damage from condensation
If the device is subjected to low temperatures or extreme fluctuations in temperature during
transportation, for example in cold weather, moisture could build up on or inside the HMI device.
Moisture causes a short circuit in electrical circuits and damages the device. In order to prevent
damage to the device, proceed as follows:
Store the device in a dry place.
Bring the device to room temperature before starting it up.
Do not expose the device to direct heat radiation from a heating device.
If condensation develops, wait approximately 12 hours or until the device is completely dry before
switching it on.
7. Please keep the enclosed documentation in a safe place. It belongs to the device. You will
need the documentation when you commission the device for the first time.
8. Write down the identification data of the device.

3.3 Connect the device

This chapter shows you how to connect MindConnect Nano to the power supply and to the internet
(MindSphere).
3.3.1 Connect the power supply

Requirements
• The protective conductor is connected. Refer to the chapter “Connecting the protective earth”.
• A two-core cable with a cable cross-section of 0.75 mm² to 2.5 mm² for the 24 VDC
connection.
• A slotted screwdriver with a 3mm blade.
Note
The device should only be connected to a 24 VDC power supply which satisfies the requirements of
safety extra low voltage (SELV) according to IEC/EN/DIN EN/UL 60950-1.
The power supply must meet the NEC Class 2 or LPS requirement in accordance with IEC/EN/DIN
EN/UL 60950-1.
The MindConnect Nano package does not include power supply. The appropriate power supply
product from Siemens with the name SITOP could be used.
Procedure
1. Switch off the 24 VDC power supply.
2. Connect the cores of the power supply.
3. Insert the terminal at the indicated position.
Figure 3-2 Power supply

3.3.2 Connect device to networks

The following options are available for integrating the device in existing or planned system
environments and networks.
Figure 3-3 Interfaces of MindConnect Nano
Enclosure Usage
Nr. Description
Label
RJ45 Ethernet connection

PN/IE LAN X1 1 for 10/100/1000 Mbps
1 Access to the internet (to MindSphere)
P1 To start Onboarding
process
USB 2.0 port, high current.

2 X63 Required during Configuration File on USB stick
onboarding process.
RJ45 Ethernet connection

PN/IE LAN X2 1 for 10/100/1000 Mbps Access to the plant network (e.g.
3
P1 To complete Onboarding S7,OPC UA)
process
• Before you start with, Onboarding insert Ethernet cable into the port labeled with X1P1 to
connect to MindSphere.
Figure 3-4 Connecting the port X1P1 for internet (MindSphere)

Note
During the onboarding process, only one USB stick is supported. Do not plug in more than one USB
stick. The recommended USB port is the USB port with label X63.
It is recommended to connect your field Asset via the port X2P1 (plant network) after the onboarding
process.
3.4 Commission the device

This chapter shows you how to commission MindConnect Nano.
3.4.1 General information on commissioning
CAUTION
Danger of burns
The surface of the device can reach temperatures of over 70 °C. Any unprotected contact may
cause burns.
Avoid direct contact during operation of the device. Touch the device only with appropriate
protective gloves.
3.4.2 Switch on the device
Requirements
• The device connected to the power supply.
• The network cables plugged in correctly.
Procedure
1. Set the on/off switch to position "I" (ON). The "PC ON/WD" LED lights up.
Figure 3-5 Set the switch to “ON”
3.5 Result
You can onboard MindConnect Nano to MindSphere after connecting the interfaces of MindConnect
Nano and switching it on.


4 Onboard MindConnect Nano to MindSphere

4.1 Overview
This chapter describes the initial configuration of an Asset and MindConnect Nano in order to onboard
MindConnect Nano to MindSphere.
To establish the initial connection between MindConnect Nano and MindSphere (onboarding), you
have to configure essential Asset and MindConnect Nano data. For onboarding full configuration is
not required, although you can accomplish all steps in the Asset Configuration. To configure an Asset
for data collection, refer to chapter “Configure Data Collection”.
The respective data to be configured for onboarding is described in the following procedure.
Requirements
• MindConnect Nano connected to the internet and powered on.
• The connection cable for the internet is correctly plugged into the Ethernet port for the
internet (MindSphere).
• You have received the link to the MindSphere UI with credentials (user and password
data).
A customer account is created (refer to chapter “Customer Management")
Procedure
In order to onboard MindConnect Nano, proceed as follows:
1. Log into MindSphere.
2. Configure Asset data.
3. Configure MindConnect Nano.
Note
If nothing else is configured manually, MindConnect Nano will try to obtain IP addresses for both
adapters via DHCP. Please refer to the chapter “Configure MindConnect Nano” of this document.
4. Export the initial configuration to your local USB stick.

5. Insert the USB stick into the port of MindConnect Nano.
6. Connect Ethernet cable for data acquisition into the port X2P1 (Access for plant network).
Result
The initial connection between MindConnect Nano and MindSphere is established by transferring
the configuration manually via USB stick. Any subsequent Asset configuration will automatically
be synchronized (except network configuration) with the onboarded MindConnect Nano. The
connection to the Asset is permanent and can only be cancelled by offboarding. For this purpose,
refer to chapter “Offboard MindConnect Nano”.

4.2 Log into MindSphere

• Log into MindSphere by clicking on the link, received per email from Siemens.
• The MindSphere landing page for login will appear.
• Log into MindSphere with personal login data and agree to the terms of use upon reading
them.
• You will be redirected to MindSphere Launchpad.
Figure 4-1 MindSphere Launchpad
Note
MindSphere supports only English and German languages. Therefore it is recommended to set
the browser default to English, if you use a different language.
4.3 Configure Asset data

This chapter outlines how to configure the data for your Asset.
To establish the initial connection of MindConnect Nano to MindSphere, you can create a new Asset
or copy an already created Asset (refer to chapter “Duplicate an Asset”).
In order to create and configure a new Asset, proceed as follows:

• Go to MindSphere Launchpad (see image 4-1), open Asset Configuration. The overview
page with Asset list and specific information (Asset name and ID, customer name, onboarded
and online statuses as well as progress of Assets configuration) will be displayed, when
Assets have already been configured. In case that there are no Assets, the Asset list will be
empty and you create a very first Asset.
• Click Add New Asset.
Figure 4-2 Creating a new Asset
The dialog window with four steps appears.

• In the first step Asset Information, enter Asset name, Asset type, Asset ID and description,
which can be freely specified. You can also upload an Asset image.
Figure 4-3 Specifying Asset Information

• Procced to the second step Location or click Next. This step is not mandatory for onboarding
and can be configured later. Though information from Location will be shown with an Asset in
the list view of the MindApp Fleet Manager.
• Select Customer name, specify Asset location: Country, City, Street etc.
A customer area map can be attached to an Asset, so that the asset location can be visualized in
the Fleet Manager.
• To create an area, click Add:
Figure 4-4 Adding an area
• Enter freely chosen area name, e.g. “Hall2”. Then click Update and upload a picture from your
computer.
Figure 4-5 Uploading an area picture
• Click Save to confirm the configuration.

Figure 4-6 Specifying Asset Location
In the image there is an area with name “Hall2” and uploaded area map “Plan.jpg”. The image has to
be in any raster format e.g. *.jpg, *.jpeg, *.gif, *.bmp, *.png and can have a maximum size of 10 MB. It
is recommended the image width to be approximately 500 px. After saving, you have the option to
add an additional area, edit or delete an existing area.
Important hint
When opening an Asset with existing area map. In this case some buttons are deactivated, that it's
not possible to add an area or to upload a picture. In this case follow the next steps:
• Deselect the customer
• Select the customer again. The buttons are accessible again.

Please note that for any action (create area, upload picture, etc.) the configuration must be saved to
get the changes active.

• After you have configured Location, go to the next step by clicking MindConnect
Management or Next to configure MindConnect Nano.
4.4 Configure MindConnect Nano

This chapter informs you how to configure MindConnect Nano information and network connection.
MindConnect Nano is configured in MindConnect Management. By clicking on MindConnect
Management overview a dialog window with four steps appears, where you can start configuration by
selecting Start configuration or the first step Information.
• Enter the MindConnect Nano Unique ID, which can be obtained from the rating plate located
on the back panel of your MindConnect Nano.
Figure 4-7 Configuring MindConnect Nano Information with example ID
The next step to be configured is network configuration of MindConnect Nano.
4.4.1 Network configuration

Network configuration of MindConnect Nano requires information on the Ethernet interfaces for data
acquisition (Ethernet labeled with X2P1) and MindSphere (Ethernet labeled with X1P1). If your
company uses a proxy server, it must also be configured to connect MindConnect Nano to
MindSphere. Contact your IT administrator for details on your local network settings.
Proceed to the next step either by clicking Next in the MindConnect Management window or click the
Ethernet Interface for Data Acquisition or Next to configure network configuration for access to
Data Sources (S7 PLC 300/400 or OPC UA server).There are two options to configure the plant
network. You can enter either static IP address or use DHCP. The last option is possible, if there is a
DHCP server available in your company network.

• For static IP address, enter the respective information.
Figure 4-8 Configuring Ethernet for plant network: static IP address
• For DHCP, select the DHCP check box.
Figure 4-9 Configuring Ethernet for plant network: DHCP

To configure interfaces for the internet access, go to Ethernet Interface for MindSphere
Connection or click Next. There are also two options to connect to MindSphere. You can enter either
a static IP address or use DHCP. The last option is possible, if there is a DHCP server available in
your company network.
• For static IP address, enter the respective information (DNS server is optional).
Figure 4-10 Configuring Ethernet for MindSphere: static IP address
• For DHCP, select the DHCP check box.
Figure 4-11 Configuring Ethernet Interface for MindSphere: DHCP

If required, you can configure a proxy server as well. Consult your company IT department if you need
to configure a proxy.
To configure a proxy, go to Proxy:
• Select the Proxy exists check box. Enter IP address, port of proxy server. You can specify
also user name and password, but it is not mandatory.
Figure 4-12 Configuring Proxy
Supported types of Proxy authentication are:

• Basic (User name + password)
• Digest (User name + password)
• Anonymous (No User name + password, leave it empty)
Proxy supports https/https, no SOCKS.

To complete the configuration, click Save. Then go to Overview, click Save and export to USB to
transfer this configuration to USB device.
Figure 4-13 Saving and exporting configuration to USB device
4.5 Transfer configuration to USB stick

In order to transfer the configuration to the USB stick, proceed as follows:
• Download the configuration file for the Asset and copy or move it to the root directory of your
USB stick.
Note
The USB stick has to be FAT or FAT32 formatted and may only contain a single partition.
The configuration file in the USB stick is only valid for seven days.
• Switch on MindConnect Nano.

MindConnect Nano starts up.

• Make sure that Ethernet ports of MindConnect Nano are connected as described in chapter
“Connect device to networks”.
• Wait, until the power LED light “PC ON/WD” on MindConnect Nano is GREEN.
Figure 4-14 LED “PC ON/WD”
• Insert the USB stick with configured Asset data into the USB port (X63) of MindConnect
Nano.
MindConnect Nano recognizes the USB configuration and the LED light “RUN/STOP /L1” will
show ORANGE during configuration. The Onboarding status in Asset Configuration will be
displayed orange for a short time.
MindConnect Nano receives configuration from USB and deploys it. The LED light
“RUN/STOP /L1” will at first blink GREEN and then change to constant GREEN.
Figure 4-15 LED “RUN/STOP /L1”
If the LED light “RUN/STOP /L1” remains ORANGE, refer to chapters ”LED lights ” and
“Troubleshooting”.
• Remove USB device from MindConnect Nano.
• Check status on MindConnect Nano and Asset Configuration:
Make sure that LED lights “PC ON/WD”, “RUN/STOP /L1” show a constant GREEN.
MindConnect Nano is now successfully onboarded to MindSphere.

Figure 4-16 LEDs "PC ON/WD" and "RUN/STOP/L1"
• Make sure that the UI shows the status Onboarded and the status Online (internet
connection between MindConnect Nano and MindSphere). Refresh of the Asset
Configuration is required.
Figure 4-17 Onboarded and Online status
Note
If you make changes on the network configuration of already onboarded MindConnect Nano,
these changes must be transferred to MindConnect Nano via USB stick.
4.6 Connect Port X2P1

After configuring your Asset, MindConnect Nano and transfering configuration via USB drive to
MindConnect Nano, you can now insert the Ethernet cable for your plant network into the port labeled
with X2P1.

• Insert the plant network cable into the port X2P1
Figure 4-18 Connecting Ethernet Port X2P1 for data acquisition
4.7 Result
The initial connection between MindConnect Nano and MindSphere is established.
Once MindConnect Nano is onboarded, the connection to your Asset is permanent and your
Asset for data collection can be configured. This requires configuration of machine data to be
monitored. Any additional configuration (except network configuration) of the connected Asset
will automatically be synchronized with your onboarded MindConnect Nano.


Configure Data Collection
5 Configure Data Collection

5.1 Overview
This part of Getting Started shows how to enable data collection by configuring the data from the field
in the Asset Configuration after an Asset has been onboarded. This therefore necessitates full
configuration of machine data (Data Points).
Requirements
• A PC with internet access.
• MindConnect Nano is onboarded
• Valid credentials (user and password data) for MindSphere.
Procedure
To configure data to be collected from your Asset, proceed as follows:
1. Log into your MindSphere account.
2. Configure Asset Aspects
3. Configure the Data Points collected by MindConnect Nano from the Asset.
Result
MindConnect Nano receives the configuration from MindSphere via an existing internet connection.
MindConnect Nano starts the data acquisition. The time series will be displayed in the MindApp Fleet
Manager.
Note
When two different users edit the same Asset concurrently, the changes on the Asset made by the
last user will be saved.
There is no notification among the different users about the changes the other user has made.
Note
The number of Assets created in the Asset Configuration is limited. You can create up to 10 000
Assets.
If the number of assets reaches 10.000, the button Add new Asset will be disabled . To create new
Assets some old Assets need to be deleted.

5.2 Log into MindSphere

Refer to the steps in chapter “Log into MindSphere” to log into MindSphere.
5.3 Configure Aspects

This chapter provides information on configuring Aspects for Data Sources (S7 and OPC UA). Data
Points are attached to a respective Aspect. The number of Data Points is limited. A maximum of 110
Data Points per MindConnect Nano can be defined.
The following diagram provides the information on the relationship between Aspects, Data Sources
(OPC UA and S7) with reference data from the physical Asset and their configuration in MindSphere.
Figure 5-1 Asset Configuration
The diagram shows the Data Points “Pressure_1”, “Pressure_2” as well as “Power_1”, “Power_2”
which belong to their corresponding Aspects (PressureStatus or EnergyConsumption) and have their
references to Data Sources (OPC UA and S7).
To configure Aspects, proceed as follows:
• Go to MindSphere Launchpad, click Asset Configuration.
• Select your onboarded Asset. You can search for your Asset by Asset name, ID or customer’s
name in the search box. Click icon to edit your Asset.

Figure 5-2 Editing an Asset
The dialog window of Asset Configuration appears.
• Go to the step Aspects. The dialog window with Aspect configuration will be opened showing
MindSphere Units: 1, which is the default value for an unconfigured Asset. An Asset has
been created and onboarded, but Aspects have not yet been configured for this Asset. For
more information, refer to chapter “MindSphere Units for Data Modeling”.
Figure 5-3 MindSphere Units in Aspects
• Click Add Aspect. Specify Aspect Name e.g. “PressureStatus”. Select Data Source
Protocol: you can select between S7 or OPC UA protocols for each Aspect.

5.3.1 Configure S7 Protocol

To configure S7 Protocol, select S7 as Data Source protocol.
• Go to Configuration and enter IP Address of S7.
Figure 5-4 Configuring S7 Address
Configuring the reading cycle affects the speed data collection of your Asset. By default, the data will
be collected at a cycle speed of 5 seconds. Speed of the reading cycle affects amount of MindSphere
Units as well (refer to chapter “MindSphere Units for Data Modeling”).
5.3.1.1 Configure S7 Data Points

To configure Data Points, proceed as follows:

• Go to Data Points and click Add Data Point.

• Enter specified name, address and data type of Data Points to be monitored in the MindApp
Fleet Manager.
• Select a respective physical unit in the UNIT list or leave it empty.
Figure 5-5 Configuring Data Points for S7
• To enter an address of Data Point in S7, see how it is configured in the S 7. Refer to the
official documentation of STEP 7 Engineering and TIA Portal.
Figure 5-6 Configuring S7 data in the STEP 7 Engineering UI.
Note
Basic knowledge of S7 300/400 engineering is required. This documentation does not provide this
knowledge. Please refer to the official S7/UI TIA-Portal documentation.
Refer to chapter “Overview of S7 data types” for detailed information on data types.
You can configure further Data Points and confirm the configuration by clicking Save and confirming
Accept actual settings

5.3.2 Configure OPC UA Protocol

To configure OPC UA, click Add Aspect
• Specify Aspect name e.g. “EnergyConsumption” and select OPC UA as Data Source Protocol.
Go to Configuration and enter OPC server name and address.
Figure 5-7 Configuring OPC UA server
OPC server name can be freely chosen. For address you need specify an IP address und port
number, for example: opc.tcp://192.168.47.11:5121

5.3.2.1 Configure OPC UA Data Points

To configure OPC UA Data Points, proceed as follows:
• Go to Data Points, click Add Data Point and specify name, address and data type of Data
Points to be monitored in the MindApp Fleet Manager. You can select a respective physical
unit in the UNIT list or leave it empty.
Figure 5-8 Configuring OPC UA Data Points
Configuring the reading cycle affects the speed data collection of your Asset. By default, the data will
be collected at a cycle speed of 5 seconds. Speed of the reading cycle affects amount of MindSphere
Units as well (refer to chapter “MindSphere Units for Data Modeling”).

ADDRESS Configuration of Data Points in OPC UA in detail
There are two options to address an OPC UA Data Point.
1. Direct addressing
NodeId:ns=7;s=PLC1.MachineData.Power_1
Figure 5-9 Direct addressing
2. Object path addressing
/opcua//Objects/1:SYM:/7:PLC1/7:MachineData/7:Power_2|serverURL:opc.tcp://192.168.0.14
:55101
Figure 5-10 Object path addressing

After you have configured your Data Sources via OPC UA or S7 protocol, confirm your configuration
with Save.
Each time, when saving an Asset, where the Aspect configuration was changed, a dialog box appears
informing you of the newly calculated MindSphere Units. Due to the changed Aspects, amount of
MindSphere Units changes as well.
• Confirm Accept actual settings and save the Asset:
Figure 5-11 Confirming actual settings
5.4 Result
MindConnect Nano receives the configuration from MindSphere via an existing internet
connection. MindConnect Nano starts the data acquisition. You can go to the Fleet Manager, to
see time series of a configured Asset.

6 Perform visual analysis on Assets

6.1 Overview
This chapter describes how to receive the status of your fleet and investigate in detail the data of your
Assets.
Requirements
• MindConnect Nano is connected to the internet and onboarded
• Aspects and Data Points are configured
Procedure
To see the visualized data and perform further processing on an Asset, you can proceed as follows:
1. Monitor Assets in list view and searching them by sorting and filtering as well as configuring
their Aspects in different charts.
2. Creating Rules und Requests for threshold monitoring of variables.
Result
You will get automatic Requests for your Assets. You can drill down to analyze status, send manual
Requests or adapt Rules for automatic Requests.
6.2 Monitor Assets in the MindApp Fleet Manager

This chapter describes how to monitor data of a selected Asset in the Fleet Manager. The configured
Assets in the Asset Configuration are already displayed in the list on the left side of the Fleet
Manager window.
6.2.1 Find an Asset

The MindApp Fleet Manager offers some options for viewing and easy finding/sorting/filtering
of Asset(s) to be monitored.
To view an Asset you can select between List, Hierarchy and Area views:
List: List shows Assets alphabetically sorted, which were configured in the Asset Configuration. The
Assets contain the following information: Asset name, customer, customer address and number of not
closed requests sorted by priority level.
To see the Assets in the List:

• Go to Fleet Manager in the MindSphere Launchpad. The overview page with Asset list
appears. Select a required Asset from the list.
Figure 6-1 Asset list
To quickly find the relevant Assets, you can restrict your Asset list by defining a filter and sorting.
Filter has the following criteria: country, severity of requests and customer. With sorting you can
change the order as follows:
• Assets alphabetically (A-Z)
• Assets with most Requests by priority first
• Assets with most Requests at all first
• To filter and sort click Filter&Sort
Figure 6-2 Setting a filter
In the example a customer 'tenantName' is selected and all Assets of this customer are displayed.
The filter icon indicates that one filter is set for this view.
You can use a search box as well and search for any text. Although, the search function is possible in
the list that is already loaded, this means that the search function is limited to the filtered objects.
Hierarchy: displays created areas per customer and Assets depending on the filter settings. If an
area is selected, you can use either List view or Area view. With a selected area of a customer you
can see an area map where an Asset is located.
To see Assets in the Hierarchy, proceed as follows:

• Click Hierarchy and select a customer e.g. “tenantName”, and then select an area e.g. “Hall-
2”
Figure 6-3 Configuring Hierarchy and List view
You can change from List to Area.

• Click the button Area (on smaller screen resolutions e.g. on a tablet click the button with the
icon ).
The selected area will show the Asset(s) as grey rectangular(s) and the area map picture.
The Assets can be selected by clicking on them.
Figure 6-4 Configuring Hierarchy and Area view
The example shows, customer 'tenantName' is selected and area 'Hall-2 'is displayed. The hierarchy
icon has an exclamation mark icon meaning that a customer/area is selected.
As default there is no position assigned to the Assets.

• For changing the position and size of an Asset, click the edit button .
The position of an Asset can be changed by drag and drop. The size can be changed via the
corners, when the Asset is selected.
Figure 6-5 Editing an Asset
• Apply or reject the changes the buttons
6.2.2 View Aspects and Requests

After you have selected an Asset to be monitored, you can see the status of its single Aspects and
Requests in detail in the right column.
Aspects
If an Aspect is collapsed, the Asset name and the number of not closed Requests per priority level are
displayed.
If an Aspect is expanded, the last not closed Request per priority level is displayed as well as the data
of all data points in a graph.
• Go to Aspects, select and expand an Aspect e.g. ‘EnergyConsumption’:
Figure 6-6 Selecting and expanding an Aspect

In the Aspect view, you can monitor time series of variables by configuring the different views of the
charts and by setting time frame (Time picker: day, week, and month). There are the following types
of charts:
• Line chart
• Pie chart
• Bar chart.
Line chart: displays incoming values as data points connected with lines. These data points are the
values and shown according to period set in the time frame. Pie and bar charts show the last
available values of configured time frame or values from the time period, when a request was
selected.
You can use the mouse or two fingers gesture to zoom in and out the chart as desired. This only
applies for the actual chart, the time picker is not influenced.
You can sort the variables by their physical units e.g. to show only time series by “A” for power.
With time picker you can select day, week, month, quarter and year. If you choose <days>, you can
select any number of days. The whole day can be selected (from 0:00 to 24:00). Accordingly, weeks
(from Monday to Sunday) as well as months (from beginning till end of the month) can be chosen.
To configure a required time span, proceed as follows:
• Select e.g. week and any day of this week e.g. the 11th of August. It will automatically show
the whole week from Monday to Sunday.
Figure 6-7 Selecting time span
If the actual time span is selected, the refresh cycle is every 60 seconds.

Requests
The status of an Asset can also be monitored by viewing of Requests. If an Aspect is collapsed, not
closed Requests per priority level are also displayed:
Figure 6-8 Viewing Requests

• To view all Requests, go to Requests. A dialog window with all requests of an Asset will be
opened:
Figure 6-9 Viewing all Requests
A request can be created for only one variable. Therefore a request will be automatically assigned
to a respective Aspect
• To edit Request, select it and set it to InProcess or Closed.
Figure 6-10 Changing status of Requests

In this way, other users of the system can see that the Request is already being processed.
When you have completed the Request, set it to Closed. It is possible to set a completed Request to
InProcess again.
You can perform the Request status for one or more Requests at once by selecting multiple Requests
at the same time.
6.3 Configure Requests

In this chapter, you get to know how to configure Requests.
There are two ways to configure a Request in the Fleet Manager:
1. Create a Rule for automatically generating Requests: Rules are used to monitor a value and
the system will generate a Request if the value exceeds or falls below a threshold (flank
triggered).
2. Create Request manually, for example, to give information on a certain machine status or to
Request maintenance.
You can create several rules for each Asset and edit or delete them.
You can also delete several rules at once if necessary. A rule can monitor exactly one variable.
6.3.1 Create a Rule for automatically generated Requests
To create a Rule, proceed as follows:
• Go to Fleet Manager in the MindSphere Launchpad. Select an Asset and its Aspect to be
monitored (refer to the previous chapter “Monitor Assets in the MindApp Fleet Manager”).
• Select a variable of this Aspect and click icon
Figure 6-11 Creating a Rule for automatic Request

A dialog window with a table containing existing Rules will appear. The rules are displayed in this
table with the following columns: Rule name, Request priority, Event description and recommended
action
• Click + Add new rule to create a new rule. A wizard will lead you through the configuration.
Figure 6-12 Adding a new Rule
Dialog window with five rule steps appears.
• Select variable for monitoring and click Step 2.
Figure 6-13 Creating a rule - Step 1

• Select the Condition and enter a value, then click Step 3 to proceed.
• Set Request limitations, if required. You can select between: None, Limit requests in time or
Hysteresis. Then click Step 4 to proceed.

• In Prio select required priority (Urgent, Important and Information)

• Type text for Description and Action, and then proceed to Step 5.
• Change Rule name if necessary:

• Click Save to activate the Rule.
6.3.2 Create a manual Request

To create a manual Request, proceed as follows:
• Go to Fleet Manager in the MindSphere Launchpad. Select an Asset and its Aspect to be
monitored (refer to the previous chapter “Monitor Assets in the MindApp Fleet Manager”).
Then select a variable and click icon
Figure 6-18 Creating Manual Request

• Configure Description, Action, Severity, Timestamp and Measuring Point for manual Request.
• Click Create to activate your Request.
Figure 6-19 Configuring Manual Request
6.4 Result
You will get automatic Requests for your Assets. You can analyze status, send manual Requests or
adapt Rules for automatic Requests.

Appendix
7 Appendix
7.1 Technical Specifications of MindConnect Nano
Functions
Field protocol – S7 Siemens S7 (for S7-3xx / S7-4xx / ET-200s PLCs)
Field protocol – OPC UA Part 8 of the OPC UA specification (Data Access)
Configuration of data collection With Asset Configuration tool in MindSphere
Data buffering Up to 500 MB buffering space for collected data
Proxy support Yes
DHCP support Yes
Security Connection outbound via HTTPS on port 443 to

MindSphere only; no incoming connection accepted
SSL/TLS encryption of data in transit to MindSphere
Installation type/mounting
Mounting DIN rail, wall mounting, portrait mounting
Design Box PC, built-in unit
Supply voltage
Type of supply voltage 24 V DC
Mains buffering
● Mains/voltage failure stored energy time 20 ms
Processor
Processor type Intel Celeron N2807
Drives
CFast 4 GB
Memory
Type of memory DDR3L
Main memory 2 GB
Interfaces
USB port 1x USB 3.0 / 3x USB 2.0
PCIe slot 1x PCIe x1 (Disabled)
Serial interface 1x COM (Disabled)
Video interfaces
● Graphics interface 1x DisplayPort (Disabled)
Industrial Ethernet

Appendix
● Industrial Ethernet interface 2x 1000 Mbit RJ45
Monitoring functions
Status LEDs Yes
Fan No
EMC
Interference immunity against discharge of static electricity
● Interference immunity against discharge of ±6 kV contact discharge acc. to IEC 61000-4-2; ±8 kV air
static electricity discharge acc. to IEC 61000-4-2
Interference immunity to cable-borne interference
● Interference immunity on supply cables ±2 kV acc. to IEC 61000-4-4, burst; ±1 kV acc. to IEC
61000-4-5, surge symmetric; ±2 kV acc. to IEC 61000-4-
5, surge asymmetric
● Interference immunity on signal cables >30m ±2 kV acc. to IEC 61000-4-5, surge, length > 30 m
● Interference immunity on signal cables < 30m ±1 kV acc. to IEC 61000-4-4; burst; length < 3 m; ±2 kV
acc. to IEC 61000-4-4; burst; length > 3 m
Interference immunity against voltage surge
● asymmetric interference ±2 kV acc. to IEC 61000-4-5, surge asymmetric
● symmetric interference ±1 kV acc. to IEC 61000-4-5, surge symmetric
Interference immunity against high-frequency electromagnetic fields
● Interference immunity against high frequency 10 V/m for 80 - 1000 MHz and 1.4 - 2 GHz, 80% AM acc.
radiation to IEC 61000-4-3; 3 V/m for 2 - 2.7 GHz, 80% AM acc. to
IEC 61000-4-3; 10 V for 10 kHz - 80 MHz, 80% AM acc.
to IEC 61000-4-6
Interference immunity to magnetic fields
● Interference immunity to magnetic fields at 50 100 A/m; to IEC 61000-4-8

Hz
Emission of conducted and non-conducted interference
● Interference emission via line/AC current cables EN 61000-6-3, EN 61000-6-4, CISPR 22 Class B, FCC
Class A
Degree and class of protection

IP (at the front) IP40
IP (rear) IP40
Standards, approvals, certificates

CE mark Yes
UL approval Yes
● UL 508 Yes
cULus Yes
RCM (formerly C-TICK) Yes
KC approval Yes

Appendix
EMC CE, EN 61000-6-4:2007, EN 61000-6-2:2005
EN 61000-6-2 Yes
Dust protection Protection against foreign bodies > 1 mm
FCC Yes
Marine approval
● Germanischer Lloyd (GL) Yes
● American Bureau of Shipping (ABS) Yes
● Bureau Veritas (BV) Yes
Ambient conditions
Ambient temperature during operation
● Ambient temperature during operation 0 °C up to 60 °C
● min. 0 °C
● max. 60 °C
Ambient temperature during storage/transportation
● min. -20 °C
● max. 60 °C
Relative humidity
● Relative humidity Tested according to IEC 60068-2-78, IEC 60068-2-30:

Operation: 5% to 80% at 25 °C (no condensation),
Storage: 5% to 95% at 25 °C (no condensation)
Vibrations
● Vibration load in operation Tested to DIN IEC 60068-2-6: 10 Hz to 58 Hz: 0.075

mm, 58 Hz to 200 Hz: 9.8 m/s² (1 g)
Shock testing
● Shock load during operation Tested according to IEC 60068-2-27: 150 m/s², 11 ms
Software
MindConnect Software Pre-installed MindConnect Software
Dimensions
Width 191 mm
Height 100 mm
Depth 60 mm

Appendix
7.1.1 ESD guideline
What does ESD mean?

An electronic module is equipped with highly integrated components. Due to their design,
electronic components are highly sensitive to overvoltage and thus to the discharge of static
electricity. Such electronic components or modules are labeled as electrostatic sensitive
devices.
The following abbreviations are commonly used for electrostatic sensitive devices:
• ESD – Electrostatic sensitive device,
• ESD – Electrostatic Sensitive Device as a common international designation.
Electrostatic sensitive devices can be labeled with an appropriate symbol.
NOTICE
Damage to ESD from touch
Electrostatic sensitive devices, ESD, can be destroyed by voltages which are far below
the human perception limit. If you touch a component or electrical connections of a
module without discharging any electrostatic energy, these voltages may arise.
The damage to a module by an overvoltage can often not be immediately detected and
only becomes evident after an extended period of operation. The consequences are
incalculable and range from unforeseeable malfunctions to a total failure of the machine or
system.
Avoid touching components directly. Make sure that persons, the workstation and the
packaging are properly grounded.
Charge
Every person without a conductive connection to the electrical potential of his/her surroundings
can be electrostatically charged.
The material with which this person comes into contact is of particular significance. The figure
shows the maximum electrostatic voltages with which a person is charged, depending on
humidity and material. These values conform to the specifications of IEC 61000-4-2.

Appendix
NOTICE
Grounding measures
There is no equipotential bonding without grounding. An electrostatic charge is not
discharged and may damage the ESD.
Protect yourself against discharge of static electricity. When working with electrostatic
sensitive devices, make sure that the person and the workplace are properly grounded.
Protective measures against discharge of static electricity

• Disconnect the power supply before you install or remove modules which are sensitive to
ESD.
• Pay attention to good grounding:
- When handling electrostatic sensitive devices, make sure that persons, the workstation and
devices, tools and packaging used are properly grounded. This way you avoid static
discharge.
• Avoid direct contact:
- As a general Rule, do not touch electrostatic sensitive devices, except in the case of
unavoidable maintenance work.
- Hold the modules at their edge so that you do not touch the connector pins or conductor
paths. This way, the discharge energy does not reach and damage the sensitive components.
- Discharge your body electrostatically before you take a measurement at a module. Do so by
touching grounded metallic parts. Always use grounded measuring instruments.

Appendix
7.1.2 Structure of MindConnect Nano interfaces

MindConnect Nano is composed of all-metal enclosure, resistant to vibrations and shocks, also with
electromagnetic compatibility and the following designed interfaces.
7.1.2.1 Designed interfaces
Figure 7-1 Interfaces of MindConnect Nano
1. Protective conductor connection

2. Connection for a DC 24V 1,8 A power supply- M /L+ NEC CLASS 2
3. USB 3.0 port, high current- X60
4. On/off switch
5. USB 2.0 port, high current –X61, X62, X63. (Port for Setup is X63)
6. RJ45 Ethernet connection 1 for 10/100/1000 Mbps–X1 P1- for Internet (to MindSphere)
7. RJ45 Ethernet connection 1 for 10/100/1000 Mbps - X2 P1– for automation unit (Asset)
7.1.2.2 LED lights

The LED lights statuses provide information on efficient self-diagnostics.
Figure 7-2 LED lights- bottom view 1

Appendix
Figure 7-3 LED lights- bottom view 2
Description of the LED lights
Name Status Description

• Power on
GREEN
PC ON/WD
• System restart
ORANGE
• No connection to proxy
ORANGE • No connection to MindSphere
For explanation of possible problems and respective
solution, please refer to the chapter “Troubleshooting”.
Blinking • Connection to MindSphere is being

L1-RUN/STOP ORANGE established
• Onboarding is in progress
Blinking GREEN
GREEN • MindConnect Nano is onboarded to MindSphere
Blinking
L2 - ERROR • Firmware update active
ORANGE

Appendix
• No connection to Data Sources

ORANGE For explanation of possible problems and respective
L2 - ERROR • Data loss

Blinking RED For explanation of possible problems and respective
RED • Firmware update error
Blinking
USB stick is active:
ORANGE • Installing USB configuration
Onboarding failed:
ORANGE • System Error
L3 - MAINT • Configuration file on the USB stick is not valid
• USB stick Error

Blinking RED For explanation of possible problems and respective

Appendix
7.2 Mounting MindConnect Nano
7.2.1 Permitted mounting positions and surrounding temperature

The following mounting positions and surrounding conditional temperature are permitted.
• Horizontal mounting position
The horizontal mounting position is the preferred position.
Figure 7-4 Horizontal mounting position
• Vertical mounting position
Figure 7-5 Vertical mounting position
Note
> 50 °C: Install in RAL
RAL = Restricted Access Location - e.g. a lockable cabinet

Appendix
• Free space around the device

Ensure that the following clearance measurements to another component or to a wall
of housing are complied with:
- Above the device: ≥ 50 mm
- Below the device: ≥ 100 mm
7.2.2 Connecting the protective earth
Figure 7-6 Connecting protective earth

Appendix
7.2.3 Mounting types

Note
Ensure that the mounting surface on the wall can bear four times the total weight of the device,
including fixing elements.
Use only the anchors and screws specified in the operating instructions.
The following mounting types of the device are possible:
• Mounting on rails
• Wall mounting
• Upright mounting

Appendix
7.2.4 Installing the cable strain relief

The cable strain relief plate carries the cables and prevents unintentional loosening of the connector
from the device. The cable strain relief is available as an accessory.
Procedure
Figure 7-7 Installing the cable strain relief
1. Insert the metal plate of the strain relief left and right into the second to the last notch left and
right.
2. Secure the strain relief on the left and right respectively with an M3x8 setscrew.
3. After connecting, secure the connection cables with cable ties to the cable strain relief.
7.2.5 Installing Ethernet connector strain relief

The Ethernet connector strain relief prevents accidental loosening of the Ethernet connector from the
device. The Ethernet connector strain relief is available as an accessory.
Procedure
Figure 7-8 Installing Ethernet connection strain relief

Appendix
1. Insert the metal plate of the Ethernet connector strain relief into the second and third to the last
notch.
2. Fasten the Ethernet connector strain relief with 2 setscrews.
3. Secure the Ethernet connector with cable ties.
7.3 Maintaining MindConnect Nano

You find all the information on maintaining in the official IPC227E documentation. In the next chapter
you can see the information on replacement of the backup battery.
7.3.1 Replacing the backup battery

Prior to replacement
WARNING
Risk of explosion and release of harmful substances
Improper handling of lithium batteries can result in an explosion of the batteries.
Explosion of the batteries and the released pollutants can cause severe physical injury.
Worn batteries jeopardize the function of the device.
Note the following when handling lithium batteries:
• Replace the battery every 5 years.
• Replace the lithium battery only with the type recommended by the manufacturer.
• The order number is A5E34345932.
• Do not throw lithium batteries into fire, do not solder on the cell body, do not
recharge, do not open, do not short-circuit, do not reverse polarity, do not heat
above 100°C and protect from direct sunlight, moisture and condensation.
NOTICE
Disposal of batteries and rechargeable batteries
Batteries and rechargeable batteries do not belong in domestic garbage. The user is
legally obliged to return used batteries and rechargeable batteries.
Used batteries and rechargeable batteries pollute the environment as special waste. You
as a user are liable for prosecution if you do not properly dispose of batteries and
rechargeable batteries.
Please observe the following when disposing of batteries and rechargeable batteries:
• Dispose of used batteries and rechargeable batteries separately as hazardous
waste in accordance with local regulations.
• You can return used batteries and rechargeable batteries to public collection
points and wherever batteries or rechargeable batteries of the type in question
are sold.
• Label the battery container "Used batteries and rechargeable batteries".

Appendix
Requirements
• The device is disconnected from the power supply.
• The device is opened.
• The drive has been removed, see section "Replacing the drive" in the IPC 227E
Documentation.
Procedure – removing
NOTICE
Time may be deleted
The time will be deleted if it takes you longer than 30 seconds to replace the battery. The
device is no longer synchronous. Time-controlled programs will no longer run or will run
at the wrong time. This may damage the plant.
Reset the time for the device.
Figure 7-9 Replacing the backup battery
1. Lift up the cover slightly and open it carefully. Do not damage the seal in the process. Lay the
cover aside next to the device. The battery cables should not be subjected to any pressure in
doing so.
2. Pull out the connection plug of the battery cable.
3. Remove the battery with the attached Velcro from the Velcro fastener on the cover. Remove
also the Velcro fastener on the cover.
Procedure - installation
• To install the replacement battery, follow the steps for removing the battery in the reverse
order. A Velcro fastener is provided with the replacement battery.
• Stick a Velcro fastener on the battery.
• Replace the Velcro on the cover/enclosure. When sticking on the new Velcro, pay attention to
the position mark on the enclosure.
• Attach the replacement battery with the Velcro to the Velcro on the cover/enclosure.

Appendix
7.3.2 Firmware update of MindConnect Nano

New firmware versions are regularly released to improve product performance. Before the firmware
update starts, you will be notified in advance e.g. per email.
• Firmware update runs on MindConnect Nano automatically
• During the firmware update data loss of few minutes may occur.
• During the update it is not recommended to configure or modify Assets in the Asset
Configuration.
Upon success, MindConnect Nano will automatically reboot the system.
In case of a failed update, please refer to chapter ”Troubleshooting”.

Appendix
7.4 Handling of Asset
7.4.1 Overview of OPC UA data types

The following table outlines the data types of the OPC UA Protocol and in Visual Analyzer of
MindSphere.
OPC UA Data Types Store as
Boolean Bool
Byte Float
Int16 Float
UInt16 Float
Int32 Float
UInt32 Float
Int64 Float
UInt64 Float
Float Float
Double Float
String String
7.4.2 Overview of S7 data types

The following table gives information on data types of the S7 in Asset Configuration of MindSphere.
S7 Data Types Data Type Address Example
Boolean Bool DB1.DBX0.0, M0.0
Byte Signed/unsigned (sINT, uINT) DB1.DBB0, QB0

Int Signed (sINT) DB1.DBW0
Word Signed/unsigned (sINT, uINT) DB1.DBD0
DInt Signed (sINT) QD0
DWord Signed/unsigned (sINT, dINT, REAL) MD0
REAL REAL DB1.DBREAL0

Appendix
7.4.3 List of measuring units

In this chapter you can find the complete list of measuring units, which can be selected in a Data
Point of an Aspect the Asset Configuration. You can select a required unit or leave it empty.
Figure 7-10 Measuring units
Table List of the measuring units
UNITS
" g/m2 l/m_.s MVA
% g/m3 l/min MW
%(m) g/mol lb mW
%(V) gai lb/Btu MWh

Appendix
%O gai/l lb/gal N
%O(m) galUS lb/lbm N/m
%O(V) GAU lb/MB N/mm2
°C GJ lb/scf nA
°F GJ/m3 lb/ton ND
µA GJ/tm3 m nF
µF GJ/ton m.b_/s nm
µg/l GOhm m.Pa/s ns
µg/m3 GPHUS m/h Ohcm
µl GPMUS m/min Ohm
µm gro m/s Ohmm
µs h m/s2 One
µS/cm Hectar m_/kg oz
µSv/h hl m2 P
1/cm3 hPa m2/s Pa
1/M2 hrs m3 PAC
1/m3 Hz m3/d PAIR
1/min Inch2 m3/h PAL
A Inch3 m3/m3 Pas
acre J m3/s pF
AU J/kg mA ppb
Bag J/kgK MB/bbl ppb(m)
bar J/m3 MB/ton ppb(V)
Bq J/mol mbar ppm
Bq/cm2 K mF ppm(m)
Bq/g K/min mg ppm(V)
Bq/kg K/s mg/cm2 ppt
Bt. kA mg/g ppt(m)
Bt/bbl kai/kg mg/kg ppt(V)

Appendix
Bt/ft3 kBq/kg mg/l PrC
Bt/gal kg mg/m3 PRS
Btu/lb kg/bbl MHz ps
Can kg/dm3 mile ptUS
Car kg/J Mile2 qtUS
Case kg/kg min ROL
cd kg/kgm MJ s
Cl kg/m2 mJ S/m
cm kg/m2s ml ST
cm/h kg/m3 ml/m3 t
cm/s kg/MB mlai t/bbl
cm2 kg/mol mm t/Btu
cm3 kg/s mm/a t/Joul
cm3/s kg/scf mm/h t/m3
Crate kg/sm2 mm/s t/t
d kg/ton mm2 t/TJ
D kgai mm2/s t/tm3
Days kHz mm3 TBq
deg kJ mmol thou
dm kJ/g mmol/g ton
dm3 KJ/kg mMol/l ton/gl
Dr KJ/mol MN ug/c2m
dz km mN/m V
EA km/h MOhm val
EU km2 mol VAM
EU/ml kmol mol/kg W
F kOhm Mol/l W/mk
Foot kPa mol/m3 Weeks

Appendix
fozUS kt Months Wm2ppb
ft2 kV MPa yd
ft3 kVA mPa.s yd2
g KW MPGUS yd3
g/cm3 kwh ms yr
g/hg l mT
g/kg l/hkm MV
g/l L/hr mV
7.4.4 Asset handling in Asset Configuration

This chapter describes how you can duplicate or delete Assets.
7.4.4.1 Duplicate an Asset

You can duplicate an Asset with all configurations. Such properties as Asset name, Asset ID,
MindConnect Nano Unique ID and IP address must be adapted.
To duplicate an Asset, proceed as follows:
• Select the Asset that you want to duplicate from the list and then click icon :
Figure 7-11 Duplicating an Asset

Appendix
Note
During duplicating an Asset do not duplicate the static IP address in the Ethernet Interface for
MindSphere Connection. The text box with IP address must be cleared out. The same IP address
cannot be used for two Assets.
Figure 7-12 Duplicating an Asset
7.4.4.2 Delete Asset

When an asset is deleted, the time series data and the rules are deleted as well and cannot be seen
in the Fleet Manager afterwards.
To delete an Asset, proceed as follows:
• Select the Asset that you want to delete from the list and then click the trash icon:
Figure 7-13 Deleting an Asset

Appendix
After an Asset has been deleted, the MindSphere Units will not be calculated any more.
When before starting the onboarding process by generating the first OBT no Aspects have been
created for an Asset, then the event "First OBT generated" contains 1 as MSU, otherwise it contains a
previously calculated MSU.
7.4.5 Save and share a configured view in the Fleet Manager

In the Fleet Manager, the URL with a configured view can be saved and shared by using an email
client installed on your computer.
To send an email click share icon :
Figure 7-14 Sending a configured view
An email with URL of the current view will be automatically opened in your email program. There you
can edit your email and send it.
The information saved in URL depends on the currently configured dialog window and its features.
But any user gestures cannot be saved into the URL e.g.
• Hidden variables below the opened chart
• Zooming in or out of a selected area on the line chart.
Note
The MindApp Fleet Manager will not detect whether there is any email client installed on your
computer or whether the access to the client is denied. Accordingly, there is no user notification from
Fleet Manager.

Appendix
7.4.6 MindSphere Units for Data Modeling

MindSphere Unit (MSU) is the basis for fees invoiced monthly per Asset and per used application.
The value of a MindSphere Unit will be indicated during the ordering of MindAccess/MindApps and
will be stated in the order sheet.
Starting point for fee creation is 1 MSU, when an Asset has been created and onboarded. Number of
MSUs will grow depending on the number of configured Aspects and their Data Points.
The calculated MSUs per Asset can be seen in the Aspects tab in the Asset Configuration:
Figure 7-15 MindSphere Units
The sum of calculated MindSphere Units depends on:

• Number of Data Points
• Reading Cycle of a Data Point
• Data types of Data Points
Number of Data Points

The more Data Points are configured, the more MindSphere Units will be calculated. For example,
one configured Data Point of the type bool with reading cycle of 15 seconds causes 1 MindSphere
Unit.

Appendix
Figure 7-16 MindSphere Units calculated per an Aspect
Reading Cycle of Data Points

The reading cycle of an Aspect affects the number of units as well. A faster Reading cycle leads to
more MindSphere Units
For example, to read Data Points each second will lead to more MindSphere Units than to read a
Data Point each 15 seconds.

Appendix
Figure 7-17 MindSphere Units per reading cycle of 15seconds
Data Types
The calculation of the MindSphere Units depends on different data types of a Data Point. For
example, Bool is the lowest value and String is the highest value for MindSphere Unit.
Figure 7-18 MindSphere Units of data type “STRING”

Appendix
Accepting MindSphere Units

When saving an Asset, a dialog box appears informing you about the newly calculated MindSphere
Units. The dialog has to be confirmed, for the changes to take effect. If the dialog is not confirmed, the
changes will not be saved.
Figure 7-19 Accepting MindSphere Units
Limitation of MindSphere Units

It is possible to configure data points up to 10 000 MindSphere Units per Asset.
If the amount of the MindSphere Units exceeds 10 000, the MSUs will be colored red and saving of
the configuration will not be possible.
Figure 7-20 Limitation of MindSphere Units
Account Overview
You can see the overall MindSphere Units for an Asset per MindApp in "Account Overview".

Appendix
There is a table for available applications e.g. MindApps Fleet Manager and overall MindSphere Units
per App for the configured Assets. Fees will be issued monthly.

Appendix
7.5 Offboard MindConnect Nano

You can offboard your MindConnect Nano in the following cases,
• If you want to connect it to a new Asset.
• If you onboard a new MindConnect Nano to the same Asset (e.g. replacement)
• If it is malfunctioning and needs to be replaced.
In order to offboard MindConnect Nano from MindSphere, follow these steps:
• Go to the MindConnect Nano Information
• Click Offboard
Figure 7-22 Offboarding MindConnect Nano
Note
In general the offboarding process can take up to ten minutes. Therefore, do not turn off
MindConnect Nano during this time, before the offboarding process is completed.

Appendix
7.6 User Account management

The user accounts are managed in the User Management and Customer Management. The user
rights depend on the following types of roles.
• Admin
• Users
• Customer
7.6.1 User rights
Launchpad Rights Description Admin User Customer

/UI
Create Asset Create and duplicate buttons X

are enabled
Delete Asset Delete button is enabled X
View Asset Contains viewing of all areas of X X X

Configuration Asset Configuration
View View MindSphere Units X X

MindSphere
Units
Change Change and save MindSphere X

MindSphere Units
Units
Modify Asset Asset Name, Asset ID,

X X
Information Description can be changed
View Customer Column in Asset List and Field X X

Asset
Information in Asset configuration of
Configuration
Customer assignment is visible
Modify customer Assignment of Asset to X

Information customer can be changed
Delete Time
X
Series Data
Modify location Asset location can be changed X X X
Modify Aspects Add, change, delete Aspects X

and their Data Points
Modify Data S7 Configuration (IP-Address)

Source Settings and OPC UA Configuration X X X
of Aspect (Name, IP, Certificate,
Authentication) can be changed

Appendix
Modify MindConnect Nano Unique ID X X X

MindConnect can be changed
Nano Information
Onboard of On-/Off Boarding Process X X X

MindConnect
Nano
Modify Network Ethernet port and proxy settings X X X
of MindConnect Nano can be
changed
Export to USB Configuration file can be X X X

stick generated
Firmware Update Update of a new firmware X X X
Asset picture Show and change Asset picture X X X
Area map Show and change Area map X X X
View User View user X X

User
Management Modify User Create, modify and delete users X
View customers View customers X X
View users of View users of customer X

customer
Customer
Management Modify Create, modify and delete X X
customers customers
Modify Create, modify and delete X

customer’s users customer’s users
View account View Apps and MindSphere X X

Units per App
Account
Overview
Modify Apps Management of Apps X

Appendix
Modify Rules View Rules and Settings X X X
Modify Request Set in progress and close X X X

Fleet
Manager Assets, Data show on base of scopes X X X
Points and
Values, requests,
Hierarchy, Area
map
Create Manual Create Manual Request X X X
request
7.6.2 Create and modify a user and a customer user

The Admin creates accounts for users in the User Management and accounts for customers in the
Customer Management. After an account has been created, a user will receive an Email notification
to activate his login credentials.
User Management
To create a user, follow these steps:
• Go to the User Management in MindSphere Launchpad.
• Click Add new User
Figure 7-23 Creating a user
• Enter all required information for a user.
To modify or delete a user, proceed as follows:
• Select a user, click icon and make required changes or delete a user :

Appendix
Figure 7-24 Modifying a user
Customer Management
To create a customer, proceed as follows:
• Go to the Customer Management.
• To create a customer, click Add new Customer.
Figure 7-25 Creating a customer
• Enter all required information for a customer.
To create a user of the customer, proceed as follows:

• Select a Customer.
• Go to User for Customer ‘C1’, click Add new Customer User.
Figure 7-26 Creating a user of a customer
• Enter all required information for a user.

Appendix
To modify or delete a customer or a user of a customer, proceed in the same way as described in
User Management of this chapter.
Note
When creating a user account (for user or customer), you have to assign an Email address in
order to activate a user/customer account.
Figure 7-27 Assigning an email to a user
It is not possible to create a user or a customer account with an already assigned Email address. A
customer’s account cannot be used for users of this customer as well.
All Email addresses to be entered on account creation need to be unique and may not be reused.
An error message will appear when entering the already assigned Email address:
Figure 7-28 Error message

Appendix
7.6.3 Reset login password

You can reset your login password quickly by going to the log in page, and clicking the link “Forgot
password?”.
In a short time you will receive an email. Please follow the instructions in this email to reset your password.

Appendix
7.7 Troubleshooting
Error Problem Possible cause Possible remedy
Network connection problem: • Check your configuration
MindConnect connection: If configured IP
Nano cannot • Either IP address is not valid and Proxy are valid
L1- onboard to or configured IP address
already exists in the network
RUN/STOP MindSphere
of MindConnect Nano
LED • Either disabled or invalid
ORANGE configured Proxy
• Interrupted Connection
No internet • IP address is configured via
connection DHCP, but there is no
internet connection.
• No connection to Data • Check the connection

L2 - ERROR Source between MindConnect Nano
LED and Data Sources (Plant
Network ports and cables -
ORANGE Although an Asset S7/OPC UA Server)
is onboarded, no • The address of the Data • Check the connection
time series are Point configuration can be between MindConnect Nano
uploaded to the incorrect and Data Sources (Plant
Fleet Manager and Network ports and cables -
S7/OPC UA server)
Visual Analyzer.
• Check Data Sources
configuration.
• Check configuration of each
Data Point.
• Incorrect Asset Configuration • Check configuration of your
• Not accomplished Asset Asset (Network
MindConnect Configuration (Network Configuration).
Nano cannot Connection)
onboard to
MindSphere • Invalid ID of MindConnect • Check if MindConnect Nano
Nano ID is correct.
• MindConnect Nano was too • Check outbound connection

L2- ERROR long offline, so it could not • Check Ethernet cables
LED blinking Data loss send data to MindSphere and • Check Proxy (IP address,
the storage is full. User Authentication can be
RED
required)
• Technical problems with a • MindConnect Nano will
new version of firmware automatically restart and then
• Certificate problems firmware update will be
• Authentication problems etc. carried out after a while.
L2- ERROR Firmware update • If MindConnect Nano does
not restart automatically,
RED error
restart MindConnect Nano by
switching on and off the
“power button” on
MindConnect Nano.

Appendix
Error Problem Possible cause Possible remedy

• Configuration file on the USB • Make sure that the data on
stick is invalid the USB stick still is valid.
(The data, which you exported
to the USB stick, is still valid
only for 7 days.). If it is
expired, use the Asset
L3- MAINT
Configuration to export a new
LED Onboarding failed valid configuration to your
ORANGE USB stick.
• Check Asset Configuration
and reconfigure, if it is
required and export a new
configuration to USB stick.
• Incorrect formatting of USB • Check format and partition of

L3-MAINT Problems with
stick the USB stick.
LED blinking USB stick
• USB stick is damaged • Try a new USB stick
RED
Problems with USB stick: • Remove and plug an USB
Although no LED
stick into MindConnect Nano
lights will be • Configuration file in USB stick • Check the diagnosis file on
shown except PC cannot be read or accepted the USB stick.
ON/WD with by MindConnect Nano: • Check the name of the
constant GREEN, • Problems with configuration configuration file. It must have
MindConnect file MindConnect Nano ID. Do not
Nano still cannot • Configuration file is located in change the name of the
be onboarded to an incorrect directory. downloaded file.
• Expired configuration file on • Check if the directory is valid.
MindSphere.
the USB stick (Configuration file must be in
Although the • The configuration file is the root directory of the USB
internet connection invalid or not copied to the stick.)
is OK. USB stick • Make sure that the data on
the USB stick is still valid.
(The data, which you exported
to the USB stick, is still valid
only for 7 days.) If it is
expired, use the Asset
Configuration to export a new
valid configuration to your
USB stick.
• Unknown • Switch MindConnect Nano off
System Error
and on again. If the problem
persists, contact your
Siemens Support/„Expert
Center“.

7.8 List of abbreviations
Abbreviation Description
GUI Graphical User Interface
HTTPS Hyper Text Transfer Protocol Secure
IP Internet Protocol
IoT Internet of things
LAN Local Area Network
MSU MindSphere Unit
OPC UA Open Platform Communications Unified Architecture
PC Personal Computer
S7 STEP 7
UI User Interface

Glossary
8 Glossary
Account Overview
In Account Overview you find a table with all available applications (MindApps e.g. Fleet
Manager) and overall MindSphere Units per App for the current Asset Configuration.
For more information on MindSphere Units refer to chapter ”MindSphere Units for Data
Modeling”.
Aspect
Aspects of an Asset describe the content of the imported data. For example: The pump
skid has an Aspect e.g. “energy_management” that contains the Data Points: "power",
"current", "voltage" etc.
Asset
An Asset is a logical representation of a machine or an automation system with one or
multiple automation units (e.g. PLC).
The Asset is a central part of industrial cloud technology. The data from the customer’s
Asset will be collected and sent to MindSphere to make that data available for further
processing and analytics. For collecting data of this “physical” Asset, a “virtual” Asset is
configured in the Asset Configuration UI.
Asset ID
Asset ID is a serial number assigned by the manufacturer to a 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.
Asset Type
Asset type is a sort or kind of a product line made by one manufacturer. Example:
SINAMICS, SIMATIC, SIMOTION, SINUMERIK etc. are Asset types of Siemens products.
Data Point
Data Point is in reference to an element of an Asset in Data Source and can be configured
in the Asset Configuration and visualized in the MindApp Fleet Manager.

Glossary
Data Source
Data Source is a physical element of a device, which can be monitored by MindSphere.
Example: OPC UA Server, STEP 7.
Event
An Event is a change of a Data Point state. Events are used for the Requests: Events are
defined by a Rule. With a Rule it is possible to define the Request, which will be created in
MindSphere when the Event is triggered.
Besides the monitoring Rule, a description of the Event, the resulting action and priority
can be lodged.
See also “Request”, “Rule".
Last Connection
"Last Connection" status in the Asset Configuration gives the information, when
MindConnect Nano was online for the last time. .
MindApp
MindApp is an application, which is not part of core cloud services of MindSphere, but
developed specifically for the MindSphere industrial IoT platform.
MindApp Fleet Manager

Fleet Manager is a visualization tool to get an overview of existing Assets and their
information (Asset name, customer name, location). Fleet Manager displays your
configured Asset, Aspects with Data Points in charts, a list of all Requests etc. It is
possible to save configured view as bookmark and send it per email.
Filter&Sort:
To quickly find a required Asset from this list you can use the filter&sorting function or the
search box. The Assets can be filtered by country, severity of requests and customer.
Sorting can be done by the following criteria:
• Assets alphabetically
• Assets with most Requests by priority first
• Assets with most Requests at all first
Besides you can configure hierarchy and area, where you can see an area map of a
customer with Asset(s).
Aspect View:
In three different charts (line, pie and bar charts) the values of variables assigned to
Aspects can be displayed in different time frames (time picker).
Rules and Requests:
Fleet Manager enables creation of rules for automatically generated Requests and
manual Requests. For more information, refer also “Rule”, “Request”, and “Event".

Glossary
MindConnect Nano
MindConnect Nano is a preconfigured Industrial PC that allows connectivity to
MindSphere. The purpose of MindConnect Nano is to collect data from the field and send
it to MindSphere via industrial protocols such as OPC UA and S7. The device supports
transmission of data encrypted through a secured internet connection to MindSphere to
enable cloud-based applications and services.
Supported protocols are:
• TCP/IP
• Serial
MindConnect Nano can only be used in conjunction with MindSphere. It contains Open
Source SW which is provided free of charge.
MindConnect Nano ID
MindConnect Nano ID is a unique serial number, which can be found on the enclosure of
the box.
MindSphere Customer Management

Customer Management is the administration of MindSphere customer accounts. In the
Customer Management, the Admin can create accounts for their customers. Assets can be
assigned to a customer in order to let users of this customer see the assigned Assets. Login
for customer user can also be administrated by the Admin in the customer configuration.
MindSphere Launchpad
MindSphere Launchpad is the entry point for the Asset Configuration, Fleet Manager and
User-/ Customer Management.
MindSphere
The MindSphere is the Siemens Industrial IoT Platform comprising the core cloud services
and applications (MindApps), whereas the MindConnect Element (MindConnect Nano)
provides secure and easy connectivity from the field/machine to the MindSphere Platform.
MindSphere Asset Configuration

MindSphere Asset Configuration is a Web Graphical User Interface, where Assets can be
created, modified, duplicated and deleted.
The following Asset configurations are available:
• Common Information: name, type, description
• Location: address and/or GPS coordinates
• Data Sources – connected via Ethernet: SIMATIC S7-300/400 PLCs and
OPC UA Server
• Data Points of Data sources with their properties as well as the definition
of acquisition cycles from 1 second up to daily (in predefined time ranges).

Glossary
• Network setting of MindConnect Nano (2 Ethernet ports and Proxy Server

Settings)
• Assigning Assets to a customer.
MindSphere Units
MindSphere Units are the basis for calculation of invoice issued at the end of the month
per Asset and per used application.
The sum of calculated MindSphere units in the Asset Configuration depends on:
• Number of Data Points
• Reading Cycle of a Data Point
• Data types of Data Points
The more variables (Data Points) you configure, the more MindSphere Units will be
calculated for variable units.
The reading cycle of a Data Point affects the number of Units as well. For example, to
read a Data Point each second costs more than to read a Data Point each 10 seconds.
The calculation of the MindSphere Units depends on different data types of a Data Point.
For example, Bool is the lowest value and String is the highest value for MindSphere Unit.
MindSphere User Management

User Management is th eadministration of MindSphere user accounts. There are two
groups of users with different rights for managing and displaying: Admin and User.
Offboarding Process
The Offboarding process is the stopping process of the connection between MindSphere
and MindConnect Nano.
The Offboarding process is required, when:
• new MindConnect Nano must be onboarded
• changing Network Configuration
Before a new MindConnect Nano can be onboarded, the old MindConnect Nano must first
be offboarded.
Onboarded/Offboarded Mode
Onboarded is the state of MindConnect Nano after successful Onboarding process.
Offboarded mode is the mode of the MindConnect Nano after the Offboarding process.
Onboarding Process
The Onboarding process is required to connect a new MindConnect Nano with
MindSphere. It basically consists of an authentication of the new device and an
assignment to the owner's user space.

Glossary
During the Onboarding process the first communication between MindConnect Nano and
MindSphere will be established. That means that MindConnect Nano will be connected to
an Asset. The onboarding process contains Asset and MindConnect Nano configurations
and synchronization of these configurations to MindConnect Nano. After the onboarding
process the changes on the Asset configuration can be done, if it is necessary.
Online/Offline Mode
Online indicates internet connection, when the MindConnect Nano sends the data to the
server. Offline mode means the absence of the internet connection and the MindConnect
Nano does not send any data to the server.
Operation Center
Siemens department which administrates the user accounts: creates a new tenant,
creates the initial structure for a new user and a customer.
Request
A Request can be created in order to trigger an Event. It will be triggered on the first
exceeding value (flank trigger).
There are two scenarios for Requests:
1. You can configure a Request manually, if it recognizes an Event in the Visual
Analyzer.
2. You can create a Rule for an automatic Request, if a Rule recognizes an Event.
Request contains:
• Description
• Recommended action
• Prio (Info, Important, urgent)
• Timestamp
• Assigned Asset
See also “Event", "Rule".
Rule
With Rules a user can configure an automatic monitoring of Data Points on Events. For
example, a Request will be created automatically by the system, if a value exceeds or falls
below a threshold.
Rule(s) can be created for automatically generated Requests to the following Event
conditions:
• Data Point < reference value
• Data Point <= reference value.
• Data Point > reference value
• Data Point >= reference value.
• Data Point = reference value.

Glossary
Rules will be saved for the corresponding Asset. Duplicating of an Asset will not duplicate
its Rules.
See also “Event", "Request".
Time Series
Time Series is a sequence of measurements, which are produced by Data Sources over
time. Analysis and visualization tools can retrieve collected time series and present it to
the user after processing. In the Asset Configuration the measurements, that have to be
collected, can be specified.

MindSphere Getting Started October 2016 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

MindSphere Getting Started October 2016 PDF

Загружено:

Авторское право:

Доступные форматы

Preface

Configure Data Collection 5

Perform visual analysis

Version October 2016

Proper use of Siemens products

Siemens AG Copyright © Siemens AG, 2016, and

Basic knowledge requirements

Scope of validity of this document

Scope of this documentation

Find your contact person or open a Support Request

MindSphere – Getting Started, 10/2016 3

4 MindSphere – Getting Started, 10/2016

5.2 Log into MindSphere............................................................................................................ 40

MindSphere – Getting Started, 10/2016 5

7.5 Offboard MindConnect Nano ............................................................................................... 88

6 MindSphere – Getting Started, 10/2016

Time Series .............................................................................................................................. 103

MindSphere – Getting Started, 10/2016 7

8 MindSphere – Getting Started, 10/2016

Note the following for system expansions:

MindSphere – Getting Started, 10/2016 9

Battery and rechargeable battery

Note the following when handling lithium batteries:

Strong high-frequency radiation

10 MindSphere – Getting Started, 10/2016

Disclaimer for third-party software updates

Open Source Software

MindSphere – Getting Started, 10/2016 11

1.2 Notes on usage

12 MindSphere – Getting Started, 10/2016

2 Getting Started with MindSphere

2.2 Functional overview of MindSphere

Figure 2-1 MindSphere overview

MindSphere – Getting Started, 10/2016 13

With MindSphere and MindConnect Nano you can:

2.3 Structure of MindSphere Service Provision

Figure 2-2 MindSphere elements

14 MindSphere – Getting Started, 10/2016

MindSphere Asset Configuration

MindApp Fleet Manager

MindSphere User and Customer Management

MindSphere – Getting Started, 10/2016 15

2.4 Working with MindSphere

Prepare MindConnect Nano for MindSphere

16 MindSphere – Getting Started, 10/2016

• Create manual Requests or Rules for automatically generated Requests to monitor

MindSphere – Getting Started, 10/2016 17

18 MindSphere – Getting Started, 10/2016

3 Prepare MindConnect Nano for MindSphere

Figure 3-1 MindConnect Nano

3.2 Check package upon delivery

MindSphere – Getting Started, 10/2016 19

20 MindSphere – Getting Started, 10/2016

3.3 Connect the device

3.3.1 Connect the power supply

Figure 3-2 Power supply

MindSphere – Getting Started, 10/2016 21

3.3.2 Connect device to networks

Figure 3-3 Interfaces of MindConnect Nano

RJ45 Ethernet connection

USB 2.0 port, high current.

RJ45 Ethernet connection

Figure 3-4 Connecting the port X1P1 for internet (MindSphere)