I'll file a bug report, sure, if you think it's a bug... I usually assume operator error so I don't start with bug reports. :D
On Mon, Apr 7, 2014 at 3:29 PM, Michael Haberler <mai...@mah.priv.at> wrote: > > Am 07.04.2014 um 19:46 schrieb Rod Fitzsimmons Frey <rodf...@gmail.com>: > > > Thanks Michael. That fixed things, with no apparent ill effects on > > positioning, etc. > > hm, I would still like to understand the causality here. > > I am fairly sure it has to do with the way the interpreter deals with a > queuebuster (which is in effect a function continuation - exit and restart > a function at a later point where the code exited, pretty much like the > Python yield) > > obviously that doesnt play well with M73 which operates on the function > call stack; it could be the M73 kicks in when it should not yet > > for those using an M73 in a remap - until we know better (you guys all > file bug reports, do you ;-): > > - avoid it in a remap NGC procedure > - if you use codes which impact modal state, look into predefined > variables to save and restore them explicitly: http://goo.gl/eN8WGb > > > - Michael > > > > > On Mon, Apr 7, 2014 at 1:19 PM, Michael Haberler <mai...@mah.priv.at> > wrote: > > > >> > >> Am 07.04.2014 um 19:06 schrieb Rod Fitzsimmons Frey <rodf...@gmail.com > >: > >> > >>> Thanks Michael. Here's the relevant files > >>> > >>> https://gist.github.com/rodfrey/10024205 > >> > >> My gut feeling is - some odd interaction between the M73 and the fact > that > >> you do a queuebuster here > >> would you try and remove the M73 and see if the error reoccurs? not sure > >> if its needed at all > >> > >> > >> (hey, gists are a great way to share details of an error without running > >> into pastebin.* expiration! ) > >> > >> -m > >> > >>> > >>> It works well until I exceed 1200mm/min on any section of my program. > >>> > >>> > >>> On Mon, Apr 7, 2014 at 12:52 PM, Michael Haberler <mai...@mah.priv.at > >>> wrote: > >>> > >>>> > >>>> Am 07.04.2014 um 17:52 schrieb Rod Fitzsimmons Frey < > rodf...@gmail.com > >>> : > >>>> > >>>>> Hi! I'm having some issues with remapping M6 when I up my feed > rates. > >>>> My > >>>>> program works great at 750mm/min, but when I up it to 2000mm/min I > get > >>>> this > >>>>> error: > >>>>> > >>>>> M7x: restore_settings failed executing: ' F2000.0': Queue is not > empty > >>>>> after tool change > >>>>> > >>>>> It will happen a few hundred commands into the path with whatever > tool > >>>> I've > >>>>> set to the higher feed rate. > >>>>> > >>>>> Any pointers or hints? > >>>> > >>>> yes - first please post the context: configs and the exact command > being > >>>> executed > >>>> > >>>> (as a general guideline for reporting errors, see > >>>> > >> > https://github.com/mhaberler/asciidoc-sandbox/wiki/Reporting-an-error-with-Machinekit > >> ) > >>>> > >>>> background of the error (happened to me already, too!): > >>>> > >>>> the code violates an invariant, that is: for any 'queuebuster' type > >>>> operations, post that operation the task/interpeter/motion complex > waits > >>>> for all commands up to that operation have been completed; then goes > >> ahead > >>>> and synchronizes the interpreter with the actual state of the machine, > >> then > >>>> continues the program > >>>> > >>>> if you want to really know it all.. read this: > >>>> > >>>> > >>>> > >> > http://www.linuxcnc.org/docs/devel/html/remap/structure.html#_a_short_survey_of_linuxcnc_program_execution > >>>> > >>>> I recently wrote up a note which explains how the interpreter > interacts > >>>> with the rest of linuxcnc, this is a bit more detailed: > >>>> > >>>> > >>>> > >> > https://github.com/mhaberler/asciidoc-sandbox/wiki/Interpreter-control-flow-explained > >>>> > >>>> I cant conjecture where that comes from without seeing the config and > >> the > >>>> remap Python+NGC code though > >>>> > >>>> - Michael > >>>> > >>>> > >>>> > >>>>> > >>>> > >> > ------------------------------------------------------------------------------ > >>>>> Put Bad Developers to Shame > >>>>> Dominate Development with Jenkins Continuous Integration > >>>>> Continuously Automate Build, Test & Deployment > >>>>> Start a new project now. Try Jenkins in the cloud. > >>>>> http://p.sf.net/sfu/13600_Cloudbees_APR > >>>>> _______________________________________________ > >>>>> Emc-users mailing list > >>>>> Emc-users@lists.sourceforge.net > >>>>> https://lists.sourceforge.net/lists/listinfo/emc-users > >>>> > >>>> > >>>> > >>>> > >> > ------------------------------------------------------------------------------ > >>>> Put Bad Developers to Shame > >>>> Dominate Development with Jenkins Continuous Integration > >>>> Continuously Automate Build, Test & Deployment > >>>> Start a new project now. Try Jenkins in the cloud. > >>>> http://p.sf.net/sfu/13600_Cloudbees_APR > >>>> _______________________________________________ > >>>> Emc-users mailing list > >>>> Emc-users@lists.sourceforge.net > >>>> https://lists.sourceforge.net/lists/listinfo/emc-users > >>>> > >>> > >> > ------------------------------------------------------------------------------ > >>> Put Bad Developers to Shame > >>> Dominate Development with Jenkins Continuous Integration > >>> Continuously Automate Build, Test & Deployment > >>> Start a new project now. Try Jenkins in the cloud. > >>> http://p.sf.net/sfu/13600_Cloudbees > >>> _______________________________________________ > >>> Emc-users mailing list > >>> Emc-users@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/emc-users > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> Put Bad Developers to Shame > >> Dominate Development with Jenkins Continuous Integration > >> Continuously Automate Build, Test & Deployment > >> Start a new project now. Try Jenkins in the cloud. > >> http://p.sf.net/sfu/13600_Cloudbees > >> _______________________________________________ > >> Emc-users mailing list > >> Emc-users@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/emc-users > >> > > > ------------------------------------------------------------------------------ > > Put Bad Developers to Shame > > Dominate Development with Jenkins Continuous Integration > > Continuously Automate Build, Test & Deployment > > Start a new project now. Try Jenkins in the cloud. > > http://p.sf.net/sfu/13600_Cloudbees > > _______________________________________________ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
