Go to homepage

Oh no, something went wrong. Please check your network connection and try again.

← All categories

Pipe Fittings

Elbows, bends, tees, reducers and couplers, priced per element. Angle is the field most often missed.

LoopbuildPipeFittings.txt: 5 parameters, plain text. Load it once and reuse it in every project.

The shared parameters

The names matter exactly as written: these are the column headers Loopbuild looks for. They are all text fields on purpose: length and angle parameters export in whatever unit the project is set to, which changes the number we read.

ParameterRevit categoriesType or InstanceExampleWhat it does
LB_MaterialRequiredPipes, Pipe Fittings, Pipe AccessoriesTypePVC-UThe material family: PVC-U, CPVC, ABS, PE100, PP, copper, steel or cast iron. Without it, nothing on that row can be priced.
LB_AngleRequiredPipe FittingsInstance9045 or 90, on elbows, bends and tees. Keeps a 45° and a 90° of the same size as separate lines with separate products.
LB_Size_SecondaryPipe FittingsInstance63The reduced outlet in millimetres, on reducers, reducing tees and reducing bushes. Leave it empty on equal fittings.
LB_Pressure_RatingPipes, Pipe FittingsTypePN16PN16, PN10, or a value in bar. Breaks ties between otherwise identical products.
LB_Connection_TypePipes, Pipe FittingsTypesolvent weldSolvent weld, threaded, push-fit, compression or flanged. Breaks ties between otherwise identical products.

Built-in columns to include

Nothing to create for these: Revit already has them, they simply have to be columns in the schedule you export. Revit won't let you create a shared parameter with one of these names, which is why they aren't in the file.

ColumnWhat it does
Family and TypeIdentifies the product. If your schedule only carries Type, that works too.
SizeThe diameter. Millimetres, inches and DN are all read correctly.
System ClassificationTells us whether the run is pressure or drainage: a pressure pipe and a soil pipe of the same size are different products. System Name works as well.
CountOnly needed when your schedule lists one row per type rather than one row per element.