On 16/4/17 3:23 pm, Gene Heskett wrote:
> On Saturday 15 April 2017 19:35:57 Gene Heskett wrote:
>
>> On Saturday 15 April 2017 19:17:23 Gene Heskett wrote:
>>> On Saturday 15 April 2017 06:29:22 Phillip Carter wrote:
>>>> I have just noticed in sim/axis/gantry that joint 3 does not jog
>>>> with the leftbracket/rightbracket keyboard keys but does with the
>>>> minus/equals keyboard keys. Is this the correct behaviour?
>>> I also, for lack of anything better to do, rigged up my chop saw and
>>> sawed off a couple hunks on 1.5" thick alu to make a new set of
>>> bearing pushers to fit the larger OD of the correct bearing. Fired
>>> up linuxcnc -l, (this after an early morning update of
>>> LinuxCNC-2.8-pre to LINUXCNC - 2.8.0-pre1-2988-ge9f9469) x and z are
>>> still swapped at the keyboard yet before being homed. Hit ctl+home,
>>> and it homed to the correct places, and in the correct directions
>>> and homeing order. Tapped the uparrow, then downarrow, and z moves
>>> left-right. Tapped the left and right arrows, and x moves in and
>>> out. Switch to MDI, and its now scrambled as well, as in G0X moves
>>> Z and G0Z moves X. So it appears Phillips commit made the keyboard
>>> scramble apply to MDI too, which means it cannot run code I ran on
>>> it just 2 days ago.
>>>
>>> Help! I do not have another functioning lathe now.
>>>
>>> Can you back out Phillips commit and retrigger the buildbot? It at
>>> least ran correctly after being homed, and I could use it, once it
>>> had been homed.
>>>
>>> Thanks guys.
>>>
>>> Cheers, Gene Heskett
>> Touring what could have been hell, I just installed that version on
>> both of my mills, and things appear to be working as expected on all 7
>> axis's they have. So this seems to be a lathe only problem. That
>> should help narrow the search.
>>
>> Cheers, Gene Heskett
> Poking and prodding with the lathe, I turned on debugging to 0x7fffffff
> and ran it, and I note in the terminal a couple things that look odd,
> but I don't have a working lathe to compare it to, so I'll paste them
> here.
>
> task: machine: 'The Little Monster' version 'unknown'
> emcTaskOnce: Python plugin configured
> emcTaskOnce: extract(task_instance): KeyError: ('task',)
>
> emcTaskOnce: no Python Task() instance available, using default
> iocontrol-based task methods
> emcTrajSetJoints(2) returned 0
> emcTrajSetAxes(3, 5)
>
> The config does have a LATHE=1 in the display section.
>
> And only XZ are specified anyplace.
> gene@lathe:~/linuxcnc/configs/my_LinuxCNC_machine2$ grep -i xz
> my_LinuxCNC_machine2.ini
> GEOMETRY = XZ
> JOG_AXES = XZ
> COORDINATES = XZ
> KINEMATICS = trivkins coordinates=XZ
>
> What does the above tell us? Line by line please.
>
> Thanks all.
>
> Cheers, Gene Heskett
For a lathe JOG_AXES=ZX would be best and is the default if not specified.
See extract from
http://linuxcnc.org/docs/devel/html/config/ini-config.html#_display_section
*
/JOG_AXES =/- The order in which jog keys are assigned to axis
letters. The left and right arrows are assigned to the first axis
letter, up and down to the second, page up/page down to the third,
and left and right bracket to the fourth. If unspecified, the
default is determined from the [TRAJ]COORDINATES, [DISPLAY]LATHE and
[DISPLAY]FOAM values.
--
Cheers, Phill
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
