Thank you. That worked.

We recently got version X. I'm struggling with it but little by little I'm figuring it out. One thing I can't seem to figure out is when I updated my Heidenhain post it started to do something strange. It used to output the "Datum Shift" at the beginning of the program. Now it puts it after the drilling cycle. Does anyone know what I could do to fix this problem? Thanks. Before update 0 BEGIN PGM 1 INCH 1 TOOL CALL 1 Z S1200 2 CYCL DEF 7.0 DATUM SHIFT 3 CYCL DEF 7.1 X0 4 CYCL DEF 7.2 Y0 5 L X+0 Y+0 R F6298 M 6 L X-.551 Y+0 R F M03 7 CYCL DEF 1.0 PECKING 8 CYCL DEF 1.1 SET UP -0.1 9 CYCL DEF 1.2 DEPTH -0.4115 10 CYCL DEF 1.3 PECKG -0.4115 11 CYCL DEF 1.4 DWELL 0. 12 CYCL DEF 1.5 F100 13 L Z1.3615 R F M99 14 L Z1.2615 R F M 15 L Z+1.3 R F 16 L Y-.0208 R F 17 L Z+1.2 R F 18 L Z+1.0836 R F100 19 L Y+.049 R F 20 L X-1.653 R F 21 CC X-1.653 Y0. 22 C Y-.049 DR+ R F 23 L X-.551 R F 24 CC X-0.551 Y0. 25 C Y+.049 DR+ R F 26 L Y-.0208 R F 27 L Z+1.0058 R F After Update 0 BEGIN PGM 1 INCH 1 CYCL DEF 1.0 PECKING 2 CYCL DEF 1.1 SET UP -0.1 3 CYCL DEF 1.2 DEPTH -0.4115 4 CYCL DEF 1.3 PECKG -0.4115 5 CYCL DEF 1.4 DWELL 0. 6 CYCL DEF 1.5 F100 7 L X-.551 Z1.3615 R F M99 8 L Z1.2615 R F M 9 TOOL CALL 1 Z S1200 10 CYCL DEF 7.0 DATUM SHIFT 11 CYCL DEF 7.1 X0 12 CYCL DEF 7.2 Y0 13 L X+0 Y+0 R F6298 M 14 L X-.551 Y+0 R F M03 15 L Z+1.3 R F 16 L Y-.0208 R F 17 L Z+1.2 R F 18 L Z+1.0836 R F100 19 L Y+.049 R F 20 L X-1.653 R F 21 CC X-1.653 Y0. 22 C Y-.049 DR+ R F 23 L X-.551 R F 24 CC X-0.551 Y0. 25 C Y+.049 DR+ R F 26 L Y-.0208 R F 27 L Z+1.0057 R F

Is this what you need? % 32 N100 G70 G75 G90 32 N102 G0 T1 M6 32 N104 G0 X.15 Y0. 32 N106 S1069 M3 32 N108 Z.25 32 N110 Z.1 36 N112 G1 Z-.1 F6.4 38 (this is where it works) N114 X.25 40 N116 G3 X-.25 I0. J0. 42 N118 G3 X.25 I0. J0. 44 N120 G1 X.15 46 N122 G0 Z-.2 64 (this is where it doesn't)

When I run the mphur post, on a contour, the program feeds down on the first level and rapids down to the remaining levels. I would like it to feed down to all levels. I tried posting it with some different posts and they all work properly.

I use it at home. It's reasonably priced and it works.

We cut green carbide on our machines. If you're not familiar with green carbide, It's a grey chalky powdered metal. There is virtually no cutting force exerted on the machine, so I couldn't tell you how rigid these machines really are.

We have quills on all our machines and have yet to use them. Although the handle for the quill is an excellent place to mount a dust collecter hose. Do you mean support for the control? I always go directly to Anilam with any control issues.

We have 3 Fryar M300's with Anilam 5300 controls. We've had them for about 4 years and they are fairly reliable. The biggest problem we have is, the nylon bushing in the variable speed head melts down occasionally. As far as the Anilam control goes, it's one of the most user friendly controls, I've ever used.

I was wondering if one of you guys ,that were able to get on the site, would be kind enough to explain this?

I use MC for modeling and toolpaths at work. At my shop at home I use Alibre Design for modeling and Visual Mill for toolpaths.

I've had problems with sending to a Dynapath in the past because there where too many characters in the file name.

I sent my file to my dealer and he couldn't see anything wrong with it. He sent me back a .bmp file of what was on his screen when he verified it on his computer. It was perfect. I posted both examples on the FTP site in the "All Pictures" folder as "rotary.bmp" and "rotaryb.bmp".

I'm using Mastercam verify. I'll call my reseller for a quote on Vericut.

I put a file in the FTP site in the MC8 folder called "blades.mc8". When I run this in verify, the part looks terrible. It looks like the tool cuts through the part in several places, but when I post process it and run it on the machine it looks different. It still cuts through the fins in a couple places but not in the same places it shows when I verify it. Can you guys take a look at it and tell me what I'm doing wrong? Thanks.

We had a similar problem with our 10M control. We traced it down to a computer chip on one of the boards.