#9 Pass increment anomoly

[Goatofmendez]

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried several other threads and it is always the same - approx 2.2x the pass estimate in the program. Is there a setting I have missed somewhere that it causing this to happen???

thanks

[stephanbrunker]

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, haven't switched the m1076 and m1176 macros and don't using the 1024-2 screenset.

Please post a screenshot showing your passes calculation. I'll get these values, but for 13 passes.

[Goatofmendez]

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 am using Mach3 Version R3.043.062

[Goatofmendez]

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 0.119 0.406 11 0.047 0.908
4 0.091 0.498 12 0.044 0.953
5 0.077 0.575 13 0.042 0.995
6 0.068 0.642 14 0.041 1.036

[stephanbrunker]

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 = CInt((Total_Depth - Depth_lastpass)^2 / First_pass_Depth^2)
End If

If I calculate that line per hand with the values above
r (StartX) = 5.887
x (EndX) = 4.683
h (First_Pass_Depth) = 0.22

I'll get npass=10 for seq=1 (Sandvik), which is correct and what my Mach3 installation does. The npass value is then proceeded to the Diags page. Because I cannot reproduce that error, I am not able to debug it. The usual way would be to set test=true in the macro and add lines which output the intermediate values which then you can check in the test.tap file. That is also a way to check if really the right macro is active.

There only one thing a little bit off - the Turn option values for MinDepthPerPass and Clearance look like they are for an operating with Imperial setting (for Metric, something like 0.02 mm is a minimum value for the smallest increment and 0.1 mm is not much of a clearance), but these aren't part of that calculation.

If it is really that macro which is active, then something must alter the values on the way.

And as it is written on several places, the equal setting means that the chip area is constant. Because the tool is quite sharp, the first chip has not much of an area, thus the big increment.

[Goatofmendez]

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 = 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 = CInt((Total_Depth - Depth_lastpass)^2 / First_pass_Depth^2)
End If

If I calculate that line per hand with the values above
r (StartX) = 5.887
x (EndX) = 4.683
h (First_Pass_Depth) = 0.22

I'll get npass=10 for seq=1 (Sandvik), which is correct and what my Mach3
installation does. The npass value is then proceeded to the Diags page.
Because I cannot reproduce that error, I am not able to debug it. The usual
way would be to set test=true in the macro and add lines which output the
intermediate values which then you can check in the test.tap file. That is
also a way to check if really the right macro is active.

There only one thing a little bit off - the Turn option values for
MinDepthPerPass and Clearance look like they are for an operating with
Imperial setting (for Metric, something like 0.02 mm is a minimum value for
the smallest increment and 0.1 mm is not much of a clearance), but these
aren't part of that calculation.

If it is really that macro which is active, then something must alter the
values on the way.

And as it is written on several places, the equal setting means that the
chip area is constant. Because the tool is quite sharp, the first chip has
not much of an area, thus the big increment.

---

[tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/
Pass increment anomoly

Status: open
Milestone: 1.0
Created: Fri Dec 29, 2017 07:04 PM UTC by Goatofmendez
Last Updated: Mon Jan 01, 2018 06:17 PM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[stephanbrunker]

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.

[Goatofmendez]

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 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.

---

[tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/
Pass increment anomoly

Status: open
Milestone: 1.0
Created: Fri Dec 29, 2017 07:04 PM UTC by Goatofmendez
Last Updated: Tue Jan 02, 2018 02:21 PM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Goatofmendez]

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 = 0.0699 pass 3)

G00 X5.5059 Z1.0398

G32 X5.5059 Z-8.9802 F1

G01 X5.887 Z-9.2967 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0589 pass 4)

G00 X5.447 Z1.0033

G32 X5.447 Z-9.0167 F1

G01 X5.887 Z-9.3821 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0519 pass 5)

G00 X5.3951 Z1.0347

G32 X5.3951 Z-8.9853 F1

