Not sure, but usually I import first the reference then after the stock model. It looks like your colleague is doing in the other way.
↧
Re: mat'l removal simulation: "Could not tessellate"
↧
Re: When you use Style, how do you feel?
What's New in Creo 4.0 is listed in the Help Center, and there is a demo on G3. What do you think about this...Dean?
↧
↧
Re: Arbortext - consolidate table at the topic level in the ouput
I'm curious as to why you have information organized in a way that is not the way you want it actually organized? Why is the information split up into these different tables in these topics if you don't actually want it in those topics?
↧
Re: How to hide imported step file in model tree?
Hi,
I guess that Sohaib Imran wants to hide geometry represented by import feature, only. His model contains another solid features probably related to import feature shape. In such situation, he cannot use you layer solution, because it hides all solid geometry.
MH
↧
Re: mat'l removal simulation: "Could not tessellate"
An update so I don't leave this subject hanging...
Following up on the good suggestion we investigated an accuracy mismatch. Both models were the same. Later I did some playing with importing a step file of our casting into a new part with more and more accuracy but that didn't get me anywhere.
When I went through the process of exporting a step file (of our casting) then re-importing it into a new part, I was able to see some questionable areas that didn't show as geom checks in the original casting model. If you want to try this: when importing a step file, hit the Red Cross Import Data Doctor button and there is a geom check embedded in there. When it was something I could easily fix like a round we didn't need for mfg I would go back and delete it and try again. After a couple of iterations I finally had a very clean model to work with. With high hopes we brought this into his mfg program but we still got the “ Could not tessellate stock model” error.
We are out of time on this particular project so he's going to move on. He said he can manually step through the program and look for crashes. To those of you who use this mfg software: I may not be describing this last part correctly.
Problem not solved. If it shows up again on a simpler part we may chase it further.
Thanks for your time, Bruce
↧
↧
Re: mat'l removal simulation: "Could not tessellate"
I'm not sure what he usually does but when I was watching him the reference model was in place then he added the stock model.
↧
Re: How to hide imported step file in model tree?
That is very likely true.
↧
Re: Mathcad Lizenz Problem
Eigenartiger Effekt. Denn selbst ohne gültige Lizenz sollte Prime zumindest im stark eingeschränkten Express-Modus starten und laufen.
Der Grund, warum Prime plötzlich meint, keine gültige Lizenz zu haben, kann in einer Änderung der Netzwerksituation liegen. Also wenn zB bei der Installation der WLAN-Modus eingeschaltet war und dann später deaktiviert wird oder umgekehrt. Denn die Lizenz ist an die MAC-Adresse jener Netzwerkkarte gebunden, die von Prime nach einem bestimmten Algorithmus als die "primäre" festgelegt wird. Wenn diese Karte dann nicht mehr vorhanden ist oder ein andere Netzwerkadapter dazu kam und nun als primär deklariert wird, stimmt die Lizenz nicht mehr.
Aber ich glaube nicht, dass das bei dir die Ursache für das Fehlverhalten ist, denn wie schon geschrieben, sollte Prime dann ja trotzdem starten.
Möglich, dass eine Änderungen in der dotNET Umgebung für den Fehler verantwortlich ist, aber das ist nur eine sehr vage Vermutung.
Du solltest versuchen, eine Anfrage an den PTC-Support zu richten. Ich glaube, dass es da für EDU-Lizenzen eine eigene Anlaufstelle gibt.
Bin mir nicht sicher, ob https://www.ptc.com/appserver/lm/mathcad/call_logger/callLogger.jsp die richtige Stelle ist.
Der Lizenzcode, den du von deiner Schule erhalten hast, ist, wie ich vermute, nur für eine einmalige Installation gültig, im Zuge derer du ein Lizenzfile bekommst, welches an deine Hardware (MAC) gebunden ist. Beim Versuch, eine weitere Installation damit vorzunehmen, sollte dann eine Fehlermeldung kommen, dass der Produktcode nicht (mehr) gültig ist. Möglicherweise gibts aber auch Codes, die für mehr als eine Installation gültig sind.
Ich hoffe, dass du dir durch die Neuinstallation nicht die ehemalige Lizenzdatei license.dat gelöscht/überschrieben hast. Jedenfalls scheint mir dein Problem nicht ein Lizenzproblem zu sein und du benötigst dann die Lizenzdatei, wenn der eigentliche Fehler behoben ist.
↧
Re: What is the difference between master vault, replica vault and cache vault?
When you save a file it goes into the upload vault.
You also need to have Windchill configured to use file vaults, which is OFF by default.
In order for the file to actually get to the master vault location, you need to check in that file.
↧
↧
Re: is Creo 4.0 datecode:F000 a beta release?
You are dealing with the age-old problem of using multiple vendors.
PTC releases Creo 4 for general use, date code F000.
Infor PLM gets their copy and now have something they can code against to update their product to accept Creo 4 data.
PTC released builds of Windchill at the same time as Creo 4, so it can accept Creo 4 data.
Infor PLM may still release an updated version of their product that will work with Creo 4 F000, or they may wait until M010/M020 is released.
In the mean time, you will just have to stay with Creo 3.
↧
Re: Setting the default value for the OOTB WTPart attributes via OIR
another related post with other options - Setting the default values for the OOTB WTPart attributes
↧
Re: mat'l removal simulation: "Could not tessellate"
Found the problem !
I kept wondering that if the casting model was the problem, could it be "healed" by translating it into another format then back into a creo? Creating a step file didn't give us results so I next tried creating a .stl file. I didn't research it but was hoping the .stl could then converted back to a .prt file somehow.
The first attempt at creating a .stl file failed with these error messages:
"Unable to triangulate highlighted surface. Aborting output."
"Unable to triangulate part BDP146-P4-040C_REV_03_3. Aborting output."
I couldn't find the highlighted surface but the message led me to believe the software identified a problem that was localized. I found the problem area by:
- creating a cut (side view) as the last feature in the model tree and hacked away 90 percent of the casting.
- retry creating the .stl file. (success!)
- edit the side view cut to re-introduce the casting a chunk at a time.
- repeat the process until the .stl creation fails again.
In this case I was able to narrow the problem down to a small area. I changed the side view cut feature to a surface so I could see where I had been and next went to a front view and used the same method to narrow down the problem area even more.
It appears the problem is in a round that was built with surfaces in an area of the casting that's nasty to work on. Since we are crunched for time, I left the cut feature that found the problem in place and used it to just remove the problem. My co-worker was so happy when it worked he offered to restore my 1960 Chrysler! No, not really.
Summary: I don't know why the problem exists but it is related to a round between two complex surfaces. Geom checks didn't flag the problem, but a .stl model could not be created because of the problem. The .stl creation process was used along with cuts to remove material to get a work piece that would display properly in mfg.
Thanks everyone for your input! Bruce
↧
Re: is Creo 4.0 datecode:F000 a beta release?
Shouldn't vendors get the code BEFORE release so they are ready?
Anyway...does anyone use F000 in production? It may not be the definition of Beta but I consider it Beta.
↧
↧
Re: is Creo 4.0 datecode:F000 a beta release?
Haha, I started to say that only the brave few actually put F000 in to production but it's still a production release.
↧
What is the error 'K03_UWGM_ACTION_NAME_MODIFYFORPRIVATE'
When a user tries to update his workspace he gets the following error: K03_UWGM_ACTION_NAME_MODIFYFORPRIVATE...never saw this one before.
↧
Re: is Creo 4.0 datecode:F000 a beta release?
I usually wait until M040 or higher before rolling out a new release to my users.
I do have F000 installed on the non-production side so I can play with it.
Right now the holdup I have is Windchill 10.0 and what it supports. I have to go to Windchill11 before I can use Creo 4. Hopefully before June this year.
↧
Re: What is the error 'K03_UWGM_ACTION_NAME_MODIFYFORPRIVATE'
What version/build, etc.
↧
↧
Re: download manikins
Hi Andrew,
You will need to contact Maintenance to renew your Maintenance contract and get an updated license. Call 1-800-477-6435, 9 for Customer Care, 2 for Maintenance, License Management & Training.
Thanks,
Amit
↧
Re: retrieve older file version
Look in the options to open a file.
↧
Re: download manikins
I often wish I downloaded all content when I have access.
This rental model is really going to catch a lot of people by surprise.
I have a lot of old Pro|E disks and I know many contain some really good data.
Problem is, there is no easy way to access any of it without a proper install.
Not sure how to best deal with all this content.
However, when PTC shortcuts me, I'll find another supplier to cover my bases.
↧