Solved: Jogging past axis limits..?

sinned6915

@nightowl999
do you have and H564 statements in your homing macros ?

formating: use three back ticks , the one under the ~, top left of your keyboard.

test

Nightowl

Forgive me, @sinned6915, but I'm not really sure what you mean, but I don't have H564 statements in the homing files. I do have them in the config.g file, though (M564 S1 H1)

jay_s_uk

@nightowl999 both your X and y endstop locations are set to the minima (X1 and Y1). When you home, the minima limit from M208 is applied even though you're moving to the Maxima.
Change the 1 to a 2 (so X2 Y2) in your M574

Nightowl

There is definitely something wrong with the configuration files of my machine.

As I understand it, M564 is used to limit (or not) axis movements, with the S limiting (or not) movement outside the axis boundaries and H to allow (or not) moving the axes without homing.

In my config.g file (above) there is the line "M564 S1 H1" and, when I first start up the machine, I can't move an axis without homing it first, as I would expect (and I get the G0/G1: insufficient axes homed error).

If I then send M564 H0 S1, I can move any axes in any direction, but also past it's limits, which I thought the S1 would prevent.

Am I going mad?

Nightowl

I did that, @jay_s_uk, but then the endstops didn't activate, but I'll try (anything) again!

UPDATE: Now I get the G0/G1: target position outside machine limits when I try to move any axis. The proximity sensors do work, though!

jay_s_uk

@nightowl999 you'll need to do the same with your Z endstop too.
There's also no need to include M564 as S1 H1 are the default setup

Nightowl

I'm in the process of doing that now, @jay_s_uk, but won't I still have the same problem?

jay_s_uk

@nightowl999 not if you're jogging to the -ve once homed

Nightowl

Blinkin' 'eck, @jay_s_uk, you've only gone and sorted it!

The only thing, and I might just have to get used to this, is that the machine home coordinates are back to the maxima values, rather than 0, 0, 0 I was hoping to achieve.

I don't care any more . It's not as if the machine co-ordinates really matter with a CNC, as the starting point of the work being cut is more important!

jay_s_uk

@nightowl999 exactly. Typically front left is 0,0. Ideally you want it there as otherwise whatever you're cutting is the opposite way it appears on screen.
Homing to max is perfectly fine.
If you did want to flip it the other way you'd have to change your M574s back, flip the move direction in M569 and rewrite your homing files to move towards the minima rather than the maxima

Nightowl

Thanks, @jay_s_uk. I think it's time I started doing stuff, rather than messing about!

Talking of homing... Because I can't really reach the back of the machine when it's homed, I temporarily REM'd out the lines relating to the Y axes in the homeall.g file. But, it still homed the Y axes.

Does the Home All button on the dashboard run the homeall.g file, or the individual home files?

jay_s_uk

@nightowl999 homeall but if a certain axis isn't there, it then calls the homing file for that axis, unless they're hidden

Nightowl

Well, I don't know who had that foresight, @jay_s_uk, but that would explain the magical event

I really appreciate the help, thank you.

sinned6915

@nightowl999 said in Solved: Jogging past axis limits..?:

I think it's time I started doing stuff, rather than messing about!

That will leave a bruise if your don't sort this out!

Did you follow the basic comissioning procedure that it outlined in the docs?
https://docs.duet3d.com/en/How_to_guides/Commissioning#h-7-check-endstops
Its really straight forward to to take it step by step

If you do it 'half-way' then it WILL come back to haunt you someday. DAMHIKT!

Nightowl

@sinned6915 said in Solved: Jogging past axis limits..?:

That will leave a bruise if your don't sort this out!

Did you follow the basic comissioning procedure that it outlined in the docs?
https://docs.duet3d.com/en/How_to_guides/Commissioning#h-7-check-endstops
Its really straight forward to to take it step by step

If you do it 'half-way' then it WILL come back to haunt you someday. DAMHIKT!

Yeah, I followed those instructions closely, but it's in changing things to suit my situation that made it difficult (in my mind, anyway), and trying to keep track of incremental changes is a bit challenging.

I believe this is sorted now, so apart from one or two other capabilities I want to integrate into the system (using an old Carbide3D touch probe, install a power fail/resurrect ability and install an externally switched feed hold (pause/resume) facility, I'm almost ready to cut stuff!

sinned6915

@nightowl999 said in Solved: Jogging past axis limits..?:

Carbide3D

I am in the middle of comissioning a mill right now too. I understand what you are going through.

GOOD LUCK!

fcwilt

@nightowl999 said in Solved: Jogging past axis limits..?:

I believe this is sorted now, so apart from one or two other capabilities I want to integrate into the system (using an old Carbide3D touch probe, install a power fail/resurrect ability and install an externally switched feed hold (pause/resume) facility, I'm almost ready to cut stuff!

Would you post a picture or two of your mill?

Thanks.

Frederick

Nightowl

Sure, @fcwilt, but I’ll do it tomorrow 🥱

Nightowl

Not sure if this is what you wanted, @fcwilt, but here you go:

The machine is a RatRig 1075 KillerBee, although I've made a few amendments to the supplied machine, including using 4x proximity sensors instead of limit switches, and redesigned the spoil board supports. It has a Duet 3 MB6HC control board (as you already know!) connected via a wired network to a Microsoft Surface Pro.

Most of my work is done on my iMac, which is in the house, so I connect to the Surface Pro and the Duet via a wired network using powerline adapters.

Apart from my own knowledge limits, everything seems to work well - but the proof will be when I eventually make something!

fcwilt

@nightowl999

Thanks for the pictures.

Frederick