Anafaze-Project-CheckList

Issues: Must Corrects / Checks

• Notify-time-Temp-Implementation - allow user to notify of reaching TIME or TEMP value

• Resolve Tom Morris editing issues - acts like no thermocouple extremes are set before parsing profile

Messaging

• Alarm-Messages
• Wait state messaging: when starting wait | when wait complete
• "w" action is reset by setting equal start and stop times

Log File related

• Verify logfile operations use LONG integers. Will run out of room if is only 16 bit ints
• previous log file can not be deleted when software is open/running. Appears file not closed somewhere.
• too many files open error = #67 - see error 424
• error = 424 - object required - in logging part of control loop - see error #67 above

Chart related

• No log trace shown when number of samples in the logfile is small
• Chart shows log trace of previous large data set when new log file is reset and has nothing in it - when software rebooted -> shows nothing => update missing!
• display of Number of log file points on chart does refresh when the chart is repainted
• reset log file / time does not put new stuff up on plot

User interface issues

• Add close after click code in mnu routines - otherwise the user has to consciously close
• Channel message filter - option to display only messages for the particular channel and IO timer above
• Allow global setting of email alert addresses from MultiTraj menus
• Highlight row executing on profile chart display on trajectory form
• Mask channel error messages selection
• Set XXXX menu title = invisible | also its drop down menu - leave in for later expansion if needed.
• Lock out AutoStart settings of ganged channels once first channel is gang is set. - to prevent setting up the gang start more than once.

Security issues

• Add "time bomb" security measure - in control loop: conditional KeyCheck based on outcome of low probability random number generator - should have mean time between checks = 1 month.

software operational issues

• Computer temperature readouts do not match controller. They are 1 I/O cycle behind the controller.
• Communication error should be flagged if communications goes down - does not do this right now
• Error handling in new routines
• Verify user prompt erasers at above a certain length of text - prevent overflow errors!
• Make sure all routines use variable CONTROLLER ADDRESS instead of numeric constant

Issues: Can be delayed

• Logfile Rendering becomes low quality >4000 logfile points
• Implement condition rerendering of chart - cut down processing time for larger renders - example 1000 point render
• route channel prompts of ganged messages to all gang channel prompts
• Temperature bumping - so temperature can be actively bumped up under the Trajectory form

Issues: Future Features

• Profile Download to controller
• WebCam - to allow photo being taken of art object setup in oven. - allow for autodocumenting in a database library online!
• Need some sort of extensible interface that can input / output messages. Allow users to write their own code to do custom functions and fit this project into other control projects as a subpiece.
• Command-Column-Implementation function for auxillary I/O - example flipper valve fan cooling

Resolved Issues

• Wait-Function-Implementation-for fast as possible ramping up / down Temperature-Profile-Notes

Resolved with need of more verification testing

• need more characters in command column - perhaps is easier to increase field size in all columns?

• checksum should be reconned from end of file not from the beginning: thus changing field size in future will not induce checksum routine changes in future | or put in the header ?