PACiS GTW GTW/EN T/C40, Technical Manual

Page: 137 / 298

Communication GTW/EN CT/C40
PACiS Gateway Page 29/64
CAUTION: IF THE DIRECTORY IS FULL, WHILE THE OLDEST FILE IS LOCKED BY
SCADA (FILE SELECTED AND NOT ACKNOWLEDGED) IT IS NOT
POSSIBLE TO RENAME THE NEW .TMP_READY IN .SOE104 IN THIS
CASE, IF THIS SITUATION LAST A VERY LONG TIME, THE NUMBER
OF .TMP_READY FILE CAN INCREASE, WITHOUT LIMIT. SUCH A
SITUATION SHOULD NOT HAPPEN IF THERE’S NO BUG IN THE
SCADA …
Remark: For dll point of view there’s no correlation between the way a digital
input is sent to SCADA, and the way it is stored in the SOE file: an
event, if configured as recorded, is always time tagged in the SOE file
(even if in SCE user chooses to sent it with no date to the SCADA).
3.8 Disturbance file management
Disturbances files are not produced by the gateway. The producer has just to put the files in
the disturbance directory, naming them 1.tmp_ready, 2. tmp_ready, etc … If file x.DIS104 is
present when producer starts, the first file he has to add is x+1.tmp_ready. Tmp_ready files
are after managed exactly as SOE files, except their extension is DIS104.