Setting up a test run on the V2-10. Using F360.
My gcode works just fine in the simulator, no errors.
when I try to run the same code on the machine, it starts up, moves into position and then shuts down when the Z is supposed to move. I then get an error stating that the Z is trying to move beyond it's limit.
After that, when re-homing the machine the Z then shows -5.000 on the DRO. The only way to get it back to 0.000 is to disconnect the machine from USB and from power and restart everything.
The error is on line 20 of the gcode, here is line 19, 20 and 21 (in mm)
N75 G1 X-13.026 Y4.134 F10000.
N80 G43 Z24.7 H12
N85 G1 Z8.585
The machine limits I read in the FAQ is z = 3.55 in (-3.45 in to 0.1 in) (-87.63mm to 2.54mm) in Z
So it appears that the Z is trying to move in the opposite direction - but shouldn't the simulator indicate that as well?
When I setup the machine orientation, should the Z axes be pointing in the direction the Z moves? or does it matter?
I'm missing something here.
Bob,
Yep, that is how the orientation is set up. Thanks for confirming I have the axes right. I assumed the arrow is pointing in the positive direction. So in the home position, the z is pointing to the spindle, the Y up and the X away from me.
Tokyo,
I have "Document Unit" selected in the post process window - should I specify?
qrot
I did not set a z offset. Does the simulator use info from the pocketNC user interface? Should I be connected to the machine when using the simulator?
Up to now, all my experiences has been on manual mills and lathes, so don't hurt me :)
Thanks