I am a licensed partner of Siemens PLM. I provided some post processor for our cusotmer.
how can I protect the post for only the customer with the Sold install and the customer can't edit or copy to other solt to install
I know that we have post Configurator can protect by Sold to install and date, but I already have the post and not using post configurator, I only use post builder and already have (.pui, .tcl, .def file) so how can I protect
1) Option in post builder to encrypt it.
2) Post Builder creates 3 files when you create a post for any machine. a) xx.pui, b) xx.tcl and c)xx.def. Provide only tcl and def file to customer. Do not share pui file. Create SoldTo/Install output in post processed file.
if you use the Post Configurator, then you can encrypt your postprocessors,
add a time bomb and limit them to Sold To ID`s.
There are three licenses for the Post Configurator:
Basic: - Free and included in all NX CAM licenses
Advanced: NX31439 - Get all owners of a Post Builder license for free!
Full: NX31440 - must be bought and only then can be used also the encryption, time bomb and
Sold To ID functions.
Please also note the new Post Hub platform. This is a cloud in which one can offer and test postprocessors. In the future maybe whole machine kits, with simulation. Is currently in the testing phase and a great idea to make postprocessors available worldwide and makes it easier for the end user to find postprocessors and their providers!
yes yes the postprocessor world is crazy already. When I develop a postprocessor specifically for a customer, I not only process the know-how of the customer in the NC code, but also implement corresponding solutions and NX interfaces with my programming know-how. Both should be protected! The PB I know too little, since I am currently only concerned with the PC. Of course, there is always the requirement of customers to disclose the source code. But in what form or documentation, there is scope. Therefore in the PC the different functions to encrypt, time bomb or Sold To ID. If the customer wants to have everything open, well then he can, but the post office remains protected by Sold To ID and Time Bomb. For the protection of my source code, the customer must commit to me. There are then nice dicussions with the customer IT ;-). My opinion is that as a postprocessor developer I do not deliver an unencrypted postprocessor. After all, yes, I also get proper trouble if it has postprocessor errors or does not work as ordered. If the customer does not accept that, okay. Gives enough to other customers. Incidentally, I can not get the source code of Windows as a customer either. Maybe there will eventually be free post processors for NX. But they are just as good as the competitors in the market ;-)
Windows 10 Enterprise
At start of program, create a block with below statement
MOM_output_literal "SoldTo_Install ID xxxx". Mention actual id of customer instead of xxxx. So each time user post process the tool path in NX, first line would be their SoldTo ID
Check the syntax of the above as I don't remember.
I did this before for a company. You can embed .tcl and .def files in a dll file and force NX to run the files from there using NXOpen. I remember I wrote a VB code for this. You can then read McAddress, computers hardware serial numbers (hard disks, motherboard, graphic card, modem...) or extract server information (License Server, Sold To ID, Webkey, Issuer, Version, Siemens Licensing version) and use them to lock the dll file to be run only for a designated PC or customer. I also wrote a code to read the date from internet in order to make expiration date for the post processor. Also a connection to a ftp containing counter text files, when the number of post outputs should be limited, so the dll file read the current number over the internet and added one into the defined file until the limited number of post processings reached.