On Thursday 02 April 2020 08:36:11 andy pugh wrote: > On Thu, 2 Apr 2020 at 12:25, Ken Strauss <[email protected]> wrote: > > > The fact that m66 Enn uses #5399 regardless of the nn is being an > > > obstacle. It means that I'll have to use some digital outputs to > > > tally whether or not #5399 has been read and by whom. > > I don't understand the problem. The inputs can only be read one at a > time. > > M66 E0 > #50 = #5399 > M66 E1 > #51 = #5399 > M66 E2 > #52 = #5399 > M66 E3 > #53 = #5399
I'm doing similar with #<_varname> but keeping them "in-synch" is being a connundrum. It sure seems to be a cobble job to use a dio, set when the motion.analog-out-NN has been written with fresh data in the hal file, and cleared by a read of that memory location, but I fail to see how a dio using an MCode can be used to tell hal the last value written has not been read yet. And if the data gets scrambled, we are back to broken taps. The path is not 2-way. > > I like the suggestion. I believe that the docs say that M66 Enn is > > limited to nn=0 to 3. Tormach's PathPilot appears to allow nn=0 to > > 7. > > You can have up to 64 each of analogue and digital inputs using the > num_aio and num_dio modparams to motmod. > http://linuxcnc.org/docs/2.8/html/man/man9/motion.9.html 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
