Did you change your .ini file back to HOME_IGNORE-LIMITS=YES? if you're
using a limit switch as a home switch you need to use "yes" to ignore
limits. You should set HOME_IS_SHARED=1 as well since you are sharing a
home switch with a limit switch.
Besides that you may need to invert
I did required changes, now it happens that homing procedure is breaked
with following output on machinekit console:
00:43:42 MT_EMC_OPERATOR_ERROR
00:43:42 hit limit in home state 7
00:43:42 MT_EMC_OPERATOR_ERROR
00:43:42 joint 0 on limit switch error
I updated hal and ini files... Maybe you
The hal component did work fine then my friend "cleaned it up" and it acts
weird when you enable the filter. Could just remove the filter pin and post
it but it is rather handy.
I've been tracking down an issue with the stepgens and depending on what
the issue is it may be part of the smart
according to your hal file you don't have a negative X limit switch, it's
commented out. Your home switch input is connected to your minimum limit.
Your .ini is setup to "home ignore limits" on the X axis. By what you said
it seems that your trying to home to the Xmax side, but your home
I also tried with
HOME_IGNORE_LIMITS =NO
in my ini, but then I get:
23:39:18 MT_EMC_OPERATOR_ERROR
23:39:18 hit limit in home state 5
23:39:18 MT_EMC_OPERATOR_ERROR
23:39:18 joint 0 on limit switch error
On Sunday, 18 August 2019 22:27:04 UTC+2, Klemen Zhivko wrote:
>
> I forgot to say I
I forgot to say I use beaglebone black with cramps hat, NC (normally
closed) home switch, and also debounce component as i saw from linuxcnc
forum that not debouncing signal could be issue.
On Sunday, 18 August 2019 22:25:47 UTC+2, Klemen Zhivko wrote:
>
> Hi guys,
>
> I am using machinekit
