Dirk Zimoch
90a727c901
Most errors found with: codespell -L cach,thst,odly,aslo,parm,parms,inpu,ges,prset,pevent,ptd,pring,valu,noo,noe,ned,inout,ro,siz,froms,nd,fo,singl,sart,multy,tthe,allong,ment,inate,nodel,tring,alse,ture,thi,wille,numer Some more manually found (its -> it's) c++20: Do not use apostrophe (e.g. can't) in unquoted #error message
1.7 KiB
1.7 KiB
New afterIocRunning IOC Shell Command Added
This release incorporates PR #558 which added a new IOC shell command afterIocRunning. This command allows startup scripts to schedule arbitrary commands to be executed automatically after the IOC initialization phase (iocInit).
afterIocRunning allows you to write better-structured IOC shell files to include in your startup scripts without tracking where iocInit is located (and how IOC is deployed) e.g.:
- to achieve the best maintainability (e.g. encapsulation of the context into one file),
- to improve writing boot sequences,
- to improve IOC startup flexibility and scripting capabilities,
- it replaces the community
afterInitanddoAfterIocInitIOC shell commands, - community usage examples:
pf4filters.iocsh- enable/disable with a single comment (full description)- ALS-U autosave management
Features
- Define commands that run after IOC initialization completes.
- Executes following
iocInitandautosaveinitialization (important for proper PV configuration). - Supports any valid IOC shell command as an argument.
- Example usages:
afterIocRunning "dbpf <PV> <VAL>"afterIocRunning "date"afterIocRunning "dbpf $(P)EvtClkSource-Sel 'Upstream (fanout)'"afterIocRunning "dbpf $(P)Enable-Sel Enabled"