I just setup the rigidtap.ngc similar to what disclosed the bug in 2.5.3, where the z axis would stop at the sw limit as it plunged the g33.1 motion, while the spindle continued on, either breaking the tap, or pulling it out of the chuck and then jamming it back in.
With the 2.6.0-sim from version last night, it now detects the over travel and will not execute it at all. Not exactly what I wanted as that will make me rechuck the work to gain clearance. But its a heck of a lot better than letting it run, and wrecking the workpiece or breaking the tap. Thank you very much, whoever fixed that. Now, I've added the "net spindle-reverse motion.spindle-reverse" which gets me the start buttons for both dirs, and reduced the divisor in the spindle-mass calculation which should make it more nearly match what I have as its the biggest 4 jaw chuck a 7x12 can mount. Now I need to figure where I put an abs module in the signal path to the rpm display. Clue? loadrt'd and addf'd but where does the pair of net statements fit? Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
