And while on the subject, is there a post-processor variable to output the cut definition in the tool comment.

Been going thru the XML tags to find this information but just can't seem to locate it. Is this information easy to find? If so, where did you find it. Looked in the sample files in the SST Report section - Versions 2023 and 2024.

Thanks!

Hi all! Just wondering if it is possible to get the Cutting Definition name output in ActiveReports? Any info will be helpful. Thanks!

Thanks Ron - using a new software is like having someone ask me how to show the axis lines in Mastercam (F9). Simple things seem to get it the way. Would you mind sharing your screen layout? Also, in a classroom context, what would be the easiest way to validate a program from Mcam to VC? Using the MCAMV I would suspect but for the lathe tooling we would need to get into the activating/disabling components in the turret manually. On the Doosan machine, we are gradually getting up to speed with the Mill-Turn module from Mastercam - do you think the MCAMV will play well between these environements? Haven't tried it out yet. Will attend the upcoming VUE meeting mid-May and try to get info on free on-line training. Anyway, thanks for the info - always good to have a Mcam/VC expert on hand to answer questions. Can also serve for others in the group.

Thanks for the reply - in the process of setting this up to be used in a school with 3rd year mechanical enginnering students at college level so it has to be pretty straight forward. I've been playing around with the MCAMV function for the milling machines (3 axis VMC, 4 axes pallet changer and 5 axis VF3 with TR160) and it works pretty well for now. Tool transfer and part positionning is less of a problem. Would like to streamline the lathe machines (2 axes XZ, 3 axis XZC and a new Doosan LSYA with sub-spindle). Struggling on simple things in Vericut without training (how to stop simulation at each toolchange or at a M01), but getting buy so far. Again - thanks for the input!

Hi to all, Well it's been a while since posting on here, hoping to get some insight on how you guys do things. I'm in the process of setting up Vericut for toolpath simulation on our mills and lathes, and would like to know your best practices on the lathe side of things. More specifically, I'm trying to use the MCAMV export to Vericut function for the lathe when using 3D tools setup in Mastercam. The lathe turret setup needs to be adjusted to the gage point of the tool so that everything lines up on the machine. My tools are used on VDI and BOT style turrets on different machines so I want to have the tools transfered from Mcam to VC instead of defining each tool in each machine independantly inside of Vericut. Also looking into using the "Machining Cloud" for tool definitions inside of Mastercam - curiously, the 3D tools from Machining Cloud exported to VC and the 3D Tools from Mastercam do not match when looking at gage point position. Am I missing something here? For each machine I will be modeling the tool locators (Axial/Radial Heads, Boring Bar holders, etc ...) but would like to have a common database for the standard tools. Any help would be appreciated. Thanks!

Never mind - found the problem

Hi Mick, Any reason the SZ section of the XML file is not being generated? This is keeping the part material tag from being outputted SZ/MATERIAL. Thanks!

Hi all, Does anyone know if there is a way to turn on the different plane icons even if they are not active? Would like to see the different icons and their positions with a visibility toggle like the Levels (active always on, others depending on the visibility status). Thanks!

Hi all, Have you all noticed that the shade settings in X9 no longer permit the possiblity to shade only certain solids if needed. Now it seems the "All Entities" option in older versions is no longer available, it's always "on". Unless there is another way? Thanks!

Got it - HP tech made me go thru multiple loops of updating drivers and BIOS when I specifically asked if it was possible to assign the NVidia card to a specific software. They're answer was no, not possible. That's when I started looking at the NVidia control panel and fixed the issue. They wanted me to send in the unit for hardware issues. Thanks!

Hi Aaron, How did you manage to force the use of the NVidia graphics card when using Mastercam?

