On 01/13/2017 08:39 AM, Gene Heskett wrote:
> On Friday 13 January 2017 04:05:51 John Morris wrote:
>
>> On 01/07/2017 02:42 AM, John Morris wrote:
>>> I've been asked about some seemingly unintuitive behavior: the max
>>> velocity slider is not applied to rotary-only motion. You can try
>>> this yourself by running the `axis_9axis.ini` config, setting the
>>> max velocity slider to zero, and noting rotary axes still move after
>>> e.g. `g0 a180 f40`.
>>
>> So, I now have a proof-of-concept branch that plumbs a max angular
>> velocity from the UI to TP and back. Similar to max [linear]
>> velocity, it uses units (degree)/minute. In the Axis GUI, it's easy
>> to scale max angular velocity proportionally to (max
>> velocity)/([DISPLAY]MAX_LINEAR_VELOCITY) wrt
>> [DISPLAY]MAX_ANGULAR_VELOCITY. The plumbing involves adding extra
>> args or fields to existing functions, structs and NML messages related
>> to max velocity, so when one is set, the other is always set at the
>> same time.
>>
>> However, I'm leaning away from submitting the changes for mainline
>> inclusion. My heart isn't really in this one, and I'm not feeling the
>> passion for doing what it takes to ready it for GA (sincere thanks to
>> Norbert for offering to do the gmoccapy integration!), although I'm
>> happy to push it somewhere if anyone's curious. Thanks again for all
>> the replies.
>>
>> John
>>
> This one I can see a need for. I don't often have my table mounted and
> plugged in, but I have often, thru sloppy coding no doubt, had lcnc ask
> the table for a faster move than the motor can muster up because that
> cheap $100 when I bought it years ago table has so much backlash that
> I've tightened it up so that I need to apply an airhose to exert some
> internal lifting pressure by easing the holddowns friction, an air
> bearing of sorts. I made a hole into the side of the base casting, and a
> hole in the bearing face that intersected that hole, and a groove for
> that air all the way around the face of the base casting. Without that,
> perhaps a whole minute for a whole 360 turn. any faster and the motor
> will stall as its only a 220oz nema23. I've a 12 volt compressor I've
> always intended to rig so I could turn it on with gcode, wait a second
> for pressure, and turn it off when the move was done. But so far that
> itch hasn't been scratched. What I really need is a bigger table that
> doesn't mount the motor at an angle so its always hitting something.
>
> So this one I'll vote up by 1. Being able to limit it, and make the rest
> of the program wait on the slow table, would be helpful to me.
As long as your rotary axis has a correct e.g. `[AXIS_3]MAX_VELOCITY`
parameter set, mainline LCNC will do the right thing, and the linear
axes' velocity will be limited as appropriate by the rotary axis to
produce coordinated motion (the converse is also true). I actually
wrote a unit test in this branch that verifies this. So if I'm
understanding your concern, you're already covered, and don't need these
changes.
These changes apply only to those wishing to apply the max angular
velocity slider setting (whether combined with or separate from the
existing max velocity slider) to pure rotary motion. Many folks needing
needing to limit pure rotary motion can still use feedrate (in
degrees/minute) for pure rotary G01 A/B/C moves, and there's a separate
angular jog speed slider in Axis that appears when a rotary axis is
configured.
John
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
