Thomas Kaiser wrote: > > That's exactly what I was looking for. It works perfect for me, right now. > > On the other side, the "or" suggestion from John looks good, too. But I > could not get it working till now :-( > John, do you have a real live example for me? >
The two approaches are significantly different. In one case, you disconnect the signal from the outside world (the parallel port or other input), and then manually set it one way or the other to test things. In my opinion, that is the preferred way if you are simply testing. The other case, using an OR block, means that either the outside world OR your test signal can activate the input. I really don't see a reason for doing things that way - you are just adding more parts, pins, and signals which won't be used once you get your machine working. On the other hand, if you will always want the "force" button, then you the OR solution is the way to go. Regards, John Kasunich ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
