Epilog Laser Post Process Error

[george]

I'm trying to generate files for the Epilog Laser but the Post Process fails and just says to check the log files. I tried to search through some of the many files but I couldn't find any clues.

Where exactly do I look?

Here's a link to my project if someone wants to try and generate the file to see if you also get the error. http://a360.co/2oF7jB0

Thanks,

George

[paul.clauss · Accepted solution]

Hi @george

Thanks for posting! I was able to have a look at your file this morning and noticed that, without making any changes to your file, the post outputs an error noting the compensation type being used, as shown below:

Legal: Copyright (C) 2015-2016 by Autodesk, Inc.
Generated by: Fusion 360 CAM 2.0.2938
...
Width: 137.16
Height: 53.34
Error: Compensation in control is not supported.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error: Failed to execute configuration.
Stop time: Friday, April 14, 2017 6:41:23 PM
Post processing failed.

You can resolve this issue and get the program to post by changing the "Compensation Type" (in the Passes tab) to "In Computer." I have shown this in the screencast below.

Hopefully this helps! Please let me know if you have any questions - I am happy to continue troubleshooting.

[george]

Hi Paul,

Thanks for catching that. That always seems to default to in computer so I'm not sure why it's changed on these processes. What log file did I need to go to to find the detailed message? As a side note if possible it would have been nice to see this error written into the actual file.

Thanks,

George

[paul.clauss]

Hi @george

Thanks for the response! While I am unsure of which log you would need to look into to see the detailed error message, the error message shown in my screencast was brought up by simply posting the operations (before changing the compensation type) with the generic Epilog post and making sure that "Open NC file in editor" was enabled in the post process dialogue box. Because of the error, the post is unable to output its usual .html file and opens Brackets to display the more detailed error message shown in my last post.

Hopefully this helps! Please let me know if you have any questions.

[george]

I normally don't view my post processed files so I had that selection unchecked. Interesting that this information is only written to this file and not the actual file generated on your hard drive. That might be something worth changing in one of the future updates.

[paul.clauss]

Hi @george

Thanks for posting! The error message is actually seen on the file that is saved to your hard drive - the file opened by the NC editor is the post processed file that is saved on the hard drive. In most cases this file will be a .nc text file containing g-code. 

To clarify, the file being viewed when "Open NC file in Editor" is enabled is the actual file generated on your hard drive. The command simply opens the file after generating it.

In the case of the Epilog, the post processed file that will be sent to the machine is an .html file, but the error you were experiencing prevents the .html file from being generated. Because of this, the posted code that is opened in the editor is actually a .log file, saved locally to wherever you have set your output folder to be.  

Hopefully this helps! Please let me know if you have any questions.