hazards,digital logic
raticus wrote;
What on earth is a hazard problem?
Sounds bad!!!
Raticus;
The best way to explain a hazard is this way.
Hazards are created when using minimizing techniques like k-mapping.
Sometimes the minimizing is too good.
For example, If you get you k-map to 2 gates but there is no overlap on the k-map. A condition may cause a short duration pulse from one on/off state to the other.
Sometimes the hazard isn't critical but...! and I mean a big BUT - It can cause unexpected results. These results usually cause undesired outputs etc...
I think the best way to deal with hazards is in the initial design phase of the circuit (paper and pencil). As your minimizing your equations, you can see the hazards on the k-map, paper, etc...
Here you can see which hazards (if any) are critical and must be dealt with and which are not critical because it will happen in a "don't-care" state.
I hope this explaination helps out a little. I know there are members who has more knowledge there.
Hope this helps.
WA