Parametric Pipe tap

Parametric Pipe tap

Anonymous
Not applicable
7,175 Views
4 Replies
Message 1 of 5

Parametric Pipe tap

Anonymous
Not applicable

I have tried to get a pipe tap to represent correctly

I am new to revit and am sure im missing something

I am using 2012 (forced to by client requrements)

My tap is  appearing at the default od of 48.3 regardless of the pipe size attaching

I would really like this to work for me

I have attached files and screen shots

Regards

pete

0 Likes
Accepted solutions (1)
7,176 Views
4 Replies
Replies (4)
Message 2 of 5

AVysotskiy
Advocate
Advocate
Accepted solution

Hi alatier,

 

I checked your tap in Revit 2014 - it works great:

2014-01-22_112949.png

 

 

But there is one small thing - in my case I have in parameter Lookup Table Name value Pipe Spud Steel, and you wrote Pipe Spud Steel.csv .

 

2014-01-22_112938.png

 

Try to delete .CSV from parameter. I hope it will help.

 



Alexander Vysotskiy
CEO of Vysotskiy consulting | BIM trainer | University lecturer
Free BIM training courses (Russian only)
Facebook | VK | LinkedIn

Message 3 of 5

Anonymous
Not applicable

Thanks Alex

I can see it is working for you in 2014. That is exactly what I want!

I tried what you suggested, but just got an error response as per below (I also renamed the lookup file "tap" (just in case there was another Pipe spud.csv on the path being referenced in error)

It is very frustrating as Revit is just ignoring the lookup table and applying the default

I would even be happy if revit would just add 6mm to the pipe diameter and leave it at that, but I cant even make that work.

I am not sure if revit is actually even looking at my table, and is just returning the default

As I understand it the formulae looks at the table and (eg say 50NB pipe is the current size)

1. Ignores the 1st column (for user reference)

2. Looks down the second col until it finds the current pipe size

3. looks accross till it finds the referenced column (in this case "FOD")

4. Returns the value in the matching row (in this example = 60.3) This shold then replace the Outside Diameter (default) or 48.3

5. If it doesnt find the pipe diameter, it should multiply the diameter (40mm) x 1.5 and return that, In this example that would be 75mm

6. I have no idea what the third parameter is for, but an error is returned if it isnt present

 

In spite of all of this, revit is returning 48.3 in every case. This shouldnt be an option (except if 40NB pipe is being used)

 

I have googled, asked people and experermented, an i cant get it to work

What I am doing at the moment is changing the size on every instance manually

Revit is slow enough without having to do this

Pete

 

 

0 Likes
Message 4 of 5

AVysotskiy
Advocate
Advocate

Hi Pete.

 

Unfortunately I can't check this family on Revit 2012 - I even haven't got installation files.

 

If you want add 6mm to the pipe diameter and leave it at that you should write in the formula field of parameter Out Side Diameter value Diameter + 6 (or Diameter + 6 mm).

 

2014-01-23_101757.png

 

BUT there is one problem in your family.

 

I tried to use formula above - it works in family, but not in project : 

2014-01-23_102224.png

 

Why and how to fix:

You added parameter Radius to both of connectors in tee family :

 

2014-01-23_102754.png

 

This way Revit tries to pick both of connector radius to set tap size.

You should remove association for connector on the side of bigger pipe:

 

2014-01-23_103111.png

 

Now it works perfect without using CSV files :

 

2014-01-23_103239.png

 

If you really need to fix your problems with CSV and you have possibility to use Teamviewer on your work, write to my e-mail, I'll try to help.



Alexander Vysotskiy
CEO of Vysotskiy consulting | BIM trainer | University lecturer
Free BIM training courses (Russian only)
Facebook | VK | LinkedIn

0 Likes
Message 5 of 5

traka33
Explorer
Explorer

Bonjour,

 

J'utilise cette famille en version revit 13.

je fais appel à un CSV qui existe déja dans revit "Coupling - Generic.csv".

 

01.JPG02.JPG

 

0 Likes