i would suggest, if you wish to parse the Var file, that you still use a HAL pin. I would have a HAl pin from the Var file (or however else) that can be connected to IOcontrol. i agree that putting the parsing in IOcontrol makes sense.
In this way if you leave the pin unconnected - it works like now. If you connect it to the parsed pin, then you get the most common way to for linuxcnc to remember the tool. but also someone could connect the pin to something else - such as a toolchange in a lathe - it has 'mechanical' memory. I would not bother with 2.8 - this bug has been around a long timem but is stable. Hopefully 2.9 gets a lot of tool manipulation updates. Chris M ________________________________ From: andy pugh <[email protected]> Sent: June 10, 2019 10:45 AM To: EMC developers Subject: Re: [Emc-developers] iocontrol.cc never runs EMC_TOOL_INIT message On Mon, 20 May 2019 at 20:01, Chris Morley <[email protected]> wrote: > > If the toolnumber is saved to a var file then one could write code to read > the file and set a HAL pin that is connected to iocontrol I still want to look at doing this via the vars file (or, possibly, as an INI entry that automatically adds to the vars file). And I think it all belongs in the EMC_TOOL_INIT, so we need to make that work too :-) I half feel that TOOL_INIT not running is a 2.8 bug, but then iocontrol contains a workaround (or two) which complicates that decision. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
