transition Diameter-read only

[MarryTookMyCoffe]

in pipe transition, parameters for Diameter is Read Only, any one know how to walk around this?
I thing I can do small pipes on both site, but I would like to avoid this.

[jeremytammik]

it is controlled via the BIM by other properties, possibly on other elements.

the entire pipe system section shares one single diameter.

how do you control it via the user interface?

that is always the question you need to ask yourself first of all.

play with the user interface to modify the diameter of pipe system sections and explore the results in RevitLookup.

that will tell you all.

Cheers,

Jeremy

[MarryTookMyCoffe]

I expected nothing and i'm still disappointed...

Every other fitting work with connectors in the same way except a Transition, which block parameters assigned to a connector.
I DID LOOK UP THIS IN UI, that's why Im asking for "work around ".

Why The Transition blocks Parameter when non other fitting do this?

[Revitalizer · Accepted solution]

Hi,

afaik, you can use dummy pipes for creating transitions.

1. Create two pipes of the desired diameters somewhere outside all other elements.
2. Connect them by doc.NewTransitionFitting.
3. Delete the dummy pipes.
4. The remaining transition FamilyInstance will still have the correct diameter parameter values.
5. Move it to the desired location.

Revitalizer

[MarryTookMyCoffe]

it is painful that this is the only way

[Revitalizer]

Hi,

yes, painful as often.

Think of a dentist who wants to extract a tooth.

Normal way is:

• open mouth
• grab tooth
• pull tooth

Revit API way is:

• cannot open mouth exception
• develop new extraction device to access oral cavity via ear
• develop new optical device (want to see the extraction process), insert into ear number two
• pull tooth

Sometimes, also ear cannot be used, so you are forced to find another body opening.

Dirty workarounds...

Revitalizer

[MarryTookMyCoffe]

so I figure out how to avoid this mess with transition. I decide that i'm just going to ignore transition from api side and use  Union(with two connectors assigned to a different parameters) and dump them in the very end of union list in PipeType, that way user schould never came across them.

Oh and I discover something irritating in process, that I wish I knew moth before. We can assigned parameters to description even if connector in family is fitting type. They didn't turn it off, they just made it invisible. My code would be so much simpler.