Seb, I agree with that. I think FO is a bit of an evil thing. The program should be corrected if the feed is not perfect although that is not practical if the program only runs once. I use gmoccapy mostly and I hide the FO functions normally. Jog speeds are jog speeds and they are not feed speeds.
On 2014-11-14 07:10, Sebastian Kuzminsky wrote: > On 11/13/2014 09:40 PM, Dewey Garrett wrote: >> inifile: support jog_ignore_feed_override >> >> with inifile setting: >> [TRAJ]JOG_IGNORE_FEED_OVERRIDE >> and provide hal input pin: >> ini.traj_jog_ignore_feed_override >> >> Signed-off-by: Dewey Garrett <dgarr...@panix.com> >> >> >> http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2b5c9ce > I like the idea of making jogs immune to Feed Override, but why go > through Task to do it? Why not have motion export the > jog_ignore_feed_override pin directly? > > ... Or, maybe jogs should *always*, unconditionally, be immune to FO, > and just use the commanded jog speed. Jogging isn't a feed (and it > isn't a rapid), so it's not at all clear to me that FO (or RO) should be > applied, ever. > > -- Regards /Groete Marius D. Liebenberg +27 82 698 3251 +27 12 743 6064 QQ 1767394877 ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
