...
- Matlab Framework for Feedback Applications
- DONE:read EGU from PVs and display units wherever possible - DONE except matrix params and PID values (??? ask juhao)
- DONE:use new event API - see matlab prog. man. - DONE cant use one-shot, will stick with F1,F2 1Hz 5Hz 10Hz setup
- DONE:use lcaUtil_NewMonitorValue - DONE
- add code to read config PVs instead of xml file whereever possible (tolerances, dispersion)
- add limits checking on actuators, states, measurements - inlcuding checking TMIT on all measurements for validity? see notes on disc. w/Paul
- add readback of actuators and compare to desired value
- before starting loop, read current actuator value as initial value
- add error checking on devices - DONE upon init: reports severity of all act, states, meas PVs
- add error checking on communications, calculations -
- DONE:rename source files for flat file system (prefix=fb)
- DONE:add a Stop() function : DONE first cut- if anything goes wrong, STOP the feedback (if we try to take any corrective action our single-minded (threaded) matlab stops looping anyway)
- may need to check pulse-ids on all measurements and compare to be sure they are from same pulse - try this later when we have a 'real' pulse-id
- test all feedbacks individually on Kiosks, sunrays determine where best to run in control room.
- investigate long-term run (must be able to run well for at least a full shift 8 hours)
- investigate memory and processor usage, determine if they run well enough with more than one matlab/feedback instance at a time on a processor
- application to collect reference orbit data - TBD
...