OPPIZ

This should not be...

Please send me a copy of the PST you are using

AND the MC8/MC9 that you are posting AND a copy

of the NC that is currently being output.

I will also need to know your MC HASP #

PostGuy

You can also determine this by setting a user-defined variable in these postblocks that get called just prior to the threading postblocks ->

PTHDEXT is called if an external thread

PTHDINT is called if an internal thread

Felix information >

www.dapra.com/html/felix.htm

1> post.TXT files

You can copy the MPLFAN.PST to MORI.TXT an alter it as needed. Note that MC does NOT read from MPLFAN.PST in this case. All default TeXT comes from the main system TXT file. (LATHE8.TXT in this case). The TXT info. from your MORI.TXT then over-rides the default TXT.

2> LATHE8.PRM file

Don't worry about it.

PRM files for MC are (most often) used to store parameter information states. Yes, you problably knew that! If MC (and some C-Hooks) need a .PRM, it is usually created by the process that needs to save info. for the next time it runs.

That was the problem.

To setup the default mode for determining

to Tool Length & Tool Diameter offset number...

From the main menu in Mill v9.0 ->

Screen, Configure, NC Settings, Operation Defaults, select your ?.DF9 operation defaults file, click the Job Setup button and change the 'add' values in the Tool Offset Registers section.

If you don't wish to use the 'add' method, use

the 'From Tool' setting. It tells MC to pull whatever values you have programmed in your MC9 toolpath with NO manipulation.

PAC

I cannot duplicate the problem here.

If you could please send me the MC9

with the toolpaths you are posting

and the .PST you are using.

PostGuy

The numbers output with Fastmode : 0 and BUG4 : 1

is the physical line position in the NCI file that is being processed by the post processor when those NC blocks are generated. You could load up the NCI file and page down to that line (the 222 line in the NCI file) or if you are using a decent editor (PFE or CIMCO Edit) you can do Edit -> GoTo Line and enter the line to move to.

Roger

All, you have scratched a pet peeve of mine. So here is my $.02

I've been AMAZED over the years that people don't backup!

Your larger business usually has a network person that will handle

this - IF you let them know what data you need backed up.

But, in too many small to medium size shops I've seen nonexistent backup

procedures. I've seen shops loose big $$$$, all because of a crash or stolen PC.

PC replacement cost is minor - it is the DATA lost that will kill you.

There is nothing quite like the feeling of coming into work in the morning

and looking at that blank spot were your PC used to be.

I am talking from personal experience here! (This was not @ CNC)

They probably only took 3 PCs with montitors and an HP Laser printer,

because they did not have enough room to carry them all away.

Charles had a good point about backing up some data to another PC.

Quick, easy and cheap. (I do it myself) But this is NOT a complete solution.

See above: "Your PC walks out the door."

Tape is still used everyday on networks for backing large amounts of data.

If you are looking for Tape/RAID/CD-RW/DVD solutions,

check out -> www.megahaus.com

(I get $nothing$ for this endorsement.)

From my experience these guys know what they are doing.

Some tape details (there are MANY tape options)

(I used one of these Sony 7000 series on the network)

Sony 7000-series SCSI 4mm DDS-2 DAT Internal Tape Drive - $439.00

uses 'DDS-2' type tape media, 4-8GB capacity - $7.00

Sony 9000-series SCSI DDS-3 DAT Internal Tape Drive - $575.00

uses 'DDS-3' type tape media, 12-24GB capacity - $12.00

These are internal SCSI devices (external configurations available for approx.

$70.00 more), so you must have a SCSI interface on your PC, or you can add

a quality SCSI interface card for around $200.00

These 4mm DAT drives cost more than many of the other tape drive types,

BUT they are fast and the cost of the tape media is comparitivly low.

Yes, you can get Travan type tape drives for around $200.00, but the

tapes will cost you $30.00 - $40.00 each to achieve the same capacity.

If your tapes are expensive, so you only use one that is always in the PC

you have NOT gained anything! Don't laugh, I've seen people do this.

I'd like to address a couple quotes from previous postings...

---------------------------------------------------------------------

In my opinion a raid cage with drive duplicators is the way to go.

It's a lot more expensive than zip, or even DVD writeables, but data

transfer rates are a lot faster. Once it's installed you never have

to worry about it too...

---------------------------------------------------------------------

RAIDs can be a good choice for data protection.

