On Monday 04 October 2021 22:36:31 Chris Morley wrote: > HI Gene. > > AXIS never had pins to control selection of axes - only status > outputs. There is a good reason. If you use an external switch to > control the selection, then you must disallow GUI selection, because > the external and GUI selection can get out of synch.
It currently works on the correct axis key held down to switch, and remembers that selection. That true is visible in axisui. My circuit is issueing a pulse, fixed at 30ms at the moment so it can be caught in the 200hz jog-thread. I've been running for years with a 10 microsecond pulse and the rest of my hal logic hasn't missed a beat in that many years. > AXIS currently > has no option to disallow GUI axis selection and i wouldn't think that > would be a good option without some visual changes. You could probably > add code to AXIS with axisrc option but that would require someone to > help you figure out how. I might be up to that, but not without some hand holding. > If you are adventurous and are using 2.8 or master you could try > qtaxis. Qtaxis is an AXIS look alike (mostly) and covers most of > AXIS's features. It is also (with some work) fully customizable. I'm running ther current master on all machines, sitting on pins and needles waiting for pyvcp to die, but it hasn't, yet. How do I sample it, assuming I start with a clone of my current config? I cloned the 6040 config, and changed the DISPLAY to qtaxis and then qtaxis.ui but it can't execute either. Probably missing the correct qtvcp etc. Dependencies list? > It not super tested though - or at least i haven't heard feedback from > anyone. One nice feature of qtaxis is you can undo an offset touch off > with a single button press. But its new code and would require working > through problems. (I'd suggest cloning your config) Might not be worth > the trouble for you. To get rid of this problem, seems to me to be no more than a 9 input or. Last plus input wins, and that logic is already there. acccepting the last true signal, although I cannot imagine in my case I'd have enough hands to run the dials, each of which is pulseing an input as I turn them, while at the same instant playing chopsticks on the keyboard. I can reach one dial and the keyboard, but can't find a reason I should if this is fixed. The internal logic in axis obviously has "abcuvwxyz" inputs, and expanding that logic with 9 or2's & bringing those extra 9 inputs out for the user's logic to tickle from his hal file seems like an easy solution to the touch-off of the wrong axis problem. But lets try Qtaxis first, it could be just what the dr ordered. It doesn't run, probably missing dependencies. Thanks Chris. 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, 1940) 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-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
