Just throwing this out there, but If it was me I would not tackle this as a post problem but a machine problem.  I would add M10/M11 to that matsuraas or vice versa.  That way you can use the same exact program for each machine.

If M10 is already taken up then create a new Mcode M110/M111 and Mcode alias it. 

I am assuming fanuc control here but, Put 110 in paramter #6021 and make a new program in the library folder O9021

O9021(Universal 4th lock)

M10

M99

etc etc etc.  This way everything is automated and you don't have to keep track of machine descriptions.  But whatever floats your boat.

i didn't understand what you were trying to do intially, but after thinking about this for a while.  I think I got it.    There must be some kinda verification macro to check what program you're trying to run to make sure its right one.  

The reply I gave before was wrong.  

So you want to output #602=0050 instead of #602=O0050?

Due to a large portion of people pirating the software, people here are a bit hesitant to give out information on post editing.  If you're familiar with working on the post for the mill, i'll give you a hint.  Max speed in found in the post,  you should be able to find it pretty quickly. 

I don't think there is any way to control it directly in the program as it sits now,  but you can edit the post to do whatever you want it to do.  You can add a modifier or just hard code a static number instead of the variable.  Lots of ways to skin a cat on that one. 

Quote

So it calculates largest diameter machined @ 1000sfm. 

not quite, but pretty close.  It calculates the rpm it at whatever the first positional movement is.   Thats why a boring bar would start faster than an OD turn tool.  

It usually helps if you tell people what version of mastercam you're on.  If you're paying for maintenance your rep should be able to help you easily.  Have you talked to them yet about this?  

Quote

G97 S2247 M03 ( where does this S# come from ?)

This number is calculated out from your SFM.  

1000 SFM * (12/pi)  /  1.7" Diameter = 2247 RPM

So it kicks on the spindle at the correct speed for your SFM at your first positioning move.  This number is also limited to your max spindle speed.  

Money is a bit tight at the new company right now,  I wished I knew that walking into this place but i'll definitely be pushing for them to get me camplete when it gets a little better.  

Talked a bit with the owner and he told me they had a mastercam "post guy" out on the floor for 2 weeks working on the Nakamura post.  The post was kinda rough and totally not usable without heavy manual edits.  Not sure how they made it this long honestly.  

I'll talk to the owner.  Hopefully they can re-up on the maintenance.  The software I have is V4, lol.  I loaded it up for fun, and its terribly outdated.  Goes to show you how fast software develops in 10 years.  

Thanks again

camplete did come with the machine but the company decided not to keep maintenance going on that.  I'm new to the company and trying to figure out whats going on.  Seems the "programmers" before pieced together and edited programs to work. 

I'll contact my distributor

Thanks Ron

Hey guys,

I just started with a new company that has a Nakamura Super NTJX mill turn that had some post work done by our local distributor.   I fixed a couple things, but now there's just the Z axis on the lower turret that is giving me fits.  

It's not posting the Z in the right direction.  All the Z are inversed.  After hunting around, it seems I would have to play with the scase area in the post to invert the Z.  The only problem is I can't find it.  There are no mentions of scase in my post.  The post does have a .psb thats encrypted.  It could be in there, but I can't tell at the moment.

What I want to know now is, am I barking up the wrong tree?  Is there anywhere else it would normally be?  

Could you please include an example of modifying imported operations?

What I am trying to do is to save a "template" file of operations I normally use.  When I start the nethook, I would like it to ask for new geometry data.  Then import the operations from the "template" file and change the drill points to the new specified drill points.

Awesome, I must of skipped over that one.  Any chance there's one out there with drilling?  

I downloaded all the examples from the mastercam website for nethooks.  Is there anywhere I can find examples of creating geometry and or applying simple tool paths.

Does the machine have a fine bore drill cycle?  Its normally G76 on fanuc machines.  If so, then you should be able to use the Fine Bore drill cycle in mastercam.

If this is a fanuc machine, Just make sure the retract orientation is set up correctly in the parameters for the machine.  Parameter 5101 bit 4 and 5.  

 7 6 5 4 3 2 1 0

X X 0 0 X X X X        Retracts X+

X X 0 1 X X X X        Retracts X-

X X 1 0 X X X X        Retracts Y+

X X 1 1 X X X X        Retracts Y-

Gcode Cycle syntax should look like this = G76 Z [Depth] R [Feed Plane] Q [Retract Amount] F [Feed]

if this is something you are going to do on a regular basis, then I would consider using a custom drill cycle.  If its a one time deal, i would just Gcode it.  

At my old shop on one of our vertical machines, we noticed that coolant pooling at the tip would cause the laser to be inconsistent.  We adjusted the air and it helped a lot.

Over here we get on average within .0005 of our external tool setter.  Usually repeatability within .0002.  Are the tools always off a certain amount?

i have the non curved one.  I used to use two 16:9 monitors but I switch just to this one.  So far im liking it.  I was thinking about adding back one of the 22" 16.9 but using it in vertical orientation.  Would be useful when looking at code or spreadsheets.  

hdmi 2.0 can support 4k @ 60fps

hdmi 1.4 can support 4k @ 30fps 

Theres only a handful of nvidia cards that has hdmi 2.0.  

back to topic, i opted for the LG 34" 21:9 super widescreen monitor.  3440x1440.  I'm liking it so far.  I was gonna get the seiki 39" tv and use it for a monitor.   

You can alias "standard" M-codes?

 

MInd = Blown.  

didn't know you could do that either.  pretty cool.

closest i've seen is to alias M103 for M3.  Checks the speed and activates M3, turns on coolant.   

i think you forgot to put thru spindle coolant on too.  Cools down the stylus tip to achieve maximum accuracy.  

nice, I really like the creativity.  Here's my take on it.  About the same thing but written different just for kicks.  I normally use 8000 program numbers for in house macros, and leave 9000 for system/builder macros.  Unless I make my own G/M code like foghorn mentioned.  Used more local variables.  I also rolled in the #550 macro as variable V.  

M99

Another idea would be to have all the code you want the operator to edit in one spot.  That way they don't have to hunt around. 

(*******EDIT ONLY HERE ********)

(V = VISE POSTION)

(W = WORK OFFSET G54=1, G55=2, etc)

G65 P8050 V1 W1. X2 .Y-1.5 Z1. (G54)

G65 P8050 V2 W2. X2. Y-1.5 Z1. (G55)

(*******EDIT ONLY HERE ********)

is that the one just logs just the past 20 or so button presses?  Parameter 3195?

thanks for the replies guys

it would be nice if everyone owned up to what they did, but unfortunately because we have multiple shifts, we're playing the blame game.  Night shift guy blames day shift for sabotage.  To my knowlendge fanuc doesn't have any logging ablilties within the machine itself.  The ones with focas can output that info if theres a computer logging it, but thats just my understanding of focas.  I haven't actually gotten the chance to play with it hands on.  

I know about the keylogger param 3195.  Is there any feature thats logs more than just keystrokes?  Time and date stamps for when operators change offsets?  Anyone have any experience with this?  

any particular reason why you want an RMP vs the OMP.  In my neck of the woods, OMP are a lot more common than RMPs.  You'd might have better luck finding an OMP

OMP is optical, and RMP is radio.

We recently had an issue where an operator had a huge crash.  The night operator is blaming the day guy of sabotage and vice versa.  I know we can go ahead and solve this issue using macros to auto imput/verify offsets before the program runs.

One of the supervisors mentioned that the fanuc 31i control has the ability to log offsets entries, run data, key presses, etc etc.  Has anyone seen this?  I can see this might be possible with FOCAS and a computer logging the data, but does the 31i control have native data logging abilities built in?