On 8/1/2016 10:08 AM, matthew venn wrote: > I managed to resolve the locked memory error, and started machine kit (at > least > no errors in the log). My python program (I'm not using axis) then started, > and > started homing, but none of the motors moved and the enable led on my board > didn't light.
Did the HAL file get read and started properly? You should be able to see the HAL setup by poking around with halcmd after your python program launches at startup. > As there's nothing arwy in the logs I've not got much to go on. After killing > the process and starting it as normal, everything works as expected. > > Any ideas why things aren't working non-interactively? Typically when things don't work properly when automated (cron, init scripts, etc), but work as expected from the command line, the issue is something to do with the environment. Check your path and any other settings your python program may be relying on. Some programs are also sensitive to the terminal type, and don't like being run in a non-interactive terminal or completely detached (with no standard in/out/err). I'd have to see your launch script(s) for any more specific suggestions. -- 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.
