Jon Elson wrote: > Chris Radek wrote: > >> What is your spindle encoder hooked to? Jon E and I saw this behavior >> on some PPMC boards but it is long fixed as far as I know. >> >> >> > I'm sure this is fixed for forward spindle rotation, assuming up to date > hardware, as of CNC Workshop 2007. > I think he has this. But, what about reverse spindle rotation? I'm not > completely sure about that. The code LOOKS right, but I sure have NOT > tested it that way! > > I could try it out tomorrow, though. > OK, I tried it on my mini mill, and had a couple problems. I tried a G-code file derived from the threading.ngc sample file, that just has slight changes to the thread pitch, I think. It worked mostly OK with the spindle running forward, but just hung when the spindle was running in reverse. It was right at the point where it was to sync to the spindle, and just sat there forever, until I hit E-stop. This is a cvs trunk loaded on 6/28/2008. I'm sure I should update, but it looks like Alex Joni is making a big change, changing all hal component parameters to hal pins. It seemed like that would require hal file changes to adapt.
So, would it be expected for a 6/22/08 trunk version to wait forever on a G33 with reverse spindle rotation? The second thing I saw was that the G33 synch'ed move showed strong velocity oscillation throughout the move. This used to work, and the only thing I can THINK of that changed was increasing the dispatch rate of the trajectory_thread to the same as the servo_thread. I did this at the CNC Workshop (2008) and haven't used the machine much since then. I suspect I never ran the G33 threading.ngc program since that change. Any thought why the Z movement is VERY unstable suddenly? (I stole the spindle servo amp from that controller, so I can't test the rigid tapping program that I was using at the Workshop, which DID work after speeding up the Trajectory_thread. I will try to set that up tomorrow, and see if it moves stably in Z.) The Z movement velocity was a sharp triangle wave, with some change in frequency during the G33 move. It appeared to be doing something like 0 - commanded velocity - 0 - commanded vel over and over, quite bizarre. Maybe some ini variable got altered by accident. Jon ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
