
What Is Fipio? Device Compatibility, Wiring and Maintenance
Fipio is a WorldFIP-based industrial fieldbus used to connect a controller to compatible remote I/O and field equipment. It is associated with Schneider Electric automation systems, including appropriate Modicon Premium configurations. The classic network operates at 1 Mbit/s. That bit rate does not, by itself, specify an application’s response time. [1] [2]
On an installed machine, the useful question is not simply “does this replacement have Fipio?” It is “will this exact device, interface and profile fit the controller project and the existing wiring?” A communication connector that looks right can still carry the wrong interface. A supported network interface can still expose a different process-data layout.
This guide focuses on maintaining and renewing installed Fipio systems. The image above is conceptual, not a product-compatibility list or an installation drawing. Published limits below are tied to specific hardware and document editions; worked examples are engineering illustrations, not field-test results.
Before replacing hardware, identify the complete device
A practical starting point is the full order code, firmware revision, bus address, device profile and input/output lengths. Record these alongside the saved PLC project and device parameters. A family name on a front cover is not enough to establish interchangeability; nor does an identical plug prove that the spare has the required application behaviour.
The Momentum catalogue makes the distinction concrete: 170 FNT 110 00 is listed with TSX Series 7/April 5000 managers, while 170 FNT 110 01 is listed with Premium. In the TBX range, an analogue connection point requires TBX LEP 030. Check the full assembly rather than treating every Fipio adapter as the same item. [2] [5]
Also distinguish a native network device from a conventional sensor wired into remote I/O. A pressure transmitter may provide a local analogue signal; the I/O station, not the sensor itself, participates in Fipio. The PLC then works with a numerical input and its configured meaning. This distinction matters when tracing a fault or planning which field wiring to retain.
A Fipio-to-PROFINET gateway is not necessarily a Fipio manager
The HMS AB7655-F is explicitly described as FIPIO Slave / PROFINET-IO Device. Those role names matter more than the broad phrase “connects the two networks.” A slave interface is not a declaration of Fipio manager capability. [7]
Architectural consequence: a bridge with those roles still needs the managing function on its Fipio side. Removing the original manager PLC and leaving only this slave interface does not give a new controller automatic ownership of the existing Fipio stations. Moving data between control systems and replacing a fieldbus manager are different projects.
For a move to PROFINET or EtherNet/IP, define the boundary first: which controller remains, which network is being replaced, and who owns each command? An Ethernet switch does not supply a Fipio manager or translate application data. A gateway plan must cover direction, units, validity and loss-of-communication behaviour—not just a pair of network names.
The same discipline applies when considering CANopen equipment or a new servo system. Select against the required control function and controller support. Neither keeping Fipio nor removing it is automatically the right decision; spare availability, access to engineering tools, validation effort and permitted downtime need to be considered together.
A real process-data example: Altivar 61/71 with VW3A3311
VW3A3311 is the standard Fipio option documented for Altivar 61/71. Its FED C32 profile provides 32 words in each direction, with the first eight assigned to the communication scanner. Do not read that as 32 freely assignable scanner entries. Use the option manual alongside the Altivar 61 documentation, not in place of the drive’s programming instructions. [3]
| Controller data | Word | Meaning |
|---|---|---|
| Output to drive | 0 | CMd — control word |
| Output to drive | 1 | LFrd — speed reference |
| Input from drive | 0 | EtA — status word |
| Input from drive | 1 | rFrd — output speed |
Check the installed scanner assignments before using this default map. The manual’s LFrd example uses 1000 for 1000 rpm, not 1000 Hz. For this particular card, the nine-pin Sub-D data connections are pin 6 (+) and pin 7 (−); that is not a universal nine-pin serial pinout. [3]
Begin with read-only checks. Compare the reported status and speed with the drive display, then investigate command ownership under an approved test plan. Transmitting a command does not prove that the motor has moved. Whether the reported speed is a measured shaft value or a drive-derived value depends on the installation, including its control method and encoder feedback arrangement.
A 32-word area contains 64 bytes when each word is 16 bits. Two such areas contain 128 bytes of logical application data. This arithmetic does not describe a complete on-wire exchange, overhead, or guaranteed throughput. Treat the process image and the network traffic as different quantities.
A correct telegram can still produce a wrong engineering value
The input image is only useful when the receiver knows what the number means. With a 4–20 mA input, specify the input range, signedness, scaling and any diagnostic values. Do not assume that every Fipio analogue module uses the same counts-per-unit conversion.
Illustrative scale, not a device specification: suppose a 0–10 bar transmitter produces 4–20 mA and an imaginary input module maps that span to 0–10000 counts. At 12 mA the assumed raw value is 5000, giving 5000 / 10000 × 10 = 5 bar. The 0–10000 range is not a Fipio-defined format and is not claimed for a particular TBX or STB module. Actual modules may use different ranges and diagnostic codes.
This is why the PID controller needs both a correctly scaled measurement and a rule for invalid or stale data. Measurement accuracy and calibration are not established by successful communication. A stable reading on an HMI might be a real steady process—or the last value retained after the source disappeared.
What the bus manager actually schedules
Fipio uses a bus arbitrator to organise access: a requested variable is published by its producer and used by the relevant consumers. Cyclic I/O traffic and aperiodic services occupy different roles in the exchange schedule. Generic master–slave terminology is therefore useful background, but not a complete explanation of the variable-based mechanism. [1] [2]
Keep the names separate. WorldFIP identifies the technology-family context; a Fipio implementation still needs the appropriate device and communication profile. Fipway is not simply another spelling of Fipio. A programming adapter can support both without making the project configurations interchangeable. Likewise, Uni-Telway or Modbus RTU support does not establish Fipio support. [1] [8]
Fipio is a fieldbus, not ordinary Ethernet with a different cable. Do not import the shared-data arrangement described for FL-net or the processing model of EtherCAT into a Fipio design. Similar automation goals do not make their on-wire mechanisms, commissioning tools or device roles identical.
Count addresses, segment loads and island modules separately
| Item | Documented scope | Interpretation |
|---|---|---|
| Connection-point space | 0–127; manager 0, programming terminal 63 [1] | 126 other address positions remain. This is not a promise of 126 field devices on one cable segment. |
| VW3A3311 address selection | 1–62 [3] | The particular drive option accepts a smaller range than the overall space. |
| TBX IP20 monobloc addressing | 1–31 [5] | This subfamily cannot be assigned every general Fipio address. |
| STBNFP2212 data sheet | 32 per segment; up to 32 addressable I/O modules per island [4] | Bus participants and modules behind an island interface are different populations. |
Maintain separate engineering checks for the manager CPU, address selection, electrical segment and local I/O assembly. A free address cannot compensate for an overloaded segment; a free island slot cannot compensate for an incompatible profile. The smallest applicable restriction still governs the proposed change.
The legacy TSX DR FIP manual also specifies a 36-device station-or-repeater count in C2/3, whereas the STB sheet states 32 per segment. Do not merge these into a universal limit or use 36 to override a 32-device product restriction. Apply the counting method and hardware scope of the relevant installation manual. [1] [4]
Cable selection starts with the specified medium, not the plug
Documented Fipio cable families use a 150 Ω shielded twisted data pair. Characteristic impedance is not the resistance expected from an ohmmeter across a disconnected length of cable. A superficially similar RS-232, RS-422 or RS-485 connection is not an adequate cable or terminator specification. [6]
Use the specified line-termination accessories at the electrical segment ends. TSX FP ACC7 is one documented example; it should not be interpreted as an instruction to terminate every station. Some IP67 assemblies place data and 24 V supply conductors in the same cable jacket. Separate conductors remain separate circuits—sharing a jacket does not imply that the data pair supplies the equipment. [1] [6]
Before opening connectors or making resistance measurements, establish a safe process state and follow the equipment’s isolation procedure. Never apply a resistance test to a live bus. The inspection should cover screen connections, routing near motor cables and the local power supply; relevant electrical test methods need to be chosen for the actual circuit and instrument.
Worked cable budget: why physical length can mislead
For the TSX FP CCxxx two-pair drop-cable arrangement covered by TSX DR FIP C2/1–C2/2, physical drop length is multiplied by three when calculating equivalent trunk length. This is a rule for that documented arrangement, not a universal factor for every Fipio or IP67 accessory. [1]
Assumed installation: 600 m of trunk and drops of 40 m, 35 m and 25 m.Lequivalent = 600 + 3 × (40 + 35 + 25) = 900 m
That is below the arrangement’s 1000 m equivalent-length limit. Add another 40 m drop of the same type:Lnew = 600 + 3 × 140 = 1020 m
The physical cable total is only 740 m, yet the equivalent-length rule is exceeded. This is a design calculation, not a commissioned-network test.
Use the cable family and connection method to select the rule. An Ethernet cable-distance limit is not a Fipio limit. Adding repeaters creates additional segments to be designed and terminated; optical extensions have their own hardware and fibre conditions. A catalogue’s end-to-end kilometre figure is not permission for one uninterrupted copper run.
Separate I/O age from the network bit rate
A useful response-time model includes sensor filtering, conversion, input transfer, PLC scheduling, output transfer and actuator response. State which work each term includes; otherwise it is easy to omit a stage or count the same scheduling wait twice. The fastest visible number on a communication card is not the complete control-loop budget.
Assumed timing budget: allow 4 ms for input processing, up to 10 ms until the input transfer completes, up to 20 ms for the program to produce its output, and up to 10 ms for output transfer. These allowances total 44 ms, before actuator response. They are illustrative assumptions, not published Fipio timing guarantees. Actual upper bounds require a validated project and appropriate measurements.
For real-time communication, define the acceptable maximum delay and data age, not just the average update time. A data logger should identify where its timestamp originates. A SCADA refresh interval belongs to the supervisory display path and should not be mistaken for the field I/O update interval.
Commission from a known project, then prove each layer
Capture a baseline. Record CPU and interface references, station addresses, cable branches, segment ends, software versions and the last working application. Save device parameters as well as the PLC project. A replacement that has been used elsewhere may carry an address or scanner map from another machine.
Match the engineering environment. Confirm the actual PL7 or Control Expert project requirements, device profile and data lengths. When selecting PLC programming cables, distinguish a dedicated interface such as TSXCUSBFIP from a generic USB–RS-485 adapter. The manufacturer identifies TSXCUSBFIP as a Fipway/Fipio USB gateway; the reference alone does not establish compatibility with every operating system and driver. [8] [10]
Prove readings before enabling movement. Use a controlled, non-disruptive input change to compare the field device, PLC image and display. Test communication loss, CPU STOP and power restoration as separate cases under an authorised safe test plan. Document whether recovery can reinstate a previous run request, rather than treating restored communication as automatic permission to restart.
Troubleshoot the layer that matches the symptom
All stations disappear. Start with shared causes: manager state, common supply, configuration, trunk continuity and segment ends. Compare the last working state with the most recent change. A common loss of communication does not establish that every field device has failed independently.
One station is absent. Check address duplication, the permitted address range, the configured device type, local power and that station’s connection. Record the original state before changing switches. Making a station reappear under another address does not explain why the original address failed.
The bus is healthy but one analogue channel is wrong. Move downstream to channel configuration, sensor supply, module order and scaling. The TBX manual treats module and channel diagnostics separately. A healthy interface indicator is not evidence that every field input is valid. [5]
A drive reports CnF or ILF. The VW3A3311 manual distinguishes a network communication fault from a card/internal-link fault. This distinction changes the diagnostic starting point; neither code should be reduced automatically to “bad bus cable.” [3]
Outputs do not behave as expected after a loss. Consult the specific device response. The Momentum catalogue distinguishes discrete outputs forced to zero from configurable analogue behaviour. On the ATV61/71 option, network-fault response is configured through CLL. Disconnecting communication does not guarantee one universal stop state. [2] [3]
A reliable exchange is not a safety function or a security boundary
Error checking does not, by itself, authenticate the sender or encrypt the data. Include the connected PLC, maintenance PC and gateway in an industrial cybersecurity assessment. Access control, backups and limits on remote intervention should not be delegated to the name of the fieldbus. NIST’s OT guidance treats security alongside operational, reliability and safety requirements. [9]
A normal network stop request must not be substituted for Safe Torque Off, an emergency-stop circuit or another validated protective function. Machinery safety and SIL requirements concern the complete function and its implementation. Valid communication, correct engineering units, an appropriate fault response and verified protection are separate acceptance checks.
Sources and document scope
Product