On Thursday 07 October 2021 22:38:39 John Dammeyer wrote: > > From: Gene Heskett [mailto:[email protected]] > > Subject: [Emc-users] Another question I haven't asked but should, re > > incorporating my dials into the active axis buttons. > > > > Hello all; > > > > Axis apparently hasn't the resources to do what I want, and which I > > am convinced other users with controlling pendents would also find > > very handy. > > > > Is there anther gui besides axis, that can do what I want? > > > > What I want is for a signal from one of the dials that can move this > > lathe, to update the last active axis button. These signals are only > > activated if the dial is enabled AND being turned. They are not > > generated if the dials enabling timer has timed out. The result > > would be equivalent, and identical to jogging the machine with the > > keyboard resulting in a touchoff always being applied to the last > > axis moved. > > > > If there is another gui that *can* be made to do that, please name > > it, and I will attempt to learn it. > > > > Thanks all. > > > > Cheers, Gene Heskett. > > Hi Gene, > > I agree with you that the pendant should change the radio button. > It's a human factors user issue that needs to be fixed. The problem > is as far as I can see the pendant doesn't send information when the > dial is switched to another axis. > Separate per axis dials here John. Located on the carriages apron.
> And if you think about it, the switch itself doesn't rotate back to X > if you have it on Z and jog X on the keyboard. So you're right that > the radio button can only change if a step message is sent for a > specific axis. Presently ONLY by the keyboard or a mouse click, both of which are about as handy as a $3 bill. Which I can do but only to halui, which also registers it in its halshow section, but axis ignores that halui stuff. > I did start looking into it but haven't had time over the last little > while. I think this should be possible but it requires a change to > AXIS to make the radio buttons read/write and available which it looks > like they aren't. And the pendant software has to be able to then set > the radio button. Which is exactly what I want to do. And no one has given me a reason this cannot be done. Someone, Chris I think, made the argument that it could get out of synch, and what I want to do assures that synchronization is maintained by assuring the radio buttons follow that last moved by rule. The present situation puts it out of synch unless the mouse is used to click on the correct button, or the keyboard jog key is used, and the keyboard jog key moves the machine off the point I just set with the dials. The dials have their own per click size settings that are not affected by the axis jog speed sliders. I can set movement as small as .0001" per click, or up to 20 thou, each dial independently, I can set it for more in hal, but even at 20 thou that machine can't keep up with a good spin of the dials. There are, acc the docs, two modes for jogging, one is absolute value, the other stops when the dial stops, but that just feels wrong. And takes longer to detect the stop, overshooting the desired position. I can even set up mseeages to remind me to use the mouse to correct the radio buttons, but that gets me a message per click, and would get tiresome clearing all those at 400 per full turn, particularly when an in pin in axisui would only need two target additions in the net statements from the click detectors in my hal file to solve this problem correctly and forever. > Like you I've been caught with touching off what I think is the Z > because I used the pendant to sneak up to the surface but on AXIS it's > still at X. Then press start and watch it head at full speed toward > the table because Z is incorrect. Or in the lathe case, run a tool with a $20 carbide chip in it into a chuck jaw spinning at whatever rpm, with my bronze bushings and only a 1 horse motor, 600 revs is tops but its still a bent tool and a shattered chip even at 30 revs. Eggzactly John, with EGG$penive broken tooling being part of the hill-air-itty ensuing. Absolutely nothing hilarious about broken tooling. The keyboard inputs are only true for the duration of the keypress and I can't make a good argument to deny me the ability to "or" that signal from my dials to do exactly the same as the last moved by logic in axis that now runs those buttons. I'm not using the inputs in halui, but testing a year or so back, using halui to move the machine also fails to update the axis buttons. Fixing that would also enable this to become automatic once the "net" statement were corrected. I'd call fixing that a huge step forward in "mistake free" usability. Thanks John. We make 2 on record as having been "caught out" by this. The answer to how many more of us there might be in that "caught out" list would include anybody using a pendant or game pad as a pendent. Thats likely at least half of us. Thanks John. 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
