Newbie setup Gmocappy setup

what program gcode are you using , make sure it does not go to x0 y0 first
how are you asking it in gcode to go to tool change positon etc

post your setup code so we can check

see change.ngc in your macros folder for the sequence , it might help

Hi CNCBasher

Sorry the troubles I'm making. I use the Tool_lenght_probe-.ngc, as you recommended. Have changed g20 to g21.

Maybe I've misunderstood, but I thought that the tool-change command did all the stuff, and was incoorperated in the test-program above.

This code do not involve the probe-coordinats nor the toolchangeposition bescribed in the ini-file.
After homing I load the program, and before running I move the cnc to a new origin. When I run the program and get to the g30 command the CNC goes back to the origin (0,0) and not the x-y parameter I've declined in the setup-ini, trying to find the probe.

I've tried to look in the change.ngc, but can not understand much....It looks to me that the change.ngc is not activated at all....


I'll hope this description is understandable and usefull ind this error-hunt...

Sincerly
Steen

see Norberts video here

Hi
I've seen the video a couple of times before. The central point is that my change.ncg is not called as shown in the video....

Been struckling with the homing procedure this evening. The x and y end-switches is not released ....something has been changed that have change the homing process. I've been comparing the befor- and after- inifiles. in the axis-sections they are identical...

...but with some manipulation I could at last load the program in the video. Got an error telling something like "the coordinatsystem could not be changed because of the cutter comparison set on"...could'nt get further....

Sorry all the troubles I'm making .... :blush:

Sincerly
Steen

Hi CNCBasher

I've solved the homing problem by changing the values for HOME, MAX_VELOCITY, MAX_ACCELERATION and STEPGEN_MAXACCEL- settings in the ini-file.

Have you found anything suspicious in the setup that couses the probe-problem.....? The change.ngc is not called when the tool is changed...

SIncerly
Steen

Hi Steen,

I just took a short look at your config:

in your hal file you still do load:

please comment that one out!

second in your INI File pléase change your Subroutine path:
Report what happen.

Are you able to launch your macro "go_to_pos X-pos Y-pos Z-pos"

Norbert

Hi CNCBAsher

Have done the changes you're requested. Still the same. Using the tool_length_probe.ngc-samplefile:
The change-code is still not accessed during the run, as it it shown in the video you showed me..

Sincerly
Steen

Sorry newbynobi

My answer was to you. I thought the answer came from CNCbasher

Sincerly
Steen

Hi again

Just a guess.: are these lines correct in the ini-file ?
Especially the 2 last lines. In all other lines the equalsign is with an space-char on each side....

Sincerly
Steen

Hi Steen,

you are wellcome.

Do you execute the tool_length_probe.ngc file?

If so,

This file does not contain any M6 code, and that one is the remaped code, so it will never be executed!!

Please open "gmoccapy_2_tools_with_cutter_radius_compansation.ngc" and run that file, what does your machine do?

Norbert