Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-28 Thread John Thornton 
ArcEye from the forum has info on key mapping in Axis

http://www.mgware.co.uk/

JT

On 6/27/2015 4:49 PM, Tom Easterday wrote:
> I tried all combinations of STEP_SCALE, MIN_LIMIT, and MAX_LIMIT using the 
> .axisrc hack to display a back lathe.  There is one config where everything 
> works EXCEPT that the up arrow moves the carriage down and down arrow moves 
> the carriage up  - see "4) " below.  So, I if I can find the trick to 
> remap the arrow keys I might have this working.  I don’t see the keys being 
> messed with in the .axisrc code below.  Does anyone know what I would enter 
> to reverse the meaning of the arrow keys for just the X axis (up/down keys)?  
> Or, barring that, is there some other parameter that I have overlooked that 
> will get me the behavior shown here: 
> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe 
>  ?
>
>
> I have this in .axisrc:
> if lathe:
>   bind_axis("Down", "Up", 0)
>   def set_view_y(event=None):
>   widgets.view_z.configure(relief="link")
>   widgets.view_z2.configure(relief="link")
>   widgets.view_x.configure(relief="link")
>   widgets.view_y.configure(relief="sunken")
>   widgets.view_p.configure(relief="link")
>   vars.view_type.set(4)
>   o.reset()
>   glRotatef(90, 1, 0, 0)
>   glRotatef(90, 0, 1, 0)
>   if o.canon:
>   mid = [(a+b)/2 for a, b in zip(o.canon.max_extents, 
> o.canon.min_extents)]
>   glTranslatef(-mid[0], -mid[1], -mid[2])
>   size = [(a-b) for a, b in zip(o.canon.max_extents, 
> o.canon.min_extents)]
>   o.set_eyepoint_from_extents(size[0], size[2])
>   else:
>   o.set_eyepoint(5.)
>   o.perspective = False
>   o.lat = -90
>   o.lon = 0
>   o.tkRedraw()
>
> TclCommands.set_view_y = commands.set_view_y = set_view_y
> root_window.bind("v", commands.set_view_y)
> root_window.after_idle(commands.set_view_y)
>
> ---
> If I have:
> MIN_LIMIT= - 2.1
> MAX_LIMIT=0.001
> Then,
> If I change the sign of step_scale:
>
> “+” causes:
>   1) up arrow to move down, down arrow to move up  (bad)
>   2) motor down is more negative on dro, motor up is more positive (good)
>   3) turret moves from home position zero to -2.1 as it should (good)
>  4) * see note above
>
> “-“ causes
>   1) up arrow moves up, down arrow moves down (good)
>   2) motor up is more negative, motor down is more positive (bad)
>   3) turret won’t move down, but will move up and hit hard stop (bad)
> ---
> If I have:
> MIN_LIMIT= 2.1
> MAX_LIMIT=0.001
> Then,
> If I change the sign of step_scale:
>
> “+” causes:
>   1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
> limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft 
> limit”
>
> “-“ causes
>   1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
> limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft 
> limit”
> ---
> If I have:
> MIN_LIMIT= 0.001
> MAX_LIMIT= 2.1
> Then,
> If I change the sign of step_scale:
>
> “+” causes:
>   1) up arrow to move down, down arrow to move up  (bad)
>   2) motor down is more negative on dro, motor up is more positive (good)
>   3) turret won’t move down, but will move up and hit hard stop (bad)
>
> “-“ causes
>   1) up arrow moves up, down arrow moves down (good)
>   2) motor up is more negative, motor down is more positive (bad)
>   3) turret moves from home position zero down to 2.1 as it should but 
> wrong sign (bad)
> ---
> If I have:
> MIN_LIMIT= 0.001
> MAX_LIMIT=  - 2.1
> Then,
> If I change the sign of step_scale:
>
> “+” causes:
>   1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
> limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft 
> limit”
>
> “-“ causes
>   1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
> limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft 
> limit”
> ———
>
> -Tom
>
>
> ———
>
>> On Jun 26, 2015, at 11:53 PM, Tom Easterday  wrote:
>>
>>
>>> On Jun 26, 2015, at 10:33 PM, Kirk Wallace  
>>> wrote:
>>>
>>> I think the up arrow and positive X motion values should move the cross
>>> slide in a positive direction. For back or rear tool lathes it is common
>>> for the positive direction to be away from the operator position (with
>>> the spindle to the left). You should be able to set up the motion part
>>> fairly easily using the sense (+/-) of the scale value.
>> Agreed, and I can set the scale such that +X is up.  Check.
>>
>>> Once the hardware motion is set up, the plotter screen can be addressed
>>> and will need the .axisrc patch or some other software solution applied
>>> to Gremlin. I suspect if the .axisrc patch doesn't

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Tom Easterday 
Would be good to take a look
Thanks,
-Tom

