On Thu, Sep 18, 2014, at 12:32 PM, [email protected] wrote: > >From the hal: > > # ---Encoder feedback signals/setup--- > > setp hm2_5i25.0.encoder.00.counter-mode 1
That _should_ be setting it. But looking at a .hal file to see if it should be setting a bit is not the same using either halcmd show or halmeter to actually look at the real value of the bit _while_ LinuxCNC is running. > Also, even if the encoder setup was wrong, or not set at all, shouldn't I get > some movement in LinuxCNC followed by an error perhaps? You might be right. But troubleshooting is an incremental process. If you know the encoder isn't working right (counting back and forth isn't right), then fix that before going on to the next step. Sometimes one broken thing can cause really bizzare and unexpected side effects elsewhere. > I get absolutely no movement in LinuxCNC yet in PnCConf open loop test it > works. When the open loop test is working, open another shell, and use "halcmd show all >good" to save the entire working setup to a file called "good" for review. When LinuxCNC is not working, open another shell, and use "halcmd show all >bad" to save the entire broken setup to a file called "bad" for review. Then perhaps put both files at a site like pastebin and post a link here so others can review as well. One of HAL's biggest strengths is that you can look at it while it runs, using halcmd show, halmeter, and halscope. There are very few problems that can evade carefull application of those tools. -- John Kasunich [email protected] ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
