Eric H. Johnson wrote: > I will try to get some more information over the next few days. If you would > like to see the configuration, I have posted it here: > http://pastebin.com/m2760010c
Great, thanks for posting that! A couple of comments on that config: It looks like it was based off an older, somewhat buggy hm2-servo config. Specifically, the [AXIS_*]OUTPUT_SCALE is not used by the hm2-servo.hal file. The [AXIS_X]MAX_VELOCITY is used in the hal file as pid.X.maxoutput, which i think is wrong. Oops, i just noticed that the standard hm2-servo config does the same, i'll check in a fix for that. The [AXIS_*]INPUT_SCALE values look strange. Is that really what the encoders are producing? The [AXIS_*]FERROR and MIN_FERROR look very large to me. Is it really acceptable for the machine to be a quarter inch off while feeding? In hm2-servo.hal, the hostmot2 driver is loaded with all debugging flags turned on, that's probably not needed. Oops, i just noticed that the standard hm2-servo config does the same, i'll check in a fix for that too. ;-) Wow, this machine has a GlueGun? :-) > The servo portion is basically right out of the example. An easy thing to > try might be to disable hal_joystick. After that, I guess they will need to > start learning how to use halscope. Yes, i think trying it without the joystick would be a good experiment to do. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
