Ok, I'm starting to figure out the halcmd thing... halcmd shows that the count mode is not being set correctly when testing in PnCConf. When in linuxCNC halcmd shows that is is being set to TRUE (I edited it in hal to use TRUE instead of 1). However in linuxCNC halcmd seems to be showing that based on my MDI commands the dir output and enable outputs are being set correctly while the spinout is not. Looking at the hal again I may have spotted something:
spinout is getting this: net spindle-vel-cmd-abs => hm2_5i25.0.7i76.0.0.spinout yet I don't see spindle-vel-cmd-abs being set: net spindle-vel-cmd-rps <= motion.spindle-speed-out-rps net spindle-vel-cmd-rps-abs <= motion.spindle-speed-out-rps-abs net spindle-vel-cmd <= motion.spindle-speed-out net spindle-vel-cmd-rpm-abs <= motion.spindle-speed-out-abs Not sure if that is an error, but halcmd seems to show the correct dir and enable outputs while the vel stays at 0 ------Original Mail------ From: "John Kasunich" <[email protected]> To: <[email protected]> Sent: Thu, 18 Sep 2014 13:24:20 -0400 Subject: Re: [Emc-users] New to LinuxCNC and PnCConf and need some help... 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 ------------------------------------------------------------------------------ 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
