Any thoughts about an issue I am having with my Elite Journeyman. I was trying to carve a simple inscription which I broke down into three toolpaths to try understand what is going wrong. The first is the text carved with a 60 degree V-Groove bit (Amana 45705). The board blank had already been secured with tape/CA glue. Next installed a 1/8 inch end-mill for probing, ensured the bit diameter in the probing dialog was set correctly. Next probed x/y and then Z and homed the machine. Machine went home and then to toolsetter clicked the toolsetter and rested. Next changed to bit to the V-Groove, re-probed the Z and homed/toolsetter again. Loaded the text toolpath and clicked rewind twice (some video had recommended this) then clicked cycle start. The targeted engraving depth was 0.2 but the machine then goes to the correct start position and drives the bit close to 1/2 inch into the workpiece before I could hit the emergency stop, ruining the workpiece (again). Then installed new workpiece, re-probed the Z, re-homed, re-clicked the toolsetter, rewound the program and clicked cycle start. The carve then proceeded correctly and finished correctly. The next carve was the outlining with the same bit but I did re-probe the Z and re-homed it before starting the cycle. The cycle ran correctly. The final part was a two-part toolpath with a 1/8 inch endmill finishing with a 1/16 inch endmill. Installed the 1/8 inch endmill and re-probed the Z, re-homed with toolsetter and clicked cycle start. The machine sent the bit to the correct carve point but was trying to carve well above the workpiece surface (could have been at the safe Z) so stopped the cycle (not with the Emergency stop). Then re-probed the Z re-homed with toolsetter and clicked cycle start. The carve then continued correctly, changing to the 1/16 bit when required and completed correctly.
This is not the first time I have seen this but it has taken some time to record the sequence accurately. I have questioned OneFinity support and they just say this it is me not homing the machine correctly. Another question I have is that is there any way to read what the first cut Z value is going to be? If you have managed to read this long post do you have any ideas what is happening?
I had this exact same issue. You need to home only once when you turn on your machine, unless you get a hard error, in which case you need to home again.
There are gremlins in the MASO PLC logic, I’ve all kinds of weird stuff happen.
Home first, then x,y,z your work piece and it’ll start working as you expect 
David,
I agree with KSR, that is way too many homing sequences. I only home once on start up and that is with the last bit still installed so that the touch probe can satisfy itself. Make sure you never change a bit unless the Masso directs you to (that includes shutdown and restart, and loading new tool paths) or you will have further problems. I don’t usually set the X,Y, and Z with the touch block on the materials until after the bit called for in the file is installed and touched off, I hit the red stop button on front and then use the block. Once X, Y, and Z are zeroed, then I just hit the rewind and cycle start.
Now this becomes more puzzling. When asking OneFinity/Masso support folks they were very specific that the system should be homed which includes a trip to the Tool-Setter After the XYZ probing was performed every time. I did start doing this with some improvements but not a solution.
I think the confusion is the way Masso does its tool setter height offset. I’ve seen a few posts here and it seems to be an issue that a few users have.
Per the Masso doc, the tool in the spindle when homed & touched off is the one that sets the reference tool height (ie tells the control were the tool setter height is), from there with the same tool in the spindle you set the Z-zero for you part setup. It then knows what the height dif is between the setter and the part.
If you install a different tool in the spindle and rehome/touch off it messes things up.
To change a tool(after the initial homing) you MUST go to MDI and do a TxxM6.
It might be good practice and the end of the day to do an MDI T1M6(or a tool u keep the same all the time) always using the same tool to set the tool setter offset.
I think JR is on to something here.
I’ve had 3 of these mishaps since installing the ATC and I think its because I’ve been using the “Sync” and “Load” commands to control the tool in the spindle. The behavior is a little hinky because I’ve used the Load subroutine before a job to load the first bit in the job then done the XYZ probing and STILL had it prompt me for a bit change at the start of the job.
I haven’t found the definitive pattern that causes it nor have I developed a fail-safe to prevent it. One thing, though, is that it only happens on the first bit of the job so that’s the one to watch like a hawk…if it makes it through the initial cut with that one, the remaining bit changes are uneventful.
Craig