Home position y value not allowing full travel of unit

My machine is is set up at 18" in the y, 32" in the x. I would expect it to home at X0Y18, however it is now homing at 0, 6.692. No matter what I do I can’t change the y value. With the 6.692 set, and my machine max y travel at 18", the y direction travel only is about 11.3" at current before it stops so I can’t travel in the complete Y available space. Where it stops, the position is indicating 0,0 but is well short of the actual machine origin true 0,0. I have a Neje Master 2S Max. This issue just popped up as I used to have full range.

I pulled the power on the unit today and ever so slowly manually moved the unit to the machine origin. When I finally got it there, plugged in the machine and connected it to LB it was indicating a position of 0,0. I hit ‘Home’ and it stopped at the same spot it was stopping previously heading the opposite direction and gave me an 'ALARM:9 Homing fail" error. After this it again called this point, in the middle of my y axis 0,0. Any thoughts on what I can do?

It seems to know it’s not at 0, 0

So it sounds like it’s moving off the home location. Do you have anything set up to do this?

Can you move it ‘back’ to 0, 0?

:smile_cat:

jkwilborn, I rewrote my problem situation after experimenting last night with a little more detail. Hope this helps.

Have you made any recent GRBL changes?

If not and this was recently done then this sounds like it could be a work offset issue. Can you run these commands in Console after a homing operation?

$I
$$
$#
?

Ran and ended up with this:
[VER:1.1f.20180715:]

[OPT:VML,35,254]

Target buffer size found

ok

$0=10

$1=200

$2=0

$3=7

$4=0

$5=0

$6=0

$10=1

$11=0.010

$12=0.002

$13=0

$20=0

$21=0

$22=1

$23=1

$24=100.000

$25=1000.000

$26=250

$27=1.000

$30=1000

$31=0

$32=1

$100=80.000

$101=80.000

$102=80.000

$110=4000.000

$111=4000.000

$112=4000.000

$120=200.000

$121=200.000

$122=200.000

$130=170.000

$131=170.000

$132=150.000

ok

<Idle|MPos:0.000,170.000,0.000|FS:0,0>

[G54:0.000,0.000,0.000]

[G55:0.000,0.000,0.000]

[G56:0.000,0.000,0.000]

[G57:0.000,0.000,0.000]

[G58:0.000,0.000,0.000]

[G59:0.000,0.000,0.000]

[G28:0.000,0.000,0.000]

[G30:0.000,0.000,0.000]

[G92:0.000,0.000,0.000]

[TLO:0.000]

[PRB:0.000,0.000,0.000:0]

ok

ok

Your machine believes it’s 170x170mm. Have you recently changed settings or updated your firmware?

You can correct the max travel portion but it’s possible there are other things configured incorrectly.

Run these commands in Console:

$130=810
$131=460

Rehome and test.

Not to my knowledge, but I’ve been checking a lot of functions this week trying to figure out this issue. When I look at how the laser is setup in LB, it is at the 32x18. Is there a way to change those settings in LB now, or should I look for an update from Neje?

Run the two commands I list. I suggest also specifying your work area in mm rather than inches as that’s how it’s designed. You can work in inches no problem.

  1. push the units button on the numeric edits toolbar
  2. go to Edit->Device Settings
  3. set work area to 810x460, then OK
  4. you can change the units back to inches if you like in numeric edits toolbar

Thanks, I’ll give them a shot and let you know how it goes.

If this occurs, the machine does not know where it is.

If your machine homes, normally this should be fixed and it may solve some of your problems.

Since it’s attempting to home, I assume it’s configured properly.

:smile_cat:

That worked! Get rid of one problem now trying to fix the next. Now, the laser keeps pausing. Tried 3 different runs. First time it went to .5%, next 2 %, this time 4%. Stays ‘Busy’ like it is still doing something but program and laser not moving. Any idea?

Typically those things are associated with connection issues of some sort.

Not sure in your case but Neje does have a page that discusses these types of disconnections. See if this applies to you:
Solution of NEJE Master 2 serises device stop working – NEJE (neje99.com)

Thanks for your help. Still working on the stopping issue. Checked all the components and drivers out and they seem ok. Going to work on some static control this weekend.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.