@@cskovach stainless. 4140. Whatever you wanna do. Hard to find videos of anyone running a proven program in something other than aluminum with these. I work in 17-4 mostly. But I’m down for whatever you upload.
@@durangotang1681so far I’ve cut 1018, 316L, a little bit of 304 and some aluminum. I’ll try to put together some clips I have and get some material to do some more demos. In 316 I’ve done 220 SFM at .800” DOC with .025” stepover, around 50 IPM with a 5 flute bullnose which turned out to be a pretty conservative recipe. Didn’t push it too hard because I was trying not to scrap parts lol
You could use G53 coordinates instead of G56 so it use machine coordinate which stay always the same. Also you could use a macro loop that check elapsed time between start of the gcode to now to increment the spindle speed at predefined times while keeping the XYZ motion. Something like this, that increment the spindle base on a number of XY motion ( to be tried): G40 G49 G90 #1 = 0 N10 [IF #1 LT100] GOTO N20 [IF #1 EQ 100] GOTO N99 N20 G0 G53 X0 Y0 Z0 G0 G53 X max Y max Z min #1 = #1 + 1 [IF #1 EQ 20] GOTO N15 [IF #1 EQ 40] GOTO N25 [IF #1 EQ 60] GOTO N35 [IF #1 EQ 60] GOTO N45 GOTO N10 N15 S1500 M3 GOTO N10 N25 S4000 M3 GOTO N10 N35 S6000 M3 GOTO N10 N45 S8000 M3 GOTO N10 N99 #1=0 M2
I’ll give that a try. Looks like just a really basic loop counter which I didn’t even think about using. So then you would just vary the number of cycles for each spindle step to spend the desired amount of time at each speed. Makes sense. Thanks for taking the time to type all of that up, really appreciate it.
Thats so good to know! Does it give you options for hand jog resolution? For example, one "click" on the handwheel only moves "x" much? Like you mentioned, if your tool is .010" from the vise, will one click on the wheel move the travel by .001 or .010 or ?? The 22MA control looks better and better. Thank you for sharing!
Regular mpg mode functions that way. You can change the step resolution from .0001”, .001”, or .010”. I just tried it within that same program though and Mpg sim mode does not seem to respond to that, it moves the same step with each “click” of the wheel regardless of what you have the mpg resolution set on. Though you control the step size somewhat with the feed override. It could be how my program is written though. I need to investigate that.
I see. Thanks for the quick response. Do you think it works with other programs differently to make you think it has something to do the way you wrote the program? Please keep us posted on what you find out. Thank you. And subscribed! 👍
@@paulboon2285the reason I say that is you’ll notice I don’t define a feedrate for any of the axis motion in the program. It is operating based on the rapid feedrate override. I.e I start it down at 25% rapid, then ramp it up to 50% once 10 minutes or so have passed. I’m not an expert in g-code - barely have my feet under me in that aspect so I didn’t want to rule out the possibility of what you were asking about due to my own ignorance. If there’s anything else you want to see with the machine or the control let me know and I’ll try to demonstrate it to the best of my ability.
Thank you for putting this out there! I’m just getting started and don’t want to crash my machine. Appreciate you humbleness.
This is going to save some heartburns for me! Thank you!
That is a great tip! Thanks for the caution and sharing your solution. Definitely helps this guy. Many thanks Chuck.
Happy to help
Keep that sweet machining content coming. Can’t wait to see. Really considering the same setup including fourth axis
I’ll do my best! If there’s anything in particular you’d like to see let me know.
@@cskovach stainless. 4140. Whatever you wanna do. Hard to find videos of anyone running a proven program in something other than aluminum with these. I work in 17-4 mostly. But I’m down for whatever you upload.
@@durangotang1681so far I’ve cut 1018, 316L, a little bit of 304 and some aluminum. I’ll try to put together some clips I have and get some material to do some more demos.
In 316 I’ve done 220 SFM at .800” DOC with .025” stepover, around 50 IPM with a 5 flute bullnose which turned out to be a pretty conservative recipe. Didn’t push it too hard because I was trying not to scrap parts lol
@@cskovach that’s good to hear.
You could use G53 coordinates instead of G56 so it use machine coordinate which stay always the same. Also you could use a macro loop that check elapsed time between start of the gcode to now to increment the spindle speed at predefined times while keeping the XYZ motion.
Something like this, that increment the spindle base on a number of XY motion ( to be tried):
G40 G49 G90
#1 = 0
N10
[IF #1 LT100] GOTO N20
[IF #1 EQ 100] GOTO N99
N20
G0 G53 X0 Y0 Z0
G0 G53 X max Y max Z min
#1 = #1 + 1
[IF #1 EQ 20] GOTO N15
[IF #1 EQ 40] GOTO N25
[IF #1 EQ 60] GOTO N35
[IF #1 EQ 60] GOTO N45
GOTO N10
N15
S1500 M3
GOTO N10
N25
S4000 M3
GOTO N10
N35
S6000 M3
GOTO N10
N45
S8000 M3
GOTO N10
N99
#1=0
M2
I’ll give that a try. Looks like just a really basic loop counter which I didn’t even think about using. So then you would just vary the number of cycles for each spindle step to spend the desired amount of time at each speed. Makes sense.
Thanks for taking the time to type all of that up, really appreciate it.
Very cool.
Thats so good to know! Does it give you options for hand jog resolution? For example, one "click" on the handwheel only moves "x" much? Like you mentioned, if your tool is .010" from the vise, will one click on the wheel move the travel by .001 or .010 or ?? The 22MA control looks better and better. Thank you for sharing!
Regular mpg mode functions that way. You can change the step resolution from .0001”, .001”, or .010”.
I just tried it within that same program though and Mpg sim mode does not seem to respond to that, it moves the same step with each “click” of the wheel regardless of what you have the mpg resolution set on. Though you control the step size somewhat with the feed override.
It could be how my program is written though. I need to investigate that.
I see. Thanks for the quick response.
Do you think it works with other programs differently to make you think it has something to do the way you wrote the program?
Please keep us posted on what you find out. Thank you. And subscribed! 👍
@@paulboon2285the reason I say that is you’ll notice I don’t define a feedrate for any of the axis motion in the program. It is operating based on the rapid feedrate override. I.e I start it down at 25% rapid, then ramp it up to 50% once 10 minutes or so have passed.
I’m not an expert in g-code - barely have my feet under me in that aspect so I didn’t want to rule out the possibility of what you were asking about due to my own ignorance.
If there’s anything else you want to see with the machine or the control let me know and I’ll try to demonstrate it to the best of my ability.