The easiest way to get the correct value of the response time is to use SOPAS. Open the SDD offline, choose the desired MLG-2 and read out the given 'System Boundaries':

Example for a MLG05A-0595I10501

Definitions for Timing

Important:

The settings (in 'Performance Options' Tab) of 'Function Reserve' (e.g. cross beam) and 'Response Time' (e.g. High-Speed-Scan) influence the scan time of the MLG-2 and thus the times explained here.
For example with High-Speed-Scan in many applications a significant decrease of the scan time is possible!
→ Make these settings before!

Example for field bus devices using the example device from above:

Reproducibility = 2.9ms
→  That means every 2.9ms new data is available to be transferred via field bus. If it's transferred depends on the master (PLC) of the field bus.
The master sets the cycle time of the field bus (in which cycle is the data fetched?). Is the field bus cycle time faster than the reproducibility it will happen that the same data set is transferred twice.

Minimum presence time = 5,8ms
→  Only significant for detection task. Not for field bus.

Response time = 10.6ms
→  After the response time of 10.6ms it's guaranteed that the object which entered the field of view of the light curtain at 0.0ms is detected.
AND the detection is evaluated and transferred to the IO-Controller (ready to be fetched by the field bus).
It does NOT contain any transmission times on the field bus.

Transmission time on the field bus:

It's not possible to give this value from our side. The transmission time is highly depended on various factors:
- Used field bus (protocol)
- Used baud rate
- Used network topology (number of switches and bridges (devices) in the network)
- Used master and settings of the master