Advanced Search

And Andy found this on the mailing list from one of the developers...

AXIS doesn't pay attention to jog keys with modifier keys pressed
because this had some bad interactions with using the numeric keypad as
digits in MDI mode.

You can put magic incantations in the file ~/.axisrc that customize the
jog keys and also get rid of this behavior of ignoring the key if a
modifier key is pressed.

Here is an example which changes the keys that jog the active axis, and
the keys that jog the A axis:

# -- cut here

---

# Bind ; and ' to jog active axis
root_window.bind("<semicolon>", commands.jog_minus)
root_window.bind("<apostrophe>", commands.jog_plus)
root_window.bind("<KeyRelease-semicolon>", commands.jog_stop)
root_window.bind("<KeyRelease-apostrophe>", commands.jog_stop)

# Bind ( and ) to jog axis 3 (0=X, 1=Y, 2=Z, 3=A, 4=B, ...)
root_window.bind("<parenleft>", lambda e: jog_on(3, -get_jog_speed(3)))
root_window.bind("<parenright>", lambda e: jog_on(3, get_jog_speed(3)))
root_window.bind("<KeyRelease-parenleft>", lambda e: jog_off(3))
root_window.bind("<KeyRelease-parenright>", lambda e: jog_off(3))
# -- cut here

---

To edit your ~/.axisrc file, open a terminal window (Applications > Accessories >
Terminal). Then type "gedit .axisrc". Paste the lines above into the file,
then click save, then close the application.

The next time you run emc, the settings in the .axisrc file will take effect.

To edit it again, just do the same thing: "gedit .axisrc" in the
terminal.

If you want to use different keys, here's how to figure out what to use instead
of "parenleft" and so on: In the terminal, type "xev". A new window
will pop up. Click on it, but keep an eye on the terminal window. When
you press a key, it will print several lines of information on the
terminal. The one that matters is this one:
state 0x0, keycode 34 (keysym 0x5b, bracketleft), same_screen YES,
^^^^^^^^^^^
that keysym string is the one to put in your .axisrc file.

Jeff

And we just found step-by-step instructions:

thread.gmane.org/gmane.linux.distributio...er/12638/focus=12642

Andy's suggestion to use .axisrc is better than my not so well thought out answer. If it exists, the contents of ~/.axisrc are executed as Python source code just before the AXIS gui is displayed. Putting your changes in .axisrc they won't get overwritten at the next upgrade...

John

btvpimill wrote:

Andy, Simply Golden. You make it almost childs play.

Well, of course, it ISN'T child's play, because all these things interact, and all servos have finite
gain, and all systems have springiness and mass. So, this imposes additional effects that
come in in the form of natural vibrational frequencies. So, you can get resonances if
there is springiness and mass, and the servo loop adds energy at those frequencies.

But, Andy's explanation is a good foundation. The best thing is to set up a servo
system, learn how to use Halscope, and play with the servo response and how
the PID and FF1 & 2 affect it. Of course, the whole plan is to reduce following
error under a variety of situations to a minimum.

One of the bad features of the I term is that a machine tool axis is not a steady
state system, it is constantly accelerating and decelerating and reversing
direction, while cutting tools apply additional perturbations to the system.
A good I response while in one mode will adversely affect the system when the
load or direction changes. That's why I use it sparingly.

When you first try to set up a servo it will all seem magic, and the settings will
seem to have no rational connection to what happens. If you play with it for
a while, it will start to make sense.

Jon

BigJohnT wrote:

Otherwise you would have to modify axis.py to change the key bindings. I scanned through the 3400 lines of code and nothing jumped out at me.

Is this thing on?
www.linuxcnc.org/component/option,com_ku.../lang,english/#14678

Ok, that makes sense the machine is correct but you don't stand in the conventional position. Have you give any thought to using a joy pad to jog with instead of lugging the keypad to the machine? Otherwise you would have to modify axis.py to change the key bindings. I scanned through the 3400 lines of code and nothing jumped out at me.

John

here is a scheme.

Here is the photo.

If i stay left side all is ok, but usually i stay in front and i confuse me with jog.

Normally when you stand in front of a XYZ machine the X axis is the one that goes left/right, the Y in/out, the Z up,down. Normal machines X+ jogs the tool to the right and Y+ jogs the tool away from you and Z+ jogs the tool up. I say tool because some machines move the spindle in XY and some move the material in XY but relative to the material the tool movement is what you want to move in the correct directions.

Unless you have some strange machine... do you have a photo of it?

John

Thanks,
when i'm in front of the machine i see Y axis: moving right + direction, moving left - direction. X axis moving to me + direction and far to me - direction.
Home position is right - up (far to me).

I hope you understand my bad english!

So when push arrow key i need:

arrow-right -> Y +
arrow-left -> Y -
arrow-up -> X-
arrow-down -> X+

where can i find axis.py?

ioiotutu wrote:

is it possible remap some commands keys?

I think so.
linuxcnc.org/docs/html/gui_axis.html#r1_11_4

Though I don't know if that allows you to re-map keys which are already allocated. I also have no idea what the correct syntax is, but you can probably just copy the program lines from inside Axis.

AFAIK you have edit axis.py to change keyboard mapping. Are you wanting to do this because your machine jogs backwards?

John

I have a couple of buttons that feel natural to use when holding down the top buttons... hmmm all I ever use is fast and slow... I need to change mine to have an axis lock out.

John

Hi,
is it possible remap some commands keys?

I need to swap arrow-left/arrow-right (X moving) with arrow-up/arrow-dn (Y moving). Is there a config file for this?

Thanks,
Michele

jeff_HATC wrote:

2) G10 sets variables to certain values for the cordinate system. Can it do this for register 5241?

#5241 is the X-position of Coordinate System 2. Are you sure that is the one you want to set?
EMC2 will accumulate rotations in the motor position registers, that is just the way it is. it won't cause any problem until you get to several billion revolutions. It needs to do this to correctly sequence the step generator.

3) I am not sure why a rotary table would be allowed to go past 360 anyways.

. Milling spirals is one example, you could legitimately G1 X50 A3600 to make a 10-turn 3mm pitch spiral.

Any way to force it to see 360 and zero as the same position?

Yes, see WRAPPED_ROTARY in www.linuxcnc.org/docview/html/config_ini...b:%5BAXIS%5D-section

Whilst it makes sense to wrap a rotary if you are doing a position then mill sequence, if you are doing machining cuts using the rotary you almost certainly don't want to wrap.

I think you want to use G10 L20 A0 at the start of your cycle, and accept that the axis offset value will accumulate.
(doing it at the start means that the value in that parameter file will be reset on the first run after a restart.). The data types used mean that there is no danger of overflow.