Dennis, I do not know what version of MC Wire you have, but I would suggest trying the MPW-FA10.PST on the (v9 and higher) CD. It has several common configuration options. Check the 'User Preference Settings' section in the PST.

+1000 to Mike on this one! Take 30 seconds and post your toolpaths using an "unmodified" mpfan or mpmaster post. This can save you a lot of wasted time guessing as to where the problem is! [ 05-28-2004, 04:38 PM: Message edited by: Roger Martin from CNC Software ]

Lars, What you need to do is tell the PST that you've output the 'F2.0' feedrate. In your logic that output the "F2.0", try adding a line that reads-> prv_fr = 2

Lars, THe Feedrate problem is most likely caused by your "F2.0 at the G40 line". You've changed the Feedrate, but the PST doesn't know this. Specifically which MITS post are you using? Also, what Version of MC is that PST from ? Knowing that, it should be a simple fix.

Brent & Lars, If the change from STCW to Thread & Cut points is too much, you're going to freak when you see X! Seriously... The Thread/Cut point method gives you a lot of power and flexability over the old STCW. I know, I've heard it before "STCW was easier". You just need to get in there and use the Thread/Cut method and you'll find it is no more work than STCW, but actually can save you steps much of the time. Many times you don't even need to define a Cut Point! And if you're doing multiple contours, it's the way to fly!

Short answer -> you don't.

itspaul, I know that the MC communication will not do man-readables. I doubt the CIMCO DNC will either, but I cannot say I'm positive about that. You could check with -> CIMCO Integration

Dave, The technical term for that '2' is -> typo But '2' should have the same effect as '1'

camguymtl, First... What information are you trying to gather from the tool(s) in the file? Depending on what data you want/need, you may not need to use Buffers. Setting the variable 'tooltable : 2' so that the (pre-scan) PWRTT postbock is called allows for gathering quite a bit of information.

Come on Charles... You're ruining it for me! I was hoping that Mike would bite on this. And after he tried it, I could find out how it well it works - before I attempted it.

Come on Charles...

quote: Running a tape punch is a communications issue. Steve said it right. You could use the CIMCO or the Mastercam communications to punch tape. I've done it using the MC communications to several different tape punches. It usually involves a lot of trial & error, but it's definatley do-able.

Method 1 -> From the Main menu in the Wire system, select Screen, Chg attibs, enable the Point Style option and select Wire Thread from the dropdown list. Now just go and select you point(s) and they become Thead Points Method 2 -> Use the TCPOINT C-Hook. *This C-Hook came with the MR0304 maintanance update.* If you have this, check out the TCPOINT.DOC in the CHOOKS folder. The .DOC explains how to use it and how you can (optionally) integrate it into the Wire system menus.

quote: At this time, all of my thread points will an additional point, separate of the chain. That is almost always going to be true. What I was fishing for is, do you have to change plain ol' regular points into Thread Points? There are a couple way to do that, other than creating a Thread Point on top of the regular point, and then having to delete the regular point so you don't select it when you go to chain up your wirepath.

quote: I was thinking of building one with a spare box. Mike, Check this out, sounds very interesting... A Cool Alternative to Media Center and TiVo

Troy, Are the drawings you are supplied with already have a point for the Thread Position? Meaning you need to change a regular point into a Thread Point so you can use it for chaining. Tim is correct in that -> ...you should always create your start point (Thread Point) where you want to begin your cut. I try not to use the term Start Point when refering to Thread Point - they are differnet. Start Point is not necessarily where you being burning, the exception is if you have not defined a Thread Point to tell the system where the thread the wire and begin the burn. When you do that (not recommended) the only thing the system has to work with is the Start Point.

Mike, SATA Hard Drive: 36GB 10K SATA150 Hard Drive It is a 10,000 RPM drive. They are supposed to be screaming fast and you want too make sure they have good cooling. I've seen them only in 36GB or 74GB. Could be larger ones out there - but even the 36 & &74's are expensive. About twice the price of a good 7200RPM drive that has double the capacity.

Murphy, Post Name : MPW-CF240 Description : Charmilles Robofil 240 with Fanuc control Contact your MC Dealer, they can get this for you.

