Bill Craven

Resellers
  • Content count

    160
  • Joined

  • Last visited

  • Days Won

    1

Bill Craven last won the day on February 28

Bill Craven had the most liked content!

Community Reputation

58 Excellent

About Bill Craven

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,534 profile views
  1. 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)
  2. 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.
  3. 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.
  4. 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.
  5. Yep, That is pretty much the world I live in. This will be another rabbit hole for me to fall down. Sleep is for wimps.
  6. Where is this Javascript file located? Many thanks Gunther for your excellent work.
  7. Bill Craven

    Active Reports: Minimum Z depth for each operation

    The report that I developed was based upon one of the default reports included by Mastercam. This was for a Mill/Turn type machine. The reason that I chose that for my starting point was: so that I would only have one report to tweak as I found that I wanted to change something. If I had worked just with the Mill report and then the Lathe report, I would have to go back and make changes so that the output would look the same. I wanted to minimize the number of reports that I have to maintain. So back to your question: "how does it know?" It really doesn't. There are two things that happen when you create a Setup sheet in Mastercam. 1. Mastercam goes out and looks at the Active Reports rpx files, makes a list of what information is needed for the rpx files and then goes to the mcam file and extracts and saves the data that the rpx files needs to an XML file. 2. Active Reports ( a separate program that Mastercam has licensed ) then takes over and goes into the XML file and gathers the information for the report and creates a buffer or temporary data file. Active reports then massages that data and places it in the report according to your template If you go back and look at one of the XML files in the Chrome browser and start at the top, you will see that is where the hierarchy starts. The first part of the XML file contains the data for the "SETUP SHEET". This data only appears once. <SETUPSHEET> <COMPANY>My company name</COMPANY> <USER>Windows User</USER> <BUILD>21.0.23937.0</BUILD> <SIM>xxxxx</SIM> <SOURCE>MASTERCAM</SOURCE> <UNITS>Inch</UNITS> <VERSION>2017</VERSION> <DATE-LONG>Tuesday, February 26, 2019</DATE-LONG> <DATE-SHORT>2/26/2019</DATE-SHORT> <TIME>8:21 PM</TIME> <YEAR>2019</YEAR> (there was more. This was just the start of that section) The next data is the Safety Zone (or Stock information) It also only appears once. When Mastercam is looking at the MCAM file there will only be information for the SZ section based upon what product was being used. Mill,. Lathe, or Mill/Turn. It gathers that information (if you have requested it for your report with the rpx file) and stores it in a buffer. Next is the NCFILE section. It has information about the names of the files used and some other stuff. This data is only gathered and output to the XML file once. The next section is the OPERATION section and it is very short but does repeat in the XML file for each Operation. It only holds the operation number and the operation type. <OPERATION> <SPACER>SJV</SPACER> <NAME>1 - Contour (2D)</NAME> The next section is information about the Operation and it is specific to the product being used. It might be OPERATION-M, or OPERATION-L or OPERATION-T (for text, Manual entry) A sub section of this product specific operation is going to be the TOOL, and then TOOL-L or TOOL-M information and it has to be specific because of the way that Mastercam defines tools for Milling is different than the way it defines tools for Turning. If it is a turning tool, then there are more sections for INSERT, HOLDER, CUSTOM, DRILL. I am not using that data for my "SHORT" report. By carefully and consistently naming the tools, I can just use the name field in my report and still give the operator all of the information that he needs to know that he has the correct tool. Again, this information is stored the the buffer. Think about all of the information that is required to fully describe everything about an operation. Each operation has to be defined as to what it does, what tool is used, what Work offset is used, etc. After building this "buffer", Active Reports builds and outputs the report to the screen. Most people have little idea of how much work it took to gather that information and put it in an XML file. I didn't even touch on Mastercam loading the backplot image and geometry and taking a snapshot for every operation, or taking snapshots or each tool, each insert in Lathe and the touchoff point Mastercam sequentially gathers the information for each operation and then Active Reports collects that information and presents it in a report. So, if you create a report that you want to output a tool depth, but don't have an OPERATION rpx before the TOOL rpx how would Active Reports know which tool depth to use for the report? From the Active reports Tips and Tricks doc: MIN and MAX Values Beginning in 2019, each min/max is relative to the Tplane or WCS used in the operation. World coordinates are available. There are different tags for each. Examples: MIN-Z-TPLANE, MIN-Z-WCS, MIN-Z-WORLD. In previous versions, the WCS must be the same in all operations selected or World values are used for MIN/MAX-Z, etc. Values will be relative to the WCS origin. If you aren't using 2019, my reports will probably not give you accurate stickout information. Most of the time, when Active reports is missing information because we have the XML tag names wrong or the path in the XML file not specified correctly, Active reports doesn't output any data. (as you have seen in your tests) What version of Mastercam are you using?
  8. Bill Craven

    Free Active Reports Setup Sheet

    I don't know. It wouldn't hurt to try it. It does not overwrite any of the default installed Active Report Templates.
  9. Bill Craven

    changing multiple diameters

    This chook is still included. ArcMultiEdit.dll Works for wireframe arcs.
  10. Bill Craven

    Free Active Reports Setup Sheet

    Greetings all, I have developed a setup sheet that is really more of an Operation check list. Developed for minimal paper waste. It works with all three of the main program types without changing report templates: Mill, Lathe, and Mill/Turn. The operations are color coded: Blue is turning, Yellow is Milling, and red is Manual Entry. If the tools are named in Mastercam the way that I recommend, all of the information will be there for the operator: Insert codes, etc. Included in the zip file that is attached is a sample turning program with milling, the Active report templates, a Word doc with instructions on how to install and where to enter information. For best results, pay close attention to the Word doc on what and where I enter the names and comments of the tools and operations. Disclaimer: Use at your own risk. Active_Reports_OP_Tool_List_short.zip
  11. Bill Craven

    Active Reports: Minimum Z depth for each operation

    I just took your setup sheets and tried to modify them to output the MIN-Z that you were looking for. (and failed) It took a while for me to get back to this thread. I have been juggling too many chainsaws this week. I have attached an Operation and Tool List report that will work with Mill, Lathe, and Mill/Turn. Also included in the zip file is an installation and configuration doc, a sample Mastercam part file, and a sample report. The hierarchy is very important. For this report, I used the following hierarchy OP and Tool List (MT) short.rpx - OP and Tool List (FILE) Short.rpx - OP and Tool List (OPERATION) Short.rpx - OP and Tool List (OPERATION-L) Short.rpx - OP and Tool List (OPERATION-M) Short.rpx - OP and Tool List (OPERATION-T) Short.rpx - OP and Tool List (MAN-ENT-INFO) Short.rpx and I am outputting sub-reports that don't produce any output, but are critical to gathering the correct data. I added the MIN-Z that you were looking for and I also added the "Top of Stock" data. In some cases the MIN-Z is not below Z zero. A little quick math subtracting the MIN-Z from the top of stock will give the tool stickout that is your ultimate goal. AR is supposed to be able to do calculated fields, but I have not been successful in getting that to work. The sample report below is from a Lathe part with milling. Active_Reports_OP_Tool_List_short.zip
  12. Bill Craven

    Active Reports: Minimum Z depth for each operation

    The secret handshake only needs to be used when you are in designer and trying to find a specific XML tag. You don't need to change the XML reference every time. I only update it when I want to run the preview. They include sample XMLs in the SST\Samples directory. They even have the "Full" XML file that was created with the secret handshake. It is interesting that your Z depths show up as positives. Is your part set above Z zero and are you using an adjusted WCS? If you have time, try this: Change the depth of one of your operations so that it has a unique number. Like: -1.2345 Run your setup sheet tool list and create a full XML file with the secret handshake. Drop it in Chrome, and then search for that unique depth. Note the XML tag, and then change the MIN-Z tag in your rpx file to match. As you can see, there is more than one MIN-Z. By looking for that unique number, you can quickly find the tag that you are looking for. Without doing the secret handshake you might not see all of the different tags for MIN-Z I like how you are sticking with this and trying to figure this out. Most people get a little ways in and drop it, either because of the complexity or they just don't have the time to spend on this when spindles aren't turning.
  13. Bill Craven

    Active Reports: Minimum Z depth for each operation

    Not exactly. When you tell Mastercam to create a setup sheet, it looks at the RPX templates that you have specified and the operations that you selected and ONLY gathers that information from your Mastercam file and dumps that into an XML file. This is why it is so important to be able to force Mastercam to do a complete dump of the data in a Mastercam file via "the secret handshake" I feel your frustration. There are days when AR really aggravates my tourette syndrome. You can get AR to output some of the data that you want without doing a complete set of reports. But if you have a very large file with hundreds of operations, the setup sheet generation time can take a very long time. If you are doing simple every day stuff with 20 operations and 10 tools, it doesn't really matter if it takes several minutes to generate a tool list. I have attached your sample setup sheets that generate the min Z value that you were looking for. Place both of the rpx files in the SSD directory, not the misc directory, and then select setup sheet from the operation manager, (not Tool List) then press F2 to select your test report tool list. See if you get the results that you are looking for. Note that I did not delete all of your old fields, I just turned off the visibility. As far as the truncated boxes that you are seeing, they are only labels showing what data fields you have selected. You can rename them to anything that want. They are only visible in designer. test report.rpx -test subreport.rpx

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