I have attached an example file and the resulting posted code as well as the generic post that is loaded with X3.
I am experiencing a funny XY move when the B axis move crosses over from B- toward B+. When it hits B0 it makes a funny XY move that gouges the part.
I discovered that if I go to the "Swarf5ax" tab in the operation and change the "Step increment" value to anything other than the default .050 then the posted G code does not fall on B0 and I don't get the funny XY gouge move.
Seems to me that I am always taking a chance every time I post a job that the B move may fall on B0 and I would get a gouged part.
Is this a bug? Try reproducing this error with the sample part I have attached.