doodlela.blogg.se - Camworks post processor

Tool Changer Type: Carousel or Optional SMTC Now before you start pulling out your credit card and loading it up with optional extras, get your machine specs noted: Flex those Google skills and find out all of the specs of your machine. So you fire up your SOLIDWORKS, check on the SOLIDWORKS CAM add-in and we’re ready to go. If you’re more of a ¼ mile than a Bonneville type of person, look out for the traffic signals highlighting the key areas to adjust and they’ll get you off the line and into victory lane ASAP. Learn How to Set up Your Machine in the Technology Database in SOLIDWORKS CAM Take a celebratory sip of your favorite brew, stretch those knuckles, as we’re about to walk you through your first steps of getting your machine and post processor setup. There sure is, and you’re in the right spot. But every time you fire it up, you always repeat the same steps, Machine, Tool Crib, Post Processor etc and every time you think to yourself, there must be an easier way. Post processors are any more complicated, given they don't do anything particularly different.You’ve been through the tutorials, took a class or two and are feeling pretty good about getting programming using SOLIDWORKS CAM. My posts are pretty heavily modified, and I've customized them for BobCAD and Vectric. Most CAM systems have a post processor selection for a generic 3-axis GCODE mill. Other than that, it's a very generic post processor.and I think those are a lot of things that MAKE IT a generic one.

Remember that it DOES support interpolation control (versus exact-stop mode) and you can set the tolerance.

It might be a DLL-based API that not exposed in GCODE, but who knows

Theoretically it can do "probing" of some form, but I've seen no references as to the expected GCODE.

remember that just because you put it in the GCODE, if you don't have the required licenses, it may not work.

There are no other hardware outputs, so none of the flood or other coolant controls do anything.

Spindle speed commands do not control the outputs.

basic drill pecking is supported, but the newer pecking and tapping cycles are not there.

I'm almost certain that the controllers CANNOT handle incremental positioning mode.

The controller technically *can* handle inline comments, but I avoid them just for my own paranoia.

it can do 3 digits of actual resolution (the HDs can), so I typically give it 4.

it can't handle more than one toolpath in a single file, because of the only-one M02 restriction.

Do NOT use the M06 tool change commands unless you want a Pause/Continue in your process.that won't actually let you change the bit unless they're set precisely at the same height.

the controllers CAN do 3D helical interpolation.

don't use + in field values (Z+5.0 can crash the controller).

A Generic GCODE-output usually works pretty well.