> On Jun 27, 2015, at 7:12 PM, Drew Rogge  wrote:
> 
> Hey Tom,
> 
> I'm not sure I have everything correct on my EMCO 120 but I can send you my 
> config files if it would help.
> 
> Drew
> 
>> On 6/27/15 3:48 PM, Tom Easterday wrote:
>> Check that, doing this doesn’t seem to have any effect that I can see.  The 
>> tools still appear as back tools but the arrow keys are still mapped 
>> incorrectly.
>> -Tom
>> 
>>> On Jun 27, 2015, at 6:32 PM, Tom Easterday  wrote:
>>> 
>>> 
 On Jun 27, 2015, at 6:13 PM, Kirk Wallace  
 wrote:
 You might try changing
 bind_axis("Down", "Up", 0)
 to
 bind_axis("Up", "Down", 0)
 
>>> That seems to put the display back in normal (not back tool) mode, but the 
>>> X arrow keys are still backwards…
>>> -Tom
>>> 
>> 
> 
> --
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors 
> network devices and physical & virtual servers, alerts via email & sms 
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> ___
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Drew Rogge 
Hey Tom,

I'm not sure I have everything correct on my EMCO 120 but I can send you my 
config files if it would help.

Drew

On 6/27/15 3:48 PM, Tom Easterday wrote:
> Check that, doing this doesn’t seem to have any effect that I can see.  The 
> tools still appear as back tools but the arrow keys are still mapped 
> incorrectly.
> -Tom
>
>> On Jun 27, 2015, at 6:32 PM, Tom Easterday  wrote:
>>
>>
>>> On Jun 27, 2015, at 6:13 PM, Kirk Wallace  
>>> wrote:
>>> You might try changing
>>> bind_axis("Down", "Up", 0)
>>> to
>>> bind_axis("Up", "Down", 0)
>>>
>> That seems to put the display back in normal (not back tool) mode, but the X 
>> arrow keys are still backwards…
>> -Tom
>>
>

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Tom Easterday 
Check that, doing this doesn’t seem to have any effect that I can see.  The 
tools still appear as back tools but the arrow keys are still mapped 
incorrectly.
-Tom

> On Jun 27, 2015, at 6:32 PM, Tom Easterday  wrote:
> 
> 
>> On Jun 27, 2015, at 6:13 PM, Kirk Wallace  
>> wrote:
>> You might try changing
>> bind_axis("Down", "Up", 0)
>> to
>> bind_axis("Up", "Down", 0)
>> 
> 
> That seems to put the display back in normal (not back tool) mode, but the X 
> arrow keys are still backwards…
> -Tom
> 


--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Tom Easterday 
BTW, where did you find that “def bind_axis” thing?  I was trying to find what 
the code meant.  

