I can't offer any info with the HX400iG but we have a HX800iLTGA that we're very happy with. We were looking at the HX250iG but that is on the back burner right now.

I use M98 or M198 in a while/do loop every day. M173 is either a M98 or M198 dependent on the need in my routers. I've not tried a G65 call with a M98/M198 but it should work. O5024 (4 PART CLUSTERTOWER FOR 2 PARTS ROUTER) (-0-) WHILE[#[#539+600+[1-1]]EQ1]DO1 (SURFACE 2) IF[#172EQ5101]GOTO211 IF[#172EQ5103]GOTO213 IF[#172EQ5104]GOTO211 #900=[#539+[1-1]] G91 G00 X0 G54 P[#900] G90 G00 B0. M#173 P[#170+2] GOTO211 END1 (-90-) N211 WHILE[#[#539+600+[1-1]]EQ1]DO1 (SURFACE 1) IF[#172EQ5102]GOTO312 IF[#172EQ5103]GOTO213 IF[#172EQ5106]GOTO213 #900=[#539+[1-1]] G91 G00 X0 G54 P[#900] G90 G00 B90. G201B90. G91 G00 X0 G59 M#173 P[#170+1] GOTO213 END1 N213 WHILE[#[#539+600+[2-1]]EQ1]DO1 (SURFACE 3) IF[#172EQ5101]GOTO411 IF[#172EQ5102]GOTO312 IF[#172EQ5105]GOTO312 #900=[#539+[2-1]] G91 G00 X0 G54 P[#900] G90 G00 B270. G201B270. G91 G00 X0 G59 M#173 P[#170+3] GOTO312 END1 (-180-) N312 WHILE[#[#539+600+[2-1]]EQ1]DO1 (SURFACE 2) IF[#172EQ5101]GOTO411 IF[#172EQ5103]GOTO413 IF[#172EQ5104]GOTO411 #900=[#539+[2-1]] G91 G00 X0 G54 P[#900] G90 G00 B0. M#173 P[#170+2] GOTO411 END1 (-270-) N411 WHILE[#[#539+600+[2-1]]EQ1]DO1 (SURFACE 1) IF[#172EQ5102]GOTO501 IF[#172EQ5103]GOTO413 IF[#172EQ5106]GOTO413 #900=[#539+[2-1]] G91 G00 X0 G54 P[#900] G90 G00 B90. G201B90. G91 G00 X0 G59 M#173 P[#170+1] GOTO413 END1 N413 WHILE[#[#539+600+[1-1]]EQ1]DO1 (SURFACE 3) IF[#172EQ5101]GOTO501 IF[#172EQ5102]GOTO501 IF[#172EQ5105]GOTO501 #900=[#539+[1-1]] G91 G00 X0 G54 P[#900] G90 G00 B270. G201B270. G91 G00 X0 G59 M#173 P[#170+3] GOTO501 END1 N501 M99 (----------START TOOL PATHS----------)

Here's how I create My work offsets and G-code after. We always use a probe to find offsets the first time around and then store them for future use on each machine. Work_vari is a variable for using either a 48 or 300 max_offset dependent on the machine_def. p36_5502 # two sided tombstone router sub_prg_no$ = 5502 " ", e$ sub_prg_no$ , "(WORK OFFSET CREATOR)",e$ "#1=0", e$ # accumulated X distance between parts per fixture "#2=0", e$ # accumulated y distance between parts per fixture "#11=", no_spc$, *work_vari, no_spc$, "-19", e$ # X fixture variable "#12=", no_spc$, *work_vari, no_spc$, "-18", e$ # y fixture variable "#13=", no_spc$, *work_vari, no_spc$, "-17", e$ # z fixture variable "#14=", no_spc$, *work_vari, no_spc$, "-16", e$ # b fixture variable "#15=0", e$ # B Work Axis "#16=0", e$ # parts counter "#17=0", e$ # fixture counter "#18=0", e$ # vertical parts counter "#19=" no_spc$, *multi_offset_no, e$ # vertical parts counter "N1WHILE[#15LE270]DO1", e$ "#[#11+[#539*20]]=#1", e$ "#[#12+[#539*20]]=#2", e$ "#[#13+[#539*20]]=#921", e$ "#[#14+[#539*20]]=#15", e$ "#16=#16+1", e$ "#18=#18+1", e$ "#11=#11+[#19*20]", e$ "#12=#12+[#19*20]", e$ "#13=#13+[#19*20]", e$ "#14=#14+[#19*20]", e$ "IF[#155GT#18]THEN#2=#2+#156", e$ "IF[#155EQ#18]GOTO2", e$ "END1",e$ "N2WHILE[#18EQ#155]DO1" e$ "IF[#154GT#16]THEN#1=#1+#157", e$ "IF[#154EQ#16]GOTO3", e$ "#2=0", e$ "#18=0", e$ "IF[#15LE270]GOTO1", e$ "END1", e$ "N3WHILE[#16EQ#154]DO1", e$ "#1=0", e$ "#2=0", e$ "#15=#15+180", e$ "#16=0", e$ "#18=0", e$ "IF[#15GT180]GOTO4", e$ "GOTO1",e$ "END1", e$ "N4", e$ O5502 (WORK OFFSET CLEARING) #1=0 #2=0 #11=7000-19 #12=7000-18 #13=7000-17 #14=7000-16 #15=0 #16=0 #17=0 #18=0 #19=1 N1WHILE[#15LE270]DO1 #[#11+[#539*20]]=#1 #[#12+[#539*20]]=#2 #[#13+[#539*20]]=#921 #[#14+[#539*20]]=#15 #16=#16+1 #18=#18+1 #11=#11+[#19*20] #12=#12+[#19*20] #13=#13+[#19*20] #14=#14+[#19*20] IF[#155GT#18]THEN#2=#2+#156 IF[#155EQ#18]GOTO2 END1 N2WHILE[#18EQ#155]DO1 IF[#154GT#16]THEN#1=#1+#157 IF[#154EQ#16]GOTO3 #2=0 #18=0 IF[#15LE270]GOTO1 END1 N3WHILE[#16EQ#154]DO1 #1=0 #2=0 #15=#15+180 #16=0 #18=0 IF[#15GT180]GOTO4 GOTO1 END1 N4 M99 Edit: Adding first tool (probe) N1 G91 G30 X0 Y0 Z0 G00 G17 G20 G40 G49 G64 G69 G80 G90 G94 M28 #153=1 WHILE[#910EQ1]DO1 IF[#1001NE1]GOTO99003 GOTO601 END1 WHILE[#910EQ2]DO1 IF[#1000NE1]GOTO99003 GOTO601 END1 N601 M06 T4 (OMP400 PROBE WITH 6MM X 100MM STYLUS) M117 T06 #154=1 #155=1 #156=0. #157=0. #170=4010 #172=5202 #173=98 #174=0 #198=0 #199=0 M98P5502(work offset creation sub call) M98P5036(parts router call) M05 G91 G30 X0 Y0 Z0 #153=#0 M01

