X axis only goes so far in one direction

So I’ve got the LR3 built, thanks to everyone along the way!

But I may have an issue, the X axis will go acros the gantry the entire way to the right side ( if you’re standing behind it) but will only go to the left as far as when you started ie 0 on the LCD. I’m assuming it thinks it started clear on the left end and will not go negative ( move X axis to -1.00 MM for example) on the screen because of this. Is that correct?

So some more info would be good. Is this the v1e fw or did you make your own?

Yes it won’t go past 0.

If you use the home X command it should go all the way to the left, trigger the endstop and set its position as 0. You want to home X and Y when you power on and Z before starting any job.

That is only if soft stops are enabled. I thought they were disabled by default.

I would definitely check which firmware you have, and reset defaults (M502).

1 Like

It’s the v1e fw

1 Like

Which one? 515D?

I flashed the V1CNC_SkrPto_DualLR_2209 version 2.1.1/515

hi, I am having this error as well, I loaded V1CNC_SkrPto_DualLR_2209 version 2.1.1/515.

and when I try to home X, it moves towards zero, but stops at zero and not going all the way to the switch.
This is what it looks like in the configuration.h
// Min software endstops constrain movement within minimum coordinate bounds

#define MIN_SOFTWARE_ENDSTOPS
#if ENABLED(MIN_SOFTWARE_ENDSTOPS)

// The size of the printable area
#define X_BED_SIZE 1220 // 200
#define Y_BED_SIZE 1220 // 200

// Travel limits (linear=mm, rotational=°) after homing, corresponding to endstop positions.

#define X_MIN_POS
#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

I ave hardware endstops, so do I need to comment out the min?

Hello @Manbub ,

It would probably be better to start a new thread, but…

I’m guessing that you have an LR3 with an SKR Pro v1.2, and It sounds like you are experiencing an issue where it will move using the MOVE commands ok, but it will stop when homing if you start the homing command when the gantry is a large distance from the endstops. Is that correct?

If so, there are two things that you can do:

  1. Move the gantry closer to the endstops using the MOVE command before homing, or
  2. Change the #DEFINE_Y_BED_SIZE and/or #DEFINE_X_BED_SIZE to the actual size of your table.

The former is easier, the latter will require editing, compiling and flashing the firmware. But I have done this with mine, because I wanted to be able to home it from anywhere on the table.

See this thread…

1 Like

Thank you let me try today and will get back

Ok I made the value the correct size 1280mm x and y.
The z homing and y homing bot work correctly. The x homing still has an issue.

When I turn it on, move the x to the middle using the move command and try to home, it moves towards zero and stops 2 inches before it hits the sensor. The red led turn on. I made sure the switch works by using the g code command as well as watching the led turn on and off.

Also what is weird if I move the router in the x to the middle without using the move command the. Tell it to home x, it moves 10mm to the positive then stops and it says that’s zero.

Any ideas?

There is a typo (you say the z axis works, then say again that z is still not working). Which axis is still not working?

That indicates an open circuit in the X endstop.

Be very careful when you do this, and do it very slowly with the controller unplugged. The motors will act as a generator, and can damage the stepper drivers.

That’s what I thought , but I used my continuity tester and it is connected from the switch to the connector. Also when I click the switch the red led goes on and off

Please start a new thread, I’ll assist you there…

Include all relevant info, like type of build (LRx), controller (SKRx), whether it worked before and then failed, or never worked, etc.

A video of the problem can tell a lot .

closing old topic to help fight spambots