1.6. Conversion from decimal numerationBecause octal and hexadecimal numeration systems have bases that are multiples of binary (base 2), conversion back and forth between either hexadecimal or octal and binary is very easy. Also, because we are so familiar with the decimal system, converting binary, octal, or hexadecimal to decimal form is relatively easy (simply add up the products of cipher values and placeweights). However, conversion from decimal to any of these "strange" numeration systems is a different matter. The method which will probably make the most sense is the "trialandfit" method, where you try to "fit" the binary, octal, or hexadecimal notation to the desired value as represented in decimal form. For example, let's say that I wanted to represent the decimal value of 87 in binary form. Let's start by drawing a binary number field, complete with placeweight values: . .         weight = 1 6 3 1 8 4 2 1 (in decimal 2 4 2 6 notation) 8 Well, we know that we won't have a "1" bit in the 128's place, because that would immediately give us a value greater than 87. However, since the next weight to the right (64) is less than 87, we know that we must have a "1" there. . 1 .        Decimal value so far = 64_{10} weight = 6 3 1 8 4 2 1 (in decimal 4 2 6 notation) If we were to make the next place to the right a "1" as well, our total value would be 64_{10} + 32_{10}, or 96_{10}. This is greater than 87_{10}, so we know that this bit must be a "0". If we make the next (16's) place bit equal to "1," this brings our total value to 64_{10} + 16_{10}, or 80_{10}, which is closer to our desired value (87_{10}) without exceeding it: . 1 0 1 .        Decimal value so far = 80_{10} weight = 6 3 1 8 4 2 1 (in decimal 4 2 6 notation) By continuing in this progression, setting each lesserweight bit as we need to come up to our desired total value without exceeding it, we will eventually arrive at the correct figure: . 1 0 1 0 1 1 1 .        Decimal value so far = 87_{10} weight = 6 3 1 8 4 2 1 (in decimal 4 2 6 notation) This trialandfit strategy will work with octal and hexadecimal conversions, too. Let's take the same decimal figure, 87_{10}, and convert it to octal numeration: . .    weight = 6 8 1 (in decimal 4 notation) If we put a cipher of "1" in the 64's place, we would have a total value of 64_{10} (less than 87_{10}). If we put a cipher of "2" in the 64's place, we would have a total value of 128_{10} (greater than 87_{10}). This tells us that our octal numeration must start with a "1" in the 64's place: . 1 .    Decimal value so far = 64_{10} weight = 6 8 1 (in decimal 4 notation) Now, we need to experiment with cipher values in the 8's place to try and get a total (decimal) value as close to 87 as possible without exceeding it. Trying the first few cipher options, we get: "1" = 64_{10} + 8_{10} = 72_{10} "2" = 64_{10} + 16_{10} = 80_{10} "3" = 64_{10} + 24_{10} = 88_{10} A cipher value of "3" in the 8's place would put us over the desired total of 87_{10}, so "2" it is! . 1 2 .    Decimal value so far = 80_{10} weight = 6 8 1 (in decimal 4 notation) Now, all we need to make a total of 87 is a cipher of "7" in the 1's place: . 1 2 7 .    Decimal value so far = 87_{10} weight = 6 8 1 (in decimal 4 notation) Of course, if you were paying attention during the last section on octal/binary conversions, you will realize that we can take the binary representation of (decimal) 87_{10}, which we previously determined to be 1010111_{2}, and easily convert from that to octal to check our work: . Implied zeros .  . 001 010 111 Binary . —  — . 1 2 7 Octal . Answer: 1010111_{2} = 127_{8} Can we do decimaltohexadecimal conversion the same way? Sure, but who would want to? This method is simple to understand, but laborious to carry out. There is another way to do these conversions, which is essentially the same (mathematically), but easier to accomplish. This other method uses repeated cycles of division (using decimal notation) to break the decimal numeration down into multiples of binary, octal, or hexadecimal placeweight values. In the first cycle of division, we take the original decimal number and divide it by the base of the numeration system that we're converting to (binary="2" octal="8", hex="16"). Then, we take the wholenumber portion of division result (quotient) and divide it by the base value again, and so on, until we end up with a quotient of less than 1. The binary, octal, or hexadecimal digits are determined by the "remainders" left over by each division step. Let's see how this works for binary, with the decimal example of 87_{10}: . 87 Divide 87 by 2, to get a quotient of 43.5 . — = 43.5 Division "remainder" = 1, or the < 1 portion . 2 of the quotient times the divisor (0.5 x 2) . . 43 Take the wholenumber portion of 43.5 (43) . — = 21.5 and divide it by 2 to get 21.5, or 21 with . 2 a remainder of 1 . . 21 And so on . . . remainder = 1 (0.5 x 2) . — = 10.5 . 2 . . 10 And so on . . . remainder = 0 . — = 5.0 . 2 . . 5 And so on . . . remainder = 1 (0.5 x 2) . — = 2.5 . 2 . . 2 And so on . . . remainder = 0 . — = 1.0 . 2 . . 1 . . . until we get a quotient of less than 1 . — = 0.5 remainder = 1 (0.5 x 2) . 2 The binary bits are assembled from the remainders of the successive division steps, beginning with the LSB and proceeding to the MSB. In this case, we arrive at a binary notation of 1010111_{2}. When we divide by 2, we will always get a quotient ending with either ".0" or ".5", i.e. a remainder of either 0 or 1. As was said before, this repeatdivision technique for conversion will work for numeration systems other than binary. If we were to perform successive divisions using a different number, such as 8 for conversion to octal, we will necessarily get remainders between 0 and 7. Let's try this with the same decimal number, 87_{10}: . 87 Divide 87 by 8, to get a quotient of 10.875 . — = 10.875 Division "remainder" = 7, or the < 1 portion . 8 of the quotient times the divisor (.875 x 8) . . 10 . — = 1.25 Remainder = 2 . 8 . . 1 . — = 0.125 Quotient is less than 1, so we'll stop here. . 8 Remainder = 1 . . RESULT: 87_{10} = 127_{8} We can use a similar technique for converting numeration systems dealing with quantities less than 1, as well. For converting a decimal number less than 1 into binary, octal, or hexadecimal, we use repeated multiplication, taking the integer portion of the product in each step as the next digit of our converted number. Let's use the decimal number 0.8125_{10} as an example, converting to binary: . 0.8125 x 2 = 1.625 Integer portion of product = 1 . . 0.625 x 2 = 1.25 Take < 1 portion of product and remultiply . Integer portion of product = 1 . . 0.25 x 2 = 0.5 Integer portion of product = 0 . . 0.5 x 2 = 1.0 Integer portion of product = 1 . Stop when product is a pure integer . (ends with .0) . . RESULT: 0.8125_{10} = 0.1101_{2} As with the repeatdivision process for integers, each step gives us the next digit (or bit) further away from the "point." With integer (division), we worked from the LSB to the MSB (righttoleft), but with repeated multiplication, we worked from the left to the right. To convert a decimal number greater than 1, with a < 1 component, we must use both techniques, one at a time. Take the decimal example of 54.40625_{10}, converting to binary: REPEATED DIVISION FOR THE INTEGER PORTION: . . 54 . — = 27.0 Remainder = 0 . 2 . . 27 . — = 13.5 Remainder = 1 (0.5 x 2) . 2 . . 13 . — = 6.5 Remainder = 1 (0.5 x 2) . 2 . . 6 . — = 3.0 Remainder = 0 . 2 . . 3 . — = 1.5 Remainder = 1 (0.5 x 2) . 2 . . 1 . — = 0.5 Remainder = 1 (0.5 x 2) . 2 . PARTIAL ANSWER: 54_{10} = 110110_{2} REPEATED MULTIPLICATION FOR THE < 1 PORTION: . . 0.40625 x 2 = 0.8125 Integer portion of product = 0 . . 0.8125 x 2 = 1.625 Integer portion of product = 1 . . 0.625 x 2 = 1.25 Integer portion of product = 1 . . 0.25 x 2 = 0.5 Integer portion of product = 0 . . 0.5 x 2 = 1.0 Integer portion of product = 1 . . PARTIAL ANSWER: 0.40625_{10} = 0.01101_{2} . . COMPLETE ANSWER: 54_{10} + 0.40625_{10} = 54.40625_{10} . . 110110_{2} + 0.01101_{2} = 110110.01101_{2}
