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 switch is the Xmin side and homing is ignoring the limit switches so....crash.
Your hal file lines 339-341 are: net limit-x-min => axis.0.home-sw-in #net limit-x-min => axis.0.neg-lim-sw-in net limit-x-max => axis.0.pos-lim-sw-in Should be: net limit-x-max => axis.0.home-sw-in net limit-x-min => axis.0.neg-lim-sw-in net limit-x-max => axis.0.pos-lim-sw-in If you are using the max limit switch as your home switch you need to connect the signal from the actual switch to both pins as above. When homing is active the limit switches are ignored as per the .ini file but that is OK because it is your home switch. On Sunday, August 18, 2019 at 4:27:04 PM UTC-4, Klemen Zhivko wrote: > > 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 client and use homing of X axis with following code: >> >> pb.Message.Container.Builder builder = Container.newBuilder(); >> pb.Status.EmcCommandParameters emcCommandParameter = >> pb.Status.EmcCommandParameters.newBuilder().setIndex(0) >> .build(); >> builder.setType(ContainerType.MT_EMC_AXIS_HOME); >> builder.setEmcCommandParams(emcCommandParameter); >> builder.setTicket(getNextTicket()); >> Container container = builder.build(); >> socket.send(container.toByteArray(),0); >> >> When I check hal signal with command: >> watch -n 2 halcmd show pin axis.0.pos-lim-sw-in >> I see that on manual press signal changes... Documented in video: >> https://www.youtube.com/watch?v=-BAKEVgsQ6I >> >> However when xmax home limit is touched, x axis continue moving on when >> finally it is stucked and cannot physically move further, having weird >> motor noise of stucked axis move. I need to power off machine (software). >> Fom machinekit I get: >> 21:51:12 MT_EMC_OPERATOR_ERROR >> 21:51:12 joint 0 on limit switch error >> >> It sounds like a hal problem but cannot find an error. >> >> My ini file is in: >> >> https://github.com/zhivko/PipeCutter/blob/master/src/main/resources/myini/machinekit/CRAMPS.ini >> >> One of first hal files is in: >> >> https://github.com/zhivko/PipeCutter/blob/master/src/main/resources/myini/machinekit/CRAMPS.hal >> >> It seems I cannot make homing work. Can somebody check my ini and hal - >> is there an error? >> >> Image of xmax home switch is on attached picture. >> >> >> Hope for any reply. >> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/a6532152-d32b-4e1b-85a4-d687e0ce7388%40googlegroups.com.
