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

2017-01-23 Thread Gene Heskett
On Monday 23 January 2017 13:10:00 John Kasunich wrote: > On Mon, Jan 23, 2017, at 12:29 PM, Gene Heskett wrote: > > The catch-22. :) In your case & similar fixed speed no encoder > > situations John, could you do an s number in your gcode 10% faster > > than the nameplate speed for that belt posi

[Emc-developers] Torch Height Control

2017-01-23 Thread John Thornton
I'm looking for ideas for the thc comp. If the gain is set high enough to react to say corrugated stock you get oscillation (overshoot). There are some pretty smart folks on this mailing list, if I can get some hints I'll run with it. The current version in LinuxCNC is: // convert encoder

Re: [Emc-developers] import emccanon

2017-01-23 Thread andy pugh
On 23 January 2017 at 21:35, Sebastian Kuzminsky wrote: > I think the Python module called emccanon is built into the C library > called librs274 (from src/emc/rs274ngc/canonmodule.cc). I think > therefore emccanon is only accessible to Python code running in a Python > interpreter linked with th

Re: [Emc-developers] import emccanon

2017-01-23 Thread Sebastian Kuzminsky
On 01/23/2017 12:42 PM, andy pugh wrote: > What is the requirement to be able to import emccanon? > It seems to work in remap code, and in the tests (for example > https://github.com/LinuxCNC/linuxcnc/blob/af15a4d90e1d51d5309db65fe1c9511e486df411/tests/remap/fail/canon_error/remap.py > ) > But if I

[Emc-developers] import emccanon

2017-01-23 Thread andy pugh
What is the requirement to be able to import emccanon? It seems to work in remap code, and in the tests (for example https://github.com/LinuxCNC/linuxcnc/blob/af15a4d90e1d51d5309db65fe1c9511e486df411/tests/remap/fail/canon_error/remap.py ) But if I try "import emccanon" in a GladeVCP handler, it ex

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

2017-01-23 Thread John Thornton
For spindles that don't have control all you need is M3/4 S1. JT On 1/23/2017 11:18 AM, Robert Ellenberg wrote: > John, you raise a good point here. The general assumption is that the S > word is a reasonable prediction of spindle speed. What do you think of > having a check at both interp time

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

2017-01-23 Thread John Kasunich
On Mon, Jan 23, 2017, at 12:29 PM, Gene Heskett wrote: > > The catch-22. :) In your case & similar fixed speed no encoder situations > John, could you do an s number in your gcode 10% faster than the > nameplate speed for that belt position? I have an encoder. An encoder (at least a single

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

2017-01-23 Thread John Kasunich
On Mon, Jan 23, 2017, at 12:18 PM, Robert Ellenberg wrote: > John, you raise a good point here. The general assumption is that the S > word is a reasonable prediction of spindle speed. What do you think of > having a check at both interp time and runtime? I kinda think you're going to want that

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

2017-01-23 Thread Gene Heskett
On Monday 23 January 2017 10:43:21 John Kasunich wrote: > On Sat, Jan 21, 2017, at 04:28 AM, John Morris wrote: > > I also thought of these three possible intended scenarios pointed > > out in this thread, and can think of valid arguments for each, > > briefly: > > > > 1. The manual says it's an e

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

2017-01-23 Thread Robert Ellenberg
John, you raise a good point here. The general assumption is that the S word is a reasonable prediction of spindle speed. What do you think of having a check at both interp time and runtime? That would cover all cases. For machines like yours, we could suppress the interp-time error. Is there an IN

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

2017-01-23 Thread John Kasunich
On Sat, Jan 21, 2017, at 04:28 AM, John Morris wrote: > I also thought of these three possible intended scenarios pointed out in > this thread, and can think of valid arguments for each, briefly: > > 1. The manual says it's an error, and it's up to the user to avoid it > (status quo) > 2. Th