Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
Dear PTC CEO and programers.
Deae PROE FANS
I wrote this to the PTC, but no response.
Forward message>
I am using PROE WF5 PRO/nc as cad/cam system
CAD is OK I like it.
BUT!!! CAM-PRO/NC is not a CAM. When you make something new it is 80% buttons an menus, but engine is the same all the time.You are making olny small changes. Your "CAM" can not compute toolpaths on backround (multitasking)It is not using multiple core technology, I am siting on my chair an waiting for hours. (I have XEON64bit 8GB RAM HP Z400) So wake up PTC. You have a lot of bugs in your "CAM" I am not your employe tester. Bugs are in re-rough, Rough, Finishing, Profile, local mill and surface steps. There are bugs and engine is not good too.
I am using EDGECAM too. If you will sleep, I will throw proe away.(to the recycle bin)
Sorry for my english. It is bad, but it is better then then your "CAM"
You have two options
1.new engine for PRO/NC
2.integrate pro/toolmaker in pro/nc
Bukaj
You wrote
@DanielSantos wrote:
Bukaj,
...
Many of the issues people have with Pro/NC are caused by the cumbersome and outdated documentation, non-intuitive workflow and lack of real life examples in PTC training material and PTCU. They don't have real life NC programmers working for them. So, I'd like to suggest you to visit this place more often, drop your questions (Politely please ;->) and perhaps you can learn some tips here that will make your life easier... Yes, many of us understand your pain, but Pro/NC deserves a last chance I think...
...
Best regards,
Daniel
Haha, you are totally right, but those Problems still exists. They are even relying more than ever on the community and do not answer any questions anymore.
And if, for sure it will only be fixed for future releases..
>>>but keep in mind that Pro/NC has the ability to use multi-core and remote computing for more than 10 years, something that is only avaliable in the last3/4 years.
Yes, it is true, but you must have more than one licence! I have only one licence. So I can not start another proe on behind. Job manager does not work when you have only one licence.
(Am I right?)
Bukaj
Bukaj,
Talked to a PTC guy today and I need to add a remark to my last statement: If you set your own machine as the remote computation server, then Pro/NC job manager will use the multi-cores you have and it will not attempt to grab another NC license: it will use the license you are using.
I'm not sure which toolpaths supports multi-core processing or if all them do it. It would be good if someone from PTC could clarify this, an old doubt I have...
By the way, HSMWork also licenses the NCGraphics kernel, and two ex-NCGraphics employees are now working as freelancers, coding for Cimco/HSMworks... you can find their blog here: <u>www.freesteel.co.uk</u>- Wikipedia says that aproximately 10 CAM vendors licenses NCGraphics technology... so I think Creo/NC will have an interesting future...
Rgds,
Daniel
Bukaj,
By the way:
My last post was not clear, sorry: Pro/NC does not have multi-core toolpaths... it won't split the computation of any toolpath in multi cores... what it will do is to run Pro/NC in one core and compute the toolpath in another...
HTH
Daniel
My last post was not clear, sorry: Pro/NC does not have multi-core toolpaths... it won't split the computation of any toolpath in multi cores... what it will do is to run Pro/NC in one core and compute the toolpath in another...
Hey Daniel
Is there a better guide to setting up the job manager to process toolpaths on multiple cores? The help files seem to be lacking some details. would there be a diffrence between xp and 7?
Wow, thank you. This helped a LOT. I never found out how to find a server. Now I managed it. I just wonder now how I can set that server in a way that I never have to designate that server(s) I want to use again.
Like setting that server ip / hostname inside a proe-config.
Pretty late answer, but since nobody answered and I am still happy using it since yesterday..
Try sending one step alone and not multiple nc-steps.
Then it works.
If it is calculated you can either get the calculatoin via the get button OR you just let creo show the toolpath. The Task is automatically removed from the Jobmanager..
And today, I have the same problem as you (Christopher F. Gosnell):
I calculate one step with Distributed Computing (it does not matter if I start it on my own Machine or on another PC) and I see in my working folder a file called:
myNCprojectname_8640_tmp.tph.1
BUT when I now fetch this file or start the "showpath" command, it recalculates again.
After that, this mentioned file is deleted, so it is able to recognize that data..
Now, it is a bad habit to leave the customer alone with such stuff.