Announcement

Collapse
No announcement yet.

Assigning Room Name/Number through to Mechanical Euqipment Through Spaces

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Assigning Room Name/Number through to Mechanical Euqipment Through Spaces

    First dynamo project time....

    So I'm trying to find the room name and number via spaces so that I can then write them to parameters in my mechanical equipment. I'm using bounding boxes for the spaces and mechanical equipment and then checking if they intersect. I've got it working, but there is one case as per my example image below where, if the space is irregularly shaped (the hallway) and overlaps other spaces/equipment, then I can't reliably retrieve what space that equipment is in.

    Obviously I could break my hallway into smaller spaces such that the bounding boxes don't overlap each other, but that seems non-user friendly/intuitive/dumb/not something that you necessarily want to do. Is there a better way to find the geometry of the spaces such that they don't overlap each other? I tried using the FamilyInstance.Space node from Rythm, but it was giving me null values and subsequently grief for equipment that isn't in a space (say a rooftop unit).


    Attached Files

    #2
    Never mind, I figured it out. Switched from using bounding box to getting the actual geometry.
    Attached Files
    Last edited by evan.dodds; July 7, 2017, 06:10 PM.

    Comment


      #3
      I also switched out the 'equipment not in space' part to fill in as the equipment's associated level rather than giving an error message.
      Attached Files

      Comment


        #4
        I tinkered with something similar to this last year. It turned into a much bigger project than I thought it would be, and I learned a lot in the process. My approach involved getting the EID of the Equipment (i.e. a VAV box) and writing it to a parameter in the HVAC Zone it served. The DYN then used a homemade version of Excel's VLOOKUP to get the names/numbers of the spaces inside the HVAC Zone, join them into a single string ("Room 101, Room 102, Room 103...") and then write that to a text parameter in the VAV family. I used it on a real project a few weeks ago and it saved me from, manually filling out the "Areas Served" schedule column for about 100 VAVs.

        Your bounding box approach is interesting, though. I haven't really messed around with them yet.
        Last edited by Necro99; July 24, 2017, 03:04 PM.

        Comment


          #5
          The bounding box method I found out was not the way to go since it can't handle complex geometry (see my hallway example). I switched to just finding the geometry and if it intersects instead. I tried using the "FamilyInstance.Space" node from the Rythm package, but I found it can't handle when an element is not in a space. It returns a null and just drops it from the output so you can't even consider which piece equipment is not in a space.

          Comment


            #6
            I still think that it's dumb that the space can see what room it's in, but you can't access/pass that through to an equipment schedule...

            Comment

            Related Topics

            Collapse

            Working...
            X