New MP.DLL (9.15)

[gcode]

I noticed that there is a new mp.dll download

in the patches section dated 7/29/03.

Can anyone tell me what has been added (or fixed)

with this new file? TIA

 

edit

The download mpv915.exe adds a file named

mpparam.dll to the root Mastercam folder.

In my clean install of V9.1 SP1, there is a copy

of mpparam.dll dated 02/20/03 in the MC root folder

In my CHOOKS folder there is another copy

dated 5/21/03.

Which folder is the correct location for mpparam.dll, the Mastercam root or the CHOOKS

folder ????

 

[ 08-02-2003, 12:40 PM: Message edited by: gcode ]

[Rekd™]

The only thing I'm aware of is the new function for posts that allows you to call a vb script from the post without going thru the vb script dialog.

 

runVBS()

 

I've tried using this, but either it is ignored or it generates an un-declared variable error.

 

I was hoping for some info about how the syntax works, here's what I've tried:

 

runVBS(strScriptName) (with variables declared)

runVBS(scriptname.vbs)

runVBS("scriptname.vbs")

runVBS(C:Path to scriptscriptname.vbs)

runVBS("C:Path to scriptscriptname.vbs")

 

'Rekd

 

[ 08-02-2003, 12:55 PM: Message edited by: Rekd ]

[Guest CNC Apps Guy 1]

Nice sig rekd. That's hilarious.

[Roger Martin from CNC Software]

MP v9.15 -> added the RunVBS() command and corrected a problem with the value of the pre-defined variable ARC_PITCH always being ZERO.

 

'rekd -

Are you sure you are running MP.DLL v9.15?

 

To determine the version of MP.DLL

(or MPL.DLL, MPWIRE.DLL)

 

1. Locate the desired file using Windows Explorer

(in the Chooks folder of the Mastercam installation).

2. Right-click on the DLL file.

3. Select "Properties" off the drop-down menu.

4. Select the "Version" tab.

5. Select "File Version" in the "Items name" list.

6. Read the "Value" (to the right).

 

Check out the sample files in the "Run VBS sample.zip" located the 'VB_Scripts' folder on the Forum FTP site.

 

The MPPARAM.DLL goes in the MAIN Mastercam directory, with MILL9.EXE (NOT in the CHOOKS!)

[gcode]

"The MPPARAM.DLL goes in the MAIN Mastercam directory, with MILL9.EXE (NOT in the CHOOKS!)"

 

If this is the case, the SP1 update files need to be changed. I had several versions of V9 and a couple of beta versions on my box.

I uninstalled all of them and deleted their folders.

I did a fresh install of V9.1, then applied all the SP1 files. Mastecam has been very stable

and much faster. However, per my first post on this subject I had an older version of

mpparam.dll in my MC91 folder and the new one

(from the chooks patch???) in the chooks folder.

 

edit

The version that I downloaded from the patches

folder this weekend is labeled 9.10 SP1 Beta1

 

[ 08-04-2003, 09:29 AM: Message edited by: gcode ]

[Rekd™]

Roger,

 

MPPARAM = 9.1

 

MP = 9.15

 

I can't connect to the FTP site for the samples, can you post a link to it, or email it to me?

 

Thanks.

 

'Rekd

[Mick from CNC Software Inc.]

Rekd,

 

Off the top of my (jet lagged) head put the Call keyword infront of the command.

[Roger Martin from CNC Software]

Rekd,

 

RunVBS() is a "File FUNCTION", which means it has a return value ->>

 

# Define a string that holds the name of the VBS script to be run.

strVBS "c:mcam9vbstrip_comments.VBS"

 

# Define a numeric variable to hold the value returned by the RunVBS() function.

result : 0

 

#Run the VBS script (FULL Path/Name is required !)

result = runvbs(strVBS)

[Rekd™]

Thanks, Roger. Now it's working. Looking forward to the samples. I replied to the email.

 

'Rekd teh too much fun

[Rekd™]

Roger,

 

I got the files. Thanks.

 

It's looking for mp_vbs.dll as the post executable, I changed it to mp.dll and ran it, it made it thru, but didn't strip the comments from the file. Is there another post executable, mp_vbs?

 

'Rekd

[Roger Martin from CNC Software]

My bad...

 

This line in the sample MP_VBS.PST should read ->

 

91. Name of executable post processor? MP

 

Once you make that change, I'm sure it DID strip the(COMMENTS)!

 

Check the same directory where the your NC file was placed. By default the VBS script "dresses" the input NC filename with "CLEAN_" to create the filename for the NC file - with all (COMMENTS) stipped out.

 

If your operations would be creating TEST.NC

You will end up TEST.NC (un-altered) and CLEAN-TEST.NC (stripped of COMMENTS)

 

Check the top of the VBS script for details on how you can alter this behaviour.

 

[ 08-04-2003, 04:06 PM: Message edited by: Roger Martin from CNC Software ]

[Rekd™]

TY!

 

'Rekd teh Life Is Good