G95 / G94 in properties.menu

G95 / G94 in properties.menu

mbTRAAF
Contributor Contributor
1,302 Views
10 Replies
Message 1 of 11

G95 / G94 in properties.menu

mbTRAAF
Contributor
Contributor

Good morning all,

 

unfortunately our Mazak postprocessor lacks the possibility to switch between G94 and G95.

I have seen on various Fanuc postprocessors that there is the possibility to choose.

Could someone help us do this?

0 Likes
Accepted solutions (2)
1,303 Views
10 Replies
Replies (10)
Message 2 of 11

boopathi.sivakumar
Autodesk
Autodesk

@mbTRAAF 

I think you can copy and paste the codes from fanuc it will work 

just all you need to do is find useG95 in the fanuc post and you have copy and paste the codes in mazak  in the same location.

You can use the vs code to make the edit easier

https://forums.autodesk.com/t5/hsm-post-processor-forum/technical-faq/td-p/7473258 

The above link will help you some of the contents before you need to edit

If you have problems with the modified post just poke here

 


Boopathi Sivakumar
Senior Technology Consultant

0 Likes
Message 3 of 11

mbTRAAF
Contributor
Contributor

Hi there,

since Fanuc and Mazak are not exactly the same, I think it won't work that way.
I copied all entries except for the G95 in rigid tapping.
Rigid tapping should be with Mazak G84.3 & G84.2 ......

I attached the changed post as requested!
Unfortunately it doesn't work that way ........
Should you make an answer to this contribution, I would like to ask you to use the above postprocessor as a template.

I would be very happy about answers .....

 

0 Likes
Message 4 of 11

mbTRAAF
Contributor
Contributor

in a quiet minute I managed it now.
Now I have found that the feeds are unfortunately not entered in the parameter feeds.

An error message is thrown out that the machine does not support this.

The machine drives this without problems.

I would be grateful for support

0 Likes
Message 5 of 11

boopathi.sivakumar
Autodesk
Autodesk
Accepted solution

@mbTRAAF 

This is because at the moment it won't support the both but you can do some tweaks to make it work

go this place and block it

  } 
  // if (properties.useG95 && properties.useParametricFeed) {
  //   error(localize("Parametric feed is not supported when using G95."));
  //   return;
  // }
  if (properties.useG95) {

this is line which is throwing the error

and in the function getFeed(f) add change something like this below

function getFeed(f) {
  if (properties.useG95&& !properties.useParametricFeed) {
    return feedOutput.format(f / spindleSpeed); // use feed value
  }
  if (activeMovements) {

and in the 

function initializeActiveFeeds() at the end made some changes like this
  for (var i = 0; i < activeFeeds.length; ++i) {
    var feedContext = activeFeeds[i];
    if(properties.useG95){
      writeBlock("#" + (firstFeedParameter + feedContext.id) + "=" + feedFormat.format(feedContext.feed/spindleSpeed), formatComment(feedContext.description));
    }else{
      writeBlock("#" + (firstFeedParameter + feedContext.id) + "=" + feedFormat.format(feedContext.feed), formatComment(feedContext.description));
    }
  }
}
var currentWorkPlaneABC = undefined;
function forceWorkPlane() {
  currentWorkPlaneABC = undefined;
}
Save and test the file carefully

Boopathi Sivakumar
Senior Technology Consultant

0 Likes
Message 6 of 11

mbTRAAF
Contributor
Contributor

Thanks for the quick answer !!!!

0 Likes
Message 7 of 11

mbTRAAF
Contributor
Contributor

 

Hi Mr. Boopathi,

 

Unfortunately there is still a mistake in the postprocessor.

This is already available in the post processor of the first article.

 

And he just throws me a parameter feed (# ...) or F ...... feed.

According to the programs, there are several that have to be called up.

It does not matter whether parameter feed or G95 is activated in the properties menu or not Enclosed the currently

adapted post processor.

 

 

0 Likes
Message 8 of 11

mbTRAAF
Contributor
Contributor
Thanks for the PM,
 
and apologize that I'm only now reporting.
So the problem that exists is this:
Only one feed is written out in both parameter and normal feed output (F). (See program 1000)
However, several feeds are called up in the program and these should also remain available. (# 101, # 102, # 103 ect. See also F - feeds)
Now I would like to ask that these be output as in Program 2000.
 
Many thanks
0 Likes
Message 9 of 11

mbTRAAF
Contributor
Contributor

Here are the Programms.

0 Likes
Message 10 of 11

boopathi.sivakumar
Autodesk
Autodesk
Accepted solution

@mbTRAAF 

You have removed the this line

  var feedContext = activeFeeds[i]
While copy pasting things
go this section by searching
var currentWorkPlaneABC = undefined;
and add the line in red your final code will be like this 
  for (var i = 0; i < activeFeeds.length; ++i) {
    var feedContext = activeFeeds[i];
    if(properties.useG95){
      writeBlock("#" + (firstFeedParameter + feedContext.id) + "=" + feedFormat.format(feedContext.feed/spindleSpeed), formatComment(feedContext.description));
    }else{
      writeBlock("#" + (firstFeedParameter + feedContext.id) + "=" + feedFormat.format(feedContext.feed), formatComment(feedContext.description));
    }
  }
} 
var currentWorkPlaneABC = undefined;
It will work now
 

Boopathi Sivakumar
Senior Technology Consultant

Message 11 of 11

mbTRAAF
Contributor
Contributor
Thank you very much for your effort and your patience
0 Likes