web
You’re offline. This is a read only version of the page.
close
Support Portal

Why are my configured settings for the MLG-2 / MLG-2 WebChecker ProNet device lost after a restart?

Configured settings reset after PLC restart if a configuration module/assembly is active. Remove it or adjust parameters to prevent overwrites.
Related Products
MLG-2 ProNet
MLG-2 WebChecker
MLG-2

Table of Contents

After a PLC restart or power cycle, settings previously configured via SOPAS ET (e.g., Beam Blanking Mask) are reset to default. This often causes confusion because changes seem not to be saved.

 

The issue is caused by using the Configuration Module (for PROFINET) or the Configuration Assembly (for Ethernet/IP) in the PLC. "StartUp Entrys" used in EtherCAT could lead to the same issue, but are not used by default.
These modules contain a subset of device parameters. When the PLC restarts, the parameters stored in these modules are automatically sent to the sensor, overwriting any settings previously applied via SOPAS ET or other methods.


PROFINET

Common project planning tools (e.g., the TIA Portal from Siemens) require a GSDML file for integration of the devices into the network. If the configuration module is included in the PLC hardware configuration, its parameters will overwrite SOPAS settings after every restart.

 

Alternative configuration methods:

  • SOPAS ET
  • Service/acyclic data via PROFINET
  • Direct TCP/IP interface

Note: If the configuration module is still used in these cases, these settings are overwritten by the settings in the configuration module as soon as the PLC restarts.

 

Ethernet/IP
The MLG-2 can be integrated in Ethernet/IP in various ways and can be configured independently of the integration.:

  • As a generic module: All module settings are entered manually.
  • Using an EDS file: The MLG-2 module settings have been predefined.

Configuration methods:

  • Configuration Assembly
  • Controller Tags
  • SOPAS ET

Note: If Configuration Assembly is active, the parameters entered there overwrite the parameters configured via SOPAS ET during system startup. When integrated using the EDS file, behavior depends on the selected I/O assembly instances.

 

Recommendation

Only use the Configuration Module or Configuration Assembly if no other configuration method is applied.

If you want to configure exclusively via SOPAS ET, remove the Configuration Module (PROFINET) or Configuration Assembly (Ethernet/IP) from the PLC configuration or do not enter Startup Entrys for parameters (EtherCAT).

Keywords:
ProNet, configuration module, GSDML, configuration assembly, EDS