9/15/2022 12:47 PM | |
Joined: 1/21/2013 Last visit: 5/15/2024 Posts: 2784 Rating: (450) |
Hi Anoop Balagopal, the IO device always receives the IP address from the PLC. Whether the device name is also assigned depends on your configuration.
Kind regards |
This contribution was helpful to1 thankful Users |
9/15/2022 8:19 PM | |
Joined: 7/7/2010 Last visit: 5/15/2024 Posts: 14734 Rating: (2367) |
I have not had any PN IO device automatically accept it's IP from the PLC. If the topology is configured - and wired per configuration, and as Stefan states, the PLC project is configured to overwrite device names (and IPs) of all connected IO devices, it will do as you are stating you want to do. However, this feature has great responsibility associated with it. If someone (physically) swaps 2 Sinamics Control Units (from VFDs) after VFD1 fails, any internal programming and configuration for VFD1 is now from VFDs, but the PN name and IP will get changed. If these 2 VFDs are different sizes, they will not run. However, if the drive units connected to the CUs are the same part #, they might start up and maybe even run, but the tuning and motor settings may not match. For simple PLC and remote I/O swaps where identical part #'s and firmware revisions are swapped, having the PN name and IP swap is great - especially for remote IO without any local control (brainless remote I/O controllers). I hope this makes sense. If there are lots of PN I/O devices that get ALL their configuration data via profinet configuration, it's a great feature. It however, can also end up corrupting your PN network by accidentally renaming / renumbering IPs remote I/O devices when network cabling gets re-routed and technicians / engineers not accustomed to handling this scenario can really mangle things up - and make you look bad in front of customers.
|
science guy |
|
This contribution was helpful to2 thankful Users |
Follow us on