I found a forum post where someone claims that you can change the key mapping 
(see below).  In following those instructions I added this to my .axisrc file 
but it didn’t help (I also tried changing the sign in front of get_jog_speed in 
case I had it on the wrong one but that didn’t work either...

root_window.bind(“", lambda e: jog_on(0, -get_jog_speed(30)))
root_window.bind(“", lambda e: jog_on(0, get_jog_speed(0)))
root_window.bind("", lambda e: jog_off(0))
root_window.bind("", lambda e: jog_off(0))

I got “Up" and “Down" by running the xev thing where I get a line that looks 
like:
state 0X10, keycode 111 (keysym 0xff52, Up), same_screen Yes,
and
state 0X10, keycode 116 (keysym 0xff54, Down), same_screen Yes,
when I hit the up and down arrow keys respectively

-Tom

===

"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("", commands.jog_minus)
root_window.bind("", commands.jog_plus)
root_window.bind("", commands.jog_stop)
root_window.bind("", commands.jog_stop)

# Bind ( and ) to jog axis 3 (0=X, 1=Y, 2=Z, 3=A, 4=B, ...)
root_window.bind("", lambda e: jog_on(3, -get_jog_speed(3)))
root_window.bind("", lambda e: jog_on(3, get_jog_speed(3)))
root_window.bind("", lambda e: jog_off(3))
root_window.bind("", 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”
===


--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Tom Easterday 

> On Jun 27, 2015, at 6:13 PM, Kirk Wallace  wrote:
> You might try changing
> bind_axis("Down", "Up", 0)
> to
> bind_axis("Up", "Down", 0)
> 

That seems to put the display back in normal (not back tool) mode, but the X 
arrow keys are still backwards…
-Tom


--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Kirk Wallace 
On 06/27/2015 02:49 PM, Tom Easterday wrote:
> I tried all combinations of STEP_SCALE, MIN_LIMIT, and MAX_LIMIT
> using
the .axisrc hack to display a back lathe. There is one config where
everything works EXCEPT that the up arrow moves the carriage down and
down arrow moves the carriage up - see "4) " below. So, I if I can
find the trick to remap the arrow keys I might have this working. I
don’t see the keys being messed with in the .axisrc code below. Does
anyone know what I would enter to reverse the meaning of the arrow keys
for just the X axis (up/down keys)? Or, barring that, is there some
other parameter that I have overlooked that will get me the behavior
shown here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe
 ?
>
>
> I have this in .axisrc:
> if lathe:
>   bind_axis("Down", "Up", 0)
>   def set_view_y(event=None):
>   widgets.view_z.configure(relief="link")

It looks like bind_axis() above does something with key bindings:
"...
> def bind_axis(a, b, d):
> root_window.bind("" % a, kp_wrap(lambda e: jog_on(d, 
> -get_jog_speed(d)), "KeyPress"))
> root_window.bind("" % b, kp_wrap(lambda e: jog_on(d, 
> get_jog_speed(d)), "KeyPress"))
> root_window.bind("" % a, lambda e: jog_on(d, 
> -get_max_jog_speed(d)))
> root_window.bind("" % b, lambda e: jog_on(d, 
> get_max_jog_speed(d)))
> root_window.bind("" % a, lambda e: jog_off(d))
> root_window.bind("" % b, lambda e: jog_off(d))
..."

You might try changing
bind_axis("Down", "Up", 0)
to
bind_axis("Up", "Down", 0)

-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-27 Thread Tom Easterday 
I tried all combinations of STEP_SCALE, MIN_LIMIT, and MAX_LIMIT using the 
.axisrc hack to display a back lathe.  There is one config where everything 
works EXCEPT that the up arrow moves the carriage down and down arrow moves the 
carriage up  - see "4) " below.  So, I if I can find the trick to remap the 
arrow keys I might have this working.  I don’t see the keys being messed with 
in the .axisrc code below.  Does anyone know what I would enter to reverse the 
meaning of the arrow keys for just the X axis (up/down keys)?  Or, barring 
that, is there some other parameter that I have overlooked that will get me the 
behavior shown here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe 
 ?


I have this in .axisrc:
if lathe:
 bind_axis("Down", "Up", 0)
 def set_view_y(event=None):
widgets.view_z.configure(relief="link")
widgets.view_z2.configure(relief="link")
widgets.view_x.configure(relief="link")
widgets.view_y.configure(relief="sunken")
widgets.view_p.configure(relief="link")
vars.view_type.set(4)
o.reset()
glRotatef(90, 1, 0, 0)
glRotatef(90, 0, 1, 0)
if o.canon:
mid = [(a+b)/2 for a, b in zip(o.canon.max_extents, 
o.canon.min_extents)]
glTranslatef(-mid[0], -mid[1], -mid[2])
size = [(a-b) for a, b in zip(o.canon.max_extents, 
o.canon.min_extents)]
o.set_eyepoint_from_extents(size[0], size[2])
else:
o.set_eyepoint(5.)
o.perspective = False
o.lat = -90
o.lon = 0
o.tkRedraw()
  
TclCommands.set_view_y = commands.set_view_y = set_view_y
root_window.bind("v", commands.set_view_y)
root_window.after_idle(commands.set_view_y)

---
If I have:  
   MIN_LIMIT= - 2.1
   MAX_LIMIT=0.001
Then,
If I change the sign of step_scale:

“+” causes: 
1) up arrow to move down, down arrow to move up  (bad)
2) motor down is more negative on dro, motor up is more positive (good)
3) turret moves from home position zero to -2.1 as it should (good)
4) * see note above

