tcommis, send me your post and i'll take a look.

stoney, how are you sending and receiving code from the machine. Cimco has an add-on to their DNC system called NCBase. It is a database add-on that allows you to attach any type of file to a NC or job folder. You can then attach setup sheets, html files, mc9 files, pictures, just about anything. And them see any of those associated to the job. Give us a call and we can fill you in some more.

ya, i think nachum has problems

More importantly it is not the FULL maintenance release. It is minus samples, help files, posts, CATIA translator and others. Dealers will be getting CD's for every maintenance customer.

nachum, the download is about 115Mb, not even a 1/4 of a CD, but still huge.

it will be a disk. CNC is sending us disks and labels for all maintenance customers. Right now dealers can download it, but it is giant and only part of the full maintenance release. As soon as we get them, they will go out to the customers.

the info i have is max of 4800 on 6m. Set with parameter 311, 4800 = xxxx1001

dealers have the Maintenance release but it is not officially released to users for about a week.

these guys hardware reportedly increases speed and capacity. http://www.e-manufacturing.com/products/mme.htm

MF, this is the tap section from the mpmaster post. code: ptap #Canned Tap Cycle pdrlcommonb #RH/LH based on spindle direction if use_pitch, pbld, n, "G95", e if use_pitch = 0, [ pcan1, pbld, n, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, prdrlout, *feed, strcantext, e ] else, [ if met_tool, pitch = n_tap_thds # Tap pitch (mm per thread) else, pitch = 1/n_tap_thds # Tap pitch (inches per thread) pcan1, pbld, n, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, prdrlout, *pitch, !feed, strcantext, e ] pcom_movea tapflg = 1 If you look at it, it can output 2 different types of feedrate. When use_pitch = 0, the feedrate is the 'feed' variable, which is formated to 2 decimal places. If use_pitch = 1, the feedrate is the 'pitch' variable, which is formated to 4 decimal places. You can set use_pitch = 1 at the top of post and you will get a 4 place decimal. Or change the format of 'feed' for use_pitch = 0. You would do that like this: code: if use_pitch = 0, [ result = newfs (two, feed) pcan1, ...

can you save out of Rhino as a DXF or IGES? Mastercam should be able to read those.

CIMCO Integration , www.cimco-integration.com makes a great Hiedenhain 5 axis post.

tcommis, if you would like to try it, give me a call and I can translate a file or 2 for you.

you can use surfaces and create-curve-slice, select surface(s) and use cplane(1) or Z plane at 0. If you had Solids, you can do a toolpath right on the solid without having to do the slice. You can also 'stitch' surfaces into a solid.

unfortunatly for some MC users, reseller skill and willingness vary. That is not to say that your dealer(s) aren't one of the best. In your area of the world, I consider both WA territory dealers to be some of the best. You might want to call them, I'm sure they will be just as helpful.

the default posts are set to output what you see in MC. So BerTau is right, if you set the clearance the same in both ops, it rapids XY then Z down, or Z up then XY. We are just cheating it in the post to make sure we always get that.

Tony, the mods uses the zinc variable, so it doesn't matter if it is in the positive or negative zone.

I think Tony was just showing an easy example of paths with different rapid heights. The post mod above will make the Z-up rapids first or Z-down rapids after.

cncme, here you go. code: prapidout #Output to NC of linear movement - rapid if zinc > 0, pbld, n, pzout, e pcan1, pbld, n, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pcout, strcantext, scoolant, e# <=== REMOVED pzout pbld, n, pzout, e Does the XY rapid first before negative Z rapid. The Z positive rapids before XY.

would make a great chook or vbscript, but i don't know of one. anyone else?

cncme, i can't access ftp from home, email me that zip.

MF, you can do this in mpmaster. code: pfzout #Force Z axis output sav_absinc = absinc if gcode > 80, absinc = 1 if absinc = zero, *zabs, !zinc else, *zinc, !zabs absinc = sav_absinc pzout #Z output sav_absinc = absinc if gcode > 80, absinc = 1 if absinc = zero, zabs, !zinc else, zinc, !zabs absinc = sav_absinc This will cause the post to use incremental depth for drill cycles.

What settings are changing??

try this instead: code: pretract #End of tool path, toolchange sav_absinc = absinc absinc = one sav_coolant = coolant result = prv_coolant # <=== ADDED coolant = zero if result = 1, coolant = 0 # <=== CHANGED if result = 2, coolant = 5 #Mist off <=== CHANGED if result = 3, coolant = 6 #Tool off <=== CHANGED #cc_pos is reset in the toolchange here cc_pos = zero gcode = zero if prv_mi6=1,pccrloff pbld, n, sccomp, *sm05, psub_end_mny, e pbld, n, sgabsinc, sgcode, *sg28ref, "Z0.", scoolant, e pbld, n, "M100", e absinc = sav_absinc coolant = sav_coolant Should work for you.

post up the pretract section of your post and i'll make some edits. The problem is, that at the pretract, coolant value is already updated to the next tool change.