Hi Andy, I did a lot of testing yesterday and it looks as if axis is failing.
When I developed my app I tested it together with axis and I'm sure, everything I tested was in sync with axis. So when I started with G43.1 tests and had a different output than axis, I thought, I found a bug in my app. But after investigation I was sure, my app did nothing but showing values from nml. On Montag, 13. April 2020, 16:55:17 CEST andy pugh wrote: > On Mon, 13 Apr 2020 at 05:26, Reinhard <[email protected]> wrote: > > Behaviour may be ok from sight of motion, but it is not from user sight > > (with me being the user ;) ). > > Are you able to do a git bisect to find exactly where the behaviour changed? When I saved screenshots of my app it was beginning of november last year. That time I was able to read tooltable from nml and I remember, that backend provided the tool properties, but not the comment field. So I wrote a filereader for the tooltable too, as I consider the comment a very important property. But as there could be differences between tooltable file and tooltable, I disabled filereader and stayed with tooltable provided from backend. I remember, that I tested lots of tooltable files provided by linuxcnc to test imperial values as well as metric ones. So may be, that the increasing of the tooltable did not change any behaviour, but some changes before may caused changes. Don't know, when the tooltable became useless. Having 1001 entries with no values sounds more than ridiculous. Back to the G43.1 tests - as I wrote, I got confused by the toollength and the G0Z30 - as axis shows the toollength stil as 30 and my app showed only 0.5 as tool-length. In my mind, G43.1 should be an addon to actual tool length (as I got the recommendation to that command as counterpart to Heidenhains TL). So I saw different values for toollength in axis and my app. Second toolchange without G43.1 showed the right toollength in my app again, so I was even more confused. Yesterday evening I found a globbered tool table file - and thought: whow, backend changes even worse than expected. But the globbering did not came from backend, but from axis, where I issued a save and reload to see, whether backend will change tooltable values. So at least two misbehaviours of axis found. Therefor I should not rely any more on axis. But is the only gui that runs on buster without troubles. Reinhard _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
