Any best practice on how to connect the OI-server on IntegrtionStudio to my local PLC (SE M5xx and Siemens S7)?
Any best practice on how to connect the OI-server on IntegrtionStudio to my local PLC (SE M5xx and Siemens S7)?
Jakob, these are my methods on connecting an on-premise device to Integration Studio - however you may encounter other avenues or vendors depending on policies set forth within your organization. The application utilized is Hamachi by LogMeIn, it's a easy to use virtual private network that is capable of establishing direct links between computers without any sophisticated configurations, with access up to 5 machines without any cost - however if you exceed this limitation they'll charge you around $49/year for 6-32 computers.
A quick workflow is indicated below and guides:
https://support.logmeininc.com/hamachi/help#__browse-tree-title-get-started--hamachi-fundamentals
Installing Hamachi and Network Setup
Configurating Communication Drivers to talk to On-Premise Device
In the configuration below I'll be demonstrating connections to a Modbus simulator and using that particular data to send up to Integration Studio.
1. Within my PLC machine, I've already configured the connections to Hamachi Network and launched an instance of the Modbus simulator. In the Hamachi client you should see the IP address configured for the systems - take note as you'll be using this to enter into the configuration settings of the OI-Server
2. Within the Integration Studio environment, configure the Hamachi Client and test out the network connectivity, simple ping works as a quick test for connectivity
3. Once you've established connectivity within your integration studio environment, go to your configuration settings for the OI-Server within the Operations Control Management Console (or SMC for older versions) and configure the drivers for the device. In my demonstration we are connecting to the Modbus simulator and specifying the PLC client IP Address within the configuration.
4. You can now save and close your configuration, right-click on the MBTCP icon and activate the communication drivers.
5. Depending if you have any clients connected you should start to see data from the devices.
Jakob, these are my methods on connecting an on-premise device to Integration Studio - however you may encounter other avenues or vendors depending on policies set forth within your organization. The application utilized is Hamachi by LogMeIn, it's a easy to use virtual private network that is capable of establishing direct links between computers without any sophisticated configurations, with access up to 5 machines without any cost - however if you exceed this limitation they'll charge you around $49/year for 6-32 computers.
A quick workflow is indicated below and guides:
https://support.logmeininc.com/hamachi/help#__browse-tree-title-get-started--hamachi-fundamentals
Installing Hamachi and Network Setup
Configurating Communication Drivers to talk to On-Premise Device
In the configuration below I'll be demonstrating connections to a Modbus simulator and using that particular data to send up to Integration Studio.
1. Within my PLC machine, I've already configured the connections to Hamachi Network and launched an instance of the Modbus simulator. In the Hamachi client you should see the IP address configured for the systems - take note as you'll be using this to enter into the configuration settings of the OI-Server
2. Within the Integration Studio environment, configure the Hamachi Client and test out the network connectivity, simple ping works as a quick test for connectivity
3. Once you've established connectivity within your integration studio environment, go to your configuration settings for the OI-Server within the Operations Control Management Console (or SMC for older versions) and configure the drivers for the device. In my demonstration we are connecting to the Modbus simulator and specifying the PLC client IP Address within the configuration.
4. You can now save and close your configuration, right-click on the MBTCP icon and activate the communication drivers.
5. Depending if you have any clients connected you should start to see data from the devices.
Great feed back. I give it a try.