Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homing to Y max - Y axis moves double distance #11793

Closed
stevegoddard opened this issue Sep 10, 2018 · 10 comments
Closed

Homing to Y max - Y axis moves double distance #11793

stevegoddard opened this issue Sep 10, 2018 · 10 comments
Labels
C: Configuration T: Question Questions, generally redirected to other groups.

Comments

@stevegoddard
Copy link

stevegoddard commented Sep 10, 2018

configuration.zip

Description

Hi,
I have a P3 Steel (Prusa i3 clone) that i have just rebuilt with a larger bed (200 x 300).
All was working fine. But to maximise the area of the bed I could use I decided to move the Y endstop from the min to the max position.

This has resulted in very odd behaviour:

G28 Y homes the bed correctly to the Y max endstop (bed forward).
M114 then reports the Y position at 300 (this is correct).
G1 Y150 moves the bed 300mm backwards (effectively to the Y min position)!! It should move the bed to the halfway position.
Moving Y to any values lower than 150 (i.e. 100 or 0) result in the bed moving too far and the stepper jamming.
Moving Y to any values between 300 and 150 result in the bed moving twice the requested distance - for instance: G1 Y290 moves the bed backwards 20mm rather than 10mm.

My config:

// Specify here all the endstop connectors that are connected to any endstop or probe.
// Almost all printers will be using one per axis. Probes will use one or more of the
// extra connectors. Leave undefined any used for non-endstop and non-probe purposes.
#define USE_XMIN_PLUG
//#define USE_YMIN_PLUG
#define USE_ZMIN_PLUG
//#define USE_XMAX_PLUG
#define USE_YMAX_PLUG
//#define USE_ZMAX_PLUG

#define X_HOME_DIR -1
#define Y_HOME_DIR 1
#define Z_HOME_DIR -1

// The size of the print bed
#define X_BED_SIZE 200
#define Y_BED_SIZE 300

// Travel limits (mm) after homing, corresponding to endstop positions.
#define X_MIN_POS 0
#define Y_MIN_POS 0
#define Z_MIN_POS 0
#define X_MAX_POS X_BED_SIZE
#define Y_MAX_POS Y_BED_SIZE
#define Z_MAX_POS 200

Config files attached.

Thanks,
Steve

@brandstaetter
Copy link
Contributor

Moving Y to any values lower than 150 (i.e. 100 or 0) result in the bed moving too far and the stepper jamming.

#define Y_MIN_POS 0

something does not match up here - why did you set the bed size to 300 yet only want to use 150 to 300?

@stevegoddard
Copy link
Author

stevegoddard commented Sep 10, 2018

@brandstaetter - I want to use the entire bed!

I have the bed defined as:

#define Y_BED_SIZE 300

And the usable area:

#define Y_MIN_POS 0
#define Y_MAX_POS Y_BED_SIZE //i.e. 300

When i home the bed, it moves to position 300 - correct.
I should then be able to move it to position 0 - but any movements are doubled. So if i try and move it any distance greater than around 150 it hits the end of the printer and jams.

@brandstaetter
Copy link
Contributor

Ah I see. So please check your DEFAULT_AXIS_STEPS_PER_UNIT.

@stevegoddard
Copy link
Author

Hi @brandstaetter ,
Axis steps have not changed with the swapping of the Y endstop. Using standard GT2 belt and 20 tooth pulleys. Both X and Y use the same pulleys. X is operating fine with correct movement.

#define DEFAULT_AXIS_STEPS_PER_UNIT   { 80, 80, 400, 160 }

@thinkyhead
Copy link
Member

Does M502, M500 (and reboot) help at all?

@thinkyhead thinkyhead added T: Question Questions, generally redirected to other groups. C: Configuration labels Sep 12, 2018
@stevegoddard
Copy link
Author

Thanks for the suggestion @thinkyhead - I've not tried this - but i have EEPROM disabled. I'll give it a try though.
I've been going lots of Goggling and I'm pretty sure the issue relates to my TMC2130 drivers which I have just added to X,Y and Z. But they were working fine prior to swapping the Y endstop from min to max.
I'm going to upgrade from 1.1.8 to 1.1.9 - hope to finish this tonight and see if that resolves the issue. I'll report back.

@thinkyhead
Copy link
Member

Good luck. Yes, TMC2130 stepper drivers are known to do odd things like this. But let's try to rule them out first and then if needed we can see if something else is going on.

@stevegoddard
Copy link
Author

Upgrade to 1.1.9 solved this issue.

Very odd.

Thanks for all the help!

@gmg23
Copy link

gmg23 commented May 14, 2019

I am having this same problem running 1.1.9 and 1.1.X bug fix. Running a new Tevo Tornado stock everything. All axis work perfectly during homing, I can move the bed from the LCD, and they operate perfectly during bed leveling. Been pulling my hair out all day. Basically an G0 or G1 command cause the Y axis to go to max position (300). After that Y is completely unrecoverable unless homed. This causes prints to literally just print in a single line on the back of the bed. Y ends up at ~280 after bed leveling and as soon as the print tries to send the bed back to center, it goes to 300 and locks up. Terminal shows the print working normally. The LCD reports the Y position as if the bed is moving appropriately. I am at a total loss. Would really appreciate any suggestions. Thanks in advance.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C: Configuration T: Question Questions, generally redirected to other groups.
Projects
None yet
Development

No branches or pull requests

4 participants