---
title: "A Modbus Register Response Is Not Yet an Industrial AI Quantity"
description: "Leviathan Systems — Technical content Published 2026-10-20; updated 2026-10-20."
canonical: "https://www.leviathansystems.co/articles/industrial-ai-modbus-register-value-encoding-units"
last-updated: "2026-10-20"
---

# A Modbus Register Response Is Not Yet an Industrial AI Quantity

Leviathan Systems — Technical content
Published 2026-10-20; updated 2026-10-20.

A raw Modbus register export and a decoded application quantity deliver different information. The consumer needs the applicable device map to establish which words belong together, their numeric interpretation, scale and unit. Receiving the expected words does not establish that the AI input represents the intended quantity. Compare where that interpretation is performed and what evidence accompanies the delivered value.

## Separate the word from the application quantity

The MODBUS Application Protocol Specification V1.1b3, dated April 26, 2012, describes input and holding registers as 16-bit words in section 4.3. Section 4.2 illustrates most-significant-byte-first encoding: a register containing 0x1234 sends byte 0x12 before 0x34. Section 4.4 makes the mapping to the device application vendor and device specific.

Those rules leave a larger value's interpretation to establish. Byte order inside one word does not identify which words form a group, their significance within that group, an integer or floating-point interpretation, or a physical unit. A general claim of big-endian Modbus is therefore insufficient evidence for an offered 32-bit Float32 layout.

For a buyer, the useful distinction is between preserving words and preserving meaning. An exporter can faithfully return every supplied word while leaving the receiving team responsible for the application interpretation. That can be an appropriate division of work, provided the buyer recognizes what remains to be supplied.

