GLC150-BG41-FLEX-24V - Pro-face LT Type B Flex Network operator interface

The Pro-face LT Type B unit provides a Flex Network interface for an operator-facing control system. Evidence and installation boundaries are recorded for maintenance review.

Documented product role

Rebuilt from individual evidence

System placement

Unknown: Evidence boundary for the captured source set.

Pro-face identifies GLC150-BG41-FLEX-24V as the LT Type B model with a Flex Network interface.

The LT Type B unit controls remote I/O through its Flex Network interface.

Flex Network I/O units connect to the LT through the two-channel Flex Network interface.

The LT can send communication data to connected Flex Network I/O units, with up to 63 units across both channels.

The unit sits between an operator interface and the remote I/O network in the LT control system.

Operator logic reaches remote I/O units through the LT Flex Network interface.

Unknown: The installed screen project, connected I/O topology, firmware, and site-specific compatibility are not established by the captured sources.

Exact reference
GLC150-BG41-FLEX-24V
Category
HMI / Display
Evidence checked
2026-09-12

System role

This section explains what the product does and where it acts in the surrounding system.

Function
Controls the documented remote-I/O communication function.
System position
Sits between the operator interface logic and connected remote I/O units.
Upstream / inputs
Receives configured communication data from the LT control logic and connected network.
Downstream / outputs
Sends communication data to connected Flex Network I/O units.
Limitations
Unknown: The installed screen project, connected I/O topology, firmware, and site-specific compatibility are not established by the captured sources.

Evidence ledger

Facts, inferences, and unknowns are kept separate.

Facts

  • Pro-face identifies GLC150-BG41-FLEX-24V as the LT Type B model with a Flex Network interface.

    Confidence: high

  • The LT Type B unit controls remote I/O through its Flex Network interface.

    Confidence: high

  • Flex Network I/O units connect to the LT through the two-channel Flex Network interface.

    Confidence: high

  • The LT can send communication data to connected Flex Network I/O units, with up to 63 units across both channels.

    Confidence: high

Inferences

  • The unit sits between an operator interface and the remote I/O network in the LT control system.

    Confidence: medium

    Rationale: The manufacturer manual identifies this exact model as LT Type B and documents the Flex Network connection to remote I/O.

  • Operator logic reaches remote I/O units through the LT Flex Network interface.

    Confidence: medium

    Rationale: The manual documents both the two-channel interface and communication to remote I/O units, supporting this system-level signal path.

Unknowns

  • Unknown: The installed screen project, connected I/O topology, firmware, and site-specific compatibility are not established by the captured sources.

    Confidence: low

    Missing evidence: The installed screen project, connected I/O topology, firmware, and site-specific compatibility are not established by the captured sources.

System position diagram

Diagram showing GLC150-BG41-FLEX-24V between LT control logic and Flex Network I/O units.

Reading limit: system position only, not a wiring or safety drawing.

System position of GLC150-BG41-FLEX-24V from the captured evidence.

Enlarged system diagram

Diagram showing GLC150-BG41-FLEX-24V between LT control logic and Flex Network I/O units.

System position of GLC150-BG41-FLEX-24V from the captured evidence.

View Mermaid source
flowchart LR
  upstream[LT control logic] --> unit[GLC150-BG41-FLEX-24V]
  unit --> downstream[Flex Network I/O units]
View diagram labels
Nodes
LT control logic; GLC150-BG41-FLEX-24V; Flex Network I/O units
Edges
Upstream data enters the product; The product provides the documented downstream function

Next action

Decision: The exact model and Flex Network system role are documented; verify the installed project and I/O topology before service.

Next action: compare the installed LT project and connected I/O topology with the documented Flex Network arrangement before sourcing.

Request help with this reference

Request help with this reference

Provide the exact reference, machine context, and observed symptom so the next review can stay evidence-based.

Submission is unavailable until durable storage is verified.

Recovery request details
Add context only if useful
Optional updates
Recipient and data disclosure

Recipient and data disclosure

Named recipient: Ardkor human-qualification queue (internal local preview). No partner delivery is enabled here.

Data retained for this review: reference, selected route, location, technical context, contact details, consent state, and any accepted private attachment.

Response expectation: none is promised. If external routing is enabled later, the partner name, disclosed fields, and response expectation must be shown and accepted again.

Withdrawal and deletion: use the private request controls from the receipt to withdraw further processing or request access/deletion. The request remains recorded until the relevant Ardkor systems and any recipient confirm completion.

Read the privacy information before sending. For corrections, access, or deletion help, use the contact page or email reference@ardkor.org; mailbox delivery and attendance have not been verified.

This routing state is separate from watch, marketing, payment, and analytics choices. If no capable service match is found, the request remains a human-qualification lead and is never presented as provider acceptance. Ardkor is not an emergency or safety service and submission does not guarantee availability, price, repair, sourcing, or response.