I used a RAID setup when I used to be the Network Guy (not @ CNC).

If setup properly, it can save the day when a hard drive crashes.

But if this is all you do, you do NOT have an adequate backup.

See above: "Your PC walks out the door."

----------------------------------------------------------------------

The problem I see with a CD writer is that I'd have to switch disks...

I'd rather let the backup run in the wee hours....

----------------------------------------------------------------------

IMHO,

This is a good choice if your are not trying to backup more than will fit

on a single CD every day. I used an HP brand CD-RW to back up certain critical

files that changed daily on the network. (these files were also backed to tape)

It was very easy to setup a couple BAT file (or CMD file for you XP users)

and using the Windows Task Scheduler to run these command files in the

middle of the night. This worked very well for me. I used quality CD-RW

equipment and media. Like Charles, "I have NEVER EVER had a CD go bad".

Quality CD-RW drive will run you around $150.00 Yes, I know you've seen

ads for $89.00 You get what you pay for.

DVD recorders are definitely up an up and coming option.

Cost is still around $500.00 for an internal drive and the media

about $15.00 per disk.

Since you've read this far, you may have noticed that I backed up data to ->

1> Tape

2> to another computer hard drive on the network

3> to a CD-RW

4> and used a RAID setup on the primary PC

Extreme you say? Maybe. But when they just HAD to have that data,

they were very happy that I could retrieve it.

Thanks for reading this far...

One last point -> Backup your Mastercam Post Processors !!!

NOT just the *.PST files. You ant the *.TXT for the post and some (special)

posts have a *.PSB file also.

If you are not sure of which files, get everything out of your

POSTS directories.

I know of one place that lost the only copy of their post processor.

(? you only have ONE copy!?!)

and shut down the CNCs in the shop for an entire weekend. They had a super

rush job that WAS supposed to ship out by Tuesday. Needless to say, they did

not make delivery (can you say "Just in Time" manufacturing?) and were out

of the loop next time this customer put a large job out for bids.

With business down for many, spending time and money on this stuff may

not seem top priority. But, if something *bad* happens, how much is that

going to really cost your business? Probably more than you think!

Didn't mean to write a book here, but this stuff is IMPORTANT!

Roger

Kyle,

Please send me copies of your Makino GF6 post

Need BOTH the .PST & .TXT files

If UPDATEPST9 is having a problem updating a PST,

we certainly want to know about it.

Andy,

Looks like you are missing the 'Z' depth on the 2nd thru Nth drilled location.

You should not have to output the 'G83' for each position on a Fadal.

In a post the 1st drilled point code output for a DRILL cycle is handled by -> PDRILL

The 1st drilled point code output for a PECK cycle is handled by -> PPECK

The 1st drilled point code output for a CHIP BREAK cycle is handled by -> PCHPBRK

and there is PTAP for tapping, etc...

All the subsequent drilled locations in the cycle are handled by the 'P?_2' postblocks ->

PDRILL_2, PPECK_2, PCHPBRK_2, etc...

You need to check the code in the PPECK_2 postblock.

Many times all that postblock does is call PDRILL_2

Example from an "old" post

--------------------------------------------------

pdrill_2 # Canned Drill Cycle

n, x, y

ppeck_2 # Canned Peck Drill Cycle

pdrill_2

--------------------------------------------------

You need to make it possible for the Z (drill depth) value to be output ->>

--------------------------------------------------

pdrill_2 # Canned Drill Cycle

n, x, y, depth

--------------------------------------------------

If you REALLY want the G83 X Y Z output for EVERY position you could do something like this ->

--------------------------------------------------pdrill_2 # Canned Drill Cycle

# Force EVERYTHING to output

n, *sgdrill , *x, *y, *depth

--------------------------------------------------

Roger

All,

Please note that there will be a Post Docs addendum for new stuff in v9.

The "Post Processors - What's New in v9.pdf"

will be in your new MCAM9 folder after installing v9.

Felix,

If you just need to change the 'P' letter on the G54P1 to be a 'J', here is the simple change ->

Find this line in the MPFAN.PST ->

fmt P 4 p_wcs #WCS P address

Change to (change 'P' to 'J') ->

fmt J 4 p_wcs #WCS J address

Toby,

Where is the 'bldnxtool' command variable getting set to '1'is your posts? If the only place is in the PQ postblock ->

