Dear Sir/Madam, I'm submitting suggestions for post processor Siemens 840d. Most of this can be implemented via simple modification of post processor. Maybe following modifications would be interesting for others.   1.) Cycle832 This cycle is currently using fixed values. This is somehow acceptable for older controllers. New controllers can control this cycle much more efficiently. Maybe it is time for update?   Following code changes cycle832 parameters based on stock to leave. I'm sure your programmers can optimize next few lines for better efficiency. This cycle greatly improves motion smoothness.   if (properties.useCycle832) { if (hasParameter("operation-strategy") && (getParameter("operation-strategy") == "drill")) { writeBlock("CYCLE832()"); } else if (hasParameter("operation:tolerance")) { var tolerance = Math.max(getParameter("operation:tolerance"), 0); if (tolerance > 0) { var workMode = 0; //Thresholds var stockToLeaveThresholdFinish = toPreciseUnit(0.05, MM); //Finishing var stockToLeaveThresholdRoughing = toPreciseUnit(0.1, MM); //Roughing //Stocks from Operation var stockToLeave = (hasParameter("operation:stockToLeave")) ? getParameter("operation:stockToLeave") : 0; var verticalStockToLeave = (hasParameter("operation:verticalStockToLeave")) ? getParameter("operation:verticalStockToLeave") : 0; var minStockValue = Math.min( stockToLeave, verticalStockToLeave ); // get smallest stock value //Check conditions for Finishing if ( minStockValue < stockToLeaveThresholdFinish ) { workMode = 1; } else { workMode = 2; } //Check conditions for Roughing if ( minStockValue >= stockToLeaveThresholdRoughing ) { workMode = 3; } if (workMode) { writeBlock("CYCLE832(" + xyzFormat.format(tolerance) + ", " + workMode + ", 1)"); } else { writeBlock("CYCLE832()"); } } else { writeBlock("CYCLE832()"); } } else { writeBlock("CYCLE832()"); } }     2.) Program end Program usually ends with following:   G0 SUPA Z0 D0 G0 SUPA X0 Y0 D0 M30 This code disables tool length and once program ends tool height is incorrectly displayed.   Maybe it would be safer to add D1 before M30?   writeBlock(gMotionModal.format(0), "D1"); // enable tool length compensation     3.) Lead in - lead out Would it be possible to have IJK for milling (usearcturn=true) and ForceXYZ() for  lead in/out? I am experiencing a lot of errors in end point of circle when using 2d contour and rouging passes. This would solve mentioned issue.   4.) Thread milling Current code is not optimized for multi flute/row thread cutters. Is it possible to optimize this via post processor or is this problem much more complicated?   Thank you for reading my suggestions and best regards! Show More

I have looked at the post files and am a little perplexed why there are so many post types? In all the years I have been a CNC programmer and Machinist I use basically one post and modify it slightly for each machine type. I have used this format for Haas, Fanuc, Matsura with yasnac controls, Fadel in the EIA mode not the "fadel format"and Mitsubishi control types. As I stated I just tweak a few lines and it is safe efficient and clean looking code. My operators appreciate that is is easy to find next tools when searching too. I wish someone would build a cleaner looking post for fusion 360. I am not a post geek I will pay my reseller to tweak it if need be or if a new machine needs a slight tweak. I have downloaded and used the post files for a few machines some worked some needed editing of the G-code. I would love to see a simple post made that has the following features, so I can easily modify it without spending hours of learning time just to make a small change..... Then forget what I learned a few months later......    1. make the start of a tool and the end of each tool semy hard coded into the post, add variable but make it east to identify and edit. like this  N1 G28 G91 Z0 M5 G0 G17 G40 G49 G80 G90 G98 M6 T4 G54 X1. Y1. M3 S3000 G43 Z3. H1 M8 ............       END OF TOOL M9 G28 G91 Z0 M5 M1  (*)   Make the sequence numbers on the first line of each tool, we do not need sequence numbers on every line!  make the tool number, RPM, coolant, height offset and work offset,  x,y values variables, everything else hard code it.  The body part of the program is just standard stuff that can be addressed later.....   Just my humble opinion I hope I made some sense ????               Show More

Hello  CAM  Friends    Does anyone have a working fusion 360 cam post for a Hurco VMX30ui (5-axis mill) ? Currently the fusion 360  “hurco generic” post. Does not work with our machine.      I think its great that autodesk has provided us with a "beta hurco post" I will try it tomorrow on our machine. I will give an update on the post as soon as I get some results.   As a side note  any recommendations or contacts on where I can find a post that work with our machine would be greatly appreciated.     thank you    Also I have heard through the grape vine that there are companies using fusion 360 cam on hurco 5-axis mills. So there is hope 🙂     Show More

Wondering if anyone was working on this or is there a generic one that would work well.   Thanks. Show More

I would like a Post processor for Shark HD3 router. There are some odd ones out there that used to work but now dont. If I could access one right through Fusion/AutoDESK that would help. They are a .tap file I believe. Show More

I would like Autodesk to create a post specifically for the XYZ 2-OP Prototrak CNC machine. Show More

New HSM post-writer here...   I would greatly like to see enhanced interactivity between post-processors and HSM.   As a post writer for CAMWorks (and SolidWorksCAM), I came to really appreciate how CAMWorks allows to implement "post questions" through "Post" tabs found both at the setup/global level and at the operation level.   In HSM, there are, of course, several properties that can easily be set or toggled on/off or by users in the Post-process dialog (ex. rigid tap, tool preload, tool list header, etc). There are also a couple of fields that can be populated (program number, program comment). However, additional custom properties cannot be added to the list of configurable properties, additional output fields cannot be added (for example, programmer name, etc.), and all of these configurations are global-level, not operation level. For operation level stuff, Manual NC entries might be used, but again there is no way to add new or custom Manual NC entries to the existing choices (I am aware of pass-through, but not what I am looking for).   I understand that there is a rudimentary I/O mechanism for HSM that can be found with the "Interactive Fanuc" generic post. This is a good start,but is again only for global-level changes. And for some reason or other, no one has built on this idea since it was developed in 2012 for HSMWorks.   Why do I want/need I/O? I can give several examples of what I would use it for. Of course, most of these examples will have their own hack. What I am asking for is a more universal I/O mechanism that works both at the set-up level and the operation level, and that allows all this customization to be standardized rather than hacked on a case-by-case basis. Basically an elegant new tool to unleash more power.   Examples:   At the set-up level, I want to be able to easily capture more header fields in addition to Program Number and Program Comment/Name. Like Part Number, Part Revision, Part name, Set-Up Number, NC Code Rev., Date, Time, Programmer Name. (I am already familiar with the Date and Time Stamp hack).   At the operation level, I want to be able to manually manage Low-Gear M41/High-Gear M42/ or a default of no output. (I am aware that there is a Low-Gear/High-Gear hack that manages gear selection automatically - but it breaks down when RPM ranges overlap - hence the need for manual control; a gear change might be implemented as a Manual NC).   At the operation level, I want to be able to manually manage output of drilling operations as canned cycles or as long code (point to point) - sometimes variable pecking is really useful, but most other times canned cycles are fine.  (The current long code output hack works globally only).   This type of I/O mechanism would have allowed the control of coolant combinations (flood, mist, thru, high pressure, air) to be achieved through radio buttons or pull-downs, rather than today's not-so-elegant (albeit functional) list of every possible coolant combination.   As I stated, such an I/O mechanism is used by others (i.e., CAMWorks). It is an effective way to add flexibility to posts (to make posts more versatile off-the-shelf), all the while making the post writer's life easier.   Thanks! Show More

hello  im looking for help. i am currently trying to prototype a seat back and pad using inventor and hsmworks.  i have access to a CNC at work but cant find the right post possessor for it. we have a easy jet   http://www.casadeibusellato.com/en/products/cnc-working-centers.c8565/cnc-working-center---nesting.8566/easy-jet.8568   does anyone know what i can use to get my files to work on this machine? thanks   Show More

I'm interested in having a CAM post processor for WARDjet waterjet systems. I can provide some sample code output from other CAM programs if needed! Show More

I wish I had the programing skills and the time to resolve this myself. It seems like LinuxCNC is widely used and would be worth it.   Thanks Show More

Can we get a post processor written for the CNC Masters MX 4 axis control? It's a relatively short list of G and M code but also has probing capabilities.  Here is the list.   The Master Software supports these standard Milling Machine G-Codes and M-codes: G00 = Position (Fast speed) G01 = Linear interpolation (Feed speed) G02 = Circular interpolation (CW) G03 = Circular Counter-clockwise interpolation (CCW) Format: X__Y__I__J__ I,J are relative distance from start to center. Incremental Z can be added for helical designs. G40 = Cancels G41 and/or G42 G41 = Tool Radius compensation left G42 = Tool Radius compensation right G54 = Work Offset in Absolute Mode G55 = Work Offset G56 = Work Offset G57 = Work Offset G58 = Work Offset G59 = Work Offset G70 = Input in inches G71 = Input in millimeters G73 = High-Speed Peck Drilling Cycle G81 = Drilling Cycle G82 = Counter Boring Cycle G80 = Cancel Cycle G83 = Deep Hole Peck Drilling Cycle G90 = Absolute move (Modal) G91 = Relative/Incremental move (Modal) M00 = Pause M03 = Spindle on M04 = Spindle on reverse M05 = Spindle off M08 = Coolant on M09 = Coolant off M30 = End program   This control has 4 axis and is capable of running all simultaneously X,Y,Z, and W W is a simple rotary table that can be set up in A,B, and C positions   Thanks, Dave   Show More