Chain model in Teamcenter 1

[moovrr]

I would like to model a chain assembly as a re-usable part which I read is a challenge on it's own, but to compound the problem the part will need to be released in Teamcenter, so it would appear that if it is modelled as a straight chain then it will remain straight once added to an assembly, which isn't desirable as the chain route will need to be modified to fit the individual fixture assembly.
I know there is the option of alternate ID's for different chain routes but these will not transfer through a Teamcenter multi-site connection, and so would be lost and the chain would revert to a straight chain I believe.
The chain in question is shown here;

http://www.wdsltd.co.uk/products/St...Retaining-Clip-and-Chain-111/?highlight=chain

which is a 4 piece assembly with a fixed length.

I have tried a series of assembled and constrained links which is OK but not the easiest to control.
I have also tried to use Electrical routing which allows me to fix the length of the centreline, but this is unfamiliar to me and the end users of the chain.
Ignoring the multi-site issue affecting alt-id's mentioned above, does anyone have any better guidance or alternative methods to incorporate the above?
Note; I am not trying to model each link precisely, I would be happy with just a bounding centreline route to represent the chain.

Thanks for your help.

moovrr

 

[Walterke]

We have the exact same problem with hydraulic tubing.
When two tubes have the same diameter and length, and have the same nipples attached to it, it needs to get the same number. However, when implementing it in our assembly, different tubes are placed in a different way.

We've tried numerous way to make this work, but haven't found anything good yet.

I'll have a look at that electrical routing you mentioned, as it seems like it might be the thing we need.

NX 7.5
Teamcenter 8

 

[cowski]

Have you tried alt-reps?

 

[SiW979]

Walterke

You'd be better looking at mechanical routing which uses deformable parts so you can have one hydraulic hose in multiple configurations in the same assembly very easily, you can also establish rules that would flag up if you violated them for example the minimum acceptable bed radius of each type of tube (stock) There are other ways of doing it without mechanical routing, but these are a little more complex and you have to understand how to use mate overrides and WAVE linking, we do here at as we have yet to get the mechanical routing configured.

Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com

 

[tk369]

moovr:
Would it be possible to use reference sets? That way, your model could contain several variations of your chain. In other words, in your "chain" model, build the variations you need-even on separate layers and add each variation to a ref set.

Then, add the "chain" component to your assembly using the discriminate reference set. This shows the one you need in each separate assembly, and keeps the the others hidden, but still intact.

regards..tk

ted kralovic

VisVSA, NX-6, Macbook, iPhone 3GS, Garmin 765T, Garmin Forerunner 405, Garmin eTrex Vista Hcx, among others

 

[moovrr]

tk369,
Thanks for your suggestion but the problem is that although we know the length of the chain, we can't predict the routing configurations that will be required by the users of it.

Cowski,
Sorry I meant Alt reps don't transfer through multi-site not Alt ID's.

JCBCad,
It sounds like mechanical routing uses similar rules to electrical routing so for a representative chain I could probably use either application.
I believe you use Teamcenter so you'll know the issues above but it sounds like you have developed a method which would be applicable to my scenario, we use Wave linking extensively so I would welcome hearing your method.

Thanks all

moovrr

 

[SiW979]

Here is a method which works without using mechanical/electrical routing.

1. All our endfittings are modelled but not released as we only ever buy the hose in as a single part number. So when we add the two end fittings in to a part to create a hose, we turn them to reference only so they do not appear in the BOM. Also all end fittings have a single curve drawing in between two centers of the end fitting where the hose material would be pushed in.

2. Both end fittings are added to the hose model, in the correct oreintation with a gap between them where the hose material would be. Note that we do not model the hose material as our hoses are specified by a table drawing and not a dimensioned drawing, the hose material will bea added at the assembly level.

3. The hose is added to the assembly and one end is constrained. Then use the override position on the other end and contrain/position it to the other port.

4. Ensure the correct reference set if active so you can see the curves in each of the end fittings and then WAVE link them.

5. Now use a bridge curve to join the WAVE linked curves.

6. Use the tube command to represent the hose material.

7. Note that if one end moves, the hose will move and update.

It's not perfect, it is jsut a representation and trying to simulate exact lengths and min bend rads is impossible, however it will do exactly what you want, and it works for our company who have over 10,000 hoses on 300 machines across the world. I would however prefer to use the full on mechanical routing.

I will post a link to a video below this, I just need to swap computers.

Good luck



Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com

 

[SiW979]

Damn! I can't upload the video link I'm afraid. Sorry

Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com

 

[moovrr]

JCBCad

Thanks for taking the time to explain your method, it's a shame you weren't able to upload the video to assist with the words.
From your description you say you create a bridge curve in the assembly the hose is added to, so this makes the hose specific to the required assembly route I assume?
You use Teamcenter so does this method allow you to multi-site the standard end fittings? I assume not if they are not Released.
I think we would both benefit from using the mechanical routing to fix the length, my only issue there has been that the alt reps for each chain route we would create will not be replicable through multi-site, but at least the straight chain would be.

Does anyone have any advice how is the best way to assemble the standard end fittings of the chain or hose to a route curve and stock, i.e. should all parts be assembled into one assembly or should the fittings be assembled into the routing component?

 

[SiW979]

It does allow us to multisite the end fittings as we have a process called datashare which allows us to upload (share) data to our main server called the HUB. The hub can only have parts on it that have status, such as production released (green flag, read only, numeric revision) protosype released (orange flag read only, alpha revision)or data shared (red flag with black arrow, read only, alpha revision) this means that any one else on the other sites around the world can import the end fittings and use them on their own sites as reference geometry to construct the hose.

Unfortunately, the hose cannot be represented as a component of the hose and all hose material in a particular assembly is modelled at the same level. I might be able to upload the video today once I have had a word with our IT guys.

Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com

 

[moovrr]

Thanks JCBCad, our setup sounds very similar with the multi-site capability, and I can see how you can use datashare for the unreleased end fittings but not the hose modelled at the assy level.
We can only share Released Items in Teamcenter so I presume I could use your method to share end fittings having Released the Items first, then any site could add them to an assy and set as reference only so they do not appear in the BOM.
If you aren't modifying the end fittings (only wave linking them after adding to your assy) is there another reason why you don't Release them?

If your assy has several hoses, do you then have as many Tube bodies in that assemblies part navigator (1 for each hose)?

Regards

moovrr

 

[SiW979]

We will never actually buy individiual end fittings, we buy the finished hose which as a minimum will usually consist of 2 end fittings at each end of the hose material and the hose will be 1 part number. The way we are set up here, as soon as something is "production released" it sets of a whole chain of events where down stream functions like purchasing, manufacturing, service etc all get automatic notification of the part/s that have been released so they can make arrangments to stock parts, create storage space on the production lines, and procure the part, therefore if we properly released the hose end fittings, then would see these as being parts that need to be sourced individually. As I stated in an earlier post, we have one common repository that can bee seen by all of our 18 divisions, called the HUB, this is where released data is stored an only data that has status such as Production/Protoye can be placed (read only not WIP) therefore the datashare process allows us to give status to the end fittings of the hoses which means other divions can find them on the HUB and import them on to their server for use. They just will never appear on a BOM.

The hoses do unfortunately appeat as many tube bodies at assembly level rather than individual hoses.

Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com

 

[moovrr]

Thanks for the clarification.

moovrr

 

[SiW979]

Managed to get the video to upload

http://screencast.com/t/klWLLOKc

Best regards

Simon NX7.5.3 - TC 8

http://www.jcb.com