Hello, is there a way to configure the ETH XT module dynamically? The customer would like to choose if it would be connected or not and define the IP. I also noticed that, when I add the ETH module it seems to become the principal profinet interface, and you need to change the PLC IP or the project’s IPs range Is this behaviour correct? Is there a way to change it? (and use the ETH XT module to connect with the customer network for example and not for profinet)
Hi Gianluca, Does this info center page answer any of your questions? https://www.plcnext.help/te/PLCnext_Engineer/Adding_left-alignable_Axioline_F_extension_modules.htm If not:
is there a way to configure the ETH XT module dynamically? The customer would like to choose if it would be connected or not and define the IP.
By “dynamically”, do you mean that the customer would like to enable and disable the Ethernet interface, and define the IP address, from a PLCnext Engineer program at run-time? If so, what is the purpose of doing this (out of interest?) Note this feature of the extension module:
When you use the left-alignable AXC F XT ETH 1TX Ethernet interface, it automatically takes over the PROFINET® controller functionality. In this case, the controller is always a PROFINET® device.
Even though the extension module is automatically assigned as a Profinet Controller - and this cannot be changed - it is also possible to use this interface for other (non-Profinet) communication on the customer network. ~ Martin.
Hi Gianluca - just a minor correction to my earlier answer. My statement that “this cannot be changed” is not correct. It is possible to change this behaviour by adding a custom configuration file to the controller. However this causes cascading side-effects in other parts of the PLC which must also be worked around, and so it is not something that we can recommend. This topic will be addressed in future firmware versions, but if is a requirement for a current project, please let us know and we can discuss the options. ~ Martin.
Hello Martin, I totally forgot this post (I do not receive any notification of answers from the forum)
By “dynamically”, do you mean that the customer would like to enable and disable the Ethernet interface, and define the IP address, from a PLCnext Engineer program at run-time? If so, what is the purpose of doing this (out of interest?)
The customer would like to create the project of a generic configuration and use it for every application of the same type without changing the project He would like just to set every parameter in the web server, event the left aligned module. Will it be possible to configure them in the runtime? (maybe there has been some news form july ?)
if is a requirement for a current project, please let us know and we can discuss the options.
for the moment is a nice to have Thank you for support Gianluca
Hi Gianluca, Yes, sorry, this forum does not send notifications, at the moment …
The customer would like to create the project of a generic configuration and use it for every application of the same type without changing the project
OK, so the configuration would be set once for each application, while the program is not controlling a process, so it’s not the end of the world if the PLC needs to restart, for example.
He would like just to set every parameter in the web server, event the left aligned module.
When you say “web server”, do you mean the Web-based management (WBM), or an eHMI screen, or perhaps a custom web application? When you say “every parameter”, the solution will probably depend on which parameters your customer wants to change. For example, Ethernet parameters like IP address and Gateway can usually be changed by editing a file on the PLC. If all the parameters your customer wants to change can be changed from the PLC’s command line, then it may be possible to use the Shell function in PLCnext Engineer (via the PLCnextBase library) to call the required commands, and trigger these commands from the eHMI. That’s only one possible solution … there may be others (e.g. install a web application alongside the eHMI that can change the parameters). WBM is evolving all the time and may include some of these features in the future, but it is difficult to say for sure if or when that might happen. ~ Martin.
Hi,
OK, so the configuration would be set once for each application, while the program is not controlling a process, so it’s not the end of the world if the PLC needs to restart, for example.
Exactly, they will set the application at the commissioning and would not need to set it again, a reboot shouldn’t be a problem
hen you say “web server”, do you mean the Web-based management (WBM), or an eHMI screen, or perhaps a custom web application?
at the moment they use the eHMI and not a customized web server, anyway they can adapt the PLC program to launch shell commands aswell (so it is not needed that the shell commands would be launched directly from the eHMI) If it is possible to set the module using system files and shell commands, please let me know Gianluca
Good Morning Gianluca, the network configuration is done via the sys file /etc/network/interfaces, the interface of the leftside extension is “enpls0”. So, you can modify the interface setting directly in this file or with the “PBCL_SysNetwork_1” functionblock coming with the PLCnext Base lib. But, as the extensions becomes as default the role of the PN Controller you’re not completely free in the configuration of the Subnet.
If the PN Controller is used, must the subnet match to the PN configuration, otherwise will the PN startup (configuration is layer 3) fail. However, I guess there might be (as usual) a solution, but to be more precise it would be great to have the detailed demands. Please send them to me by mail. Thx, Frank