The way I do this is to give a separate variable to every part and then use the variables as on/off switches. We base this for 64 parts max on each pallet. On pallet A the variables are #601, #602, #603, #604 --- #664. On pallet B they are #665, #666, #667 --- #728. We also use a macro program to turn on/off the variables if needed.

Do a compare between your 2017 and 2018 post. There may have been a hiccup.

Yeah, there's some real weight for our 800mm pallet platform. I know of one company that built a wood platform around a 800mm Mazak horizontal. I liked that platform better than our tread plate. It felt like it would be easier on the feet and knees.

Our fab shop did ours. You should have a few in your area. You're in trailer/rv country aren't you?

If an operator or setup person has to think about what offset to use then he is adding time to the setup. I have casting parts that have ten separate offsets to hold ±.005 on a ±.030 sand casting. The operators put the fixtures where I tell them, load the castings and push the button. They like it that way.

If you're using the NC4 then the edge checking macro is O9862. The broken tool detection (plunge checking) is macro O9863.

I only have one 2018 file because of that issue. The only way I could fix that problem was to rename the 2017 post folder or the entire 2017 folder. If you do that 2018 will say it couldn't find that post but "found one in your 2018 folder". Why can't Mastercam just do what the config file tells it to?

I get a lot of Mitsubishi that "stocks" in CA or Toronto, until I buy them. I was told it will be a while before there is a good variety of Hitachi tooling in CA a few months ago. I do like their variety though.

We had an Okuma salesman in here a while ago. While Our Supervisor was showing him our machines he was watching the salesman's reaction as they were walking by our Enshu's. I was told he had a funny look.

The last I've heard (6-7 years ago) was that Enshu made six models for Okuma. I think the MA-500 was one of them. We have three GE480Hs, three JE80Ss and three JE60Ss all 40 tapers. The GE480H machines have the 31i control. If Enshu had a 800mm pallet we probably would have one of them. They are very nice machines that just keep running.

My reseller gave me a post ref guide from V9 through X7 during the X7 rollout. I don't know if there is anything later. I haven't tried it yet but Code Expert may give you some help.

Don't face with sharp corner end mills. Also if you have to face use dynamic face climb cut making sure the flutes are cutting into the part especially around the corners to eliminate chipping. Edit: I was concerned about molybdenum on my first time but found it cut better than what the internet was saying.

The machining cloud uses my Novo name and password to log in.

I'm surprised that Sandvik is on the machining cloud. I was under the impression the Kennametal owned it.

600 IPM (15m?) seems slow for a Makino. I saw a Leblond Makino going faster than that at IMTS in either 1992 or 1994.

2018 was able to a couple days ago. I did a repair with no success. Is there something that I can fix?

You have to take the bad with the good. I haven't played with 2018 yet, but with going to the rollout there are many small changes that will overall make less operations to get the job done.

You can back them up to an external drive of some sort.

Is the non-stained area on this material where clamps were?

We had issues with 6061 when we were running full synthetic coolant (Castrol). We switched to oil soluble and haven't had a problem since.

Thanks gcode, This looks like the beginning of a Windows style update system. If it is I'm fine with it, just find a name to call it, stick with that name and update once a month.

The migration of this version has been a workout for some reason but now I have a couple templates made. My problem is if I want to update a part on an older MC version in 2018 the machine def defaults to the 2017 for the update and then states that it needs to update that machine/control. I tell it no and it loads the 2017 machine anyway. When I try to replace the machine by clicking the 2018 folder and pick the one I want it picks the 2017 one even though I'm not in that folder. If I rename the 2017 folder MC says that it can't find the file I'm looking for but it found a 2018 machine in the 2018 folder. I click ok (or whatever the response is supposed to be) and 2018 loads up. I've made a couple template files with this process and they load up correctly but we have thousands of files from V9 to 2017 that won't. It appears right now the only fix is to remove 2017 completely or rename the folder before loading a file and naming it back after. I haven't tried 2018 yet and I don't want to make a commitment until I'm comfortable with 2018. Has anyone else had this issue?