PlanMaker OCT2HEX: 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.

=OCT2HEX(Number [, Digits])

Number is required. Supply octal text, using only 0 through 7. 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 octal 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 =OCT2HEX(A2) and C2 =OCT2HEX(A2,12) through row 7.

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

The source gives both =OCT2HEX("52") and =OCT2HEX("0052") as 2A. Their common quantity is 42: 5×8+2=2×16+10. Width 1 is too short for 2A and gives the documented #NUM! error.

The negative control =OCT2HEX("37777777726") is FFFFFFD6. Its unsigned positional value is 4,294,967,254; subtracting 2^32 gives −42. The high-bit-set representation uses eight hex digits under PlanMaker’s 32-bit rule, not a ten-character negative word.

On CompactReadings, put text 377,400,401 in F2:F4. Fill G2 =OCT2HEX(F2,3) through G4. Expected strings are 0FF,100,101, corresponding to decimal 255,256,257. Each reading increases by one even though the displayed digits cross different carry boundaries.

A two-place request fits FF but cannot hold 100. Conversion can represent the later number within its signed domain, while the requested receiver field is too narrow. Keep that formatting failure distinct from an out-of-range source value.

The inputs 17777777777,20000000000,37777777777 convert respectively to 7FFFFFFF,80000000,FFFFFFFF. Their signed quantities are 2,147,483,647; −2,147,483,648; −1. The middle pair is not a continuously increasing unsigned interval after interpretation.

For a positive bit-group control, =OCT2HEX("645") is 1A5, because both mean 421. This checks a different grouping of the same nine significant bits. It does not choose signedness, byte order or a field’s semantic meaning for an external file; preserve that specification with the raw source.

=OCT2HEX("52",8.9) has independent expected output 0000002A, 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.