“-“ causes
1) up arrow moves up, down arrow moves down (good)
2) motor up is more negative, motor down is more positive (bad)
3) turret won’t move down, but will move up and hit hard stop (bad)
---
If I have:  
   MIN_LIMIT= 2.1
   MAX_LIMIT=0.001
Then,
If I change the sign of step_scale:

“+” causes: 
1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft limit”

“-“ causes
1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft limit”
---
If I have:  
   MIN_LIMIT= 0.001
   MAX_LIMIT= 2.1
Then,
If I change the sign of step_scale:

“+” causes: 
1) up arrow to move down, down arrow to move up  (bad)
2) motor down is more negative on dro, motor up is more positive (good)
3) turret won’t move down, but will move up and hit hard stop (bad)

“-“ causes
1) up arrow moves up, down arrow moves down (good)
2) motor up is more negative, motor down is more positive (bad)
3) turret moves from home position zero down to 2.1 as it should but 
wrong sign (bad)
---
If I have:  
   MIN_LIMIT= 0.001
   MAX_LIMIT=  - 2.1
Then,
If I change the sign of step_scale:

“+” causes: 
1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft limit”

“-“ causes
1) Up arrow causes error: “Can’t jog joint 0 further past min soft 
limit”, Down arrow causes error: “Can’t jog joint 0 further past max soft limit”
———

-Tom


———

> On Jun 26, 2015, at 11:53 PM, Tom Easterday  wrote:
> 
> 
>> On Jun 26, 2015, at 10:33 PM, Kirk Wallace  
>> wrote:
>> 
>> I think the up arrow and positive X motion values should move the cross 
>> slide in a positive direction. For back or rear tool lathes it is common 
>> for the positive direction to be away from the operator position (with 
>> the spindle to the left). You should be able to set up the motion part 
>> fairly easily using the sense (+/-) of the scale value.
> 
> Agreed, and I can set the scale such that +X is up.  Check.
> 
>> Once the hardware motion is set up, the plotter screen can be addressed 
>> and will need the .axisrc patch or some other software solution applied 
>> to Gremlin. I suspect if the .axisrc patch doesn't move the virtual tool 
>> up in a top view, there is something wrong with the patch installation 
>> or maybe it isn't compatible with newer versions of LinuxCNC.
>> 
>> The soft limits are based on the machine zero location which are set by 
>> homing. Since your home is to the upp

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-26 Thread Tom Easterday 

> On Jun 26, 2015, at 10:33 PM, Kirk Wallace  
> wrote:
> 
> I think the up arrow and positive X motion values should move the cross 
> slide in a positive direction. For back or rear tool lathes it is common 
> for the positive direction to be away from the operator position (with 
> the spindle to the left). You should be able to set up the motion part 
> fairly easily using the sense (+/-) of the scale value.

Agreed, and I can set the scale such that +X is up.  Check.

