Changing timestep effects simulation results highly? Insulation and window U values very low impact.

edit

After many trial simulations, I was able to find the problem in my model. It was caused by having 2 setpoint managers on the same node and the minimum part load ratios of the boilers was set to 1. After realizing that this was the case, I came across to a warning in the Input Output Reference Document related with having two setpoint managers on the same node. I didn't know this when I was producing the model. And because I was trying so many different things, I think I left the minimum part load ratio as 1, not knowing how it would effect the simulations.

(I am still working on finding out why the insulation thicknesses don't effect the simulation results as expected..)

From Input Output Reference Document (1.49 Group Setpoint Managers):

No two setpoint managers should use the same setpoint node for like control types. For the case when two setpoint managers place a setpoint on the same setpoint node (e.g., a temperature setpoint placed on the same node by two different setpoint managers), the setpoint value on the node is calculated by the last setpoint manager simulated. Within a specific type of setpoint manager (e.g., Scheduled), the setpoint managers are simulated in the order found in the input data file (idf) when viewed using a text editor. It is also possible for two different types of setpoint managers to place setpoints of like control variable on the same node. In this case, the order of simulation for the type of setpoint manager determines which setpoint manager is the last to write a setpoint value to the node. This conflict in setpoint node data is most likely to cause inaccurate simulation results. For this reason, a conflicting setpoint node name warning message is issued so that the conflict can be resolved. Duplicate setpoint node names found within a specific node list will not typically cause problems with the simulation (the same value is written twice to the same node). In this case a duplicate setpoint node name warning is issued, however, this could be an error in the spelling of the node name and should be corrected.