BIN2HEX in WPS Spreadsheet: Convert Binary Fields and Preserve Their Signed Meaning

• Introduced: documented by 2019-06-12 in the official WPS lesson; the first release is not established.
• Availability: Current WPS Windows documentation confirms this function. The historical lesson’s edition field is blank.
• Scope: exact current supported builds and other WPS clients remain unverified.
• Checked: October 14, 2026. Documentation and independent calculations; no native WPS execution.

=BIN2HEX(number,[places])

The historical lesson describes a maximum of ten binary input characters and a sign bit with two’s-complement negative notation. Places controls output characters and can be omitted.

The source contains editorial naming slips: one padding paragraph says DEC2BIN, and several remarks spell BIN2HEX as BINZHEX. Its title, syntax and WPS walkthrough consistently identify BIN2HEX, and the walkthrough independently confirms the omitted-width behavior. These slips do not establish an alternative function called BINZHEX.

Use explicit binary strings. The source’s ten-bit input convention is different from a decimal number that happens to contain only zeros and ones.

Enter only column A below in Text-formatted A2:A6. Put =BIN2HEX(A2) in B2 and =BIN2HEX(A2,4) in C2; fill both down.

The quantities are 5, 37, 73, 165 and 300. For 100101, group positive bits as 0010 0101, giving hex 25. The positional check is 2×16+5=37.

For 100101100, group as 0001 0010 1100, giving hex 12C. Its value is 1×256+2×16+12=300. Leading zeros align groups or pad an output without changing the quantity.

Binary text 100101 and decimal number 37 represent the same quantity through different input contracts. BIN2HEX expects the former representation, not the latter decimal quantity.

To add 1 to the converted quantity, decode the output first:

=HEX2DEC(BIN2HEX("100101"))+1

Expected number: 38. HEX2DEC interprets the intermediate hex string 25 as decimal 37. Ordinary decimal arithmetic on the displayed digits 25 would use a different quantity.

Keep numeric data and encoded labels in separate columns rather than relying on how a code looks.

The lesson states that a negative binary input ignores places and returns ten hexadecimal characters. The independently modeled conversions are:

The input uses ten bits, while the output uses forty. For −5, the corresponding unsigned patterns are 2^10−5 and 2^40−5. Each must be decoded using its own signed width to recover −5.

Simply grouping the first negative string as unsigned bits would give 3FF, or positive 1023, rather than −1. That would change the meaning instead of converting it.

=BIN2HEX("1111111011",4) has expected output FFFFFFFFFB under the lesson’s negative-width rule. The example uses a valid width; it does not establish error precedence for conflicting invalid arguments.

For C2:C6 in the first example, =HEX2DEC(C2) yields the independently expected sequence 5, 37, 73, 165 and 300.

A reverse =HEX2BIN(C2,10) yields ten-character binary representations. For the first value, the result is 0000000101, preserving the quantity 5 but not the original three-character width.

HEX2BIN has a documented narrower target interval than the full hexadecimal decoder. The selected positive values fit it; arbitrary hexadecimal strings should not be assumed to do so.

Within its BIN2HEX lesson, WPS documents invalid binary digits or more than ten input characters as #NUM!; insufficient places as #NUM!; fractional places as truncated; nonnumeric places as #VALUE!; and negative places as #NUM!.

For the positive value 300, hex 12C needs three characters, so =BIN2HEX("100101100",2) follows the insufficient-width condition. Places 4.9 truncates to 4 and gives 012C.

The naming slips above are disclosed rather than copied into working formulas. Zero places, prefix cleanup, coercion and native error ordering remain unverified. All examples use the canonical BIN2HEX name established by the WPS-specific title, syntax and walkthrough.

• WPS Academy: BIN2HEX, 2019-06-12 (Chinese).
• Current WPS Windows BIN2HEX introduction.
• Editorial testing standards.

Complete function-specific documentation reviewed. Worked outputs are independently calculated expectations, not captured native results. Formulas use English names and comma separators; check the installed locale. Product/client and source gaps retain their explicit scope.