G01 X5.887 Z-9.3939 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.047 pass 6)

G00 X5.3481 Z1.0067

G32 X5.3481 Z-9.0133 F1

G01 X5.887 Z-9.4609 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0432 pass 7)

G00 X5.3049 Z1.0322

G32 X5.3049 Z-8.9878 F1

G01 X5.887 Z-9.4712 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0402 pass 8)

G00 X5.2647 Z1.0086

G32 X5.2647 Z-9.0114 F1

G01 X5.887 Z-9.5282 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0377 pass 9)

G00 X5.227 Z1.0307

G32 X5.227 Z-8.9893 F1

G01 X5.887 Z-9.5375 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0357 pass 10)

G00 X5.1913 Z1.0099

G32 X5.1913 Z-9.0101 F1

G01 X5.887 Z-9.5879 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.034 pass 11)

G00 X5.1573 Z1.0296

G32 X5.1573 Z-8.9904 F1

G01 X5.887 Z-9.5964 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0324 pass 12)

G00 X5.1249 Z1.0108

G32 X5.1249 Z-9.0092 F1

G01 X5.887 Z-9.6422 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0311 pass 13)

G00 X5.0938 Z1.0288

G32 X5.0938 Z-8.9912 F1

G01 X5.887 Z-9.65 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0299 pass 14)

G00 X5.0638 Z1.0115

G32 X5.0638 Z-9.0085 F1

G01 X5.887 Z-9.6922 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0289 pass 15)

G00 X5.0349 Z1.0282

G32 X5.0349 Z-8.9918 F1

G01 X5.887 Z-9.6995 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0279 pass 16)

G00 X5.007 Z1.0121

G32 X5.007 Z-9.0079 F1

G01 X5.887 Z-9.7388 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0271 pass 17)

G00 X4.9799 Z1.0277

G32 X4.9799 Z-8.9923 F1

G01 X5.887 Z-9.7457 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0263 pass 18)

G00 X4.9536 Z1.0126

G32 X4.9536 Z-9.0074 F1

G01 X5.887 Z-9.7827 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0256 pass 19)

G00 X4.928 Z1.0272

G32 X4.928 Z-8.9928 F1

G01 X5.887 Z-9.7892 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0249 pass 20)

G00 X4.9031 Z1.013

G32 X4.9031 Z-9.007 F1

G01 X5.887 Z-9.8242 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0243 pass 21)

G00 X4.8788 Z1.0269

G32 X4.8788 Z-8.9931 F1

G01 X5.887 Z-9.8305 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0237 pass 22)

G00 X4.8551 Z1.0133

G32 X4.8551 Z-9.0067 F1

G01 X5.887 Z-9.8638 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0232 pass 23)

G00 X4.8319 Z1.0266

G32 X4.8319 Z-8.9934 F1

G01 X5.887 Z-9.8698 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0227 pass 24)

G00 X4.8092 Z1.0136

G32 X4.8092 Z-9.0064 F1

G01 X5.887 Z-9.9016 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0222 pass 25)

G00 X4.787 Z1.0263

G32 X4.787 Z-8.9937 F1

G01 X5.887 Z-9.9073 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0218 pass 26)

G00 X4.7652 Z1.0138

G32 X4.7652 Z-9.0062 F1

G01 X5.887 Z-9.9379 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0214 pass 27)

G00 X4.7438 Z1.026

G32 X4.7438 Z-8.994 F1

G01 X5.887 Z-9.9434 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.021 pass 28)

G00 X4.7229 Z1.0141

G32 X4.7229 Z-9.0059 F1

G01 X5.887 Z-9.9728 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Decrement = 0.0206 pass 29)

G00 X4.7023 Z1.0258

G32 X4.7023 Z-8.9942 F1

G01 X5.887 Z-9.9782 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

(Last Pass ID_OD = 1)

(Decrement = 0.0193 pass 30)

G00 X4.683 Z1.0146

G32 X4.683 Z-9.0054 F1

