Protocol First: Substituting a Fieldbus Module Without Break

Protocol First: Substituting a Fieldbus Module Without Breaking the Network

A fieldbus head module looks interchangeable with its successor when both sit side-by-side on the DIN rail, but the network underneath does not care what the device looks like — it cares what it speaks. The protocol stack, the master/slave role and the engineering files determine whether the network comes back up cleanly or takes the rest of the line down with it. As an independent China-based industrial automation distributor and sourcing desk, we treat the protocol layer as the first axis to verify, and we verify every substitute against the original manufacturer's datasheet before offering it. The customer's own qualification process decides what ships into the cabinet.

Why the fieldbus layer gets overlooked until the network refuses to come back

A buyer message that lands in our inbox at the start of an urgent line-down situation usually focuses on the visible part of the problem: the part number on a worn label, the slot in the backplane, the order code stamped on the front of the head station. The wording is almost always about the part itself: «Чем заменить снятый модуль ET 200S?» — what replaces a discontinued ET 200S module? — or «Нужен аналог головного модуля WAGO 750» — we need an alternative for a WAGO 750 head module. The buyer does not mention PROFINET, PROFIBUS, EtherCAT or Modbus TCP until the substitute has already been ordered, mounted and powered, and the controller fails to find the station.

The reason the protocol stays invisible for so long is that fieldbus modules are visually similar across revisions. A 6ES7151-1BA02-0AB0 and a 6ES7151-1CA01-0AB0 both look like the same small head station; a WAGO 750-842 and a 750-885 look alike at a glance. The substituted part is a "compatible" module in the catalog sense — same family, same series, same brand. The substituted part is not necessarily compatible with the network the controller was programmed for, and that is the gap where independent sourcing desks earn their keep or cause a second outage.

A documented cross-reference from the original manufacturer can confirm that a head station talks the same protocol at the same revision; absent that document, the protocol comparison has to be done by reading the engineering files. We do not do that reading for the customer — the program lives on the customer's engineering workstation, and program edits are out of scope for a sourcing desk — but we tell the buyer which documents to pull and which axes will fail closed if those documents do not line up.

What the network actually requires from a head module

A fieldbus head module is a translator between the backplane of the remote I/O station and the network the controller scans. The controller does not see the digital and analog I/O modules behind the head; it sees the head's network interface. Four things have to line up for that interface to be accepted by the controller:

The fieldbus protocol family has to match. PROFINET, PROFIBUS, EtherCAT, Modbus TCP, EtherNet/IP, CC-Link, DeviceNet and the older INTERBUS all look like "Ethernet" or "fieldbus" to a buyer who is in a hurry, but they are not interchangeable. A WAGO 750-341 (PROFIBUS) cannot be dropped into a station that a controller has been scanning as a PROFINET device. The catalog entry may use the word "Ethernet coupler", and the protocol slots are still open.

The device description file has to match the controller project. PROFINET stations are described by GSDML files, EtherCAT stations by ESI files, EtherNet/IP stations by EDS files, PROFIBUS stations by GSD files. The controller imports the file when the station is added to the project, and the imported file determines which modules and which diagnostics the controller will recognise. A substitute head station at a higher firmware revision usually ships a newer GSDML; the controller project may need to be re-imported for the new revision before the station will come online.

The master/slave role has to match the network design. A PROFINET head station can usually act as a controller (master) or a device (slave); a PROFIBUS head station is always a slave; an EtherCAT station is always a slave. Substituting a head station with a different role inverts who scans whom and breaks the rest of the network even if the protocol is correct.

The IP address, device name and topology have to fit the existing project. PROFINET stations carry a device name as well as an IP address. EtherCAT stations are addressed by their position in the ring. If the new head station resets these to factory defaults, the controller will not find it until someone re-commissions it from the engineering software.

The network stack and firmware version of the substitute head station also need to be checked against the controller's stack. A PROFINET head station that supports only PROFINET specification 2.3 cannot be addressed by a controller that has been configured for specification 2.4 features such as media redundancy or shared device. The network comes up; the features the project relied on do not.

Twelve-axis comparison applied to a remote I/O head swap

The substitution framework we use across every cross-reference — twelve axes that include form, terminal layout, electrical ratings, firmware, communication and certification — applies cleanly to a head-module swap, and most of the axes resolve to unknown rather than to matched because the manufacturer does not publish a side-by-side comparison for discontinued heads. The shape of the answer is the same regardless of brand, and we treat the result as a starting point for the customer's engineering check rather than as a clearance to ship.

Form and mounting almost always match within a series because the DIN-rail clip and the backplane connector are the parts that survive across revisions. A 750-842 and a 750-885 share the same footprint; an ET 200S IM151-1 and an IM151-3 also share the same footprint. Matched on this axis for in-series substitutes.

