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

GSDML compatibility for MLG-2 and Fieldbus modules

Which GSDML file to use for MLG-2 PROFINET integration, avoid TIA Portal errors, and ensure compatibility with FBM firmware versions.
Related Products
FBM-N11 FIELDBUSMODULE
MLG-2 ProNet
MLG-2

Table of Contents

Which GSDML file should I use for my MLG-2?

When selecting the correct GSDML for the MLG-2, there are two points to check:

  • Which firmware does the MLG-2 have?
  • Which firmware does the Fieldbus Module (FBM) have?

Since an MLG-2 ProNet can theoretically be combined with different Fieldbus-Modules (and thus also function as an EtherCAT or Ethernet/IP device with the corresponding FBM), there is a dependency here.

In general, the firmware of the light curtain bars plays a smaller role. The main difference is determined by the FBM used.

 

Background:
Due to a temporary component shortage, a new hardware chip was introduced for the FBMs, resulting in a new firmware version V2.0.0. However, this version lacked full compatibility with the previous chip (e.g., tunnel between the BUS ports and the config port, allowing the sensor to be connected via the BUS port and parameterized via SOPAS). Once the original components became available again, the older firmware version V1.2.0 (and later V1.2.1) was reintroduced.

This situation led to the coexistence of two firmware versions and corresponding GSDML files, which can cause compatibility issues in TIA Portal.

 

Overview of MLG-2 firmware versions shipped with FBM versions

MLG-2
Firmware version

(called APR on sick.com)

FBM
Version

2.3.0

FBM1: V1.2.0R

2.4.0

FBM2: V2.0.0R

FBM1: V1.2.1R

4.0.0

FBM1: V1.2.1R

 


 

On the website, you will find various GSDML files for the MLG-2 ProNet. Below is a brief overview of the latest GSDML files.

For each GSDML file you find the matching versions listed beside the download link.

APR stands for the firmware version of the MLG-2 light curtain bar.

FBM stands for firmware version of the Field Bus Module.

GSDML V1.0.3 (TIA V2.35)

When importing the GSDML V1.0.3 into TIA Portal, only one device entry appears:

MLG-2 ProNet (support of the FBM 1)

 

Offline device properties defined in the GSDML:

  • Firmware-version: V1.2.0
  • Hardware: 1

GSDML V2.0.0 (TIA V2.43)

When importing the GSDML V2.0.0 into TIA Portal, two device entries appear:

  • V1.2.0 (legacy support - FBM1)
  • V2.0.0 (new chip version)

This is because the GSDML V2.0.0 file includes definitions for both firmware versions.

 

 Device Access Point DAP1 - Offline device properties defined in the GSDML:

  • Firmware-version: V1.2.0
  • Hardware: 1

 

Device Access Point DAP2 - Offline device properties defined in the GSDML:

  • Firmware-version: V2.0.0
  • Hardware: 2

 

After integrating the GSDML file into the project, TIA Portal performs a validation during startup and online comparison to ensure the actual device matches the project configuration. The following aspects are primarily checked:

  • DeviceID and VendorID
    Must match exactly.

  • HardwareRelease
    Must be at least the required revision. Describes the physical revision of the device (e.g., new electronics, additional ports, modified ASICs).

  • SoftwareRelease
    Deviations can result in warnings. Describes the software running on this hardware.

  • Module structure
    Must be identical.

Note: These checks and compatibility results also depend on the TIA Portal version used, as different versions may handle revisions and schema validation differently.

 

What incompatibilities can occur and recommendations

 

When connecting an FBM1 (Firmware V1.x.x), the following GSDML files can be used:

  • GSDML MLG-2 (PROFINET) V1.0.3
  • GSDML MLG-2 (PROFINET) V2.0.0 → DAP 1

However, if the online device firmware differs from the offline configuration (read from the GSDML), TIA Portal may display additional information or warnings, for example:

 

Module exists.
OK

 

Additional information for the module:
The installed (online) firmware version is not identical with the configured (offline) firmware version.
Firmware version: V2.0
Configured firmware version: V1.2

 

See the screenshots for details:

 

Important: Using FBM1 with GSDML V2.0.0 → DAP 2 will result in an error:

 

Module exists.

Error

Error in lower-level component.

 

A hardware component was inserted but its type does not match the configured module type.

Resolution:

Check the inserted hardware component or correct the configuration, if necessary.

 

See the screenshots for details:

 

When connecting an FBM2 (Firmware V2.0.0), the following GSDML files can be used:

  • GSDML MLG-2 (PROFINET) V1.0.3
  • GSDML MLG-2 (PROFINET) V2.0.0 → DAP 1
  • GSDML MLG-2 (PROFINET) V2.0.0 → DAP 2 (recommended)

Summary Table

 

MLG-2
Firmware version 
Online
Firmware version in TIA

FBM
Version

Online 
Hardware version in TIA
GSDML Options Recommendation Offline Firmware version in GSDML Offline Hardware version in GSDML Remarks
2.3.0 V1.2.0

FBM1: V1.2.0R

1 V1.0.3 or 

V2.0.0 (DAP 1)
V2.0.0 DAP 1 1.2.0 1

 

DAP 1 OK

DAP 2 → Error

 

2.4.0 V2.0.0

FBM2: V2.0.0R

2 V1.0.3 or

V2.0.0 (DAP 1 or DAP 2)
V2.0.0 DAP 2 2.0.0 2 DAP 2 recommended
V2.0.0

FBM1: V1.2.1R

1 V1.0.3 or

V2.0.0 (DAP 1)
V2.0.0 DAP 1 1.2.0 1

DAP 1 OK; possible warning;


DAP 2 → Error

4.0.0 V2.0.0

FBM1: V1.2.1R

1 V1.0.3 or

V2.0.0 (DAP 1)
 V2.0.0 DAP 1 1.2.0 1

DAP 1 OK; possible warning;


DAP 2 → Error

 

Additional Notes

As mentioned earlier, these checks and compatibility results also depend on the TIA Portal version and the CPU used, as different versions may handle revisions and schema validation differently.

In some cases, TIA Portal and certain CPUs can require an exact match between firmware and hardware versions.
To address this, a modified GSDML was created where the offline firmware version was set to V2.0.0 to cover scenarios such as an MLG-2 with V4.0.0 (TIA online version V2.0.0) and FBM1.

Currently, there is no GSDML or DAP available for an exact match.
This modified GSDML is intended only for exceptional cases. If you need it, please create also a support ticket and provide the following details:

  • The CPU used
  • The TIA Portal version
  • The error encountered (as shown in TIA Portal → Online → Device Diagnostics)
Keywords:
gsdml, error, warning