what happened to the Haas pre-ngc post processor?

[TLJFab]

Need help after fusion update. my post processor is gone and there is not a haas pre-ngc anymore. Problem is multiple wcs is limited to g54 through g59, then it goes to g154 part 1 part 2 ect ect. My pre ngc does NOT use g154 part 1 ect ect. I have g54 through g59, and G110 through g129 which i use frequently, now im limited to g54-g59 only. Really???I can only run 4 parts at a time now??? Update messed up everything. 

[engineguy]

@TLJFab 

It is still there in the Library, was only updated 2 days ago so up to date, go to  https://cam.autodesk.com/hsmposts?

[TLJFab]

Thank you for that, unfortunately it doesn't help my issue. I thought it was the post processor, but might be wrong. For the life of me I cannot seem to figure this one out. My issue is when I do a set up with multiple wcs, the available locations are g54 through g59 then it goes to extended wcs g154 part 1, part 2, ect. which my vf4 does not recognize.

 My vf4 has G54 through G59, and G110 through G129. Previously, I could post to all of these, but now it only allows g54-G59. How do I get it back to what I had before this change? Ive tried changing the selected machine and post processor but when I run the post, it still uses g54-g59, BUT then jumps to g154 part#'s which errors my vf4 immediately and says invalid g code on the controller.

 Even when I try to post an old saved file that I used for 8 wcs locations and worked fine, now, they don't work as it only post to g154 part#'s ect ect. Please see attached post for reference. G54-G59 are fine but then it jumps to G154 which is the problem.

[engineguy · Accepted solution]

@TLJFab 

Try downloading the latest HAAS Pre NGC Post Processor and open it in your Text Editor (I use Visual Studio but Notepad will do just fine) and go to the section shown in theimage below and change the G154 to G110 and that should hopefully then output the G110 P* for you.

P.S. Just tested it and I get the correct G110 P* being posted if I have the "Multiple WCS" enabled in the Setup.

.nc file attached.

[engineguy · Accepted solution]

@TLJFab 

Just some additional information for you if you don`t already know it, if you keep your Post Processor in the Post Processor "Installed Library" then if you also have the "Automatic Post and Machine" updates enabled in your "Preferences" then the Post Processor WILL be overwritten during any updates if the Post Processor is updated in the HSM Library.

Always best to keep your good working Post Processor in your "Personal Post Library" and use it from there, or even your "Cloud Posts",  then if you want to leave the "Automatic Updates" enabled in your "Preferences" you will always have the latest Post Processor available to refer to now and again, might be something that if of use to you in there 🙂

It is also best practice to save your good working PP .cps file in a folder somewhere on your computer so tah if you have a problem in the future you can easily copy/paste the good one back into your PP library 🙂 🙂 🙂

[TLJFab]

Can't thank you enough!!!! Worked pretty much as you instructed except i had to edit the post to show this:And 

Then set my set up WCS to show this:

Posted out to Visual Studio and verified all is PERFECT!

THANK YOU AGAIN,

time to make some chips!

[TLJFab]

will do for sure. I thought that it was saved to my library, but upon your advice looked into it, and yep your spot on, it was being updated which is what caused my issue. Thank you very much

[dbmatt76]

Hello all,

The above correction for a "Standard" range of 54-59 and an "Extended" range of 110-129 makes sense and is something that I also changed.

However, is there a syntax that will let you have your cake and eat it too for having the full range selectable? IE 54-59 AND 110-129 as a selectable range. So if you wanted to leverage all 26 work offsets in a setup, you could still say to start with G54, tell it that you want 26 instances, incrementing the count by one and still have it play nice when skipping the boundary from 59 to 110. 54 would be instance 1, 59 would be instance 6, and 110 would be instance 7 in that list.

I'd love to just add a 3rd option after Standard and Extended to be "All" with this crossover list. I've tried a few syntax guesses with multiple number ranges separated with &&, ||, and some regular expressions with no luck, but that could be bad syntax on my part rather than just not being possible.

Any thoughts?

Thanks!