Difference: RunControlTasks (1 vs. 18)

Revision 18
02 Jun 2005 - Main.SimonLang
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="RunControl"
 

Status and "to do" list for RunControl

  • error reporting in async record? report via alarm status, how to check?
Revision 17
19 Apr 2005 - Main.MathiasMuench
Line: 1 to 1
 

Status and "to do" list for RunControl

  • error reporting in async record? report via alarm status, how to check?
Line: 32 to 32
 
  • Complicated start procedure in trigconc crate. Make two "logical" systems out of it? Be careful, there is only one readout.
  • "shw" IOC works also for trigconc by adding the proper DB files, so it's a matter of naming. But sequencer needs parametrization of sub system name (right now "SHW" is hardcoded)
  • Switch on error logging from param and vme library in the proper place (where conLvme / conParam is called).
Changed:
<
<
  • Create a record for the state of one complete crate (most probably via gensub).
>
>
  • Create a record for the state of one complete crate (most probably via gensub). Was done with sub record.
  • generate database files and adl files from module list. Probably via msi -V?
 

META TOPICMOVED by="MathiasMuench" date="1110983868" from="Hadesdaq.RunControlToDo" to="Hadesdaq.RunControlTasks"
Revision 16
15 Apr 2005 - Main.MathiasMuench
Line: 1 to 1
 

Status and "to do" list for RunControl

  • error reporting in async record? report via alarm status, how to check?
Line: 32 to 32
 
  • Complicated start procedure in trigconc crate. Make two "logical" systems out of it? Be careful, there is only one readout.
  • "shw" IOC works also for trigconc by adding the proper DB files, so it's a matter of naming. But sequencer needs parametrization of sub system name (right now "SHW" is hardcoded)
  • Switch on error logging from param and vme library in the proper place (where conLvme / conParam is called).
Added:
>
>
  • Create a record for the state of one complete crate (most probably via gensub).
 

META TOPICMOVED by="MathiasMuench" date="1110983868" from="Hadesdaq.RunControlToDo" to="Hadesdaq.RunControlTasks"
Revision 15
14 Apr 2005 - Main.MathiasMuench
Line: 1 to 1
 

Status and "to do" list for RunControl

  • error reporting in async record? report via alarm status, how to check?
Line: 29 to 29
 
  • Error reporting is solved, works via errorlog on epics and syslog outside, both go to syslog.
  • Error handling still completely void
  • Shower works with sequencer that is configured via Param, no second implementation yet.
Changed:
<
<
  • Complicated start procedure in trigconc crate. Make two "logical" systems out of it?
>
>
  • Complicated start procedure in trigconc crate. Make two "logical" systems out of it? Be careful, there is only one readout.
 
  • "shw" IOC works also for trigconc by adding the proper DB files, so it's a matter of naming. But sequencer needs parametrization of sub system name (right now "SHW" is hardcoded)
Changed:
<
<

frown So no chance to get it running today.
>
>
  • Switch on error logging from param and vme library in the proper place (where conLvme / conParam is called).
 

META TOPICMOVED by="MathiasMuench" date="1110983868" from="Hadesdaq.RunControlToDo" to="Hadesdaq.RunControlTasks"
Revision 14
16 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
Added:
>
>

Status and "to do" list for RunControl

 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 11 to 13
 
      • Sequencer breaks somewhat the idea, e.g. asyncronous processing / PACT status is not usable as in IOC.
      • DB records need special record types for sequential fan out or status fan in.
  • Next steps (which one first?)
Changed:
<
<
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
>
>
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
 
  • Move syslog initialization from device support init to ioc init (main) Even better: Move it to function and register this with IOC shell.
  • Epics Error logging via syslog basically works,
Changed:
<
<
but rcState is the wrong place. Put it into *Main.cpp or make
>
>
but rcState is the wrong place. Put it into *Main.cpp or make
  an iocsh command from it
  • How to wait for completion of control command in crate
  • Success/Fail messages for standard functions are done in blubctrl.c, but not in ioc.
Changed:
<
<
  • IOC/Sequencer works verly nicely as replacement for *ctrl/script in shower. Now generalize it so that it can work in different systems. Where to get parameters? Channel Access or Parameter Library?
>
>
  • IOC/Sequencer works verly nicely as replacement for *ctrl/script in shower. Now generalize it so that it can work in different systems. Where to get parameters? Channel Access or Parameter Library?
 
    • create function that gets list of units
Changed:
<
<
    • do dynamic assignment that uses this list
>
>
    • do dynamic assignment that uses this list

  • Error reporting is solved, works via errorlog on epics and syslog outside, both go to syslog.
  • Error handling still completely void
  • Shower works with sequencer that is configured via Param, no second implementation yet.
  • Complicated start procedure in trigconc crate. Make two "logical" systems out of it?
  • "shw" IOC works also for trigconc by adding the proper DB files, so it's a matter of naming. But sequencer needs parametrization of sub system name (right now "SHW" is hardcoded)

