First cut success - with questions!

Nightowl · 21 May 2022, 18:12

Before homing, M114 reports the following:
X:0.000 Y:0.000 Z:0.000 E:0.000 Count 0 0 0 Machine 0.000 0.000 0.000 Bed comp 0.000

Just a moment, and I'll home it...

Nightowl · 21 May 2022, 18:15

@JoergS5
After homing, it's:
X:547.000 Y:784.000 Z:97.000 E:0.000 Count 218800 313600 38800 Machine 547.000 784.000 97.000 Bed comp 0.000

JoergS5 · 21 May 2022, 18:20

@nightowl999 said in First cut success - with questions!:

@JoergS5
After homing, it's:
X:547.000 Y:784.000 Z:97.000 E:0.000 Count 218800 313600 38800 Machine 547.000 784.000 97.000 Bed comp 0.000

The 218800 is a value from your M92 setting and the homing position. What is your M92 setting, please?

Nightowl · 21 May 2022, 18:22

@joergs5 All axes are set at 400 steps per mm

JoergS5 · 21 May 2022, 18:24

@joergs5 ok, I think it's 218800/547 = 400.

This means, for every mm your router moves, the Count value for X will be incremented by 400. So you can always see where the firmware thinks that your router is.

Now before you start the error G0/G1 move, you can make a M114 and know where the router is. (of course the G1 before will be this position also in most cases, but to be sure...).

NB the values being all 0 at the beginning is, because firmware doesn't know where your steppers are at the beginning. This is what homing is meant for: telling the firmware where the stepper's positions are. The only reason why the firmware Count values and true stepper position may vary is if there are lost steps (M122 hiccups hight numbers will tell you).

JoergS5 · 21 May 2022, 18:29

@nightowl999

X:547.000 Y:784.000 Z:97.000 E:0.000 Count 218800 313600 38800

547 * 400 = 218800
784 * 400 = 313600
97 * 400 = 38800

or other round, from the Count value divide by your M92 (400) and you'll get the current mm position.

Nightowl · 21 May 2022, 18:30

@JoergS5
Should I move the axes to the Work XYZ first, set Work XYZ, then run M114?

JoergS5 · 21 May 2022, 18:32

@nightowl999 said in First cut success - with questions!:

@JoergS5
Should I move the axes to the Work XYZ first, then run M114?

My proposal would be to move to the last position which is ok. Then make a M114 and notify the Count values, then verify that the next command throws an error.

Nightowl · 21 May 2022, 18:35

@joergs5 Sorry, I edited the question as you answered...

I've now placed the spindle at the Work XYZ (without the cutter installed!) so should I set Work XYZ then run M114?

Nightowl · 21 May 2022, 18:38

M114 before setting Work XYZ...
X:37.000 Y:204.000 Z:85.000 E:0.000 Count 14800 81600 34000 Machine 37.000 204.000 85.000 Bed comp 0.000

Some more information:
Since installing the spoil board, my Z height has reduced to 75mm, but I haven't changed it in the config.g file yet.

M114 after setting Work XYZ...
X:0.000 Y:0.000 Z:0.000 E:0.000 Count 14800 81600 34000 Machine 37.000 204.000 85.000 Bed comp 0.000

JoergS5 · 21 May 2022, 18:45

@nightowl999 said in First cut success - with questions!:

M114 after setting Work XYZ...
X:0.000 Y:0.000 Z:0.000 E:0.000 Count 14800 81600 34000 Mach

Interesting! I was not sure, whether it will be corrected or not.

So work change (did you make it by G54?) doesn't change the count values.

I've learned here something also!
XYZ are the values from the work XYZ view, and the Machine coordinates behind are the true original coordinates.

Nightowl · 21 May 2022, 18:47

@joergs5
I just clicked the Work XYZ button on the Dashboard. I don't know anything about G54??

Nightowl · 21 May 2022, 18:48

@joergs5
The workzero.g file has the following lines:

; workzero.g

; G90 ; set to absolute positioning
G53 G1 Z{move.axes[2].max} F1500 ; raise the Z to the highest position
G1 X0 Y0 F2400 ; go directly above the work zero position
G1 Z0 F2400 ; go to the work Z zero position

JoergS5 · 21 May 2022, 18:49

@nightowl999 said in First cut success - with questions!:

@joergs5
I just clicked the Work XYZ button on the Dashboard. I don't know anything about G54??

I think it's not so important now, we want to find the reason for the error message.
One possible reason could be that the M208 limits take the XYZ values. But let's verify by you searching for the first error G0/G1.

Nightowl · 21 May 2022, 18:51

@joergs5 OK. Shall I load and run the file?

Actually, what I did was upload the gcode file, then right-clicked it and simulated the project, with these results:

21/05/2022, 19:54:21 File 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode will print in 0h 14m plus heating time
21/05/2022, 19:54:19 M37 P"0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode"
Simulating print of file 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode

JoergS5 · 21 May 2022, 18:58

@nightowl999 said in First cut success - with questions!:

G53

G53 is to clear coordinate changes and not using any machine coordinates, so I would not run it.
https://duet3d.dozuki.com/Wiki/Gcode#Section_G53_Use_machine_coordinates

There should be G54 to G59 somewhere else, probably in your Cut2D software.

The problem now is that I don't know your software and which commands are run. I can only help to find out the reason why there is the G0/G1 error message.

JoergS5 · 21 May 2022, 19:00

@nightowl999 said in First cut success - with questions!:

and simulated the proj

unfortunately it didn't find an error line, so it didn't help.
The simulation mode may have some shortcuts, e.g. not checking limits....

Nightowl · 21 May 2022, 19:03

@joergs5

Well, starting the file seemed to work, too.

I'm not sure what's going on here, but I'm also getting random disconnects

JoergS5 · 21 May 2022, 19:08

@nightowl999 said in First cut success - with questions!:

also getting random disconnects

I am innocent

Nightowl · 21 May 2022, 19:08

@joergs5

What I'll do now I know this file runs is to let it finish, s
hut everything down and use the same Work XYZ coordinates again tomorrow, but with the other file, and see how that goes.