Stuart Stevenson wrote: > Gentlemen, > I had read the manual about the axis.N.index-enable. I had tried > these commands. I am working with my Z axis as this is the easiest to > reach. > > ############################### > > linkpp axis.2.index-enable ppmc.0.encoder.02.index
OK, first thing - never ever EVER use linkpp. It is evil! I know that seems harsh, and its not your fault that you are using it, so please don't take that the wrong way. Let me explain: The linkpp command was added as a shortcut to easily link two pins together. The normal way to do that was (and still is): # create a signal newsig some-meaningful-name whatever-type-the-pins-are # use the signal to connect the pins linksp some-meaningful-name the-first-pin linksp some-meaningful-name the-second-pin The result of those three commands is a signal with a name that means something, connecting the two pins. The linkpp version of that is much shorter and more convenient: linkpp the-first-pin the-second-pin That is equivalent to: # create a signal newsig the-first-pin whatever-type-the-pins-are # use the signal to connect the pins linksp the-first-pin the-first-pin linksp the-first-pin the-second-pin You still wind up with a signal connecting the two pins, but now the signal is named after the first pin. Having a signal and a pin with the same name is legal, but very confusing. In hindsight, 'linkpp' is an abomination that should never have been invented. We now have a much better "shorthand" way to connect two (or more) pins, the 'net' command: net some-meaningful-name the-first-pin the-second-pin The above line is equivalent to the very first example - it results in a new signal with a name that means something, connecting the two pins. > this gives me the error as follows > > HAL: ERROR: signal 'axis.2.index-enable' already has output or I/O > pin(s)HAL:14: linkpp failed > > halshow shows the axis.2.index-enable pin connected to axis.2.index-enable > halshow shows nothing connected to ppmc.0.encoder.02.index > > ############################### > > linksp Zindex axis.2.index-enable > linksp Zindex ppmc.0.encoder.02.index > > ############################### > > linksp Zindex ppmc.0.encoder.02.index > linksp Zindex axis.2.index-enable > > ############################### You get points for persistence - you've tried three different ways of connecting those two pins. Unfortunately ppmc.0.encoder.02.index is not the pin you want. In my last email I wrote: > there should be a HAL pin from the driver called > ppmc.N.encoder.M.index-enable index-enable, not index. Connect the ppmc index-enable to the axis index-enable (use newsig + linksp, or net, not linkpp). I have no idea what the ppmc 'index' pin does. Jon Elson, do you know? It is not part of the "canonical encoder interface", and it is just causing confusion. If there is no good reason for it, it should be deleted. > What am I missing, besides gray matter and a clue? :) No, you were led astray by a confusingly named pin. Regards, John Kasunich ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
