WOW, Dewey added tool table database to ioControl_V2.cc
https://github.com/LinuxCNC/linuxcnc/commit/2dbb2f640fb87e7fe40c6d83cee381f8643233be#diff-6ae0a0db16051707fa75a5b511194a81291d1f59df7b291cab793c15bf180ca0 This commit refactors internal tool data handling to: 1) Update and consolidate functions in a new directory: src/emc/tooldata 2) Define an applications interface: src/emc/tooldata/tooldata.hh 3) Support a new interface to a user-provided tool database management program specified by [EMCIO]DB_PROGRAM 4) Use a new mmapped tooldata interface between EMCIO and TASK while maintaining number of allowed pockets specified by CANON_POCKETS_MAX=1001 5) Deprecate tooldata in nml messages between EMCIO and TASK (legacy nml message method remains available using configure --enable-toolnml until removal) 6) Minimize impact to current users of master branch and continue to pass the suite of runtests on all supported buildbot machines. 7) Clarify program variable names that use a sequential index (idx) for accessing internal tooldata. Note: some legacy variable names like: pocketPrepped, selected_pocket,current_pocket are still used in a few places because of their inclusion in fielded user remap scripts or the tests suite. These items may be renamed in the future. Looks like ioControl_V2.cc was added in 2011 so it's been here since 2.6? On 4/1/21 5:24 AM, andy pugh wrote:
We have had iocintrol_v2 available for a long time, but the documentation does not dscribe the difference very well. There is documentation, on the Wiki: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ToolchangerProtocolProposal Which I have just been prompted to look through by a forum post. It does seem to be better. I am thinking that perhaps we should move the docs from the Wiki into the docs, and that the setup wizards and sample configs should be set up to use it. Thoughts?
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
