Anafaze-Project-CheckList: Difference between revisions
Jump to navigation
Jump to search
New page: == Issues: Must Corrects == == Issues: Can be delayed == == Issues: Future Features == |
No edit summary |
||
| Line 1: | Line 1: | ||
== Issues: Must Corrects == | == Issues: Must Corrects == | ||
*Error handling in new routines | |||
*Verify logfile operations use LONG integers. Will run out of room if is only 16 bit ints | |||
*Verify user prompt erasers at above a certain length of text - prevent overflow errors! | |||
*Highlight row executing on profile chart display on trajectory form | |||
*Channel message filter - option to display only messages for the particular channel and IO timer above.... | |||
*wait function-for fast as possible ramping up / down | |||
*implement COMMAND function for auxillary I/O - example flipper valve fan cooling | |||
*implement NOTIFY command - allow user to notify of reaching TIME or TEMP value | |||
*Communication error should be flagged if communications goes down - does not do this right now | |||
| Line 8: | Line 16: | ||
== Issues: Can be delayed == | == 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 | |||
== Issues: Future Features == | |||
*Profile Download to controller | |||
Revision as of 13:54, 21 November 2008
Issues: Must Corrects
- Error handling in new routines
- Verify logfile operations use LONG integers. Will run out of room if is only 16 bit ints
- Verify user prompt erasers at above a certain length of text - prevent overflow errors!
- Highlight row executing on profile chart display on trajectory form
- Channel message filter - option to display only messages for the particular channel and IO timer above....
- wait function-for fast as possible ramping up / down
- implement COMMAND function for auxillary I/O - example flipper valve fan cooling
- implement NOTIFY command - allow user to notify of reaching TIME or TEMP value
- Communication error should be flagged if communications goes down - does not do this right now
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
Issues: Future Features
- Profile Download to controller