Okay; I'm just a little confused on why its important to use KVA instead of VA when Revit itself OTB is using VA?
Really all I was trying to do is get Revit to insert the FLA based on the NEC 2011 table.
FLA*Voltage=VA(for 1 and 2 pole circuits)
FLA*Voltage*sqrt(3) = VA(for 3 pole circuits)
1 hp or 4.6*208=957 rounded up
1 hp or 2.1*480*sqrt(3)=1746 rounded up
"Correct, I opened the CVS file and it says ##other##feet."
I see. Upon further testing, mine exporte changed to "##number##feet" when in fact it was "##other##" in the initial .CVS file. I believe that the "feet" extension to the "##number" is actually irrelevant, because I loaded that export version into the same Family and it works all the same.
Additionally, I tried modifying the original .CVS file to "##number##" (no "feet") and upon loading it into the Family, an error message pops up "Revit has encountered a serious error...".
BOTTOM LINE: use "##number##feet" for unitless values; Revit does not appear to add the feet units to the listed number.
"Okay; I'm just a little confused on why its important to use KVA instead of VA when Revit itself OTB is using VA?..."
I changed the units to kVA to create an example family to suit the needs of the original request (which was kVA) but this could be VA just the same - just correct the Family Project Units under the Manage tab.
"This looks promising; but where is the lookup table that you used in the formula?
Not sure how the formating of the .csv file would go here."
Attached is a .CSV file, and I shall explain the workings of it here. You can easily customize the CSV. file structure to suit your exact needs.
Below is the Lookup formula:
size_lookup(Lookup_Table, "A", 0, Voltage / 1 V, Horsepower) * 1 A
Red = "Lookup_Table" references a Text Parameter which reads the name of the imported Lookup Table. This does not have to reference a separate parameter, and could instead just read the Lookup Table's name in quotes.
Green = Which column in the referenced CSV. file to retrieve the value from.
Gold = This is the value to return if the search is invalid and does not find an appropriate listing in the .CSV table. For instance if you entered 0.875 as the Horsepower (which is not listed in the Lookup Table) the value returned here would be 0 [zero].
Blue = This is the value that is looked up in the second column of the .CSV file (the first column is ignored). This is a mandatory argument to the function. Note that since the numbers in the .CSV table are unitless, the units must be stripped from the value, hence the "/1V".
Magenta = This is a secondary lookup value, which searches the third column of the .CSV file. This allows you to lookup more than one condition and report the appropriate value. In this example, it first searches for the listed Voltage and then searches for the listed Horsepower, and returns the result that matches BOTH conditions. This is an optional argument, and you can add more columns as needed.
Orange = This just applies the appropriate units to the unitless value that is looked up in the .CSV table. This can be easily modified to suit any non-Text Parameter Type.
*Note that the first column in the .CSV file is ignored by Revit.
Very good explanation; thank you very much!
This is what I have put together with the input that I received from you guys.
It appears that this family is working very well; I did not include the entire table but now I have something that I can add to.
Only issue that I did have was using Number of Poles in the formula; I just could not figure out a way to get it to let me use that in a formula which is why I put the work around for Single Phase in the Constraints. I tried several ways other than this to use Number of Poles but in the end it did not like it.
Note that the electrical information is based on the information Revit uses to connect loads.
i.e... I used it how it is named in the system; Number of Poles happens to be one of those system defined parameters; a lot of people like to change this to Phase or Number of Phase; I like mine to be named the exact way Revit names them.
I would be interested to pick your brain on temperatures and GPM along with other systems on the Mech side; I do mostly Electrical but I create families all the time for other disciplines as well. I have done a little Mech and IM fairly good at Mech and Piping but I need more jobs to do in those areas to really grasp the impact at a final design level. Hopefully the next two projects coming up they'll let me off my leash so to speak.
Thank you for reawakening this thread! It worked out very well, and I'll give you Kudos for that!
"...Only issue that I did have was using Number of Poles in the formula; I just could not figure out a way to get it to let me use that in a formula which is why I put the work around for Single Phase in the Constraints. I tried several ways other than this to use Number of Poles but in the end it did not like it..."
A problem with the method you have here is that the "Single Phase" options is bound to become "out of sync" with the "Number of Poles" because it is an Instance Parameter. I think you are best off changing "Single Phase" to a Type Parameter and creating two separate Family Types (one for Single Phase, one for Three Phase) and setting these Parameters appropriately.
The reason I bring this up is because if the Number of Phases is powering the Connector, a user is bound to eventually change or copy it and uncheck the "Single Phase" option while "Number of Poles" is still set to 3. If a user is required to change the Type in order to switch it between single and three-phase, they will more likely remain correct.