#138 Divide-by-zero for home search speed = 0

[Anonymous]

I changed the "home search speed" from 0.05 to 0.0, based on the description in the manual that reads:

HOME_SEARCH_VEL = 0.0 Initial homing velocity in machine units per escond. A value of zero
means assume that the current location is the home position for the machine

(Typo: "escond" in original should be "second")

That causes stepconf to fail when writing the output file, but without producing an error message. It writes the ini file up to that line, then returns to the final screen; attempting to quit produces the "file not saved" dialog.

Starting stepconf from a console produces this Python trace cascade:

Traceback (most recent call last):
File "/usr/bin/stepconf", line 1310, in on_complete_finish
self.data.save()
File "/usr/bin/stepconf", line 778, in save
self.write_inifile(base)
File "/usr/bin/stepconf", line 406, in write_inifile
self.write_one_axis(file, 1, "y", "LINEAR", all_homes)
File "/usr/bin/stepconf", line 488, in write_one_axis
latchvel = get("homevel") / abs(get("homevel"))
ZeroDivisionError: float division

Perhaps a checkbox to say "Do not home this axis" or "This axis does not have a home switch" would be in order?

Other than that, I like it a lot!

[Jeff Epler]

Logged In: YES
user_id=2772
Originator: NO

If an axis does not have a home switch, then do not select an input pin as home switch on the pin assignment page. I realize that this makes it difficult to have a combined home switch for X and Y but no home switch on Z. I'll have to give this kind of configuration more thought.