1) Because I'm cutting FibreLAM panels, I'm cutting with an oscillating Z depth to avoid burning the bit. MasterCAM can automatically add a linear oscillation, something that resembles /\/\, or a high speed curve like a Sine curve. Either way results in very abrupt movements because even though it's in CV mode and no longer rounds my corners, it's treating both the linear and the High Speed oscillations as Exact Stop on each line of code. How do I set Mach3 so that I get perfectly square corners and yet don't end up with Exact Stop style movements.
2) Unfortunately because I had to get a panel cut, once the nested series of parts didn't work I simply overworte that code with a single part at a time program, so the original code doesn't exist, but MasterCAM and the Mach 3 screen both showed the correct movement, but once the parts were being cut, the router ignored a Z move to out above the panel and so when it did a rapid to the next slot it ripped right through the parts and then went back to business as usual. In fact it cut the rest of the slots and then the outside edge of each panel without any further incident. What on earth would cause a machine to ignore a line of code clearly visible on the screen? I'll try to recreate that program in MasterCAM.
3) And yesterday after I made the changes to the auto zero in the homing limits, I discovered the hard way that the table would go right past the limit switches and hit the physical end of the track. But it was rather random, sometimes it would pick them up as normal and other times it would pass right by.
I did find out some interesting things from this router table company that is helping me over the phone. He knew that my stepper motors lose all torque past a certain rpm so I needed to keep my feed speeds down to compensate. He knew what values should be in the step pulse and direction pulse in the motor tuning. I have to give him all the details on my table's movement gears and tracks and the Z screwgear and he's going to calculate exact steps per pulse for me.
EDIT: I can't remember the size of the piece of material I had that gave me the nesting layout that cause the issue, but here's the NC code for a single part. the table clearly ignored a move exactly as line N300, then it ran line N310, which ripped through the part, then it may or may not have ignored the Z.1 move before continuing merrily on its way cutting all the other slots and edges.