PlanMaker HEX2BIN: 32-Bit Conversion, Width and Worked Examples

The PlanMaker 2026 manual, 2024 manual and 2021 manual were retrieved on October 15, 2026. They document this function in those manual families. They do not establish its original introduction or a last-working-version endpoint; both historical endpoints remain unverified. Support in every FreeOffice/mobile edition or individual desktop build is outside this check.

No native PlanMaker execution was performed. Expected values below are independently checked mathematical controls, not captured application results. Formulas use the English manual’s commas; verify localized names and separators in the installed product.

=HEX2BIN(Number [, Digits])

Number is required. Supply hexadecimal text, using only 0–9 and A–F. Quote literals inside formulas and set source cells to text before entering them. This avoids automatic decimal interpretation or loss of long numeral strings.

The documented domain is signed −2,147,483,648 through 2,147,483,647. Negative inputs and results use a 32-bit two’s-complement word. The manual’s encoded endpoint notation identifies signed values; it is not an increasing interval of ordinary unsigned hexadecimal magnitudes. These are PlanMaker-specific rules, not assumed limits of another product with the same function name.

Digits is optional: omitted means the required width is chosen automatically. A supplied Digits must be greater than zero. Fractional Digits are truncated. If a positive result needs more significant places than the requested width, the documented error is #NUM!. Negative values use their 32-bit representation and ignore Digits. This guide tests that rule with positive widths; it does not infer precedence when a negative Number is combined with an invalid width.

Create BaseControls with Source in A1, Converted in B1 and Width_12 in C1. Format A2:A7 as text and enter the exact strings below. Fill B2 =HEX2BIN(A2) and C2 =HEX2BIN(A2,12) through row 7.

In a copy change A3 from 2A to 2B. B3 becomes 101011, and C3 becomes 000000101011. Row 4 remains an independent leading-zero control for the original 42.

The vendor’s =HEX2BIN("2A") returns 101010. =HEX2BIN("2A",8) returns 00101010, and width 2 gives #NUM!. The accompanying prose says fewer than five binary digits is insufficient, but 42 actually requires six significant binary digits. A five-digit unsigned numeral reaches only 31. This guide uses the correct six-position requirement rather than repeating that explanatory typo.

The hexadecimal expansion is 2×16+10=42; its binary expansion is 32+8+2. Neither the visible characters 2A nor 101010 should be treated as decimal measurements without conversion.

On RegisterBits, set F2:F3 to text and enter A5,A4. Fill G2 =HEX2BIN(F2,8) through G3. Expected strings are 10100101,10100100. Only the rightmost bit changes. The corresponding decimal values are 165 and 164, so the change is one unit.

For a carry boundary, =HEX2BIN("FF",8) gives 11111111. Changing FF to 100 requires 100000000, nine bits; the same eight-place request is insufficient. The conversion’s 32-bit domain allows 256, but a separate eight-bit field rule would reject it.

=HEX2BIN("80000000") has expected output 10000000000000000000000000000000, the signed minimum −2,147,483,648. =HEX2BIN("FFFFFFFF") gives 32 ones, encoding −1. A left zero appended to a positive display is formatting; the high bit of the 32-bit signed word determines a negative interpretation.

Keep source text and word size alongside the expanded bits. This example does not establish a hardware register’s flag names, byte order or transport format. Those meanings come from its own specification.

=HEX2BIN("2A",8.9) has independent expected output 00101010, because truncating 8.9 gives width 8. This does not establish how a fractional source Number or a text numeral containing a decimal point is handled. Use explicit integer widths in production worksheets.

Invalid digits, prefixes, whitespace, Boolean values, blanks and numeric-text coercion outside the source examples do not have a complete documented error matrix here. No exact error token is invented for those cases. Inspect the raw input when a conversion seems wrong; a numeric cell that has already changed the source text cannot be repaired merely by choosing another output base.

Record the installed build, edition, language and workbook format before native reproduction. Check displayed strings and saving/export separately. A mathematically correct representation does not prove that an external receiver accepts the word size or preserves leading zeroes.