MPBinX Guide Reference Mastercam 2017
MPBinX Guide Reference Mastercam 2017
Quick Start
Notes:
During encryption, MPBinX removes all code between [STARTBIN] and
[ENDBIN]from the original post file. The resulting .PSB file contains the
removed code in encrypted form.
You can select a .PSB that has already been encrypted if its associated .PST file is
also present. Simply insert new [STARTBIN] and [ENDBIN] tags in the .PST file.
You can delimit any amount of text—from one line to the entire post processor
file—with [STARTBIN] and [ENDBIN]. However, we recommend that you leave
whatever code the user needs to make minor modifications without your help.
MPBINX USER’S GUIDE / Encrypting a post with MPBinX • 3
3 In the Post processor filename field, select the .PST or .PSM file to be encrypted.
4 Select the Target directory. MPBinX writes the encrypted post and log files here.
5 In the Options and SIM type access selection boxes, choose the level of
protection. You can encrypt the post in either of two ways:
To run only on specific SIM or software license numbers.
To run only on specific types of SIMs. (See the guidelines below.)
6 To prevent the post from being updated:
7 Click OK to process the files and close the dialog box, or click Apply to process
the selected files and leave the dialog box open.
8 Click View log file to review the results. MPBinX writes the log file to the target
directory as mpbinx.log.
9 Distribute the new .PST and .PSB files to the end user. Save the original post file
(the one you chose in Step 3) so that you can create new .PSB files, as needed.
4 • REV: MAY 2016
Encrypting posts for specific SIM numbers or software license numbers—The advantage
is that the post binary file will run only on a computer with one of the specified SIM
numbers or software licenses. Users cannot read or modify the post, nor can they share
the post with other users. The disadvantage is that a separate post binary file must be
made for each specified SIM or software license. When the original post is changed, new
binary files must be made for each user.
MPBinX supports three types of license numbers:
SIMs (HASPs)
Software license container number (X9 only)
Software license numbers (beginning with Mastercam 2017)
When encrypting by SIM number or software license, use the SIM number(s) window in
to list all of the valid SIMs or software licenses for which the post will run. When MPBinX
processes the post, it generates a separate output file for each number.
See Binning a post to a software license number on page 7 to learn more about software
licensing.
6 • REV: MAY 2016
TIP: You can mix-and-match SIM numbers and software license numbers in the
same list or text file.
MPBINX USER’S GUIDE / Guidelines for encrypting a post • 7
If you are binning to the container number in X9, only use the 7 digits after the
dash.
If you are binning to the license number in Mastercam 2017, do not include the
W—only the 5-digit number.
8 • REV: MAY 2016
If you are using the most recent version of CodeMeter, the interface will be different. The
screen will look like this:
Quick Start
NOTE: If you are binning to an Eval license, please be aware that if the customer
purchases the product, the license number WILL change and the post will need to
be binned again!
Similarly, if an Eval period is extended with a new license, the license number will
also change and the post will need to be binned again.
Please refer to Mastercam’s Software Licensing Guide to learn more about software
licensing and CodeMeter containers.
MPBINX USER’S GUIDE / Re-encrypting a .PSB file • 9
NOTE: This option is only available to Resellers who are running MPBinX on a
Dealer SIM.
4 Enter and confirm the desired password into the Password Protection fields.
By default, the only SIM or software license authorized to update the post with the
UpdatePost C-Hook is the one displayed in Your SIM Number. You can type additional
authorized SIMs in the Additional SIMs Allowed box. Or, you can load a list of SIM
numbers from a text file. See Storing SIM or license numbers in a text file on page 6 to
learn more.
MPBINX USER’S GUIDE / Locking posts from being updated • 11
Quick Start
12 • REV: MAY 2016
MPBinX can also be used to encrypt the machine definition files used for Mastercam
Simulation. You can choose to encrypt either the XML machine definition file, PRM files,
the STL files that store the component models, or any combination.
To encrypt machine defintion files, follow the same process as Encrypting a post with
MPBinX on page 3 and select the desired machine definition files.
While PST files that are encrypted need to be prepared with [STARTBIN] and [ENDBIN]
tags, no such tags or other preparation are needed for machine definition files. For each
selected file, the entire file is encrypted.
The STL files might be either ASCII files or binary files. MPBinX will automatically detect
the file type and process it appropriately. Because of this, you typically do not need to
select the binary files option:
Encrypted machine definition files will have a modifed extension that can be used to
identify them:
Text files that are encrypted will have -TBIN appended to their extension. For
example, Integrex-MarkIV.XML will be encrypted as Integrex-
MarkIV.XML-TBIN.
Binary files that are encrypted will have -BIN appended to their extension. For
example, a binary STL file such as TURRET.STL will be encrypted as
TURRET.STL-BIN.
STL files in ASCII format will have the -TBIN extension.
Typically the goal of encrypting the files is to prevent them from being copied and
modified, instead of restricting their use to a specific user. In that case, enable all the SIM
types when selecting the encrption method: