The first one is a bug.  The axis should operate correctly when going to 
the tool change position.  Locking rotaries require a lock/unlock loop 
which doesn't happen during a tool_change_at_30 configuration.

the second is something that isn't possible at the moment (that I know 
of) other than the oword work you have done (I have to play with that - 
and your i/ov2) great work!  It would be nice to be able to enable which 
axis have to move for a tool change.  for  me - really z and y need to 
move.  but with g30 all have to.  that is why I picked g30 as I can 
change it with gcode.  Thinking out loud - maybe something similar to 
homing sequence.   then you could also say - z moves first - then xy can 
move together and so on.   Then it could be done with one mechanism 
instead of multiple ini settings.

hope this made sense... ;)

sam

On 03/20/2011 03:24 AM, Michael Haberler wrote:
> skunkworks - let me understand this fully - do you want either:
>
> a) on any toolchange entry move (TOOLCHANGE_POSITION, TOOL_CHANGE_AT_G30) 
> have moves for indexer axes bracketed with unlock/lock operations (first 
> paragraph)
> b) have something like an axis mask which limits movements during toolchange 
> positioning to axes explicitly enabled in this mask? ('it would be cool..')
>
> these are quite different things - b) really doesnt make much sense without a)
>
> I would assume that the mask from b) would be limited only to the 'entry 
> moves' during m6
>
> ---
> note that all you want can be already done with the 
> toolchange-in-gcode-by-oword subs because you're not limited by the fixed 
> sequencing and options which are executed in a normal M6, and the normal Gx 
> moves seem to work fine with a locking indexer
>
> I know the documentation isnt there yet - I swear I have the toolchanger.txt 
> file open in the other window ;-)
>
> -m
>
>
> Am 19.03.2011 um 20:14 schrieb SourceForge.net:
>
>> Bugs item #3226864, was opened at 2011-03-19 14:14
>> Message generated for change (Settings changed) made by skunkwork
>> You can respond by visiting:
>> https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3226864&group_id=6744
>>
>> Please note that this message will contain a full copy of the comment thread,
>> including the initial issue submission, for this request,
>> not just the latest update.
>> Category: Motion Controller
>> Group: None
>> Status: Open
>> Resolution: None
>> Priority: 5
>> Private: No
>> Submitted By: skunkwork (skunkwork)
>>> Assigned to: Chris Radek (cradek)
>> Summary: Tool_change_at_g30 doesn't unlock rotory axis
>>
>> Initial Comment:
>> commanding a tool change when Tool_change_at_g30=1 and Locking_indexer=1 in 
>> the ini - the rotory axis doesn't unlock but still tries to move the the g30 
>> rotary axis position. This causes a following error as the axis is locked.  
>> Commanding a G30 normally acts correctly - rotary axis unlocks - rotates 
>> then locks - then subsequent axis motion is done.
>>
>> It would be cool if there was a mechanism to set which axis will move 
>> instead of all moving.
>>
>> thanks
>> sam
>>
>> ----------------------------------------------------------------------
>>
>> You can respond by visiting:
>> https://sourceforge.net/tracker/?func=detail&atid=106744&aid=3226864&group_id=6744
>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>> _______________________________________________
>> Emc-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Emc-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to