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

Thanks for your reply.

 

I was not very clear in my last reply. What I meant to say was that the g-code ran on the machine - meaning the programme started (rather than alarming out),  the spindle came up from where it was positioned and did a tool change, it selected the 80mm face mill (T1) - which is correct and as programmed , the spindle started and rapid down started - again as programmed.

 

I then purposely stopped the programme using "Cycle Stop" as my objective at that point was just to test whether the g-code would actually run lines without alarming out - I was not attempting to actually carry out the facing operation as the job was not even set up in the vice. It was Sunday and I was out of time.

 

Later this week I plan to actually set up a block in the vice and see if the code can perform the facing operation as intended. At this point all I know is the g-code with the different post processor settings actually runs where as when I logged  this thread I could not get it to run without alarming out. I don't yet know whether the cutter will go where it is supposed to.

 

I spoke with Siemens Tech support today and but no useful or actionable information was provided. I tried to get clarity whether changing the post setting from SUPA to "Retract Position" might have any un-desired effects but they could not tell me.

 

So I think cautiously testing the code on in a dry run with a large Z offset and reduced feed / speed is probably the way to go and see if it behaves as programmed / expected.