Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

YoDoug®

Verified Members
  • Posts

    1,309
  • Joined

  • Last visited

  • Days Won

    45

Posts posted by YoDoug®

  1. One thing about the mill/turn product

    It is machine specific

    If CNC does not have your machine built yet, you are out of luck

    I would love to try mill/turn out on our Okuma YB1200 VTM, but Mastercam does

    not have mill/turn for that model Given it's tiny user base ( less than a dozen in the US), it's unlikely it ever will be

    supported by mill/turn

    The first thing to do before getting excited about the mill/turn module is to make sure

    your machine is supported.

     

    That's a bummer. That's why I like Esprit for MTM. They cover just about every machine out there. They have a full time employee at Okuma, Mazak, Mori, and a few of the swiss makers that just do machine sim and post support. When a new Okuma comes out we have a simulation in days. Posts are not far behind. 

  2. I have a question about the G41 lead in on an Okuma OSP P300 control. If you use a straight 90 degree move on the G41 line to activate the cutter compensation and then cut a straight line and comp out at 90 degrees it will cut the straight line at an angle equal to whatever the tool has been adjusted to like it is activating the comp across the whole length of the line after the G41. We asked Okuma if this is a parameter issue and they said that you always have to program with a two axis move on the G41 line and it has always been that way. This is not an issue on any of our other machines as far as I know. Any one else ever encounter this? 

     

    Yes I have seen it and it is not always evident. In Mastercam I always do a line into arc lead-in type.

    • Like 2
  3. Doug,

     

    You'd be doing yourself a favor by getting a copy of the Renishaw Prod+ Configuration Utility. You can modify the RenMF file to use any range of variable numbers you want. Then the output doesn't step on your existing macros.

     

    Again, that's part of the reason they "default" to outputting everything. That way Renishaw ensures that you are first setting all the values in the correct variables, then using those variable values inside the measuring routine macros.

     

    Another advantage for users with limited memory is that by including the Macros being called as subroutines, you are using the most limited amount of memory possible. For example, if you are only probing a single surface, and a bore, you only need the "protected move macro", "single surface measure", "4 point bore/boss", and the "calibration" macros. You don't have to load all the "unused" macros.

     

    Obviously users that have the full Inspection Plus package would just want to call their "standard" macro calls. (I say "their standard", because Renishaw sells different levels of the Inspection Plus software, so it is possible you might have different macro program numbers for "your particular installation".)

     

    Colin, no need for the config utility. A little over ten years ago we purchased Productivity+ at a job I was at. It was version 1.01. They said we we may have been the first US company to purchase it. I spent a lot of time with Renishaw software people working out posts and software bugs. I got to know the posts, or at least the non encrypted part, very well. There was a lot less functionality back then. The software has come a long way. anyways, we do edit the RenMF file to non conflicting variables now that we know, but we still prefer our Okuma touch setting routines over the Ren GUI. 

    • Like 1
  4. I'm not sure about other controls but in Okuma mills I run the standard inspection plus calibration routines through the Renishaw GUI at the machine. Then I am calibrated and good to go for both Ren GUI probing and the Productivity+. We did however find there is a variable conflict between the in process calculation variable numbers and the Renishaw tool setting software variables for calibration. If we run a productivity + routine it overwrites the location of the touch setter. However, we normally don't set customers up with the Renishaw tool setting because we have our own macros that use the Okuma gauging software for tool setting that require less input from the operator. 

  5. I don't understand why the mastercam inspection plus plugin wants you to calibrate and use a different set of variables than the inspection plus already int he machine. IMO this does nothing other than complicate the process and increase the risk of an accident.

     

    It's the same macro numbers for calibration variables. In addition to the regular 4 point inspection plus calibration routine you need to run the inspection plus vector calibration routine. That is probably the data that is missing. 

  6. I use macros quite a lot. If there is a repetitive operation that needs to happen and I can get it down to one command, I'll do it. The key is having it well documented. I have them for attachment changes on a double coulmn, coord. rotation for RAH, angle hole drilling "canned cycles", and so on.

    I have a library I keep adding to and try to keep a similar writing process through them all.

     

    I made one the other day for a family of parts. The program is now able to make the 40+ parts by updating six variables.

     

    Once again the key is documentation. It is very important that you or anyone else can read the macro a year after it has been written and understand the basic use and function (I put a sample of how to use it at the top of the file). Also it is important that you can read the logic easily for when revisions/edits are required. The final thing is the idiot proofing. Make sure there are all the appropriate safety checks in place.

     

    +1 to proper documentation

     

    I will just add that I have always kept a spreadsheet of to keep track of macros. The spreadsheet contained columns for macro numbers, description, etc. The rows contains variables used in the macro. This way you can filter columns to easily check for variable conflicts and compatibility from machine to machine. 

    • Like 2
  7. Hi All,

     

    For those with Okuma mills, Below is the fix for the spindle tool commanded in program error. This fix will work for U100 E100 and P200 machines. It may also work on older ones but O have not tried them.

     

     

    Ok, Save the following text as tool.lib

     

     

    OTCK (GET NOMINATED TOOL)

    IF [PT EQ EMPTY] NERR

    IF [PT EQ VTLCN] NEND

    IF [PT EQ VNTOL] NM6

    IF [VNTOL EQ 0] NCT

    M64

    NCT T=PT

    NM6 M6

    NEND G56 H=PT D=PT

    GOTO NRTS

    NERR M63

    M6

    NRTS RTS

     

    ONOT1(M201)

    M63

    M329

    M06

    RTS

     

    ONOT2(M202)

    M64

    M63

    M329

    M06

    RTS

     

     

    Copy this tool.lib file to MD1 directory of the machine.

     

    If the buffer has been set large enough all will be sweet, If not you will need to initalize the buffer and reset it to a binary number (say 4800)

    If in doubt miss this step

     

    Turn off all power

     

    Restart Machine - Note if there are any lib registration errors, If there are none all is good if there are *lib errors see previous step

     

    Go to Parameters G and M codes

     

    Next to G116 set OTCK

     

    Save, Yes very important

     

    On a new P200 control you will need to register the *.lib file. From Run mode, press extend then Register lib files

     

     

    OK now G code needs to look like this

     

    Blah Blah

    G116 T4

    G00 X0 Y0 Blah Blah

     

    So if T4 is in the spindle the program will continue with no errors if not the machine will go and get T4 then continue. This will also work thru DNC-DT

     

    Hope this helps someone graemlins/cheers.gif

     

    For P300 machines change the VNTOL to VTLCN. It will eliminate alarms if the tool is designated as heavy or large tool. It also will address alarms with tool numbers greater than 999.

    • Like 1
  8. The G116 only works if you have the "tool change macro", I've seen very few machines with the macro.

    The macro is nothing more than a .sub file with the VATOL logic.

     

    There are switches in our master based posts, not sure what you are using as a base post.

     

    To add this in is fairly easy.

     

    You need to initilize the variables we are using:

    tno     : "0"

    stooln : ""

    strn     : "N" 

    str1     : "1"

     

     

    The code I attached earlier will replace your M06 call out, could be in ptlchg, psof ect... depending on base post.

     

    I would suggest using VTLCN instead of VATOL. VATOL is a system variable that is a 16 bit binary that includes tool data besides the tool number. Bit 0-9 are for tool number. Bit 10-15 are for attributes, large tool, etc. VTLCN is just the tool number only.

  9. Gentlemen,

     

    Something isn't adding up ...........................................................................................E1600 mill/turn.  

    Preface:  I'm an Esprit guy until we made the switch to MCam.  

     

    I want to know what Mcam salesman was able to go into a shop with an E1600 and convince them to dump Esprit and switch to Mcam. That guy could sell snowblowers in hell !!!

    • Like 6
  10. Below is a slide from an Okuma presentation on Navi M-i. It is not the greatest image but it shows where the machine adjusts spindle speed from 3500 rpm to 3712 rpm to eliminate the chatter shown in the graph. This is done real time and will update as cutting conditions change, tool wear, part geometry changes, etc. You can set parameters and boundaries on how much adjustment can be made and save that data to the tool info. Now I will say it is not a magic bullet. It can make small adjustments to make small to moderate gains in performance. It is still subject to the laws of physics though and it will not make a poor setup or process into a good one.

    post-13170-0-50878300-1443536988_thumb.jpg

  11. Colin, Have you seen a first hand demo of Okuma Navi M-i. It uses vibration sensors to adjust the spindle speed by slight amounts to counter act the chatter from the harmonics of the flutes striking the material. It is a very robust solution with many parameters that can be set to control the outcome. 

  12. Just a few thoughts on this. 

     

    1. Not all vibration sensing options from MTB's only slow down the speed. Some will speed up slightly if applicable. Okuma's machine Navi M-i will adjust the rpm as needed to reduce the vibration sensed in the spindle. It does not change the feedrate so you do not see a cycle time change. 

     

    2. Unless the machine is a fixed table adding a vibration into the table would take ever constantly changing servo tuning parameters. MTB's put a lot of effort into tuning out servo vibration because of the ill effects. 

    • Like 1

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...