ok. I found out we are not running TCP/IP protocol for security reasons. We are running NetBeui..Next solution please.. Russ

I will forward this info..thanks for the assistance.. Russell

I just ran it by our IT guy and he says it's not a network issue, it's a MC issue. more posts please. I would like to hear from the more informed guys and Millman put it... Thanks

Has anyone had a problem with the file structure being so deep that mastercam crashes. We are using V9.1 MR0304 We are working off the network. Here is what the file structure looks like: P:/folder name/folder name/folder name/folder name/folder name/folder name It is essentially 6 levels deep and P: would be the mapped drive to the network. I found out a couple of things. 1-if I go to the 5th folder level it posts fine 2-if I rename all the folders and use an underscore between the names it posts fine to the 6th level. (folder_name) What's up?

We have just upgraded our nethasp and we are now receiving the following error. The SIM has become disconnected. Masercam will be automatically shut down. You will get one chance to save your file. Has anyone else received this message? If so any help would be appreciated.. We are using V8.1.1 on a W2K box. Thanks in advance

That didn't work..the 2d path is fine. the project path is fine too, until of course i check the add depths box, then it comes no where near the surface i am projecting on.

Hi there, I have a question about projected toolpaths. We still have V8.1.1 and I am projecting a toolpath onto a surface and then attempting depth cuts and can't get the desired results. Comments please. Thanks

Hello there, I'm here in Tacoma Russ

What I mean by debug is this: I label my groups by tool, this way I can find what I'm looking for quickly. My experience has been that If you label by operation searching through to find the problem area can be difficult and if another programmer has to step in and make some changes, it's even more fun. As I said I have had as many as 200 operations in a single op, and I have found you had better have a good labeling system for sure. Well, everybody has their own way of doing things that's for sure. If it's working for you great. Thanks for the input. Russell

Hey there, IMHO dependant on the file size my experience has been it is best to save each operation as a different file. I have several different reasons for this method. 1) the files can sometimes get very large very quick and become corrupt 2) It can be very difficult to de-bug when you have say 50 operations more or less 3) The grouping being what it is doesn't allow you to make a sub group. 4) verify can be a pain in the butt. 5) posting is an issue I could probably think of a few more. Trust me I have done it the way you are speaking of. I know what some of you are going to say. But you have too many geometry files. Get over it, Until mastercam comes up with say a Modsys and a unibase for example as in NCL I have had the best luck with this method. Russ To thine own self be true

Thanks James I will try it out first chance I get. As far as the benefit of the M300 macro it stops the need for reposting even if the part is not in the same location on a tombstone for instance, at which point you would only need to change your X,Y, and Z values in the initial G10 line at the beginning of the program which the M300 macro uses to calculate the x and y changes for a given rotation and then automatically writes it to the corresponding wcs based on the C value. No input by the operator/set up person is needed. It makes verification easier for multiple op parts since you don't have to move the geo as far via stlxform. In the unlikely event we have to move the fixture to a different location we will use our probe to pick up a new origin. All that being said, if there is a better way and as I said before, I have done extensive centerline programming, I would love to hear about it. I am always open to new ideas. I will keep you posted as to my progress with the post and respond to any other inquiries as soon as I can. Much appreciated

Thanks for the replies guys.. Here's the deal. Yes I have programmed from centerline for years and if the tooling is not dead on you know the drill of re-posting. With the M300 macro you program to part origins and the macro does all the calculations behind the scenes and you only have to post once for the rest of your life, provided you are a perfect programmer. We do use hard tooling IMHO M300 is the way to go. Here is an explanation of the output. A54.01 refers to extended wcs G54.1 p1 This is the part origin position @ B0 in this case the B value is the rotation set by your tool plane however many they may be. C is the wcs you wish to write to C54.02 writes to G54.1 P2 Therefore the M300 A54.01 will be the same at the beginning of every line only the B value and the C value will change according to your rotations. I don't think a 6 axis post is required, a lot of post work I suspect, that's why I'm asking You could learn a lot from a dummy like me. Does that help you guys

I guess I was unclear, I too have been programming for quite some time and have a fully operational post (except for a little editing as I was referring to) All I want to know is how to modify the post to do what I asked in my first message. I know Brian's abilities are very exceptional and have been in contact with him for many years, there is no problem with the macro, just the post. Can you help me now? Thanks for the lecture/3rd degree.

Why yes Ellison did make this custom macro and it's a dream come true in my opinion. Does that make a difference to you?

