I am interested in setting up a Profinet network within my manufacturing facility to link various devices such as a PLC, HMI, and multiple Profinet-based Weight Transmitters. I am aware that in order for effective communication to occur, all devices must be on the same subnet. However, due to the significant distance between them, it is impractical to establish direct connections or connect through a single network switch. My strategy is to link each device to the closest Ethernet port provided by the IT department for intranet connections in the plant. These ports automatically assign IP addresses to connected devices, which may or may not fall within the same subnet. For example, devices on the 3rd floor have IP addresses in the subnet 172.16.103.x, whereas those on the ground floor use 172.16.102.x. Despite being on different subnets, devices on different floors can still communicate, likely due to IT's routing configurations for plant-wide connectivity. While I am uncertain, this setup gives me hope that my PLC on the first floor can communicate with a Weight Transmitter on the 3rd floor. However, my concern lies in the manual assignment of IP addresses to each device. I question whether devices on separate subnets can communicate in this scenario. Additionally, I am unsure if the networks on the 3rd and 1st floors are physically connected, as my knowledge of network infrastructure is limited. Before proceeding with the project and purchasing equipment, I need clarification on these aspects. If my initial plan is not feasible, I am interested in exploring alternative solutions.
In the world of Profinet, it is the responsibility of the IO Controller to allocate IP addresses to the IO Devices. It is crucial not to delegate this task to a third party, such as the DHCP server of the office network. While it is technically possible to collaborate with the IT department to reserve IP addresses, it is strongly advised to keep the Profinet network separate from the office network to avoid any potential complications. IT departments often have different priorities, such as performing server maintenance or network changes after office hours, which may disrupt production processes that run round-the-clock. For large distributed plants, it is essential to carefully plan and design a Profinet network that can efficiently handle the workload. Fortunately, Profinet cables are affordable and readily available.
JesperMP noted that in Profinet, the IO Controller is responsible for assigning IP addresses to IO Devices, rather than allowing a third party such as the office network's DHCP server to do so. While it is possible to work with IT to reserve IP addresses for your use, it is not advisable to mix Profinet with the office network due to differing priorities between production and IT departments. For instance, IT may conduct server maintenance or network changes after office hours, while production is still operational. In the case of a large distributed plant, it is recommended to design a dedicated Profinet network. Profinet cables are cost-effective. Additionally, although this weight transmitter is not a Siemens product, it can be integrated into a Siemens Profinet network using a GSDML file in TIA Portal. Regarding the connectivity of transmitters located on different floors, even if IP addresses are reserved by the PLC, they may still be in different physical networks. This raises the question of whether the PLC will be able to locate and connect to them effectively.
Integrating Profinet with the office network may pose some challenges, but it can be done successfully with the right configuration. While Profinet cables are cost-effective, it is essential to ensure proper connectivity between the Profinet IO Controller and IO Device using Ethernet switches. However, integrating Profinet into a complex office network with multiple interconnected subnets and routers may lead to complications. IT policies and restrictions could potentially hinder the smooth integration of a Profinet Device into the network. Troubleshooting issues that arise from mixing Profinet with an office network can be quite difficult.
In a discussion, JesperMP noted the potential challenges of integrating Profinet with the office network, highlighting the cost-effectiveness of Profinet cables. While it is technically feasible to connect the Profinet IO Controller to the IO Device using regular Ethernet switches, navigating through multiple switches within a complex office network may pose difficulties. IT departments often segment office networks into multiple subnetworks connected by routers, enforcing rules and limitations that could hinder the integration of a Profinet Device. Troubleshooting issues that arise from mixing Profinet with the office network can be complex. Considering the option of directly connecting the IO device to the PLC instead of utilizing IT ports, it may eliminate network uncertainties but could potentially require laying lengthy Profinet cables. The maximum distance allowed for a Profinet cable is typically 100 meters. While incorporating switches could extend this distance, it may incur additional costs. In a scenario where the manager prefers utilizing the nearest Ethernet ports to connect transmitters to the PLC through the company's network, suggesting the use of switches and direct connections may be the optimal solution. Clarifying if exceeding the 100-meter limit is permissible when utilizing switches between the PLC and IO device (transmitters) would be advisable.
Certainly! Ethernet can easily be extended using switches, allowing for increased connectivity and network flexibility.
In your case, it sounds like using a VPN (Virtual Private Network) could be a feasible solution. A VPN artificially inserts a device into a specific network, which could solve your issue with automatic IP assignments. Through a VPN, you can assign fixed IP addresses to your devices regardless of their physical location within the plant. It would be best to collaborate with your IT department to set this up accordingly to ensure seamless communication across floors. However, remember that communication latency might be higher in a VPN compared to a direct connection due to the overhead of additional processing and data encapsulation. Make sure to consider this in the context of your application and the response times you require.
Your current strategy is sound considering the restrictions you've mentioned. Using the Ethernet ports provided by your IT department is a good start, as it simplifies a portion of the infrastructure. It seems you have a good grasp on the basics. However, the potential challenge lies in the manual assignment of IP addresses, like you noted. To overcome this, you might want to see if your IT department allows modification of their DHCP structure. If they do, you can possibly request to have certain fixed IP addresses that are on the same subnet. If this can't happen due to IP conflicts or security policy, a VPN setup between the devices could work since VPNs tunnel data over different subnets. It's a more advanced solution, but it might be the only one, depending on your IT's flexibility. Always remember to involve your IT department as early as possible in the process to ensure smooth integration and compliance with their policies.
It sounds like you're dealing with some intricacies of networking in your facility setup. With Profinet, it is actually possible for devices on different subnets to communicate, provided that the routing between these subnets is properly set up. This is something your IT department takes care of. However, a crucial factor would be device visibility in these different subnets, as Profinet devices need to "see" and talk to each other to operate properly. If that's technically not possible, VPN - Virtual Private Network - could potentially be an alternative solution to connect your devices across different subnets. This way, they could effectively appear to be on the same subnet even though they are physically linked through different network segments. Needless to say, closely liaising with your IT department to assess these possibilities would be an essential step.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Yes, devices on separate subnets can communicate with each other within a manufacturing facility if there are appropriate routing configurations in place to facilitate communication across different subnets.
Answer: - Manual assignment of IP addresses may not be necessary if the network infrastructure is configured to route communication between devices on different subnets effectively.
Answer: - The physical connections between networks on different floors may vary depending on the network infrastructure design. It is recommended to consult with the IT department or network administrators for clarification on the connectivity between different subnets.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.