Manual tool change + tool lengh touch off

More
10 years 2 months ago #79020 by clunc
Possibly the only thing I have in common with you, and your skills.

Still. It's a start...

I'm going to try to insert a (MSG,) before the tool change reminding of the M6/M600 remaps.

Thank you for the re-ply. And for the scripts smarter than me.

Please Log in or Create an account to join the conversation.

More
10 years 1 week ago #81856 by pommen
I'm loving the tool measurements from Orange Cat. I have been using it since this spring and have not run into any trouble that I didn't cause myself.

Has anyone been able to combine this routine together with the tool change dialog of Gmoccapy? I'm thinking it could be changed to fit, but I haven't had any luck with it so far.

/Peter

Please Log in or Create an account to join the conversation.

More
10 years 1 week ago - 10 years 1 week ago #81939 by auto-mation-assist
I have been playing with this in gmoccapy and it seems to work in simulation as far as preview movement is concerned. One problem I'm having issues with to do further testing is that when the present mounted cutting tool tool has to be removed to manually exchange it with the new desired tool the "resume" dialog never pops up on the screen. There is no problem when there is no tool already mounted . In that case the code movement completes to the end.

So, after this pop up message: "Please remove the mounted tool and press OK when done". It never shows the resume popup dialog and the code appears to stay in pause mode.

I'm thinking that there may be a potential linking issue with the line I copied from the code if this is what should pop up the resume dialog:

(DEBUG, Change to tool #<_current_tool> with diameter #<ToolDiamMM>mm, #<ToolDiamIn>in then click Resume )
Last edit: 10 years 1 week ago by auto-mation-assist.

Please Log in or Create an account to join the conversation.

More
10 years 1 week ago #81940 by auto-mation-assist
In my sim configuration I have:

RS274NGC_STARTUP_CODE = G17 G20 G40 G43H0 G54 G64P0.005 G80 G90 G94 G97 M5 M9
PARAMETER_FILE = sim.var
FEATURES=30
SUBROUTINE_PATH = /home/john/linuxcnc-dev/configs/sim/gmoccapy/macros:
REMAP=M6 modalgroup=6 ngc=tool-change
REMAP=M600 modalgroup=6 ngc=tool-job-begin

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 100000
SERVO_PERIOD = 1000000
TOOL_CHANGE_AT_G30 = 0


In hal
net tool-prep-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change => iocontrol.0.tool-changed

---

Do I have to use prolog= epilog= ??

Please Log in or Create an account to join the conversation.

More
10 years 1 week ago - 10 years 1 week ago #81944 by auto-mation-assist
I misunderstand the "resume" that it actually is the "pause" button" in gmoccapy when running a gcode program. So when running a program it looks like the tool change function from the code in this thread appears to work ok.

What I was looking for is a dialog box that appears is when a M6 T3 command for example is entered in the midi when a T2 tool is already installed and has to be removed before the T3 tool could be loaded. The tool-change code pauses in such a case and there is now way to get it out of pause mode without a dialog pop up and a "ok" button to proceed after a manual tool change made by entering a tool change cmd from the midi.

These should be in the postgui file since they are also needed.

net tool-change gmoccapy.toolchange-change <= iocontrol.0.tool-change
net tool-changed gmoccapy.toolchange-changed <= iocontrol.0.tool-changed
net tool-prep-number gmoccapy.toolchange-number <= iocontrol.0.tool-prep-number
Last edit: 10 years 1 week ago by auto-mation-assist.

Please Log in or Create an account to join the conversation.

More
10 years 1 week ago - 10 years 1 week ago #81946 by auto-mation-assist
Here are some notes I wrote to myself so I wont get to confused in a year or so from now.

For tool change routine by "orangecat" for use in gmoccapy. Alows for automatic tool length measurement and tool changing from inside running gcode file. Can also be used manually.

M600 should near the header of every gcode file as mentioned in the file documentation.

To be Done: Need a dialog when M6 command is manually entered in midi when a existing tool is already installed
during tool change. Perhaps a gui panel for manual use?

Files needed: In /'user-name'/config/macro folder:
tool_change.ngc -- wrtten by "orangecat"

In macro folder open terminal and generate two symlinks
$ ln -s tool_change.ngc tool-job-begin.ngc
$ ln -s tool_change.ngc tool-change.ngc

In my temporary ini file I have:

RS274NGC_STARTUP_CODE = G17 G20 G40 G43H0 G54 G64P0.005 G80 G90 G94 G97 M5 M9
PARAMETER_FILE = sim.var
FEATURES=30
SUBROUTINE_PATH = /home/john/linuxcnc-dev/configs/sim/gmoccapy/macros:
#--- The below two lines are for tool change ---
REMAP=M6 modalgroup=6 ngc=tool-change
REMAP=M600 modalgroup=6 ngc=tool-job-begin

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 100000
SERVO_PERIOD = 1000000
#--- The below line is for tool change ---
TOOL_CHANGE_AT_G30 = 0

In my hal file I have:
net tool-prep-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change => iocontrol.0.tool-changed

In my postgui hal file I have:
net tool-change gmoccapy.toolchange-change <= iocontrol.0.tool-change
net tool-changed gmoccapy.toolchange-changed <= iocontrol.0.tool-changed
net tool-prep-number gmoccapy.toolchange-number <= iocontrol.0.tool-prep-number

The hal and the postgui hal files could be combined in postgui.hal
Last edit: 10 years 1 week ago by auto-mation-assist.
The following user(s) said Thank You: pommen

Please Log in or Create an account to join the conversation.

Time to create page: 0.099 seconds
Powered by Kunena Forum