The chuck was to be machined facing upwards.
I normally use raster x-y for work but last night I though I would try some of the other options to get a feel for what they do.
Roughing command was the first option (can't remember what that was here at home will update here)
The finishing command I used spiral as it looked to be the most logical from the little picture.
After lots of messing about with over travel alerts due to the program being written to go negative on the x command to machine the whole block I got it to run.
It completed a lot of the program but then hung/crashed (needed task manager to kill VR5) at the same place twice. Given issues I have had with VR5 in the past with this I decided to run the program in VR2. VR2 came up with an error when the cutter was in the same position as in VR5 and this is where there is a G19 in the code. A quick google told me what G19 (G18 & G17) are for but why is it crashing on this?
My only assumption is that QuickCAM 3D, VR 5 and newer machines understand G19. So when it is post processing it is creating a program which contains commands that the Micromill 2000 machines don't understand. This is why VR5 is crashing mid program as the micromill doesn't understand what the command is and hangs. However VR2 is a bit more intelligent and gives a report that it doesn't understand it.
Shouldn't VR5 take into account the limitations of the machine it is producing the code for and use commands that it understands or is there something else going wrong.
I have attached all the G code files I did last night, the last one almost ran to the end but I had to stop it as the Micromill lost position with 300lines of code left to run

Feedback Please
Pete