Post Processing issues

[Anonymous]

There was an update a few days ago and at that time post processor would not work at all.

I had an update installed today and post processing visually works, but every .nc file is 277kb. I view it in candle and it "looks" normal but when loaded into the cnc nothing happens when the job is started. Also progress starts at 33%

I eliminated machine issue by loading an old .nc into it and it started to run fine, what's going on and what can I do?

[seth.madore]

What post processor are you using, and can you share your Fusion file?
Can you also share an old .nc program so we can compare outputs?

File > Export > Save to local folder, return to thread and attach the .f3d file in your reply

[Anonymous]

I'm post processing in grbl, i dont currently have my laptop and can
probably only grab the .nc files through onedrive, but ill do the export
this evening and post.

[Anonymous]

Here's a .nc that works, and one that doesn't ill label them, as well as the F3D.

[Anonymous]

Messed around with it last night with no changed results.

[seth.madore]

On the file that does NOT work, try removing the comments about the personal use limitations:

(When using Fusion 360 for Personal Use, the feedrate of)
(rapid moves is reduced to match the feedrate of cutting)
(moves, which can increase machining time. Unrestricted rapid)
(moves are available with a Fusion 360 Subscription.)

Those are 63 characters long, but your old file is only 61. That "may" be the issue. I thought we addressed the line length...🤔

[Anonymous]

Alright, I'll try that shortly

[Anonymous]

Removing that does fix the sitting idle issue, but it gets stuck after the first function, ie. Does the countour, then sits idle and does not move to the pocket. I removed the contour and started with the pocket and it did not continue to the last contour. So still some issues. 

[seth.madore]

It posts that out at each toolpath, I believe. Does it occur later on?

[Anonymous]

Yes it stops qhwn going to a new function, ill search the file and see if
it occurs later in the script.