Controller configuration vs PC parameterization

[Webinar_Question]

What is the difference between the controller configuration vs pc parameterization?

[Alex.W]

What is the difference between the controller configuration vs pc parameterization?

The controller configures the device during start-up. The settings made during project planning are transferred to the device and checked to see whether the device meets the expectations, e.g. whether the order number is correct or whether the firmware version has a certain minimum version.

The device can also be parameterized using external tools. This can be a web server on the device or a separate tool that parameterizes my device via RPOFINET data records. In the classic sense, this is done for complex devices such as drives or laser scanners. In this way, not everything has to be configured in the controller engineering tool, but the know-how can be "hidden" in your own tool, e.g. because you don't want to show all device dependencies publicly.

PROFINET also offers a standard, called TCI (= Tool Calling Interface), to call up your own parameterisation tool from the engineering tool of the controller and already transfer the data, such as what is contained in the project, which configuration was selected, which (IP) address settings were made. You can also save the data from your own tool together with the controller project. This makes the work of the system builder or operator much easier.