However, I think I've tried that before and encountered complications, but maybe only with overflow/underflow checking, which (I assume) we're ignoring here. pdf section 29) you will see that the instructions are for bit and byte manipulation with only add and subtract math functions so Rev Ed already have to impliment multiply and divide plus 16-bit math in firmware. We have other school projects underway that need this expanded PICAXE maths function so are interested in finding an elegant solution.

The GCF of two non-zero integers, x(16) and y(32), is the greatest positive integer m(16) that divides both x(16) and y(32) without any remainder.However I am sure with the brains of ALAN, WOMAI , Q Maths and others an optimal picaxe subroutine can be configured and agreed on to give an immediate solution. Be careful in changing to other variables than those used here as some of the consituent bits of word variables w1 and w0 are used to simplify the maths. So, if we were writing a "specification" for a "32-bit divison" subroutine and agree that it's to be a 32-bit numerator divided by a 16 (or 15) bit divisor, we still have to decide whether the result should be 16 or 32 bits and whether the input variable values should be retained, corrupted or maybe overwritten by result data. As the rain sensor is probably only accurate to around 5 - 10% you could just scale all of your data down to single words.

All other numerators should gnererate an out-of-range value and as I said earlier my code has no range testing. That is very different from a "32 bit" division with 3 "input" words and perhaps as many (assigned) output words (result, remainder). This is being done in hopes of cooling Esau's wrath for what Jacob did to him 20 years earlier (Genesis 27:30–35; 27:41–45). In all parts of the kingdom of Christ, the lowest as well as the highest, "judgment" and "righteousness" shall prevail (comp.I don't know if this may help or inspire anyone, but here's the code to calculate a 32-bit result from a 16-bit x 16-bit multiplication, "result = lhs * rhs", using only word and byte values.

quick question does each socket need its own MCB or can I run 2 16amp sockets off of the same 16 amp MCB if they are not going to be used at the same time? However, I believe that womai's code takes about 30% longer to execute (probably because of the / and * instructions) and I suspect (not tested) westaut's is longer still because of the 32 iterations. But I would likely work out on paper what each step of the algorithm should produce and then compare what stepping through the program produces. I can't test the X-series shift commands, but the w2 = w2 + w2 format (to shift left) appears to be about 10% faster than w2 = w2 * 2 and twice the speed of w2 = w2 / 2 (shift right).The lack of direct support for overflow/carry flags with PICaxe basic is rather a pain, so a "cheat" I've done is to restrict the denominator to one bit less i. The ENCS63/415/S13/32/16 has a 63 Amp Panel Inlet by Mennekes and 9 different outlets, each protected by a Type A RCD and C Curve MCBs by ABB or Doepke.