Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
andrewJ5JUW
in reply to: jaredSADUH

Just a further update on this issue.

 

I got some time between other jobs to dry run the G-code.

 

I am happy to say the code ran faultlessly end to end with no unexpected or spurious moves.

I then created some additional tool paths this time calling up multiple tools and performing facing, 2D profiling and 2D pocketing commands. Again - these dry ran 100mm or so above the bed without any issues.

 

So at this point although I have not actually cut metal with the code so I can't say if the tool paths are producing accurate results I am confident enough now to try machining some first test parts using F360 created code rather than code I have programmed on the mill using the Siemens ShopMill on the control.

 

This setting also allows Tool names to be as per the text in F360 e.g - 80mm face mill in F360 is fine and comes out as "T1" (80mm face mill). The tool name in the Tool List on the machine must match letter letter though. Easy enough to do. 

 

In summary - if you have an 828D control, and you use the F360 post that is published on their library for the 840D control (which is recommended by F360 when I raised the issue with them during a test drive before purchase) - don't leave the field for "Safe Retracts and Home Positioning" as "SUPA" - change it to "Clearance Height" and the code will run without alarming. Also - set the "Tool as name" check box as ticked so the control recognizes tool names correctly AND make sure the tool list on the machine matches exactly what the tool library name in F360 is - letter for letter.

 

Lastly proceed with caution - I have dry run this only.