Job Setup

[MachineSMMC]

I am just cusrious to see how people handle Job Setups. We have 4 different verticle mills 2 of them require me to set the Job Setup a little differently than the other two.

 

Is there a way to have a couple of different Jopb Setups saved and then call them up for the different machines?

 

Any info on the or realted topics would be greatly appreciated.

 

Thanks in Advance

[iowajim62]

Hi,

 

I would use multiple Cfg. files. 1 per Machine.

 

This is from MC Help.

 

quote:

---

Managing configuration files

System configuration values and settings are saved in configuration files, which use the CFG extension and must reside in the main Mastercam directory. There are standard configuration files for each Mastercam product for both English and metric units. You can also create custom configuration files to meet specific workflow requirements, and merge configuration files.

---

Go to Screen,Configure,Files Lower left corner.

HTH

[Jimmy Wakeford from Barefoot CNC]

you can make a file and set job setup the way you want. save it. start new file then

main menu-toolpath-jobsetup-import button then select the file you made and highligh jobsetup.

 

Jimmy

[iowajim62]

Jimmy,

 

Great Idea Thank You !

 

Learn something new everyday.

[TeccBoxx]

Awesome this is "Tip of the Day" thanks guys.

[Roger Peterson]

Something many people forget about is assigning a cfg file to a post. If you do this as soon as you pick your post it will pick a predefined cfg file which can have different op defaults, including job setup, different tool libraries...

 

Very cool, takes a bit to get setup but you will like the results.

 

 

HTH

[MachineSMMC]

Roger

 

Does it explain how to do this in the help files?

[Rekd™]

I believe it's question 76 under Numberd Questions for Mastercam. At the bottom of the post.

 

You basically set up a config file, named after the post if you like, then call that config file from the post;

 

code:

---

 76. Configuration file name? HAAS VF3 Post 4 Axis Prestage.cfg 

---

HTH

 

'Rekd

[Rekd™]

Also, you can call your post from the config file. So make sure they match so you don't load a post that calls a config file that calls a different post, that calls a different config file, that calls a 3rd post, that calls a 3rd config file, etc etc etc.

This is from the config file;

code:

---

 [file names]

550. Default post processor (PST)? haas HAAS VF3 Post 4 Axis Prestage.

551. Default parameter file (PRM)? mill9

552. Default tool library (TL9)? c:mcam91milltoolstools.tl9

553. Default material library (MT9)? c:mcam91milltoolsmatls.mt9

554. Default setup sheet template? swag setup sheet access csv.set

555. Default operation library (OP9)? c:mcam91millopsoperat.op9

556. Default operations and job setup file (DF9)? c:mcam91millopsdefaults.df9

---

'Rekd teh Loop Until Sanity = False

[A-ron1286490684]

Thanks! This forum is awsome!

 

A-ron -teh one more step eliminated in the process!

 

[ 07-21-2003, 11:40 AM: Message edited by: A-ron ]

[MachineSMMC]

Rek'd

 

I am having trouble getting what Roger suggested to work. Any ideas. Please contact me if you would like to see my files.

 

Thanks

[Rekd™]

SMMC,

 

Open a post for a machine, and look towards the bottom for;

 

code:

---

# --------------------------------------------------------------------------

# Configuration File association parameters (default is "y")

# --------------------------------------------------------------------------

400. Name of associated cfg file? YourConfigFile.cfg

401. Read SYSTEM COLORS section? y

402. Read ALLOCATIONS section? y

403. Read TOLERANCES section? y

404. Read DATA PATHS section? y

405. Read COMMUNICATIONS section? y

406. Read DRAFT SETTINGS section? y

407. Read MISCELLANEOUS section? y

408. Read NC SETTINGS section? y

409. Read DIALOG SCRIPTS section? y

410. Read DESIGN SETTINGS section? y

411. Read PLOTTER SETTINGS section? y

412. Read ALT-KEY ASSIGNMENTS section? y

413. Read CAD section? y

414. Read START/EXIT section? y

415. Read SCREEN section? y

416. Read FILE NAMES section? y

 

---

In question 400 you can enter the config file name you want to use for that machine.

 

You can copy your Mill9.cfg file and configure it thru SCREEN/CONFIGURE for that machine. Name it something easy to spot, like I have HAAS VF3 POST 4 AXIS PRESTAGE.CFG to go with HAAS VF3 POST 4 AXIS PRESTAGE.PST.

 

So when I create a program for that machine, I select the post, and it loads the right config file.

 

In a nutshell, you will have:

 

Machine 1.PST

Machine 1.CFG

 

Machine 2.PST

Machine 2.CFG

 

The post files have the config files' names in Question 400 as shown above. So when you load Machine 1.PST, it applies the settings from Machine 1.CFG.

 

If you're still unsure on how to do this, email me thru the board, and I'll go a little more in depth.

 

HTH

 

'Rekd

[Müřlıń®]

I havent messed with cfg files.

 

I just used the same one for all since I never needed to change it.

 

Give me an example of why one cfg wouldnt work on 2 diffrent machines....for future refrence

 

Murlin

[iowajim62]

Hi Murlin,

 

One is HaasVF3.pst, the other is MazakHM4.pst.

One post is for VMC, the other is for Horizontal Mazak. By setting up your post or config files all you have to do is pick a post/file when you start programming a new part for that particular machine. That way when you "brainfart" and remember to go setup your post,config to use that 240 tool library for the Horizontal not for the Haas it is already done for you. Just skipping some of the "setup of MC" for each job.

[Rekd™]

Here's a few snippits from the config file that may be desirable to change for specific machines..

code:

---

 [units]

1. File is metric (y/n)? n

---

code:

---

 [file names]

550. Default post processor (PST)? haas vf3 post standard

551. Default parameter file (PRM)? mill9

552. Default tool library (TL9)? c:mcam91milltoolstools.tl9

553. Default material library (MT9)? c:mcam91milltoolsmatls.mt9

554. Default setup sheet template? swag setup sheet access csv.set

555. Default operation library (OP9)? c:mcam91millopsoperat.op9

556. Default operations and job setup file (DF9)? c:mcam91millopsdefaults.df9

 

---

code:

---

[communications]

600. Format: (A)scii, (E)ia or (B)inary? A

601. Communcations port number (1 or 2)? 1

602. Baud rate (110,300,600,1200,2400,4800,9600,19200,38400)? 38400

603. Parity (E/O/N)? N

604. Data bits (7 or 8)? 7

605. Stop bits (1 or 2)? 1

606. Delay after end of line (seconds)? 0.00000000

607. Echo keyboard to screen in terminal emulation (y/n)? y

608. Strip carriage returns (y/n)? n

609. Strip line feeds (y/n)? n

610. Read parameters from PST file (y/n)? n

611. Handshaking (0=None, 1=Software, 2=Hardware)? 0

612. DOS communications mode? n

613. Display to screen? y

---

To name just a few. Notice that it points to certain tool/operations libraries that can be specific to that machine.

 

'Rekd