In the attached template file there are logic expressions in the @CYCLCHG
section that will re-evaluate #XPOS, #YPOS, #ZPOS, #XCTR, #YCTR, #XCTR,
#XHOME, #YHOME, #ZHOME, #ZCHK, #PECK and #CLEAR prior to their output and
round their value to the nearest half thousandth.

=============================================
 Fred Lauzus, CAM Programming Coordinator
 High Steel Structures, Incorporated
 mailto:[EMAIL PROTECTED] http://www.highsteel.com
=============================================
 



-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 9:12 AM
To: [EMAIL PROTECTED]
Subject: RE: [mfg-smartcam] G-code output


Apparently SMF question #21 suppresses output moves of less than the
assigned value and does not round the value to an the nearest even
increment. 

============================================= 
 Fred Lauzus, CAM Programming Coordinator 
 High Steel Structures, Incorporated 
  mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
http://www.highsteel.com <http://www.highsteel.com/>  
============================================= 
  

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 25, 2002 6:15 PM
To: [EMAIL PROTECTED]
Subject: [mfg-smartcam] G-code output


Hi all,
 
When smf question #21 is set to .0005" the g-code should post in .0005"
increments. Yet when I post, my g-code is still being produced with .0001"
increments.
Can anyone help with this? Am I missing an additional setting somewhere?
I need to try .0005" increments to trouble shoot a re-occurring error in our
Proto Trak MX2 toolroom mill controls.
 
Thanks in advance.
   
 Chris Kocourek
Tool Design Engineer
FLEXTRONICS

 

Attachment: m_fanuc.tmp
Description: Binary data

Reply via email to