Revision history [back]

This is definitely an OpenStudio problem, you should open an issue on Github

My two cents:

• You have correctly identified that when you add a new one, the problem seems to move around. Well, partially. If you click on the splitter, and add a new zone, behind the scene the last ATU (Let's call it ATU-1) seems to be cloned to add this new thermal zone with a new ATU (let's call it ATU-1bis), and something seems amiss in the sense that the it reset the inducedAirInletNode of this ATU-1.
• If you're looking for a quick work around, drop the thermal zone first, then add a Four Pipe Induction ATU to the inlet node of the zone. This works fine (the addToNode method works)
• The initial design choice is questionable to me. It seems that the induced air inlet node is set during the call to the addToNode method (see source code here). I think it would make more sense to set the inducedAirInletNode during the forward translation, and to completely hide the inducedAirInletNode property in the API as well (it's not visible in the OS App but there's a getter (no setter) in the API).

This is definitely an OpenStudio problem, you should open an issue on Github

My two cents:

• You have correctly identified that when you add a new one, the problem seems to move around. Well, partially. If you click on the splitter, and add a new zone, behind the scene the last ATU (Let's call it ATU-1) seems to be cloned to add this new thermal zone with a new ATU (let's call it ATU-1bis), and something seems amiss in the sense that the it reset the inducedAirInletNode of this ATU-1.
• If you're looking for a quick work around, drop the thermal zone first, then add a Four Pipe Induction ATU to the inlet node of the zone. This works fine (the addToNode method works)
• The initial design choice is questionable to me. to me. It seems that the induced air inlet node is set during the call to the addToNode method (see source code here). I think it would make more sense to set the inducedAirInletNode during the forward translation, and to completely hide the inducedAirInletNode property in the API as well (it's not visible in the OS App but there's a getter (no setter) in the API).