TBXSAP10 - Schneider Electric TBX FIPIO and AS-i gateway

Schneider Electric TBX FIPIO and AS-i gateway with a documented system role and explicit evidence boundaries.

Documented function

Rebuilt from individual evidence

System position

Unknown: Evidence boundary

Schneider Electric identifies TBXSAP10 as a gateway module for an AS-i line and FIPIO.

The TBX SAP 10 guide states that the gateway connects the AS-i sensor-actuator bus through FIPIO to TSX model 40, APRIL 5000, and Premium PLCs and decentralizes I/O.

The gateway sits between the AS-i sensor-actuator bus and the PLC over the FIPIO network.

Unknown: The connected AS-i slaves, FIPIO address, PLC program, bus power, and site-specific wiring are not established by the captured sources.

Exact reference: TBXSAP10
Category: PLC / CPU
Evidence checked: 2026-09-12

System role

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

Function: Routes AS-i sensor and actuator data to and from the PLC through FIPIO.
System position: Sits between the AS-i sensor-actuator bus and the PLC over the FIPIO network.
Upstream / inputs: Receives cyclic data from AS-i sensors and actuators.
Downstream / outputs: Exchanges the AS-i I/O image with the connected PLC over FIPIO.
Limitations: Unknown: The connected AS-i slaves, FIPIO address, PLC program, bus power, and site-specific wiring are not established by the captured sources.

Evidence ledger

Facts, inferences, and unknowns are kept separate.

Facts

Schneider Electric identifies TBXSAP10 as a gateway module for an AS-i line and FIPIO.
Confidence: high
- www.se.com — retrieved 2026-09-12; high confidence
The TBX SAP 10 guide states that the gateway connects the AS-i sensor-actuator bus through FIPIO to TSX model 40, APRIL 5000, and Premium PLCs and decentralizes I/O.
Confidence: high
- manualzz.com — retrieved 2026-09-12; medium confidence

Inferences

The gateway sits between the AS-i sensor-actuator bus and the PLC over the FIPIO network.
Confidence: high
Rationale: The guide explicitly describes both networks and the PLC connection, supporting this system position.
- www.se.com — retrieved 2026-09-12; high confidence
- manualzz.com — retrieved 2026-09-12; medium confidence

Unknowns

Unknown: The connected AS-i slaves, FIPIO address, PLC program, bus power, and site-specific wiring are not established by the captured sources.
Confidence: low
Missing evidence: The connected AS-i slaves, FIPIO address, PLC program, bus power, and site-specific wiring are not established by the captured sources.

System position diagram

Diagram showing TBXSAP10 between AS-i sensor-actuator bus and FIPIO-connected PLC. — System position of TBXSAP10 from the captured evidence.

View Mermaid source

flowchart LR
  upstream["AS-i sensor-actuator bus"] --> item["TBXSAP10"]
  item --> downstream["FIPIO-connected PLC"]

View diagram labels

Nodes: AS-i sensor-actuator bus; TBXSAP10; FIPIO-connected PLC
Edges: Documented upstream connection; Documented downstream function

Next action

Decision: The evidence supports TBXSAP10 as an AS-i to FIPIO gateway with a concrete PLC I/O integration role; verify the installed buses and PLC configuration before replacement.

Next action: Match the exact gateway, AS-i slave list, FIPIO address, PLC family, bus power, and wiring against the cited guide.

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.

Reference or description *Recovery mode *Country *RegionEmail *Phone

I’m unsure of the exact reference or route; keep my description for human qualification.

Add context only if useful

ManufacturerMachine or lineComponent typeUrgencyProduction impactQuantityAcceptable conditionNeed byPreferred contact

Technical context

What is known so far?

Optional updatesNotify me when the supplier price changesSubscribe to the ardkor.org newsletter

This may be safety-sensitive or emergency-related; hold it for human handling.Allow anonymous landing and source categories to be saved with this request for analytics. This is optional and separate from routing.

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.

External routing consent: I separately authorize Ardkor to use this request for human qualification in the named internal queue. No external partner is authorized by this checkbox.

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.