<?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: Bugs? in Fusion Support Forum</title>
    <link>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9866561#M98561</link>
    <description>&lt;P&gt;Hello Seth.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; If I post a setup file with the Anilam post it works fine and is executed by may lathe just fine , only the coolant does not turn on and off with the tool change. If I post the same setup file or any setup file with the CNC to VS code post it will fail at the last onclose function in the file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I have modified my lathe and Anilam post heavily to suit. I have no problem fixing the coolant if I can debug it with the CNC to VS code.&amp;nbsp; Even though it&amp;nbsp; seems to be a&amp;nbsp; change Auto Desk has made that has jacked it up. I have not had time or inclination to look at the CNC to VS code post to see if I can find some thing wrong. I figured that should be Auto Desks thing as everyone will use it and it should be maintained to their standards.&lt;/P&gt;&lt;P&gt;&amp;nbsp; If the Anilam lathe post is no longer available I think I have an original copy if anyone needs it.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Nov 2020 07:16:27 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2020-11-13T07:16:27Z</dc:date>
    <item>
      <title>Bugs?</title>
      <link>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9863108#M98559</link>
      <description>&lt;P&gt;I have found since the last update I have a few thing not working as they used to on my Anilam 4200T controlled lathe with a 8 tool turret .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Coolant turns on and stays on during tool change. I previously modified this so it turned off , changed tools and came back on before continuing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Looking into problem 1 in the post lead to problem 2. Posting with export cnc file to vs code fails at on section end for the last record , no matter how many operations are in the post.&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ce9178; font-weight: bold;"&gt;Error&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;:&amp;nbsp;Autodesk&amp;nbsp;HSM&amp;nbsp;Post&amp;nbsp;Processor&amp;nbsp;extension&amp;nbsp;not&amp;nbsp;found.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ce9178; font-weight: bold;"&gt;Error&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;&amp;nbsp;at&amp;nbsp;line:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #569cd6;"&gt;100&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #d4d4d4;"&gt;Failed&amp;nbsp;while&amp;nbsp;processing&amp;nbsp;onSectionEnd()&amp;nbsp;for&amp;nbsp;record&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #569cd6;"&gt;2751&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #d4d4d4;"&gt;###############################################################################&lt;/SPAN&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;SPAN style="color: #ce9178; font-weight: bold;"&gt;Error&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;:&amp;nbsp;Failed&amp;nbsp;to&amp;nbsp;invoke&amp;nbsp;function&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #ce9178;"&gt;'onClose'&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ce9178; font-weight: bold;"&gt;Error&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;:&amp;nbsp;Failed&amp;nbsp;to&amp;nbsp;invoke&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #ce9178;"&gt;'onClose'&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;&amp;nbsp;in&amp;nbsp;the&amp;nbsp;post&amp;nbsp;configuration.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #ce9178; font-weight: bold;"&gt;Error&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;:&amp;nbsp;Failed&amp;nbsp;to&amp;nbsp;execute&amp;nbsp;configuration.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #d4d4d4;"&gt;Stop&amp;nbsp;time:&amp;nbsp;Wednesday,&amp;nbsp;November&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #569cd6;"&gt;11&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #569cd6;"&gt;2020&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="color: #6a9955;"&gt;10:54:52&lt;/SPAN&gt;&lt;SPAN style="color: #d4d4d4;"&gt;&amp;nbsp;PM&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="color: #d4d4d4;"&gt;Post&amp;nbsp;processing&amp;nbsp;failed.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. I previously posted about the new Turning profile roughing and finish not have a safe Z retract option when inside profiling is selected. I did find a post that suggested turning on legacy tool paths to get around this.&lt;/P&gt;&lt;P&gt;You can put the legacy profiling strategy back on the menu by doing the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Solution -&amp;gt; type cam.f in the text prompt, click enter&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; check the option "old-turning-profile-strategy", click close&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Personally I still prefer the old strategies.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2020 23:19:50 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9863108#M98559</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-11-11T23:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: Bugs?</title>
      <link>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9865569#M98560</link>
      <description>&lt;P&gt;I'm not seeing an Anilam lathe post in the HSM Post Library. Can you share it here, along with a sample file?&lt;BR /&gt;File &amp;gt; Export &amp;gt; Save to local folder. Take that .f3d file and your .cps post file and dump them into a .zip folder and share that here, if you don't mind&lt;/P&gt;</description>
      <pubDate>Thu, 12 Nov 2020 19:10:39 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9865569#M98560</guid>
      <dc:creator>seth.madore</dc:creator>
      <dc:date>2020-11-12T19:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: Bugs?</title>
      <link>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9866561#M98561</link>
      <description>&lt;P&gt;Hello Seth.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; If I post a setup file with the Anilam post it works fine and is executed by may lathe just fine , only the coolant does not turn on and off with the tool change. If I post the same setup file or any setup file with the CNC to VS code post it will fail at the last onclose function in the file.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I have modified my lathe and Anilam post heavily to suit. I have no problem fixing the coolant if I can debug it with the CNC to VS code.&amp;nbsp; Even though it&amp;nbsp; seems to be a&amp;nbsp; change Auto Desk has made that has jacked it up. I have not had time or inclination to look at the CNC to VS code post to see if I can find some thing wrong. I figured that should be Auto Desks thing as everyone will use it and it should be maintained to their standards.&lt;/P&gt;&lt;P&gt;&amp;nbsp; If the Anilam lathe post is no longer available I think I have an original copy if anyone needs it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2020 07:16:27 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/fusion-support-forum/bugs/m-p/9866561#M98561</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-11-13T07:16:27Z</dc:date>
    </item>
  </channel>
</rss>

