Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: Azalin on March 29, 2023, 09:45:36 AM
-
Hi,
I have added lots of scripts to the screen set in my Mach4 but I feel like I need to update to a newer version because my current Mach4 sometimes dives about 10mm into the part and crashes (on start). No matter what I tried just didn't help and I feel really desperate.
1- So what is the best approach on updating Mach4?
2- Can I keep and use my custom screen set in the newly installed Mach4? Or do I copy and paste all the script into the new screen set?
Please note that I don't have any ATC hardware in my mill. I only do manual tool change.
Best,
Suat
-
If you did not give your screenset a unique name then it might get overwritten.
About your bit diving into the material.
Does your gcode file have tool number information?
-
Hi,
I have lines like this:
N25 T3 M6 D3 H3
-
But removing M6 or D3 H3 doesn't work.
-
The problem is you are telling the software to use tool information.
If you did a tool touchoff then opened the file with the tool information and ran it the Z position will not be correct.
Removing the tool information and not doing a touchoff will not fix the problem.
Here is my suggestion.
Close Mach4
Make a gcode file without the tool information.
Start Mach4 again and do your setup.
Try the file without the tool information first.
-
I tried to run some of my gcodes to figure in what situation the Z axis plunges into the material. It did it again but I could not reproduce the same thing.
However I noticed that Mach4 changed some tool heights in the tool table. Now I have zeroed everything in the tool table.
Are you suggesting I only need M6 (removing T# and D# H#)? If so I'll try that.
Thanks
-
Ah how silly I am. Program won't stop on M6 without T because Mach4 thinks I still have the same tool.
-
It really sounds like you are trying to run before you walk.
Put the different tools in different files.
Yes it can be done in one file but tools are different lengths.
That is what the tool table is for.
Each tool has a different length and it is set accordingly.
The H# selects the length from the tool table.
If you did not set it correct the machine has no idea how high it needs to be.
-
Hi,
to answer the question about updating.
If you download a new build of Mach4 then you'll also get a new copy of wx4.set, wx6.set etc and all the standard screen sets. If you have an existing
copy of lets say wx4.set and you have been adding and editing bits of it then it will get overwritten and all your edits will be lost.
What you need to do is your current screen set, whatever it is called, you need rename it to give it a unique mane. Then when you update to a later build it will be left
alone, and you can carry on using the same scree set but in a later build.
Craig
-
It really sounds like you are trying to run before you walk.
Put the different tools in different files.
Yes it can be done in one file but tools are different lengths.
That is what the tool table is for.
Each tool has a different length and it is set accordingly.
The H# selects the length from the tool table.
If you did not set it correct the machine has no idea how high it needs to be.
I think there is a misunderstanding. As I said in my initial post I do all the tool change manually. Because I change tools manyally I never open the tool table. By manually I mean:
Say I use 4 different tools in one gcode file:
- I ran the code, on T1 M6 (and whatever the D and H is) I adjust the Z axis and zero. Hit start, machine goes and does the job as expected.
- When the code comes to M6 T2 I do the same again: I change the tool, adjust Z then zero, hit Start and boom. it crashes.
I did this millions of times on Mach3 and never faced a problem like this.
-
Hi,
to answer the question about updating.
If you download a new build of Mach4 then you'll also get a new copy of wx4.set, wx6.set etc and all the standard screen sets. If you have an existing
copy of lets say wx4.set and you have been adding and editing bits of it then it will get overwritten and all your edits will be lost.
What you need to do is your current screen set, whatever it is called, you need rename it to give it a unique mane. Then when you update to a later build it will be left
alone, and you can carry on using the same scree set but in a later build.
Craig
Thanks Craig
-
Azalin,
Just remember that is not going to fix your problem.
-
Azalin,
Just remember that is not going to fix your problem.
You are right.
Don't miss my last post
https://www.machsupport.com/forum/index.php?topic=47245.msg296567#msg296567 (https://www.machsupport.com/forum/index.php?topic=47245.msg296567#msg296567)
-
Don't miss my last post
https://www.machsupport.com/forum/index.php?topic=47245.msg296567#msg296567
I saw it.
That is why I said make each tool a different file instead of trying the manual change in the middle of a file and needing different lengths.
Just make sure to remove tool information if you do this before opening the file.
-
Thanks Bill
-
I'm curious. Are you setting tool lengths somewhere on your machine? Also, to use the H for the tool length, you need to call a G43 H(Toolnumber)
-
I think Chad's on the right track. You're either resetting the Z zero for each tool and then calling a tool length with a G43 Hx in your gcode, or you're not resetting the Z zero. If your gcode has tool length calls, like G43 Hx Zxx, and there is a number in the tool table, AND your reset Z zero in there somewhere, you're doomed!
I think what you need to do is either set tool lengths by gaging the tools first, set them in the tool table and just run the program without having to stop and reset the Z zero, or, like Bill said, run each tool as a separate gcode file and just use a tool number that doesn't have a length in the tool table and set the Z zero WITH the tool before each file.
It ain't Mach4:)
Tom
-
Hi,
I use Bills strategy also. I have only manual tool change and must perforce touch off in Z every toolchange.
I use Fusion and its really quite convenient for this procedure.
I do the CAD per normal then go to the CAM section. I do all the tool operations say with the 1.5mm four flute endmill
on one material setup. It's very useful to think about and decide early on a work zero that will remain consistent throughout
multiple operations.
Now when I want to swap tools to 1/8th or 1/4 say, I make a new setup, but Fusion offers the convenience of re-using the existing material setup,
and if you have chosen the work zero appropriately then you can retain the same work zero, at least X and Y, but touch off the Z alone and zero at the tool change.
Fusion applies a post processor to each setup, thus with the two setups which are essentially replicas, I end up with two toolpath files, and I name them OP1, OP2 etc. Its quite
convenient. Most importantly NO-COCKUPS!
Craig