You didn't need to change the switch, just the "polarity" that it's seen as in hal. I don't use a BBB but since it has an "invert" parameter on the GPIO pins, that should do the job. I was actually incorrect in what I said before, that signal is prior to the pin input so it won't change by inverting the BB pin. looking at the BBB pin in hal should show it's value is inverted if you set the invert parameter. Otherwise you could also use the "not" component prior to the BBB pin to do the same thing.
Or if it's easier for you and you have extra switches laying around you can try the NO switch like you said. On Wednesday, August 21, 2019 at 12:46:24 PM UTC-4, Klemen Živkovič wrote: > > Thanks Justin, > I will try this immediately. > As per your suggestion I changed switch to NO switch. > On halscope I saw that raw signal from beaglebone oscillates pretty much, > and it is not clear to me why, as it is tied to 5v over resistor. > > See x-max signal fro cramps schematic. > https://reprap.org/mediawiki/images/5/5a/CRAMPS.v2.1.sch.pdf > > However I use debounce in my hal, and signal seems to be stable as saw > from my previous halscope picture. > > Regards > > On Wed, 21 Aug 2019, 16:55 justin White, <[email protected] <javascript:>> > wrote: > >> Yes you can make one switch work. >> >> Change lines 340-342 to this: >> 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 >> >> Now your axis 0 max and home hal pins are connected to the same signal. >> Keep HOME_INGNORE_LIMITS=YES because you have to ignore the fact that you >> will trip the limit switch signal while homing >> >> As you see by the post I linked to it is not perefereable to have your >> switches reading true when they are not tripped, this is the case because >> your switches are NC and you are using a non-inverted input.. Whether this >> *can >> *work or not I don't know toggle this line to 0 or 1: >> setp bb_gpio.p8.in-07.invert 1 >> >> ....until the signal "limit-x-max" reads false when the switch is not >> tripped. It's still a NC switch and operates the same way, all you're doing >> here is changing the value that it is seen as in hal. >> >> On Wednesday, August 21, 2019 at 9:40:47 AM UTC-4, Klemen Živkovič wrote: >>> >>> Yes there is only one switch - this is enough for calibrating x axis - >>> no? >>> It is max limit switch since it position is positive. >>> Have you seen anything weird in my last configuration because I still >>> cannot make this work? >>> regards >>> >>> On Wed, 21 Aug 2019 at 14:44, justin White <[email protected]> wrote: >>> >>>> That is a limit switch since it's at the very end of travel, but >>>> there's only one switch? The first hal file you posted had that whole >>>> section commented out. >>>> >>>> That is either your min-limit, or your max limit, depending on how that >>>> thing is oriented. I would tend to call that the Min-limit but that's up >>>> to you. If that's your minimum limit switch then you don't have a home or >>>> max limit switch. >>>> >>>> >>>> >>>> -- >>>> website: http://www.machinekit.io blog: http://blog.machinekit.io >>>> github: https://github.com/machinekit >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Machinekit" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/machinekit/6a9AUOleAXE/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/machinekit/e52adf48-2a4f-4eb2-bf1b-615648763e56%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/machinekit/e52adf48-2a4f-4eb2-bf1b-615648763e56%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> -- >>> Klemen Živkovič >>> Župančičeva 34 >>> 1290 Grosuplje >>> Slovenia >>> mobile: 051 381 888 >>> >> -- >> website: http://www.machinekit.io blog: http://blog.machinekit.io >> github: https://github.com/machinekit >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Machinekit" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/machinekit/6a9AUOleAXE/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/machinekit/58db6373-158b-4420-a136-e6ab6f172664%40googlegroups.com >> >> <https://groups.google.com/d/msgid/machinekit/58db6373-158b-4420-a136-e6ab6f172664%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/c915d0b4-bfd0-4324-aaef-1b64687df233%40googlegroups.com.
