Work with probe

This might be a better general LCNC question but since it happens inside one of the probe macros I thought I'd start here.

The issue is with manual tool change as parsed in a users g-code likeMy observations were that the system would move to the tool position.  Move up and then move down again.  It appears as if the commenting this statement out of doesn't seem to make a difference as the manual tool change operation movement is still being done.I determined that behaviour by discovering that there are two XYZ locations for tool changes.  The guide tells us to add this:The guide doesn't tell us to remove these tool change parameters as I have with the '#' symbolsBy setting the XYZ TOOL_CHANGE_POSITION to a dramatically different position from the [CHANGE_POSITION] shows that the spindle is first moved to that position and then to the [EMCIO] TOOL_CHANGE_POSITION. Commenting those out leaves the spindle at the [CHANGE_POSITION]

I think it's happening because of this in the psng_manual_change.ngc subroutine file.
Why is there in essence a recursive call to the M6 function we are currently in?  I don't understand why that is there.  I suspect that's what results in the use of the [EMCIO] TOOL_CHANGE_POSITION.

Anyone have any ideas about this?
Thanks
John





 

Well, it's not recursive, the remap option load the appropriate code when the program calls M6.
Then, inside the remapped code, it's the original M6 that is called to ensure LinuxCNC is aware of tool change and set all necessary values on the modal state of the machine (tool number, tool diameter, tool length, etc).

If original M6 is not called within remapped function, the tool will not be considered as changed and probably make erratic behaviour after M6 call in main program.

furynick wrote:

Well, it's not recursive, the remap option load the appropriate code when the program calls M6.
Then, inside the remapped code, it's the original M6 that is called to ensure LinuxCNC is aware of tool change and set all necessary values on the modal state of the machine (tool number, tool diameter, tool length, etc).

If original M6 is not called within remapped function, the tool will not be considered as changed and probably make erratic behaviour after M6 call in main program.
 

So the question then is if the loadusr manual tool change line is commented out but there are values in [EMCIO] like TOOL_CHANGE_POSITION why is there a move to that location?  What else is running that probably shouldn't be?  Commenting that out solves the move problem but there are others on the test bench Pi4 where I haven't' re-enabled the loadusr manual tool change.

I'll put together a detailed description of those.  Very strange. 

Hey,
just wondering if there is version for 2.9?

myval wrote:

Hey,
just wondering if there is version for 2.9?
 

I found it is easier to use the qtDragon screens, there is a probe screen incorporated and the screen looks nice too.

Thanks for your info. Testing it as we speak.
It did not like my old axis setting so have to manually se it again. (no big deal) the screen definitely looks better then axis
Thanks

myval wrote:

Thanks for your info. Testing it as we speak.
It did not like my old axis setting so have to manually se it again. (no big deal) the screen definitely looks better then axis
Thanks
 
 

There are two probe screens available, Versa probe and probe screen.
The manual explains how to use either through the ini file (confusingly not under the [probe] heading in the manual).

right I get all my settings and script run sweet in qtdragon now but I think I am getting dumber.
I can not figure out signal for the probe pin input.

right, got the signal sorted (just had my brain scrambled last night)
But, I can not get basicprobe to work, versaprobe seems to work but the screen is all messed up (it looks like it needs bigger screen to work correct)
With the basic probe when I press any buttons it does not move at all and no error messages

Well, after some trial and errors I finally find a workflow to use probe screen.

I can't use qtdragon as my screen is limited to 1280x1024 and I don't want to replace it (19" rack server console).

Power on
Home
Tool setter
Touchplate height
Zero Z
Touchplate XY

The only remaining problem is tool change, the M6 remap break current program, after confirming tool change everything is stopped.
I have to duplicate Txx M6 to keep the program running and the tool height isn't adjusted as intended.

It seems this is a known problem as several people in this thread reported same issue but I didn't find the solution by reading replys to those messages. If anyone have an idea ...