right click to edit propertie of an axis. Is that what you mean?

Bruce, You have 2 choices in the op for how to change these defaults, 1. do it in the op defaults 2. do it in the control def for the machine. control def overrides op defaults, to my understanding. Also, I do not believe that either will override values in existing operations, so on any program you've got that already has paths assigned you will have to go in and manually change. In addition, any parts that you have programmed prior to changing the disk copy of your control def will have to be changed as well. Plus, if you open an existing file using your previous (unedited) control def, you will have to re-load the machine (properties, files, replace) with the updated machine to create a new toolpath copy of the new machine to work with. I take a lot of calls from customers having trouble nailing down where to make these changes so that they will stick. Hope that helps

Some basic Idea of computer programming helps, as well. Knowing how if/then statements and understanding how to initialize variables, what the heck a string is, and how flags work are really helpful. In my own experience, I suggest that when making any change first check the numbered questions and the variable initialization to see if what you want is already available as a switch, wherein you only have to make one small change of one number/value. You can also check in your post and read through what the misc. values do so that you may properly set those in mcam. Oh, and BTW. Backups are for sissies (who like pulling out their hair) HTH,

ligrow, when creating a line tangent to an arc, just use the create line endpoints and allow the autocursor to highlight an arc. crossing over the arc itself switches the tangency from a positive direction to a negative, and after you sketch a second endpoint you can change the angle as you see fit in the ribbon bar. On questions like this, you can use the above mentioned V9 to X function map as an invaluable resource, but the neat little functionalities of the command that have altered since V9 are not fully explained. I would recommend watching the introducing mastercam X video at least twice for any new X user. This will help you in seeing some of the neat functions with creating linesendpoints, and it will also give you some insight into the way X works.

Is anyone out there programming a C-axis lathe with polar moves? How does this work? The machine in question is a mori seiki 240 CC with a conversational control that can output polar coordinate moves on the C axis, which cuts a lot of program size off the part. Can we substitute this using Mcam? if so, How?

Indeed.

quote: Basically a direction vector telling giving the machine info, so it knows how (in what direction) to cancel Comp, which occurs in N190 which is the lead-out move off the contour (back to the Thread Pt. position in this case). from what do I derive the value of the dummy move? Is it always 1"? Now the real kicker... do any of CNC's posts do this automatically? I've looked at agie.pst and at mpwagie.pst, of which agie.pst gives me an error "path not found" when I select it for use and mpwagie doesn't appear to make these moves. how would I change MPWAGIE to include this manner of cutting? OR do I need to re-evaluate how I'm drawing/chaining my geometry? If you recommend a different plan, I'd be very thankful to hear it. Thanks a great deal, regardless, that lesson helped a great deal already. Thanks again,

Wire V9.1 Can anybody (I'm hoping roger martin is out there somewhere) explain to me how the dummy moves need to look for older agie machines? I'm working on a post for an agiemeric CNC 100 and I have been reading about the parameters. I've noticed from my searches that a lot of the old agie machines require dummy moves, and some of the documentation looks that way as well, but I can't seem to understand how these dummy moves work... could somebody explain it to me? Thanks

John, Still not having any luck on that. IS there any way you could send me an example csv file? Mine that I'm trying is just an excel file with level names in the first column. Thanks

quote: You could also create a .csv file(excel) with levels pre-named and load that into X John, How does this work? once you create the CSV file, how do you load it into mastercam? Also, Does it work for mastercam 9 as well? Thanks

Jeff, (to further Spade's reply) Changing any of the attributes of existing geometry is actually easier, I think, than it was in V9. In X, simply highlight any geometry you want then right click on the attribute you want to change at the bottom of the screen. It also works if you don't have any geometry selected, that is, if you right click on any of the attribute Icons, you will be prompted to select the geometry to which the change will apply. I think this is a big time saving improvement from having to exit out of everything you're doing and enter the screen>change color business. JM2C. Hope that helps a bit.

I would think Tommy Dorgan Would have something to input on this.

Del, You should still be able to program with that error. You will just have to manually change your power setting. I am still awaiting a fix from CNC HTH

I believe I am having a problem that fits into this one. HTML setup sheet from V9 when properly loaded in X will not work. (HTML.set) Gives an error stating “cannot find SETUPSHT.doc in folder C:McamxMillNCI” and then opens internet browser window to specified homepage. Anybody out there had this problem?

Welcome to the forum class! Now Get Back to work!

Thanks, Paul. I'll try that

Welcome to the forum, Murray Mold! You've come to the right place. Did you get the file I sent? Let me know when you get a chance to try it out. Thanks,

I hope this helps, I just fixed this problem in a post I had for another customer with a hurco post. In the post: First I narrowed it down using the debug info tracking down where the missing "e$" was. There wasn't a missing e$ anywhere on the post side so I nailed down the best place to put one and inserted one in the lines of code, this way, nomatter where the missing end of block was, it jumped to the next line. I figured if I can't get rid of that extra seq/. #, maybe I can move it to the next line. SO I inserted an e$ here: ptlchg0$ # Null tool change 1000 e$ if comment$ = 1, n$, popcode,e$ pr pcan n$, sgplane, ss$,e$ if prv_z$ <> zr$ & op_id$ <> prv_op_id$, n$, psg00, zr$,e$ if prv_c$ <> c$, protary pstorfr !op_id$ I then found that I needed to put another one in the plin section, and I'm still testing it but I think that got it. HTH

Woo Hoo!

AT least it is maintained like the other drop downs, where after you use it the last one you use jumps to the surface for one-click. I really don't think it's that bad.

Thad, I don't know of a technical term for it, and none of the videos from Mcam I've seen call it anything. I think if I were to call it anything, I would call it the fastpoint toolbar. For those of us out there who want that to be more useful, you may try putting a flyout in your right mouse button to have this option there. It's in the autocursor category. HTH

Right on brett! I was racking my brain trying to find the concversion to arcs. Bill, You'll be looking for linarc$, should be in the pinit section of the post.

Bill, which post and machine def are you using?

Bill, If yer using Mcam X, check your control def under "arc" and look for the break options. the questions sleepy's referring to above were replaced in X posts by the control def options. HTH.

quote: You can force autocursor by selecting from the dropdown menu a little to the left of All and Only. That would be this little guy right here: HTH. I find that frustrating too, but I think the new autocursor's usability outweighs this problem, IMO