Sanity check: Make sure it properly initializes

Previously the way the error code was dealt with meant if the
error code never changed from the initial value the alarm was
never initialized.  The alarm API already checks for toggling
the field so no need to avoid it in the wrapper method.
ManualControl: Ensure that alarm is always initialized

Same logic as the previous alarm.  It might make sense to move
the logic that prevents double toggling the fields into the
alarms.c file like AlarmSet.
Merge pull request #225 from peabody124/sanity_check

Fix system alarm error codes