[esp-r] Re: Using Temporal Data Feature

[Geissler Achim]

Hi Denis

maybe this can help, if you have not already solved the problem. The set-up outlined below worked for me. The point may be that some entries in the tdf have more than one column of data attached. So, you need to give the controller the item number, not necessarily the data-column number.

Achim

===

Item 5 in .tdf

*items
*tag,Setp<<zone>>  
*type,SETPTTT 
*menu,Set point temp:                 
*aide,Set point temp                      
*other,   0   1
*fields, 1
REAL  1 29      0.000   -101.000    101.000  Set point temperature (C) :        
*end_item

====
Control file: <<item number of setpoint entry in .tdf>>

Zone control for occupancy-driven heating
   4  # No. of functions
* Control function    1
# senses dry bulb temperature in <<zone>>.
    1    0    0    0  # sensor data
# actuates the air point in KR_SE.
    1    0    0  # actuator data
    1 # No. day types
    1  365  # valid Thu-01-Jan - Thu-31-Dec
     1  # No. of periods in day: weekdays    
    0   11   0.000  # ctl type, law (reads from temporal file item. 5), start @
     12.  # No. of data items
  2950.000 0.000 0.000 0.000 1.000 3.000 -5.000 <<5.000>> 0.000 0.000 1.000 0.000

  
====
Configuration file (.cfg)

*tdf  ../nets/<<file>>.tdfa
# tdf item id, item type, <related zone>, <related surface> 
...    
Setp<<zone>>   SETPTTT   loop_1          ALL            <<fifth item in tdf file>>
...


===



-----Ursprüngliche Nachricht-----
Von: esp-r-bounces at lists.strath.ac.uk [mailto:esp-r-bounces at lists.strath.ac.uk] Im Auftrag von Denis Fan
Gesendet: Dienstag, 4. Oktober 2011 18:14
An: esp-r at lists.strath.ac.uk
Betreff: [esp-r] Using Temporal Data Feature

Hi everyone,

I tried to use the temporal data feature to link external temperature, as well as heating and cooling setpoints in my ESP-r model. I have successfully linked the external temperature (DBTEXTT) without any problem, but not with the heating and cooling setpoints (HTCLSETP). I hope someone can help me out on this.

I can view the setpoints data  from the view/edit temporal entities - in this case I assumed the tdfa file is fine and shouldn't has any conflicts in its formatting. I checked I have added the temporal entity for HTCLSETP and is linked to a 'Match sensed value' control loop for a particular zone (zone1). The specification of this control function is as follows:

=====
The sensor for function  9 senses dry bulb temperature in zone1.
The actuator for function 9  is the air point in zone1.
There have been  1 day types defined.
Day type  1 is valid Fri-01-Jan to Fri-31-Dec, 2010 with  1 periods.
Per|Start|Sensing  |Actuating  | Control law       | Data
   1  0.00 db temp   > flux      Sensed temp setpts  2.0 3.0
Match sensed values (ideal:2 setpoints) heating setpt col. no. in tdf
2.00 cooling setpt
col. no. in tdf 3.000

....

Zone to contol loop linkages:
 zone ( 1) zone1      << control  9

=====

Values 2.0 and 3.0 are used here, as column 2 and 3 from the tdfa file has the heating and cooling setpoint values respectively. I run a simulation, but the zone air temperature doesn't matched with the setpoints, and the result is more behaving like using free floating.
Wondering whether I have done something wrong? Many thanks.

Regards,
Denis

_______________________________________________
esp-r mailing list
esp-r at lists.strath.ac.uk
http://lists.strath.ac.uk/mailman/listinfo/esp-r