Stephen Wille Padnos wrote: > andyholcomb wrote: > > >> Hi John, just a reminded to not let you forget about me, please. Or any >> buddy else that can help; because I am still having the problems and >> have no idea where to start. >> >> Thanks >> Andy >> >> andyholcomb wrote: >> >> >> >>> When I get it to mess up the motor-pos-cmd is jittering at the 4th 5th >>> 6th etc decimal place, so is the pos cmd and the pos cmd fdback. The >>> dir is also bouncing back and fourth but the step appears to be fine. >>> >>> Andy >>> >>> >>> > Hi Andy. > > What are the SCALE settings for the jittery axes? All are set at 40000 > When you say "Manual > mode" , do you mean jogging only? Yes > Do the axes jitter regardless of what > the MDI command is? They jitter sometimes as soon as I go into mdi or auto mode, if I move x in manual mode and then then go to mdi mode, the x axis may start to jitter, it seems like it only jitters if the axis has been moved. I was messing with it earlier I moved all of my axises in manual mode and them went to mdi mode, the x and the z axis were jittering, I entered g00 x0y0 and the x and the y move as they should; but the z was still jittering during the move. > For example, if X tends to jitter, does it do so > only when you issue moves that include X, or does it also do so when you > do Z or YZ only moves? > > It may be good to look at your configuration info. If you could put > your .ini and .hal files on http://pastebin.ca and send us the link, it > would be helpful. If you could also provide a short sample program that > exhibits the problem, it would be good. > It works fine when the program is running but if I pause it or stop in auto mode it sometimes goes nuts (Not so true I have had a axis mess up while the file was running, the z was jittering while the code was running on the x and y axises( z slowly went down)). In MDI mode, sometimes it will start doing it as soon as I press f5 to go into MDI mode other times it does it when the command is completed, other times it does it on the still axis while the command is running. The program is irrelevant. I think it started happening after I put my backlash setting in, would that have anything to do with it? I just went out and set all of my backlashes to 0 and it does not seem to do it. Does this help?
Andy > - Steve > > >>> John Kasunich wrote: >>> >>> >>> >>>> andyholcomb wrote: >>>> >>>> >>>> >>>>> This is a new and updated (today) install. I am running steppers >>>>> motors. In manual mode it works great, MDI and Auto mode it will >>>>> randomly go nuts on on one or two varying axises. Nuts, sometimes >>>>> going back and forth about 10 or 20 degrees on a axis with no movement >>>>> on the digits on the screen. Or, moving slowly in one direction with no >>>>> movements on the location display of the screen. On the MDI it seams to >>>>> do it when I first start up and go into that mode, I can execute some >>>>> code and it stops all the time I think. On the auto it will do it >>>>> sometimes when I go into the mode and sometimes when I get done with a >>>>> program. It will stop if I go back to Manual mode all the time. >>>>> >>>>> Any thoughts? >>>>> >>>>> >>>>> >>>>> >>>>> >>>> If the display isn't changing, EMC thinks it isn't moving. Time for >>>> some classic "divide and conquer" debugging. EMC sends position >>>> commands out the HAL pins axis.n.motor-pos-cmd. Open another shell >>>> while EMC is running, and invoke halmeter. Select the motor-pos-cmd >>>> pin, and you will get a "meter" displaying the current command from EMC. >>>> Then do whatever you do to make it misbehave. If the meter shows no >>>> change, then EMC proper isn't commanding that motion. You start >>>> multiple halmeters - put a couple on the step generator pins as well, >>>> both command and feedback. If the stepgen feedback isn't changing, then >>>> the step generator isn't commanding that motion either. >>>> >>>> If you find something changing when it shouldn't, report back what you >>>> found. If none of those pins are changing but your axis is still >>>> moving, you probably want to look at the step pins. It doesn't make >>>> sense to discuss next steps in much detail, since they depend on what >>>> you find in the first steps. >>>> >>>> Troubleshooting is _always_ an interactive process. Ask a question, >>>> conduct a test to find the answer, and then ask a new question based on >>>> what you just discovered. >>>> >>>> Regards, >>>> >>>> John Kasunich >>>> >>>> > > ------------------------------------------------------------------------- > 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 > > ------------------------------------------------------------------------- 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
