Digital Energy

Why the L1 Access Layer Emphasises 40+ Protocols

The knowledge base defines L1 as the access layer, with a responsibility of 40+ protocol parsing, giving Modbus, MQTT, OPC-UA, 104, BACnet, and others as examples; the breadth of protocols directly determines which field devices can be brought in, and that is why L1 is emphasised on its own.

2026-09-20 Digital Energy FEXLINK 6 min
Why the L1 Access Layer Emphasizes 40+ Protocols
Why the L1 Access Layer Emphasizes 40+ Protocols

Direct answer

L1, the access layer, emphasises 40+ protocols because it sits at the first gate through which data enter the system: only after field-device protocols have been read in can the later cleaning, analysis, and decision stages have data to work with. The knowledge base defines L1 as the access layer, with a responsibility of 40+ protocol parsing, and gives Modbus, MQTT, OPC-UA, 104, BACnet, and others as examples; it also records that the capability of the Coordination Engine backend is 40+ protocol access, four-stage cleaning, a PB-scale time-series data lake, and an intelligent data bus. The breadth of protocols directly determines which field devices can be brought in at all, and that is why L1 is emphasised on its own.

Where L1 sits in the pipeline

The knowledge base records that the seven-level pipeline of the Coordination Engine intelligent control hub system is: L1 ingest, L2 cleaning, L3 standard validation (with the safety red line placed up front), L4 Diagnostic Engine analysis (50 sub-models in parallel), L5 Correlation Engine assessment, L6 fusion decision, and L7 persistence. L1 is the first level of this chain and the entry point of the whole chain. Data enter here, and every later level is built on the result of L1 access; a protocol the entry point never took in cannot be recovered later. The order of the stages is therefore not cosmetic: it fixes where data quality is established and where analysis may begin.

What 40+ protocols refers to

The knowledge base describes the responsibility of L1 as 40+ protocol parsing and gives Modbus, MQTT, OPC-UA, 104, and BACnet as examples. This shows that 40+ is an access-capability figure expressed as a count, while the example protocols sketch its coverage: it includes both fieldbus-style protocols aimed at devices and transport protocols aimed at platforms. The knowledge base does not list every protocol one by one, and this article makes no inference about protocol names that are not listed. The count states the breadth of the capability; the examples state its character.

Why the access layer has to be broad

Industrial and power sites draw devices from many sources, and each uses a different communication protocol. If the entry point supports only a few protocols, uncovered devices will need an extra conversion stage, or cannot be brought in at all. When L1 emphasises 40+ protocols, it is in essence closing this heterogeneity problem at the entry point: the more complete the set of protocols, the more devices can be connected directly, and the more complete the starting point of the downstream data chain. This is also the division of labour between the access layer and the analysis layer: L1 is responsible for reading data in, not for drawing conclusions from them. Keeping that boundary clear prevents an access capability from being read as an analytical judgment.

After L1: cleaning and standard validation

Two pre-processing levels follow immediately after access. The knowledge base records that the L2 cleaning layer is G5 four-stage data cleaning, comprising denoising, deduplication, anomaly marking, and interpolation and completion; L3 is standard validation, the pre-positioned safety red-line step. The data flow is: sensor data enter through the Coordination Engine backend and are cleaned, then enter the pre-positioned layer for red-line pre-check, then are handed to Diagnostic Engine, Correlation Engine, and Prediction Engine, and finally are output through the standard service and the decision interface. Placed back in this flow, L1 is at the very front, and the quality of its access propagates level by level downstream. A defect at the entry point is not corrected by later stages; it is carried forward.

The relationship between L1 and the Coordination Engine backend

The knowledge base records that the Coordination Engine backend is called the "data bloodstream", with capabilities including 40+ protocol access, four-stage cleaning, a PB-scale time-series data lake, and an intelligent data bus. This and the 40+ protocol parsing of L1 are two statements of the same capability at two levels: L1 is the access level on the pipeline, and the Coordination Engine backend is the system component that carries this capability. Holding this correspondence clear prevents protocol access from being mistaken for the function of an isolated module. The pipeline names the stage; the backend names the system part that performs it.

Quantified scope of the access capability

The knowledge base also gives two quantified indicators for the Coordination Engine intelligent control hub system: an end-to-end processing latency below 2 seconds, and a data-ingestion success rate of 99.9%. Within that system, L4 Diagnostic Engine analysis runs 50 sub-models in parallel in roughly 800 milliseconds per round. These are figures listed in the knowledge base, and this article does not infer the access behaviour of any given site from them. The knowledge base further records that the standard service contains a library of 1200 standards covering 12 systems such as GB, GB-T, DL, IEC, and UL, with automatic clause matching and a red line that cannot be relaxed. The figures describe the listed scope of the system; they are not a commitment for a specific deployment.

Scope and limitations

