FDS does not create a "_devc_ctrl_log.csv" file; smoke detectors do not trigger #12201
-
I have a case with smoke detectors which record data, but never trigger. There is also no "[Casename]_devc_ctrl_log.csv" file. This is for a fire on a particular floor of a building. The exact same setup with fire, smoke detectors and temperature sensors works just fine on another floor of said building. I let the case run for around 250 seconds, but the detectors still do not trigger while logging > 90 % obscuration. I have compared the .fds files of the working case for the other floor with this one, but can not spot anything amiss. FDS version is 6.8.0. As I am unsure if I'm looking at a bug or PEBKAC error after all, I'm asking here first. Note: The "out of mesh" devices are semi-intentional/accepted and a product of Pyrosim's handling regarding scenarios and control logic (too complex to explain here), but should not cause any issue. Deactivating or removing them does not improve things.
If I simulate the entire building, not just a single floor, I get a "[Casename]_devc_ctrl_log.csv" file and the detectors trigger just fine. Could it be that FDS does not like meshes that do not start at or near z = 0, at least for devices with a trigger? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Please reopen this as the original question (as to why devices do not trigger if the mesh does not start at z = 0 m) remains unanswered. |
Beta Was this translation helpful? Give feedback.
After fixing the source code to get the devc log (see issue #12202), the devc log was showing all four devices changing state between 23 and 27 s.