Updates to web site, enable input, reverse input, etc.

We have a limit on RPM implemented in DMOCmotorController and CODAmotorcontroller
I was just dropping torque to zero if we exceeded our RPM limit.  After bench testing today, I'm going to try cutting torque request in half when hitting RPM limit.  It's a little bumpy as is on the test bench.

Modified web site to display throttle raw values instead of percentages.  I have found these values very useful when setting upper and lower limits on the THROTTLE page.  Percentages somewhat less so.

ENABLE and REVERSE work well on the UQM.  The UQM quits reporting rpm and torque and current when in reverse, other wise works as expected.

ENABLE works particularly well on CODAUQM module.  I can actually be cranking away at 2200 rpm and 71 Nm or torque - about 50 amps, and lose teh enable - everything comes to a stop.

But both enable and reverse are very strange on DMOC645.  Reverse works,  but takes regen values as positive torque commands in the reverse direction.  As a result, very low throttle levels cause lots of motor rotation in reverse - we should be in regen.

Similarly the ENABLE input has little effect for DMOC645.