As long as I am reporting software issues, might as well do this one too:
If you have an SLX control and an indexer (though it probably also effects non-indexer lathes), be aware of a peculiar tool comp bug on this control. Drills are set up with the back edge and point as their reference X and Z and are comp'ed by their radius which must also be entered. This is different than how turning tools are entered. If you start a program with the indexer on a drill, ALL tools will be comp'ed that way during a position statement (not sure about actually turning). I.e. they will be one radius off. On the other hand, if you start the program with a non-drill indexed, a drill will be comp'ed as though it was a turning tool during a position, i.e., a position of a drill to X = 0 will result in the drill point being off by a radius. Positions (rapid moves) actually are not suppose to comp but they do in this sense.
I presume the same is true of a non indexer, if you start with a drill called out as the tool you would get the same result. Note that it only matters what is the current tool when you push Mode>Run.
For small radius turning tools you might not notice that it is off by the radius. The motion is correctly depicted in the tool path preview, and does what I say. Prototrak shrugged their shoulders and said they aren't maintaining the software in that control anymore, moved on to the ELX. No work around that I know of, except don't start the run with a drill as the current tool, and don't expect positions of drills to work as you might think.
If you have an SLX control and an indexer (though it probably also effects non-indexer lathes), be aware of a peculiar tool comp bug on this control. Drills are set up with the back edge and point as their reference X and Z and are comp'ed by their radius which must also be entered. This is different than how turning tools are entered. If you start a program with the indexer on a drill, ALL tools will be comp'ed that way during a position statement (not sure about actually turning). I.e. they will be one radius off. On the other hand, if you start the program with a non-drill indexed, a drill will be comp'ed as though it was a turning tool during a position, i.e., a position of a drill to X = 0 will result in the drill point being off by a radius. Positions (rapid moves) actually are not suppose to comp but they do in this sense.
I presume the same is true of a non indexer, if you start with a drill called out as the tool you would get the same result. Note that it only matters what is the current tool when you push Mode>Run.
For small radius turning tools you might not notice that it is off by the radius. The motion is correctly depicted in the tool path preview, and does what I say. Prototrak shrugged their shoulders and said they aren't maintaining the software in that control anymore, moved on to the ELX. No work around that I know of, except don't start the run with a drill as the current tool, and don't expect positions of drills to work as you might think.