> Once the hardware motion is set up, the plotter screen can be addressed 
> and will need the .axisrc patch or some other software solution applied 
> to Gremlin. I suspect if the .axisrc patch doesn't move the virtual tool 
> up in a top view, there is something wrong with the patch installation 
> or maybe it isn't compatible with newer versions of LinuxCNC.
> 
> The soft limits are based on the machine zero location which are set by 
> homing. Since your home is to the upper right, your min soft limits 
> should have large negative values and small positive max values. The 
> Tormach slant bed lathe has:
> 
> [AXIS_0]
> ...
> MIN_LIMIT = -10.0
> MAX_LIMIT =   0.001
> ...
> 
> [AXIS_2]
> ...
> MIN_LIMIT = -12.0
> MAX_LIMIT =   0.001
> ...
> 
> http://www.tormach.com/uploads/images/content_images/15l_slantpro/Tormach_15L_SlantPro_Lathe.jpg
>  
> 

Check.  I had them this way (and will put them back), the piece I was missing 
is that I will need to either modify the .axisrc or other such hack to make 
sure everything coincides with this convention. I thought it was something I 
had configured wrong.  I may just be the .axisrc config and I will look at that 
tomorrow.   BTW, I had a chance to observe the Tormach lathe at the recent CNC 
Workshop.  It is a fairly nice machine and the work Tormach has done on the UI 
is very very nice.  I wish I could grab their lathe UI and use it!

> You can get these values by jogging an axis to just inside of a firm 
> limit and getting the axis position in G53 axis value in inch units. 
> Reading G53 isn't convenient, but zeroing all tool and workspace offsets 
> in G54 should do the trick. You can use MSG:
> http://linuxcnc.org/docs/html/gcode/overview.html#sec:messages
> 
> with numbered or name parameters:
> 
> http://linuxcnc.org/docs/html/gcode/overview.html#_numbered_parameters_a_id_sub_numbered_parameters_a
> 
> to check offsets and such.

