Results
- 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 3 – Accessing the Allen- Bradley PLC via the ControlNet interface
In this scenario, the CIP client reads data from the Allen- Bradley PLC. Now, the communication path will be through the CompactLogix acting as bridge between EtherNet/IP and ControlNet.

The yellow line in the above image represents the communication path (route parameters).
In the communication path, the red marked sections always contain a network specific address. The blue marked part identifies the backplane or the interface to be used. It is not important that the backplane is physically existing or virtual. The green part identifies the slot number of the next bridge module (next hop) or the destination module.
Chap. 11.3