First time here? Check out the Help page!
2016-01-22 12:39:12 -0500 | commented question | ideas on a workaround to override default control measures for water flow in Air Loop HVAC coils The reason I think this is relevant to my current study is that the logic of the specific physical controller is designed to set either the hot or chilled water flow rate based on a calculated desired supply temperature. |
2016-01-22 12:22:45 -0500 | commented question | ideas on a workaround to override default control measures for water flow in Air Loop HVAC coils Yes, thanks, I have tried this and can effectively establish the set-point of the sensor node. Because I am interfacing with an ExternalInterface I can actually do this just be defining the setpoint through SetPointManager:Scheduled and referencing a schedule that is specified by the external interface (which is really just a real controller signal). What I am hoping to accomplish is to actually just drive the coil flow and monitor temperature. Not sure if this will be possible, and if not, I will just resort to doing just that. This is artificial though, and it would be ideal to set the flow. |
2016-01-21 14:11:30 -0500 | commented question | ideas on a workaround to override default control measures for water flow in Air Loop HVAC coils Thank you Julien, I will be sure to format better next time. :) |
2016-01-20 13:15:26 -0500 | received badge | ● Editor (source) |
2016-01-20 13:13:14 -0500 | asked a question | ideas on a workaround to override default control measures for water flow in Air Loop HVAC coils I am using the BCVTB to control E+ air loop simulations using building controllers. The simulated air handlers all have water based heating and cooling coils delivering conditioned air via In other words, I have attempted to replace the I realize that the point of the In summary, my first choice would be to control the coil water flow, as it represents the actual control situation for this system. I already know that I can control the coils indirectly by sending in the desired SAT, only the logic of these particular controllers will have to be tweaked if this is indeed the only option. Does anyone have any ideas on a workaround to override default control measures for water flow in Air Loop HVAC coils? |
2015-12-15 22:25:23 -0500 | commented answer | EnergyPlus: enforcing user defined fan speed for air handler at each timestep Thank you for your most helpful post Aaron. I have just looked again at these inputs related to VFD efficiency and such, and while this works to simulate VFD usage, I am truly hoping to command the the simulation in real time with a schedule type input to simulate varying the frequency and power over time. |
2015-12-15 16:47:01 -0500 | asked a question | EnergyPlus: enforcing user defined fan speed for air handler at each timestep Hello all: Does anyone know of a way to either input a schedule for fan speed or a way to create a custom fan object that allows a user to specify fan speed at each time-step? For my current study it would be nice to look closely at behavior of VFD control sequences. I have looked at the idf fields for Fan:VariableVolume, Fan:ComponentModel, Fan:ConstantVolume, and Fan:OnOff, and it does not appear that this is possible. I believe one way this could work is if it were possible to enter a schedule value for certain relevant fan only it does not appear that this is yet possible as these fields expect a number only. Does anyone have an idea for a work around or another possible solution? Your help would be much appreciated. Best regards, Tyler Noble |
2015-10-21 12:01:12 -0500 | commented question | Any ideas to correct this GenOpt 3.1 error? Thank you for your help Julien! I thought I had updated all version objects, but looking inside of the .ini file and looking at the reference files there is also the template file, which I had missed Simulation { Files { Template { File1 = singleZonePurchAir_template.idf; } Input { File1 = singleZonePurchAir.idf; } Log { File1 = singleZonePurchAir.err; } Output { File1 = singleZonePurchAir.eso; } I only had altered the version object for the .idf file and not the template. After updating the template file all is well and it works now. |
2015-10-20 19:46:37 -0500 | received badge | ● Student (source) |
2015-10-20 19:23:15 -0500 | asked a question | Any ideas to correct this GenOpt 3.1 error? Running the GPSHookeJeeves GenOpt example using Eplus v8.2 gives me this error in GenOpt: In the 'tmp-genopt-run-1' folder the singleZonePurchAir.err file shows these warnings: I used an idf version update tool to go from v 7.0 to 8.2, and I altered the GenOpt cfg and the .ini files from the example folder. Updating did alter the output variables to be for v8.2 instead of the original: for v7.0. I am confused as to why the version warning still persists, and I am also not sure where the Key=*, VarName= warnings/errors are coming from. Thus far I haven't been able to located these particular variables in v8.2 .rdd files. Any ideas? I did take a look at this post: Can GenOpt 3.1 be coupled to E+ 8.2 or just E+ 7.0 |
2015-07-13 11:06:34 -0500 | received badge | ● Supporter (source) |