I just got a new machine and reloaded fusion 360 , i cant get it to post a complete setup getting error ,but will post iindividually with no problem

[drwd...@gmail.com]

What am I missing , worked properly before the new PC

Thanks Wayne

[Q Rothing]

Hi Wayne,

If you could post or email me a screenshot of the error you are receiving I would be happy to try to help! 

Thanks,

Q Rothing (qrot...@pocketnc.com)

Applications Engineer, Pocket NC

[drwd...@gmail.com]

Information: Configuration: Pocket NC
Information: Vendor: Pocket NC
Information: Posting intermediate data to 'C:\Users\12267\Documents\NC programs\1001.ngc'
Information: Total number of warnings: 4
Error: Failed to post process. See below for details.
...
Code page changed to '1252 (ANSI - Latin I)'
Start time: Sunday, June 16, 2019 5:30:51 PM
Loading locale from 'C:\Users\12267\AppData\Local\Autodesk\webdeploy\production\0b5dbc3659d50d942194174a776e4172a7ae70fc\Applications\CAM360\Data\Posts\common.en.lang'
Warning: function getProgramNameAsInt does not always return a value
Warning: function getProgramNameAsInt does not always return a value
Warning: function getProgramNameAsString does not always return a value
Code page changed to '20127 (US-ASCII)'
Post processor engine: 4.3.0 45221
Configuration path: C:\Users\12267\AppData\Local\Autodesk\webdeploy\production\0b5dbc3659d50d942194174a776e4172a7ae70fc\Applications\CAM360\Data\Posts\pocket nc.cps
Include paths: C:\Users\12267\AppData\Local\Autodesk\webdeploy\production\0b5dbc3659d50d942194174a776e4172a7ae70fc\Applications\CAM360\Data\Posts
Configuration modification date: Saturday, May 25, 2019 8:16:55 PM
Output path: C:\Users\12267\Documents\NC programs\1001.ngc
Checksum of intermediate NC data: ba89802e7cf7c1fb52da3d9d2c49f16d
Checksum of configuration: b492dd50f67284110d712dd8f0fd04ea
Vendor url: http://www.pocketnc.com/
Legal: Copyright (C) 2012-2019 by Autodesk, Inc.
Generated by: Fusion 360 CAM 2.0.5827
...
Warning: Work offset has not been specified. Using G54 as WCS.

###############################################################################
Error: Work plane is not supported: A-180. B90.
Error at line: 635
Error in operation: 'Adaptive1 (2)'
Failed while processing onSection() for record 17011.
###############################################################################

Error: Failed to invoke function 'onSection'.
Error: Failed to invoke 'onSection' in the post configuration.
Error: Failed to execute configuration.
Stop time: Sunday, June 16, 2019 5:30:51 PM
Post processing failed.

This is the message screen, its weird because each op posts individually
only when I try to post multiple ops or whole setup do I get the error

Thanks for looking at it

Wayne

[Q Rothing]

Thanks for posting that, Wayne. We do occasionally see that behavior. Do you see the line that says "Error in operation: 'Adaptive1 (2)'? Normally, the operation that is listed on that line has something wrong with it and won't post even by itself. That is is what I would normally guess is happening to you since the line "Error: Work plane is not supported: A-180. B90" suggests you are trying to have the machine move to an A coordinate that is not possible on the machine (A axis negative limit is -25 degrees). But, you said that all of the operations post fine individually so that changes things. Moving forward, I would try suppressing that operation and see if that allows you to post the rest of the setup as one. If that works, you may need to rebuild that operation from scratch to make sure there are no glitches with it. It is also possible that that move is not possible from the machine's previous position so you could try reordering the operations as well.

These are the usual culprits and fixes of this problem. Let me know what you end up with and I can try to help you from there if need be!

Thanks!

Q 

[drwd...@gmail.com]

Yes it is weird, each op posts individually,and when I suppress (2),it still wont post, with error in (3),but when I suppress both (2) and (3) it posts remainder.

It appears that the move from A(90) to A(0) is the cause of the error but only when B is +/- 90 , it is happening in more than one program so I suspect a post error? strangely none of the code calls for a move beyond A limits when they post individually

[Q Rothing]

Hmm that is strange. Based on what I know, I would agree, it is either a post issue or it has to do with the order in which you have your operations built. This may be something that you have to reach out to Autodesk about. If you would like me to keep looking into it you can email me your Fusion file and I can see if anything jumps out at me.