Igor Chudov wrote: > Here's something strange. It is not really a big problem for me, as I can > find workarounds, but someone may find it interesting. > > I messed with rigid tapping today (see videos). In real steel, at 500 RPM, > worked like a charm. > > Then I experimented some more "in the air", varying the RPM. > > Everything works great at 500 and even up to 1000 RPM. However, if I > increase my speed to 1,500 RPM, my program bombs out with "following error" > and stops. > You need to run Halscope and catch it in the act. I am pretty sure, however, you are getting a Z-axis (Joint 2) following error, due to the slam-reversal. Your spindle can probably reverse faster than the Z axis can keep up with. I had the same problem, and added a filter to slow down the speed change. It seems to help greatly. See (again) the config file set for me Bridgeport. > That, alone, is not really a problem, this just means that I run into limits > of my encoder or PPMC or EMC2. Fine with me. > > What is interesting is that after this, EMC2 becomes somewhat screwed up. > > First, it gives following errors even at RPM reduced back to 500 RPM. > > Second, it becomes generally messed up, and hitting the "reload code" button > leads to erratic behavior, the run/pause/stop buttons are greyed out, etc. > > I need to restart EMC2 to clear that. > > It is very easily reproducible for me and requires no material. It is like > some bit is not properly cleared, or something. > OK, this is DIFFERENT behavior than I have experienced. I can think of a couple possible explanations. One is that due to the interrupted cycle, the G33.1 has not quite completed and reset all it's flags. I am not using the latest EMC version, so it is possible there is some recent change that causes this. I certainly did have similar following errors and E-stops from my VFD thinking the motor was overheating, but never saw this sort of problem.
Another possibility is that something is messing up the normal operating state of the PPMC boards, but this sounds more like it is in EMC2, or maybe in Axis, if a file reload doesn't even work. If you didn't do an E-stop when it got in this state, you might try that and see if it clears the condition. Jon ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
