How do i remove G94 call showing up on my post process

[hgmyr]

I'm working with a Haas V2 machine and I need to manually remove the G94 code on my post process.  I'm looking for a solution so I don't have to keep manually deleting this each time i post.  Thanks.

[Steinwerks]

Just curious, but why does it need removal?

[hgmyr]

When running the program on the Haas we are getting an error with the G94/G95 call. Our Haas VF-2 machine does not support IPR/MMPR feed units for milling.

[AchimN]

If you are using the generic HAAS post, there is a piece of code like this:

  // absolute coordinates and feed per min
  writeBlock(gAbsIncModal.format(90), gFeedModeModal.format(94), gPlaneModal.format(17));

Just delete the G94 command so the code has to be this:

// absolute coordinates and feed per min
  writeBlock(gAbsIncModal.format(90), gPlaneModal.format(17));

[hgmyr]

Achim, this worked for me.  Thank you!

[AchimN]

Excellent, thanks for your feedback!

[Anonymous]

I have been searching high and low for answer for this problem. Our older Haas VF-1 throws a 301 Error Code because of G94. Now I just need to find out how to edit the code, Lol. Thank you Very Much!

[ANDERSONRODANDCHOPPER]

AchimN,

I located this section of code in my processor and it is set up exactly how you recommend above with the g94 portion removed.   However,   The post continues to have G94 in it.  I have o manually delete it in brackets so I wont alarm out on the Haas.   My Machine is a 1995 VF2.  

thank you,

Josh

[jrenw]

How do you get to what you posted to edit it, I've looked all over trying to figure it out. Would love not to have to open every post in an editor just to remove the G94

Randy

[gulliver22K55SX]

The post processor has numerous G94 instances.  If  you remove the very first instance as mentioned, then it just inserts a G94 further down into the resulting post and causes an error.  I tried removing every instance, and then it couldnt compile.  Further help is needed please.

[james.stoddart]

In my post process config, I located and deleted the 

 gFeedModeModal.format(94),

 Instead of posting at the start processes, the G94 posts before my first G1 move. Is there a way to fix this?

[gulliver22K55SX]

So, I found a fix to turn off the G94, by accident.  You can download and use the "Haas with 4th axis" (even if you dont have a 4th axis).  Set it as your default post processor, and then turn on "Rotary moves use IPM feeds".  When this is enabled, the G94 will not be included in your post anymore.

Btw, if you have the optional Haas programable coolant, there's a bug in the post processor and a fix for that as well.

[james.stoddart]

As well, this line would need to be removed. If you are still having issues, then use find feature to search 94 and see if you can break down where the issues are.

function onOpen() {
if (properties.useDPMFeeds) {
gFeedModeModal.format(94);

}

If you are using the generic HAAS post, there is a piece of code like this:

  // absolute coordinates and feed per min
  writeBlock(gAbsIncModal.format(90), gFeedModeModal.format(94), gPlaneModal.format(17));

Just delete the G94 command so the code has to be this:

// absolute coordinates and feed per min
  writeBlock(gAbsIncModal.format(90), gPlaneModal.format(17));

. 

[billcainautodesk]

You can also just put a line in onOpen before the first G94. What this will do is make the 94 active without outputting it because there is not a writeBloack or writeln. That way the rest of the G94's should not come out because of modality. 

  gFeedModeModal.format(94);

[james.stoddart]

So I would delete the if (properties.useDPMFeeds) before the {gFeedModeModal.format(94);}? If not, could you provide an example of the lines of code needed to initiate this command?

Thank you,

James Stoddart

[billcainautodesk]

I don't think your in the right place. In function onOpen add the line below.

if ((getNumberOfSections() > 0) && (getSection(0).workOffset == 0)) {
for (var i = 0; i < getNumberOfSections(); ++i) {
if (getSection(i).workOffset > 0) {
error(localize("Using multiple work offsets is not possible if the initial work offset is 0."));
return;
}
}
}
gFeedModeModal.format(94);
// absolute coordinates and feed per min
writeBlock(gAbsIncModal.format(90), gFeedModeModal.format(94), gPlaneModal.format(17));

switch (unit) {
case IN:
writeBlock(gUnitModal.format(20));
break;
case MM:
writeBlock(gUnitModal.format(21));
break;
}

[gulliver22K55SX]

Good news, Bob Schultz has modified the pre-ngc post processor to do two things:

1. get rid of the g94
2. insert two m8's if you have Programmable coolant and check the box for such.  Reason for two is it will get the coolant going, and it will put another after the height offset so the programmable coolant is set correctly.  If it did just the latter, the coolant might not be flowing by the time metal is starting to be cut.

It should be posted in the post processor downloads soon.