Thanks for looking Andy..im working long hours so have got far. I have done some code work on this and can get tool init to be called but not io_init and tool_ init I still dont quite understand how messages are queued.
Iocontrol v2 handles error conditions on the hardware side.allows linuxcnc to be aware of them. Its work from Michael H.... so was not integrated completely. We can make it standard by changing all sample configs. I would wait till after 2.8 is made. My 2 cents. -------- Original message -------- From: andy pugh <[email protected]> Date: 2019-04-28 10:46 a.m. (GMT-07:00) To: EMC developers <[email protected]> Subject: Re: [Emc-developers] iocontrol.cc never runs EMC_TOOL_INIT message On Thu, 18 Apr 2019 at 04:34, Chris Morley <[email protected]> wrote: > > While I was toying with a tool startup problem from the forum, I discovered > that iocontrol.cc never runs > the EMC_TOOL_INIT NML message even though taskclass.cc sends it. This has been sat in the bottom of my inbox waiting for me to got round to looking at it. (And I still haven't, in any detail) > So when iocontrol is first run the serial number is 0 and the echo is > immediately advanced to 1 when updating the HAL pins. > When the EMC_TOOL_INIT message comes it has a serial number of 1 and echo > already has a number of 1. > So the EMC_TOOL_INIT is never run but the serial/echo number synchs and > everything works from there. I see the same code in iocontrolV2. (What is "better" about iocontrolv2 and why isn't it the default?) -- 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
