Gene Heskett wrote: > Greetings guys; > > newsig motion.probe-input bit > linkps parport_pin-10-input => motion.probe-input
You are only making half the connection. You're an electronics guy, are you familiar with the concept of netlists? A net connects two or more pins. Or how about wiring diagrams? Wires typically are numbered, and wire 23 connects two or more things. In HAL, a signal corresponds to a net or a wire, and pins are the things it connects. Your first command above creates a signal (or net or wire, whatever term makes the most sense to you) called "motion.probe-input". That command does NOT connect the signal/net/wire to anything. The second command connects the signal to the parport. But you haven't connected it to the motion controller. What you really want to do is connect a signal between the _pin_ "motion.probe-input", and the parport pin. That signal needs a name, but I strongly recommend that you do not use either pin name for the signal, it just leads to confusion. Lets call the signal "probe". The following commands create the signal, connect it to the motion controller, and connect it to the parport, in that order. newsig probe bit linksp probe motion.probe-input linksp probe parport.0.pin-10-in In version 2.1.4 or CVS head, there is a shorthand command to do this, called net. You give the signal name first, then the pin(s) that you want the signal to connect, like so: net probe motion.probe-input parport.0.pin-10-in Hope this helps, John Kasunich ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
