Re: [Emc-developers] Question about changes to homing and soft-limits

2017-01-20 Thread andy pugh
On 20 January 2017 at 22:34, Roland von Kurnatowski III wrote: > My thought for a hack would be to simple be able to change the values of > pins holding the min_x, max_x etc of the axis. I saw there where > ini.0.max_limit but this value doesnt seem to have any effect when

[Emc-developers] Question about changes to homing and soft-limits

2017-01-20 Thread Roland von Kurnatowski III
I have been proceeding with a number of retrofits I have come up with a couple of issues with a Brother T-217 Firstly the tool change process is handled entirely by moving the z axis there are a number of cams at the top end of travel that grasp the tool, release the drawbar etc. Moving into this

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread Gene Heskett
On Friday 20 January 2017 11:17:30 Jon Elson wrote: > On 01/20/2017 07:01 AM, Robert Ellenberg wrote: > > I think it's a bug (or at least an oversight), see this issue: > > > > https://github.com/LinuxCNC/linuxcnc/issues/167 > > > > I have an experimental fix: > > > >

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread Gene Heskett
On Friday 20 January 2017 10:01:46 andy pugh wrote: > On 20 January 2017 at 14:19, John Kasunich wrote: > > I think it is a terminology thing. Where the manual says "it is an > > error", read it to mean "if you do this, you made an error and all > > bets are off",

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread Gene Heskett
On Friday 20 January 2017 07:46:59 John Morris wrote: > The manual for G33 spindle synchronized motion [1] reads, "It is an > error if [...] The requested linear motion exceeds machine velocity > limits due to the spindle speed." > > It seems that doing that actually doesn't cause an error, as >

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread Jon Elson
On 01/20/2017 07:01 AM, Robert Ellenberg wrote: > I think it's a bug (or at least an oversight), see this issue: > > https://github.com/LinuxCNC/linuxcnc/issues/167 > > I have an experimental fix: > > https://github.com/robEllenberg/linuxcnc-mirror/tree/feature/spindle-sync-overhaul-2.7 > > It

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread andy pugh
On 20 January 2017 at 14:19, John Kasunich wrote: > I think it is a terminology thing. Where the manual says "it is an error", > read it to mean "if you do this, you made an error and all bets are off", > rather than "if you do this, LCNC will detect and report it".

Re: [Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread Robert Ellenberg
That's true, though I think we should warn users of errors we can detect as early as possible, so they don't have to destroy a part to learn the significance of a line in the documentation. On Fri, Jan 20, 2017, 9:22 AM John Kasunich wrote: > > > On Fri, Jan 20, 2017, at

[Emc-developers] G33 linear motion limits exceeded error

2017-01-20 Thread John Morris
The manual for G33 spindle synchronized motion [1] reads, "It is an error if [...] The requested linear motion exceeds machine velocity limits due to the spindle speed." It seems that doing that actually doesn't cause an error, as demonstrated by the regression test in the top commit here [2].