Home › Forums › TinyG › TinyG Support › Z max limit input not working
Tagged: zmax homing limit switch
- This topic has 4 replies, 2 voices, and was last updated 4 years, 6 months ago by cmcgrath5035.
-
AuthorPosts
-
May 3, 2020 at 7:25 pm #11824BoonstraMember
I hope you can help me solve this issue im having.
If got al limit switches working except the Zmax.
As soon as it hits the switch it freezes, it doesnt back off as on the other axis.
feeder> G28.2 Z0
{“r”:{},”f”:[1,0,9]}
{“qr”:47}
{“qr”:45}
{“qr”:46}
{“sr”:{“stat”:9,”vel”:200,”feed”:200,”coor”:0,”momo”:1,”dist”:1,”posz”:-1.04339,”mpoz”:-1.04339}}
{“er”:{“fb”:101.03,”st”:203,”msg”:”Limit hit [$clear to reset, $lim=0 to override] – input 6″}}
{“sr”:{“vel”:0,”posz”:5.5,”mpoz”:5.5}}
>These are my g2core settings
#define Z_AXIS_MODE AXIS_STANDARD
#define Z_VELOCITY_MAX 600
#define Z_FEEDRATE_MAX Z_VELOCITY_MAX
#define Z_TRAVEL_MAX 15
#define Z_TRAVEL_MIN 0
#define Z_JERK_MAX JERK_MAX
#define Z_JERK_HIGH_SPEED Z_JERK_MAX
#define Z_HOMING_INPUT 1
#define Z_HOMING_DIRECTION 1
#define Z_SEARCH_VELOCITY 200
#define Z_LATCH_VELOCITY 50
#define Z_LATCH_BACKOFF -2
#define Z_ZERO_BACKOFF -1- This topic was modified 4 years, 6 months ago by Boonstra.
May 3, 2020 at 8:22 pm #11826cmcgrath5035ModeratorHmmm, have not played much with G2 homing
See https://github.com/synthetos/g2/wiki/Digital-IO#digital-inputs-during-homing
What is the value in Parameter {zhi: ?
Behavior implies that the switch being hit is still acting as a limit, not homing
May 4, 2020 at 11:19 am #11827cmcgrath5035ModeratorI sort of stumbled on this rather old thread which may be of interest to you
https://synthetos.comtopics/how-to-configure-himing-switches-in-tinyg2/#post-8990A quick look sort of confirms to me that, at least 4.5 years ago, your
#define Z_HOMING_INPUT 1
above should be
#define Z_HOMING_INPUT 6
maybe?From the “er” message, it is input 6 that is acting like a limit
May 11, 2020 at 5:58 am #11829BoonstraMemberThx for the hint,
I was think to digital cause i used to set the homing inputs to 0 or 1 for easy axis.
i thought that the input was defined somewhere else and that i only had to enable 1 or disable it 0.with assigning the correct input to the axis its working like a charm.
next hurdle would be squaring the gantry as it has a motor on either side of it.
my setup is based opun a ooznest OX with 2 stepper drivers for the Y axis and on either side a proximity sensor.
i ant to use these sensors to square out the gantry because the repeataibilty of these sensors is very accurate.but i dont see it’s implemented yet but a work around by diasbeling 1 motor to home the second one. One huge disatvantage is that the motor is free to move while it needs to be fixed. any idea on this?
May 11, 2020 at 10:04 am #11830cmcgrath5035ModeratorHere is a link to an old discussion on the topic
https://synthetos.comtopics/is-dual-gantry-homing-supported/#post-10025Here is a discussion on G2core
https://github.com/synthetos/g2/issues/359 -
AuthorPosts
- You must be logged in to reply to this topic.