For the hygrometer portion of the verification, we included two simulation outputs. Both demontrate the high level correct operation from the frequency determiner input, to the BCD outputs. Set 3 shows the correct operation of the keypad portion of the design.
Once this humidity was determined, we manually changed the frequency of freq_in (from the humidity sensor), to represent a change in humidity of +1%. This should result in no change in any of the outputs from the chip, because changes or 1% are not recorded, as described in the frequency determiner section of this report. Thus, on page 3 of this simulation, where the frequency determiner is finsihed its task, we see no change occured in any of the output values.
We then proceeded to manually change the humidity again by a further +1%. We would expect this change to have appeared on our output this time, since a total change of +2% occured from the last sample. This is in fact what happened. The count from counter1 (the humidity counter) decreased by 2, representaing an increase in humidity of 2%. Thus, this new value was latched and the value progressed down the datapath. See page 4 of the simulation wave for more details.
We repeated the cycle one more time, as seen on pages 5 and 6 of simulation 1. A further change of +1% in humidity produced no change in the outputs (page 5), and an additional change of +1% was recorded in the outputs (page 6). This represents a total change of +4% from the beginning of the simulation, from 27% to 41% relative humidity.
On page 4, 20 was entered on the keypad. This was output correctly in BCD. On page 5, the 'humid' signal went low, due to the desired level (20%) being less than the actual value (39%).