V9.1 Patches Setup sheet problem

[Davidgil]

I just looked for a address on the mastercam website to e-mail bugs and didn't find one. Can someone post where I should send bugs I find as I would like to send them the following probable bug:

I just installed the updated patch to fix the setup sheet, and found that I was now able to use the .set. The problem I am finding now, however, is that if there is a remachine operation the setup sheet will post many entries for the same remachine operation. To find the error on my end I did the following: Create a rectangle. Create a contour operation using 1/4 endmill to machine down .305". Create a remachine operation using 1/8 endmill to machine areas not covered by 1/4 endmill. Post as normal, and then run setup sheet using mill2.set.

Thanks much,

Dave

[ProductDevelopmentGuy]

Send bugs - including a thorough description and any files (MC9 or otherwise) - to [email protected]

 

PDG

[Davidgil]

Thanks PDG

[Davidm]

I also am experiencing the multiple entries on setup sheet for each depth cut of single operation. I am using html.set and when setup sheet is produced the .nc file is lost or overwritten as well.

[Allan Brown]

Sounds like null toolchanges for depth cuts are being picked up as full toolchanges in the post. This would be an NCI issues I believe. I've added logic in the HTML.set to avoid this current issue.

 

Remnants from the switch to .pst back to .set are responsible for wiping out your NC files. I've corrected this - thanks and 'oops'. Updates in the Tools and Patches areas.

 

[ 04-17-2003, 12:24 PM: Message edited by: Dave Thomson ]

[Davidm]

Thank you

[Davidgil]

Thanks,

Dave

[Randy Walker]

After installing the patch I was able to use the setupsheet with the rightclick menu option but it provides information about the null tool changes which is way too much information to print. I still use my work around of nameing my setup sheet with a .pst extension and post it from the post menu.

[Davidgil]

Randy,

You're not alone. We are still having the same problem here.

Dave

[NYMike]

The strange thing is I can get the setup sheet right one time and then it comes back to the problem and lists the same tool for each depth.

????????

[Roger Martin from CNC Software]

To fix the multiple tool data outputs in an existing .SET Setup Sheet generator...

 

Add the four (4) lines of code to your .SET file as shown below ->

Search for the 2nd occurrence of "psetup" in the .SET file.

(This will be at the END of the PSOF postblock)

Add the 4 lines marked: #Added (4/22/03)

in this section of the .SET file ->

 

code:

---

psetup # Call for toolchange info output

!op_id #Added (04/22/03)

 

 

ptlchg0 # Null tool change

!gcode

!op_id #Added (04/22/03)

 

 

 

ptlchg # Output of time calculations for the last tool run

if op_id = prv_op_id, ex # If True, NOT a real toolchange - Added (04/22/03)

 

ptooldata # Output ending data for tool (X,Y,Z, Feed limits, Time)

" ", e # Blank line

tmax_fr = fr # Initialize (max fr used in current tool)

tmin_fr = fr # Initialize (min fr used in current tool)

psetup # Call for toolchange info output

!op_id #Added (04/22/03)

---

**** NEW ****

In addition to the above changes....

You want to add the addtional changes shown ->>

 

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

 

Now search further down on the .SET file for 2nd occurrence of "pwritbuf1"

Add the one (1) line marked: #Added (4/22/03)

into this posblock ->>

 

code:

---

pwritbuf1   # Write Buffer 1

b1_gcode = gcode

if gcode = 1002 & op_id = prv_op_id, b1_gcode = 1000 #Added (4/22/03)

b1_tcode = t

b1_xmax = x_max

b1_xmin = x_min

b1_ymax = y_max

b1_ymin = y_min

b1_zmax = z_max

b1_zmin = z_min

b1_gcode = wbuf(one, wc1) # Write the record

---

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

 

*NOTE* the following change is NOT needed in the MILL2.SET or ROUTER2.SET

 

Now search further down on the .SET file for the occurrence of "pwritbuf2"

Add the (2) lines marked: #Added (4/22/03)

into this posblock ->>

 

code:

---

pwritbuf2   # Write Buffer 2

b2_gcode = gcode

if gcode = 1002 & op_id = prv_op_id, b2_gcode = 1000 #Added (4/22/03)

!op_id #Added (4/22/03)

b2_ccomp = ccomp

b2_cc = cc

b2_cc_computer = cc_computer

b2_gcode = wbuf(two, wc2)

---

 

[ 04-25-2003, 05:51 PM: Message edited by: Roger Martin from CNC Software ]

[NYMike]

Roger,

Will there be a patch to correct this in the near future?

[Roger Martin from CNC Software]

quote:

---

Will there be a patch to correct this in the near future?

---

Yes, there will be an update.

In the "near future..." How near is near?

I cannot tell you a time frame, since...

1> I don't know it.

2> I don't control it.

 

The .SET files on the v9.1 CD are not the

problem, these changes to the .SET files

are designed to work around the root problem.

 

In addition, I plan on having updated SETs ->

MILL.SET, MILL2.SET, and MILLM.SET

ROUTER.SET, ROUTER2.SET and ROUTERM.SET

available for download from www.mastercam.com

on Monday.

(I will post a message when they are available)

 

*Note that ->

These updated SET files will be the SETs that

were on the v9.1CD with the changes shown in

my previous posting ^^above^^

 

Please see my previouis posting.

It contains *NEW* information!

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

[NYMike]

Thanks Roger.