frown So no chance to get it running today.
 
Added:
>
>
META TOPICMOVED by="MathiasMuench" date="1110983868" from="Hadesdaq.RunControlToDo" to="Hadesdaq.RunControlTasks"
Revision 13
14 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 19 to 19
  an iocsh command from it
  • How to wait for completion of control command in crate
  • Success/Fail messages for standard functions are done in blubctrl.c, but not in ioc.
Added:
>
>

  • IOC/Sequencer works verly nicely as replacement for *ctrl/script in shower. Now generalize it so that it can work in different systems. Where to get parameters? Channel Access or Parameter Library?
    • create function that gets list of units
    • do dynamic assignment that uses this list
Revision 12
14 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 18 to 18
  but rcState is the wrong place. Put it into *Main.cpp or make an iocsh command from it
  • How to wait for completion of control command in crate
Changed:
<
<
  • Success/Fail messages for standard functions are done in blubctrl.c, but not in ioc.
>
>
  • Success/Fail messages for standard functions are done in blubctrl.c, but not in ioc.
Revision 11
10 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 13 to 13
 
  • Next steps (which one first?)
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
Changed:
<
<
  • Move syslog initialization from device support init to ioc init (main) Even better: Move it to function and register this with IOC shell.
>
>
  • Move syslog initialization from device support init to ioc init (main) Even better: Move it to function and register this with IOC shell.
 
  • Epics Error logging via syslog basically works,
Changed:
<
<
but rcState is the wrong place. Put it into *Main.cpp or make
>
>
but rcState is the wrong place. Put it into *Main.cpp or make
  an iocsh command from it
Added:
>
>
  • How to wait for completion of control command in crate
  • Success/Fail messages for standard functions are done in blubctrl.c, but not in ioc.
 
Revision 10
10 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 14 to 14
 
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
  • Move syslog initialization from device support init to ioc init (main) Even better: Move it to function and register this with IOC shell.
Added:
>
>
  • Epics Error logging via syslog basically works, but rcState is the wrong place. Put it into *Main.cpp or make an iocsh command from it
 
Revision 9
10 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Line: 13 to 13
 
  • Next steps (which one first?)
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
Added:
>
>
  • Move syslog initialization from device support init to ioc init (main) Even better: Move it to function and register this with IOC shell.
Revision 8
09 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Changed:
<
<
  • IOC for shw ready, test it in old runctrl
>
>
  • IOC for shw ready, test it in old runctrl
 
  • Control and State of single modules works nicely, how to make larger entities? Statement: init and reset can be done completely in parallel, start and stop need some means of sequencing. Some kind of aggregation via dfanout/fanout may work, but strange to sequence. How to do error handling? Let a sequencer run in each crate.
Changed:
<
<

-- MathiasMuench - 18 Feb 2005
>
>
  • Seqencer for shw ready, tested with tcl-run-control.
  • Things to discuss, find pros/cons:
    • One sequencer for each crate? For the whole system?
    • Use sequencer programs for "fan in/fan out" from crate/system to single module or use DB records.
      • Sequencer breaks somewhat the idea, e.g. asyncronous processing / PACT status is not usable as in IOC.
      • DB records need special record types for sequential fan out or status fan in.
  • Next steps (which one first?)
    • Make IOC/sequencer for more crates, generalize it
    • Do proper error handling and reporting
Revision 7
03 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
  • IOC for shw ready, test it in old runctrl
Added:
>
>
  • Control and State of single modules works nicely, how to make larger entities? Statement: init and reset can be done completely in parallel, start and stop need some means of sequencing. Some kind of aggregation via dfanout/fanout may work, but strange to sequence. How to do error handling? Let a sequencer run in each crate.
 

-- MathiasMuench - 18 Feb 2005
Revision 6
02 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
Added:
>
>
  • IOC for shw ready, test it in old runctrl
 

-- MathiasMuench - 18 Feb 2005
Revision 5
01 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
Added:
>
>
  • mu_lib produces seg fault when called with invalid DAQ_SETUP
 

-- MathiasMuench - 18 Feb 2005
Revision 4
01 Mar 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
Changed:
<
<
  • snc compiler works, but no runtime
>
>
  • snc compiler works, but no runtime If cas and gdd are removed from base/src/Makefile, also remove them from configure/CONFIG_BASE.
 

-- MathiasMuench - 18 Feb 2005
Revision 3
28 Feb 2005 - Main.MathiasMuench
Line: 1 to 1
 
  • error reporting in async record? report via alarm status, how to check?
Added:
>
>
  • snc compiler works, but no runtime
 

-- MathiasMuench - 18 Feb 2005
Revision 2
25 Feb 2005 - Main.MathiasMuench
Line: 1 to 1
Changed:
<
<
  • error reporting in async record? report via alarm status, how to check?
>
>
  • error reporting in async record? report via alarm status, how to check?
 

-- MathiasMuench - 18 Feb 2005
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)