Forgot your password?
typodupeerror

Comment Re:That, or... (Score 1) 258

You wouldn't cut a complex surface with a normal end-mill, you'd use a ball end-mill as you say. You'll always have some amount of scallops in that case, you control how large they are by using a fine step-over, and if that's not good enough you'd have an after machining finishing operation to minimise the scallops. Millions of injection moulding tools and dies are made this way.

Granted multi-axis machining can be better with a ball end mill, but in that case you'd be using a 5 axis machine where the cutter is angled with lead and lag from the surface normal.

4 axis lets you do continuous machining around a cylinder

For 'prismatic solids' multi axis (4 or 5) just saves you some set up time, e.g. machining on the front face, then top face, then back face, but it's still a 3-axis (if you include helical or ramped entry) machining operation. This would be an indexed table, it can be positioned between cuts but it can't run simultaneously with the cutting path

Comment Re:That, or... (Score 1) 258

What would you want from Mazatrol or other extensions?

As far as I remember Mazatrol was a 'conversational' programming format that tried to make it easier for the operator to enter simple 2d paths (area clearance, finish profile, etc.). Maybe it had some better drill cycles than standard G-Code? I think G-Code was charged as an option on their controllers and some people didn't have it, which made writting post-processors a pain.

If you have a CAM system then G-Code is all you need. Some people with old controllers like using macros, but mostly that was due to limited memory on the controller (overcome with 'drip-feed' via serial communication, the machines were slow anyway) and the hope that night-operators could change the toolpath on the control if needed, but for the most part cutter radius compensation is all they needed.

Anything with 3D (x, y and Z) toolpaths mostly just needs linear feeds (G1) and coordinates. Some machines can take a NURBS curve for the parts of the toolpath, although that never really seemed to catch on well.

Maybe controllers have moved on more since I last wrote any posts but I don't think so. If anything with 5 axis it comes back to G1 xyzuv to give the angle of the tool relative to the workpiece and even less fancy cycles for the operator.

Hardware Hacking

Grad Student Invents Cheap Laser Cutter 137

An anonymous reader writes "Peter Jansen, a PhD student and member of the RepRap community, has constructed a working prototype of an inexpensive table-top laser cutter built out of old CD/DVD drives as an offshoot of his efforts to design an under $200 open-source Selective Laser Sintering (SLS) 3D printer. Where traditional laser cutters use powerful, fixed-focus beams, this new technique dynamically adjusts the focal point of the laser using a reciprocating motion similar to a reciprocating saw, allowing a far less powerful and inexpensive laser diode to be used. The technique is currently limited to cutting black materials to a depth of only a few millimeters, but should still be useful and enabling for Makers and other crafters. The end-goal is to create a hybrid inexpensive 3D printer that can be easily reconfigured for 2D laser cutting, providing powerful making tools to the desktop."
GNU is Not Unix

New LLVM Debugger Subproject Already Faster Than GDB 174

kthreadd writes "The LLVM project is now working on a debugger called LLDB that's already faster than GDB and could be a possible alternative in the future for C, C++, and Objective-C developers. With the ongoing success of Clang and other LLVM subprojects, are the days of GNU as the mainstream free and open development toolchain passé?" LLVM stands for Low Level Virtual Machine; Wikipedia as usual has a good explanation of the parent project.

Slashdot Top Deals

It appears that PL/I (and its dialects) is, or will be, the most widely used higher level language for systems programming. -- J. Sammet

Working...