using CTRL function to ramp down fan

[gforney]

What the model suppose to do is:

Initially the fan is running, when a smoke detector activates it will 
allow a 20 seconds delay before turning off the fan.

The fan is turn off by slowly ramping down for 20 seconds before coming to 
a stand still.

The CTRL3 function is not working, the fan does not come to a stand still 
around the 20 seconds delay.

Thanks for your help.

Original issue reported on code.google.com by dntra2 on 2008-10-13 01:02:28

---

• _Attachment: box_test.out_

[gforney]

sorry attached the wrong file.  Please discard the above attachment.

Original issue reported on code.google.com by dntra2 on 2008-10-13 01:04:12

---

• _Attachment: box_test.data_

[gforney]

we'll take a look at it.

Original issue reported on code.google.com by drjfloyd on 2008-10-13 12:54:36

• Labels added: Application-FDS

[gforney]

From the User's Guide:

A CUSTOM function uses the numerical output of a DEVC along with a RAMP to determine

the output of the function.

You are trying to use the CUSTOM function with a CTRL as the input.  We should be 

trapping this as an error, but we are not (this has been fixed).  Also, the CUSTOM

function merely sets a TRUE or FALSE based on how the RAMP is evaluated (i.e. the 
numerical values of the RAMP are not used for anything other than determining TRUE

or FALSE).  So the FAN RAMP is not going to be multiple by the FAN RAMP DOWN.  The

CUSTOM function using FAN RAMP DOWN would only set whether or not the fan is 
active.  

In your case create a single time_delay function linked to the DEVC SD_1.  Have that

time delay give the total time delay you need to the fan being fully off.  Apply 
that control function to your fan surface.

Original issue reported on code.google.com by drjfloyd on 2008-10-13 14:48:14

[gforney]

Jason -- the warnings and error statement successfully trapped the improper input 
for the linux compile.

Original issue reported on code.google.com by mcgratta on 2008-10-13 15:17:55

[gforney]

Have you tested the fix since the release of 5.2.4?  If so please report back if the
fix has addressed your issue.

Original issue reported on code.google.com by drjfloyd on 2008-12-03 14:13:10

[gforney]

(No text was entered with this change)

Original issue reported on code.google.com by drjfloyd on 2009-03-13 15:28:34

[gforney]

(No text was entered with this change)

Original issue reported on code.google.com by drjfloyd on 2009-03-13 15:30:18