On 9/18/2017 10:01 PM, Tom M wrote: > I'm in the process of changing my Mostly Printed CNC MPCNC from gantrykins > to trivialkin with Charles's gantry solution. > > The MPCNC is somewhat unique in that it has a dual gantry solution. > I setup a git repo where I have my perfectly working gantrykin solution > (less limit switches) a branch called autohome where I'm working on the > trivialkin/ gantry solution. > > At this point, I don't have the limits switches wired, but I have the "S", > "-" switches wired together so they simulated NC. > I can get axis to display and simulate jogging, but nothing is happening > with the motors. In my master(gantrykin) solution, I can here the > motor's click when I enable axis, but there is silence when I run trivial > kins. > > I'm not sure if instantiated the gantry object correctly(it looks a little > weird to me) Could someone give this a quick gander and see if there's > anything obviously wrong with this? > https://github.com/Workshop88/MPCNC/blob/AutoHoming/MPCNC.hal#L58
I don't see any obvious goofs in your HAL file. Check the ESTOP and machine-power signal chains on your hardware and make sure the stepper drivers are being enabled. Also, you can find a bit of documentation regarding instantiated components here: http://www.machinekit.io/docs/hal/instcomp_writing_a_component/ ...but it looks like the newinst command didn't get added to the online HAL docs. -- Charles Steinkuehler [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
