Post processing error all of a sudden - Feed Rate Optimization Results in Cut Speed of Zero

Just following up on this because I have the Post Processor changed I just haven’t gotten around to testing it thoroughly yet. It’s effectively just one line changed that solves the PS error that occurs. I’ll include a link here: https://drive.google.com/file/d/1B5BL_NWpSuMvd63agygBzkZmpqAFiuae/view?usp=sharing

Fairly certain that this change should solve most issues that you’re seeing with Feed Optimization. Let me know if y’all find any issues or it doesn’t work as intended. Hopefully can get this tested soon and up on the website so people don’t need to dig in the forum.

2 Likes

Zachary, thank you for taking the time. I did a quick test and it did not work for me but I did not test it on the actual enclosure. (Note: I am using a Langmuir Forum member’s FireControl program mod.)

I may have done something wrong but this is the design I cut. The largest hole is 0.48 inches. The cut path is yellow so it is slowing down for these cuts:

I processed this first with the Post Processor v1.6 and my mock-up on my desktop showed the expected error and he does have the expected final notation of “(PS0)”

No surprise there.


Now, I used the 1.7 Post processor and the gcode shows the same thing “(PS0)” at the end of the code file.

The mock-up is still showing the same error.

TestNew PostProcessor16.nc (1.2 KB)

TestNew PostProcesser w17used.nc (1.5 KB)

2 Likes

Can also add, downloaded post processor and tested a .875 circle with smoothing and feed optimization. Had the same result with no cut speed.

Am I missing something here? I use feed optimization every single day without a hitch. I’ve been on version 1.6 for years.

It only happens if you are cutting a solid circle, I was cutting out filler plugs to weld into a truck frame. It cut without issue when optimization and smoothing turned off.

1 Like

I understand now. Sounds like a Fusion issue. I will try it tomorrow morning and report back.

This is the current easiest solution. Make your standard feed rate for that particular cut the same feed rate as you would for feet optimization and no error will occur.

2 Likes

The issue is the Post Processor only checks for Cutting moves and not also Reduced movement.

There is 2 lines that need to be changed. Line 463 and line 517 for FireControl-v1.6.cps.

This line

if(getMovement() == MOVEMENT_CUTTING && feed > maxCuttingFeedRate){

needs changed to

if((getMovement() == MOVEMENT_CUTTING || getMovement() == MOVEMENT_REDUCED) && feed > maxCuttingFeedRate){
5 Likes

Here’s a file for those that want to test but not mess with editing the file.

Zipped cause we can’t attach a cps file.

FRO-Edit-FireControl-v1.6.cps.zip (4.7 KB)

5 Likes

@Muddr, you posted post processor definitely worked thru that issue.

Here are the last few lines of my test file:

And it loaded into FireControl just fine:

5 Likes

@Muddr is smart. He knows things…

Well done!

2 Likes