Hey guys, If there is anyone familiar with the M300 macro on the Mori-Seki horizontal you will know what I am after here, even if you're not I am sure someone will be able to help me out. Currently I have set up our post to hard code the M300 at the beginning of the program which looks like this: G90G10L2P0X0Y0Z0B0 G90G10L20P1X Y Z B0. M300A54.01 B C54.02 The B values in the M300 lines must be put in manually, as well as changing the C value which corresponds to the work coordinate system. One of my stupid human tricks is I can be dyslexic and input the wrong rotation. Can someone direct me as to how I might be able to have the B rotation output as well as the C54.02 change according to the corresponding work offset. For example: G90G10L2P0X0Y0Z0B0 G90G10L20P1X-12.401Y-11.497Z6.0775B0. (the x,y,z values in the line above will still need to be put in by the set up person) M300A54.01B90.C54.02 M300A54.01B85.043C54.03 M300A54.01B274.899C54.04 I will check back here periodically for your help. Thanks in advance

Hi there I am running V8.1.1 on a P4 2.0 GHz with 512 ram NVIDIA GeForce4 Ti 4400 and I can't load a 9.5 meg STL file to run through verify. I have tried lowering my hardware acceleration to 1 notch above none, changed my color to 256, 16 bit, and 32 bit to no avail. Is there a size limit on STL files? I have used stlxform on this file to stage it through. Could this have an affect? I am on op#5 and would like to see my part to completion in verify if you know what I mean. I have spent the whole day in contact with me reseller & CNC Software..Can the forum provide the answer?.Help!! Thanks

Heyyyyyy, I had the problem you are referring to a couple of days ago..Turns out I was not at SP1 like I thought..Does it say Mill Version 9.0 SP1 on your title bar at the top border of MC..Or do alt+v to confirm SP1.. Good luck Russell

Heyyyyyy, Here's the scenario..I have created a tplane to cut a specific feature and of course MC gives it a number (which by the way would be nice if it stayed that number all the time, not change the next time you open MC). Now I go back to say the top view, all's well right. Now I want to view the tplane I just created so I pick tplane (or cplane, or gview), number, type the number of the tplane and it is adding 1 everytime..I type 93 it goes to 94..S'up with that?.. Am I wacked or what?

Good afternoon As far as I know postworks is for NCL only.. Russ

Good morning James Wow!!! That would be awesome..no editing. Granted I only have to do some minor edits such as removing the G325 on tools larger than .75 and input rotations on the M300 lines, but if you can get me edit free I would be so grateful..I am sure my reseller will not have a problem with it. Here is my resellers name ,# & contact. [email protected] is where I send my inquiries. Steve Kidd Cimtech Inc. 253-922-8770 www.multiaxis.com Thanks again

Hello fellow MC users, I have a post problem I am sure someone can help me with. Ideally I would like to have the post go from +90.0 (or +91.0) to -90.0 (or -91.0) when rotating, as opposed to +90.0 to +270.0 which the post would consider the shortest distance. The post I currently am using works fine as long as you don't go past 90 degrees. I am working on a SH5000 Mori. The part has open angles which I am facing perp to the outer walls hence I am going past 90 degrees on both sides. Clear as mud right.. I am using a modified Mori fan 16 post Charles Davis from San Diego directed me to. I have tried to email him via the address on his contact card and it keeps getting kicked back to me. Help!!! Thanks in advance regardless of the outcome!!!! R.Johnson

Kenneth's name certainly won't be on my list of programmer's if we need some work done. Sounds pretty selfish & insecure to me. I hope you change your outlook, otherwise your reputation will catch up to you and nobody will want to work with you. If we didn't share info we wouldn't be where we are today. Good luck Jerry is right on the money however. I would hire him.. Russell

Yes, Yes and Yes again. If not you will surely end up with some funky cuts. The safety line should look something like this: G0 G17 G40 G49 G80 G90 Z0 sgplane in your post is what controls the output of this. The post should output this at all plane changes..

The only time I have gotten this error is when my rotation is compound (5axis).. The first step is to isolate the operation. Now look at the tool from the side view to make sure it is not tipping in 2 axes. Dollars to donuts this is what's happening. I have made this mistake a few times myself. Let me know if this works.

Orient your part so it is in the front view. This is how it will look in the machine. Now set your tool plane to front and you are good to go provided you make the changes James spoke of..rotate about the -Y- axis.