|
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
#16
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Well, I experimented a litte, and still cannot reproduce precisely what ckrug described. But then, I didn't (and still don't) fully understand the description anyway (hence the questions I asked earlier in the discussion). Maybe you could post a command sequence so that we could see what you did?
That said, just a few notes on instance vs. contents data. Let's assume we have an assembly a1 owning a part p1. If you save this in *.sd* format, you'll get the following files:
Instance data comprise all information which is particular to a given instance of an object. Contents data are common to all instances of the object, i.e. those data are shared. We'll see below what this means in practice. If you analyse p1.sdpc, you'll notice that nowhere in the file you'll find the name of the part. This is because the part name belongs to the part's instance data, and those are stored with the owning assembly. Why are instance data stored with the assembly? Well, because they only make sense in that particular assembly. The part p1 might have been shared into some other assembly, and there it might have a completely different name, such as foobar. (Other assembly-relative data for a part include its transformation relative to the owning assembly.) a1.sdac contains both assembly contents data and instance data for the assembly's children. Originally, those data were actually written into two files, but then it was noticed that the two files could actually be combined without loss of functionality. This simplified file administration somewhat, but makes it a little more difficult to explain the instance/contents concept Analysing a1.sdac will indeed show you that this file knows about a part called p1. Setting a "model name" adds an interesting twist - the model name belongs to the contents portion of a part. If you save p1 after setting its model name to, say, wouldtherealp1pleasestandup, a file called wouldtherealp1pleasestandup.sdpc will be created, and in this file you will indeed find the model name wouldtherealp1pleasestandup. I'd suggest that with this background information in mind, we should step through the complete description of the case and understand what's really happening.
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
#17
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
ckrug, Seems that you got the answer, but still the question of why it happens. I've been dealing with this issue over and over with the legacy data I had inherited. Added to that complexity on my end is a hierarchy of sub-folders six or so deep that mimics the levels of the assembly.
Sounds as if you're only dealing with in in a single folder directory. That can be very helpful to work out the issue. On my end, I have to compare files sizes, file dates and Mi files staying blue. I've avoided PKG and BDL files altogether. They can cause trouble if one isn't careful.
__________________
Support Your Local Sheriff - At high noon Jason: "How much does it pay?" Citizen: "Well, none of our other sheriffs ever lived long enough to find out." Co-Create 2007 (15.50G) ANSYS Workbench 14 SolidWorks 2011 UGNX-7.5 / TeamCenter UA 8 PADS 2000 Applicon Bravo Autotrol CADAM Pro/E |
#18
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
Thanks for the heads up on this. Great explaination indeed. Without it, I thought that the 3D Data was the original and the Instance was a copy for everything else to use. Guess that isn't the case for the CoCreate understanding. Why have something saved as 3D Data that can have several names everywhere in different assemblies If part 2134 needs to be used everywhere, then it should be part 2134. Not something out of the blue. BOM and part inventory people would shoot me for not keeping the same component p/n.
__________________
Support Your Local Sheriff - At high noon Jason: "How much does it pay?" Citizen: "Well, none of our other sheriffs ever lived long enough to find out." Co-Create 2007 (15.50G) ANSYS Workbench 14 SolidWorks 2011 UGNX-7.5 / TeamCenter UA 8 PADS 2000 Applicon Bravo Autotrol CADAM Pro/E |
#19
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
Code:
unicycle |____ wheel |____ ... other parts bicycle | |____ wheel |____ wheel |____ ... other parts Quote:
Claus
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
#20
|
|||
|
|||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
I cannot think of a good way to regenerate this problem. As you request, here is a command sequence (I'll simplify the names a little more then my previous example and add a little more detail about my specific case. The part 1 is actually a small assembly, which I will now call a3) Also, all of the below names are "Model Names" not part or instance names: - Load a1.sdac (a1 contains a2 which contains a3 which contains p1,p2,etc.) Here is where I notice that the part number (model name) for a3 is incorrect. Darn. I run a little script in my directory that creates a "where used list" and upon inspection, a3 is only used in a2. So this means I can just change the model name for a3 without breaking any other assemblies. - Change the "model name" of a3 to a4. - Save "3D data" for a2. Everything looks good in the options dialog box. - Start New Session - Load a2.sdac a2 which contains a4 which contains p1,p2,etc are all loaded correctly as expected - Start New Session - Load a1.sdac a1 which contains a2 which contains a3. which contains p1, p2, etc. is loaded incorrectly. a2 should have loaded a4 not a3. Unless there is some share of a3 loaded before a2 is loaded, I don't see how this can happen? I cannot find any shares of a3 outside of a2 As a troubleshooting step, I made a copy (one level only) of a1 and called it a1_copy. When I loaded a1_copy.sdac, it correctly loads a1_copy which contains a2 which contains a4 which cotnains p1, p2,etc. So I have a great solution when I know the problem exists. My issue is that I stumbled blindly onto this problem. How do I know this is the only case of this behavior? |
#21
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
That was the thing I didn't get at first - I thought you had a reproducible way of provoking the problem, but apparently all you have is a repository of files (with some history behind them), and some of them exhibit the behavior which you are describing. Correct?
If so, then we'll have to work though a number of scenarios to find out how we could possibly arrive at the stage you're describing. I'm a little too busy right now to start with this right away - hope I'll have some more time next week. Claus PS: If you need quick and thorough answers, I recommend to talk to PTC support. I know we have some excellent filing experts in the team who will be able to analyse the situation quickly.
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
#22
|
|||
|
|||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
A quick note, upon investigating my data I have discovered that I have data files all the way back to ME30 and/or One Space version 8 (not sure where it switched over to OneSpace). When I first started at HP we used ME30. I wonder how far back CC Modeling is backward compatible? Thanks again for your help. Cheers, Calvin |
#23
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
Claus
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ Last edited by clausb; 07-30-2009 at 09:18 AM. |
#24
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
BTW, where exactly do you see those messages? As a message box? As a message in the console window?
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
#25
|
|||
|
|||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
This message comes through when the file is loaded in the console window. At least I think that is what you are calling the console window. The same window that tells you about missing files. I was really hoping to understand the reason behind these messages because I'm certain they are causing additional problems. They are very nondescript when I get them. Is there a way to determine what secondary item or file is missing or any tools that I can use to troubleshoot the error? I realize I can just continue on "with no harm" but it still bugs me to not know. It's good to hear about the backward compatibility. Every once in a while I do "save 3D data" instead of save modify, which I assume is dragging the data forward. Only old unloaded data remains in previous versions. Cheers, Calvin |
#26
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Just to clarify the terms - the screenshot indicates what I call the "console window", versus what's known as the "output window".
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
#27
|
||||
|
||||
Re: secondary object of type 'asbm_struct' was missing.
Quote:
Maybe our support folks have tools for this. I'm not sure. Quote:
__________________
CoCreate Modeling FAQ: http://www.clausbrod.de/CoCreateModeling/ |
Tags |
asbm_struct, error |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|