BUSLOOM MANUAL

Data type reference

Widths, ranges, register order, notation, conversion, and display semantics.

19 · VALUE REFERENCE

Data type reference

Modbus registers are always 16-bit words. A Busloom tag explains how one or more consecutive words become one logical value. Data type controls width and interpretation; byte/word order controls layout; scale and offset produce engineering units; notation and labels control presentation.

Supported tag data types

TypeRegistersRaw range / interpretationNotes
booleanBit space: 1 bit · register space: 1 wordFalse when zero, true when non-zeroBit views always use Boolean; register Boolean may have custom true/false labels
uint1610 … 65,535Supports decimal, hexadecimal, or binary notation
int161−32,768 … 32,767Two's-complement signed integer
uint3220 … 4,294,967,295Word order matters; integer notation is independent
int322−2,147,483,648 … 2,147,483,647Two's-complement signed integer
float322IEEE-754 single precisionRoughly seven significant decimal digits
float644IEEE-754 double precisionRoughly fifteen significant decimal digits
ascii1–125Two bytes per register after configured orderingNUL and non-printable bytes affect the visible text

The decode pipeline

  1. Collect the complete word span

    The source view must include the tag start and every continuation register required by the selected type.

  2. Apply byte order

    Big endian keeps the two bytes inside each 16-bit word; little endian swaps them.

  3. Apply word order

    Most-significant-first keeps register order; least-significant-first reverses the word sequence for the logical value.

  4. Interpret the type

    Read the resulting bytes as signed/unsigned integer, IEEE-754 float, Boolean, or ASCII.

  5. Convert to engineering units

    For numeric types, engineering value = decoded raw number × scale + offset.

  6. Format for display

    Apply precision, notation, unit, and optional value label without changing the underlying decoded number.

32-bit layoutWord 0 bytesWord 1 bytesBusloom settings
ABCDABCDBig-endian bytes · most-significant word first
BADCBADCLittle-endian bytes · most-significant word first
CDABCDABBig-endian bytes · least-significant word first
DCBADCBALittle-endian bytes · least-significant word first

Engineering and presentation fields

FieldWhat it changesWhat it does not change
Scale / offsetNumeric engineering value and inverse encoding for writesAddress, word span, byte order
Display decimalsVisible rounding from automatic precision through 0–12 decimalsFull decoded/exported numeric evidence
UnitContext shown beside values and in reportsNumeric value
Minimum / maximumValidation of manual and automated engineering writesDevice-side limits or alarm behavior
Numeric value labelsAdds a named state beside an exact numeric value and accepts that label as write inputThe numeric value remains visible and retained
True / false labelsNames Boolean statesStored Boolean semantics
DescriptionHuman documentation available in settings and inspectorsProtocol traffic