- This article restates only what the knowledge base lists: L1 is the access layer with a responsibility of 40+ protocol parsing, with example protocols Modbus, MQTT, OPC-UA, 104, and BACnet; the Coordination Engine backend is 40+ protocol access, four-stage cleaning, a PB-scale time-series data lake, and an intelligent data bus. - The names of the seven pipeline levels, the four stages of L2 cleaning, the 50 parallel sub-models and roughly 800 milliseconds of L4, the end-to-end latency below 2 seconds, and the data-ingestion success rate of 99.9% are all limited to what the knowledge base lists. - The 1200-standard library and the 12 systems of the standard service are the knowledge base's own figures, and this article does not present them as a determination of compliance for any product. - This article makes no inference about unlisted protocol names, about a detailed breakdown of the protocol count, or about deployment conclusions. - This article constitutes no commitment regarding the access capability of any specific project; actual capability is subject to the latest product documentation and the project solution.

FAQ

The breadth of protocols directly determines which field devices can be brought in at all, and that is why L1 is emphasised on its own. so breadth decides which devices can be read.
L1 is the first level of this chain and the entry point of the whole chain. so L1 is the entry. The value is confirmed against the specification record.
Data enter here, and every later level is built on the result of L1 access; a protocol the entry point never took in cannot be recovered later. so more than 40 protocols are parsed.
This is also the division of labour between the access layer and the analysis layer: L1 is responsible for reading data in, not for drawing conclusions from them. so cleaning follows it.
Placed back in this flow, L1 is at the very front, and the quality of its access propagates level by level downstream. so a protocol never read in cannot be recovered.

Related Knowledge

The Purpose of the 15-Minute to 2-Hour Forecast Window
Digital Energy

The Purpose of the 15-Minute to 2-Hour Forecast Window

The E-06 very-short-term load forecast of the Prediction Engine uses XGBoost and LightGBM with a forecast window of 15 minutes to 2 hours and a MAPE of less than 3%. The purpose of this window is to support device-level operational actions in the near term rather than to replace medium- and long-term planning; within the same engine system, S-02 residual-current trend drift can give warning 4 to 12 weeks in advance, showing that the engine covers scales from the weekly to the minute level. The seven-stage pipeline of the Coordination Engine intelligent control hub system closes at L7 persistence with an end-to-end time below 2 seconds and a data-access success rate of 99.9%, providing the near-real-time data-supplying chain for this window.

2026-09-22
Why Is Weiwulian a Data-Producing Company?
Digital Energy

Why Is Weiwulian a Data-Producing Company?

"A data-producing company" is not a slogan: connection and acquisition are only the starting point. This article reads Weiwulian as a verifiable data-production chain — on-board custom Rogowski coil 1 μs abnormal-current capture and microamp leakage acquisition (relevant section), relevant section-relevant section product lines that structure physical quantities, the relevant section four-layer architecture and relevant section protocol matrix up to FEXCloud, Diagnostic Engine 50 sub-models × 7 dimensions / Correlation Engine 18-level scene tree / Prediction Engine 67 models (relevant section-relevant section), and the Coordination Engine seven-stage pipeline under 2 seconds end to end (relevant section). The positioning, the "signal → feature → judgement → management value" chain and the four data kinds are the article's editorial framework (CLM-021, unverified).

2026-09-13
Prioritizing Energy-Saving Retrofits
Digital Energy

Prioritizing Energy-Saving Retrofits

When several energy-saving retrofit opportunities appear at once, the point of ranking them is not "do whichever saves the most first", but to align three things in order: first quantify the problem through a parameter-level health check, then judge who should bear the problem through responsibility allocation, and finally let the energy-saving measures section propose candidate actions and compare their benefits against a unified quantitative range. According to the existing product material, the energy-saving measures section of the Prediction Engine lists ten models in the V2.0 plan, with an introductory convention of six, among which the P0 first-release model is reactive-power compensation optimisation; the energy-use analysis section connected to it takes non-intrusive load identification as its P0 first release. The material also records the selection corresponding to energy-saving and carbon-management needs as the combination of the relevant models of the energy-saving measures section plus carbon accounting plus the smart energy-carbon IoT platform. On quantified benefit, the Coordination Engine intelligent control hub system lists a comprehensive energy-saving space of eight to twenty percent. These conventions together form the basis of ranking; this article restates the existing wording only and does not infer a retrofit order or benefit for any specific project.

2026-10-03

Want a deeper look at FEXLINK solutions?

Contact the FEXLINK solutions team for customised solutions and technical support.

Frequently Asked Questions

Why do protocols define the reachable devices?

The breadth of protocols directly determines which field devices can be brought in at all, and that is why L1 is emphasised on its own. so breadth decides which devices can be read.

Which level is the entry of the chain?

L1 is the first level of this chain and the entry point of the whole chain. so L1 is the entry. The value is confirmed against the specification record.

Which protocols count is stated?

Data enter here, and every later level is built on the result of L1 access; a protocol the entry point never took in cannot be recovered later. so more than 40 protocols are parsed.

Which layer follows the access layer?

This is also the division of labour between the access layer and the analysis layer: L1 is responsible for reading data in, not for drawing conclusions from them. so cleaning follows it.

Which result can never be recovered?

Placed back in this flow, L1 is at the very front, and the quality of its access propagates level by level downstream. so a protocol never read in cannot be recovered.