OK.. I have been running my machine for the last few months with ZERO issues.. I upgraded to the Redline HMI…
Running a new project, Something is up and I can’t figure it out. I have a tool setter and my Probe Block. This is my normal steps of operation…
Load my file, Put in my first bit, and then I zero out x and y to match the location of my project.. I then PROBE just Z with the block. All good right?? Well normally it is.
When I run the program, it prompts for a tool change. Of course the bit is already in there so I hit ok and it goes and measures it on the tool setter. Now…Here is where it gets weird… It moves over to the project and starts to air carve! As if the z setting is lost.. I set Z with the Probe Block.. but after measuring the tool setter, its all wrong.. I have not changed anything in regards to the tool setter location or configing it. It has worked perfect since I first set it up.
So.. I reset Z again with the probe block and then hit run again. So it restarts WITHOUT measuring the bit and starts the carve. … Next Problem.. When it prompts for a tool change, I change the bit.. IT moves over to the tool setter and measures,… Then moves over to my project and dives straight through the material as if the Z was not even set!.. I’ve ruined 5 slabs of Walnut having to redo this every time. I dont understand what is going on. I have never had this problem.
So I decided to load separate tool paths.. one for each bit.. 1st tool path… set z with probe block and then hit go. it measures the bit on the tool setter and then starts a normal carve. Again.. I used the prob block and the z height is right. SO.. that tool is done.. I load the next tool path. put in the new bit and measure it again with the Probe block. I hit go. It measures the bit with the tool setter.. moves over my project and again ignores the z setting and dives it deep into my project again.
I dont know if the tool setter has become corupt or what.
Usually this works flawless.. I load a bit, measure z. hit run. it measures it on the tool setter and then starts to carve as normal. when it prompts a bit change.. I change it, it measures it and then it starts to carve at the correct z setting. Thats how its been working for the last 2 months. for the last 3 days.. It has lost its mind and this sequence of steps does not work.. Something is going on between the prob block and the tool setter.
What does this mean? My tools all match. From the Tool Database, Tools in the HMI.. etc etc.
I dont understand what you are saying? Every project I have run. I set z with the probe block… then I load the File, Hit run.. It prompts me for the first tool.. Which is the Tool I loaded.. So I just hit next and then it moves over to the toolsetter and measures it.
What do you mean the FIRST Tool in the Controller Tools Section?
Are you saying I have to put tool number 1 in.. even though I am not using that tool? I am confused.
Home your machine: Always run a Home All command immediately when you turn on the machine.
*** Match the tool: Ensure the tool number displayed on your controller screen matches the actual physical bit loaded in the spindle.**
*** Measure initial length: Measure your starting tool on the tool setter before probing the XYZ workpiece zero for your project.** [1, 2]
Performing Manual Tool Changes in a File
Follow on-screen prompts: When running a G-code file with multiple tools, the machine will pause and prompt you when a tool change is required. [1, 2]
Move to change location: The spindle will move to your designated Manual Tool Change position. [1, 2]
Swap the bit: Remove the old bit and install the new tool requested by the controller. [1, 2]
Resume the cycle: Press Cycle Start. The machine will automatically move to the tool setter to probe and calculate the new tool length offset, then return to the job and resume carving. [1, 2]
I do always home the machine.. Again, My normal steps have always worked..
The Tool is matched! Both in the Database, In my Gcode, and on the HMI..
I normally do not do manual tool changes. I run all my tool paths in one file. The only reason I mentioned this, was because I was trying to trouble shoot it.
OF put out a document that shows the steps for the Probe and the Toolsetter when loading a new program to run. I can’t find it though. Again.. This has been the order I have run and its worked from the beginning..
Load my first bit I am going to need.
set my x,y
probe z with the probe block
load the program and hit start
it prompts you for the first bit needed. Which I normally already install and its ready to go
I hit ok and then it moves over to the tool setter and measures it
then it carves normally..
This has been how I have ran the machine for the last 2 months with zero issue. It would prompt for bits as needed, measure them and then continue.
Based on the description above that you posted.. I would need to load the last bit from a previous project or whatever that I am not going to even use.
I cant find the steps that OF posted on the correct sequence when using the probe block and the tool setter together with the new Redline HMI..
Did you ever get it working properly? I’ve just ruined three pieces of walnut doing the exact same thing. I’ve been using CNCs for six years. The support people sent me to the same article you were sent to…
Mine homes, then clicks the toolsetter, so it knows where it is from the second it gets turns on, then every tool change it hits it again. Changing bits and then hitting the toolsetter again, it may think it is somewhere else - then it has you change bits and gets the same number, but offset from the previous reading.