Welcome! Log In Create A New Profile

Advanced

Minimum X not zero, but it is set to 0

Posted by pockpock 
Minimum X not zero, but it is set to 0
December 22, 2017 09:11PM
Hi,

For some reason my X-axis has a minimum position of 10 instead of 0.

My limits are set as follows
#define X_MIN_POS 0
#define X_MAX_POS 317

But after homing I can move in the range [10..327]
I assume I have set some kind of offset, which settings could do that?

I was searching for "offset" and "10" in the whole config but couldn't find anything
and google isn't helping much.
I've attached my "Configuration.h"-file just in case

Thanks in advance

Best

Edited 1 time(s). Last edit at 12/22/2017 09:12PM by pockpock.
Attachments:
open | download - Configuration.h (57.7 KB)
Re: Minimum X not zero, but it is set to 0
December 22, 2017 09:51PM
You home to max, that sets max position from their it calculates min position

I would guess #define X_MAX_POS 317 should be #define X_MAX_POS 327
Re: Minimum X not zero, but it is set to 0
December 22, 2017 10:05PM
If I do that then I get the range [10..337]
while 10..20 is outside the movable area of the axis

Anyway shouldn't the homing to max set it to the defined "max-value" not "max-value+10"?
Re: Minimum X not zero, but it is set to 0
December 23, 2017 04:40AM
whats in your configuration_adv.h ?
Re: Minimum X not zero, but it is set to 0
December 23, 2017 10:24AM
As far as I recall it is unchanged.

I will try to use an other Marlin version in the evening.

Edited 1 time(s). Last edit at 12/23/2017 10:54AM by pockpock.
Attachments:
open | download - Configuration_adv.h (47.2 KB)
Re: Minimum X not zero, but it is set to 0
December 23, 2017 08:30PM
After upgrading to the newest stable version (1.1.7) the issue is gone. Just spent some time diff-ing the configuration files to make sure I don't forget anything.
For reference my faulty version was 1.1.1

Thanks for the help
Sorry, only registered users may post in this forum.

Click here to login