Generic Post Process Error after Update

Generic Post Process Error after Update

livewireweldingllc
Explorer Explorer
481 Views
2 Replies
Message 1 of 3

Generic Post Process Error after Update

livewireweldingllc
Explorer
Explorer

Hello, I am running Fusion 360 on a Mac and have been for years. Recently updated to the latest version of Fusion 10.14.6. and am having frustrating problems.

 

I have been using the RS-274D/rs274 generic post processor with no issues on thousands of files.  When I would normally post a program I could name it in the post process box that pops up, and when I clicked ok it would open the computers directory and I could choose where to save it and it would already have the file name I created.   Once save it would be listed as the file name and then .NC. In my computer directory under file type it just said document.

 

Now this is where the problem lies after an update.  I post process like normal, using the RS-274D and when I put in the file name and hit ok it brings me to the computer directory where the file will be saved just like normal, except there is no file name, it did not transfer.  This would be the least of my worries but once the post is saved in a file it does not have the .NC after it. When looking in the computer directory under file type it no longer says "document" like it normally does, it says Unix Executable.  I didn't notice this to be a problem until I put the USB in the machine and it wasn't recognizing any of the posted files.

 

To trouble shoot things further I posted an old known good tool path just like normal and ran into the same issue where it wasn't saving as a .NC and wasn't recognizable by the cnc machine. I also took an old saved .NC file known to work and it opened and ran on the machine without issue.

 

I have also tried posting with GBRL and Rich Auto (since that's my controller type just always used the RS-274D. Either way I ran into the same issue every time where I did not get a good file to run on the machine.

 

Attached is a sample file if anyone else needs this for trouble shooting. I have also attached a good working file CAB1.NC. I tried to attach a sample of a bad posted file but it won't attach and says file type not supported.

 

I have delt with Fusion crashes and bugs before but this has been the worst for me yet and I would greatly appreciate any help.

 

I just found the weirdest work around! Its a huge pain but it worked to get the job done for today.  Example: created new sub folder named TEST, saved posted named 123 inside this folder. As expected the post is no good because of the problem I am having.  I then post the same thing but this time save the post with the same name as the folder "TEST".  When saved in the same parent directory as the "TEST" folder I get prompted that my file name already exists and get asked if I would like to replace it with my new file. I click yes replace. Everything is done, then I check the directory.  Where my "TEST" folder was is now another folder auto created named "TEST.bak" but the original "TEST" folder is also still there and inside it is the post I named TEST and it shows up as TEST.NC like I am used to seeing.  Just ran it on the machine and it works just like its supposed to.

 

I tried to post like I normally would before all this and I was back to the original issue, so I did not solve anything just found a work around to at least keep me making money! Again any help would be great but I truly believe this is a Fusion program error not an operator error.

 

0 Likes
Accepted solutions (1)
482 Views
2 Replies
Replies (2)
Message 2 of 3

seth.madore
Community Manager
Community Manager
Accepted solution

Yes, this is a known issue currently being looked at. For know, you're going to have to type the file name and follow it with a ".nc"


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 3

livewireweldingllc
Explorer
Explorer

Wow thanks that appears to work, will try on the machine in the morning.  I did not realize simply adding the .nc made a difference it how it recognized the file. Good to know there is a real fix on the way!

0 Likes