Can simulate. Cannot post.

Can simulate. Cannot post.

jcamve
Advocate Advocate
663 Views
7 Replies
Message 1 of 8

Can simulate. Cannot post.

jcamve
Advocate
Advocate

I am not so new to Fusion  but I have no one to teach me down here but you tutorials and the old trial and error method.

I have the same problem I have read about in this thread. In posting I get a message advising me that there is a machine configuration error that does not allow posting. The orientation lines with the "1" inserted that I have seen in one of the posts do not appear in my machine after the update. I am using a Mach3 post processor.

Thanks for any reply.

Julio.

0 Likes
Accepted solutions (1)
664 Views
7 Replies
Replies (7)
Message 2 of 8

Anonymous
Not applicable

I have no clue as to what exactly your issue is but if I was to guess from content of your post, I'd say define your setup correctly and don't use machine configuration.

Some issues have been reported related to machine configuration and if you do your work on same machine, chances are you'll never need it.

0 Likes
Message 3 of 8

jcamve
Advocate
Advocate

I thank you for your note. My issue is that even though I can simulate a job on posting the process I get a warning stating a machine configuration error that impedes posting. In reviewing similar issues I noticed that in one event a fellow reported that one additional line appeared in the machine configuration pages related to axes orientations with a number "1" already inserted in every axis box. The issuing party states he removed these numbers from the box that did not belong to the axis being configured and everything went well.  However one reply stated that this new line was an error in a Fusion update that would be corrected.

I just tried a wood engraving job and am attaching the report I got. Please note the CAM kernel error mentioned.

 

Warning: Tool length is larger than supported for this machine.
Enabled feature flags: machine-configuration
Debug: Initialization elapsed time: 1 ms
Debug: Writing ironjob to C:\Users\Julio\AppData\Local\Temp\Fusion360CAM\1\operation27.ironjob
Debug: Writing jobfile to C:\Users\Julio\AppData\Local\Temp\Fusion360CAM\1\operation27.hsm-job
Debug: Using CAM kernel from: C:\Users\Julio\AppData\Local\Autodesk\webdeploy\production\39ae3be83754e11319952e5fb0373ee11dd09c95\Applications\CAM360\camkernel.exe
Error: Internal CAM kernel error. Please report through your support channel.
Debug:
Debug: Total processing time: 296 ms
Debug: Total elapsed time: 396 ms

 

Any other further note will be appreciated.

Julio.

0 Likes
Message 4 of 8

jcamve
Advocate
Advocate
0 Likes
Message 5 of 8

seth.madore
Community Manager
Community Manager

Can you export and share your Fusion file?
File > Export > Save to local folder. Return to thread and attach the .f3d file in your reply. If you'd rather not post the file publicly, you can PM me the A360 link, referencing this thread so I know what's going on.


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 6 of 8

Anonymous
Not applicable
Accepted solution

Point I was trying to make is not to debug the machine configuration but instead question whether or not you actually need it, it seems to be in early stage of development and has issues.

There are users that need to post same file for different machines, so they need those machines to be correctly configured and machine configuration itself needs to be bug free for concept to work.

If all your work is done on same machine, for all practical purposes, you can just ignore it and get on with making parts.

Subsequently, if the machine configuration does work, it can be used in simulation to uncover potential crash issue not visible in simulating tool path alone.

For instance, you can have fixture, bolts and other obstacles to avoid where simulating crash costs nothing as opposed to having to determine danger of crash as you run the tool and make chips, but it is still theoretical assumption based on all things being correctly interpreted.

 

In my view, dry running program in machine is trustworthy step before making a single cut, while machine simulation can save you time, one wrong variable in its configuration and simulation process can cost you a bundle if you trust it without dry running program and physically ensuring crash free run.

At this stage, I have no use for machine configuration in any of my Fusion files. 

Message 7 of 8

jcamve
Advocate
Advocate

I will try running a simulation without the  machine configuration and see if it woks. Will come back and let you know. Thanks a lot for your time.

Julio.

0 Likes
Message 8 of 8

jcamve
Advocate
Advocate

The problem is no longer. Nevertheless, accept my thanks for your kindness.

0 Likes