Direct Answer

A cheaper pass-through gateway saves money, so why must some projects use a protocol-conversion gateway? The judging criterion is "who turns registers into data points": choose pass-through when the cloud already has unified parsing and the device point tables are fixed; choose protocol conversion when device brands are mixed, the cloud does not do proprietary parsing, or local caching is needed. The FG-0221-ER offers both pass-through and conversion forms, and the ESX intelligent edge computing gateway supports edge-side parsing — pick the gateway form by "parsing responsibility".

A scene: a project ordered pass-through gateways to save money, but the site had 6 meter brands and the cloud recognized only standard protocols — the pass-through gateways shipped raw registers upstream, the cloud could not parse them, and the data was useless — switching to protocol-conversion gateways, edge-side parsing made the platform work. Pass-through or conversion, in one line: look at "who turns registers into data points" — the cloud parses, choose pass-through; the cloud does not parse, choose conversion.

1. The Pass-Through Gateway's Boundary: A Pipe Only

Duty — a pass-through gateway is only a "pipe": it moves site frames unchanged to the cloud — no parsing, no mapping, no caching; Prerequisite — the cloud must have unified parsing: the platform reads register tables and maps points — parsing responsibility sits in the cloud; Advantages — cheap, simple, fast forwarding: frames travel unchanged, no edge-side logic; Limits — useless when the cloud does not parse proprietary protocols; no caching or local alarms during an outage — a pure pipe has no edge intelligence.

In one sentence: the pass-through gateway is a "courier" — frames delivered as-is, parsing in the cloud — choose it only when the cloud can parse; without that, it is wasted.

A boundary example: a project's cloud platform already had built-in point tables for mainstream meters (standard Modbus) — pass-through gateways shipped frames as-is and the cloud parsed and mapped them — simple and cheap. The money pass-through saves is conditional on the cloud already parsing — "the cloud can parse" is the pass-through's entry ticket.

2. The Protocol-Conversion Gateway's Edge Duties: Parse + Map + Cache

Parsing — edge-side register reads and protocol parsing: translates raw frames into standard data points; Mapping — edge-side point-table mapping: applies point tables by device type, unified format upstream; Caching — local cache during an outage, catch-up after recovery: no data loss, no alarm interruption; Edge intelligence — local alarms, local logic: what pass-through cannot do, conversion can — "no blackout during an outage".

In one sentence: the protocol-conversion gateway is a "translator plus warehouse" — parsing, mapping and caching on the edge; the cloud receives standard data points — a little more money buys edge capability.

An edge example: 6 meter brands, the cloud recognizing only standard protocols — the conversion gateway parsed 6 protocols on the edge and unified the mapping upstream — the cloud received all-standard data and the platform integrated in one pass. The extra money for a conversion gateway buys "the cloud does not need per-brand adaptation" — the edge digests the messy protocols and the cloud only sees standard.

3. Cloud-Side vs Edge-Side Parsing: Cost Comparison

Cloud-side parsing (pass-through) — the cloud adapts per brand: more brands, more adaptations; every brand upgrade requires parsing changes — parsing cost grows with brand count; Edge-side parsing (conversion) — one mapping suite on the gateway: however many brands, all digested on the edge — parsing cost is one-time, not brand-scaled; Bandwidth cost — pass-through ships raw frames (large); conversion ships standard points (small) — conversion saves bandwidth at high data volumes; Maintenance cost — pass-through maintains parsing in the cloud, conversion maintains mapping on the edge — edge maintenance wins with mixed brands.

In one sentence: the cost watershed is "brand count" — few brands, cloud parsing is cheaper; mixed brands, edge parsing is cheaper — choose by on-site brand complexity.

A cost example: 3 brands (few) — the cloud builds 3 adaptation suites, the pass-through plan is cheap; another project with 8 brands (mixed) — 8 cloud adaptations, 8 places to touch on every upgrade — switching to edge parsing, one mapping suite, cheaper long term. Few brands, pass-through saves; mixed brands, conversion saves — parsing cost follows brand count, so the choice follows brand count.

4. Why Mixed-Brand Projects Inevitably Choose Conversion

Parsing explosion — more brands, more cloud adaptations: N brands, N adaptation suites, N-fold maintenance; Upgrade risk — a brand firmware upgrade changes the protocol: all cloud adaptations must be redone — edge mapping is locally redone; Integration speed — edge parsing goes live in one pass; cloud adaptation goes live per brand — weeks apart in project schedule; Engineering norm — mixed brands are the norm on site: 3-6 brands in one switch room is common — the conversion gateway is "standard equipment for mixed-brand sites".

In one sentence: the parsing cost of mixed-brand projects grows exponentially — the more mixed the brands, the better value edge conversion — an inevitable choice driven by the engineering norm.

