Message-ID: <21913121.1075840449194.JavaMail.evans@thyme>
Date: Thu, 27 Jun 2002 01:45:00 -0700 (PDT)
From: mark.walker@enron.com
To: joe.chapman@enron.com, garth.ripton@enron.com
Subject: Operating State 29
Cc: mark.fisher@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bcc: mark.fisher@enron.com
X-From: Mark V Walker
X-To: Joe Chapman, Garth Ripton
X-cc: Mark Fisher
X-bcc: 
X-Folder: \mark fischer 7-12-02\Notes Folders\All documents
X-Origin: FISCHER-M
X-FileName: mark fischer 7-12-02 LNotes.nsf

Joe Chapman sent us an email listing a short textual description associated 
with each value of Operating State 29.  Some are easy to interpret (ex. 11 is 
"Feathering position") because they are a visible element on the state 
transition diagram in the controller document supplied by Garth.  Others 
aren't easy to interpret.   Where should we look to understand the triggering 
criteria for text strings associated with Operating states 0-6 and 13.   We 
are willing to do the work of reading the documentation if you can tell us 
what to read.  These values are labeled "Blade angle setpoint (all blades)",  
" Blade angle plus", "Blade angle minus",  "Blade angle stop", " Blade angle 
setpoint (single blades)", and "Manual speed setting".    I assume from these 
names and the fact that they are not common in the SCADA data that all but 
Blade angle stop are solely used for controller parameter changes or software 
changes.   We want to use Operating State 29 in our Statistical Process 
Control and reporting logic but the lack of understanding on these parameter 
values holds us back.