Output from your HELIX TEST.MC9 using the MPFAN.PST (from Mill v9.1SP2) G0 G90 X-.0007 Y-1.0156 A0. S4000 M3 G43 H1 Z.25 Z.1 G1 Z.075 F15. X-.0904 Y-1.0116 Z.0736 F10. G2 X-.0912 Y-1.0115 R.0156 F.01 G1 X-.106 Y-1.0101 Z.0733 F10. G2 X-.1069 Y-1.01 R.0157 F.01 G1 X-.1951 Y-.9967 Z.0719 F10. G2 X-.1959 Y-.9966 R.0157 F.01 G1 X-.211 Y-.9935 Z.0717 F10. G2 X-.2118 Y-.9933 R.0157 F.01 G1 X-.2984 Y-.9708 Z.0702 F10. G2 X-.2992 Y-.9706 R.0156 F.01 G1 X-.3137 Y-.966 Z.07 F10. G2 X-.3145 Y-.9657 R.0156 F.01 G1 X-.3982 Y-.9343 Z.0686 F10. G2 X-.3989 Y-.934 R.0156 F.01 G1 X-.413 Y-.9279 Z.0683 F10. G2 X-.4137 Y-.9275 R.0157 F.01 G1 X-.4937 Y-.8876 Z.0669 F10. G2 X-.4944 Y-.8872 R.0157 F.01 G1 X-.5077 Y-.8796 Z.0667 F10. G2 X-.5084 Y-.8792 R.0156 F.01 G1 X-.5837 Y-.8311 Z.0652 F10. G2 X-.5844 Y-.8306 R.0156 F.01 G1 X-.5969 Y-.8217 Z.065 F10. G2 X-.5975 Y-.8212 R.0156 F.01 G1 X-.6674 Y-.7655 Z.0636 F10. G2 X-.668 Y-.765 R.0156 F.01 G1 X-.6795 Y-.7548 Z.0633 F10. G2 X-.6801 Y-.7543 R.0157 F.01 G1 X-.7438 Y-.6916 Z.0619 F10. G2 X-.7443 Y-.691 R.0157 F.01 G1 X-.7547 Y-.6797 Z.0617 F10. G2 X-.7552 Y-.6791 R.0157 F.01 G1 X-.812 Y-.61 Z.0602 F10. G2 X-.8125 Y-.6094 R.0156 F.01 G1 X-.8216 Y-.5971 Z.06 F10. G2 X-.8221 Y-.5964 R.0157 F.01 G1 X-.8713 Y-.5218 Z.0586 F10. G2 X-.8717 Y-.5211 R.0156 F.01 G1 X-.8795 Y-.5079 Z.0583 F10. X-.8797 Y-.5076 F.01 X-.8953 Y-.4795 Z.0578 F10. Z.1 F6.16 G0 Z.25 Yes the 'helic_arc' switch setting affects what the PST outputs, but it is the input to the PST that is important here. The filter will... Create arcs in XY Create arcs in XZ Create arcs in YZ The important word here is Create arcs IN XY plane. So what the data the PST is getting to process are arcs segments IN the XY plane and the XYZ linear moves to ramp down to the next arc segment. Segment of NCI input to the PST (with <- Linear & <- Circular comments added) -> 1 <- Linear 0 -0.090406 -1.011576 0.073571 10. 3000 2 <- Circular 0 0 -0.091219 -1.011518 -0.089704 -0.995967 0.073571 0.01 0 0 1 <- Linear 0 -0.106044 -1.010073 0.073333 10. 0 2 <- Circular 0 0 -0.106853 -1.009973 -0.104528 -0.994522 0.073333 0.01 0 0 1 <- Linear 0 -0.195102 -0.996694 0.071912 10. 0

quote: I created a 3/4 turn simple helix. xy plane about .1 pitch in the z direction. Andy, What method was use to create this?

The values you are looking for are in the .OPS file that gets build when you post. This means that this line in the .PST (or .SET) must be set to tell the system that you want the OPS file -> code: 1502. Write operation information to binary file (.ops)? y Below is some code stripped out of the MILL.SET (from v9.1SP2) A couple variables are declared to hold the values sucked in from the OPS file -> code: # Variables to hold info read from 'additional parameters' fmt 2 stock # Amount of stock to leave fmt 2 zstock # Amount of stock to leave This pparameter postblock is called 'automatically' to read the OPS data. The command -> code: result = fprm(opcode) # Run the parameter table for current OPCODE tells the PST to look for a 'fprmtbl' for the OPCODE being processed. You can add these 2 lines into your pparameter postblock to see what is being read from the OPS -> code: pparameter # Read in the 20000 series 'additional parameters' from OPS file "OPCODE = ", ~opcode, e #<diagnostic> "PRMCODE = ", prmcode, " = ", sparameter, e #<diagnostic> result = fprm(opcode) # Run the parameter table for current OPCODE A 2D Mill contour is OPCODE=2, so the 'fprmtbl 2' (Parameter Table #2) gets executed. The command in this prmtbl tells MP to load the value from parameter '10010' (10010 is the 'prmcode') into our 'stock' variable, and the value from parameter '10068' into our 'zstock' variable. code: fprmtbl 2 2 #[contour] 10010 stock # Amount of stock to leave 10068 zstock * This '307 parameter Information.PDF' of the Post Reference Guide documents this stuff. * This last 2 pages of that PDF explains a 'bute formce' method of determining the 'prmcode' for a specific .OPS file parameter. * This is "usually" quicker than looking thru all the tables of documentation to find the approriate 'prmcode'!

I assume that you tried the Options->Program Setup->Partners->Mastercam dialog in The MetaCut Utilites That is the real way how to configure MCU's integration in MC If that just does not work, and you know what you are doing in the Registry... **** Think is all the warnings you've read about editing your Registry. They apply here. *** Under this key are the config settings -> HKEY_CURRENT_USERSoftwareNorthwood DesignsThe MetaCut UtilitiesMCU2CAM Setting the value to 0 (Zero) will disable any MCU integration with the specificed MC CFG file.

quote: I was wondering what is it about the VB script that makes MC NOT run the startup chook, but still performs other "setup" type functions according to my config file. There is only one "execute type" startup item, the rest as you say are "setup" type items. quote: You have over-ridden the startup with the FileGet.VBS in your shortcut that starts MC

Ahhh... I read MCU and thought MetaCut MCU.... Easy fix! You have over-ridden the startup with the FileGet.VBS in your shortcut that starts MC So you just need to add MCUTILS.DLL into your script -> code: Call Main Sub Main RunMastercamCommand "fileget" RunMastercamChook "SETDIRS.DLL" RunMastercamChook "MCutils.DLL" End Sub

quote: what exactly was it about that script that didn't allow the MCUtils Thad, The combination works for me. (Tested with Mill v9.1Sp2 & MCU Light v2.13) The only MCU integration setting I have is -> Add MCU button to Operations Manager And it is still there on the Op. Manager if I use the fileget.VBS startup script. What is your MCU integration? Put another way, what part of MCU fails start if you use Mick's script in the MC startup shortcut?