pq #Setup post based on switch

if stagetool = one, bldnxtool = one

You can correct the 'T0' tool pre-select problem by adding bldnxtool : one to the variable declarations toward the top of the PST file (drop it in right after 'stagetool') ->>

stagetool : 1 #0 = Do not pre-stage tools, 1 = Stage tools

bldnxtool : 1 #1 = build the list of Tools

That is one quick way.

The other method is to get an updated MP.DLL

There is a newer version of the MP.DLL available that will also correct this problem with NO post changes.

Fred,

To set toolpath parameter defaults...

Screen -> Configure -> NC Settings

Click on Operation Defaults button (lower left)

Select your Operation Defaults file (a .DF8 file)There are Inch and Metric versions.

Now select the Paramters line of the toolpath type you wish to alter (Lathe Drill in this case)

Go to the Drill Cycle Parameters page and set your desired defaults. Now just OK, OK and OK

to get out to MC main menu. Done!

To get the MPFAN.PST (from the v8.1.1 CD) to output a list of the tools

used in the program to output at the start of the NC file ->

First, you must tell the PST to do a pre-scan of the NCI file.

Add this varaible to the MPFAN.PST ->>

tooltable : 1 #Do a pre-scan of the NCI (calls postblock 'PWRTT')

Now you need to add the PWRTT postblock that will be called because

of the 'tooltable' setting. We will just have this call the PTOOLCOMMENT

postblock that already exists in the PST.

pwrtt # Called at each toolchange (and NULL toolchange) in the program

if t > 0, ptoolcomment # Only do if T > 0 (at a real toolchange)

------------------------------------------------------------------------------------------------------------

Note that the tool list will output PRIOR to the '%' at the start of the NC file.

If you wish to reposition the tool list so that it outputs after the initial NC startup

blocks, you would relocate the startup blocks. Move them from PSOF and

place them into the PHEADER postblock.

pheader #Call before start of file

if met_tool = one, #Metric constants and variable adjustments

[

ltol = ltol_m

vtol = vtol_m

maxfeedpm = maxfeedpm_m

]

# Start of NC file.... following lines relocated from PSOF postblock ->>

"%", e

*progno, e

"(PROGRAM NAME - ", progname, ")", e

"(DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, ")", e

The result in output such as ->

%

O1234

(PROGRAM NAME - MTEST)

(DATE=DD-MM-YY - 17-12-01 TIME=HH:MM - 10:27)

(1/4 FLAT ENDMILL TOOL - 1 DIA. OFF. - 1 LEN. - 1 DIA. - .25)

(5/16 FLAT ENDMILL TOOL - 4 DIA. OFF. - 4 LEN. - 4 DIA. - .3125)

(3/8 DRILL TOOL - 3 DIA. OFF. - 3 LEN. - 3 DIA. - .375)

(1/4 CENTERDRILL TOOL - 5 DIA. OFF. - 5 LEN. - 5 DIA. - .25)

N100G20

N102G0G17G40G49G80G90

Bracketed postblocks:

Another form of postblock is the bracketed postblock,

which is a user-defined nested postblock. The post writer

declares a bracketed postblock by using the open and close

brackets ([,]) as postline statements surrounding the postlines

to be nested.

Bracketed postblocks are intended to make the post customization

file more readable and are always used within the traditional

postblocks.

Bracketed postblocks are implied postblocks, which means they

do not have a postblock labels declared by the post writer.

*** Answer to the question ***

Note: The post executable assigns labels to implied postblocks,

which are used internally when the post customization file is parsed.

Nate,

You would make the change in the MILL8.TXT file

This will change Mist -> Air in the Coolant

drop-down list on the operation parameters screen.

Find this line -> 8332. "Mist"

and change to -> 8332. "Air"

Of course you would also need to alter your Post

to output the proper AIR code. If using MPFAN.PST

you alter the string select value ->

sm08_1 M8 #Coolant Mist

Rory,

It is not THAT difficult to do.

No, there are not pre-defined variables

for these 'additional parameters'

We've got too many already

I've just done a new MILL.SET that has

many output options for cycle time and

max/min XYZ information output.

If anyone wants a copy, I've put it on

the Forum FTP in the "Text & post files & misc"

area as "NEW-MILL.SET"

Rory,

Quick answer is YES

Any values you can get using the (InHouse) HTML setup sheet generator - you can get with the SET