A mixed-brand example: 5 brands in a switch room, no private parsing in the cloud — pass-through meant 5 cloud adaptations and a 6-week cycle — switching to a conversion gateway, one edge parse and a 2-week cycle — integration speed 3× apart. Mixed brands + cloud without parsing = the must-have scenario for conversion — the question is not "expensive or cheap", it is "can it integrate at all".

5. Hybrid Deployment in the Transition: Pass-Through + Conversion Together

Scenario — a project in transition: some devices are already adapted in the cloud, some brands are not — use a mix when one gateway form cannot solve everything; Practice — already-adapted brands run pass-through (cheap), unadapted brands run conversion (works) — each form covers its segment; Unified uplink — both forms go to the same platform: unified management, pass-through and conversion data normalized; Transition strategy — conversion first, then pass-through: once the cloud adapts everything, a conversion gateway can be demoted to pass-through — no wasted investment.

In one sentence: no either/or during transition — adapted brands pass through, unadapted brands convert, both upstream to one platform — conversion first, then pass-through, investment not wasted.

A hybrid example: 3 brands already adapted in the cloud, 2 not — adapted brands ran pass-through (saving cost), unadapted brands ran conversion (keeping access) — both upstream to one platform with unified management; once the cloud adapted all, the conversion gateways were demoted to pass-through. "Pass-through saves + conversion keeps the access" in parallel — hybrid deployment balances cost and integration.

6. Common Misconceptions: Three Judgment Errors Between the Two

Misconception one: look only at price, not parsing responsibility — choose pass-through because it is cheap, without confirming whether the cloud parses — wasted entirely with mixed brands; Misconception two: think conversion is omnipotent — protocol conversion solves "protocol incompatibility", not "missing physical ports" — no-port devices still need external modules; Misconception three: pick only one form in transition — all pass-through or all conversion — mixing adapted and unadapted balances cost and access.

In one sentence: three misconceptions map to three judgments — parsing responsibility, capability boundary, hybrid deployment — judge right and the gateway form does not rework.

A misconception example: a project bought a full batch of pass-through for the price — on arrival, 4 brands had no cloud adaptation — the whole batch was swapped for conversion, and the savings became rework costs — the review: ordering before confirming the cloud's parsing capability. The right way to save with pass-through is "confirm the cloud parses first" — judgment first, then the saving holds.

7. Back to FEXLINK: How to Decide Pass-Through or Conversion

To land this logic on products: the FG-0221-ER offers both pass-through and protocol-conversion forms, and the ESX intelligent edge computing gateway supports edge-side parsing, mapping and outage caching — pick the form by "parsing responsibility": the cloud parses, choose pass-through; the cloud does not, choose conversion; in transition, deploy hybrid. Three steps: ① look at the cloud (unified parsing?) → ② look at the brands (mixed?) → ③ look at outages (local cache and alarms needed?) — three answers and the form is decided.

One summary: pass-through vs conversion is a "parsing responsibility" contest — "the cloud parses" chooses pass-through (saves money); "the cloud does not parse / brands mixed / outage capability needed" chooses conversion (keeps access) — the criterion in one line: who turns registers into data points. Ask whether the cloud parses first, then whether brands are mixed — two questions answered, the gateway form is set.

One reminder: do not force pass-through to save money — choosing pass-through without confirming the cloud's parsing capability is betting "the site is all standard protocols" — in mixed-brand, cloud-unparsed projects, every cent saved by pass-through becomes rework cost later. The money in selection is saved by "judging right" — confirm the parsing responsibility first, then order the gateway form.

Scope and Limitations

  • The conclusions in this article are intended for LV distribution and electrical-safety sites. Criteria are compiled from public codes and FEXLINK product documentation, and product parameters follow the latest selection handbook and product knowledge base.
  • Quantitative criteria (protection zone, discharge and residual voltage, earth resistance, thresholds and grading) hold under the preconditions stated in this article. Where the site voltage level, earthing arrangement, environmental category or load profile differs, the figures must be recalculated. Specific configurations involving FG-0221-ER(transparent transmission and protocol conversion), ESX intelligent edge computing gateway should be verified against actual circuit parameters.
  • Specific product models and parameters are subject to the latest selection handbook and product knowledge base; this article does not constitute selection or procurement advice.
  • Standard numbers cited here refer to the currently effective editions; when a standard is revised, the related quantitative conclusions must be re-checked.
  • Deployment and implementation for specific projects must be carried out by qualified engineers based on site survey and design drawings.

Frequently Asked Questions

Transparent Passthrough vs. Protocol Conversion Gateway

A cheaper pass-through gateway saves money, so why must some projects use a protocol-conversion gateway