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 
> <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 <[email protected]> wrote:
>>
>>
>>> On Jun 26, 2015, at 10:33 PM, Kirk Wallace <[email protected]> 
>>> 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.0000001
>>> ...
>>>
>>> [AXIS_2]
>>> ...
>>> MIN_LIMIT =                     -12.0
>>> MAX_LIMIT =                       0.0000001
>>> ...
>>>
>>> http://www.tormach.com/uploads/images/content_images/15l_slantpro/Tormach_15L_SlantPro_Lathe.jpg
>>>  
>>> <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.XXXX and Z: X.XXXX).  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
>> [email protected]
>> 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
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to