Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
Does anyone know why creo hangs when I'm using full asynchronous mode example (Creo Object Toolkit C++)? I choose to start creo with graphic-display in full asynchronous mode.I have tried different solution like check the PRO_COMM_MSG_EXE Path.But I'm not sure if the PRO_DIRECTORY is in Common_Files location.Hope somebody help me with this dilemma.Thank you very much!
Solved! Go to Solution.
No this is not required, but in Full Asynchronous Mode, you should have created some callback Menus in Creo during you Init, after connection or after starting Creo.
In Asynchronous Mode, you should have an event loop, and call ProEventProcess.
If you call ProAsynchronousEventLoop the call may not return, until you don‘t interrupt this loop, the return may not needed if you have your own Menue Callbacks.
For PRO_COMM_MSG_EXE take care of blanks in the path, but if Creo is already started, this is probably not an issues any longer. You find the path after starting Creo and search for it in the Task Manager, just take this full path.
Please read carefully the notes in the TOOLKIT User Guide.
In Creo you have :
In Asynchronous Mode you may need ProEventProcess to push the execution of your calls. If you connect, do your task and disconnect, this may not required before each function call. Don’t forget you can run/connect to Creo on a complete other Workstation. But for sure you have the communication overhead.
search ptc\<creo version> directory for 'pro_comm_msg.exe'. point your system evironment variable to the directory of the found file
I have tried to check the PRO_COMM_MSG_EXE Path.It didn't work.Creo Session started by full asynchronous mode still "No response".
I have tried to check the PRO_COMM_MSG_EXE Path.It didn't work.Creo Session started by full asynchronous mode still "No response".
check your windows firewall rules registry settings
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
search the hive for pro_comm_msg.exe
should have this in its data string: Action=Allow|Active=TRUE|Dir=In|Profile=Domain
Mine registry file value contains"Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Public"
Does it matters?
I think need to setup COM server for VB API.
Check this
https://community.ptc.com/t5/Customization/Errors-using-Creo-Parametric-VB-API-in-HEEDS/m-p/808253
https://community.ptc.com/t5/Customization/Setting-Up-VB-API/m-p/415961
No this is not required, but in Full Asynchronous Mode, you should have created some callback Menus in Creo during you Init, after connection or after starting Creo.
In Asynchronous Mode, you should have an event loop, and call ProEventProcess.
If you call ProAsynchronousEventLoop the call may not return, until you don‘t interrupt this loop, the return may not needed if you have your own Menue Callbacks.
For PRO_COMM_MSG_EXE take care of blanks in the path, but if Creo is already started, this is probably not an issues any longer. You find the path after starting Creo and search for it in the Task Manager, just take this full path.
Please read carefully the notes in the TOOLKIT User Guide.
In Creo you have :
In Asynchronous Mode you may need ProEventProcess to push the execution of your calls. If you connect, do your task and disconnect, this may not required before each function call. Don’t forget you can run/connect to Creo on a complete other Workstation. But for sure you have the communication overhead.