G01 X5.887 Z-10.0063 F 1.5651249151426

G00 X5.987

G00 X5.987 Z2.02

G80

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 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.

---

[tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/
Pass increment anomoly

Status: open
Milestone: 1.0
Created: Fri Dec 29, 2017 07:04 PM UTC by Goatofmendez
Last Updated: Tue Jan 02, 2018 02:21 PM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Goatofmendez]

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] #9 Pass increment anomoly

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.

---

[tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/
Pass increment anomoly

Status: open
Milestone: 1.0
Created: Fri Dec 29, 2017 07:04 PM UTC by Goatofmendez
Last Updated: Tue Jan 02, 2018 02:21 PM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[stephanbrunker]

Partially good news: Now was able to reproduce the error. That means I can debug. I'll tell you if I found the cause.

[Goatofmendez]

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 PM UTC by Goatofmendez
Last Updated: Wed Jan 03, 2018 09:03 AM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[stephanbrunker]

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 to do and cutted on alternating sides of the tool. That should be obvious ...

However, I improve the documentation in the help and while debugging, I cleaned up the m1076 macro up more - you should have seen the original one. And about the crashes - the test mode is meant to expand the G76 line into a file with all the single lines and should be executed offline, which it does without crashes.

And I change the default value for the Extended Mode to true, which changes the Diag DROs on runtime to tell on which pass with which X depth you actually are.

[Goatofmendez]

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 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 to do and cutted on alternating sides of the
tool. That should be obvious ...

However, I improve the documentation in the help and while debugging, I
cleaned up the m1076 macro up more - you should have seen the original one.
And about the crashes - the test mode is meant to expand the G76 line into a
file with all the single lines and should be executed offline, which it does
without crashes.

And I change the default value for the Extended Mode to true, which changes
the Diag DROs on runtime to tell on which pass with which X depth you
actually are.

---

[tickets:#9] https://sourceforge.net/p/mach3threadinghelper/tickets/9/
Pass increment anomoly

Status: open
Milestone: 1.0
Created: Fri Dec 29, 2017 07:04 PM UTC by Goatofmendez
Last Updated: Wed Jan 03, 2018 08:30 PM UTC
Owner: nobody

Settings:
Sanvik type 1 in parameters and in mach3 turn options
"Diameter" turn mode in parameters and in mach 3.

When creating a thread (e.g. M6 x 1.0) I set the passes to 10
Pass Increment Depth
1 0.117 0.117 6 0.050 0.478
2 0.097 0.214 7 0.046 0.524
3 0.089 0.302 8 0.042 0.566
4 0.068 0.370 9 0.039 0.605
5 0.057 0.428 10 0.037 0.642

G21
G77 r XX x5.887 k0.0 z XX
G76 p1.0 r5.887 x4.603 h0.234 i29.5 k2.02 z-10.0 l360 q2

Yet when I run the G76 (above) it actually does 24 passes, I have tried
several other threads and it is always the same - approx 2.2x the pass
estimate in the program. Is there a setting I have missed somewhere that it
causing this to happen???

thanks

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/mach3threadinghelper/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[stephanbrunker]

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 pass. I don't know why ... . Both the app and the macro uses exactly the same formulas to get concurrent results.

As for testing, if you use a Smoothstepper and it is not on or not connected, you can use "Cancel" in the startup window (Cannot connect with ...) and then using Mach3 in a kind of demo mode which I used to debug the code. The test output works fine in that mode, because it only creates the code lines and doesn't execute them (the G32 lines would wait for the trigger). You can still run these ThreadTest.tap files later.

I added the m1176 macro call for two reasons: Internally, the complete macro gets compiled first like in test mode, but is being loaded into the execution buffer. Because of that, it will display only the last comment in brackets, not the actual one. The Extended=true option calls another macro out of the compiled code, which displays the pass number and increment on the command line and updates the DROs when it is executed (and not while compiling).