Welcome to eMastercam

April 5, 2006

No longer works in my 9.1 Sp2.

MastercamScriptEditor.dll: Build 1.0.116 on 12-16-2003

mcamvb.dll: 1.0.0.1 on 12-16-2003

Am I out-dated? I couldn't find more current dlls.

[ 04-05-2006, 01:12 PM: Message edited by: Rekd ]

Mastercam X - User Interface Survey · December 29, 2005

quote:

The Mastercam interface is the most highly configurable interface I've ever seen in ANY application. If your spending too much time moving up and down the screen grabbing the button you need,

you need to create you own Right Mouse Button (RMB) menu. Or create you own floating tool bar.

It's new. It's different. Some will like it, some wont.

CNC did a great job. They've got more to do, obviously, but they've done a great job so far.

November 23, 2005

quote:

The most important thing to be aware of, It does not function correctly if you turn on cutter comp. In v9.1sp2 and 9.1mr0304, If you set the compensation type to Control or Wear or Reverse the results will not be what you would expect. Usually mostly it does not decelerate into the corner. But it does drop the feedrate at the corner and accelerate out. Use "Computer" comp for best results.

Thanks for the help!

September 12, 2005

LoL, I thought you were going to suggest a 'time-out' box for people that use bad language.

September 2, 2005

I'm with john. Unless you've got a 2kb memory card in your machine, more info is better.

August 17, 2005

Here's what I'm referring to...

August 17, 2005

In v9 I could toggle "Operation Types" on or off in the display, that has been removed from X.

Can I have it back?

Please?

August 17, 2005

quote:

Remember what wasn't broke , don't fix it!

Um... I thought it was a complete re-write, so EVERYTHING is new.

You might consider playing with it for 'simpler' parts so you can get used to it. It's really not that much the same as older versions, so you're pretty much learning a new program.

August 16, 2005

quote:

It'll help us track it down (and help others avoid it) if you could share a little more information about how you got that to happen.

:sarcasm:

But it's so much more fun to bitch and complain about the bad and ignore the good...

:/sarcasm:

August 15, 2005

If you don't have solids, you can't modify them.

August 12, 2005

From the chinese site referred above...

quote:

Attention: But explains

the version is not extremely stable frequently needs you re- starts the permission procedure

LMAO, duh...

August 12, 2005

You can measure a verified part.

Looks like the same engine, though.

August 12, 2005

Glenn, just a thought, but what if you tried creating a new fillet on that corner? In 9 it would prompt you about filletting existing fillets, but I'm not sure the result to the solid.

Might be worth a shot.

August 11, 2005

quote:

I just recently stumbled upon the divide function when trimming. I used to always break the line, them trim it. Talk about feeling like a dumbass!

x2

August 10, 2005

quote:

Call SetCurrentFileName(Files(m-1)) ' <- this appears to do nothing at all

I tried that too, with the same result.

quote:

Sounds like a request to QC should be put in.

Yep.

Thanks.

August 10, 2005

*bump*

I know I'm old fasioned, but anyone got any ideas??

August 9, 2005

I use Misc Values. Toggle MI10 to 1 and it parks the machine. It also prompts for a comment to put with the M00.

Define the variable for comment prompt

code:

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

# User Defined Questions

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

fq 3 stopcomment M00 found for: //t//; //strtool//. Enter a Comment...

Make the sub..

code:

pstop      # Stop routine ()

pretract

q3 #Stop Comment?

stopcomment = ucase(stopcomment)

if stopcomment = "", n, "M00", e

if stopcomment <> "", n, "M00", "(", *stopcomment, ")", e

# n, "M00", e

if wcstype > one, absinc = zero

n, *spindle, *speed, pgear, strcantext,e

pcan1, pbld, n, *sgcode, *sgabsinc, pwcs, pfxout, pfyout, *cabs, E

pbld, n, "G43", *tlngno, pfzout, scoolant, next_tool, e

absinc = sav_absinc

Call the sub (last line in my case)

code:

ptlchg0         #Call from NCI null tool change (tool number repeats)

pcorner_round

if mi7 <> 0, pdump

pcuttype

pcom_moveb

toolcount = toolcount + 1

prvtp = rbuf(3,toolcountp)

if toolcountn <= tooltotal, nexttool = rbuf(4,toolcountn)

else, nexttool = first_tool

if mi10=one & op_id<>last_op_id, pstop

Results

code:

N2722 G01 G40 Y1.9688

N2723 G00 Z1.

N2724 M09

N2725 G91 G28 Y0. Z0.

N2726 G90

N2727 M00 ( RETENSION )

N2728 M03 S6800

N2729 G00 G90 X.3713 Y3.2288 A0.

N2730 G43 H2 Z1. M08

(OPERATION: 47 POCKET)

N2731(OP 1)

N2732(UPPER POCKETS RETENSION)

(T2: 3/16 CB EM 4FL TICN)

( TOOLPATH - POCKET)

( STOCK LEFT ON X & Y = 0.)

( STOCK LEFT ON Z = 0.)

N2733(OP ID: 8)

(I may not have shown all the variables)

Or you could use Manual Toolpaths, but that's not as robust.

August 9, 2005

Lately I've been getting longer and longer delays when bringing up the file/get dialog. Some times up to 20-30 seconds or more.

I'm making a script to read the recent files from the reg and prompting to open one of them.

Seems to work ok except that it's not using the name in the title bar, and when I go to File/Save, it doesn't have the name.

How can I open a file via the script and have it actually display the name like it does when using File/Get, as well as having it use the file name when saving?

code:

askNumber "Enter file number", 1, 10, m ' prompt

NewMC(0) 'initialize a new file

OpenMC(Files(m-1)) 'open file

Also notice the NewMC(0) line. If I don't use it, it seems to merge the current file with the one I'm opening, but still doesn't have the name.

August 8, 2005

quote:

In X ALT-A is only used to set the time interval between saves. Autosave will save when the time interval is reached but not if you open the dialog box and then close it.

That means the bug in autosave is fixed? When I open autosave to disable it, it saved when I close it, after I said I don't want to use it... :/

August 2, 2005

post snippits from each post.

July 29, 2005

Lars,

Looked at your file and I'm not sure which way to go. Only thing I can suggest is that you run finish passes for the tools that are going in those holes.

i.e. bore the big holes, drill the small holes, then bore the big holes again then drill small ones again. That will knock a lot of the burrs off, and might make it easier to deburr them by hand if that's an option.

HTH

July 23, 2005

Copied from my reply on CNCzone.com

Look for General Output Settings in your post and switch it to zero.

code:

# General Output Settings

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

arcoutput : 0 #0 = IJK, 1 = R no sign, 2 = R signed neg. over 180

You might have to force output on arc moves as well.

July 23, 2005

quote:

youens

I thought it was yunes? Oh, that was Penn. N/M.

July 22, 2005

quote:

oh hey Rekd I typed slow so that you can read this at home.

Time to play my favorite game; What finger am I holding up???

July 21, 2005

Have you tried this?

code:

# Additional General Output Settings

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

...

progname : 1 #Use uppercase for program name

...

Sign In

Welcome to eMastercam

Profiles

Forums

Downloads

Store

eMastercam Wiki

Blogs

Gallery

Events

Posts posted by Rekd™

Join us!

Useful Links

Legal

Follow us