output feedrate in a section

[Anonymous]

Does anyone have an example of getting Feedrate
early in a section?

I tried something like

var F = cycle.feedrate;    
write(feedOutput.format(F));

also
var F = getMaximumFeedrate();
write (feedOutput.format(F);

the answer is
F = currentSection.getMaximumFeedrate(); // need to handle as a object.method

Hope this helps someone else...

[fonsecr]

Not sure what you are actually trying to do but you would likely often want to get a particular feedrate and not just the minimum or maximum feedrate.

You can check out the parametric feed feature. See "useFeedQ" for the generic Heidenhain post. This shows how to get the feedrate in use before the corresponding toolpath is processed.

[Anonymous]

Rene,

I am most impressed with your monitoring of the
Forum. I am getting more impressed with HSMWorks
software pretty much on the hour.

I will try to go through the mentioned resource.

Actually I was trying to pull various feedrates out
to use in the script. The one I mentioned was the
only one that worked so far. My specific one was
the Down Feed Rate. Is this itemized out somehwere?

If I purchase the software does it come with a ready
to go Hurco VM2 post for 3D or will I have to keep
modifying as I have been? We have the ISNC option
on the unit.

thank you for the excellent service...
Adam

[fonsecr]

The generic HURCO post has an option to switch between ISO NC mode and Basic mode. The generic posts might work out of the box but often further customization can be required. The reseller would normally be able to provide you with the desired post.

[fonsecr]

One thing to note is that all parameters in the user interface are accessible from the post processor.

This means that you can get any feedrate you would like to use in the post.

Here is an example:
http://forum.hsmworks.com/index.php?topic=53.msg156#msg156

The primary cutting feed can be accessed using the getParameter("operation:tool_feedCutting"). You can see all parameters available simply be using the "dump.cps" post. This will output a text file listing all information transferred to the post processor.

[Anonymous]

Did the dump.cps and looked at output.

  F = getParameter("operation:tool_feedPlunge");
  writeBlock(feedOutput.format(F));

getParameter() works pretty nice.

How do you pull out various pieces of different
operations. Is there a "cycle ID" that allows you
to know what the difference is between
feedcutting,feedEntry,feedRamp,feedPlunge,feedRetract
by the Cycle?

Didn't quite understand the Q thing yet but I need to
read the posts some more.

thanks for all the help, its working

[fonsecr]

You can scan through all operations (called sections in the post processor) and access all the parameters. Check out the Section class in the post processor manual included with the installation.

Code could look something like this:

var mySection = getSection(mySectionIndex);
if (mySection.hasParameter("myparam")) {
  var value = mySection.getParameter("myparam");
  // use it here
}

You can differentiate the operation strategies using the parameter called "operation-strategy".

[4nonCa00D]

This helped me a lot, thanks!