Figure 66: Beam status — Example 1
•
The green beams have been made.
•
The red beams have been blocked.
•
The bits represent the status of the beams on the MLG-2 (made = logical 0,
broken = logical 1).
•
The count direction of the beams depends on the configured beam numbering (in
the example, beam 1 on the connection side).
The run-length code indicates how many beams currently have the same status.
Table 51: Example run-length code with 30 beams
Beams 1…30
0 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0
R
L
C
1
RLC2 RLC3 RLC4 RLC5 RLC6 RLC8
1 4 6 4 6 4 5
RLC = 1464645
The example shows: 1 beam made, 4 beams blocked, 6 beams made, 4 beams
blocked, 6 beams made, 4 beams blocked, 5 beams made.
Table 52: Example run-length code with the first beam blocked
Beams 1…30
– 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0
R
L
C
1
RLC2 RLC3 RLC4 RLC5 RLC6 RLC8
0 5 6 4 6 4 5
RLC = 0564645
The RLC1 always indicates the number of beams made. If the first beam is blocked, the
RLC1 will therefore be zero. Only the RLC2 indicates how many beams are blocked; in
the example, this value = 5.
Beam status
Table 53: Beam status
Index Access Data type Description
30h…3Fh R UINT-32 These modules transfer the status of the
beams of the MLG-2.
30h: beam 1 – 32.
31h: beam 33 – 64.
…
3Fh: beam 481 – 512.
THE MLG-2 ON THE PROFIBUS NETWORK 7
8018748.1Q3I/2024-12-18 | SICK O P E R A T I N G I N S T R U C T I O N S | MLG-2 ProNet
71
Subject to change without notice
To Next Page
Loading...
