Problem using the multiplex function in HVAC-module

[KarinaA]

Hi all,

(Almost) everytime I try to move a component within the multiplex which is just inside the zone (and attached to a room within the multiplex, see figure), I recieve an error message saying something like "the VE MFC Application has encountered a problem and needs to close". Is this a common bug?

Also, is there a way of expanding the multiplex zone? For instance, if I have a 3x3 square grid and like to expand it to a 5x5 square grid (to involve some additional components), is that possible? From what I have found, I can only get a larger multiplex-box/zone by deleting the last one and create a new one, but then, all the layers will dissappear.

Thanks,
Karina

[PCully]

Hi,

Sorry you are having trouble with this. Can I check you are running <VE> 6.0.3? This is regarded by serious users of the multiplex feature as the first stable version.

We are aware of similar issues where the <VE. can crash when copying components/controllers into or out of a multiplex. I have an early development version of <VE> to be released later this year and it appears some of these issues have been addressed already. In the meantime i would suggest you don't copy into or out of multiplexes for now.

Unfortunately there is no way to expand the multiplex area at the moment. This feature may be added in a later version of <VE> but does not feature in any development plans at the moment. I wall raise this in the team to try move it up the priority list.

Hope this helps a bit, sorry I can't do any more for you at the moment.

Phil

[KarinaA]

Hi Phil,

Thank you for your answer! I am running version 6.0.3. I finally managed to avoid it fram crashing and now I have completed the simulation. I am doing a simulation on a building which has about 190 zones so it might have been my coomputer that can't handle the large amount of data. I must say, despite the problems I had, the multiplex function is really great!

Best Regards,
Karina

[JosephG]

I'm having repeated crashes with multiplexing in V605, when trying to edit direct acting heaters in a multiplex containing 90 zones. I'm wondering if anyone out there is still having stability problems when using multiplexing. It's also taking about 30 seconds to open the edit window for a room object in that same multiplex.

It's kind of ironic when you think about it, multiplexing was created to simplify the task of creating editing multiple rooms within ApacheHVAC so you're not stuck doing the same editing over and over, and now it seems editing too many rooms is precisely my problem.

[KarinaA]

Hi Joseph,

I am having the same problem, also in v6.0.5, but with radiators (quite the same thing) and this was for a multiplex with 90 zones as well. It can take up to 1 min 45 sek until the edit window opens, but then, my computer is not as fast as yours I guess. Also, a strange thing happens! Sometimes the room within the multiplex turns black instead of green and when I select it in order to edit it, the program crashes. Really strange.

Cheers,
Karina

[JosephG]

Did you have it before V605? I haven't really had to push the limits on ApacheHVAC in V6 until now, and I figured I'd get more work done by using multiplexing and committed to project deadlines as I figured "I know how to use it, and I understand how it works", and now I'm starting to regret it there's bugs in that as well. I would have spent less time nights troubleshooting the whole thing if I just copied the rooms 90 times and connected them, at least I know *that* works.

[JosephG]

BTW I found a way around its repeated crashes if you want to edit a highly repeated multiplex.

I've tried splitting my multiplex in two to have 2 multiplexes of 45 rooms each, but it still crashes. My guess is that there is probably a maximum number of rooms to be attached to a multiplex, but honestly I don't have time to debug it. That should be IES's job before a release, and the software should not allow you to do something that would make it "reliably" crash. There should be a limit to the number of rooms assignable to a multiplex if it's going to crash otherwise.

Anyway, here's the way out of this mess. You're not going to like it if you have lots of editing done, but it's better than crashing and being stuck. (1) Select the room in question, (2) delete it, (3) save, (4) add it again, (5) apply the room names to it using room groups, and (6) add your radiators with the new configuration you desire. Make sure you use setpoint control and not proportional control, as only setpoint control has allows using the room in which the radiator is located as input for control, proportional requires that each of your rooms be selected one by one in the multiplex which is not only a pain in the ass but it will probably crash.

[KarinaA]

Hi again,

I started using APHVAC in v6.0.2. The program has definitely improved since then. It crashed alot back then. For example, whenever I selected a component within a multiplex and moved it, the program crashed. Also, it could crash by only saving changes made to a radiator. The problems that you (and I) have, they've been around at least since I started using the multiplex-function.

The solution you suggest, I'll definitely try that! I have used proportional control before so this might work better. Thanks for the tip!

/Karina

[geshen516]

this problem still exists in the latest version..
scare me.

[patpease]

Hi,

has there been a resolution to this bug? I have a multiplex of 91 rooms that works fine. But then one with only 27 is crashing whenever I go to edit any of the controllers inside it. I've tried deleting the controllers and re-adding, but no luck.

Thanks