Tag: Integration

This integration type block allows to apply optimization and other data mining techniques to PTC Creo parts and assemblies by integrating them into a workflow as a Creo block instance. Such instance maps document parameters to block input and output ports, so they can be changed in run-time by receiving data from other blocks. On each change of input parameters, the block starts a new PTC Creo process to calculate characteristics which are then sent to block output ports.


The Creo block can run only on a Windows host but configuration is available under Linux. The host to run the Creo block must have PTC Creo installed with Visual Basic API support. This is required for the block’s run-time and for building document parameter trees. Other configuration options are available anywhere.

The Creo block actually launches PTC Creo when you build the document parameter tree (while configuring the block) and when the block starts (in a running workflow). Visual Basic API is required for communication between pSeven and PTC Creo. In PTC Creo setup, this component is found under API Toolkits.

If the Visual Basic API has been set up correctly, the PRO_COMM_MSG_EXE environment variable should be set to the absolute path of the Creo environment file, pro_comm_msg.exe. Typically, this path is:

creo_loadpoint\Common Files\datecode\machine_type\obj\pro_comm_msg.exe

where creo_loadpoint is the PTC Creo installation directory, datecode is the release’s datecode, and machine_type is “i486_nt” for 32-bit or “x86e_win64” for 64-bit Creo. For example:

C:\Program Files\PTC\Creo 2.0\Common Files\M110\x86e_win64\obj\pro_comm_msg.exe

Alternatively, you can set the Creo environment file path in block’s options. Note that the option setting overrides PRO_COMM_MSG_EXE. This allows to select another installed version of PTC Creo without changing the system environment variable.