Ok, I completely lost you on using MSG and named parameters to help in getting 
the values of G53.  Can’t I just read G53 off the preview window (I think that 
is what is shown in the upper left (Not in front of machine but something like 
Rad: X. and Z: X.).  I have been zero’ing G54 from the Machine menu 
because I think that is how I had screwed up my tool offsets a couple days ago. 
 How would I use MSG and named parameters to get that?

Many thanks for your help,
-Tom
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-26 Thread Kirk Wallace 
On 06/26/2015 04:20 PM, Tom Easterday wrote:
>
>> On Jun 26, 2015, at 6:28 PM, Kirk Wallace
>>  wrote:
>>
>> On 06/26/2015 03:01 PM, Tom Easterday wrote:
>>>
>>> I set up an .axisrc file to enable the back tool lathe function.
>>> I zero my machine in the upper left.

.snip

>> This should change your X axis motion but will have no effect on
>> the plotter screen.
>
> Yes, that is how I had it (and the arrow keys work that way), but
> then positive X is down which is opposite according to
> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe
> .  Also
> setting Min Limit and Max Limit seems to get confused (or I do)...
>
> -Tom

I think the up arrow and positive X motion values should move the cross 
slide in a positive direction. For back or rear tool lathes it is common 
for the positive direction to be away from the operator position (with 
the spindle to the left). You should be able to set up the motion part 
fairly easily using the sense (+/-) of the scale value.

Once the hardware motion is set up, the plotter screen can be addressed 
and will need the .axisrc patch or some other software solution applied 
to Gremlin. I suspect if the .axisrc patch doesn't move the virtual tool 
up in a top view, there is something wrong with the patch installation 
or maybe it isn't compatible with newer versions of LinuxCNC.

The soft limits are based on the machine zero location which are set by 
homing. Since your home is to the upper right, your min soft limits 
should have large negative values and small positive max values. The 
Tormach slant bed lathe has:

[AXIS_0]
...
MIN_LIMIT = -10.0
MAX_LIMIT =   0.001
...

[AXIS_2]
...
MIN_LIMIT = -12.0
MAX_LIMIT =   0.001
...

http://www.tormach.com/uploads/images/content_images/15l_slantpro/Tormach_15L_SlantPro_Lathe.jpg

You can get these values by jogging an axis to just inside of a firm 
limit and getting the axis position in G53 axis value in inch units. 
Reading G53 isn't convenient, but zeroing all tool and workspace offsets 
in G54 should do the trick. You can use MSG:
http://linuxcnc.org/docs/html/gcode/overview.html#sec:messages

with numbered or name parameters:

http://linuxcnc.org/docs/html/gcode/overview.html#_numbered_parameters_a_id_sub_numbered_parameters_a

to check offsets and such.


-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-26 Thread Tom Easterday 

> On Jun 26, 2015, at 6:28 PM, Kirk Wallace  wrote:
> 
> On 06/26/2015 03:01 PM, Tom Easterday wrote:
>> 
>> I set up an .axisrc file to enable the back tool lathe function. I
>> zero my machine in the upper left.
> 
> Do you mean machine zero is with the tool position in the upper right?

I move the turret all the way in Z to the right, and all the way up in X.  I 
find a hall sensor on each axis stepper and that is zero.

> 
>> -Z is to the left of that so my head moves from 0 to -6.9 (or so).  -X
>> is downward, so I can move from 0 to -2.1 (or so).  Even though I
>> have no positive values of X or Z, the positive X and Z directions
>> correspond to what is shown on the web page here:
>> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe
>>  ( +X up, and
>> +Z to the right).  But, while the left/right arrow keys move in Z as
>> they should, the Up/Down arrow keys move X in the opposite directions
>> as one would expect (up key moves down, down key moves up).
>> 
>> Do I need to remap keys or do I have some other parameter set
>> incorrectly? -Tom
> 
> Try editing your .ini file under [AXIS_0] STEP_SCALE = -10159.9997 and 
> change to STEP_SCALE = 10159.9997
> 
> This should change your X axis motion but will have no effect on the 
> plotter screen.

Yes, that is how I had it (and the arrow keys work that way), but then positive 
X is down which is opposite according to 
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe 
.  Also setting Min 
Limit and Max Limit seems to get confused (or I do)...

-Tom
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Re: [Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-26 Thread Kirk Wallace 
On 06/26/2015 03:01 PM, Tom Easterday wrote:
>
> I set up an .axisrc file to enable the back tool lathe function. I
> zero my machine in the upper left.

Do you mean machine zero is with the tool position in the upper right?

> -Z is to the left of that so my head moves from 0 to -6.9 (or so).  -X
> is downward, so I can move from 0 to -2.1 (or so).  Even though I
> have no positive values of X or Z, the positive X and Z directions
> correspond to what is shown on the web page here:
> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe
>  ( +X up, and
> +Z to the right).  But, while the left/right arrow keys move in Z as
> they should, the Up/Down arrow keys move X in the opposite directions
> as one would expect (up key moves down, down key moves up).
>
> Do I need to remap keys or do I have some other parameter set
> incorrectly? -Tom

Try editing your .ini file under [AXIS_0] STEP_SCALE = -10159.9997 and 
change to STEP_SCALE = 10159.9997

This should change your X axis motion but will have no effect on the 
plotter screen.


-- 
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

[Emc-users] Back tool lathe movement question (was lathe tool display bug in Axis preview on the developers list)

2015-06-26 Thread Tom Easterday 

I set up an .axisrc file to enable the back tool lathe function. I zero my 
machine in the upper left.  -Z is to the left of that so my head moves from 0 
to -6.9 (or so).  -X is downward, so I can move from 0 to -2.1 (or so).  Even 
though I have no positive values of X or Z, the positive X and Z directions 
correspond to what is shown on the web page here: 
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BackToolLathe 
 ( +X up, and +Z to the 
right).  But, while the left/right arrow keys move in Z as they should, the 
Up/Down arrow keys move X in the opposite directions as one would expect (up 
key moves down, down key moves up).  

Do I need to remap keys or do I have some other parameter set incorrectly?
-Tom

--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users