Hi to all ... Working on a project that calls for the following on a HMC: Need to output all individual tools with the first work offset to validate operator has done correct tool measurement; Then need to use the last tool in the program and run thru each work offset and angular value to validate position. Been trying with buffer files but thought that maybe someone has already done this type of program. Thanks! The program would look something like this: % 00100 G00 G17 G20 G40 G80 G90 G91 G28 Z0. M06 T6 (U DRILL 25MM) G00 G17 G90 G54.1 P1 B0. X0 Y0 G43 H6 Z1.0 T7 G91 G28 Z0. M06 T7 (CORODRILL 16.5 MM) G00 G17 G90 G54.1 P1 B0. X0 Y0 G43 H7 Z1.0 M01 (END OF TOOLS) G00 G90 G54.1 P1 X0 Y0 B0. G43 H7 Z1.0 G91 G28 Z0. G00 G90 G54.1 P2 X0 Y0 B-90. G43 H7 Z1.0 G91 G28 Z0. G00 G90 G54.1 P7 X0 Y0 B-90. G43 H7 Z1.0 G91 G28 Z0. G91 G28 X0. Y0. G91 G28 B0. G90 M30 %

Still in the Tool Manager, what does the Print function suppose to do? I can't seem to get anything to print. Is it possible to print out the Tool List of the library, or the image of each tool? Thanks!

Hi Kevin, Been playing around with the Machine Simulation setup for a HAAS VF2 and VF3. Somehow, the STL files I've created for this machine gets scaled down to a metric environnement, ie, for example, the machine housing looks very very small in comparaison to the part, tool and fixture. Tried recreating the STL files and bingo, everything looks great. Didn't change any settings or units in the Mastercam file for the STL creation. Does anybody know why the machine stl elements would be scaled down to metric .... or how they should be done in the first place? Had the same problem with the VF3 simulation models. If I can sort this out to make it bullet proof, I don't mind putting them up on the FTP site for everyone to use. Regards, Luc

Thanks for the replies ... I think I'll look into the ActiveReport Toollist ... seems to populate the data correct!

Hi all, If I have multiple operations using different NC file names, can I combine the output in a single setup sheet using the MILL.SET? Thanks! Luc

Hi to all, Is there an existing code to get the specific HST Toolpath type? With opcode$ we can sort the type of toolpath operation, I would like to comment the HST type operation (Core Roughing, Area Clearance, Waterline ...) Thanks!

Hi all, Using X5 I'm experiencing the following: When saving a geometry with Drafting as a DXF file. When DXF file is re-opened, the aspect ratio of the numbers will change. If this file is again saved out as a DXF file, the aspect ratio becomes even smaller when re-opened. Anyone ever have issues with this? Thanks!

Colin, could you upload the instructions on converting a Router post to a Mill post on the FTP site, this would be helpfull for all I think! Thanks

Colin, could you upload the instructions on converting a Router post to a Mill post on the FTP site, this would be helpfull for all I think! Thanks

Hi guys, Unless I'm missing something very important, this it what I did with a SmartCAM post about 15-20 years ago, and same would apply now. I just got my hands on a Madaula Angle Head and will be modifying the post to support it. The post will be modified the following way: - if the Tplane/Cplane is at a different angle then the WCS, this will indicate the use of the Angle Head; - Prompt for the tool length which will be added to the pivot distance. - The calculated tip point coordinate in Mastercam will be "backed up" along the tool axis according to the 2 potential rotary angles (by trig functions); - The outputted code will be that of the heads pivot position. - voilà On the other hand, I know that the router posts make good use of the Flex Aggregate Heads and will adjust outputted code according to the C-Axis angle and the Tilt angle as Colin suggests. Maybe just add the Router post logic into the Mill post. Just my 2%!!!

+1

Here's one way to use Reverse Wear in a production shop with many operators ... When we are cutting external contours in climb milling (CW), we use normal wear comp, ie, G41 (left side comp) output. This has the effect that if you want to INCREASE the size of whats being machined, you add a "+" value in the comp of the tool, if you want to REDUCE the size of whats being machined, you enter a "-" value in the comp of the tool. For example, +0.002 will increase the overall wall size by 0.002" When cutting an internal pocket finish pass, in climb milling, we will cut CCW, but at the same time, we will use a G42 (right side comp). This has the same effect then before, ie, that if you want to INCREASE the size of whats being machined, you add a "+" value in the comp of the tool, if you want to REDUCE the size of whats being machined, you enter a "-" value in the comp of the tool. This method makes it a lot easier for the operator to determine the correct "sign" of the comp required to adjust machining. Just my 2%