Greetings all; Back to reinventing a new wheel here.
I have added 10 new variables to the variables.txt file, and dedicated 6 of them already. But I see a problem from one aspect, I need to zero two of then when lCNC is started, so that if I run the blanket-chest-3.ngc code without first setting this #var to non-zero, it will squawk and exit. Similarly, the calibration routine should squawk and exit if it finds a zero in #var, make me consciously hit F5, and from the MDI command line, enter a #4993=1.0 or 2.0 depending on which tool is mounted. And because the vars needs set in sequence, the calibration routine needs to check to see it the first tools routine has been run by checking #4995 for non-zero, bitching and exiting, forcing me to mount the 1/4" mill and do the first setup since the code needs those #vars non-zero too. So, in this string in the .ini file: RS274NGC_STARTUP_CODE= yadda yadda Is it possible to do something like '#4990=0.0' etc so that this stuff is forced to zero at linuxcnc startup, forcing me to run this calibration code first? And does it need quoting as above to contain the argument? Trying to paint myself back out of a corner here. ;-) Or, would it be simpler to remove those #vars from linuxcnc.vars so they are not saved between sessions? Setting them by MDI command line would allow the code to load as opposed to exiting because they have not been created. Several additional ways to skin this cat I think. Thoughts please. Thank you. 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> ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