Terminal layout can change silently. The power terminals, the service interface and the address selector may move between revisions even when the outline does not. Verify with the datasheet — out-of-series substitutes require a closer look.

Electrical ratings (supply voltage, current on the backplane, inrush) usually hold within a series but can be tighter on a newer head station with a faster processor. Matched on this axis for in-series substitutes; check before out-of-series.

Function and I/O do not apply at the head level — the head only carries the I/O modules behind it — but the maximum number of slots and the maximum backplane distance can change. Differs on slot count for some migration paths.

Firmware, hardware version and engineering-software compatibility is the axis that breaks the swap. The substitute head may need a different GSDML revision; the controller project may need to be re-imported; the program blocks that referenced the old revision may need to be rebuilt. Unknown to us by design — the program lives on the customer's engineering workstation and we do not have visibility into it.

Communication and protocol is the axis that decides whether the network comes back at all. The protocol family, the role, the supported revision and the diagnostics must all match. Verify against the original manufacturer's datasheet before quoting the substitute as compatible.

Mechanical parameters (connector torque, allowed cable cross-section) usually hold but can tighten on newer heads; environmental class (operating temperature, vibration) usually holds; ingress protection usually holds; materials and construction usually holds; certifications and lifecycle — CE, UL, the lifecycle stage field — are the axes where the manufacturer sometimes drops an approval on the older head station and adds it on the newer one, and the customer's market may require an approval the newer head does not carry. Unknown to us for the customer's market; we do not advise on certifications.

The shape of the answer for any head-station swap is the same: matched on the visible axes, unknown on the firmware and the program-software axes, and verify before any commitment. That last line is not boilerplate. It is the only honest answer an independent desk can give when the program lives on the customer's workstation.

What we will and will not do on a head-module cross-reference

We will pull together the catalog data — datasheet links, protocol fields, lifecycle stage, available substitutes within the same series — and produce a one-line-per-axis table that the buyer's engineering team can read against their own project. We will not re-import the GSDML into the controller, will not re-commission the station on the network, will not change the device name or IP address, and will not certify that the substitute station will operate the same diagnostics as the original.

The substitute head station ships with its own datasheet, its own set of GSDML files and its own commissioning manual. The customer's engineering team downloads those, compares them against the original project, updates the project where needed and downloads the new configuration into the controller. Until that step is done, the station does not come online. Once it is done, the line comes back up.

The one situation in which we will not offer a substitute is when the head station carries a functional-safety protocol — PROFIsafe, CIP Safety — and the replacement is from a different brand or a different safety revision. That determination belongs to the customer's functional-safety process, not to a sourcing desk, and we will tell the buyer so explicitly when the request would otherwise look like a routine cross-reference.

When the protocol axis is the whole answer

The protocol axis collapses the question to its simplest form: does the substitute speak what the controller scans? If yes, the rest of the axes are engineering work. If no, the rest of the axes do not matter, and the substitute is the wrong answer regardless of how well the form factor or the terminal layout lines up.

The case where this matters most is a panel built around a controller that has been discontinued and is being replaced as part of a migration. The I/O station behind the controller may still be in production, but the controller will look for the original protocol family at the original revision. A migration that does not check the protocol stack first will swap a working I/O station for a working substitute and lose the network at commissioning time. The protocol axis is the axis that decides whether a migration is a swap or a redesign.

Quote structure for a head-module substitution request

A request that lands as a single line — one part number, one cross-reference — gets a single-line response: the substitute, the protocol field, the lifecycle stage, the available condition per line and the per-line price, MOQ and lead time.

A request that lands as a half-rack migration — five or six head stations across three brands — gets a table response: one row per line, one column per protocol field, and one column for the unknown axes we cannot resolve from our catalog. The customer reads the table against their own project and replies with the lines they will commit to. Cross-brand line item lookups across our catalog are routine for us, and lines that touch three brands or more are quoted as one consolidated shipment under the trade term you confirm.

In both cases the buyer receives the same discipline: every line is sourced individually, every line is conditioned individually with the condition stated per line (new, new surplus, refurbished or used), every line is priced individually. Nothing is bundled into a single figure that hides a costly substitute. The lead time is quoted per order rather than carried from a previous quote. Where a line is ambiguous, we come back with a clarifying question instead of substituting our best guess into the quote. Send us your bom when you are ready and we will work it line by line.

What the customer ships with the substitute head

A fieldbus head station ships with the same documents that travel with any automation order: a commercial invoice, a packing list and, where the head is sold as refurbished, the bench-test record captured at the desk. For a used unit pulled from a working station, the photograph record taken before dispatch captures the front, the label, the address selector and any connector wear that the buyer should see before the unit goes into the cabinet. For a new-surplus unit, the photograph record captures the sealed packaging and the original label.

