from my Heidenhain experience every cell in the tool table is mapped to system variables which are loaded when the tool table is loaded
because of this i could write a row of cells in the tool table and use them for whatever i wanted example cell 1= tool pod, cell 2 = tool diamets, cell 3 = favorite color, cell 3 = flow meter set point for whatever i wanted simple, & flexible regards Tomp tjtr33 On 11/26/2014 01:57 PM, Sebastian Kuzminsky wrote: > On 11/26/2014 11:58 AM, andy pugh wrote: >> On 26 November 2014 at 18:00, Eric H. Johnson <ejohn...@camalytics.com> >> wrote: >> >>> I need to set a couple outputs based on which tool is selected. I only have >>> 3 tools. I expect others have run into this issue. So far the easiest way I >>> see is to convert iocontrol.0.tool-number into a float and then use >>> comparators on that value to set the states of my outputs. >> > ... >> >> This seems like a case where an extra field in the tool database would >> be rather handy. > > How would this extra field in the tool db be exposed in HAL? Wouldn't > that require changes to IO? > > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
