On Wednesday 06 March 2019 16:11:24 a k wrote: > hi > Andy > what about > " The closed loop drive has the ability to issue an > e-stop if it gets out of synch and can't fix it, and you should add > that alarm pin to the lcnc e-stop logic in your hal file" > 1. this only software code add in or need allocate wire -hardware etc. > 2. is a there description on documentation where talk about add e-stop > in case of using close loop system? > > thanks you > aram > What you'll probably find will be quite near the end of your main hal file. It is not well described (IMO) in the LinuxCNC Documentation.pdf nor in the corresponding hal document. You'll find all this doc stuff in a normal install, in /usr/share/doc/linuxcnc.
Here is a snip from one of my machines that has not been modified since the install. Word-wrap off. # ################################################## # Standard I/O Block - EStop, Etc # ################################################## setp estop-latch.0.ok-in true #setp watchdog-reset.in false # A basic estop loop that only includes the hostmot watchdog. # reset from machine-enable button net user-enable <= iocontrol.0.user-request-enable => estop-latch.0.reset net enable-latch <= estop-latch.0.ok-out => iocontrol.0.emc-enable-in # setup the edge, alias wd-bite-reset #net watchdog0 <= iocontrol.0.user-request-enable => watchdog-reset.in #setp wd-bite-reset.out-width-ns 1000 #setp wd-bite-reset.both true #net watchdog1 <= wd-bite-reset.out => watchdog-reset.enable # now it should be reset, now let a bite trigger it off #all one line! # net watchdog1 <= hm2_[HOSTMOT2](BOARD).0.watchdog.has_bit => estop-latch.0.fault-in watchdog-reset.enable # now its off,reset it # so is this #net watchdog2 <= watchdog-reset.out => hm2_[HOSTMOT2](BOARD).0.watchdog.has_bit That which is preceded by a # sign is commented out. An <= can have only one source, but there is nothing to stop you from adding an "or" func- tion that accepts an error signal from an input pin on one input, the watchdog.has_bit on the other input, and then feeding the or's output into the "net" label watchdog1 so that a signal from either src stops it all in its tracks. > On Wed, Mar 6, 2019 at 1:59 AM andy pugh <[email protected]> wrote: > > On Wed, 6 Mar 2019 at 03:36, a k <[email protected]> wrote: > > > Big question : is it possible on one system LCNC have 2 axis using > > > open loop (where software tune axis) and one axis that is close > > > loop? > > > > Yes, LinuxCNC doesn't know or care. > > > > You could even run a gantry with a linear motor on one side and a > > stepper motor on the other. It would be daft, but it would work. > > > > -- > > atp > > "A motorcycle is a bicycle with a pandemonium attachment and is > > designed for the especial use of mechanical geniuses, daredevils and > > lunatics." > > — George Fitch, Atlanta Constitution Newspaper, 1916 > > > > > > _______________________________________________ > > Emc-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/emc-users > > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
