<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Post drill cycle output help in Manufacturing (CAM)</title>
    <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325252#M221</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks For the input everybody.&amp;nbsp; I'm currently reaching out to some other resources here in the company, and i'll try to update this thread on any good outcome.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Nov 2016 17:07:00 GMT</pubDate>
    <dc:creator>imiller</dc:creator>
    <dc:date>2016-11-04T17:07:00Z</dc:date>
    <item>
      <title>Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325247#M216</link>
      <description>Hello all,I'm transitioning to Creo Manufacturing and having a few problems with my post processing.&amp;nbsp; Here is the main issue:The controller I am using is an Anilam 6000M.When I post-process a CL file for drilling, I get this as an output:G81 X-4.1791 Y-2.5 Z-.0709 R.0787 F.138X4.1791Y0.X-4.1791Y2.5X4.1791G80I</description>
      <pubDate>Sun, 13 Dec 2020 18:37:14 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325247#M216</guid>
      <dc:creator>imiller</dc:creator>
      <dc:date>2020-12-13T18:37:14Z</dc:date>
    </item>
    <item>
      <title>Re: Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325248#M217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I thought there would be a setting in the NC Post Processor part of the program, the one that loads the "Java Option File Generator". I was wrong, there isn't anything there, that I could see, which would do what you wish.&lt;/P&gt;&lt;P&gt;This likely means you will have to do some FIL code stuff to handle DRILL, PECK, etc. CYCLES. I've not had the pleasure of handling this type of operation, with the exception of some time calculations, and am not sure of the intricacies of doing so. It's possible, but I think I'd want to make sure that any of the common variables that would normally be set by a CYCLE are correctly handled. Tricky.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2016 17:14:21 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325248#M217</guid>
      <dc:creator>KenFarley</dc:creator>
      <dc:date>2016-11-03T17:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325249#M218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Your cycle CL data is in couplet form so you can use POSTF(28) and POSTF(29). These functions locate and remove couplets and words, so you may grab the values you need and build the G code line. There will be a bit of coding involved to account for different types of cycles and to output the XY values.&lt;/P&gt;&lt;P&gt;ex:&lt;/P&gt;&lt;P&gt; FRTIDX=POSTF(28,3,(ICODEF(IPM)))&lt;/P&gt;&lt;P&gt;IF(FRTIDX.NE.0)THEN&lt;/P&gt;&lt;P&gt; FEDCUR=POSTF(7,(FRTIDX+1))&lt;/P&gt;&lt;P&gt;ENDIF&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from FIL we use to get the feed rate if in IPM from a cycle. There are GPOST and FIL manual somewhere in you CREO installation or you can order them hardcopy from AustinNC. If you need a lot of post help contacting them would be a good idea. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Josh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2016 22:01:06 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325249#M218</guid>
      <dc:creator>joshuataylor</dc:creator>
      <dc:date>2016-11-03T22:01:06Z</dc:date>
    </item>
    <item>
      <title>Re: Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325250#M219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ken is correct that there is no option for this in the Option File Generator.&amp;nbsp; It can leave out the XY on the G8x block if it is modal but not add it to the next block.&amp;nbsp; This will need to be done in the FIL file and the best option is to use the _OUTPT macro to edit the existing tape block.&amp;nbsp; If you are not familiar with FIL and/or this macro it will be difficult. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2016 14:15:34 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325250#M219</guid>
      <dc:creator>AustinN.C.,Inc.</dc:creator>
      <dc:date>2016-11-04T14:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325251#M220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah.&lt;/P&gt;&lt;P&gt;My big concern is that the drilling cycles are modal:&lt;/P&gt;&lt;P&gt;* The initial CYCLE/ DRILL sets the drilling mode "on"&lt;/P&gt;&lt;P&gt;* Subsequent "GOTO" lines just output the new X, Y (and possibly Z) coordinates. &lt;/P&gt;&lt;P&gt;* A final CYCLE/ OFF (?) turns "off" the drilling mode&lt;/P&gt;&lt;P&gt;You'd have to be sure to handle all the different types of drilling cycles (DRILL, PECK, REAM, etc) as well as the accompanying GOTO positions.&lt;/P&gt;&lt;P&gt;It's possible, just not something that can be quickly written here. I'd need to do a lot of testing to be confident I had it right.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2016 17:04:05 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325251#M220</guid>
      <dc:creator>KenFarley</dc:creator>
      <dc:date>2016-11-04T17:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Post drill cycle output help</title>
      <link>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325252#M221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks For the input everybody.&amp;nbsp; I'm currently reaching out to some other resources here in the company, and i'll try to update this thread on any good outcome.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Nov 2016 17:07:00 GMT</pubDate>
      <guid>https://www.ptcusercommunity.com/t5/Manufacturing-CAM/Post-drill-cycle-output-help/m-p/325252#M221</guid>
      <dc:creator>imiller</dc:creator>
      <dc:date>2016-11-04T17:07:00Z</dc:date>
    </item>
  </channel>
</rss>

