Hey @RafaelA ,
I have no idea what types of edits you’re trying to make to HVAC or how you are making them but, if you are actually getting an IDF and starting to run the simulation, then the .err file that EnergyPlus outputs will usually tell you what’s specifically wrong. Debugging is different if the error is happening before you get to the simulation step.
Also, I would say that there are ~5 levels of HVAC workflows with Honeybee, each one requiring more expertise but allowing a finer level of control over the HVAC
HVAC Workflows with Honeybee/OpenStudio
(ordered by level of difficulty)
- Use the HVAC system templates that are included in Honeybee and just customize some of the high-level properties like heat recovery.
- Use the Honeybee HVAC templates as a starting point but manually customize some things in the OpenStudio Application before running the simulation with the HB Run OSM component.
- Build an entire custom HVAC system using IronBug and assign it to your Honeybee-exported OSM using the workflow described here.
- Use the Honeybee HVAC templates as a starting point but edit the HVAC properties using the OpenStudio SDK, either with a GHPython component like you see here or with an OpenStudio Measure.
- Write a GHPython component or Measure that assigns an entire HVAC system from the ground up.
Technically, there’s also manually editing the IDF but you don’t really get any more control from this than you would working with the OpenStudio SDK. Plus it’s several times more painful when you don’t have the OpenStudio SDK to manage things like the connections between HVAC equipment.
If you let me know which level you’re at, that will also help me give you advice.