Hi Gene, It's been a long time since I've looked at the code, and I don't have it in front of me.
But... 1. The file is named _clear_offset.ngc -- isn't it (you didn't leave out the .ngc)? 2. As I recall, the file is opened the first time it is referenced (and memory mapped). After that, the copy in memory is used. That means if you changed the file to make a correction, it won't be noticed until the next time linuxcnc is restarted. Just some possibilities. Good luck (and happy holidays). Ken On Tue, Dec 12, 2017 at 5:33 PM, Gene Heskett <[email protected]> wrote: > On Tuesday 12 December 2017 12:01:57 Gene Heskett wrote: > > > Greetings all; > > Not getting anywhere, I have even straced linuxcnc, but the error is > exactly the same, mixed into the strace output. > > Is there a special bit in the DEBUG value that will enable tracing the > steps it takes to execute a HALUI=halui, MDI_COMMAND=o<name-of-file> ? > > TASK seems to be the one, but isn't enough noisier to help me. > Here is what it logs for one of the 5th thru 8th MDI_COMMANDS > > Issuing EMC_TASK_PLAN_EXECUTE -- ( +509,+268, > +18,o<_align_start>\032call,) > emc/task/emctask.cc 397: interp_error: EOF in > file:/usr/share/axis/images/axis.ngc seeking o-word: o<_align_start> > from line: 0 > EOF in file:/usr/share/axis/images/axis.ngc seeking o-word: > o<_align_start> from line: 0 > emc/task/emctaskmain.cc 2336: error executing command > 509:EMC_TASK_PLAN_EXECUTE > emcTaskIssueCommand() returning: -1 > > So I added the INTERP flag, and then get this: > > emcTaskPlanSynch() returned 0 > Issuing EMC_TASK_PLAN_EXECUTE -- ( +509,+268, > +18,o<_align_start>\032call,) > emcTaskPlanLevel() returned 0 > emc/task/emctask.cc 397: interp_error: EOF in > file:/usr/share/axis/images/axis.ngc seeking o-word: o<_align_start> > from line: 0 > EOF in file:/usr/share/axis/images/axis.ngc seeking o-word: > o<_align_start> from line: 0 > Interpreter stack: - int Interp::read_text(const char*, FILE*, > char*, char*, int*) - int Interp::_read(const char*) - int > Interp::_execute(const char*) > emcTaskPlanExecute(o<_align_start> call) returned 5 > emcTaskPlanLevel() returned 0 > emc/task/emctaskmain.cc 2336: error executing command > 509:EMC_TASK_PLAN_EXECUTE > emcTaskIssueCommand() returning: -1 > emcTaskPlanLevel() returned 0 > > So what is an error 5? > > Another file in the git pull on the rock64 says thats an INTERP_ERROR. > > So I am beginning to think this is not my error. However, I moved one of > them to the top of the list without effecting the text of the error. So > it must be a syntax error in postgui.hal, or the file itself. So here is > the shortest of one of these 4 files that cannot be run. > ========= > o<_clear_offset> sub > ; this subroutine is used to clear the offsets after using align > G10 L2 P0 R0 > G92.1 > ; turn all tallys off > m65p8 > m65p9 > m65p10 > (msg,alignment offsets cleared) > o<_clear_offset> endsub > M2 > =========== > > And I might have found it, I had renamed the file slightly, on all 4 of > them, without changing the internal names. Duh... Goes off to check it > out. Fixed the internal names to match file names. No diff in the error > messages. Next, take leading underscores out of all names, ok since I've > moved them all to a subdir, first in path. But the 1st 4 were treated > exactly the same, with _leading underscores, and they work just > fine. > > > > . > So I'll invert the order in postgui.hal one more time for effect. Done, > no diff, it's simply making no effort to execute MDI_COMMANDS 5-8. But > moving on of them to first in list does not make it work either. > > Its been a while since I found a bug, have I again? At any rate its time > I go play chief cook and bottle washer while you folks cogitate on how > to tell me I'm an idiot. :) > > > On the 5th command in the list, and all subsequent commands after the > > first 4, I am not getting the expected result, which is running the > > command, but instead is logging this in the launching terminal: > > > > emc/task/emctask.cc 397: interp_error: EOF in > > file:/usr/share/axis/images/axis.ngc seeking o-word: o<_align_start> > > from line: 0 > > EOF in file:/usr/share/axis/images/axis.ngc seeking o-word: > > o<_align_start> from line: 0 > > > > The file, just like the first 4, exists in the first listed link in > > the SUBROUTINE_PATH statement in the .ini file. > > > > 4 command limit? Doesn't say anything in the docs but up to 64. > > > > Call me puzzled? > > > > Cheers, Gene Heskett > > > Cheers, Gene Heskett > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > Genes Web page <http://geneslinuxbox.net:6309/gene> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Emc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-users > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