The shipping documents do not change with the destination. A head station bound for Moscow gets the same commercial invoice and packing list as a head station bound for Munich or Manila. What changes is the trade term on the quotation: EXW, FCA, DAP or DDP — whichever term the buyer confirmed when the quote was accepted. Transit time is a property of the carrier and the customs channel; we do not quote a fixed number of days. The terms of sale on the quotation are the contract. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.

What to send in the first message

For a single-line head substitution, send the part number on the label, the brand and series, the protocol family if it is known, the machine or station the head is going into and the urgency. A photograph of the front of the head with the address selector or the device-name sticker visible moves the identification forward by one round-trip.

For a migration across several stations, share your bom in any format — Excel, PDF, a photograph of a printed table — with the part numbers, the quantities and any substitution notes the engineering team has already written. Where a part number is partial or a description is ambiguous, send it anyway and flag it; identification is part of the work, not a prerequisite for it.

The fastest path through a head-module substitution request is the same as the fastest path through any other line in a sourcing desk's queue: a clean part number on the first message, the urgency stated up front and a willingness to accept that the protocol axis will need to be verified before the order is committed. Every other axis is engineering work; the protocol axis is the one that decides whether the network comes back. When the protocol axis is settled, contact our sourcing desk through the inquiry page and we will work the line from there.

About this article

This piece was written by the aoctrl.com supply-chain desk, an independent distributor — not an authorized distributor of any manufacturer named in the article — for procurement, hardware engineer, maintenance and panel builder readers who need to keep an automation line running. As of September 2026, the protocol stacks named in the article (PROFINET, PROFIBUS, EtherCAT, Modbus TCP, EtherNet/IP, CC-Link, DeviceNet, INTERBUS) and the head-module families named (Siemens ET 200S, WAGO 750) remain the fieldbus and remote I/O families in current use in the China-based surplus and factory channels we work with. No manufacturer has endorsed this material.

Data Notes

Protocol stacks named are general-purpose fieldbus families; per-substitute protocol coverage depends on the individual head station's datasheet, not on the family name.
Lifecycle-stage values reflect the manufacturers' own published notices; a station marked active by the manufacturer may still be in allocation at franchised channels.
Per-line condition, MOQ, price and lead time are quoted per order, not carried from previous quotes.
Trade terms (EXW, FCA, DAP, DDP) are the term stated on the quotation; transit time is a property of the carrier and the customs channel.

FAQ

When a fieldbus head module is discontinued, what actually replaces it?

Three routes exist: remaining channel stock of the original part, a manufacturer-documented cross-reference to the next-generation head in the same series, or a last-time-buy allocation before the original is no longer manufactured. Each route carries a different lifecycle profile, and the route that applies depends on the brand, the series and the urgency the buyer is working with.

Is the substitute head station pin compatible with the original?

Within the same series and same generation, mounting and backplane connector usually match. Out-of-series substitutes usually require re-checking the terminal layout and the power-rail pin assignment against the datasheet. The substitute that looks interchangeable on the rail is not always interchangeable on the network.

Does the substitute head station need a new GSDML file?

Usually yes. PROFINET, PROFIBUS, EtherCAT, EtherNet/IP and other industrial-Ethernet families are described by GSDML, GSD, ESI or EDS files, and the controller project imports those files when the station is added. A substitute head station at a higher firmware revision usually ships a newer GSDML; the controller project may need to be re-imported before the station will come online.

Who re-commissions the station on the network after the swap?

The customer's engineering team. The program lives on the engineering workstation and is not visible to a sourcing desk. We supply the substitute head with its datasheet and its GSDML files; the engineering team imports the new files into the project and downloads the new configuration into the controller.

Will a higher-priced substitute work where a cheaper one fails?

Not necessarily. The protocol stack, the firmware revision and the engineering files decide whether the station comes back online. A more expensive substitute with the wrong protocol stack still leaves the controller unable to find the station. The right substitute is the one whose protocol fields match the controller project, regardless of price.

Do you substitute head stations on safety-rated networks?

No. Where the head carries a functional-safety protocol — PROFIsafe, CIP Safety — and the request is for a different brand or a different safety revision, we will not offer a substitute. The determination belongs to the customer's functional-safety process, and we tell the buyer so explicitly when the request would otherwise look like a routine cross-reference.

What documents travel with the substitute head?

A commercial invoice, a packing list and, for refurbished or used units, the photograph record or bench-test record captured before dispatch. The shipping documents do not change with the destination. Trade terms — EXW, FCA, DAP or DDP — are the term stated on the quotation, and the quotation is the contract.