- Getting Connected to MindSphere
- Document history
- Safety Notes
- Introduction
- Overview of MindConnect Elements
- User roles and scopes in "Getting Connected to MindSphere"
- Mounting and installing MindConnect Elements
- Connecting MindConnect Elements
- Onboarding MindConnect Elements
- Overview of onboarding MindConnect Element
- Logging in to MindSphere
- Creating an asset
- Enable connection to MindConnect Element
- Configuring network and diagnostic settings
- Transferring configuration to MindConnect Elements Mindconnect Nano and Mindconnect IoT2040
- Using MindConnect Software Agent to connect industrial data sources to MindSphere
- Overview of MindConnect Software Agent
- User interface of MindConnect Software Agent
- Onboarding and Installing MindConnect Software Agent
- Diagnosing MindConnect Software Agent
- Device Maintenance
- Settings in MindConnect Software Agent
- Using MindConnect Software Agent's Hyper-V VM
- Managing or maintaining the virtual machines or instances in MindConnect Software Agent
- Configuring MCSA in Docker
- Differentiating MCSA between Windows and Linux
- Known restrictions of MindConnect Software Agent
- Troubleshooting
- Configuring data in Asset Manager
- Creating an aspect and variables
- Creating a type in Asset Manager
- Adding a data source and data points
- Mapping an aspect to a data source
- Importing data source configurations for MindConnect Nano/IoT2040
- Importing data source configurations with datapoint mapping for MindConnect Software Agent
- Configuring MindConnect element using API
- Configuring protocols
- Overview of supported protocols for MindConnect Elements
- Overview of S7 protocol
- Overview of OPC UA protocol
- Overview of Modbus TCP protocol
- Overview of Modbus RTU protocol
- Overview of SIMATIC I/O Shield
- Overview of SYSTEM protocol
- Overview of Rockwell protocol
- Overview of S7+ protocol
- Overview of Fanuc Focas protocol
- Overview of Sinumerik protocol
- Overview of IEC61850 protocol
- Overview of MTConnect protocol
- Firmware update for Mindconnect Nano / IOT 2040
- Remote functions
- Visual analysis of assets in Fleet Manager
- Appendix
- Data center locations
- Quality code settings
- Technical specifications of MindConnect Nano
- Technical specifications of MindConnect IoT2040
- Offline buffer
- Read performance MindConnect Elements
- Firewall Settings
- ESD guideline
- Return of defect hardware
- List of abbreviations
- MindConnect EthernetIP - CIP Communication path (route parameters) settings
- Glossary
- Document history
- Safety Notes
- Introduction
- Overview of MindConnect Elements
- User roles and scopes in "Getting Connected to MindSphere"
- Mounting and installing MindConnect Elements
- Connecting MindConnect Elements
- Onboarding MindConnect Elements
- Overview of onboarding MindConnect Element
- Logging in to MindSphere
- Creating an asset
- Enable connection to MindConnect Element
- Configuring network and diagnostic settings
- Transferring configuration to MindConnect Elements Mindconnect Nano and Mindconnect IoT2040
- Using MindConnect Software Agent to connect industrial data sources to MindSphere
- Overview of MindConnect Software Agent
- User interface of MindConnect Software Agent
- Onboarding and Installing MindConnect Software Agent
- Diagnosing MindConnect Software Agent
- Device Maintenance
- Settings in MindConnect Software Agent
- Using MindConnect Software Agent's Hyper-V VM
- Managing or maintaining the virtual machines or instances in MindConnect Software Agent
- Configuring MCSA in Docker
- Differentiating MCSA between Windows and Linux
- Known restrictions of MindConnect Software Agent
- Troubleshooting
- Configuring data in Asset Manager
- Creating an aspect and variables
- Creating a type in Asset Manager
- Adding a data source and data points
- Mapping an aspect to a data source
- Importing data source configurations for MindConnect Nano/IoT2040
- Importing data source configurations with datapoint mapping for MindConnect Software Agent
- Configuring MindConnect element using API
- Configuring protocols
- Overview of supported protocols for MindConnect Elements
- Overview of S7 protocol
- Overview of OPC UA protocol
- Overview of Modbus TCP protocol
- Overview of Modbus RTU protocol
- Overview of SIMATIC I/O Shield
- Overview of SYSTEM protocol
- Overview of Rockwell protocol
- Overview of S7+ protocol
- Overview of Fanuc Focas protocol
- Overview of Sinumerik protocol
- Overview of IEC61850 protocol
- Overview of MTConnect protocol
- Firmware update for Mindconnect Nano / IOT 2040
- Remote functions
- Visual analysis of assets in Fleet Manager
- Appendix
- Data center locations
- Quality code settings
- Technical specifications of MindConnect Nano
- Technical specifications of MindConnect IoT2040
- Offline buffer
- Read performance MindConnect Elements
- Firewall Settings
- ESD guideline
- Return of defect hardware
- List of abbreviations
- MindConnect EthernetIP - CIP Communication path (route parameters) settings
- Glossary
Case 2 – Accessing the Allen- Bradley PLC via integrated Ethernet port
In this scenario, the CIP client sends some data into the CPU module using the integrated Ethernet port. In a CPU module with integrated Ethernet port, the Ethernet port is in the same slot as the CPU module.
The CIP client in the MindConnect sends a request package to the CPU module at 192.168.0.32 addressing the processor module in slot 0.

Following the previous schema, the above image represents the communication path (route parameters).
Following the previous made explanations, the CIP message travels first through the processor module to the backplane and it returns back to the processor module for interpretation. For such situations, it is possible to use an abbreviated communication path only containing the IPv4 address.
The MindConnect block uses the parameter "slot" to form the communication path (route parameters).