We have CSS on and are threading with a G33 on our Emco lathe and we are seeing the spindle decelerating during the cut. Seems like the spindle speed should be fairly steady at a given X location during a G33 and what it seems like is that the spindle is still decelerating to speed while it’s in the cut rather than before the cut.
We are rapid-ing (G0 in Z) out of the part at the center of the part (X=0) and so CSS spins the spindle up to full speed as I’d expect (*) but it appears that our spindle is still decelerating to speed as the next threading pass is happening. We read that G33 will wait for spindle-at-speed before looking for the index pulse. But our spindle-at-speed signal seems to be high during the full cycle once the spindle speeds up the first time. It seems like spindle-at-speed should go low after rapiding out of the part as it moves to it’s next X location and decelerates to it’s next speed at the cutting diameter. Or are we misunderstanding spindle-at-speed when CSS is in effect? (*) Is it normal that a G0 move also triggers CSS to spin up (or down)? Seems like the trajectory planner would know where the next cutting move is and not adjust the spindle speed until it needs to. In our case we are rapiding out of the part at X=0 and the spindle speeds up when it doesn’t really need to. -Tom ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
