Bill Craven

  • Content count

  • Joined

  • Last visited

  • Days Won


Bill Craven last won the day on February 28

Bill Craven had the most liked content!

Community Reputation

78 Excellent

About Bill Craven

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,715 profile views
  1. Bill Craven

    Tool Inspection for Generic Lathe Post

    Below is some of the modifications that I have made to my generic lathe post. Maybe someone will find it useful. I have incorporated logic so that the post will output all of the information needed to do a complete restart even after hitting the reset button on the control. My basic lathe post outputs block numbers based upon the Operation number from Mastercam. In combination with my setup sheets, the operator can restart the program from the beginning of almost any operation (if force tool change is checked) Inside the roughing operation that has the tool inspection turned on, I have reinitialized the block numbers so that for that roughing operation the block numbers will start at N1, but will revert back to the block numbers matching the Operation number. I added a comment so that the operation number can be verified by the operator I also have logic in this post so that the turret will rotate up or down by a variable in the post so that the operator can easily access the insert and inspect and change it if needed. As posted: Here is the code from the post: ptool_insp #Tool inspection point #Modify following lines to customize output for tool inspection points if posttype$ = two, #Lathe tool inspection point [ n_insp = n_insp + 1, "(TOOL INSPECTION POINT)", e$ "G28 U0", e$ "G28 W0", e$ pturinsp if prmcode$ = 29999, #Only output tool insp comment if one was entered with this insp point sparameter$ = ucase(sparameter$) *e$ #blank line *e$ *e$ pbld, n$, *sm00, "(", sparameter$, ")", e$ *e$ *n_insp, "( BLOCK NUMBER FOR RESTART INSIDE OP ", *op_no, ") ", e$ !spaces$ spaces$ = zero scomm_str, sopcomm, scomm_end, e$ *e$ *e$ *e$ pbld, n$, "G0" *toolno, e$ #Restate tool number pbld, n$, pfsgplane, e$ #Restate plane code prpm, pfspindle_l, e$ # pspindle , e$ # Output programmed RPM #Restate spindle pcss, e$ pbld, n$, "G99 ", e$ *Scoolantx, e$ prv_feed = c9k #Set prv_values to c9k to force them out with next moves prv_gcode$ = c9k prv_workofs$ = c9k if coolant$, prv_coolant$ = c9k ] else, #Mill tool inspection point pbld, n$, *sm00, "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$ pturinsp tur_insp = (t$ + tur_insp_no) * 100 if tur_insp_no > 0, [ if tur_insp >= tur_loc, tur_insp = tur_insp - tur_loc *tur_insp, e$ else, *tur_insp, e$ ] else, [ if tur_insp <= zero , tur_insp = tur_insp + tur_loc *tur_insp, e$ else, *tur_insp, e$ ] There are several variables that need to be initialized. If the tur_insp_no is minus, the turret will rotate up, if it is positive the turret will rotate down.
  2. I believe what Mr. guru was referring to is: There were cases where Active Reports would take a long time to generate a report. 30 minutes or more. From what I recall it had something to do with min/max values. Ah, I found it. From the tips and tricks Word doc: Processing Time When any MIN or MAX values are in the report, the BNCI file must be searched, which takes longer. Cycle time also takes time, but not as much. With a large file or lots of operations selected, the report can take a very long time to run (15-30 minutes in some cases). I haven't run into this problem and I have run reports with over a hundred operations. X+ is blazingly fast. A great utility. I still use it to check for coolant conditions and other things, but I need the polish and detail with 1 click that Active reports gives me when I am generating the documentation for turnkeys for customers. Regards, Bill
  3. I agree. I was spending as much time documenting things for the setup sheets and tool lists as I was programming. Then, if I had to make a change, I would have to go back and fix my documentation. My current setup sheets are basically a one click and done, with the exception of Viewsheet screen shots for WCS setup, chuck jaw, etc. detail. A lot of times I will setup my laptop at the machine and work with the operator and see how I can make his job easier, safer, and more efficient. I feel the same way about making my post processors generate code that requires no hand edits. I recently developed a post that outputs block numbers that match the operation numbers, so a machinist can look my setup sheet, find which operation they want to run or re-run and then search for that block number. I worked as a machinist many years ago where the programmer's nickname was: "I think I got it right this time, Bob" - Not so much fun - Did you ever look at the Active Report templates that I posted back on February 23rd? (Funky text colors in the link below, click on the "Free Active Reports Setup Sheet") I like looking at how other people do things and try to learn from everything I see.
  4. Great job Steve! Active Reports is very powerful, but is not very friendly to learn. The other part of that is that once you have a report template done, you might not need to make any changes for a year or more, and when you go back the learning curve starts
  5. I was unable to open your file. It gave me an error message. Try this: Bind the full data XML file to the report. Then select the xml file with full data from the secret handshake. Then find the field that you want to include in your report. Then drag and drop that field onto your report. Note the path is included Try running your report without the conditional statement and see if it displays. Once you get that displaying correctly, then start working on the script. I am not very familiar with the scripting for Active reports. It looks like you have not defined txtIsFinishTool.Text correctly.
  6. The short answer: The long answer is to use the "secret handshake" to output all data to the XML file. From the Active Reports Tips and Tricks Word Doc available from Mastercam (i've attached it here) Mastercam does not output all of the data about a toolpath to the XML file. Mastercam looks at the RPX report file and only outputs the data that is being called for those reports. The "secret handshake" forces the output of all data to the XML file. ActiveReports Tips-Tricks.docx
  7. Bill Craven

    Looking for MasterCAM Skill testing.

    Yeah, I call them Nintendo programmers. It's not that they are not smart, they just lack the experience.
  8. Bill Craven

    SolidWorks - Mastercam Add-on

    I like this word.
  9. Bill Craven

    Setup sheet images

    Click on the add Geometry button and then you can select a solid model of the part (and fixtures) as well as lines and arcs and drafting notes. The geometry and models that you select will be captured for each operation with the outline of the toolpath. Sometimes I will create cutaway models of the fixture so that the fixture location can be seen without obscuring the part.
  10. Bill Craven

    High level training

    A lot of my time these days is developing 'turnkey' part programs, and many times it is for a customer that has just bought a new machine with advanced capabilities and doesn't have anyone in house that knows how to run the machine and even set offsets, etc. Starting with a good post is very helpful, but if the parameters in the machine are set differently from the parameters that worked for a 'proven' post, you might not get the desired motion. Working with posts from Mr. Postability (Dave Thompson) and posts from the crew at In House Solutions have been positive experiences. But if you can't tell them why a snippet of code doesn't work, they can't fix it. I end up burning a lot of time going back and forth between an Application Engineer from the machine tool manufacturer and the post developers. Okay, I'm done whining. I love my job. I really do. The mental stimulation is what keeps me going.
  11. Bill Craven

    Active Reports: Minimum Z depth for each operation

    I run a simulation in Mastercam using MachSim. MachSim allows me to set up the 3 view display. For each operation I use a screen capture program called Snagit to capture the 3 views and then I save the screen captures with names that have the operation numbers in them. Then when I run the Active Reports setup sheet, I can change out the default screen captures that Mastercam creates for the setup sheets and replace them with the screen captures that I saved when running MachSim. Attached is a Word doc from Mastercam explaining how to change the screen captures. how to use custom images in ActiveReports.docx
  12. Bill Craven

    MC2019 operation numbers

    Thanks Jay, That looks sweet. I've got 2020 loaded, but haven't had much time to work with it. I have to work in the version that my customers use. (you know how it is)
  13. Bill Craven

    MC2019 operation numbers

    If you go to the Operation display Options, there are 2 different Operation numbers available. "List numbers" will be a sequential operation list. The "Internal operation ID" is the operation number that was assigned when you created the operation. If you have the Internal operation ID displayed, then when you move operations around, the operation numbers don't change. If you delete an operation the Internal operation ID is not used and not "recycled" A neat organization tip: I use Internal operation ID numbers to put toolpath geometry on. As an example; If I have 10 operations, (1 through 10) I will put the toolpath geometry for internal op ID 1 on Level 101, the geometry for internal op ID 2 on level 102 and so on. This way if I come back to this file a year from now (or hand off this file to someone else), they can easily find the geometry for that operation.
  14. Bill Craven

    Active Reports tool projection

    Laying on my back, looking at the underbelly of the bus and wondering who threw me here... Thanks Ron. lol Actually, I am glad to help. Short answer: Try using OVERALL-LENGTH for the XML tag. This is where some of the confusion starts to happen. In the XML file, Physical Length is the overall length. The overall length is the stickout or projection length. The "Setup Sheet XML Outline and Tag Glossary" doesn't have accurate definitions for the tags. The XML tag "Physical Length" is the number that you entered for the "Overall Length" when you were defining the tool. Overall-length is the stickout or projection length. The spAssembly/ToolProjection tag should work, (the same stickout number is in that field) but unless you have drilled down to that level of the XML file in your report, Active Reports won't output anything. Longer answer: Get a XML file viewer. I like XML Notepad from Microsoft. It is free and you can easily see the outline format of the XML file. If you don't want to install another piece of software, just drag and drop the XML file into Chrome. It will display all of the tags and the data stored in them. From either of these programs you can search for the "Tool Projection" number that you entered when you were setting up the tool on the holder page of the operation. Another way of thinking about the "hierarchy" of the xml file is to think of each branch of the outline as a floor in a building. Unless you are on that floor, or have created a path statement to that floor, you can't output that data to your report. Form the screen grab above, you can see that OVERALL-LENGTH is on the floor above spAssembly.
  15. Bill Craven

    4th axis drill and tap macro

    If you have a solid model of the part and have the Mastercam multi-axis module, you could do it as a 5 axis drill path. This works especially well if the holes aren't evenly spaced.

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