Mach3 Threading Helper Activity
Helps with the Mach3 CNC Threading functionality
Status: Beta
Brought to you by:
stephanbrunker
Activity for Mach3 Threading Helper
-
stephanbrunker committed [r17]
-
Mach3 Threading Helper released /G76Thread 0-33v2 Win32 portable.zip
-
-
-
-
-
-
-
-
-
Update to v0.32
-
-
Threading Increments anomoly
-
Nobody forces you ... I only wish I could fix some issues based on Mach3 itself. MinIncrement is such a case, it depends on the X axis mode. Means: If you change the mode, you have to change the minimum default too if you want equal behaviour. (same for Clearances ...) That is not entirely logical, but anyway. I only regret my time looking into issues which aren't part of what I did.
-
Goatofmendez posted a comment on ticket #10
It's OK I had to stop using your helper. It caused more problems than it solves. Regards Steve From: stephanbrunker [mailto:stephanbrunker@users.sourceforge.net] Sent: 08 July 2018 10:23 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #10 Threading Increments anomoly Why in the world do you want to use so many passes? To get these values, i had to aim for 37 in equal strategy. Because of the minimum, only 32 should be executed anyway. For most of them, you hit the minimum...
-
-
Why in the world do you want to use so many passes? To get these values, i had to aim for 37 in equal strategy. Because of the minimum, only 32 should be executed anyway. For most of them, you hit the minimum value which is because without pressure, the tool won't cut properly. Even my lathe with only 500 Watts can make this thread in 10-15 passes max, and that is on the safe side. The difference can be because of rounding of such small amounts or a different setting for the minimum. After pass #16,...
-
Hard coded thread data definitions?
-
Spindle rpm increase or decrease whilst running threading
-
That is a issue of Mach3 and not of the Gcode. If you have the extended threading diagnostic active, the true RPM is displayed on runtime and the RPM is a closed control loop based on the spindle index and the Z speed.
-
The form has removed spacing - try this (extra section is what mach3 shows. Helper code line for 1/2 UNF 20 thread: G76 P1.27 R12.597 X11.005 H0.306 I29.5 K7.773 Z-32.5 L360 Q3 Helper ---------------------- Mach3 Pass Increment Depth 1 0.153 0.153 ---------------------------- 0.307 2 0.064 0.217 ---------------------------- 0.1272 3 0.049 0.266 ---------------------------- 0.0975 4 0.041 0.307 ---------------------------- 0.0823 5 0.036 0.343 ---------------------------- 0.0725 6 0.033 0.376 ----------------------------...
-
The form has removed spacing - try this Helper code line for 1/2 UNF 20 thread: G76 P1.27 R12.597 X11.005 H0.306 I29.5 K7.773 Z-32.5 L360 Q3 Helper ----------------------Mach3 Pass Increment Depth 1 0.153 0.153 ---------------------------- 0.307 2 0.064 0.217 ---------------------------- 0.1272 3 0.049 0.266 ---------------------------- 0.0975 4 0.041 0.307 ---------------------------- 0.0823 5 0.036 0.343 ---------------------------- 0.0725 6 0.033 0.376 ---------------------------- 0.0655 7 0.030...
-
Spindle rpm increase or decrease whilst running threading
-
Threading Increments anomoly
-
Pass increment anomoly
-
Yes, Cut type is explained on Mach3_threading.pdf on page 27. Type 0 and 2 are Flank Infeed righthanded and lefthanded, and Type 1 is Alternating Flank infeed. InFeed Type is the formula for the increment, with 0 for an equal cutting area and 1 for the Sandvik formula. As you can see, the increments for the Sandvik formula are smaller at first, and bigger for the last ones and if you confuse that, the number of passes will be off, because the number of passes is calculated from the size of the first...
-
-
-
-
To be clear.. so I should be setting Infeed Type to = 1. And leave the cut type = 0???? How do I execute the G76 line offline? Great work!!! Thanks From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 03 January 2018 21:52 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #9 Pass increment anomoly I found the cause of the error: 20 inches in front of the monitor. But as an excuse, i found it only because i made the same error and the offical Mach3 documentation...
-
I found the cause of the error: 20 inches in front of the monitor. But as an excuse, i found it only because i made the same error and the offical Mach3 documentation is ... bad. There are two different options in the Turn Options: Cut Type and InFeed Type. These names are not distinct and not documentated. I did that in a way that I named the Sandvik Formula InFeed, but it is easily confused ... you set the Cut Type option to 1 and not the InFeed Type option. The macro then did what it was programmed...
-
Oh good - I thought I was going insane :-) From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 03 January 2018 20:31 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #9 Pass increment anomoly Partially good news: Now was able to reproduce the error. That means I can debug. I'll tell you if I found the cause. [tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/ Pass increment anomoly Status: open Milestone: 1.0 Created: Fri Dec 29, 2017 07:04...
-
Partially good news: Now was able to reproduce the error. That means I can debug. I'll tell you if I found the cause.
-
I set test mode to true and upon processing the threading (G76) line the machine just stops - spindle and everything. Sometimes it will crash Mach3 completely and then also crash ESS. I have to turn ESS off at the wall to reset. I set the test back to false and all works again. I can repeat this time and time again, the same thing happens. From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 03 January 2018 09:03 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets]...
-
Printout of Threadtest.tap (Taper = 0) (Infeed Angle = 29.5) (Total_Depth = 1.204) (StartZ = 2.02) (EndZ = -10) (Passes = 30) (Seq = 0 ) (Min_Decrement = 0.001 ) (Dia Mode ) G0 X5.987 Z2.02 G32 x5.987F 1 G32 x5.987F 1 (Decrement = 0.22 pass 1) G00 X5.667 Z1.0822 G32 X5.667 Z-8.9378 F1 G01 X5.887 Z-9.1205 F 1.5651249151426 G00 X5.987 G00 X5.987 Z2.02 (Decrement = 0.0911 pass 2) G00 X5.5759 Z0.9942 G32 X5.5759 Z-9.0258 F1 G01 X5.887 Z-9.2842 F 1.5651249151426 G00 X5.987 G00 X5.987 Z2.02 (Decrement...
-
Yes, I added m1076.mls to Mach3\ folder and the others to the Mach3\macros\Mach3Turn\ folder. Strangely I have another machine set up and tried it on that and I get exactly the same thing. I will set test mode and see what it says Regards Steve From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 03 January 2018 09:03 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #9 Pass increment anomoly No, I use a Smoothstepper myself. Did you put the m1076.m1s macro in...
-
No, I use a Smoothstepper myself. Did you put the m1076.m1s macro in the Mach3\ folder? For this macro, it is different from the other macros which are in mach3\macros. As I said, the easiest way to check would be to edit the macro to test mode. The test mode will output all the generated GCode into a file, beginning with some diagostics (lines 124-131). I'd add some more like Depth_Lastpass and First_Pass_Depth to check the passs calculation.
-
I don't get it either - it is really strange. Would Ethernet Smoothstepper have anything to do with it? From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 02 January 2018 14:21 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #9 Pass increment anomoly Sorry, but I don't get it. The G76 line is correct and the formula in the M1076.m1s macro is: StartX = tXStart() EndX = tEndX() Total_depth = abs(StartX - EndX) First_pass_Depth = tFirstPass() Depth_Lastpass =...
-
Sorry, but I don't get it. The G76 line is correct and the formula in the M1076.m1s macro is: StartX = tXStart() EndX = tEndX() Total_depth = abs(StartX - EndX) First_pass_Depth = tFirstPass() Depth_Lastpass = tDepthLastPass() Min_Decrement = GetMinPass() seq = tGetInfeedType() 'infeed formula (0 - equal, 1 - Sandvik) 'calculate number of passes from First Pass Depth and Last Pass (optional) If seq = 1 Then npass = CInt((Total_Depth - Depth_lastpass)^2 * 0.3 / First_pass_Depth^2) + 1 Else npass =...
-
Also - perhaps I am missing something, but looking at the output of Equal and Sanvik cut types it seems like the Sanvik is more equal than 'Equal' actually is? The first step on 'equal' has a massive drop off. Pass Increment Depth (equal) 1 0.278 0.278 9 0.048 0.834 2 0.115 0.393 10 0.045 0.880 3 0.088 0.482 11 0.043 0.922 4 0.075 0.556 12 0.041 0.964 5 0.066 0.622 13 0.039 1.003 6 0.059 0.681 14 0.038 1.041 Pass Increment Depth (sandvik) 1 0.157 0.157 9 0.052 0.813 2 0.130 0.287 10 0.049 0.862 3...
-
It would be far simpler for most people to be able to ignore the tip diameter completely and be able to put in your own cut depth. e.g. have an over-ride tickbox. Having the program set the cut depth without being able to adjust it is problematic. I know I can set the depth in the actual Gcode, but then the pass calculations are not right. Like I say I find i have to adjust the final depth of cut in the gcode on most threads that the helper provides. regards
-
I was using the previous version, however it seems the new .31 version does the same for me. I was and still am using the lset and the new .m1s files from your install instructions. G76 P1.0 R5.887 X4.683 H0.22 I29.5 K2.02 Z-10.0 L360 Q0 Pass Increment Depth 1 0.110 0.110 6 0.047 0.448 2 0.091 0.201 7 0.043 0.491 3 0.083 0.284 8 0.039 0.531 4 0.064 0.347 9 0.037 0.567 5 0.054 0.401 10 0.034 0.602 but in diagnostics it states 30 passes. (see pics) - the only difference I can see is that I use smoothstepper....
-
I was using the previous version, however it seems the new .31 version does the same for me. I was and still am using the lset and the new .m1s files from your install instructions. G76 P1.0 R5.887 X4.683 H0.22 I29.5 K2.02 Z-10.0 L360 Q0 Pass Increment Depth 1 0.110 0.110 6 0.047 0.448 2 0.091 0.201 7 0.043 0.491 3 0.083 0.284 8 0.039 0.531 4 0.064 0.347 9 0.037 0.567 5 0.054 0.401 10 0.034 0.602 but in diagnostics it states 30 passes. (see pics) - the only difference I can see is that I use smo...
-
-
-
There seems something wrong. For an M6x1, Infeed = Sandvik and diameter mode, for 10 passes I'll get that output in the attachment. The output line is G76 p1.0 r5.887 x4.403 h0.271 i29.5 k4.02 z-10.0 l360 q0 With the values similarly in the parameters tab and the turn options page of Mach3, after loading a gcode with that line, the Diags tab in Mach3 will show 10 passes and it makes 10 passes. So, you cannot be using the 0.31 version, haven't the options similar in parameters and Mach3 Turn options,...
-
There seems something wrong. For an M6x1, Infeed = Sandvik and diameter mode, for 10 passes I'll get that output in the attachment. The output line is G76 p1.0 r5.887 x4.403 h0.271 i29.5 k4.02 z-10.0 l360 q0 With the values similarly in the parameters tab and the turn options page of Mach3, after loading a gcode with that line, the Diags tab in Mach3 will show 10 passes and it makes 10 passes. So, you cannot be using the 0.31 version, haven't the options similar in parameters and Mach3 Turn options,...
-
There seems something wrong. For an M6x1, Infeed = Sandvik and diameter mode, for 10 passes I'll get that output in the attachment. The output line is G76 p1.0 r5.887 x4.403 h0.271 i29.5 k4.02 z-10.0 l360 q0 With the values similarly in the parameters tab and the turn options page of Mach3, after loading a gcode with that line, the Diags tab in Mach3 will show 10 passes and it makes 10 passes. So, you cannot be using the 0.31 version, haven't the options similar in parameters and Mach3 Turn options,...
-
It would be good to have a thread depth over-ride. When I came here 17 years ago, you all laughed at me. Well, you’re not laughing now, are you! Nigel Farage MEP - [Addressing the European Parliament June 28th 2016] From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 30 December 2017 10:11 To: [mach3threadinghelper:tickets] Subject: [mach3threadinghelper:tickets] #8 Thread data anomoly In that table is only only the very basic thread definition. I used these tables: http://www.emuge-franken-bg.com/attachments/article/97/15%20Gewindetabellen.pdf...
-
Thread data anomoly
-
In that table is only only the very basic thread definition. I used these tables: http://www.emuge-franken-bg.com/attachments/article/97/15%20Gewindetabellen.pdf . On the 7th page (#485) the last figure tells how the tolerance fields are applied. (Also the help in "about Threads"). For pitch 1 mm, the mensuration is 26µm for tolerance class g, and for grade 6 the tolerance is 180µm for the outside diameter and 112 for the pitch diameter. My program outputs 5.887 +- 0.087 and 5.269 +- 0.054 . That...
-
Pass increment anomoly
-
Thread data anomoly
-
Output format
-
fixed with v0.31
-
-
-
Its written with Freebasic, available here on Sourceforge. FB uses the QuickBasic Syntax, but has a complete set of Windows header files for the GUI programming and supports Oop and other features of an up-to-date programming language.
-
Its written with Freebasic, available here on Sourceforge. FB uses the QuickBasic Syntax, but has a complete set of Windows header files for the GUI programming.
-
Its written with FreeBasic, available here on Sourceforge. FB uses the QuickBasic Syntax, but has a complete set of Windows header files for the GUI programming.
-
Hi thanks for the reply - what Basic is it written in? E.g which editor and version are you using? The files look like the old Visual Studio VB5 style. Thanks Steve ---------------------------------------------------------------------------- When I came here 17 years ago, you all laughed at me. Well, you're not laughing now, are you! Nigel Farage MEP - [Addressing the European Parliament June 28th 2016] From: stephanbrunker [mailto:stephanbrunker@users.sf.net] Sent: 21 December 2017 21:08 To: [mach3threadinghelper:tickets]...
-
The answer is: not really. I based the app on a bunch of tables at: http://www.emuge-franken-bg.com/attachments/article/97/15%20Gewindetabellen.pdf but instead of hard coding all the tables, whenever possible I converted the data into formulas whenever possible so you can create virtually every Thread in spec but with the possibility to choose diameter and pitch at will. So you can create a M9.5 x 0.8 or something else simply by typing it into the appropiate fields - the values entered by the dropdown...
-
The answer is: not really. I based the app on a bunch of tables at: http://www.emuge-franken-bg.com/attachments/article/97/15%20Gewindetabellen.pdf but instead of hard coding all the tables, whenever possible I converted the data into formulas whenever possible so you can create virtually every Thread in spec but with the possibility to choose diameter and pitch at will. So you can create a M9.5 x 0.8 or something else simply by typing it into the appropiate fields - the values entered by the dropdown...
-
The answer is: not really. I based the app on a bunch of tables at: http://www.emuge-franken-bg.com/attachments/article/97/15%20Gewindetabellen.pdf but instead of hard coding all the tables, whenever possible I converted the data into formulas whenever possible so you can create virtually every Thread in spec but with the possibility to choose diameter and pitch at will. So you can create a M9.5 x 0.8 or something else simply by typing it into the appropiate fields - the values entered by the dropdown...
-
Hard coded thread data definitions?
-
Output format
-
I can. Might be a few days, because I've some other things on top of it in my stack.
-
Output format
-
Try to look at the Mach3 main menu: There is a Item: "View" and a subitem "Load screens"
-
Hi, quick question - when installing the .lset (an corrected Turn screenset 1024-2.lset -> install in %Mach3path%/) Do you rename 1024-2.lset to -> 1024.lset. Or keep it as 1024-2.lset??? Is there any particular way to install or do you just copy it to the folder? Thanks Steve ---------------------------------------------------------------------------- When I came here 17 years ago, you all laughed at me. Well, you're not laughing now, are you! Nigel Farage MEP - [Addressing the European Parliament...
-
Hi, quick question – when installing the .lset (an corrected Turn screenset 1024-2.lset -> install in %Mach3path%/) Do you rename 1024-2.lset to -> 1024.lset. Or keep it as 1024-2.lset??? Is there any particular way to install or do you just copy it to the folder? Thanks Steve
-
-
-
Its hidden in Mach3: Config - Ports and Pins - Turn options - Infeed Type Type 0 is equal, Type 1 is sandvik Threre you can also set the Cut Type (on which side of the tool to cut) - see Mach3Threading.pdf, page 27, this is normally 0: righthanded flank infeed, cutting mostly at the left edge of the tool. the x,z clearances and the minimum decrement. these values had to be the same in the calculator options and in Mach3, that the number and depth of the passes calculated are identical. The same is...
-
Its hidden in Mach3: Config - Ports and Pins - Turn options - Infeed Type Type 0 is equal, Type 1 is sandvik Threre you can also set the Cut Type (on which side of the tool to cut) - see Mach3Threading.pdf, page 27 the x,z clearances and the minimum decrement. these values had to be the same in the calculator options and in Mach3, that the number and depth of the passes calculated are identical. The same is true for the motor acceleration values. It has no grave implications because the generated...
-
Its hidden in Mach3: Config - Ports and Pins - Turn options - Infeed Type Type 0 is equal, Type 1 is sandvik Threre you can also set the Cut Type (on which side of the tool to cut) - see Mach3Threading.pdf, page 27 the x,z clearances and the minimum decrement. these values had to be the same in the calculator options and in Mach3, that the number and depth of the passes calculated are identical. The same is true for the motor acceleration values. It has no grave implications because the generated...
-
Quick questio though - how does mach3 know the difference between a parallel thread and a sandvik? I got the sae code from both options Equal thread G21 G77 r XX x9.931 k5.0 z XX G76 p0.75 r9.931 x8.81 h0.177 i29.5 k6.641 z-15.0 l360 q2 Sandvik thread G21 G77 r XX x9.931 k5.0 z XX G76 p0.75 r9.931 x8.81 h0.098 i29.5 k6.641 z-15.0 l360 q2
-
-
UNF or custom threads????
-
I just put 0.30v4 online, where the naming of the UNF and UNEF threads in the dropdown is fixed.
-
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0 My calculator uses the same formula than the G76 macro to determine the number of passes...
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0 My calculator uses the same formula than the G76 macro to determine the number of passes...
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0 (https://sourceforge.net/p/mach3threadinghelper/tickets/_discuss/thread/88d6491d/7e...
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0 (/https://sourceforge.net/p/mach3threadinghelper/tickets/_discuss/thread/88d6491d/7...
-
The program displays a list of all the cutting passes. There are two formulas: Sandvik and equal for calculating the pass depth. Equal means that the cross section of the chip remains constant. For sandvik, the formula is slightly different with smaller increments at the beginning and greater at the finish, the "H" value is only the depth of the first cut. G76 p1.5 r4.925 x3.813 h0.352 i29.5 k5.782 z-10.0 l360 q0
-
It is a standard thread 1/2 UNF 20 TPI, however when cutting I want to be able to cut deep when starting the thead and then change cutting depth when nearer the finish (to get a better thread finish). This also speeds up the thread cutting process. e.g. G0 X12.55 G76 X11.4 Z-32.0 Q1 P1.270 J0.06 L45 H0.06 I29 C1.0 B0.01 T0 G0 X11.4 G76 X11.0 Z-32.0 Q2 P1.270 J0.01 L45 H0.025 I29 C2.0 B0.01 T0 Cut at H0.06 depth from 12.55mm to 11.4mm, then next cut at H0.025 from 11.4mm to 11mm thanks
-
Hi, the nut is definitely out of spec, I had them checked. However I cannot change the nut (welded into part) So I have to change my thread slightly to accomodate. Changing the x value will be fine. I already do this in mach3 and it works fine. thanks
-
Hi, the nut is definitely out of spec, I had them checked. However I cannot change the nut (welded into part) So I have to change my thread slightly to accomodate. Changing the x value will be fine. thanks
-
It is a standard thread 1/2 UNF 20 TPI, however when cutting I want to be able to cut deep when starting the thead and then change cutting depth when nearer the finish (to get a better thread finish). This also speeds up the thread cutting process. thanks
-
You can either change that in the output code - that is the x value. Because existing nuts are normally within the specs, that means your tool is not 100% perfectly calibrated, so I usually change that in the tooltable. In this case, it would be interesting to measure the pitch diameter what you've cut on your bolt. But really, my program just takes the tables of the specs and calculate from there the x values, regarding the tip form of the tool, so you are free to change the x value.
-
UNF or custom threads????
-
Great thanks - I see UNF now. Regarding custom threads - I have an M10x75 fine metric thread and the code produced created the inner diameter x as x8.81 e.g -> [G76 p0.75 r9.931 x8.81 h0.177 i29.5 k6.641 z-15.0 l360 q1] However the bolt is for an existing nut and 8.81 is loose - in mach3 it is set for 8.95 to create a tighter fit. Can i simply change this in the output code? e.g -> [G76 p0.75 r9.931 x8.95 h0.177 i29.5 k6.641 z-15.0 l360 q1] thanks Steve
-
Second pass with different thread depth?
-
Great thanks - I see UNF now. Regarding custom threads - I have an M10x75 fine metric thread and the code produced created the inner diamers x as x8.81 [G76 p0.75 r9.931 x8.81 h0.177 i29.5 k6.641 z-15.0 l360 q1] However the bolt is for an existing nut and 8.81 is loose - in mach3 it is set for 8.95 to create a tighter fit. Can i simply change this in the output code? e.g [G76 p0.75 r9.931 x8.95 h0.177 i29.5 k6.641 z-15.0 l360 q1] thanks Steve
-
I cannot imagine that to be a regular thread. Do you have a specification? In principle, you can do that manually within the output code, the x value is the thread depth. But if you change that value, the result would invalidate the profile for that specific pitch, because pitch and depth are related trough the specification of that thread. Simply spoken: you wouldn't be able to cut outside and inside thread with a normal angled cutter. Theoretically, it would be possible to create a thread with...
-
First, UNF 1/2 - 20 TPI is on the list (spec #11 is UNF). I should change the names to make that more obvious. If you are working within these specifications, the fields for diameter (in inch fractions) and pitch are open for editing, so you can change that.
-
Second pass with different thread depth?
-
UNF or custom threads????
1 >