References: [MB1](https://www.modbus.org/file/secure/modbusprotocolspecification.pdf)

## Read type, unit and range as separate definitions

Schneider Electric's Vigilohm IM10-H, IM15H and IM20-H register-table-format page in VIGED310023EN-05 illustrates the distinction. It documents separate Unit, Type and Range columns alongside address, register and description fields. Its note specifies big-endian byte order for that product documentation's Float32 data type. That product-specific note is not a layout rule for every Modbus device.

A coding type describes a representation; a unit identifies the quantity's unit of expression. A permitted range can be narrower than the coding type allows. None substitutes for the others. The page supplies a useful example of how documentation separates these meanings; it is not the source of the fictional energy map below.

References: [MB2](https://www.productinfo.schneider-electric.com/im10h_15h_20h/5c6572558469760001311068/IM10H15H20H%20UM/English/BM_IM10H-20HUserManual_0000203462.xml/$/R_Communications_ModbusRegisterFormat_IM20_0000088508)

## MBVAL-111: two words become one 10 kWh quantity

MBVAL-111 is a wholly fictional interpretation of already supplied words, 0x0001 and 0x86A0. Its hypothetical map explicitly defines one unsigned 32-bit count spanning those two words, with the HIGH WORD FIRST, at 0.1 Wh per count. No real device, register address, capture or measured energy use is represented. The example defines a representation for arithmetic; it provides no device procedure.

Under that stipulated map, the first word contributes the high 16 bits and the second contributes the low 16 bits. Their unsigned decimal word values are 1 and 34464. The high-word contribution is multiplied by 2^16 = 65536, so the combined count is 1 × 65536 + 34464 = 100000 counts.

The scale then establishes 100000 counts × 0.1 Wh/count = 10000 Wh. Converting Wh to kWh gives 10000 Wh ÷ 1000 Wh/kWh = 10 kWh. The two received words have therefore supplied parts of one stipulated value, rather than two independent energy observations.

Each step answers a different question. Grouping establishes that the words belong to one value. Word significance establishes their positions. The unsigned integer definition establishes the count interpretation. Scaling supplies Wh, and the final unit conversion expresses that same quantity in kWh. HIGH WORD FIRST and 0.1 Wh/count are assumptions of this fictional map, not universal Modbus rules.

## The same words can survive while their meaning is lost

Suppose an offer returns two independent fields, 1 and 34464, and labels each energy. It has retained the separate decimal word values but lost MBVAL-111's grouping. Neither field is the stipulated 100000-count value. Two fields also do not establish two observations at different times; here they are the two parts defined for one value.

Now suppose another offer correctly combines the words but returns 100000 Wh. It has attached the unit without applying the stipulated scale. That is 100 kWh, ten times the example's 10 kWh. Returning 10000 and changing its label from Wh to kWh would instead omit the unit conversion: 10000 kWh is one thousand times 10 kWh. A unit label cannot perform arithmetic.

Type errors are a different mechanism. Width determines how many bits participate; signedness determines how a signed encoding treats them. This example's combined integer has its top bit clear, so this one value would not distinguish unsigned from signed 32-bit two's-complement interpretation. A plausible result here cannot verify signedness for other values. Float32 is another numeric representation, not a synonym for two registers or a scaled integer.

Likewise, the two individual words can retain their internal byte order while their positions in a larger group are reversed. Confirming the within-word byte rule cannot resolve that grouping error.

## Compare the two offers at the consumer's actual input

Consider an offer that supplies raw words and leaves decoding to the buyer's software owner. Against MBVAL-111, its deliverable is the word pair, plus whatever origin and mapping information the offer actually includes. It can satisfy a raw-export requirement. If the intended consumer requires energy in kWh, the interpretation work still needs an identified owner and an applicable definition.

A second offer promises decoded application quantities. For this same fictional input and map, it should be able to explain the chain from the two words to 100000 counts, 10000 Wh and the returned 10 kWh. That explanation makes the promised transformation assessable. A screen displaying 10 alone leaves both its derivation and its unit unresolved.

Connect the explanation to the actual proposed equipment and software: identify the device model, applicable firmware and map revision, selected mapped quantity, word grouping, numeric representation, scale and returned unit. The appointed device and software owners establish the actual interpretation. A worked explanation using an unrelated map does not establish applicability to their equipment.

Also identify any normalization performed before the consumer receives the value. If the feed returns 10 kWh, the receiving team needs to know that the scale and unit conversion have already been applied, rather than apply them again. Preserve enough interpretation identity with retained data to explain it later; a newer map should not silently redefine what earlier records meant.

## A correct interpretation leaves other evidence to establish

MBVAL-111 establishes a conditional result: these words, interpreted under this stipulated map, yield 10 kWh. It does not establish that the two words came from one coherent device update, that the observation is fresh, that any associated quality or status is acceptable, or that the value corresponds correctly to the physical process. Those are separate evidence requirements for the intended use; a register-map document cannot prove them by itself.

Keep unresolved interpretation visible too. If the map's applicability, a documented special-value meaning or a required conversion is unknown, a normal-looking number does not resolve that gap. Treating an unknown interpretation as zero would introduce a new quantity unsupported by the supplied evidence. The consumer's responsible team must define how that unresolved input is handled.

The related OPC UA guide addresses capture, filtering and retained change history. The operational digital-twin guide addresses physical identity and time-qualified relationships; the Redfish guide addresses metric timing and resource-health meaning. These complement the decoding decision. Buying more compute or retaining more rows cannot, by itself, establish an absent application definition.

## Bring a separate cabling requirement to its physical scope

If the equipment project separately needs physical network cabling, Leviathan's Structured Cabling & Fiber Installation service covers agreed fiber and copper installation to approved pathways, endpoint schedules and labeling rules. The service and project inquiry below are appropriate for discussing those physical connections and their handoff records.

Share a nonconfidential equipment and connection outline, supplied-material responsibilities and required installation records to discuss scope, requirements and availability. Modbus interpretation, data-feed software, industrial-control integration and AI operation remain with the appointed device, software and process owners.

References: [L1](https://www.leviathansystems.co/services/structured-cabling)

## Primary sources

- [MB1 — Modbus Organization — MODBUS Application Protocol Specification V1.1b3](https://www.modbus.org/file/secure/modbusprotocolspecification.pdf). Checked 2026-10-20. April 26, 2012; sections 4.2–4.4, printed pages 5–7. Establishes register encoding and the boundary to device-specific application mapping.
- [MB2 — Schneider Electric — Vigilohm Modbus register table format, VIGED310023EN-05](https://www.productinfo.schneider-electric.com/im10h_15h_20h/5c6572558469760001311068/IM10H15H20H%20UM/English/BM_IM10H-20HUserManual_0000203462.xml/$/R_Communications_ModbusRegisterFormat_IM20_0000088508). Checked 2026-10-20. Preserved original edition-05 primary-page text defining unit, coding type, permitted range and the product's Float32 byte order. Applies only to those format definitions, not a current-edition claim or the fictional energy map.
- [L1 — Leviathan Systems — Structured Cabling & Fiber Installation](https://www.leviathansystems.co/services/structured-cabling). Checked 2026-10-20. Defines agreed physical fiber and copper installation, endpoint identification and connection records for a separate cabling requirement.

## Related Leviathan resources

- [OPC UA sampling, queues and missing changes](/articles/industrial-ai-opcua-sampling-queue-publishing)
- [Operational digital twins: identity, time and relationships](/articles/operational-digital-twin-identity-time-relationships)
- [Redfish metric timing and resource-health meaning](/articles/redfish-metric-report-time-versus-resource-health)
- [Structured Cabling & Fiber Installation](/services/structured-cabling)
- [Discuss a separate physical network-cabling project](/contact?service=structured-cabling&from=%2Farticles%2Findustrial-ai-modbus-register-value-encoding-units)

## Discuss a separate physical cabling project

Share a nonconfidential equipment, connection and handoff outline to discuss physical installation scope, requirements and availability.

[Discuss the scope](/contact?service=structured-cabling&from=/articles/industrial-ai-modbus-register-value-encoding-units)